Smart Intune Remediation Manager is a SmartM365 operational tool designed to make Microsoft Intune remediation work easier to review, edit, publish, export, and maintain. It combines a local WPF interface with a CLI deployment workflow for teams that manage remediation packages as source-controlled operational assets.
Why this tool exists
Endpoint remediations are powerful, but managing them manually in the Intune admin center can become slow when teams need to compare local scripts, review cloud content, export reports, reset execution history, or publish multiple packages consistently. The goal of Smart Intune Remediation Manager is to reduce that operational friction without hiding the underlying PowerShell and Graph workflow.
What it helps with
- Browse local SmartM365 remediation packages and cloud Intune remediations side by side.
- Edit detection and remediation scripts locally before publishing.
- Run PSScriptAnalyzer checks before deployment.
- Create or update Intune remediation packages through Microsoft Graph.
- Publish detection-only packages when no remediation action should run.
- Export cloud remediation scripts, metadata, assignments, and execution reports.
- Reset remediation history by recreating the remediation object and preserving assignments.
Authentication model
The tool uses delegated interactive Microsoft Graph authentication. It does not use app-only authentication, certificates, client secrets, stored credentials, or unattended access. This keeps the workflow aligned with an operator-driven administration model where actions are tied to the signed-in account.
Operational use cases
A practical use case is preparing a set of remediation packages locally, validating script quality, then publishing them to Intune with consistent naming. Another common scenario is reviewing existing cloud remediations, exporting their current scripts and assignments, and comparing them with source-controlled versions before making changes.
Recommended practice
- Keep remediation source files in Git.
- Use clear detection and remediation naming conventions.
- Test detection-only behavior before enabling remediation actions.
- Review exported execution reports before broad rollout changes.
- Use deployment rings and avoid publishing large changes without a rollback plan.
Where to find it
The source files and documentation are available in the WorkplaceCloudHub GitHub repository under SmartM365/Intune/Remediation/GUI. This website does not host direct software downloads; GitHub is used for review, traceability, and version history.