Welcome to Microsoft Q&A forum.
As I understand, you want to restrict the Azure redis cache using private endpoint.
Your application should connect to
<cachename>.redis.cache.windows.net on port
6380. We recommend avoiding the use of
<cachename>.privatelink.redis.cache.windows.net in configuration or connection string.
A private DNS zone, named
*.privatelink.redis.cache.windows.net, is automatically created in your subscription. The private DNS zone is vital for establishing the TLS connection with the private endpoint.
For more information, see Azure services DNS zone configuration.
Why can't I connect to a private endpoint?
- Private endpoints can't be used with your cache instance if your cache is already a VNet injected cache.
- You have a limit of one private link for clustered caches. For all other caches, your limit is 100 private links.
- You try to persist data to storage account where firewall rules are applied might prevent you from creating the Private Link.
- You might not connect to your private endpoint if your cache instance is using an unsupported feature.
What features aren't supported with private endpoints?
- Trying to connect from the Azure portal console is an unsupported scenario where you'll see a connection failure.
- Private links can't be added to caches that are already geo-replicated. To add a private link to a geo-replicated cache: 1. Unlink the geo-replication. 2. Add a Private Link. 3. Last, relink the geo-replication.
Please check and let us know if above pointers are correctly done in your Redis Cache.
Also verify that your app service is deployed in the same virtual network and subnet as the private endpoint for the Redis Cache.
Share screenshots or other relevant details to troubleshoot the issue.