Azure Managed Redis (redisEnterprise) deployment failed

Abhishek Antony (CP, IN) 0 Reputation points
2026-06-30T13:01:46.21+00:00
Creating an Azure Managed Redis cluster in West Europe fails after ~2 minutes
of provisioning with a generic terminal error "OperationFailed / The operation failed"
(statusCode Conflict). No actionable detail is returned at any layer (deployment
operations, activity log, operationStatus)

error :

{
  "code": "DeploymentFailed",
  "target": "/subscriptions/<sub-id>/resourceGroups/rg-gen/providers/Microsoft.Resources/deployments/CreateRedisEnterprise-red-th-20260630180636",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
  "details": [
    {
      "code": "ResourceDeploymentFailure",
      "target": "/subscriptions/<sub-id>/resourceGroups/rg-gen/providers/Microsoft.Cache/redisEnterprise/red-th",
      "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."
    }
  ]
}
Azure Cache for Redis
Azure Cache for Redis

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

0 comments No comments

1 answer

Sort by: Most helpful
  1. Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator
    2026-07-02T07:15:34.1433333+00:00

    Hi @Abhishek Antony (CP, IN)
    Thanks for sharing the error details.

    The DeploymentFailed / ResourceDeploymentFailure message is a generic Azure Resource Manager error indicating that the Azure Managed Redis (Microsoft.Cache/redisEnterprise) resource reached a terminal Failed provisioning state. Since the deployment and Activity Log don't provide a more specific error, this can occur for several reasons, including transient backend provisioning issues, regional capacity constraints, or SKU/configuration availability.

    To help narrow down the cause, I'd recommend the following:

    • Review the Activity Log and Deployment operations for the failed deployment to see if any additional diagnostic information or correlation IDs are available. The following article explains how to inspect deployment operations: https://learn.microsoft.com/azure/azure-resource-manager/templates/deployment-operations
    • Check Azure Service Health to determine whether there are any ongoing service issues affecting Azure Managed Redis in the target region: https://status.azure.com/
    • Retry the deployment after some time, as transient provisioning failures can occasionally resolve on a subsequent attempt.
    • If possible, try deploying the same configuration in another supported Azure region. If the deployment succeeds elsewhere, it may indicate a region-specific capacity or provisioning issue.
    • Verify that the selected SKU and configuration are supported in the target region and that your subscription has any required quota or capacity available.

    If the issue persists after these checks, it would be helpful if you could share the following information (excluding any sensitive details):

    • Which Azure Managed Redis SKU and size are you deploying?
    • Is the deployment being performed through the Azure portal, ARM/Bicep template, Azure CLI, or PowerShell?
    • Does the failure occur only in West Europe, or have you observed the same behavior in another region?
    • Are there any additional details shown in the Activity Log or deployment operations (for example, a correlation ID or nested error message)?

    If no additional diagnostics are available and the deployment consistently fails, I'd recommend opening an Azure Support request so the engineering team can review the backend provisioning logs for the failed operation.

    References:

    I hope this helps. Please let us know the results of the above checks, and we'll be happy to assist further.

    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.