Your users can access the resources in your Horizon Cloud environment that you have entitled to them by pointing their browser to the fully qualified domain name (FQDN) that your organization has configured for end-user connections to those resources.
These steps describe using a browser to launch a desktop provided by the pod.
Note: If integration with a VMware Workspace ONE® Access™ environment is configured, end users might have to access their desktops and remote applications using that environment. See Horizon Cloud Environment with Single-Pod Brokering — Enforce Having End Users Go Through Workspace ONE Access to Access Their Entitled Desktops and Applications.
- Familiarize yourself with the most up-to-date information regarding Horizon HTML Access. For example, to check for up-to-date Horizon HTML Access support information, see the VMware Product Interoperability Matrixes at https://www.vmware.com/resources/compatibility/sim/interop_matrix.php and to see the respective documentation, see the Horizon HTML Access documentation page at https://docs.vmware.com/en/VMware-Horizon-HTML-Access/index.html.
- From your organization's DNS information, obtain the fully qualified domain name (FQDN) that your organization has associated in its domain name system (DNS) for end-user connections to this Horizon Cloud pod in Microsoft Azure, such as
For example, when the pod is configured to use Unified Access Gateway for end-user connections, your organization's DNS has a CNAME record that maps the FQDN configured on the gateway to the Azure load balancer's auto-generated public FQDN. See How to Obtain the Horizon Cloud Pod Gateway's Load Balancer Information to Map in Your DNS Server.
- If you want your end users' Horizon HTML Access clients to retry the connection automatically when the system has to power on the underlying desktop VM or RDSH VM, set the Allow Client to Wait for Powered-Off VM option to Yes. This option is located on the Horizon Universal Console's Broker page. The Horizon HTML Access client starting with version 4.10 has this feature implemented.
- Verify that you have the credentials for a user that has a VDI desktop, session desktop, or remote application assignment.
- Point a browser to a URL of the form https://<desktops-FQDN>, where desktops-FQDN is the fully qualified domain name that was added to your DNS for end-user connections.
For example, if your company's DNS associated an FQDN of myDesktops.example.com, point the browser to https://myDesktops.example.com.
- Sign in using the credentials for a user that has a desktop assignment.