2.1. Add Devices to Microsoft Entra ID
💡 First Principle: A device identity is a directory object, like a user or a group, and how a device gets it records a promise about ownership. Registration says "this is the user's device, with a work account added"; join says "this device belongs to the organization, and you sign in to it with your work account". Single sign-on, which policies fit and how much control is appropriate all follow from that promise.
Why care? Device identities are the prerequisite for both device-based Conditional Access and Intune MDM, and the wrong join type bites: a hybrid joined laptop that never sees a domain controller becomes unusable, and an Entra joined device can't receive Group Policy. Translate each requirement ("the devices still rely on Group Policy", "employees use their own phones") into a join type.
Think of a hotel: a registered device is a guest with a key card for the facilities they need; a joined device is staff housing the organization owns and runs; a hybrid joined device is listed with both the old on-premises front desk and the new cloud booking system, so it must still check in with the old desk now and then.
⚠️ Common Misconception: Because registered and joined devices both appear in Microsoft Entra ID and can both be targeted by Conditional Access, it's tempting to treat them as interchangeable. They aren't. Registration is for personal (BYOD) devices whose users keep signing in with a local or personal account, adding a work account only to reach organizational resources; join is for organization-owned devices that users sign in to with their Entra work account.