Configure App Volumes Manager Integration with Azure Virtual Desktop

App Volumes Manager can be deployed from the Microsoft Azure Marketplace for Azure Virtual Desktop Remote Apps and Desktops experience. In addition to installing and configuring Omnissa App Volumes in the Azure Marketplace, you can entitle applications directly in Azure Virtual Desktop. For this capability, App Volumes Manager and Azure Virtual Desktop must be integrated.

This integration synchronizes the CURRENT packages and certain application properties between App Volumes Manager and Azure Virtual Desktop. An App Volumes application maps to an App attach package which is an Azure resource in Azure Virtual Desktop.

For information on synchronization triggers and how the application maps to the Azure resource, see Synchronization Triggers between App Volumes Manager and Azure Virtual Desktop Integration.

How to Proceed With the App Volumes Manager Integration with Azure Virtual Desktop

Depending on the status of your deployment, use the following table to understand how to proceed.

Prerequisites

If you want to add another integration or edit the integration between App Volumes Manager and Azure Virtual Desktop, then follow these prerequisites:

• The following permissions for the resource group must be set when selecting either authorization method (Managed Identity or Application Registration):

  • Microsoft.Authorization/permissions/read
  • Microsoft.Resources/subscriptions/resourceGroups/read
  • Microsoft.DesktopVirtualization/appattachpackages/read
  • Microsoft.DesktopVirtualization/appattachpackages/write
  • Microsoft.DesktopVirtualization/appattachpackages/delete

  To set the permissions on the resource group, navigate to the Access control (IAM) menu of a resource group, click Add, and select the Add custom role functionality. For more information, see the corresponding Microsoft documentation.

• Ensure that you do not have any Azure tag policy that prevents the creation or update of an App attach package for a resource group which is integrated with App Volumes Manager. For information about policy definitions for tag compliance, see the Microsoft Documentation.

• Edit the URL (secure address) of this (current) App Volumes Manager instance to an accessible IP address.

  This URL is associated with an App attach package after the synchronization between App Volumes Manager and Azure Virtual Desktop. The URL is used to indicate the App Volumes Manager and the specific application from where the synchronization occurred.

  To edit this URL, see Edit an App Volumes Instance.

• Ensure that you have the Application Registration information handy. This information is obtained when registering App Volumes as an application in the Microsoft Entra ID admin center. See Prerequisites for Deploying App Volumes Manager through Azure Marketplace.

Procedure

1. Go to INFRASTRUCTURE > Integrations.

2. In the Add App Volumes Integration page, fill up the following information:

   Option	Description
   Type	Azure Virtual Desktop
   Name	Enter a name for this integration.
   Subscription ID	Enter the subscription ID which has the resource group meant for integration.
   Resource Group Name	Enter the name of the resource group which belongs to the Subscription ID entered previously.
   Authorization Method	You can select either Managed Identity or Application Registration as the authorization method for this integration. For Managed Identity, go to the Azure portal and either enable system-assigned managed identity on the VM where App Volumes Manager is installed or add and assign a user-assigned managed identity to the VM. For Application Registration, enter the Tenant ID, Client ID, and Client Secret of the registered App Volumes application.

3. Click Add.

   App Volumes Manager is integrated with Azure Virtual Desktop.

Results

• App Volumes applications with CURRENT packages are automatically synchronized with the Resource Group.

• The App attach package name is derived from the name of the App Volumes application. Such a naming convention helps in identifying the App Volumes application which is synchronized after the integration. However, later, if the name of the application changes in App Volumes Manager, then the App attach package name is not updated in the Azure portal.

  To view the changed name of the App Volumes application, navigate to the App attach package. In the Essentials pane of the App attach package details page, click JSON View, and locate the displayName property. This property indicates the name of the App Volumes application.

What To Do Next

• Entitle Applications in Azure Virtual Desktop

• If a package fails to synchronize, then instead of waiting for the scheduled background job to run, you can manually synchronize the integration.

• Delete an App Volumes Manager Integration with Azure Virtual Desktop