Support Tip: New Google-based Compliance Screens for Kiosk Mode
Published Feb 12 2021 12:25 PM 5,216 Views

We now support the use of Google’s compliance screens on Android Enterprise dedicated devices that leverage kiosk mode. As a result, you can now configure a password policy and ensure that your end-users will be guided down a path to enforce said policy. The screens will get invoked if you configure a password policy in device configuration and/or device compliance. That experience would look something like this (this example is a password policy requiring 4 digits): 


Password policy experience requiring 4 digitsPassword policy experience requiring 4 digits


Below are other screens your users may see, depending on what compliance policies you have applied to their devices. We will update as more screens get introduced.


Minimum OS level

Minimum OS level user experienceMinimum OS level user experience


Set a new screen lock

Set a new screen lock user experienceSet a new screen lock user experience


A couple of things to note about this feature:

  • The 9 days until wipe that shows in the screens is the default behavior of the Google compliance screen if the device is non-compliant with the policies that have been configured in console. So, even if you said in Intune to “mark device as non-compliant but not wipe it” the end-user will see this screen and their device would get wiped after 9 days if they remain non-compliant.

  • On some Android devices running OS 10 or lower, encryption can’t be enforced unless the device also has a passcode. For these devices, if you require encryption for compliance but don’t set a policy for device password, the user won’t have a great remediation path for gaining compliance and their device will be at risk of wipe.


Learn more about Android Enterprise device password restrictions here.


Let us know if you have any questions by commenting on this post or reaching out to @IntuneSuppTeam on Twitter.


Post updates:

  • 2/16: Added a couple of things to note about this feature.
  • 7/26: Updated post to reflect the functionality’s availability on all dedicated devices running kiosk mode.
Version history
Last update:
‎Jul 26 2021 01:43 PM
Updated by: