Author: Purna Mehta, Product Manager, Redis Inc and Shruti Pathak, Product Manager, Microsoft
Today we’re introducing two capabilities for migrating from Azure Cache for Redis (ACR) to Azure Managed Redis (AMR): an AI-assisted planning skill and a native migration workflow in the Azure portal. Used together, these tools provide a structured path from initial assessment to a fully cleaned-up Azure Managed Redis deployment.
This post walks through each phase of the migration, what to expect at each step, and how the agent and portal work together to reduce complexity and risk.
Why Migrate to Azure Managed Redis?
Azure Managed Redis is Microsoft’s next-generation managed Redis offering for enterprise workloads on Azure. It delivers higher throughput and lower latency than Azure Cache for Redis, along with flexible SKU tiers, enhanced clustering, active geo-replication, and advanced persistence options.
Azure Managed Redis supports Redis-based AI workloads on Azure, including integrations for vector search and intelligent caching. If you’re building AI-powered applications on Azure, Azure Managed Redis is the recommended platform for Redis-based scenarios.
We recognize that migrating a production cache requires care. That is why we built an end-to-end experience that begins with AI-assisted planning and ends with a guided portal migration.
There is also a practical reason to start planning now: Azure Cache for Redis is being retired, and Azure Managed Redis is the path forward for Redis workloads on Azure. Migrating early gives you time to validate dependencies, update configurations, and make the transition on your own schedule instead of under deadline pressure. Just as importantly, the Azure Cache for Redis hostname will eventually expire, so cleaning up references to the old hostname is an important part of completing the migration cleanly. For details, see the retirement announcement and this blog post.
The rest of this post outlines the planning and execution phases for migrating from Azure Cache for Redis to Azure Managed Redis with the Redis migration tooling.
Phase 1: Migration Planning
Before touching any infrastructure, you need a clear view of what you are migrating, what the target should look like, and which risks to address. The new Azure Cache for Redis migration agent skill helps with that. You can also refer to the migration documentation here.
The migration agent skill can be added to any AI agent and invoked from AI-powered chat assistants such as GitHub Copilot and Claude. With read access to your Azure subscription, the skill can inspect your existing Azure Cache for Redis instances and help you:
- Compare and contrast Azure Cache for Redis and Azure Managed Redis
- Guide through selecting the appropriate Azure Managed Redis SKUs
- Help convert IaC templates
- Help with planning and execution of migration along with troubleshooting common issues
You interact with it conversationally, asking questions and refining the plan iteratively until you are confident in the approach.
In a typical planning session, the skill analyzes your source cache configuration in detail, including SKU and tier, memory size, eviction policy, persistence settings, clustering topology, TLS configuration, and any geo-replication setup. It then maps those properties to available Azure Managed Redis tiers and recommends the most appropriate target configuration for your workload. The skill can also fetch real-time cache usage metrics and recommend SKU optimizations.
Beyond the SKU recommendation, the skill identifies potential compatibility issues and configuration gaps you need to address before migrating. This might include client library version requirements, changes to supported Redis commands, differences in eviction policy behavior between tiers, or networking considerations if your cache is deployed in a VNet. Surfacing these issues early, before you have provisioned anything, gives you time to address them without pressure.
The skill can also help you choose a migration strategy. If downtime tolerance is low, it walks you through online migration options and what to expect during cutover. If your workload can tolerate a maintenance window, it can outline a simpler offline path. You can also ask follow-up questions about cost, rollback, or how to validate the new instance before switching traffic.
At the end of the planning session, ask the agent for a structured migration checklist. It should summarize the recommended target configuration, pre-migration action items, and the step-by-step plan for Phases 2 and 3. This gives your team a shared reference for execution.
|
Note: The AI-assisted migration planner is intended to support planning, not replace expert judgment. For highly critical workloads, we recommend working closely with a Solutions Architect or migration specialist to validate your plan before proceeding. |
Phase 2: Provision the Target Azure Managed Redis Cache
With a clear migration plan from Phase 1, you are ready to create your Azure Managed Redis target instance. This step is straightforward, but one constraint matters: the target AMR cache must be in the same subscription and region as the source ACR cache. This is a requirement of the portal migration workflow in Phase 3, which links the two instances together to perform the migration.
In the Azure portal, create a new Azure Managed Redis resource in the same subscription and region as your source cache. Apply the tier and SKU recommended in Phase 1, whether that is Balanced for general-purpose workloads, Memory Optimized for memory-intensive scenarios, or Compute Optimized for throughput-heavy applications. Configure the instance as outlined in your migration checklist, including Redis Users for Entra ID authentication, private endpoints, eviction policy, persistence, clustering, and TLS. The migration agent skill can also help update your IaC templates by converting them from Azure Cache for Redis to Azure Managed Redis.
Once the instance is provisioned and running, note the resource name. You will select it by name when you start migration in Phase 3. At this point the AMR instance is empty, which lets you validate the configuration, test connectivity from your application environment, and confirm everything looks correct before migration.
|
Note: Redis Migration tooling works by switching the DNS endpoint from your source Azure Cache for Redis instance to the target Azure Managed Redis instance. No data is transferred as part of this process. |
Phase 3: Initiate Migration from the Azure Portal
Note: Before using the Redis migration tooling, please review the limitations of the tooling and other migration options.
To use the Redis Migration tooling, navigate to your source Azure Cache for Redis instance in the Azure Portal and select Migrate in the command bar.
Choose a target Azure Managed Redis instance from the dropdown, which lists only AMR instances in the same subscription and region as your source cache.
Review the migration summary comparing source and target configurations. An automated compatibility check surfaces warnings or errors with guidance for resolving them. You can acknowledge warnings to proceed, but errors must be addressed first. We strongly recommend running the migration during a maintenance window or low-traffic period.
Your resource state will update to “Migrating” while the migration is in process. After migration completes, the Azure Cache for Redis hostname redirects requests to the Azure Managed Redis instance, allowing applications to continue using the existing source connection string temporarily.
|
Note: Keep your source ACR cache running and do not delete it. If you encounter problems after the migration, you can initiate a rollback to the original ACR cache and resume normal operation while you investigate. The source cache remains available and unchanged throughout the migration process. Once you are confident the new instance is stable and performing as expected, you can retry Phase 3 and then proceed to Phase 4 to clean up the source cache. |
Phase 4: Ensure success and delete old Azure Cache for Redis instance
After migration, monitor application health to confirm everything is working as expected. If issues arise, you can roll back the migration. Once you have verified success, you can delete the source Azure Cache for Redis instance. The Azure Cache for Redis instance is now decoupled from its hostname and can be deleted safely. The hostname will continue to point to the new Azure Managed Redis instance.
Phase 5: Update applications to use the Azure Managed Redis hostname
After you confirm the migrated Azure Managed Redis instance is running as expected, update your applications to use the Azure Managed Redis connection string instead of the old Azure Cache for Redis connection string. This step is required because the old Azure Cache for Redis hostname will be purged automatically. Because traffic is already flowing to the migrated instance, this update should have minimal impact.
It is easy to postpone this step, but doing it promptly keeps your subscription clean, avoids unnecessary cost, and removes ambiguity about which cache instance is active.
The main cleanup task is purging the source Azure Cache for Redis hostname. Before you do, confirm that no applications or services still reference the old connection string, including Key Vault secrets, environment variables, monitoring dashboards, and background jobs. Take a few minutes to search broadly, since any missed reference will fail after the old hostname is purged.
Once all references have been updated, use the ‘unlink’ API to purge the source Azure Cache for Redis hostname. If the Azure Cache for Redis instance has associated resources such as private endpoints, or diagnostic settings, review whether they should be removed or reconfigured for the new AMR instance. Finally, update any internal documentation, runbooks, and architecture diagrams that still reference the old cache. At that point, the migration is complete.
Getting Started
Both the migration planning agent skill and the portal migration workflow are available today. Here is how to get started:
- The migration agent skill is available here and includes setup instructions.
- To provision your Azure Managed Redis target, find instructions here.
- To start migration, go to your source Azure Cache for Redis cache in the Azure portal and select "Migrate to Azure Managed Redis" from the command bar. More details about the migration tooling are available here.
We recommend starting every migration with a session with the planning agent, even when the migration seems straightforward. It consistently surfaces configuration details and compatibility issues that are easy to miss and can cause problems later. A few minutes of planning up front is well worth the time.
Reach us at AzureManagedRedis@microsoft.com or through your account team with questions, suggestions, or stories from your migration journey.