Added preview notes

Author: flang-msft

articles/redis/includes/tier-preview.md

@@ -0,0 +1,10 @@
+---
+ms.date: 12/17/2024
+
+ms.topic: include
+---
+
+> [!IMPORTANT]
+> All in-memory tiers with 250 G of storage are in the preview including Memory Optimized M250 and higher; Balanced B250 and higher; and Compute optimized X250 and higher. All these tiers are in preview
+>
+> All Flash Optimized tiers are in preview.

articles/redis/overview.md

@@ -49,24 +49,26 @@ There are four tiers of Azure Managed Redis available, each with different perfo
 
 Three tiers are for in-memory data:
 
+[!INCLUDE [tier-preview](includes/tier-preview.md)]
+
 - **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.
 
 One tier stores data both in-memory and on-disk:
 
-- **Flash Optimized** 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.
+- **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.
 
 >[!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](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.
+> 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 (preview) an Azure Managed Redis instance](how-to-scale.md).
 
 ### Tiers and SKUs at a glance
 
@@ -86,10 +88,11 @@ 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](how-to-scale.md)                                                              | Yes               | Yes               | Yes               | Yes               |
-| [Data persistence](how-to-persistence.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               |
 | [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 (preview)                                                               | Yes             | Yes               | Yes                 | No                |
 | [Connection audit logs](monitor-diagnostic-settings.md)                                 | Yes (Event-based) | Yes (Event-based) | Yes (Event-based) | Yes (Event-based) |
 | [JSON data structures(that is, Redis JSON)](redis-modules.md)                              | Yes               | Yes               | Yes               | Yes               |
 | [Search functionality (including vector search)](redis-modules.md)                      | Yes               | Yes               | Yes               | No                |