Data Agent offer different numbers in Fabric Data Agent vs same agent in Copilot 365

Hello, Jeanxyz. Unfortunately without additional information that shows examples of such behavior it's hard to suggest concrete fixes. But, most likely, you don't have precise instructions in your Fabric Data agent that limit possible answers. The issue is, most likely, that when you use Copilot 365 the question is interpreted by the Copilot 365 and then the Data Agent is accessed not via its UI but another way, through the published endpoint, that is programmatically. This is multi-agent scenario. Then, Copilot creates its own answer from the Data Agent response. You are dealing with a broken phone scenario. You need to customize and thoroughly test instructions in your Data Agent that make sure that programmatic access follows the same path of interpretation as the UI chat. I cannot give you exact instructions, but I hope you get an idea. The most reliable way is to have query examples in your Data Agents instructions associated with keywords or topics in the questions that the Data Agent receives.

If you share some samples of behavior it might be possible to think of specific ways to formulate the instructions.

Think of it this way: two data engineers receive the same vague request and each one creates their own version of a query. Occasionally they may give the same results, but most likely they will provide different results, unless both of them follow the same precise pattern of querying the data.

Hope this helps unblock your journey.