Lumen help

Creating an IP VPN Dynamic Connection to Azure

With Lumen® Dynamic Connections, you can use Control Center to create a connection from a Lumen IP VPN to Microsoft Azure. To create the connection, you'll need an ExpressRoute service key from Microsoft. Be sure to have that information handy to type in (or copy/paste).

To create an IP VPN Dynamic Connection to Azure:

Dynamic Connections (IP VPN)
  1. Click Create Connection.
Dynamic Connections (Create AWS Connection)
  1. From the Customer ID and Billing Account Number lists, select the customer ID and billing account number you want to add Dynamic Connections to.

    Control Center fills in the WAN Inventory section based on your selection.
  1. In the Connection Name field, type a name for the connection you're creating.
  1. Fill in the information for the Azure connection:

    1. From the Cloud Provider list, select Azure.

    2. In the ExpressRoute Service Key field, type or copy and paste your ExpressRoute service key provided by Microsoft. (Note: You can only use a service key that isn't assigned to an active connection. The ExpressRoute service key is a unique service key and is different from the service key for your cloud service from Azure.)

      Once you fill in the ExpressRoute service key, Control Center retrieves connection information from Microsoft and fills in the on ramp information.
  1. In the WAN Inventory section, select a VRF for the other end of your connection.
  1. Use the Billing Method buttons to select whether you want monthly or hourly billing for the connection, then select the bandwidth for the connection.
  1. In the Connector Details section, fill in the additional details for the connection:

    1. From the Cloud Resource list, select whether the connection is public or private.

    2. In the AS Number on Azure field, type the autonomous system number from Microsoft.

    3. From the Routing Option list, select routing option you want to use for the connection:

      • Routing Option 1 - Support the 3 RFC 1918 aggregates (default): supports,, Aggregate routes will be created and the Lumen PE will be configured to advertise these aggregates toward the cloud provider gateway router on the connector-specific eBGP session.

      • Routing Option 2 - Advertise All Routes, Block Specific: The Lumen PE eBGP connector session will be configured with a policy to block the advertisement of routes towards the cloud provider that contain the community 6745:8601. If you want to block specific routes, you must set this community to routes on the BGP session as the routes enter the Lumen IP VPN network (i.e. on a managed/unmanaged CPE using BGP export policy).

      • Routing Option 3 - Optional Customer Defined Aggregates, Allow Specific: select this option to enter your aggregate subnets. The Lumen PE will be configured to advertise these aggregates toward the cloud provider gateway router on the connector-specific eBGP session.

    4. Use the buttons to select whether you want to advertise default routes and whether this is a primary or backup connection.
  1. In the Contacts section, fill in the information for the order and technical contacts for your organization.

    1. Type the contact's first name, last name, phone number, and email address. (Be sure to use the phone number format shown on the screen.)

    2. In the Notification Preference field, select the preference for how Lumen notifies this contact of progress on your order: email, text, or both.

    3. If the technical contact for the connection is the same as the order contact, leave the checkbox selected. If the technical contact is different, clear the checkbox, then fill in the information for the technical contact.
  1. In the Connection Summary box (on the right), read through the terms and conditions, then click the checkbox to accept the terms.
  1. Click Submit.

    Control Center creates the request for the connection and places it in Pending Activation status. Once Lumen assigns the permanent VRF, the connection changes to Active status.