First-Gen Tenants - Specify the Microsoft Azure Subscription Information for the New Horizon Cloud Pod

In this step of the pod deployment wizard, you provide the Microsoft Azure subscription information that you want to use for this pod.

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.

Prerequisites

• Verify that you have met the prerequisites described in First-Gen Tenants - Using the First-Gen Horizon Universal Console to Perform an Automated Deployment of a Pod into Microsoft Azure.
• For this wizard step, verify that you have the subscription-related information as described in First-Gen Tenants - Subscription-Related Information for the Horizon Cloud Pod Deployment Wizard.
• Complete the steps in First-Gen Tenants - Start the Pod Deployment Wizard for Deploying a Pod-Manager-Based Pod.

Procedure

1. On the wizard's first step, specify the subscription to use for this pod by selecting the name of a previously entered subscription or entering new subscription information.

   

   If you select an existing subscription, the step is populated with that subscription's information that was previously entered into the system.

   Note: You might wonder why there would be previously entered subscription information when you are deploying a pod from the initial Getting Started page. Previously entered subscription information is possible in situations such as the following examples:

   • You start the wizard, enter subscription information in this first wizard step, and click Add to submit the subscription information to the system and progress forward in the wizard. Then on a subsequent step, you cancel out of the wizard before completing all of the steps. In this situation, the system has saved the subscription information you entered in this first wizard step after you clicked Add. Even though you cancel out of the wizard in a subsequent step, the system retains that previously entered subscription information.
   • You used this Horizon Cloud customer account record before, deploying first and subsequent pods for that account record, and then at some point in time, deleted those pods. When you log back in with the credentials that are associated with your Horizon Cloud customer account record, subscription information that was previously entered is still associated with that customer record, and previous subscription names are displayed in the drop-down list.

   Option	Description
   Apply Subscription	Select the name of a previously entered subscription or select Add New to enter new subscription information.
   Subscription Name	When providing new subscription information, enter a friendly name so you can identify this subscription from other previously entered subscriptions. The name must start with a letter and contain only letters, dashes, and numbers.
   Environment	Select the cloud environment associated with your subscription, for example: Azure - Commercial, for the standard global Microsoft Azure cloud regions Azure - China, for the Microsoft Azure in China cloud Azure - US Government, for the Microsoft Azure US Government cloud
   Subscription ID	Enter your cloud capacity subscription ID (in UUID form). This subscription ID must be valid for the environment you selected. For Microsoft Azure, you can obtain this UUID from your Microsoft Azure portal's Subscriptions area.
   Directory ID	Enter your Microsoft Azure AD Directory ID (in UUID form). For Microsoft Azure, you can obtain this UUID from your Microsoft Azure Active Directory properties in the Microsoft Azure portal.
   Application ID	Enter the application ID (in UUID form) associated with the service principal you created in the Microsoft Azure portal. Creating an application registration and its associated service principal in your Microsoft Azure Active Directory is a prerequisite.
   Application Key	Enter the key value for the service principal's authentication key that you created in the Microsoft Azure portal. Creating this key is a prerequisite.
   Use a Different Subscription for External Gateway	Enable this toggle when you want to deploy an external Unified Access Gateway configuration into its own subscription, separate from the pod's subscription. Using separate subscriptions for the external gateway gives your organization the flexibility to assign separate teams control over those subscriptions, depending on their area of expertise. It allows for more granular access control for which people in your organization can access the pod's assets in its subscription's resource groups and which people can access the gateway's assets. When this toggle is turned on, the fields for entering the gateway's subscription information are displayed. Specify the information in those fields as you did for the pod's subscription.

   Important: This screen does not provide a way to delete the previously entered subscription values associated with a particular Subscription Name. Even though this occurrence is rare, you might imagine a situation where you:

   1. Set up the subscription-related pieces in Microsoft Azure.
   2. Start the Add Cloud Capacity wizard, enter those subscription values in the first step, and progress on to the next wizard step.
   3. However, upon reading the networking values requested in the next wizard step, you cancel out of this wizard and open a new browser tab to go into the Microsoft Azure portal and adjust your networking configuration to meet the prerequisites.
   4. While in the Microsoft Azure portal, you then also decide to make a new application registration to have a service provider with a different name.
   5. You return to the browser that has the Getting Started page and restart the Add Cloud Capacity wizard. At this point, your previously entered subscription name is still in the Apply Subscription drop-down list. However, if you select that name, all of the fields are prepopulated with the previous values, including the old application ID, and there is not a way within this specific screen to change the values, or edit or delete that subscription name to start over with the same name. If this happens to you, first cancel out of the wizard. Then navigate to the console's Getting Started page, click Manage > Manage Subscriptions, and use the Delete action to delete that previously entered subscription name. Then you can start the new-pod wizard again, enter the values you want to use, and proceed forward.

   The following screenshot is an example with the main subscription details completed.

   

2. Proceed to the next wizard step.

   When you click the button to proceed to the next step, the system verifies the validity of all of the specified values and whether they are appropriately related to each other, such as:

   • Is the specified subscription ID valid in the selected environment.

   • Are the specified directory ID, application ID, and application key valid in that subscription.

   • Is the application's service principal for the specified application ID assigned a role that permits all of the operations that the deployment process requires for the type of deployment you are doing. For a description of the service principal and its role requirements, see the topic First-Gen Tenants - Create the Horizon Cloud App Registration and First-Gen Tenants - When Your Organization Prefers to Use a Custom Role for the First-Gen Horizon Cloud App Registration. If you see an error message about correcting values, at least one of the values is invalid either by not existing in your subscription or not having a valid relationship with another of the values. Here is a list of some, though not necessarily all, situations that can result in that error message:

   • If you specified a Directory ID that is in your subscription but you specified an Application ID value that is in a different directory.

   • If the specified service principal's assigned role does not permit the operations that the pod deployer requires. Important: More than one piece might be invalid when that error message appears. If you see that error message, verify the subscription-related information that you collected and the configuration of the service principal.

3. Specify pod details and networking information by following the steps in First-Gen Tenants - Specify Pod Configuration Information for the Horizon Cloud Pod You Are Deploying Into Microsoft Azure Using the Deployment Wizard.

Previous topic:First-Gen Tenants - Start the Pod Deployment Wizard for Deploying a Pod-Manager-Based Pod

Next topic:First-Gen Tenants - Specify Pod Configuration Information for the Horizon Cloud Pod You Are Deploying Into Microsoft Azure Using the Deployment Wizard