Known Issue: Android devices lose access to Intune-managed resources after upgrading to Android 12

[Intune_Support_Team]

We are aware of an issue where customers lose access to Microsoft Intune-managed resources or are prevented from completing enrollment after upgrading certain devices from Android 11 to Android 12. Currently, this includes some OPPO, OnePlus, and Realme devices enrolled as Android Enterprise personally-owned work profile. We’ve gotten a few cases and seen some comments on posts in the Intune Customer Success blog. We’ve then shared those scenarios with our contacts at device OEMs and Google support.

Latest update:

Working with Google and Device OEMs - OPPO/OnePlus/Realme engineering has found an issue in the PackageManagerService#getInstalledPackages Android API. When the APK calls this function in a non-primary user, it will fail. Device OEMs have identified a fix and are currently working with Google TAM services to validate that the fix is implemented for each of the affected brands (OPPO, OnePlus, and Realme).

Device OEMs will do a gradual rollout of the fix with periodic OTA updates. The goal is to have the fix rolled out to all S-product devices across OPPO, Realme, and OnePlus brands before the end of May, so make sure to install the latest OS updates as they are released.

We do not have sharable target dates for individual devices or brands at this time, so we encourage affected customers to install any new OTA updates as soon as they become available. Keep in mind that dates are subject to change with all software releases. If Device OEMs provides any additional timeline information to Intune or Google support teams, we will continue to update this post as new information becomes available.

At this time, we’re aware of three device types that can have this issue and here’s the latest we have from Google and the device manufacturers:

1. OPPO devices - OPPO has identified a fix and are working on submitting a gradual rollout of the fix with periodic OTA updates.
   
   
2. OnePlus devices - OnePlus has confirmed the issue has been resolved in the latest build for the OnePlus 9 series. As confirmed by a few of you in the comments of this post, please ensure you have build: LE2123_11_C.47 and higher to resolve this issue. A few comments around that this issue is also hitting the OnePlus 10 series. OnePlus engineering is investigating and a fix will be available in future releases. Note that build NE2217_11_A.03 does not fix the issue on OnePlus 10 device; OnePlus is aware. 
   
   
3. Realme devices - Realme has identified a fix and are working on submitting a gradual rollout of the fix with periodic OTA updates.

Again, as OEMs release updated OSes, please install them as they become available. For device specific information on when an OTA update will be available to your device, contact your respective device OEMs for further updates. We will also continue to update this post as new information becomes available. If you have any questions, reply to this post or reach out to @IntuneSuppTeam on Twitter.

Post updates:

03/22/22: Update to the latest update section.

04/14/22: Updated post with latest information from device OEMs.

04/29/22: Updated post with latest information from device OEMs.

05/25/22: Updated post with additional OPPO info from device OEM.