Azure redis cache is not being created in vnet private subnet

Question

Vnet = 10.0.0.0/16
Subnet = 10.0.1.0/24 (private subnet)

capacity = 1

family = "P"

sku_name = "Premium"

non_ssl_port_enabled = true

minimum_tls_version = "1.2"

public_network_access_enabled = false

redis_version = 6

While creating the redis cache with above given parameters, we are getting error.

{"code":"AzureCacheForRedisLongRunningOperationFailure","message":"An error occurred during the long running operation. Request Id: 38562d60-7c14-40d5-aa51-820a151f2ac3, Correlation id: eba85af0-2f5c-44ff-9256-43eec01b553a"}

Answer

Thanks for posting your question in the Microsoft Q&A forum.

Ensure the subnet you're using (10.0.1.0/24) is dedicated to Azure Cache for Redis and doesn't contain other resources,(Azure Cache for Redis requires a dedicated subnet when using VNet integration)
Make sure there are enough available IP addresses in the subnet. Azure Cache for Redis needs at least 5 IP addresses for a non-clustered cache
Verify that the account you're using has the necessary permissions to create resources in the specified VNet and subnet.
Make sure there's no NAT Gateway assigned to the subnet, as Azure Cache for Redis is not compatible with NAT Gateways

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful

Share via

Azure redis cache is not being created in vnet private subnet

1 answer

Your answer