Move Android devices from device administrator to personally-owned work profile management
You can help users move their Android devices from device administrator to personally-owned work profile management by using the compliance setting to Block devices managed with device administrator. This setting lets you make devices non-compliant if they're managed with device administrator.
When users see that they're out of compliance for this reason, they can tap Resolve. They'll be taken to a checklist that will guide them through:
- Unenrolling from device administrator management
- Enrolling into personally-owned work profile management
- Resolving any compliance issues.
- Users must have Android device administrator enrolled devices with Android Company Portal version 5.0.4720.0 or later.
- Set up Android personally-owned work profile management by connecting your Intune tenant account to your Android Enterprise account.
- Set Android Enterprise personally-owned work profile enrollment for the group of users who are moving to personally-owned work profile.
- Consider increasing your user device limits. When unenrolling devices from device administrator management, device records might not be immediately removed. To provide cushion during this period, you might need to increase device limit capacity. This increase is so that the users can enroll into personally-owned work profile management.
- Configure Azure Active Directory device settings for Maximum number of devices per user.
- Adjust the Intune device limit restrictions by setting the device limit.
Create device compliance policy
In the Microsoft Intune admin center, select Devices > Compliance policies > Policies > Create Policy.
On the Create a policy page, set Platform to Android device administrator > Create.
On the Basics page, type in the Name and Description > Next.
On the Compliance settings page, in the Device Health section, set Block devices managed with device administrator to Yes > Next.
On the Actions for noncompliance tab, you can configure the available actions for noncompliance to customize the end-user experience for this flow.
Some actions to consider include:
Mark device noncompliant: By default, this action is set to zero (0) days, marking devices as noncompliant immediately. You can increase the number of days to give users a grace period. During this grace period they can see the flow to move to personally-owned work profile management without yet being marked noncompliant. For example, you can set this action to 14 days to give users the time to move from device administrator to work profile management without the risk of losing access to resources.
Send push notification to end user: Configure this action to send push notifications to the device administrator devices. When a user selects the notification, it will launch the Android Company Portal to the Update device settings page where they can start the flow to move to personally-owned work profile management.
Send email to end user: Use this action to notify users about the move from device administrator to personally-owned work profile management. In the email, you can include the following URL. When this URL is selected, it launches the Android Company Portal to the Update device settings page. From this page, they can start the flow to move to work profile management.
- For US government, you can use this link instead:
- Of course, you can use user-friendly hyper-text for the links in your communication with users. However, don't use URL-shorteners because the links may not work if changed that way.
- If the Android Company Portal is open and in the background, when a user taps the link they might go to the last page they had open instead.
- Users must tap the link on an Android device. If they instead paste it into a browser, it will not launch the Android Company Portal.
On the Scope tags page, select any scope tags you want to include.
On the Assignments page, assign the policy to a group that has devices enrolled with device administrator management > Next.
On the Review + create page, confirm all your settings, and then select Create.
The end user flow to move to new device management setup guides users through unenrolling from device administrator management. It also helps users get set up with personally-owned work profile management. Users must have Android device administrator enrolled devices with Android Company Portal version 5.0.4720.0 or later.
User sees an error after tapping Resolve
If users see an error after tapping the Resolve button, it's likely because of one of these reasons:
- Personally-owned work profile enrollment isn't set up correctly. Either an Android Enterprise account isn't connected or enrollment restrictions are set to block personally-owned work profile enrollment.
- The device is running Android 4.4 or earlier, which doesn't support personally-owned work profile enrollment.
- The device manufacturer doesn't support personally-owned work profile enrollment on the device model.
Resolve button doesn't appear on the user's device
The Resolve button won't appear on the user's device if the user enrolls into device administrator management after they've been targeted with the device compliance policy explained above.
To get the Resolve button to appear, the user must postpone setup and restart the process from the notification.
To avoid this condition, use enrollment restrictions to block enrollment into device administrator management.
User sees an error after tapping URL to Update device settings page
Users might see an error page in the browser when they tap the URL to the Update device settings page of the Android Company Portal. This error can be caused by one of the following conditions:
- The device isn't an Android.
- The Android device doesn't have the Company Portal app.
- The Android Company Portal version is earlier than 5.0.4720.0.
- The Android device uses Android 6 or earlier.
Submit and view feedback for