Availability zones
What it is
An availability zone is a physically separate group of one or more datacenters inside one Azure region. Zones have independent power, cooling, and networking. Think of a region as a city-sized service area and zones as separate, well-connected buildings in that area: a serious problem at one building need not stop the others.
Many, but not all, Azure regions have availability zones. A zone-enabled region commonly exposes logical labels such as 1, 2, and 3. Those labels are not a global street address: the same label can map to a different physical zone in another subscription.
Microsoft diagram: What are availability zones?
Why it exists
A single virtual machine or data copy can fail with the datacenter that hosts it. Spreading independently usable parts of a workload across two or more zones reduces that single-datacenter risk while keeping the workload in one region. It does not protect against a whole-region outage, a bad software release, deleted data, or an incorrectly configured identity.
How it works
Azure services support zones in one of three ways:
- A zonal resource goes into one zone you select. It is isolated from other zones but is not, by itself, resilient to its own zone failing.
- A zone-redundant resource is distributed or replicated across multiple zones by the Azure service. The service manages the cross-zone placement and failover.
- A regional (nonzonal) resource has no zone choice. Azure places it within the region; do not assume it survives a zone failure.
For zonal resources, the customer must build the pattern: multiple instances in different zones, a way to route traffic to a healthy instance, and a plan for state and data. The exact choices depend on the service and its available SKUs. Check the service reliability guide and region support before treating a design as zone-resilient.
Northwind example
Northwind runs two copies of its ordering application in one zone-enabled region: one VM in zone 1 and another in zone 2. A load balancer sends shoppers only to the healthy copy. Its order data uses zone-redundant storage. If zone 1 loses power, the zone-2 application and the replicated data can continue serving orders.
This is still a single-region design. If the whole region is unavailable, Northwind needs a separate multi-region recovery design, plus backups for accidental deletion or corruption.
Compare the close terms
| Term | Protects mainly against | What you must remember |
|---|---|---|
| Availability zone | A failure affecting one zone | It is a physical-fault boundary within a region. |
| zone-redundant | A single-zone failure | Azure spreads a supported service across zones. |
| availability-set | Some hardware and planned-maintenance failures within a datacenter | It is not a substitute for cross-zone placement. |
| Region pair or multi-region design | A regional outage | It requires a separate design and failover plan. |
| Backup | Deleted, corrupted, or historical data | Replication does not undo a bad write. |
Tradeoffs and failure modes
- Cross-zone traffic, supported SKUs, and replicated components can change cost or latency; test the actual workload.
- Putting every component in different zones can still fail if the database, DNS, credentials, or traffic-routing layer is a single point of failure.
- A one-zone VM is zonal, not highly available. A region that has zones does not make every deployed resource zone-resilient automatically.
- Zone numbers should not be compared across subscriptions without checking the subscription-specific mapping.
Where it appears in the route
Start with AZ-900 architecture. Then use AZ-104 compute to choose service-specific resiliency settings.
Sources and re-audit
- Microsoft Learn — What are availability zones?, checked 2026-09-16.
- Microsoft Learn — Azure reliability guides by service, checked 2026-09-16.
Related
zone-redundant · azure-region · availability-set · virtual-machine-scale-set · redundancy-lrs-zrs-grs · azure-backup