Microsoft Exchange Online Outage Causes Email Failures, Auth Issues

The Exchange Online outage tracked as EX1464935 is a Microsoft 365 service incident causing authentication failures and email delivery problems across Exchange Online. Microsoft first acknowledged the issue at 5:30 PM UTC, after a spike in user reports on social media prompted its engineering teams to open an investigation, according to an admin center update reported by BleepingComputer.

Microsoft classified the incident as a critical service issue with noticeable user impact rather than a minor advisory. The company has not yet disclosed which regions are affected, but outage tracker Downdetector logged reports from tens of thousands of Exchange Online users struggling to receive email via Outlook or access the platform.

Microsoft listed four categories of symptoms tied to the EX1464935 incident in its admin center update. Reports point to a mix of delivery and sign-in failures rather than a single isolated bug, which may suggest an authentication-layer problem affecting multiple downstream Exchange functions, though Microsoft has not confirmed a specific root cause.

• Delays or failures when sending or receiving email messages.
• Authentication-related errors when accessing Exchange Online services.
• Difficulties accessing or performing actions within Exchange administration experiences.
• Intermittent failures affecting mailbox operations and message delivery workflows.

Microsoft said it has "isolated a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity," and is analyzing service telemetry to find the underlying cause and validate remediation options, per its own admin center statement.

The outage affects Exchange Online customers broadly rather than a single tier of subscription, based on the symptom list Microsoft published. Users could see delays sending or receiving email, authentication-related errors, and difficulties accessing or performing actions within Exchange administration experiences, along with intermittent failures affecting mailbox operations and message delivery workflows.

Because authentication is implicated, some users may also face sign-in errors when Exchange Online tries to validate their credentials, separate from any mail-flow delay. Microsoft has not published a regional breakdown, so it remains unclear whether the impact is concentrated in specific geographies or global.

Exchange Online is the backbone of business email for a large share of Microsoft 365 tenants, so authentication and mail-flow failures translate directly into missed communications, delayed approvals, and support tickets piling up for helpdesk teams. An outage classified as an incident by Microsoft signals it considers the impact severe enough to warrant dedicated engineering response rather than routine monitoring.

This incident follows a pattern of Exchange Online disruptions in 2026. Microsoft mitigated a widespread mail flow pipeline issue in June that affected customers across North America, Asia-Pacific, and Europe, according to BleepingComputer's reporting on Microsoft's own incident history.

In April 2026, Microsoft also resolved a separate outage that blocked mailbox access via Outlook on the web, Outlook desktop, and Exchange ActiveSync, plus a weeks-long issue affecting Outlook mobile and macOS mailbox access.

Microsoft has not confirmed a root cause or a fix timeline as of this writing; the company says it is still assessing the scope of impact and monitoring for additional affected scenarios. Admins should treat this as a developing story and expect further admin center updates under incident EX1464935 rather than a public postmortem until the issue is mitigated.

The Exchange Online incident (EX1464935) blocks core mail flow and sign-in for a large but unspecified share of customers, halting business email until Microsoft finds a fix.

Microsoft is investigating an active Exchange Online outage, tracked as EX1464935, causing email delivery failures and authentication errors since 5:30 PM UTC.