Microsoft Entra hybrid joined device
Answer: A device joined to on-premises Active Directory and also registered as a device in Microsoft Entra ID.
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
- Not the same as Entra joined
- Requires synchronization and registration plumbing
What to check next
- Inspect dsregcmd status
- Validate SCP, sync, and device authentication
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
- Tenant ID and cloud
- Object type and object ID
- User, app, or device context
- Where the value was observed