Does anyone know when Azure Managed Redis will support Redis databases?

Hi Björn Hasselberg,

Greetings!!

Currently, Azure Managed Redis only supports a single logical database per instance. This is a known limitation, and Microsoft has not yet announced a timeline for supporting multiple Redis databases

I recommend keeping an eye on the official Azure updates or the What’s New in Azure Managed Redis page for any announcements regarding new features.

Hope this helps. Do let us know if you any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Hello Björn Hasselberg,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to know when Azure Managed Redis will support Redis databases.

As of today, Azure Managed Redis supports only one logical Redis database per instance. See Microsoft’s Azure Managed Redis development FAQ and overview - https://azure.microsoft.com/en-us/products/managed-redis/#FAQ

Yes, Microsoft has not published a timeline for adding multiple logical Redis databases to Azure Managed Redis. The current “What’s new” and product pages list features and show items in preview/GA, but do not announce a date for multi-database support. To track announcements, see the Azure Managed Redis “What’s new” page and the general Azure Updates feed.

If you need multi-database behavior now practical options:

1. Use key namespaces (recommended): Prefix keys per application/tenant (e.g., app1:session:..., app2:cache:...). This is a common and recommended pattern; Redis documentation and experience suggest namespacing keys rather than using multiple logical databases. Namespacing also works with clustering and modules.- https://redis.io/learn/howtos/antipatterns
2. Run separate Redis instances: Create multiple Azure Managed Redis instances (one per logical database) or keep using a non-clustered Azure Cache for Redis tier that supports multiple DBs (if applicable). Separate instances avoid SELECT/DB coupling and are more scalable (take advantage of multiple cores).
3. If you’re migrating from Azure Cache for Redis Enterprise: Microsoft documents a migration path (export/import RDB, dual-write strategies). Review the migration guidance before switching to Managed Redis. - https://xtls-v4.hkg1.meaqua.org/en-us/azure/redis/migrate/migrate-overview

How to get notified or request a timeline from Microsoft: https://redis.io/blog/5-key-takeaways-for-developing-with-redis/

• Subscribe to the Azure Updates feed and filter for Redis / Azure Managed Redis. This will surface any feature announcements as soon as Microsoft publishes them.
• Watch the Azure Managed Redis “What’s new” page (Microsoft Docs).
• If you need an official product roadmap or SLA commitment, open an Azure support request from your subscription — Microsoft support or your Azure account team can provide product planning information or add your scenario to feature request channels.

NOTE:

If you need logical separation today, use key prefixes or separate instances rather than depending on a future multi-db feature. That approach aligns with Redis best practices and with Azure’s current product set. If you must track Microsoft’s roadmap, subscribe to Azure Updates and the Managed Redis “What’s new” page and open an Azure support ticket to express your need (this can influence prioritization).

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.