🔒 Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided AZ-900 Domain 2
Domain 2 — Module 1 of 11 9%
8 of 26 overall

AZ-900 Study Guide

Domain 1: Describe Cloud Concepts

  • What is Cloud Computing? Free
  • Cloud Models: Public, Private, and Hybrid Free
  • Cloud Pricing: Consumption, Serverless, and Pay-as-You-Go Free
  • High Availability and Scalability Free
  • Reliability, Security, and Manageability Free
  • IaaS, PaaS, and SaaS Explained Free
  • Choosing the Right Cloud Service Free

Domain 2: Describe Azure Architecture and Services

  • Azure Regions, Zones, and Datacenters
  • Resources, Resource Groups, and Subscriptions
  • Azure Virtual Machines
  • Azure Compute: Containers, Functions, and App Service
  • Azure Networking: VNets, Subnets, and Peering
  • Connecting to Azure: VPNs, ExpressRoute, and DNS
  • Azure Storage Services
  • Data Migration: Moving to Azure
  • Microsoft Entra ID: Your Identity Hub
  • Authentication and External Identities
  • Azure Security: RBAC, Zero Trust, and Defender

Domain 3: Describe Azure Management and Governance

  • What Affects Your Azure Bill
  • Pricing Calculators: TCO and Azure Pricing
  • Cost Management and Tags
  • Azure Governance: Purview, Policy, and Locks
  • The Azure Portal and Cloud Shell
  • Infrastructure as Code: ARM, Bicep, and Arc
  • Azure Advisor and Service Health
  • Azure Monitor: Logs, Alerts, and Insights

AZ-900 Study Guide

Domain 1: Describe Cloud Concepts

  • What is Cloud Computing? Free
  • Cloud Models: Public, Private, and Hybrid Free
  • Cloud Pricing: Consumption, Serverless, and Pay-as-You-Go Free
  • High Availability and Scalability Free
  • Reliability, Security, and Manageability Free
  • IaaS, PaaS, and SaaS Explained Free
  • Choosing the Right Cloud Service Free

Domain 2: Describe Azure Architecture and Services

  • Azure Regions, Zones, and Datacenters
  • Resources, Resource Groups, and Subscriptions
  • Azure Virtual Machines
  • Azure Compute: Containers, Functions, and App Service
  • Azure Networking: VNets, Subnets, and Peering
  • Connecting to Azure: VPNs, ExpressRoute, and DNS
  • Azure Storage Services
  • Data Migration: Moving to Azure
  • Microsoft Entra ID: Your Identity Hub
  • Authentication and External Identities
  • Azure Security: RBAC, Zero Trust, and Defender

Domain 3: Describe Azure Management and Governance

  • What Affects Your Azure Bill
  • Pricing Calculators: TCO and Azure Pricing
  • Cost Management and Tags
  • Azure Governance: Purview, Policy, and Locks
  • The Azure Portal and Cloud Shell
  • Infrastructure as Code: ARM, Bicep, and Arc
  • Azure Advisor and Service Health
  • Azure Monitor: Logs, Alerts, and Insights
Domain 2: Describe Azure Architecture and Services Premium ⏱ ~12 min read

Azure Regions, Zones, and Datacenters

Azure runs in 60+ regions across the globe. Understanding regions, availability zones, and how Azure's physical infrastructure is organised is fundamental to designing resilient cloud solutions.

Azure’s physical infrastructure

☕ Simple explanation

Think of Azure like a global chain of hotels.

Datacenters = individual hotel buildings, full of servers instead of rooms.

Availability zones = separate buildings in the same city, each with its own power and cooling. If one building catches fire, guests move to the other buildings.

Regions = cities where the hotels operate. “Australia East” is Sydney, “UK South” is London.

Region pairs = partner cities. If a natural disaster hits Sydney, Melbourne (the paired region) can take over.

Azure has 60+ regions in over 140 countries — more global coverage than any other cloud provider.

Azure’s physical infrastructure is organised in a hierarchy:

Datacenters are physical facilities containing networked computer servers. Each datacenter has its own power, cooling, and networking infrastructure. You never interact with individual datacenters directly.

Availability zones are physically separate locations within an Azure region. Each zone is made up of one or more datacenters with independent power, cooling, and networking. A region typically has three availability zones (Zone 1, Zone 2, Zone 3).

Regions are geographical areas containing one or more datacenters. When you deploy a resource, you choose a region. Examples: Australia East (Sydney), UK South (London), East US (Virginia).

Region pairs link two regions in the same geography for disaster recovery. Updates are rolled out to paired regions sequentially, and if a widespread outage occurs, one region from each pair is prioritised for recovery.

Azure regions

A region is a geographical area on the planet containing at least one (but often multiple) datacenters that are networked together with a low-latency network.

Why regions matter

