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: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 14:23 UTC Customize Public modeDiscuss ChangeIntel on Discord

Advancing Windows security: Disabling NTLM by default

From 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, safely structured

Windows is moving toward a more secure authentication model by phasing out New Technology LAN Manager (NTLM) in favor of stronger, Kerberos‑based alternatives. This transition is taking a three-phased approach, leading toward disabling NTLM by default in upcoming Windows releases. With each phase come new capabilities so that your organization has the tools, visibility, and compatibility support needed.

When will this happen

  • NTLM has been deprecated since June 2024.
  • Today, enhanced auditing is available as part of Phase 1 toward NTLM disablement.
  • In the second half of 2026, new tools will be available to Windows Server 2025 and Windows 11, version 24H2 and later: IAKerb, Local KDC, upgrade to negotiate Kerberos.
  • With the next version of Windows Server and its corresponding client version, NTLM will be disabled by default. Additional support for handling NTLM-only cases will be built in.

How this will affect your organization

Disabling NTLM represents a major evolution in Windows authentication, and a critical step toward a passwordless, phishing resistant future. A phased strategy enables you to mitigate NTLM-related risks in a secure and predictable manner, without disrupting your organization.

What you need to do to prepare

If your organization is beginning or accelerating its NTLM reduction efforts, now is the right time to engage your identity, security, and application owners to take concrete steps:

  1. Deploy enhanced NTLM auditing to identify where NTLM is still used.
  2. Map dependencies across applications and services and prioritize remediation. This may include reaching out to application developers to update critical applications.
  3. Migrate and validate that critical workloads succeed with Kerberos. The capabilities that will be released in the second half of 2026 will significantly expand the scenarios where you can use Kerberos successfully.
  4. Begin testing NTLM-off configurations in non-production environments.
  5. Enable Kerberos upgrades as they become available through the Windows Insider Program, and then more broadly later this calendar year.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Learn more

Links from the notice and their documentation checks

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.
  • 3 linked pages have not been read yet.
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 14:23 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current