Windows Autopilot Deployment: A Step-by-Step Guide (2025)

Windows Autopilot is revolutionizing the way organizations deploy and manage Windows devices. By leveraging cloud technologies, it eliminates the traditional hassles of imaging and manual configuration, simplifying the deployment process. This comprehensive guide will help you understand, configure, and deploy Windows Autopilot effectively.

What is Windows Autopilot?

Windows Autopilot, a collection of cloud-based technologies by Microsoft, streamlines the deployment and configuration of new devices. It helps IT professionals prepare devices for productive use with minimal effort. Autopilot can also reset, repurpose, and recover devices while maintaining compliance with organizational standards.

Advantages of Windows Autopilot

• Simplified Deployment: Uses the OEM-installed Windows OS, eliminating the need for custom images.
• Automation: Applies organizational policies and installs essential apps.
• Scalability: Supports remote deployment, saving time and resources.
• Integration: Seamlessly works with Azure Active Directory (AAD) and Microsoft Intune.
• Enhanced User Experience: Provides a streamlined, consistent setup process for end users.

Key Prerequisites for Windows Autopilot Deployment

1. Supported Windows Versions: Windows 10/11 Pro, Enterprise, or Education editions.
2. Licensing: Requires subscriptions such as Microsoft 365 Business Premium, Microsoft Intune, or Enterprise Mobility + Security (EMS). (Checkout Complete List)
3. Azure Active Directory Premium: Essential for device enrollment and management (Premium P1 or P2)
4. Internet Connectivity: Devices must connect to the internet during the deployment process.

---

Windows Autopilot Deployment Process Overview

1. Register Devices: Capture the device hardware ID and upload it to the Microsoft Endpoint Manager admin center.
2. Create Deployment Profiles: Define policies, settings, and apps for devices.
3. Assign Profiles: Link devices to deployment profiles for automated configuration.
4. Monitor Deployment: Track the process and ensure all configurations are applied successfully.

Step-by-Step Windows Autopilot Setup

• • Open PowerShell and run:

md c:HWID 
Set-Location c:HWID 
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted -Force 
Install-Script -Name Get-WindowsAutopilotInfo -Force 
Get-WindowsAutopilotInfo.ps1 -OutputFile AutopilotHWID.csv

• Select Yes when the NuGet package installation option appears.

• • Goto C Drive and you should see the HWID Folder. 
  • Save the generated AutopilotHWID.csv file for registration.

2. Alternative option to have Upload the Hardware Hash online to an Intune portal

Any device can have its hardware hash directly uploaded to an Microsoft Intune Portal, but it’s particularly helpful for devices that are going through OOBE and Windows Setup. To submit a device’s hardware hash directly:

For a Device Having OOBE and Windows Setup:

• At the sign-in prompt after OOBE starts, open a command prompt window with the keystroke Shift+F10.

• Type the following commands at the PowerShell prompt windows:

powershell.exe

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned
Install-Script -Name Get-WindowsAutopilotInfo -Force
Get-WindowsAutopilotInfo -Online

• Accept the installation of NuGet from the PSGallery when asked.
• When the Microsoft Entra ID sign-on prompt appears, log in using an account that is at least an Intune Administrator.

• Approve the required app registration permissions if prompted. The hardware hash uploads automatically.

3. Verify the Hardware Hash Upload

• Login to the Microsoft Intune or Endpoint Portal.
• Navigate to Devices on the left-hand pane.
• Under Devices | Overview, select Windows under By platform.
• Go to Windows | Device onboarding > Enrollment > Windows Autopilot > Devices.
• Select Sync in the toolbar.
• Wait for the sync to finish. The sync might take several minutes.
• The device will show up in the device list on the Windows Autopilot devices tab in Intune once the sync is finished. Make sure the device has a Windows Autopilot profile assigned to it.

Restart the device if it’s going through Windows Setup and OOBE. It will pick up the Windows Autopilot profile, and OOBE will run through the provisioning process.

4. Register Devices in Intune

4.1 Existing Devices 

• • Log in to the Microsoft Endpoint Manager admin center or Intune Portal.

• Navigate to Devices > Device Onboarding Enrollment > Windows Tab > Windows Autopilot option > Devices.

• • Import the AutopilotHWID.csv file.

4.2 New Devices (OOBE) Purchased from Vendor

If you have already registered or plan to register for the Windows Autopilot program, you can allow your hardware vendor to directly upload the devices’ hardware IDs to Intune. To enable this, your organization must first enroll in the Windows Autopilot Customer Program. Once registered, the vendor will be able to upload the hardware IDs directly into the Windows Autopilot service.

An Intune admin can then view these devices under
Endpoint Manager > Devices > Enrollment > Windows Autopilot > Devices.

After the devices appear in this section, you should create an Azure AD dynamic group to ensure the Autopilot deployment profile and other configurations are automatically applied.

5. Create Deployment Profiles

• In the Intune Portal Go to Devices >
• Device Onboarding Enrollment > Windows Tab>Windows Autopilot option > Deployment profiles.

• • Click Create profile and configure:
    • • Deployment Mode: Self Deploying Mode
    • • Join to Azure AD: Azure AD Joined
    • • User Account Type: Standard
    • • Hide Privacy Settings: Yes

6. Assign Deployment Profiles

• • Link profiles to device groups for seamless deployment.

7. Test the Deployment

• • Reset the device to Out-of-Box Experience (OOBE).

• • Turn on the device, connect to the internet, and follow the OOBE steps.

• • Log in using Azure AD credentials to trigger the deployment.

---

Troubleshooting Tips

• • Device Not Appearing in Intune: Ensure the hardware ID file is correctly formatted and uploaded.

• • Deployment Stuck at a Step: Check network connectivity and Intune configurations.

• • Licensing Issues: Verify that the required Azure AD and Intune licenses are active.

---

FAQs

• • Can Windows Autopilot be used with existing devices?
    Yes, devices can be reset to OOBE and enrolled in Autopilot for repurposing.

• • How does Autopilot ensure security?
    Autopilot enforces organizational compliance through Azure AD and Intune policies during deployment.

• • Is internet access mandatory for Autopilot deployment?
    Yes, devices must connect to the internet to communicate with Azure AD and Intune services.

• • Can Autopilot configure third-party applications?
    Yes, applications can be added to deployment profiles for automatic installation during setup.

• • What happens if a device is lost or stolen?
    Devices enrolled in Autopilot can be remotely locked, wiped, or reset to ensure data security.

• • What is the purpose of using Windows Autopilot?
    Windows Autopilot simplifies the device deployment process, automates configuration, and ensures compliance, reducing IT workload and enhancing user productivity.

• • How does Windows Autopilot work?
    Windows Autopilot works by leveraging cloud-based technologies to configure devices during the Out-of-Box Experience (OOBE). It applies policies, installs apps, and joins devices to Azure Active Directory, making them business-ready.

• • Which device or devices can be deployed by using Windows Autopilot?
    Windows Autopilot supports the deployment of Windows 10/11 Pro, Enterprise, and Education devices. It can be used with physical hardware and virtual machines.

---

Conclusion

Windows Autopilot simplifies the deployment process, enabling organizations to deliver a seamless, efficient, and secure experience for end users. With its robust capabilities and integration with cloud services, it’s a game-changer for modern device management.

---

Related Links:

• Complete the Intune Implementation with the Templates or Copy the Configuration Policies from Other Tenant
• Endpoint Privilege Management (EPM) enables IT administrators to allow or block specific applications from being installed by end users without requiring elevated (admin) permissions.
• Step-by-Step Guide for Enroll and Migrate windows Devices to Microsoft Intune