This page describes how to use the console'sImages - Multi Pod page to import a Windows VM from the Microsoft Azure Marketplace into your first-generation Horizon Cloud tenant's IMS image catalog. At the end of the creation process, the new imported image is listed on the console's Multi-Pod Images page, ready to be published as a multi-pod image.

Attention: This information applies solely when you have access to a first-gen tenant environment in the first-gen control plane. As described in KB-92424, the first-gen control plane has reached end of availability (EOA). See that article for details.

As of August 2022, Horizon Cloud Service - next-gen is generally available and has its own guide, Using Horizon Control Plane next-gen.

An indication of which environment you have, next-gen or first-gen, is the pattern that appears in the browser's URL field after you log in to your environment and see the Horizon Universal Console label. For a next-gen environment, the console's URL address contains a portion like /hcsadmin/. The first-gen console's URL has a different section (/horizonadmin/).

In a first-gen tenant that has multiple pods in its pod fleet, when you run this Import from Azure Marketplace workflow and select a pod, consider selecting the fleet's pod that has the lowest manifest version in which to create the base VM and which will be the pod that directs the publication process to all pods within the tenant's fleet.

When using this automated Import VM from Marketplace workflow to create a base VM, the system automatically uses certain VM sizes by default. The system's default choice is based on its internal settings, and selections you make in the wizard for operating system (OS) and whether to make the image GPU capable.

Important: To be supported for use in first-gen Horizon Cloud on Microsoft Azure deployments, all imported base images must be built from Windows-based VMs that are sourced from the Azure Marketplace. Even if you try an image obtained from other origins and the console does not prevent you from using it within the console's workflows, use of such images is unsupported.

If the image is running a Windows 11 operating system, in addition to the requirement to be directly sourced from the Azure Marketplace, the image cannot have been subsequently processed for it to be validly supported in first-gen Horizon Cloud on Microsoft Azure deployments. Importing Windows 11 VM from any other sources such as Shared Image Gallery (SIG), Azure Managed Images, Azure VM snapshot, and the like is currently unsupported.

For additional considerations about supported combinations of Gen-1 and Gen-2 machines for the image-related workflows with first-gen Horizon Cloud on Microsoft Azure deployments, which OSes are supported for which machine generation, refer to Support for Images Sourced from Pods on Microsoft Azure.

Multi-pod image - Import VM from Marketplace wizard creates:
  • Non-GPU Windows-10 OS or a Windows 10 Enterprise multi-session OS or a Windows Server OS multi-pod image, a Standard_DS2_v2 VM
  • Non-GPU Windows 11 OS or a Windows 11 OS Enterprise multi-session OS multi-pod image, a Standard_D4s_v3 VM
  • GPU-capable multi-pod image, Standard_NV12s_v3 VM
Important: According to the OSes and GPU selection you plan to use, ensure that your Azure subscriptions have quota availability for the VM types in the preceding list. If your subscription does not have the appropriate quota, the Import VM from Marketplace workflow will fail because the VM could not be created in the subscription.
Note: The console's automated import VM wizard no longer provides Windows 7 as a selection option. As a result, references to Windows 7 that previously appeared in this page have also been removed.

If you cannot obtain quota from Microsoft Azure for the Standard_NV12s_v3 family in your subscription and you want to have a GPU-capable golden image, you can use this alternative. Starting with the v2204 service release, Horizon Cloud supports the manual import of a Standard_NV4as_v4 VM from the Azure Marketplace to configure a GPU-enabled golden image using AMD graphics drivers. The pod must be running the v2204 release's manifest version to obtain that support. For the steps to manually import such a VM from the Azure Marketplace to use in your Horizon Cloud on Microsoft Azure deployment, first follow the sequence of pages starting with Manually Build and Import a Virtual Machine from Microsoft Azure into Horizon Cloud and its subsequent pages in the Procedure and those pages' What to do next sections. Then when the imported VM is on the console's Imported VMs page, use Move to Multi-Pod Images to move that VM to the console's Images - Multi-Pod page. Refer to the page Move a VM to the Multi-Pod Images for what to watch out for when using this method.


