Key Points
- Availability zones are independent datacenter groups in an Azure region.
- Zone-redundant resources are managed by Azure; zonal resources need customer-managed replication across zones.
- Decide per component: stateless apps often need two zones, while quorum-based or highest-durability stores may need three zones.
What is changing
The article explains that zone resiliency is not a single number you apply to a whole workload; you must decide how many zones each component needs to survive the loss of one zone. Azure services offer zone-redundant resources that Azure manages, while zonal resources stay in one zone and require you to replicate across zones yourself. For each component you should ask: can the remaining zones carry the operating state after a zone loss, does correctness need a third failure domain for quorum or highest durability, and how does cost and capacity differ between two-zone and three-zone layouts.
The practical takeaway is to start with service-managed zone redundancy wherever it fits, and only use a three zones design when a component genuinely requires a third failure domain, such as quorum-based systems or stores targeting the highest durability. Validate the choice against the service’s SKU, tier, and region guidance, and consider cost only after the resiliency objective is met.
Why it matters
This matters most to cloud architects and DevOps engineers who design production workloads on Azure. They will need to review each part of their application—frontend, queues, caches, databases—to decide the right zone pattern instead of defaulting to three zones everywhere.
The impact applies to any Azure region that supports availability zones; the guidance is not limited to specific tiers or SKUs, though you must check each service’s zone support. By following the component-level approach you can avoid unnecessary capacity, cost, and operational complexity while still meeting your resiliency goals.
Share your experience with zone-resilient designs or ask questions in the comments below.