Merge pull request #286457 from igorpag/igorpag-rel-patch3

Updates submitted by FTA as agreed with @anaharris-ms

Author: Jill Grant

articles/reliability/cross-region-replication-azure-no-pair.md

@@ -1,107 +1,102 @@
 ---
-title: Cross-region replication for non-paired regions
-description: Learn about cross-region replication for non-paired regions
+title: Cross-region replication for nonpaired regions
+description: Learn about cross-region replication for nonpaired regions
 author: anaharris-ms
 ms.service: reliability
 ms.subservice: availability-zones
 ms.topic: conceptual
-ms.date: 06/14/2024
+ms.date: 09/10/2024
 ms.author: anaharris
 ms.custom: references_regions
 ---
 
-# Cross-region replication solutions for non-paired regions
+# Cross-region replication solutions for nonpaired regions
 
 Some Azure services support cross-region replication to ensure business continuity and protect against data loss. These services make use of another secondary region that uses *cross-region replication*. Both the primary and secondary regions together form a [region pair](./cross-region-replication-azure.md#azure-paired-regions).
 
-However, there are some [regions that are non-paired](./cross-region-replication-azure.md#regions-with-availability-zones-and-no-region-pair) and so require alternative methods to achieving geo-replication. 
+However, there are some [regions that are nonpaired](./cross-region-replication-azure.md#regions-with-availability-zones-and-no-region-pair) and so require alternative methods to achieving geo-replication. 
 
 This document lists some of the services and possible solutions that support geo-replication methods without requiring paired regions. 
 
 
+## Azure API Management
+Azure API Management doesn't provide a real cross-region replication feature. However, you can use its [backup and restore feature](/azure/api-management/api-management-howto-disaster-recovery-backup-restore) to export the configuration of an API Management service instance in one region and import it into another region. As long as the storage account used for the backup is accessible from the target region, there's no paired region dependency. An operational guidance is provided in [this article](/azure/api-management/api-management-howto-migrate).
+
+
 ## Azure App Service
-For App Service, custom backups are stored on a selected storage account. As a result, there's a dependency for cross-region restore on GRS and paired regions. For automatic backup type, you can't backup/restore across regions. As a workaround, you can implement a custom file copy mechanism for the saved data set to manually copy across non-paired regions and different storage accounts.
+For App Service, custom backups are stored on a selected storage account. As a result, there's a dependency for cross-region restore on GRS and paired regions. For automatic backup type, you can't backup/restore across regions. As a workaround, you can implement a custom file copy mechanism for the saved data set to manually copy across nonpaired regions and different storage accounts.
 
-## Azure Backup
 
-To achieve geo-replication in non-paired regions:
+## Azure Cache for Redis
+Azure Cache for Redis provide two distinct cross-region replication options that are [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). In both cases, there's no explicit dependency on region pairs.
 
-- Use [Azure Site Recovery](/azure/site-recovery/azure-to-azure-enable-global-disaster-recovery).  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 non-paired region if it is supported by Azure Site Recovery. You can have maximum data retention up to 15 days with Azure Site Recovery.
-- Use [Zone-redundant Storage](../backup/backup-overview.md#why-use-azure-backup) to replicate your data in availability zones, guaranteeing data residency and resiliency in the same region.
 
+## Azure Container Registry
+Geo-replication enables an Azure container registry to function as a single registry, serving multiple regions with multi-primary regional registries. There's no restrictions dictated by region pairs for this feature. For more information, see [Geo-replication in Azure Container Registry](/azure/container-registry/container-registry-geo-replication).
 
 
-## Azure Database for MySQL 
+## 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 restriction.
 
 
+## Azure Database for MySQL 
 Choose any [Azure Database for MySQL available Azure regions](/azure/mysql/flexible-server/overview#azure-region) to spin up 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:
 
-For geo-replication in non-paired regions with Azure Database for PostgreSQL, you can use:
 
-**Managed service with geo-replication**: Azure 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 may 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*.
+**Managed service with geo-replication**: Azure 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 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 below to replicate the data to a non-paired region.  
+You can also utilize any of the two customer-managed data migration methods listed to replicate the data to a nonpaired region.  
 
 - [Copy](/azure/postgresql/migrate/how-to-migrate-using-dump-and-restore?tabs=psql).
 
 - [Logical Replication & Logical Decoding](/azure/postgresql/flexible-server/concepts-logical).
-
-
 
-## Azure Data Factory
 
-For geo-replication in non-paired regions, Azure Data Factory (ADF) supports Infrastructure-as-code provisioning of ADF pipelines combined with [Source Control for ADF](/azure/data-factory/concepts-data-redundancy#using-source-control-in-azure-data-factory).
+## 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/data-factory/concepts-data-redundancy#using-source-control-in-azure-data-factory).
 
 
 ## Azure Event Grid
+For geo-replication of Event Grid topics in nonpaired regions, you can implement [client-side failover](/azure/event-grid/custom-disaster-recovery-client-side).
 
-For geo-replication of Event Grid topics in non-paired regions, you can implement [client-side failover](/azure/event-grid/custom-disaster-recovery-client-side).
 
 ## Azure IoT Hub 
-
-For geo-replication in non-paired regions, use the [concierge pattern](/azure/iot-hub/iot-hub-ha-dr#achieve-cross-region-ha) for routing to a secondary IoT Hub. 
-
-
-## Azure Key Vault
-
-[!INCLUDE [Key Vault in non-paired regions guidance](~/reusable-content/ce-skilling/azure/includes/key-vault/includes/key-vault-non-paired-regions.md)]
-
+For geo-replication in nonpaired regions, use the [concierge pattern](/azure/iot-hub/iot-hub-ha-dr#achieve-cross-region-ha) for routing to a secondary IoT Hub. 
 
 
 ## Azure Kubernetes Service (AKS)
-
 Azure Backup can provide protection for AKS clusters, including a [cross-region restore (CRR)](/azure/backup/tutorial-restore-aks-backups-across-regions) feature that's currently in preview and only supports Azure Disks. Although the CRR feature relies on GRS paired regions replicas, any dependency on CRR can be avoided if the AKS cluster stores data only in external storage and avoids using "in-cluster" solutions.
 
 
 ## 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).
 
-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, by using either [Geo Replication](/azure/service-bus-messaging/service-bus-geo-replication) or [Geo-Disaster Recovery](/azure/service-bus-messaging/service-bus-geo-replication) features.
 
-## Azure SQL Database
 
-For geo-replication in non-paired regions with Azure SQL Database, you can use:
+## Azure SQL Database
+For geo-replication in nonpaired regions with Azure SQL Database, you can use:
 
 - [Failover group feature](/azure/azure-sql/database/failover-group-sql-db?view=azuresql&preserve-view=true) that replicates across any combination of Azure regions without any dependency on underlying storage GRS.
 
-- [Active geo-replication feature](/azure/azure-sql/database/active-geo-replication-overview?view=azuresql&preserve-view=true) to create a continuously synchronized readable secondary database for a primary database. The readable secondary database may 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*.
+- [Active geo-replication feature](/azure/azure-sql/database/active-geo-replication-overview?view=azuresql&preserve-view=true) 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 non-paired regions with Azure SQL Managed Instance, you can use:
+## Azure SQL Managed Instance 
+For geo-replication in nonpaired regions with Azure SQL Managed Instance, you can use:
 
 - [Failover group feature](/azure/azure-sql/managed-instance/failover-group-sql-mi?view=azuresql&preserve-view=true) that replicates across any combination of Azure regions without any dependency on underlying storage GRS.
 
 
 ## Azure Storage
-
-
-To achieve geo-replication in non-paired regions: 
+To achieve geo-replication in nonpaired regions: 
 
 - **For Azure Object Storage**:
 
@@ -113,8 +108,8 @@ To achieve geo-replication in non-paired regions:
    >Object replication isn't supported for [Azure Data Lake Storage](../storage/blobs/data-lake-storage-best-practices.md).
 
 
+- **For Azure NetApp Files (ANF)**, you can replicate to a set of nonstandard pairs besides Azure region pairs. See [Azure NetApp Files (ANF) cross-region replication](/azure/azure-netapp-files/cross-region-replication-introduction).
 
-- **For Azure NetApp Files (ANF)**, you can replicate to a set of non-standard pairs besides Azure region pairs.  See [Azure NetApp Files (ANF) cross-region replication](/azure/azure-netapp-files/cross-region-replication-introduction).
 
 - **For Azure Files:**
 
@@ -132,8 +127,8 @@ To achieve geo-replication in non-paired regions:
    > 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.
 
 
-
-
+## Azure Virtual Machines
+To achieve geo-replication in nonpaired regions, [Azure Site Recovery](/azure/site-recovery/azure-to-azure-enable-global-disaster-recovery) service can be sued. 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.