When you create an Azure resource (a VM, a database, a storage account), you choose which region to deploy it in. This matters because:

FactorWhy It Matters
LatencyDeploy close to your users for faster response times
Data residencySome regulations require data to stay in specific countries
Service availabilityNot all Azure services are available in every region
PricingPrices vary between regions

Harbour Health’s region choice

Harbour Health needs their patient data to stay within a specific geography for regulatory compliance. They deploy to Australia East (Sydney) — the closest Azure region to their Auckland office — and configure data residency policies to ensure data stays within Australia.

ℹ️ Region pairs

Azure pairs most regions within the same geography:

RegionPaired RegionGeography
Australia EastAustralia SoutheastAustralia
UK SouthUK WestUnited Kingdom
East USWest USUnited States
North EuropeWest EuropeEurope

Why pairs matter for the exam:

  • Platform updates are rolled out to one region in a pair first, then the other — minimising simultaneous downtime
  • If a broad outage occurs, one region from each pair is prioritised for recovery
  • Some services (like geo-redundant storage) replicate data to the paired region automatically

Sovereign regions

Some Azure regions are sovereign — isolated from the main Azure cloud for government or regulatory reasons:

Sovereign RegionWho It’s For
Azure Government (US)US government agencies and their partners
Azure ChinaOrganisations operating in China (operated by 21Vianet, not Microsoft)

Exam tip: Sovereign regions are physically and logically separate from the main Azure cloud. Azure Government meets US government security requirements. Azure China is operated by a separate company due to Chinese regulations.

Availability zones

Availability zones are physically separate locations within a single region. Each zone has independent power, cooling, and networking.

Think of it like this: if Region = City, then Availability Zone = different neighbourhoods in that city, each with its own power grid.

WhatWithout ZonesWith Zones
A fire in one datacenterYour app might go downYour app keeps running in other zones
A power outageYour app might go downOther zones have separate power
Network failureYour app might go downOther zones have separate networking

How Summit Construction uses availability zones

Summit deploys their project portal across three availability zones in Australia East:

  • Zone 1: Primary VM
  • Zone 2: Secondary VM
  • Zone 3: Tertiary VM

A load balancer distributes traffic across all three. If Zone 1 goes offline, Zones 2 and 3 handle all traffic automatically. Zero downtime.

💡 Zone-redundant vs zonal services

Azure services support availability zones in two ways:

  • Zonal services: You pin a resource to a specific zone (e.g., a VM in Zone 1)
  • Zone-redundant services: Azure automatically spreads the resource across zones (e.g., zone-redundant storage)

Exam tip: If a question asks “how to achieve the highest availability within a single region,” the answer is usually deploying across multiple availability zones.

Azure datacenters

You never interact with individual datacenters directly — you work with regions and zones. But it helps to know what’s inside:

  • Thousands of physical servers in racks
  • Redundant power supplies and generators
  • Advanced cooling systems
  • 24/7 physical security (guards, biometrics, cameras)
  • Network connectivity to other datacenters in the region

Key concept: Datacenters are the physical foundation. Availability zones group datacenters. Regions group zones. You choose regions; Azure manages the rest.

🎬 Video walkthrough

🎬 Video coming soon

Azure Regions, Zones, and Datacenters — AZ-900

Azure Regions, Zones, and Datacenters — AZ-900

~9 min

Flashcards

Question

What is an Azure region?

Click or press Enter to reveal answer

Answer

A geographical area containing one or more datacenters networked together with low latency. You choose a region when deploying resources. Examples: Australia East, UK South, East US.

Click to flip back

Question

What are availability zones?

Click or press Enter to reveal answer

Answer

Physically separate locations within a region, each with independent power, cooling, and networking. Typically 3 zones per region. Deploying across zones protects against datacenter-level failures.

Click to flip back

Question

What are region pairs?

Click or press Enter to reveal answer

Answer

Two Azure regions in the same geography linked for disaster recovery. Updates roll out sequentially across pairs. If a wide outage occurs, one region from each pair is prioritised for recovery.

Click to flip back

Question

What are sovereign regions?

Click or press Enter to reveal answer

Answer

Azure regions isolated from the main cloud for government/regulatory compliance. Examples: Azure Government (US agencies) and Azure China (operated by 21Vianet). They are physically and logically separate.

Click to flip back

Knowledge Check

Knowledge Check

Harbour Health needs to ensure patient data stays within Australia due to data residency regulations. Which Azure concept helps them achieve this?

Knowledge Check

Summit Construction deploys VMs across three availability zones in a single region. What does this protect against?

Knowledge Check

What is the PRIMARY purpose of Azure region pairs?


Next up: Azure’s organisational hierarchy — resources, resource groups, subscriptions, and management groups.

← Previous

Choosing the Right Cloud Service

Next →

Resources, Resource Groups, and Subscriptions

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.