Azure ExpressRoute Global Reach

Connect your on-premises networks and Azure virtual networks across different Azure regions.

What is Azure ExpressRoute Global Reach?

Azure ExpressRoute Global Reach extends the benefits of ExpressRoute connectivity from your on-premises network to the Azure backbone network. This allows you to extend your on-premises network to your Azure virtual networks, and vice-versa, across different Azure regions. It's an ideal solution for scenarios where you need to connect your geographically dispersed on-premises datacenters to your Azure environments.

Key Benefits:

How it Works

ExpressRoute Global Reach works by enabling your circuits to exchange traffic between your on-premises network and your Azure virtual networks. When you enable Global Reach, your on-premises routers that are connected to ExpressRoute circuits in different locations can communicate directly with each other over the Azure backbone network.

The core components involved are:

Configuration Steps:

  1. Ensure you have ExpressRoute circuits established for each on-premises location you want to connect.
  2. Configure your on-premises routers to advertise the address prefixes for your local networks and to accept routes for remote networks.
  3. Create or configure ExpressRoute gateways in your Azure virtual networks in the respective regions.
  4. Establish connections between your on-premises network and your Azure virtual networks using ExpressRoute.
  5. Enable ExpressRoute Global Reach on your ExpressRoute circuits and peerings.
  6. Configure routing to allow traffic to flow between your on-premises networks and Azure virtual networks across regions.
Important: ExpressRoute Global Reach requires a Microsoft peering or a private peering configuration. Service providers may have specific requirements or additional configuration steps.

Use Cases

Technical Considerations

IP Addressing

Ensure that your on-premises IP address spaces and Azure virtual network address spaces do not overlap. Global Reach relies on the Azure backbone to route traffic between these distinct address spaces.

Border Gateway Protocol (BGP)

BGP is used to exchange routing information. You will need to configure BGP peering between your on-premises routers and the Azure ExpressRoute gateways. The maximum number of prefixes you can advertise depends on your ExpressRoute SKU.

# Example BGP configuration snippet (conceptual) router bgp 65001 neighbor 10.100.1.2 remote-as 65501 neighbor 10.100.1.2 update-source Vlan100 ! address-family ipv4 unicast network 192.168.1.0 mask 255.255.255.0 exit-address-family

Service Provider Integration

Your chosen ExpressRoute service provider plays a crucial role. They will assist in provisioning the circuits and can help with the peering and routing configurations required for Global Reach.

Tip: Consult your ExpressRoute service provider's documentation for specific instructions on enabling Global Reach.

Getting Started

To get started with ExpressRoute Global Reach:

  1. Review the official Azure ExpressRoute Global Reach documentation.
  2. Work with your network team and ExpressRoute service provider to plan your connectivity.
  3. Provision and configure your ExpressRoute circuits and Azure resources.
  4. Enable Global Reach through the Azure portal, Azure CLI, or PowerShell.

By leveraging ExpressRoute Global Reach, you can build a robust, high-performance, and secure hybrid network that spans your on-premises infrastructure and the Azure cloud across the globe.