Before the narrative, here is the current status of the incident, based on data Microsoft has posted to its admin console and reported through the University of Pennsylvania’s IT department and Computerworld.
- Status: Resolving — the Microsoft 365 outage has entered its second day, with search still disrupted.
- Affected services: Exchange Online, SharePoint Online, OneDrive for Business, Teams, and Microsoft 365 Copilot.
- Started: August 31 at 11:55 a.m. UTC, with the broader multi-service incident officially logged at 3:08 p.m. UTC.
- Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services.
- Mail flow: Largely recovered; search and several other functions remain degraded.
Microsoft 365 outage enters its second day
Microsoft is still working to clear a widespread disruption that has now stretched across two days. Much of the Exchange Online mail flow has come back, but search and a range of other functions across Exchange Online, SharePoint, OneDrive, Teams, and Microsoft 365 Copilot remain affected, according to the company’s incident page.
Notably, Microsoft has stopped short of calling this a complete outage. Instead, it has tracked a spread of degraded or fully failed functions across multiple services, which is a distinction IT teams will want to keep in mind when assessing impact on their own environments.
How the incident unfolded
The timeline, as reconstructed from Microsoft’s admin console data, begins at 11:55 a.m. UTC on August 31, when the company started investigating a rise in user reports of Exchange Online problems. By 12:33 p.m. UTC, Microsoft said it had isolated a common failure pattern across affected Exchange Online requests tied to authentication and protocol connectivity.
About an hour later, a potential corrective action was identified, though the company was still evaluating how to deploy it. Then, roughly an hour after that, Microsoft reported the problem had spread beyond Exchange Online to other Microsoft 365 services.
At 3:08 p.m. UTC, the company logged the official start time of the broader incident and soon pointed to the root cause: an issue within a core authentication configuration used by multiple Microsoft 365 services.
A fix that required reverting infrastructure
Microsoft’s response over the following hours was cautious. At 4:36 p.m. UTC, the company said it was re-examining recent changes and exploring ways to safely restore the affected components, including potentially reverting an update that had been pushed to the affected infrastructure. That language suggests the incident was likely triggered by a change that did not behave as expected when rolled out.
By 5:55 p.m. UTC, mitigation testing had produced positive results, and Microsoft was continuing to test strategies for applying the necessary authentication component. At 6:40 p.m. UTC, it began implementing a targeted mitigation, reapplying core authentication components across a sample of affected infrastructure while reporting that some users were starting to see recovery in certain scenarios.
The company then expanded the mitigation and began restarting targeted sections of infrastructure, signaling a shift from diagnosis to controlled restoration.
What’s broken and what’s back
The list of impaired functions paints a picture of how deeply the authentication issue cut across the productivity suite. Microsoft listed degraded or failed features including Exchange Online connectivity and search, SharePoint Online and OneDrive for Business search, file access, synchronization, and content loading, plus Teams search, calendars, and presence.
Even Microsoft 365 Copilot was caught up in the disruption, with prompts that require Microsoft 365 data failing to function. That is a telltale sign of the root cause: anything that reaches into your stored files, mail, or contacts to answer a query would break when the underlying authentication layer faltered.
Search recovery remains uncertain
The recovery was not uniform across all enterprise customers. By late Monday, Microsoft was reporting widespread recovery of Exchange Online mail connectivity, but it warned that some organizations could take longer to drain backlogged mail queues that had built up during the outage.
The company later validated persistent recovery of mail flow across the environment and shifted its focus to restoring search. But that partial recovery did not close the incident. Microsoft continued working on search-related issues into Tuesday, restarting affected infrastructure and reapplying the authentication-component fix across more environments.
In its latest update at 2:39 a.m. UTC, Microsoft said those efforts had “yielded progress,” with incremental improvement in service-health telemetry for search across a sample of the affected environment. It has not provided an estimated time for full resolution and said it would share a recovery timeline only when one becomes available.
What this means for you
For everyday users, the practical impact is uneven. If your mail is arriving and sending again, the worst may be over — but you may still find that searching for old messages, files, or contacts returns nothing or times out. Calendar and presence indicators in Teams can also be unreliable, which affects scheduling and knowing whether a colleague is available.
For teams that lean on Microsoft 365 Copilot to summarize documents or pull data from your files, expect those features to keep failing until the search layer is fully restored. Enterprises should also plan for delayed workloads: backlogged mail queues can take hours to clear, and employees may be without access to critical information and tools until services are completely healthy.
What to do while services recover
There is no quick fix on the user side, since this is an infrastructure-level problem Microsoft must resolve on its end. The most useful steps are to monitor the official status page at status.cloud.microsoft for updates, avoid repeatedly retrying searches in a way that adds load, and flag lingering issues to your IT team if they persist after Microsoft declares the incident resolved.
If you are an admin managing a fleet, give backlogged mail queues time to drain and check with your monitoring tools before assuming mail flow is fully healthy. Microsoft has said it will provide a recovery timeline when one is available, so the duration of this disruption remains uncertain as it moves into its second day.
Source: Computerworld
Over to you: Is your mail back but search still broken, or are you still waiting for everything to recover?
