InsufficientCapacity sur Managed Redis en West Europe

Julien B 0 Points de réputation
2026-09-30T07:31:48.8133333+00:00

Bonjour,

Voici l'analyse du bot de support azure sur mon impossibilité de créer des instances de managed redis en west europe:

The Managed Redis deployment in West Europe is failing because the region does not currently have enough capacity to place the resource. Repeated creation attempts for the Redis instance in the target resource group returned ResourceOperationFailure with a nested InsufficientCapacity error and the message that the request failed due to insufficient capacity, recommending a different Redis size or region. The failure is not limited to one SKU, since attempts with both Balanced_B10 and MemoryOptimized_M10 also failed the same way. There is no corresponding Redis service health incident or active platform issue identified that would explain the failure, and the resource health state being Unknown/Transient does not indicate a separate root cause. The evidence points to a West Europe platform capacity constraint as the actionable cause. The failure is caused by a regional capacity shortage for Azure Managed Redis in West Europe. Evidence found:

  • The Redis resource in rg-weu-ass-prd-vmselectassur (test-prd-redis) was created in West Europe, which is a supported region for Azure Managed Redis.
  • Multiple create attempts for that same resource failed with ResourceOperationFailure and the nested error InsufficientCapacity / “Request failed due to insufficient capacity. Retry using a different Azure Managed Redis size or region.”
  • The failure was not tied to one SKU: the logs show failed attempts with both Balanced_B10 and MemoryOptimized_M10.
  • Subscription health data showed no active or resolved Redis service issues in the last 30 days; the only active service-health item was unrelated maintenance for Azure Database for MySQL Flexible Server.
  • The resource’s current health is reported as Unknown/Transient, which does not contradict the provisioning failure but does not provide a separate root cause. Overall, the evidence points to a platform-side capacity constraint in West Europe rather than a configuration, policy, or service-health incident.

J'ai bien compris que le problème concerne bien les instances managed redis sur west europe , la question est de savoir si des actions sont en cours pour résoudre ce soucis, et quand peut on espérer avoir une disponibilité de ce service en west europe?
Il n'est pas question pour moi de créer ce service en north europe ou autre région, mon infra est sur west europe.
Merci d'avance,

Cache Azure pour Redis
Cache Azure pour Redis

Service Azure qui donne accès à un cache Redis sécurisé et dédié, géré par Microsoft.

0 commentaires Aucun commentaire

1 réponse

Trier par : Les plus anciens
  1. Maksood Ahmed 10 Points de réputation Personnel externe Microsoft Modérateur
    2026-10-01T11:52:48.28+00:00

    Hello @Julien B ,

    Since the Managed Redis resource is still showing Updating and the user assignment is stuck in Deleting, I recommend not deleting or recreating the Redis instance, especially because it is currently in use.

    Please try the following:

    1. Open the Managed Redis resource in the Azure portal.
    2. Go to Activity Log and check the user access removal operation for any failure or error details.
    3. Check Resource Health to see whether Azure reports any issue with the resource.
    4. Avoid repeatedly trying to delete the user assignment while the current operation is still processing.

    If the resource continues to stay in Updating, please share the relevant error from the Activity Log here. Make sure to remove subscription IDs and any sensitive information before posting it. This will help us understand why the operation is stuck and determine the next step without affecting the active Redis instance.

    FYR:

    Azure Managed Redis access policy assignment REST API

    Azure CLI - Redis access policy assignments

    Cette réponse a-t-elle été utile ?


Votre réponse

Les réponses peuvent être marquées comme « Acceptées » par l’auteur de la question et « Recommandées » par les modérateurs, ce qui aide les utilisateurs à savoir que la réponse a résolu le problème de l’auteur.