Inventory for non-Windows devices
Your inventory should work for laptops, tablets, peripherals, and non-Windows devices—even if Intune workflows differ.
An inventory is still valuable even when downstream management tools vary by platform.
Capture consistent identifiers and add notes for platform-specific management differences.
Key points
- Capture identifiers that exist on the device
- Use notes for management tool differences
- Avoid forcing Windows-only assumptions
Related guides
Bulk upload CSV quality checks (before Intune import)
Before importing, validate your CSV: headers, duplicates, whitespace, and invalid characters that can cause failures.
Avoid Graph rate limits during Intune operations
Practical ways to reduce 429/503 errors when calling Graph for Intune checks/imports: batching, retries, and pacing.
Reporting and compliance for device identifier workflows
Build simple reports (counts, verification status, imports) so you can answer audits quickly without manual digging.
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.
Handling shared devices in your inventory
Shared devices need extra context: location, purpose, and ownership notes so they don’t get treated like assigned laptops.
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.
This guide is informational. If you’re using Intune features, ensure you have the right tenant permissions and administrator consent where required.