Evaluate Azure VNet peering costs for multi-region architectures. Choose an analysis mode to get started.
Simulate Azure VNet peering cost for a target multi-region architecture without importing Azure usage data.
Upload Azure Cost Management billing export files to analyze actual network-related costs.
Upload exported network traffic data to estimate peering cost from observed traffic flows.
This mode requires Azure Cost Management + Billing exports. Data is not real-time and depends on your billing access scope.
The usage details export contains all billed line items including network-related meters. This is required to analyse actual VNet peering cost.
The price sheet can help understand negotiated prices or meter-level pricing specific to your agreement. Not required for basic analysis.
This mode analyses traffic volumes, not direct billed cost. Uploaded traffic data will be mapped to public Azure pricing to estimate peering cost. Useful for identifying high-volume inter-region traffic.
Prepare or export a CSV file containing inter-region traffic data. Two formats are supported:
Columns: source_region, target_region,
traffic_gb, and optionally direction.
Exported from Azure Traffic Analytics with region-level aggregation.
If your traffic data uses custom region identifiers, you can provide
a mapping to standard Azure region names. Not needed if standard
armRegionName values are used.
Configure traffic parameters to estimate VNet peering cost between two Azure regions.
| Direction | Traffic | Outbound | Inbound | Subtotal |
|---|
Upload your Azure billing export to analyse actual network-related costs.
| Category | Meter | Region | Usage | Cost |
|---|
| Region | Network cost | Peering cost | Meters |
|---|
Upload your traffic summary CSV to estimate peering cost from observed inter-region flows.
| Source | Target | Traffic (GB) | Rate ($/GB) | Est. cost |
|---|