Create or modify an Exchange peering with Route Server using the Azure portal

This article describes how to create a Microsoft Exchange peering with a route server using the Azure portal. This article also shows how to check the status of the resource, update it, or delete and deprovision it.

Before you begin

Create and provision an Exchange peering

Sign in to the portal and select your subscription

From a browser, go to the Azure portal and sign in with your Azure account.

If you have multiple subscriptions and need to switch subscriptions:

  1. Select the profile button, and then select Switch Directory.

    Select Switch directory

  2. Choose a subscription you want to use for peering setup.

    Choose subscription

Create an Exchange peering with route server

As an Internet Exchange Provider, you can create an exchange peering request by Creating a Peering.

  1. On the Create a Peering page, on the Basics tab, fill in the boxes as shown here:

    Register Peering Service

  • Select your Azure Subscription.

  • For Resource group, you can either choose an existing resource group from the drop-down list or create a new group by selecting Create new. We'll create a new resource group for this example.

  • Name corresponds to the resource name and can be anything you choose.

  • Region is auto-selected if you chose an existing resource group. If you chose to create a new resource group, you also need to choose the Azure region where you want the resource to reside.

    Note

    The region where a resource group resides is independent of the location where you want to create peering with Microsoft. But it's a best practice to organize your peering resources within resource groups that reside in the closest Azure regions. For example, for peerings in Ashburn, you can create a resource group in East US or East US2.

  • Select your ASN in the PeerASN box.

    Important

    You can only choose an ASN with ValidationState as Approved before you submit a peering request. If you just submitted your PeerAsn request, wait for 12 hours or so for ASN association to be approved. If the ASN you select is pending validation, you'll see an error message. If you don't see the ASN you need to choose, check that you selected the correct subscription. If so, check if you have already created PeerAsn by using Associate Peer ASN to Azure subscription.

  • Select Next: Configuration to continue.

Configure connections and submit

  1. On the Create a Peering page, on the Configuration tab, fill in the boxes as shown here:

    Configure route server

    • For Peering type, select Direct
    • For Microsoft network, select AS8075 with exchange route server.
    • Select SKU as Basic Free. Don't select premium free as it's reserved for special applications.
    • Select the Metro location where you want to set up peering.
  2. Under Peering Connections, select Create new

  3. Under Direct Peering Connection, fill in the following BGP session details:

    Screenshot shows the Direct Peering Connection pane with details added.

    • Peering Facility, select the appropriate physical location for the peering
    • Session Address Provider, select Peer
    • Session IPv4 prefix will be provided by the exchange provider peer
    • Peer session IPv4 address, will be selected by the exchange peer for the route server from their IP prefix range.
    • Microsoft session IPv4 address, will be the router IP allocated from the IP prefix range.
    • Session IPv6 is optional at this time.
    • Maximum advertised IPv4 prefix can be up to 20000.
    • Use for Peering Service is disabled by default. It can be enabled once the exchange provider has signed a Peering Service Agreement with Microsoft.
  4. Upon completion, select Save.

  5. Under Create a peering, you'll see validation passed. Once validation passed, select Create

    Validation of settings

    Note

    For normal Internet Service Providers (ISP) who are a Microsoft Peering Service partner, customer IP prefixes registration is required. However, in the case of exchange partners with a route server, it is required to register customer ASNs and not prefixes. Same ASN key would be valid for the customer's prefix registration.

  6. Select Registered ASNs under the Settings section.

    Screenshot shows the Peering pane with the Registered A S Ns menu item called out.

  7. Select Add registered ASN to create a new customer ASN under your exchange subscription.

    Screenshot shows the Register an A S N pane with Name and A S N text boxes.

  8. Under Register an ASN, select a Name, populate the customer ASN, and select Save.

  9. Under Registered ASNs, there will be an associated Prefix Key assigned to each ASN. As an exchange provider, you'll need to provide this Prefix Key to your customer so they can register Peering Service under their subscription.

    Screenshot shows the Registered A S Ns pane with prefix keys.

Verify an Exchange peering

After the Peering resource is deployed successfully, you can view it by following these steps.

  1. Go to Resource groups, and select the resource group you selected when you created the Peering resource. Use the Filter box if you have too many resource groups.

    Resource groups

  2. Select the Peering resource you created.

    Screenshot that shows the Peering resource yuo created.

  3. The Overview page shows high-level information, as shown here.

    Peering resource Overview pane

  4. On the left, select ASN information to view the information submitted when you created PeerAsn.

    Peering resource ASN information

  5. On the left, select Connections. At the top of the screen, you see a summary of peering connections between your ASN and Microsoft, across different facilities within the metro. You can also access the connections summary from the Overview page by selecting Connections in the center pane, as shown.

    Peering resource Connections

    • Connection State corresponds to the state of the peering connection setup. The states displayed in this field follow the state diagram shown in the Exchange peering walkthrough.
    • IPv4 Session State and IPv6 Session State correspond to the IPv4 and IPv6 BGP session states, respectively.
    • When you select a row at the top of the screen, the Connection section on the bottom shows details for each connection. Select the arrows to expand Configuration, IPv4 address, and IPv6 address.

    Screenshot that highlights an arrow that expands a section.

Modify an Exchange peering

This section describes how to perform the following modification operations for Direct peering.

Add Exchange peering connections

  1. Select the + Add connections button, and configure a new peering connection.

    Peering resource view

  2. Fill out the Exchange peering Connection form, and select Save. For help with configuring a peering connection, review the steps in the "Create and provision a Direct peering" section.

    Exchange Peering Connection form

Remove Exchange peering connections

  1. Select a peering connection you want to delete, and then select ... > Delete connection.

    Delete connection button

  2. Enter the resource ID in the Confirm Delete box, and select Delete.

    Delete confirmation

Add an IPv4 or IPv6 session on Active connections

  1. Select a peering connection you want to modify, and then select ... > Edit connection.

    Edit connection button

  2. Add IPv4 address or IPv6 address information, and select Save.

    Peering connection modifications

Remove an IPv4 or IPv6 session on Active connections

Removing an IPv4 or IPv6 session from an existing connection isn't currently supported on the portal. For more information, contact Microsoft peering.

Deprovision an Exchange peering

At this time, deprovisioning isn't supported by using the Azure portal or PowerShell. To deprovision, contact Microsoft peering.

Next steps

Additional resources

For more information, see Internet peering FAQs.