Microsoft 365, AD and Windows · #37

Online Intune Device Inventory Reconciliation

Matches device records from three sources; name similarity is never treated as a certain match.

  • Data is processed in your browser and not sent to a server
  • Export: CSV

Tool

Get-ADComputer -Filter * | select Name

displayName,deviceId columns required.

deviceName,azureADDeviceId[,serialNumber]

What does this tool do?

A device has separate records in AD, Entra and Intune, and they drift: a reimaged computer leaves two records in Entra, a device deleted from Intune stays in Entra. Matching by name gives wrong results in these cases. The tool matches Intune ↔ Entra exactly by azureADDeviceId; AD ↔ Entra by name is marked 'probable', and several Entra records with the same name are 'ambiguous'.

How to use it

  1. Paste the Entra device list with displayName,deviceId, the Intune list with deviceName,azureADDeviceId,serialNumber and the AD list with Name as CSV.
  2. Press Calculate; download the table as CSV.

Fields

AD computers (optional)
Get-ADComputer -Filter * | select Name
Entra devices
displayName,deviceId columns required.
Intune devices (optional)
deviceName,azureADDeviceId[,serialNumber]

Worked example

InputValue
AD computers (optional)
Name
PC-0042
PC-0043
LAB-01
PC-0099
Entra devices
displayName,deviceId
PC-0042,5f2a9c1e-7b3d-4e8a-9c21-0a1b2c3d4e5f
PC-0043,6a3b8d2f-8c4e-5f9b-ad32-1b2c3d4e5f60
LAB-01,7b4c9e30-9d5f-6a0c-be43-2c3d4e5f6071
LAB-01,8c5d0f41-ae60-7b1d-cf54-3d4e5f607182
Intune devices (optional)
deviceName,azureADDeviceId,serialNumber
PC-0042,5f2a9c1e-7b3d-4e8a-9c21-0a1b2c3d4e5f,CZC1234ABC
PC-0043,6a3b8d2f-8c4e-5f9b-ad32-1b2c3d4e5f60,CZC1234ABD
TABLET-07,00000000-0000-0000-0000-000000000000,R52M90XYZ

Expected result: PC-0042 and PC-0043 in all three sources (Intune certain, AD probable); LAB-01 has two Entra records → ambiguous; TABLET-07 is in Intune but its Entra ID does not match; PC-0099 only in AD.

One of LAB-01's Entra records is probably left over from a reimage; confirm which is active by the last activity date in Entra and do not delete automatically. TABLET-07's zero GUID shows the Intune record is not linked to Entra.

Method and assumptions

An Intune row matches exactly if its azureADDeviceId equals an Entra deviceId (case-insensitive).

An AD row is probable if the first label of its name matches one Entra record; with several Entra records of that name it is ambiguous and not matched automatically.

Using the result and troubleshooting

Ambiguous records and records in one source only are clean-up candidates; check last activity first. For hybrid devices check the device state with the dsregcmd Output Analyzer.

Limits and common mistakes

  • Matching Entra onPremisesSecurityIdentifier to AD SIDs is not done in this version.
  • Last activity dates are not evaluated.

Frequently asked questions

Why are two devices with the same name not merged?

The same name may belong to two physical devices or to the old and new record of one device. A wrong merge leads to deleting a healthy record.

Related tools and service

  • dsregcmd Output AnalyzerExtracts the join type, PRT state and diagnostic codes from dsregcmd /status output and produces a masked copy for sharing.
  • Entra Connect Sync Inventory DiffMatches on-premises AD and Entra user lists by source anchor; shows attribute differences and unmatched objects.

Related service: Microsoft 365, Azure, AWS and Google Cloud Services

Systems online tools · See all online tools