1.1.1. Identity, Enrollment, and Policy: Three Layers of Device Control
💡 First Principle: Each layer answers a different question — who is this device?, may we manage it?, and what should it do? — and each layer can only work once the one below it exists. That ordering is what turns a vague symptom into a precise diagnosis: find the lowest layer that is missing or broken, and fix that first.
Picture a new hire's laptop arriving at their home. Before Intune can install Microsoft 365 Apps on it, three things must already be true. The device must have an identity in Microsoft Entra ID, so policies and access decisions have an object to point at. It must be enrolled in Intune, so it has a management channel and checks in for instructions. Only then can a policy — a configuration profile, a compliance policy, an app assignment — be delivered to it.
The identity layer lives in Microsoft Entra ID. A device can be registered (a personal device where the user adds a work account), joined (an organization-owned device whose user signs in to Windows with their Entra account) or hybrid joined (joined to on-premises Active Directory and registered in Entra ID as well). The identity type tells you who owns the device and what single sign-on it gets. Phase 2 covers how to choose.
The enrollment layer lives in Intune. Enrollment creates a managed device record, installs a management profile, and starts the device's regular check-ins. How a device enrolls determines how much control you get: a corporate iPhone enrolled through Apple Business Manager can be supervised and locked down; a personal iPhone enrolled by its owner gets a narrower, privacy-preserving set of controls. Ownership — corporate or personal — is recorded at enrollment and changes what Intune is allowed to see and do.
The policy layer is everything you actually configure: device configuration profiles, compliance policies, app deployments, endpoint security policies, update policies and scripts. Every one of these is assigned to groups and delivered through the enrollment channel.
There is one deliberate shortcut. App protection policies (mobile application management, MAM) work at the app level instead of the device level. They protect organization data inside apps such as Outlook and Teams whether or not the device is enrolled, which is why they're the standard answer for personal phones whose owners won't hand device control to their employer. The dotted line in the diagram shows that path: it needs an identity (the user signs in to the app with a work account) but skips enrollment entirely.
What breaks when a layer is missing? A device with no identity can't be targeted by Conditional Access. A device that is identified but not enrolled never receives configuration profiles and can't report compliance. A device that is enrolled but not in the right group simply gets nothing — and that last case is the most common real-world "policy didn't apply" problem.
⚠️ Exam Trap: When a question says a device "appears in Microsoft Entra ID but not in Intune", the device has an identity but never enrolled. Look for answers about MDM user scope, enrollment restrictions or licensing — not about the policy itself.
Reflection Question: A contractor's personal Android phone must keep company email data from being copied into personal apps, and the contractor refuses to enroll the device. Which layers are present, which are absent, and which kind of policy still works?