[AMR] Cross-ref reliability content

Author: dlepow

articles/redis/architecture.md

@@ -127,7 +127,11 @@ This table shows a general example of the relationship of _Size_ to _vCPUs/prima
 
 [!INCLUDE [tier-preview](includes/tier-preview.md)]
 
-## Running without high availability mode enabled
+## High availability mode 
+
+High availability (HA) can be enabled on Azure Managed Redis instances in all tiers. This configuration is recommended for all production scenarios and for access to the availability SLA.
+
+When you enable HA mode, your instance is deployed with primary and replica shards distributed across at least two nodes. In regions that support availability zones, Azure Managed Redis distributes the nodes across zones by default. In regions without availability zones, the primary and replica shards are distributed across at least two nodes in the same zone. For more information, see [Reliability in Azure Managed Redis](/azure/reliability/reliability-managed-redis).
 
 You can run without high availability (HA) mode enabled. This configuration means that your Redis instance doesn't have replication enabled and doesn't have access to the availability SLA. Don't run in non-HA mode outside of development and test scenarios. You can't disable high availability in an instance that you already created. You can enable high availability in an instance that doesn't have it. Because an instance running without high availability uses fewer VMs and nodes, vCPUs aren't used as efficiently, so performance might be lower.
 

articles/redis/overview.md

@@ -1,7 +1,7 @@
 ---
 title: What is Azure Managed Redis?
 description: Learn about Azure Managed Redis to enable cache-aside, content caching, user session caching, job and message queuing, and distributed transactions.
-ms.date: 11/10/2025
+ms.date: 03/04/2026
 ms.topic: overview
 ai-usage: ai-assisted
 ms.custom:
@@ -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, an Azure Managed Redis instance is deployed with primary and replica shards distributed across at least two nodes. In regions that support availability zones, Azure Managed Redis distributes the nodes across zones by default. 
 
-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).
+In regions without availability zones, the primary and replica shards are distributed across at least 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.