097: Userless Enrollment
Implementation Effort: Medium
User Impact: Medium
Overview
Userless enrollment is used when a device is intended for a shared task, kiosk, scanner, meeting room, or other scenario where associating the device with one primary user is not the right management model. In Intune, this typically maps to dedicated-device or similar device-centric management patterns. For Zero Trust, userless devices should have highly constrained functionality, device-based targeting, limited data persistence, and a clear reprovisioning path when the device changes hands or falls out of a healthy state.
Implementation Guidance
- Select the correct enrollment pattern for the scenario, such as Android Enterprise dedicated devices or a supported AOSP path when Google Mobile Services are not present.
- Use automated provisioning where possible, such as QR, zero-touch, or other bulk onboarding methods that fit your hardware supply chain.
- Target policies and apps to device groups rather than user groups when no primary user context exists.
- Deploy only the required apps and settings, and pair the device with kiosk, launcher, network, update, and compliance controls appropriate to its role.
- Document the operational lifecycle: how the device is named, handed out, recovered, reset, and returned to service.
- Monitor for drift, app crash loops, and devices that are offline or stuck outside compliance for extended periods.
Reference
- Android device enrollment guide for Microsoft Intune - Microsoft Intune — Summarizes enrollment options and tasks for Android Enterprise dedicated devices in Intune.
- Step 5 – Enroll devices in Microsoft Intune - Microsoft Intune — Includes AOSP corporate-owned userless and user-associated enrollment paths in Intune.
- Configure the Microsoft Managed Home Screen App - Microsoft Intune — Explains how to configure Managed Home Screen for Android Enterprise devices.