Service issues › CW1466621

Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error

Resolved Microsoft 365 Copilot Chat General incident
Started
03 Sep 2026 06:30 UTC
Resolved
03 Sep 2026 19:45 UTC
Status
serviceRestored
Origin
microsoft

Timeline & resolution

03 Sep 2026 20:58 UTC · regular

Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error User impact: Users' queries to Copilot Chat may have returned no response, and users received an error. More info: When users attempted to query Copilot Chat, some of their queries may have returned no response and instead, users may have received an error that stated, "Something went wrong." Final status: We've applied configuration changes to rebalance the request traffic and confirmed using our service health telemetry that the impact is remediated. Scope of impact: Any user that attempted to query Copilot Chat may have been impacted. Start time: Thursday, September 3, 2026, at 6:30 AM UTC End time: Thursday, September 3, 2026, at 7:45 PM UTC Root cause: An increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses prevented the service from being able to efficiently process requests. Next steps: - We're continuing to investigate the source of the increased request traffic, so that we can determine how to prevent similar impact to users' Copilot Chat queries in the future. This is the final update for the event.

03 Sep 2026 18:42 UTC · regular

Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error User impact: Users' queries to Copilot Chat may return no response, and users receive an error. More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong." Current status: We've identified an increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses which is preventing the service from being able to efficiently process requests. We're evaluating our mitigation options to identify the most effective method to remediate the impact. Scope of impact: Any user attempting to query Copilot Chat may be impacted. Start time: Thursday, September 3, 2026, at 6:30 AM UTC Root cause: An increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses which is preventing the service from being able to efficiently process requests. Next update by: Thursday, September 3, 2026, at 9:00 PM UTC

03 Sep 2026 17:27 UTC · regular

Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error User impact: Users' queries to Copilot Chat may return no response, and users receive an error. More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong." Current status: Our service health monitoring alerted us to an increase in failures occurring when users attempt to query Copilot Chat. We're reviewing our service health telemetry to isolate the source of the failures, so that we can developed a mitigation plan. Scope of impact: Any user attempting to query Copilot Chat may be impacted. Next update by: Thursday, September 3, 2026, at 6:30 PM UTC

03 Sep 2026 17:16 UTC · regular

Title: We're looking into a potential problem impacting Microsoft 365 Copilot Chat User impact: We're checking for potential impact to your users. Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.

© Microsoft — archived from Microsoft 365 service health. Content notice