SkarpChapter 6 of 20
Azure Core Architecture: Regions, Region Pairs, and Availability Zones
Peek under the hood of Azure’s global infrastructure to see how regions, region pairs, and Availability Zones work together to deliver resiliency and high availability.
The Azure Core Architecture Big Picture
Why Azure Core Architecture Matters
AZ-900 expects you to recognize how Azure is physically and logically organized so you can reason about availability, resiliency, and data location.
7 Azure Core Architectural Components
You must know this exact list and order: 1. Azure regions 2. region pairs 3. Availability Zones 4. Azure datacenters 5. Azure resources 6. resource groups 7. subscriptions.
Link to Earlier Modules
You already met IaaS, PaaS, SaaS and the shared responsibility model. Here you see the physical and logical foundation Microsoft provides for those services.
What You Will Be Able to Answer
By the end, you should comfortably answer: where data lives, how Azure survives failures, and how regions, zones, and datacenters relate to resources, groups, and subscriptions.
Azure Regions: What They Are and Why They Matter
Definition of an Azure Region
An Azure region is a set of datacenters in a specific geographic area, linked by a high-bandwidth, low-latency network, and exposed as a named deployment location.
Regions and Resource Creation
When you create most Azure resources, you must pick a region like West Europe or East US. That choice affects where data lives and how fast users reach it.
Regions and Data Residency
Regions are grouped into geographies (for example, Europe). Many organizations choose regions to satisfy laws and policies about where data must be stored.
Regions and Latency
Placing workloads in regions close to users usually reduces latency. Exam questions may ask you to pick the best region to optimize performance for a user base.
Common Exam Confusion
Do not confuse regions with Availability Zones or datacenters. A region is the broad named location; zones and datacenters are structures inside that region.
Azure Datacenters: The Physical Foundation
What Is an Azure Datacenter?
An Azure datacenter is a physical facility with servers, storage, networking, power, and cooling. It is the real-world building behind the cloud.
Datacenters Form Regions
Several nearby datacenters are grouped to create an Azure region. You choose regions when deploying resources; you do not choose individual datacenters.
Shared Responsibility Reminder
Microsoft secures and operates datacenters. You design how your apps use regions and zones to achieve the level of availability your business needs.
From Physical to Logical
Think in layers: datacenters → region → (Availability Zones) → your Azure resources, organized into resource groups and subscriptions.
Availability Zones: High Availability Inside a Region
Definition of Availability Zones
Availability Zones are physically separate locations within an Azure region, each with independent power, cooling, and networking.
Zones and Resiliency
Deploying across multiple zones in the same region lets your app survive the loss of a whole zone, such as a major datacenter outage.
How Zones Are Built
Each zone is made of one or more datacenters. Zones in a region are connected with high-speed private fiber to keep latency low.
Exam Distinctions
Region = geographic area. Zone = isolated location inside that region. Datacenter = physical building(s) that make up a zone.
Not Every Region Has Zones
Some Azure regions do not support Availability Zones. In those cases, cross-region strategies like region pairs become more important.
Region Pairs: Disaster Recovery Across Regions
What Is a Region Pair?
A region pair is a logical relationship between two Azure regions in the same geography, such as North Europe paired with West Europe.
Why Region Pairs Exist
Region pairs support disaster recovery and safer platform updates by separating regions and updating them in a staggered fashion.
Benefits to You
You can deploy geo-redundant solutions across a region pair, and some services like Geo-Redundant Storage replicate data automatically to the paired region.
Region Pairs vs Zones
Region pairs work across regions and protect from region-wide failures. Availability Zones work inside a region and protect from zonal or datacenter failures.
Putting It Together: Regions, Zones, and Datacenters in a Scenario
Scenario Setup
European e-commerce site: EU-only data, survive a datacenter failure, and recover from a regional disaster. How do we use regions, zones, and pairs?
Step 1: Pick a Region
Choose West Europe as the primary region: it is in the EU geography and close to German, French, and Dutch customers.
Step 2: Use Availability Zones
Deploy the app and database across Zone 1 and Zone 2 in West Europe so a single zone or datacenter failure does not take you offline.
Step 3: Use the Region Pair
West Europe is paired with North Europe. Configure geo-redundant storage and a secondary app deployment in North Europe for regional disasters.
Mapping to the 7 Components
Datacenters → zones → regions, with resources deployed into resource groups and subscriptions. Region pair adds cross-region resiliency.
Thought Exercise: Map Requirements to Azure Components
Work through this short thought exercise. You do not need to write code; just reason it out.
Situation:
A startup in Brazil is building a real-time gaming backend on Azure. Their requirements:
- Most players are in Brazil and neighboring countries.
- They want the lowest possible latency for those players.
- They can tolerate brief downtime if a whole region fails, but they cannot tolerate losing player data.
- They want to keep architecture simple for now.
Task 1: Choose a primary region
- Which Azure region would you choose to minimize latency for Brazilian players?
- Hint: Think about geography and proximity.
Task 2: Decide whether to use Availability Zones
- Would you deploy across multiple Availability Zones in the chosen region? Why or why not, given their tolerance for downtime but not for data loss?
Task 3: Decide how to protect data across regions
- If you do not build full active-active deployments in two regions, what simpler option could you use to ensure data is safe if the region is lost?
- Hint: Think about storage replication to a paired region.
Pause and answer these questions in your own words. Then compare with the guidance in the next explanation step.
Thought Exercise Debrief: Reasoning Like the Exam
Picking the Primary Region
For Brazilian players, Brazil South is the natural choice to minimize latency. Exam answers often reward choosing the geographically closest region.
Should We Use Zones?
If available, zones help survive datacenter failures and keep data safe without cross-region complexity. They fit the "no data loss" requirement well.
Protecting Data Across Regions
Use geo-redundant storage or database replication to the paired region. Services may be single-region, but data is safely copied elsewhere.
Matching Requirements to Components
Low latency → region. Datacenter failure → Availability Zones. Region-wide disaster with data safety → region pairs and geo-replication.
Quick Check: Regions, Datacenters, and Zones
Test your understanding of the basic relationships.
Which statement best describes the relationship between Azure regions, Availability Zones, and Azure datacenters?
- A region is a single datacenter; multiple regions form an Availability Zone.
- An Availability Zone is a set of datacenters inside a region; multiple zones form the region.
- A datacenter is a set of regions; regions and zones are logical labels on top.
- Availability Zones and regions are the same thing; datacenters are unrelated.
Show Answer
Answer: B) An Availability Zone is a set of datacenters inside a region; multiple zones form the region.
An Azure region is a geographic area made up of multiple datacenters. Within some regions, those datacenters are organized into Availability Zones. Each zone consists of one or more datacenters with independent power, cooling, and networking.
Quick Check: Region Pairs vs Availability Zones
Distinguish cross-region and in-region resiliency.
Your company wants its app to keep running if a single datacenter fails, but they do NOT want to deploy in multiple regions yet. Which Azure feature should you use?
- Region pairs
- Availability Zones
- Multiple subscriptions
- Resource groups in different regions
Show Answer
Answer: B) Availability Zones
Availability Zones provide resiliency against datacenter-level failures within a single region. Region pairs are for cross-region disaster recovery, subscriptions are billing and management boundaries, and resource groups do not provide physical resiliency.
Flashcards: Core Terms and the Canonical List
Use these flashcards to reinforce the key terms and the seven Azure core architectural components.
- List the seven Azure core architectural components in order.
- 1. Azure regions 2. region pairs 3. Availability Zones 4. Azure datacenters 5. Azure resources 6. resource groups 7. subscriptions
- What is an Azure region?
- An Azure region is a set of datacenters deployed within a specific geographic area, connected through a dedicated high-bandwidth, low-latency network, and exposed as a named location where you deploy services.
- What is an Azure datacenter?
- An Azure datacenter is a physical facility that houses servers, storage, networking equipment, power, and cooling. Multiple nearby datacenters are grouped to form an Azure region.
- What are Availability Zones?
- Availability Zones are physically separate locations within an Azure region, each made up of one or more datacenters with independent power, cooling, and networking, designed to provide high availability within the region.
- What is a region pair?
- A region pair is a logical relationship between two Azure regions within the same geography that supports disaster recovery, prioritized regional recovery, and staggered platform updates.
- How do Availability Zones and region pairs differ?
- Availability Zones provide resiliency within a single region (against datacenter or zone failures), while region pairs provide cross-region resiliency (against regional disasters and for geo-replication).
- Where do Azure resources, resource groups, and subscriptions fit into this picture?
- Azure resources (VMs, storage, databases) are deployed into specific regions (and sometimes zones). They are logically organized into resource groups, which in turn exist within subscriptions that define billing and access boundaries.
- Which component is most directly tied to data residency requirements?
- Azure regions (and their geographies) are most directly tied to data residency, because they determine where data is physically stored.
Key Terms
- region pair
- A logical relationship between two Azure regions within the same geography that supports disaster recovery, prioritized regional recovery, and staggered platform updates.
- Azure region
- A set of Azure datacenters deployed within a specific geographic area, connected through a dedicated high-bandwidth, low-latency network, and exposed as a named location where you deploy services.
- subscription
- A logical container that groups Azure resource groups and resources, defines billing and usage boundaries, and is associated with an Azure account.
- Azure resource
- An instance of a service you create in Azure, such as a virtual machine, storage account, database, or web app.
- resource group
- A logical container in Azure that holds related resources for an application or workload, enabling unified management, deployment, and lifecycle control.
- Azure datacenter
- A physical facility that houses servers, storage, networking equipment, power, and cooling. Multiple nearby datacenters are grouped to form an Azure region.
- Availability Zone
- A physically separate location within an Azure region, consisting of one or more datacenters with independent power, cooling, and networking, designed to provide high availability within the region.