Identifier-based asset deduplication

​What it is — We're rolling out identifier-based deduplication for hardware assets. When more than one tool reports the same physical device — say Kandji and an Atomicwork Discovery scan both pick up the same MacBook — Atomicwork now merges them into a single asset record, with every contributing source listed on it.

Why it matters — Without this, every integration creates its own record for each device, so it shows up as two or three separate assets. That inflates your asset count, splits lifecycle history across records, and makes audits and license tracking harder than they should be.

Now you get one accurate record to assign, ticket, and report on, pulled together from Intune, Kandji, Jamf, Azure AD, Atomicwork Discovery, and manual/API/CSV additions.

How it works — Matching runs automatically, using shared hardware identifiers to confirm two records belong to the same device.

Note: If you're importing assets via CSV, import before connecting your integrations to avoid duplicate rows.

​Learn more
​