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
RSSWeek of 19 Oct 2026
- Windows 365 Windows 365 Enterprise known issues
May need admin actionCheck the dates against your plans.
3 new passages (about 100 words), 1 edited passage (3 words changed), 1 removed passage (6 words).
Changed in: Administrator protection isn't supported on Cloud PCs · Solution
NewAdministrator protection isn't supported on Cloud PCs [added: If your Cloud PCs are Microsoft Entra hybrid joined and receive the Windows security baselines from the Microsoft Security Compliance Toolkit through Group Policy, Administrator protection is turned on starting with the October 2026 Windows security update, even if you didn't enable it.]
Before: No saved wording on this side.
After: If your Cloud PCs are Microsoft Entra hybrid joined and receive the Windows security baselines from the Microsoft Security Compliance Toolkit through Group Policy, Administrator protection is turned on starting with the October 2026 Windows security update, even if you didn't enable it.
NewSolution [added: If your Cloud PCs receive these baselines through Group Policy, set User Account Control: Configure type of Admin Approval Mode to Legacy Admin Approval Mode in a Group Policy Object that applies to your Cloud PCs and takes precedence over the baseline, then restart them.]
Before: No saved wording on this side.
After: If your Cloud PCs receive these baselines through Group Policy, set User Account Control: Configure type of Admin Approval Mode to Legacy Admin Approval Mode in a Group Policy Object that applies to your Cloud PCs and takes precedence over the baseline, then restart them.
3 more changed passages · see them all
Microsoft's commit: Add Group Policy security baseline note to Administrator protection known issue (#12651)
Observed 20 Oct 20:00 UTC · current page · CC BY 4.0
- Global Secure Access Manage Private Access traffic forwarding profiles
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
1 new passage (about 20 words).
NewKnown limitations [added: Switching to v2 is a non-reversible action. All previous configurations get carried over with no changes to end user traffic.]
Before: No saved wording on this side.
After: Switching to v2 is a non-reversible action. All previous configurations get carried over with no changes to end user traffic.
Microsoft's commit: Update note on switching to v2 for Private Access
Observed 20 Oct 18:42 UTC · current page · MIT
- Purview Purview changes
May need admin actionCheck your firewall and proxy allow lists; check whether new requirements apply to your setup.
1 edited passage (17 words changed).
EditedData Loss Prevention … data transferred over FTP and SFTP
[removed: from managed Windows devices. It can enforce][added: and apply] restrictive actions[removed: to help prevent data exfiltration. Configure][added: based on your organization’s requirements. To get started, configure] FTP and SFTP transfer activities in your Endpoint DLP[removed: policies to get started.][added: policies.] See Protect FTP and SFTP transfers …Before: … data transferred over FTP and SFTP from managed Windows devices. It can enforce restrictive actions to help prevent data exfiltration. Configure FTP and SFTP transfer activities in your Endpoint DLP policies to get started. See Protect FTP and SFTP transfers …
After: … data transferred over FTP and SFTP and apply restrictive actions based on your organization’s requirements. To get started, configure FTP and SFTP transfer activities in your Endpoint DLP policies. See Protect FTP and SFTP transfers …
Observed 20 Oct 13:32 UTC · current page
- Defender Defender for Identity deployment
May need admin actionCheck your firewall and proxy allow lists; check whether new requirements apply to your setup; check the roles and permissions you grant.
4 edited passages (51 words changed).
Changed in: Select your deployment method · Choose a deployment flow
EditedSelect your deployment method [removed: For e][added: E]ligible domain[removed: controllers][added: controllers, AD FS, AD CS, and Microsoft Entra Connect servers] running Windows Server 2019 or[removed: later,][added: later support] sensor[removed: v3.x supports onboarding][added: v3.x. You can onboard these servers] with or without Microsoft Defender for Endpoint deployment.[removed: Other eligible identity-role servers require Defender for Endpoint onboarding.]Before: For eligible domain controllers running Windows Server 2019 or later, sensor v3.x supports onboarding with or without Microsoft Defender for Endpoint deployment. Other eligible identity-role servers require Defender for Endpoint onboarding.
After: Eligible domain controllers, AD FS, AD CS, and Microsoft Entra Connect servers running Windows Server 2019 or later support sensor v3.x. You can onboard these servers with or without Microsoft Defender for Endpoint deployment.
EditedSelect your deployment method … for Endpoint, activate sensor v3.x directly.
[removed: For domain controllers that aren't onboarded to Defender for Endpoint,][added: Otherwise,] use the sensor v3.x onboarding package.[removed: AD FS, AD CS, and Microsoft Entra Connect servers must be onboarded to Defender for Endpoint before activation.]Any supported server type Windows Server …Before: … for Endpoint, activate sensor v3.x directly. For domain controllers that aren't onboarded to Defender for Endpoint, use the sensor v3.x onboarding package. AD FS, AD CS, and Microsoft Entra Connect servers must be onboarded to Defender for Endpoint before activation. Any supported server type Windows Server …
After: … for Endpoint, activate sensor v3.x directly. Otherwise, use the sensor v3.x onboarding package. Any supported server type Windows Server …
2 more changed passages · see them all
Observed 20 Oct 12:46 UTC · current page
- Windows NTLMv1 SSO enforcement phases
May need admin actionCheck the dates against your plans.
3 edited passages (89 words changed).
Changed in: Introduction · References
EditedIntroduction 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 …Before: 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 …
After: This article details changes related to auditing and enforcement of blocking NTLMv1-derived cryptography in Windows. The changes apply to the Windows versions listed in Applies To (Windows 11, versions 26H2, 26H1, 25H2, and 24H2, and Windows Server 2025). The BlockNtlmv1SSO setting and associated Audit and Enforce events are supported throughout the normal lifecycle of these Windows versions, and there are currently no plans to remove the setting. These changes are part of the …
EditedIntroduction [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 …Before: The October 2026 Windows security update introduces a change that strengthens NTLMv1 security by changing the internal …
After: Windows updates released on and after October 13, 2026, strengthen NTLMv1 security by changing the internal …
1 more changed passage · see them all
Observed 20 Oct 07:19 UTC · current page
- Microsoft Graph Graph changes
May need admin actionCheck the roles and permissions you grant.
3 new passages (about 60 words), 1 removed passage (1 word).
New section: Applications
NewApplications [added: Updated the availability of the coopEnforcement property on the authenticationBehaviors resource to include the supported national cloud deployments: US Government L4, US Government L5 (DoD), and China operated by 21Vianet.]
Before: No saved wording on this side.
After: Updated the availability of the coopEnforcement property on the authenticationBehaviors resource to include the supported national cloud deployments: US Government L4, US Government L5 (DoD), and China operated by 21Vianet.
NewIdentity and access | Governance [added: Added the roleManagementCustomCalloutExtension resource type and related methods for integrating external approval, ticketing, compliance, and audit workflows into Privileged Identity Management role assignment lifecycle events.]
Before: No saved wording on this side.
After: Added the roleManagementCustomCalloutExtension resource type and related methods for integrating external approval, ticketing, compliance, and audit workflows into Privileged Identity Management role assignment lifecycle events.
Microsoft's commit: Document coopEnforcement national-cloud availability (#29674)
Observed 20 Oct 01:31 UTC · current page · CC BY 4.0
-
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
1 edited passage (38 words changed).
EditedLinux server … remediation, and a clean upgrade experience. [added: Encryption at rest is optional, but we strongly recommend configuring your Docker or Podman environment to encrypt files used by Microsoft Tunnel containers. For information] … For information about installing and configuring …
Before: … remediation, and a clean upgrade experience. … For information about installing and configuring …
After: … remediation, and a clean upgrade experience. Encryption at rest is optional, but we strongly recommend configuring your Docker or Podman environment to encrypt files used by Microsoft Tunnel containers. For information … For information about installing and configuring …
Observed 20 Oct 00:13 UTC · current page
Quoted wording: © Microsoft Corporation · source and applicable license beside each change.