Azure Managed Redis - Creation Failed with SKU not supported in your subscription / region

Question

Azure Managed Redis - Creation Failed with SKU not supported in your subscription / region

Cedric Ahlers 115

Hi all,

We're trying to deploy Azure Managed Redis in Germany West Central, but resource creation fails with this error:

Creation of Azure Managed Redis with the SKU Balanced_B3 is not supported for your subscription in Germany West Central. Please choose a different SKU or region. If you need access to this SKU, please contact support.

We are trying to deploy two nodes setups of Balanced_B0 and Balanced_B3.

What we checked: The Azure Products available by region page doesn't list "Azure Managed Redis" by name. We assumed it falls under "Redis Cache Balanced", which shows as GA in Germany West Central.

Why not Azure Cache for Redis: Azure Cache for Redis is being retired (31.03.2027 and 30.09.2028), so we don't want to start new development on it. We're following Microsoft's recommendation to use Azure Managed Redis instead.

Questions:

Does anyone how to read the Products available by region page for Azure Managed Redis? Is Azure Managed Redis (Balanced tier) generally available in Germany West Central, or is it restricted or capacity-limited there?
If it's restricted per subscription, what's the right way to request access for these SKUs? Is it a quota or region-enablement request through Azure Support? I didn't found a related subscription quota for Redis.

Thanks for any pointers.

0 comments

1 answer

Your answer

Answer 1

Hi @Cedric Ahlers ,
This error indicates that while the SKU is generally available in Germany West Central at a regional level, your specific subscription offer type (such as Pay-as-you-go, Dev/Test, or Visual Studio) or datacenter capacity policies have restricted provisioning for that SKU in that region.

1. How to verify SKU availability for Azure Managed Redis

The Products available by region page reflects general platform availability across the datacenter, but it does not account for subscription-level restrictions or local capacity allocations. Under the hood, Azure Managed Redis uses the Microsoft.Cache/redisEnterprise resource provider.

To see the exact SKUs currently available to your subscription in Germany West Central, run the following Azure CLI command:


az redisenterprise list-skus --location germanywestcentral

If Balanced_B0 and Balanced_B3 do not appear in the output, the provider is gating those SKUs for your subscription tier in that region.
You can also ensure the resource provider is registered on the subscription:
```
  az provider register --namespace Microsoft.Cache
```

2. How to request access through Azure Support

Because Azure Managed Redis does not have a self-service slider in the Subscriptions > Quotas blade, access must be requested through a support ticket:

In the Azure Portal, navigate to Help + support > Create a support request.
Set the following basic parameters:
- Issue type: Select Technical (or Service and subscription limits (quotas) if available for Redis Enterprise).
- Service: Azure Cache for Redis (or Azure Managed Redis).
- Problem type: Provisioning, scaling, or deletion (or Quota or limit increase).
- Problem subtype: Unable to create cache / Allocation failure.
In the request details, include the following information:
- Subscription ID: Your target subscription ID.
- Region: Germany West Central (germanywestcentral).
- Target SKUs: Balanced_B0 and Balanced_B3.
- Cluster architecture: 2-node High Availability setup.
- Business justification: Note your migration/new project requirements and the retirement timeline of Azure Cache for Redis.

Recommended Alternatives While Waiting

Alternative Regions: If your data residency policies allow, test deployment in West Europe (westeurope) or North Europe (northeurope), where Managed Redis capacity is generally less constrained.
Alternative SKUs: Test provisioning an entry-level compute or memory SKU (e.g., MemoryOptimized_M10) to confirm if the gate applies strictly to the Balanced tier or across the entire service for your subscription.