> 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/windows-management.md).
# Windows Management
Assess management status of Windows devices in Microsoft Entra ID to prioritize enrollment.
The Windows Management report displays details for Windows devices in your Microsoft Entra ID environment. The report focuses on management status to help you identify unmanaged devices.
The report provides a summary of Windows device management states and detailed device information.
## Focus Table - Windows Management State
View Windows device management states.
Use the **Focus Table** to get a quick view on the different **Windows management states** of your devices:
* Unmanaged disabled devices
* Managed disabled devices
* Unmanaged enabled devices
* Managed enabled devices
* Unmanaged devices not in use
* Managed devices not in use
* Unmanaged devices in use
* Managed devices in use
Or try the predefined **Filter Templates** to look for more specific use cases.
Looking for devices that maybe should have been managed? Try the **Show Active Entra ID Registered Devices with Owners**.
---
# 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/windows-management.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.
