Hi thanks for your post. Yes that seems to be the case. What ive noticed is settings.txt (which holds the connection string, and works when on local host) is not published. Now i have placed this in the directory on the server with ftp... but this then throws the error DNS_PROBE_FINISHED_NXDOMAIN... which is a web page not available error. Its like if i put in the settings.txt file the page is not even found to throw the connection string null error.
Ive looked in the directory of the site i copied the source code and settings.txt is not present there.
I feel like the settings.txt file should be incorporated into the compiled version that is published to azure....
Okay so here is what i found.
The statement of the DNS_PROBE_FINISHED_NXDOMAIN error if settings.txt is present in App_Data is 100% correct. The problem is the URL Azure provides http://yourwebsite.azurewebsites.net/ does not work, and its not until the custom domains are hooked up and used to navigate to the website that the site runs as expected.
Open Start > Settings > Network & Internet > Status
Scroll down to the bottom then click Network reset
If that does not work.
press Windows key + X
Click Device Manager
Expand Network adapters
Right click your adapter
Exit Device Manager, restart. Windows 10 should detect the network adapter then reinstall it. Check if you can connect and browse.