Merge pull request #310381 from johndowns/reliability-cache-redis-move

v-ccolin · web-flow · commit 00c61b315f05 · 2026-01-19T16:38:14.000Z
Redis reliability - Update product documentation
diff --git a/articles/redis/TOC.yml b/articles/redis/TOC.yml
@@ -103,6 +103,10 @@ items:
         items:
           - name: Microsoft Entra ID for authentication
             href: entra-for-authentication.md
+      - name: Reliability
+        items:
+          - name: Reliability in Azure Managed Redis
+            href: ../reliability/reliability-managed-redis.md?toc=/azure/redis/toc.json&bc=/azure/redis/breadcrumb/toc.json
       - name: Security and networking
         items:
           - name: Using TLS with a managed cache
diff --git a/articles/redis/breadcrumb/toc.yml b/articles/redis/breadcrumb/toc.yml
@@ -0,0 +1,11 @@
+- name: Azure
+  tocHref: /azure
+  topicHref: /azure/index
+  items:
+  - name: Redis
+    tocHref: /azure/redis/
+    topicHref: /azure/redis/index
+    items:
+    - name: Redis
+      tocHref: /azure/reliability/
+      topicHref: /azure/redis/index/
diff --git a/articles/redis/media/migrate-cache-redis/enable-zones-on-existing-cache.png b/articles/redis/media/migrate-cache-redis/enable-zones-on-existing-cache.png
diff --git a/articles/redis/migrate-cache-redis-zones.md b/articles/redis/migrate-cache-redis-zones.md
@@ -77,7 +77,7 @@ Updating `ZonalAllocationPolicy` to any other value than `Automatic` isn't suppo
 Learn more about:
 
 > [!div class="nextstepaction"]
-> [Azure services that support availability zones](availability-zones-service-support.md)
+> [Azure services that support availability zones](/azure/reliability/availability-zones-service-support)
 
 > [!div class="nextstepaction"]
-> [Azure regions that support availability zones](regions-list.md)
+> [Azure regions that support availability zones](/azure/reliability/regions-list)
diff --git a/articles/redis/migrate/migrate-overview.md b/articles/redis/migrate/migrate-overview.md
@@ -66,7 +66,7 @@ Finally, Azure Managed Redis offers the Microsoft Entra ID authentication when y
 | Azure Sovereign Cloud support     | No                                                | Yes (coming soon)                 |
 | Hostname DNS suffix               | `<name>.<region>.redisenterprise.cache.azure.net` | `<name>.<region>.redis.azure.net` |
 
-\* When **High availability** is enabled, Azure Managed Redis is zone redundant in regions with multiple Availability Zones.
+\* When **High availability** is enabled, Azure Managed Redis is zone redundant in regions with multiple availability zones. For more information, see [Reliability in Azure Managed Redis](/azure/reliability/reliability-managed-redis).
 
 ## Considerations when you move from Enterprise to Azure Managed Redis
 
diff --git a/articles/redis/overview.md b/articles/redis/overview.md
@@ -97,9 +97,9 @@ The following table helps describe some of the features supported by tier:
 | [Time Series database capability (that is, Redis TimeSeries)](redis-modules.md)            | Yes                    | Yes                    | Yes                    | Yes                    |
 | [Import/Export](how-to-import-export-data.md)                                              | Yes                    | Yes                    | Yes                    | Yes                    |
 
-\* When **High availability** is enabled, Azure Managed Redis is zone redundant in regions with multiple Availability Zones. 
+\* When **High availability** is enabled, Azure Managed Redis is zone redundant in regions with multiple availability zones. 
 
-When you use High availability (HA), an Azure Managed Redis instance is deployed with primary and replica shards across two nodes. In regions without Availability Zones, the primary and replica shards are deployed across two nodes in the same zone.
+When you use High availability (HA), an Azure Managed Redis instance is deployed with primary and replica shards across two nodes. In regions without availability zones, the primary and replica shards are deployed across two nodes in the same zone. For more information, see [Reliability in Azure Managed Redis](/azure/reliability/reliability-managed-redis).
 
 > [!IMPORTANT]
 > The Balanced B0 and B1 SKU options don't support active geo-replication.
diff --git a/articles/reliability/TOC.yml b/articles/reliability/TOC.yml
@@ -98,12 +98,6 @@ items:
         href: /azure/service-fabric/service-fabric-disaster-recovery?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json#availability-of-the-service-fabric-cluster
   - name: Databases
     items:
