NTLMv1 SSO enforcement phases
Any two versions this installation kept of the page, compared the same way as each observed change. All guidance changes · Latest observation
What changed
3 edited passages (89 words changed). The changed wording mentions dates and deadlines, supported platforms, settings and controls. Review the source to confirm the effect.
May need admin actionCheck the dates against your plans; check the platforms and versions you run; check the settings the wording names.
This article details changes [added: related to auditing and enforcement of blocking NTLMv1-derived cryptography] in [added: Windows. The changes apply to the] Windows [added: versions listed in Applies To (Windows] 11, versions 26H2, [added: 26H1,] 25H2, and 24H2[added: ,] and Windows Server[removed: 2025, focusing on the auditing][added: 2025). The BlockNtlmv1SSO setting] and[removed: enforcement][added: associated Audit and Enforce events are supported throughout the normal lifecycle] of[removed: blocking NTLMv1-derived cryptography.][added: these Windows versions, and there are currently no plans to remove the setting.] These changes are part of the …
[removed: The October 2026]Windows[removed: security update introduces a change that strengthens][added: updates released on and after October 13, 2026, strengthen] NTLMv1 security by changing the internal …
Date Change October [added: 19, 2026 The article was retitled and the Introduction section was revised. Windows 11, version 26H1 was added to the list of products this article] … 14, 2026 Edits across the article …
Short quotes of Microsoft's changed wording from Microsoft source, © Microsoft Corporation. Read the page for the full text.
Sections to inspect
Read the current Microsoft source
Compared across every change between the two versions, so an edit made and later undone does not show. Observation time is not publication time. Full source bodies are not published; as the page's license allows, only Microsoft's changed wording is shown.