Merge pull request #313804 from shpathak-msft/main

Add migration tooling details

Author: Stacyrch140

articles/azure-cache-for-redis/TOC.yml

@@ -35,17 +35,21 @@
     items:
     - name: Overview
       href: /azure/redis/migrate/migrate-basic-standard-premium-overview
-    - name: Understand
+    - name: Understand differences
       href: /azure/redis/migrate/migrate-basic-standard-premium-understand
-    - name: Self-service
+    - name: Explore migration options
+      href: /azure/redis/migrate/migrate-basic-standard-premium-options
+    - name: Self-service migration
       href: /azure/redis/migrate/migrate-basic-standard-premium-self-service
+    - name: Migration using tooling
+      href: /azure/redis/migrate/migrate-basic-standard-premium-with-tooling
   - name: Migrate Enterprise tier to Azure Managed Redis
     items:
     - name: Overview
       href: /azure/redis/migrate/migrate-redis-enterprise-overview
-    - name: Understand
+    - name: Understand differences
       href: /azure/redis/migrate/migrate-redis-enterprise-understand
-    - name: Self-service
+    - name: Self-service migration
       href: /azure/redis/migrate/migrate-redis-enterprise-self-service
   - name: Migrate to Azure Redis from other caches
     href: cache-migration-guide.md

articles/azure-cache-for-redis/cache-whats-new.md

@@ -15,6 +15,10 @@ appliesto:
 
 Find out what's new in Azure Redis.
 
+## April 2026
+
+### Tooling to migrate Azure Cache for Redis instance to Azure Managed Redis (preview)
+Tooling to aid migration from Azure Cache for Redis (Basic, Standard, and Premium) is now available in Public Preview. When migration is initiated using the tooling, your Azure Cache for Redis endpoint is updated to point to your precreated Azure Managed Redis. For more information, see [Migration using tooling](/azure/redis/migrate/migrate-basic-standard-premium-with-tooling).
 
 ## October 2025
 

articles/redis/TOC.yml

@@ -161,23 +161,27 @@ items:
           href: /azure/developer/github-copilot-azure?toc=/azure/redis/toc.json&bc=/azure/redis/breadcrumb/toc.json
   - name: Migration
     items:
-      - name: Migrate Basic, Standard, or Premium tiers
+      - name: Migrate Basic, Standard, or Premium tiers to Azure Managed Redis
         items:
           - name: Overview
-            href: migrate/migrate-basic-standard-premium-overview.md
-          - name: Understand
-            href: migrate/migrate-basic-standard-premium-understand.md
-          - name: Self-service
-            href: migrate/migrate-basic-standard-premium-self-service.md
-      - name: Migrate Enterprise tier
+            href: /azure/redis/migrate/migrate-basic-standard-premium-overview
+          - name: Understand differences
+            href: /azure/redis/migrate/migrate-basic-standard-premium-understand
+          - name: Explore migration options
+            href: /azure/redis/migrate/migrate-basic-standard-premium-options
+          - name: Self-service migration
+            href: /azure/redis/migrate/migrate-basic-standard-premium-self-service
+          - name: Migration using tooling
+            href: /azure/redis/migrate/migrate-basic-standard-premium-with-tooling
+      - name: Migrate Enterprise tier to Azure Managed Redis
         items:
           - name: Overview
             href: migrate/migrate-redis-enterprise-overview.md
-          - name: Understand
+          - name: Understand differences
             href: migrate/migrate-redis-enterprise-understand.md
-          - name: Self-service
+          - name: Self-service migration
             href: migrate/migrate-redis-enterprise-self-service.md
-      - name: Migrate to Azure Redis from other caches
+      - name: Migrate to Azure Managed Redis from other caches
         href: migrate/migration-guide.md
   - name: Azure Cache for Redis
     items:

articles/redis/migrate/migrate-basic-standard-premium-options.md

