> 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/interactive.md).
# Interactive Domain Join
**Interactive Domain Join** keeps the join account off the deployment media: the technician types the account and its password in Foundry Deploy at each deployment.
Interactive mode lists domains and OUs only. No account or password is stored.
## Before you start
* Make sure technicians have a join account, written as `DOMAIN\user` or `user@domain`, and its password.
* The device must reach a domain controller when the join runs, after the restart. The Windows edition must not be a Home edition, and each device needs its own computer name.
This mode does not need Password protection.
## Configure
1. Open **Domain Join > Interactive** and select **Enable**. If another Domain Join or Windows Autopilot mode is active, confirm with **Change mode**.
2. Optional: under **Domains**, select **Add**, enter the **Domain name**, such as `corp.contoso.com`, and select **Add domain**. Once a domain is listed, technicians can join only a listed domain; with none, they type the domain name.
3. Optional: select a domain, then under **Organizational units** select **Add**, enter a **Display name** and the **Distinguished name** of the OU, such as `OU=Workstations,DC=corp,DC=contoso,DC=com`, and select **Add OU**. **Import from domain** reads the OUs from the directory instead.
4. Open **Start** and create or update the media.
## What the technician sees
At each deployment, the [Domain Join step](/foundry-deploy/domain-join.md) of Foundry Deploy asks for the domain, the join account, its password and, when the domain lists several, the OU. For a domain without listed OUs, the technician may type an OU or leave it empty. The technician can also choose **Do not join a domain**; nothing is then asked.
When the technician selects **Next**, Foundry Deploy checks the account and its password with the domain. See [Account check](/foundry-deploy/domain-join.md#account-check).
## Check the result
* On **Start**, **Interactive** under **Domain Join** reads **Configured**.
* On a deployed device, follow the hand-over checks of the [Domain Join step](/foundry-deploy/domain-join.md).
## Limits
No join account or password is written to interactive media, including the ones saved on the Zero-touch Domain Join page.
## Related
* [Domain Join](/foundry-osd/domain-join.md): the two modes and their requirements
* [Domains and OUs](/foundry-osd/domain-join/domains-and-ous.md)
* [Domain Join troubleshooting](/troubleshooting/domain-join.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 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/interactive.md?ask=&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.
