Android device administrator management was released in Android 2.2 as a way to manage Android devices. Then beginning with Android 5, the more modern management framework of Android Enterprise was released (for devices that can reliably connect to Google Mobile Services). Google is encouraging movement off of device administrator management by decreasing its management support in new Android releases.
Because of these changes by Google, in the fourth quarter of 2020, you will no longer have as extensive management capabilities on impacted device administrator managed devices.
Note: This date was previously communicated as third quarter of 2020, but it has been moved out based on the latest information from Google.
Device types that will be impacted
Devices that will be impacted by the decreasing device administrator support are those for which all three conditions below apply:
Devices will not be impacted if they are any of the below:
Google's decreased device administrator support prevents configuration of these settings from applying on impacted devices.
Configuration profile device restrictions settings:
Compliance policy settings
Android 10: For all device administrator managed devices (including Samsung) running Android 10 and later, Google has restricted the ability for device administrator management agents like Company Portal to access device identifier information. This restriction impacts the following Intune features after a device is updated to Android 10 or later:
Android 11: We are currently testing Android 11 support on the latest developer beta release to evaluate if it will cause impact on device administrator managed devices.
Impacted configuration settings:
Impacted compliance settings:
Devices will begin being impacted in the fourth quarter of 2020. At that time, there will be a Company Portal app update that will increase the Company Portal API targeting from level 28 to level 29 (as required by Google).
At that point, device administrator managed devices that are not manufactured by Samsung will be impacted once the user completes both these actions:
To avoid the reduction in functionality coming in the fourth quarter of 2020, we recommend the following:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.