Azure blocks at create and update, and a deny does not touch what already exists
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
The library holds 30 Azure guardrails across 10 risk classes, written in Azure Policy (built-in definitions), Azure RBAC deny assignments (created by deployment stacks), Azure resource locks, Management group assignment. 28 of them have a documented way to test the effect before enforcing.
All guardrails ยท Azure mechanisms
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, while modify and deployIfNotExists change or deploy settings instead of blocking, and audit only warns. Effects are evaluated in order, so an earlier modify or append can change the request so a deny does not trigger. Existing resources that match are only marked noncompliant. Assignments cascade from management groups by inheritance, and scopes excluded with notScopes are not evaluated at all.
Three other mechanisms sit beside it. Resource locks block deletion or modification at a subscription, resource group or resource and override user permissions, but they apply only to control plane operations. Deny assignments attach deny actions to principals at a scope; Azure creates them for generally available scenarios such as deployment stack deny settings, and customer-managed deny assignments are in private preview. Management groups organize subscriptions into a hierarchy up to six levels deep. The library holds 30 Azure entries, 27 of them Azure Policy.
The mechanisms
- Azure Policy (built-in definitions)Azure Policy evaluates resource create and update requests against assigned policy definitions.
- Azure RBAC deny assignments (created by deployment stacks)A deny assignment attaches a set of deny actions to a user, group or service principal at a scope.
- Azure resource locksA lock on a subscription, resource group or resource blocks deletion (CanNotDelete) or modification and deletion (ReadOnly) of the locked scope.
- Management group assignmentManagement groups organize subscriptions into a hierarchy so that policy and access assigned on a management group cascade to all its subscriptions by inheritance.
The 30 entries
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.
Related pages
Sources
- Azure Policy (built-in definitions), read 10 Nov 2026
- Azure RBAC deny assignments (created by deployment stacks), read 10 Nov 2026
- Azure resource locks, read 10 Nov 2026
- Management group assignment, read 10 Nov 2026
Last reviewed 16 Nov 2026.