Azure Managed Redis: Creation fails due to regional capacity shortage in East US 2 — Insufficient Capacity

Priyesh-2156 0 Reputation points
2026-09-24T07:08:04.6733333+00:00

Problem description

I am attempting to create a new Azure Managed Redis cluster in the East US 2 region, but the deployment fails with an 'InsufficientCapacity' error for multiple SKU sizes (Balanced_B3, Balanced_B5, and ComputeOptimized_X3). The failed resources were deleted after each attempt. I want to understand the cause of this issue and possible solutions.

Environment

Service: Azure Managed Redis; Resource Type: Microsoft.Cache/redisEnterprise; Region: East US 2

What I've already tried

I have tried creating the cluster with different SKUs and sizes (Balanced_B3, Balanced_B5, ComputeOptimized_X3). Each attempt resulted in the same 'InsufficientCapacity' error. The failed resources were deleted after each attempt. I have also checked for any cleanup issues or naming conflicts, but the problem persists.

Current status

The creation attempts continue to fail with 'InsufficientCapacity' across multiple sizes in East US 2. I am seeking confirmation on regional capacity availability and guidance on next steps to resolve this issue.

Azure Cache for Redis
Azure Cache for Redis

An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. SIVASANKAR YEDDULA 250 Reputation points Microsoft External Staff Moderator
    2026-09-24T09:01:23.86+00:00

    Hi Priyesh,

    Thank you for sharing the details.

    Based on the reported behavior, the deployment is failing during Azure Managed Redis resource allocation with InsufficientCapacity.

    Since you have already tested multiple configurations, including Balanced_B3, Balanced_B5, and ComputeOptimized_X3, with the same result in East US 2, no additional Redis-side configuration changes are recommended at this stage.

    Recommended mitigation

    1. Avoid repeatedly retrying the same SKUs in East US 2, as this is unlikely to provide a reliable resolution while the capacity condition persists.
    2. If your architecture permits, deploy Azure Managed Redis in another supported Azure region.
    3. If East US 2 is mandatory, Azure-side capacity validation is required. The Azure Managed Redis service team should validate whether the requested configurations can currently be allocated in East US 2.
    4. If another suitable Azure Managed Redis SKU becomes available in East US 2 and meets your workload requirements, it can be considered as a temporary alternative.

    Conclusion

    This behavior should not be treated as an application, Redis configuration, naming, or cleanup issue based on the information currently available.

    The recommended path is:

    Alternative supported SKU in East US 2 → alternative region where possible → Azure-side capacity validation when East US 2 is mandatory.

    If your workload must remain in East US 2, service-side capacity validation is the appropriate next step rather than further customer-side configuration changes.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.