In this short demo, I tested how a Microsoft Fabric Data Agent can be used through Microsoft Teams and Microsoft 365. I also showed how prompt wording can affect an answer when querying Green Trip data.
Key Takeaways
- A Data Agent can be published for use in Microsoft 365.
- I accessed the published agent through Microsoft Teams.
- The sample agent used Green Trip data.
- An initial passenger question returned an answer I identified as incorrect.
- Refining the prompt produced the expected response in this scenario.
- Chat history remained available through the app.
Microsoft Fabric Data Agent publishing to Microsoft 365
I started with a Microsoft Fabric Data Agent that I had created earlier. When publishing it, I selected the option to publish it to Microsoft 365 as well.
After publishing, I could view the agent details, including its URL and MCP information. This makes the Data Agent available beyond its original Fabric context.
Next, I moved to Microsoft Teams. I could open the agent through the app, and I also showed an option to access it through the Microsoft 365 corporate area in Teams.
Opening the sample agent in Teams
The agent in my demo was named Sample Data Agent and was fed by Green Trip data. Once opened in Teams, I could ask questions directly in the chat interface.
This demonstrates a practical Microsoft Fabric Data Agent in Teams workflow: publish the agent, open it through the Microsoft 365-connected experience, and interact with the available data through chat.
Microsoft Fabric Data Agent prompt refinement in Teams
I first asked for the highest number of passengers. The agent returned 9 passengers, while also showing the Fabric MCP activity behind the response.
However, I knew that this result did not answer the question I intended to ask. The issue was the wording of my prompt, not a confirmed issue with the integration itself.
I then refined the question to ask: Which year has the highest total passenger count? The Data Agent MCP ran again in the background and returned the response I expected.
This quick test shows why prompt specificity matters. Asking about the “highest number of passengers” can produce a different result than asking for the year with the highest total passenger count.
What this demo did not test
This was a short, single-scenario demonstration. I did not test multiple data sources, alternative permissions, or a wider set of questions. The specific year and passenger total returned by the refined prompt were not stated in the demo.
Can Microsoft Fabric Data Agent chat history remain available?
Yes. In the app experience I showed, the chat history remained available. This allows me to revisit previous Data Agent conversations from the interface.
Frequently Asked Questions
Can I use a Microsoft Fabric Data Agent in Microsoft Teams?
In this demo, yes. I published the Data Agent to Microsoft 365 and opened it through Microsoft Teams.
Why did the first passenger question return an incorrect result?
I identified that the first question was not specific enough for the answer I wanted. After I changed the prompt to ask about the year with the highest total passenger count, the agent returned the expected response.
Conclusion
This Microsoft Fabric Data Agent demo showed a simple path from publishing to Microsoft 365 through asking questions in Teams. I also observed that clearer prompts can help the agent return a more relevant response for the intended question. If you use Data Agents with Microsoft 365, consider testing your prompts carefully and reviewing your chat history as you work.
Super User