Azure Resources Created After App Volumes Manager Deployment on Azure

After deploying App Volumes Manager using the Azure Marketplace offer, depending on the administrator choices, some resources are automatically provisioned as part of the Azure Marketplace and a few others can be created by the administrator.

The resources which can be automatically deployed as part of Azure Marketplace are as follows: Azure virtual machine, public IP address, Azure virtual network, Azure storage and file share, Azure private endpoint, and network security group. The rest of the components required are as follows: resource group, subnet, network interface, and database.

Note:

• For more information about any of the Azure resources, see the relevant Microsoft documentation.

• Public IP address and Azure storage and file share are deployed only if you have opted for the automatic provision of these resources.

The following Azure resources are created:

• Azure Virtual Machine

  This resource is based on the latest Windows server OS with App Volumes Manager pre-installed on the virtual machine instance.

• Public IP address

  A public IP address can be used make App Volumes Manager accessible from the public internet by configuring the IP address for the virtual machine which has the pre-installed App Volumes Manager.

  If administrators do not want to make the virtual machine accessible over a public internet, they have the option of selecting the value as None when configuring the IP address in the Azure Marketplace offer wizard.

• Azure Virtual Network

  To ensure connectivity between App Volumes agent (installed on a session host virtual machine) and App Volumes Manager and Azure Storage, a virtual network peering must be configured between the virtual network where the Azure Virtual Desktop host pool is deployed and the virtual network of the virtual machine where the App Volumes Manager is installed.

• Azure Storage and Azure File Share

  These resources are used by App Volumes as application storage for hosting the application packages which are mounted and delivered on Azure Virtual Desktop Host pools.

  Administrators can choose an automatic provision of the storage account and file shares by the Azure Marketplace offer. As a result, the storage is automatically configured. If administrators have opted to use the IP address of the private endpoint to access the storage account, then the UNC path of the delivery and staging file shares contain the IP address and the name of the private endpoint. To find the storage account associated with this IP address, navigate to the Private endpoint in the Azure portal and click the Private link resource. The storage account details are displayed.

  Note: When accessing the storage account from a public network, it is recommended that you perform the following:

  1. Navigate to the Networking tab of the storage account.
  2. In the Firewalls and virtual networks > Public network access section, select Enabled from selected virtual networks and IP addresses.
  3. In the Firewall section, select Add your client IP address. Alternately, administrators can choose to use an existing storage and configure the file shares in the App Volumes Manager admin UI after the deployment.

• Azure Private End Point

  A private end point is required to secure access to the Azure Storage.

• Network Security Group

  The network security group is preconfigured with inbound and outbound firewall rules to allow the following:

  • RDP (Remote Desktop Protocol) access to the virtual machine where App Volumes Manager is installed.
    
    
  • HTTPS access to App Volumes Manager admin UI.
    Note: If you want to access the App Volumes Manager admin UI using HTTP (port 80, insecure), then you can manually configure the inbound port rule in the Azure portal, navigating to the Settings > Networking section of the virtual machine which has App Volumes Manager installed.