Forum Discussion

PatrickF11's avatar
PatrickF11
Steel Contributor
Aug 24, 2021

Android Enterprise (COPE) - Device password not prompting

Hi,

i'm experience the following weird problem:

When enrolling Android devices with android enterprise COPE mode (fully managed with work profile) the password setup prompt isn't showing up for the end-user.

Afterwards the device is, of course, not compliant, because we want a passcode to be present.

 

Reffering to the these MS Docs:

  • Device default (default): Most devices don't require a password when set to Device default. 
    If you want to require users to set up a passcode on their devices,
    configure this setting to something more secure than Device default.

-> Of course i've already configured a more secure type than default (in this case Numeric).

By the way: All the other configuration profiles works just fine.

 

Any idea on how to deal with this?

At this moment i'm using a workaround with Conditional Access: When not compliance you can't do anything with the M365 world in your hands, unless you're device gets compliant. πŸ˜„

 

Thanks in advance.

Greetings,

Patrick

  • PatrickF11's avatar
    PatrickF11
    Steel Contributor
    Just to "close" this one: I've found the solution by myself. (And it is quite logical. πŸ˜‰
    The Assignment of the corresponding profile was set to a dynamic group. While the initial setup flow the device object isn't in the corresping group, yet. Seems legit, isn't it?
    • mitcheman88's avatar
      mitcheman88
      Copper Contributor

      PatrickF11 

       

      Did you had to wipe the device through intune and perform an enrollment via QR again? I've got the same issue. Out of the box device does not get the password prompt for the container while enrolling. When I wipe an enrolled one it gets the prompt. 

       

      I'm also using a dynamic group for the devices. 

      • PatrickF11's avatar
        PatrickF11
        Steel Contributor

        mitcheman88 

        Yes, i've got the exact same issue.

        Already enrolled devices won't get the passcode. It seems that this only happens during enrollment.

        Therefore i've switched to all device assignment for the passcode profile. (The few existing devices were setup manually with a device pin.)

Resources