> 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.

[Domain Join](/foundry-osd/domain-join.md) is the alternative to Windows Autopilot. Enabling it replaces the active Autopilot mode, and enabling an Autopilot mode replaces Domain Join; Foundry asks for confirmation. Create the media again after switching.

## 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.foundryosd.com/foundry-osd/autopilot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.