Add network interfaces to an Azure Virtual Machine

If you have resources in multiple virtual subnets within Azure that you want to protect with a single 300v Airwall Gateway, you can add additional network interfaces to the two included in a standard Azure 300v deployment.

Note: You can add as many additional network interfaces as the Azure instance allows.
Supported Versions

Conductor and Azure Cloud Airwall Gateways v3.0 and later

Required Role
  • System or network administrators
  • Permissions to edit the Azure Cloud Airwall Gateways. You need to be a manager of at least one overlay that these Airwall Gateways are in.
Supported on these Airwall Edge Services
Airwall Gateway 300v only.

Before you Begin

Before you add an interface, consider:

  • Cost – An Azure virtual machine (VM) that supports multiple interfaces increases the cost, so weigh the costs and benefits of adding more network interfaces versus deploying multiple 300v Airwall Gateways.

  • Machine type – If you are using the default Azure VM, Standard A2 v2, you must upgrade the machine type to one that supports the number of NICs you want. A list of available NICs per machine type is available in the Azure documentation. Select a machine series from the list (for example, the Av2-series) and scroll to the right in the table to find the maximum number of NICs.

  • Update your Conductor and Airwall Gateway 300v to v3.0 – v3.0 is required to manage the route injection for devices on the additional network interfaces.

Add a Network Interface (NIC) to an Azure 300v deployment

These instructions may change. Please refer to the Azure documentation for updated information.
  1. Go to the Azure VM that is hosting your 300v Airwall Gateway.
  2. Stop the Azure VM.

    Azure interface showing stop button

  3. Go to Settings > Size, and select a new machine type. This screenshot shows upgrading to a Standard A4 v2 that allows up to 4 NICs.

    Azure interface showing going to Settings>Size and selecting a new machine type

  4. In the 300v’s Resource Group, create a new Network Interface object (NIC).

    In Azure, create a new Network Interface object, or NIC

  5. Under the Azure VM’s SettingsNetworking, select Attach network interface and under Attach existing network interface, select the network interface you created.

    In your Azure VM, attach the new network object

  6. Restart the Azure VM.

    Azure interface showing Start button

Once the Azure VM reconnects to the Conductor, the 300v updates its port information with a third network interface with the overlay gateway IP already configured:

Conductor showing Airwall with updated port information