Official documentation checked October 14, 2026.
“Sorry, something went wrong” is a generic Copilot failure, not a diagnosis. Record the app, exact action, account, and error details, then distinguish a service problem from an account, file, client, or network condition. Preserve your work before restarting an app or retrying a request.
Why Copilot Shows the “Sorry, Something Went Wrong” Error
Requirements vary across organizational Copilot, eligible Copilot Chat, consumer Copilot, and individual app features. Microsoft’s requirements documentation lists account, entitlement, client, cookies, mailbox, and network conditions. A generic error alone does not identify a bad token or prove that a paid add-on must be purchased.
For a particular document or message, file format, source access, encryption, or processing policy can also matter. A problem limited to one source needs a different investigation from a failure across users and applications. Avoid assuming that a product-wide Copilot COM add-in or one Office cache folder controls every experience.
Steps to Fix the Copilot Error
- Preserve and record: save the document or draft and record the error time, client version, exact feature, and any displayed correlation ID. Keep secrets and personal information out of support screenshots.
- Confirm the account: verify the account shown in the affected service. For work content, use the organization’s intended account and entitlement. Follow license-validation guidance if the message specifically concerns a license.
- Isolate scope: try a small, permitted, non-sensitive example using the same feature. Compare the approved web and desktop experiences if both support it. Record the difference without treating it as proof of corruption.
- Check service health: for organizational use, ask the administrator to review Health > Service health in Microsoft 365. Follow Microsoft’s service-health instructions.
- Refresh a confirmed app entitlement problem: save work, use File > Account > Update License in a Windows Microsoft 365 app, then restart open apps. Mac has its documented Refresh License control. See the supported refresh procedure.
For a browser-only session problem, consider deleting only the affected site’s stored cookies after saving unsent work. In Edge, use Settings > Privacy, search, and services > Cookies > See all cookies and site data, search for that site, and remove its entry. Microsoft’s cookie guide explains the difference from clearing cookies for every site.
Related Copilot Errors and Their Fixes
Only Outlook fails: record whether the problem concerns drafting, a thread summary, or Chat. Use that feature’s support requirements; do not try to enable an assumed Copilot COM add-in.
Only Teams fails: compare the supported Teams web experience and current client. Give IT the exact client/version and symptoms. Do not delete the legacy Teams directory or OfficeFileCache as a general repair for all modern clients.
Connection errors across features: Microsoft provides a Copilot connectivity troubleshooter in Get Help. Review its findings with IT. The current requirements include Microsoft 365 endpoints and WSS support; a short list of old Copilot URLs is not a complete allowlist.
Have the network team investigate approved proxy, firewall, VPN, and connectivity settings. Keep required protection in place. Disabling a VPN or all extensions, resetting Office activation, or running a repair-install scenario without evidence can interrupt other work and does not establish the cause.
Copilot Account Contexts: Error Handling Differences
| Context | Verify | Escalation path |
|---|---|---|
| Organizational licensed capability | Account, required entitlement, feature and source conditions | Microsoft 365 administrator and product support |
| Organizational Copilot Chat | Eligible base subscription, account and permitted capabilities | Tenant and client support |
| Personal Copilot | Personal account and consumer service requirements | Account/service support |
Escalating an Unresolved Copilot Error
Provide the error text, time, client version, feature, scope of affected users, and results of the harmless comparison. Include a displayed correlation ID, but never token or cookie values. Report whether a known service advisory applies. This article checked official guidance, not your device or tenant, and does not support the previous claim that these steps resolve over 90 percent of errors.