Add a device compliance policy for Android devices in Intune
An Intune device compliance policy for Android specifies the rules and settings that Android devices must meet to be considered compliant. You can use these policies with conditional access to allow or block access to company resources. You can also get device reports and take actions for non-compliance. You create device compliance policies for each platform in the Intune Azure portal. To learn more about compliance policies, and any prerequisites, see Get started with device compliance.
The following table describes how noncompliant settings are managed when a compliance policy is used with a conditional access policy.
|Policy setting||Android 4.0 and later, Samsung Knox Standard 4.0 and later|
|PIN or password configuration||Quarantined|
|Jailbroken or rooted device||Quarantined (not a setting)|
|email profile||Not applicable|
|Minimum OS version||Quarantined|
|Maximum OS version||Quarantined|
|Windows health attestation||Not applicable|
Remediated = The device operating system enforces compliance. (For example, the user is forced to set a PIN.)
Quarantined = The device operating system does not enforce compliance. (For example, Android devices do not force the user to encrypt the device.) When the device is not compliant, the following actions take place:
- The device is blocked if a conditional access policy applies to the user.
- The company portal notifies the user about any compliance problems.
Create a device compliance policy
- Sign in to the Azure portal.
- Select All services, filter on Intune, and select Microsoft Intune.
- Select Device compliance > Policies > Create Policy.
- Enter a Name and Description.
- For Platform, select Android. Choose Settings Configure, and enter the Device Health, Device Properties, and System Security settings. When done, select OK, and Create.
Rooted devices: If you enable this setting, jailbroken devices are evaluated as noncompliant.
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. Choose the maximum allowed threat level:
- Secured: This option is the most secure, as the device can't have any threats. If the device is detected as having any level of threats, it is 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 existing threats on the device are low or medium level. If the device is detected to have high-level threats, it is determined to be noncompliant.
- High: This option is the least secure, and allows all threat levels. It may be useful if you're using this solution only for reporting purposes.
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.
Up-to-date security provider: Require that an up-to-date security provider can protect a device from known vulnerabilities.
Threat scan on apps: Require that the Android Verify Apps feature is enabled.
On the legacy Android platform, this feature is a compliance setting. Intune can only check whether this setting is enabled at the device level. On devices with work profiles (Android for Work), this setting can be found as a configuration policy setting. This allows administrators to enable the setting for a device.
If your enterprise uses Android work profiles, you can enable Threat scan on apps for your enrolled devices. Establish a device profile and require the system security setting. For more information, see Android for Work device restriction settings in Intune.
SafetyNet device attestation: Enter the level of SafetyNet attestation that must be met. Your options:
- Not configured
- Check basic integrity
- Check basic integrity & certified devices
Device property settings
- Minimum OS version: When a device doesn't meet the minimum OS version requirement, it's reported as noncompliant. A link with information about how to upgrade is shown. The end user can choose to upgrade their device, and then get access to company resources.
- Maximum OS version: When a device is using an OS version later than the version specified in the rule, access to company resources is blocked. The user is asked to contact their IT admin. Until there is a rule change to allow the OS version, this device can't access company resources.
System security settings
- Require a password to unlock mobile devices: Require users to enter a password before they can access their device.
- Minimum password length: Enter the minimum number of digits or characters that the user's password must have.
- Required password type: Select whether a password should have only numeric characters, or there should be a mix of numbers and other characters. Choose from:
- Device Default
- Low security biometric
- At least numeric
- Numeric complex: Repeated or consecutive numerals (such as "1111" or "1234") are not allowed.
- 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.
- Password expiration (days): Select the number of days before the password expires and the user must create a new password.
- 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 of data storage on a device (Android 4.0 and above, or KNOX 4.0 and above): Choose Require to encrypt data storage on your devices. Devices are encrypted when you choose the Require a password to unlock mobile devices setting.
Block apps from unknown sources: Choose to block devices with "Security > Unknown Sources" enabled sources (Android 4.0 – Android 7.x. Not supported by Android 8.0 and later). To side-load apps, unknown sources must be allowed. If you're not side-loading Android apps, then enable this compliance policy.
Side-loading applications require that the Block apps from unknown sources setting is enabled. Enforce this compliance policy only if you are not side-loading Android apps on devices.
Company portal app runtime integrity: Checks if the Company Portal app has the default runtime environment installed, is properly signed, is not in debug-mode, and is installed from a known source.
Block USB debugging on device (Android 4.2 or later): Choose to prevent deviceS from using the USB debugging feature.
Minimum security patch level (Android 6.0 or later): Select the oldest security patch level a device can have. Devices that are not at least at this patch level are noncompliant. The date must be entered in the
In your policy, choose from existing locations. Don't have a location yet? Use Locations (network fence) in Intune provides some guidance.
- Choose Select locations.
- From the list, check your location, and choose Select.
- Save the policy.
- Select Actions for noncompliance. The default action marks the device as noncompliant immediately. This action applies when you select at least one location, and if the device isn't connected to the selected locations.
You can change this action to update the schedule when the device is marked non-compliant, such as after one day. You can also configure a second action that sends an email to the user when the device is no longer compliant with your locations.
Assign user groups
- Choose a policy that you've configured. Existing policies are in Device compliance > Policies.
- Choose the policy, and choose Assignments. You can include or exclude Azure Active Directory (AD) security groups.
- Choose Selected groups to see your Azure AD security groups. Select the user groups you want this policy to apply, and choose Save to deploy the policy to users.
You have applied the policy to users. The devices used by the users who are targeted by the policy are evaluated for compliance.