2.1 Azure Regions and Availability Zones
Key Takeaways
- Azure operates in 60+ regions across 140+ countries, making it one of the largest global cloud infrastructures.
- An Azure Region is a set of data centers deployed within a latency-defined perimeter and connected through a regional low-latency network.
- Availability Zones are physically separate data centers within a region, each with independent power, cooling, and networking.
- Region Pairs are two regions in the same geography that provide automatic replication and failover for select services.
- Sovereign regions (Azure Government, Azure China) operate independently with restricted access for compliance requirements.
Azure Regions and Availability Zones
Quick Answer: Azure has 60+ regions worldwide. Each region contains one or more data centers. Availability Zones are physically separate data centers within a region with independent power, cooling, and networking. Region Pairs provide cross-region redundancy.
Azure Regions
An Azure region is a set of data centers deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network. Azure has more global regions than any other cloud provider.
Key Facts About Azure Regions
| Fact | Detail |
|---|---|
| Total regions | 60+ (with more announced) |
| Countries/territories | 140+ |
| Geographies | Americas, Europe, Asia Pacific, Middle East, Africa |
| Data residency | Data stays within the region's geography unless you explicitly configure replication |
| Service availability | Not all services are available in every region |
| Pricing | Prices vary between regions |
How to Choose a Region
Selecting the right Azure region depends on four key factors:
- Compliance and data residency — Legal or regulatory requirements may mandate where data must be stored (e.g., GDPR requires data to stay in the EU)
- Proximity to users — Choose the region closest to your end users for the lowest latency
- Service availability — Some newer Azure services are only available in select regions initially
- Pricing — Resource costs can vary between regions (e.g., US East is often cheaper than West Europe)
On the Exam: When a question asks about choosing a region, compliance/data residency is ALWAYS the top priority. If there are no compliance requirements, choose based on proximity to users.
Availability Zones
Availability Zones (AZs) are physically separate locations within an Azure region. Each zone is a fully independent data center with its own power supply, cooling system, and network connectivity.
Key Facts About Availability Zones
- Each availability zone is an independent data center within a region
- Zones are connected through high-speed, private fiber-optic networks
- A minimum of three zones exist in each enabled region
- They protect against data center-level failures (fire, flood, power outage)
- Not all regions support Availability Zones
Zone-Redundant vs. Zonal Services
| Deployment Type | Description | Example |
|---|---|---|
| Zonal services | You pin a resource to a specific zone | Deploy a VM in Zone 1 |
| Zone-redundant services | Azure automatically replicates across zones | Zone-redundant Azure SQL Database |
| Non-regional services | Globally deployed, not tied to a specific region | Azure Active Directory (Entra ID), Azure Front Door |
How Availability Zones Protect Your Workloads
If one data center in a region fails (Zone 1 goes down), your zone-redundant resources in Zones 2 and 3 continue to operate. This provides 99.99% SLA for VMs deployed across availability zones.
On the Exam: Availability Zones protect against data center failures WITHIN a region. Region Pairs protect against entire REGION failures. Know the difference.
Region Pairs
A region pair consists of two Azure regions within the same geography (such as US, Europe, or Asia). Azure automatically configures certain services to replicate between paired regions for disaster recovery.
Key Facts About Region Pairs
| Feature | Description |
|---|---|
| Minimum distance | At least 300 miles (480 km) apart to reduce the likelihood of a shared disaster |
| Planned maintenance | Azure rolls out updates to one region in a pair at a time (never both simultaneously) |
| Recovery priority | If a widespread outage occurs, one region in each pair is prioritized for recovery |
| Data residency | Both regions in a pair are in the same geography (data stays within the geography) |
Examples of Region Pairs
| Region 1 | Region 2 |
|---|---|
| East US | West US |
| North Europe (Ireland) | West Europe (Netherlands) |
| Southeast Asia (Singapore) | East Asia (Hong Kong) |
| UK South | UK West |
| Canada Central | Canada East |
Sovereign Regions
Sovereign regions are Azure instances that are physically and logically isolated from the main Azure commercial cloud. They exist to meet strict compliance requirements:
Azure Government
- For: US federal, state, and local government agencies and their contractors
- Compliance: FedRAMP High, DoD SRG, ITAR, CJIS
- Regions: US Gov Virginia, US Gov Texas, US Gov Arizona, US DoD Central, US DoD East
- Access: Requires screening and validation of US government affiliation
Azure China (operated by 21Vianet)
- For: Organizations operating in China
- Compliance: Chinese regulations requiring data to remain within China
- Operator: 21Vianet (a Chinese data center provider), NOT Microsoft directly
- Access: Separate Azure portal, separate billing, separate identity
On the Exam: Sovereign regions are completely separate instances of Azure. Azure Government is for US government entities. Azure China is operated by 21Vianet, not Microsoft directly.
What is the PRIMARY factor to consider when choosing an Azure region?
What do Availability Zones protect against?
Who operates Azure China?
How far apart are Azure Region Pairs?