Azure Managed Redis deployment failed

Possibly the region capacity issue. Error doesn't show reason of failure

Hi X-Yauheni Amelyanovich,

It looks like you're trying to spin up a “Balanced B3” Redis instance in East US via the portal, but that SKU isn’t showing up and the provisioning just returns an opaque OperationFailed. Here’s what’s likely going on and some things you can try:

Balanced SKUs are legacy names and aren’t surfaced in the portal UI drop-downs anymore. • The portal now shows Basic, Standard and Premium tiers. • For a B3-equivalent instance, you’d pick either Standard S3 or Premium P1 (depending on replication needs).

If you really need the old “Balanced” label or larger SKUs, create via CLI or ARM/Bicep instead of the portal: • Example CLI:

az redis create \
  --name myCache \
  --resource-group myRG \
  --location eastus \
  --sku Premium \
  --vm-size P1 \
  --replicas 1

• Or use an ARM/Bicep template to choose any supported SKU that maps to B-series sizes.

Check region and subscription quotas—some VM-sizes aren’t available in every region or may be throttled by your subscription. You can list available SKUs in East US with:

az redis list-skus --location eastus

If you’re provisioning into a VNet and running into “OperationFailed” without much detail, network config can be the culprit. We actually recommend using Private Link instead of VNet injection to reduce complexity and avoid intermittent creation failures.

Let me know:

• Which exact tier/size you’re selecting in the portal?
• Are you creating inside a VNet or using a private endpoint?
• Have you tried the CLI/ARM approach or checked the Azure Activity Log for more error details?

Reference docs:

1. Choosing the right tier: https://learn.microsoft.com/azure/azure-cache-for-redis/cache-overview#choosing-the-right-tier
2. Quickstart (Basic/Standard/Premium): https://learn.microsoft.com/azure/azure-cache-for-redis/quickstart-create-redis
3. Quickstart (Enterprise tier): https://learn.microsoft.com/azure/azure-cache-for-redis/quickstart-create-redis-enterprise
4. CLI samples: https://learn.microsoft.com/azure/azure-cache-for-redis/cli-samples
5. ARM template/Bicep: https://learn.microsoft.com/azure/azure-cache-for-redis/cache-redis-cache-arm-provision?tabs=CLI
6. Private Link guidance: https://learn.microsoft.com/azure/azure-cache-for-redis/cache-private-link
7. VNet migration guidance: https://learn.microsoft.com/azure/azure-cache-for-redis/cache-vnet-migration

There is a capacity issue in East US. You can deploy in other regions such as Central US, US West 2, or US West 3, as there are no capacity issues in those areas.

You can raise request through the link https://portal.azure.com/#create/Microsoft.Support

Hope this helps—let me know what you find out!