Review Azure inter-region data transfer costs
On this page
Classify each material transfer by source, destination, service, and connection type before applying a rate. Start with billed usage and billing meters, then verify whether the path uses bandwidth, local or global virtual network peering, replication, a gateway, or a service-specific exception.
Why this is worth a look
A region boundary does not create one universal Azure charge. Azure distinguishes general bandwidth from transfers covered by peering, ExpressRoute, or content delivery. Virtual network peering charges ingress and egress, gateway transit can add peering charges on the spoke side, and services such as Blob Storage and Front Door have their own documented billing behavior.
Run this check
CHECKLISTUse this read-only register with an authorized Azure Cost Management view or export to document recurring flows and reconcile usage to billing components.
INTER-REGION TRANSFER PATH REGISTER
Review period: completed billing period __________________
Billing scope: subscriptions, services, and regions included __________________
FLOW
Flow name and owner: __________________
Source service and resource: __________________
Source region: __________________
Destination service and resource: __________________
Destination region: __________________
Connection or service path: public | local VNet peering | global VNet peering | VPN | ExpressRoute | gateway transit | service replication | Front Door | other
Direction: __________________
Expected monthly volume: ______ bytes or ______ GB
Operational reason for the cross-region path: __________________
BILLING RECONCILIATION
Billing line or meter label: __________________
Usage quantity: ______
Usage unit: __________________
Price or rate shown: __________________
Charge and currency: __________________
Related service-processing or replication charge: __________________
Ingress charge: yes | no | service-specific | unknown
Egress charge: yes | no | service-specific | unknown
Path and billing component matched: yes | no
Pricing exception reviewed: yes | no
Unmatched item or follow-up owner: __________________How to confirm it
- 01
Set the review scope
Use an authorized Azure Cost Management view or export for a completed billing period. Record the subscriptions, services, regions, and usage units included, and keep expected flow volume in bytes or GB separate from billed charges.
- 02
Inventory recurring flows
List replication, application calls, backups, data copies, hub-and-spoke transit, and user delivery separately. Record both endpoints, regions, connection type, direction, and the operational reason for crossing the region boundary.
- 03
Read the billed usage
For each material line, record the billing line or meter label, usage quantity, unit, displayed price or rate, charge, and currency. Use the billing view or export's own labels instead of assuming a universal Cost Details schema.
- 04
Match the network path
Determine whether the flow used general bandwidth, public transfer, local or global virtual network peering, VPN, ExpressRoute, gateway transit, or a managed service path. Peering keeps traffic on Microsoft's private backbone, while Azure documents ingress and egress charges for peering. Gateway transit can charge traffic to the gateway on the spoke side.
- 05
Check exceptions and reconcile
Review the relevant service pricing behavior before assigning a rate. Blob Storage documents data transfer for geo-redundant storage and network bandwidth fees for cross-region replication. Front Door Standard and Premium do not bill origin-to-Front Door traffic, including across regions, but do bill their documented request and data-transfer components. Match each charge to one path and billing component, and keep unmatched lines for investigation.
Before making changes
Assume the reviewed billing scope includes every relevant subscription and service, the period is complete, and expected volumes use a consistent bytes or GB unit before comparison. Azure public prices are estimates and actual pricing can vary by agreement, purchase date, and currency exchange rate. Same-availability-zone transfer and inter-region transfer are separate billing cases, and documented service exceptions can change the expected component.