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

Microsoft Azure Version 1 original current

Imported from official source

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. …

This version

Version
1 of 1
Recorded
September 20, 2026 19:52
Change
Initial
Content hash
f340f55595cb4a66d864756c3e1e9689
All versions
Revision history

Officially records where a publication came from, not whether it is true. Imported records are reproduced from an organization's own official source.