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
‹ March 2027 ›
MonTueWedThuFriSatSun12345678910111213141516171819202122232425262728293031

March 2027 in brief

No change observed this month under these filters.

Week of 26 Oct 2026

  1. Windows Server AD FS DKM container hardening

    Read to decideA few words changed without matching a rule; read the marked wording to decide.

    1 edited passage (2 words changed).

    Changed wording view
    EditedEvent references
    … the event entry with Instance ID [removed: <Instance ID>.] [added: .] There may be more events with …
    Before: … the event entry with Instance ID <Instance ID>. There may be more events with …
    After: … the event entry with Instance ID . There may be more events with …

    Observed 30 Oct 00:27 UTC · current page

Week of 19 Oct 2026

  1. Read to decideNew content in “Active Directory site configuration”; read it to see whether it concerns you.

    3 new passages (about 80 words).

    New section: Active Directory site configuration

    Changed wording view
    NewActive Directory site configuration
    [added: The Microsoft Entra provisioning agent uses standard Active Directory domain controller discovery mechanisms. Incorrect DNS configuration, subnet-to-site mappings, or site configuration can cause synchronization failures, performance issues, or intermittent connectivity problems.]
    Before: No saved wording on this side.
    After: The Microsoft Entra provisioning agent uses standard Active Directory domain controller discovery mechanisms. Incorrect DNS configuration, subnet-to-site mappings, or site configuration can cause synchronization failures, performance issues, or intermittent connectivity problems.
    NewActive Directory site configuration
    [added: Ensure that servers hosting provisioning agents are in correctly defined Active Directory sites. In Active Directory Sites and Services, associate each server's IP subnet with the appropriate site. Proper site and DNS configuration helps the agent discover appropriate domain controllers and can improve synchronization reliability and performance.]
    Before: No saved wording on this side.
    After: Ensure that servers hosting provisioning agents are in correctly defined Active Directory sites. In Active Directory Sites and Services, associate each server's IP subnet with the appropriate site. Proper site and DNS configuration helps the agent discover appropriate domain controllers and can improve synchronization reliability and performance.

    Microsoft's commit: Document HR provisioning timeout troubleshooting (#14678)

    Observed 23 Oct 08:15 UTC · current page · MIT

  2. 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

Week of 12 Oct 2026

  1. 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

    Changed wording view
    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

  2. Active Directory AD FS

    Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    1 removed passage (18 words).

    Changed wording view
    RemovedAD FS Overview
    [removed: Applies to: ✅ Windows Server 2025, ✅ Windows Server 2022, ✅ Windows Server 2019, ✅ Windows Server 2016]
    Before: Applies to: ✅ Windows Server 2025, ✅ Windows Server 2022, ✅ Windows Server 2019, ✅ Windows Server 2016
    After: No saved wording on this side.

    Observed 13 Oct 00:39 UTC · current page · CC BY 4.0

  3. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 23:53 UTC · current page

  4. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 23:53 UTC · current page

  5. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 23:53 UTC · current page

  6. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 23:53 UTC · current page

  7. Entra Cloud Sync changes

    Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 19:19 UTC · current page

  8. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 19:19 UTC · current page

  9. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 12 Oct 19:19 UTC · current page

Week of 5 Oct 2026

  1. Entra Cloud Sync changes

    May need admin actionCheck the dates against your plans.

    3 new passages (about 30 words), 1 removed passage (about 30 words).

    New section: 1.1.2507.0

    Also changed: Fixed issues · Microsoft Entra provisioning Agent: Version release history

    Changed wording view
    New1.1.2507.0
    [added: Release date: October 8, 2026]
    Before: No saved wording on this side.
    After: Release date: October 8, 2026
    NewFixed issues
    [added: Fixed an issue that failed installation of the agent on a localized Windows Server installation, including but not limited to Polish, German, and Dutch languages with error 0x80070643.]
    Before: No saved wording on this side.
    After: Fixed an issue that failed installation of the agent on a localized Windows Server installation, including but not limited to Polish, German, and Dutch languages with error 0x80070643.

    1 more changed passage · see them all

    Observed 9 Oct 17:50 UTC · current page · MIT

  2. Entra Cloud Sync changes

    Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    2 new passages (about 60 words), 1 edited passage (1 word changed).

    Changed in: Microsoft Entra provisioning Agent: Version release history · Known issues

    Changed wording view
    NewMicrosoft Entra provisioning Agent: Version release history
    [added: Warning Microsoft Entra Provisioning Agent version 1.1.2505.0 may fail to install on localized Windows Server installations, including Polish, German, and Dutch versions. For more information, see Known issues.]
    Before: No saved wording on this side.
    After: Warning Microsoft Entra Provisioning Agent version 1.1.2505.0 may fail to install on localized Windows Server installations, including Polish, German, and Dutch versions. For more information, see Known issues.
    NewKnown issues
    [added: If you are installing the agent on a localized Windows Server installation, including but not limited to Polish, German and Dutch languages, the operation may fail with error 0x80070643 and rollback.]
    Before: No saved wording on this side.
    After: If you are installing the agent on a localized Windows Server installation, including but not limited to Polish, German and Dutch languages, the operation may fail with error 0x80070643 and rollback.

    1 more changed passage · see them all

    Observed 7 Oct 17:31 UTC · current page · MIT

  3. No action expectedA spelling or formatting correction; the meaning is unchanged.

    1 edited passage (1 word changed).

    Changed wording view
    EditedUpdated Features
    Introduced a registry key that allows you to set the precedence number for custom rules to be more than 100, if needed. The precedence of the first standard rule can be set using the key H[removed: LK][added: KL]M:\SOFTWARE\Microsoft\Azure AD Connect\FirstStandardRulePrecedence, allowing for more custom rules. If no value is set, 100 is the default.
    Before: Introduced a registry key that allows you to set the precedence number for custom rules to be more than 100, if needed. The precedence of the first standard rule can be set using the key HLKM:\SOFTWARE\Microsoft\Azure AD Connect\FirstStandardRulePrecedence, allowing for more custom rules. If no value is set, 100 is the default.
    After: Introduced a registry key that allows you to set the precedence number for custom rules to be more than 100, if needed. The precedence of the first standard rule can be set using the key HKLM:\SOFTWARE\Microsoft\Azure AD Connect\FirstStandardRulePrecedence, allowing for more custom rules. If no value is set, 100 is the default.

    Observed 7 Oct 17:31 UTC · current page · MIT

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 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current