Споделяне чрез

Compare Windows Autopilot device preparation and Windows Autopilot

Windows Autopilot device preparation vs. Windows Autopilot

Feature Windows Autopilot
device preparation
Windows Autopilot
  • Support for Government Community Cloud High (GCCH) and Department of Defense (DoD) environments.
  • Faster, more consistent provisioning experience.
  • Near real-time monitoring and troubleshooting info.
Supported modes
Join types supported
  • Microsoft Entra join.
  • Microsoft Entra join.
  • Microsoft Entra hybrid join.
Device registration required? No. Yes.
What do admins need to configure?
  • Windows Autopilot device preparation policy.
  • Device security group with Intune Provisioning Client as owner.
  • Windows Autopilot deployment profile.
  • Enrollment Status Page (ESP).
What configurations can be delivered during provisioning?
  • Device-based only during the out-of-box experience (OOBE).
  • Up to 10 essential applications (line-of-business (LOB), Win32, Microsoft Store, Microsoft 365).
  • Up to 10 essential PowerShell scripts.
  • Device-based during device ESP.
  • User-based during user ESP.
  • Any number of applications.
Reporting & troubleshooting Windows Autopilot device preparation deployment report:
  • Shows all Windows Autopilot device preparation deployments.
  • More data available.
  • Near real-time.
Windows Autopilot deployment report:
  • Only shows Windows Autopilot registered devices.
  • Not real-time.
Supports LOB and Win32 applications in same deployment? Yes. No.
Supported versions of Windows
  • Windows 11, version 23H2 with KB5035942 or later.
  • Windows 11, version 22H2 with KB5035942 or later.

Which Windows Autopilot solution to use

Which version of Windows Autopilot to use is dependent on many factors and variables, with each environment having different needs. Windows Autopilot device preparation in its initial offering isn't as feature rich as Windows Autopilot, but it does have some advantages and features not available in Windows Autopilot.

In general, the following are some of the major factors when considering between Windows Autopilot device preparation or Windows Autopilot:

Requirement Windows Autopilot
device preparation
Government Community Cloud High (GCCH) and
Department of Defense (DoD) environments
User-driven scenario
Pre-provisioned scenario
Self-deploying scenario
Existing devices scenario
Autopilot reset support
Microsoft Entra join
Microsoft Entra hybrid join
Windows Autopilot Reset
Windows 11
Windows 10
Deploy Win32 and LOB applications
in the same deployment
Simpler deployment configuration and experience
Extensive customization of deployment
and OOBE experience
No requirement to pre-stage devices
Install more than 10 applications during OOBE
Run more than 10 PowerShell scripts during OOBE
Near real-time monitoring
Block user from accessing desktop until
user based configurations are applied
HoloLens support
Teams Meeting Room support
Device Firmware Configuration Interface
(DFCI) Management support
Autopilot into co-management

Using Windows Autopilot device preparation and Windows Autopilot concurrently

Windows Autopilot device preparation and Windows autopilot can be used concurrently and side by side within an organization. However, any one device in an environment can only run one of the two solutions. Windows Autopilot profiles take precedence over Windows Autopilot device preparation policies. If a Windows Autopilot registered device needs to go through a Windows Autopilot device preparation deployment, it must first be removed as a Windows Autopilot device. For more information, see Deregister a device.