Jamf, Intune and ADE: reliable Apple inventory without duplicates

Article created October 13, 2026 · Source reviewed October 13, 2026 · Official source: Jamf Security Cloud · Topic: Automated Device Enrollment, Intune, and compliance

Jamf Security Cloud now automatically removes duplicate device records that could appear during Automated Device Enrollment with Microsoft Intune. For an organization, the fix reduces inventory noise, but it does not replace end-to-end control across Apple Business Manager, Intune, Microsoft Entra, and Jamf.

1. What Jamf fixes exactly

In its October 8, 2026 release notes, Jamf explains that Microsoft Entra assigns a temporary identifier during Automated Device Enrollment with Microsoft Intune. When a device synced to Jamf Security Cloud before Entra assigned its permanent identifier, the temporary record could remain in inventory alongside the final record.

Jamf Security Cloud now deletes these duplicates automatically so they never appear in inventory. The announcement covers this specific case; it does not establish that every duplicate, whatever its cause, will be removed automatically.

2. Why duplicates distort operations

Two records for one endpoint can inflate counts, obscure ownership, and create inconsistencies across Jamf, Intune, and Entra. An inactive temporary record can also be mistaken for a device that is noncompliant, unprotected, or still in service.

The right measure is therefore not only the number of rows removed. Teams need to verify that each physical device converges on one permanent identity, owner, enrollment state, and consistent compliance status in every system.

3. What does this change for a Belgian or French organization?

For an SMB, the fix can reduce manual checks and counting errors. For a mid-market company, large enterprise, or public administration in Belgium or France, its main value is improving the reports used by support, security, compliance, and lifecycle teams.

GDPR also supports avoiding unnecessary records and being able to explain their purpose. Automatic deletion helps, but the organization must still govern retention, access, and the rules applied to genuinely active records.

4. Underside view: control identity convergence

Our view is that zero-touch enrollment should be tested as an identity chain, not merely as a sequence of setup screens. The serial number, hardware identifier, Entra object, Intune object, and Jamf record should converge on the same operational device.

This approach complements Apple Business Manager and Automated Device Enrollment governance and control of the Jamf–Entra ID integration. It prevents an interface cleanup from masking a synchronization defect or an incomplete return process.

5. Recommended controls

• Record current duplicates and their cause before treating the fix as effective in the tenant.
• Test a new ADE enrollment and follow the temporary identifier through to the permanent identity.
• Compare serial number, identifiers, and compliance state across Apple Business Manager, Intune, Entra, and Jamf.
• Review rules, licences, groups, and alerts that rely on device count or state.
• Also test reenrollment, erase, replacement, and return workflows to identify orphaned records.
• Document the expected synchronization delay and escalation path when a duplicate persists.

Official source: Jamf Security Cloud Release Notes — Automatic Deletion of Duplicate Device Records Created During Enrollment, published October 8 and reviewed October 13, 2026.