Forum Discussion
Fabric data agent
- Anonymous1 year ago
Hi Shiyao ,
You're absolutely right currently, the Fabric Data Agent SDK is indeed limited to the Fabric runtime (like notebooks) and doesn’t support integration directly within a custom Python backend running outside Fabric. And unfortunately, even when running inside Fabric, it doesn’t expose the raw SQL queries the data agent generates during inference or interaction with the Azure AI Foundry agent.
At this point, Microsoft hasn’t provided a built-in way to log or intercept the translated SQL queries within an agent run via the Azure AI Projects Python SDK. The obfuscated references (like ) are more about traceability than transparency.
If your goal is to manually or automatically validate what SQL was generated, a workaround could be:
- Injecting a custom critic or reasoning prompt into your Foundry agent pipeline that forces the agent to explain what SQL it would run not perfect, but it helps with transparency.
- Raising feedback to Microsoft, since SQL traceability during inference is a critical need for auditing and enterprise-grade validation. This is still a gap in the current agent ecosystem.
Thanks,
Akhil.
Hi Shiyao
just following up to see if the info on using the Fabric Data Agent SDK for evaluation and response inspection was helpful. Were you able to try customizing the evaluation prompts to get more insight into the query logic?
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Regards,
Akhil.
- Shiyao1 year ago
Microsoft Employee
Using Fabric Data Agent SDK won't help as I can't host my Python backend code completely in Fabric runtime. As I understand, Fabric Data Agent SDK is only supported in Fabric notebook. I'm looking for logging the translated SQL queries for manual/automated fact checking while users are interacting with Azure AI Foundry agent, not about just a few sample evaluation prompts.