Review Azure inter-region data transfer costs
On this page
This check is due for a source refresh. Confirm the current documentation before you rely on provider-specific details.
Mispricing transfer can hide peering or service charges, so verify billing coverage and match every material flow to its billed meter before applying a per-GB rate. Check both endpoints and the service path because peering can charge at both ends, while Front Door applies direction-specific rules.
What you need first
- Tool
- Use your Azure bill or invoice, which records billed charges, and a plain-text copy of the register below. Start with one completed billing period and the relevant subscriptions. No terminal is needed.
- Access
- Ask an authorized Azure billing colleague to provide read-only billing results for the subscriptions and period you select, including meter labels, quantities, units and charges where available.
- If you do not use that tool
- Give your billing colleague the subscription list and completed billing period. Request confirmation of the included subscriptions and services, plus the relevant transfer and service meter lines. Ask the network or service owner to identify each flow's endpoints, regions, direction and connection type.
Why this is worth a look
Using one bandwidth rate can miss peering charges or assign a charge to exempt traffic. Azure treats bandwidth, peering, ExpressRoute and content delivery as separate pricing paths. Peering charges inbound and outbound traffic at both ends, gateway transit can charge the spoke network, and Front Door's direction determines which transfer meter applies.
Run this check
CHECKLISTComplete these read-only steps in a text file using billing records supplied by an authorized colleague and path details from service owners. Verify scope before estimating and retain each meter's own usage unit.
TRANSFER PATH AND BILLING REGISTER
[ ] Set the completed billing period: __________________
[ ] List included subscriptions and services: __________________
[ ] Ask the billing colleague to confirm that these records cover the listed subscriptions, services and period.
[ ] If coverage cannot be confirmed, label the estimate INCOMPLETE and state the missing scope.
REPEAT FOR EACH MATERIAL FLOW
[ ] Record owner and purpose: __________________
[ ] Record source service/resource and region: __________________
[ ] Record destination service/resource and region: __________________
[ ] Record direction: __________________
[ ] Confirm path with the owner:
general bandwidth | local virtual network peering |
global virtual network peering | gateway transit |
ExpressRoute | Front Door | other/unknown
REPEAT FOR EACH RELATED BILLING COMPONENT
[ ] Copy the billed meter label: __________________
[ ] Copy usage quantity and exact unit: __________________
[ ] Copy charge and currency: __________________
[ ] Record the applicable rate if available: __________________
[ ] Match the line to a path, direction and endpoint: __________________
If the match is uncertain, mark UNKNOWN rather than assigning a rate.
CHECK BEFORE ESTIMATING
[ ] General bandwidth: use the applicable inter-region per-GB pricing,
not a universal rate for every service or connection type.
[ ] Peering: account for inbound and outbound charges at both ends.
For global peering, check each endpoint's pricing zone.
[ ] Gateway transit: check peering charges on the spoke network.
[ ] Front Door Standard/Premium: distinguish edge-to-origin traffic
from origin-to-Front Door traffic. Do not assign an Azure origin
egress charge to traffic sent to Front Door.
[ ] Blob Storage: review its separate meter lines rather than treating
the whole service charge as network transfer.
[ ] Keep usage units and billing periods consistent before comparison.
[ ] Record unmatched lines and a follow-up owner: __________________
[ ] Mark estimate ready only when coverage of the selected subscriptions,
services and completed billing period is verified and all material
components are matched.How to confirm it
- 01
Choose one completed period
Request billing records for the subscriptions and services involved in the flows you want to review. Keep the review read-only and use the same completed billing period throughout.
- 02
Confirm the actual path
Ask the network or service owner to fill in both endpoints, regions, direction and connection type. Mark unknown paths for follow-up rather than assuming all cross-region traffic uses general bandwidth pricing.
- 03
Verify scope and match components
Ask the billing colleague to confirm that the records cover every selected subscription, service and the completed period. Copy meter labels, usage quantities, units and charges into the register. For peering, check both ends; for gateway transit, check the spoke network. Use the endpoint pricing zones for global peering. Do not confuse those billing zones with Availability Zones.
- 04
Resolve service exceptions
Check Front Door Standard or Premium traffic by direction: edge-to-origin transfer bills per GB, but Front Door does not bill origin-to-Front Door traffic, and Azure origins have no egress charge for that path. Origin request processing can still cost money. Review Blob Storage's separate meter lines without assuming every line is transfer. Leave unmatched components or unverified coverage out of a finalized estimate, label it incomplete, and state the missing scope.
Before making changes
Verify, rather than assume, that the records cover every selected subscription, service and completed billing period. If coverage cannot be confirmed, label the estimate incomplete and state the missing scope. Keep each meter's unit intact; do not assume a GB label always means the same measurement across services. Azure public prices are estimates, and actual pricing can vary by agreement, purchase date and currency exchange rate.