Add a device compliance policy for Android work profile devices in Intune
An Intune device compliance policy for Android work profile devices specifies the rules and settings that these 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 different platforms 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 work profile|
|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:
- If a conditional access policy applies to the user, the device is blocked.
- 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 enterprise. 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, and means that the device cannot 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 the threats that are present 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, as it 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.
- 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
Threat scan on apps
On devices with Android work profiles, the Threat scan on apps setting can be found as a configuration policy setting. Administrators can 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 Work device restriction settings in Intune.
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 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 there is a rule change to allow the OS version, the device cannot 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: Choose whether a password should contain only numeric characters or a mix of numerals and other characters. Choose from:
- Device Default
- Low security biometric
- At least numeric
- 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.
- 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.
- Require encryption on mobile device: You don't have to configure this setting because Android work profile devices enforce encryption.
- Block apps from unknown sources: You don't have to configure this setting as Android work profile devices always restrict installation from unknown sources.
- 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: You don't have to configure this setting because USB debugging is already disabled on Android work profile devices.
- Minimum security patch level: 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 YYYY-MM-DD format.
- Restricted apps: You can restrict apps by adding their bundle IDs to the policy. Then if a device has the app installed, the device will be marked as noncompliant.
- App name: Enter a user-friendly name to help you identify the bundle ID.
- App Bundle ID: Enter the unique bundle identifier for the app provider. For Android, the app bundle ID is taken from the store URL for the app. For example, if the URL to the app in the store is https://play.google.com/store/apps/details?id=com.Slack, the App Bundle ID = com.Slack.
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.