Deny assignment
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
An Azure RBAC object that attaches a set of deny actions to a user, group or service principal at a scope. It blocks actions even when a role assignment grants them. In generally available scenarios, Azure creates and manages them.
An example, sourced
Microsoft documents that a deny assignment "attaches a set of deny actions to a user, group, or service principal at a particular scope for the purpose of denying access." Customer-managed deny assignments are in private preview, and for generally available scenarios Azure creates them, for example when deploying a deployment stack with deny settings. The page lists deny assignment properties that include excluded principals and excluded control plane and data plane actions, so a deny can carry its own exceptions.
Why it matters here
You cannot write a deny assignment directly in general availability. The route to one is a deployment stack, so plan it in your infrastructure code. Because only Azure creates these in general availability, find the deployment stack that owns one before you try to work around it. Its deny settings, not a hand-written rule, define the block.
Related pages
Sources
- https://learn.microsoft.com/en-us/azure/role-based-access-control/deny-assignments, read 10 Nov 2026
Last reviewed 16 Nov 2026.