Lumen help

Creating an IP VPN Dynamic Connection to Azure Gov

To create an IP VPN Dynamic Connection to Azure Gov:

  1. Click Services.

    Control Center shows the Services console. Use the console to access an inventory of your services, check the status of orders, and manage your services.
Services console
Dynamic Connections (showing IP VPN tab)
  1. In the Connection Name field, type a name for the connection you're creating. (Be sure to use something memorable. This name will appear on your invoice.)
  1. From the Cloud Provider list, select Azure Gov.
IP VPN Create Connection (showing Azure Gov selected)
  1. 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. (You can't change the bandwidth once you create the connection. If you need to choose a different bandwidth after creating a connection, disconnect the connection and create a new one.)
  1. In the Connector Details section, fill in the additional details for the connection. (Control Center automatically the connection as private and sets 12076 as the AS number for Azure Gov.)

    1. 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:8600. 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.

    2. 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. These contacts will receive notifications for order submissions, connection activations, and disconnect requests for the connection:

    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, places it in Pending Activation status, and routes you to the connection dashboard so you can monitor the status of the connection. To see status updates, click
    . Once Lumen assigns the permanent VRF (within five minutes), the connection changes to Active status.