Power Platform Community Forum Thread Details

Hi everyone,

I’m currently testing a Fabric Data Agent by connecting it as a Connected Agent inside Microsoft Copilot Studio . Everything works well for the first few minutes — the agent responds to all queries as expected.

However, we consistently experience the following issue:

The agent works normally for about 5 minutes

After ~5 minutes, the agent stops responding completely (no error, no timeout message — just no reply at all, aget says no data related to the question could be found, but 5 minutes ago it was answering the same questions.)

If we Disable → Enable the connection, or remove and re‑add the Fabric Data Agent, it starts working again — but again only for around 5 minutes

This behavior is reproducible every single time

So my questions are:

Is there any session timeout, connection timeout, or preview‑related limitation that would cause Fabric Data Agents to stop responding after a few minutes?

Is this a known issue in the Fabric Data Agent → Copilot Studio (Preview) integration?

Is there any recommended workaround or configuration on our tenant side?

We didn’t find any official documentation mentioning a 5‑minute timeout, so any insight would be greatly appreciated.

Thanks in advance!

Categories:

Autonomous agents

General topics

Hello,
It is not caused by configuration errors but is a known limitation or instability in the Fabric Data Agent and Copilot Studio Connected Agent preview integration. The agent typically works for a few minutes, then stops responding without errors and only resumes after reconnecting.

Known community workarounds include temporarily re-enabling the Fabric Data Agent connection to reset the MCP session, using the Fabric Data Agent directly instead of the Data Agent MCP Server connector (which shows higher reliability), ensuring both agents are published under the same account and tenant for stable authentication, and avoiding long idle periods to reduce potential session expiration issues.