Merge pull request #305772 from flang-msft/fxl---Revise-the-SKU-table-in-AMR-overview-doc-to-indicate-preview-SKUs

v-regandowner · web-flow · commit 064349970a2d · 2025-09-19T13:55:42.000-04:00
fxl---updates to the tier table
diff --git a/articles/redis/TOC.yml b/articles/redis/TOC.yml
@@ -175,7 +175,7 @@ items:
   - name: Move from Azure Cache for Redis to Azure Managed Redis 
     href: migrate/migrate-overview.md
   - name: Migrate to Azure Redis from other caches
-    href: /azure/azure-cache-for-redis/cache-migration-guide
+    href: migrate/migration-guide.md
 
 - name: Azure Cache for Redis 
   href: /azure/azure-cache-for-redis/index
diff --git a/articles/redis/configure.md b/articles/redis/configure.md
@@ -27,10 +27,10 @@ You can view and configure the following settings using the **Resource Menu**.
 - [Settings](#settings)
   - [Authentication](#authentication)
   - [Advanced settings](#advanced-settings)
-  - [Data persistence](#data-persistence-preview)
+  - [Data persistence](#data-persistence)
   - [Encryption](#encryption)
   - [Active geo-replication](#active-geo-replication)
-  - [Scale](#scale-preview)
+  - [Scale](#scale)
   - [Properties](#properties)
   - [Locks](#locks)
 - [Administration](#administration)
@@ -76,10 +76,10 @@ The **Settings** section allows you to access and configure the following settin
 
 - [Authentication](#authentication)
 - [Advanced settings](#advanced-settings)
-- [Data persistence](#data-persistence-preview) (preview)
+- [Data persistence](#data-persistence) 
 - [Encryption](#encryption)
 - [Active geo-replication](#active-geo-replication)
-- [Scale](#scale-preview)
+- [Scale](#scale)
 - [Properties](#properties)
 - [Locks](#locks)
 
@@ -109,7 +109,7 @@ The following properties are set:
   - Eviction Policy
   - Defer Redis DB version updates
 
-### Data persistence (preview)
+### Data persistence
 
 Use **Data persistence** to enable, disable, or configure data persistence for your Redis cache. Azures Managed Redis offers Redis persistence using either RDB persistence or AOF persistence.
 
@@ -125,7 +125,7 @@ For more information, see [Configure disk encryption for Azure Managed Redis ins
 This functionality can be used to replicate a cache across Azure regions, providing greater data durability and availability.
 For more information, see [Configure active geo-replication for Azure Managed Redis instances](how-to-active-geo-replication.md)
 
-### Scale (preview)
+### Scale
 
 Select **Scale** to view or change the size and performance tier of your Redis instance. For more information on scaling, see [How to Scale Azure Managed Redis](how-to-scale.md).
 
diff --git a/articles/redis/how-to-persistence.md b/articles/redis/how-to-persistence.md
@@ -1,5 +1,5 @@
 ---
-title: Configure data persistence (preview) - Azure Managed Redis
+title: Configure data persistence - Azure Managed Redis
 description: Learn how to configure and manage data persistence your Azure Managed Redis instances
 ms.date: 05/18/2025
 ms.topic: conceptual
@@ -12,7 +12,7 @@ appliesto:
 ---
 # Configure data persistence for an Azure Managed Redis instance
 
-[Redis persistence (preview)](https://redis.io/topics/persistence) allows you to persist data stored in cache instance. If there's a hardware failure, the cache instance is rehydrated with data from the persistence file when it comes back online. The ability to persist data is an important way to boost the durability of a cache instance because all cache data is stored in memory. Data loss is possible if a failure occurs when cache nodes are down. Persistence should be a key part of your high availability and disaster recovery strategy with Azure Managed Redis.
+[Redis persistence)](https://redis.io/topics/persistence) allows you to persist data stored in cache instance. If there's a hardware failure, the cache instance is rehydrated with data from the persistence file when it comes back online. The ability to persist data is an important way to boost the durability of a cache instance because all cache data is stored in memory. Data loss is possible if a failure occurs when cache nodes are down. Persistence should be a key part of your high availability and disaster recovery strategy with Azure Managed Redis.
 
 > [!IMPORTANT]
 >
diff --git a/articles/redis/media/overview/sku-tiers-large.png b/articles/redis/media/overview/sku-tiers-large.png
diff --git a/articles/redis/media/overview/sku-tiers.png b/articles/redis/media/overview/sku-tiers.png
diff --git a/articles/redis/migrate/migration-guide.md b/articles/redis/migrate/migration-guide.md
@@ -7,12 +7,11 @@ ms.custom:
   - ignite-2024
   - build-2025
 appliesto:
-  - ✅ Azure Cache for Redis
-  - ✅ Azure Managed Redis
+    - ✅ Azure Managed Redis
 ---
 # Migrate to Azure Managed Redis from other caches
 
-This article describes a number of approaches to migrate an existing Redis cache running on-premises or in another cloud service to Azure Managed Redis.
+This article describes a number of approaches to migrate an existing cache running on-premises or in another cloud service to Azure Managed Redis.
 
 ## Migration scenarios
 
diff --git a/articles/redis/overview.md b/articles/redis/overview.md
@@ -1,8 +1,8 @@
 ---
 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: 05/18/2025
-ms.topic: how-to
+ms.date: 09/19/2025
+ms.topic: overview
 ms.custom:
   - ignite-2024
   - build-2025
@@ -46,10 +46,11 @@ Azure Managed Redis supports Redis version 7.4.x. For more information, see [How
 
 There are four tiers of Azure Managed Redis available, each with different performance characteristics and price levels.
 
-Three tiers are for in-memory data:
+### Tiers and SKUs at a glance
 
-[!INCLUDE [tier-preview](includes/tier-preview.md)]
+:::image type="content" source="media/overview/sku-tiers.png" alt-text="An image of a table that shows a comparison of skus and tiers." lightbox="media/overview/sku-tiers-large.png":::
 
+Three tiers store in-memory data:
 - **Memory Optimized** Ideal for memory-intensive use cases that require a high memory-to-vCPU ratio (8:1) but don't need the highest throughput performance. It provides a lower price point for scenarios where less processing power or throughput is necessary, making it an excellent choice for development and testing environments.
 - **Balanced (Memory + Compute)** Offers a balanced memory-to-vCPU (4:1) ratio, making it ideal for standard workloads. This tier provides a healthy balance of memory and compute resources.
 - **Compute Optimized** Designed for performance-intensive workloads requiring maximum throughput, with a low memory-to-vCPU (2:1) ratio. It's ideal for applications that demand the highest performance.
@@ -58,22 +59,18 @@ One tier stores data both in-memory and on-disk:
 
 - **Flash Optimized (preview)** Enables Redis clusters to automatically move less frequently accessed data from memory (RAM) to NVMe storage. This reduces performance, but allows for cost-effective scaling of caches with large datasets.
 
+You can also use the [data persistence](how-to-persistence.md) feature to store data on-disk for the in-memory tiers. Data persistence stores a backup copy of data on-disk for quick recovery if you experience  an unexpected outage. This is different than the Flash Optimized tier, which is designed to store data on-disk for typical operations.
+
+Storing some data on-disk using the Flash Optimized tier doesn't increase data resiliency. You can use data persistence on the Flash Optimized tier as well.
+
 >[!NOTE]
 > For more information on how the Flash Optimized tier is architected, see [Azure Managed Redis Architecture](architecture.md#flash-optimized-tier)
 >
 
->[!IMPORTANT]
-> You can also use the [data persistence (preview)](how-to-persistence.md) feature to store data on-disk for the in-memory tiers. Data persistence stores a backup copy of data on-disk for quick recovery if you experience  an unexpected outage. This is different than the Flash Optimized tier, which is designed to store data on-disk for typical operations.
-> Storing some data on-disk using the Flash Optimized tier doesn't increase data resiliency. You can use data persistence on the Flash Optimized tier as well.
->
-
-For instructions on how to scale between tiers and SKUs, see [Scale an Azure Managed Redis instance](how-to-scale.md).
+- For instructions on how to scale between tiers and SKUs, see [Scale an Azure Managed Redis instance](how-to-scale.md).
+- For pricing information, see the [Azure Managed Redis Pricing](https://aka.ms/amrpricing)
 
-### Tiers and SKUs at a glance
-
-:::image type="content" source="media/how-to-scale/tier-diagram.png" alt-text="Table showing the different memory and vCPU configurations for each SKU and tier of Azure Managed Redis.":::
-
-For pricing information, see the [Azure Managed Redis Pricing](https://aka.ms/amrpricing)
+[!INCLUDE [tier-preview](includes/tier-preview.md)]
 
 ### Feature comparison
 
@@ -87,8 +84,8 @@ The following table helps describe some of the features supported by tier:
 | [Replication and failover](failover.md)                                                 | Yes               | Yes               | Yes               | Yes               |
 | [Network isolation](private-link.md)                                                    | Yes               | Yes               | Yes               | Yes               |
 | [Microsoft Entra ID based authentication](entra-for-authentication.md)                             | Yes               | Yes               | Yes               | Yes               |
-| [Scaling (preview)](how-to-scale.md)                                                              | Yes               | Yes               | Yes               | Yes               |
-| [Data persistence (preview)](how-to-persistence.md)                                       | Yes               | Yes               | Yes               | Yes               |
+| [Scaling](how-to-scale.md)                                                              | Yes               | Yes               | Yes               | Yes               |
+| [Data persistence](how-to-persistence.md)                                       | Yes               | Yes               | Yes               | Yes               |
 | [Zone redundancy](high-availability.md)                                                 | Yes               | Yes               | Yes               | Yes               |
 | [Geo-replication](how-to-active-geo-replication.md)                                     | Yes (Active)      | Yes (Active)      | Yes (Active)      | No                |
 | Non-clustered instances                                                               | Yes             | Yes               | Yes                 | No                |
@@ -112,31 +109,7 @@ The following table helps describe some of the features supported by tier:
 - **Network performance**: If you have a workload that requires high throughput, network bandwidth might cause a bottleneck. You can increase bandwidth by moving up to a higher performance tier or by moving to a large instance size. Larger size instances have more bandwidth because of the underlying VM that hosts the cache. Higher bandwidth limits help you avoid network saturation that causes timeouts in your application. For more information on bandwidth performance, see [Performance testing](best-practices-performance.md)
 - **Maximum number of client connections**: Each SKU has a maximum number of client connections. This limit increases with higher performance tiers and larger instances sizes. The following table shows the maximum client connections allowed per Azure Managed Redis SKU.
 
-[!INCLUDE [tier-preview](includes/tier-preview.md)]
-
-|  Size (GB)  |    Memory Optimized   |    Balanced   |   Compute Optimized  |  Flash Optimized (preview)|
-|:-----------:|:---------------------:|:-------------:|:--------------------:|:--------------------:|
-|    0.5      |       -               |    15,000      |         -            |       -              |
-|     1       |       -               |    15,000      |         -            |       -              |
-|     3       |       -               |    15,000      |         30,000        |       -              |
-|     6       |       -               |    15,000      |         30,000        |       -              |
-|     12      |   15,000               |    30,000      |         75,000        |       -              |
-|     24      |   30,000               |    75,000      |         150,000       |       -              |
-|     60      |   75,000               |    150,000     |         200,000       |       -              |
-|     120     |   150,000              |    200,000     |         200,000       |       -              |
-|     180 *   |   200,000              |    200,000     |         200,000       |       -              |
-|     240 *   |   200,000              |    200,000     |         200,000       |       75,000          |
-|     360 *   |   200,000              |    200,000     |         200,000       |       -              |
-|     480 *   |   200,000              |    200,000     |         200,000       |       150,000         |
-|     720 *   |   200,000              |    200,000     |         200,000       |       200,000         |
-|     960 *   |   200,000              |    200,000     |         -             |       200,000         |
-|     1440 *  |   200,000              |        -       |         -             |       200,000         |
-|     1920 *  |   200,000              |        -       |         -             |       200,000         |
-|     4500 *  |       -                |        -       |         -             |       200,000         |
-
-  \* These tiers are in Public Preview.
-
-- **High availability**: Azure Managed Redis provides high availability. The SLA only covers connectivity to the cache endpoints. The SLA doesn't cover protection from data loss. For more information on the SLA, see the [SLA](https://azure.microsoft.com/support/legal/sla/cache/v1_0/). It's possible to disable high availability in an Azure Managed Redis instance. This lowers the price but results in data loss and downtime. We only recommend disabling high availability for dev/test scenarios.
+ **High availability**: Azure Managed Redis provides high availability. The SLA only covers connectivity to the cache endpoints. The SLA doesn't cover protection from data loss. For more information on the SLA, see the [SLA](https://azure.microsoft.com/support/legal/sla/cache/v1_0/). It's possible to disable high availability in an Azure Managed Redis instance. This lowers the price but results in data loss and downtime. We only recommend disabling high availability for dev/test scenarios.
 
 ### Other pricing considerations
 
