Microsoft announced the public preview of Redis 8 on Azure Managed Redis. It was part of a batch of Ignite 2026 announcements. Microsoft listed seven Azure Managed Redis updates, led by the Redis 8 and agent kit previews. The Azure Updates entry carries the shorthand "Redis 8" in its title. Microsoft Learn is more precise: the version you create is Redis 8.2.
What Microsoft actually documented
Microsoft Learn's overview says Azure Managed Redis supports two versions. Redis 7.4 is the default and Redis 8.2 is in preview. The documented behavior is:
- Where to pick it: when you create an instance in the Azure portal, you select the version from the Redis version drop-down on the Advanced tab.
- Sign-up: Microsoft Learn tells you to sign up for the Redis 8 preview to try 8.2. The documentation I could review doesn't spell out the sign-up process, eligibility rules or regional availability, so check those before planning a rollout.
- Eligible tiers: Memory Optimized, Balanced and Compute Optimized, with all Redis modules included.
- Not supported: Flash Optimized SKUs, geo-replication and custom data access policies.
- No in-place upgrade: upgrading existing instances to Redis 8.2 isn't supported. Microsoft's announcement post says the same: 8.2 is for new instances only, and existing Redis 7.4 caches keep running as before.
What "preview" means here
Azure Managed Redis itself is generally available. It reached GA in May 2025, and only Redis 8.2 carries the preview label. The Azure Updates page defines "In preview" as available to all Azure customers for non-production use and testing. I wouldn't read that as a production recommendation. I haven't checked the preview terms for service-level commitments, so confirm those before relying on the SLA.
Why you might care
Microsoft's blog pitch is that new instances can use faster commands, more built-in data structures, and new tools for streams, vectors and observability. These are Microsoft's claims. The documentation I reviewed doesn't include benchmarks or a list of Redis 8.2 command changes, so treat the performance gains as unverified until you test them. Microsoft does say the official client libraries (redis-py, node-redis, Jedis, Lettuce, go-redis and NRedisStack) and Redis Insight support Redis 8.
The three eligible tiers differ in memory-to-vCPU ratio:
| Tier | Memory-to-vCPU ratio | Microsoft's positioning |
|---|---|---|
| Memory Optimized | 8:1 | Memory-intensive workloads, lower price point, good for dev/test |
| Balanced | 4:1 | Standard workloads |
| Compute Optimized | 2:1 | Maximum throughput |
Practical guidance for admins and developers
- Treat it as a test bed. Stand up a new Redis 8.2 instance in a non-production subscription or resource group. Replay representative traffic and check client library behavior.
- Check your architecture against the exclusions. If you depend on active geo-replication, Flash Optimized capacity or custom data access policies, Redis 8.2 isn't an option yet. Microsoft's feature table lists active geo-replication as Redis 7.4 only.
- Plan for migration, not upgrade. Because in-place upgrade isn't supported, moving an existing workload means creating a new cache and moving the data. I'd verify the procedure in the current documentation before committing to a plan.
- Don't change production defaults. Redis 7.4 remains the default and the documented stable choice.
Bottom line
The news is a new opt-in preview that, for now, only suits greenfield experiments. Microsoft hasn't published a general availability date, so use the preview to find compatibility problems early. Keep production on Redis 7.4 for the time being.
References
- (In preview) Public Preview: Redis 8 in Azure Managed Redis Azure Updates · 2026-11-17T20:00:32Z
- Build faster applications with Redis 8: Now in preview on Azure Managed Redis techcommunity.microsoft.com
- What’s new in Azure Managed Redis at Microsoft Ignite 2026 techcommunity.microsoft.com