Android Enterprise settings to mark devices as compliant or not compliant using Intune

This article lists and describes the different compliance settings you can configure on Android Enterprise devices in Intune. As part of your mobile device management (MDM) solution, use these settings to mark rooted (jailbroken) devices as not compliant, set an allowed threat level, enable Google Play Protect, and more.

This feature applies to:

  • Android Enterprise

As an Intune administrator, use these compliance settings to help protect your organizational resources. To learn more about compliance policies, and what they do, see get started with device compliance.

Before you begin

Create a compliance policy. For Platform, select Android Enterprise.

Device health

  • Rooted devices: Choose Block to mark rooted (jailbroken) devices as not compliant. When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance.
  • Require the device to be at or under the Device Threat Level: Use this setting to take the risk assessment from the Lookout MTP solution as a condition for compliance. When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance. To use this setting, choose the allowed threat level:
    • Secured: This option is the most secure, and means that the device can't have any threats. If the device is detected with any level of threats, it's evaluated as noncompliant.
    • Low: The device is evaluated as compliant if only low-level threats are present. Anything higher puts the device in a noncompliant status.
    • Medium: The device is evaluated as compliant if the threats that are present on the device are low or medium level. If the device is detected to have high-level threats, it's determined to be noncompliant.
    • High: This option is the least secure, as it allows all threat levels. It may be useful if you're using this solution only for reporting purposes.

Google Play protect

  • Google Play Services is configured: Require that the Google Play services app is installed and enabled. Google Play services allows security updates, and is a base-level dependency for many security features on certified-Google devices. When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance.
  • Up-to-date security provider: Require that an up-to-date security provider can protect a device from known vulnerabilities. When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance.
  • SafetyNet device attestation: Enter the level of SafetyNet attestation that must be met. Your options:
    • Not configured (default): Setting isn't evaluated for compliance or non-compliance.
    • Check basic integrity
    • Check basic integrity & certified devices

Note

On Android Enterprise devices, Threat scan on apps is a device configuration policy. Using a configuration policy, administrators can enable the setting on a device. See Android Enterprise device restriction settings.

Device properties settings

  • Minimum OS version: When a device doesn't meet the minimum OS version requirement, it's reported as noncompliant. A link with information on how to upgrade is displayed. The end user can choose to upgrade their device, and then access company resources.
  • Maximum OS version: When a device is using an OS version later than the version in the rule, access to company resources is blocked. And, the user is asked to contact their IT admin. Until a rule is changed to allow the OS version, this device can't access company resources.

System security settings

Password

  • Require a password to unlock mobile devices: Require users to enter a password before they can access their device. When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance. This setting is applied at the device level. If you only need to require a password at the work profile level, then use a configuration policy. See Android Enterprise device configuration settings.

  • Minimum password length: Enter the minimum number of digits or characters the user's password must have.

  • Required password type: Choose if a password should include only numeric characters, or a mix of numerals and other characters. Your options:

    • Device Default
    • Low security biometric
    • At least numeric (default)
    • Numeric complex
    • At least alphabetic
    • At least alphanumeric
    • At least alphanumeric with symbols
  • Maximum minutes of inactivity before password is required: Enter the idle time before the user must reenter their password. When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance.

  • Password expiration (days): Select the number of days before the password expires, and they must create a new one.

  • Number of previous passwords to prevent reuse: Enter the number of recent passwords that can't be reused. Use this setting to restrict the user from creating previously used passwords.

Encryption

  • Encryption of data storage on device: Choose Require to encrypt data storage on your devices. When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance.

    You don't have to configure this setting because Android Enterprise devices enforce encryption.

Device Security

  • Block apps from unknown sources: Choose to block devices with "Security > Unknown Sources" enabled sources (supported on Android 4.0 – Android 7.x; not supported by Android 8.0 and later). When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance.

    To side-load apps, unknown sources must be allowed. If you're not side-loading Android apps, then set this feature to Block to enable this compliance policy.

    Important

    Side-loading applications require that the Block apps from unknown sources setting is enabled. Enforce this compliance policy only if you're not side-loading Android apps on devices.

    You don't have to configure this setting as Android Enterprise devices always restrict installation from unknown sources.

  • Company portal app runtime integrity: Choose Require to confirm the Company Portal app meets all the following requirements:

    • Has the default runtime environment installed
    • Is properly signed
    • Isn't in debug-mode
    • Is installed from a known source

    When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance.

  • Block USB debugging on device: Choose Block to prevent devices from using the USB debugging feature. When you choose Not configured (default), this setting isn't evaluated for compliance or non-compliance.

    You don't have to configure this setting because USB debugging is already disabled on Android Enterprise devices.

  • Minimum security patch level: Select the oldest security patch level a device can have. Devices that aren't at least at this patch level are noncompliant. The date must be entered in the YYYY-MM-DD format.

Select OK > Create to save your changes.

Next steps