As you know Azure Front Door Service (AFD) is the solution to define, manage, and monitor the global routing for your web traffic by optimizing for best performance and instant global failover for high availability.
Well, AFD is now allowing you to define specific rules to manage various sets of conditions and actions to redirect HTTP request to HTTPS, direct requests to either desktop or mobile experience, implement HTTP security header (the famous HTTP Strict-Transport-Security (HSTS), X-XSS-Protection, Content-Security-Policy, X-Frame-Options or Access-Control-Allow-Origin) and more.
In a nutshell, you can view it as the IIS URL Rewrite component available for IIS servers on-premises.
The Rule Engine for AFD is currently in preview and available for all existing and new Front Door service.
You can define your rules after you have created your Front Door.
To start implementing it, logon to your Azure portal (https://portal.azure.com/) and go to the Front Door service you want to configure
There access the Rule engine configuration blade to create (and later manage) your rules
Rule configuration is simple as you define the condition(s) and action(s) associated with