Microsoft has resolved problems with Outlook authentication and email flow on Exchange Server deployments that arose following the installation of October 2026 Windows Server security patches. The company had previously disclosed this issue in mid-October, noting that users experienced login failures and email access problems after applying the latest updates to systems with Windows Server 2019 or newer versions.
The root cause stemmed from a new default constraint on memory allocation for Endpoint Mapper when processing Endpoint Lookup operations, which was introduced in the October 2026 updates. Microsoft stated at the time: "After installing the October 2026 Windows security update [..], some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication."

The impact was not uniform across all Exchange deployments. Microsoft noted: "Not all Exchange servers will be impacted by installation of those updates equally; the severity and speed of impact varies based on Exchange server load. Some servers might never see a problem." The company clarified that this OWA known issue was separate from the October 2026 Exchange server security updates themselves and advised against removing those patches.
November Updates Deliver the Fix
Microsoft announced via the Windows release health dashboard that the November 2026 Patch Tuesday updates (KB5131080 and KB5131090) resolve the known issue. The company recommended deploying these cumulative updates across all affected systems.
For organizations unable to immediately roll out the latest patches, Microsoft provided a temporary solution involving a registry modification on affected Exchange Server systems. IT administrators can execute the following command from an elevated Command Prompt to expand the maximum number of Endpoint Lookup calls and increase the memory available to Endpoint Mapper, followed by a system restart:
reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f
After the device reboots, administrators should observe the Exchange environment closely and consider raising the Endpoint Mapper memory limit further if the problem reoccurs.