Study guide

Microsoft Entra Device Identity and Grouping

MD-102 Endpoint Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Exam Overview and MD-102 Study Strategy

Current Exam Facts Audience Profile and Endpoint Admin Mental Model Domain Map and Weighting Strategy Six-to-Ten-Week Study Plan and Readiness Checklist

2 Prepare Infrastructure for Devices

Microsoft Entra Device Identity and Grouping Intune Enrollment by Platform Compliance and Conditional Access Admin Roles, Windows Hello, Windows LAPS, and Local Groups

3 Deploy and Configure Managed Devices

3.1 Autopilot vs. Provisioning Packages 3.2 Autopilot Modes, ESP, and Naming 3.3 Windows 11 Upgrades and Windows 365 Cloud PCs 3.4 Configuration Profiles and Assignment Filters

4 Intune Suite, Remote Actions, and Operational Troubleshooting

4.1 Endpoint Privilege Management and Enterprise App Catalog 4.2 Advanced Analytics, Remote Help, Cloud PKI, and Tunnel for MAM 4.3 Remote Actions and Bulk Actions 4.4 Defender Intelligence, BitLocker Key Rotation, and KQL Device Query Troubleshooting

5 Manage Applications with Intune

5.1 App Deployment Decision Matrix and Packaging 5.2 Microsoft 365 Apps, Office Policies, ODT, OCT, and Admin Center 5.3 App Stores and Update Lifecycle 5.4 App Protection, App Configuration, and Conditional Access

6 Protect Devices, Manage Updates, and Final Review

6.1 Endpoint Security Policies and Security Baselines 6.2 Defender for Endpoint Integration and Onboarding 6.3 Update Rings, Feature Updates, Platform Updates, and Delivery Optimization 6.4 Final Seven-Day Review Plan and Mixed Scenario Priorities

Microsoft Entra Device Identity and Grouping

Key Takeaways Explain This Topic AI

The current MD-102 Prepare infrastructure domain expects you to choose between Microsoft Entra joined, Microsoft Entra registered, and Microsoft Entra hybrid joined device states.

Use Microsoft Entra joined for organization-owned cloud-first devices, Microsoft Entra registered for BYOD access, and Microsoft Entra hybrid joined only when on-premises Active Directory dependencies still matter.

A Microsoft Entra device identity is the object that Intune, Conditional Access, and device-targeted groups use to make management and access decisions.

Security groups can contain devices or users, but Microsoft 365 groups contain users only; dynamic groups can be dynamic user or dynamic device, not both.

Dynamic device rules should use stable device attributes such as deviceTrustType, managementType, or enrollment-related values instead of user attributes.

Last updated: June 2026

Why device identity is the first infrastructure decision

Microsoft's current MD-102 study guide lists Prepare infrastructure for devices at 25-30% of the exam and starts with adding devices to Microsoft Entra ID. That is not just terminology. Device identity controls how users sign in, whether the device can satisfy device-based Conditional Access, how Intune sees the endpoint, and which groups can target enrollment, compliance, and configuration. Get the identity decision wrong and every downstream policy targets the wrong population.

Microsoft Entra ID can represent a device in three main ways: Microsoft Entra registered , Microsoft Entra joined , and Microsoft Entra hybrid joined . The exam usually gives you business constraints, not a direct vocabulary question. Read for ownership, sign-in identity, on-premises dependency, and desired management level.

Scenario clue Best device state Why it fits

New corporate Windows laptops, cloud-only tenant, users sign in with work accounts Microsoft Entra joined The device is organization-owned and joined only to Microsoft Entra ID, which supports modern sign-in and Intune enrollment.

Personal Windows, iOS, Android, or macOS device that should keep the user's existing personal sign-in Microsoft Entra registered Registration gives the device a workplace identity for resource access without converting it into a fully joined corporate device.

Existing domain-joined Windows devices still need Group Policy, domain line-of-sight, or AD machine authentication Microsoft Entra hybrid joined The device remains joined to Windows Server Active Directory and is also represented in Microsoft Entra ID.

No Microsoft Entra object, no Intune management, local-only sign-in Workgroup or local-only This rarely satisfies MD-102 management requirements unless the question is asking what is missing.

Join and register decisions

Microsoft Entra joined is the modern default for organization-owned Windows endpoints when the tenant can manage devices from the cloud. It is also a strong answer for remote workers because it avoids requiring line-of-sight to domain controllers during normal use. Pair it with Intune automatic enrollment by making sure the user is licensed and in the Microsoft Intune MDM user scope, so the join also triggers enrollment.

Microsoft Entra registered is the lighter BYOD state. A user adds a work or school account to an existing device, and the device receives a Microsoft Entra device object while keeping its personal sign-in. Registration alone is not the same as Intune enrollment. If the organization requires a compliant BYOD device, the user normally registers the device and then enrolls it into Intune so compliance policies can evaluate it.

Microsoft Entra hybrid joined is appropriate when the organization is not ready to leave on-premises Active Directory. Microsoft notes that hybrid joined devices need periodic line-of-sight to domain controllers; if that is a problem for remote staff, favor Microsoft Entra join. On MD-102, hybrid join is usually the right answer only when the scenario explicitly mentions legacy Group Policy, domain-joined computer accounts, on-premises apps that use machine authentication, or an existing Configuration Manager co-management design.

Microsoft's stated guidance is that new cloud-native deployments should use Microsoft Entra join, so treat hybrid join as the legacy-compatibility answer, not the default.

Grouping for Intune and Conditional Access

Groups are how an endpoint administrator turns identity into targeting. Use security groups for device management, app assignment, compliance policies, Conditional Access scoping, and administrator delegation. Microsoft 365 groups are collaboration groups and can only contain users, so they are not the right answer for device-membership targeting.

Group choice Use it when MD-102 trap

Assigned user group You need a stable pilot, department, or ring based on people A user assignment follows the user across multiple devices. That may be good for apps, but not always for device-specific controls.

Assigned device group You need exact membership for high-risk devices, shared devices, or break-fix targeting Manual membership is precise but does not scale well.

Dynamic device security group You need automatic membership based on device attributes Device rules cannot reference the device owner's user attributes.

Dynamic user security group You need automatic membership based on user attributes such as department This targets users, not a specific hardware population.

Useful dynamic device rule patterns include all devices with device.objectId -ne null , Microsoft Entra joined devices with device.deviceTrustType -eq "AzureAD" , hybrid joined devices with device.deviceTrustType -eq "ServerAD" , and registered devices with device.deviceTrustType -eq "Workplace" . For Intune-managed devices, device.managementType -eq "MDM" is often more meaningful than join state alone, because it isolates the devices Intune actually manages.

Plan groups around the policy lifecycle. A compliance policy might target all managed corporate Windows devices. A Conditional Access policy might target all users but exclude break-glass accounts. An enrollment profile might target a dynamic device group populated by an enrollment profile name or other enrollment-time attribute. The exam rewards understanding that groups are not just containers; they are the control plane for who receives settings and who is evaluated for access.

Exam checklist

Identify ownership first: corporate, personal, shared, kiosk, or contractor-owned.

Identify sign-in requirements: work account primary sign-in, personal sign-in with work access, or domain sign-in.

Identify legacy dependencies: Group Policy, on-premises AD, domain controllers, or Configuration Manager.

Choose the group type that matches the target: user group for people, device group for devices, security group for management, dynamic group for scale.

Remember that registration, join, and Intune enrollment are related but separate concepts, and a device can have an Entra identity without being enrolled.