Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Uploading and Deploying a vTA Image Through the Azure Web GUI

Signing In to Azure

  • Go to You will be redirected to a URL associated with your location. The description that follows deals with the English-language version of the GUI.
  • Sign in to your Azure account.
  • You are taken to a user interface that looks like this:

Creating a Storage Account

  • In the left-hand pane, click Storage accounts. This opens a view listing your existing storage accounts, if any.

  • Click “+ Add” to create a new storage account.
  • Make the appropriate choice under Resource group (we are assuming here that some resource group has already been created). The remaining settings can be left as-is.

  • Click the Review + create button at the bottom.
  • Click Create.

Your storage account is now created. Refresh the Storage accounts page if necessary to see your account in the list.

Creating a Storage Container (Blob)

  • Click your account in the Storage accounts list.
  • Click Blobs.

  • Click ”+ Container”.
  • Enter a name for the container.
  • For the other settings, the defaults can be kept here as well.
  • Click OK. Your container is now created.

Uploading the Test Agent VHD File to the Storage Container

The next step is to upload your Test Agent VHD file to the storage container you just created.

  • Click the storage container in the list of containers.
  • Click Upload.

  • Under Files, select your Test Agent VHD file.
  • Expand Advanced.

  • Important: Under Blob type, select Page blob.

  • Keep the defaults for the remaining settings.
  • Click Upload.

The upload will take some time as the Test Agent VHD file is approximately 2 GB in size.

Creating an Image

  • In the left-hand pane, click Images.

  • Click ”+ Add”.

  • Enter a name for the image.
  • Make the appropriate choice under Resource group.
  • Under OS type, select Linux.
  • Under Storage blob, browse to select the VHD file you uploaded in the section Uploading the Test Agent VHD File to the Storage Container.
  • Leave the remaining settings unchanged.
  • Click Create. The image will now appear in the Images view.

Creating a Virtual Machine

In this section we will create a virtual machine (VM) in which to run the vTA.

  • In the Images view, click the image you created.
  • Click Create VM.

  • Under Administrator account, you need to provide an SSH key pair to be able to log in to the Test Agent admin menu later on:
    • Set Authentication type to “SSH public key”.
    • Enter an arbitrary string under Username. This setting cannot be left undefined, but it is not used when logging in to the Test Agent.
    • Under SSH public key, paste your SSH public key.
  • Under Inbound port rules, do as follows:
    • Set Public inbound ports to “Allow selected ports”.
    • Under Select inbound ports, select “SSH (22)”.
  • Keep the defaults for all other settings.
  • Click Review + create, then Create.

The virtual machine is now created.

Logging In to the Test Agent

Here is how to log in to the Test Agent via SSH. This is needed in order to register the Test Agent with the Paragon Active Assurance system, and it is also useful for troubleshooting:

  • In the left-hand pane, select Virtual machines.
  • Select the virtual machine created for the Test Agent.
  • Note down the Public IP address of the virtual machine.

  • At a command prompt, type:

where id_rsa is the name of the file holding your SSH private key and vm_public_ip is the virtual machine’s public IP address.

You are now taken to the Test Agent admin menu:

Here you can register the Test Agent with the Paragon Active Assurance system as described in the support documentation under Test AgentsConfiguring Test Agents from the local consoleRegistering a Test Agent from the local console. Upon registration, the Test Agent will be visible in Control Center.

Again, please note that initialization of the Test Agent with user data using cloud-init cannot be done through the web GUI. The Azure CLI must be used for this purpose; see the section Creating a Virtual Machine.

The other functionality found here is likewise described in the Paragon Active Assurance support documentation: see the remaining topics under Test AgentsConfiguring Test Agents from the local console. The following functions are particularly helpful:

  • UtilitiesPing for checking that the vTA has a working internet connection.
  • UtilitiesTroubleshoot connection for verifying that the Paragon Active Assurance management connection is working.