Azure Front Door to Windows Server some IIS help.

[khushiee]

Right now, I have an Azure Front Door going to a Windows Server that has a sub folder that is called "AppServer" and then you have to type Windowsserver.com/AppServer/home before it routes properly.  What do you suggest for IIS that I can have windowsserver.com be routed to windowsserver.com/appserver/home instead of having to type it?

[adrynalyne]

On 26/10/2025 at 12:42, khushiee said:

Right now, I have an Azure Front Door going to a Windows Server that has a sub folder that is called "AppServer" and then you have to type Windowsserver.com/AppServer/home before it routes properly.  What do you suggest for IIS that I can have windowsserver.com be routed to windowsserver.com/appserver/home instead of having to type it?

IIS rewrite rules. 

[neufuse Veteran]

Yes IIS rewrite rules works...

but who made this app? if you wrote it yourself and it's like ASP.NET Core or kesterl hosted in IIS or something else there are much better ways to do it

[davidmubarak]

When using Azure Front Door with a Windows Server running IIS, make sure your backend is correctly configured to handle requests forwarded from Front Door. First, ensure the backend pool in Azure Front Door points to your IIS server’s public endpoint or Azure-hosted IP with a valid DNS name. Then, in IIS, enable HTTPS and install a valid SSL certificate if Front Door communicates over TLS. Also, check that your firewall allows inbound traffic from Azure Front Door’s IP ranges.

If you’re using URL rewrites or redirects, verify that they return the correct host headers — Front Door forwards the original host by default, so make sure IIS is configured to accept it (you can adjust the binding settings to “All Unassigned” or add the exact hostname).

Lastly, confirm that health probes from Front Door aren’t being blocked and are mapped to a simple /health or /ping endpoint. Once those are in place, your Windows Server with IIS should work smoothly behind Azure Front Door.