> 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/interactive-hardware-hash.md).
# Interactive hardware hash upload
Interactive upload stages an assistant that asks a technician to authenticate during Windows OOBE, after Windows deployment completes.
## Prerequisites
* An authorized technician account.
* Microsoft Graph delegated permissions required by the workflow.
* Network access to Microsoft authentication and Autopilot services.
* A process for selecting the correct group tag during the OOBE assistant.
## Configure interactive upload
1. Open **Windows Autopilot > Interactive hardware hash upload**.
2. Enable the interactive workflow.
3. Return to **Start** and confirm Autopilot readiness.
Enable the interactive registration assistant for use during Windows OOBE.
## During deployment
Foundry Deploy provisions the interactive registration assistant during Windows deployment. After Windows starts in OOBE, the assistant presents device-code sign-in, group-tag selection, hardware hash capture, and upload. The technician completes authentication in a browser, returns to the deployment device, and waits for registration to finish.
Do not share device codes or authentication screenshots. If registration fails, collect the stage and error details described in [Autopilot troubleshooting](/troubleshooting/autopilot.md).
---
# 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/interactive-hardware-hash.md?ask=&goal=
```
`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.