Multicloud Transit Integration with Azure VNG Workflow

Currently, Aviatrix Multicloud Transit solution requires encryption over Azure ExpressRoute or External Device to on-prem directly. There are times when encryption is not required and native network connectivity on ExpressRoute is highly desirable. In such scenarios, the Aviatrix Transit solution including Transit FireNet can only forward traffic between Spoke VNets or inspect east-west traffic only, as shown with these Azure Transit Network design patterns.

Multicloud Transit Integration with Azure VNG allows Aviatrix Multicloud Transit solution to integrate with native Azure Virtual Network Gateway (VNG) and enables Aviatrix Transit Gateway to inspect traffic from on-prem to cloud in addition to east-west and egress traffic inspection. Both native Spoke VNet and Aviatrix Spoke Gateway based Spoke VNets are supported.

Data packets are forwarded natively to on-prem through Azure Virtual Network Gateway (VNG) either over Express Route or Internet, and in the meantime, Aviatrix Transit Gateways are inserted in the data path between VNG and Spoke VNet. This allows you to run advanced function such as firewall inspection for on-prem to Spoke and between the Spokes.

This document describes the configuration workflow for the following network diagram, where there are two Spoke VNets, one with Aviatrix Spoke Gateway ( and one native Spoke VNet (


The key ideas for this solution are:

  • The edge (WAN) router runs a BGP session to Azure VNG via Azure ExpressRoute or VPN where the edge router advertises to the Azure VNG the on-prem routes and the VNG advertises the Spoke VNet CIDRs.

  • Aviatrix Controller periodically retrieves route entries from the Transit VNet VNG route table advertised from on-prem. The Controller then distributes these routes to Spoke VNet and Aviatrix Transit Gateway.

  • Azure native VNet Peering is configured between each Spoke VNet and Transit VNet VNG with Allow Remote Gateway attribute configured on the Spoke VNet to automatically advertise routes from Spoke VNet to VNG and to On-prem.

  • Traffic coming from on-prem to VNG is routed to the Azure Load Balancer which then forwards traffic to both Aviatrix Transit Gateways for Active-mesh deployment. The same Load Balancer is also used to distribute traffic to firewalls for inspection.

  • Traffic coming from Spoke VNet is routed to Aviatrix Transit Gateway directly which then forwards the traffic to the Azure Load Balancer. Future release will support ActiveMesh in this direction of traffic.


Upgrade Aviatrix Controller to the latest version.

We highly recommend creating an Azure Transit VNET with the Transit + FireNet option enabled. Create a VNG in this Transit VNet.

Connecting VNG on On-Prem

If you have already created the VNG in Transit VNet, skip this section.

Building Azure ExpressRoute is your responsibility. For more information about Azure ExpressRoute, see the below documents:

Adjust the topology depending on your requirements.

Follow the steps below to set up this configuration workflow.

  1. Create an ExpressRoute circuit. See Tutorial: Create and modify an ExpressRoute circuit.

  2. Create Azure private network for an ExpressRoute circuit. See the private peering section in Create and modify peering for an ExpressRoute circuit.

  3. Create a VNG in Transit VNet with Transit + FireNet enabled. Note that this step may take up to 45 minutes to complete. See Configure a virtual network gateway for ExpressRoute using the Azure portal for more information.

  4. Connect a virtual network to an ExpressRoute circuit. See Connect a virtual network to an ExpressRoute circuit using the portal.

  5. Check ExpressRoute Circuits - List Routes Table on the Azure portal.

Checking ExpressRoute Circuits Routes Table in Azure

  1. Log in to the Azure portal and search for "ExpressRoute circuits" in the search bar.

  2. Select the ExpressRoute circuits that you created.

  3. Select the Azure private peering row.

  4. Select Get route table to verify routes learned from on-prem.

Connect Aviatrix Transit Gateway with VNG

Refer to Global Transit Network Workflow Instructions for the below steps. Please adjust the topology depending on your requirements.

Deploying an Aviatrix Multicloud Transit Gateway and HA in Azure

Connecting Transit Gateway to Azure VNG

Connect to an Azure VPN Gateway (VNG).

This procedure assumes the Azure VNG is already deployed in the Transit VNet.

To connect the Transit Gateway to Azure VNG (VPN Gateway):

  1. Go to Networking > Connectivity > External Connections (S2C) tab.

  2. Click + External Connection.

  3. Enter the following values:




    A unique name to identify this connection to VNG.

    Connect Public Cloud To

    1. Select the CSP Gateways radio button.

    2. Click on the dropdown menu and select Azure VNG.

    Aviatrix Gateway

    Select the name of the Transit Gateway to connect to VNG.

    If Azure VNG has not been deployed in the Transit VNet, this step cannot complete.

    VNG Name

    The name of the Azure VNG.

  4. Click Save.

The new Azure VNG connection appears in the table.

Checking Effective Routes Info on Azure Portal

  1. Log in to the Azure portal and search for "Network interfaces" on the search bar.

  2. Select the Aviatrix Transit Gateway’s interface.

  3. Navigate to the "Effective routes" page by selecting Effective routes under the Support + troubleshooting section.

  4. Check route entry for On-prem pointing Next Hop Type Virtual network gateway.


Attach Spoke VNet to Aviatrix Transit Gateway

  1. Deploy Aviatrix Spoke Gateway in Spoke VNet. Create an Azure VNET for Aviatrix Spoke Gateway by using the Aviatrix feature Create a VNG in Transit VNet or manually deploy it in cloud portal or feel free to use existing virtual network.

  2. Deploy a Spoke Gateway in the Azure Spoke VNet with High Availability and HPE enabled. HPE is optional.

An instance size of at least Standard_D5_v2 will be required for High Performance Encryption Mode Encryption for higher throughput. Please refer to High Performance Encryption Performance Benchmarks for performance details.
  1. Attach Spoke Gateways to Transit Network.

Ready to Go

Now you should be able to send traffic from cloud to on-prem as well as on-prem to cloud over Azure Express Route.

For FireNet deployment, follow the Transit FireNet workflow.


By design routes advertised to VNG to on-prem are limited only to native spoke VNET peering. They do not advertise non-native spoke/transit-to-transit peerings.