> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-insights/advanced-insights-and-microsoft-updates-inventory.md).
# Advanced Insights and Microsoft Updates Inventory
Advanced Insights Update scanning (this is not relevant for Patch Insights)
*Applies to: Patch My PC Advanced Insights*
If you use **Intune** to manage your windows updates (**Windows Update for Business**) then none of that compliance data is visible from ConfigMgr. This requires you to have to read compliance data from BOTH ConfigMgr and Intune.
## Solution
* You get **complete** visibility of **all** update compliance from Advanced Insights
The Microsoft Updates Dashboard
***
## How does it work?
We supplement your ConfigMgr compliance data with **additional data** from Microsoft Update.
Our Inventory Extensions WMI Provider runs on clients and scans against Microsoft Update to find update compliance data. This data is then pulled into ConfigMgr via Hardware Inventory for reporting.
***
## Requirements
1. You must complete the implementation steps in the [Configuration Guide](/patch-my-pc-insights/advanced-insights-inventory-extensions.md)
2. Clients must be configured to use **Windows Update for Business**
---
# 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.patchmypc.com/patch-my-pc-insights/advanced-insights-and-microsoft-updates-inventory.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.
