How to Manually Register Devices with Windows Autopilot

Introduction

Learning how to manually register devices with Windows Autopilot is an essential skill for IT administrators who need precise control over their device deployment process. While many organizations rely on OEM pre-registration or partner-assisted enrollment, manual registration gives your team the flexibility to onboard any compatible Windows device on your own terms. This is especially valuable for small and mid-sized businesses that purchase hardware from multiple sources or inherit devices from mergers and acquisitions. In this guide, we walk through the entire process from start to finish so your team can deploy devices confidently and efficiently.

What Windows Autopilot Actually Does for Your Business

Windows Autopilot is a cloud-based device provisioning service built into Microsoft's ecosystem that transforms the way organizations set up and configure new Windows devices. Instead of requiring IT staff to manually image each machine, install software, and configure settings one by one, Autopilot automates the entire out-of-box experience. When a registered device is powered on for the first time, it connects to Azure Active Directory and Microsoft Intune, applies your organization's policies, installs required applications, and delivers a fully configured, work-ready machine — all without anyone in IT needing to touch the device physically. This dramatically reduces deployment time and human error while giving end users a seamless onboarding experience.

For small and mid-sized businesses, the appeal of Autopilot goes beyond convenience. It standardizes the way every device enters your environment, ensuring that security baselines, compliance policies, and software configurations are applied consistently across your entire fleet. Whether you are setting up five laptops for a new office or deploying fifty devices for a growing team, the process remains repeatable and auditable. The service integrates tightly with Microsoft Intune for mobile device management and Azure Active Directory for identity, meaning your devices are enrolled, secured, and managed from the moment a user signs in for the first time.

How the Registration and Deployment Process Works

At the heart of Windows Autopilot is the hardware hash — a unique cryptographic fingerprint generated from specific hardware identifiers on each device, including the serial number, manufacturer details, and network adapter information. When you register a device, you are essentially uploading this hardware hash to the Autopilot service through Microsoft Intune or the Microsoft Partner Center. Once the hash is on file, Autopilot recognizes the device the next time it connects to the internet during the out-of-box setup experience and applies the appropriate deployment profile. This is what allows a device to configure itself automatically without any local IT intervention.

The deployment profile you assign to a device or group of devices controls exactly what the setup experience looks like. You can configure whether the device joins Azure AD or a hybrid domain, whether users see a simplified or fully customized setup screen, whether local administrator accounts are created, and which applications and policies are pushed immediately upon enrollment. Profiles can be scoped to specific devices or applied dynamically based on group membership, giving administrators fine-grained control over how different user populations receive their machines. Understanding this flow is important before you begin the manual registration process, because the hardware hash upload is only the first step — assigning the right profile ensures the device behaves exactly as intended when it reaches the end user.

Step-by-Step Guide

1. Verify Prerequisites and Licensing: Before you begin, confirm that your organization has the required Microsoft 365 or Intune licenses, specifically Microsoft 365 Business Premium, Microsoft 365 E3, or E5, or an Intune standalone subscription with Azure AD Premium P1 or higher. You will also need Global Administrator or Intune Administrator rights in your Microsoft tenant to upload device information and manage Autopilot profiles.
2. Collect the Hardware Hash from the Device: Power on the target device and allow it to reach the initial setup screen, then press Shift+F10 to open a Command Prompt before completing any setup steps. Run the following PowerShell command to generate and save the hardware hash as a CSV file: Install-Script -Name Get-WindowsAutoPilotInfo followed by Get-WindowsAutoPilotInfo -OutputFile C:\autopilot.csv, which will create a file containing the device's serial number, Windows product ID, and hardware hash.
3. Transfer the CSV File Securely: Copy the generated CSV file from the device to a location accessible on your administrative workstation, using a USB drive, secure file share, or cloud storage as appropriate for your environment. Ensure the file is handled securely since it contains unique device identifiers that should not be shared outside your IT team.
4. Sign In to the Microsoft Intune Admin Center: Open a browser and navigate to endpoint.microsoft.com, then sign in with your administrator credentials to access the Microsoft Intune admin center. From the left navigation panel, go to Devices, then select Windows, and then Windows Enrollment, followed by Devices under the Windows Autopilot Deployment Program section.
5. Import the Device Using the CSV File: Click the Import button within the Windows Autopilot Devices section and browse to select the CSV file you collected from the device. The import process may take several minutes to complete, and you will need to refresh the device list manually to confirm the device has appeared with a status of Assigned or Ready.
6. Create or Assign a Deployment Profile: Navigate to Deployment Profiles within the Windows Enrollment section and either select an existing profile or create a new one by defining the deployment mode, join type, user-facing settings, and any skip steps appropriate for your organization. Once the profile is configured, assign it to the device or to a dynamic Azure AD group that includes the newly registered device, ensuring the profile will be applied when the device goes through setup.
7. Validate the Registration and Ship or Hand Off the Device: Return to the Windows Autopilot Devices list and confirm the device shows the correct profile assignment and a status indicating it is ready for deployment. You can now factory reset the device or leave it at the out-of-box experience screen, then ship it directly to the end user or hand it off on-site, knowing that when the user powers it on and connects to the internet, Autopilot will take over and complete the configuration automatically.

Comparing Windows Autopilot Registration Methods

Best Practices

• Use Dynamic Azure AD Groups: Create dynamic device groups based on naming conventions or purchase order attributes so newly imported devices are automatically assigned the correct deployment profile without manual group management.
• Standardize Your CSV Naming Convention: Name each exported hardware hash CSV file with the device serial number and date so you can easily track which devices have been registered and troubleshoot any import errors later.
• Test Profiles Before Mass Deployment: Always validate a new or updated Autopilot deployment profile on one or two test devices before rolling it out to a large batch to catch configuration errors before they affect end users.
• Document Your Deployment Profiles: Keep a written record of each profile's settings, scope, and intended user group so that any member of your IT team can understand and manage the Autopilot configuration without relying on institutional knowledge.
• Monitor Enrollment Status Reports: Use the Enrollment Status Page and Intune's device enrollment reports to track deployment success rates and quickly identify devices that failed to complete the Autopilot process so issues can be resolved before they impact productivity.

Frequently Asked Questions

Can I Register a Device That Has Already Been Set Up and Is in Active Use?

Yes, you can manually register devices with Windows Autopilot even if they are already configured and in use, as long as you can collect the hardware hash from the device. You would run the Get-WindowsAutoPilotInfo script on the live machine to generate the CSV file, upload it to Intune, and assign a deployment profile. However, the Autopilot profile will only take effect the next time the device goes through the out-of-box experience, which typically means a factory reset or clean reinstall of Windows is required to trigger the automated setup flow.

How Long Does It Take for a Registered Device to Appear in Intune?

After you import the CSV file into the Microsoft Intune admin center, it typically takes anywhere from a few minutes to about 15 minutes for the device to appear in the Windows Autopilot Devices list. You may need to manually refresh the page since the admin center does not always update automatically. If the device does not appear after 30 minutes, double-check that the CSV file was formatted correctly and that no duplicate hardware hashes exist in your tenant from a previous registration attempt.

What Happens If I Assign the Wrong Deployment Profile to a Device?

If a device receives the wrong deployment profile, you can update the profile assignment in Intune before the device completes its out-of-box setup, and the corrected profile will be applied instead. If the device has already gone through setup with an incorrect profile, you will need to reset the device and allow it to run through the Autopilot process again with the correct profile assigned. This is why testing profiles on a small number of devices before broad deployment is strongly recommended, as catching profile errors early saves significant remediation time.

Is There a Limit to How Many Devices I Can Import at Once?

Microsoft Intune supports importing a single CSV file containing up to 500 device entries at one time through the admin center interface. If you need to register more than 500 devices in a single batch, you can split the entries across multiple CSV files and import them sequentially. For very large deployments, Microsoft also supports bulk registration through the Microsoft Graph API, which allows programmatic uploads without the 500-device per file limitation and is better suited for enterprise-scale rollouts.

Do I Need Internet Access on the Device During the Hash Collection Process?

No, you do not need an active internet connection on the device to run the Get-WindowsAutoPilotInfo script and collect the hardware hash, since the script reads hardware identifiers locally from the device itself. However, if you use the -Online parameter with the script, it will attempt to upload the hash directly to your Intune tenant, which does require internet connectivity and appropriate credentials. For most manual registration workflows, collecting the hash offline and uploading the CSV separately from an admin workstation is the more practical and controlled approach.

If your team is spending too much time on device provisioning or struggling to scale your deployment process, Always Beyond can help you design and implement a streamlined Windows Autopilot workflow tailored to your organization's size and needs. Our managed IT services team handles everything from profile configuration to ongoing device management so your staff can focus on running the business — contact Always Beyond today.