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.
While some Azure services support geo-redundancy and geo-replication by using paired regions, you can create solutions that support multiple regions even when those regions aren't paired. This article lists some of the services and possible configurations for multi-region solutions, without requiring paired regions. To learn more about each Azure service and how it supports reliability, see the Azure service reliability guides.
Azure AI Search
To learn about how to create multi-region solutions using Azure AI Search, see Reliability in Azure AI Search.
Azure API Management
To learn about how to create multi-region solutions using Azure API Management, see Reliability in Azure API Management.
Azure App Service
To learn about how to create multi-region solutions using Azure App Service, see Reliability in Azure App Service.
Azure Blob Storage
To learn about how to create multi-region solutions using Azure Blob Storage, see Reliability in Azure Blob Storage.
Azure Cache for Redis
Azure Cache for Redis provide two distinct cross-region replication options that are active geo-replication and passive geo-replication. In both cases, there's no explicit dependency on region pairs.
Azure Container Registry
To learn about how to create multi-region solutions using Azure Container Registry, see Reliability in Azure Container Registry.
Azure Cosmos DB
If your solution requires continuous uptime during region outages, you can configure Azure Cosmos DB to replicate your data across multiple regions and to transparently fail over to operating regions when required. Azure Cosmos DB supports multi-region writes and can distribute your data globally to provide low-latency access to your data from any region without any pairing restriction.
Azure Database for MySQL
Choose any Azure Database for MySQL available Azure regions to spin up your read replicas.
Azure Database for PostgreSQL
For geo-replication in nonpaired regions with Azure Database for PostgreSQL, you can use:
Managed service with geo-replication: Azure PostgreSQL Managed service supports active geo-replication to create a continuously readable secondary replica of your primary server. The readable secondary might be in the same Azure region as the primary or, more commonly, in a different region. This kind of readable secondary replica is also known as geo-replica.
You can also utilize any of the two customer-managed data migration methods listed to replicate the data to a nonpaired region.
Azure Data Factory
For geo-replication in nonpaired regions, Azure Data Factory (ADF) supports Infrastructure-as-code provisioning of ADF pipelines combined with Source Control for ADF.
Azure Event Grid
For geo-replication of Event Grid topics in nonpaired regions, you can implement client-side failover.
Azure IoT Hub
To learn about how to create multi-region solutions using Azure IoT Hub, see Reliability in Azure IoT Hub.
Azure Kubernetes Service (AKS)
To learn about how to create multi-region solutions using Azure Kubernetes Service (AKS), see Reliability in Azure Kubernetes Service (AKS).
Azure Monitor Logs
Log Analytics workspaces in Azure Monitor Logs don't use paired regions. To ensure business continuity and protect against data loss, enable cross-region workspace replication. For more information, see Enhance resilience by replicating your Log Analytics workspace across regions.
Azure Queue Storage
To learn about how to create multi-region solutions using Azure Queue Storage, see Reliability in Azure Queue Storage.
Azure Service Bus
Azure Service Bus can provide regional resiliency, without a dependency on region pairs, by using either Geo Replication or Geo-Disaster Recovery features.
Azure SQL Database
For geo-replication in nonpaired regions with Azure SQL Database, you can use:
Failover group feature that replicates across any combination of Azure regions without any dependency on underlying storage GRS.
Active geo-replication feature to create a continuously synchronized readable secondary database for a primary database. The readable secondary database might be in the same Azure region as the primary or, more commonly, in a different region. This kind of readable secondary database is also known as a geo-secondary or geo-replica.
Azure SQL Managed Instance
For geo-replication in nonpaired regions with Azure SQL Managed Instance, you can use:
- Failover group feature that replicates across any combination of Azure regions without any dependency on underlying storage GRS.
Azure Storage
To achieve geo-replication in nonpaired regions:
For object storage: To learn about how to create multi-region solutions using Azure Blob Storage, see Reliability in Azure Blob Storage.
For Azure NetApp Files, you can replicate to a set of nonstandard pairs besides Azure region pairs. To learn more, see Reliability in Azure NetApp Files.
For Azure Files:
To copy your files to another storage account in a different region, use tools such as:
For a sample script, see Sync between two Azure file shares for Backup and Disaster Recovery.
To sync between your Azure file share (cloud endpoint), an on-premises Windows file server, and a mounted file share running on a virtual machine in another Azure region (your server endpoint for disaster recovery purposes), use Azure File Sync.
Important
You must disable cloud tiering to ensure that all data is present locally, and provision enough storage on the Azure Virtual Machine to hold the entire dataset. To ensure changes replicate quickly to the secondary region, files should only be accessed and modified on the server endpoint rather than in Azure.
For Azure Queue Storage: To learn about how to create multi-region solutions using Azure Queue Storage, see Reliability in Azure Queue Storage.
Azure Virtual Desktop
For geo-replication in nonpaired regions for Azure Virtual Desktop, you need to consider session host virtual machines and storage for user profiles, applications, and data. Microsoft manages the Azure Virtual Desktop control plane, which is globally distributed and highly available.
For session hosts, you can deploy virtual machines in multiple regions in an active-active scenario, or replicate them across regions using Azure Site Recovery in an active-passive scenario.
For storage, see Azure Storage.
For more information, see Multiregion Business Continuity and Disaster Recovery (BCDR) for Azure Virtual Desktop and Azure Virtual Desktop service architecture and resilience.
Azure Virtual Machines
To achieve geo-replication in nonpaired regions, use Azure Site Recovery service. Azure Site Recovery is the Disaster Recovery service from Azure that provides business continuity and disaster recovery by replicating workloads from the primary location to the secondary location. The secondary location can be a nonpaired region if supported by Azure Site Recovery.