My question is about existing functionality and if I have misconfigured a privatelink.

I have an app service that is publicly accessible. Let’s say with a custom domain name mytestsite.com so that points to mytestsite.azurewebsites.net.

This app service connects to databases and other external services that are on a vnet so I’ve enabled vnet between the app service and these other services. Now that I’ve done that, an nslookup to my public custom domain name includes the privatelink url that looks like mytestsite.privatelink.web.azurewebsites.com.

Our customer who connects to our public site via a custom domain has their own private network with privatelink dns zone from azure which are now conflicting with the privatelink url showing in our nslookup.

I can’t tell if there is a misconfiguration on our side or on their side or if adding an app service to a vnet is behaving as intended. Should it have the privatelink url in nslookup?