Microsoft 365 Consumer Outage History

A routing issue in Microsoft 365 Consumer caused Copilot traffic to be directed to unhealthy infrastructure, resulting in users being unable to access the Microsoft Copilot desktop or web app due to access and timeout errors. The incident lasted 2.5 hours and was resolved by rerouting requests to healthy infrastructure, with service health recovery confirmed through telemetry monitoring.

Microsoft 365 Consumer experienced a major outage affecting Microsoft Copilot for 3.2 hours, preventing users from accessing the service. The issue was caused by high utilization on the underlying infrastructure supporting Copilot's LLM APIs. Microsoft resolved the incident by applying mitigations to the infrastructure and adjusting routing paths, throttling rules, and retry logic at the service level.

Microsoft Copilot experienced access failures for some users, with affected users receiving 401-error response codes when attempting to use the service. The incident lasted 32 minutes and has been resolved.

Microsoft 365 Copilot experienced a potential service issue that lasted 24 minutes. Microsoft investigated the problem and checked for impact to user organizations. The incident was classified as major status but was resolved within the initial investigation timeframe.

Microsoft 365 Copilot users were unable to select "Allow editing" when using Copilot through Word or Excel, forcing them to only use "Chat mode" for queries. The issue was caused by a recent update that incorrectly marked "Allow editing" and other agent mode functionalities as unavailable to non-premium users. Microsoft deployed a code fix that reached 90% completion during the 7.8-hour incident.

Microsoft 365 Copilot Chat experienced a potential service issue that lasted 4 minutes. Microsoft investigated the incident and checked for impact to user organizations. The issue was resolved quickly with the service returning to normal operation.

Microsoft Teams Free experienced a major outage lasting 529.9 hours where new users who signed up during the impact window were unable to search for, chat with, or call other users due to a backend change that caused them to bypass required onboarding steps, leaving their profiles incomplete and appearing as "Unknown users" to others. Microsoft deployed a fix after extensive validation and gradually rolled it out to affected users, with monitoring ongoing to ensure full resolution across the environment.

Microsoft 365 Consumer users experienced intermittent issues signing in to Outlook.com. The incident was related to a persistent issue from a previous case (OL1292958) that continued to affect user access. Microsoft resumed their investigation, analyzing service telemetry to determine the scope and next steps for resolution.

Microsoft 365 Consumer users experienced intermittent sign-in failures to Outlook.com for 28.5 hours, with users reporting "too many requests" errors and unexpected sign-outs, particularly affecting iOS users accessing Outlook and Hotmail through the default Mail app. Microsoft resolved the issue by rolling back a backend configuration change that was causing authentication key failures. iOS users were required to manually re-enter their passwords through iPhone Settings > Mail > Accounts to restore access after the service was fixed.

Microsoft Copilot for personal use experienced intermittent service issues for 1.5 hours due to decreased performance on supporting infrastructure. Users encountered error messages including "Having trouble with requests" and "I'm sorry, I'm having trouble responding to requests right now." Microsoft investigated recent changes that may have contributed to the performance degradation and resolved the issue.