This feature is only available if all your first-generation Horizon Cloud Microsoft Azure deployments in your first-gen tenant are running the IMS-compatible manifest version or later manifest. Refer to First-Gen Tenants - IMS System Requirements.


  1. To start the Import VM from Marketplace wizard, on the first-gen console's Multi-Pod Images page, do one of the following:
    • If the tenant's pod fleet has both Horizon Cloud on Microsoft Azure deployments and Horizon deployments, click New > Create from Azure Marketplace.
    • If the fleet solely has Horizon Cloud on Microsoft Azure deployments, click New.
  2. In the wizard, select the pod in which to create the VM.
    First select the pod's associated location and then select the pod from the list of pods at that location.
    After you select a location, the choices in the Pod list are filtered to show the pods available in the selected location.
    Important: If you are planning to use this image for GPU-enabled desktops or remote applications, ensure that the selected pod resides in a Microsoft Azure region that supports GPU-enabled virtual machines (VMs) and that your Microsoft Azure subscription supports GPU-enabled VMs. GPU-enabled VMs are only available in some Microsoft Azure regions. See Microsoft Azure Products by region for details.
  3. Select the details for the base VM.
    Option Description
    OS Select the Microsoft Windows operating system to use for the image's underlying VM.
    Note: This drop-down menu takes a few moments to populate the entries.
    Include GPU Enable this toggle to specify a GPU-enabled image.
    • If this toggle is dimmed, that means your Microsoft Azure subscription in the selected pod's region does not support GPU hardware.
    Important: Using this toggle results in the system importing a VM from the Azure Marketplace with the Standard_NV12s_v3 VM type. To get the GPU capabilities in that imported VM, after the import process is completed, you must log into the VM's operating system and install the supported NVIDIA graphics drivers.
    Enable Public IP Address Enable this toggle to configure a public IP address for this base VM. When enabled, the VM gets both a private IP address and a public one.

    When this toggle is turned off, the VM is configured with only a private IP address in your Microsoft Azure environment.

  4. Provide administration details.
    Note: The user name and password you enter must meet the Microsoft requirements for acceptable user names and passwords for creating a VM in Microsoft Azure. For the list of requirements, see username requirements and password requirements in the Microsoft documentation.
    Option Description
    Username Type the admin name that you want for the VM's local administrator account. This local administrator account is created in the VM during the process. This name will be used for the local admin account to access the VM's operating system. This name can be a maximum of 15 characters in length, must not end in a period ("."), and must not be one of the admin names that are not allowed when creating a VM in Microsoft Azure.
    Important: Ensure you can remember this local administrator account information (this name and the password that you specify in the Password text box), or that you write it down so you can retrieve the information later. You need these credentials to add any third-party applications to this base image.
    Password Enter the password that you want for that administrator account. The password must adhere to the Microsoft Azure password rules:
    • Must not be one of the admin account passwords that are not allowed when creating a VM in Microsoft Azure
    • Must be from 12 through 123 characters in length and meet three out of the following four complexity requirements:
      • Contain a lowercase character.
      • Contain an uppercase character.
      • Contain a digit.
      • Contain a special character, such as (!@#$%/^&*)
    Verify Password Re-type the password.
  5. In the Name text box, provide a name for the image and an optional description.
    Option Description
    Name Enter a name for the image.
    Important: Do not enter a name that was previously used for an image in your Horizon Cloud environment. Due to a known issue, the VM creation process fails silently if you reuse a name that is already listed on the Multi-Pod Images page. The system does not create the VM in Microsoft Azure but an error message does not appear in the administrative console.

    When selecting a name, confirm that the name you are using does not already appear as an image name on either the Multi-Pod Images page or the Images page.

    The name must adhere to the following rules:

    • It cannot contain an underscore character (_).
    • It can have only alphanumeric characters and the hyphen.
    • The name must start with an alphabetic character (not a number).
    • The name cannot end with a hyphen (-).
    Description Enter an optional description for the image.
    Important: You must assign at least one marker to have the image later available for creating assignments in the console's Create Assignment workflow. If you do not assign at least one marker now, the image will not appear in the UI as a choice in the assignment creation workflow later. Ensure you have at least one string displayed in this box before you click Import.

    Use this UI box to define one or more reference markers that you want to associate with the image. The markers will be associated with version 1.0 of the image.

    As you type in characters, those characters appear in both the UI's box and in a blue row below the box.

    Important: After typing in characters, you must complete the addition of the marker to this UI box. Either press your Enter key or click the string displayed in the blue row below the box. After the string is fully added to the UI box, the box will display the characters with a curved outline around them and a little x for removing it. If you do not see the string displayed in the box with a curved outline around it, then the marker is unsaved. The marker needs to be saved for the image to be used in assignments.
  6. Click Import.
    Horizon Image Management Service starts to import the image into the catalog and creates a new image in the list. The in-progress ( Cycling arrow icon representing operation that is in progress) icon appears in the Status column for the image on the Multi-Pod Images page.
  7. To monitor the import progress, click the name of the image on the Multi-Pod Images page.
    The details page for the image appears.

    Image details page showing version 1.0 import in progress
    The in-progress ( Cycling arrow icon representing operation that is in progress) icon appears in the Status column for version 1.0 while the import is underway. During this process, Horizon Image Management Service creates a copy of the image in the resource group of the Microsoft Azure subscription corresponding to the source pod. It also registers the image with the service by storing the image's metadata in the image catalog. When the import is complete, the status of image version 1.0 changes to Deployment Complete.

What to do next

Publish the first image version based on the imported image. Publishing the image version replicates the image to selected Horizon Cloud on Microsoft Azure deployments. See First-Gen Horizon Cloud Pods - Publish an Image.
Important: In the console's publishing workflow, remember to select to install the Horizon Agent, especially if you intend to use this image with App Volumes on Azure features. The imported image does not yet have the agent features until they are installed in the publishing workflow.

The following screenshot illustrates the location of the Install Horizon Agent toggle in the Publish Image wizard.

Screenshot of the Install Horizon Agent toggle and a green arrow pointing to it.