> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory/active-directory-sync-v8-50-priority-r.md).

# Active Directory Sync v8.50 requirements

Prepare Active Directory, REST API, and operator prerequisites for Active Directory Sync v8.50.

Have these in place before installing AD Sync on v8.50 or later:

* An **Authorising Operator Group** (SSO login plus Local Administrator on the AD Sync UI machine).
* A valid **REST API client connection** (test with the REST Diagnostic tool).
* A **REST operator** with create/edit/delete cardholder privilege.
* A privileged **Domain User** account.
* An active AD Sync **connection to the Domain Controller**.

![The REST Diagnostic tool running ping / TCP / SSL connection checks against the Command Centre REST endpoint](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-76dd4525824c70e2bdbc25d7d2467a89a8efab05%2FSECHUB-AD-SYNC-14-rest-diagnostic-tool.png?alt=media)

***

🔗 **Related**

* [Sync v8.50 - Installation Supporting Document](/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory/active-directory-sync-v8-50-installati.md). The install order.
* [Sync User Accounts Requirement](/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory/active-directory-sync-user-accounts-re.md). Domain and service account permissions.


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory/active-directory-sync-v8-50-priority-r.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.