Azure Front Door Pricing Guide UK 2026

The Premium Downgrade Trap

The part engineers usually miss is not request pricing. It is the product decision they only discover after a billing review: Azure Front Door Premium cannot be downgraded to Standard in place. If you choose Premium for a pilot, then later decide you only need Standard, the path back is a new profile and a manual migration.

That matters because Front Door tends to be deployed early in internet-facing architectures and then left alone. A small initial decision can become sticky operational debt: routes, WAF policies, certificates, and DNS cutover all have to be revalidated when you migrate later.

What Actually Drives Cost

Front Door pricing looks simple at first, but four separate dimensions usually show up in real architectures:

• Base profile fee: a standing cost for the selected tier
• Requests: charged by request volume, which matters for chatty web apps and API-heavy traffic
• Outbound transfer: edge-to-user traffic, which can exceed the request line item for media-heavy sites
• Security features: WAF and DDoS assumptions, which can dominate low-traffic environments

The hidden optimisation is often architectural: reducing outbound bytes, collapsing unnecessary rules, and choosing the lowest tier that matches your actual feature set beats obsessing over tiny per-request differences.

Classic vs Standard vs Premium

Classic is a retirement problem. If you still run it, the comparison you need is not "what does Classic cost?" but "what is the least painful migration target?"

Standard is usually the right baseline when you need modern Front Door capabilities without paying for Premium-only security posture. Premium earns its keep when the advanced security and edge features are truly used — not just enabled.

In practical terms, Standard is the default recommendation for teams that want modern Front Door without creating future migration friction.

WAF and DDoS Assumptions

Security pricing is where teams start mixing unrelated controls. Front Door WAF, Front Door's built-in platform protections, and Azure DDoS Protection are not interchangeable cost buckets. This guide treats them separately on purpose.

The calculator's first-pass model is designed for estimation, not invoice reconstruction. It is most useful for comparing tiers and for surfacing how easily security add-ons can distort a "cheap CDN" assumption.

Front Door Calculator

Use the calculator below to compare Classic, Standard, and Premium using the same request, transfer, WAF, and DDoS inputs. The warning state is intentional: this is a migration decision tool as much as a pricing tool.