Skip to content
Azure Cache for Redis retirement

Azure Cache for Redis is retiring. Migrate on your schedule, not Microsoft's.

Every Azure Cache for Redis tier is being retired in favor of Azure Managed Redis. We assess your caches, pick the right tier, update your applications, and cut over with minimal downtime, before the deadline forces it.

Get a migration assessment See the retirement timeline

// key dates

The clock is already running.

Existing caches keep running until retirement, but you can no longer create new ones, which makes scaling out or rebuilding environments harder every month you wait.Sources: Microsoft's retirement FAQ and retirement announcement.

Enterprise & Enterprise Flash

Basic, Standard & Premium

Creation blockedRetirementRetired

  1. New caches blocked

    No new Enterprise caches for anyone; no new Basic/Standard/Premium caches for new customers.

  2. Blocked for existing customers

    Existing customers can no longer create Basic, Standard, or Premium caches.

  3. Enterprise tiers retire

    Enterprise & Enterprise Flash retire. Remaining instances are disabled starting April 1, 2027.

  4. Basic, Standard & Premium retire

    Instances are disabled starting October 1, 2028.

// why now

Why not just wait?

Fewer options over time

Once creation is blocked, cloning or scaling a legacy cache for a new environment gets harder every month.

Deadlines create rushed cutovers

Migrations done in the final months compete for the same engineers and the same change windows.

It's not a lift-and-shift

Endpoints, ports, clustering behavior, and tier sizing differ in Azure Managed Redis, so apps and configuration need attention.

There's upside

Azure Managed Redis runs on Redis Enterprise, is zone-redundant by default, and offers tiers you can size for memory, compute, or cost.

// what's included

Assessment, migration, hand-over.

1. Migration assessment

  • Inventory of every Azure Cache for Redis instance across your subscriptions
  • Usage, size, and feature review (persistence, geo-replication, modules, clustering)
  • Application dependency map: which services use which cache, and how
  • Target tier and sizing recommendation, with a cost comparison
  • Written migration plan and risk list

2. Migration

  • Infrastructure-as-code for the new Azure Managed Redis instances
  • App and configuration updates (connection strings, ports, TLS, clustering)
  • The right approach per workload: fresh cache, dual-write, or export/import
  • Non-production first, then a planned production cutover with rollback
  • Monitoring and alerts on the new caches

3. Hand-over

  • Documentation and runbooks
  • Decommissioning of the old caches
  • 30 days of post-migration support

// how it works

Four steps, no surprises.

  1. 01

    Assessment

    We inventory and analyze your caches and deliver a written plan. Typically 1–2 weeks.

  2. 02

    Plan approval

    You get a fixed scope and quote for the migration.

  3. 03

    Migrate

    Non-production first, then production in a planned cutover window. Typically 2–6 weeks, depending on the number of caches.

  4. 04

    Validate & decommission

    Confirm performance, then retire the old caches.

// pricing

Know the cost before you commit

Assessment
Quoted after a short scoping call
Migration
Quoted from the assessment

Every environment is different, so we quote once we've seen yours. You get a fixed scope and price before any work starts.

// why enligh10

Done carefully, the first time

  • Five years of hands-on Redis experience.

    We know where Redis migrations tend to go wrong, and plan around it.

  • Azure specialists.

    We focus on the Microsoft cloud, so we know its edge cases, pricing, and roadmap.

  • Minimal downtime by design.

    Every cutover has a rehearsal and a rollback plan.

  • You keep everything.

    Infrastructure-as-code and runbooks live in your repositories.

// faq

Common questions

Which tiers are affected?
All of them: Basic, Standard, Premium, Enterprise, and Enterprise Flash. Enterprise tiers have the earliest deadline.
Will my existing caches stop working right away?
No. Existing caches keep running and receive maintenance until their tier's retirement date. What changes first is your ability to create new caches.
Do I need to change application code?
Usually only configuration, such as connection strings, ports, and TLS settings, but it depends on your client libraries and whether you use clustering. The assessment tells you exactly what changes.
Can we migrate with zero downtime?
Often close to it. The right approach depends on whether your cache holds data you can rebuild or data you must preserve. We'll recommend the safest option for each workload.
Is Azure Managed Redis more expensive?
It depends on your tier and usage. Some workloads cost less on the right Azure Managed Redis tier. The assessment includes a side-by-side cost comparison.
What if we're on the Enterprise tier?
Start now. Enterprise and Enterprise Flash retire March 31, 2027, and any remaining instances are disabled starting April 1, 2027.

Know exactly what your Redis migration will take.

Tell us a little about your caches. We'll start with an inventory, and you'll leave with a clear picture of the work, the risk, and the timeline.

  • A reply from an engineer, not a sales team
  • A short call to scope the assessment
  • No obligation to migrate with us

Email us a few details about your caches and we'll set up a short scoping call. Rough answers are fine.

Request a migration assessment

Or write to info@enligh10.com. We reply within one business day.