Pureport supports private connectivity to Microsoft Azure via the Microsoft Azure Partner program, both for Private Peering to a VNet and Microsoft Peering to connect privately to services normally accessed via the Internet such as Azure Storage, Azure SQL, Azure AD, Dynamics 365, and many of the other PaaS features offered by Microsoft Azure.

This article describes connecting via Microsoft Peering. Typically a Microsoft Peering connection requires 10 unused, unique public IP addresses and an AS number to establish peering. The Pureport Multicloud Fabric provides these for you.

To use Pureport to connect to Azure via ExpressRoute using Microsoft Peering, perform the steps to set up an ExpressRoute circuit and then provision the Connection in your Pureport Network:

  1. Create an ExpressRoute Circuit and Service Key in the Azure Portal.
  2. Create a new Connection in the Pureport Console.
  3. Confirm circuit is up/up on the Azure side.
  4. Configure Microsoft Peering in the Azure Portal.

Note: Microsoft authorization is required to use ExpressRoute for Office 365. Microsoft reviews every customer request and authorizes ExpressRoute for Office 365 usage onlywhen a customer's regulatory requirement mandates direct connectivity. For more information refer to Azure ExpressRoute for O365


Before you begin:

  • Ensure that you have access to the Azure portal.
  • Ensure that you have permissions to create new networking resources. Contact your account administrator if you do not have the right permissions.

Creating your Azure ExpressRoute Circuit and Service Key

For complete information, refer to the Azure documentation site.

  1. Sign into the Azure Portal.

  2. To create a new ExpressRoute Circuit, select Create a resource > Networking > ExpressRoute. You can alternatively search for ExpressRoute in the search bar.
    Note: If ExpressRoute is not listed, use the Search field to find the ExpressRoute option.

  3. Complete the fields on the Create ExpressRoute Circuit page. 
    Be aware of the following special fields and values:
    • Circuit Name: Enter a descriptive name for the circuit.
    • Provider: Select Equinix.
      Note: Although Pureport is the Connectivity Provider, Equinix is the Ethernet Exchange Provider. For complete information, see "ExpressRoute Connectivity Providers" in the Azure documentation.
    • Peering location: The Azure peering location must match the Pureport location you will choose in the next step via the Pureport console. For a list of supported locations see Pureport Locations and Cloud Regions.
    • Bandwidth: Select the circuit speed. This must match the speed you will select in the next step via the Pureport console.
    • SKU: Select Standard (adequate for most needs).
    • Billing Model: Select Metered (the best choice for most needs). See the ExpressRoute pricing page for more information.
    • Resource Group: Select the appropriate Azure resource group.
    • Location: Select the Azure Region for this connection. In general, this should match the region where the target VNet is deployed. For a list of supported regions, see Pureport Locations and Cloud Regions.

  4. Click Create.

To review the properties of the new circuit:

  1. Select All Resources.
    Tip: Use the filters to easily find a specific resource.

  2. Select the circuit. The system displays its properties.
    Note: If the Azure portal displays an error message stating Invalid ExpressRoute state, the circuit is still being provisioned and should be available shortly.

Note: Use the Copy icon to copy your Service Key number to your PC's clipboard. You will need to complete the provisioning process in the Pureport Console.

Create an Azure ExpressRoute Connection in the Pureport Console

Use this procedure to create a new connection:

  1. Login to the Pureport Console using an account with an appropriate Role. At a minimum you will need the Create and Update permissions for Networks. For more information on Roles, see the Accounts, Members and Roles article.

  2. In the left navigation bar, select Networks.

  3. Select the network you wish to add the connection to Azure.
    To create a new network for this connection, see Creating a Network.

  4. Select Add Connection... in the upper right of the console or click the location on the network map.

  5. In the New Connection page, select Azure ExpressRoute from the connection Type dropdown.
  6. Select the Pureport location, Cloud region (Select which Azure Cloud Region you specified in the Location field when you created the ExpressRoute circuit above), Peering type and Speed you wish to provision the connection.

    Note:  For connectivity to various Azure public-facing services (Office Dynamics, Azure Storage, etc) choose a peering type of  Microsoft. 

  7. Enter your Azure Service Key (that you copied earlier from the Azure portal) and click Next.

  8. Enter a meaningful Name and Description, then click Add Connection.

Confirm circuit is Enabled on the Azure portal

To review the properties of the circuit, return to the Azure portal and check the Provider Status of the circuit.

Confirm that the Provider status is Provisioned:

Circuit and provider status

Configure Microsoft Peering for the circuit

Confirm you have the following information from the Pureport Console before you proceed:

  • The /30 Primary Subnet for the primary link
  • A /30 subnet Secondary Subnet the secondary link
  • The VLAN ID to establish this peering
  • The Peer ASN for peering
  • Advertised Public Prefixes
  • The Customer ASN
  • Routing Registry Name
  • The Shared Key

In this article, the following sample connection information is used:

  1.  Select All Resources.
    Tip: Use the filters to easily find a specific resource.

  2. Select the circuit. The system displays its properties.

  3. In the Peerings area, select Microsoft.

  4. Configure Microsoft peering and save the configuration.
    This image shows a configuration using the previous sample information.

  5. If successful, the Status will change to Configured, as shown here: 
  6. Configure your route filters and attach them to your Expressroute Circuit.
    See the Azure documentation for complete information on configuring route filters for Microsoft peering.