Last updated: June 2026
To cut Azure Front Door and CDN costs, migrate classic CDN to Front Door Standard or Premium, choose Standard unless you need the Premium-only WAF and bot protection, raise the cache hit ratio so more requests are served from the edge, and consolidate sites behind one profile. The largest single saving is usually improving cache efficiency, because every cached response avoids origin egress and billed data transfer.
- Front Door Standard and Premium bill a monthly base fee plus data transfer, requests, and rules.
- Premium adds the managed WAF, bot protection, and private link at a higher base fee.
- Classic Azure CDN is retiring; migrate to Front Door Standard or Premium.
- A higher cache hit ratio is the largest lever on data transfer cost.
Azure Front Door is a global edge platform that combines content delivery, caching, TLS termination, and optional web application firewall in front of your origins. Cutting its cost means choosing the tier that matches your real feature needs, serving as many requests as possible from the edge cache, and consolidating profiles rather than running one per site. This article is part of our Azure cluster; the pillar it links up to is the complete guide to Azure cost optimization. Tier selection and cache tuning are Cut steps in our See, Cut, Lock, Run method.
How is Azure Front Door priced?
Azure Front Door Standard and Premium bill a monthly base fee plus charges for outbound data transfer, the number of requests, and routing rules, with Premium adding the managed web application firewall, bot protection, and private link at a higher base fee. As of June 2026, per the Azure Front Door pricing page, data transfer and request volume scale with traffic while the base fee is fixed per profile. Because egress is driven by how much traffic reaches the origin, the cache hit ratio is the single largest lever, followed by the tier choice. Verify the current figures on the linked Azure page before acting, because edge pricing changes.
| Cost component | What drives it | Main lever |
|---|---|---|
| Base fee per profile | Tier (Standard or Premium), profile count | Use Standard, consolidate profiles |
| Data transfer (egress) | Traffic served, cache hit ratio | Raise cache hit ratio, compress assets |
| Requests and rules | Request volume, rule set count | Trim unused rules and endpoints |
| Premium security | Managed WAF, bot protection, private link | Scope Premium to apps that need it |
What happened to Azure CDN?
Azure CDN Standard from Microsoft (classic) is being retired, and Front Door is now the primary edge service. Per the Azure CDN classic retirement FAQ, the classic service stopped accepting new profile creation in August 2025 and is scheduled for full retirement on September 30, 2027, with Microsoft directing customers to migrate to Azure Front Door Standard or Premium. If you still run a classic CDN profile, plan the migration well before the retirement date and treat it as an opportunity to pick the Front Door tier that matches your real needs rather than carrying forward an oversized configuration. Verify the current timeline in the linked Azure documentation, because retirement dates can move.
How do you cut Azure edge costs, step by step?
These five steps modernize the profile, match the tier, and raise cache efficiency.
- Migrate off classic CDN to Front DoorMove any classic CDN profile to Front Door Standard or Premium, since classic CDN is retiring, and pick the tier that matches real needs. The result is a supported service sized correctly from the start.
- Choose Standard over Premium where you canUse Front Door Standard unless you need the Premium-only WAF, bot protection, or private link. The result is the higher Premium base fee avoided where it adds nothing.
- Raise the cache hit ratioTune caching rules, cache keys, and time-to-live so more requests are served from the edge. The result is less origin egress and lower billed data transfer.
- Consolidate profiles and endpointsServe multiple domains and routes through one profile rather than one per site. The result is one base fee instead of many.
- Trim routing rules and unused endpointsRemove rule sets, routes, and endpoints that no longer serve live traffic and delete idle profiles. The result is the fixed-fee waste eliminated.
Paying Premium edge fees with a low cache hit ratio?
Our Azure cost audit migrates classic CDN to the right Front Door tier, raises the cache hit ratio to cut origin egress, consolidates profiles, and trims unused rules and endpoints. On the performance model you pay only from realized savings. No savings, no fee.
Book an Azure cost audit →Should I use Front Door Standard or Premium?
Use Front Door Standard unless you need the Premium-only features: the managed web application firewall with managed rule sets, bot protection, or private link to origins. Premium carries a higher base fee, so the common mistake is selecting it for the reassurance of "more security" on applications that face no untrusted traffic and use none of the managed rules. Scope Premium to internet-facing applications that genuinely benefit from its managed protection, and keep simpler delivery on Standard. The same tier-matching discipline applies to the gateways behind the edge, covered in our guide to optimizing Azure Application Gateway and Load Balancer costs.
Tier names, billing components, and the classic CDN retirement timeline reflect Azure as of June 2026. Verify current pricing and dates on the linked Azure documentation before acting, because edge service packaging and rates change.
The Azure Cost Optimization Field Guide includes the cache hit ratio worksheet and the Front Door tier selection checklist we apply on engagements. It is the downloadable companion to this article.
Frequently asked questions
How is Azure Front Door priced?
Azure Front Door Standard and Premium bill a monthly base fee plus charges for outbound data transfer, the number of requests, and routing rules, with the Premium tier adding the managed web application firewall, bot protection, and private link at a higher base fee. Data transfer and request volume scale with traffic, while the base fee is fixed per profile. Raising the cache hit ratio and choosing the right tier are the main cost levers. Verify current rates on the Azure Front Door pricing page.
What happened to Azure CDN?
Azure CDN Standard from Microsoft (classic) is being retired, with the classic service no longer accepting new profile creation since August 2025 and full retirement scheduled for September 30, 2027. Microsoft directs customers to migrate to Azure Front Door Standard or Premium, which is now the primary content delivery and edge service. Plan the migration before the retirement date and choose the Front Door tier that matches your real feature needs. Verify the current timeline in the Azure documentation.
How do I lower Front Door data transfer cost?
Lower data transfer cost by raising the cache hit ratio so more requests are served from the edge instead of the origin, tuning cache keys and time-to-live, and compressing cacheable content. Every request served from cache avoids an origin pull and reduces billed egress, so cache efficiency is the largest lever on a content-heavy workload. Caching static assets aggressively and keeping dynamic, uncacheable responses minimal is where most of the saving comes from.
Should I use Front Door Standard or Premium?
Use Front Door Standard unless you need the Premium-only features: the managed web application firewall with managed rule sets, bot protection, or private link to origins. Premium carries a higher base fee, so applying it where Standard would do inflates cost. Scope Premium to internet-facing applications that benefit from its managed security features and keep simpler delivery on Standard.
The short version
Azure edge savings come from migrating classic CDN to the right Front Door tier, choosing Standard over Premium where you can, raising the cache hit ratio to cut origin egress, and consolidating profiles. When you want your Front Door estate right-sized and the cache efficiency tuned, that is exactly what our Azure cost optimization service delivers.
Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: Azure pricing ↗, Azure documentation ↗ and FinOps Foundation Framework ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.