Integrating Horizon 7 or Horizon 6 with the Workspace ONE Access service lets you provide users the ability to access their entitled Horizon desktops and applications from the Workspace ONE portal or app. You can integrate independent Horizon pods, which consist of Horizon Connection Server instances, and pod federations, which contain multiple pods and can span multiple sites and data centers.
You deploy and manage desktop and application pools in the Horizon Administrator interface. You also create entitlements for Active Directory users and groups in Horizon, not in Workspace ONE Access. You must sync these users and groups to the Workspace ONE Access service from Active Directory before integrating with Horizon.
To integrate Horizon pods and pod federations with Workspace ONE Access, you create one or more virtual apps collections in the Workspace ONE Access console. The collections contain the configuration information for the pods and pod federations, as well as sync settings. You then sync the Horizon resources and entitlements to Workspace ONE Access.
In the Workspace ONE Access console, you can view the Horizon desktops and applications. You can also view user and group entitlements.
End users can run their entitled desktops and applications from the Workspace ONE portal or app. These desktops and apps can be accessed over HTML in a browser or over a supported display protocol in the Horizon Client.
Workspace ONE Access supports the following versions and features.
- Integrating independent Horizon pods is supported for Horizon 6 and later.
- Integrating pod federations, created using the Cloud Pod Architecture feature, is supported for Horizon 6.2 and later.
- HTML Access is supported for Horizon 6.1.1 and later.
- Certificate SSO is supported for Horizon 7.x.
See the VMware Product Interoperability Matrix for the latest support information.