Error during Azure Redis Cache Deployment: status Failed

Question

Error during Azure Redis Cache Deployment: status Failed

ManuelM 0

Issue Description:

I'm encountering an error while deploying an Azure Redis Cache instance using Terraform in my development environment. The deployment fails with the following message:

{
    "authorization": {
        "action": "Microsoft.Cache/redis/write",
        "scope": "/subscriptions/94a9e5d9-7934-4263-8dab-d6aa4c055c8f/resourceGroups/sikuro-dev/providers/Microsoft.Cache/redis/sikurosharedcache-sikuro-dev"
    },
    "status": {
        "value": "Failed",
        "localizedValue": "Failed"
    },
    "properties": {
        "statusMessage": "{\"status\":\"Failed\",\"error\":{\"code\":\"ResourceOperationFailure\",\"message\":\"The resource operation completed with terminal provisioning state 'Failed'.\",\"details\":[{\"code\":\"AzureCacheForRedisLongRunningOperationFailure\",\"message\":\"An error occurred during the long running operation. Request Id: 89455630-5b77-4224-9748-27aa873f23d1, Correlation id: 5f910495-d578-47da-8b79-230008a3582f\"}]}}"
    }
}

What I’ve Tried So Far:

Checked Role Assignments: The identity performing the deployment has Contributor permissions on the resource group.
Subscription Quotas: Verified that my subscription allows Redis Cache creation in this region.
Network Considerations: The Redis instance is not deployed within a VNET, so no firewall issues should be present.
Retries: Attempted redeploying with different capacity without success

Questions:

Does this error indicate a permissions issue, or could it be related to the SKU misconfiguration?

Could this be caused by a regional quota or a provisioning limitation?

Is there a way to get more detailed logs on why the Redis instance is failing to provision?

Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-04T10:58:51.3233333+00:00
Hi @Manuelm Maida

Greetings!

As I understand it, you're encountering an issue while deploying Azure Redis Cache.

Based on the information you've provided, it appears to be related to a provisioning limitation.

Here are some insights and suggestions to help you manage this setup more efficiently.

When you deploy Azure Cache for Redis to a Resource Manager virtual network, the cache must be in a dedicated subnet that contains no other resources except for Azure Cache for Redis instances. If you attempt to deploy an Azure Cache for Redis instance to a Resource Manager virtual network subnet that contains other resources, or has a NAT Gateway assigned, the deployment fails. The failure is because Azure Cache for Redis uses a basic load balancer that is not compatible with a NAT Gateway

There are some VNet limitations when provisioning Azure Redis Cache.

When using a VNet injected cache, you must keep your VNet updated to allow access to cache dependencies, such as Certificate Revocation Lists, Public Key Infrastructure, Azure Key Vault, Azure Storage, Azure Monitor, and more.

VNet injected caches are only available for Premium-tier Azure Cache for Redis, not other tiers.

You can't inject an existing Azure Cache for Redis instance into a Virtual Network. You must select this option when you create the cache.

The subnet range you use for creating the cache should not already be in use by other resources within that VNet. Please refer to the Microsoft documentation link for common misconfiguration issues with Azure Redis Cache and VNets. Configure a virtual network - Premium-tier Azure Cache for Redis instance - Azure Cache for Redis | Microsoft Learn I hope this information helps. Please do let us know if you have any further queries.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-07T09:23:11.2666667+00:00

Hi @Manuelm Maida

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-08T01:50:16.7633333+00:00

Hi @Manuelm Maida

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
ManuelM 0 Reputation points

2025-04-08T16:23:37.01+00:00

Thank you for the detailed response. I'd like to clarify my current setup:

My Redis instance is being deployed in the same subnet as my AKS cluster, with no other services present except for these two resource types. What's puzzling is that I've successfully instantiated the same Redis configuration in another subscription without any issues.

The reason I need to keep the Redis instance in the same subnet as AKS is connectivity - when I've tried placing Redis in a separate subnet, I've encountered persistent connection issues from the pods.

