Workflow for deploying App Volumes Manager using Azure Marketplace

Use the Azure Marketplace offer to deploy an Azure virtual machine image with App Volumes Manager already installed and partially configured. Additionally, you can also use this offer to integrates Azure Virtual Desktop with App Volumes Manager.

As an administrator, you must perform the rest of the configuration using the App Volumes Manager admin UI.

Note: When using any of the Microsoft applications in the procedure described in this task, see the relevant Microsoft documentation. However, ensure that you follow specific configurations required for deploying Omnissa App Volumes on Azure.

Prerequisites

• Ensure that you have read through the Configuration Scenarios of Azure Virtual Desktop Integration with App Volumes Manager.

  See Configuration Scenarios of Azure Virtual Desktop Integration with App Volumes Manager.

• Ensure that you are aware of the requirements necessary for this workflow.

  For more information about these requirements, see Prerequisites for Deploying App Volumes Manager through Azure Marketplace.

• After the deployment, some Azure resources such as Azure virtual machine, public IP address, Azure virtual network and so on are created. For a better understanding of these Azure resources, see Azure Resources Created After App Volumes Manager Deployment on Azure.

• If you want to use an existing virtual network when configuring the basic details for deploying App Volumes using Azure Marketplace, ensure that you have created a virtual network which can be used in the Azure subscription.

  When deploying App Volumes in the Azure Marketplace, the same virtual network is required so that other components in the Azure infrastructure such as virtual machines (active directory domain services and App Volumes Manager) and file share can communicate with each other. It is recommended that all virtual machines reside in the same region as the virtual network.

  For information about how to create a virtual network, see the corresponding Microsoft documentation.

• If you intend to integrate App Volumes Manager with Azure Virtual Desktop, then ensure that you have the following permissions:

  • Microsoft.Authorization/roleDefinitions/write

  • Microsoft.Authorization/roleAssignments/write

  • Microsoft.ManagedIdentity/userAssignedIdentities/assign/action

  • Microsoft.ManagedIdentity/userAssignedIdentities/read

Procedure

1. In the Microsoft Azure portal, click Marketplace.

2. Search for the App Volumes: Apps on Demand offer.

3. Click the offer.

4. Follow the prompts.

5. Click Create.

6. In the Create App Volumes window, create a virtual machine that runs Windows:

   1. In the Basics tab, enter the following:

      Fields	Values
      Project Details	To manage deployed resources, select the Subscription and Resource group. Alternately, you can also create a new resource group.
      Instance details	Enter the Region. Enter the name of the virtual machine. To remote desktop into the App Volumes Manager virtual machine, enter the credentials (user name and password) for the local administrator. Optional: Change the default size of the virtual machine as per the options provided. By default, a new public IP address is created. Alternately, you can also select any existing IP address for the virtual machine. Note: If you do not want to use a public IP address for the App Volumes Manager virtual machine, select None. Depending on the public IP address created previously, you can create a DNS prefix for the public IP address. If you choose to access the App Volumes Manager admin UI in a browser using a public IP address, then you can keep the DNS name handy.
      Configure virtual networks	By default, a new virtual network and a corresponding subnet are created. Alternately, you can select an existing virtual network and the corresponding subnet.

   2. Click Next.

   3. In the App Volumes configuration tab, select the desired database:

      Options	Steps
      Local SQL Server Express Database	This is the default option. No further action required. Note: It is not recommended to use this option for production environment.
      Remote SQL Server database	Enter the Database connection details as follows: Enter the Host name. Enter the Database Name. Enter the Username and Password of the user account used to access the Remote SQL Server database. Optional: If you have the relevant certificate to validate the SSL connection to SQL server, select the Enable SQL Server certificate validation check box. By default, this check box is selected. Note: If you do not have a relevant certficate to validate the SSL connection to SQL server, then clear the Enable SQL Server certification validation check box. To upload SQL Server certificate, click the folder icon and browse to a local directory where the CA certificate is present. Select the file and click Open.

   4. Configure the File Share details section:

      The following options are presented:

      • If you want the Azure Marketplace offer to automatically provision storage with file shares, then perform the following:

        1. Select Create new file shares.

           This is the default option.

        2. Depending on your requirement:

           Option	Procedure
           Leave the Integrate with private DNS zone check box blank	The Azure Marketplace offer uses the IP address of the private endpoint as the file share address. This is the default option.
           Select the Integrate with private DNS zone check box	As prerequisites, ensure that the following is configured: Create a private DNS zone with the instance name as privatelink.file.corewindows.net. In the private DNS zone, add the virtual network of the domain controller as the virtual network link. Adding the virtual network as the virtual network link ensures successful name resolution of the file storage account to the IP address of the private endpoint. Select an existing Private DNS Zone.

      • If you want to use an existing storage, then select Use existing file shares.

        After the Azure Marketplace offer is deployed, you must manually configure the storage in App Volumes Manager admin UI using existing file shares.

   5. Select the AVD Integration check box, then perform the following steps:

      Note: Ensure that you use App Volumes agent 2410 and later versions only.

      1. Enter the Entra ID details of the application that you registered earlier.

      2. Select the desired Managed Identity Type.

         Option	Description
         System assigned	System assigned managed identity is automatically created. App attach packages are granted access at the same resource group level where the App Volumes Manager gets deployed.
         User assigned	Manually create a user assigned managed identity. App Volumes Manager requires these permissions to create and manage App attach packages for these resource groups. Note: Ensure that the following permissions are set for the resource group: Microsoft.Authorization/permissions/read Microsoft.Resources/subscriptions/resourceGroups/read Microsoft.DesktopVirtualization/appattachpackages/read Microsoft.DesktopVirtualization/appattachpackages/write Microsoft.DesktopVirtualization/appattachpackages/delete Click Add. In the Add user assigned managed identity window, select the desired Subscription and User assigned managed identities. Click Add.

   6. Click Next.

   7. In the Tags tab, create the desired tags.

   8. Click Review + Create.

   9. To start the deployment, click Create.

      Results

      • Depending on the options you have chosen in the previous steps, the Azure Marketplace offer deploys all or some of the resources: Azure virtual machine, public IP address, virtual network, Azure storage and file share, private endpoint, and network security group.
      
      
      • Ensure that you make note of the App Volumes Manager IP address and port number. This information is required when you use the Azure Marketplace offer to deploy an Azure virtual machine image with App Volumes agent installed.

What to do next

• For installing App Volumes agent, see Install App Volumes Agent.

• If you have skipped the automatic storage provisioning (Use existing file shares), then you must manually add existing file shares to App Volumes Manager using the admin UI.

  For this configuration see Configure and Register the Machine Manager.

• Complete the rest of the App Volumes Manager configuration. See Configuring App Volumes Manager.

  Note:

  • Ensure that you configure the integration between App Volumes Manager and Azure Virtual Desktop from within App Volumes Manager. See Configure App Volumes Manager Integration with Azure Virtual Desktop.

  • If you want to edit the registered Entra ID domain, see Register a Domain.

• If all your entities are in Active Directory, then use Microsoft Entra Connect to synchronize entities with Microsoft Entra ID.

  For more information about Microsoft Entra Connect, see the Microsoft documentation.