Proposed Pull Request Change

📄 Document Links

View on GitHub View on Microsoft Learn

--- title: Multi-Region Solutions in Nonpaired Regions description: Learn about how to create multi-region solutions even when the regions aren't paired. See Azure services and configurations for multi-region solutions. author: anaharris-ms ms.service: azure ms.subservice: azure-reliability ms.topic: article ms.date: 10/09/2025 ms.author: anaharris ms.custom: - subject-reliability - build-2025 --- # Multi-region solutions in nonpaired regions Some Azure services support geo-redundancy and geo-replication by using paired regions, but you can create solutions that support multiple regions [even when those regions aren't paired](./regions-paired.md). This article lists some of the services and possible configurations for multi-region solutions that don't require paired regions. To learn more about each Azure service and how it supports reliability, see the [Azure service reliability guides](./overview-reliability-guidance.md). ## Azure AI Search To learn about how to create multi-region solutions using Azure AI Search, see [Reliability in AI Search](./reliability-ai-search.md). ## Azure API Management To learn about how to create multi-region solutions by using Azure API Management, see [Reliability in API Management](./reliability-api-management.md). ## Azure App Service To learn about how to create multi-region solutions by using Azure App Service, see [Reliability in App Service](./reliability-app-service.md). ## Azure Cache for Redis Azure Cache for Redis provides two distinct cross-region replication options: [active geo-replication](/azure/azure-cache-for-redis/cache-how-to-active-geo-replication) and [passive geo-replication](/azure/azure-cache-for-redis/cache-how-to-geo-replication). Neither option explicitly depends on region pairs. ## Azure Container Registry To learn about how to create multi-region solutions by using Azure Container Registry, see [Reliability in Container Registry](./reliability-container-registry.md). ## 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](/azure/cosmos-db/how-to-manage-database-account#add-remove-regions-from-your-database-account) and to transparently fail over to operating regions when required. Azure Cosmos DB supports [multi-region writes](/azure/cosmos-db/multi-region-writes) and can distribute your data globally to provide low-latency access to your data from any region without any pairing restrictions. ## Azure Database for MySQL Choose any [Azure Database for MySQL available Azure regions](/azure/mysql/flexible-server/overview#azure-regions) to create your [read replicas](/azure/mysql/flexible-server/concepts-read-replicas#cross-region-replication). ## Azure Database for PostgreSQL For geo-replication in nonpaired regions with Azure Database for PostgreSQL, you can use a managed service that supports geo-replication. The Azure Database for PostgreSQL managed service supports active [geo-replication](/azure/postgresql/flexible-server/concepts-read-replicas) to create a continuously readable secondary replica of your primary server. The readable secondary replica might be in the same Azure region as the primary server or, more commonly, in a different region. This kind of readable secondary replica is also known as *geo-replica*. You can also use either of the following customer-managed data migration methods to replicate data to a nonpaired region: - [Dump and restore](/azure/postgresql/migrate/how-to-migrate-using-dump-and-restore) - [Logical replication and logical decoding](/azure/postgresql/flexible-server/concepts-logical) ## Azure Data Factory To learn about how to create multi-region solutions by using Azure Data Factory, see [Reliability in Azure Data Factory](./reliability-data-factory.md). ## Azure Event Grid For geo-replication of Azure Event Grid topics in nonpaired regions, you can implement [client-side failover](/azure/event-grid/custom-disaster-recovery-client-side). ## Azure IoT Hub To learn about how to create multi-region solutions by using Azure IoT Hub, see [Reliability in IoT Hub](./reliability-iot-hub.md). ## Azure Kubernetes Service (AKS) To learn about how to create multi-region solutions by using Azure Kubernetes Service (AKS), see [Reliability in AKS](./reliability-aks.md). ## 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/azure-monitor/logs/workspace-replication). ## Azure Service Bus Azure Service Bus can provide regional resiliency without a dependency on region pairs. For more information, see [Reliability in Service Bus](./reliability-service-bus.md). ## Azure SQL Database To learn about how to create multi-region solutions using Azure SQL Database, see [Reliability in Azure SQL Database](./reliability-sql-database.md). ## Azure SQL Managed Instance To learn about how to create multi-region solutions using Azure SQL Managed Instance, see [Reliability in Azure SQL Managed Instance](./reliability-sql-managed-instance.md). ## Azure Storage To achieve geo-replication in nonpaired regions: - **For Azure Blob Storage (object storage):** To learn about how to create multi-region solutions by using Azure Blob Storage, see [Reliability in Blob Storage](./reliability-storage-blob.md). - **For Azure NetApp Files:** To learn about how to create multi-region solutions using Azure NetApp Files, see [Reliability in Azure NetApp Files](reliability-netapp-files.md). - **For Azure Files:** To learn about how to create multi-region solutions using Azure Files, see [Reliability in Azure Files](./reliability-storage-files.md). - **For Queue Storage:** To learn about how to create multi-region solutions by using Azure Queue Storage, see [Reliability in Queue Storage](./reliability-storage-queue.md). - **For Azure Table Storage:** To learn about how to create multi-region solutions using Azure Table Storage, see [Reliability in Azure Table Storage](./reliability-storage-table.md). ## Azure Virtual Desktop For geo-replication in nonpaired regions for Azure Virtual Desktop, you need to consider session host VMs 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 VMs in multiple regions in an active-active scenario, or replicate them across regions by using [Azure Site Recovery](/azure/site-recovery/azure-to-azure-enable-global-disaster-recovery) in an active-passive scenario. - For storage, see [Azure Storage](#azure-storage). For more information, see [Multiregion business continuity and disaster recovery (BCDR) for Azure Virtual Desktop](/azure/architecture/example-scenario/azure-virtual-desktop/azure-virtual-desktop-multi-region-bcdr#active-active-vs-active-passive) and [Azure Virtual Desktop service architecture and resilience](/azure/virtual-desktop/service-architecture-resilience). ## Azure Virtual Machines To learn about how to create multi-region solutions using Azure Virtual Machines, see [Reliability in Azure Virtual Machines](./reliability-virtual-machines.md). ## Next steps - [Azure services with availability zones](availability-zones-service-support.md) - [List of Azure regions](regions-list.md) - [Reliability guidance](./reliability-guidance-overview.md)