fairfax 0.2.2

What happens when Microsoft deletes or moves a page fairfax cites?

• A deleted page now fails the weekly check. A page that returns 404 or 410 is reported as GONE and exits 1, so the watch workflow opens an issue. A timeout or server error is still UNREACHABLE (exit 2), since that is usually temporary.
• Every source has an archived copy. All 33 cited pages, plus the Power Platform PDF, have a Wayback Machine snapshot that was checked to contain every row fairfax cites from it (1,164 rows). Findings in --format md and json, fairfax facts --format json and fairfax explain link to it.
• fairfax verify --archived runs the same checks against the snapshots instead of the live pages.
• tools/mark_checked.py saves a new snapshot whenever Microsoft updates a page, and records it only after the cited rows are found in it.

Data: Microsoft updated the Teams service description on 2026-10-12. Two cited rows were reworded (Teams events, Webinars (Teams events)); every status is unchanged.

pip install --upgrade fairfax · uses: intikhab49/fairfax@v0.2.2

fairfax 0.2.1

The GitHub Action's description is now under the Marketplace's 125-character limit, so the action can be listed there. No other changes from 0.2.0, which has the full notes.

pip install --upgrade fairfax · uses: intikhab49/fairfax@v0.2.1

fairfax 0.2.0: Microsoft 365, sign-in errors, verify, SARIF, MCP server, GitHub Action

fairfax now covers Microsoft 365 as well as Azure and Power Platform, decodes the sign-in errors that mixing clouds causes, and checks its own citations against Microsoft's live pages every week.

New

• Microsoft 365. Copilot, Teams, Exchange Online, SharePoint, OneDrive, Purview, Intune, and Defender for Endpoint and XDR: 446 new features, each quoted from Microsoft's per-cloud tables. The dataset is now 633 features from 33 Microsoft sources.
• Roadmap dates on blocked findings. Six Microsoft 365 roadmap items are linked by hand to the features they deliver. A finding says when the target month has passed, or when the roadmap and the table disagree.
• fairfax explain decodes 9 cross-cloud AADSTS sign-in errors, such as AADSTS900439, from the code or the whole message: Microsoft's wording, the cause and the right sign-in host for your clouds.
• fairfax verify re-reads every cited Microsoft page and confirms each cited row is still there, word for word. A weekly workflow in this repo runs it and opens an issue when Microsoft changes one.
• SARIF output for check and scan (--format sarif).
• GitHub Action. uses: intikhab49/fairfax@v0.2.0 runs check and scan, writes the job summary, marks findings on their lines and can upload SARIF to code scanning.
• fairfax mcp, a Model Context Protocol server, so coding agents can find features, check a plan, scan code and explain errors with citations: claude mcp add fairfax -- fairfax mcp.
• Scan knows the Defender XDR and Defender for Endpoint API hosts, including GCC's own (api-gcc.security.microsoft.us).

Fixed

• 17 entries in 0.1 summarized a table instead of quoting it: 11 Azure OpenAI models, 3 Azure AI Language features and 3 endpoint rows. The endpoint rows now quote Microsoft. The other 14 can't be a single row, so they are marked cite: summary and fairfax verify re-derives them from the live page.

Changed

• Report headers count features (633) rather than entries: Purview publishes one page per cloud, so its features have one entry per cloud.
• New statuses, in Microsoft's own words: planned, in development, on engineering backlog, rolling out.

pip install --upgrade fairfax · Website · Sign-in errors · Availability tables

fairfax 0.1.2

Packaging and docs only, no change to the checker or the dataset.

• PyPI now links to the website (https://intikhab49.github.io/fairfax/), the availability tables, the docs and the changelog.
• More keywords and classifiers on PyPI.
• The README links the website and has an FAQ.

fairfax 0.1.1

Packaging release. The checker and the dataset are the same as 0.1.0.

• The PyPI page now shows pip install fairfax and a PyPI version badge.
• The version number lives only in src/fairfax/__init__.py.
• This is the first version published by GitHub Actions through PyPI trusted publishing, so no API token was involved.

pip install --upgrade fairfax

fairfax 0.1.0

First release.

fairfax checks a planned Microsoft gov-cloud stack (GCC, GCC High, DoD, Azure Government) against Microsoft's own availability tables, and quotes the Microsoft row behind every finding.

• fairfax check plan.yaml sorts each planned feature into blocked, cross-cloud, retiring, notes or ok.
• fairfax scan <path> finds Microsoft endpoints in code that belong to the wrong cloud. It knows that GCC keeps the worldwide Entra ID and Graph endpoints.
• fairfax facts --grep <word> finds feature keys, and fairfax facts --stale 90 lists the cited pages due for another check.

The dataset has 187 features, 8 stack rules and 55 endpoint mappings, taken from 14 Microsoft Learn pages and the Business Applications US Government PDF (May 2026). Every page was checked on 2026-10-11.

pip install fairfax

The two files attached here are the exact files published to PyPI (same SHA-256).