Copilot Agents Not Working – SystemError

(0) Share

Report

Posted on by AudreyAmstuz

Hi everyone,

I’m currently experiencing an issue with Microsoft Copilot custom agents and I’d like to know if others are facing the same problem.

Since yesterday (May 18, 2026), all my agents stopped working completely:

- Even a very simple test agent (basic prompt) returns: “Something went wrong” / SystemError

- Creating a new agent does not fix the issue

- The problem is consistent across sessions and browsers

Additionally:

- The Copilot chat itself works fine

- But the Agents environment seems broken

This suggests the issue is not related to prompt configuration or data, but rather a backend or service problem.

Important: everything was working correctly earlier the same day.

Has anyone experienced similar issues with Copilot Agents recently?

Is there any known incident or workaround?

Thanks in advance for your help.

Categories:

Copilot Studio pre-built agents/templates

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Romain The Low-Code... 2,731 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello,

Most of the time, it's related to a strategy environnement (DLP) change by one of you'r IT admin wich appli a global DLP (often removing Web, SharePoint, or teams as a channel, removed credits).

Could also be a problem with the tool inside the agent, when you have a problem with a tool, it work sometime in studio but crash in teams.

Solution to test :
if you can create a new environnement : test with it.

Test an agent with only one of the folowing each time to know what's going wrong and push to teams :

- general knowledge

- web grounding

- sharepoint knwoldege

- a basic tool like send email

- an agent flow

- a power automate

If everything is broken , even the first one with general knowledge -> ask you'r admin if they change something and then ask to open an official ticket from you M365 tenant.

I hope it help you to solve the problem :) if yes please check the answer as the good one, mark it verified it's important for the community and search engine :)

Was this reply helpful? Yes No
AudreyAmstuz 2 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Thanks for your answer.

I tested with a completely minimal setup:

- brand new agent

- only general knowledge (no tools, no SharePoint, no web grounding)

The issue still occurs.

Has anyone else experienced the same recently?

Thanks!

Was this reply helpful? Yes No
Romain The Low-Code... 2,731 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

it happen on all environnement ? best to try on a new one. if issue is still on a new one, sadlye need to open an official MS ticket from your tenant :(

Was this reply helpful? Yes No
Nivedipa-MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hello AudreyAmstuz,
This looks like a service-side incident, not a configuration issue on your end — the symptoms match a Copilot agents runtime outage (chat still works, but agents return SystemError across all agents, including a fresh one, in multiple browsers and sessions).

Next steps:

Check Microsoft 365 Service Health in the admin center (admin.microsoft.com → Health → Service health) — filter on Microsoft 365 Copilot. Active incidents show up as MO/CP-prefixed advisories.

Check the Copilot Status page: https://portal.office.com/servicestatus

If nothing is posted, open a Microsoft 365 support ticket from the admin center and include: tenant id, agent id, a correlation/conversation id from the failing response (DevTools → Network → failed request → response headers x-ms-correlation-id / client-request-id), timestamp (UTC), and a screenshot of the SystemError. That helps route it to the Copilot Agents PG faster.

Workaround: none on the client side — agents runtime failures clear only after the service is restored. Avoid republishing in a loop; once the backend recovers, that can leave the agent in a half-updated state.

Was this reply helpful? Yes No