Azure Managed Redis - All SKUs unavailable in France Central during deployment

Hi Koteru Shyam Kishore Reddy & thx for join me at Q&A platform,

every Azure Managed Redis SKU fails validation in France Central, including Balanced_B0, is an important clue. This looks less like a problem with one particular cache size and more like a regional availability, subscription eligibility, or resource provider restriction.

I'd first distinguish between a SKU being supported in a region and that SKU being available for new deployments right now. Those aren't necessarily the same thing. Azure Managed Redis can encounter temporary regional capacity restrictions even when the selected SKU is normally supported.

Because you're getting the same validation error through both the Azure portal and Bicep, I'd focus on the response from Microsoft.Cache/redisEnterprise rather than troubleshooting the portal itself. Check the deployment's detailed error response, including the error code, inner error details, and correlation ID. In particular, we need to distinguish an unsupported SKU or subscription restriction from an actual InsufficientCapacity response.

I wouldn't recommend repeatedly trying every SKU in France Central. If all of them are rejected during validation, changing cache sizes probably won't help until the underlying restriction is identified.

I'd also verify that Microsoft.Cache is registered for the subscription and check whether any Azure Policy restrictions apply. Those are quick checks, although the SKU-specific error makes a regional service restriction more likely than a simple provider registration issue.

Microsoft has acknowledged that Azure Managed Redis can experience temporary regional capacity restrictions, but I couldn't confirm a current France Central-wide outage or an ETA for restored capacity. <Cite ref="turn288282view0"/>

As a diagnostic, try the same Balanced_B0 configuration in another supported region, using the same subscription. If it passes validation there but fails consistently in France Central, that would strengthen the case for a region-specific restriction. It wouldn't establish the exact cause, tho.

At this point, I'd open an Azure support case and ask the Azure Managed Redis engineering team to confirm whether France Central is experiencing a temporary deployment restriction, whether new deployments are blocked for all SKUs or only for certain subscriptions, and when capacity is expected to become available. Include the failed deployment correlation IDs and UTC timestamps.

One question: does the deployment return an explicit InsufficientCapacity error code, or only the message that the SKU is not currently available in France Central? That distinction matters because the latter could also indicate a regional SKU availability or subscription eligibility restriction rather than exhausted physical capacity.

rgds,

Alex

p.s. if my answer is help - pls mark it as an answer