Hello Ashutosh Jadhav,
Why the mismatch occurs
- Azure Activity Log categorizes most resource-level operations (including Microsoft.Security resource provider actions) under Administrative, not Security.
- The policy definition uses "equals": "Security" for the category field, which does not match the real signal type in alerts.
How to resolve
You have two options:
Option 1: Modify the Policy Definition
- Clone the built-in policy and create a custom policy.
- In the definition, change:
"field": "Microsoft.Insights/ActivityLogAlerts/condition.allOf[*].equals",
"equals": "Security"
To
"equals": "Administrative"
Assign your custom policy instead of the built-in one.
Option 2: Accept Built-in Limitation
- Keep the alerts with category = Administrative (correct for compliance in practice).
- Document the deviation and mark the policy as not applicable or override compliance in Defender for Cloud.
As a best practice, always verify the actual Activity Log category for the operations using Azure Activity Log schema and for Microsoft.Security operations like policies/write or securitySolutions/delete, the category is Administrative.
Thanks.
Kindly check and let us know if you have further questions?