Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Guidance changes

Observed changes to selected Microsoft guidance. Review in My radar · Timelines and exceptions

469 of 469 selected pages have a baseline. 401 pages have an observed change; the newest was seen today.

Coverage and checks

469 of 469 selected pages have a baseline · 401 with observed changes · 469 current checks

Observed changes

RSS
‹ October 2026 ›
MonTueWedThuFriSatSun123456178910111221314151617183193202211222312422526274282292308312

Monday 19 October 2026 · day in brief

3 changes to 3 pages

3 may need admin action

Windows 1 · Windows Server 1 · Power Platform 1

← 18 Oct20 Oct →All days

Week of 19 Oct 2026

  1. Windows Server AD FS DKM container hardening

    May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices; check the roles and permissions you grant.

    18 new passages (about 1020 words), 12 edited passages (179 words changed), 27 removed passages (about 610 words).

    New sections: In this article · Opting out of automatic remediation · Ownership failure event case (Event ID 1137) · Save the previous SDDL (Recommended) and 3 more

    Also changed: CVE-2026-56155: AD FS Distributed Key Manager container ACL hardening · Summary · Take action · Expected secure state changes and 1 more

    Changed wording view
    EditedCVE-2026-56155: AD FS Distributed Key Manager container ACL hardening
    [removed: Note] Original publish date: July 14, 2026 …
    Before: Note Original publish date: July 14, 2026 …
    After: Original publish date: July 14, 2026 …
    NewIn this article
    [added: Opting out of automatic remediation]
    Before: No saved wording on this side.
    After: Opting out of automatic remediation

    3 more changed passages · see them all

    Observed 19 Oct 00:53 UTC · current page

  2. May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices; check the dates against your plans.

    26 new passages (about 560 words), 12 edited passages (133 words changed), 3 removed passages (about 70 words).

    New sections: Changes · Preparing for Enforce mode · Temporary security exception · References

    Also changed: Introduction · Background · Goal · New registry key and 4 more

    Changed wording view
    EditedIntroduction
    This article details [removed: the recent and upcoming] changes in Windows 11, [removed: version] [added: versions 26H2, 25H2, and] 24H2 and Windows Server 2025, focusing on the auditing and [removed: eventual] enforcement of blocking NTLMv1-derived cryptography. These changes are part of [removed: Microsoft’s] [added: the] broader [added: Microsoft] initiative to phase out NTLM.
    Before: This article details the recent and upcoming changes in Windows 11, version 24H2 and Windows Server 2025, focusing on the auditing and eventual enforcement of blocking NTLMv1-derived cryptography. These changes are part of Microsoft’s broader initiative to phase out NTLM.
    After: This article details changes in Windows 11, versions 26H2, 25H2, and 24H2 and Windows Server 2025, focusing on the auditing and enforcement of blocking NTLMv1-derived cryptography. These changes are part of the broader Microsoft initiative to phase out NTLM.
    NewIntroduction
    [added: The October 2026 Windows security update introduces a change that strengthens NTLMv1 security by changing the internal default behavior when the BlockNtlmv1SSO registry value is] …
    Before: No saved wording on this side.
    After: The October 2026 Windows security update introduces a change that strengthens NTLMv1 security by changing the internal default behavior when the BlockNtlmv1SSO registry value is …

    3 more changed passages · see them all

    Observed 19 Oct 00:53 UTC · current page

  3. Power Platform Power Platform deprecations

    May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices; check the roles and permissions you grant.

    86 new passages (about 1980 words).

    New sections: Deprecation of Microsoft Dataverse for Teams environments · Timeline · What's the recommended migration path for Dataverse for Teams environments? · Who can upgrade a Dataverse for Teams environment? and 8 more

    Also changed: Why is this change needed? · Impact · What isn't affected · Action required and 1 more

    Changed wording view
    NewDeprecation of Microsoft Dataverse for Teams environments
    [added: Microsoft Dataverse for Teams environments are deprecated. The deprecation happens in three phases. You can't create new Dataverse for Teams environments starting November 15, 2026.] …
    Before: No saved wording on this side.
    After: Microsoft Dataverse for Teams environments are deprecated. The deprecation happens in three phases. You can't create new Dataverse for Teams environments starting November 15, 2026. …
    NewWhy is this change needed?
    [added: Dataverse for Teams provides a subset of Microsoft Dataverse capabilities. For example, it limits each environment to 2 GB of storage, doesn't provide direct API] …
    Before: No saved wording on this side.
    After: Dataverse for Teams provides a subset of Microsoft Dataverse capabilities. For example, it limits each environment to 2 GB of storage, doesn't provide direct API …

    3 more changed passages · see them all

    Observed 19 Oct 00:22 UTC · current page

Quoted wording: © Microsoft Corporation · source and applicable license beside each change.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current