Azure Global Infrastructure
Source: Dev.to
From the Ground Up: How Azure Is Built
Servers: The Building Blocks of the Cloud
- Powerful computers that store data, run applications, and process information.
- Azure uses millions of servers worldwide.
- Always online and built to handle heavy workloads.
- These servers live inside secure facilities called data centers.
Data Centers: Where the Cloud Lives
A data center is like a fortress for technology. It’s packed with servers, networking equipment, cooling systems, and backup power. Microsoft currently operates 400+ data centers (as of this writing) across the globe, forming the backbone of Azure.
- Racks
- Clusters
- Server farms
Fault Domains
A fault domain is a safety zone – a group of servers that share the same power source and network switch. If one fails, only that domain is affected.
- Purpose: Protects your application from hardware failures.
Update Domains
Update domains ensure that while some servers are being updated, others stay online.
- Purpose: Keeps your application available during maintenance.
Availability Zones
An Availability Zone (AZ) consists of three or more physically separate locations within a single region. Each zone has its own power, cooling, and networking.
- If one zone goes down, the others stay fully operational.
- Designed for zone‑redundant applications, protecting against large‑scale events like fires or power outages.
Azure Region
An Azure region is a set of data centers located in a specific geographical area. Azure has 70+ regions worldwide (as of this writing).
Example Regions
- East US
- Canada Central
- West Europe
- Japan East
Regions let you choose where your data is stored based on:
- Performance (closer = faster)
- Data residency laws
- Compliance requirements
Region Pairs
Region pairs provide built‑in disaster recovery and resilience.
- Updates happen in one region at a time.
- Data stays within the same geography.
- Faster recovery during disasters.
- Typically at least 300 miles (483 km) apart to reduce the risk of both being affected by the same natural disaster.
Azure Geographies
A Geography is the largest organizational boundary in Azure. It includes two or more regions that meet specific compliance and residency laws.
Example Geographies
- Africa
- Canada
- United States
- Europe
- Brazil
- Asia
- Australia
- United Kingdom
- Japan
- India
Geographies ensure organizations meet local regulations and keep data within legal jurisdictions.
Hierarchy Overview (Smallest → Largest)
- Server
- Rack
- Data Center
- Availability Zone
- Region
- Region Pair
- Geography
This layered design gives Azure:
- High availability
- Low latency
- Strong disaster recovery
- Global coverage
- Compliance with regional laws
Fun Facts
- Latency Matters: Choose regions closest to your users for better performance.
- Data Residency Requirements: Industries like healthcare and finance often require data to stay within a country.
- Sovereign Clouds: Azure offers specialized environments such as Azure Government (US) and Azure China for customers with strict regulatory needs.
Pro Tip
If you’re a beginner, start by exploring the Azure region closest to you. It’s the easiest way to see how geography impacts performance and compliance.