A VMware Horizon Cloud Service on Microsoft Azure environment combines the management simplicity of the Horizon Cloud control plane with the economics of Microsoft Azure. You connect your Microsoft Azure subscription to Horizon Cloud to manage and deliver virtual RDS-enabled Windows servers and remote applications. Setting up the environment involves deploying the required VMware software into your Microsoft Azure capacity. The deployed VMware software creates an appropriately configured entity, called a Horizon Cloud node, which pairs with the control plane. After the node is deployed, then you use the control plane to create RDSH farms and entitle remote desktops and applications to your end users.

VMware Horizon Cloud Service on Microsoft Azure Architecture

Horizon Cloud is a control plane that VMware hosts in the cloud. This cloud service enables the central orchestration and management of remote desktops and applications in your Microsoft Azure capacity.

VMware is responsible for hosting the service and providing feature updates and enhancements for a software-as-a-service experience.

The cloud control plane also hosts a common management user interface referred to as the Horizon Cloud Administration Console, or Administration Console for short. The Administration Console runs in industry-standard browsers and provides IT administrators a single location for management tasks involving user assignments and the virtual desktops, remote desktop sessions, and applications. The Administration Console is accessible from anywhere at any time, providing maximum flexibility.

Node Deployment in Microsoft Azure

A Horizon Cloud node, or node for short, has a physical regional location in a Microsoft Azure cloud. In the node deployment wizard, you select where to place the node, according to the regions available for your particular Microsoft Azure subscription. You also select an existing virtual network (vnet) that the node will use in your selected region.

You can deploy more than one node and manage all of them from the Horizon Cloud Administrator Console. The nodes you deploy after the first one can reuse the same vnet as your first node or use different vnets. Also, each node can be in a different Microsoft Azure region, using a vnet in that region.

The node deployment process automatically creates a set of resource groups in your Microsoft Azure capacity. Resource groups are used to organize the assets that the environment needs, such as:

  • Virtual subnets

  • VMs for the node manager instance

  • VMs for the Unified Access Gateway and load balancer instances

  • VMs for the master RDS-enabled server images

  • VMs for the assignable (published) images that are made from the master images

  • VMs for the RDSH farms that provide the remote desktops and remote applications

  • Additional assets that the VMs and the environment require for supported operations, such as network interfaces, IP addresses, disks, and various items along those lines.

All of the resource groups created by Horizon Cloud in your Microsoft Azure environment are named using the prefix vmw-hcs.

In the following diagram, RG means resource group.



Architecture illustration of the node's resource groups, VMs, and subnets


Microsoft Azure Terminology and References

The VMware Horizon Cloud Service on Microsoft Azure product documentation uses the applicable Microsoft Azure terminology as appropriate in the descriptions and task steps of the VMware Horizon Cloud Service on Microsoft Azure workflows. If the Microsoft Azure terminology is unfamiliar to you, you can use the following applicable references in the Microsoft Azure product documentation to learn more.

Note:

All capitalization and spelling in the citations below follow the same capitalization and spelling found in the linked-to articles in the Microsoft Azure documentation itself.

Table 1. References in the Microsoft Azure Documentation That Relate to Your Use of Horizon Cloud

Useful Microsoft Azure References

Description

Microsoft Azure glossary: A dictionary of cloud terminology on the Azure platform

Use this glossary to learn the meaning of terms as used in the Microsoft Azure cloud context, for terms such as load balancer, region, resource group, subscription, virtual machine, and virtual network (vnet).

Note:

The Microsoft Azure glossary does not include the term service principal because the service principal is a resource automatically created in Microsoft Azure when an application registration is created in Microsoft Azure. The purpose of making an application registration in your Microsoft Azure subscription is because that is the way you authorize Horizon Cloud as an application to use your Microsoft Azure capacity. The application registration and its companion service principal enable the Horizon Cloud cloud service acting as an application to access resources in your Microsoft Azure subscription. Use the next reference below to learn about applications and service principals that can access resources in Microsoft Azure.

Use portal to create an Azure Active Directory application and service principal that can access resources

Use this article to learn about the relationship between an application and a service principal in a Microsoft Azure cloud.

Azure Resource Manager overview

Use this article to learn about the relationships between resources, resource groups, and the Resource Manager in Microsoft Azure.

Azure VNet

Use this article to learn about the Azure Virtual Network (VNet) service in Microsoft Azure. See also Azure Virtual Network FAQs.

Azure VNet Peering

Use this article to learn about virtual network peering with the Azure VNet.