Azure Management Groups: Centralized Policy and RBAC Across Subscriptions
A company has five Azure subscriptions, each managed by a different department. The IT governance team needs to enforce a single set of compliance policies (e.g., allowed VM SKUs) and assign a specific role to a central security team across all subscriptions. The goal is to minimize administrative overhead. Which Azure component should the governance team use as the scope for these assignments?
Quick Answer
The answer is to place all subscriptions under a single management group and assign policies and roles at that group level. This works because management groups create a hierarchical scope above subscriptions, allowing you to apply Azure Policy and RBAC assignments centrally; any policy or role set at the management group level is automatically inherited by all child subscriptions, which eliminates the need for repetitive per-subscription configurations. On the AZ-900 exam, this scenario tests your understanding of how management groups enable centralized governance across multiple subscriptions, and a common trap is to mistakenly choose Azure Policy itself or a single subscription as the scope—remember that management groups are the container that aggregates subscriptions for bulk assignments. A useful memory tip: think of a management group as a “master folder” for subscriptions—set rules once in the folder, and every file inside follows them.
⚠ Common exam trap
Candidates often think resource groups are the natural scope for governance, but management groups are designed specifically for cross-subscription policy and RBAC inheritance, making them the correct choice for minimizing overhead across multiple subscriptions.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Place all subscriptions under a single management group and assign policies and roles at that management group level.
Management groups provide a hierarchical scope above subscriptions, enabling centralized governance. By placing all five subscriptions under a single management group, the IT governance team can assign Azure Policy definitions (e.g., allowed VM SKUs) and role-based access control (RBAC) roles (e.g., for the security team) once at that management group level. This inheritance automatically applies the policies and roles to all child subscriptions, minimizing administrative overhead compared to per-subscription or per-resource-group assignments.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Assign the policies and role at each subscription level individually.
Why it's wrong here
This option is possible but not efficient because it requires repeating the same assignments across five subscriptions, increasing administrative overhead and potential for inconsistencies.
When this WOULD be correct
If the question stated that each subscription requires unique compliance policies or roles due to differing departmental needs, and the goal is to enforce per-subscription governance without inheritance, then assigning at each subscription level would be appropriate.
- ✗
Create a resource group in each subscription and assign policies and roles at the resource group level.
Why it's wrong here
Resource groups exist within a single subscription and cannot span subscriptions. This approach would not apply assignments to all subscriptions from a single point; you would still need to manage each subscription separately.
When this WOULD be correct
If the question specified that compliance policies and role assignments need to vary per department or per workload, and each department's resources are isolated within separate resource groups, then assigning at the resource group level would be correct. For example, 'A company has five Azure subscriptions, each containing multiple resource groups for different projects. The governance team needs to enforce different policies for each project team within a subscription.'
- ✓
Place all subscriptions under a single management group and assign policies and roles at that management group level.
Why this is correct
A management group can contain multiple subscriptions. Assignments made at the management group level are inherited by all subscriptions within it, providing a single, centralized scope for enforcement. This minimizes administrative overhead.
- ✗
Create an Azure Blueprint definition and apply it to each subscription separately.
Why it's wrong here
Azure Blueprints are designed for orchestrating the deployment of resource templates, policies, and role assignments. However, to apply a blueprint to multiple subscriptions, you must create a separate blueprint assignment for each subscription, which creates more overhead than using a management group.
When this WOULD be correct
A company needs to deploy a consistent set of Azure resources (e.g., a network topology, a set of VMs with specific configurations) across multiple subscriptions, and the resources must be deployed as a single, versioned package that can be updated centrally. In this case, an Azure Blueprint would be the correct component to define and apply the resource templates and policies together.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-900 exam frequently reuses these exact scenarios with slightly different constraints.
✓Place all subscriptions under a single management group and assign policies and roles at that management group level.Correct answer▾
Why this is correct
A management group can contain multiple subscriptions. Assignments made at the management group level are inherited by all subscriptions within it, providing a single, centralized scope for enforcement. This minimizes administrative overhead.
✗Assign the policies and role at each subscription level individually.Wrong answer — click to see why▾
Why this is wrong here
Assigning policies and roles at each subscription individually creates high administrative overhead, contradicting the goal to minimize it, and does not leverage Azure's hierarchical management group structure for centralized governance.
★ When this WOULD be the correct answer
If the question stated that each subscription requires unique compliance policies or roles due to differing departmental needs, and the goal is to enforce per-subscription governance without inheritance, then assigning at each subscription level would be appropriate.
Why candidates choose this
Candidates may think that since each subscription is managed by a different department, individual assignments are necessary, overlooking the management group capability to apply policies and roles across multiple subscriptions with a single assignment.
✗Create a resource group in each subscription and assign policies and roles at the resource group level.Wrong answer — click to see why▾
Why this is wrong here
Assigning policies and roles at the resource group level does not scale across multiple subscriptions; it requires repeating the assignment in each subscription, increasing administrative overhead. The goal is to enforce policies across all subscriptions with minimal overhead, which management groups achieve by inheritance.
★ When this WOULD be the correct answer
If the question specified that compliance policies and role assignments need to vary per department or per workload, and each department's resources are isolated within separate resource groups, then assigning at the resource group level would be correct. For example, 'A company has five Azure subscriptions, each containing multiple resource groups for different projects. The governance team needs to enforce different policies for each project team within a subscription.'
Why candidates choose this
Candidates may think resource groups are a natural scope for governance because they are commonly used to organize resources, and they might assume that applying policies at a lower level is more precise. However, they overlook the requirement to minimize administrative overhead across multiple subscriptions.
✗Create an Azure Blueprint definition and apply it to each subscription separately.Wrong answer — click to see why▾
Why this is wrong here
Applying an Azure Blueprint definition to each subscription separately still requires manual application per subscription, which does not minimize administrative overhead as effectively as a single management group assignment that automatically propagates to all subscriptions.
★ When this WOULD be the correct answer
A company needs to deploy a consistent set of Azure resources (e.g., a network topology, a set of VMs with specific configurations) across multiple subscriptions, and the resources must be deployed as a single, versioned package that can be updated centrally. In this case, an Azure Blueprint would be the correct component to define and apply the resource templates and policies together.
Why candidates choose this
Candidates may think that Azure Blueprints are designed for governance and compliance, and thus assume they are the best tool for enforcing policies and roles across subscriptions, overlooking that management groups provide a more efficient scope for role and policy assignments.
Analysis generated from the official AZ-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
Learn chapter
Azure Regions and Geographies
Key term
Role
A role is a named set of permissions that can be assigned to users or groups to control access to resources in an IT environment.
Key term
Azure Policy
Azure Policy is a service in Microsoft Azure that lets you create, assign, and manage rules to ensure your resources stay compliant with your company standards and service-level agreements.
About these practice questions
This AZ-900 question is part of Courseiva's 981-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on AZ-900
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company has three Azure subscriptions: one for the engineering department, one for marketing, and one for finance. The central IT team needs to apply a common set of Azure Policy definitions (e.g., allowed locations for resources) that must be enforced across all three subscriptions. Additionally, each department manager must be able to apply custom policies that only affect their own subscription. The IT team wants to organize the subscriptions into a hierarchy where they can assign the common policy at the top level and delegate custom policy assignment at the subscription level. Which Azure feature should the IT team use to create this hierarchical structure?
medium- ✓ A.Management groups
- B.Resource groups
- C.Azure Policy
- D.Azure role-based access control (RBAC)
Why A: Management groups allow you to create a hierarchical structure of Azure subscriptions, enabling you to assign common Azure Policy definitions (like allowed locations) at a top-level management group that applies to all child subscriptions. Each department subscription can then have its own custom policy assignments, as management groups support inheritance and delegation of policy assignments across the hierarchy.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-900 exam.