This post has been republished via RSS; it originally appeared at: Intune Customer Success articles.
By: Shanthi Thillairajah | PM | Microsoft Endpoint Manager - Intune
Microsoft Endpoint Manager – Intune support for Android Enterprise corporate-owned devices with a work profile is now in public preview! You can start enrolling devices here in the Microsoft Endpoint Manager admin center. Corporate-owned devices with a work profile is one of the corporate management scenarios in the Android Enterprise solution set. This corporate-owned, personally-enabled (COPE) scenario offers separation between work and personal profiles, similar to that offered for personally-owned work profile devices, while giving admins more device-level control. IT admins can see, control, and configure the work accounts, applications, and data in the work profile, while end users are guaranteed that admins will have no visibility into the data and applications in the personal profile. This scenario is targeted at organizations that wish to enable personal use on corporate-owned single-user devices that they have provided for work. This management scenario is available for Android 8+ (Oreo and higher) devices.
What is available in the first preview release?
This preview release is intended to demonstrate the corporate-owned work profile capabilities that we have built so far. We hope to gather feedback and iterate on the design and functionality before the end-to-end scenario becomes generally available in the Microsoft Endpoint Manager admin center. The following features are included in today’s preview:
- Enrollment: Create multiple enrollment profiles with unique tokens that do not expire. This includes device enrollment using NFC, token entry, QR code, Zero Touch, or Knox Mobile Enrollment.
- Device Configuration: A subset of the existing settings for fully managed and dedicated devices.
- App Management: App assignments, app configuration, and associated reporting capabilities. Support for app protection policies will be added in a subsequent preview update.
- Device Compliance: The compliance policies that are currently available for fully managed devices.
- Device Action: Delete device (factory reset), reboot device, and lock device are available.
- Conditional Access: The conditional access capabilities that are currently available for fully managed devices.
- Resource Access: Certs, Wi-Fi, and VPN. Support for PFX Create is not available in this preview.
- MTD Support: Admins can push MTD apps to the work profile.
What features are in development?
We are continuing to develop several other features while we collect feedback on this preview. We anticipate adding in the features below in subsequent preview updates prior to general availability. This post will be updated when these features are available in public preview:
- Support for app protection policies (APP, also known as MAM).
- Personal usage policies - these settings will configure the personal side of the device, including disabling camera and screen capture on the personal side.
- Work profile password configuration - these settings will create requirements for the work profile password. Device password configuration will be available in the initial preview release.
- Password reset device action for the work profile.
- Filter fully managed, dedicated, and corporate-owned work profile devices separately.
Intune admins can enable enrollment for this scenario by selecting the “corporate-owned devices with a work profile” enrollment tile (indicated with the red arrow below). Admins can create multiple enrollment profiles with unique tokens that do not expire.
End User Enrollment
There are new screens in the end user enrollment flow that help inform the user about the functionality of the work profile and personal profile on the device. Here are some examples of the screens:
Next, there are screens that will guide your end user through setting up admin requirements like creating a device password, installing work applications, and registering the device. After a successful enrollment, the user should see two sections labeled work and personal after they swipe up to see their full application list.
You can create device configuration profiles to assign to corporate-owned devices with a work profile to disable device features, assign certificates, or configure VPN.
To create a device configuration profile, select a profile under the “Fully Managed, Dedicated, and Corporate-Owned Work Profile” category shown below. Device configuration profiles in this category can be applied to fully managed, dedicated, and corporate-owned work profile devices.
Some of the settings in the Device Restrictions profile do not apply to corporate-owned devices with a work profile; however, there are headers under each setting category that indicate which device types a particular setting can be applied to. Below is an example of these headers used in the Users and Accounts category.
Some settings only apply at the work-profile level for corporate-owned devices with a work profile. These settings still apply device-wide for fully managed and dedicated devices. They are marked with the “work profile-level” descriptor in the setting name, as shown in the example below.
The compliance settings that are available for fully managed and dedicated devices will be applicable to corporate-owned devices with a work profile for this preview. To create a compliance policy, admins should select “Android Enterprise” as the platform and “Fully managed, dedicated, and corporate-owned work profile” as the policy type.
IT admins can deploy apps and utilize app configuration for corporate-owned devices with a work profile as a part of this preview release. To create an app configuration policy for managed devices, admins should select “Android Enterprise” for the platform and “Fully Managed, Dedicated, and Corporate-Owned Work Profile” for the profile type.
As referenced above, there is no support for app protection policies (APP, also known as MAM) in this preview release.
Customer Support for This Preview
The available preview features are fully supported through our Intune support channels.
- There is a known issue with being able to enforce a device-wide password. End users have the ability to get around device password requirements on corporate-owned devices with a work profile, regardless of admin policy. This happens when a user turns off the “use one lock” setting on their device which enables setting separate work profile and device passwords. This effectively allows the user to turn off device password and only use a work profile password with the requirements that the admin set for device password. We are working to address this issue in an upcoming release.
- There is a known enrollment bug where some devices are getting stuck on the “Updating Device…” screen after the end user inputs their corporate credentials. There is a fix that will be rolled out in the next month.
How Can You Reach Us?
As you validate and build out the Android Enterprise corporate-owned devices with a work profile preview scenarios, we would appreciate your feedback on IT admin's device configuration and end-user's device enrollment experiences. Keep us posted on your Android experience through comments on this blog post, through Twitter (@IntuneSuppTeam), and request any new features on UserVoice.
Android Enterprises Resources
For information about the new privacy protections on company-owned devices, refer to Google’s blog post.
- Set up Intune enrollment of Android Enterprise corporate-owned devices with work profile
- Enroll your Android Enterprise dedicated, fully managed, or corporate-owned with work profile devices
- Android Enterprise device settings to allow or restrict features using Intune
- Android Enterprise settings to mark devices as compliant or not compliant using Intune
Blog post updates
- 7/20/20: We previously noted that previously stated that UI was continuing to roll out. As confirmed by engineering, UI has been rolled out across all tenants and this feature is now fully available to use!
- 8/18/20: With an update to the known issues section regarding an enrollment bug and the “Updating Device…” screen. A fix will be rolled out in the next month.