Providing Access to Horizon Cloud Service Desktops and Applications in Omnissa Access

You can integrate your Horizon Cloud Service tenant with your Omnissa Access tenant to provide users the ability to access Horizon Cloud desktops and applications from the Omnissa Intelligent Hub app and portal. This lets you provide users a single place to access all their applications securely from multiple devices.

Types of Horizon Cloud-Omnissa Access Integrations

There are two methods for integrating Horizon Cloud with Omnissa Access. The type of integration method you use depends on the type of Horizon Cloud environment that you have.

• Horizon Cloud Service on Microsoft Azure with Universal Broker environments

  For these environments, you set up the integration between Horizon Cloud and Omnissa Access in the Horizon Cloud administration console. Horizon Cloud assignments are pulled into the Intelligent Hub catalog directly from Horizon Cloud when users log into the Hub portal. Assignments do not have to be synced to Omnissa Access first.

  This integration method is available for Omnissa Access Cloud only. An Omnissa Access connector is required to sync users and groups from Active Directory to your Omnissa Access tenant.

  For information about using this integration method, see Horizon Cloud Environment with Universal Broker - Integrate the Tenant with Omnissa Access and Intelligent Hub Services in the Horizon Cloud Service documentation.

• Horizon Cloud Service on Microsoft Azure with Single-Pod Broker environments, and Horizon Cloud Service on IBM Cloud environments

  For these environments, you integrate Horizon Cloud with Omnissa Access by creating a Virtual Apps collection in the Omnissa Access console and syncing user entitlements from your Horizon Cloud tenant to your Omnissa Access tenant. Administrators can view Horizon Cloud desktops and applications in the Omnissa Access console. End users access their desktops and apps from the Intelligent Hub app or user portal.

  An Omnissa Access connector is required to sync resources and entitlements from Horizon Cloud to your Omnissa Access tenant as well as to sync users and groups from Active Directory to your Omnissa Access tenant.

  Important: Only Omnissa Access connector versions 22.05 and later support integration with Horizon Cloud Service on Microsoft Azure with Single-Pod Broker and Horizon Cloud Service on IBM Cloud environments. For information about the 19.03.0.1 connector, which also supported integration with these types of environments, see the Product Lifecycle Matrix and Knowledge Base article 83996.

  For information about using this integration method, follow the requirements and procedures described in this document. Also see A Horizon Cloud Environment with Single-Pod Brokering — Integrating the Environment's Horizon Cloud Pods in Microsoft Azure with Omnissa Access in the Horizon Cloud Service on Microsoft Azure documentation.

Important: You cannot use both of these integration methods concurrently. If you plan to integrate with Horizon Cloud Service on Microsoft Azure with Universal Broker, you must delete any existing Horizon Cloud virtual apps collections in the Omnissa Access console.