\n
30th November, 2023
\n
\n
We are investigating an issue making some management policies permanent on Android 14. This issue affects two sets of management policies, one set when upgrading from Android 13 to Android 14, and one set on every reboot of Android 14 devices.
\n
\n
Your EMM can provide the lists of affected policies specific to their product. We recommend reviewing the affected policies set on your Android 13 devices, and if those existing policies are unlikely to change for the lifecycle of the device then no further action is required.
\n
\n
If those policies are likely to change, we recommend the following:
\n
\n- Consider unsetting those policies that are made permanent on upgrade prior to upgrading to Android 14.
\n- We have provided recommended workarounds to our EMM partners, and have already implemented them if they are using our Android Management API (AMAPI). Please check with your EMM to see whether they have implemented these workarounds, or are using AMAPI. We will be adding additional redundancy to AMAPI’s workarounds in the coming weeks.
\n- You can safely re-enable affected policies on Android 14 once confirming the workaround is in place with your EMM.
\n
\n
If your devices are already impacted and have policies that have been made permanent, the only available remediation to clear the affected policy behavior is to remove the work profile on personally-owned devices or factory reset on company-owned devices.
\n
\n
Note: If the following policies are set on a personally-owned Android 14 device, they will become permanent and users must factory reset their devices if they wish to clear them. We recommended backing up personal data prior to a factory reset to help mitigate data loss. There is no workaround for these policies.
\n
\n
We will keep this post updated as additional information becomes available.
\n