Entra ID Change Tracker

Tier A

Microsoft announced this as a change with structured metadata behind it — a labelled "Type" field on the What's New page, or an official Graph API deprecation entry. The strongest signal available: this is Microsoft formally saying "this is changing."

Tier B

Official Microsoft documentation content says this is happening — a docs changelog entry, a release-notes callout, or a What's New entry without the structured metadata Tier A relies on. Still Microsoft's own words, just without the formal label.

Tier C

A signal that something is coming, not an announcement of it — specifically, a new how-to article appearing in Microsoft's documentation repository before it's been added to the curated changelog. Useful as an early heads-up; treat it as less certain than Tier A or B until it's confirmed elsewhere.

Deadline confidence

Every deadline the tracker shows a countdown for was picked out of Microsoft's own text, not just the first date-shaped string it found. Stated means the cutoff was spelled out in the same sentence as words like "retired," "deprecated," or "must migrate" — the strongest kind of date. Derived means cutoff language was nearby but not in the same sentence. Both get a normal countdown.

Unconfirmed dates

Sometimes the only date in an entry doesn't have clear cutoff language near it — it might be a rollout date, a publish date, or a genuine deadline Microsoft just didn't phrase clearly. Rather than guess with a countdown, the tracker shows the date plainly, labelled "possible date… unconfirmed." Treat it as a lead to verify against the linked Microsoft article, not a date to plan around. The same items are marked with a leading "~" in the .ics calendar feed.

Microsoft 365 Roadmap

Alongside the documentation and changelog sources above, the tracker also pulls Microsoft's own 365 Roadmap for items tagged "Microsoft Entra". Roadmap items carry structured Microsoft metadata (a feature id, a lifecycle status, a stated date), so they're treated as Tier A like any other structured announcement. When a roadmap entry clearly matches something already being tracked, it's attached to that item as a supplementary "Roadmap" note rather than shown as a second, duplicate card — labelled with a definite "Roadmap" tag when the match is an explicit id reference, or hedged as "likely related" when it's based on title and date similarity instead (a hedge on purpose: similarity is a judgement call, not a fact, and this tracker would rather under-match than wrongly weld two different features together). Roadmap entries that don't clearly match anything already tracked become their own standalone card. Occasionally the roadmap states a different date for a feature than another Microsoft source does for the same item — both official channels, genuinely disagreeing — shown as a plain ⚠ Dates disagree flag rather than silently picking one. Neither date is hidden in that case.

↻ Revised

The tracker records every change it observes to an item's tracked fields (title, category, status, deadline, deadline confidence, announced date, service area) as its own dated revision. When an item's deadline specifically has changed — not just any field, since a title reword or a status drifting from green to yellow as time passes isn't a "slip" — the card gets this badge, and expanding it shows the deadline's full history: every value it has held and when the tracker first saw each one, plus the complete underlying revision log on demand. This is observed, not asserted — the tracker began recording on 16 August 2026; a deadline that slipped before that date, with no further change since, will show as "never moved" until its next real change, because that earlier history genuinely isn't visible to the tracker. "Moved N times" always means N times the tracker has personally witnessed, not the item's full lifetime — said plainly here rather than implying more certainty than the record actually has. Expect this to be sparse at first: the record is young and gets richer as more builds run.

What this tracker covers

Every item is matched against a single, fixed list of Entra and associated identity services — an item that doesn't match anything on this list isn't shown, on purpose, rather than left in as noise. Filter the feed by service area using the chips in the filter bar. Currently covered:

Loading…