AD functional level upgrade planning
No content change seen yet. Watched since 5 Oct 17:50 UTC, last read today 20:15 UTC, next check 21 Oct 02:15 UTC. Microsoft's own edits are listed below.
Read the Microsoft source · Link to this observation · My radar
Timeline
From the capture of 5 Oct 17:50 UTC · an earlier observationLegacy capture: table structure or oversized sections are unavailable for extraction
Microsoft's revision log on this page · 13 entries
Dates from the page's own change log or history section. They describe earlier edits, not upcoming policy.
- Identifying your functional level upgradeRequirement
Extracted automatically from Microsoft's wording. Confirm dates, conditions and whether they apply to you in the source before acting; a month or quarter is a window, not a day.
How this timeline changed
Changes between ChangeIntel's readings of the page, between commits of its source file where Microsoft publishes it, in Internet Archive copies of pages that keep no other history, and entries from Microsoft's own change log (dated as Microsoft dates them). Edits between readings that neither records are unknown.
-
-
-
No longer on the page Upgrading functional levels to Windows Server 2025Microsoft's source, commit ea806f7
-
No longer on the page Upgrading functional levels to Windows Server 2025Microsoft's source, commit ea806f7
52 earlier changes
-
No longer on the page Upgrading functional levels to Windows Server 2025Microsoft's source, commit ea806f7
-
No longer on the page Upgrading functional levels to Windows Server 2025Microsoft's source, commit ea806f7
-
-
-
Observed history and review priority
Captured 5 Oct 17:50 UTC; extracted 16 Oct 16:10 UTC. Extractor: microsoft-1/9/fc65ebeb286710c0a830833db8a7e5de7e266b79981fe9c7c34479be9369ad3c/legacy.
Earlier unavailable versions and edits between checks are unknown. A missing statement requires review; it does not mean the policy was cancelled. Recovered historical statements are not original revision snapshots.
Retained observations · 18
Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.
- 12 Oct 19:50 UTC · 13 candidates
- 6 Oct 17:57 UTC · 16 candidates
- 5 Oct 17:50 UTC · 16 candidates
- 11 Mar 12:37 UTC · 13 candidates
- 11 Mar 12:19 UTC · 13 candidates
- 3 Mar 2025 21:42 UTC · 13 candidates
- 3 Mar 2025 21:33 UTC · 13 candidates
- 6 Jan 2025 16:31 UTC · 13 candidates
- 1 Nov 2024 22:14 UTC · 13 candidates
- 25 Oct 2024 17:01 UTC · 13 candidates
- 22 Oct 2024 16:23 UTC · 13 candidates
- 15 Jul 2024 12:17 UTC · 13 candidates
- 30 May 2024 09:23 UTC · 13 candidates
- 23 May 2024 19:23 UTC · 14 candidates
- 7 May 2024 20:55 UTC · 26 candidates
- 16 Apr 2024 16:39 UTC · 26 candidates
- 16 Apr 2024 16:25 UTC · 26 candidates
- 15 Apr 2024 20:42 UTC · 26 candidates
Microsoft's edits
History on GitHubCommits to the page's source in MicrosoftDocs/windowsserverdocs, with Microsoft's own messages. Commit dates can be hours or days before Learn publishes the change. ChangeIntel keeps a copy of each diff, so an edit stays readable here if GitHub stops serving it. Read 19 Oct 23:40 UTC.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Retained observations
- 12 Oct 19:50 UTC
9 removed passages (about 70 words). The changed wording mentions dates and deadlines, prerequisites. Review the source to confirm the effect.
- 6 Oct 17:57 UTC
Source metadata changed; retained article content is unchanged.
- 5 Oct 17:50 UTC · shown above
What changed
First observed 18 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.