> 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/domain-join.md).

# Domain Join

**Domain Join** joins the target device to an Active Directory domain during deployment, before the first sign-in. Foundry performs the join in installed Windows, after the restart, with a join account: an Active Directory account allowed to add computers to the domain.

Two modes differ in who supplies the join account.

|                                                                    | [Zero-touch](/foundry-osd/domain-join/zero-touch.md)        | [Interactive](/foundry-osd/domain-join/interactive.md)    |
| ------------------------------------------------------------------ | ----------------------------------------------------------- | --------------------------------------------------------- |
| Join account                                                       | Stored on the media, encrypted with the Deployment password | Typed by the technician at each deployment                |
| [Password protection](/foundry-osd/general.md#password-protection) | Required                                                    | Not required                                              |
| Domains listed in Foundry OSD                                      | At least one                                                | Optional; with none, the technician types the domain name |
| Organizational unit (OU) typed by the technician                   | Never                                                       | Allowed for a domain that lists no OU                     |

In both modes, the technician can choose **Do not join a domain** at a deployment, so the same media also deploys computers that stay outside the domain. The join remains the preselected choice, and no setting removes the other one.

Start with the page of the mode you use: it carries the steps to enable it. Both modes share the same lists of domains and OUs, described in detail in [Domains and OUs](/foundry-osd/domain-join/domains-and-ous.md). The technician's side is the [Domain Join step](/foundry-deploy/domain-join.md) of Foundry Deploy; failures are in [Domain Join troubleshooting](/troubleshooting/domain-join.md).

Domain Join and [Windows Autopilot](/foundry-osd/autopilot.md) exclude each other: enabling one mode asks you to confirm before it replaces the active one.

## Before you start

These requirements apply to both modes.

* **Network at join time.** The join runs in installed Windows, not in Windows PE. The device must then reach the domain's DNS servers and a domain controller. The Internet check in Foundry Connect does not test this.
* **Join account.** Ask your Active Directory administrator for an account that may add computers to the domain, reuse an existing computer account when a device is redeployed under the same name, and move computer accounts to the OUs you list. Foundry does not check these permissions.
* **Computer name.** Each device needs its own name, because the name identifies its computer account. See [Machine naming](/foundry-osd/customization/machine-naming.md).
* **Windows edition.** Windows Home editions cannot join a domain: Foundry skips the join and the installation continues. The editions are listed in [Supported versions](/reference/supported-versions.md#windows-11-editions).
* **Custom answer file.** It must meet extra rules when Domain Join is active. See [Unattend](/foundry-osd/customization/unattend.md#what-a-custom-answer-file-overrides).

Test the join on one device first: a wrong account or an unreachable domain only shows after Windows is installed.


---

# 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/domain-join.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.