ExpressRoute Circuit Configuration
You'll learn how to provision and configure an ExpressRoute circuit with your service provider to establish dedicated private connectivity to Azure.
What Is an ExpressRoute Circuit?
An ExpressRoute circuit is the logical connection object representing your dedicated, private link between your on-premises network and Microsoft Azure. Think of it as reserving a lane on a private highway—you're not building the road yourself, but you're configuring your access to it through a connectivity partner.
The Provisioning Process
Step 1: Create the Circuit
You define your circuit in Azure, specifying bandwidth (50 Mbps to 100 Gbps), peering location (e.g., "Silicon Valley"), and SKU tier (Standard or Premium for global connectivity).
Step 2: Service Provider Coordination
Azure generates a unique Service Key—a GUID that identifies your circuit. You provide this key to your connectivity provider (Equinix, AT&T, Verizon, etc.), who provisions the physical connection on their side.
Step 3: Provider State Verification
The circuit moves through states: NotProvisioned → Provisioning → Provisioned. You monitor this in Azure Portal until your provider confirms completion.
Step 4: Configure Peerings
Once provisioned, you configure one or more peerings (private, Microsoft, or both) with BGP settings, VLAN IDs, and peer ASNs—this is where routing begins.
Key Configuration Elements
- Bandwidth: Cannot be changed easily; requires new circuit
- SKU: Standard (regional) vs Premium (global reach)
- Billing Model: Metered or unlimited data plans
- Service Key: The critical handoff point between you and your provider
Key Takeaway: ExpressRoute circuit configuration is a coordinated process between Azure and your service provider, centered around the service key exchange and culminating in BGP peering setup—proper sequencing ensures smooth private connectivity activation.