Azure ExpressRoute pricing stacks four meters: the circuit (per Mbps/Gbps bandwidth, monthly), the data charge (metered per-GB outbound or unlimited), optional add-ons (Premium, FastPath, Global Reach), and the carrier or telco port at the customer end (not billed by Microsoft). The four levers that cut ER spend 25–40%: pick metered vs unlimited from observed egress baseline (the crossover is around 50–60% of circuit capacity); right-size circuit bandwidth against actual P95 not theoretical headroom; drop Premium unless multi-region/cross-tenant peering is actually required; review Global Reach links for hub-and-spoke patterns that could be replaced by VNet peering. Microsoft account teams systematically oversize ExpressRoute at deal time; the post-go-live audit consistently finds 30–40% of bandwidth and Premium tier are unused.
How ExpressRoute actually bills
Azure ExpressRoute pricing is one of the most opaque cost areas in the portfolio because the bill arrives from at least three places: Microsoft for the circuit, the carrier or provider for the port, and Microsoft again for data and add-on charges. The Microsoft-side meters:
- Circuit (port speed): monthly flat rate by speed (50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, 10 Gbps, 40 Gbps, 100 Gbps).
- Data: Metered (pay per GB outbound; inbound free) or Unlimited (flat per Mbps/Gbps add-on, no per-GB).
- Premium add-on: extra monthly charge per circuit; enables global connectivity (peering to regions outside the circuit's geopolitical region), increased route limits, and connecting to more virtual networks.
- ExpressRoute FastPath: typically included on Premium-eligible circuits at supported speeds; enables direct data-plane bypass of the gateway for higher throughput.
- Global Reach: per-Mbps/Gbps charge to interconnect ExpressRoute circuits across regions (turns Azure into your WAN backbone).
The carrier port is billed separately and varies by provider, location, and term — that piece is outside Microsoft pricing but often the second-largest line item.
Metered vs Unlimited data
The classic ExpressRoute right-sizing question. Metered bills per GB outbound at a regional rate; Unlimited bills a flat per-Mbps surcharge tied to the circuit speed and removes the per-GB meter. The crossover point depends on actual egress — rough rule: if you sustain >50–60% of circuit capacity outbound, Unlimited is cheaper; below that, Metered.
The audit lever: pull 90 days of outbound utilisation from ExpressRoute monitoring; compute average outbound TB/month; compare against the Unlimited surcharge math. We routinely find circuits on Unlimited where Metered would save 20–35%, and the reverse pattern on high-utilisation circuits where Metered overruns Unlimited by 15–25%.
Circuit bandwidth right-sizing
Most ExpressRoute circuits are sized at procurement against worst-case theoretical traffic, not observed P95. The pattern: enterprise architecture provisions 10 Gbps "for headroom"; production sustains P95 of 1.4 Gbps. The result: $X paid 24/7 for capacity that is exercised <10% of the time.
The challenge: upgrading a circuit speed mid-term is straightforward; downgrading typically requires re-provisioning. That asymmetry biases enterprises toward over-sizing — reasonable on day one, less defensible after 18–36 months of real data. The audit posture: review circuit utilisation at every MACC review window and at every EA renewal; right-size down where the data supports it.
Microsoft account teams routinely recommend Premium add-on, FastPath, and Global Reach during the initial ExpressRoute design conversation. Premium is genuinely required for some patterns (multi-region from a single circuit; high route counts) but often layered onto deployments that don't need it. Global Reach is convenient but pricey — cheaper hub-and-spoke patterns via VNet peering frequently substitute. The buyer's posture: deploy Premium and Global Reach only against a specific architectural requirement, not as a default. Audit annually.
Premium, FastPath, Global Reach
Three add-ons that compound on top of the base circuit:
- Premium: required for global connectivity from a single circuit (peering into regions outside the geo), increased VNet count, and higher route limits. Audit: is your peering pattern actually global, or could a Standard circuit per region serve cheaper?
- FastPath: data-plane bypass of the ExpressRoute gateway. Worthwhile for high-throughput VMs needing >10 Gbps; check supported SKUs and circuit speeds. Often available on Premium-eligible circuits without separate per-month charge but with feature-specific caveats.
- Global Reach: connects ExpressRoute circuits in different metro areas via the Microsoft backbone — effectively makes Azure your WAN. Bills per-Mbps/Gbps between connected circuits. Audit: is the inter-region traffic high enough to justify Global Reach over the carrier's alternative MPLS routing or a Virtual WAN hub?
ExpressRoute Direct: the higher-volume tier
ExpressRoute Direct (100 Gbps or 10 Gbps port pairs at Microsoft Enterprise Edge sites) bills as a port-pair flat fee plus per-circuit charges within the port capacity. For organisations consuming >10 Gbps aggregate ExpressRoute, ER Direct is typically more economical and offers MACsec, granular per-circuit billing, and finer control. The trade-off: provisioning complexity and the need for facilities engagement at the Microsoft Enterprise Edge.
Anonymised case study: $480K ExpressRoute reduction
A financial-services client operated five ExpressRoute circuits across three regions, all Premium, three on Unlimited, two on Metered, plus Global Reach linking all pairs. Total Microsoft-side ER spend $1.5M/year (carrier port additional). The audit found: average circuit utilisation 18% (largest circuit 26%, smallest 4%); two Premium circuits had no global-peering use case (they served single-region VNets); Global Reach had been turned on between every pair "for resilience" but only one pair actually saw inter-region traffic; the two Metered circuits were over-running budget into the Unlimited break-even zone monthly. Remediation: downsize four circuits one bandwidth tier; drop Premium on two circuits; remove four of six Global Reach links; flip the two Metered circuits to Unlimited; consolidate two circuits in the same metro into one larger circuit. Annual saving: $480K (32% of prior spend). The client now monitors all networking as a quarterly governance review.
The Microsoft Licensing Briefing — 3 minutes, every Friday
Independent analysis of Microsoft commercial moves, with implications for your EA and Azure commit. No vendor spin.
No spam. Unsubscribe any time.
Where to take this from here
ExpressRoute is one of the most over-spent line items on enterprise Azure invoices because its costs are partially obscured by the carrier relationship and partly defended by network-team conservatism. Sequence the work: circuit utilisation review first; Metered/Unlimited selection second; Premium and Global Reach audit third; ER Direct evaluation for >10 Gbps consumers fourth. Pair with Azure networking costs for the broader networking line item, Azure Firewall licensing for the security-perimeter cost, and Azure MACC explainer for the commitment that absorbs networking spend. For renewal leverage, the EA tier collapse 2026 playbook. For end-to-end support, our Azure & MACC Advisory covers ExpressRoute as part of total Azure cost discipline. Request a discovery call to benchmark.