Skip to content

Intune and Windows Autopilot troubleshooting: 5 checks for reliable provisioning

PDQ Team
PDQ team|November 17, 2026
General2 2026
General2 2026

TL;DR: The key to troubleshooting Intune and Autopilot is to put the setup in order: do your prerequisites, then registration, profile assignment, enrollment, app installation, and lastly the device checks. Before you alter any policies, get the logs and error information from an affected machine. Fix the root of the problem and run a test on another setup to be sure the device is fit for the user.

A laptop may have completed its Windows setup yet be without the company’s security policies or apps. In other cases, it will not make it to the sign-in screen as it should. These are all put down as “Autopilot problems” even if the reasons differ. While Autopilot does the initial work, Intune is responsible for management and enrollment. See where things stand at each step before resetting a device or making changes to its policies.

1. Check Autopilot prerequisites and network access

Begin with the Windows edition and version that are supported, the licenses on hand, and the kind of Microsoft Entra join in use. Make certain the user has the right Intune license and is covered by the MDM user scope for automatic enrollment. Should you be doing Windows Autopilot device preparation, note that it is for Microsoft Entra join, not hybrid.

Then put Microsoft’s required Autopilot services to the test. From the network the employee will be using, go over the DNS, proxy, and firewall settings. Just because a connection is good in the IT office is no guarantee it will hold up on a home or branch network.

2. Check device registration and enrollment eligibility

With classic Windows Autopilot, find the device in the proper tenant and confirm that the serial number in its record matches the device. Registration being complete is not the same thing as having a deployment profile assigned, so confirm the profile assignment too. Also check if the account can join Microsoft Entra ID and whether Intune is putting restrictions on the device.

Windows Autopilot device preparation is done differently and generally forgoes the old hardware-hash registration. If device association is in play, look into that too since a classic Autopilot record can live alongside the new flow. When a user signs in but the device won’t enroll in Intune, the issue is likely with enrollment and not the app assignments. 

3. Verify the profile or policy assignment

In the Intune admin center, navigate to Devices > Windows.

Microsoft Intune admin center with arrows pointing to Devices in the sidebar and the Windows platform tile.

Under Device onboarding, select Enrollment, then go to Windows Autopilot > Devices to see which devices are registered for classic Windows Autopilot.

Microsoft Intune Windows enrollment page with arrows pointing to Enrollment, the Windows Autopilot section, and its Devices link.

Check the Profile Status and confirm that it shows as Assigned. Open the device record and verify that the intended profile is assigned and Date assigned is populated. The right profile needs to be in place ahead of setup. If not, have a look at the deployment mode, exclusions, and device group membership.

If the company setup doesn’t show up, start with the profile. For device preparation, verify the policy’s user-group assignment or its device-targeted assignment when device association is used. It presents a Setting up for work or school screen in lieu of the ESP.

4. Identify the app or policy blocking Autopilot setup

The ESP in classic Autopilot tracks progress as Windows gets on with enrollment and the like. An app installation that brings setup to a halt requires some digging into the app’s dependencies, context, and detection rule. A timeout only means the limit ran out, not which part went wrong. If one laptop has no trouble with an app and another does, compare them before overhauling the provisioning policy.

Microsoft has troubleshooting steps for the ESP. On a user’s device, create C:\Temp and from an elevated prompt type mdmdiagnosticstool.exe -area Autopilot -cab C:\Temp\Autopilot.cab. For Win32 issues, the Intune Management Extension logs in C:\ProgramData\Microsoft\IntuneManagementExtension\Logs will tell you more.

Device preparation has a deployment report to identify the stage or script that failed. Put that right first.

5. Validate apps and policies after Autopilot setup

Take a test device with the same Windows version and policies as the ones giving trouble. Check the Microsoft Entra join and Intune enrollment. Have a user log in and open the applications they would normally use. Don’t rely on the setup screen; verify in Intune that the compliance and security policies are there. A desktop is not enough if the necessary apps are absent.

Make note of the model, the Windows version, the profile, and any errors or time taken. If the failure looks to be hardware, set it against a working device of the same make. Test one setting at a time to isolate the variable.


After enrollment, PDQ can be used with Intune for inventory, patching, and software deployment. We cover how to simplify Microsoft endpoint management with PDQ. Our guides on WSUS, Intune, and Configuration Manager, and on picking an endpoint platform, will show where those tools belong. Provisioning and Microsoft policy are still left to Autopilot and Intune.

ConnectIcon CTA

Manage Windows & macOS devices from anywhere

With PDQ Connect, get real-time visibility into remote and local devices, deploy software, remediate vulnerabilities, automate routine maintenance, and remotely troubleshoot endpoints from one easy-to-use platform.

PDQ Team
PDQ team

The PDQ content team writes practical guides for sysadmins on patching, software deployment, and endpoint management. Built for sysadmins, by sysadmins, our content is shaped by real-world IT experience and the tools we create — like PDQ Connect, a cloud-based platform for remotely managing Windows and macOS devices. We focus on simple, secure, and pretty damn quick solutions you can use in real environments, whether you're managing 15 devices or 15,000. The goal is always faster fixes, fewer surprises, and healthier fleets.

Related articles