ot working for Foundry Agent with Knowledge Setup

[avashneu]

Language/Version
What package version of the SDK are you using.

• Language: C#
• Package version:
• SDK Use: Agents Hosting / Clients / Tools

If you're using the Agent Hosting system, please complete the following information:

• How are you Hosting this:
• Are you deploying:
• Are you using Azure Bot Services: Yes
• What Client are you using: MSTeams
• What dotnet\node\python version is your build in:

Describe the bug
A clear and concise description of what the bug is.

• Please include any stack trace information you can share.
  I am trying to use this SDK to connect to Azure AI foundry agent. The Azure AI Foundry has Fabric Data Agent knowledge setup. If I remove the knowledge from Foundry Agent, it works fine.

When I test, I get the following error. Does this SDK support this parameter and where should it be defined?
**
Error sending message to Azure agent: Missing required parameter: 'tools[0].fabric_dataagent'.
Status: 400 (Bad Request)
ErrorCode: missing_required_parameter

Content:
{
"error": {
"message": "Missing required parameter: 'tools[0].fabric_dataagent'.",
"type": "invalid_request_error",
"param": "tools[0].fabric_dataagent",
"code": "missing_required_parameter"
}
}
**

To Reproduce
How can we reproduce this error?

Please provide Code Snippets, Channel type, and any special configuration we will need to reproduce this problem.

Note: If your issue is with the Copilot Studio Client and its interaction with a feature of Copilot Studio, we would ask that you prepare and make available a simplified power platform solution with a Copilot Studio agent that causes the problem.
If you're not comfortable with this and we require that to explore your issue report, we will ask you to create a Support Ticket with Microsoft so that we can proceed.

Expected behavior
SDK to interact with Azure AI Foundry agent irrespective of the agent knowledge setup.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[sarahcritchley]

@avashneu thanks for raising your issue. Looks like a problem with the fabric tool integration/configuration. Can you share a bit more about your setup here? It looks like Foundry has some expectations around the tool setup, including tool_choice parameter usage.

[avashneu]

@sarahcritchley, when I test my agent in Azure AI Foundry with Fabric data agent setup, it works fine in the Foundry playground.

This is the setup I'm using to Integrate Azure AI Foundry to MS Teams (README summarizes the objective & setup) - https://github.com/davrous/AzureAgentToM365

And these are the parameters that are getting passed -

[sarahcritchley]

Got it, thanks for clarifying. David's sample uses Semantic Kernel, so I am anticipating based on that, and the error you're getting back it's something related to semantic kernel's expectation of fabric as a tool to be used. The Foundry agent isn't using semantic kernel when you test it in the playground.

I'll loop in @sphenry but also i will pull in any additional people to validate the initial take and provide guidance on what you need to do to make the fabric connector work

[avashneu]

Thanks @sarahcritchley. The final objective is to use Fabric Data Agenet through MS Teams. As per my understanding, there's no direct integration supported yet (except using Copilot Studio - but we are restricted by some Data Loss Policy set at the organizational level). So, I'm trying to use Azure AI Foundry as the bridge between Fabric Data Agent and Teams.

[sarahcritchley]

Adding @lindazqli who can provide some guidance on Foundry + Fabric. @lindazqli check out the error that @avashneu is getting above - could you provide some guidance on why this might be happening? Thank you!

[lindazqli]

hey @avashneu when you set up your agent, did you add a Fabric Connection for your Fabric tool? https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/tools/fabric?pivots=portal

[avashneu]

Hi @lindazqli , Yes, I had added Fabric data agent as connection in the AI Foundry agent. When I do so, I get the error mentioned in the reported bug.

[MattB-msft]

I have been working with David on sorting out the issue here.
The root issue, for most of these, appears to be that the AI Foundry Project API wants (semi-demands) to use the DefaultCredentialConstructor for communications, but it does not seem to well support a non-interactive identity.

I have worked with David to modify his sample to use user-based OBO auth flows for connecting to AI Foundry which seem to have sorted out the issue in most cases.

@lindazqli and @avashneu, Given its working in playground (which is using your interactive authentication) and not in a deployed agent (which is using a managed identity) I'm inclined to think this is the same issue.

David should have his sample updated in a few days with updated instructions.

if that does not fix the issue for you, we can follow up further,

[avashneu]

@MattB-msft , Thanks for the update. I'll try it on my end too once with the updated sample.

[MattB-msft]

@MattB-msft , Thanks for the update. I'll try it on my end too once with the updated sample.

The updated sample is posted on a branch on his repo.,.there is an open PR.
it does require you to do some setup in ABS and the Teams Manifest to make it work with SSO