Integrating Equinix ExpressRoute with Microsoft Azure VMware Solution

This document provides a step-by-step guide to connecting Equinix Fabric to Microsoft Azure VMware Solution (AVS) via ExpressRoute. It includes architecture details, configuration steps, BGP peering setup, and troubleshooting methods.

1. Introduction

  • ExpressRoute provides a private connection between Microsoft Azure and a network (e.g., Equinix).
  • It allows dynamic routing, high availability, and secure direct cloud access without traversing the public internet.
  • ExpressRoute enables VMware SDDC (Software-Defined Data Center) environments in Equinix to connect seamlessly to AVS.
  • Global Reach connects ExpressRoute circuits for optimized routing between AVS and native Azure services.

2. Architecture

  • The setup involves Equinix Fabric, Microsoft Azure ExpressRoute, and AVS.
  • Azure ExpressRoute circuit connects Equinix to Microsoft Enterprise Edges (MSEE).
  • A dedicated AVS private cloud connects through ExpressRoute Global Reach for seamless communication.
  • Uses BGP (Border Gateway Protocol) to dynamically exchange routes between Equinix and Azure.

3. Requirements

Before setting up Equinix to Azure AVS ExpressRoute, ensure the following:

A fully functional VMware SDDC in an Equinix data center.
Top-of-Rack (ToR) switches configured in Equinix Fabric.
Deployed AVS cluster in Azure.
Azure Virtual Network (VNet) for native Azure service access.
ExpressRoute circuit in Azure for private connectivity.
Two /30 subnets for transit networks (Primary & Secondary connections).
Origin VLAN ID (Colocation ToRs) & Destination VLAN ID (Azure side).
BGP Autonomous System Numbers (ASN) configured properly.

4. Workflow: Setting Up Equinix ExpressRoute to Azure AVS

Step 1 – Create a Resource Group

  1. Log in to the Azure portal.
  2. Navigate to Resource Groups → Create a new Resource Group.
  3. Provide a name and region for the Resource Group.
  4. Add tags for easier management (e.g., “Production,” “Development”).

Step 2 – Create the ExpressRoute Circuit in Azure

  1. Navigate to Create a ResourceSearch for ExpressRoute → Select Create.
  2. Choose the Resource Group created in Step 1.
  3. Select the Region closest to the Equinix data center.
  4. Enter a Name for the ExpressRoute connection.
  5. Configuration:
    • Port Type: Provider (since Equinix is the service provider).
    • Provider: Select Equinix.
    • Peering Location: Choose the region where the Equinix ports are located.
    • Bandwidth: Select based on expected traffic needs.
    • SKU:
      • Standard: Up to 10 VNets, 4,000 routes.
      • Premium: If more than 10 VNets or 4,000 routes are needed.
    • Billing Model: Choose between Metered (pay-per-usage) or Unlimited (flat-rate pricing).
  6. Click Create to provision the ExpressRoute circuit.

Step 3 – Create Equinix Connection

  1. Log in to Equinix Fabric portal.
  2. Navigate to Connections → Create Connection.
  3. Select “Microsoft Azure” under “Select Services”.
  4. Choose “Azure ExpressRoute” → Click Create Connection.
  5. Enter the Service Key from the Azure portal (generated in Step 2).
  6. Select Origin Port in Equinix Fabric.
  7. Assign:
    • VLAN ID for Origin (Colo ToRs).
    • VLAN ID for Destination (Azure side).
  8. Configure Peering Type:
    • Private Peering: For Azure VMware Solution.
    • Microsoft Peering: If using services like Microsoft 365.
  9. Review configuration & Submit.
  10. The provisioning typically completes within 10 minutes.

Step 4 – Configuring BGP Peering

Configure BGP on Equinix ToRs

  • Use BGP ASN 12076 (Microsoft).
  • Assign IPs from /30 subnets configured in the requirements.

Configure Peering in Azure

  1. Navigate to the ExpressRoute circuit in the Azure portal.
  2. Under Peerings, select Azure Private Peering.
  3. Configure:
    • Peer ASN (ASN from Equinix ToRs).
    • Primary /30 subnet (Use first IP for ToR, second for Azure).
    • Secondary /30 subnet (Required even if using a single link).
    • VLAN ID (Must match Seller C-tag set in Equinix Fabric).
  4. Click Save.
  5. Verify BGP session:
    • Equinix portal → Check Provisioned status.
    • Ping Microsoft router IP from the Equinix side.

Step 5 – Connecting ExpressRoute to AVS

  1. Enable ExpressRoute Global Reach in the Azure portal.
  2. Generate an Authorization Key in the ExpressRoute circuit.
  3. Copy the Authorization Key and go to AVS Private Cloud Resource.
  4. Navigate to Manage → Connectivity → ExpressRoute Global Reach → Add.
  5. Enter the Authorization Key and confirm.
  6. Monitor the connection status.
  7. Run a continuous ping test from Equinix VMware SDDC to AVS vCenter to verify connectivity.

5. Troubleshooting

Common Issues & Fixes

IssueResolution
BGP not establishedCheck VLAN ID configurations and ensure correct ASNs are assigned.
Cannot ping Microsoft routerVerify ToR subnet settings and test connectivity from Equinix ToR.
Equinix status shows “Pending BGP”Ensure private peering settings are configured correctly in Azure.

7. Additional Resources

🔗 Microsoft ExpressRoute Connectivity Models
🔗 Azure VMware Solution
🔗 Equinix Fabric Overview
🔗 Equinix Cloud Exchange & Network Edge Videos

Final Thoughts

This guide outlines how to establish a private, high-performance connection between Equinix Fabric and Microsoft Azure VMware Solution using ExpressRoute. Proper network planning, VLAN mapping, and BGP configurations are key to a successful deployment.

meenakande

Hey there! I’m a proud mom to a wonderful son, a coffee enthusiast ☕, and a cheerful techie who loves turning complex ideas into practical solutions. With 14 years in IT infrastructure, I specialize in VMware, Veeam, Cohesity, NetApp, VAST Data, Dell EMC, Linux, and Windows. I’m also passionate about automation using Ansible, Bash, and PowerShell. At Trendinfra, I write about the infrastructure behind AI — exploring what it really takes to support modern AI use cases. I believe in keeping things simple, useful, and just a little fun along the way

Leave a Reply

Your email address will not be published. Required fields are marked *