# Set up department insights

Department insights let you slice [BI 360](/guides/bi-360.md) by team, function, or business unit — for example Marketing, Finance, Sales, R\&D, or Clinical Operations — so you can see adoption, license use, and content ownership at a department level instead of just tenant-wide.

To enable them, Datalogz needs **department data** for your users. Department data comes from your identity provider, specifically the department field on each user account in Entra ID (Azure AD), which Datalogz joins to the users, owners, and licenses it has ingested from your BI tools.

Once Entra ID department data is connected, the following [insights](/guides/bi-360.md) become available in BI 360:

* **Department User Breakdown** — adoption and activity per team
* **License Utilization by Department** — allocated vs. active licenses per team
* **Department Dashboard Ownership** — content ownership and inactivity per team
* **Department BI Health Snapshot** — top active and at-risk departments on the Executive Summary

## How to set it up

To enable department insights:

1. Confirm Entra ID / Azure AD is configured for your tenant.
2. Go to **Settings** > **User Directory**.
3. Set up the Entra ID connector.
4. Department dimensions become available in BI 360 within one ingestion cycle.

If Entra ID is not connected, the rest of BI 360 still works — the department breakdowns are simply hidden from the Organizational and Reporting tabs and from the Executive Summary.


---

# Agent Instructions: 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:

```
GET https://docs.datalogz.io/guides/bi-360/set-up-department-insights.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.