Creation of Azure Managed Redis in North Europe fails

Hello @Robin Smorenburg ,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are trying to create Azure Managed Redis in North Europe, but it fails.

Since the same Azure Managed Redis configuration works in Germany West Central, the root cause is most likely isolated to North Europe regional provisioning, SKU capacity, availability-zone/high-availability placement, or a backend Microsoft.Cache/redisEnterprise service issue. Because, the failure is not proven to be a Terraform code issue. - https://docs.azure.cn/en-us/reliability/overview-reliability-guidance

What you can do is to:

• Stop changing the Terraform configuration randomly because the working deployment in another region already validates the core resource definition.
• Retrieve the failed ARM deployment operation details and correlation ID from the failed North Europe deployment.
• Validate whether the issue is specific to the SKU, high availability setting, or North Europe regional backend capacity.
• If North Europe is mandatory, open an Azure Support request with the failed deployment operation JSON and correlation ID.
• If production cannot wait and business rules allow it, deploy the same Managed Redis configuration in a confirmed working region such as Germany West Central or West Europe.

This is the only reliable path to both restore deployment progress and obtain the real root cause. A regional workaround can unblock deployment, but it does not prove or fix the North Europe backend issue. Azure deployment history provides the failed operation details and correlation ID required by Microsoft Support to trace the failed provisioning operation. - https://library.tf/providers/hashicorp/azurerm/latest/docs/resources/managed_redis

If the workload must stay in North Europe for latency, residency, or compliance reasons, using Germany West Central should not be treated as the final fix. Azure Managed Redis data resides in the selected Azure region by default, and Microsoft recommends placing the cache in the same region as the client application for best performance and lowest latency. - https://www.linkedin.com/pulse/deploying-azure-managed-redis-active-geo-replication-portal-perez-4ghae

Use the associated links for more reading and implementation guides:

• Azure Managed Redis quickstart and regional availability guidance
• Reliability in Azure Managed Redis

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.

Hi @Robin Smorenburg

We identified that the cache creation failure you are experiencing is related to temporary service capacity availability in the Azure region rather than an issue with your configuration or deployment template.

Capacity availability can change over time as Azure resources are continuously allocated and rebalanced across regions and availability zones. Because of this, a retry may succeed if additional capacity becomes available or if the service is able to place the cache on alternate underlying infrastructure.

As potential mitigations, you may consider one or more of the following:

• Retry the cache creation after some time.
• Select an alternative SKU or SKU family.
• Deploy the cache in a different Azure region, if your workload allows.
• Check updates via Service Health in Azure portal.

The Redis Engineering team continues to work closely with the broader Azure platform teams to monitor service capacity and improve the provisioning experience. At this time, we are unable to provide a specific timeline for when additional capacity may become available in the affected region.

We understand the impact this may have on your deployment plans and appreciate your patience. We remain committed to improving capacity planning, visibility, and customer guidance to help reduce the likelihood of similar situations in the future.

Hi,

This is likely due to lack of available capacity in the region. Several other people have experienced same thing recently. Their deployment fails with "OperationFailed" error. As a test, I just tried to create Azure Managed Redis B1 in North Europe and it failed for me as well.

You may try deploying to other nearby (closer than Germany West Central) regions. It may fail in those as well, but worth a try.

-TP