Azure CDN Cost Calculator

Price Azure CDN or Front Door egress and requests, and value the origin bandwidth your cache hit ratio saves.

Inputs

Data delivered to clientsTB/month

CDN egress price per GBUSD

Cache hit ratio%

Origin egress price per GBUSD

What the same byte would cost leaving Azure directly.

Requestsmillions/month

Price per 10,000 requestsUSD

Profile base feeUSD/month

Front Door Standard lists near $35; Premium is substantially higher.

Monthly Cost

$2,286.42

CDN Egress Charge

$1,658.88

Origin Fetch Charge

$142.54

Request Charge

$450.00

Traffic Still Reaching the Origin

1,638GB

Saving vs Serving Everything from the Origin

$0.00

Blended Cost per Delivered GB

0.1116USD/GB

Step by step

Values used
Data delivered to clients = 20 TB/month; CDN egress price per GB = 0.0810 USD; Cache hit ratio = 92 %; Origin egress price per GB = 0.0870 USD; Requests = 500 millions/month; Price per 10,000 requests = 0.0090 USD; Profile base fee = 35 USD/month
Azure CDN Cost
origin traffic = delivered GB × (1 − cache hit ratio); monthly = delivered GB × CDN price + origin GB × origin egress price + requests ÷ 10,000 × request price + base fee.
Monthly Cost
= 2,286.42
CDN Egress Charge
= 1,658.88
Origin Fetch Charge
= 142.54
Request Charge
= 450.00
Traffic Still Reaching the Origin
= 1,638 GB
Saving vs Serving Everything from the Origin
= 0.00

How it works

A CDN replaces expensive origin egress with cheaper edge egress, but only for the fraction it can cache — every miss pays both the CDN rate and the origin egress rate for the same byte. That makes the cache hit ratio the single most important input: at 92% the double-charged share is small, at 50% the CDN can cost more than serving directly. Cache-control headers and query-string handling are what actually move the hit ratio, so tuning them is a cost lever rather than a performance nicety; CDN egress is priced by geographic zone and volume band, so confirm the rates for the regions your users are in with the Azure pricing calculator.

Formula

Azure CDN Cost

origin traffic = delivered GB × (1 − cache hit ratio); monthly = delivered GB × CDN price + origin GB × origin egress price + requests ÷ 10,000 × request price + base fee.

cache hit ratio: Share of requests served from the edge without touching the origin
origin fetch: Egress the origin still pays for every cache miss
blended per GB: Total divided by delivered bytes, the number to compare against direct egress

Frequently Asked Questions

How is Azure CDN Cost calculated?

origin traffic = delivered GB × (1 − cache hit ratio); monthly = delivered GB × CDN price + origin GB × origin egress price + requests ÷ 10,000 × request price + base fee. A CDN replaces expensive origin egress with cheaper edge egress, but only for the fraction it can cache — every miss pays both the CDN rate and the origin egress rate for the same byte. That makes the cache hit ratio the single most important input: at 92% the double-charged share is small, at 50% the CDN can cost more than serving directly.

Why does Azure CDN Cost matter?

Cache-control headers and query-string handling are what actually move the hit ratio, so tuning them is a cost lever rather than a performance nicety; CDN egress is priced by geographic zone and volume band, so confirm the rates for the regions your users are in with the Azure pricing calculator.

What values do I need to enter?

This calculator takes 7 inputs: Data delivered to clients, CDN egress price per GB, Cache hit ratio, Origin egress price per GB, Requests, Price per 10,000 requests, Profile base fee. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

You might also need

Azure Network Cost Calculator Azure Blob Storage Calculator Azure DNS Calculator