Failure to deploy an Azure Managed Redis resource in West Europe region

Question

Failure to deploy an Azure Managed Redis resource in West Europe region

Vladislav Karamfilov 15

We are trying to deploy a non-clustered Azure Managed Redis resource in West Europe. We have tried with different sizes (B0, B1, B3, B5) and all deployments are failing with statusCode: "Conflict", statusMessage: { "status": "Failed", "error": { "code": "OperationFailed", "message": "The operation failed." } }. Deployment of B0 non-clustered Azure Managed Resource in North Europe region succeeded but we want our Redis resource to be in West Europe.

Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-05-20T07:39:19.5166667+00:00
Hi **Vladislav Karamfilov,
**Thankyou for reaching microsoft Q&A!

Have you tried any other nearby regions (e.g., North Europe, France Central) and confirmed success?

Is the issue consistent across all SKUs or only specific sizes?

Are you enabling zone redundancy during deployment?
Vladislav Karamfilov 15 Reputation points

2026-05-20T12:02:36.1566667+00:00
Hello @Pilladi Padma Sai Manisha

As I described in the issue description - we have successfully deployed a North Europe resource but it's not what we need.

We have tried all of the described sizes and all failed in the same way - after 30 minutes we get the described error above.

Zone redundancy is auto-enabled for West Europe (with High Availability turned on as we do and need)
Martin Møller 5 Reputation points

2026-05-20T12:11:12.6866667+00:00

Experiencing the exact same problem as described by @Vladislav Karamfilov Experienced the first time ~24 hours ago.

Deployments to other regions than West Europe succeeds while West Europe continues to fail after about 30 mins.
Vladislav Karamfilov 15 Reputation points

2026-05-21T13:35:17.1066667+00:00

Thank you, @Pilladi Padma Sai Manisha !

We will consider using the North Europe region but we are concerned about the latency we'll introduce. We don't need this big cache size as B10 - actually, B0 is more than enough for our current usage patterns.

When do you expect the issue to be resolved for the West Europe region? How can Azure clients be informed about this fix (should we subscribe to some news feed or something)?
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-05-25T11:16:28.9866667+00:00

Hi Vladislav Karamfilov,

We are currently coordinating with our team regarding the ETA. We will provide you with an update as soon as we receive further information from them.
Reece Collett 1 Reputation point

2026-05-28T07:47:09.2133333+00:00

This is affecting us greatly - Is there any update on an ETA for this to be resolved?
Martin Bach 0 Reputation points

2026-07-29T15:18:58.7733333+00:00

hi @Pilladi Padma Sai Manisha ,

any updates here?
Sreekumar Gopakumar 0 Reputation points

2026-07-30T05:33:31.4166667+00:00

I face the same error for West Europe, North Europe and Sweden Central now. So what's the solution to fix this ?

2 answers

Your answer

Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-05-20T07:39:19.5166667+00:00

Hi **Vladislav Karamfilov,
**Thankyou for reaching microsoft Q&A!

Have you tried any other nearby regions (e.g., North Europe, France Central) and confirmed success?

Is the issue consistent across all SKUs or only specific sizes?

Are you enabling zone redundancy during deployment?
Vladislav Karamfilov 15 Reputation points

2026-05-20T12:02:36.1566667+00:00

Hello @Pilladi Padma Sai Manisha

As I described in the issue description - we have successfully deployed a North Europe resource but it's not what we need.

We have tried all of the described sizes and all failed in the same way - after 30 minutes we get the described error above.

Zone redundancy is auto-enabled for West Europe (with High Availability turned on as we do and need)
Martin Møller 5 Reputation points

2026-05-20T12:11:12.6866667+00:00

Experiencing the exact same problem as described by @Vladislav Karamfilov Experienced the first time ~24 hours ago.

Deployments to other regions than West Europe succeeds while West Europe continues to fail after about 30 mins.
Vladislav Karamfilov 15 Reputation points

2026-05-21T13:35:17.1066667+00:00

Thank you, @Pilladi Padma Sai Manisha !

We will consider using the North Europe region but we are concerned about the latency we'll introduce. We don't need this big cache size as B10 - actually, B0 is more than enough for our current usage patterns.

When do you expect the issue to be resolved for the West Europe region? How can Azure clients be informed about this fix (should we subscribe to some news feed or something)?
Pilladi Padma Sai Manisha 11,605 Reputation points Microsoft External Staff Moderator

2026-05-25T11:16:28.9866667+00:00

Hi Vladislav Karamfilov,

We are currently coordinating with our team regarding the ETA. We will provide you with an update as soon as we receive further information from them.
Reece Collett 1 Reputation point

2026-05-28T07:47:09.2133333+00:00

This is affecting us greatly - Is there any update on an ETA for this to be resolved?
Martin Bach 0 Reputation points

2026-07-29T15:18:58.7733333+00:00

hi @Pilladi Padma Sai Manisha ,

any updates here?
Sreekumar Gopakumar 0 Reputation points

2026-07-30T05:33:31.4166667+00:00

I face the same error for West Europe, North Europe and Sweden Central now. So what's the solution to fix this ?

Answer 1

Pilladi Padma Sai Manisha 11,605 Microsoft External Staff Moderator

Hi Vladislav Karamfilov,
We validated this internally with the engineering team, and the deployment failures are currently caused by a capacity constraint in the West Europe region for Azure Managed Redis Enterprise.

This is a known platform-side issue and not related to your configuration, quota, or permissions. As a workaround, please use another region such as North Europe or try a B10 SKU or higher, as some higher SKUs are provisioning successfully.

Thanks for your patience and understanding.

0 comments

Answer 2

Taz 9,366 MVP Volunteer Moderator

Hi Vladislav,

This looks more like a regional capacity issue in West Europe rather than a deployment/configuration problem, especially since the same deployment works in North Europe.

The Conflict / OperationFailed error is commonly seen when the selected Redis SKU currently has limited or unavailable capacity in that region.

Please check:

Activity Log for a detailed backend error

Any subscription quota/policy restrictions

Deployment without zone redundancy (if enabled)

Since all tested SKUs are failing only in West Europe, I would recommend raising a support ticket with the correlation ID and deployment timestamp for backend validation.

Vladislav Karamfilov 15 Reputation points

2026-05-20T11:27:35.59+00:00

Hello @Taz and thank you for the quick answer!

I have checked the Activity Log and didn't find any additional info about the underlying reason. I don't see any quotas we can request for Redis resources. During creation we always check High Availability which handles the zone redundancy requirements in the selected region (as far as I understand from the docs). We cannot raise a support ticket because we are not paying for a support plan in this subscription and in another one we have we pay for the basic support which basically sends us here...