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.
In the pod deployment wizard's screens, you will select the VNet and either:
- Specify the address spaces for subnets that the pod deployer will create in the VNet.
- Specify the subnets you created in advance for use by this pod.
If you do not want to create the subnets in advance, the pod deployer will automatically create the following subnets on your VNet:
- Management subnet, for IP addresses used by the VMs involved in management activities of the pod itself
- Desktop subnet, for IP addresses used for the RDSH server VMs and VDI desktop VMs on that subnet. When the internal Unified Access Gateway configuration is specified in the deployment wizard, the Unified Access Gateway VMs also use IP addresses from this subnet.
Important: The VMs for your VDI desktops, the RDS images, and every server in the pod's RDS farms consume these IP addresses. Because this desktop subnet cannot be extended after the pod is deployed, ensure you set this range large enough to accommodate the number of desktops you anticipate you will want this pod to provide. For example, if you anticipate this pod should provide over 1000 desktops in the future, ensure this range provides for more than that number of IP addresses.
- DMZ subnet, for IP addresses used by the optional external Unified Access Gateway configuration.
When you have the deployer automatically create the subnets, the deployer always creates the new subnets in the VNet. In terms of the VNet's address space, the deployer handles the subnet address spaces you enter into the wizard as follows:
- If you specify address spaces in the wizard that are not already in the VNet's address space, the deployer automatically updates the VNet's configuration to add those address spaces. Then it creates the new subnets in the VNet.
- If the address spaces specified in the wizard are already contained within the VNet's existing address space, the deployer simply creates the new subnets in the VNet using the specified address spaces.
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 (standard global)
- Microsoft Azure Germany
- Microsoft Azure China
- Microsoft Azure US Government
Log in to the portal using the URL appropriate for your account.
- From the Microsoft Azure portal's left navigation bar, click (Virtual networks) and then click Add.
The Create virtual network screen appears.
- Provide the information for the required fields.
Option Description Name Specify a name for the VNet. Address space Specify the VNet's address space. Subscription Select the same subscription that you are planning to use when you deploy the pod. Resource Group You can either choose an existing resource group or have a new one created when the virtual network is created. Location Select the same region into which you are planning to deploy the pod.
Subnet and Address range
Microsoft Azure requires creating one subnet when creating a VNet. You can either retain the default values or customize the name and range. If you want to use this subnet for one of the pod's required subnets, specify the appropriate address range according to the pod deployer requirements. As an example, if you want to use this subnet for the pod's tenant subnet, ensure it has an IP address range to match the /27 minimum that the deployment wizard requires. See Optionally Create the Pod's Required Subnets on your VNet in Microsoft Azure.Important: If you use this subnet for one of the pod's required subnets, you cannot also use it for other resources.Retain the default values for the optional settings.
- Click Create.
The virtual network (VNet) is created in your Microsoft Azure account.
What to do next
If you want to manually create 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 Optionally Create the Pod's Required Subnets on your VNet in Microsoft Azure and 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 Configure the Virtual Network's DNS Server.
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 DNS Requirements for a Horizon Cloud Pod in Microsoft Azure and Ports and Protocols Requirements for a Horizon Cloud Pod at the September 2019 Release's Manifest Level.