data agent
30 TopicsFabric Data Agent published to M365 has lost conversational context since yesterday
Hello, I’m experiencing a strange issue with a Fabric Data Agent that has been published to Microsoft 365. The agent continues to work correctly when accessed directly from Fabric. However, when using the same agent through Microsoft 365, it appears to have lost its ability to maintain conversational context and follow-up questions. Up until Friday, everything was working as expected, and I have not made any changes to the agent configuration, semantic model, capacity, permissions, or data sources. Example: User: Give me the payments for July. Agent: (Returns the correct results.) User: Give me the payments for June as well. Agent: "What would you like me to provide?" Previously, the agent correctly understood that the follow-up question referred to payments and would return the requested information. Now it seems unable to retain context between messages. The issue only occurs in the Microsoft 365 published version of the agent. The same agent continues to behave correctly inside Fabric. Has anyone else noticed a similar degradation in conversational context retention or follow-up question handling during the last couple of days? Any feedback would be appreciated. Thank you.Solved301Views0likes5CommentsData Quality
Hi everyone, One challenge I keep thinking about is maintaining high data quality across enterprise data platforms. For those working with Microsoft Fabric: How do you validate incoming data? Do you automate quality checks within pipelines? Which tools or techniques have proven most effective? How do you handle unexpected schema changes or invalid records? I'm interested in learning about practical strategies that have worked well in production environments. Thank you!Solved211Views0likes5CommentsService Principal authentication works with Lakehouse Data Agent but fails with Semantic Model
Hello, I am currently experimenting with Data Agents in Microsoft Fabric and I created two different agents: One connected to a Semantic Model One connected to a Lakehouse My goal is to programmatically interact with these agents from a Python application in order to display the chatbot interface inside my own application. According to the official documentation (Consume Fabric data agent from external applications with Python client SDK - Microsoft Fabric | Microsoft Learn), the recommended authentication method is to use InteractiveBrowserCredential, where the user signs in with their Microsoft credentials and then interacts with the Data Agent. However, for my use case, I replaced this authentication method with a Service Principal using ClientSecretCredential, since the application needs to run without interactive user login. Here is what I observed: When the Data Agent is connected to a Lakehouse, everything works correctly using the Service Principal. When the Data Agent is connected to a Semantic Model, the authentication works but queries against the data fail. Specifically: The agent responds correctly to general prompts such as greetings ("hello", "goodbye"). But when the question requires accessing the underlying Semantic Model, the agent returns an error similar to "unable to connect to the data source". From the documentation, I noticed that Service Principals are currently not supported, which might explain the behavior. However, since the same authentication method works with Lakehouse-based agents, I wanted to confirm whether this limitation is expected. My questions are: Is it expected that Service Principal authentication works with Lakehouse agents but not with Semantic Model agents? Are there any recommended workarounds for non-interactive authentication when using Semantic Model Data Agents? Is there a timeline or roadmap for supporting Service Principal authentication with Semantic Models in Fabric Data Agents? Thank you very much for your help.Solved3.4KViews1like4CommentsShare Fabric Data Agent
Hi, I’m trying to share a Fabric Data Agent connected only to a Lakehouse (no semantic model). I gave: Read + Execute permissions on the Lakehouse access to the Data Agent itself According to the documentation, workspace access should not be required. However, when the target user asks a question to the agent, the agent says it cannot answer and returns this message: “I could not access the data needed to answer your question because there is a database permission issue related to access to the customer table. This means I cannot retrieve the information about the customer with the highest consumption.” And when opening the Data Agent, I get this error: "PowerBINotAuthorizedException Error retrieving workspace network security settings" Why is the Data Agent trying to access Power BI workspace security settings if it is only connected to a Lakehouse? Is there an additional permission required that is not documented? Thanks.Solved2.2KViews0likes5CommentsFabric Data Agent Limitations of 25 items
There's no way for Fabric Data Agent to give more than 25 items of a list. And this is quite confusing. I have a dataset with the States and Presidents of USA. It is full with 50 states and 47 presidents. As you can see here, when asking for the list, it only contains the 25 first. When looking at the DAX query, it gives the 50 in result. // List all U.S. states with their abbreviations, sorted by state name. EVALUATE SELECTCOLUMNS( // Use SUMMARIZE to ensure distinct state rows if duplicates exist SUMMARIZE( 'america_states', 'america_states'[nom], 'america_states'[abréviation] ), "State Name", 'america_states'[nom], "Abbreviation", 'america_states'[abréviation] ) ORDER BY [State Name] ASC No TOPN here, or any filter/limitation. When asked, Agent says there are 50 lines in the table (good answer), but says that the "tool" gives only 25. Obviously, the "tool" is not DAX because it is correct. It's another mysterious tool. I understand that, to maintain a "conversation context", the "tool" is limited on answers with 25 items. My colleagues and I are looking for use-cases when Fabric Data Agent could be relevant. But this limitation of 25 (which is very small, he can't even give the 50 states of USA) is a bad argument for us to use this Fabric Artefact. When trying to build cool agents for the company, and when testing them, users may ask some lists of items. They could have a warning for the partial results.. but 25... gasps !!! Of course, when you ask Copilot for the Web, you get a list with more than 25 items "Here’s the full list of the 50 U.S. states and their capitals in English: Alabama – Montgomery Alaska – Juneau Arizona – Phoenix Arkansas – Little Rock California – Sacramento North Carolina – Raleigh South Carolina – Columbia Colorado – Denver Connecticut – Hartford North Dakota – Bismarck South Dakota – Pierre Delaware – Dover Florida – Tallahassee Georgia – Atlanta Hawaii – Honolulu Idaho – Boise Illinois – Springfield Indiana – Indianapolis Iowa – Des Moines Kansas – Topeka Kentucky – Frankfort Louisiana – Baton Rouge Maine – Augusta Maryland – Annapolis Massachusetts – Boston Michigan – Lansing Minnesota – Saint Paul Mississippi – Jackson Missouri – Jefferson City Montana – Helena Nebraska – Lincoln Nevada – Carson City New Hampshire – Concord New Jersey – Trenton New York – Albany New Mexico – Santa Fe Ohio – Columbus Oklahoma – Oklahoma City Oregon – Salem Pennsylvania – Harrisburg Rhode Island – Providence Tennessee – Nashville Texas – Austin Utah – Salt Lake City Vermont – Montpelier Virginia – Richmond West Virginia – Charleston Washington – Olympia Wisconsin – Madison Wyoming – Cheyenne" Does anyone agree that the limitation is too smal ? ThanksSolved6.7KViews1like8CommentsFabric Data Agent in Copilot Studio not outputting message
I am having a problem that I have connected my Copilot Studio agent to a Fabric Data Agent. I can ask a question within the chat window, and it will output a response in the MCP popout window, but not in the chat window, and I can't get it to respond in Teams or M365 after I published it either. It is answering because if I ask it to repeat, it will, so just when it calls that MCP, it doesn't send that message.Solved2.2KViews0likes4CommentsFabric Data Agents - residency
I tested and ontology could only be created with the 2 tenant settings for processing and storing outside of our region being enabled. Assuming the same is true for data agents. I would like an official answer that this is the case. Unless you are in the US region, data sent to azure OpenAI can be stored outside you capacity's geographic region, compliance boundary, or national cloud instance. Copilot admin settings - Microsoft Fabric | Microsoft Learn Thank you.Solved4.2KViews1like2CommentsAzure AI Search in Data agents not working
Hi, I have followed the instructions on the documentation but nothing has helped. I have assigned Search Index Data Contributor, Search Index Data Reader, and even Search Service Contributor role to my account. I have set the API Access control to Both, not just Role-based access control. Then, I have added two indexes to the data agent and have tried both semantic search and simple search. Neither of them worked. I don't get an error either.4.4KViews0likes6CommentsFabric Data Agent Tool not working
Issue with Microsoft Foundry Agent tool: Fabric Data Agent. Getting error: tool_user_error: Fabric run failed during execution. Find out more troubleshooting details here - https://aka.ms/foundryfabrictroubleshooting I have checked the troubleshooting page but nothing useful as the error is "too generic" Foundry Agent is using Model: Gpt-4.1 Tool connected: Fabric Data Agent My Agent was working fine till few hours back and it's been working since last few days ever since it's been created. I have admin access for my Entra ID in Fabric workspace and also Data Agent. I have both Azure AI User and Azure AI Admin role at foundry service and project level. Even provided the Foundry service project's Managed Identity Admin rights on the Fabric Workspace. I have separately tested the Fabric Data Agent from Fabric workspace and it's working absolutely fine. I have even created a new connection for the Fabric Data Agent and tried with a new agent, still it's same. I have also tried by changing the LLM Model. Not sure what happened suddenly! Can anyone help or suggest? Also, is there any Quota limit?Solved3.5KViews0likes6Comments