> 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/intune-drilldown.md).
# Intune Drilldown
If You use Intune as deployment system, this report will give you information on all devices.
This drilldown report will show all devices in you Intune environment with status and who's using the different devices.
**Slicer menu:**
* Devices : shows number of devices based on your filtering
* Device Activity: When it was last synced with intune
* Device State: If device activity is more than 90 days ago = Inactive, else Active
* OS : Operating system from Intune
* In Entra: If device in Intune has a corresponding object in Entra ID. If you find some of these devies you should investigate.
* Duplicate: It is possible to get same serialnumber registered in Intune as two individual registrations. If you find some, please investgigate and delete the duplicate not in use one.
* Compliance: Compliance state from Intune
**In device details table we've added some new columns:**
* Last user: Latest sign in to the device and user that did it
* Users count: How many users have signed in to the device
* Logged on users: Displays all users that have signed into the device
* Storage health: to help you find devices with full disk etc.
---
# 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/intune-drilldown.md?ask=&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.
