In the Microsoft Azure portal, you create a virtual machine (VM) with the Windows server guest operating system that you want to use for the remote desktops and remote applications. You create this VM using the same subscription that you used for the Horizon Cloud node.

About this task

This VM must be created in the resource group named vmw-hcs-nodeID-base-vms, where nodeID is the node's UUID identifier. Horizon Cloud automatically detects VMs located in that resource group and then lists them on the Inventory screen in the Administration Console. Also, this VM must get connected to the same virtual network to which the node is connected.

For RDS-enabled master VMs, Horizon Cloud supports using the Microsoft Windows 2012 R2 Datacenter and Microsoft Windows 2016 Datacenter VMs that are available in the Microsoft Azure portal's VM catalog.


In this release, GPU is not supported in Microsoft Windows Server 2016 due to a limitation in the Horizon Agent. If you want to have GPU acceleration for your RDS desktop, you must use Microsoft Windows 2012 R2 Datacenter for that desktop.

Also, the Microsoft server VM types that support GPU acceleration are the NV6 types. Those choices are only available in some Microsoft Azure regions. To have GPU-based RDS desktops available from the node, the node must be in a Microsoft Azure region in which those NV6 VM types are available. The NV6 Standard type is recommended.


Obtain the following information about the node for which you are creating the VM. To see this information, open the node's details in the Horizon Cloud Administration Console by navigating to Settings > Capacity and clicking the node's name. Obtain from the node's Summary tab:

  • The name of the virtual network to which your node is connected. You must select the same virtual network when creating the VM.

  • The node's UUID for the node for which you are creating the VM. You need this UUID to identify that node's resource groups in the Microsoft Azure portal, so that you know in which resource group to locate the VM.


  1. Log in to the Microsoft Azure portal using the Microsoft Azure account associated with the subscription used to deploy the node.
  2. Navigate into the node's vmw-hcs-nodeID-base-vms resource group by clicking Resource Groups in the portal's left hand navigation, locating that specific resource group, and then clicking on its name.

    To list only the resource groups for a particular node, on the Resource groups screen, type that node's ID into the Filter by name field.

  3. In the screen for that vmw-hcs-nodeID-base-vms resource group, click Add.

    Location of Add button to add VM to the base-vms resource group

  4. In the Search Everything field, enter Windows Server Datacenter to list the available Windows Server Datacenter VMs.

    This release supports using the Windows Server 2012 R2 Datacenter and Windows 2016 Datacenter VMs that appear in the list. They are listed with Publisher = Microsoft and Category = Compute.


    If you want to have GPU-based desktops, select Microsoft Windows 2012 R2 Datacenter in this step. In this release, GPU is not supported in Microsoft Windows Server 2016 due to a limitation in the Horizon Agent.

    List of Windows Server Datacenter VMs to choose in the Microsoft Azure portal

  5. Click the one you want for the base VM.
  6. In the new pane, verify that the deployment model is set to Resource Manager and then click Create.

    Deployment model setting and Create button

    The portal displays the wizard steps for creating the virtual machine, open to the Basics step.

    Create VM wizard opened at step 1 Basics step

  7. In the Basics step, complete the required fields and then click OK to save your values and go to the next step.




    Give this VM a name of up to 15 alphanumeric characters.

    VM disk type

    Keep the default (SSD). You can adjust this setting in the next wizard step.

    User name

    Enter a name for the default administrator account.


    Confirm password

    Enter a password for the default administrator account, and confirm it.

    The password must adhere to the password complexity rules that Microsoft Azure defines for the VM. Typically the password must be at least 12 characters long have three of the following: one lower case character, one upper case character, one number, and one special character that is not backslash (\) or hyphen (-).


    Keep the default setting of your subscription selected.

    Resource group

    Verify that Use existing is selected and the selected resource group matches the one from step 2. If it does not match, select the correct resource group (vmw-hcs-nodeID-base-vms).


    Verify that Location matches the Microsoft Azure region in which your node is deployed.


    If you want to have a GPU-based VM, the node's Microsoft Azure region needs to have the NV6 VM type available. That NV6 type is not available in all Microsoft Azure regions.

    Already have a Windows Server license?

    Choose the selection that is appropriate for your organization.

    Create a VM Basics step with values filled in

  8. In the Size step, select a size for the VM and then click Select to save your selection and go to the next step.

    The pane displays the VM size options as selectable blocks. You might have to click View all to see more size options.


    To have GPU-based desktops, change Supported disk type to HDD and select one of the NV family types. Only the NV types allow installation of the GPU drivers. NV6 Standard is recommended.

    Create a VM in Microsoft Azure Step 2 VM Size



    Supported disk type

    To have GPU-based desktops, select HDD. Otherwise, keep the default SDD setting.

    VM size

    Select the VM profile. To have GPU-based desktops, select one of the NV family types. NV6 Standard is recommended. Otherwise use one of the D_V2 series.

  9. In the Settings step, configure the virtual network and subnet settings as described below, and then click OK to save your entries and go to the next step.

    Keep the default values for the other settings.

    • You must keep Storage - Use managed disk set to Yes. If the VM does not have Storage - Use managed disk set to Yes before you install the agents, Horizon Cloud cannot use this VM and you will have to create a new one to use.

    • As described in the prerequisites section above, you must set the Virtual network to the same one that the node uses.

    • Do not alter the defaults for the other options in the Settings screen (such as no extensions, etc). Keep the defaults for those options. Do not make changes other than what is mentioned below.



    Storage - Use managed disk

    Set this option to Yes (the default).


    Ensure this option is set to Yes. Otherwise, your VM will be unusable in Horizon Cloud.

    Virtual network

    Click Virtual network and select the same virtual network to which the node is connected.


    Click Subnet and select the one named vmw-hcs-nodeID-net-tenant. To see their full names, hover over each one and see the names in the tooltips.

    Create a Base VM in Microsoft Azure Step 3

    After you click OK, a validation runs. When it passes, the wizard moves to the final Purchase step.

  10. In the Purchase step, review the summary and verify the settings, especially the resource group, virtual network, subnet, and Managed set to Yes.

    The resource group and subnet names should contain the node's UUID (nodeID).



    Resource group




    Virtual network

    The node's virtual network.



    Create a base VM in Microsoft Azure

  11. Click Purchase.

    Microsoft Azure starts deploying the new VM into the resource group.

What to do next

Fully deploying the VM can take several minutes. When the portal's dashboard indicates the VM is created and ready, make a remote desktop connection to the VM's public IP address and continue configuring the base VM. Complete the steps in Manually Configure the Master Virtual Machine in Microsoft Azure.