Small nuggets. Big impact.

Never miss a Microsoft docs change again.

MSChanges watches Microsoft's official documentation repositories on GitHub and turns every edit into a clean, filterable feed — Intune, Entra, Defender, Sentinel, Purview, Copilot and Microsoft 365, all in one place.

Tracked straight from Microsoft's official documentation repositories on GitHub.

700+Tracked doc changes
7Microsoft products
90dRolling window
5Docs repos tracked
Coverage

Every product that matters, in one feed

MSChanges follows the public MicrosoftDocs repositories and files each change under the right product.

Features

Built for people who live in the admin portals

A focused tool for IT pros, consultants and MVPs who need to know what Microsoft just changed.

One chronological feed

Every documentation edit, newest first, grouped by day — so a quick scan tells you what moved this week.

Filter by product & status

Tabs for each product, pills for added / modified / renamed / removed, and a time window — combine them instantly.

See the actual diff

Click any change for a popup with the real line-by-line diff — additions and removals highlighted — without leaving the page.

Straight to the source

Every entry also deep-links to the exact GitHub diff and, where known, the live learn.microsoft.com page.

Find a specific document

Type any keyword — a feature, a setting, a file name or path — and the feed filters across titles, areas, commit messages and paths.

A year on one timeline

A horizontal activity timeline shows when and where docs changed over the last 365 days. Click any bar to focus that period.

Fresh every day

A scheduled GitHub pipeline rechecks the documentation repositories daily, so the feed keeps up with Microsoft automatically.

Installable & offline

Install MSChanges as a PWA. The latest feed is cached, so it keeps working with no network at all.

How it works

A GitHub pipeline does the watching

No scraping, no guesswork — straight from Microsoft's own source of truth.

  1. 1

    Watch the repos

    A scheduled GitHub Action walks the public MicrosoftDocs repositories — memdocs, entra-docs, defender-docs and more.

  2. 2

    Classify every edit

    Each changed documentation page is filed under its product and area, with its status, author, commit and diff.

  3. 3

    Ship a static feed

    The result is written to a single data file the site loads — fast and instantly filterable.

FAQ

Frequently asked questions

Where does the data come from?

Directly from the public MicrosoftDocs/* repositories on GitHub — the same source Microsoft publishes learn.microsoft.com from. A scheduled GitHub Action reads recent commits, extracts the changed documentation pages and writes them into the feed.

How often is it updated?

The pipeline runs on a schedule (a few times a day) and on demand. The app's status bar shows when the feed was last generated — currently recently.

Why isn't Purview showing changes?

Microsoft Purview's compliance documentation is not published to a public GitHub repository, so it can't be tracked from source the way the other products are. Purview-related edits that appear in other repos are filed under Purview automatically, and the product is listed so coverage can grow if a public source becomes available.

Is it affiliated with Microsoft?

No. MSChanges is an independent open-source project and is not affiliated with, endorsed by or sponsored by Microsoft. It only links to publicly available documentation and GitHub commits.

How far back does the history go?

The pipeline looks back up to 365 days, and the timeline lets you switch between 7, 30, 90, 365 days or all. How far the dense history reaches depends on how active each repository is — the busiest ones (Entra, Defender) fill the most recent months first. Each page shows its most recent change.

Ready when you are

See what Microsoft changed today

No install, no accounts. Open the feed and start filtering.