Azure Regions, Zones & the Resource Hierarchy
AZ-900 AZ-900 · Describe Azure architecture and services
How Azure is organised physically
Azure is a global network of datacenters, and the exam expects you to describe how that physical footprint is organised: datacenters, regions, region pairs, availability zones, and sovereign regions. These are the building blocks everything else sits on — compute, storage, and networking all live somewhere, and "somewhere" in Azure means a region, and often a zone inside it.
A region is a geographical area containing one or more datacenters, connected by a low-latency network. Azure has more than 60 regions worldwide — more than any other cloud provider — so customers can usually place resources near their users. When you create a resource, you pick a region, and that choice affects latency (how fast users reach it), cost (prices vary by region), and which services are available (not every service runs in every region). Regions are the unit of data residency: a resource's data stays in its region unless you deliberately configure replication elsewhere.
A datacenter is the physical building: servers, storage, networking, power, and cooling, run by Microsoft. You never interact with a datacenter directly — you interact with regions and zones — but the exam wants you to know datacenters are the physical layer underneath regions.
Region pairs and sovereign regions
Every Azure region is paired with another region — its region pair — at least 300 miles away, inside the same geography where possible (for example, UK South pairs with UK West). Region pairs matter for two reasons. First, platform updates: Microsoft rolls updates out to one region of a pair at a time, so a bad update cannot take down both at once. Second, disaster recovery: services that replicate across regions (such as geo-redundant storage) replicate to the paired region by default, and data residency is preserved because the pair stays in the same geography. If a question describes a service replicating to a second region automatically, the paired region is the destination.
Sovereign regions are isolated instances of Azure for governments with specific requirements — for example, Azure Government in the United States, and Azure China (operated by 21Vianet). They are physically and logically separated from the public Azure cloud and are available only to qualifying government customers. The exam only requires you to know they exist and why: data sovereignty and government compliance.
Availability zones: surviving a datacenter failure
An availability zone is a physically separate datacenter (or group of datacenters) within a region, with its own independent power, cooling, and networking. Regions that support zones have at least three of them. The point of zones is to survive a datacenter-level failure: if you run two virtual machines in different zones and one zone goes down, the other keeps serving. This is the mechanism behind the strongest VM availability SLA in Azure.
Zones are often confused with availability sets, and the exam tests the difference. An availability set protects against failures inside a single datacenter: it spreads virtual machines across fault domains (groups of VMs sharing a power source and network switch, so a hardware failure hits only one domain) and update domains (groups rebooted together during maintenance, so only some VMs restart at once). Zones protect against the whole datacenter failing; sets protect against rack-level failures and maintenance reboots. The SLAs tell the story:
| Configuration | VM availability SLA |
|---|---|
| Single VM with premium SSD (no redundancy) | 99.9% |
| Two or more VMs in one availability set | 99.95% |
| Two or more VMs across availability zones | 99.99% |
Remember the order: zones beat sets, sets beat a single VM. A question asking for the highest availability for virtual machines is answered with availability zones.
The resource hierarchy: how Azure is organised logically
On top of the physical footprint sits a logical hierarchy that controls how resources are organised, secured, and billed. From the top:
Management groups sit at the top. They are containers for subscriptions, used to apply governance — policies, access control, compliance — across many subscriptions at once. A management group can contain other management groups, nesting up to six levels below the root, so a large organisation can mirror its structure (for example, a group per division, with groups per department beneath). Whatever you apply at a management group flows down to everything beneath it.
Subscriptions are the unit of billing and access. Every Azure resource belongs to exactly one subscription, and the subscription is what gets the bill. Subscriptions also carry limits and quotas, and they are a boundary for access control: giving someone access to a subscription gives them access to everything in it (subject to role). Organisations use multiple subscriptions to separate environments (production vs development), departments, or projects — for separate billing and separate access.
Resource groups are containers for resources within a subscription. A resource group holds the resources for one solution or workload — a web app, its database, its storage — so they can be managed, monitored, and deleted as a unit. The rules matter for the exam: a resource belongs to exactly one resource group; resource groups cannot be nested; deleting a resource group deletes everything in it; and the resources in a group can live in different regions (the group itself has a location, but its resources do not have to share it). Moving resources between groups is possible, with some restrictions.
Resources are the individual Azure services themselves — a virtual machine, a storage account, a virtual network, a database. They are the bottom of the hierarchy and the things you actually use.
Worked example: organising a company
A company with offices in Europe and Asia runs production and development environments. Sensible organisation: a management group per region (Europe, Asia) for governance, subscriptions per environment inside each (production, development) for separate billing and access, and resource groups per application inside each subscription (web shop, reporting, HR system). A policy applied at the Europe management group — "resources may only be created in European regions" — flows down to every subscription and resource group beneath it. A developer given access to the development subscription cannot touch production. And when the reporting project ends, deleting its resource group removes every resource cleanly. Hierarchy, billing, access, and lifecycle — one structure does all four.
Exam traps to watch for
- Confusing availability zones with availability sets. Zones are separate datacenters in a region (99.99% SLA for VMs); sets spread VMs across fault and update domains inside one datacenter (99.95%).
- Thinking a resource group forces its resources into one region. Resources in a group can be in different regions; only the group itself has a location.
- Saying a resource can belong to several resource groups or that groups can nest. One resource, one group; groups cannot contain other groups.
- Mixing up the hierarchy order. Management groups contain subscriptions, subscriptions contain resource groups, resource groups contain resources — governance flows down, billing happens at the subscription.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A company needs its virtual machines to keep running even if an entire Azure datacenter fails. Which feature should it use?
Explanation: Availability zones are physically separate datacenters within a region, so VMs spread across zones survive a whole-datacenter failure (99.99% SLA). An availability set protects against failures inside one datacenter (rack-level and maintenance), not the loss of the datacenter itself. A resource group is an organisational container, not a redundancy mechanism. A management group governs subscriptions; it provides no availability.
Exam objective: AZ-900 Describe the core architectural components of Azure: describe availability zones
Q2.What is the top level of the Azure resource hierarchy, used to apply governance across multiple subscriptions?
Explanation: Management groups sit at the top of the hierarchy and contain subscriptions, letting governance (policies, access) apply across many subscriptions at once. Resource groups contain resources within one subscription. Subscriptions sit below management groups. Regions are physical locations, not part of the management hierarchy.
Exam objective: AZ-900 Describe the core architectural components of Azure: describe management groups
Q3.A company wants its production and development environments billed separately, with developers unable to access production resources. What is the best way to organise this in Azure?
Explanation: Subscriptions are the unit of billing and a boundary for access control, so separate subscriptions give separate bills and separate access. One subscription with one resource group gives neither. Separate resource groups in one subscription still share one bill. Separate regions do not separate billing or access at all.
Exam objective: AZ-900 Describe the core architectural components of Azure: describe subscriptions
Q4.Which statement about resource groups is correct?
Explanation: Deleting a resource group deletes everything it contains — that is one of its main purposes. A resource belongs to exactly one resource group. Resource groups cannot be nested. And resources in a group can live in different regions; only the group itself has a location.
Exam objective: AZ-900 Describe the core architectural components of Azure: describe Azure resources and resource groups
Q5.Azure replicates geo-redundant storage to a second region, and rolls platform updates out to one region at a time. What is the second region called?
Explanation: Every Azure region has a region pair — another region at least 300 miles away in the same geography — which receives geo-replication and is updated separately. A sovereign region is an isolated Azure instance for governments. An availability zone is a datacenter within a region, not a second region. 'Paired datacenter' is not an Azure term.
Exam objective: AZ-900 Describe the core architectural components of Azure: describe Azure regions, region pairs, and sovereign regions
Q6.A company runs two virtual machines in a single availability set. What availability SLA does Azure offer for this configuration?
Explanation: Two or more VMs in one availability set carry a 99.95% SLA. 99.9% is the SLA for a single VM with premium SSD. 99.99% requires VMs spread across availability zones. No configuration offers 100%.
Exam objective: AZ-900 Describe the core architectural components of Azure: describe availability zones
Q7.A government agency must use an isolated instance of Azure that is physically and logically separated from the public cloud. Which Azure offering meets this need?
Explanation: Sovereign regions (such as Azure Government and Azure China) are isolated Azure instances for governments with specific sovereignty requirements. A public region is part of the shared public cloud. An availability zone is a datacenter within a region. A region pair is two public regions linked for replication and updates.
Exam objective: AZ-900 Describe the core architectural components of Azure: describe Azure regions, region pairs, and sovereign regions
Q8.Which of the following correctly lists the Azure resource hierarchy from the highest level to the lowest?
Explanation: The hierarchy is management groups at the top, then subscriptions, then resource groups, then resources at the bottom. The other options scramble the order: resource groups never sit above subscriptions, and resources are always at the bottom.
Exam objective: AZ-900 Describe the core architectural components of Azure: describe the hierarchy of resource groups, subscriptions, and management groups