Microsoft 365, AD and Windows · #36

Online Entra Connect Sync Inventory Diff

Matches on-premises AD and Entra user lists by source anchor; shows attribute differences and unmatched objects.

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

Tool

CSV with header. Data does not leave your browser.

CSV with header.

Name of the objectGUID or ms-DS-ConsistencyGuid column.

GUID → Base64: the AD GUID is converted to ImmutableId format.

What does this tool do?

In hybrid identity a user's two records are linked not by name or UPN but by the sourceAnchor: by default the AD objectGUID (or ms-DS-ConsistencyGuid), shown in Entra as the Base64 onPremisesImmutableId. The tool performs this conversion, matches the lists and lists value differences in columns with the same name.

How to use it

  1. Export AD: Get-ADUser -Filter * -Properties mail | select objectGUID,userPrincipalName,mail,displayName | ConvertTo-Csv -NoTypeInformation.
  2. Export Entra via Graph or the Entra admin center with onPremisesImmutableId,userPrincipalName,mail,displayName.
  3. Choose key column names and encoding and press Calculate. Compared attributes are columns with the same name in both lists.

Fields

On-premises AD CSV
CSV with header. Data does not leave your browser.
Entra CSV
CSV with header.
AD key column
Name of the objectGUID or ms-DS-ConsistencyGuid column.
Entra key column
Key encoding
GUID → Base64: the AD GUID is converted to ImmutableId format.

Worked example

InputValue
On-premises AD CSV
objectGUID,userPrincipalName,mail,displayName
b3a1c2d4-1e2f-4a5b-8c9d-0e1f2a3b4c5d,[email protected],[email protected],Ayşe Demir
7f1e2d3c-4b5a-6978-8a9b-0c1d2e3f4a5b,[email protected],[email protected],Ali Yılmaz
0a0b0c0d-1111-2222-3333-444455556666,[email protected],,SQL Service
Entra CSV
onPremisesImmutableId,userPrincipalName,mail,displayName
1MKhsy8eW0qMnQ4fKjtMXQ==,[email protected],[email protected],Ayşe Demir
PC0ef1pLeGmKmwwdLj9KWw==,[email protected],[email protected],Ali Yılmaz
zzzzzzzzzzzzzzzzzzzzzz==,[email protected],,Eski Kullanıcı

Expected result: Ayşe matches but the UPN differs (ayse.demir ↔ ayse.kaya); Ali matches and is identical; the SQL service account is only in AD; 'Eski Kullanıcı' only in Entra.

Ayşe's UPN changed in AD but did not reach Entra: if the UPN domain (contoso.com) is verified and in sync scope, Entra Connect should update it; otherwise check the sync error log. The AD-only service account has a .local UPN and is most likely out of scope on purpose.

Method and assumptions

Default conversion: the 16 bytes of objectGUID in Windows GUID byte order (first three fields little-endian) are Base64-encoded; that is the ImmutableId in Entra. The same applies to ms-DS-ConsistencyGuid.

For matched records, columns with the same name in both lists (except the key) are compared case-insensitively.

Using the result and troubleshooting

AD-only users may be outside the sync scope (OU/group filter) or in error; Entra-only users may be cloud accounts or old records that never soft-matched.

For attribute differences AD is always the source; do not edit in Entra, fix in AD and wait for sync.

Limits and common mistakes

  • Entra Connect's rules engine (transformation rules) is not executed; two exports are compared.
  • Groups and devices are out of scope in this version.

Frequently asked questions

Why is ImmutableId Base64 and not a GUID?

Entra stores the source anchor as bytes and shows it as Base64. The tool converts the GUID text to Windows byte order and Base64-encodes it.

Related tools and service

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

Systems online tools · See all online tools