As part of the process of deploying a Horizon Cloud pod using your Microsoft Azure capacity, a set of resource groups are automatically created in your Microsoft Azure subscription. This topic describes those resource groups and their purpose. You can see these resource groups when you log in to your Microsoft Azure environment using the Microsoft Azure portal. If you deploy the pod's external gateway into its own subscription, the resource groups that support that gateway are created in that subscription.

In the tables in the following sections, the podID refers to the pod's unique identifier. You can find a pod's identifier displayed in the pod's details page, navigating from the Horizon Cloud Administration Console's Capacity page. The poolID refers to the unique identifier for a farm or VDI desktop assignment. The Deployment-ID refers to the unique identifier related to an external gateway when it is deployed using its own VNet, separate from the pod's VNet.

Resource groups that contain VMs also contain the resources associated with those VMs, such as the VMs' network interfaces (NICs), network security groups (NSGs), and similar artifacts. Log in to the Microsoft Azure portal and navigate to the resource group to see the artifacts it contains. For details about the default rules in the NSGs that the pod deployer creates for the pod VMs' NICs, see Default Network Security Group Rules for the VMs in a Horizon Cloud Pod Deployed in Microsoft Azure.

Some resource groups are per pod, while others are created in your Microsoft Azure subscription to contain resources that are used with all of the pods deployed using the same Microsoft Azure subscription. Such cross-pod resource groups are created when the first pod is deployed using that subscription.

Note:
  • Starting with the March 2020 service release, the Horizon Cloud deployer provides for deploying the external Unified Access Gateway configuration into an existing resource group that you create, instead of one automatically created by the deployer. This option is available only when you use a separate subscription for that external Unified Access Gateway configuration. In this scenario, that resource group's naming is controlled by you and your organization, and does not follow the pattern described here.
  • Starting with the October 2020 service release, the Horizon Cloud deployer provides for applying custom Azure resource tags on the resource groups that the deployer creates during the pod deployment and gateway deployment processes. This feature is available when running the workflow to deploy a new pod or when running the workflow to edit a pod to add a new gateway configuration.
  • From November 2020, if your tenant record is configured to use Horizon Infrastructure Monitoring with your pods in Microsoft Azure, when you activate that feature on a pod, the system deploys the Horizon Edge Virtual Appliance in its own resource group, in that pod's subscription.

Per-Pod Resource Groups Created By Horizon Cloud

When custom Azure resource tags are specified in the pod deployment wizard, the deployer applies those specified tags to the following resource groups during the pod deployment process:

  • vmw-hcs-podID
  • vmw-hcs-podID-base-vms

When deploying a gateway configuration, you can optionally choose to have the deployer apply the same Azure resource tags that are specified for the pod or specify different custom resource tags. In either case, the deployer will apply the same set of custom resource tags to the resource groups for both types of gateways.

When creating a farm or VDI desktop assignment, you can specify custom Azure resource tags. The Azure resource tags specified in the farm or assignment creation wizards are applied to the resource groups for those farms or VDI desktop assignments when they are created.

When the Horizon Edge Virtual Appliance is deployed, the deployer applies the pod's custom Azure resource tags to the vmw-hcs-podID-edge resource group.

Resource Group Purpose
vmw-hcs-podID Contains the pod manager VMs and their associated resources.
vmw-hcs-podID-uag Created when the pod has an external Unified Access Gateway configuration. Contains the Unified Access Gateway VMs and their associated resources.
vmw-hcs-podID-uag-internal Created when the pod has an internal Unified Access Gateway configuration. Contains the Unified Access Gateway VMs and their associated resources.
vmw-hcs-podID-base-vms Contains the base image VMs created either by running the Import Virtual Machine from Marketplace wizard or manually, and those VMs' associated resources. After an image VM is published to Horizon Cloud — also known as sealing the image — the VM continues to reside in this resource group along with its associated resources.
vmw-hcs-podID-poolID Contains the VMs for a farm or VDI desktop assignment and those VMs' associated resources. Each time a farm or VDI desktop assignment is created, this resource group is created for it. For every farm or VDI desktop assignment in the pod is one of these resource groups.
vmw-hcs-podID-recovery
Note: As of service release v2111, use of this resource group is deprecated. For new deployments starting from that time, the pod deployer no longer creates this resource group in your Microsoft Azure subscription.

