> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/user-guides/power-bi/groups.md).

# Groups

Entra ID groups control a large part of what people have access to in Microsoft 365: applications, Teams, SharePoint sites, licenses, devices and even privileged roles. Over time most tenants build up hundreds of groups. Many of them lose their owners, end up empty, collect guests nobody remembers inviting, or are never given a description that explains what they are for.

At the same time, groups are often the best way to see who uses what. If access to an application or service is given through a group, the members of that group are the people who should carry its cost.

The Groups reports help you with both: keeping your groups under control, and using them to allocate cost.

#### What problems the Groups reports solve

* **Unclear ownership** - Groups with no active owner, or only one, are hard to govern. Nobody approves access, and nobody notices when the group is no longer needed.
* **Hidden access** - Guests, inactive guests, disabled users and external owners can keep access through groups long after they should have lost it.
* **Privileged access through groups** - Role-assignable groups give Entra ID roles to their members, and their owners decide who those members are.
* **Group sprawl** - Empty groups and groups without a description make it hard to know what is in use and what can be removed.
* **Cost without an owner** - Applications, services and shared resources are often paid for centrally, with no easy way to see which departments or users actually use them.

#### Reports under Groups

**Drilldown**

An overview of all Entra ID groups in your tenant. The report groups common governance findings into use cases, such as **No active owners**, **Guest as owner**, **Empty group** and **Missing description**, and lets you drill down to the individual groups, members and owners.

Use it for group governance, access reviews and cleanup.

[Read more about Drilldown](/user-guides/power-bi/groups/groups-drilldown.md)

**Cost Allocation**

Shows how the cost items you have set up are allocated to users. Each cost item has a price per user, a fixed monthly price or both, and is connected to one or more groups. The report calculates what each user costs per month and lets you break the cost down by department, company, country and other user properties.

Use it for internal chargeback, budgeting and to find cost allocated to users who no longer need access.

[Read more about Cost Allocation](/user-guides/power-bi/groups/groups-cost-allocation.md)

**HINT:** The Cost Allocation report is empty until you have created cost items in **Settings → Configuration → Group Cost Allocation**. See [Group Cost Allocation. ](/user-guides/settings/configuration/group-cost-allocation.md)

#### Data freshness

Groups, members and owners are collected automatically every night, at around midnight. Changes made in Entra ID during the day will show in the reports after the next nightly collection. If you need updated data right away, click **Collect Group Members** in **Settings → Configuration → Group Cost Allocation**.


---

# 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://docs.bsure.io/user-guides/power-bi/groups.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.