Microsoft 365 Copilot Chat experienced a roughly 4-hour outage starting September 3, 2026, where user queries returned no response and displayed a "Something went wrong" error. The root cause was a spike in request traffic that overwhelmed the service infrastructure responsible for processing Copilot Chat responses. Users also reported broader M365 impact, including Intune failing to pull endpoint telemetry, policies not applying to new assets, ESP timeouts during app installs, and Graph API queries via PowerShell freezing.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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
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
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with