Study guide
2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups)
Microsoft Azure Fundamentals AZ-900
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips
2 Domain 1: Cloud Concepts (25-30%)
1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model
3 Domain 2A: Azure Architecture Components
2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview
4 Domain 2B: Azure Compute Services
2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop
5 Domain 2C: Azure Networking Services
2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery
6 Domain 2D: Azure Storage Services
2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics
7 Domain 2E: Azure Identity, Access, and Security
2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services
8 Domain 3A: Azure Cost Management
3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization
9 Domain 3B: Azure Governance and Compliance
3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together
10 Domain 3C: Azure Monitoring and Management Tools
3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health
11 Additional Azure Services and Exam Review
Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice
12 Advanced Azure Topics and Service Deep Dives
Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans
2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups)
Key Takeaways Explain This Topic AI
Azure organizes everything in four scopes: Management Groups → Subscriptions → Resource Groups → Resources, with governance inheriting downward.
Management groups sit above subscriptions; a tenant has one root management group, the tree nests up to six levels deep, and you can create up to 10,000 management groups.
A subscription is both a billing boundary (one invoice) and an access/limit boundary (RBAC scope, quota ceiling).
Every resource lives in exactly one resource group; resource groups cannot nest, and deleting a resource group deletes all resources inside it.
Azure Policy and RBAC assigned at a higher scope are inherited by all child scopes; inheritance flows down, never up.
Last updated: October 2026
The Four Management Scopes
Azure organizes every deployment into four nested scopes . From top to bottom they are Management Groups → Subscriptions → Resource Groups → Resources . Each scope is a place where you can assign Azure Policy (rules) and Role-Based Access Control (RBAC) (permissions), and those assignments inherit downward to every child scope.
Level 1 — Management Groups
Management groups are containers above subscriptions used to apply governance across many subscriptions at once. Key limits:
A tenant (your Microsoft Entra directory) has exactly one built-in root management group ; every subscription ultimately folds up to it.
The tree nests up to six levels deep (this depth count excludes the root level and the subscription level).
You can create up to 10,000 management groups per tenant.
Each management group and subscription has exactly one parent , but a parent can have many children.
Use case: a bank creates a "Production" management group, assigns a policy that forces disk encryption, and every current and future subscription under it is automatically compliant — no per-subscription work.
Level 2 — Subscriptions
A subscription is two boundaries at once:
Billing boundary — each subscription produces a separate invoice ; you split subscriptions by department, environment, or project to track spend.
Access and limit boundary — RBAC can be scoped here, and subscriptions carry quota ceilings (for example a default cap on vCPUs per region). Hitting a limit is often the reason to add another subscription.
Level 3 — Resource Groups
Resource groups (RGs) are logical containers for related resources. Memorize these rules:
- Rule Detail
- Membership Every resource belongs to exactly one resource group
- Nesting Resource groups cannot be nested
- Location The RG has a region, but it is metadata only — it can hold resources from any region
- Movement Resources can be moved between RGs (and across subscriptions)
- Deletion Deleting an RG deletes every resource inside it
- Lifecycle Best practice: group resources that are created and deleted together
- Level 4 — Resources
A resource is a single manageable service instance: a VM, a storage account, a virtual network, a SQL database. It always lives inside one resource group.
Inheritance
Azure Policy assignments, RBAC role assignments, and resource locks applied at a higher scope cascade to all children ; tags do not. Inheritance is one-directional.
- Assigned at Applies to
- Management group All child subscriptions, RGs, and resources
- Subscription All RGs and resources in it
- Resource group All resources in it
- Resource That resource only
- Worked scenario
A company assigns a policy at the "Corp" management group that denies creation of any VM larger than Standard_D4s_v5 . A developer in a subscription three levels below tries to deploy a Standard_D16s_v5 VM. The deployment is blocked — the deny policy was inherited all the way down. Moving the subscription to a management group without that policy would lift the restriction.
Trap 1: Inheritance flows down only . A tag set on one resource does NOT propagate up to its resource group.
Trap 2: "How many resource groups can a resource belong to?" — exactly one . Resources can be moved , never co-owned.
Trap 3: Which scope is the billing boundary? The subscription , not the resource group.
Why Organizations Use Multiple Subscriptions
Because a subscription is both a billing boundary and a limit boundary, splitting workloads across subscriptions is a common governance pattern. Three typical strategies appear in scenarios:
Per environment — separate dev, test, and production subscriptions so a misconfigured dev resource can never affect production, and each environment's spend is isolated on its own invoice.
Per department or business unit — IT, Marketing, and Finance each get a subscription, making chargeback and budgeting clean.
Per limit ceiling — when a single subscription approaches a quota (such as the default vCPU cap in a region), adding another subscription raises headroom.
Resource Group Design in Practice
The golden rule for resource groups is shared lifecycle : put resources that you will create, update, and delete together into the same group. A three-tier web app — front end, API, and database for one project — belongs in one resource group so you can tear it all down in a single action when the project ends.
- Good grouping Reasoning
- All resources for one app/environment Created and deleted together; one delete cleans up everything
- Resources sharing an RBAC/policy need Assign access and rules once at the group
- Resources tracked as one cost line Tag/report at the group level
Because a resource group's region is only metadata (where its deployment record lives), a single group can legitimately hold a VM in East US and a storage account in West Europe. The group's location does not constrain where its resources run.
Tags Round Out Governance
Management scopes organize resources structurally; tags organize them logically across scopes. A tag is a name=value pair (for example environment=production , costCenter=marketing ) attached to a subscription, resource group, or resource. Tags power cost reporting and can be required by Azure Policy — a policy can deny any resource that lacks a mandatory owner tag. Note that, unlike RBAC and Policy, tags applied to a resource group are NOT automatically inherited by the resources inside it ; you must apply or enforce tags at the resource level or use policy to inherit them.
One-line recap: Management group = governance across many subscriptions; subscription = billing + limits; resource group = lifecycle container; resource = the thing itself; and Policy/RBAC inherit downward while tags do not inherit in either direction.