The core architecture of Azure
Regions, region pairs, sovereign regions, availability zones, datacentres, and how resources, resource groups, subscriptions and management groups fit together.
- 15 min
- 7 concepts
- Try it yourself
- 5-question check
Learn
Azure has two kinds of building blocks. Physical: datacentres, grouped into availability zones and regions around the world. Management: resources, grouped into resource groups, subscriptions and management groups so you can organise, secure and pay for them.
- 1
Describe Azure regions, region pairs, and sovereign regions
A region is a geographical area with one or more datacentres connected by a low-latency network, such as UK South. You choose a region for each resource.
Many regions are paired with another in the same geography, such as UK South and UK West, for disaster recovery and staggered updates. Some newer regions have no pair. Sovereign regions are isolated instances of Azure for governments, such as Azure Government in the US and Azure operated by 21Vianet in China.
Remember: Region pairs are at least 300 miles apart where possible.
- 2
Describe availability zones
Availability zones are physically separate locations within a region, each with independent power, cooling and networking. Supported regions have at least three zones.
Zonal services are pinned to one zone (like a VM). Zone-redundant services replicate across zones automatically (like zone-redundant storage).
Remember: Zones protect against a datacentre failure within a region.
- 3
Describe Azure datacenters
Datacentres are the physical buildings full of servers, with their own power, cooling and networking. You don't choose a datacentre directly; you choose a region and, where offered, a zone.
Remember: Datacentre → zone → region → geography.
- 4
Describe Azure resources and resource groups
A resource is anything you create: a VM, a storage account, a database. Every resource must be in exactly one resource group, a logical container. Resource groups can't be nested.
Deleting a resource group deletes everything in it, so group resources that share a lifecycle. Permissions and policies applied to a group are inherited by its resources.
Remember: One resource, one resource group. No nesting.
- 5
Describe subscriptions
A subscription is a unit of billing and access control. Every resource group lives in one subscription. You might use separate subscriptions for environments (dev and prod), departments or billing boundaries. Subscriptions also have limits, such as how many resources of a type you can create.
Remember: Subscriptions separate billing and access.
- 6
Describe management groups
Management groups sit above subscriptions so you can apply policy and access to many subscriptions at once. They can be nested up to six levels deep, below the root management group. A subscription belongs to one management group.
Remember: Govern many subscriptions together with management groups.
- 7
Describe the hierarchy of resource groups, subscriptions, and management groups
From the top: root management group → management groups → subscriptions → resource groups → resources. Policies and role assignments flow down the hierarchy, so something assigned at a management group applies to every subscription, group and resource below it.
Remember: Settings flow down, never up.
The management hierarchy
- Management groupsApply policy and access across subscriptions, up to six levels deep
- SubscriptionsBilling and access boundaries
- Resource groupsLogical containers for resources that share a lifecycle
- ResourcesVMs, storage accounts, databases and so on
Try it
Assign a role at different levels of the hierarchy and see how it flows down.
This interactive part needs JavaScript.
In the portal
- Management groupsAzure portal: Management groups
- SubscriptionsAzure portal: Subscriptions
- Create a resource groupAzure portal: Resource groups > Create
Key terms
Click a card to see the definition.
Check your understanding
5 questions. Score 80% or more and these skills are marked as confident in your AZ-900 study plan.
Can resource groups be nested?
Resource groups can't contain other resource groups. Management groups can be nested.
What happens when you delete a resource group?
Deleting the group deletes its contents.
What's the minimum number of availability zones in a region that supports them?
Zone-enabled regions have at least three zones.
Which is at the top of the hierarchy?
Management groups sit above subscriptions.
What is Azure Government an example of?
Sovereign regions are isolated from main Azure.
Sources
- Microsoft Learn: Describe the core architectural components of Azure
- Microsoft Learn: What are availability zones?
- Microsoft Learn: Azure region pairs and nonpaired regions
- Microsoft Learn: What are Azure management groups?
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.