Fabric Data Agent Tool not working

Thank you, bariscihan for your response.

Hi AyusmanBasu0604,

We appreciate your inquiry on the Microsoft Fabric Community Forum.

Based on my understanding, the issue is unlikely to be related to permissions, configuration, model choice, or the Fabric Data Agent itself, since the same agent executes successfully when run directly in Microsoft Fabric and also from Classic Foundry (East US). The failure occurs only in the new Azure AI Foundry (East US2).

A temporary workaround is to continue using Classic Foundry Agents for Fabric Data Agent execution. Since this behavior started abruptly, it may be region or runtime specific. We kindly request you to raise a Microsoft Support ticket using the provided link: Microsoft Fabric Support and Status | Microsoft Fabric so that engineering can review the backend logs.

We hope the information provided will assist in resolving the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.

Hi,
From the behavior described, this looks less like a Fabric Data Agent configuration issue and more like an execution or service-layer issue between Foundry Agent and Fabric.

If the Fabric Data Agent works correctly when triggered directly from the Fabric workspace, but fails only when invoked via Foundry Agent, the failure is likely happening during the tool execution handshake (Foundry → Fabric job execution). The tool_user_error: Fabric run failed during execution message is typically returned when Fabric fails before returning a detailed internal error.

Since you already validated:

• Entra ID permissions (Fabric workspace + Data Agent access)

• Azure AI User/Admin roles at Foundry level

• Managed Identity access to Fabric workspace

• New connection + new agent test

• Model switch test

• Fabric Data Agent standalone execution success

I would mainly suspect one of the following:

• Temporary backend/service-side issue (very common when errors are generic)
• Token delegation or identity refresh issue between Foundry and Fabric
• Capacity / quota / throttling scenario (especially if this started suddenly)
• Recent backend runtime update or regression on Foundry tool connector

Suggested Quick Checks

• Check Fabric Capacity metrics and CU utilization at failure time
• Check Fabric Activity Logs for failed runs triggered by service principal / MI
• Re-create Foundry → Fabric connection (even if already done, forces token refresh)
• Test with a minimal Data Agent query (to rule out timeout / payload issues)
• Verify Foundry project region vs Fabric workspace region alignment

Reference

Official troubleshooting guide:
https://aka.ms/foundryfabrictroubleshooting

If Fabric Data Agent works standalone but fails only via Foundry, in most cases this turns out to be either service-side transient failure or identity delegation edge cases rather than role misconfiguration.

If you can share region, capacity SKU, and whether multiple agents are impacted, it might help narrow this further.

Hi AyusmanBasu0604,

We are following up to see whether what we shared resolved your issue. If the issue still persists, please raise a Microsoft Support ticket using the provided link: Microsoft Fabric Support and Status | Microsoft Fabric, so that engineering can review the backend logs.

If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

Hi AyusmanBasu0604,

Thank you for the update and for sharing your insights and working approach, which will be beneficial to other members of the community. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.