Autopilot v1 or Autopilot v2?

A few years back, I worked with an enterprise rollout where everything looked perfect on paper—devices were ready, profiles were configured, and timelines were tight. But once deployment started, reality kicked in.
Devices failed to recognize profiles, provisioning got stuck midway, and troubleshooting became a daily routine. What was expected to be a smooth zero-touch deployment quickly turned into a dependency-heavy process requiring constant monitoring.
This wasn’t a one-off case. This is how traditional Autopilot behaves when there are too many moving parts—device registration, hybrid identity, ESP dependencies, and app sequencing.

Fast Forward to Today
Now imagine a different experience.
A user opens a new device, signs in, and within minutes the device is configured, secured, and ready. No manual pre-registration. No unpredictable app installs. No complex provisioning states.
That’s where the new Autopilot Device Preparation (often referred to as Autopilot v2) changes the game.
But here’s the important part—this is not a replacement. It’s an evolution with trade-offs.
Two Approaches, Two Mindsets
Instead of comparing features, think of this as two different philosophies:
Classic Autopilot (v1) — Control & Flexibility
This model is built for environments where control matters more than speed.
Works well with hybrid environments
Supports multiple deployment scenarios (kiosk, shared, pre-provisioned)
Allows deep customization during setup
Handles complex enterprise requirements
But it comes at a cost:
More dependencies
Slower provisioning
Higher chances of failure during ESP

Autopilot Device Preparation (v2) — Simplicity & Speed
This approach is designed for modern, cloud-first organizations.
No hardware hash dependency
Streamlined provisioning experience
Faster device readiness
Improved visibility and troubleshooting
However, it intentionally removes complexity:
No hybrid join
Limited customization
Fewer apps during provisioning
Focused only on modern deployment scenarios

What Actually Changes in Real Life?
The biggest shift is not technical—it’s operational.
With v1, IT teams spend time preparing devices before users even see them.
With v2, the focus shifts to policies, identity, and cloud configuration—devices become just endpoints.
This means:
Less effort in pre-deployment
More reliance on cloud identity
Better user experience
Faster rollout cycles

Where Most Organizations Get It Wrong
A common mistake is assuming “new equals better.”
That’s not always true.
If your environment still depends on:
Hybrid identity
Complex provisioning workflows
Large app deployments during setup
Then moving to v2 too early can actually create limitations instead of solving problems.

How to Decide the Right Approach
Think in terms of your environment maturity:
👉 Stay with Classic Autopilot (v1) if:
You rely on hybrid infrastructure
You need deep provisioning control
You support multiple device types and scenarios
👉 Move to Autopilot Device Preparation (v2) if:
You are cloud-first (Entra ID)
You want faster and simpler deployments
You are standardizing on Windows 11
You prefer reliability over customization

The Bigger Picture
This shift is not just about Autopilot—it reflects where endpoint management is heading.
Less dependency on infrastructure.
More reliance on identity.
Simplified provisioning.
And a stronger focus on user experience.

Final Thought
Autopilot v1 gave us flexibility when environments were complex.
Autopilot v2 is built for a world were simplicity and speed matter more.
The real question is not which one is better—
it’s which one aligns with your organization’s future.