1.1. The Modern Management Model
💡 First Principle: Modern management treats every device as an untrusted, internet-connected endpoint that must prove who it is and how healthy it is before it gets anything. Because management travels over the internet, the same model works for a laptop in the office, a phone on a train and a Cloud PC in an Azure region, and each layer of control can be granted or withheld independently.
Why care? Without this model, scenario questions become guesswork. Traditional management assumed devices sat on a domain network that Group Policy and imaging servers could reach. MD-102 assumes devices may never see the corporate network, may be owned by the employee, and may be provisioned straight from the manufacturer to the user's home. Answers that need line of sight to a domain controller fail there; answers built on three cloud layers work anywhere.
Think of it as a stack — identity at the bottom, enrollment in the middle, policy on top (1.1.1) — with portals that each own a slice of it (1.1.2).
⚠️ Common Misconception: Because both happen during one sign-in on a corporate Windows laptop, it's easy to assume that joining a device to Microsoft Entra ID and enrolling it in Intune are one step. They're separate layers: join or registration creates a device identity in Microsoft Entra ID, and enrollment makes the device an MDM-managed object in Intune. A personal phone can be Entra registered with only its apps managed and never be enrolled, and Windows automatic enrollment is simply a setting that chains enrollment onto join.