Add devices to Microsoft Entra ID
Choosing between Entra registration, Entra join and hybrid join, joining and registering devices, and device groups with dynamic membership rules.
- 14 min
- 4 concepts
- Try it yourself
- 4-question check
Learn
Before Intune can manage a device well, Entra ID needs to know about it. How a device is added decides who owns it, how users sign in and which policies can target it.
- 1
Choose an appropriate device join type, including considerations such as device registration and Microsoft Entra join
Entra registered: personal (BYOD) Windows, macOS, iOS and Android devices; users add a work account. Entra joined: organisation-owned Windows 10/11 (and macOS with Platform SSO) signed in with a work account; recommended for new cloud-first devices. Hybrid joined: joined to on-premises AD and registered in Entra ID, for existing estates that still depend on Group Policy or on-premises authentication.
Remember: New corporate Windows devices: Entra join.
- 2
Join devices to Microsoft Entra ID
Join during OOBE (signing in with a work account, or automatically with Autopilot) or later from Settings > Accounts > Access work or school > Join this device to Microsoft Entra ID. Device settings control Users may join devices, the maximum number of devices per user and whether MFA is required. With MDM auto-enrolment set up, the device enrols in Intune when it joins.
Remember: Join + automatic enrolment = managed from day one.
- 3
Register devices to Microsoft Entra ID
Registration happens when a user adds a work or school account (Windows), installs and signs in to the Company Portal or Microsoft Authenticator (iOS, Android, macOS), or enrols as a personal device. The user keeps signing in with their personal account. Registration lets Conditional Access see the device.
Remember: Registered devices sign in with a personal account.
- 4
Plan and implement groups for devices in Microsoft Entra ID, including dynamic group membership rules
Device groups target policies and apps at devices regardless of who signs in. Dynamic device rules use properties such as
device.deviceOSType,device.deviceOwnership,device.deviceModel,device.enrollmentProfileNameanddevice.devicePhysicalIds(for Autopilot group tags), for example(device.devicePhysicalIds -any (_ -eq "[OrderID]:Sales")).Remember: Autopilot group tag → OrderID in devicePhysicalIds.
Device identity options
| Option | Ownership | Sign in with | Best for |
|---|---|---|---|
| Entra registered | Personal | Personal account | BYOD |
| Entra joined | Corporate | Work account | New cloud-first devices |
| Hybrid joined | Corporate | AD account | Existing AD-dependent estates |
Try it
Pick the join type.
This interactive part needs JavaScript.
In the portal
- Device settingsEntra admin center: Entra ID > Devices > Device settings
- Dynamic device groupIntune admin center: Groups > New group
- All devicesEntra admin center: Entra ID > Devices > All devices
Key terms
Click a card to see the definition.
Check your understanding
4 questions. Score 80% or more and these skills are marked as confident in your MD-102 study plan.
Which join type suits a new corporate laptop with no AD dependency?
Entra join is recommended for cloud-first corporate devices.
Which property targets Autopilot group tags in a dynamic rule?
Group tags appear as [OrderID] in devicePhysicalIds.
Where do you limit how many devices each user can join?
Maximum number of devices per user is a device setting.
What happens when a user adds a work account to a personal Windows PC?
Adding a work account registers the device.
Sources
- Microsoft Learn: What is a device identity?
- Microsoft Learn: Plan your Microsoft Entra join deployment
- Microsoft Learn: Dynamic membership rules for devices
- Microsoft Learn: Create an Autopilot device group
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.