Service issues › CW1517097
Some users may not receive responses from Microsoft 365 Copilot Chat in the web and desktop apps
- Started
- 20 Oct 2026 14:29 UTC
- Resolved
- 20 Oct 2026 16:01 UTC
- Status
- serviceRestored
- Origin
- microsoft
Timeline & resolution
20 Oct 2026 16:12 UTC · regular
Title: Some users may not receive responses from Microsoft 365 Copilot Chat in the web and desktop apps
User impact: Users may not have received responses from Copilot Chat in the web and desktop apps.
More info: Some affected users may have seen an error message such as "Oops! Something happened. Can you try again?" or experienced prompts that remained in progress without completing.
Final status: While we were in the process of analyzing information provided by affected users and service monitoring telemetry, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users attempting to use Copilot Chat on the web or desktop apps may have been impacted.
Start time: Tuesday, October 20, 2026, at 12:58 PM UTC
End time: Tuesday, October 20, 2026, at 3:10 PM UTC
This is the final update for the event.
20 Oct 2026 14:30 UTC · regular
Title: Some users may be unable to receive responses from Microsoft 365 Copilot Chat in the web and desktop apps
User impact: Users may be unable to receive responses from Copilot Chat on the web and desktop apps.
More info: Some affected users may see an error message such as "Oops! Something happened. Can you try again?" or experience prompts that remain in progress without completing.
Current status: We're reviewing information provided by affected users and service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Some users attempting to use Copilot Chat on the web or desktop apps may be impacted.
Next update by: Tuesday, October 20, 2026, at 5:30 PM UTC
© Microsoft — archived from Microsoft 365 service health. Content notice