Deploy a Conductor on Microsoft Azure

You can deploy an Airwall Conductor on Azure and manage physical, virtual, and cloud Airwall Edge Services, and Airwall Agents. Use the following steps to deploy a Conductor on the Microsoft Azure platform.

Note: Click the print icon printer icon in the top right to print or download this topic.

Prerequisites

To get started, make sure you have access to your Azure account. If you don't have an account, you can create a free Microsoft Azure account and upgrade it to a full account later. If you have an existing Azure account, make sure your billing information is set up. You cannot create a project until you are able to link your billing information to your newly created project.

You need to purchase a Conductor license voucher for your Conductor to complete Step 3. After your purchase is complete, you get an email from Tempered Fulfillment with your voucher code.

Note: If you are familiar with how Azure organizes the components, you should be able to easily understand what is required and create them manually. However, this document does not cover a full manual deployment of a Conductor in Azure.

Step 1: Log in to Azure Cloud

From a Web browser, navigate to https://portal.azure.com and log in using your Azure credentials.

Step 2: Add a Conductor image

You add a Conductor image from the Azure marketplace to your project to create an instance.

  1. In Azure, select Create a Resource, and search for Tempered Conductor Deployment.
  2. Select Tempered Airwall Conductor Deployment Wizard 2.2, go to the Plans tab and check the version of the Conductor, and then select Create.
    Tempered Airwall Conductor Managed in the Azure Marketplace
  3. On the Create Tempered Airwall Conductor Managed 2.2 page, Basics tab:
    Subscription
    Select your subscription model from the drop-down.
    Resource group
    Create a resource group for your virtual network. To do this click Create New, enter a new name, and click OK.
    Region
    Select the region for this instance.
    Create a resource group in Azure
  4. Select Next: Virtual Machine Settings. On the Virtual Machine settings tab:
    Virtual Machine name
    Enter a prefix for the virtual machine.
    Configure virtual networks
    Select or create a Virtual network.
    Public shared subnet
    Select a public subnet from the virtual network you selected.

    Azure Virtual machine settings

  5. Select Next: Endpoint settings. On the Endpoint Settings page:
    Conductor Public IP address
    Select Create new, then under Create public IP address, set SKU to Basic and Assignment to Static, and select OK.
    DNS label
    Enter a prefix for the DNS name. Check to make sure you get the green check, indicating the name is valid.

    Azure endpoint settings page, and create a public IP dialog

  6. Select Next: Review + create.
  7. Review your settings, and accept the Terms of Use, and then select Create. Azure starts deploying your image to the resource group you specified.
    Azure deploying the Conductor image

Step 3: Verify the install

At this point the Conductor instance is running in your cloud provider.
To verify, paste your Conductor IP into a browser window. It should show you the Initial Conductor Configuration page. To log in, configure, and license your Conductor, see Log in and Configure the Conductor.
Note: In v2.2.8 and earlier, it shows the Provisioning page. See License and Provision a Conductor (v2.2.8 and earlier).

It may take several minutes for the Conductor to become available after it starts, so if you attempt to access it and your browser appears to stop responding, please try again in a few minutes.

Note: When running the Conductor for the first time, you may receive notifications indicating the connection is not private. Once you have finished configuring the Conductor, you can install a custom certificate on the Conductor that prevents these notifications in the future.
  1. When Azure finishes deploying, it takes you to the Conductor instance. Leave this page up as you verify the install. Navigate to Outputs, and next to publicIp, select the copy icon to copy the public IP for your cloud Conductor.
  2. Go to a web browser, enter in the IP you copied, and bypass the security warning.
  3. Sign in to the Conductor:
    1. Go back to Azure Outputs page, and next to conductorPassword, click the copy icon to copy the Conductor password.
      Note: If you do not see a password on this page, it's likely you are not using the Managed image.
    2. Enter username: admin, and the password you copied. The default is Tnw-<privateIpOfPublicNic>.
    3. Change your password when prompted.
  4. The Conductor starts the Initial Conductor Configuration wizard. To log in, configure, and license your Conductor, see Log in and Configure the Conductor.
    Note: In v2.2.8 and earlier, it shows the Provisioning page. See License and Provision a Conductor (v2.2.8 and earlier).
  5. When you've finished configuring, licensing, and provisioning your Conductor, you can sign in to start using or continuing configuring your Conductor.
For more information, see:

Verify, Configure, Provision, and License a Cloud Conductor

At this point the Conductor instance is running in your cloud provider.
To verify, paste your Conductor IP into a browser window. It should show you the Initial Conductor Configuration page. To log in, configure, and license your Conductor, see Log in and Configure the Conductor.
Note: In v2.2.8 and earlier, it shows the Provisioning page. See License and Provision a Conductor (v2.2.8 and earlier).

It may take several minutes for the Conductor to become available after it starts, so if you attempt to access it and your browser appears to stop responding, please try again in a few minutes.

Here are the default passwords for cloud Conductors. You are prompted to change the password as soon as you log in:
  • Alibaba Cloud – Tnw-<instanceID>
  • Amazon Web Services – Tnw-<instanceID>
  • Microsoft Azure – Tnw-<privateIpOfPublicNic>
  • Google Cloud – Tnw-<instanceID>
Note: In Microsoft Azure, if you do not see a password on the Azure Outputs page next to conductorPassword, it's likely you are not using the Managed image.
Note: When running the Conductor for the first time, you may receive notifications indicating the connection is not private. Once you have finished configuring the Conductor, you can install a custom certificate on the Conductor that prevents these notifications in the future.
For more information, see:

Additional Information

Once your Conductor is installed, you can configure and manage it as you would a physical Conductor. See Configure a Conductor. For additional help, you can search Airwall help by using the search bar at the top of the page or the navigation links to the left.