Public mode

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

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 08:08 UTC Customize Public modeDiscuss ChangeIntel on Discord

Hardening administrative actions: Windows imaging, cloning, and auth workflows

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

What the notice says

Microsoft’s text, with source markup removed
Administrative actions are undergoing hardening changes that might require operational change to support your organization’s security posture. With the August 2025 Windows non-security update, devices were hardened against unauthorized attempts to bypass loopback detection. However, if you’ve cloned machines without Sysprep, you might see Kerberos and NTLM authentication failures. This is by design. The recommended solution is to rebuild affected devices using supported imaging methods. A temporary workaround is also available.    When will this happen: September 2025 and later: Windows security updates include hardening changes that strengthen the trust boundary between identity, authentication, and User Account Control (UAC). April 2026 and later: Windows security updates include a temporary workaround for machines cloned without Sysprep. This registry-based compatibility option isn’t recommended. It reduces security protections introduced by recent updates. End of 2027: The temporary workaround expires.    How this will affect your organization: This affects your organization if:  You manage devices on Windows 11, version 24H2 and later or Windows Server 2025. You installed the August 2025 non-security update or September 2025 security update (or later) on these devices. You notice Kerberos or NTLM authentication failures. These failures surface as LsaSrv Event ID 6167 in the System event log of the target machine. You need to adjust your strategy to clone Windows images.   What you need to do to prepare: Take the following actions:  Stop any automation that clones devices without Sysprep. If not addressed, devices end up with duplicate security IDs (SIDs). Rebuild all devices with duplicate SIDs from scratch, then run Sysprep. It's not sufficient to unjoin devices and run Sysprep.  If needed for transition only, temporarily roll back the hardening change with a registry-based option. Please contact Microsoft Commercial Customer Service and Support (CSS) to get information about this registry value.  For details and instructions, review Hardening administrative actions: What IT pros need to know.    Additional information: Hardening administrative actions: What IT pros need to know KB5070568: Kerberos and NTLM authentication failures due to duplicate SIDs KB5068222: Strengthening administrator protection and Kerberos authentication The Microsoft policy for disk duplication of Windows installations Sysprep

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
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 27 Oct 08:08 UTC · 271 of 272 readable · 270 fully read · documentation 469/469 current