Understand the concept
Microsoft Entra ID provides the tenant identity context. Management groups organize subscriptions; subscriptions contain resource groups and resources. These levels support management and access at different scopes. A resource group organizes related resources but is not a physical zone or a failure-isolation guarantee.
Apply and decide
Regions and availability zones address location and isolation. Services do not have identical options in every region. Region choice must consider data, latency, availability, and recovery. Different resource groups do not prove resilience: examine physical placement, dependencies, and whole-service recovery.
Workplace application
A project organizes applications by resource group to simplify management. This does not demonstrate that machines occupy different zones. Separate governance design from resilience design and inspect the shared database. For policies spanning subscriptions, identify the correct hierarchy scope. During region selection, confirm needed service capabilities rather than assuming identical availability and recovery in every location.
Two VMs in different resource groups but the same zone may fail from the same zonal event.
Common pitfalls
Treating a resource group as a physical zone or recovery guarantee.
Related topics: Compute and connectivity · Storage, retention, and recovery
Administrative scope and failure domain are different dimensions.
Reference: AZ-900 study guide: skills measured July 20, 2026 · AZ-900 skills measured July 20, 2026