Microsoft Entra joined device
Answer: An Entra joined device uses Microsoft Entra ID as its organizational join authority rather than an on-premises Active Directory domain and can be managed through cloud services such as Intune.
Administrator playbook
Decide, verify, and document
Use the curated answer as a starting point, then prove the outcome against the target tenant or device.
What it means
- The device has an organizational Entra device identity
- It is different from Entra registered and hybrid joined
- Windows Home cannot perform the same organizational join
What to check next
- Inspect AzureAdJoined in dsregcmd
- Confirm tenant ID and device ID
- Verify MDM enrollment separately from join state
Verify success
- Confirm the object type and identifier in the authoritative tenant.
- Compare the portal value with Microsoft Graph or the local device state.
- Use IDs—not display names—when proving that two references point to the same object.
Escalate when
- Two portals or APIs return conflicting identifiers for the same expected object.
- The issue crosses tenant or cloud boundaries.
- A production authorization decision depends on the object relationship.
Copyable admin briefAnswer, next checks, source, and review date
Inspect Microsoft Graph context
Get-MgContext | Select-Object ClientId,TenantId,Account,AuthType,ScopesRead-only. Useful when a term or identifier is being interpreted in the wrong tenant.
Evidence to preserve
- Local signal
- AzureAdJoined = YES
- Authority
- Microsoft Entra ID
- Management
- Separate MDM state
- Tenant ID and cloud
- Object type and object ID
- User, app, or device context
- Where the value was observed