Azure RBAC deny assignments (created by deployment stacks): what it can block and where it stops
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Azure RBAC deny assignments (created by deployment stacks) is a Azure mechanism. A deny assignment attaches a set of deny actions to a user, group or service principal at a scope. It applies to principals named in the deny assignment (all principals when the zero GUID is used), on the managed resources and optionally their child scopes.
All mechanisms ยท Azure guardrails
A deny assignment attaches a set of deny actions to a user, group or service principal at a scope. Microsoft documents that Azure creates and manages them for generally available scenarios, for example when you set deny settings on a deployment stack.
A deny assignment attaches a set of deny actions to a user, group or service principal at a scope. Microsoft documents that Azure creates and manages them for generally available scenarios, for example when deny settings are set on a deployment stack. Customer-managed deny assignments are in private preview.
Limits: deployment stack deny settings cover only resources the template defines explicitly, a stack can exclude at most five principals, and deny settings can exclude up to 200 role-based management actions. No simulation or dry run was found for deny assignments on 2026-11-10. 1 library entry uses this mechanism.
Documented limits
- Customer-managed deny assignments are in private preview; for generally available scenarios Azure creates and manages them. (source)
- Deployment stack deny settings cover only resources the template defines explicitly. (source)
- A deployment stack can exclude at most five principals from its deny settings. (source)
- Deny settings can exclude up to 200 role-based management actions. (source)
Testing before enforcement
none found on 2026-11-10
The 1 library entry written in it
- Deployment stack deny settings (Azure RBAC deny assignment)Azure, Azure RBAC deny assignments (created by deployment stacks), organization integrity
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 RBAC deny assignments (created by deployment stacks), read 10 Nov 2026
- Limit, read 10 Nov 2026
Last reviewed 16 Nov 2026.