Skip to content
Filed underOutages

Exchange Online outage, 31 August 2026: an authentication fault

On 31 Aug 2026 Exchange Online was degraded for nearly 12 hours (EX1464935). Microsoft traced it to a core authentication configuration.

Written by
KDC
Published
Reading time
3 minutes

Key takeaways

  • Exchange Online was degraded across all connection methods on 31 August 2026 for nearly 12 hours.
  • Microsoft's preliminary cause was an issue in a core authentication configuration shared by several Microsoft 365 services.
  • The admin incident was EX1464935; search lagged behind the rest of the recovery.

At a glance

FieldDetail
ProviderMicrosoft 365 (Exchange Online)
Started31 August 2026, about 8:30 a.m. PT (15:30 UTC)
DurationNearly 12 hours, to about 8:30 p.m. PT
ServicesExchange Online, OneDrive, SharePoint, Teams, Purview, Defender XDR
StatusResolved
Official referenceEX1464935
Outage summary.

What happened

Downdetector reports began around 8:30 a.m. Pacific time and peaked at around 6,000. Microsoft's status account referenced incident EX1464935 and said Exchange Online was affected across all connection methods (Tom's Guide live blog).

OneDrive, SharePoint, Teams, Purview and Defender XDR were affected too, likely because Microsoft's root cause names an authentication configuration used by multiple Microsoft 365 services.

The cause

Microsoft's preliminary root cause was "an issue within a core authentication configuration used by multiple Microsoft 365 services". Engineers re-applied authentication components and restarted infrastructure to recover (Tom's Guide).

Secondary sources say a broader incident, MO1465074, was also opened. We have not seen that ID in a primary Microsoft source, so treat it with care.

Why authentication outages hit so wide

When the service that proves who you are fails, every app that relies on it fails at once. That is why a mail problem showed up in file sharing and security tools on the same afternoon. The same pattern appeared in July 2025, when Microsoft linked a long Outlook outage to an authentication component (The Register).

Recovery

  • Service was largely restored by about 8:30 p.m. PT, nearly 12 hours after reports began (Tom's Guide).
  • Tom's Guide reported that search lagged further behind, so recent messages could be missing from results for a while.

What admins can do

  • Subscribe to Service Health notifications in the Microsoft 365 admin center so incident IDs reach you first.
  • Keep break-glass admin accounts and a written plan for telling staff what is happening.
  • After recovery, rebuild search indexes only if results stay incomplete for more than a day.

Earlier Microsoft outages with a similar shape

This was the second long Exchange Online incident of 2026. On 22 January, incident MO1221364 hit Outlook, Exchange Online, Teams, SharePoint and OneDrive. Microsoft's status said "a portion of dependent service infrastructure in the North America region isn't processing traffic as expected", and the fix was reported around 10:30 p.m. PST, about 8 hours in total (TechRepublic, ENow).

A year earlier, from 22:20 UTC on 9 July 2025, users could not reach their mailboxes through any connection method. Microsoft pointed to mailbox infrastructure linked to an authentication component and then a configuration change, and service returned for most users by about 19:21 GMT on 10 July (The Register).

The common thread is shared infrastructure: when a component many services lean on falters, mail is only the most visible casualty.

FAQ

How long was Exchange Online down on 31 August 2026?

Nearly 12 hours, from about 8:30 a.m. to 8:30 p.m. Pacific time, according to Tom's Guide.

What caused it?

Microsoft's preliminary explanation was an issue within a core authentication configuration used by several Microsoft 365 services.

What was the incident ID?

EX1464935. A broader incident, MO1465074, is reported by secondary sources only.

Why was search slow afterwards?

Tom's Guide reported that search lagged behind the rest of the recovery. Microsoft did not give a separate reason.

Sources