Study guide
2.5 Management Groups, Subscriptions, and Resource Groups
AZ-104 Microsoft Azure Administrator Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation and Microsoft Learn Source Control
1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log
2 Chapter 2: Identity, RBAC, and Governance Foundations
2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab
3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization
3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab
4 Chapter 4: Storage Accounts, Access, and Data Protection
4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab
5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep
5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab
6 Chapter 6: Containers, App Service, and Platform Compute
6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab
7 Chapter 7: Virtual Networking, Routing, and Secure Access
7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab
8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting
8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab
9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery
9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab
10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs
10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab
11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path
11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths
2.5 Management Groups, Subscriptions, and Resource Groups
Key Takeaways Explain This Topic AI
Management groups organize subscriptions for inherited governance and access.
Subscriptions are billing, quota, policy, and access boundaries for Azure resources.
Resource groups are lifecycle and management containers, but resources can have dependencies across groups.
Governance hierarchy questions often test inheritance direction and choosing the right scope.
Last updated: May 2026
The Azure Management Hierarchy
Azure governance starts with a hierarchy. At the top is the Microsoft Entra tenant and the tenant root management group. Under that, organizations create management groups. Subscriptions are placed under management groups. Resource groups live inside subscriptions. Resources live inside resource groups.
Level Main purpose Common governance use
Tenant Identity boundary and directory trust. Directory roles, users, groups, tenant-wide identity settings.
Management group Organize subscriptions. Assign policy and RBAC across many subscriptions.
Subscription Resource, billing, quota, and access boundary. Separate environments, departments, or billing units.
Resource group Lifecycle container for related resources. Delegate workload administration and apply tags, locks, or policy.
Resource Individual service instance. Fine-grained access or lock only when needed.
Inheritance flows downward. A policy assigned at a management group can affect child subscriptions. An RBAC role assigned at a subscription can affect child resource groups. A lock at a resource group can affect resources in that group. The reverse is not true.
Management Groups
Management groups solve the problem of scale. If an organization has twenty production subscriptions, assigning the same allowed locations policy to each subscription is possible but tedious. Assigning it once at a Production management group is cleaner. Child subscriptions inherit the assignment.
A common layout is:
Management group Contains Example controls
Tenant root group All management groups and subscriptions in tenant. Broad baseline policy, used carefully.
Platform Connectivity, identity, management subscriptions. Central operations RBAC and required diagnostics.
Landing zones Application subscriptions. Standard tags, allowed regions, security baseline.
Production Production workloads. Strict policy, limited owner assignments.
Sandbox Experiment subscriptions. Cost controls and less restrictive service policy.
Exam trap: management groups do not contain resources directly. They contain subscriptions or child management groups. If a question asks where a VM is located, the answer is resource group in a subscription, not management group.
Subscriptions
A subscription is a major operational boundary. It is associated with billing, resource quotas, Azure RBAC scope, policy assignment scope, and service limits. Many organizations separate subscriptions by environment, workload, department, compliance requirement, or lifecycle.
Use separate subscriptions when you need stronger isolation, separate billing, different quota management, or distinct governance. Use resource groups inside one subscription when the workloads can share subscription-level policy, network model, and billing relationship.
Portal path: Subscriptions > select subscription for IAM, policies, budgets, resource providers, and resource groups. Administrators should know how to switch directories and subscriptions in the portal because many support tickets come from working in the wrong context.
Resource Groups
A resource group is a logical container for resources that are often managed together. Resource groups make it practical to delegate workload administration, deploy templates, view costs by group, apply locks, and clean up resources. However, a resource can connect to resources in other groups. A VM in one resource group can use a virtual network in another if permissions and architecture allow it.
Resource group location often confuses candidates. The resource group has a location because Resource Manager stores metadata there. The resources inside can be in different supported Azure regions. For operational clarity, most teams still group resources sensibly by workload and region.
Resource group design Good fit Risk
By application and environment rg-payroll-prod , rg-payroll-dev Clear lifecycle and delegation.
By resource type only rg-all-vms , rg-all-storage Harder to delete or delegate whole workload.
By shared platform service rg-hub-network Works for central networking with controlled access.
One giant group Everything Poor delegation, cleanup, and blast-radius control.
Portal And CLI Decision Logic
Use the portal to inspect hierarchy, move a subscription under a management group, or review policy inheritance visually. Use CLI for repeatable subscription and group operations. az account list --output table
- az account set --subscription <sub-id>
- az group create --name rg-app-prod --location eastus
- az group list --query "[].{name:name,location:location}" --output table
- az account management-group list
Before running any create or delete command, verify the active subscription with az account show . This is a real administrator habit and an exam clue. If a command succeeds in the wrong subscription, RBAC was not the problem; context was.
Governance Scenarios
Scenario: All production subscriptions must allow resources only in eastus and centralus . Assign an allowed locations policy at the Production management group. Do not configure the policy separately on every resource group unless the question limits the requirement to a single workload.
Scenario: The networking team manages hub VNets in three subscriptions. Put those subscriptions under a platform management group and assign appropriate RBAC to a networking security group at that management group. This avoids repeated per-subscription assignments.
Scenario: A development team needs full control over its application resources but no access to shared networking. Put app resources in a workload resource group, assign Contributor on that resource group, and keep shared network resources in a separate group with narrower permissions.
Scenario: A resource group delete operation fails because a resource has a delete lock. The resource group boundary defines lifecycle, but locks and dependencies still matter. Remove the lock only if governance permits it, then retry.
Exam Traps
Do not say a resource group is a billing account. It helps view and organize costs, but the subscription is the primary billing boundary in these questions.
Do not assume moving a resource group changes the region of resources. Movement and region placement are separate topics and many resources have move limitations.
Do not assign governance at tenant root casually. Tenant root assignments can affect every subscription in the tenant and are difficult to reason about in large estates. On the exam, use the lowest common parent scope that includes all required targets and excludes non-targets.