This section discusses the steps required to create a cloud configuration of type Azure.

Use NSX Advanced Load Balancer UI to create a cloud configuration of type Azure, so that NSX Advanced Load Balancer can spin up Service Engines in the Azure VNet, and the load balance workloads present there.

Follow the given steps to complete the cloud configuration.

  1. Log in to the NSX Advanced Load Balancer UI using the Controller IP address, navigate to Infrastructure > Clouds.

  2. Click the Create button to add a new cloud. Provide a name, and select Microsoft Azureas the Cloud infrastructure type.

  3. On the next tab, provide information related to the Azure account.

    Figure 1.
  4. NSX Advanced Load Balancer UI has the option to select the desired License Model.

  5. Start by clicking Create Credentials tab and provide Azure credentials. You can either choose an Azure account username/password, or an Application ID.

  6. In the screenshot below, the username method is used.

    Figure 2. Azure Credentials
  7. Select the license model that you want to use. You can either select the Pay-as-you-go, or the Bring your own license option. The below screenshot exhibits the option for the Pay-as-you-go license model. For the PAYG licence model, the license type is set to SE Bandwidth automatically.

    Figure 3. Azure License
    1. For the Bring your own license model, you can use the drop-down menu to use the following licence types: Cores SE Bandwidth.

  8. Save and select these newly created credentials and provide the Azure subscription ID.

  9. Click Next. Provide the Azure location details. These details are associated with the location of resource group, the resource group and the VNet that can be used, and the subnet for the Service Engine management network.

  10. Optionally, a DNS provider can be selected as well. Instead of Azure DNS, AWS Route 53 can also be used by selecting Other.

  11. Click Complete, to provision the Azure cloud.

  12. At this time, the Controller will upload the Service Engine VHD into an Azure storage account, so that SEs can be deployed as required by the applications.

  13. Save the settings.

The system is now ready for virtual service creation.