Learning to COPE with AMAPI

Omnissa has improved your Android device management capabilities by integrating with Android Management API (AMAPI). Developed by Google, AMAPI is a new approach to the full mobile device management lifecycle for Android devices in the enterprise. In this new approach, Omnissa Workspace ONE transmits the device’s desired state to AMAPI which in turn pushes policies to the Android Device Policy (ADP) client, which applies them to the device.  In AMAPI, it is ADP, a native component of Android that serves as the primary management application on the device.  

Aside from applying management policies, ADP also transmits device state information to AMAPI, which in turn transmits this to Workspace ONE UEM through Google Pub/Sub.

This Android device management approach allows Omnissa to be more agile in responding to rapidly evolving mobile device management needs and strategies. It also promises to unlock new device management capabilities, like AMAPI’s Lost Mode. 

With the latest iteration of Workspace ONE UEM¹, we have reworked Corporate Owned Personally Enabled (COPE) device management mode using AMAPI. COPE mode allows mobile device administrators to meet security requirements and maintain overall control of the asset, while providing users the privacy to still use it as a personal device. Android achieves this by creating a Work Profile on the device that houses all work data and applications. This delineation prevents data loss by allowing administrators to control communication between work and personal apps. Organizations can only affect the Work profile, where they can remotely push applications and provide secure access to sensitive corporate data.  

To start managing devices in COPE mode using AMAPI, log into your Workspace ONE UEM environment and:  

• Configure enrollment using your method of choice - QR code, Zero-Touch Enrollment, or Knox Mobile Enrollment. 
• Push policies to set passcode requirements, add WiFi configurations, and more.
• Distribute applications to the device through the managed Google Play Store.  

The local APD client guides the end user through administrator policy implications and ensures compliance. 

For a feature comparison between AMAPI and our traditional approach to Android device management, Custom Device Policy Controller (DPC), see Android Management API Support in Workspace ONE UEM (6000185). Stay tuned for upcoming enhancements to our AMAPI integration and join our Early Access community to be the first to see them!  

¹ This integration is available only to customers on Omnissa modern architecture. To learn more about modern architecture, please see this Tech Zone article: Workspace ONE UEM Modernization Wave 1.