Learn the answers to common questions, patterns, and best practices for Azure Cache for Redis.
Which Azure Cache for Redis services were deprecated?
Caches with a dependency on Cloud Services (classic)
What should I do with any instances of Azure Cache for Redis that depend on Cloud Services (classic)?
You should migrate all caches with a dependency on Cloud Services (classic). In August 2021, we announced Cloud Services (classic) will be retired on August 31, 2024. Any instances of Azure Cache for Redis that are dependent on Cloud Services (classic) need to be retired by the same date.
You should migrate caches with a dependency on Cloud Services (classic) before August 31, 2024.
How many caches are affected?
We’ve made an effort to migrate as many caches as transparently possible. Because of this, few caches and customers are affected.
How do I know if a cache is affected?
Please check Azure Advisor Recommendations. If your cache is affected, you see a recommendation in your subscription.
How do I migrate Cloud Services (classic) caches to Azure Virtual Machine Scale Sets?
We have migrated most caches from being built on Cloud Services (class) to being built on Azure Virtual Machine Scale Sets. Migrating to Azure Virtual Machine Scale Sets removes the dependency. There are two ways to initiate this process for caches in a VNet:
Migrate to a new cache using Private Links (recommended).
Create a new cache that uses Private Link for network isolation rather than VNet injection and migrate your data to this cache. This option gives you the best and most secure network isolation experience, while also ensuring that all new caches are created using updated infrastructure.
Migrate to a new cache in a new Azure Resource Manager VNet subnet.
This option will fix the underlying dependency on Cloud Services while maintaining a similar VNet experience. We have migrated most caches from being built on Cloud Services (class) to being built on Azure Virtual Machine Scale Sets. To migrate, delete the existing cache and create a new cache in a new Azure Resource Manager VNet subnet. For recommended options for migrating the data in the cache, see Migrate to Azure Cache for Redis.
My cache isn't using VNet injection, but I received notice that I need to migrate. What should I do?
Check to see if your cache is using geo-replication. If so, you’ll need to migrate your data from your current geo-replicated pair to a fresh geo-replicated pair.
- Create a new geo-replicated pair of Premium caches that match the same configuration as your current pair of caches.
- Unlink your original pair of geo-replicated caches and export an RDB file from the primary cache.
- Import the RDB file into the primary cache in your new geo-replicated pair.
The new pair of geo-replicated caches won't have the same dependency on Cloud Services.
What happens if caches aren't upgraded/migrated by August 31, 2024?
These caches will be shut down, and you'll lose any data in your caches.
What is the timeline for support?
Retirement will occur in three phases so that you have the maximum amount of time to migrate:
Active Stage (now to April 30, 2023)
Caches have full support, with no change in status from today. This period is given to allow customers time to transition off Cloud Service (classic) with minimal interruption.
Maintenance Stage (May 1, 2023 to December 31, 2023)
Caches will receive critical security, stability, and bug fixes, but no new features.
Inactive Stage (January 1, 2024 to August 31, 2024)
Caches will only receive critical security fixes. All customers with support issues will be requested to migrate to a VMSS-based cache before receiving support. Customers must move off their caches by August 31, 2024.
Where can I get more information if I have more questions about this retirement?
What if my Azure Cache for Redis question isn't answered here?
If your question isn't listed here, let us know and we'll help you find an answer.
To reach a wider audience, you can post a question on the Microsoft Q&A question page for Azure Cache and engage with the Azure Cache team and other members of the community.
If you want to make a feature request, you can submit your requests and ideas to Azure Cache for Redis User Voice.
You can also send your question to us at firstname.lastname@example.org.