> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/pam/knowledge-base/how-to-articles/configure-pam-domain-account-provider-through-devolutions-gateway.md).

# Configure PAM domain account provider through Devolutions Gateway

Configure a Devolutions Server PAM domain account provider through Devolutions Gateway to manage multiple Active Directory domains.

This option makes it possible to support Active Directory domain accounts in Devolutions Server PAM for multiple domains on different networks, via Devolutions Gateway. It gives you the ability to use Devolutions Server PAM to manage several Active Directory domains at once and isolate Devolutions Server from the rest of Active Directory to force use of Devolutions Gateway. This feature is especially useful for MSP's needing to access multiple subnets from different clients.

### Configuration

1. Connect to the Devolutions Server web interface.
2. Go to ***Administration*** – ***Privileged access*** – ***Providers***.
3. Click ***Edit*** on an already configured ***Domain provider***.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Read more about <a href="/pam/pam-with-devolutions-server/providers/managed-providers/domain-user-provider.md">domain providers</a>.</p></div>
4. Enable ***Use Devolutions Gateway*** under the ***Domain*** section.
5. Click on the ellipsis button to choose the Devolutions Gateway and then click on ***Select***.
6. Click on ***Edit*** to choose the ***Domain controller*** (which is now mandatory because of the ***Use Devolutions Gateway*** option).
7. Click on ***Save*** in the ***Preferred domain controller*** window.
8. To save these settings and close the window click on ***Save***.


---

# 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.devolutions.net/pam/knowledge-base/how-to-articles/configure-pam-domain-account-provider-through-devolutions-gateway.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.