Server error on Agent Deployment from Azure Foundry to teams and agent365

Question

I have built a simple agent with a MCP server in azure foundry.

Every time I try and message it in teams I get the following error "Something went wrong, please retry. If issue persists, please use following identifiers in any support request: ConversationId = a:1SEjOGDiGzf1CUa-VirVaB8coger69DgCzxb6qbGv2Kz_W4FBK0jC8rsg1sg43ccj27V-A3EK78g1F0_KzngYW6kiTB0t0hBqnA51O95PRCYip9A4kXD2lnGJiZnxu06y, activityId = 1764771996849

 "

When I check the azure bot in my resource group and test the web chat I get the same response.

Now I look in the Foundry Monitor dashboard and can see that there were conversation started and failed. It is hitting the foundry but failing. When I review the application insight attached no logs appear to be captured for that.

I have checked permissions on the foundry and the project and they have the correct role. I also have been able to use other agents just fine.

Answer 1

It sounds like you're encountering issues with your Azure Foundry agent when trying to communicate via Teams. Here are a few troubleshooting steps you can consider:

1. Check Agent Configuration: Ensure that your agent is properly configured in Azure Foundry. Verify that the connection strings and endpoint URLs are correct.
2. Permissions: Although you mentioned that permissions are correct, double-check that the managed identity associated with your agent has the necessary permissions to access both Azure Foundry and the Teams environment.
3. Application Insights: Since you noted that no logs appear in Application Insights, ensure that logging is correctly set up for your agent. You might want to enable additional logging to capture more detailed information about the failures.
4. Network Issues: Check for any network-related issues that might be preventing communication between Azure Foundry and Teams. This includes firewall settings and any geo-blocking that might be in place.
5. Review Foundry Monitor: Since you see conversation attempts in the Foundry Monitor dashboard, investigate any error messages or additional details provided there that might give clues about the failure.
6. Testing with Other Agents: Since other agents are functioning correctly, compare the configurations of the working agents with the one that is failing to identify any discrepancies.

If these steps do not resolve the issue, consider reaching out to Azure support with the provided identifiers for further assistance.

---

References:

• How to troubleshoot your deployments and monitors in Microsoft Foundry portal
• Azure SRE Agent Preview frequently asked questions
• Foundry Agent Service resource and data loss recovery
• Tutorial: Invoke an App Service web app from Foundry Agent Service
• Common Issues