If you attempted to connect your app to a subnet and it failed and would like to get more information, this flow will help you with this. Tried to configure VNet integration via Azure Portal or ARM template, but it failed The troubleshooter will show you the results clearly along with recommendations: The connection could succeed on a tcp level, but you might still be facing issues executing http requests for example. Please note that this is just a tcpping from your app’s instance to the specific endpoint. You can use a hostname:port or IP:port combination to test the connectivity. If everything looks healthy or just a warning insights was discovered, the flow will continue to ask for an endpoint to test connectivity to.

If an issue is found, the troubleshooter will display the issue along with the recommended next steps to you: This flow will start by running the following checks on your app: Unable to connect to a resource, such as SQL or Redis or on-prem, in my Virtual Network This guided troubleshooter takes you step by step to understand your issue and provide curated solutions based on your inputs: You can access the tool by going to the Diagnose & Solve Problems blade and either use the search bar to search for it or use the quick link available under popular troubleshooting tools section: We are happy to announce the release of our new diagnostic tool ‘Network/Connectivity Troubleshooter’ available now in the Diagnose & Solve Problems blade. Troubleshooting networking & connectivity issues when running on App Services just became easier.

Troubleshoot Network/Connectivity issues on App Service & Functions

Azure web app deployment slot vnet