Wednesday, November 10, 2021

Known Issue: Samsung devices are noncompliant after restart or update

We are aware of an issue where some Samsung devices show as noncompliant after an automatic restart or after a managed update is applied. This could potentially affect access to corporate resources, depending on the Conditional Access policies set by the IT administrator. We are working to resolve this issue with Samsung, but in the meantime, we wanted to give you more information and workaround instructions to help you bring devices back into compliance.


For Samsung Galaxy devices with Android device administrator (DA)  management or Android Enterprise personally-owned work profiles, this issue occurs when the user runs an automatic restart (Settings > Auto restart at set times) on the device. After the restart, the device shows as noncompliant in Intune, which can block access to corporate resources. This issue affects Android (DA) and Android Enterprise personally-owned work profile Samsung Galaxy devices running Android 9 or later.


  • To work around the issue, users need to unlock the phone, launch the Company Portal, and trigger a device sync. Once the sync is completed, the device should show as compliant in Intune and access to corporate resources should be restored.


For Android Enterprise fully managed Samsung devices, this issue occurs when the device receives and completes a managed update. After the update, the device shows as noncompliant in Intune, which can block access to corporate resources. This issue affects Samsung devices provisioned as Android Enterprise fully managed devices running Android 11 and later.


  • To work around the issue, users need to unlock the phone, open the Device Policy Controller app, and trigger a sync. Once the sync is completed, the device should show as compliant in Intune and access to corporate resources should be restored.

We will continue to update this post as new information becomes available. If you have questions or comments for the Intune team, reply to this post or reach out to @IntuneSuppTeamon Twitter.

Posted at