Release IntuneAutomation Scripts 2026.07.28 · ugurkocde/IntuneAutomation

Fixes

Updated 56 Azure Automation compatible Microsoft Graph scripts so script-level progress, outcomes, no-op decisions, warnings, and completion summaries are recorded in standard job output.
This resolves runbooks that appeared to stop immediately after a successful Microsoft Graph connection because later messages were written only to the Information stream.
All eight notification runbooks now visibly report data retrieval, no alert required paths, email delivery attempts, and final results in Azure Automation job history.

Kept helper-function diagnostic logging off the output stream where output pollution could alter returned data, preserving existing behavior.
Added AST-based validation that fails CI if future scripts or templates introduce script-scope Write-Information logging.
All 75 PowerShell scripts passed repository analysis. MCP build and verification completed with 38 checks passed.

Bumped the .VERSION field by one minor step for each of the 56 affected scripts.
Added a changelog entry and set .LASTUPDATE to 2026-07-28 for every affected script.
Refreshed the script index, Azure deployment templates, and test artifacts. The website now displays the updated versions, dates, and changelog entries.

No Microsoft Graph permissions or script parameters changed.
No breaking changes are included.
Existing Azure Automation users must import the updated script and publish a new runbook version, or redeploy from the updated Azure template, to receive the improved job-history output.
The 12 remediation scripts were not version-bumped because they did not contain the affected runbook logging pattern.
Fine-grained helper-function diagnostics remain on the Information stream to protect function return values. Script-level outcomes and summaries are visible in normal job history.