> For the complete documentation index, see [llms.txt](https://docs.intuneassistant.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intuneassistant.cloud/intune-assistant/reports.md).

# Reports

## What Is This Section?

The **Scripts** section of Intune Assistant gives you visibility into the PowerShell scripts deployed to your Windows devices through Microsoft Intune. It focuses specifically on **Remediation Scripts** (also known as health scripts or proactive remediations) — the most powerful scripting feature in Intune because they can both detect and fix device state automatically.

Beyond simply listing the scripts that exist in your tenant, Intune Assistant goes further: when a detection script outputs structured JSON data, the platform automatically parses that output and presents it as a full, filterable, exportable report per script. This turns your remediation scripts into a lightweight, Intune-native device inventory and data collection system.

## What Is Available

| Page                                                                             | What It Does                                                                                                                 |
| -------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [Health Scripts Report](broken://pages/c9781f25df440f7f7082778feee74a62d9cb8c05) | Browse all remediation scripts in your tenant and open a per-script device run-state report with dynamic JSON output columns |

## Why This Matters

Microsoft Intune's remediation scripts are commonly used for fixing configuration issues. But they can do much more than that. Because the detection script can return any data via `Write-Output`, IT administrators use them to collect:

* Installed browser extensions across all devices
* Registry key values
* Installed software inventory
* Hardware specifications
* Custom compliance data not available via built-in compliance policies

Until now, accessing that data meant building your own pipeline: Log Analytics, Azure Monitor, custom scripts to extract the data from Graph. Intune Assistant removes that friction — the JSON output is surfaced directly in the interface, no extra infrastructure required.

For more information on how to use remediation scripts for data collection, see [this learning page](https://learn.microsoft.com/en-us/intune/device-management/tools/deploy-remediations).\
For more information on how to create remediation scripts, see [this learning page](https://learn.microsoft.com/en-us/intune/device-management/tools/ref-remediation-scripts#powershell-scripts-for-remediations).

Also there are a lot of great resources where remediation scripts are shared by the community. Here are a few:

* [Jannik Reinhard](https://github.com/JayRHa/EndpointAnalyticsRemediationScripts)
* [Sander Rozemuller](https://github.com/srozemuller/IntuneAutomation/tree/main/RemediationScripts)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intuneassistant.cloud/intune-assistant/reports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.