Add a device compliance policy for iOS devices in Intune
An Intune iOS device compliance policy determines the rules and settings that iOS devices must meet to be compliant. When you use device compliance policies with conditional access, you can allow or block access to company resources. You can also get device reports and take actions for non-compliance. Device compliance policies for each platform can be created 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||iOS 8.0 and later|
|PIN or password configuration||Remediated|
|Device encryption||Remediated (by setting PIN)|
|Jailbroken or rooted device||Quarantined (not a setting)|
|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
- In 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 iOS.
- Choose Settings Configure, and enter the Email, Device Health, Device Properties, and System Security settings described in this topic. When you're done, select OK, and Create.
Require mobile devices to have a managed email profile: If you set this to Require, then devices that don't have an email profile managed by Intune are considered not-compliant. A device may not have a managed email profile when it's not correctly targeted, or if the user manually setup the email account on the device.
The device is considered noncompliant in the following situations:
- The email profile is deployed to a user group other than the user group that the compliance policy targets.
- The user has already set up an email account on the device that matches the Intune email profile deployed to the device. Intune cannot overwrite the user-provisioned profile, and therefore cannot manage it. To ensure compliance, the user must remove the existing email settings. Then, Intune can install the managed email profile.
Select the email profile that must be managed by Intune: If the Email account must be managed by Intune setting is selected, choose Select to specify the Intune email profile. The email profile must be present on the device.
For details about email profile, see Configure access to corporate email using email profiles with Microsoft Intune.
- Jailbroken devices: If you enable this setting, jailbroken devices are not compliant.
- Require the device to be at or under the Device Threat Level (iOS 8.0 and newer): Choose the maximum threat level to mark devices as noncompliant. Devices that exceed this threat level get marked as noncompliant:
- 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.
- Minimum OS required: When a device does not meet the minimum OS version requirement, it is reported as noncompliant. A link with information on how to upgrade is shown. The user can choose to upgrade their device. After that, they can access company resources.
- Maximum OS version allowed: When a device uses an OS version later than the version specified in the rule, access to company resources is blocked. The user is then asked to contact their IT admin. Until there is a change in rule to allow the OS version, this device cannot access company resources.
- Minimum OS build version: When Apple publishes security updates, the build number is typically updated, not the OS version. Use this feature to enter a minimum allowed build number on the device. This compliance check supports devices running iOS 8.0 and newer.
- Maximum OS build version: When Apple publishes security updates, the build number is typically updated, not the OS version. Use this feature to enter a maximum allowed build number on the device. This compliance check supports devices running iOS 8.0 and newer.
After a compliance or configuration policy is applied to an iOS device, users are prompted to set a passcode every 15 minutes. Users are continually prompted until a passcode is set.
Require a password to unlock mobile devices: Require users to enter a password before they can access their device. iOS devices that use a password are encrypted.
Simple passwords: Set to Block so users can't create simple passwords, such as 1234 or 1111. Set to Not configured to let users create passwords like 1234 or 1111.
Minimum password length: Enter the minimum number of digits or characters that the password must have.
Required password type: Choose if a password should have only Numeric characters, or if there should be a mix of numbers and other characters (Alphanumeric).
Number of non-alphanumeric characters in password: Enter the minimum number of special characters (&, #, %, !, and so on) that must included in the password.
Setting a higher number requires the user to create a password that is more complex.
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 previously used passwords that cannot be used.
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 assigned by the app provider. To find the bundle ID, see How to find the bundle ID for an iOS app.
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.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.