@@ -0,0 +1,64 @@
+---
+title: Migration options - Migrate from Basic, Standard, and Premium tiers to Azure Managed Redis
+description: Explore the available migration options for moving from Azure Cache for Redis Basic, Standard, and Premium tiers to Azure Managed Redis.
+ms.date: 03/26/2026
+ms.topic: concept-article
+ai-usage: ai-assisted
+appliesto:
+  - ✅ Azure Cache for Redis
+  - ✅ Azure Managed Redis
+
+#customer intent: As a developer with Azure Cache for Redis Basic, Standard, or Premium instances, I want to understand the migration options available to me when moving to Azure Managed Redis.
+---
+
+# Migration options - Basic, Standard, and Premium tiers to Azure Managed Redis
+
+This article describes the available migration options for moving from Azure Cache for Redis Basic, Standard, and Premium tiers to Azure Managed Redis.
+
+[!INCLUDE [Redis migration agent skill](../includes/redis-migration-agent-skill.md)]
+
+There are two migration paths to consider. We recommend **Option 1** for most customers.
+
+## Option 1: (Recommended) Self-service migration
+
+In this approach, you create a new Azure Managed Redis instance, migrate your data to it, update your applications to point to the new instance, and then delete the old Azure Cache for Redis instance.
+
+**Why this is recommended:**
+
+- **Full control.** You decide exactly when to cut over, and you can test the new instance before switching production traffic. If you have multiple applications connecting to a shared Redis instance, you can choose to migrate one application at a time.
+- **Minimal downtime.** By using a data sync strategy (such as dual-write or export/import), you can keep both caches running in parallel and switch over with minimal disruption.
+- **Independent validation.** You can verify the new Azure Managed Redis instance works correctly with your application before decommissioning the old cache.
+
+The [Self-service migration](migrate-basic-standard-premium-self-service.md) article provides step-by-step instructions for this approach, including multiple [data migration strategies](migrate-basic-standard-premium-self-service.md#step-2-migrate-your-data).
+
+## Option 2: Use migration tooling (preview)
+
+Azure provides built-in migration tooling (preview) that automates endpoint migration from your existing Azure Cache for Redis instance to a precreated Azure Managed Redis instance. After you create a new Azure Managed Redis instance and initiate the migration, the tooling updates your Azure Cache for Redis hostname to point to Azure Managed Redis, so your client applications reconnect automatically to the Azure Managed Redis instance using the same hostname and access key. After you validate the migration, delete the old Azure Cache for Redis instance and update your client applications to use the new Azure Managed Redis hostname.
+
+
+> [!IMPORTANT]
+> Review the limitations below carefully before choosing this approach.
+
+### Limitations
+
+- **Precreated target Azure Managed Redis required.** You choose and create the Azure Managed Redis instance before migration begins.
+- **No control over when cutover happens.** You can use the tool to initiate migration, but have no control on when the traffic cutover exactly happens during the migration.
+- **All client applications impacted simultaneously.** All the client applications that connect to the migrating Redis instance will migrate simultaneously. You cannot migrate one application or service at a time.
+- **Data sync not supported.** This tooling will orchestrate hostname/endpoint migration but does not migrate any data. 
+- **Limited window for rollback.** This flow supports cancellation or rollback after migration starts. However, once migration is successful, you will have limited time window to verify your applications are working as expected and perform any rollback if required.
+- **Limited window to keep both hostnames.** Once migration is successful, we highly recommend you update your applications to use the new Azure Managed Redis hostname. The hostname from your old Azure Cache for Redis instance will be automatically deleted in future.
+- **Temporary management lock during migration.** While status is **Migrating**, other management operations are blocked until migration completes.
+- **Private endpoint not supported.** Caches with private endpoints are not supported.
+- **Virtual network injected caches not supported.**
+- **Geo-repplicated caches not supported.**
+- **Not all cache configurations are copied over.** Configurations or properties like managed identities, firewall rules, persistence settings, update schedules, keyspace notifications are not copied over to the new Azure Managed Redis instance. You will need to configure Azure Managed Redis with the right configuration during creation.
+
+
+The [Migration using tooling](migrate-basic-standard-premium-with-tooling.md) article provides step-by-step instructions for this approach, including multiple [data migration strategies](migrate-basic-standard-premium-self-service.md#step-2-migrate-your-data).
+
+## Related content
+
+- [Migrate from Basic, Standard, and Premium tiers to Azure Managed Redis](migrate-basic-standard-premium-overview.md)
+- [Understand the differences](migrate-basic-standard-premium-understand.md)
+- [Plan migration execution](migrate-basic-standard-premium-self-service.md)
+- [What is Azure Managed Redis?](../overview.md)

articles/redis/migrate/migrate-basic-standard-premium-overview.md

@@ -17,20 +17,29 @@ This guide walks you through migrating your Azure Cache for Redis Basic, Standar
 
 [!INCLUDE [Redis migration agent skill](../includes/redis-migration-agent-skill.md)]
 
-## Understand the differences
+## 1. Understand the differences
 
 Before migrating, review the key differences between Azure Cache for Redis Basic, Standard, and Premium tiers and Azure Managed Redis. Understanding the feature, SKU, and client application differences helps you plan effectively and choose the right Azure Managed Redis size and performance tier.
 
 > [!div class="nextstepaction"]
 > [Understand the differences](migrate-basic-standard-premium-understand.md)
 
+## 2. Explore migration options
 
-## Plan execution
+There are two migration paths to consider — switching over to a new Azure Managed Redis instance manually or using Azure migration tooling. Review the options and their trade-offs to choose the right approach for your scenario.
 
-Follow step-by-step instructions to create your new Azure Managed Redis instance, migrate your data, update your application, and validate the migration.
+> [!div class="nextstepaction"]
+> [Explore migration options](migrate-basic-standard-premium-options.md)
+
+## 3. Plan execution
+
+Based on the option you have chosen to perform migration, follow step-by-step instructions to create your new Azure Managed Redis instance, migrate your data, update your application, and validate the migration.
+
+> [!div class="nextstepaction"]
+> [Plan execution for self-service migration](migrate-basic-standard-premium-self-service.md)
 
 > [!div class="nextstepaction"]
-> [Plan execution](migrate-basic-standard-premium-self-service.md)
+> [Plan migration with tooling](migrate-basic-standard-premium-with-tooling.md)
 
 ## Related content
 

articles/redis/migrate/migrate-basic-standard-premium-self-service.md

@@ -17,24 +17,21 @@ This article provides step-by-step instructions for migration paths. We highly r
 
 [!INCLUDE [Redis migration agent skill](../includes/redis-migration-agent-skill.md)]
 
-## Step 1: Update deployment scripts
-
-Once you have identified the appropriate Azure Managed Redis SKU, update your deployment scripts (such as ARM templates, Bicep files, or Terraform configurations) to provision Azure Managed Redis instead of Azure Cache for Redis.
-
-## Step 2: Create a new Azure Managed Redis instance
+## Step 1: Update deployment scripts and create new Azure Managed Redis instance
 
+1. Once you have identified the appropriate Azure Managed Redis SKU, update your deployment scripts (such as ARM templates, Bicep files, or Terraform configurations) to provision Azure Managed Redis instead of Azure Cache for Redis.
 1. Use the [SKU mapping table](migrate-basic-standard-premium-understand.md#choose-the-right-azure-managed-redis-size-and-sku) to select the right size (same size or bigger than the existing cache) and performance tier.
 1. Create the instance by following the [Quickstart: Create an Azure Managed Redis Instance](../quickstart-create-managed-redis.md).
 
 > [!TIP]
 > If you're unsure whether your workload is memory-intensive or compute-intensive, start with the **Balanced** performance tier.
 
-## Step 3: Migrate your data
+## Step 2: Migrate your data
 
 Choose a data migration strategy based on your tolerance for downtime and data loss.
 
 > [!NOTE]
-> If your application can tolerate data loss, or can rehydrate the cache from its data source (for example, a look-aside cache pattern), you can skip this step and proceed directly to [Step 4](#step-4-update-your-application).
+> If your application can tolerate data loss, or can rehydrate the cache from its data source (for example, a look-aside cache pattern), you can skip this step and proceed directly to [Step 3](#step-3-update-your-application).
 
 ### Export and import data using an RDB file
 
@@ -47,7 +44,7 @@ Steps:
 
 1. Export the RDB file from the existing Azure Cache for Redis instance using the [export instructions](../../azure-cache-for-redis/cache-how-to-import-export-data.md#export) or the [PowerShell Export cmdlet](/powershell/module/az.rediscache/export-azrediscache).
 1. Import the RDB file into the new Azure Managed Redis instance using the [import instructions](../how-to-import-export-data.md) or the PowerShell Import cmdlet.
-1. Proceed to [Step 4: Update your application](#step-4-update-your-application).
+1. Proceed to [Step 3: Update your application](#step-3-update-your-application).
 
 ### Dual-write strategy
 
@@ -61,7 +58,7 @@ Steps:
 1. Modify your application code to write to both the existing cache and the new Azure Managed Redis instance.
 1. Continue reading data from the existing cache until the new instance is sufficiently populated.
 1. Update the application code to read and write from the new instance only.
-1. Proceed to [Step 4: Update your application](#step-4-update-your-application).
+1. Proceed to [Step 3: Update your application](#step-3-update-your-application).
 
 ### Programmatic migration
 
@@ -75,9 +72,9 @@ Steps:
 1. Create a VM in the same region as the existing cache. If your dataset is large, choose a powerful VM to reduce copying time.
 1. Flush data from the new cache to ensure it's empty. **Don't flush the source cache.**
 1. Copy data from the source cache to the new Azure Managed Redis instance.
-1. Proceed to [Step 4: Update your application](#step-4-update-your-application).
+1. Proceed to [Step 3: Update your application](#step-3-update-your-application).
 
-## Step 4: Update your application
+## Step 3: Update your application
 
 Update your application's connection configuration to point to the new Azure Managed Redis instance. At a minimum, you need to update:
 
@@ -93,7 +90,7 @@ Update your application's connection configuration to point to the new Azure Man
 
 Azure Cache for Redis and Azure Managed Redis are compatible, so no application code changes other than connection configurations are required for most scenarios.
 
-## Step 5: Validate and decommission
+## Step 4: Validate and decommission
 
 1. Verify your application works correctly with the new Azure Managed Redis instance.
 1. Monitor the new cache for expected behavior, performance, and error rates.