Microsoft 365 suite outage history

In the early afternoon UTC, users in the United States experienced difficulties loading Microsoft 365 services, with 502 and 503 errors and authentication-related problems affecting sign-in flows. The disruption primarily impacted US users, and later expanded to some users in the United Kingdom. The issue appeared as an outage for portions of the service users rely on, with access interruptions reported across multiple Microsoft 365 components.

Microsoft 365 steadily updated its status page as engineers reviewed telemetry and investigated the root cause. Early guidance focused on 502/503 errors and Single Sign-On failures, with attention to upstream dependencies and authentication paths. Over the course of several hours, the investigation progressed as impact reports began to subside and telemetry remained stable, though a full root cause was still under assessment. The service largely returned to normal with impact reports decreasing and access restored by 6:28 PM UTC.

An outage hit Microsoft 365 across multiple services, disrupting core workflows for organizations worldwide. Users could not load or refresh files in OneDrive for Business and SharePoint Online; mail flow and attachments in Exchange Online and Outlook on the web were impacted; and Copilot prompts requiring Microsoft 365 grounding could fail. The impact was global, affecting a broad set of productivity tools used across teams and regions. Impact began around 6:39 PM UTC and continued for several days as remediation progressed.

Microsoft's status updates described remediation efforts, including refining a remediation strategy and re-applying core authentication components across affected infrastructure. By 6:29 PM UTC a substantial portion of services had recovered and availability rose toward normal levels, with continued work to restore remaining components. Full recovery was confirmed around 6:43 PM UTC, and the service was fully up by 8:09 PM UTC. The outage lasted roughly three days before full stabilization.

Impact began at Aug 17, 2026 1:03 PM UTC with a degraded search experience affecting SharePoint Online, OneDrive, Outlook on the web, and Outlook desktop. Users reported difficulty locating content, hindering file and email access for a portion of Microsoft 365 customers. The issue persisted as the service monitored telemetry and began broadening its scope to include regional impact.

Users in the North America region experienced degraded access to Microsoft 365 services, with intermittent connectivity and errors such as 'Something went wrong' across multiple apps. The incident began with an investigation announced at Jul 23, 2026 3:24 PM UTC as Microsoft 365 noted rising user reports and telemetry that suggested a potential issue.

Over the next hours, Microsoft 365 confirmed that the impact could affect multiple services, including OneDrive for Business, SharePoint Online, Microsoft Teams, the Microsoft 365 Admin Center, and Power Automate, with affected network paths identified as a focus area. The company pursued traffic rerouting and other mitigations to restore service.

In a later update, Microsoft indicated that a recent network configuration change may have contributed to the impact and began reverting the change while continuing traffic rerouting. The network revert was completed around 6:48 PM UTC and telemetry showed improving service; by 8:19 PM UTC the status returned to up as the North America region recovered. The incident appears to be regional, with affected users reporting intermittent access and errors predominantly in North America; no global outage was observed.

Impact began at 10:04 AM UTC when users were intermittently unable to access the Microsoft 365 suite portal, including Microsoft Copilot web and pages redirecting to the m365.cloud.microsoft URL. The issue manifested as timeouts with the error “Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long,” affecting authentication and access to the main portal and Copilot-related services. The incident was resolved by 6:53 PM UTC.

Users in Japan experienced brief issues accessing Microsoft 365 services, including Microsoft Teams. The incident appears to have started around 4:54 AM UTC and was resolved by 5:19 AM UTC. The Microsoft 365 status page indicated an investigation into the problem and then confirmed the service was restored, with a closure summary to follow. The impact was localized to Japan, affecting authentication and access to essential Microsoft 365 apps during the window.

Australian users of Microsoft 365 experienced brief access issues starting at 1:48 AM UTC due to a third-party networking problem that affected connectivity to Microsoft 365 services. The disruption appeared regional to Australia, with users unable to reach or use Microsoft 365 applications during the window flagged by the status page.

Microsoft 365 stated they had identified the third-party networking issue and were coordinating with the provider while attempting to reroute traffic to restore service. The service returned to normal around 1:59 AM UTC, ending a brief outage of roughly ten minutes, with the impact predominantly in Australia.

An outage affected a subset of infrastructure components impacting Microsoft Copilot in Microsoft 365 for users in Europe. Users may have experienced failures or timeouts when attempting to access Copilot. The incident began on Feb 13, 2026 2:34 PM UTC, and the provider initiated a remediation plan and restarted affected components to restore capacity. The issue was resolved by Feb 13, 2026 3:59 PM UTC. The provider issued 2 official updates during the incident, outlining the remediation steps and the gradual restoration of service capacity.

Some Microsoft 365 Admin Center users in the North America region were unable to access the service, with others reporting degraded functionality. The impact was focused on admin workflows within the North America region. The outage began at Feb 10, 2026 2:59 PM UTC and was resolved by Feb 10, 2026 5:24 PM UTC, lasting about 2 hours and 25 minutes. The incident was monitored via telemetry and the status page indicated ongoing investigation to isolate the root cause; the service posted two updates during the incident.

The outage began at Jan 22, 2026 7:44 PM UTC when Microsoft 365 flagged a potential issue affecting Defender and Purview portals and Outlook. Users across multiple regions reported admin portal access problems and issues with email delivery. The incident prompted ongoing investigation and status updates from Microsoft.

The event lasted about 10 hours and 50 minutes and was resolved by Jan 23, 2026 6:34 AM UTC. The provider issued 2 status updates during the incident. Reports from users in Boise, Caracas, Oxnard, and Quito indicate cross-regional impact on Defender, Purview, and Outlook components.