Skip to content
Cloud Governance Tools

Azure Policy (built-in definitions): what it can block and where it stops

Azure Policy (built-in definitions) is a Azure mechanism. Azure Policy evaluates resource create and update requests against assigned policy definitions. It applies to resources at the scope of the assignment (management group, subscription, resource group) and their children, except notScopes and exemptions.

All mechanisms ยท Azure guardrails

Azure Policy evaluates resource create and update requests against assigned policy definitions. With the deny effect, a matching request is stopped before it reaches the resource provider; other effects such as modify and deployIfNotExists change or deploy settings instead of blocking.

Azure Policy evaluates create and update requests against assigned definitions. With the deny effect a matching request is stopped before it reaches the resource provider; modify and deployIfNotExists change or deploy settings instead. It applies at the scope of the assignment (management group, subscription or resource group) and below, except notScopes and exemptions.

Limits: deny acts on create and update, so existing matching resources are only marked noncompliant, and denyAction does not protect child and extension resources when a delete targets the parent. To test, set enforcementMode to DoNotEnforce on the assignment, or assign with the audit effect first. 27 library entries use Azure Policy, taken from the Azure/azure-policy repository.

Documented limits

  • Deny acts on create and update requests; existing resources that match are only marked non-compliant. (source)
  • Scopes excluded with notScopes are not evaluated at all. (source)
  • Effects are evaluated in order, and an earlier modify or append can change the request so a deny does not trigger. (source)
  • denyAction does not protect child and extension resources when the delete targets the parent. (source)

Testing before enforcement

Set enforcementMode to DoNotEnforce on the assignment to evaluate it before enforcement; the audit effect separately creates a warning event without stopping the request. (source)

The 27 library entries written in it

Where Act is behind

Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.

Sources

  1. Azure Policy (built-in definitions), read 10 Nov 2026
  2. Limit, read 10 Nov 2026
  3. Limit, read 10 Nov 2026
  4. Limit, read 10 Nov 2026
  5. Testing, read 10 Nov 2026

Last reviewed 16 Nov 2026.