Quick Connect to Microsoft Azure ExpressRoute Metro (Port, Service Token, Fabric Cloud Router)

ExpressRoute Metro (currently in preview) offers an enhanced resiliency option for Equinix Fabric customers connecting privately to Azure. Using only one service key, customers can provision a circuit with diverse connections to multiple Microsoft Enterprise Edge (MSEE) locations in a metro. Connecting to Azure cloud through ExpressRoute Metro meets Microsoft’s high resiliency architecture, one of three resilient connectivity frameworks supported by Equinix Fabric. ExpressRoute Metro simplifies the deployment of high-availability connectivity to Microsoft Azure so that more customers can benefit from an automated, resilient design between their enterprise network and their Azure workloads.

Note: ExpressRoute Metro is currently available to Equinix Fabric customers connecting to Azure in Amsterdam and Singapore. Expect additional metros to go live before the end of the year as Microsoft expands support and makes the service generally available.

Microsoft offers their customers three architectures for enabling network resiliency with Azure workloads. Equinix is one of a small number of partners working with Microsoft to deploy interconnection infrastructure to support all three.

The levels of resiliency are:

  • Maximum resiliency – Diverse connections to MSEE routers in multiple locations and metros.

  • High resiliency – Diverse connections to MSEE routers in multiple locations within one metro.

  • Standard resiliency – Diverse connections to distinct MSEEs in a single location.

The high resiliency architecture provides a good balance of resiliency and simplicity since the underlying diverse elements appear as one connection. This architecture also eliminates the need for multiple Equinix Fabric connections which results in the same, or better, resiliency at a lower cost.

Customers should consider the criticality of their applications and deploy the design that offers the appropriate level of resiliency.

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

Prerequisites

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

  • An Azure account with Microsoft.

  • An ExpressRoute Metro Service Key created in the Azure Resource Manager (ARM) portal. For more information on how to create an ExpressRoute Service Key, see Quickstart: Create and modify an ExpressRoute circuit.

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

Create a Connection Using Quick Connect

  1. Log in to Equinix Fabric.

  2. Use the Context Switcher and select the project under which you want to create the connection. For more information on projects, see Equinix Identity and Access Management: Projects.

  3. From the Connections menu, select Create Connection.

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

  5. Locate the Microsoft Azure card and click Select Service.

  6. On the Azure ExpressRoute card, click Quick Connect.

  7. In the Enter Your Azure Information section, enter your ExpressRoute Metro Service Key.

    Tip: This will pre-populate the speed and peering metro of the ExpressRoute connection.

  8. Select connection type:

    • Redundant – Create a redundant pair of connections.
    • Primary – Create a single, primary connection.
    • Secondary – Create a single, secondary connection.

    Important: Redundant configuration is recommended. If you select a single connection option, no Service Level Agreement (SLA) is provided by Azure.

  9. Select peering type:

    • Azure Private – Applicable to private virtual networks.
    • Microsoft – Applicable to Office 365, Dynamics 365 and public services.

    Note: You are not required to use both services (Private and Microsoft).

    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.

  10. Click Next.

  11. Configure your connection depending on the origin asset type:

    1. From the Origin Asset Type drop-down list, select Port.

    2. In the Primary Connection section:

      • Click + Select Primary Port, then select your primary connection port and click Select Port.

        Note: Only primary ports are available for selection.

      • Enter the primary connection name.
      • Enter a VLAN ID.

        In the Azure Settings section, enter Customer VLAN (C-Tag).

        Important: Use the same VLAN ID when configuring the peering type in the Microsoft Azure portal.

    3. In the Secondary Connection section:

      • Click + Select Secondary Port, then select your secondary connection port and click Select Port.

        Note: Only secondary ports are available for selection.

      • Enter the secondary connection name.
      • Enter a VLAN ID.

    4. Click Next.

  12. In the Contact Information section, review the email address used for notifications. This address can be changed if necessary.

  13. Enter or add purchase order number.

    1. Click Select Purchase Order Number.

    2. Click Select an Existing Purchase Order.

    3. Select purchase order number you want to apply to your order, then click Done.

  14. Enter customer reference identifier, that will help you identify this order on your invoice.

  15. Click Create Connection.

  16. On the confirmation page, click View this Connection in your Fabric Inventory to see the connection in you inventory.

Service Provider Resources