Copilot Studio Agent in Teams Returns Cached Data Instead of Latest Fabric Results

Question

Copilot Studio Agent in Teams Returns Cached Data Instead of Latest Fabric Results

Tushar Sakhuja 5

I’m using a Copilot Studio agent connected to a Fabric Data Agent. The agent works correctly in the Copilot Studio test canvas and always retrieves the latest data, but when I use the same agent in Microsoft Teams, it returns outdated responses. If a user asks the same question on different days, Teams keeps giving the original answer instead of querying Fabric again, even though the underlying dataset refreshes daily. Clearing the Teams chat forces the agent to fetch fresh data, which suggests Teams is caching previous responses or reusing conversation context. How can I ensure that my Copilot Agent always performs a new, real-time query to the Fabric Data Agent in Teams and does not rely on cached or historical responses?

1 answer

Your answer

Answer 1

Sayali-MSFT 4,431 Microsoft External Staff Moderator

Hello Tushar Sakhuja - Thank you for bringing this issue to our attention.
The issue occurs because Teams retains conversation context and may reuse previous answers instead of calling the Fabric Data Agent again. To ensure real-time queries:

Add the Fabric Data Agent as a connected agent and configure topics to invoke it explicitly for analytics questions.
Write clear instructions in the agent description: always call Fabric for data queries, never reuse old answers.
Confirm the Fabric Data Agent is published and accessible in your tenant.
Avoid fallback responses from the parent agent for analytics intents.
Operational workaround: start a new chat in Teams to reset context

References:
https://dori-uw-1.kuma-moon.com/en-us/fabric/data-science/data-agent-microsoft-copilot-studio
https://dori-uw-1.kuma-moon.com/en-us/microsoft-copilot-studio/add-agent-fabric-data-agent

Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2025-12-11T06:35:37.4766667+00:00

Hello Tushar Sakhuja - Could you please confirm if your issue resolved with above information or are you still looking for additional information?
Tushar Sakhuja 5 Reputation points

2025-12-12T05:28:38.39+00:00

Thanks for the suggestions. I’ve already implemented everything that is currently available on my side, the Fabric Data Agent is connected and published, the instructions clearly tell the agent to always use Fabric for analytics, and fallback behavior is controlled.

The issue is that I don’t see any option in Copilot Studio to directly “call” the Fabric Data Agent from inside a topic. That action simply doesn’t appear for me, so I’m unable to force real-time invocation through topics even if I want to.

Also, asking users to start a new chat in Teams every time to reset the conversation context isn’t practical or feasible in a real-world scenario.

Given these limitations, is there any other recommended approach to ensure that Teams doesn’t reuse old responses and that the Fabric Data Agent is invoked reliably for fresh analytics queries?

Share via

Copilot Studio Agent in Teams Returns Cached Data Instead of Latest Fabric Results

1 answer

Your answer