The MAM (Mobile Application Management) solution set allows admins to distribute public and private apps to users on a wide range of Android devices, including older devices that do not support work profiles. MAM only enables the distribution of applications, and doesn't include the device management features of other solution sets.
Feature list
| required feature | optional feature | not supported/not applicable |
1. Device provisioning |
|||
| 1.1. DPC-first work profile provisioning | Android 5.1+ | End users can provision a work profile after downloading their EMM's DPC from Google Play. | |
| 1.7 Google Account work profile provisioning | Android 5.0+ | Customers using Google Workspace or Cloud Identity can set up a work profile with their corporate credentials. | |
2. Device security |
|||
| 2.7. Default security policies | Android 5.0+ | EMMs must enforce the specified security policies on devices by default, without requiring IT admins to configure or customize any settings in the EMM's console. | |
| 2.9. SafetyNet support | N/A | The EMM uses the SafetyNet Attestation API to ensure devices are valid Android devices. | |
| 2.10. Verify Apps enforcement | Android 5.0+ | IT admins can enable Verify Apps on devices. | |
3. Account and app management |
|||
| 3.1. Managed Google Play accounts enterprise enrollment | N/A | IT admins can create a managed Google Play Accounts enterprise—an entity that allows managed Google Play to distribute apps to devices. | |
| 3.2. Managed Google Play account provisioning | Android 5.0+ | The EMM can silently provision enterprise user accounts, called managed Google Play accounts. | |
| 3.4. Managed Google Play account provisioning | Android 5.0 and below | The EMM can silently provision enterprise user accounts, called managed Google Play accounts. | |
| 3.5. Silent app distribution | N/A | IT admins can silently distribute work apps on users' devices without any user interaction. | |
| 3.6. Managed configuration management | Android 5.0+ | IT admins can view and silently set managed configurations for any app that supports managed configurations. | |
| 3.7. App catalog management | N/A | IT admins can import a list of all the apps approved for their enterprise from managed Google Play (play.google.com/work). | |
| 3.8. Programmatic app approval | N/A | The EMM's console uses the managed Google Play iframe to support Google Play's app discovery and approval capabilities | |
| 3.9. Basic store layout management | N/A | End users can use the managed Google Play store app on their device to install and update work apps. | |
| 3.10. Advanced store layout configuration | N/A | IT admins can customize the store layout users see in the managed Google Play store app on their devices. | |
| 3.11. App license management | N/A | IT admins can view and manage app licenses purchased in the managed Google Play from the EMM's console. | |
| 3.12. Google-hosted private app management | N/A | IT admins can update Google-hosted private apps through the EMM console instead of through the Google Play console. | |
| 3.13. Self-hosted private app management | N/A | IT admins can configure and publish self-hosted private apps. | |
| 3.14. EMM pull notifications | N/A | The EMM uses pull notifications to receive Play event notifications in real time | |
| 3.15. Play EMM API usage requirements | N/A | The EMM implements Google's APIs at scale, avoiding traffic patterns that could negatively impact customers' ability to manage apps in production environments. | |
4. Device management |
|||
5. Device usability |
|||
| 5.1. Managed provisioning customization | Android 7.0+ | IT admins can modify the default managed provisioning flow UX to include enterprise-specific features. | |