An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.
Hi @Nina St. John ,
That "OperationFailed" is the outer wrapper the real underlying error is: code: AllocationFailed message: Request failed due to insufficient capacity. Retry using a different Azure Managed Redis size, region or contact Azure support for assistance.
This is a regional capacity/allocation issue for the specific Azure Managed Redis SKU + size you're requesting, not something wrong with your subscription or template.
Since you've already hit it in both West US 2 and West US 3, please try the following in this order:
Change the SKU/size (biggest lever) In the create blade, pick a different Performance tier and/or a different cache size (e.g., switch between Memory Optimized / Balanced / Compute Optimized, or pick the next size up or down). Capacity is tracked per region per SKU per size, so a different size in the same region very often succeeds when the current one fails.
Try another nearby region West US, Central US, South Central US, or East US 2 are good alternates for your workload. Keep the same SKU/size you actually need and just change region. 3. If both (1) and (2) fail with the same AllocationFailed Open a free Azure support request under: Service and subscription limits (quotas) → Azure Managed Redis, mention the SKU, size, and regions attempted, and the Redis capacity team can either reserve capacity or advise the next region with headroom. There is nothing to fix on your side the resource template is fine; it's purely regional SKU availability.