Autopilot is not Deployment

Workplace Ninjas Belgium – 4th July 2026

Our session Autopilot is not Deployment explains why bare-metal Windows deployment still matters in a modern Autopilot and Intune world. Autopilot has transformed endpoint onboarding by giving organisations a cloud-led way to enrol devices, apply policy, configure security, and move users into a managed Windows experience. But Autopilot does not install Windows, prepare storage, apply drivers, recover broken devices, or rebuild compromised machines. It begins only once Windows and OOBE are already present and functional.

You can download a copy of the slides from here

The session explores the gap between cloud onboarding and real-world deployment. That gap appears during hardware replacement, failed updates, malware recovery, device repurposing, non-OEM procurement, large-scale migration, and disaster recovery scenarios. In those moments, “just use Autopilot” is not enough, because there may be no trusted operating system for Autopilot to work from.

Our presentation positions OneDeploy as the missing deployment foundation beneath Autopilot. OneDeploy can deploy Windows from bare metal, apply the right drivers, install common base applications, include updates and configuration, and then reseal the device back to OOBE so Autopilot can take over cleanly. This allows the predictable heavy work to happen before the user sees the device, rather than relying on first-login internet downloads, slow branch connections, or user-facing enrolment delays.

We also explain how OneDeploy separates deployment metadata from customer-controlled content, supports local, network, USB and cloud deployment sources, and dynamically assembles builds using reusable operating systems, applications and drivers. This avoids traditional image sprawl while giving organisations a controlled, repeatable, and technically robust rebuild process.

For MSPs, the value is especially clear. Every customer, device type, app stack and OS version can multiply deployment effort. OneDeploy’s multi-customer model allows MSPs to centralise common engineering work, maintain customer separation, support customer-specific Autopilot enrolment, and turn device deployment and recovery into a scalable managed service.

The central message is simple: Autopilot is excellent at cloud onboarding, but it is not the whole lifecycle. OneDeploy gets devices to a clean, trusted starting line. Autopilot takes them from there.

You can also download our more detailed guide to OneDeploy and AutoPilot for Deployment.