# Microsoft — Two zones or three? A design framework for zone-resilient Azure workloads

- Company: Microsoft (microsoft.com)
- Announced: 2026-09-09T18:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://azure.microsoft.com/en-us/blog/two-zones-or-three-a-design-framework-for-zone-resilient-azure-workloads/
- Record: https://forck.live/items/10462-two-zones-or-three-a-design-framework-for-zone-resilient-azure-workloads
- Subject: Azure AI

Microsoft's guide presents a design framework for zone-resilient Azure workloads, arguing that zone resiliency should be decided component by component rather than applied uniformly. It distinguishes between zone-redundant resources managed by Azure and zonal resources that require manual configuration, and provides a decision process based on resource availability, data consistency, and cost.

## Evidence

Verbatim from https://azure.microsoft.com/en-us/blog/two-zones-or-three-a-design-framework-for-zone-resilient-azure-workloads/:

> Zone resiliency isn’t a single number you apply to a whole workload. The useful question isn’t “how many zones?” but “how many zones does each component need to survive the loss of one?” Decide zone patterns component by component, use service-managed zone redundancy wherever it fits, and reserve three-zone designs for the components that genuinely require a third failure domain.

---

Record: https://forck.live/items/10462-two-zones-or-three-a-design-framework-for-zone-resilient-azure-workloads
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md