Azure redis cache is not being created in vnet private subnet

Subu 0 Reputation points
2024-10-29T23:11:17.4633333+00:00

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"}

Azure Cache for Redis
Azure Cache for Redis
An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.
259 questions
{count} votes

1 answer

Sort by: Most helpful
  1. hossein jalilian 8,150 Reputation points
    2024-10-29T23:26:29.2966667+00:00

    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

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.