Prior to service release v2201, the pod deployer would create this resource group to hold the storage-related and snapshot-related artifacts that supported the Horizon Cloud pod backup and restore process.

Enhancements to the restore process have resulted in removal of the dependency on this resource group. For existing deployments at manifests prior to manifest 3139.x, the service will automatically delete the existing vmw-hcs-podID-recovery resource group when the deployment is scheduled for its blue-green update to manifest 3139.x or later.

vmw-hcs-podID-edge Contains the Horizon Edge Virtual Appliance and its associated resources.
vmw-hcs-podID-jumpbox This resource group is temporarily created only if you make a support request to VMware and the support team determines the way to service that request is to deploy a temporary jump box VM for communication with the VMware-managed appliances. Permission will be requested from you for such jump box deployment. This resource group and its associated resources are deleted when the support team has completed such work.

Resource Groups Created By Horizon Cloud That Are Specific To an External Gateway Deployed in its Own VNet

When deploying a gateway configuration, you can optionally choose to have the deployer apply the same Azure resource tags that are specified for the pod or specify different custom resource tags. In this scenario where the external gateway is deployed in its own VNet and Azure resource tags are specified in the deployment wizard, the deployer:

  • Applies the custom Azure resource tags that are specified for the pod itself to the vmw-hcs-Deployment-ID resource groups.
  • Applies either the resource tags specified for the pod itself or different ones specified for the gateway to the vmw-hcs-Deployment-ID-nnnnnnnn-nnnn-uag resource group.
Resource Group Purpose
vmw-hcs-Deployment-ID Contains the gateway connector VM and its associated resources. This gateway connector VM is used to connect the Unified Access Gateway instances in this external gateway configuration on its own VNet with the pod manager instances in their own peered VNet.
vmw-hcs-Deployment-ID-nnnnnnnn-nnnn-uag Created when the pod has an external Unified Access Gateway configuration. Contains the Unified Access Gateway VMs and their associated resources. The value nnnnnnnn-nnnn is a unique identifier that corresponds with what is known as the gateway set ID in the Horizon Cloud control plane.
vmw-hcs-Deployment-ID-jumpbox This resource group is temporarily created only if you make a support request to VMware and the support team determines the way to service that request is to deploy a temporary jump box VM for communication with the VMware-managed appliances. Permission will be requested from you for such jump box deployment. This resource group and its associated resources are deleted when the support team has completed such work.

Cross-Pod Resource Groups Created By Horizon Cloud

These cross-pod resource groups are created when the first pod is deployed using that subscription. If custom Azure resource tags are specified in the deployment wizard when the first pod is deployed into the subscription, the pod deployer applies those same custom tags to these resource groups when the deployer creates them.

Resource Group Purpose
vmw-hcs-images-region
Note: As of service release v2201 in February 2022, use of this resource group is deprecated. For new deployments starting from that time, the pod deployer no longer creates this resource group in your Microsoft Azure subscription.

Prior to service release v2201, the pod deployer would create this region-specific resource group the first time that a pod deployment was done in that region. For pods deployed prior to that release, this resource group contains the Horizon Cloud pre-configured VHD files used for configuring a pod's VMs for the pods deployed in a particular Microsoft Azure region (region).

vmw-hcs-diagnostics
Note: As of mid-January 2022, use of this resource group is deprecated. For new pod deployments starting from that time, the pod deployer no longer creates this resource group in your Microsoft Azure subscription.

Prior to mid-January 2022, the pod deployer would create this resource group in the subscription when the first pod deployment was done in that subscription. For pods deployed prior to that time, this resource group is used for the Horizon Cloud diagnostic storage account that contains the pod deployment log files for your subscription's pods.