Forum Discussion
Trigger cant read fabric data agent
I make an agent in Azure AI Foundry. I use fabric data agent as a knowledge. Everything runs well until I try to use trigger to orchestrate my agent. I have added my trigger identity to fabric workspace where my fabric data agent and my lakehouse located. My trigger can work well and there is no error, but my agent cannot respond as if I do a prompt via the playground. Why?
1 Reply
hi margaretaak This behavior usually happens because the trigger and the agent do not share the same execution context even though you’ve added the trigger’s identity to the Fabric workspace. A few things you may want to check:
Authentication / Identity scope
Ensure the trigger’s Managed Identity (system or user-assigned) has both “Fabric Admin/Contributor” rights on the workspace and the correct data access roles on the Lakehouse tables.
Sometimes, the trigger can invoke the agent, but the agent itself cannot fetch the data because the identity used during orchestration is not passed down.
Connection configuration
In AI Foundry, verify that your Fabric data connection is linked to the correct identity. If the connection was created under your personal account, the trigger execution may not inherit it.
Try re-creating the Fabric connection using the trigger’s Managed Identity.
Prompt orchestration differences
Running in the playground uses your account’s session and credentials.
Running via a trigger uses the trigger’s context. If data access isn’t configured identically, the agent won’t respond with Fabric knowledge.
Diagnostics
Check AI Foundry Traces (may show that the agent executed but the Fabric connector returned no data).
Compare what identity is actually being used when invoked by the trigger.
Possible workaround: If the agent works fine interactively but not through the trigger, you’ll likely need to:
Reconfigure the Fabric connection to use a shared connection (not user-based).
Assign the trigger’s identity explicitly to that connection.
