Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

6.2.3. Remediations

💡 First Principle: Remediations runs as a closed loop. A detection script asks "is the known fault present?" and answers with an exit code; only if the answer is yes does the remediation script run, and the next detection run proves whether the fix held. Because the decision is a single exit code, you can reason about any Remediations scenario by asking one question: what did the detection script return?

Think of a help desk that gets 40 tickets a week because the Office Click-to-Run service has stopped on some laptops. You could fix each one by hand. Or you could deploy a script package that checks the service every hour, restarts it when it's stopped, and reports how often it had to. That second option is Remediations, formerly Proactive remediations, found at Devices > Manage devices > Scripts and remediations.

Script packages. Each package holds a detection script, an optional remediation script and metadata, so a package can be detection-only when you just want visibility. The remediation script runs only when the detection script exits with exit 1. Any other exit code, including empty output, means "issue not found". That rule causes most broken packages: a detection script that writes "Service stopped" to the console but exits with 0 tells Intune everything is fine. Two built-in packages need only assigning: Update stale Group Policies and Restart Office Click-to-run service.

Requirements. Devices must be Entra joined or Entra hybrid joined, and either MDM-enrolled in Intune running Windows Enterprise, Professional or Education, or co-managed. Licensing is covered in 6.2's misconception. Creating packages needs permissions in the Device configurations category. Limits: up to 200 script packages, output up to 2,048 characters, and scripts encoded in UTF-8 (without a BOM if you enforce the signature check). If you enforce the signature check, the device's PowerShell execution policy applies, and the Windows client default is Restricted; without it, scripts run with Bypass. Microsoft recommends signature check No and 64-bit No for custom packages, and no reboot commands, passwords or personal data in scripts.

Scheduling and assignment. Assign packages to device groups, refined with filters if you need to, and don't mix user and device groups across include and exclude. The schedule is Once (a date and time), Hourly (every n hours, fewer than 24) or Daily (at a set time), in the device's local time unless you select Use UTC. Missed runs happen once the device is back online. For heavy or non-urgent scripts, Microsoft suggests running less often, such as every seven days. The client retrieves Remediation policy after a restart of the device or the Intune Management Extension service, after a user signs in, and every eight hours; push notifications (service release 2610) now speed delivery.

Running on demand. Run remediation (preview) runs a package immediately on one Windows device from the device's Overview page. The package doesn't need to be assigned, the admin needs the Run remediation permission under Remote tasks, the device needs WNS connectivity, and only one Run remediation action can run on a device at a time.

Monitoring. The package overview shows detection and remediation status, Device status lists each device, and output exports to CSV. Recurring scripts send a full report every seven days. On the device, the log for scheduled remediations is HealthScripts.log.

FeaturePurposeRunsFixes anything?Requirements and limits
Platform scriptsOne-time configuration taskOnce; retried up to three times on failure; reruns only if the script or policy changesOnly what the script itself does, one timeUnder 200 KB; 30-minute timeout; not on Entra registered-only devices; run before Win32 apps
Custom complianceReport a setting for compliance and Conditional AccessEvery eight hoursNo, reporting onlyWindows, macOS, Linux; one script per policy; 1 MB script and output
RemediationsDetect a known fault and fix it, repeatedlyOn a schedule (once, hourly, daily) or on demandYes, when detection exits with 1Windows Enterprise, Education or VDA licensing; 200 packages; 2,048-character output

⚠️ Exam Trap: If a scenario says the remediation script never runs although the problem is clearly present, check the detection script's exit code before anything else. Remediation runs only on exit 1. Writing output, returning $true or exiting with any other code means "no issue found", so the package quietly reports success.

Reflection Question: You need to delete a temporary folder once on every device, and separately keep a security setting from being changed back by users. Which feature fits each job, and what would go wrong if you swapped them?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned