Azure Cache for Redis creation block exception/extension

Question

Azure Cache for Redis creation block exception/extension

Alex 535

Hello,

From the retirement notice of Azure Cache for Redis (ACR), it is mentioned that the creation of new ACR will be blocked from 1Oct'26 for existing customers. Is there an exception process available to extend this block to a later date?

Cheers,

Alex.

Peram Venkateswara Reddy 5 Reputation points Microsoft External Staff Moderator

2026-07-20T09:44:03.3966667+00:00
Hi Alex,

there's no documented self-service "exception" or extension process to move the creation-block date past 1 October 2026 for existing customers. That date is a fixed, phased retirement milestone for the Basic/Standard/Premium tiers — not a per-subscription setting you can request to defer through the portal or an API.

A few points that usually address the underlying concern behind this question:

The block only stops creating new caches — your existing caches are unaffected.All existing Basic/Standard/Premium instances keep running and continue to receive regular maintenance until the service fully retires on 30 September 2028. So the Oct 2026 block doesn't remove anything you already have.

If your goal is to keep standing up new Redis instances after Oct 2026, the intended path is Azure Managed Redis (AMR) — not an ACR extension. AMR (Microsoft.Cache/redisEnterprise) is the successor service: zone-redundant by default, Microsoft Entra ID-based authentication, and generally more performant and cost-effective. It's where new provisioning is expected to happen going forward.

If you genuinely can't migrate to AMR — for example a missing feature, an unsupported region, or a SKU/size gap — the retirement FAQ explicitly directs you to reach out to Microsoft Support. That's also the correct channel for any business-exception discussion around the timeline; it's handled by Microsoft on a case basis via your account team / CSAM or a support case, not a self-service toggle. Raise it well before the Oct 2026 cutoff and include the affected subscription IDs and the specific dependency.

Recommended action: plan your migration to AMR now rather than seeking to prolong ACR creation — the tooling and guidance are already published.

References:

Frequently asked questions (FAQ) on the retirement of Azure Cache for Redis — Frequently asked questions (FAQ) on the retirement of Azure Cache for Redis - Azure Cache for Redis …

What's New in Azure Cache for Redis (retirement dates, Oct 2025) — What's New in Azure Cache for Redis - Azure Cache for Redis | Microsoft Learn

Migrate from Basic, Standard, and Premium tiers to Azure Managed Redis — Migrate from Basic, Standard, and Premium tiers to Azure Managed Redis - Azure Managed Redis | Micro…

What is Azure Managed Redis? — What is Azure Managed Redis? - Azure Managed Redis | Microsoft Learn

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
Peram Venkateswara Reddy 5 Reputation points Microsoft External Staff Moderator

2026-07-21T09:31:36.4666667+00:00

Hi @Alex Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?
Peram Venkateswara Reddy 5 Reputation points Microsoft External Staff Moderator

2026-07-22T16:38:15.1533333+00:00

Hi @Alex , Please let us know if you had the chance to review our initial troubleshooting steps. Hope the issue has been resolved.

Answer accepted by question author

0 additional answers

Your answer

Peram Venkateswara Reddy 5 Reputation points Microsoft External Staff Moderator

2026-07-21T09:31:36.4666667+00:00

Hi @Alex Just following up to see if your issue has been resolved or if you had a chance to review my earlier comment?
Peram Venkateswara Reddy 5 Reputation points Microsoft External Staff Moderator

2026-07-22T16:38:15.1533333+00:00

Hi @Alex , Please let us know if you had the chance to review our initial troubleshooting steps. Hope the issue has been resolved.

Answer 1

Hello Alex,

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

I understand that your Azure Cache for Redis creation block exception/extension.

This is a fixed retirement milestone for Azure Cache for Redis Basic, Standard, and Premium tiers. For Azure Public Cloud, creation of new Basic/Standard/Premium caches is blocked for existing customers from 1 October 2026, while existing instances continue running until 30 September 2028 and are disabled starting 1 October 2028. - https://techcommunity.microsoft.com/blog/azure-managed-redis/azure-cache-for-redis-retirement-what-to-know-and-how-to-prepare/4458721, https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/retirement-faq

Also, there is no documented self-service exception, Azure portal option, Azure CLI command, REST API, quota request, or per-subscription setting to defer that creation-block date. The supported path for creating new Redis workloads after the block date is Azure Managed Redis, not an Azure Cache for Redis extension. Recommendation is to upgrad current Azure Cache for Redis instances to Azure Managed Redis now rather than waiting for the retirement deadline. - https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/retirement-faq, - https://docs.azure.cn/en-us/redis/migrate/migrate-basic-standard-premium-options

The resolution is to:

Stop planning any new workload, CI/CD pipeline, disaster recovery process, or environment deployment that depends on creating new Azure Cache for Redis Basic/Standard/Premium instances after 1 October 2026.
Inventory all existing Azure Cache for Redis instances, including tier, SKU, region, networking, private endpoint/VNet dependency, geo-replication, persistence, firewall rules, client libraries, and application owners.
Create equivalent or right-sized Azure Managed Redis targets and validate application connectivity.
Use self-service migration for most production workloads because it gives full control over data movement, test validation, and cutover timing.
Use migration tooling only after checking its limitations, because the Basic/Standard/Premium tooling is preview, requires a pre-created Azure Managed Redis target, and is intended for endpoint migration rather than full data migration.
If migration is blocked by a missing Azure Managed Redis feature, unsupported region, SKU/size gap, networking limitation, or compliance dependency, open an Azure Support request with the exact blocker details. Microsoft documentation allows support requests through the Azure portal, and the user must have the required subscription-level permissions such as Owner, Contributor, Support Request Contributor, or Microsoft.Support/*. - https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

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

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.

Alex 535 Reputation points

2026-07-24T06:26:45.5066667+00:00

This is unfortunate that creation block can't be extended on-demand when the actual retirement is 2028, so Cx can take some time to assess and migrate.

Thanks for the details,

Alex.