Block - Mark rooted (jailbroken) devices as not compliant. Jailbroken devices Supported for iOS 8.0 and later Then, Intune can install the managed email profile.įor details about email profiles, see configure access to organization email using email profiles with Intune. To be compliant, the end user must remove the existing email settings. Intune can't overwrite the user-configured profile, and Intune can't manage it. The user already set up an email account on the device that matches the Intune email profile deployed to the device.The email profile is assigned to a different user group than the user group targeted by the compliance policy.The device is considered non-compliant in the following situations: If no email account exists on the device, the user should contact the IT administrator to configure a managed email account. If the user already has an email account on the device, the email account must be removed so Intune can set one up correctly. Require - A managed email account is required.Not configured ( default) - This setting isn't evaluated for compliance or non-compliance.Before you beginĬreate an iOS/iPadOS device compliance policy to access available settings. To learn more about compliance policies, and what they do, see get started with device compliance. As part of your mobile device management (MDM) solution, use these settings to require an email, mark rooted (jailbroken) devices as not compliant, set an allowed threat level, set passwords to expire, and more.Īs an Intune administrator, use these compliance settings to help protect your organizational resources. This article lists and describes the different compliance settings you can configure on iOS/iPadOS devices in Intune.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |