Device refresh workflows
A practical approach to handling bulk refresh cycles: staged capture, verification, and safe Intune import workflows.
Refresh cycles are where processes break: lots of devices, multiple techs, and tight timelines.
Stage capture first, verify second, and only then run optional Intune operations in controlled batches.
Key points
- Stage capture separately from verification
- Batch imports with clear reporting
- Keep a run log for each refresh wave
Related guides
Delegated vs app-only Graph access (Intune workflows)
Choose the right Graph auth mode: delegated tokens from Microsoft sign-in, or app-only credentials for service automation.
Device verification workflow: keep data trustworthy
A verification workflow helps separate “captured” data from “confirmed” data—especially when many people register devices.
Troubleshoot Microsoft Graph consent and privilege errors
Understand common Graph errors like ‘insufficient privileges’ and ‘admin consent required’ for Intune operations.
Manufacturer/model cleanup for device inventory
Standardize manufacturer and model values so search, reporting, and operational workflows stay consistent.
Troubleshoot serial mismatches
Serial mismatches happen due to label variations, OCR errors, or vendor formatting. Use a verification workflow to fix them safely.
Mobile-friendly IT workflows for device capture
How to design a mobile-friendly device registration flow: fast capture, offline expectations, and safe error handling.
This guide is informational. If you’re using Intune features, ensure you have the right tenant permissions and administrator consent where required.