Hi @Kavita Sachdeva
Welcome to the Microsoft Q&A and thank you for posting your questions here.
Approval in Azure only confirms the Private Endpoint connection on the resource side. CCV2 still needs DNS and network path to resolve and reach the Private Endpoint.
Checklist to fix:
- Ensure Private DNS zone
privatelink.redis.cache.windows.netexists, has an A record for your cache, and is linked to the VNet hosting the Private Endpoint. - Verify CCV2 resolves
yourcache.redis.cache.windows.net→ Private IP (via CNAME toprivatelink.redis.cache.windows.net). - Confirm CCV2 network can reach the VNet (VNet peering or VPN/ExpressRoute).
- Check cache SKU and
publicNetworkAccesssetting (Enterprise tiers require Private Link only). - If CCV2 still shows Awaiting Approval, open a SAP CCV2 ticket after DNS and connectivity are fixed.
Run nslookup yourcache.redis.cache.windows.net from CCV2 and confirm it returns the Private IP, not a public one.
References:
https://xtls-v4.hkg1.meaqua.org/azure/azure-cache-for-redis/cache-private-link https://xtls-v4.hkg1.meaqua.org/azure/azure-cache-for-redis/cache-private-link#troubleshooting