I should also note that I'm using Basic tier Redis instances, not Premium.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-09T11:15:16.38+00:00

Hi @Manuelm Maida

Thank you for your quick response.

My recommendation is to Choose a storage account in the same region and subscription as the cache. A Premium Storage account is recommended due to its higher throughput. Additionally, we strongly recommend disabling the soft delete feature on the storage account, as it can increase storage costs. For more information, please refer to the relevant documentation.

What is Azure Cache for Redis? - Azure Cache for Redis | Microsoft Learn

Note that data persistence is not available in the Basic and Standard tiers.

Please let me know if you need any more information. We are happy to assist.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-10T08:48:02.8266667+00:00

Hi @Manuelm Maida

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-11T08:44:17.48+00:00

Hi @Manuelm Maida

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Your answer

Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-04T10:58:51.3233333+00:00

Hi @Manuelm Maida

Greetings!

As I understand it, you're encountering an issue while deploying Azure Redis Cache.

Based on the information you've provided, it appears to be related to a provisioning limitation.

Here are some insights and suggestions to help you manage this setup more efficiently.

When you deploy Azure Cache for Redis to a Resource Manager virtual network, the cache must be in a dedicated subnet that contains no other resources except for Azure Cache for Redis instances. If you attempt to deploy an Azure Cache for Redis instance to a Resource Manager virtual network subnet that contains other resources, or has a NAT Gateway assigned, the deployment fails. The failure is because Azure Cache for Redis uses a basic load balancer that is not compatible with a NAT Gateway

There are some VNet limitations when provisioning Azure Redis Cache.

When using a VNet injected cache, you must keep your VNet updated to allow access to cache dependencies, such as Certificate Revocation Lists, Public Key Infrastructure, Azure Key Vault, Azure Storage, Azure Monitor, and more.

VNet injected caches are only available for Premium-tier Azure Cache for Redis, not other tiers.

You can't inject an existing Azure Cache for Redis instance into a Virtual Network. You must select this option when you create the cache.

The subnet range you use for creating the cache should not already be in use by other resources within that VNet. Please refer to the Microsoft documentation link for common misconfiguration issues with Azure Redis Cache and VNets. Configure a virtual network - Premium-tier Azure Cache for Redis instance - Azure Cache for Redis | Microsoft Learn I hope this information helps. Please do let us know if you have any further queries.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-07T09:23:11.2666667+00:00

Hi @Manuelm Maida

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-08T01:50:16.7633333+00:00

Hi @Manuelm Maida

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
ManuelM 0 Reputation points

2025-04-08T16:23:37.01+00:00

Thank you for the detailed response. I'd like to clarify my current setup:

My Redis instance is being deployed in the same subnet as my AKS cluster, with no other services present except for these two resource types. What's puzzling is that I've successfully instantiated the same Redis configuration in another subscription without any issues.

The reason I need to keep the Redis instance in the same subnet as AKS is connectivity - when I've tried placing Redis in a separate subnet, I've encountered persistent connection issues from the pods.

I should also note that I'm using Basic tier Redis instances, not Premium.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-09T11:15:16.38+00:00

Hi @Manuelm Maida

Thank you for your quick response.

My recommendation is to Choose a storage account in the same region and subscription as the cache. A Premium Storage account is recommended due to its higher throughput. Additionally, we strongly recommend disabling the soft delete feature on the storage account, as it can increase storage costs. For more information, please refer to the relevant documentation.

What is Azure Cache for Redis? - Azure Cache for Redis | Microsoft Learn

Note that data persistence is not available in the Basic and Standard tiers.

Please let me know if you need any more information. We are happy to assist.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-10T08:48:02.8266667+00:00

Hi @Manuelm Maida

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mallaiah Sangi 650 Reputation points Microsoft External Staff

2025-04-11T08:44:17.48+00:00

Hi @Manuelm Maida

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

Error during Azure Redis Cache Deployment: status Failed

Your answer