Skip to content

Publish Microsoft 365 incident triage article and PowerShell toolkit - #8

Open
dleontev wants to merge 4 commits into
mainfrom
codex/m365-incident-triage-toolkit
Open

dleontev wants to merge 4 commits into
mainfrom
codex/m365-incident-triage-toolkit

Conversation

@dleontev

Copy link
Copy Markdown
Owner

Adds a complete walkthrough for collecting Microsoft 365 service-health evidence and producing an incident escalation report. The downloadable PowerShell toolkit includes a synthetic demo, sample JSON/Markdown output, an escalation template, and offline regression tests. The project page now links to the available release.

The collector uses delegated ServiceHealth.Read.All in Global, validates the requested tenant, follows bounded pagination, preserves partial evidence, and raises a terminating error when collection is incomplete. Live tenant integration has not been tested; the article and README state that limitation.

Validation: all 15 offline tests pass, including the extracted ZIP; the ZIP matches its eight source files; Jekyll validation passes for 15 HTML pages, four search entries, and 13 certifications. Local browser checks cover 320/390px layouts, desktop light/dark rendering, contents links and keyboard focus, blog search, and project links. The existing Actions browser/accessibility/visual suite runs before publication.

Preserve current portfolio content and resolve the README conflict. Update toolkit article relationships to canonical URLs, normalize the synthetic sample to match the ZIP, and add offline CI and keyboard accessibility regression coverage.
Run the offline suite in a separate PowerShell process and explicitly propagate its exit status. Expected failing child processes in successful tests must not make the Actions wrapper fail after archive validation.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant