Check Azure Front Door request and transfer costs
On this page
For Front Door Standard or Premium, review the profile base fee, client request quantity, edge-to-origin transfer, and edge-to-client transfer as separate billing dimensions. Use cache behavior to explain lower origin traffic, but do not assume compression changes billable bytes.
Why this is worth a look
Each deployed profile incurs an hourly base fee, including partial hours, while endpoints within the profile do not add separate endpoint fees. Matching Host headers count as requests. A cache hit avoids the edge-to-origin component, but requests and edge-to-client transfer remain separate pricing dimensions. Rates depend on the serving edge location, and Standard and Premium have different base and request pricing.
Run this check
CHECKLISTComplete this for each Standard or Premium profile using billing records, Front Door configuration, available operational metrics, logs, and current agreement pricing.
PROFILE RESOURCE ID:
TIER: Standard | Premium
BILLING PERIOD:
DEPLOYED HOURS OR PARTIAL HOURS:
BASE FEE COST:
REQUESTS
BILLED REQUEST QUANTITY AND COST:
REQUEST EVIDENCE USED:
WAF-BLOCKED REQUESTS REVIEWED:
TRANSFER
EDGE-TO-ORIGIN BYTES AND COST:
ORIGIN-TO-EDGE FRONT DOOR COST: nonbillable
EDGE-TO-CLIENT BYTES AND COST:
EXTERNAL ORIGIN NETWORK PROVIDER REVIEWED:
CACHE
CACHE-ENABLED ROUTES:
GET TRAFFIC REVIEWED:
CACHE HIT EVIDENCE:
QUERY-STRING CACHE MODE:
AUTHENTICATED OR USER-SPECIFIC CONTENT EXCLUDED FROM CACHE:
RATE CHECK
SERVING EDGE PRICING ZONES MAPPED:
CURRENT AGREEMENT RATES USED:
CLASSIC PROFILE EXCLUDED OR REVIEWED SEPARATELY:How to confirm it
- 01
Confirm profile tier and lifetime
List each Front Door profile, its Standard or Premium tier, and deployment period. Reconcile the base fee for each deployed hour or partial hour. Do not multiply the fee by endpoint count.
- 02
Reconcile request charges
Compare the billed request quantity with the request evidence available for the same period. A request whose Host header matches the Front Door profile counts. Review WAF-blocked requests separately because Front Door charges for the request and for sending a response, without sending the request to the origin.
- 03
Separate transfer directions
Record edge-to-origin and edge-to-client quantities separately. Origin-to-Front-Door data transfer is nonbillable. Azure-origin transfer to the Front Door edge is listed as free, while an origin outside Azure might incur charges from other network providers.
- 04
Test cache assumptions
Review route cache settings, query-string behavior, and request methods. Only GET requests are cacheable, and each edge site manages its own cache. A cache hit avoids the edge-to-origin component, while the request and edge-to-client transfer remain separately priced. Do not cache authenticated or user-specific content without a reviewed privacy design.
- 05
Map rates to edge geography
Map the serving Front Door edge location to the applicable pricing zone for request and transfer review. The origin location does not set the edge-to-origin price. Use current agreement or program pricing, not illustrative documentation prices.
Before making changes
Assumes the profiles are Front Door Standard or Premium and that billing records, configuration, and operational evidence cover the same billing period. Cache evidence and origin traffic may not align one-to-one because each edge site manages its own cache. Reconcile billed request quantity against request evidence with the same scope and billing period. This workflow does not define a compression-based billing calculation. Review an external origin's provider charges separately.