You must first deploy a node into your Microsoft Azure capacity and complete some steps in the Administration Console before you begin setting up virtual RDSH server farms, RDSH session-based desktops, and remote RDSH applications in Horizon Cloud and making them available to your end users.
Fulfill the prerequisites, as described in the separate prerequisites checklist document. You can open that document from this PDF link or navigate to it from the Horizon Cloud documentation landing page.
Perform the preparatory tasks outside of Horizon Cloud. See Getting Started with VMware Horizon Cloud Service on Microsoft Azure.
Deploy the node. See Getting Started with VMware Horizon Cloud Service on Microsoft Azure.
Register your Active Directory domain with the deployed node. See Register Your Horizon Cloud Node's First Active Directory Domain.
Upload SSL certificates, if you plan to use VMware Identity Manager™, with or without True SSO, or will have clients connecting directly to the node, not through Unified Access Gateway. See Upload SSL Certificates to a Horizon Cloud Node.
Uploading an SSL certificate is recommended, even if Unified Access Gateway is used and you are not using VMware Identity Manager™. The SSL certificate ensures that clients making direct connections to the node environment can have trusted connections.
Configure an RDS-enabled server master image. See Create a Master Virtual Machine from the Microsoft Azure Marketplace.
In the master image, install the third-party applications you want to provide to your end users from that RDS image and configure other applicable customizations, such as setting desktop wallpaper, install the NVIDIA GPU drivers (for an NV6-based image), and optionally install the User Environment Manager agent.
Convert that master image into an assignable image. See Convert a Configured Master Virtual Machine to an Assignable Image.
Create an RDSH farm to provide remote applications and create assignments to those remote applications. See Farms in Horizon Cloud, Importing New Applications from an RDSH Farm Using Auto-Scan from Farm, and Create a Remote Application Assignment.
When a node is deployed to have Internet-enabled desktops, you must create a CNAME record in your DNS server that maps the fully qualified domain name (FQDN) that you entered in the deployment wizard to the node's load balancer's auto-generated public FQDN.
When a node is deployed with the Internet Enabled Desktops option set to Yes (the default), the deployed Unified Access Gateway is configured with a load balancer IP address that has an auto-generated public FQDN in the form
vmw-hcs-nodeID-uag.region.cloudapp.azure.com, where nodeID is the node's UUID and region is the Microsoft Azure region where the node is located.
In the deployment wizard, you provided:
Your FQDN (for example,
ourApps.ourOrg.example.com). This FQDN is the one which your end users use to access their desktops.
An SSL certificate that is associated with that FQDN and which is signed by a trusted certificate authority.
Your DNS server must map those two FQDNs. When the addresses are mapped, your end users can enter your provided FQDN as the server address in the Horizon Client or use with HTML Access to access their desktops.
For details on how to locate the load balancer's public FQDN in the Administration Console, see Obtain the FQDN of the Node's Load Balancer to Map in your DNS Server.
After the above workflow steps are completed, your end users can launch their assigned RDSH session-based desktops and remote applications using your FQDN in the Horizon Client or with HTML Access.