> 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/entra-id.md).

# Entra ID

Configure Microsoft Entra ID cardholder synchronization with Command Centre.

Entra ID Sync replicates cardholders between **Microsoft Entra ID** (Microsoft's cloud directory) and Command Centre, the cloud-directory counterpart to [Active Directory Sync](/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory/active-directory-sync-features-and-fun.md). It is **two-way**: Entra user create/modify/delete flows to CC cardholders (details and access permissions), and CC card details can flow back to Entra. It uses the **REST API** to write to Command Centre and **Single Sign-On** to authorize the config UI.

> ⚠️ **This is for Microsoft Entra ID, not on-prem Active Directory.** For AD, use the separate [Active Directory Sync](/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/active-directory.md) feature. And **do not run AD Sync and Entra ID Sync against the same Command Centre server at the same time.**

## Versions

| Attribute                | v1.0                                                     | v2.0+                                            |
| ------------------------ | -------------------------------------------------------- | ------------------------------------------------ |
| Full release             | August 2025                                              | November 2025                                    |
| Command Centre           | v9.20 / v9.30                                            | **v9.40+** (Entra ID SSO added to CC in vEL9.40) |
| UI authentication        | **Active Directory SSO** (Windows account → CC operator) | **Entra ID SSO** (AD not used for any purpose)   |
| `ADSingleSignOn` licence | **Required**                                             | Not required (uses Entra SSO instead)            |
| Recommendation           | Use if on CC v9.20/9.30                                  | Preferred on CC v9.40+                           |

Both versions replicate cardholders the same way. The difference is **how the person launching the Entra ID Sync UI is authenticated**.


---

# 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/entra-id.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.