You run the pod deployment wizard to deploy the components that together make up a pod-manager-based pod on Microsoft Azure and its gateway configurations. The pod's connector component pairs with first-gen Horizon Cloud so that you can use your Microsoft Azure capacity with Horizon Cloud.

Important: Use this page solely when you have access to a first-gen tenant environment in the first-gen control plane. As described in KB-92424, the first-gen control plane has reached end of availability (EOA). See that article for details.
Important: This wizard deploys the pod-manager-based type of pod into Microsoft Azure. The wizard does not deploy a Horizon pod on Azure VMware Solution (AVS), which uses the Horizon Connection Server technology. For information about manually deploying a Horizon pod on AVS, see Tech Zone's Horizon on Azure VMware Solution Architecture and Deploying Horizon with Azure VMware Solution. For that type of pod, after you have manually deployed such a pod, you can connect it to Horizon Cloud using the Horizon Cloud Connector and the steps in High-Level Workflow When You are Onboarding an Existing Manually Deployed Horizon Pod.
The deployer uses the information you provide in each step of the wizard to determine how to configure the pod. After you provide the requested information in a particular step, proceed to the next step by clicking Next.
Caution: The IP addresses mentioned in these steps are examples. You should use the address ranges that meet your organization's needs. For each step that mentions an IP address range, substitute ones that are applicable for your organization.


Before you start the pod deployment wizard, verify that you have the required items. The items you need to provide in the wizard vary according to the pod configuration options you want. For the prerequisites, see First-Gen Tenants - Prerequisites for Running the First-Gen Pod Deployment Wizard.

Pod configuration options include:

  • Selecting existing subnets that you create in advance or having the pod deployer automatically create the subnets
  • Deploying with an external or internal Unified Access Gateway configuration, deploying with both, or deploy with neither and add them later. If you deploy with only one type of gateway configuration, you can later edit the pod to add the other, non-configured type.
    If you deploy with the Unified Access Gateway configuration as... You can later edit the pod to add...
    External Internal
    Internal External
    None Either type or both types
  • Deploying with an external Unified Access Gateway configuration in its own VNet, separate from the pod's VNet.

    This scenario has these additional variations:

    • Deploying with an external Unified Access Gateway configuration in its own subscription, separate from the pod's subscription. Because VNets do not span subscriptions, this option is a special scenario of the separate VNet case — when the external gateway is deployed using its own subscription, it also means it is in its own VNet.
    • When deploying with an external Unified Access Gateway configuration in its own subscription, you can also choose to deploy it in a named resource group in that separate subscription. In this case, you must pre-create that resource group in the subscription before running the Add Pod wizard.
  • Deploying with the option for two-factor authentication configured on the pod's gateway configurations. If you deploy without two-factor authentication settings configured on the pod's gateway configurations, you can later edit the pod to add the other, non-configured type.
  • For an external Unified Access Gateway configuration, you can optionally select to not have a public IP address on the configuration's load balancer. If you select the wizard option to not have a public IP address on the load balancer, you must specify in the wizard an IP value that you have mapped to an FQDN in your DNS server. That FQDN is the one that will be used in your end users' Horizon clients for PCoIP connections to this gateway. In the deployment process, the deployer will configure that IP address in the Unified Access Gateway's Horizon configuration settings. In the Unified Access Gateway documentation, this IP value is referred to as the PCoIP External URL. Even though the Unified Access Gateway documentation refers to it as a URL, the entered value must be an IP address. You map this IP address to an FQDN in your DNS, which is the FQDN used in your end users' Horizon clients to establish their PCoIP sessions with the pod's external Unified Access Gateway configuration.
    Caution: You cannot later edit the deployed pod to change this IP address setting for the external gateway's load balancer. Therefore, ensure that you input the public IP address in the deployment wizard that matches your DNS mapping with the FQDN, and the FQDN matches the one in the certificate that you upload in the deployment wizard.