Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.2.3. Android Enterprise Enrollment Profiles

💡 First Principle: Android Enterprise expresses ownership as a shape on the device. A work profile is a fenced-off container, so it fits any device where personal use matters; fully managed means the whole device is work-only; dedicated means there's no individual user at all. Ask whether the device has one user and whether personal use is allowed, and the enrollment type picks itself.

Every Android Enterprise option depends on one tenant prerequisite: connecting Intune to Managed Google Play at Devices > Enrollment > Android > Prerequisites > Managed Google Play. Since August 2024 you can bind with a Microsoft Entra account instead of an enterprise Gmail account, and Microsoft recommends it; existing Gmail bindings stay supported and can be upgraded to a managed Google domain. The Entra account needs an active mailbox for Google's validation, and disconnecting later disables Android Enterprise management for the whole tenant.

The older Android device administrator method is deprecated and no longer available for devices with access to Google Mobile Services (GMS). For corporate devices without GMS, Microsoft recommends AOSP enrollment instead.

Personally owned work profile is the BYOD option. Work apps and data live in the work profile, and personal apps and data are untouched by Intune. It's allowed by default (only restriction policies created before July 2019 and never edited block it). The important 2026 change is how users enroll: Intune is moving personal work profile management to web-based enrollment (built on the Android Management API), the older Company Portal method is being phased out, and web-based enrollment is already the default for new tenants. Existing tenants switch on the profile with Use web enrollment for all users enrolling into Android personally owned work profile management, a tenant-level choice that can't be reversed. Users start from Teams or Outlook (recommended, driven by Conditional Access), the Company Portal app, or aka.ms/enrollmyandroid, in Chrome, Edge or the Samsung browser. Two caveats: don't enable it if passkeys are the tenant's only sign-in method, and note that the Personally owned = Block restriction doesn't apply to web-enrolled devices — to restrict BYOD, use COPE, or block work profiles for everyone and allow them for an approved group in a higher-priority restriction.

Corporate-owned, fully managed (COBO) devices have a single user and are work-only, which allows controls such as Managed Google Play-only installs and blocking factory reset. They need Android 10 or later with GMS. Intune creates a default fully managed profile and token, and you can't use dynamic groups with that default profile. A staging token lets IT or a vendor pre-provision the device, with the user finishing by signing in to the Microsoft Intune app.

Corporate-owned work profile (COPE) devices are single-user and corporate-owned but approved for personal use; the admin controls some device-wide settings and the work profile, and the user keeps a personal side. They need Android 8.0 or later with GMS, and default COPE tokens don't expire automatically.

Dedicated (COSU) devices are single-purpose — digital signage, ticket printing, inventory scanning — and need Android 8.0 or later with GMS. The default token needs no user credentials; a second token type deploys Authenticator in Microsoft Entra shared device mode, so shift workers sign in and out once across Microsoft apps. Dedicated tokens can be set to expire up to 65 years ahead, only Required apps install, and compliance policies should target device groups.

TypeOwnerUsersPersonal useMinimum AndroidFactory reset to enroll
Personally owned work profileEmployeeOneYes, personal side untouched—No
Fully managed (COBO)OrganizationOneNo10.0 with GMSYes
Corporate-owned work profile (COPE)OrganizationOneYes, outside the work profile8.0 with GMSYes
Dedicated (COSU)OrganizationNone (or shared device mode)No8.0 with GMSYes

Corporate devices are provisioned from the setup screen by QR code (recommended for most), Google zero-touch, Knox Mobile Enrollment, NFC, or token entry — typing afw#setup at the Google sign-in screen. Token entry and NFC don't work for COPE on Android 11. One Conditional Access gotcha: if a policy requires a compliant device (or blocks) for all cloud apps on Android, exclude the Microsoft Intune cloud app, because corporate Android setup authenticates in a Chrome tab.

⚠️ Exam Trap: "Dedicated" doesn't mean "dedicated to one person". Android Enterprise dedicated devices are single-purpose, kiosk-style devices with no user affinity — unless you use Microsoft Entra shared device mode, and even then they're shared, not personal. A corporate phone for one named employee is fully managed; if that employee may also use it personally, it's corporate-owned work profile; if the employee owns it, it's personally owned work profile.

Reflection Question: A delivery company has drivers who carry company phones they may also use for personal calls, and depot tablets that every shift shares to sign in to Teams. Which enrollment type fits each, and why would choosing fully managed for the drivers' phones create a problem the scenario doesn't want?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned