> 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/scripts.md).

# Scripts

{% hint style="info" %}
This page is a branch of [Intune](/modules/secure/intune.md), covering the **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 [Remediation Scripts](/modules/secure/intune/remediation-scripts.md) for Intune's separate detect-then-fix "proactive remediation" mechanism, which is a distinct category in Augmentt.
{% endhint %}

Scripts are one-way, run-once (or scheduled) device scripts pushed to enrolled devices — PowerShell on Windows, shell scripts on macOS, and script-based custom settings on Linux — with no built-in detection/remediation pairing (that's what [Remediation Scripts](/modules/secure/intune/remediation-scripts.md) are for).

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

## What this category controls

Scripts map to three different Graph sources depending on platform, matching how Microsoft itself splits script execution across OSes:

| Platform | Graph source                                                                                                                                                         |
| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Windows  | `/deviceManagement/deviceManagementScripts`                                                                                                                          |
| macOS    | `/deviceManagement/deviceShellScripts`                                                                                                                               |
| Linux    | `/deviceManagement/configurationPolicies` (Linux scripts are delivered as a Settings Catalog custom-compliance-style configuration, not a dedicated script endpoint) |

## Configuration surface

### Windows (PowerShell) and macOS (shell)

* **Script type** — PowerShell script (Windows) or shell script (macOS).
* **Script content** — the script body itself.
* **Execution context / run-as account** — run using the logged-on user's credentials, or in the system context.
* **Enforce script signature check** — require the script be signed.
* **Run in 64-bit vs. 32-bit PowerShell host** (Windows only).
* **Hide script notifications on devices** — suppress the execution toast shown to the end user.
* **Script frequency** — run once, or on a repeating schedule (every N days/hours/minutes).
* **Max retry count** — how many times to retry if the script fails.
* **Assignment** — all users, all devices, or specific groups, same as other Intune categories.

### Linux

* **Execution frequency** and **execution retries** — same intent as Windows/macOS scheduling, exposed through the Settings Catalog configuration model rather than a dedicated script endpoint.
* Linux distribution/version applicability, where the target configuration profile specifies it.

## 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 Scripts check. A one-way script's effect on posture depends entirely on what the script itself does, so it can't be generically mapped the way a fixed-schema Device Configuration or Compliance setting can.
{% endhint %}

## Related pages

* [Intune](/modules/secure/intune.md)
* [Remediation Scripts](/modules/secure/intune/remediation-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/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.