Troubleshooting

Below are some common troubleshooting steps you may need.

The below can be executed by:

• Open Kudu → Debug console → CMD

Check DNS from App Service to Private PaaS Resources

The below commands can be ran in the console for the app service to check you can resolve the Azure PaaS services such as the database and storage via their private IP addresses.

:: SQL logical server (expects CNAME → *.privatelink.database.windows.net → private IP)
nameresolver myserver.database.windows.net

:: Storage blob endpoint (expects CNAME → *.privatelink.blob.core.windows.net → private IP)
nameresolver mystorageacct.blob.core.windows.net

:: (Optional) Queue/File/Table if used
nameresolver mystorageacct.queue.core.windows.net
nameresolver mystorageacct.file.core.windows.net
nameresolver mystorageacct.table.core.windows.net

Port Reachability

The below commands check that you can reach the storage and database via their appropriate ports.

:: SQL over 1433
tcpping myserver.database.windows.net 1433

:: Storage over 443
tcpping mystorageacct.blob.core.windows.net 443

Check SCM endpoint for web app and function apps

This lets you check the SCM endpoint used for deployment resolves to the private endpoint.

nameresolver myapp.scm.azurewebsites.net

Expect CNAME → *.scm.privatelink.azurewebsites.net → private IP.

Slow DNS Resolution

If you are using a custom DNS then sure you have auto forwarders to forward to Azure DNS where appropriate