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
- 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
Quoted wording: © Microsoft Corporation · source and applicable license beside each change.