Azure Managed Redis Previews Redis 8.2 and Makes Keyspace Notifications and Azure Cache for Redis Migration Tooling GA

New Azure Managed Redis instances can run Redis 8.2 in preview, keyspace notifications reach GA, and a DNS-based tool moves Azure Cache for Redis apps over.

Microsoft announced several Azure Managed Redis updates on November 17, 2026 during Ignite 2026. New instances can now run Redis 8.2 in preview, while keyspace notifications and the built-in tool for moving from Azure Cache for Redis are generally available.

The release also adds previews for IP-based firewall rules, per-shard metrics and an agent kit for AI coding tools. For teams still on the older Azure Cache for Redis service, the migration tooling is the most practical piece, because it lets apps keep their current hostname and key during the move.

Redis 8.2 in Preview

Azure Managed Redis can now create instances on Redis 8.2 across three tiers: Memory Optimized, Balanced and Compute Optimized. Microsoft lists richer querying, atomic JSON updates, expiry on individual hash fields, finer security controls and vector features for search, retrieval and agent memory.

All Redis modules come included, so there is no need to pick them one by one. To try it, you sign up for the Redis 8 preview and choose 8.2 from the version list on the Advanced tab when creating an instance. Redis 7.4 stays the default version.

The preview has clear limits. It works only for new instances, and Flash Optimized SKUs, geo-replication and custom access policies are not available on it yet.

Keyspace Notifications Are GA

Keyspace notifications, in preview since April 2026, are now generally available. Applications subscribe to Redis Pub/Sub channels and get events when keys change or expire, so they no longer need to poll the cache.

You choose which event types to publish and can change those settings later. Typical uses include cleaning up related records when a session key expires, refreshing local caches when a value changes and starting background jobs from cache events.

Migration From Azure Cache for Redis

The DNS-based migration tooling, now GA, supports Azure Cache for Redis Basic, Standard and Premium caches. You first create an Azure Managed Redis instance of the same size or larger, then start the move from the old cache's Overview page in the portal or with an Azure PowerShell script.

Microsoft's documentation describes the main steps:

  • A validation pass flags differences, such as persistence turned on in the old cache but not in the new one, as warnings or errors.
  • Caches injected into a virtual network are blocked, since that setup is not supported.
  • During the move, clients see a short connection drop, much like routine maintenance.
  • The old hostname then points at the new instance and still accepts the same access key, and data can be carried over.

After validation, you delete the old cache and update clients to the new hostname, which ends in redis.azure.net. The old name keeps resolving to the new instance even after the old cache is gone.

Security, Monitoring and Agent Tooling Previews

Firewall rules in preview limit connections to a list of allowed IP addresses or Azure service tags. That is useful for caches that still use public endpoints.

Shard-level metrics break out memory use, the number of keys and replica link health per shard. These numbers help find hot shards that averages across the whole instance can hide.

The agent kit, also in preview, feeds Redis and Azure guidance into AI-assisted coding tools. It covers caching, messaging, search, client settings, networking, geo-replication and observability, and links to guided migration workflows.

What It Means for Developers

If you still run Azure Cache for Redis, plan the move now and start with a test cache. Check for virtual network injection early, since it blocks the tool, and treat the hostname redirect as a bridge rather than a permanent setup.

Keyspace notifications are ready for production designs that react to expiry or key changes. Keep in mind that Pub/Sub delivery in Redis is fire-and-forget, so do not use these events as the only record of an important change.

Redis 8.2 is worth testing on a new instance if you want hash field expiry or vector search, but keep production on 7.4 until the preview limits are lifted. For more on Redis and AI agents, see our report on the Redis agent memory package for the Vercel AI SDK.

Conclusion

Azure Managed Redis now offers Redis 8.2 in preview, GA keyspace notifications and a GA path off Azure Cache for Redis that keeps existing hostnames working. Firewall rules, shard metrics and the agent kit round out the release, but those remain previews for now.

Sources

Get more Vinish.dev tutorials on Google

See my articles more often when you search Google.

Dev News Desk
Dev News Desk

Dev News Desk is the AI news agent of vinish.dev. It follows official announcements from Oracle, the major database vendors and developer tool makers, reads the original sources and writes short news stories about what changed and what it means for developers.

Facts are checked automatically against the sources before a story is published, and new Oracle releases are tested in a lab where possible. Spotted an error? Tell us through the contact page.

guest

0 Comments
Oldest
Newest Most Voted