The process of integrating Workspace ONE Access with Horizon Cloud Service on Microsoft Azure with Single-Pod Broker or Horizon Cloud Service on IBM Cloud includes creating one or more virtual apps collections in the Workspace ONE Access console and syncing Horizon Cloud assignments to Workspace ONE Access using the Workspace ONE Access connector. You must also configure SAML authentication to enable trust between the Horizon Cloud tenant and Workspace ONE Access.
This documentation is based on connector version 22.05. If you are using the 19.03.0.1 connector, see earlier versions of the documentation.
Desktop and application pools are configured in the Horizon Cloud environment. You also set user and group entitlements in the Horizon Cloud tenant, not in the Workspace ONE Access service. You must sync these users and groups to the Workspace ONE Access service from Active Directory before integrating Workspace ONE Access with your Horizon Cloud tenant.
To integrate Horizon Cloud with Workspace ONE Access, you create one or more virtual apps collections in the Workspace ONE Access console. The virtual apps collections contain the configuration information for the Horizon Cloud tenants as well as sync settings.
You can set up a sync schedule for each virtual apps collection to regularly sync assignments from the Horizon Cloud tenants to the Workspace ONE Access service.
After you integrate the Horizon Cloud tenants with Workspace ONE Access and sync the virtual apps collection, you can see the Horizon desktops and applications in the Workspace ONE Access console. You can also view user and group entitlements.
End users can launch their assigned desktops and applications from the Workspace ONE Intelligent Hub app or portal. These desktops and applications can be accessed in a browser or in the VMware Horizon® Client™.