The VMware AirWatch Cloud Connector provides organizations with the ability to integrate Workspace ONE UEM with their back-end enterprise systems. This documentation describes setting up AirWatch Cloud Connector for on-premises and SaaS deployments.

In an on-premises deployment, your organization hosts all Workspace ONE UEM components and servers on its internal networks. For on-premises deployments, before proceeding with this guide, you should have read and performed the procedures in the VMware AWCM Guide. In a SaaS deployment, certain Works components are hosted in the cloud. If you are unsure whether your deployment is on-premises or SaaS, contact a VMware support representative.

The VMware AirWatch Cloud Connector runs in the internal network, acting as a proxy that securely transmits requests from Workspace ONE UEM to the organization's critical enterprise infrastructure components. This allows organizations to leverage the benefits of VMware Mobile Device Management (MDM), running in any configuration, together with those of their existing LDAP, certificate authority, email, and other internal systems. Refer to the VMware AirWatch Cloud Connector Architecture for more information.

The VMware AirWatch Cloud Connector integrates with the following internal components:

  • Email Relay (SMTP)

  • Directory Services (LDAP/AD)

  • Email Management Exchange 2010 and later (PowerShell)

  • Lotus Domino Web Service (HTTPS)

  • Syslog (Event log data)

  • Microsoft Certificate Services (PKI)

  • Simple Certificate Enrollment Protocol (SCEP PKI)

  • Third-party Certificate Services (on-premises only)