Redis is not able to provision in North Europe but works in West Europe

Question

Redis is not able to provision in North Europe but works in West Europe

Bryson Tai 45

Hi community,

We are trying to provision Azure Managed Redis in North Europe, but it is not working, after some investigation. We found it is North Europe Data Center issue as we are deploy it to West Europe.

The failed Redis only return OperationFailed error, nothing meaningful here. I check the availability of the instance we selected, it is available in this region-zone.

Error Message

"statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"OperationFailed\",\"message\":\"The operation failed.\"}]}}",

Our Redis Configuration, works in West Europe

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "redisEnterprise_redis_name": {
            "defaultValue": "example-redis-name",
            "type": "String"
        }
    },
    "variables": {},
    "resources": [
        {
            "type": "Microsoft.Cache/redisEnterprise",
            "apiVersion": "2026-02-01-preview",
            "name": "[parameters('redisEnterprise_redis_name')]",
            "location": "North Europe",
            "sku": {
                "name": "Balanced_B1"
            },
            "kind": "v2",
            "identity": {
                "type": "None"
            },
            "properties": {
                "minimumTlsVersion": "1.2",
                "highAvailability": "Disabled",
                "publicNetworkAccess": "Enabled"
            }
        }
    ]
}

We need to deploy our infrastructure to North Europe, any idea how to make it feasible? Thanks.

Smaran Thoomu 35,375 Reputation points Moderator

2026-07-14T13:45:02.5066667+00:00

Hi Bryson Tai

Thank you for sharing the detailed information.

I understand that the deployment succeeds in West Europe but fails in North Europe with a generic OperationFailed error. We'll review this further to determine whether this is related to a service-side provisioning issue or a regional constraint.

I have sent you a private message requesting a few additional details. Once we receive them, we'll coordinate with the internal team and update you with our findings.

Thank you for your patience.
Smaran Thoomu 90 Reputation points Microsoft External Staff Moderator

2026-07-15T14:51:43.45+00:00
Hi Bryson Tai

Thank you for your patience and for sharing the requested details via private message.

We reviewed the scenario with our internal team, and the deployment failure is due to a capacity constraint in the North Europe region for the requested Azure Managed Redis SKU. The generic OperationFailed message you're seeing is consistent with this backend provisioning limitation.

At the moment, the available workarounds are:

Retry the deployment after some time, as capacity may become available.

Use a different supported SKU or SKU family, if that meets your requirements.

Deploy the resource to a different Azure region, if your workload allows.

We understand that deploying in North Europe is important for your scenario, and we apologize for the inconvenience this has caused. The issue is currently being tracked internally, and we'll update this thread if there are any significant developments.

If this information was helpful, we'd appreciate it if you could mark the answer as Accepted. This helps other community members facing a similar issue find the relevant guidance more easily.

Thank you for your patience and understanding.
Bryson Tai 45 Reputation points

2026-07-16T07:21:27.1433333+00:00

Thanks for the inspection, may I also know if there are any Azure Tracking Platform to trace the resource availability?

3 answers

Your answer

Smaran Thoomu 35,375 Reputation points Moderator

2026-07-14T13:45:02.5066667+00:00

Hi Bryson Tai

Thank you for sharing the detailed information.

I understand that the deployment succeeds in West Europe but fails in North Europe with a generic OperationFailed error. We'll review this further to determine whether this is related to a service-side provisioning issue or a regional constraint.

I have sent you a private message requesting a few additional details. Once we receive them, we'll coordinate with the internal team and update you with our findings.

Thank you for your patience.
Smaran Thoomu 90 Reputation points Microsoft External Staff Moderator

2026-07-15T14:51:43.45+00:00

Hi Bryson Tai

Thank you for your patience and for sharing the requested details via private message.

We reviewed the scenario with our internal team, and the deployment failure is due to a capacity constraint in the North Europe region for the requested Azure Managed Redis SKU. The generic OperationFailed message you're seeing is consistent with this backend provisioning limitation.

At the moment, the available workarounds are:

Retry the deployment after some time, as capacity may become available.

Use a different supported SKU or SKU family, if that meets your requirements.

Deploy the resource to a different Azure region, if your workload allows.

We understand that deploying in North Europe is important for your scenario, and we apologize for the inconvenience this has caused. The issue is currently being tracked internally, and we'll update this thread if there are any significant developments.

If this information was helpful, we'd appreciate it if you could mark the answer as Accepted. This helps other community members facing a similar issue find the relevant guidance more easily.

Thank you for your patience and understanding.
Bryson Tai 45 Reputation points

2026-07-16T07:21:27.1433333+00:00

Thanks for the inspection, may I also know if there are any Azure Tracking Platform to trace the resource availability?

Answer 1

Hi Bryson Tai

You're welcome!

At the moment, there isn't a public Azure service that provides real-time resource capacity availability for specific SKUs or regions (for example, whether a particular Azure Managed Redis SKU has available capacity in North Europe).

You can use the following Azure services to stay informed about the platform:

Azure Products by Region – This page shows whether an Azure service is available in a particular region, but it does not indicate current provisioning capacity or temporary capacity constraints. https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/table
Azure Service Health – Provides information about active service issues, planned maintenance, and health advisories affecting your subscription.
Azure Resource Health – Shows the health status of your deployed Azure resources.

However, regional capacity constraints for resource provisioning are generally not exposed through these services. When capacity is exhausted, it is typically surfaced only during the provisioning operation (for example, through errors such as OperationFailed or CapacityNotAvailable).

We understand that having visibility into regional capacity availability would be valuable, and we appreciate your feedback. We'll share this as a product improvement suggestion with the appropriate team for consideration.

Thank you for your understanding.

Answer 2

Simon Minotto 0

I have the same issue, we can't create B3 or B6 or B20 in north europe, it's always failing :/

Smaran Thoomu 90 Reputation points Microsoft External Staff Moderator

2026-07-20T02:14:31.6166667+00:00
Hi Simon Minotto Thank you for the update.

We understand that you're both experiencing the same behavior when provisioning Azure Managed Redis in the North Europe region.

Based on our internal investigation, this is consistent with the current regional capacity constraints affecting the requested Azure Managed Redis SKUs in North Europe. The issue is already being tracked internally.

At this time, the available workarounds remain:

Retry the deployment after some time, as capacity may become available.

Use a different supported SKU or SKU family, if it meets your requirements.

Deploy to another Azure region, if your workload allows.

We'll update this thread if there are any significant developments or when additional information becomes available.

Thank you both for your patience and understanding.

Answer 3

Hi Bryson, because the same template succeeds in West Europe, I would treat this as either regional capacity/feature availability or a preview API issue rather than a basic template error. First try the current stable API version and confirm that Balanced_B1, kind v2, and your requested availability settings are supported in North Europe for your subscription. Check Microsoft.Cache provider registration, quota, Resource Health, and the deployment operation details rather than only the top-level OperationFailed message. If the stable configuration still fails only in North Europe, keep the failed deployment/correlation ID and open a Redis support case; regional capacity failures usually need the service team to confirm or allocate capacity. Avoid repeated rapid deployments, as they can leave overlapping operations and make the evidence harder to read.