-    - name: Azure Cache for Redis
-      items:
-      - name: Availability zones
-        href: ../azure-cache-for-redis/cache-how-to-zone-redundancy.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
-      - name: Disaster recovery
-        href: ../azure-cache-for-redis/cache-how-to-geo-replication.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
     - name: Azure Cosmos DB for NoSQL
       href: reliability-cosmos-db-nosql.md
     - name: Azure Cosmos DB for PostgreSQL
@@ -342,8 +336,6 @@ items:
         href: migrate-recovery-services-vault.md
       - name: Azure Batch
         href: reliability-batch.md#availability-zone-migration
-      - name: Azure Cache for Redis
-        href: migrate-cache-redis.md
       - name: Azure Container Apps
         href: reliability-container-apps.md#resilience-to-availability-zone-failures
       - name: Azure Container Instances
diff --git a/articles/reliability/availability-zones-enable-zone-resiliency.md b/articles/reliability/availability-zones-enable-zone-resiliency.md
@@ -74,7 +74,7 @@ Use the following guidance to prioritize Azure service groups based on their cri
 
 1. **Improve operational data storage resiliency.** Operational data stores contain valuable data that multiple workloads often use, so improving the availability of those data stores can help many workloads.
 
-   For operational data storage resiliency, focus on services like Azure SQL Database, Azure SQL Managed Instance, Azure Storage, Azure Data Lake Storage, Azure Cosmos DB, Azure PostgreSQL Flexible Server, Azure MySQL Flexible Server, and Azure Cache for Redis.
+   For operational data storage resiliency, focus on services like Azure SQL Database, Azure SQL Managed Instance, Azure Storage, Azure Data Lake Storage, Azure Cosmos DB, Azure PostgreSQL Flexible Server, Azure MySQL Flexible Server, and Azure Managed Redis.
 
 1. **Prioritize compute services.** These services are often easy to replicate and distribute among zones because they're stateless.
 
