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 12 Oct 2026
- Entra Entra licensing
May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant.
1 edited passage (4 words changed), 7 removed passages (about 570 words).
Changed in: Microsoft Entra ID Governance · Example license scenarios · Example license scenarios for PIM
EditedMicrosoft Entra ID Governance … licensing requirements for Microsoft Entra ID Governance features for member users. Microsoft Entra Suite includes all features of Microsoft Entra ID Governance. Microsoft 365 E7 also includes all ID Governance features through the Entra Suite and Agent 365. Licensing information
[removed: and example license scenarios]for Entitlement management, Access reviews, and Lifecycle Workflows are provided following the table.Before: … licensing requirements for Microsoft Entra ID Governance features for member users. Microsoft Entra Suite includes all features of Microsoft Entra ID Governance. Microsoft 365 E7 also includes all ID Governance features through the Entra Suite and Agent 365. Licensing information and example license scenarios for Entitlement management, Access reviews, and Lifecycle Workflows are provided following the table.
After: … licensing requirements for Microsoft Entra ID Governance features for member users. Microsoft Entra Suite includes all features of Microsoft Entra ID Governance. Microsoft 365 E7 also includes all ID Governance features through the Entra Suite and Agent 365. Licensing information for Entitlement management, Access reviews, and Lifecycle Workflows are provided following the table.
RemovedExample license scenarios [removed: Here are some example license scenarios to help you determine the number of licenses you must have.]Before: Here are some example license scenarios to help you determine the number of licenses you must have.
After: No saved wording on this side.
4 more changed passages · see them all
Observed 18 Oct 23:50 UTC · current page · MIT
- Defender Defender for Identity deployment
May need admin actionCheck whether new requirements apply to your setup; check the dates against your plans.
1 new passage (about 20 words), 2 edited passages (21 words changed), 1 removed passage (12 words).
Changed in: Select your deployment method · Choose a deployment flow
EditedSelect your deployment method … the following table to select the
[removed: appropriate deployment for each][added: recommended deployment. For supported v2.x platforms, see v2.x] server[removed: in your environment.][added: requirements. Review the migration prerequisites separately before upgrading an existing v2.x sensor.]Before: … the following table to select the appropriate deployment for each server in your environment.
After: … the following table to select the recommended deployment. For supported v2.x platforms, see v2.x server requirements. Review the migration prerequisites separately before upgrading an existing v2.x sensor.
EditedSelect your deployment method … Server 2019 or later with the
[removed: July][added: September] 2026 or later cumulative update Defender …Before: … Server 2019 or later with the July 2026 or later cumulative update Defender …
After: … Server 2019 or later with the September 2026 or later cumulative update Defender …
2 more changed passages · see them all
Observed 18 Oct 23:50 UTC · current page
-
May need admin actionCheck whether new requirements apply to your setup.
1 new passage (17 words), 2 edited passages (4 words changed).
New section: Configure sensors for AD FS, AD CS, and Microsoft Entra Connect
Also changed: Prerequisites
NewConfigure sensors for AD FS, AD CS, and Microsoft Entra Connect [added: Use these procedures for Defender for Identity v2.x sensors. For v3.x sensors, follow v3.x deployment and configuration.]
Before: No saved wording on this side.
After: Use these procedures for Defender for Identity v2.x sensors. For v3.x sensors, follow v3.x deployment and configuration.
EditedPrerequisites … The following additional requirements apply to [added: v2.x sensors on] AD FS, AD CS, and Microsoft …
Before: … The following additional requirements apply to AD FS, AD CS, and Microsoft …
After: … The following additional requirements apply to v2.x sensors on AD FS, AD CS, and Microsoft …
1 more changed passage · see them all
Observed 18 Oct 23:50 UTC · current page
Quoted wording: © Microsoft Corporation · source and applicable license beside each change.