Skip to main content

Azure ExpressRoute Overview

Azure ExpressRoute enables creating private connections between your infrastructure deployed in IBX data centers and your Microsoft Azure assets. ExpressRoute connections don't route through the public internet, ensuring reliability, higher bandwidth, consistent latency, and higher security.

Equinix Fabric enables you to connect from your a-side:

To your z-side Azure ExpressRoute circuit.

Options for creating the connection include:

Azure Express Route Service Profiles​

Azure ExpressRoute offers two service profiles on Fabric.

The Azure ExpressRoute service profile is for connections in the AMER, EMEA, and APAC regions and covers most use-cases.

The Azure Government ExpressRoute service profile is for connections in select US markets. You must have a service key from the Microsoft Azure Government Portal to use this service profile. Otherwise use the normal ExpressRoute service.

Creating an ExpressRoute Circuit​

In the Microsoft Azure portal, create an ExpressRoute circuit and retrieve its service key.

Refer to the Microsoft documentation for instructions on how to create an ExpressRoute circuit.

Bandwidth Options​

When you enter your ExpressRoute service key to create your connection, the bandwidth information is automatically set based on your ExpressRoute circuit configuration.

Connections to Azure ExpressRoute support changing the bandwidth on existing connections.

Resiliency Considerations​

When you create your ExpressRoute circuit, you choose the type of resiliency for your connection The levels of resiliency are:

  • Standard resiliency – Diverse connections to distinct Microsoft Enterprise Edge (MSEE) devices in a single location.

  • High resiliency - ExpressRoute Metro – Diverse connections to MSEE routers in multiple locations within one metro. The high resiliency architecture makes the underlying diverse elements appear as one connection. Using only one service key, you can provision a circuit with diverse connections to multiple Microsoft Enterprise Edge (MSEE) locations in a Metro. This architecture eliminates the need for multiple Fabric connections. Equinix supports ExpressRoute Metro in the following metros:

    • Amsterdam
    • Singapore

  • Maximum resiliency – Diverse connections to MSEE routers in multiple locations and metros. This option requires creating multiple Fabric connections.

For more information, see Design and architect Azure ExpressRoute for resiliency.

If the service key is already in use for a primary or secondary connection you may be able to add additional connections using the same key. A banner will display indicating which connection and peering types are still available for a key already in use.

A single service key will support four virtual connections on DOT1.Q ports (a primary and secondary connection for each peering type). However each of the four connections must have unique ExpressRoute peering VLAN IDs. Two virtual connections can be created with a service key on QinQ ports.

Configuring Peering​

Microsoft offers these services through Equinix Fabric:

  • Microsoft Peering – Public peering (PaaS/SaaS). Public peering, or connecting with Microsoft public offerings such as Skype, is now only available through Microsoft peering.
  • Private Peering – Private peering (IaaS)

You are not required to use both services (private and Microsoft).

Four virtual connections can be created with a single service key (each having a primary and secondary connection). However, each of the four connections must have unique ExpressRoute Peering VLAN IDs. For example, if 2000 is used as the private ExpressRoute peering VLAN ID, then the same VLAN can't be used for private or Microsoft peering.

Once the connection has been created, it waits for you to configure Microsoft peering on the Microsoft Azure portal.

To configure peering in Azure Express Route, you must log in to the Microsoft Azure portal. Refer to the Microsoft documentation for instructions on how to configure peering for an ExpressRoute connection.

  • If you are connecting to Azure ExpressRoute from a Port, the status remains PENDING_BGP_PEERING until peering is completed in the Microsoft Azure portal and the status only changes to PROVISIONED once Equinix Fabric syncs with Microsoft. If you want to synchronize the BGP peering instantly, you may use the Equinix Customer Portal or the Connection Actions API endpoint.

  • If you are connecting to Azure ExpressRoute from a Fabric Cloud Router, you also need to configure your routing details for the connection in the Equinix Customer Portal.

  • If you are connecting to Azure ExpressRoute from a Network Edge device, you also need to configure the routing details on the device, which vary by vendor (such as Cisco or Juniper).

Once peering configuration is synchronized, the connection status should change from PENDING_BGP_PEERING to PROVISIONED. To verify the route to and from the customer, visit the Microsoft Azure Portal.