AZ-305 ยท Authorization, secrets and keys
Designing Azure RBAC: who, what and where
Built-in vs custom roles, scope (management group, subscription, resource group, resource), role assignment to groups, control plane vs data plane roles, deny assignments, least privilege.
Key points
- Role assignment = security principal (prefer a group) + role definition (built-in first) + scope.
- Scopes: management group > subscription > resource group > resource; inherited downward.
- Actions/NotActions: control plane; DataActions/NotDataActions: data plane.
- Deny assignments: block even granted actions; in generally available scenarios only Azure creates them (e.g. deployment stacks).
- Least privilege: smallest role, narrowest scope.
Source: https://learn.microsoft.com/en-us/azure/role-based-access-control/scope-overview
Practice questions
Which scope sits above subscriptions in the Azure RBAC hierarchy?
- Resource group
- Management group
- Administrative unit
- Resource provider
Show answer
Answer: B. Management group
Scopes, from broadest to narrowest, are management group, subscription, resource group and resource. A management group can hold many subscriptions, so a role assigned there flows down to all of them. A Microsoft Entra administrative unit is an Entra ID concept, not an Azure RBAC scope.
Which statements about Azure deny assignments are correct?
- They block actions even when a role assignment grants them
- They can exclude specific principals from the denial
- Azure creates them, for example for deployment stack deny settings
- Administrators create them directly with az role assignment create
- They can only be applied at the individual resource scope
Show answer
Answer: A. They block actions even when a role assignment grants them, B. They can exclude specific principals from the denial, C. Azure creates them, for example for deployment stack deny settings
Deny assignments block the listed actions even if a role assignment grants them, they can exclude specific principals, and in generally available scenarios Azure creates and manages them (for example when a deployment stack uses deny settings). You cannot create your own with a role assignment command, and they are not limited to the resource scope.
A user with the Owner role on a subscription can automatically read blob contents through Microsoft Entra authorization, without using account keys.
Show answer
Answer: False
False. Owner grants all control-plane Actions but no DataActions. Reading blob data with Entra authorization needs a data-plane role such as Storage Blob Data Reader. Owner can list the account keys, but that is Shared Key access, not Entra authorization.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
