Azure Managed Redis (Redis Enterprise) creation fails with generic OperationFailed in UK South

Frode Nilsen 5 Reputation points
2026-06-19T14:00:02.3566667+00:00

Creating a new Azure Managed Redis (Microsoft.Cache/redisEnterprise) resource,

SKU Balanced_B0, in UK South fails consistently with no useful detail:

Status: Failed

Code: OperationFailed

Message: The operation failed.

Target: null

I experienced these failures throughout the entire day on both 18 June 2026

and 19 June 2026. This has failed identically across multiple attempts and

2 separate subscriptions, each attempt using a fresh resource name, hours

apart — so it's not a naming conflict, Terraform state issue, or

recreate-too-soon timing problem.

Failed operation IDs (region: UK South, 19 June 2026):

  • be5ca506-83b3-4d6c-83d9-febaec55c05b (10:02 - 10:05 UTC)
  • 61458a92-6773-4825-a766-dd31a622eb2f (10:29 - 10:31 UTC)
  • ce0ff0f4-8890-4fdf-b41d-a4dbbbd72a52 (11:50 - 11:52 UTC)

Notably, a creation of the same SKU/resource type DID briefly succeed in

UK South on 19 June (~08:45 UTC) before failures resumed shortly after, so

this isn't a permanent regional limitation — it looks intermittent/ongoing

across both days.

No incidents are showing on the public Azure status page for UK South /

Azure Cache for Redis at this time.

Has anyone else seen Balanced_B0 Redis Enterprise creation fail in UK South

over the past two days? Looking for root cause or a known workaround (e.g.

different SKU, different availability zone) while waiting on this.

Azure Cache for Redis
Azure Cache for Redis

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Manoj Kumar Boyini 19,270 Reputation points Microsoft External Staff Moderator
    2026-06-19T21:57:49.8766667+00:00

    Hi @Frode Nilsen

    Could you please wait for some time and then try deploying the Azure Managed Redis instance again. This behavior can occasionally occur due to temporary capacity constraints in the region.

    If the issue persists, please try provisioning the instance in a different region and let us know the outcome. This will help determine whether the issue is specific to the UK South region.

    Was this answer helpful?

    0 comments
  2. Frode Nilsen 5 Reputation points
    2026-06-19T17:43:51.2533333+00:00

    Hello

    No custom VNet/subnet, this is a fully public-network deployment, no NSGs, UDRs, firewall, or proxy involved. The Terraform resource has no subnet_id and public_network_access = "Enabled". Confirmed on the resource itself too:

    privateEndpointConnections: [], nothing custom in the network path.

    Balanced_B0 maps to the Balanced tier, size B0 (the smallest in that family).

    Additional options enabled:

    • high_availability_enabled = true (redundancyMode: ZR - zone-redundant)
    • clustering_policy: OSSCluster
    • client_protocol: Encrypted
    • eviction_policy: AllKeysLRU
    • persistence: both AOF and RDB disabled (no persistence)

    Importantly: the exact same Terraform configuration, identical SKU

    (Balanced_B0), identical options above, no code changes at all -> succeeds

    reliably and consistently when targeting UK West.

    The only variable changed between successful and failing attempts is the region (UK South vs UK West).

    Was this answer helpful?

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.