Skip to main content
Azure: Virtual Cross Connect

This document will provide instructions and guidelines for integrating an Azure VPC environment with the Telnyx network backbone.

Written by Customer Success
Updated over a week ago

This document will provide instructions, technical details and guidelines for integrating a Microsoft Azure Cloud environment with the Telnyx network backbone. A virtual cross connect (VXC) is a private and direct connection between cloud providers that is faster and safer than a traditional public internet connection. Using this strategy allows you to bypass the internet and gain direct and private access to Telnyx, thereby eliminating hops and reducing the risk of packet loss and jitter. You’ll also benefit from the additional security of direct interconnection.

Additional documentation:

Instructions for integrating Azure VPC with Telnyx

In this activity you will:


  • Have a Microsoft Azure cloud environment

Video Walkthrough

Coming soon! Check back frequently as we are updating our documentation.

1. Prepare Microsoft account for Azure Express Route. 

  1. Log into your Azure Portal.

    The Azure portal interface.

  2. Perform a search for express route and click on Express Route Circuits.

    An open search tab for express route circuits.

  3. Click on Add -> Provider. This provider must be Equinix, do *NOT* select Allow Classic Operations. Rename other fields at your discretion.

    Provider addition tab.
    Microsoft Azure dashboard.

  4. Click OK.

  5. Once the deployment completes, you will see your newly-provisioned Azure Express Route.

    Newly-provisioned Azure express route.

2. Set up the VXC in your Telnyx Mission Control Portal

  1. Click on "Networking" in the left-hand menu

    Telnyx Mission Control Portal.

  2. Click on the "Create New Network" button on the top-right.

    "Create New Network" button.

  3. Give your network a name and click on the "Create Network" button

    "Create Network" button.

  4. Once the Network is Created, Next step is to add the site. Click on the "Add a Site" button.

    "Add a site" button.

  5. Choose the Telnyx Backbone Network you want to peer with.

    Telnyx Backbone Network selection table.

  6. Add the VXC, by clicking on "Create VXC".

    "Create VXC" add button.

  7. Create an Azure Express Route.

    Note that in order to complete this section, Stage 1 needs to have been completed.

    Azure Express Route creation portal.

  8. Key in Azure Service Key and Microsoft Azure ASN. Typically it is 12076

    Azure Service Key and Microsoft Azure ASN credentials input.

    You can see a sample Service Key and ASN Displayed Below

    Sample Service Key and ASN display.

  9. Now create your VXC and submit it to Telnyx Network team. 

    VXC creation portal and submission button.

    Connection acceptance will be TELNYX Network Team. 

    Routing and NAT configuration interface.

IMPORTANT: Do NOT Enable Routing status via the slider, this step has to be coordinated in sync with Telnyx Network Team, as enabling this without Backend configuration may blackhole your voice traffic.

3. Turning up Routing and NAT configuration 

  1. Arrange a Maintenance activity and co-ordinate with TELNYX Network engineering to turn on the Routing. Please contact our Support Team to assist with this.

    Note: This activity has to be co-ordinate with the Network team to complete Back-end configuration during the Maintenance window. 

  2. Once you enable the circuit using the Routing Status slider, you should see a routing table in Express Route similar to the following: 

    Routing and NAT configuration interface.

Once enabled with Routing, you'll see Telnyx public ranges via Express Route Circuit. This will ensure that these are preferred over the Internet Routing Table. 

Routing table display.

That's it, you've now integrated your Google VPC and Telnyx though VXC.

Additional Resources

Review our getting started guide to make sure your Telnyx Mission Control Portal account is set up correctly.

Additionally, see:

Did this answer your question?