2.1.1. Choosing a Device Join Type
💡 First Principle: Choose the join type by asking two questions in order: who owns the device, and does it still depend on on-premises Active Directory? Ownership separates registration from the two join types, and an on-premises dependency is the only good reason to choose hybrid join over cloud-native Entra join. Microsoft itself calls hybrid join "an interim step on the road to Microsoft Entra join".
There are exactly three ways for a device to get an identity in Microsoft Entra ID, and all three can coexist in one organization. A company might Entra join every new laptop, keep hybrid join for an older fleet that still runs Group Policy, and let employees register their personal phones.
Microsoft Entra registered (older material calls it Workplace joined) is aimed at BYOD and mobile devices. The user signs in with their own credentials — a Microsoft account on a personal Windows PC, for example — and uses the Entra account only to reach organizational resources. Registration happens when the user first opens a work app, or manually through Windows Settings (the Company Portal or Microsoft Authenticator on mobile). Remember that registration isn't enrollment: MDM enrollment is a separate, further step, and many registered phones never take it, relying on app protection policies instead.
Microsoft Entra joined devices require an organizational account to sign in, and the organization owns them. Joined devices get SSO to cloud and on-premises resources — they can still reach on-premises file and print servers when they have line of sight to a domain controller — and users get self-service password reset and Windows Hello PIN reset from the lock screen. Typical fits are cloud-first organizations, remote and branch workers, seasonal staff, and users who live mostly in Microsoft 365 and SaaS apps.
Microsoft Entra hybrid joined devices are joined to on-premises AD and registered with Entra ID. They're the right choice when you must keep Group Policy, keep existing imaging, or support Win32 apps that rely on AD machine authentication. The price is that hybrid joined devices need periodic network line of sight to on-premises domain controllers; Microsoft's own wording is that without this connection "devices become unusable". Hybrid join is set up through Microsoft Entra Connect or AD FS, and since 2026 Microsoft Entra Cloud Sync can also sync AD computer objects for hybrid join (though it doesn't configure AD FS or federation).
| Microsoft Entra registered | Microsoft Entra joined | Microsoft Entra hybrid joined | |
|---|---|---|---|
| Owner | User or organization | Organization | Organization |
| Signs in to the device with | Local or personal account | Entra work account | Organizational (AD) account |
| Typical devices | Personal Windows, iOS, Android, macOS, Linux | Windows 10/11 (not Home), macOS 13+, Linux, Azure VMs | Windows 10/11 (not Home), Windows Server 2016–2022 |
| Provisioning | Settings, Company Portal, Authenticator | OOBE or Settings, bulk enrollment, Windows Autopilot | Domain join or Autopilot domain join, plus Entra Connect or AD FS |
| Management | Intune MDM (optional) or app protection | Intune MDM, or Configuration Manager co-managed | Group Policy, Configuration Manager, optionally co-managed with Intune |
| SSO | Cloud resources | Cloud and on-premises | Cloud and on-premises |
trustType in Entra | Workplace | AzureAD | ServerAD |
The planning constraints for Entra join are where the exam finds its distractors. Group Policy isn't supported on Entra joined devices — Microsoft states that management "is only possible through MDM" — so before moving a fleet, use Group Policy analytics in Intune to check how many of your GPO settings have MDM equivalents. Entra joined devices also can't be deployed with Sysprep or similar imaging tools, don't support on-premises apps that rely on machine authentication, and can't use RADIUS Wi-Fi authentication that depends on an on-premises computer object (push certificates from Intune or use user credentials instead). Mobile application management doesn't apply to Entra joined devices at all; MAM is for devices the organization doesn't manage.
One more planning detail matters for licensing. With Microsoft Entra ID P1 or P2, MDM enrollment is automated as part of Entra join for users in the MDM user scope, and if that enrollment fails, the join is rolled back. A user outside the MDM scope completes the join without enrolling, which leaves you with an organization-owned but unmanaged device.
⚠️ Exam Trap: Hybrid join is not the "safe" middle option. If a scenario's devices rarely or never reach the corporate network — field staff, home workers, a new remote office — hybrid join is wrong because those devices need periodic contact with a domain controller. Choose Entra join, and solve any remaining on-premises needs another way.
Reflection Question: A company wants to move 2,000 domain-joined laptops to cloud management, but a payroll app authenticates with the computer's AD account and 300 laptops belong to sales staff who almost never visit an office. Which join type fits each group today, and what would have to change before the payroll users could move to Entra join?