> 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/zero-touch-hardware-hash.md).

# Zero-touch hardware hash upload

Zero-touch upload registers a device without requiring a technician to sign in during deployment.

## Prerequisites

* Microsoft Entra tenant information.
* An application registration approved for the deployment workflow.
* Required Microsoft Graph application permissions and administrator consent.
* A plan to create a Foundry-managed certificate after connecting the tenant, or an approved matching PFX and private key for boot media.
* A credential-rotation process that covers certificate expiration.

## Configure zero-touch upload

1. Open **Windows Autopilot > Zero-touch hardware hash upload**.
2. Select **Connect tenant** and complete the Microsoft sign-in flow.
3. Allow Foundry OSD to create or adopt the tenant application registration used for upload.
4. Review application registration, Microsoft Graph permissions, administrator consent, and service-principal readiness.
5. Create a Foundry-managed certificate or select the approved matching PFX and provide its password for boot-media provisioning.
6. Configure the group tag when required by the organization.
7. Return to **Start** and confirm Autopilot readiness.

<figure><img src="/files/jii62nxD03CCpKCoIH1z" alt="Foundry OSD zero-touch hardware hash upload prerequisite validation"><figcaption><p>Confirm tenant, application, permission, and certificate readiness.</p></figcaption></figure>

{% hint style="danger" %}
Protect the certificate private key and generated media. Revoke or rotate the credential if its confidentiality is uncertain.
{% endhint %}

## During deployment

Foundry Deploy captures the hardware hash and uses the configured application identity to upload it.

{% hint style="warning" %}
Windows deployment can succeed even when Microsoft Graph upload or registration polling fails. Review the Autopilot result and verify the device record in the tenant before handoff.
{% 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/zero-touch-hardware-hash.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.
