Azure Global Infrastructure and Management Hierarchy: Regions, Availability Zones, Management Groups, Subscriptions and Resource Groups
Regions, Pairs and Zones
| Term | Meaning | Example |
|---|---|---|
| Region | A geographic area with one or more datacenters | centralindia (Pune), southindia (Chennai) |
| Availability Zone | Separate datacenter locations inside a region with independent power, cooling and network. Most regions have 3 | Zone 1, 2, 3 |
| Region pair | Two regions in the same geography, used for some geo-redundant services and update sequencing | Central India and South India |
| Geography | A market area for data residency | India |
| Edge locations | Points of presence for Front Door and CDN | Many cities |
| Sovereign clouds | Separate Azure clouds for governments or special rules | Azure Government, Azure China |
- Zonal services pin to a zone (a VM in zone 1). Zone-redundant services spread automatically (zone-redundant storage, SQL zone redundancy)
- Not every region has zones or every service. Check availability
- Some newer regions have no pair. Design DR yourself
Choosing a Region
| Factor | Question |
|---|---|
| Latency | Where are most users? |
| Compliance | Must data stay in a country? |
| Service availability | Does the region offer the services and VM sizes you need? |
| Price | Prices differ by region |
| Resilience | Does it have zones and a good pair or DR region? |
The Management Hierarchy
text
Tenant Root Group (Microsoft Entra tenant)
└─ Management group: Contoso
├─ Management group: Production
│ └─ Subscription: Prod-Shop
│ ├─ Resource group: rg-shop-web-prod (VMs, App Service, VNet)
│ └─ Resource group: rg-shop-data-prod (SQL, Storage)
└─ Management group: Non-Production
└─ Subscription: Dev-Shop
| Level | Purpose |
|---|---|
| Management group | Group subscriptions and apply policy and RBAC to many at once (up to 6 levels deep, not counting root) |
| Subscription | A billing and access boundary with its own quotas. Use separate ones for prod and non-prod |
| Resource group | A logical container for resources that share a lifecycle. Delete the group to delete everything inside |
| Resource | A VM, storage account, database and so on |
- RBAC and Azure Policy are inherited downward
- A resource lives in one resource group but can connect to resources in others
- The resource group has a location only for its metadata. Resources inside can be in other regions
Azure Resource Manager (ARM)
ARM is the management layer behind the portal, CLI, PowerShell, SDKs and templates. Every request goes through ARM, so RBAC, policy, locks and tags work the same everywhere.
Tags and Naming
bash
az group create --name rg-shop-web-prod --location centralindia --tags env=prod app=shop owner=asha cost-center=1001
az tag list --resource-id /subscriptions/<sub-id>/resourceGroups/rg-shop-web-prod
# Naming pattern: <type>-<workload>-<env>-<region>-<instance>
# Example: vm-shop-prod-cin-001 st shop prod storage names are lowercase letters and numbers only
- Follow the Cloud Adoption Framework naming pattern with type, workload, environment, region and number
- Use tags for cost reporting, ownership and automation. Tags are not inherited by default (use Azure Policy to copy them)
- Storage accounts and some services need globally unique, lowercase names
Practice
- Pick a region for users in India and explain why
- Draw a management group layout for a company with prod, dev and shared services
- Create a resource group with tags and delete it
- Explain the difference between a zonal and a zone-redundant service
Conclusion
Resources run in regions and zones. Management groups, subscriptions and resource groups organize them, and RBAC and policy inherit downward. Choose regions by latency, compliance and service availability, and use tags and clear names.
Quick Summary: regions; choosing; hierarchy; ARM; tags and naming.

