You create App Volumes assignments for your Horizon Cloud tenant by using the Assignments menu in the console.


Before creating an App Volumes assignment, you must first create a floating VDI desktop assignment. Due to the processing needs of Microsoft Windows 10 and Windows 11 operating systems, this assignment must have a VMware-recommended desktop model that provides at least 2 vCPU and 4 GB RAM.


  1. In the console, click Assignments and select the option that includes App Volumes or VDI.
  2. On the main assignments page, click New > App Volumes.
  3. On the wizard's Definition step, enter the values shown below.
    Option Description
    Assignment Name Enter a unique name for the new assignment.
    Description (Optional) Enter a description for the assignment.
  4. Click Next.
  5. On the wizard's Applications step, select the applications you want to provide to users.
    • To filter applications displayed, click the filter icon in the header of the Applications column and enter a filter value.
    • To display only applications you have selected, click Selected Applications to the top right of the list.

    To select an application, first select the check box and then select an application package in the Package column. You can select a package either by a marker (such as Current) or the actual name of the package (such as Notepad++ v7.7.1).

    Note: For best results, use the same OS family images for VDI desktops where the applications are being assigned as the OS family where the application package was captured.
  6. Click Next.
  7. On the Users step, search for users and groups in your registered Active Directory domains, select the ones you want to entitle to use applications from this assignment, and then click Next.
  8. On the wizard's Summary step, confirm that the information shown is correct and click Finish.


The new assignment displays in the list on the Assignments page.
Note: If any of your Horizon Cloud pods in Microsoft Azure are offline when you create or edit an App Volumes assignment, the configuration changes are propagated to the online pods only and the assignment shows a pending state. You can go to the assignment's summary page to see that the assignment is incomplete and view the status of each pod. When the problem pods come back online, the configuration changes are propagated to those pods and the assignment reaches a complete state.

If any of the problem pods remain offline for longer than 35 minutes, the assignment lapses into an error state. To bring the assignment to a complete state, first wait for all the problem pods to come back online. Then edit the assignment again as needed and save your configuration changes.