This Administration Guide explains how to use VMware Horizon® Cloud Service™ to administer the pods you have onboarded to the cloud service. Your overall Horizon Cloud tenant environment consists of the VMware-hosted cloud service and your pods deployed into their corresponding capacity environments and connected to the cloud service. To work with your tenant environment's fleet of cloud-connected pods and the desktop-as-a-service features that the service provides, you log in to and use the tenant environment's web-based administrative portal named the Horizon Universal Console, or the console for short.

The VMware Horizon services encompass various deployment modes. This document applies when you are using the web-based administrative console to work with a pod fleet in your tenant that consists of one or more of the following pod types:

Horizon pods on a VMware SDDC-based platform
This category encompasses pods based on Horizon Connection Server running within on-premises VMware vSphere installations and cloud-based VMware Cloud on AWS SDDCs, as well as running in Azure VMware Solution (AVS).
Horizon Cloud pods on Microsoft Azure
This category encompasses pods based on the VMware Horizon Cloud pod-manager technology specific for running in Microsoft Azure.

To find out more about all of the various Horizon Cloud deployment modes, see

See for information about how VMware handles information collected through this product.

The information in this document describes how to use the Horizon Cloud capabilities after you have at least one pod in your tenant's pod fleet. For information on how to add your verfy first pod to your tenant, see the Deployment Guide's Deployments and Onboarding to Horizon Cloud for Microsoft Azure and Horizon Pods topic and its subtopics.

Important: This document describes features available in the Horizon Universal Console for the current release of the Horizon Cloud Service working with the connected environments. When you have pods that are not yet updated to the currently supported release level, you will not see all of the features that this document describes when those features depend on the latest pod software level. Also, in a particular release, Horizon Cloud might include separately licensed features. The console reflects the elements related to such features only when your license includes use of such features. When you are not seeing a feature in the console that you are expecting to see, contact your VMware account representative to verify whether your license entitles your use of that feature.

Revision History for these Administrative Topics

This documentation set of topics is updated with each release of the product or when necessary. For the set of significant revisions made to date, see Revision History — Changelog.

Intended Audience

This document is intended for experienced IT system administrators who are familiar with virtual machine technology and datacenter operations.

Depending on your organization's needs and the type of pod you are working with, you might find it helpful to be familiar with these software products, software components, and their features:

  • VMware Horizon
  • VMware Horizon® Cloud Connector™
  • VMware Unified Access Gateway™
  • VMware Workspace ONE® Access™
  • VMware Workspace ONE Hub Services
  • VMware Workspace ONE® UEM
  • VMware Horizon® Client™
  • VMware Horizon® HTML Access™
  • VMware Cloud™ on AWS
  • Microsoft Azure and its Marketplace
  • Azure VMware Solution (AVS)
  • Microsoft Active Directory
  • VMware Dynamic Environment Manager™

About the Screenshots Used in This Document

The screenshots typically:

  • Show only that portion of the overall user interface screen that corresponds to the text at which point the screenshot appears, and not necessarily the full user interface.
  • Have blurred areas where appropriate to maintain data anonymity.
Note: Some screenshots are taken at a higher resolution than others, and might look grainy when the PDF is viewed at 100%. However, if you zoom to 200%, those images start to look clear and readable.

Horizon Cloud Community

Use the following communities to ask questions, explore answers given for questions asked by other users, and access links to useful information.

Contacting VMware Support

Contact VMware Support when you need help with your Horizon Cloud environment.

  • You can submit a support request to VMware Support online using your My VMware® account or by phone.
  • KB 2144012 Customer Support Guidelines provides details for getting support depending on the issue encountered.
  • After you have configured at least one cloud-connected pod, you can submit a support request by logging in to the cloud-based console and clicking Circle help icon in the Horizon Universal Console > Support.

Selected Pod-Related Terminology Used in these Administration Guide Documentation Topics

Throughout the Horizon Cloud documentation topics, you will see the following phrases. These phrases have the indicated meanings as follows.

Horizon pod on VMware SDDC
A pod that is constructed based on VMware Horizon product software, and which includes Horizon Connection Server software components. The Horizon Connection Server components are running in a supported form of an VMware SDDC (software-defined data center) that VMware supports for use with such pods. Some examples of such VMware SDDCs are an on-premises vSphere environment, VMware Cloud on AWS, or Azure VMware Solution, to name a few.
Horizon pod on Microsoft Azure, Horizon Cloud pod on Microsoft Azure, Horizon Cloud pod
A pod that is constructed by running the Horizon Cloud pod deployment wizard which deploys a pod-manager-based pod into your Microsoft Azure subscription. This type of pod is based on VMware Horizon Cloud pod-manager technology, and is supported to run in Microsoft Azure solely.
Note: A Horizon pod on Microsoft Azure is separate and distinct entity from a Horizon pod on Azure VMware Solution (AVS). Those two are based on completely different technology — one is based on Horizon Connection Server technology and one is based on the Horizon Cloud pod-manager technology.
connection broker

A connection broker is responsible for connecting end users' clients with a virtual desktop VM or farm VM for the purpose of setting up a connected session between each end-user client and the agent running in that VM. This noun — broker — is used because one general definition of the noun broker in the English language is one who negotiates a transaction.

In desktop virtualization software's use cases, the connection broker receives the end-user's client request to make a connection with a virtual desktop VM or farm VM. The connection broker then routes the request appropriately and negotiates a connected session between the agent running in one of the VMs and that end-user client. The negotiation takes into consideration what types of pod-provisioned resources the end user is entitled to make connections with.

The Horizon Cloud control plane provides two distinct connection brokering technologies: Universal Broker and Single-Pod Broker (available for Horizon Cloud pods in Microsoft Azure only). Universal Broker is a multi-tenant, cloud-based service that enables the brokering of resources that span multiple pods and makes brokering decisions based on the geographic sites of users and pods. Single-Pod Broker enables the brokering of resources from a single Horizon Cloud pod in Microsoft Azure.

The Horizon Connection Server within a Horizon pod on VMware SDDC, or the pod manager VM within a Horizon Cloud pod in Microsoft Azure, facilitates the routing of the end-user client to a resource in the pod that meets the client's connection request. (Remember that a Horizon pod on Azure VMware Solution actually has the Horizon Connection Server and not the pod manager.)

VMware Information Experience Glossary

VMware Information Experience provides a glossary of terms that might be unfamiliar to you. For definitions of terms as they are used in VMware technical documentation, go to

VMware Privacy Notices

See for information about how VMware handles information collected through this product.