Your Microsoft Azure environment must have an existing virtual network before you can deploy the Horizon Cloud pod into the environment. If you do not already have a virtual network (VNet) in the region into which you are deploying, you must create the virtual network. If you want to have the pod's external gateway deployed into its own VNet — separate from the pod's VNet, you must create that VNet also and then peer the two VNets. If you want to have the pod's external gateway using its own subscription, separate from the pod's, then you must create a separate VNet to use for that external gateway in that subscription and peer the two VNets. Because a single VNet does not span subscriptions, when you deploy an external gateway into its own subscription, that deployment also requires the external gateway to use a VNet that is separate from and peered with the pod's VNet.
| Into which VNet are you deploying the external gateway? | Subnet creation | Subnets needed |
|---|---|---|
| When deploying a pod with the external gateway using the pod's VNet |
For this configuration, you can either create subnets in advance on the VNet and specify those subnets in the pod deployment wizard, or directly type into the wizard the address spaces for the needed subnets and the pod deployer will create the subnets in the VNet.
Important: If your existing VNet is peered, the deployer cannot automatically update the VNet's address space. If the VNet is peered, the best practice is to create the subnets in advance as described in
First-Gen Tenants - In Advance of Pod Deployment, Create the Horizon Cloud Pod's Required Subnets on your VNet in Microsoft Azure. If you do not want to create the subnets in advance and you enter subnet CIDRs in the deployment wizard that are not contained within the VNet's existing address space, the wizard will display an error message and you will need to specify valid subnet address spaces to proceed, or use an unpeered virtual network.
|
Pod deployment using this configuration requires following subnets:
When you have the deployer automatically create the subnets, the deployer always creates the new subnets in the corresponding VNet. In terms of the VNet's address space, the deployer handles the subnet address spaces you enter into the wizard as follows:
|
| When deploying a pod with the choice to have the external gateway using its own VNet or subscription, separate from the pod's VNet or subscription |
For this configuration, because there are two VNets involved and these VNets must be peered, the best practice is to create the subnets in advance on the VNet and specify those subnets in the pod deployment wizard. Create the subnets in advance as described in First-Gen Tenants - In Advance of Pod Deployment, Create the Horizon Cloud Pod's Required Subnets on your VNet in Microsoft Azure. Even though the deployment wizard gives you the option of directly typing into the wizard the address spaces for the needed subnets to have the deployer create the subnets for you, if you specify address spaces that are not already in the VNet's address space, the deployer will not be able to add them to the VNet because it is a peered VNet. In this case, one VNet will have the subnets for the pod and one VNet will have the subnets for the external gateway. Those two VNets must be peered. Let's refer to the pod's VNet as VNet-1 and the external gateway's VNet as VNet-2. For each of these VNets, you can either specify the address spaces for the subnets that the pod deployer will automatically create or specify subnets that you have created in advance. |
In this type of deployment, the pod's VNet (VNet-1) gets a management subnet and a desktop subnet, used for the same purposes as described for when the external gateway is in the pod's own VNet. However, the pod's VNet does not get a DMZ subnet in this configuration because the DMZ subnet is intended for use by the external Unified Access Gateway configuration, which is in the other VNet (VNet-2) in this configuration. In this deployment configuration, the external gateway's VNet gets the following subnets:
|
You perform these steps using the Microsoft Azure portal appropriate for your registered account. For example, there are specific portal endpoints for these Microsoft Azure clouds.
- Microsoft Azure Commercial (standard global regions)
- Microsoft Azure China
- Microsoft Azure US Government
Log in to the portal using the URL appropriate for your account.
Procedure
Results
The virtual network (VNet) is created in your Microsoft Azure account.
What to do next
If you are manually creating the required subnets instead of having the pod deployment process create them, configure the newly created VNet with the subnets you will use for the pod. See the steps in First-Gen Tenants - In Advance of Pod Deployment, Create the Horizon Cloud Pod's Required Subnets on your VNet in Microsoft Azure and First-Gen Tenants - When Using Existing Subnets for a Horizon Cloud Pod in Microsoft Azure.
Configure the newly created VNet with a working DNS service and connectivity to the Active Directory service you will use with your pod. See the steps in First-Gen Tenants - Configure the DNS Server Settings Needed by the VNet Topology You Will Use for Your Horizon Cloud Pods in Microsoft Azure.
Ensure your VNet configuration, in terms of your firewalls and other network behavior, adheres to the pod deployment DNS, ports, and protocols requirements described in First-Gen Tenants - Horizon Cloud on Microsoft Azure Deployments - Host Name Resolution Requirements, DNS Names and First-Gen Tenants - Horizon Cloud Pod - Ports and Protocols Requirements.
