Reconcile inventory vs Intune
How to reconcile differences between your internal inventory and Intune state: mismatches, missing devices, and duplicates.
It’s normal for systems to drift. Inventory is a capture/verification record, while Intune reflects management state.
When discrepancies appear, use your audit logs and verification status to determine what to trust.
Key points
- Treat drift as normal and manageable
- Use audit logs to trace changes
- Investigate mismatches before re-uploading
Related guides
Corporate Device Identifier Helper: what it does
Capture device label info, keep a lightweight inventory, and optionally upload corporate identifiers to Intune—using Microsoft sign-in.
Device identity data sources: where identifiers come from
Understand common sources of device identifiers (labels, purchase records, BIOS/UEFI, asset tags) and how to reconcile differences.
Clerk + Microsoft OAuth setup overview
A high-level overview of what needs to be configured to enable Microsoft sign-in and delegated Graph access in a Next.js app.
Device registration checklist for IT teams
A short checklist for consistent device registration: capture, verify, annotate, and optionally sync identifiers.
Bulk upload CSV quality checks (before Intune import)
Before importing, validate your CSV: headers, duplicates, whitespace, and invalid characters that can cause failures.
Tenant admin consent process (what to expect)
What admins typically need to do to grant consent for Graph permissions, and how to validate success afterward.
This guide is informational. If you’re using Intune features, ensure you have the right tenant permissions and administrator consent where required.