Who this is for
- A technician still images each laptop by hand, and remote staff wait days for a replacement.
- Group Policy applies inconsistently because devices are rarely on the office network or VPN.
- BitLocker, update and Defender status is unknown for part of the fleet.
- You want Conditional Access to require compliant devices but cannot see compliance today.
- A merger brought devices managed in another tenant.
- Macs, iPhones and Android phones are managed differently, or not at all.
What is in scope, and what is not
Usually in scope
- Review of current device management, Group Policy, imaging and how devices are bought
- Entra join or hybrid join decision, documented
- Intune enrollment, compliance policies and configuration profiles
- Security baselines, BitLocker, Windows LAPS and Defender settings
- Windows Autopilot for new and replacement devices
- Packaging and deployment of core apps
- Update rings for Windows and Microsoft 365 Apps
- A wave plan for existing devices and help-desk runbooks
Handled separately or agreed during discovery
- Packaging every niche or departmental app beyond the agreed core list
- Specialty devices with on-premises dependencies, which stay on the path that fits them
- Hardware purchasing and shipping
- Mac, iPhone and Android enrollment, when not part of the agreed scope
How the project runs
- Assess. Device inventory, join state, Group Policy analytics, app catalog and support process.
- Design. Join type, rings, baseline settings and the success criteria for each ring.
- Build in the IT ring. Policies, apps and Autopilot tested on IT devices first.
- New and replacement devices. Autopilot goes live early, so improvements show up before the existing fleet moves.
- Pilot department. Real users and real apps, with defects fixed before wider rings.
- Existing devices in waves. Moved location by location or department by department, not in one weekend.
- Compliance enforcement last. Conditional Access that requires compliant devices is switched on only when enrolled devices report compliant.
- Handover. Policy documentation, onboarding guide and runbooks for enrollment failures, resets and replacements.
More risks we plan for
| Risk | How we handle it |
|---|---|
| Existing devices are not registered for Autopilot | Hardware hashes collected, or registration arranged through your reseller or OEM |
| Removing local admin rights breaks apps | Apps tested in the pilot ring and exceptions documented |
| BitLocker recovery keys are not escrowed | Key escrow confirmed before encryption is enforced |
| An update breaks a line-of-business app | Pilot update ring and a pause and rollback path |
| Help desk is not ready | Runbooks and a walkthrough before each wave |
What we need from you
- Licenses that include Intune, such as Microsoft 365 Business Premium or E3/E5
- Admin access to Intune and Entra ID
- A device inventory and how you buy devices (reseller or OEM)
- Installers and license keys for the apps in scope
- Pilot users at each location and a local contact
- Change windows for each wave
How long it takes
Our Intune and Autopilot package lists a typical duration of 6 to 14 weeks, set after discovery. The rollout in our case study, about 280 Windows devices across 11 offices and field locations with 4 deployment and update rings, took 12 weeks from baseline to handoff.
Proof from a similar project
From desk-side laptop imaging to cloud provisioning: hands-on IT setup for the standard build fell from roughly two hours to under 30 minutes, standard laptops ship directly from the supplier and enroll through Autopilot, and more than 95% of enrolled Windows devices reported compliant at handoff, with exceptions documented.