Blog Post

Intune Customer Success
1 MIN READ

Resolved: Android 11 on Samsung leading to slower corporate-owned work profile enrollments

Intune_Support_Team's avatar
Intune_Support_Team
Silver Contributor
Oct 20, 2021

Updated 12/1:
This issue is now resolved! Google has released a fix that completed rollout to affected tenants on 11/16/2021.

 

We recently had a case escalation and now have a confirmed known issue for Android 11 corporate-owned work profile enrollments on Samsung devices. We’ll keep this post updated as Google and Samsung continue to investigate. Note that Google confirmed today they have been able to reproduce this issue, but we haven’t confirmed exactly which Samsung devices are affected yet.

 

Scenario: During the Intune corporate-owned work profile enrollment flow for Samsung devices on Android 11, the enrollment appears to hang while installing the Microsoft Intune app during the required app install step. In our repro of the issue, we’re seeing the device stay on this screen sometimes over 40 minutes. Installation will continue and successfully enroll; however, it’s taking far longer than it did before or with other device manufacturers.

 

Screenshot of a Samsung device running Android 11 corporate-owned work profile device enrolling into Microsoft Endpoint Manager.

 

Scope: This issue is specific to Samsung devices running Android 11 during corporate-owned work profile enrollments. We’re able to reproduce using Samsung devices such as SM-A127F.

 

Updates: 

  • 10/29/2021 - Google believes they’ve got a potential fix and are currently testing that fix with Intune.
  • 10/19/2021 - Google is investing as a high priority with Samsung. We’ll continue to provide updates as they determine root cause.
  • 12/1/2021 - Google has released a fix that completed rollout to affected tenants on 11/16/2021.
Updated Dec 01, 2021
Version 5.0

16 Comments

Comments have been turned off for this post
  • Marc-Fom's avatar
    Marc-Fom
    Copper Contributor

    Had same thing yesterday during Android Enterprise Corporate-owned dedicated device enrollment and not only on Android 11, also on an old SM-A510F running Android 7.0 (can't go above).

     

  • ShirleyV's avatar
    ShirleyV
    Copper Contributor

    Is there any news upon this issue? I'm about to roll-out 1.400 Samsung devices, fully manages. Yesterday, we had some pilot candidates and it was dramatic. It took about 3 hours before the registration process was ready!

  • MaxM's avatar
    MaxM
    Brass Contributor

    Larry125 That's a different issue. Check MC291439 in the MS365 Message Center for details.

     

    Here's a direct link. It will only work if you have appropriate access in the MS365 admin portal:

    https://admin.microsoft.com/Adminportal/Home?ref=MessageCenter/:/messages/MC291439

     

  • Larry125's avatar
    Larry125
    Copper Contributor

    Similar but different error.  Samsung S20 Ultra unable to connect, but previously could connect to intune due to error "A device password must be at least 4 characters long", The error indicates the app thinks phone has < 4 characters which is incorrect.  

    Phone:

    One UI: 3.1

    Android version: 11

    Baseband version: G988U1UES2DUI5

    Android security patch level: Oct. 21, 2021

  • MaxM's avatar
    MaxM
    Brass Contributor

    I’m seeing these exact symptoms during Fully Managed device enrollment too, not only corp-owned Work Profile. Samsung A21. Should I open a ticket for it?

  • JFRigot's avatar
    JFRigot
    Brass Contributor

    Scope : Same here with SM-A525 devices.
    The behaviour is not consistent though. As we managed to get some speed with the creation of additional QR codes, which works for "some" time, then it slows down again.