From 62d9b1f6146ea5c56e95b3e4b0d041f4c7cfef0f Mon Sep 17 00:00:00 2001 From: Vam Date: Thu, 23 Oct 2025 11:31:16 -0700 Subject: [PATCH] Change title to 'Create a new Azure Managed Redis Instance' Updated section title and clarified migration approach for Azure Redis. --- articles/redis/migrate/migrate-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/redis/migrate/migrate-overview.md b/articles/redis/migrate/migrate-overview.md index 7a9ce300f39ef..08904eeec17c2 100644 --- a/articles/redis/migrate/migrate-overview.md +++ b/articles/redis/migrate/migrate-overview.md @@ -263,7 +263,7 @@ Learn more at: | Dual-write data to two caches | No data loss or downtime. Uninterrupted operations of the existing cache. Easier testing of the new cache. | Needs two caches for an extended period of time. | | Migrate data programmatically | Full control over how data are moved. | Requires custom code. | -#### Create a new Azure Cache for Redis +#### Create a new Azure Managed Redis Instance This approach technically isn't a migration. If losing data isn't a concern, the easiest way to move to Azure Managed Redis tier is to create new cache instance and connect your application to it. For example, if you use Redis as a look-aside cache of database records, you can easily rebuild the cache from scratch. General steps to implement this option are: