Android Enterprise feature list

This page lists the complete set of Android Enterprise features.

In most cases, your EMM solution needs to support all the standard features (star) of at least one solution set before it can be made commercially available. EMM solutions that pass standard feature verification are listed in Android's Enterprise Solutions Directory as offering a Standard Management Set.

An additional set of advanced features is available for each solution set. These features are denoted in each solution set page: work profile, fully managed device, dedicated device, and mobile application management (MAM). EMM solutions that pass advanced feature verification are listed in Android's Enterprise Solutions Directory as offering an Advanced Management Set.

Select your development method to load the appropriate feature list:


Key

star standard feature star_border optional feature remove_circle_outline not applicable

1. Device provisioning

1.1. DPC-first work profile provisioning

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.1+
star
remove_circle_outline
remove_circle_outline
star

End users can provision a work profile after downloading their EMM's DPC from Google Play.

1.1.1. The EMM's DPC must be publicly available on Google Play, and an end user must be able to install the DPC from the personal side of their device.

1.1.2. Once installed, the DPC must guide the user through the process of provisioning a work profile.

1.1.3. After provisioning is complete, no management presence can remain on the personal side of the device.

  • Any policies put in place during provisioning must be removed.
  • All Device Admin or other app privileges must be revoked.
  • The EMM's DPC must be, at minimum, disabled on the personal side of the device.

1.2. DPC-identifier device provisioning

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
remove_circle_outline
star
star
remove_circle_outline

End users can provision a fully managed or dedicated device using a DPC identifier (e.g. "afw#"), according to the implementation guidelines defined in the Play EMM API developer documentation.

1.2.1. The EMM's DPC must be publicly available on Google Play, and the end user must be able to install the DPC from the device setup wizard by entering a DPC-specific identifier.

1.2.2. Once installed, the EMM's DPC must guide the user through the process of provisioning a fully managed or dedicated device.

1.3. NFC device provisioning

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can "bump" new or factory-reset devices with the EMMs NFC provisioning app to provision a device, according to the implementation guidelines defined in the Play EMM API developer documentation.

1.3.1. The NFC provisioning app must be published to Google Play, and must use provisioning extras to pass all non-sensitive registration details (e.g. server IDs, enrollment IDs) to a device. Registration details shouldn't include sensitive information, such as passwords or certificates.

1.3.2. After the EMM's DPC sets itself as the device owner, the DPC must launch immediately and lock itself to the screen until the device is fully provisioned.

1.4. QR code device provisioning

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can use new or factory-reset device to scan a QR code generated by the EMM's console to provision the device, according implementation guidelines defined in the Play EMM API developer documentation.

1.4.1. The QR code must use provisioning extras to pass all non-sensitive registration details (e.g. server IDs, enrollment IDs) to a device. Registration details must not include sensitive information, such as passwords or certificates.

1.4.2. After the EMM's DPC sets itself as the device owner, the DPC must launch immediately and lock itself to the screen until the device is fully provisioned.

1.5. Zero-touch enrollment

Android version
Work profile
Fully managed device
Dedicated device
MAM
8.0+ (Pixel 7.1+)
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can preconfigure devices purchased from authorized resellers and manage them using your EMM console.

1.5.1. IT admins can provision company-owned devices using the zero-touch enrollment method, outlined in Zero-touch enrollment for IT admins.

1.5.2. When a device is first turned on, the device is automatically forced into the settings configured by the IT admin.

1.6. Advanced zero-touch provisioning

Android version
Work profile
Fully managed device
Dedicated device
MAM
8.0+ (Pixel 7.1+)
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can automate much of the device enrollment process by deploying DPC registration details through zero-touch enrollment. The EMM's DPC supports limiting enrollment to specific accounts or domains, according to the configuration options offered by the EMM.

1.6.1. IT admins can provision a company-owned device using the zero-touch enrollment method, outlined Zero-touch enrollment for IT admins.

1.6.2. After the EMM's DPC sets itself as the device owner, the EMM's DPC must launch immediately and lock itself to the screen until the device is fully provisioned.

  • This requirement is waived for devices that use zero-touch enrollment registration details to fully provision themselves silently (for example, in a dedicated device deployment).

1.6.3. Using the registration details, the EMM's DPC must ensure that only authorized users can proceed with activation once the DPC is invoked. At a minimum, activation must be locked down to all users of a given customer.

1.6.4. Using the registration details, the EMM's DPC must make it possible for IT admins to pre-populate all registration details (for instance server IDs, enrollment IDs) aside from unique user or device credentials (for instance username/password, activation token), so that users don't have to enter details when activating a device.

  • EMMs must not include sensitive information, such as passwords or certificates, in the zero-touch enrollment's configuration.

1.7. Google Account work profile provisioning

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
remove_circle_outline
remove_circle_outline
star_border

For customers that use G Suite, this feature guides users through the setup of a work profile after entering their corporate G Suite credentials during device setup or on a device that is already activated. In both cases, the corporate G Suite identity will be migrated into the work profile.

1.7.1. End users can provision a work profile using the Google Account provisioning method, according to the defined implementation guidelines.

1.8 Google Account device provisioning

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
star_border
remove_circle_outline
remove_circle_outline

For customers that use G Suite, this feature guides users through the installation of their EMM's DPC after they enter their corporate G Suite credentials during initial device setup. Once installed, the DPC completes the setup of a fully managed device.

1.8.1. End users can provision a fully managed device using the Google Account provisioning method, according to the defined implementation guidelines.

1.8.2. Unless the EMM can unequivocally identify the device as a corporate asset owned by the enterprise customer, the device cannot be provisioned without prompting the user during the provisioning process to take a non-default action such as checking a checkbox or selecting a non-default menu choice. It is recommended that the EMM is able to identify the device as a corporate asset so that the user does not need to be prompted.


2. Device security

2.1. Device security challenge

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star
star
star
remove_circle_outline

IT admins can set and enforce a device security challenge (e.g. PIN/pattern/password) of a certain type and complexity on managed devices.

2.1.1. Device security challenge settings must be enforced by the EMM's DPC.

2.2 Work security challenge

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
star
remove_circle_outline
remove_circle_outline
remove_circle_outline

IT admins can set and enforce a security challenge for apps and data in the work profile that is separate and has different requirements from the device security challenge (2.1.).

2.2.1. The work profile security challenge must be enforced by the EMM's DPC.

2.3. Advanced passcode management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
star_border
star_border
star_border

IT admins can configure advanced password settings on devices.

2.3.1. The following password quality types can be set for each lock screen available on a device by the EMM's DPC:

    1. Unspecified: Sets no password requirement.
    2. Something: Requires a password but doesn't set a type restriction.
    3. Weak biometric: Allows low-security biometric unlock methods, such as face recognition.
    4. Numeric: Requires a password that includes numeric characters.
    5. Numeric complex: Requires a password that includes numeric characters and has no repeating (for example, 4444) or ordered sequences (for example, 1234).
    6. Alphabetic: Requires a password that includes alphabetic or other symbol characters.
    7. Alphanumeric: Requires a password that includes both numeric and alphabetic (or other symbol) characters.
    8. Complex: Requires a password that includes a numeric, alphabetic, and special character.

2.3.2. The following password length and complexity requirements can be set for each lock screen available on a device by the EMM's DPC (guidance linked below):

    1. Minimum length required for a valid password.
    2. Minimum number of numeric characters required for a valid password.
    3. Minimum number of non-letter characters required for a valid password.
    4. Minimum number of letters required for a valid password.
    5. Minimum number of lowercase letters required for a valid password.
    6. Minimum number of uppercase letters required for a valid password.
    7. Minimum number of symbols required for a valid password.

2.3.3. The EMM's DPC can configure the following password lifecycle settings for each lock screen available on a managed device:

    1. Password expiration timeout: Coupled with the compliance enforcement feature, this forces the user to periodically update their password according to the admin-specified timeout. IT admins must be able to disable this feature.
    2. Password history length: Specifies the length of time before a user can re-use any given password. IT admins must be able to disable this feature.
    3. Maximum failed passwords for wipe: Specifies the number of times the user can enter an incorrect password before corporate data is wiped from the device. IT admins must be able to disable this feature.

2.3.4. IT admins can remotely reset a users' device and/or profile passcode using the EMM's DPC.

2.4. Smart lock management

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
star_border
star_border
star_border
remove_circle_outline

IT admins can control what trust agents in Android's Smart Lock feature are permitted to unlock devices. Admins can disable specific unlock methods like trusted bluetooth devices, face recognition, and voice recognition, or optionally disable the feature entirely.

2.4.1. IT admins can disable all Smart Lock trust agents, independently for each lock screen available on the device.

2.4.2. IT admins can selectively enable and configure Smart Lock trust agents, independently for each lock screen available on the device, for all of the following trust agents: bluetooth, NFC, places, face, on-body, and voice.

2.5. Wipe and lock

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star
star
star
star

IT admins can use the EMM's console to remotely lock and wipe work data from a managed device.

2.5.1. Devices must be locked by the EMM's DPC.

2.5.2. Devices must be wiped by the EMM's DPC.

2.6. Compliance enforcement

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star
star
star
star

If a device is not in compliance with security policies, access to work data is automatically restricted.

2.6.1. At minimum, the security policies enforced on a device must include password policy. Guidance for Play EMM API users is available in the EMM Community site.

2.7. Default security policies

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star
star
star
star

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. EMMs are encouraged (but not required) to not allow IT admins to change the default state of these security features.

2.7.1. Installing apps from unknown sources must be blocked by the EMM's DPC.

2.7.2. Access to debugging features must be blocked by the EMM's DPC.

2.8. Security policies for dedicated devices

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
remove_circle_outline
remove_circle_outline
star
remove_circle_outline

Users cannot escape a locked down dedicated device to enable other actions.

2.8.1. Booting into safe mode must be disabled by default by the EMM's DPC.

2.8.2. The EMM's DPC must be launched and locked to the screen immediately on first boot during provisioning, to ensure users do not interact with the device in any other way.

2.8.3. The EMM's DPC must be set as the default launcher to ensure whitelisted apps are locked to the screen on boot, according to the defined implementation guidelines.

2.9. SafetyNet Support

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star_border
star_border
star_border
star_border

The EMM uses the SafetyNet Attestation API to ensure devices are valid Android devices.

2.9.1. The EMM's DPC implements the SafetyNet Attestation API during provisioning, before adding corporate data to a device, by confirming that the basicIntegrity and ctsProfileMatch values return true.

2.9.2. The EMM's DPC can send a compatibility check every time a device checks in with the EMM's server, configurable by the IT admin, and can verify the APK information in the compatibility check response as well as response itself before updating corporate policy on the device

2.9.3. IT admins can configure different policy responses based on the values returned by SafetyNet, including blocking provisioning or wiping corporate data.

  • If the device or requesting APK fails any validation, access to corporate data is blocked, according to the compliance enforcement feature requirements.

2.10. Verify Apps enforcement

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
star_border
star_border
star_border

IT admins can enable Verify Apps on devices. Verify Apps scans apps installed on Android devices for malware before and after they're installed, helping to ensure that corporate data can't be compromised by malicious apps.

2.10.1. Verify Apps must be enabled by default by the EMM's DPC.

2.11. Direct Boot support

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
star_border
star_border
star_border
star_border

Apps can't run on Android 7.0+ devices that have just been powered on until the device is first unlocked. Direct Boot support ensures that the EMM's DPC is always active and able to enforce policy, even if the device has not been unlocked.

2.11.1. The EMM's DPC leverages device encrypted storage to perform critical management functions before the DPC's credential encrypted storage has been decrypted. Management functions available during Direct Boot must include (but are not limited to):

2.11.2. The EMM's DPC must not expose corporate data within device encrypted storage.

2.12. Hardware security management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.1+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can lock down hardware elements of a device to ensure data-loss prevention.

2.12.1. IT admins can block users from mounting physical external media on their device.

2.12.2. IT admins can block users from sharing data from their device using NFC beam.

2.12.3. IT admins can block users from transferring files over USB from their device.

2.13. Enterprise security logging

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can gather usage data from devices that can be parsed and programmatically evaluated for malicious or risky behavior. Activities logged include Android Debug Bridge (adb) activity, app launches, and screen unlocks.

2.13.1. IT admins can enable security logging for target devices, and the EMM's DPC must be able to retrieve both security logs and pre-reboot security logs automatically.

2.13.2. IT admins can review enterprise security logs for a given device and configurable time window, in the EMMs console.

2.13.3. IT admins can export enterprise security logs from the EMMs console.


3. Account and app management

3.1. Managed Google Play accounts enterprise enrollment

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star
star
star
star

IT admins can create a managed Google Play Accounts enterprise—an entity that allows managed Google Play to distribute apps to devices. The following enrollment stages must be integrated into the EMM's console:

3.1.1. Enroll a managed Google Play Accounts enterprise using the Play EMM API.

3.1.2. The EMM's console must silently provision and configure a unique ESA for each enterprise.

3.1.3. Un-enroll a managed Google Play Accounts enterprise using the Play EMM API.

3.2. Managed Google Play account provisioning

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star
star
remove_circle_outline
star

The EMM can silently provision enterprise user accounts, called managed Google Play accounts. These accounts identify managed users and enable unique, per-user app distribution rules.

3.2.1. The EMM's DPC can silently provision and activate a managed Google Play account according to the defined implementation guidelines. In doing so:

  • A managed Google Play account of type userAccount is added to the device.
  • The managed Google Play account of type userAccount must have a 1-to-1 mapping with actual users in the EMM's console.

3.3. Managed Google Play device account provisioning

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
remove_circle_outline
star
remove_circle_outline

The EMM can create and provision managed Google Play device accounts. Device accounts support silently installing apps from the managed Google Play store, and are not tied to a single user. Instead, a device account is used to identify a single device to support per-device app distribution rules in dedicated device scenarios.

3.3.1. The EMM's DPC can silently provision and activate a managed Google Play account according to the defined implementation guidelines. In doing so, a managed Google Play account of type deviceAccount must be added to the device.

3.4. Managed Google Play account provisioning for legacy devices

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0 and below
remove_circle_outline
remove_circle_outline
remove_circle_outline
star

The EMM can silently provision enterprise user accounts, called managed Google Play accounts. These accounts identify managed users and enable unique, per-user app distribution rules.

3.4.1. The EMM's DPC can silently provision and activate a managed Google Play account according to the defined implementation guidelines. In doing so:

    1. A managed Google Play account of type userAccount is added to the device.
    2. The managed Google Play account of type userAccount must have a 1-to-1 mapping with actual users in the EMM's console.

3.5. Silent app distribution

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star
star
star
star

IT admins can silently distribute work apps on users' devices without any user interaction.

3.5.1. The EMMs console must use the Play EMM API to allow IT admins to install work apps on managed devices.

3.5.2. The EMMs console must use the Play EMM API to allow IT admins to update work apps on managed devices.

3.5.3. The EMMs console must use the Play EMM API to allow IT admins to uninstall apps on managed devices.

3.6. Managed configuration management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star
star
star
star

IT admins can view and silently set managed configurations for any app that supports managed configurations.

3.6.1. The EMM's console must be able to retrieve and display the managed configuration settings of any Play app.

3.6.2. The EMM's console must allow IT admins to set any configuration type (as defined by the Android framework) for any Play app using the Play EMM API.

3.6.3. The EMM's console must allow IT admins to set wildcards (e.g. $username$ or %emailAddress%) so that a single configuration for an app such as Gmail can be applied to multiple users. The managed configurations iframe automatically supports this requirement.

3.7. App catalog management

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star
star
star
star

IT admins can import a list of all the apps approved for their enterprise from managed Google Play (play.google.com/work).

3.7.1. The EMM's console can display a list of all apps approved for distribution, including:

3.8. Programmatic app approval

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star_border
star_border
star_border
star_border

The EMM's console uses the managed Google Play iframe to support Google Play's app discovery and approval capabilities. IT admins can search for apps, approve apps, and approve new app permissions without leaving the EMM's console.

3.8.1. IT admins can search for apps and approve them within the EMM's console using the managed Google Play iframe.

3.9. Basic store layout management

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star
star
remove_circle_outline
star

End users can use the managed Google Play store app on their device to install and update work apps. The basic store layout is enabled by default and lists all apps approved for the enterprise, which EMMs filter on a per-users basis according to policy.

3.9.1. IT admins can manage users' available product sets to allow users to view and install applications from the managed Google Play store under the section 'Store home'.

3.10. Advanced store layout configuration

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star_border
star_border
remove_circle_outline
star_border

IT admins can customize the store layout users see in the managed Google Play store app on their devices.

3.10.1. IT admins can perform the following actions in the EMM's console to customize the managed Google Play store layout:

  • Create up to 100 store layout pages. Pages can have an arbitrary number of localized page names.
  • Create up to 30 clusters for each page. Clusters can have an arbitrary number of localized cluster names.
  • Assign up to 100 apps to each cluster.
  • Add up to 10 quick links to each page.
  • Specify the sort order of apps within a cluster and clusters within a page.

3.11. App license management

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star_border
star_border
star_border
star_border

IT admins can view and manage app licenses purchased in managed Google Play from the EMM's console.

3.11.1. For all paid apps approved for an enterprise, the EMM's console must display:

  • The number of licenses purchased.
  • The number of licenses consumed and the users consuming the licenses.
  • The number of licenses available for distribution.

3.11.2. IT admins can silently assign licenses to users without forcing that app to be installed on any of the users' devices.

3.11.3. IT admins can unassign an app license from a user.

3.12. Google-hosted private app management

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star_border
star_border
star_border
star_border

IT admins can update Google-hosted private apps through the EMM console instead of through the Google Play console.

3.12.1. IT admins can upload new versions of apps that are already published privately to the enterprise using the Google Play Developer Publishing API.

3.13. Self-hosted private app management

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star_border
star_border
star_border
star_border

IT admins can configure and publish self-hosted private apps. Unlike Google-hosted private apps, the APKs are not hosted by Google Play. Instead, the EMM helps IT admins host APKs themselves, and helps protect self-hosted apps by ensuring they can only be installed when authorized by managed Google Play.

3.13.1. The EMM's console must help IT admins host the app APK, by offering both of the following options:

  • Hosting the APK on the EMM's server. The server can be on-premise or cloud-based.
  • Hosting the APK outside of the EMM's server, at the discretion of the customer. The enterprise customer must specify in the EMM console where the APK is hosted.

3.13.2. The EMM's console must generate an appropriate APK definition file using the provided APK and must guide IT admins through the publishing process.

3.13.3. IT admins can update self-hosted private apps, and the EMM's console can silently publish updated APK definition files using the Google Play Developer Publishing API.

3.13.4. The EMM's server only serves download requests for the self-hosted APK that contain a valid JWT within the request's cookie, as verified by the private app's public key.

  • To facilitate this, the EMM's server must guide IT admins to download the self-hosted app's license public key from the Play Developer Console, and upload this to the EMM console.

3.14. EMM pull notifications

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star_border
star_border
star_border
star_border

Instead of periodically querying Play to identify past events such as an app update that contains new permissions or managed configurations, EMM pull notifications proactively notify EMMs of such events in real time, enabling EMMs to take automated actions and provide custom admin notifications based on these events.

3.14.1. The EMM must use Play's EMM notifications to pull notification sets.

3.14.2. EMM must automatically notify enterprise admin (for instance by an automated email) of the following notification events:

  • newPermissionEvent: Requires an enterprise admin to approve new app permissions before the app can be silently installed or updated on users' devices.
  • appRestrictionsSchemaChangeEvent: May require enterprise admin to update an app's managed configuration to maintain intended functionality.
  • appUpdateEvent: May be of interest to enterprise admins who wish to validate that core workflow functionality is unaffected by app update.
  • productAvailabilityChangeEvent: May impact users' ability to install the app or take app updates.
  • installFailureEvent: Play is unable to silently install an app on a users' device, suggesting there may be something about the device configuration that is preventing the install. EMMs should not immediately retry a silent install after receiving this notification, as Play's own retry logic will have already failed.

3.14.3. EMM automatically takes appropriate actions based on the following notification events:

  • newDeviceEvent: During device provisioning, EMMs must wait for newDeviceEvent before making subsequent Play EMM API calls for the new device, including silent app installs and setting managed configurations.
  • productApprovalEvent: upon receiving a productApprovalEvent notification, EMM must automatically update the list of approved apps imported into the EMM console for distribution to devices if their is an active admin session, or if the list of approved apps is not automatically reloaded at the start of each admin session.

3.15. API usage requirements

Android version
Work profile
Fully managed device
Dedicated device
MAM
remove_circle_outline
star
star
star
star

The EMM implements Google's APIs at scale, avoiding traffic patterns that could negatively impact customers' ability to manage apps in production environments.

3.15.1. The EMM must adhere to the Play EMM API usage limits. Failure to correct behavior that exceeds these guidelines may result in suspended API access, at Google's discretion.

3.15.2. The EMM should distribute traffic from different customers throughout the day, rather than consolidating all customers' traffic at specific or similar times. Behavior that fits this traffic pattern, such as scheduled batch operations for all enrolled customers, may result in suspend API access, at Google's discretion.

3.15.3. The EMM should not make consistent, incomplete or deliberately incorrect requests that make no attempt to retrieve or manage actual customer data. Behavior that fits this traffic pattern may result in suspended API access, at Google's discretion.


4. Device management

4.1. Runtime permission policy management

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
star
star
star
remove_circle_outline

IT admins can silently set a default response to all runtime permission requests made by work apps.

4.1.1. IT admins must be able to choose from the following options when setting a default runtime permission policy for their organization:

  • prompt (allows users to choose)
  • allow
  • deny

The EMM should enforce these settings using the EMM's DPC.

4.2. Runtime permission grant state management

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
star
star
star
remove_circle_outline

After setting a default runtime permission policy (see 4.1.), IT admins can silently set responses for specific permissions from any work app built on API 23 or above.

4.2.1. IT admins must be able to set the grant state (default, grant, or deny) of any permission requested by any work app built on API 23 or above. The EMM should enforce these settings using the EMM's DPC.

4.3. WiFi configuration management

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
star_border
star_border
star_border
remove_circle_outline

IT admins can silently provision enterprise WiFi configurations on managed devices, including:

4.3.1. SSID, via the EMM's DPC.

4.3.2. Password, via the EMM's DPC.

4.4. WiFi security management

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
star_border
star_border
star_border
remove_circle_outline

IT admins can provision enterprise WiFi configurations on managed devices that include the following advanced security features:

4.4.1. Identity, via the EMM's DPC.

4.4.2. Certificate for clients authorization, via the EMM's DPC.

4.4.3. CA certificate(s), via the EMM's DPC.

4.5. Advanced WiFi management

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can lock down WiFi configurations on managed devices, to prevent users from creating new configurations or modifying corporate configurations.

4.5.1. IT admins can lock down corporate WiFi configurations in either of the following configurations:

4.6. Account management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
star_border
star_border
remove_circle_outline

IT admins can ensure that only authorized corporate accounts can interact with corporate data, for services such as SaaS storage and productivity apps, or email. Without this feature, users can add personal accounts to those corporate apps that also support consumer accounts, enabling them to share corporate data with those personal accounts.

4.6.1. IT admins can prevent users from adding or modifying accounts.

  • When enforcing this policy on a device, EMMs must set this restriction before provisioning is complete, to ensure users cannot circumvent this policy by adding accounts before the policy is enacted.

4.7. G Suite account management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
star_border
remove_circle_outline
remove_circle_outline

IT admins can ensure that only authorized G Suite accounts can interact with corporate data. Without this feature, users can add personal Google Accounts to corporate Google apps (for example Google Docs or Google Drive), enabling them to share corporate data with those personal accounts.

4.7.1. IT admins can specify G Suite account(s) to be activated by the user during provisioning, after the account management lockdown is in place.

4.7.2. The EMM's DPC must prompt the user to activate their G Suite account, and ensure that only the specific user account can be activated by specifying the account to be added.

4.8. Certificate management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
star_border
star_border
remove_circle_outline

Allows IT admins to deploy identity certificates and certificate authorities to devices in order to enable access to corporate resources.

4.8.1. IT admins can install user identity certs generated by their PKI on a per-user basis. The EMM's console must integrate with at least one PKI and distribute certificates generated from that infrastructure.

4.8.2. IT admins can install certificate authorities in the managed keystore.

4.9. Advanced certificate management

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
star_border
star_border
star_border
remove_circle_outline

Allows IT admins to silently select the certificates that should be used by specific managed apps. This feature also grants IT admins the ability to remove CAs and identity certs from active devices, and prevent users from modifying credentials stored in the managed keystore.

4.9.1. For any app distributed to devices, IT admins can specify a certificate that the app will be silently granted access to during runtime.

  • Certificate selection must be generic enough to enable a single configuration that applies to all users, each of which may have a user-specific identity certificate.

4.9.2. IT admins can silently remove certificates from the managed keystore.

4.9.3. IT admins can silently uninstall a CA certificate, or all non-system CA certificates.

4.9.4. IT admins can prevent users from configuring credentials in the managed keystore.

4.10. Delegated certificate management

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
star_border
star_border
star_border
remove_circle_outline

IT admins can distribute a third-party certificate management app to devices and grant that app privileged access to install certificates into the managed keystore.

4.10.1. IT admins specify a certificate management package to be set as the delegated certificate management app by the DPC.

  • Console may optionally suggest known certificate management packages, but must allow enterprise admin to choose from the list of all apps available for install, for applicable users.

4.11. Advanced VPN management

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
star_border
star_border
star_border
remove_circle_outline

Allows IT admins to specify an Always On VPN to ensure that data from specified managed apps will always go through a configured VPN. Note: this feature requires deploying a VPN client that supports both Always On and per-app VPN features.

4.11.1. IT admins can specify an arbitrary VPN package to be set as an Always On VPN.

  • The EMM's console may optionally suggest known VPN packages that support Always On VPN, but can't restrict the VPNs available for Always On configuration to any arbitrary list.

4.11.2. IT admins can use managed configurations to specify the VPN settings for an app.

4.12. IME management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
remove_circle_outline
remove_circle_outline
remove_circle_outline

IT admins can control what input methods (IMEs) users can configure for their devices. Since the IME is shared across both work and personal profiles, blocking access to IMEs will prevent users from enabling those IMEs for personal use as well. IT admins may not, however, block access to system IMEs on work profiles (see advanced IME management for more details).

4.12.1. IT admins can configure an IME whitelist of arbitrary length (including an empty list, which blocks all non-system IMEs), which may contain any arbitrary IME packages.

  • The EMM's console may optionally suggest known or recommended IMEs for whitelisting, but must allow IT admins to choose from the list of all apps available for install, for applicable users.

4.12.2. The EMM must inform IT admins that system IMEs are excluded from management on devices with work profiles.

4.13. Advanced IME management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can control what input methods (IMEs) users can configure for their device. Advanced IME management extends the basic feature by enabling IT admins to manage access to system IMEs as well, which are typically provided by the OEM or carrier of the device.

4.13.1. Enterprise admin can configure an IME whitelist of arbitrary length (excluding an empty list, which blocks all IMEs including system IMEs), which may contain any arbitrary IME packages.

  • The EMM's console may optionally suggest known or recommended IMEs for whitelisting, but must allow IT admins to choose from the list of all apps available for install, for applicable users.

4.13.2. EMM must prevent IT admins from configuring an empty whitelist, as this will block all IMEs including system IMEs from being configured on the device.

4.13.3. EMM must ensure that if an IME whitelist does not contain system IMEs, that the third-party IMEs are silently installed before the whitelist is applied on the device.

4.14. Accessibility services management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
star_border
star_border
remove_circle_outline

IT admins can control what accessibility services can be enabled on users' devices. While accessibility services are powerful tools for users with disabilities or that are temporarily unable to fully interact with their device, they may interact with corporate data in ways that are non-compliant with corporate policy. This feature allows admins to disable any non-system accessibility service.

4.14.1. IT admins can configure an accessibility service whitelist of arbitrary length (including an empty list, which blocks all non-system accessibility services), which may contain any arbitrary accessibility service package.

  • Console may optionally suggest known or recommended accessibility services for whitelisting, but must allow enterprise admin to choose from the list of all apps available for install, for applicable users.

4.15. Location sharing management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
remove_circle_outline
remove_circle_outline
remove_circle_outline

IT admins can prevent users from sharing location data with apps in the work profile. Otherwise, the work profile location setting is user configurable in Settings.

4.15.1. IT admins can disable location services within the work profile.

4.16. Advanced location sharing management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can enforce a given location sharing setting on a managed device. This feature can ensure, for example, that corporate apps always have access to high accuracy location data, or that users don't consume extra battery by restricting location settings to battery saving mode.

4.16.1. IT admins can set the device location services to each of the following modes:

  • High accuracy.
  • Sensors only, for instance GPS, but not including network-provided location.
  • Battery saving, which limits the update frequency.
  • Off.

4.17. Factory reset protection management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.1+
remove_circle_outline
star_border
star_border
remove_circle_outline

Enables IT admins to protect company-owned devices from theft by ensuring only authorized users can factory reset devices. Admins can also disable factory reset protection entirely, if it introduces operational complexities when devices are returned to IT.

4.17.1. IT admins can prevent users from factory resetting their device from Settings.

4.17.2. IT admins can specify corporate unlock account(s) authorized to provision devices after a factory reset.

  • This account can be tied to an individual, or used by the entire enterprise to unlock devices.

4.17.3. IT admins can disable factory reset protection for specified devices.

4.17.4. IT admins can initiate a remote device wipe that optionally wipes reset protection data, thereby removing factory reset protection on the reset device.

4.18. Advanced app control

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can prevent the user from uninstalling or otherwise modifying managed apps through Settings, for instance force closing the app or clearing an app's data cache.

4.18.1. IT admins can block uninstall of any arbitrary managed apps, or all managed apps.

4.18.2. IT admins can prevent users from modifying application data from Settings.

4.19. Screen capture management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
star_border
star_border
remove_circle_outline

IT admins can block users from taking screenshots when using managed apps. This includes blocking screensharing apps and similar apps (such as Google Assistant) that leverage the system screenshot capabilities.

4.19.1. IT admins can prevent users from capturing screenshots.

4.20. Disable cameras

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can disable use of device cameras by managed apps.

4.20.1. IT admins can disable use of device cameras by managed apps.

4.21. Network statistics collection

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
star_border
remove_circle_outline
remove_circle_outline
remove_circle_outline

IT admins can query network usage statistics from a device's work profile. The statistics collected reflect the usage data shared with users in the Data usage section of Settings, and is only applicable to usage of apps within the work profile.

4.21.1. IT admins can query the network statistics summary for a work profile, for a given device and configurable time window, and view these details in the EMM's console.

4.21.2. IT admins can query a summary of work profile app network usage statistics, for a given device and configurable time window, and view these details organized by UID in the EMM's console.

4.21.3. IT admins can query a work profile's network usage historical data, for a given device and configurable time window, and view these details organized by UID in the EMM's console.

4.22. Advanced network statistics collection

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can query network usage statistics for an entire managed device. The statistics collected reflect the usage data shared with users in the Data usage section of Settings, and is applicable to usage of all apps on the device.

4.22.1. IT admins can query the network statistics summary for an entire device, for a given device and configurable time window, and view these details in the EMM's console.

4.22.2. IT admins can query a summary of app network usage statistics, for a given device and configurable time window, and view these details organized by UID in the EMM's console.

4.22.3. IT admins can query the network usage historical data, for a given device and configurable time window, and view these details organized by UID in the EMM's console.

4.23. Reboot device

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can remotely reboot managed devices.

4.23.1. IT admins can remotely reboot a managed device.

4.24. System radio management

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

Enables IT admins granular control over system network radios and associated usage policies.

4.24.1. IT admins can disable cell broadcasts sent by service providers (for example, AMBER alerts).

4.24.2. IT admins can prevent users from modifying mobile network settings in Settings.

4.24.3. IT admins can prevent users from resetting all network settings in Settings.

4.24.4. IT admins can configure if the device permits cellular data while roaming.

4.24.5. IT admins can configure whether the device can make outgoing phone calls, excluding emergency calls.

4.24.6. IT admins can configure whether the device can send and receive SMS messages.

4.24.7. IT admins can prevent users from using their device as a portable hotspot by tethering.

4.24.8. IT admins can set the WiFi timeout to the default, only while plugged in, or never.

4.24.9 IT admins can prevent users from configuring or modifying existing bluetooth connections.

4.25. System audio management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can silently control device audio features, including muting the device, preventing users from adjusting volume settings, and preventing users from unmuting the device microphone.

4.25.1. IT admins can silently mute managed devices.

4.25.2. IT admins can prevent users from modifying device volume settings.

4.25.3. IT admins can prevent users from unmuting the device microphone.

4.26. System clock management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can control device clock and timezone settings, and prevent users from modifying automatic device settings.

4.26.1. IT admins can enforce system auto time, preventing the user from setting the date and time of the device.

4.26.2. IT admins can silently toggle both auto time and auto timezone.

4.27. Advanced dedicated device features

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
remove_circle_outline
remove_circle_outline
star_border
remove_circle_outline

Provides IT admins with the ability to control more granular dedicated device features to support a variety of kiosk use cases.

4.27.1. IT admins can disable the device keyguard.

4.27.2. IT admins can disable the device status bar, blocking notifications and quick settings.

4.27.3. IT admins can force the device screen to remain on while the device is plugged in.

4.27.4. IT admins can prevent the following system UIs from being displayed:

  • Toasts
  • Phone activities (e.g. incoming calls) and priority phone activities (e.g. ongoing calls)
  • System alerts, system errors, and system overlays.

4.27.5. IT admins can enable the system recommendation for apps to skip their user tutorial and other introductory hints on first start-up.


5. Device usability

5.1. Managed provisioning customization

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
star_border
star_border
star_border
star_border

IT admins can modify the default managed provisioning flow UX to include enterprise-specific features. Optionally, admins can display EMM-provided branding during provisioning.

5.1.1. IT admins can customize the provisioning process by specifying the following enterprise-specific details: enterprise color, enterprise logo, enterprise terms of service and other disclaimers.

5.1.2. IT admins can deploy a non-configurable, EMM-specific customization that includes the following details: EMM color, EMM logo, EMM terms of service and other disclaimers.

  • EMMs must include all provisioning terms of service and other disclaimers for their provisioning flow in the system provisioning disclaimers bundle, even if the EMM-specific customization is not used.
  • EMMs may set their non-configurable, EMM-specific customization as the default for all deployments, but must allow admins to configure their own customization.

5.2. Enterprise customization

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
star_border
remove_circle_outline
remove_circle_outline
remove_circle_outline

IT admins can customize aspects of the work profile with corporate branding, for instance by setting the work profile user icon to the corporate logo, or configuring the background color of the work challenge.

5.2.1. IT admins can set the organization color, to be used as the background color of work challenge.

5.2.2. IT admins can set the display name of work profile.

5.2.3. IT admins can set the user icon of the work profile.

5.2.4. IT admins can prevent the user from modifying the work profile user icon.

5.3. Advanced enterprise customization

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
remove_circle_outline
star_border
remove_circle_outline
remove_circle_outline

IT admins can customize managed devices with corporate branding, for instance by setting the primary user icon to the corporate logo, or setting the device wallpaper.

5.3.1. IT admins can set the display name for the managed device.

5.3.2. IT admins can set the user icon of the managed device.

5.3.3. IT admins can prevent the user from modifying the device user icon.

5.3.4. IT admins can set the device wallpaper.

5.3.5. IT admins can prevent the user from modifying the device wallpaper.

5.4. Lock screen messages

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can set a custom message that's always displayed on the device lock screen, and does not require device unlock to be viewed.

5.4.1. IT admins can set a custom lock screen message.

5.5. Policy transparency management

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
remove_circle_outline
star_border
star_border
star_border

IT admins can customize the help text provided to users when they attempt to modify managed settings on their device, or deploy an EMM-supplied generic support message. Both short and long support messages can be customized, and are displayed in instances such as attempting to uninstall a managed app for which an admin has already blocked uninstallation.

5.5.1. IT admins customize both the short and long support messages.

5.5.2. Enterprise admin can deploy non-configurable, EMM-specific short and long support messages.

  • EMM may set their non-configurable, EMM-specific support messages as the default for all deployments, but must allow admins to configure their own messages.

5.6. Cross-profile contact management

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
star_border
remove_circle_outline
remove_circle_outline
remove_circle_outline

IT admins can control what contact data can leave the work profile. Both telephony and messaging (SMS) apps must run in the personal profile, and require access to work profile contact data to offer functionality for work contacts, but admins may choose to disable these features to protect work data.

5.6.1. IT admins can disable cross-profile contact search for personal apps that use the system contacts provider.

5.6.2. IT admins can disable cross-profile caller ID lookup for personal dialer apps that use the system contacts provider.

5.6.3. IT admins can disable bluetooth contact sharing with bluetooth devices that use the system contacts provider, for instance hands-free calling in cars or headsets.

5.7. Cross-profile data management

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
star_border
remove_circle_outline
remove_circle_outline
remove_circle_outline

Grants IT admins control over what data can leave the work profile, beyond the default security features of the work profile. With this feature, IT admins can enable select types of cross-profile data sharing to improve usability in key use cases, or further protect corporate data with additional lockdowns.

5.7.1. IT admins can configure cross-profile intent filters so that personal apps can resolve intent from the work profile such as sharing intents or web links.

  • Console may optionally suggest known or recommended intent filters for configuration, but can't restrict intent filters to any arbitrary list.

5.7.2. IT admins can whitelist managed apps that can display widgets on the homescreen.

  • The EMM's console must allow IT admins to choose from the list of all apps that are available for install to applicable users.

5.7.3. IT admins can block the use of copy/paste between the work and personal profiles.

5.7.4. IT admins can block users from sharing data from the work profile using NFC beam.

5.7.5. IT admins can permit personal apps to open web links from the work profile.

5.8. System update policy

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
remove_circle_outline
star_border
star
remove_circle_outline

IT admins can configure and apply over-the-air (OTA) system updates for devices.

5.8.1. The EMM's console allows IT admins to set the following OTA configurations:

  • Automatic: Devices receive OTA updates as soon as they become available.
  • Postpone: IT admins must be able to postpone OTA update for up to 30 days.
  • Windowed: IT admins must be able to schedule OTA updates within a daily maintenance window.

5.8.2. OTA configurations are applied to devices by the EMM's DPC.

5.9. Lock task mode management

Android version
Work profile
Fully managed device
Dedicated device
MAM
6.0+
remove_circle_outline
remove_circle_outline
star
remove_circle_outline

IT admins can lock an app or set of apps to the screen, and ensure that users can't exit the app.

5.9.1. The EMM's console allows IT admins to silently enable an arbitrary set of apps to install and lock to a device. Lock task mode is enabled by the EMM's DPC.

5.10. Persistent preferred activity management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
star_border
star_border
star_border
remove_circle_outline

Allows admins to set an app as the default intent handler for intents that match a certain intent filter. For example, this would allow admins to choose which browser app automatically opens all web links, or which launcher app is used when the user hits the home button.

5.10.1. IT admins can set any package as the default intent handler for any arbitrary intent filter.

  • The EMM's console may optionally suggest known or recommended intents for configuration, but cannot restrict intents to any arbitrary list.
  • The EMM's console must allow IT admins to choose from the list of all apps that are available to install for applicable users.

5.11. Keyguard feature management

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
star_border
remove_circle_outline
remove_circle_outline
remove_circle_outline

IT admins can control the features available to users before unlocking the device keyguard (lock screen) and the work challenge keyguard (lock screen).

5.11.1. The EMM's DPC can disable the following device keyguard features:

  • trust agents
  • fingerprint unlock
  • unredacted notifications

5.11.2. The EMM's DPC can disable the following work profile keyguard features:

  • trust agents
  • fingerprint unlock

5.12. Advanced keyguard feature management

Android version
Work profile
Fully managed device
Dedicated device
MAM
5.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can control advanced device keyguard (lock screen) features.

5.12.1. IT admins can disable the following device keyguard features:

5.13. Remote debugging

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

IT admins can retrieve debugging resources from users' devices without requiring users to take additional steps. Note: Bug reports are powerful tools for diagnosing issues, but may include sensitive data and thus require user consent.

5.13.1. IT admins can remotely request bug reports, view bug reports from the EMM's console, and download bug reports from the EMM's console.

5.14. MAC address retrieval

Android version
Work profile
Fully managed device
Dedicated device
MAM
7.0+
remove_circle_outline
star_border
star_border
remove_circle_outline

EMMs can silently fetch a device's MAC address, to be used to identify devices in other parts of the enterprise infrastructure (for example when identifying devices for network access control).

5.14.1. The EMM can silently retrieve a device's MAC address and can associate it with the device in the EMM's console.

Send feedback about...

Android Enterprise