Skip to main content
In this article we explain ExpressRoute SKUs: what they control, why they matter, and how to pick the right SKU for your hybrid network. You’ll learn the difference between connection models, the Local/Standard/Premium circuit SKUs, and how circuit SKUs differ from gateway SKUs. An ExpressRoute circuit is a dedicated private connection between your on-premises network and Microsoft Azure. It bypasses the public internet to provide more secure, consistent, and predictable connectivity. When you create a circuit you provision connectivity between your edge routers and Microsoft’s edge infrastructure. Connection models (how you physically connect to Microsoft)
  • Provider model: You use a Microsoft-approved connectivity provider (an exchange or network service provider). The provider provisions the physical link between your location and Microsoft’s network and typically handles port provisioning and support.
  • ExpressRoute Direct: You connect directly to Microsoft edge locations (commonly from a colocation facility). This model is used when you need very high bandwidth (for example, 10 Gbps or 100 Gbps ports) or more operational control.
If you use the provider model, select a partner from Microsoft’s list of approved partners and they will provision the physical connectivity. With ExpressRoute Direct, you are effectively your own provider and connect straight into Microsoft’s edge.
A screenshot of an Azure ExpressRoute SKUs configuration page showing form fields for port type, provider/import, SKU (Local/Standard/Premium), billing model, and classic operations. A highlighted "Local" info panel notes it provides free egress data for 1–2 Azure regions in the same metro area.
ExpressRoute circuit SKUs ExpressRoute circuit SKUs define the circuit’s reach, route limits, and the number of VNets you can peer with. Choose the SKU that matches your geographic reach and scale requirements.
  • Local
    • Reach: Single metropolitan area (same metro).
    • Use case: Connect to Azure regions reachable from the same metro; ideal for local/metro deployments.
    • Notes: Often provides free egress for 1–2 nearby Azure regions depending on the metro configuration. Best when multi-region or global reach is not required.
A screenshot of an Azure ExpressRoute SKUs configuration panel showing form options (Port type, Create new/import, Provider, SKU, Billing model) with the "Standard" SKU selected. A blue "Standard" banner on the right notes it "Grants access to all Azure regions in a geopolitical zone."
  • Standard
    • Reach: All Azure regions within a single geopolitical boundary (for example, all of Europe or all of North America).
    • Use case: Most enterprise scenarios where workloads are spread across multiple regions inside the same geopolitical area.
    • Notes: Standard is the most commonly used SKU for cross-region connectivity within a geopolitical zone.
A screenshot of an ExpressRoute SKUs configuration panel showing options such as Port type, Create new/import, Provider, SKU (Local/Standard/Premium) and Billing model with radio buttons. A blue "Premium" banner on the right notes support for over 4K routes and 10+ VNETs.
  • Premium
    • Reach: Global — access to all Azure regions worldwide.
    • Use case: Large, multi-continent enterprises and complex hybrid architectures that require global connectivity.
    • Notes: Increases route and VNet limits (supports thousands of routes and many more VNet connections). Choose Premium when you need global reach and higher scale.
Billing model ExpressRoute circuits have billing model options such as metered or unlimited data transfer. Billing specifics and pricing are outside the scope of this article; consult the ExpressRoute pricing page for current details.
Remember: Local, Standard, and Premium are circuit SKUs that control reach and scale for the circuit itself — not the Azure gateway.
Circuit SKUs vs Gateway SKUs It’s important to distinguish circuit SKUs from gateway SKUs:
  • ExpressRoute circuit SKU (Local/Standard/Premium): Determines geographic reach, route limits, and how many VNets you can connect through the circuit.
  • Gateway SKU: The virtual network gateway deployed in Azure that connects one or more VNets to the ExpressRoute circuit. Gateway SKUs determine throughput, encryption, and gateway-specific performance limits. Choose gateway SKUs independently based on throughput, SLA, and features needed in Azure.
Do not confuse ExpressRoute circuit SKUs with gateway SKUs. Circuits provide private connectivity to Microsoft; gateways are Azure resources that attach VNets to that circuit and have separate capacities and costs.
Quick comparison table
SKUGeographic reachTypical use caseScale characteristics
LocalSingle metroLocal/metro deployments with nearby Azure regionsLower route/VNet limits; often free egress to local regions
StandardSingle geopolitical regionEnterprise multi-region deployments within a geopolitical areaAccess to all regions in that geo; moderate route/VNet limits
PremiumGlobalLarge, multi-continent hybrid networksGlobal reach; higher route and VNet limits (thousands of routes)
Planning checklist
  • Decide your connection model first: Provider vs ExpressRoute Direct.
  • Choose the circuit SKU based on geographic reach and scale (Local, Standard, Premium).
  • Select gateway SKU(s) separately to meet throughput, redundancy, and encryption requirements.
  • Review billing model options (metered vs unlimited) and factor cost into design.
Useful references Summary Selecting the right ExpressRoute SKU is a foundational decision for hybrid network architecture. Match the circuit SKU to your geographic needs and scale, and then provision gateway SKUs within Azure to satisfy throughput and feature requirements. This separation of concerns simplifies planning, cost estimation, and long-term network growth.

Watch Video