@@ -140,8 +140,8 @@ The following table summarizes the availability zone support for many Azure serv
 | [Azure Bastion](./reliability-bastion.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | Redeployment | No cost impact |
 | [Azure Batch](reliability-batch.md#availability-zone-migration) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Redeployment | No cost impact for same number of virtual machines (VMs) |
 | [Azure Blob Storage](./reliability-storage-blob.md#resilience-to-availability-zone-failures) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Enablement | Moderate cost increase |
-| [Azure Cache for Redis - Enterprise](migrate-cache-redis.md#enabling-zone-redundancy-for-enterprise-and-enterprise-flash-tiers) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Redeployment | No cost impact   |
-| [Azure Cache for Redis - Standard and Premium](migrate-cache-redis.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Enablement | Minimum tier required |
+| [Azure Cache for Redis - Enterprise](../redis/migrate-cache-redis-zones.md#enabling-zone-redundancy-for-enterprise-and-enterprise-flash-tiers) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Redeployment | No cost impact   |
+| [Azure Cache for Redis - Standard and Premium](../redis/migrate-cache-redis-zones.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Enablement | Minimum tier required |
 | [Azure Container Apps](reliability-container-apps.md#resilience-to-availability-zone-failures) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Redeployment | Minimum replica count required |
 | [Azure Container Instances](./reliability-container-instances.md#resilience-to-availability-zone-failures) | | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | Redeployment | No cost impact |
 | [Azure Container Registry](/azure/container-registry/zone-redundancy?toc=/azure/reliability) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | | Always zone resilient | N/A |
diff --git a/articles/reliability/availability-zones-service-support.md b/articles/reliability/availability-zones-service-support.md
@@ -35,7 +35,7 @@ The following table lists zonal and zone-redundant Azure services. Some services
 | [Azure Bastion](./reliability-bastion.md#resilience-to-availability-zone-failures) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: |
 | [Azure Batch](./reliability-batch.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: ||
 | [Azure Blob Storage](./reliability-storage-blob.md#resilience-to-availability-zone-failures) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: ||
-| [Azure Cache for Redis](./migrate-cache-redis.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: |
+| [Azure Cache for Redis](../redis/migrate-cache-redis-zones.md) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: |
 | [Azure Compute Gallery](/azure/virtual-machines/azure-compute-gallery#high-availability) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: ||
 | [Azure Container Apps](reliability-azure-container-apps.md#availability-zone-support) | :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: ||
 | [Azure Container Instances](migrate-container-instances.md) || :::image type="content" source="media/icon-checkmark.svg" alt-text="Yes" border="false"::: |
diff --git a/articles/reliability/overview-reliability-guidance.md b/articles/reliability/overview-reliability-guidance.md
@@ -52,7 +52,6 @@ The following table provides links to reliability guidance for Azure services. E
 |Azure Batch| [Reliability in Batch](reliability-batch.md)||
 |Azure Blob Storage| [Reliability in Blob Storage](reliability-storage-blob.md) ||
 |Azure Bot Service | [Reliability in Bot Service](reliability-bot.md)||
-|Azure Cache for Redis||[Enable zone redundancy for Azure Cache for Redis](../azure-cache-for-redis/cache-how-to-zone-redundancy.md) </p> [Configure passive geo-replication for Premium Azure Cache for Redis instances](../azure-cache-for-redis/cache-how-to-geo-replication.md) |
 |Azure Chaos Studio| [Reliability in Chaos Studio](reliability-chaos-studio.md)||
 |Azure Communications Gateway | | [Reliability in Azure Communications Gateway](../communications-gateway/reliability-communications-gateway.md)|
 |Azure Container Apps| [Reliability in Container Apps](reliability-azure-container-apps.md)||
diff --git a/articles/reliability/regions-multi-region-nonpaired.md b/articles/reliability/regions-multi-region-nonpaired.md
@@ -28,10 +28,6 @@ To learn about how to create multi-region solutions by using Azure API Managemen
 
 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).
diff --git a/articles/reliability/reliability-aks.md b/articles/reliability/reliability-aks.md
@@ -106,7 +106,7 @@ This section describes what to expect when AKS clusters are configured for avail
 
 - **Traffic routing between zones:** When you deploy an AKS cluster that uses availability zones, it's important to ensure that your networking components are also zone resilient. Depending on the load balancers and other networking components that you use, you might need to explicitly configure components to route traffic to the correct nodes in the correct zones and to respond to zone outages. For more information, see [Zone resiliency considerations for AKS](/azure/aks/aks-zone-resiliency).
 
-- **Data replication between zones:** If you run a stateless workload, you should use managed Azure services, such [Azure databases](https://azure.microsoft.com/products/category/databases/), [Azure Cache for Redis](/azure/azure-cache-for-redis/cache-overview), or [Azure Storage](https://azure.microsoft.com/products/category/storage/) to store the application data. You can use these services to help ensure that your traffic can be moved across nodes and zones without risking data loss or affecting the user experience. You can use Kubernetes [deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/), [services](https://kubernetes.io/docs/concepts/services-networking/service/), and [health probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) to manage stateless pods and ensure even distribution across zones.
+- **Data replication between zones:** If you run a stateless workload, you should use managed Azure services, such [Azure databases](https://azure.microsoft.com/products/category/databases/), [Azure Managed Redis](https://azure.microsoft.com/products/managed-redis), or [Azure Storage](https://azure.microsoft.com/products/category/storage/) to store the application data. You can use these services to help ensure that your traffic can be moved across nodes and zones without risking data loss or affecting the user experience. You can use Kubernetes [deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/), [services](https://kubernetes.io/docs/concepts/services-networking/service/), and [health probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) to manage stateless pods and ensure even distribution across zones.
 
    If you need to store state within your cluster by using Azure disks, use Azure zone-redundant storage to help ensure that your data is replicated across multiple availability zones. For more information, see [Choose the right disk type based on application needs](/azure/aks/aks-zone-resiliency#make-your-storage-disk-decision).
 
diff --git a/articles/reliability/reliability-managed-redis.md b/articles/reliability/reliability-managed-redis.md
@@ -182,7 +182,7 @@ When you enable active geo-replication, you are billed for each Azure Managed Re
 
 - **Disable geo-replication on a cache instance**: Remove an instance from a geo-replication group by deleting the cache instance. The remaining instances automatically reconfigure themselves.
 
-### Capacity planning and management
+#### Capacity planning and management
 
 During a region-down event, the other instances might be under higher pressure. If an instance is often already under resource pressure and you need to prepare for the increased capacity requirements during a region failure, consider [overprovisioning the instance](/azure/reliability/concept-redundancy-replication-backup#manage-capacity-with-over-provisioning). To learn how to scale an instance, see [Scale an Azure Managed Redis instance](../redis/how-to-scale.md).
 
diff --git a/redirects/.openpublishing.redirection.reliability.json b/redirects/.openpublishing.redirection.reliability.json
@@ -154,6 +154,11 @@
             "source_path_from_root": "/articles/reliability/reliability-deployment-environments.md",
             "redirect_url": "/azure/deployment-environments/concept-reliability-deployment-environments",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/reliability/migrate-cache-redis.md",
+            "redirect_url": "/azure/redis/migrate-cache-redis-zones",
+            "redirect_document_id": true
         }
     ]
 }
