> 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/devices/devices-per-person.md).

# Devices per Person

Analyze the number of devices per user in Microsoft Entra ID.

The **Devices per Person** report displays details for devices in your Microsoft Entra ID environment. The report focuses on the number of devices per R**egistered Owne**r (user) to help you assess device distribution in your organization.

The report provides a summary of device counts per user and detailed device information.

<figure><img src="https://content.gitbook.com/content/ygloFyyKhIYtV62dMZJc/blobs/oVN3N9mnhsN5kHHAFjsr/image.png" alt=""><figcaption></figcaption></figure>

### User Device Distribution

The **Focus Table** shows the number of devices per user (where user is a registered owner of the device). Use the filter options in the **Slicer Menu** to look for different types of devices, activity and management states.&#x20;

Use the **Breakdown Table** and **Breakdown Filter** to choose your view of the distribution in your organization based on the user properties available.

Try the predefined **Filter Templates** to get inspiration on what to look for.

<figure><img src="https://content.gitbook.com/content/ygloFyyKhIYtV62dMZJc/blobs/J0MlvEWJDoMSlgJezpS3/image.png" alt=""><figcaption></figcaption></figure>


---

# 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/devices/devices-per-person.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.