Azure Services that support Availability Zones

Microsoft Azure global infrastructure is designed and constructed at every layer to deliver the highest levels of redundancy and resiliency to its customers. Azure infrastructure is composed of geographies, regions, and Availability Zones, which limit the blast radius of a failure and therefore limit potential impact to customer applications and data. The Azure Availability Zones construct was developed to provide a software and networking solution to protect against datacenter failures and to provide increased high availability (HA) to our customers.

Availability Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters with independent power, cooling, and networking. The physical separation of Availability Zones within a region limits the impact to applications and data from zone failures, such as large-scale flooding, major storms and superstorms, and other events that could disrupt site access, safe passage, extended utilities uptime, and the availability of resources. Availability Zones and their associated datacenters are designed such that if one zone is compromised, the services, capacity, and availability are supported by the other Availability Zones in the region.

All Azure management services are architected to be resilient from region-level failures. In the spectrum of failures, one or more Availability Zone failures within a region have a smaller failure radius compared to an entire region failure. Azure can recover from a zone-level failure of management services within a region. Azure performs critical maintenance one zone at a time within a region, to prevent any failures impacting customer resources deployed across Availability Zones within a region.

conceptual view of an Azure region with 3 zones

Azure services supporting Availability Zones fall into three categories: zonal, zone-redundant, and non-regional services. Customer workloads can be categorized to utilize any of these architecture scenarios to meet application performance and durability.

  • Zonal services – A resource can be deployed to a specific, self-selected Availability Zone to achieve more stringent latency or performance requirements. Resiliency is self-architected by replicating applications and data to one or more zones within the region. Resources can be pinned to a specific zone. For example, virtual machines, managed disks, or standard IP addresses can be pinned to a specific zone, which allows for increased resilience by having one or more instances of resources spread across zones.

  • Zone-redundant services – Azure platform replicates the resource and data across zones. Microsoft manages the delivery of high availability since Azure automatically replicates and distributes instances within the region. ZRS, for example, replicates the data across three zones so that a zone failure does not impact the HA of the data.

  • Non-regional services – Services are always available from Azure geographies and are resilient to zone-wide outages as well as region-wide outages.

To achieve comprehensive business continuity on Azure, build your application architecture using the combination of Availability Zones with Azure region pairs. You can synchronously replicate your applications and data using Availability Zones within an Azure region for high-availability and asynchronously replicate across Azure regions for disaster recovery protection. To learn more, read building solutions for high availability using Availability Zones.

Azure services supporting Availability Zones

Azure regions with Availability Zones

Americas Europe Africa Asia Pacific
Canada Central France Central South Africa North* Japan East
Central US Germany West Central Southeast Asia
East US North Europe Australia East
East US 2 UK South
South Central US West Europe
US Gov Virginia
West US 2

* To learn more about Availability Zones and available services support in these regions, contact your Microsoft sales or customer representative. For the upcoming regions that will support Availability Zones, see Azure geographies.

Azure Services supporting Availability Zones

Zone Resilient Services

🌐 Non-Regional Services - Services are always available from Azure geographies and are resilient to zone-wide outages as well as region-wide outages.

🔷 Resilient to the zone-wide outages

Foundational Services

Products Resiliency
Storage Account 🔷
Application Gateway (V2) 🔷
Azure Backup 🔷
Azure Cosmos DB 🔷
Azure Data Lake Storage Gen 2 🔷
Azure Express Route 🔷
Azure Public IP 🔷
Azure SQL Database (General Purpose Tier) 🔷
Azure SQL Database (Premium & Business Critical Tier) 🔷
Disk Storage 🔷
Event Hubs 🔷
Key Vault 🔷
Load Balancer 🔷
Service Bus 🔷
Service Fabric 🔷
Storage: Hot/Cool Blob Storage Tiers 🔷
Storage: Managed Disks 🔷
Virtual Machines Scale Sets 🔷
Virtual Machines 🔷
Virtual Machines: Av2-Series 🔷
Virtual Machines: Bs-Series 🔷
Virtual Machines: DSv2-Series 🔷
Virtual Machines: DSv3-Series 🔷
Virtual Machines: Dv2-Series 🔷
Virtual Machines: Dv3-Series 🔷
Virtual Machines: ESv3-Series 🔷
Virtual Machines: Ev3-Series 🔷
Virtual Machines: F-Series 🔷
Virtual Machines: FS-Series 🔷
Virtual Network 🔷
VPN Gateway 🔷

Mainstream services

Products Resiliency
App Service Environments 🔷
Azure Active Directory Domain Services 🔷
Azure Bastion 🔷
Azure Cache for Redis 🔷
Azure Cognitive Services: Text Analytics 🔷
Azure Data Explorer 🔷
Azure Database for MySQL – Flexible Server 🔷
Azure Database for PostgreSQL – Flexible Server 🔷
Azure DDoS Protection 🔷
Azure Firewall 🔷
Azure Firewall Manager 🔷
Azure Kubernetes Service (AKS) 🔷
Azure Private Link 🔷
Azure Red Hat OpenShift 🔷
Azure Site Recovery 🔷
Azure SQL: Virtual Machine 🔷
Azure Search 🔷
Azure Web Application Firewall 🔷
Cognitive Services: Text Analytics 🔷
Container Registry 🔷
Event Grid 🔷
Network Watcher 🔷
Network Watcher: Traffic Analytics 🔷
Power BI Embedded 🔷
Premium Blob Storage 🔷
Storage: Azure Premium Files 🔷
Virtual Machines: Azure Dedicated Host 🔷
Virtual Machines: Ddsv4-Series 🔷
Virtual Machines: Ddv4-Series 🔷
Virtual Machines: Dsv4-Series 🔷
Virtual Machines: Dv4-Series 🔷
Virtual Machines: Edsv4-Series 🔷
Virtual Machines: Edv4-Series 🔷
Virtual Machines: Esv4-Series 🔷
Virtual Machines: Ev4-Series 🔷
Virtual Machines: Fsv2-Series 🔷
Virtual Machines: M-Series 🔷
Virtual WAN 🔷
Virtual WAN: ExpressRoute 🔷
Virtual WAN: Point-to-Site VPN Gateway 🔷
Virtual WAN: Site-to-Site VPN Gateway 🔷


Products Resiliency
Azure DNS 🌐
Azure Active Directory 🌐
Azure Advanced Threat Protection 🌐
Azure Advisor 🌐
Azure Blueprints 🌐
Azure Bot Services 🌐
Azure Defender for IoT 🌐
Azure Front Door 🌐
Azure Information Protection 🌐
Azure Lighthouse 🌐
Azure Managed Applications 🌐
Azure Maps 🌐
Azure Policy 🌐
Azure Resource Graph 🌐
Azure Sentinel 🌐
Azure Stack 🌐
Azure Stack Edge 🌐
Cloud Shell 🌐
Content Delivery Network 🌐
Cost Management 🌐
Customer Lockbox for Microsoft Azure 🌐
Intune 🌐
Microsoft Azure Peering Service 🌐
Microsoft Azure portal 🌐
Microsoft Cloud App Security 🌐
Microsoft Graph 🌐
Security Center 🌐
Traffic Manager 🌐

Pricing for VMs in Availability Zones

There is no additional cost for virtual machines deployed in an Availability Zone. For more information, review the Bandwidth pricing page.

Get started with Availability Zones

Next steps