> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/reference-manual/v3.44.2/built-in-connectors/active-directory.md).

# Active directory

The Active Directory connector for Elimity Insights fetches users, groups and computers from Active Directory so you can keep in control of your environment. Follow the instructions below to set up the connector for your environment.

## 1. Creating a dedicated read-only account in Active Directory

As usual we recommend setting up a dedicated read-only account for this connector. Make sure that authentication to Active Directory using simple bind or NTLM works as expected. Note down the username, password and (optionally) NTLM domain of the dedicated read-only account.

## 2. Creating a source in Elimity Insights

In Elimity Insights you can now create a new Active Directory source providing the following configuration options:

<table data-full-width="true"><thead><tr><th>Configuration option</th><th>Description</th></tr></thead><tbody><tr><td>LDAP URL</td><td>URL indicating where the connector should contact your domain controller (e.g. <code>ldap://my-host:389</code> or <code>ldaps://my-secure-host:636</code>).</td></tr><tr><td>Username</td><td>Username to use for simple bind or NTLM authentication.</td></tr><tr><td>Password</td><td>Password to use for simple bind or NTLM authentication.</td></tr><tr><td>Domain</td><td>Domain for NTLM authentication; leave blank to use simple bind.</td></tr><tr><td>Search requests</td><td>JSON array describing which search requests to perform.</td></tr></tbody></table>


---

# 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.elimity.com/reference-manual/v3.44.2/built-in-connectors/active-directory.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.