# Azure Front Door Revisited

- URL: https://baeke.info/2019/04/09/azure-front-door-revisited/
- Author: Geert Baeke
- Published: April 9, 2019 (updated March 12, 2025)
- Topics: azure, web, cdn, http, static, web
- Outdated: It shows Azure Front Door (classic), which is being retired in favour of Front Door Standard and Premium.

A while ago, I wrote a [post](https://baeke.info/2019/01/12/azure-front-door-in-front-of-a-static-website/) about Azure Front Door. In that post, I wrote that http to https redirection was not possible. With Azure Front Door being GA, let’s take a look if that is still the case.

In the previous post, I had the following configuration in Front Door Designer:

![](https://baeke.info/_astro/2019-01-image-10.Inwbr6MT_24ODef.webp)

*Azure Front Door Designer*

The above configuration exposes a static website hosted in an Azure Storage Acccount (the backend in the backend pool). The custom domain deploy.baeke.info maps to geba.azurefd.net using a CNAME in my CloudFlare hosted domain. The routing rule **routeall** maps all requests to the backend.

The above configuration does not, however, redirect [http://deploy.baeke.info](http://deploy.baeke.info) to [https://deploy.baeke.info](https://deploy.baeke.info) which is clearly not what we want. In order to achieve that goal, the routing rules can be changed. A redirect routing rule looks as follows:

![](https://baeke.info/_astro/2019-04-image.DUqHpj07_ZRNGcF.webp)

*Redirect routing rule (Replace destination host was not required)*

The **routall** rule looks like this:

![](https://baeke.info/_astro/2019-04-image-1.DsfTVUly_21JxCk.webp)

*Routing rule*

The routing rule simply routes [https://deploy.baeke.info](https://deploy.baeke.info) to the azdeploy backend pool which only contains the single static website hosted in a storage account.

The full config looks like this:

![](https://baeke.info/_astro/2019-04-image-2.CaT-Zy4r_Z104BDQ.webp)

*Full config in Front Door designer*

Although not very useful for this static website, I also added WAF (Web Application Firewall) rules to Azure Front Door. In the Azure Portal, just search for WAF and add a policy. I added a default policy and associated it with this Azure Front Door website:

![](https://baeke.info/_astro/2019-04-image-3.DtxmmoG7_Z2n2TyP.webp)

*WAF rules associated with the Azure Front Door frontend*

If required, you can enable/disable WAF rules:

![](https://baeke.info/_astro/2019-04-image-4.C151VSsA_Zjgv42.webp)