Share via

ResourceDeploymentFailure when deploying Azure Managed Redis

Marc 20 Reputation points
2025-12-01T17:56:23.1766667+00:00

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

I have tried to deploy a Managed Redis resource to a subscription in West Europe location without success. I tried the exact same deployment in another subscription in the same location, and in the same subscription but another location and both worked. I am not sure what is causing the issue following these 2 successful tests.

The error is very generic in the portal:

"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

And in az cli:

Operation returned an invalid status 'OK'

This is the command I used in CLI, while in portal I used default settings:

az redisenterprise create `
    --resource-group $RG `
    --name $NAME `
    --location $LOCATION `
    --sku $SKU `
    --public-network-access $PublicAccess

Can this be related to regional quota for this subscription? What can be the reason and how to find out? Thank you.

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
  1. Q&A Assist
    2025-12-01T17:56:42.3733333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error message you are encountering during the deployment of Azure Managed Redis could indeed be related to regional quotas for your subscription. Azure has specific quotas for resources that can be deployed in each region, and if you exceed these limits, it can lead to deployment failures.

    To investigate this issue further, you can check the following:

    1. Quota Limits: Review the quotas for your subscription in the West Europe region. You can find this information in the Azure portal under the subscription settings or by using Azure CLI commands to list your current resource quotas.
    2. Resource Group Status: Ensure that the resource group you are deploying to is not in a state of deletion or any other operation that might affect new deployments.
    3. Deployment Logs: Check the deployment logs for more detailed error messages that can give you insights into why the deployment failed. You can find these logs in the Azure portal under the deployment history of the resource group.
    4. Resource Availability: Confirm that the SKU you are trying to deploy is available in the West Europe region. Sometimes, specific SKUs may have limited availability in certain regions.

    If after checking these factors the issue persists, consider reaching out to Azure support for further assistance.

    References:

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pilladi Padma Sai Manisha 590 Reputation points Microsoft External Staff Moderator
    2025-12-01T18:54:17.2266667+00:00

    Hi Marc,
    Thank you for reaching out to Microsoft QA!

    From the details you've given, since the deployment succeeds in other subscriptions and regions but fails in this specific subscription and location, the most common cause is hitting a regional quota limit for Redis or related resources in your subscription. Azure imposes quotas on the number of resources and vCPU cores a subscription can use in each region, and exceeding these limits will cause deployments to fail with errors like the one you encountered.

    Here are recommended next steps to resolve this issue:

    In the Azure Portal, go to Subscriptions > Select your affected subscription > Usage + quotas. Check the Redis SKU quotas and any compute (vCPU) quotas for the West Europe region.

    If you see your quota is 0 or fully used up for the Redis SKU or related resources, submit a quota increase request from the portal.

    Make sure the Microsoft.Cache resource provider is registered in your subscription.

    Double-check your deployment parameters (SKU, location, public network access) to ensure they are valid and supported in that region.

    Review the Activity Log for specific error messages related to the failed provisioning operation.

    If you have any partially created Redis resources stuck in provisioning, try deleting those before retrying.

    If after verifying quotas and configuration the problem persists, please share your deployment error messages or request IDs so we can assist you further. Following these steps typically resolves such deployment failures.

    We appreciate your understanding and are committed to helping you successfully deploy your Azure Managed Redis instance.

    Given that B0 works in other subscriptions/regions, and B1 works in this subscription and region, this points to a subscription + West Europe specific restriction or capacity limitation for the Balanced B0 tier, rather than an issue with your template or Managed Redis itself. Some of these SKU/region constraints are internal and do not surface as visible Redis quotas in the portal, which is why you could not see an obvious quota entry.

    If this solution helped resolve your issue, please consider clicking ‘Accept Answer’ or giving it an upvote to help others find it easily.

    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.