> For the complete documentation index, see [llms.txt](https://docs.foundryosd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foundryosd.com/foundry-osd/autopilot.md).

# Windows Autopilot

Foundry supports three Autopilot workflows. Choose the method that matches the organization’s provisioning and security model.

## Choose a method

### JSON profile

Use [JSON profile](/foundry-osd/autopilot/json-profile.md) to stage an existing Autopilot profile on the deployed device. This method does not upload the device hardware hash.

### Zero-touch hardware hash upload

Use [zero-touch hardware hash upload](/foundry-osd/autopilot/zero-touch-hardware-hash.md) for unattended registration with a Microsoft Entra application registration and certificate.

### Interactive hardware hash upload

Use [interactive hardware hash upload](/foundry-osd/autopilot/interactive-hardware-hash.md) when a technician should authenticate with a device code during deployment.

| Requirement              | JSON profile | Zero-touch upload | Interactive upload |
| ------------------------ | ------------ | ----------------- | ------------------ |
| Local profile file       | Required     | No                | No                 |
| Application registration | No           | Required          | No                 |
| Certificate              | No           | Required          | No                 |
| Technician sign-in       | No           | No                | Required           |
| Hardware hash upload     | No           | Automatic         | Interactive        |

{% hint style="warning" %}
Autopilot configuration may include tenant information, certificates, and credentials. Follow the organization’s credential and media-handling policy.
{% endhint %}


---

# 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.foundryosd.com/foundry-osd/autopilot.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.