Azure CDN Pricing in 2026: Tier Comparison, Setup & Cost Model

A single misconfigured Azure CDN tier can quietly bleed $800/month on a 50 TB workload — the delta between Standard Microsoft and Premium Verizon on that volume exceeds $3,500/year as of Q2 2026. Yet most teams pick a tier once during initial provisioning and never revisit. This guide gives you an updated Azure CDN pricing breakdown for every current tier, a step-by-step setup path through the portal changes Microsoft shipped in early 2026, a direct comparison against Azure Front Door pricing, and — critically — a cost-model walkthrough you can plug your own traffic numbers into before committing budget. If you run anything north of 10 TB/month through Azure's edge, this is the article to bookmark.

Azure CDN Pricing in 2026: What Each Tier Actually Costs

Microsoft still bills Azure CDN on outbound data transfer with zone-based multipliers. The table below reflects published rates as of May 2026 for Zone 1 (North America and Europe), which is where the majority of enterprise traffic lands. Asia-Pacific and South America zones carry a 20–60% premium depending on tier.

Key detail for 2026: Microsoft deprecated the Standard Akamai tier for new profile creation in late 2025. Existing profiles still operate, but if you are provisioning fresh, your realistic choices are Standard Microsoft, Standard/Premium Verizon, or migrating to Azure Front Door Standard/Premium. HTTPS delivery and Azure-managed SSL certificates remain free across all tiers. Custom-domain SSL with your own certificate carries no additional charge either.

Azure CDN vs Azure Front Door Pricing: Which One in 2026?

Microsoft has been steering teams toward Azure Front Door since 2024, and the convergence accelerated in 2026 with Front Door now absorbing CDN profile creation in the portal. The pricing model differs significantly.

Azure Front Door Standard charges a base fee of roughly $35/month per profile, plus $0.08/GB for the first 10 TB in Zone 1. Front Door Premium jumps to ~$330/month base and adds a per-request charge on top of bandwidth. You also pay per routing rule. For read-heavy, static-asset workloads under 20 TB/month, classic Azure CDN Standard Microsoft remains cheaper. Beyond 50 TB/month with advanced routing, WAF bundling, or Private Link origins, Front Door Premium can consolidate costs that would otherwise split across CDN + Application Gateway + WAF.

The decision pivots on whether you need L7 routing, session affinity, or integrated WAF. If you just need cache-and-deliver for blobs, images, or software downloads, classic CDN profiles still win on unit economics.

How to Set Up Azure CDN With Blob Storage in 2026

The portal UX changed in Q1 2026. The old "CDN" blade under Networking is now labeled "Front Door and CDN profiles" — same place, new wrapper. Here is the current path:

1. Create a CDN Profile

In Azure Portal, search "Front Door and CDN profiles" and select Create. Choose "Explore other offerings" and then "Azure CDN Standard from Microsoft (classic)." Assign it to your resource group and region. The profile itself is a logical container; there is no compute to provision.

2. Add an Endpoint

Within the profile, create a new endpoint. Assign a hostname (this becomes your-name.azureedge.net). For origin type, select "Storage" and point to your Blob Storage account's primary endpoint. If your blobs live in a specific container, append the container path in the origin path field.

3. Configure Caching Rules

Under the endpoint's caching rules, set override behavior to "Override" with a TTL that matches your content lifecycle — 7 days for static marketing assets, 1 hour for API schemas, and so on. Enable compression for MIME types like application/json, text/css, and application/javascript. Compression alone can reduce transfer costs 60–70% on text-heavy payloads.

4. Add a Custom Domain and SSL

Navigate to the endpoint's "Custom domains" blade. Create a CNAME record at your DNS provider pointing your subdomain (e.g., cdn.yourdomain.com) to the .azureedge.net hostname. Once DNS propagation completes (typically under five minutes on low-TTL records), the portal validates the mapping. Toggle on HTTPS and select "CDN managed" for a zero-touch certificate. Provisioning takes 1–6 hours as of 2026.

5. Validate and Purge

Hit your new custom domain endpoint with a curl -I and confirm you see x-cache: TCP_HIT after the initial miss. If you deploy updated assets, purge by path or wildcard from the portal or via the az cdn endpoint purge CLI command. Wildcard purges across large namespaces can take several minutes — plan accordingly in CI/CD pipelines.

How to Migrate Azure CDN to Azure Front Door

