> 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/azure-ad.md).

# Entra ID

The Entra ID connector for Elimity Insights fetches principals, roles and subscriptions from Entra ID 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 app registration in Entra ID

As usual we recommend creating a dedicated account for this connector. Follow the steps below to set up a new app registration in Entra ID:

1. In Azure, open the overview of your tenant's app registrations by typing 'app registrations' in the global search bar and clicking the 'App registrations' service.
2. Click the 'New registration' button.
3. Choose a name for this registration (e.g. `elimity-insights`).
4. Leave the default for 'Supported account types' and 'Redirect URI' and click 'Register'.

Note down both the client identifier and the tenant identifier for this new app registration.

## 2. Generating credentials for the new app registration

The Entra ID connector authenticates as the app registration using a client secret. Click "Certificates & secrets" in the menu on the left and add a new client secret. Immediately note down the value of your new secret.

## 3. Granting read permissions to the Graph API

Having created a new app registration in Entra ID, we now need to grant it read access to some parts of the Microsoft Graph API:

1. Click 'API permissions' in the menu on the left and only add the 'Microsoft Graph' > 'Application permissions' > 'Directory.Read.All'. If you have an Entra ID Premium P1/P2 license and would like to import sign-in activity for users, then grant 'Microsoft Graph' > 'Application permissions' > 'AuditLog.Read.All' as well.
2. Grant admin consent for these permission assignments.

## 4. Creating a source in Elimity Insights

In Elimity Insights you can now create a new Entra ID 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>Tenant ID</td><td>Tenant identifier you noted down in step 1.</td></tr><tr><td>Application ID</td><td>Client identifier you noted down in step 1.</td></tr><tr><td>Application Secret</td><td>Client secret you noted down in step 2.</td></tr><tr><td>Import sign-in activity</td><td>Enable this if you want to import sign-in activity for users; requires an Entra ID Premium P1/P2 license and the additional 'AuditLog.Read.All' permission as explained in step 3.</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/azure-ad.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.