Microsoft Outlook appeared to suffer an email service disruption on August 31, according to Tom's Guide, which tracked reports of mailbox and sending problems through the morning Pacific time. Tom's Guide reports that user complaints began appearing on Downdetector around 8:30 a.m. Pacific, then peaked around 9:30 a.m. at roughly 6,000 reports. As of the outlet's posting, the outage tracker still showed more than 5,000 reports and no clear decline. The reported user impact was concentrated in core email workflows: accessing mailboxes, delayed sending, and messages failing to send, according to Tom's Guide. The outlet framed the event as an Outlook outage, while Microsoft's own acknowledgement referred more broadly to degraded functionality across various Exchange Online functions. The official Microsoft 365 Status account on X acknowledged the issue, Tom's Guide reports. Microsoft said users may experience degraded Exchange Online functionality, and that it was reviewing service telemetry and diagnostic data to isolate the source. The company directed administrators to incident EX1464935 in the Microsoft 365 admin center. One wrinkle: Tom's Guide said the Microsoft 365 status page showed every Microsoft product as operational at the time it checked, even though the Microsoft 365 Status X account had acknowledged the Exchange Online degradation. That makes this a developing service incident rather than a cleanly documented outage from every Microsoft status channel. For operators, the practical point is that Microsoft's admin-center incident record appears to be the more relevant place to watch than the public product-status page, at least based on Tom's Guide's report. Until Microsoft posts a resolution or cause, the scope and duration remain unclear. Who benefits: Alternative communication channels inside affected companies benefit in the short term, including chat, ticketing, and phone-based escalation workflows. Who's exposed: Organizations that rely heavily on Outlook and Exchange Online for time-sensitive communication are exposed while the incident is unresolved. Admin teams also face uncertainty if public status pages and incident-channel updates do not show the same picture.