Share via

Copilot stopped working

Subhash M S 0 Reputation points
2026-06-15T04:27:18.44+00:00

Whenever a query is asked it provides the answer and within a fraction of a second it stops and says something went wrong

Microsoft Copilot | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. Demi-N 18,220 Reputation points Microsoft External Staff Moderator
    2026-06-15T09:20:06.9966667+00:00

    Hello @Subhash M S,

    Thank you for sharing the details of your issue. 

    I’ve reviewed the situation, and I want to assure you that this problem is not caused by anything on your side. It has been identified as a service incident by Microsoft and is currently being addressed.  

    Here is the official information:  

    ================================ 

    Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message

    Summary of Impact: Users of Microsoft 365 Copilot Chat are unable to submit prompts. When they attempt to do so, the service fails and returns a generic “Something went wrong.” error message, preventing normal use of Copilot Chat functionality. The issue is currently under active investigation and has not yet been resolved.

    Impact Time: Start: Monday, June 15, 2026, at 06:12 UTC. End: Ongoing (incident not yet resolved as of the latest update).

    Scope of Impact: The incident impacts Microsoft 365 Copilot Chat. Affected users cannot successfully submit prompts and instead receive an error message. Current indications suggest that less than 50 percent of users are affected, although the exact scope is still being validated.

    Action Taken: Engineering teams are investigating using customer case data, HAR files, client-side logs, and service telemetry. They are also trying to reproduce the issue internally and reviewing recent service changes that might be related. Updates are being shared regularly as the investigation continues.

    Contributing Factors: The root cause has not yet been confirmed. The team is still analyzing logs, telemetry, and recent changes to determine what’s triggering this behavior.

    Next Steps: The investigation is ongoing, with continued analysis of logs and telemetry, internal testing, and correlation with recent updates. Further updates are expected as progress is made.

    ================================ 

    Regarding this issue, since it appears to be related to a broader service incident, you may also consider reaching out to your IT administrator. They will be able to check the latest updates via the Service Health dashboard and, if needed, report the issue directly to Microsoft for further investigation on the backend.

    In addition, you may also consider submitting feedback directly within the application. This helps the product team better understand the impact from the user perspective and prioritize improvements. You can usually do this by selecting the feedback option (as shown in the screenshot) and choosing “Report a problem”.

    User's image

    This can help increase visibility of the issue and ensure it is properly captured by the engineering team.

    I’m really sorry for the inconvenience this has caused, please rest assured that Microsoft engineers are working diligently to resolve this issue as quickly as possible. I appreciate your patience and please feel free to update me if there are any changes or if you need further help.

    Warm regards,  


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.