To configure your pod with multiple tenant subnets, you use the Edit Pod workflow. These subnets are also called VM subnets. This feature where you can use multiple tenant subnets with your pods in Microsoft Azure is available for pod manifests of 2298.0 or later. You add these subnets to the pod's configuration so that you can use them for the VMs in your farms and VDI desktop assignments.
For an overview of the multiple tenant subnets feature, see Overview of Using Multiple Tenant Subnets with Your Horizon Cloud Pod for Your Farms and VDI Assignments.
Verify that the tenant subnets you want to add to the pod are already created in the Microsoft Azure portal. These subnets can be in the same VNet as the pod (the pod manager VMs) or can be in different VNets. If they are in different VNets, those VNets must be peered with the pod's VNet. When using peered VNets, those peered VNets must be in the same subscription and Microsoft Azure region as the pod.
Verify that the tenant subnets are empty. Ensure that no other resource is attached to these subnets.
- Start the Edit Pod workflow from the pod's details page by clicking Edit.
- Move to the Pod Details step and locate the Networking section.
This section displays the pod's current network configuration. The VM Subnet - Additional area displays the VNets found in the pod's subscription. The icons next to each VNet indicate the number of subnets that are already connected to the pod.
- Expand the VNet that has the subnets that you want to add to the pod.
The set of subnets in the VNet are displayed. If you expand the VNet that is also used by the pod, the pod's primary VM subnet has an indicator next to it and it is already selected.
- Select the subnets you want to add.
The following screenshot illustrates that a subnet named
tenantis the pod's primary tenant subnet, and two additional subnets are selected for adding to the pod (
- Click Save & Exit.
As described in Overview of Using Multiple Tenant Subnets with Your Horizon Cloud Pod for Your Farms and VDI Assignments, the system's background tasks run to make the necessary pod configuration changes. When those tasks successfully complete, the subnets appear in the READY state on the pod's details page.
What to do next
- Use the Microsoft Azure portal to add Network Security Groups (NSGs) for these subnets to provide network isolation for them. The Horizon Cloud Edit Pod workflow does not create such NSGs for you.
- With the VM subnets successfully added to the pod, you can start using them with your farms and VDI desktop assignments.