Connect to Microsoft Azure ExpressRoute (Network Edge Device)

Connect to Azure ExpressRoute from a Network Edge virtual device.

Note: For instructions on connecting from a Fabric port, a Fabric Cloud Router or using a service token, see Quick Connect to Microsoft Azure ExpressRoute (Port, Service Token, Cloud Router).

Prerequisites

Before creating a connection to Microsoft Azure ExpressRoute from a Network Edge virtual device, you must have:

  • An Azure account with Microsoft.

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

  • An Equinix Fabric account, with the following IAM roles assigned: Fabric Connections Manager.

  • A Network Edge virtual device.

Create a Connection to Azure ExpressRoute

To connect to Microsoft 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 Service.

  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:

    1. In the Origin section:

      1. Click Virtual Device.

        Important: If the Virtual Device option is disabled, there are no virtual devices available in the selected project. Choose a different project, that has virtual devices assigned to it, or create a new virtual device in this project.

      2. Select metro.

      3. Choose virtual device type, select connection type, then select a virtual device instance.

    2. In the Destination section, enter your Microsoft Azure ExpressRoute Service Key, then click Next.

      Tip: 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 origin location to see the pricing for any route on the Fabric network.

  8. On the Connection Details page:

    1. Enter a primary connection name.

    2. Enter a secondary connection name.

    3. Select peering type.

    4. Select network interface on your virtual device.

    5. Enter a VLAN Seller C-tag.

      Note: If you enter a C-tagged VLAN value here, it must match the C-tag value entered in the Azure portal for the selected Peering Type. This 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.

    6. Enter a purchase order number.

    7. Click Next.

  9. On the Review page:

    1. Review the Connection Summary and Redundant Connection Summary.

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

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

    4. Click Submit Order.

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

To monitor the status of your connection, from the Connections menu, select Connections Inventory.

Tip: You can use Fabric's API to automate or integrate this procedure. For more information, see Equinix Fabric API - Connect to Microsoft Azure.

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 Content

Microsoft Azure ExpressRoute Redundancy Modes

Upgrade Azure ExpressRoute Bandwidth

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

Connect to Azure Using API

You can use Fabric's API to automate this procedure and integrate it with your internal systems. For details, see Connect to Microsoft Azure.