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

# Microsoft Entra ID environment

Collect Microsoft Entra ID application credentials and permissions for Entra ID Sync.

The Azure-side values are collected by the customer's IS team.

* **Licence:** Gallagher recommends **at least Entra ID P1**.
* **Tenant ID** — Microsoft Entra ID **> Overview**.
* **Client ID (Application ID)** — **App registrations** > the app's Application (Client) ID.
* **Client Secret (value)** — **Certificates & secrets** > New client secret. **The value is visible only immediately after creation.** If lost, create a new one.

## Entra ID application permissions

The permission **Type must be `Application`**.

| Purpose                                                  | Permissions                                                                      |
| -------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Sync **from** Entra ID → CC                              | `Group.Read.All`, `User.Read.All`                                                |
| Sync **from** Entra ID → CC, incl. **custom attributes** | `CustomSecAttributeAssignment.Read.All`, `CustomSecAttributeDefinition.Read.All` |
| Sync **to** Entra ID (CC → Entra)                        | `User.ReadWrite.All`                                                             |

![Azure App registration API permissions showing the configured Microsoft Graph application permissions granted for the integration](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d0b6e15e4034286db11cced98b77ab9d9998dfd6%2FSECHUB-ENTRA-07-azure-api-permissions.png?alt=media)

***

🔗 **Related**

* [Configuration](/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/entra-id/entra-id-configuration.md). Where the Azure values are entered.
* [Limitations and Licensing](/knowledge-hub/products/cc-software/configure/identity-solutions-cardholders-and-ope/entra-id/entra-id-limitations-and-licensing.md). Licence entries and constraints.


---

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