Azure Web App – set custom domain sub directory

You would simply click the Add Hostname, and add www.whateverdomain.com in. At that point, Azure will try to verify the new hostname... So you will want to have the DNS already setup to point to your Azure IP for the web app. You could try it without DNS setup, it may have other options now (It seems like every time I login lately, that azure has new features/options). Worst case scenario you will need to remove the custom name and re-add it.

If you are just looking to test something on your webapp and do not own a custom domain or do not want to wait for DNS etc, you can modify your hosts file on your local workstation. Assuming a Windows OS, modify the file: c:\windows\system32\drivers\etc\hosts At the end of the file add a new line with your IP, space, your domain name. So:

1.2.3.4 www.whateverdomain.com

Then you will be able to browse to www.whateverdomain.com and it should work.

Azure I believe is looking for the host headers. With this hosts file trick, your machine will send the host header in the request that Azure is looking for.

I spoke with Azure support. You can, in fact, bind the same domain name to two different WebApps in this scenario, provided that:

1. They are different regions
2. You target them with TrafficManager endpoint first.

If you don't bind the custom domain to both WebApps, you will not be able to access your site after fail-over. The WebApp will refuse the traffic if the domain name is not bound.

This is what I was told and what ended up working:

1. Create Traffic Manager profiles and add both WebApps as end points. This will bind XXXX.trafficmanager.net domains to each Web App.

2. WAIT for the domains to propagate through the Azure system and show up in the "Custom Domains" menu of the WebApps.

3. Go to bind a custom domain name as usual, but make sure you select the XXXX.trafficmanager.net address as shown in the photo: