| | 6 min read |

Traditional device deployment can be a hassle. IT teams are overworked, employees face delays during onboarding, and devices often miss key configurations. These inefficiencies hurt productivity, frustrate users, and leave IT teams scrambling to fix issues after delivery. 

That’s where Windows Autopilot White Glove Pre-Provisioning comes in. This innovative solution transforms the deployment process by allowing IT teams to pre-configure devices with all necessary apps, settings, and policies before they even reach the user. The result? A seamless onboarding experience, reduced IT workload, and more time for what really matters. 

Let’s dive into what it is, its advantages, use case scenarios, and how the process works. 

What is Windows Autopilot White Glove Pre-Provisioning? 

Windows Autopilot White Glove pre-provisioning is a deployment feature designed for IT teams or partners to pre-configure Windows devices before they are handed over to end users. With this process, all necessary applications, settings, and policies are applied to a device, ensuring it's ready to use right out of the box. 

This method eliminates the need for end users to undergo lengthy setup procedures, creating a hassle-free onboarding experience. 

What are the Advantages of Windows Autopilot White Glove Pre-Provisioning?

  • 1

    Time Savings for End Users 
    End users receive devices that are fully configured and ready to use, reducing downtime and boosting productivity from day one.

  • 2

    Streamlined IT Operations 
    IT teams or deployment partners handle the setup process in advance, reducing user frustration and decreasing the burden on support teams.

  • 3

    Enhanced User Experience 
    The pre-provisioning process ensures a polished and professional first impression, as users only need to connect to Wi-Fi and sign in with their credentials.

  • 4

    Scalability 
    Ideal for large-scale deployments, this method simplifies configuring hundreds or thousands of devices with consistent settings and policies.

  • 5

    Reduced Errors 
    By pre-configuring devices, there’s less risk of users misconfiguring settings or encountering issues during setup.

What Use Case Scenarios Require Windows Autopilot White Glove Pre-Provisioning?

  • 1

    Large-Scale Device Rollouts 
    Businesses deploying devices to multiple users, such as in corporate offices or educational institutions, benefit from the efficiency of White Glove provisioning.

  • 2

    Remote and Hybrid Workforces 
    With employees spread across various locations, this process ensures remote workers receive devices that are pre-configured and secure.

  • 3

    Seasonal or Temporary Staff 
    For roles with high turnover, such as retail or customer service, pre-provisioned devices save valuable time during onboarding.

  • 4

    Partner-Assisted Deployments 
    Managed service providers (MSPs) can pre-configure devices on behalf of their clients, ensuring a seamless experience for end users.

Steps of Windows Autopilot White Glove Pre-Provisioning 

Here's a step-by-step guide to the White Glove pre-provisioning process: 

  • 1

    Device Registration
    Register the device in Microsoft Intune and assign it to a user and device group. This ensures that the device receives the appropriate settings and applications.

  • 2

    Profile Assignment 
    Create an Autopilot deployment profile and enable the pre-provisioning option. Assign the profile to the registered device.

  • 3

    Pre-Provisioning Start 
    Boot the device and initiate pre-provisioning by pressing the Windows key five times on the setup screen. This signals the device to begin the configuration process.

  • 4

    Configuration 
    The device connects to Microsoft’s cloud services to download and install assigned applications, policies, and settings.

  • 5

    Reseal 
    Once configuration is complete, the device is resealed. This resets the device for end-user delivery while preserving the applied settings.

  • 6

    User Setup 
    The end user completes the out-of-box experience by connecting to Wi-Fi and signing in with their credentials. No additional setup is needed, as the device is already configured. 

Technical Workflow of Windows Autopilot White Glove Pre-Provisioning

Windows Autopilot White Glove pre-provisioning is designed to streamline the deployment of new devices by handling most of the setup before they reach end users. This ensures that devices arrive fully configured and ready for immediate use.  

Below is the step-by-step technical workflow of the White Glove process: 

Step 1: Initiating the Pre-Provisioning Process 

The technician powers on the device and triggers the White Glove workflow by pressing the Windows key five times at the initial setup screen. This action activates the pre-provisioning process, signaling the device to begin configuration. 

 

Step 2: Verifying Device Enrollment 

Once the pre-provisioning mode starts, the system confirms that the device is registered in the correct Azure tenant. This verification ensures that the device is associated with the appropriate business and will receive the correct deployment settings. After successful validation, the provisioning process begins. 

 

Step 3: Applying Applications and Policies 

During the provisioning phase, Microsoft Intune deploys the assigned applications, policies, and configuration profiles. This process occurs during the Enrollment Status Page (ESP), which monitors and ensures that the device is fully prepared before proceeding. By the end of this stage, the device is updated with all necessary software, settings, and security policies. 

 

Step 4: Completing and Sealing the Device 

Once all applications are installed and configurations are applied, the device displays a green success screen. This screen signifies that the pre-provisioning process is complete. The device is then resealed and powered down, ready for shipment. Resealing protects the applied configurations and ensures that the device is in a clean state for the end user. 

 

Step 5: Final User Setup 

After delivery, the user powers on the device and completes the standard Autopilot out-of-box experience (OOBE). During this step, the user connects to Wi-Fi and logs in with their credentials. Since the device has already been pre-configured, all assigned applications and policies are ready to use, significantly reducing setup time and complexity. 

Prerequisites & Requirements for Windows Autopilot White Glove (Pre-Provisioning)

White Glove pre-provisioning works best when the technical foundation is solid. Before attempting to pre-provision devices, make sure the following requirements are in place.

Device Requirements:

Prerequisites & Requirements for Windows Autopilot White Glove (Pre-Provisioning)

White Glove pre-provisioning works best when the technical foundation is solid. Before attempting to pre-provision devices, make sure the following requirements are in place.

Device Requirements:

  • Windows version: Windows 10/11 Pro, Enterprise, or Education (current supported builds)

  • Hardware security: TPM 2.0 with device attestation support

  • Network access: Devices must be able to reach Microsoft Autopilot, Intune, and Entra endpoints during provisioning

  • OEM registration: Devices must be registered in Autopilot (hardware hash uploaded by OEM, partner, or admin)

Devices that fail TPM attestation or aren’t properly registered in Autopilot cannot complete pre-provisioning.

Microsoft Intune & Entra Configuration

Pre-provisioning relies on several backend components working together:

  • Autopilot deployment profile assigned to the device (user-driven profile that supports pre-provisioning)

  • Enrollment Status Page (ESP) configured to track device-targeted apps and policies

  • Device groups correctly populated for app and policy targeting

  • Microsoft Entra join model planned in advance:

    • Entra ID join (cloud-native)

    • Hybrid Entra ID join (requires line-of-sight to domain controllers at the right stage)

Misaligned profiles, missing group assignments, or ESP misconfiguration are among the most common causes of White Glove delays.

Application & Policy Considerations

Not all workloads behave the same during pre-provisioning.

Best candidates for the device phase:

  • Security baselines and compliance policies

  • Device configuration profiles

  • Core line-of-business apps required for all users

  • Microsoft 365 Apps (device context)

Be cautious with:

  • Large Win32 apps with complex dependencies

  • Apps requiring user context

  • Scripts that rely on user sign-in or interactive prompts

Designing what installs during device phase vs user phase is critical for a smooth experience.

Application & Policy Considerations

Not all workloads behave the same during pre-provisioning.

Best candidates for the device phase:

  • Security baselines and compliance policies

  • Device configuration profiles

  • Core line-of-business apps required for all users

  • Microsoft 365 Apps (device context)

Be cautious with:

  • Large Win32 apps with complex dependencies

  • Apps requiring user context

  • Scripts that rely on user sign-in or interactive prompts

Designing what installs during device phase vs user phase is critical for a smooth experience.

Conclusion 

Windows Autopilot White Glove pre-provisioning transforms the way businesses deploy devices. By pre-configuring settings and applications in advance, it delivers a streamlined experience for IT teams and end users alike. Whether you’re managing a global workforce or preparing for a large-scale rollout, this approach ensures a smooth, professional, and efficient deployment process. 

Discover How much value are your business is getting from your M365 licenses compared to your peers.

Discover:

  • Overlapping security tools can you retire

  • Business processes can you automate

  • IT functions can you modernize

Apply for the Capability & Capacity Assessment 

Andrew Reade

ANDREW READE

Andrew is our Digital Marketing Manager and oversees web-based marketing strategies and content creation for the organization. As a marketing veteran, Andrew has worked with organizations of all sizes in a diverse group of industries, from Risk Management to Transportation. Joining the organization in 2021, Andrew is based in Mobile Mentor’s Nashville, TN office.