Microsoft's published migration path (updated March 2026) uses the "Migrate" button now surfaced directly in classic CDN profile blades. The wizard creates a parallel Front Door profile, replicates your endpoints as Front Door routes, and maps custom domains. You validate the new configuration, run traffic in shadow mode via Traffic Manager or DNS weighting, then cut over. Rollback is straightforward — your classic profile remains until you explicitly delete it. One critical gotcha: rules engine syntax between classic CDN and Front Door differs. Custom rules involving URL rewrite regex or request-header conditions need manual review before migration. Test them in staging.

Cost-Model Walkthrough: 75 TB/month Workload

This is the section the other top-10 results do not provide. Let's model a concrete scenario: a SaaS platform serving 75 TB/month of mixed assets (software updates, documentation images, API payloads) with 80% of traffic in Zone 1 and 20% in Asia-Pacific.

The gap is stark. At 75 TB/month, Azure CDN Standard Microsoft costs roughly 14× more than a volume-committed alternative. For teams whose workload is primarily cache-and-deliver without Azure-native L7 routing requirements, BlazingCDN's volume pricing starts at $0.004/GB and drops to $0.002/GB at 2 PB+ commitments. It delivers 100% uptime SLA, fast scaling under traffic spikes, and stability that enterprises like Sony rely on for production delivery. If your architecture doesn't require tight coupling to Azure's routing fabric, the cost advantage at scale is difficult to justify ignoring.

Optimization Checklist for Azure CDN in 2026

• Audit your cache hit ratio weekly. Anything below 85% on static assets signals misconfigured TTLs or overly aggressive query-string variation. The Azure CDN analytics blade now exposes this directly without needing Log Analytics.
• Enable origin shielding if available on your tier. Standard Verizon and Premium Verizon support it; Standard Microsoft does not. A shield node between edge and origin cuts origin load and improves cache efficiency on long-tail content.
• Use versioned URLs (asset.v3.js) instead of cache purges in CI/CD. Purges propagate asynchronously and create consistency windows where some PoPs serve stale content.
• Review per-zone pricing monthly. A surprising amount of Azure CDN spend comes from Asia-Pacific and South America zones charging 40–60% more per GB. If traffic patterns shift, consider geo-steering latency-insensitive requests through Zone 1 origins.
• Set budget alerts at the Azure Cost Management level, scoped to the CDN resource provider. Azure CDN bills purely on usage — a traffic spike from a viral event or a bot crawl can double your bill in a day.

FAQ

How much does Azure CDN cost per GB in 2026?

On the Standard Microsoft tier, the rate starts at $0.081/GB for the first 10 TB/month in Zone 1, dropping to $0.036/GB between 150–500 TB/month. Asia-Pacific and South America zones cost more. Premium Verizon nearly doubles these rates.

How do I add a custom domain to Azure CDN?

Create a CNAME record at your DNS provider pointing to your .azureedge.net endpoint hostname. In the Azure Portal, navigate to the endpoint's Custom Domains blade, add the domain, and enable HTTPS with a CDN-managed certificate. Provisioning completes within 1–6 hours as of 2026.

What is the difference between Azure CDN and Azure Front Door pricing?

Azure CDN charges purely on bandwidth with no base fee. Azure Front Door adds a monthly base fee ($35 for Standard, ~$330 for Premium) plus per-request charges on top of bandwidth. For static-asset delivery under 20 TB/month, classic CDN is cheaper. For workloads needing L7 routing, WAF, or Private Link origins, Front Door can consolidate costs.

Can I still create new Azure CDN Standard Akamai profiles?

No. Microsoft deprecated new Standard Akamai profile creation in late 2025. Existing profiles continue to function, but Microsoft recommends migrating to Standard Microsoft or Azure Front Door.

How do I migrate from Azure CDN to Azure Front Door?

Use the built-in "Migrate" button in your classic CDN profile blade (updated March 2026). It creates a parallel Front Door configuration, copies endpoints as routes, and maps custom domains. Run the new profile in shadow mode before cutting DNS. Your classic profile remains as a rollback target until you manually delete it.

Is Azure CDN free for HTTPS?

Yes. HTTPS delivery, Azure-managed SSL certificates, and custom-domain SSL using your own certificate are all included at no additional charge across every Azure CDN tier.

What to Measure This Week

Pull your Azure CDN billing data for the last three months and calculate your effective per-GB cost — total CDN spend divided by total egress. Compare it against the tier table above. If you are paying more than the published rate for your volume band, you likely have cross-zone traffic or query-string fragmentation eroding cache efficiency. Run az cdn endpoint show on each endpoint and check originPath, queryStringCachingBehavior, and isCompressionEnabled. Fix those three fields first, re-measure after 30 days, and you will have hard numbers to decide whether your current tier is right — or whether a volume-committed provider makes more sense at your scale.