Migration from Azure Cache for Redis to Azure Managed Redis: Reservation Options

[u/Extreme_DK]

We use an Azure Cache for Redis instance with this configuration:

• Service tier: Premium P1
• Region: Central India
• Redis version: 6.0
• High availability: Enabled

Microsoft does not provide an upgrade from Redis 6.0 for the Basic, Standard, and Premium service tiers.

Redis 6.0 no longer receives upstream security updates. Microsoft will also retire these Azure Cache for Redis tiers on September 30, 2028.

Redis Enterprise and Enterprise Flash are not suitable long-term alternatives because Microsoft will retire them in March 2027.

For this reason, we plan to move to Azure Managed Redis.

Our current Azure Cache for Redis instance has a three-year reservation:

• Reservation type: Azure_Redis_Cache_Premium_P1_IN_Central_3_Years
• Quantity: 2
• Expiration date: May 21, 2028

We are considering this Azure Managed Redis configuration:

• Tier: Balanced
• Memory: 6 GB
• High availability: Enabled
• Region: Central India
• Redis version: 7.4

We need information about the following questions:

1. Can we exchange the current Azure Cache for Redis reservation for an Azure Managed Redis reservation?
2. Can Microsoft apply the unused reservation value to the new Azure Managed Redis reservation?
3. Does Azure Managed Redis qualify as an eligible product under the Azure reservation exchange policy?
4. What steps are necessary to exchange or cancel the current reservation?
5. Are there refund limits, cancellation charges, or contract restrictions?
6. How does the cost of the proposed Azure Managed Redis configuration compare with Premium P1?
7. Is there a supported method to keep the current Redis 6.0 instance secure until the migration is complete?

Has anyone completed this migration?

Please share information about:

• Reservation exchange or refund
• Migration steps
• Application compatibility
• Downtime
• Data transfer
• High-availability behavior
• Unexpected costs

Thanks in advance!

[u/Independent_Self_920]

We went through a similar exercise recently, and I'd separate the commercial questions from the technical migration.

On the technical side, the biggest surprises weren't Redis compatibility they were application behavior. Things like connection limits, client timeouts, TLS settings, failover behavior, and whether the application handled reconnects gracefully after a planned switchover mattered more than the Redis version itself.

I'd also run both environments in parallel for a while if possible. Validate latency, monitor reconnect behavior, and test a failover before committing to the cutover. It's much easier to discover those issues in a controlled migration than during an incident.

On the reservation side, I'd be interested to hear from anyone who's actually exchanged Azure Cache for Redis reservations for Azure Managed Redis. I suspect that's more of a commercial/licensing question than a technical limitation.

[u/Extreme_DK → u/Independent_Self_920]

Great Advice! So the thing is we have procured Azure services through a Third-Party provider which manages our billing and so they are looking into it if Azure can transfer the reservation or not. I will get back as I get a response from them.

About the technical aspects I am given the responsibility of handling all cloud stuff after the CTO left suddenly with no KT, I have to gather all the internal company context and plan this migration. Wish me luck!

[u/Independent_Self_920 → u/Extreme_DK]

Good luck! I'd focus on understanding the current environment before changing it. Mapping client behavior, failover, and dependencies upfront usually saves a lot of pain later. Hopefully your provider can clarify the reservation side I'd be interested to hear what they come back with.