Built a framework for SCCM-to-Intune migration that eliminates manual Autopilot import — 6.5 hours to 30 minutes, zero touch for help desk
If your organization is transitioning from SCCM to Intune, you've probably run into this problem:
Devices that were imaged with SCCM but have since lost domain connectivity. They're orphaned — you can't reach them through the domain, and the only option Microsoft gives you is a full Dell Cloud BIOS reset which takes 6.5 hours per device. For a fleet of 2,000+ devices that's simply not workable.
I built a framework that solves this. Here is what it actually changes for your team:
**For Help Desk:**
No more manual CSV exports. No more uploading hardware hashes to the Intune portal. No more waiting for sync cycles. The technician selects one dropdown during OOBE — 30 seconds of interaction — and walks away. Everything else is automated.
**For IT Operations:**
You control the Windows image through SCCM task sequences. This means consistent OS version, drivers, and baseline configuration across every device. You are not dependent on whatever version Dell Cloud pushes. Full Windows version control stays with your team.
**For Management:**
Devices automatically join the correct Azure AD dynamic group based on department. The right apps deploy automatically. No post-provisioning reconfiguration needed.
**The result:**
6.5 hours → 30 minutes per device. 92% reduction. Scales to thousands of devices without linear increase in help desk workload.
**How it works:**
The framework uses an SCCM task sequence to deploy a clean Windows 11 image, then during OOBE a popup appears asking the technician to select an organizational unit. The device registers in Autopilot via Graph API automatically, the SCCM client removes itself via SetupComplete.cmd, and the device hands off cleanly to Intune with no dual-management conflicts.
**Five technical challenges I had to solve:**
Showing interactive UI during OOBE — ServiceUI.exe bridges Session 0 to Session 1
Mouse cursor invisibility on physical hardware during early OOBE — multi-layer Win32 ShowCursor fix with continuous timer
Window not receiving keyboard focus — aggressive Win32 activation sequence
Temporary SCCM client installation and auto-removal via SetupComplete.cmd
Graph API Autopilot registration during OOBE before Autopilot handoff begins
Full framework with scripts and documentation:
github.com/alugoju/autopilot-provisioning-framework
Happy to answer questions. The cursor management on physical hardware vs VMs took the most trial and error — hope this saves someone else that headache.