Unable to provision Azure Managed Redis (Microsoft.Cache/redisEnterprise) in West US 3 due to AllocationFailed / insufficient capacity.

Dustin 0 Reputation points
2026-07-17T19:30:35.7933333+00:00

Azure portal interface prompts us to prepare to migrate our Redis Enterprise cluster to Azure Managed Redis. But this fails due to capacity. Can we get this bumped so we can start working on this?

(AllocationFailed) Request failed due to insufficient capacity.

Retry using a different Azure Managed Redis size, region or contact Azure support for assistance.

Code: AllocationFailed

az redisenterprise create \

--name myRedis \

--resource-group myRG \

--location westus3 \

--sku Balanced_B1 \

--high-availability Enabled \

--public-network-access Disabled

What I've already checked

  • The request validates fully — every parameter parses and the command reaches the allocation step before failing, so this isn't a configuration error.
  • It's not SKU-size-specific: Balanced_B1 and Balanced_B3 both fail with the same error. A minimal Balanced_B0 with HA disabled also fails, which suggests region-wide AMR capacity exhaustion rather than a tight pool for one node size.
  • Per Microsoft's Products available by region list, Azure Managed Redis (Balanced) shows as generally available in West US 3 — so this appears to be a real-time allocatable-capacity gap, not a catalog/availability gap.
  • Failed attempts leave the resource in a terminal Failed state; I've been deleting those and any orphaned private-endpoint/DNS artifacts between retries.
Azure Cache for Redis
Azure Cache for Redis

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

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ganesh Chelluri 90 Reputation points Microsoft External Staff Moderator
    2026-07-17T23:19:58.23+00:00

    Hi @Dustin ,

    Christos's read is correct - AllocationFailed on Microsoft.Cache/redisEnterprise across Balanced_B0/B1/B3 in West US 3 means the region's Azure Managed Redis (Redis Enterprise) capacity pool is temporarily exhausted. "Available by region" only means the SKU is offered, not that inventory is allocatable right now. There is no self-service switch, quota bump, or ARM/CLI flag that can force allocation on a capacity-constrained cluster type.

    What actually unblocks this

    Only the AMR (Redis Enterprise) capacity team can add regional capacity or advise a retry window. Route it through Azure Support:

    Portal -> "?" (Help) -> Help + support -> Create a support request

    • Issue type: Technical
    • Service: Azure Cache for Redis -> Azure Managed Redis (Redis Enterprise)
    • Problem type: Provisioning / Deployment failure
    • Problem subtype: Insufficient capacity / AllocationFailed

    Include (privately in the case, not this thread):

    • Subscription ID, tenant ID, resource group, target region (West US 3)
    • SKUs attempted (Balanced_B0 no-HA, Balanced_B1, Balanced_B3) with UTC timestamps
    • x-ms-request-id / correlationId from each failed deployment
    • Full error body
    • Migration deadline from the "Prepare to migrate" portal prompt
    • Whether an alternate region is acceptable for the migration architecture

    Ask the support engineer explicitly for a "regional capacity review for Microsoft.Cache/redisEnterprise Balanced family in West US 3" and an ETA. That is the phrase that gets routed to the AMR capacity PG, not just L1.

    While you wait

    • Keep the source Redis Enterprise cluster running - do not decommission it.
    • Stop retrying on a fixed cadence; each failed create leaves a Failed resource + orphaned private-endpoint/DNS records to clean up. Retry only after Support confirms capacity is added.
    • If your migration architecture can tolerate it, test-provision the same SKU in an adjacent region (for example West US 2 or West Central US) to confirm the failure is region-specific (it will succeed) and to have a fallback landing zone ready.
    • Do NOT downgrade to classic Azure Cache for Redis as a workaround - that path is being retired and is not a valid target for the AMR migration prompt you're seeing.

    Direct answer to your question
    "Can we get this bumped?" - not from the portal, and not via a quota increase (this isn't a quota; it's physical capacity in the AMR pool). It requires the AMR backend team to add regional capacity, which is done only through a support case as above.

    Was this answer helpful?

    1 person found this answer helpful.
  2. Dustin 0 Reputation points
    2026-07-20T22:03:47.3033333+00:00

    I'd put in a support request if I wasn't required to pay for it. It's odd that I'd have to buy a support plan for something I'm being told I have to do due to a retired component. If you're going to push people to migrate, shouldn't you provide the capacity needed? A 1 GB Azure Managed Redis isn't an unusually large capacity request. Feel free to close, I'm just not paying for this kind of support, it's not logical.

    Was this answer helpful?

    0 comments
  3. Christos Panagiotidis 3,301 Reputation points
    2026-07-17T19:33:16.5666667+00:00

    Your tests are useful: the same AllocationFailed result for B0 without HA, B1, and B3 indicates a West US 3 allocation shortage, not an invalid command or an HA/Private Link setting. A region being listed as available only means the SKU is offered there; it does not guarantee that capacity is currently allocatable.

    There is no portal switch that can force or reserve capacity for this deployment. Open an Azure support request for Azure Managed Redis and ask for a regional capacity review. Include the subscription and tenant IDs, resource group, West US 3, SKU attempts, UTC timestamps, deployment correlation IDs, the error, and your required migration date. That gives Support the information needed to check the service’s regional capacity and advise whether capacity can be added or when to retry.

    Until then, retain the source cluster and test another supported region only if the migration architecture can accommodate it.

    Was this answer helpful?

    0 comments

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.