Check Azure service availability zone support by region and service.
| Service | Category | Zonal | Zone-Redundant | Regions | Notes |
|---|---|---|---|---|---|
| Virtual Machines | Compute | Yes | No | 15 regions | VMs are deployed to a specific availability zone. Use VM Scale Sets with zone balancing for zone-redundant deployments. Not all VM SKUs are available in every zone. |
| App Service | Compute | No | Yes | 12 regions | Zone redundancy requires Premium v3 or Isolated v2 plan with a minimum of 3 instances. Enable zone redundancy at plan creation; it cannot be changed later. |
| AKS | Containers | No | Yes | 15 regions | AKS distributes agent nodes across availability zones when configured. The control plane is automatically zone-redundant. Use pod topology spread constraints for even distribution. |
| SQL Database | Databases | No | Yes | 13 regions | Zone redundancy is available for Premium, Business Critical, General Purpose, and Hyperscale tiers. Enabled via the 'Zone redundant' option during creation or via ALTER DATABASE. |
| Cosmos DB | Databases | No | Yes | 15 regions | Enable availability zones when adding a region to your Cosmos DB account. Zone redundancy is free of charge and cannot be toggled after the region is added. |
| Storage | Storage | No | Yes | 15 regions | Zone-Redundant Storage (ZRS) replicates data across three availability zones. Also available as Geo-Zone-Redundant Storage (GZRS) for cross-region replication. Supported for block blobs, page blobs, managed disks, files, queues, and tables. |
| Key Vault | Security | No | Yes | 15 regions | Key Vault is automatically zone-redundant in regions that support availability zones. No additional configuration is required. HSM-backed keys also benefit from zone redundancy. |
| Load Balancer Standard | Networking | Yes | Yes | 15 regions | Standard Load Balancer supports both zonal (pinned to a specific zone) and zone-redundant frontends. Zone-redundant frontends survive zone failure. Basic SKU does not support availability zones. |
| VPN Gateway | Networking | Yes | Yes | 12 regions | Use AZ SKUs (VpnGw1AZ, VpnGw2AZ, etc.) for zone-redundant deployment. Standard VPN Gateway SKUs do not support availability zones. Requires a Standard public IP. |
| Application Gateway v2 | Networking | Yes | Yes | 15 regions | Application Gateway v2 supports zone-redundant and zonal deployments. Specify zones during creation. Requires Standard_v2 or WAF_v2 SKU. V1 SKUs do not support AZ. |
| Event Hubs | Messaging | No | Yes | 14 regions | Zone redundancy is automatically enabled for new Premium, Dedicated, and Standard tier namespaces in AZ-enabled regions. Metadata and data are replicated across zones. |
| Service Bus | Messaging | No | Yes | 14 regions | Zone redundancy is automatically enabled for new Premium tier namespaces in AZ-enabled regions. Standard tier also supports AZ in select regions. Cannot be toggled after creation. |
| Redis Cache | Databases | Yes | Yes | 12 regions | Zone redundancy requires Premium or Enterprise tier. Premium tier distributes replicas across zones. Enterprise tier is zone-redundant by default. Specify zones at creation time. |
| Functions Premium | Compute | No | Yes | 12 regions | Zone redundancy requires Elastic Premium plan (EP1, EP2, EP3) with a minimum of 3 instances. Enable zone redundancy at plan creation; it cannot be changed after deployment. |
| Virtual Machine Scale Sets | Compute | No | Yes | 15 regions | VMSS can distribute instances across multiple availability zones with zone balancing. Use Flexible orchestration mode for best AZ support. Specify zones at creation time. |
| Azure Firewall | Networking | No | Yes | 15 regions | Azure Firewall can be deployed across availability zones for higher availability. Specify zones during deployment. Zone-redundant deployment has a 99.99% SLA vs 99.95% for single zone. |
| Public IP Address | Networking | Yes | Yes | 15 regions | Standard SKU public IPs support both zonal and zone-redundant deployment. Zone-redundant IPs are created by default when no zone is specified. Basic SKU does not support AZ. |
| Managed Disks | Storage | Yes | No | 15 regions | Managed disks are deployed to a specific availability zone and must be in the same zone as the VM. Use ZRS disks (currently in preview for select regions) for cross-zone redundancy. |
| Container Registry | Containers | No | Yes | 12 regions | Zone redundancy requires Premium SKU. Enable at registry creation; it cannot be added to existing registries. Geo-replication can also be zone-redundant per replica region. |
| API Management | Integration | No | Yes | 12 regions | Zone redundancy requires Premium tier. Distribute scale units across availability zones for high availability. At least 3 units are recommended for full AZ coverage. |
Output will appear here...The Azure Availability Zone Checker lets you quickly verify which Azure services support availability zones in each Azure region. Availability zones are physically separate datacenters within a region, and not all services or regions support them. This tool provides an up-to-date reference so you can plan resilient architectures without hunting through scattered Azure documentation pages. It covers compute, storage, networking, database, and platform services.
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.