Entitle users and groups to work in the Windows 365 pool group to onboard their Windows 365 Cloud PC VMs into Horizon Cloud and to create and work with Windows 365 Cloud PC VMs in the service.
Prerequisites
Before performing the steps in this task, complete the following prerequistes in the workflow:
-
Configure default agent settings. See Customize default agent features for new provisioning policies for integrated Windows 365.
-
Map Windows 365 pools to provisioning policies. See Map pools to provisioning policies for integrated Windows 365.
For related information about the sequence of steps for getting started with integrated Windows 365 in Horizon Cloud, see Configuring Windows 365 Integration.
Procedure
-
Open the Windows 365 pool group by selecting Pool Groups from the Horizon Universal Console and selecting the Windows 365 pool group.
-
Open the Entitlements tab and click Entitle.
-
With the Windows 365 pool group selected, click Next.
-
Specify the users and groups to entitle for integrated Windows 365 access and use. These users and groups are considered targets for onboarding their VMs to the Horizon agents.
-
After you entitle users and groups, open the VMs list by clicking Capacity > Pool Groups and opening the VMs tab for the Windows 365 pool group. You will start to see existing Windows 365 VMs being onboarded for those entitled users and groups, if they have assigned VMs in Windows 365.
The VMs tab may also display agent status information such as the following:
- Waiting for Agent Registration - an entitlement instruction has been sent to the Microsoft Azure portal and the user is either awaiting a Cloud PC or awaiting the installation of the Omnissa agent.
- Registering - the agent is installed and is pairing with Horizon Cloud.
- Idle - the agent is installed and functioning, and is ready to accept broker connections from Horizon Clients.
- Active - the user is currently connected to their desktops.
- Pairing Failed - the agent was not able to register.
In addition, registered users will see their Cloud PC desktop name. Entitled user and group names appear in the Assigned User column. For entitled users and groups that do not have assigned VMs in Windows 365, their names appear in the Assigned User column and their row status indicates they do not have assigned VMs.
Note: In Windows 365, all VMs are assigned to a user or group. With your completed integration of Windows 365 in Horizon Cloud and entitlement of these users and groups, the service sends information to Microsoft that the Horizon agent is installed on all of the Windows 365 VMs that are associated with these entitled users and groups.
Note: You can also remove a user entitlement by selecting the user and clicking the Remove option. Removing an entitlement instructs Microsoft to uninstall the agent. When you unentitle a group, all users in that group become unentitled. However, if a user is entitled as an individual user or as a user in a group that will remain entitled, that user does not become unentitled and does not lose access to their VMs.
Note: For related information about disconnecting the integration, see Disconnecting integrated Windows 365 from Horizon Cloud.
Results
This is the final step in the sequence of steps for integrating Windows 365 in Horizon Cloud. After you complete this Windows 365 integration workflow process, users can broker with supported Horizon Clients by using integrated Windows 365 in Horizon Cloud.
Was this page helpful?