Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides a reference list of Azure services. Some services offer built-in multiregion capabilities like geo-replication, cross-region backup, failover, or connectivity across Azure regions. Some capabilities operate automatically, while others require explicit configuration.
For each service that offers built-in multiregion support, the table shows the following information:
- Multiregion support type: The specific capability the service provides, with a link to documentation that describes the capability in more detail. Even when a service supports multiregion capabilities, review the capability's documentation to understand any limitations or configuration requirements.
- Paired regions and Nonpaired regions: Whether the capability operates between regions of that type. To learn more about paired regions, see Azure region pairs and nonpaired regions. Some rows include footnote markers that point to caveats listed below the table. Nonregional services show a checkmark in both columns because they're not tied to a specific region.
- Description: A short summary of how the capability behaves.
Services without built-in support require you to design your own multiregion solution, including replication, failover, and other aspects of recovery. To see services that don't provide built-in multiregion support, select the No built-in multiregion support tab.
List of Azure services
| Service | Multiregion support type | Paired regions | Nonpaired regions | Description |
|---|---|---|---|---|
| Multiregion deployment | Replicates the gateway component to multiple regions for latency optimization and automatic failover. | |||
| Geo-replication | Replicates configuration data across regions with active-active read/write capability. | |||
| Custom backups | Backs up app data to a storage account, which you can configure with geo-redundant storage (in paired regions) or object replication for multiregion protection. | |||
| Custom backups | Backs up app data to a storage account, which you can configure with geo-redundant storage (in paired regions) or object replication for multiregion protection. | |||
| Geo-redundant storage and cross-region restore | Replicates backup data to the paired region for disaster recovery. | |||
| Azure Storage Mover | Copies blob data to another storage account, which can be in a different region. | |||
| Geo-redundant storage (GRS) | Replicates data asynchronously to the paired region with customer-managed or Microsoft-managed failover. | |||
| Object replication | Copies block blobs asynchronously between a source storage account and a destination account, which can be in a different region. | |||
| Geo-replication | Replicates container images and artifacts across regions with active-active read/write capability. | |||
| Multiple read regions with single write region | Replicates data to multiple read regions, improving read availability and global latency, with optional failover for writes. | |||
| Multiple write regions | Replicates data across regions with active-active multi-write capability and automatic conflict resolution. | |||
| Periodic backup | Backs up data automatically at regular intervals, and uses storage GRS replication to maintain copies in the paired region by default. | |||
| Microsoft-managed failover to paired region | Replicates metadata to the paired region. Microsoft can initiate failover to the paired region during prolonged outages. In nonpaired regions, you can design your own multiregion solution for Azure Data Factory. |
|||
| Geo-redundant storage (GRS) | Replicates data asynchronously to the paired region with customer-managed or Microsoft-managed failover. | |||
| Cross-region read replicas | Replicates data asynchronously to read replicas in other regions with manual failover. | |||
| Cross-region read replicas | Replicates data asynchronously to read replicas in other regions with virtual endpoints for failover. | |||
| Multiregion protection | Protects public IP addresses in multiple regions from a single DDoS Network Protection plan that's deployed in one region. | |||
| Microsoft-managed failover to paired region | Replicates data to the paired region. Microsoft can initiate failover during prolonged outages. | |||
| Nonregional service | Operates infrastructure in multiple Azure regions. | |||
| Metadata geo-disaster recovery | Replicates metadata synchronously to the paired region. Event data isn't replicated. In nonpaired regions, you can design your own multiregion solution for Azure Event Grid. |
|||
| Geo-replication | Replicates both metadata and event data across regions with synchronous or asynchronous options. | |||
| Metadata geo-disaster recovery | Replicates metadata (entities, configuration) only. Event data isn't replicated. | |||
| Geo-redundant storage (GRS) | Replicates data asynchronously to the paired region with customer-managed or Microsoft-managed failover. You can design your own multiregion solution for Azure Files, including for premium file shares or when you use nonpaired regions. |
|||
| Nonregional service | Operates infrastructure in multiple Azure regions. | |||
| Microsoft-managed failover to paired region | Replicates data asynchronously to the paired region with Microsoft-managed or customer-initiated failover. In nonpaired regions, you can design your own multiregion solution for Azure IoT Hub. |
|||
| Microsoft-managed failover to paired region | Replicates data asynchronously to the paired region with Microsoft-managed failover. In nonpaired regions, you can design your own multiregion solution for Azure Key Vault. |
|||
| Multiregion replication | Replicates data across two regions with Traffic Manager-based routing. | |||
| Azure Kubernetes Fleet Manager | Manages multiple AKS clusters across regions with centralized orchestration and multi-cluster workload routing. | |||
| Backup | Backs up containerized applications and data in your AKS cluster, with support for restoring to a paired region using the Vault Tier. | |||
| Global load balancer | For public load balancers, the Global tier provides a single anycast IP address that routes traffic to the closest healthy regional load balancer with automatic failover. | |||
| Active geo-replication | Replicates across multiple active-active regions with manual failover. | |||
| Workspace replication | Replicates logs and configuration to a secondary region within the same region group with manual switchover. | |||
| Cross-region replication | Replicates volumes asynchronously between Microsoft-selected region pairs, including some nonstandard pairs. | |||
| Metadata geo-disaster recovery | Replicates metadata to a secondary region. Registration data isn't replicated. | |||
| Geo-redundant storage (GRS) | Replicates data asynchronously to the paired region with customer-managed or Microsoft-managed failover. In nonpaired regions, you can design your own multiregion solution for Azure Queue Storage. |
|||
| Geo-Replication | Replicates both metadata and message data across regions with synchronous or asynchronous options. | |||
| Metadata Geo-Disaster Recovery | Replicates metadata only (entities, configuration). Message data isn't replicated. | |||
| Geo-replication | Replicates across regions with Traffic Manager-based routing and automatic failover. | |||
| Cross-region VM replication | Replicates virtual machines asynchronously to a secondary region. | |||
| Active geo-replication | Replicates a single database asynchronously to a secondary region with manual failover. | |||
| Automated backups | Backs up databases automatically at regular intervals and stores copies in the paired region using geo-redundant storage. | |||
| Failover groups | Replicates groups of databases with automatic failover and transparent connection endpoint redirection. | |||
| Automated backups | Backs up managed instances automatically at regular intervals and stores copies in the paired region using geo-redundant storage. | |||
| Failover groups | Replicates instance data to a secondary region with customer-managed or Microsoft-managed failover. | |||
| Automated failover | Continues to run future tasks in the paired region when the target storage account uses GRS. | |||
| Azure-initiated disaster recovery | Microsoft can initiate failover of the Storage Mover service to the paired region during prolonged outages. Regardless of where Storage Mover is deployed, it can copy between any supported source and target regions. |
|||
| Geo-redundant storage (GRS) | Replicates data asynchronously to the paired region with customer-managed or Microsoft-managed failover. In nonpaired regions, you can design your own multiregion solution for Azure Table Storage. |
|||
| Nonregional service | Operates infrastructure in multiple Azure regions. | |||
| Azure Site Recovery | Replicates virtual machines asynchronously to a secondary region. | |||
| Geo-replication | Replicates across regions with Traffic Manager-based routing and automatic failover. | |||
| Worldwide and geo-located data storage | Operates infrastructure in multiple Azure regions. | |||
| Cross-region disaster recovery | Provides cross-region disaster recovery in paired regions. | |||
| Global and data zone deployments | Supports global, data zone, and single-region model deployments. |
1 The multiregion support for these services might require you to configure multiple Azure services.
2 These services have region selection constraints for multiregion capabilities. Review their reliability guides carefully to confirm supported region combinations and any related prerequisites before you design your architecture.