A Horizon Cloud environment requires registering at least one Active Directory (AD) domain with the Horizon Cloud pod. This topic describes the configurations that are supported for use with your Horizon Cloud pods in Microsoft Azure.
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.
The supported configurations are:
- On-premises AD server and connecting that on-premises AD with your Microsoft Azure environment using VPN/MPLS or Microsoft Azure Express Route.
- AD server running in your Microsoft Azure environment.
- Using Microsoft Azure Active Directory Domain Services. For an overview of these services that Microsoft Azure provides, see this Azure AD Domain Services article in the Microsoft documentation.
For an in-depth technical description of each supported configuration, some options for each, and the advantages and disadvantages of each, see the VMware technical paper Networking and Active Directory Considerations on Microsoft Azure with VMware Horizon Cloud.
Important: Your fleet of cloud-connected pods can consist of
Horizon Cloud pods in Microsoft Azure along with
Horizon pods installed in the VMware SDDCs (software-defined data centers) that are supported for such pods. As a result, all of those cloud-connected pods must have line of sight to the same set of Active Directory domains. If your pod fleet already consists of cloud-connected
Horizon pods and you are deploying your first
Horizon Cloud pod into Microsoft Azure, you must ensure that pod will be able to have line of sight to the Active Directory domains that are already registered with your
Horizon Cloud environment. See all of the Active Directory-related topics linked from the
Getting Started Using Your Horizon Cloud Environment topic for more details.
