Microsoft Entra device ID

Answer: The Entra device ID identifies the device object in one tenant; it is distinct from the Windows hardware identity, Intune managedDevice ID, Autopilot identity, and local certificate identifiers.

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

Re-registration can create a new directory device object
Intune and Autopilot maintain separate service records
The device ID is tenant-scoped

What to check next

Match dsregcmd DeviceId to the Entra device object
Cross-reference Intune using Azure AD device ID fields rather than display name
Remove stale duplicates only after confirming the active identity

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,Scopes

Read-only. Useful when a term or identifier is being interpreted in the wrong tenant.

Evidence to preserve

Scope: One tenant
Local source: dsregcmd /status
Not the same as: Intune managedDevice ID

Tenant ID and cloud
Object type and object ID
User, app, or device context
Where the value was observed

← Search another