> 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/entra-agent-id/step-by-step-deployment-guide.md).

# Step-by-step deployment guide

### Microsoft Entra Agent ID

The Entra Agent ID connector imports **AI agent identities** from your Microsoft Entra tenant into Elimity Insights, together with who owns and sponsors each one.

#### 1. Which data is imported

* **Agent Identity Blueprint Principals** — the tenant-local registration of a blueprint.
* **Agent Identities** — each actual running instance of a blueprint (e.g. one per region or team), along with their owners, sponsors and agent user.

{% code overflow="wrap" %}

```mermaid
graph TD;BlueprintPrincipal[Agent Identity Blueprint Principal]; AgentIdentity[Agent Identity]; AgentIdentity --> BlueprintPrincipal;
```

{% endcode %}

Attributes imported per entity type:

**Agent Identity Blueprint Principal** — AppId

**Agent Identity** — Enabled, AgentIdentityBlueprintId, CreatedAt, AgentUserId, AgentUserDisplayName, SponsorDisplayNames, SponsorIds, OwnerDisplayNames, OwnerIds

#### 2. Creating a dedicated app registration in Entra ID

As usual we recommend creating a dedicated account for this connector.

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

Note down both the **client identifier** and the **tenant identifier**.

#### 3. Generating credentials for the new app registration

The 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** (Entra shows it only once).

#### 4. Granting read permissions to the Graph API

Click **API permissions** and add these **Microsoft Graph → Application permissions**, then grant admin consent:

* `AgentIdentity.Read.All` — read agent identities
* `AgentIdentityBlueprintPrincipal.Read.All` — read agent identity blueprint principals
* `AgentIdUser.ReadWrite.IdentityParentedBy` — read agent users' parent identities
* `User.ReadBasic.All` — read agent users
* `Group.Read.All` — read groups to get sponsor group names

#### 5. Creating a source in Elimity Insights

1. Go to **Sources** → **Add Source** → search **Custom** → **Set Up**.
2. Click **Set Up** again and name the source (e.g. `Microsoft Entra Agent ID`).
3. Select **Upload export file**, click **Continue**, and upload `entra-agent-id-data-model.json`.
4. Open the **Config** tab, click **Edit**, set **Enable automatic imports via custom gateway** to `true`, and fill in the **Gateway URL**: <https://entra-agent-id-gateway-1027270379075.europe-west1.run.app>
5. Click **Add configuration value** and add the three entries according to the configuration table below.
6. Click **Save and run**. Monitor the **Logs** tab — this connector logs its progress; the **Imports** tab shows the per-run summary.

{% file src="/files/OJoMqYXT4HUaK7NOl69m" %}

| Configuration option | Key (type exactly this) | Type     | Value                            |
| -------------------- | ----------------------- | -------- | -------------------------------- |
| Tenant ID            | `Tenant ID`             | Text     | Tenant identifier from step 2.   |
| Application ID       | `Application ID`        | Text     | Client identifier from step 2.   |
| Application Secret   | `Application Secret`    | Password | Client secret value from step 3. |

***

<br>


---

# 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/entra-agent-id/step-by-step-deployment-guide.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.