After you have customized the imported VM to where it matches your business needs for the desktops and remote applications that you want provisioned to your end users, that VM is now your golden image. Before the system can use that image for assignments that you can entitle to your end users, you must use the Horizon Universal Console Publish workflow to seal the image. Publishing that golden image seals it, which makes it an assignable image.

This page applies to single-pod images located in Horizon Cloud on Microsoft Azure pods.

If you see Images - Multi-Pod displayed in the console, the features of the Horizon Image Management Service and multi-pod image management are available to you. For multi-pod images, different steps are used to publish those multi-pod images to the participating pods. In that case, you would follow the steps for publishing multi-pod images found in the Managing Horizon Images from the Cloud guide.

Important: If your pod in Microsoft Azure is configured to use a proxy, you are responsible for providing a way for the farm VMs or VDI desktop VMs that are created using this image to be configured with the proxy.


Verify that a configured image is available in the pod in which you want to create the assignable image.

Important: To be supported for use in Horizon Cloud on Microsoft Azure, 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 Horizon Cloud on Microsoft Azure. 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 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.

Verify that the Imported VMs page indicates that the VM is powered on (green status) and its agent-related status is active, as illustrated in the following screenshot.

Screenshot of an imported VM with its Agent Status column displaying Active (19.3.0)

Verify you have the credentials of an enabled local administrator account in the image VM. The system uses the local administrator account in the image sealing process, which converts a golden image into the published state. Typically, the VM's only enabled local administrator account is the one that you named when you created the image VM, as described in Creating Desktop Images for a Horizon Cloud Pod in Microsoft Azure and its subtopics.

Important: Unless you manually added additional local administrator accounts to the image VM, the VM's only local administrator account is the one you specified when you ran the Import VM wizard, or when you manually created the VM for the golden image.


  1. In the console, click Inventory > Images and then click New.
  2. Enter the required information.
    Option Description
    Location Select the location associated with the pod where you have the configured image. This field filters the set of pods that will appear for selection in the Pod list.
    Pod Select the pod that has the configured image.
    Tip: If you do not see any pods to select, verify that the Location list is not displaying a location without pods. The Location field works on the Pod list to filter out pods that are not associated with the selected location. If you previously had a pod at a location and then deleted that pod or moved it to a different location, so that the displayed location no longer has any pods, the Pod list will display no entries. Because the locations are listed alphabetically, when the screen opens, it automatically selects the one that is first in the alphabet. If that location no longer has any pods associated with it, you must switch the location to a different entry.
    Desktop This field lists the VMs located on the selected pod that the system can convert to an assignable image. Select the one you want.

    After you make a selection, information about the selected VM is displayed, such as its status.

    Image Name This field is auto-populated with the image name associated with the Desktop selection.
    Company Name Type an identifying name. This name will appear in the virtual desktops that get created based on this image. The publishing process sets the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\RegisteredOwner to this value. The name will appear in the About Windows dialog in those virtual desktops as the registered organization and owner.
    Timezone Retain the default.
    Admin credentials for the desktop Enter the credentials for the local administrator account that is enabled in the image VM. Usually the only enabled local administrator account is the one that was named when the image VM was created.
    Note: The publishing process includes running the Microsoft Windows Sysprep process. When the VM has a Microsoft Windows server operating system, the Sysprep process will reset the built-in administrator account password to this password that you type here. This password reset is done to secure the built-in administrator account after the Sysprep process has completed. The built-in administrator password is reset to the password you type here whether you specify the built-in administrator account or another local administrator account in this step.
  3. Click Publish.
    The publishing process takes several minutes to complete. The page displays the In Transition status during this process. You can use the refresh icon to see the latest status.


If the process is successful, the image's status changes to Published. When the image is in Published status, it is considered sealed in Horizon Cloud. Sealed images are those VMs that the system can use in RDSH farms for delivering session-based desktops and remote applications (in the case of RDSH-capable Windows operating systems) or use in VDI desktop assignments (in the case of single-session Windows client operating systems).
Warning: After you publish the image and it is in its sealed state in Horizon Cloud, do not use the Microsoft Azure Portal to perform actions on that image VM. Using the Microsoft Azure Portal to perform direct actions on a VM that is in the published state in Horizon Cloud is unsupported and will cause unexpected behavior. Always use the Horizon Universal Console to perform actions on sealed images.

If you find you need to change something in a sealed VM's guest Windows operating system, use the steps in the following topics, as appropriate for the situation:

Images in Published status are not listed on the Imported VMs page. They are removed from the Imported VMs page when they reach Published state. At that point, those sealed VMs are available on the Images page.

If the publish operation fails, select Monitor > Activity and locate the failed job. Correct the problem, then retry the publish operation by selecting the check box next to the image, clicking More > Convert to Desktop. Then click New, enter the required information, and click Publish to publish the image.