> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/modules/secure/intune/remediation-scripts.md).

# Remediation Scripts

{% hint style="info" %}
This page is a branch of [Intune](/modules/secure/intune.md), covering the **Remediation Scripts** policy category specifically. See that page first for how Templates, Baselines, and Policies relate to each other in general — everything below assumes that model, and see [Scripts](/modules/secure/intune/scripts.md) for Intune's plain one-way script mechanism, which is a distinct category in Augmentt.
{% endhint %}

Remediation Scripts (Intune calls these "proactive remediations") pair a **detection script** with a **remediation script**: Intune runs the detection script on a schedule, and only if it reports a problem does it run the remediation script to fix it — with device-level results (issue found/fixed, or not applicable) reported back per run.

{% hint style="warning" %}
Augmentt ships **no built-in default templates** for Remediation Scripts. Every remediation-script template is one your organization has authored or imported.
{% endhint %}

## What this category controls

Remediation Scripts map to Graph `#microsoft.graph.deviceHealthScript` (`/deviceManagement/deviceHealthScripts`), Windows-only. Because detection and remediation script content can be large, Augmentt lifts `detectionScriptContent` and `remediationScriptContent` to top-level binary fields internally rather than flattening them inline (they can exceed the 32KB flattened-field limit used elsewhere in Augmentt's data pipeline) — this is an internal storage detail, not something you configure, but it explains why remediation scripts can hold substantially larger script bodies than some other Intune content types.

## Configuration surface

* **Detection script** and **detection script content** — the script Intune runs first; its exit code/output determines whether the device has the issue.
* **Remediation script** and **remediation script content** — the script Intune runs only when detection reports a problem.
* **Script package name**, **author**, **publisher**, **version** — descriptive metadata for the remediation package.
* **Run as account** — system or logged-on user.
* **Run this script using the logged-on credentials.**
* **Run script in 64-bit PowerShell** (vs. 32-bit).
* **Enforce script signature check.**
* **Schedule / assignment** — target all users or all devices (removing an "all" assignment is required before adding specific groups), or specific groups; a run frequency (repeats every N hours, up to a 24-hour maximum, or every N days, up to a 365-day maximum), a specific run time, and a UTC toggle for that scheduled time. A one-time run can also be scheduled for a specific future date/time (validated to not be in the past).
* **License prerequisite** — remediations require Windows license verification to be enabled on the tenant before they can be used; Augmentt surfaces this as a blocking requirement rather than a configurable setting.

### Reported status (read-only, per device/run)

Detection status and remediation status per device roll up into: issue fixed, with issues, without issues, failed, not applicable, not deployed, pending devices, total remediated, and whether the run recurred on schedule.

## Resolves posture check(s)

{% hint style="warning" %}
No default templates ship for this category, and Augmentt's `SECURE_CHECK_TYPES` / `COMPLIANCE_AUDIT.*` posture-check engine has no dedicated Remediation Scripts check. What a remediation "fixes" is entirely defined by the script content you or your source tenant wrote, so — like plain Scripts — it can't be generically mapped to a framework control the way a fixed-schema policy can.
{% endhint %}

## Related pages

* [Intune](/modules/secure/intune.md)
* [Scripts](/modules/secure/intune/scripts.md)


---

# 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://helpdesk.augmentt.com/modules/secure/intune/remediation-scripts.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.