Introduction to ExpressRoute Circuits

An Azure ExpressRoute circuit provides a private, high-throughput, and low-latency connection between your on-premises network or co-location environment and Azure. It bypasses the public internet, offering enhanced reliability, speed, and security.

This section covers the essential aspects of managing your ExpressRoute circuits, from creation to configuration and ongoing maintenance. Understanding these concepts is crucial for building a robust hybrid cloud network.

Creating ExpressRoute Circuits

Creating an ExpressRoute circuit involves a few key steps. You'll need to choose a peering provider and a location that supports ExpressRoute. The process typically involves:

  • Selecting a Provider: Choose from a list of ExpressRoute partners and co-location facilities.
  • Ordering the Circuit: Work with your chosen provider to order the physical connectivity.
  • Configuring in Azure: Once your physical circuit is provisioned, you'll create a corresponding ExpressRoute circuit resource in Azure.

You can create circuits using the Azure portal, Azure CLI, or PowerShell.

Azure CLI Example:


az network express-route create --resource-group MyResourceGroup --name MyExpressRouteCircuit --provider PeeringProvider --peering-location "New York" --bandwidth 500

Key Considerations:

  • Peering Location: Must match the physical location of your connectivity.
  • Bandwidth: Choose a bandwidth that meets your current and future needs.
  • Provider: Ensure your chosen provider has a Point of Presence (PoP) at your desired location.

Circuit Peering Configuration

Once a circuit is created, you need to configure peering. ExpressRoute supports different peering types:

  • Azure Public Peering: Allows access to public Azure services (e.g., Storage, SQL Database).
  • Azure Private Peering: Allows access to your Azure Virtual Network resources.
  • Microsoft Peering: Allows access to Microsoft 365 services (e.g., Exchange Online, SharePoint Online).

Each peering configuration requires specific routing information, including BGP peering addresses and ASN (Autonomous System Number).

Important: Azure Private Peering is required to connect to your Virtual Network resources.

Example Peering Configuration (Azure Private):

You'll configure IP addresses for the primary and secondary links, along with BGP information.


# Example using Azure PowerShell
New-AzExpressRouteCircuitPeeringConfig `
    -Name "AzurePrivatePeering" `
    -CircuitName "MyExpressRouteCircuit" `
    -ResourceGroupName "MyResourceGroup" `
    -PeeringType "AzurePrivatePeering" `
    -PeerASN 65000 `
    -PrimaryPeerAddressPrefix "10.0.0.0/30" `
    -SecondaryPeerAddressPrefix "10.0.0.4/30" `
    -VlanId 200

Managing Existing ExpressRoute Circuits

After creation, you can monitor, update, or delete your ExpressRoute circuits.

  • Monitoring: Track circuit status, bandwidth utilization, and connectivity health via the Azure portal or Azure Monitor.
  • Updating Bandwidth: You can increase the bandwidth of an existing circuit without downtime. Decreasing bandwidth might require circuit recreation.
  • Adding/Modifying Peering: Configure new peering types or modify existing peering settings as needed.
  • Circuit Keys: ExpressRoute circuits have keys that are required by your connectivity provider.
  • Deletion: To delete a circuit, you must first deprovision it with your connectivity provider.

Common Management Tasks:

  • Viewing circuit status and bandwidth.
  • Modifying bandwidth.
  • Resetting BGP sessions.
  • Managing circuit keys.

ExpressRoute Bandwidth Options

ExpressRoute circuits are available in various bandwidths, from 50 Mbps to 10 Gbps. The available options may vary by provider and location.

Choosing the right bandwidth is critical for performance. Consider your current network traffic and projected growth.

  • Standard: Up to 1 Gbps.
  • Premium: Up to 10 Gbps, with additional features like global reach.

You can upgrade your bandwidth through the Azure portal. The change is typically effective within minutes.

ExpressRoute Circuit Pricing

ExpressRoute pricing is based on several factors:

  • Circuit Provisioning Fee: A monthly fee for the circuit itself.
  • Data Transfer Fees: Charges for data egress from Azure. Data ingress is generally free.
  • Port Speed: Higher bandwidth ports have higher fees.
  • SKU (Standard/Premium): Premium circuits have higher fees but offer more capabilities.

For detailed pricing information, refer to the official Azure ExpressRoute pricing page.