[German]Small note for administrators who manage Android mobile devices via Intune. Microsoft has worked with Samsung to fix a bug that prevents devices from integrating with Intune when upgrading to Android 13. A fix is available to ensure Samsung Android 13 devices can once again be managed through Microsoft's Intune MDM solution.
Intune is a cloud-based management solution for endpoints (Windows PCs, mobile devices, etc.) that was introduced in 2011. For some time now, Android devices can also be managed via Intune.
Microsoft Intune, Source: Microsoft
My impression is that the management of Android devices keeps getting stuck, because the interface between Microsoft and Google or the Android device manufacturers causes issues. In the article My impression is that the management of Android devices keeps getting stuck, because the interface between Microsoft and Google or the Android device manufacturers causes issues. In the article (Resolved) Known Issue: Devices Upgrading to Android 13 cannot enroll into management, Microsoft confirms that a problem with Samsung Galaxy S21 and S22 devices under Intune has been fixed.
Specifically, the issue was that Samsung devices could not log into Microsoft Intune as a personal work profile on Android 13. Users would then see a dialog box stating that the profile could not be created. The Samsung Galaxy S21 and Samsung Galaxy S22 devices were affected, but other models may also be affected.
A solution was then worked out in cooperation with Samsung and Google, which is now available from Samsung. To fix the issue, Microsoft recommends Intune administrators ask users to reboot the device. The Android device policy app is downloaded during enrollment, but does not change the user experience.
Unless a reboot fixes the problem for affected users, administrators should instruct those users to manually install the Android device policy from the Google Play Store, then restart the device and begin the login process again. More information can be found in Samsung's Knox documentation. (via)
Cookies helps to fund this blog: Cookie settings