> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/endpoint/autopilot/list-devices.md).

# Autopilot Devices

Autopilot Devices lists the Windows devices registered to the tenant's Autopilot service, along with the hardware details and group tag each was registered with. From here you can assign a device to a user, rename it, change its group tag, or deregister it.

## Action Buttons

{% content-ref url="/pages/S0ZDh03z03LAtt5VnOZj" %}
[Add Autopilot Device](/user-documentation/endpoint/autopilot/add-device.md)
{% endcontent-ref %}

<details>

<summary>Sync Devices</summary>

Asks the Autopilot deployment service to sync, pulling in device registrations made outside CIPP, such as those uploaded by an OEM, reseller or distributor. New devices will not appear in the list until a sync has run and completed.

{% hint style="info" %}
Microsoft only accepts a sync request every ten minutes. Requesting one sooner returns an error rather than queuing.
{% endhint %}

</details>

## Table Details

The properties returned are for the Graph resource type `windowsAutopilotDeviceIdentity`. For more information on the properties please see the [Graph documentation](https://learn.microsoft.com/en-us/graph/api/resources/intune-enrollment-windowsautopilotdeviceidentity?view=graph-rest-1.0#properties).

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Assign device</td><td>Assigns the device to a user, so that user is pre-populated at sign-in during Autopilot enrolment. Select the user from the list.</td><td>true</td></tr><tr><td>Rename Device</td><td>Sets the computer name the device will take when it enrols. Existing enrolled devices are not renamed retrospectively.</td><td>true</td></tr><tr><td>Edit Group Tag</td><td>Sets the device's group tag, which is what dynamic device groups usually key off to decide which deployment profile a device receives. Clearing the field removes the tag.</td><td>true</td></tr><tr><td>Delete Device</td><td>Deregisters the device from Autopilot. The hardware can be re-registered later, but until it is, it will no longer receive an Autopilot deployment profile.</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

{% hint style="warning" %}
Display names entered for **Rename Device** must be 15 characters or fewer, may contain only letters, numbers and hyphens, cannot contain spaces, and cannot be made up entirely of numbers. Group tags are limited to 128 characters. Both are validated in the browser and again by CIPP, so an invalid value is rejected rather than silently applied.
{% endhint %}

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cipp.app/user-documentation/endpoint/autopilot/list-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.