Connect to Microsoft Azure ExpressRoute

Equinix has an API integrated ordering process for customers seeking to provision Microsoft Azure ExpressRoute. This increases automation in the process and allows for 100% self-service for the user. Customers can provision an ExpressRoute connection via the Equinix Fabric portal within minutes as a result.

Prerequisites

Before creating a connection to Microsoft Azure ExpressRoute, users must have:

  • An Azure account with Microsoft
  • An ExpressRoute Service Key which is configured in the Azure Resource Manager (ARM) portal

  • An Equinix Customer Portal (ECP) account

  • An Equinix Fabric account

Connect to Azure via Azure ExpressRoute

  1. Log in to Equinix Fabric.

  2. From the Connections menu, select Create Connection.

  3. On the A Service Provider card, click Connect to a Service Provider.

  4. Locate the Microsoft Azure card and click Select.

  5. On the Azure Express Route card, click Create Connection.

  6. Review the steps for connecting to Azure ExpressRoute, then click Create a Connection to Azure ExpressRoute.

  7. On the Select Locations page, you can set up a connection using a port, a service token, or a virtual device.

    To create a connection using a port or redundant ports, click Port.

    1. Select the Location, and a port in that location.

    2. In the Redundant Origin section, select a secondary port.

      Note: We recommend that you select a secondary port to connect to ExpressRoute. If you select the option to create a single connection, no Service Level Agreement (SLA) is provided by Azure.

    See the following for instructions about how to use a service token or virtual device as your connection origin:

  8. In the Destination section, enter your Microsoft Azure ExpressRoute Service Key.

    Once your ExpressRoute Service Key is validated, the Azure Peering Location and bandwidth are displayed. The Pricing Overview displays updated details based on your connection location choices. It is possible to change the location of the origin port(s) to see the pricing for any route on the Fabric network.

  9. Click Next.

  10. In the Primary Connection Information section, enter:

    • Connection Name – A name for your primary connection

    • VLAN ID – Your VLAN ID (this is the S-tag VLAN value)

  11. In the Secondary Connection Information section, enter:

    • Connection Name – A name for your primary connection

    • VLAN ID – Your VLAN ID (this is the S-tag VLAN value)

  12. (Optional) Enter a VLAN Seller C-tag. If you enter a C-tagged VLAN value here, it must match the C-tag value entered in the Azure portal for the Peering Type selected (see the screen shot below). This optional value allows for the ExpressRoute circuit to move to a provisioned state. This is helpful for Fabric reseller users, or for users that have to manage multiple Azure subscriptions for different business units where they are only provided an ExpressRoute Service Key for provisioning and do not have access to ExpressRoute Peering configuration.

  13. (Optional) In the Purchase Order Number field, enter your PO number.

  14. Click Next.

  15. Review the Connection Summary and Pricing Overview.

  16. (Optional) In the Notifications section, enter any additional email address(es) that should receive notifications about this subscription.

  17. (Optional) Click Design Summary to download a copy of the design details.

  18. Click Submit Order.

Note: Charges begin as soon as the connection request is submitted.

Click the Connections menu and select Connections Inventory to view the status of your connection.

Azure Connection States

The Azure connection goes through the following states:

  • Not Provisioned – Beginning the provisioning with Microsoft Azure.

  • Pending BGP Peering – Waiting for customer to configure Microsoft peering for service name (private and Microsoft) on the Microsoft side.

  • Provisioned – Provisioning completed with Microsoft Azure.

When you create the service key on the Microsoft Azure Portal, the initial status of the service key is Not Provisioned. Once the connection is submitted to Equinix Fabric, the Azure circuit (service key) status changes to Provisioned.

Note: You configure peering on the Azure Portal only when the status is Provisioned. Azure recommends redundancy for each peering type associated with an ExpressRoute circuit Service Key.

Available Microsoft Peering Services

Microsoft offers these services through Equinix Fabric:

  • Microsoft Peering – Public peering (PaaS/SaaS)

  • 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.

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.

Note: Public peering, or connecting with Microsoft public offerings, such as Skype, is now only available through Microsoft peering.

Verify Routes on the Microsoft Azure Portal

To verify the route to and from the customer, visit the Microsoft Azure Portal.

Related Topics

Microsoft Azure ExpressRoute Redundancy Modes

Upgrade Azure ExpressRoute Bandwidth

For more information on Microsoft Azure ExpressRoute, see the Microsoft documentation.