Microsoft 365 suite Outage History

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.

Microsoft 365 experienced a brief issue starting at 4:58 PM UTC with Teams and Outlook impacted. The Microsoft 365 status page noted an investigation into a potential issue and monitoring for impact to organizations. The incident caused degraded performance for a subset of users and lasted about 1 hour and 30 minutes, with service restored by 6:28 PM UTC. A small number of user reports were observed during the window, including a sample from Petaluma, California at 5:43 PM UTC. The provider issued updates during the incident and the service returned to normal.

Microsoft 365 and Microsoft Copilot experienced sign-in and access issues in the Japan region. The outage began at 1:18 AM UTC and lasted about 2 hours and 15 minutes, with users in Japan unable to sign in or access core Microsoft 365 services. The impact appeared limited to the Japan region. The status page indicated engineers were actively reviewing telemetry to identify the underlying cause and determine mitigation actions. The provider posted two updates during the incident and restored services by 3:33 AM UTC, with no indication of a broader global impact.

Microsoft 365 experienced a regional access issue in the Japan region, with users unable to access Microsoft 365 services. The outage began at 12:54 AM UTC and was resolved by 1:43 AM UTC, lasting about 49 minutes. The incident was noted as a degraded state affecting Japan users, with third-party networking service(s) suspected as contributing factors, and an update was promised within 30 minutes. The provider issued two status updates during the incident.

An outage affected Australian users attempting to use Microsoft 365 and Microsoft Teams. The issue began at Dec 10, 2025 3:43 AM UTC and was resolved by Dec 10, 2025 5:54 AM UTC, lasting about 2 hours. User reports started around 2:45 AM UTC, indicating issues were observed locally before the official acknowledgment. The impact was geographically limited to Australia, with some users unable to access core services during the incident. The outage affected two key components: Microsoft Teams and Microsoft 365 services.

Australian users experienced a brief disruption accessing Microsoft 365 services, including Microsoft Teams. The outage lasted about 15 minutes, beginning at Dec 8, 2025 12:28 AM UTC and ending at Dec 8, 2025 12:43 AM UTC. The issue was acknowledged on the Microsoft 365 status page, which noted that users in Australia may have experienced difficulties and that the problem was being investigated.

Microsoft 365 experienced a potential service issue beginning at Oct 29, 2025 4:13 PM UTC, after the status page moved to warning and noted investigators were assessing potential impact to organizations. User reports started around 4:15 PM UTC describing login problems and other service effects from multiple regions, including Istanbul, Ashburn, Davao City, and Duvall. The incident prompted an ongoing investigation with an update expected within about 30 minutes.

The outage lasted approximately 12 hours and 40 minutes and was resolved when the status page returned to up at Oct 30, 2025 4:53 AM UTC. Microsoft 365 posted two official updates during the incident. Reported symptoms centered on login access to Microsoft 365 services such as Outlook, indicating degraded performance across affected services.

Microsoft 365 experienced a regional outage in Japan beginning Oct 27, 2025 12:23 AM UTC, with the status page showing a degraded performance state. The issue affected multiple services within Microsoft 365, including Microsoft Teams, Microsoft Outlook, and Microsoft 365 Copilot, causing degraded performance and intermittent access for users in the Japan region. The outage lasted approximately 2 hours and 30 minutes, with the service returning to normal by Oct 27, 2025 2:53 AM UTC. The incident involved two official status updates from Microsoft 365 during the degraded period.