Windows Autopilot
Windows Autopilot Devices
The Windows Autopilot Devices report provides an overview of all devices registered in Windows Autopilot. It helps you identify devices that are ready for deployment, already in use, not yet contacted by Autopilot, or possibly no longer active in Intune.
This report is especially useful for organizations that want to understand which devices are still “on the shelf”, which devices have been used during adoption or onboarding, and which devices may need cleanup or follow-up.
When to use this report
Use this report to:
Review all devices registered in Windows Autopilot
Identify devices that have not contacted Autopilot
Find devices that are registered but never used
Check whether devices are present in Intune
Investigate devices that may have been deleted from Intune
Understand which devices have been used and by whom
Support hardware inventory and adoption tracking
Follow up on devices that may still be in stock, assigned to users, or waiting for deployment
What the report shows
The report shows Windows Autopilot device records together with enrichment from Intune and Entra ID where available.
Key concepts
In Intune
The In Intune slicer shows whether the Autopilot device currently has a matching device record in Intune.
This is useful for identifying devices that are still registered in Autopilot but may no longer exist in Intune.
Typical use cases:
Finding devices that were deleted from Intune
Finding devices that have not yet been enrolled
Finding devices that may still be in storage
Comparing Autopilot registration against actual Intune inventory
Assigned user
The Assigned user field shows the user assigned to the Autopilot device, if available.
A missing assigned user does not always mean the device is unused. Some Autopilot deployment scenarios do not require a pre-assigned user.
Last used by
The Last used by field shows the last known user associated with the device.
This is especially useful when a device has been used at least once. Even if the device is no longer active in Intune, the report can still help identify who last used it.
This can help answer questions such as:
Was this device ever used?
Who last used the device?
Is this likely a shelf device or an active/adopted device?
Should the device be followed up with a user, department, or location?
Group tag and purchase order
The Group tag and Purchase order fields can help identify where devices belong operationally.
These fields are useful when devices are grouped by:
Department
Location
Deployment wave
Hardware batch
Lifecycle phase
Purchase or procurement process
Findings
The report groups devices into findings to make it easier to focus on devices that require attention.
Healthy
The device appears to be in a normal state based on the available Autopilot, Intune, and usage information.
Recommended action: No action required.
Autopilot not contacted
The device is registered in Windows Autopilot, but it has not contacted Autopilot.
This may indicate that the device has not yet been turned on, has not started deployment, or has not reached the Autopilot service.
Typical reasons:
The device is still in stock
The device has not been delivered to the user
The device has not been connected to the internet during setup
The device was imported into Autopilot but never deployed
Recommended action: Verify whether the device has been delivered, is still in stock, or is expected to be deployed.
Registered but never used
The device is registered in Autopilot, but there is no evidence that it has been used.
This can be useful for identifying devices that may still be available for assignment, deployment, or cleanup.
Recommended action: Verify whether the device is still expected to be used. If the device is no longer needed, consider whether it should remain registered in Autopilot.
No last used user found
The report did not find a last used user for the device.
This does not always mean the device is unused. It means that no last-used user information was available in the collected data.
Recommended action: Review the assigned user, Intune status, and device state before taking action.
How to use the report
1. Start with the Focus Table
The Focus Table gives a quick overview of the most important findings.
Use this table to understand the overall state of your Autopilot device inventory.
Examples:
How many devices are healthy?
How many devices have not contacted Autopilot?
How many devices are registered but never used?
2. Use the Breakdown Table
The Breakdown Table lets you group the devices by different properties.
Available breakdown options include:
Production status
Enrollment state
Assigned user
Last used by
Manufacturer
Model
Group tag
Purchase order
Tenant name
This is useful when investigating patterns, such as whether unused devices belong to a specific model, purchase order, or deployment group.
3. Filter by In Intune
Use the In Intune slicer to separate devices that currently exist in Intune from devices that do not.
This is one of the most important filters in the report.
For example:
Select No to find Autopilot devices that are not currently found in Intune.
Select Yes to focus on devices that are both registered in Autopilot and present in Intune.
4. Search for a specific user
Use the Last Used By (UPN) search box to find devices previously used by a specific user.
This is useful when:
A user has returned a device
A device was replaced
You need to identify which hardware was used by a specific person
You are investigating stale or orphaned devices
5. Use the Details Table
The Details Table shows device-level information.
Use this table to investigate individual devices and decide what action to take.
Important columns include:
Serial number: The hardware identifier
Device name: The Intune or device name, if available
Finding: The detected state or issue
Explanation: Why the device received the finding
Recommended action: Suggested next step
Assigned user: User assigned to the Autopilot device
Last used by: Last known user of the device
Last used at: Last known usage timestamp
In Intune: Whether the device exists in Intune
Has Entra device link: Whether the device has a linked Entra device
Common scenarios
Find devices that may still be in stock
To identify devices that may still be on the shelf:
Filter In Intune to No
Review findings such as Autopilot not contacted or Registered but never used
Group by Purchase order, Group tag, Manufacturer, or Model
Review the Details Table for serial numbers and recommended actions
Find devices that were registered but never used
To find devices that have been imported into Autopilot but never used:
Select the finding Registered but never used
Review whether the device has an assigned user
Check whether the device exists in Intune
Use serial number, purchase order, or group tag to follow up operationally
Find devices used during adoption
To review devices that have been used at least once:
Use the Last used by breakdown
Search for a specific user if needed
Review the last used information in the Details Table
Compare assigned user and last used by to identify ownership or usage mismatch
Find possible cleanup candidates
To find devices that may need cleanup:
Filter In Intune to No
Review devices with no assigned user and no last used user
Group by purchase order, model, or group tag
Validate whether the devices should still be registered in Autopilot before removing anything
Important notes
A device can be registered in Windows Autopilot even if it does not currently exist in Intune.
A missing last used user does not always mean the device has never been used. It means the report did not find last-used information in the available data.
Before removing devices from Autopilot, verify that the device is no longer needed and that removal aligns with your internal device lifecycle process.
Recommended workflow
Review the total number of devices
Check the Focus Table for findings
Filter on In Intune = No to identify devices missing from Intune
Review Autopilot not contacted and Registered but never used
Use Group tag, Purchase order, Manufacturer, and Model to identify patterns
Use Last used by to determine whether the device has been used before
Export or follow up on devices that require action
Last updated
Was this helpful?