To utilize the GPU features of a GPU-capable VM imported from the Azure Marketplace, you must log into the VM's Microsoft Windows operating system and install the graphics drivers appropriate for the VM type.

Horizon Cloud on Microsoft Azure deployments support these methods for importing GPU-enabled VMs from the Azure Marketplace:

Using the console's Import VM from Marketplace wizard
The wizard specifically imports a Standard_NV12s_v3 VM type.
Manually importing a VM from the Azure Marketplace
When using the manual import method, Horizon Cloud on Microsoft Azure supports importing the following VM models from the Azure Marketplace, according to the operating system you select:
Operating System Supported VM Type from the Azure Marketplace
  • Windows Server
  • Windows 10 single-session or multi-session
  • Windows 11 single-session or multi-session
 Standard_NV12s_v3

Use the NVIDIA GRID drivers, as provided by Microsoft Azure and stated in the Microsoft Azure documentation. Refer to the NVIDIA GRID section in https://docs.microsoft.com/en-us/azure/virtual-machines/windows/n-series-driver-setup.
  • Windows Server
  • Windows 10 single-session or multi-session
 Standard_NV8as_v4

Use the AMD Radeon Instinct driver, as provided by Microsoft Azure and stated in the Microsoft Azure documentation. Refer to https://docs.microsoft.com/en-us/azure/virtual-machines/windows/n-series-amd-driver-setup.

After the VM is created and the console indicates the agent status is active, you must install the appropriate driver.

At a high-level, the workflow is:

  1. Obtain the driver appropriate for the imported VM's series and Windows operating system. Refer to the preceding table.
  2. Connect to the imported VM and log in.
  3. Install the driver by following the installation instructions according to the above Microsoft Azure documentation pages.
Caution: Install the drivers as described and provided in those Microsoft pages and not other drivers.

Prerequisites

Verify the Imported VMs page indicates the agent-related status is active for the VM. To get that status, use the Imported VMs page's Reset Agent Pairing action on the VM. That action is located in the More drop-down list.

Note: When using the Microsoft Remote Desktop Client as your RDP software to connect to the VM, ensure it is the most up-to-date version. For example, the default RDP software in the Windows 7 operating system is not at a high enough version. The version must be version 8 or higher.
Verify you have at least one of the following credentials (user name and password) to log in to the VM's guest Windows operating system, according to how the VM was created.
How the VM was created Credentials to use to log in

Import Virtual Machine wizard, from the Imported VMs page.

Starting with the December 2019 service release date, the Import Virtual Machine wizard provides the option of either having the wizard-created VM joined to a specified Active Directory domain or not having the VM joined to the domain at the end of the creation process.

  • If the VM was created with the wizard's Domain Join toggle enabled, you can use either the credentials for a domain account in the specified Active Directory domain or use the local administrator account that was specified in the wizard.
  • If the VM was created with the wizard's Domain Join toggle turned off, you must use the local administrator account that was specified in the wizard. In this case, because the VM is not joined to the domain, the local administrator account is the only account that has access to log in.

Manual preparation steps.

Typically you do not need to join the VM to your Active Directory domain when you manually build the VM. To log in to that VM, use one of the following:

  • The credentials for the local administrator account that was specified when the manually built VM was created in the Microsoft Azure portal.
  • If you manually joined that VM to an Active Directory domain, the credentials for a domain account in that domain.

Procedure

  1. Use the VM's IP address in your RDP software to connect to the VM's Windows operating system.
    • If the VM was created with a public IP address, you can use that IP address in your RDP software
    • If the VM has a private IP address, you must RDP into it by one of these two methods:
      • Using another VM in your Microsoft Azure subscription that does have a public IP address and doing an outbound RDP into the imported VM.
      • Use your VPN and RDP into the VM over your corporate network
    Note: To access a VM that is running the agent-related software components, the version of the Remote Desktop Client must be version 8 or later. Otherwise, the connection fails. Using the most up-to-date Remote Desktop Client is recommended.
  2. Log in to the Windows operating system using credentials (user name and password) as described in the prerequisites here.
    When using the local administrator account credentials that were specified in the console's Import VM from Marketplace wizard when the VM was created, enter the user name as \username.
    Note: When the VM is a domain-joined VM, as described in the prerequisites here, and you want to use a domain account instead of the local administrator account, enter the user name as domain\username where domain is the name of the domain.
  3. Install the drivers as described in the aforementioned Microsoft Azure documentation page that is applicable to your imported VM's type.
  4. When the drivers are installed, restart the VM.
  5. Reconnect to the VM, log in, and verify that the driver is installed and working in the VM.
    For guidance on how to verify the driver is installed and working, refer to the Microsoft documentation page for your installed driver and that page's specific Verify driver installation section. Each of those Microsoft pages has a Verify driver installation section.
  6. Sign out of the VM's Windows operating system.