Share via

Cannot create Azure Managed Redis, end in termal state: failed all the time

Johannes Nodop 40 Reputation points
2026-05-19T11:23:43.2966667+00:00

First of all, the question is about Azure Managed Redis but the child tag is missing at the time of writing.

We have tried to do the required switch to azure managed redis but everytime we try to deploy it, it will end up in the terminal state "failed".

We tried it with terraform and from the azure Portal but the result was the same.

I checked quotas (all fine), I checked that the resource provider is registered (it is) and as I also tried to set it up via the Azure Portal I am certain the configuration is correct, available and supported, too.

(I even enabled public access to try and work around any networking issues)

The subscription and my permissions are all fine, too.

The integrated Copilot was (of course) not able to help with this.

Here is an example output:

  • Status: Failed
  • Error Code: OperationFailed
  • Error Message: The operation failed due to a conflict.
Azure Cache for Redis
Azure Cache for Redis

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

Answer accepted by question author

Manoj Kumar Boyini 16,895 Reputation points Microsoft External Staff Moderator
2026-05-20T13:49:28.6233333+00:00

Hi @Johannes Nodop

Thank you for your patience while we investigated the deployment failures.

We have validated this with our backend engineering team, and this behavior is currently due to a capacity constraint in the West Europe region. At this time, the platform is unable to successfully provision new Azure Managed Redis Enterprise instances because of limited available capacity for the required infrastructure configuration. This results in deployments failing with errors such as “OperationFailed – conflict.”

This is a known issue being tracked internally and is not related to your configuration, permissions, or quota settings.

As a workaround, we recommend attempting the deployment in an alternative region such as North Europe or another nearby region where capacity is currently available. Alternatively, you may try provisioning a B10 SKU or higher, as we have observed successful deployments for these SKUs in some cases.

We understand the inconvenience this may cause and appreciate your understanding while the capacity issue is being addressed. Please let us know if you have any questions or concerns.

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jana, Tapas 0 Reputation points
    2026-05-20T08:36:08.4133333+00:00

    I also facing the same error, Azure Managed Redis creation failed from Terraform.

    No specific error root cause is thrown in the log.

    Region:_ West Europe

    Redis Enterprise Name: "redis-test"): polling after Create: polling failed: the Azure API returned the following error: │  │ Status: "Failed" │ Code: "OperationFailed" │ Message: "The operation failed." │ Activity Id: "" │  │ --- │  │ API Response: │  │ ----[start]---- │ { │   "id": "/subscriptions/de02952e-1219-4b45-9b5e-334673dc76bf/providers/Microsoft.Cache/locations/West Europe/operationsStatus/f395fd45-62db-4f76-9b1f-0135f738532f", │   "name": "f395fd45-62db-4f76-9b1f-0135f738532f", │   "status": "Failed", │   "startTime": "2026-05-19T09:44:58.8647494+00:00", │   "endTime": "2026-05-19T10:13:28.9833016+00:00", │   "error": { │     "code": "OperationFailed", │     "message": "The operation failed.", │     "target": null │   }

     

     

    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.