Microsoft 365 (Consumer) Incident History

1. Service degradationSep 7 · 14:08 UTC

   User impact: Users may experience intermittent failures when searching in Exchange Online and OneDrive. Current status: We're proceeding to see recovery progress for Microsoft OneDrive and evaluating whether any additional actions are needed to fully remediate impact. Start time: Saturday, September 5, 2026, at 4:00 PM UTC Next update by: Monday, September 7, 2026, at 7:30 PM UTC

Reported by Microsoft 365 (Consumer) on their status page.

1. Resolved — Service restoredSep 3 · 13:45 UTC

   User impact: Users may have encountered failures when accessing Microsoft Copilot chat. More info: Affected users when attempting to access Microsoft Copilot chat, may have encountered an error message stating, "Sorry, something went wrong." Final status: We've identified a configuration change that caused a section of Copilot requests from users to be routed incorrectly, resulting in impact. We've reverted the configuration change and monitored the service health telemetry to ensure full recovery. Following validation, we've confirmed that requests are now being routed correctly and issue has been mitigated. Start time: Thursday, September 3, 2026, at 6:57 AM UTC End time: Thursday, September 3, 2026, at 12:00 PM UTC This is the final update for the event.

Reported by Microsoft 365 (Consumer) on their status page.

1. Resolved — Service restoredSep 3 · 12:30 UTC

   User impact: Users may have seen failures when accessing Microsoft Copilot chat. More info: Affected users when attempting to access Microsoft Copilot chat, may have encountered an error message stating, "Sorry, something went wrong." Final status: We've identified a configuration change that caused a section of Copilot requests from users to be routed incorrectly, resulting in impact. We've reverted the configuration change and monitored the service health telemetry to ensure full recovery. Following validation, we've confirmed that requests are now being routed correctly and issue has been mitigated. Start time: Thursday, September 3, 2026, at 6:57 AM UTC End time: Thursday, September 3, 2026, at 12:00 PM UTC This is the final update for the event.

Reported by Microsoft 365 (Consumer) on their status page.

1. Service degradationSep 3 · 12:12 UTC

   User impact: Users may see failures when accessing Microsoft Copilot chat. More info: Affected users when attempting to access Microsoft Copilot chat, may encounter an error message stating, "Sorry, something went wrong." Current status: We've observed that the affected users are being incorrectly classified as test users, causing chat requests to fail. We're working to determine what change introduced this behavior and to identify the most effective mitigation approach to restore normal service. Next update by: Thursday, September 3, 2026, at 12:30 PM UTC

Reported by Microsoft 365 (Consumer) on their status page.

1. Service degradationSep 3 · 08:41 UTC

   User impact: Users may see failures when accessing Microsoft Copilot chat. More info: Affected users when attempting to access Microsoft Copilot chat, may encounter an error message stating, "Sorry, something went wrong." Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix. Next update by: Thursday, September 3, 2026, at 10:30 AM UTC

Reported by Microsoft 365 (Consumer) on their status page.