Understanding Different Operations of Corporate-Owned, Personally Enabled (COPE) Devices in Android Enterprise Development

[Zoe]

During the development of Android Enterprise functionality, we found that COPE (Corporate-Owned, Personally Enabled) devices operate differently compared to other devices (fully-managed corporate-owned). Is there any documentation available that details the specifics of COPE device operations?

[Alex_Muc]

There is some documentation on Android Enterprise. It depends a bit on what you want to know in detail.

There are different management sets for Work Profile (BYOD, COPE) and Fully Managed Devices. There are features per set that MDM providers can/must implement. See:
https://androidenterprisepartners.withgoogle.com/glossary/emm/#

https://developers.google.com/android/work/requirements

Ideally, it should be clear in the MDM which settings and restrictions should apply to which mode.

In short, with Fully Managed devices, administrators have comprehensive insight and control over the entire device.
With Work Profile, there are two areas. The administrators can primarily control and view the work profile. The personal area is subject to privacy and administrators can make device-wide settings that are relevant to security. (e.g. block sideloading of apps)

[Moombas]

Or to say it a bit different: COPE is a mix of BYOD and COBO where the device is owned by the company and has less admin possibilitys than on fully managed.