Publishing an Agent to Microsoft Teams and Copilot Produces a Server Error in Azure AI Foundry #223
Replies: 3 comments
-
|
I'm seeing the same thing. I noticed that foundry won't allow you to specify an existing Azure Bot registration-it will auto create one. Also, the appID for the bot is b10665ee-9a08-43d6-bea6-fd4979290ddb, which appears to be the copilot app ID? I'm mostly interested in getting a knowledgebase-grounded agent to work via a directline bot framework connection anyway, so any help here would be welcome! |
Beta Was this translation helpful? Give feedback.
-
|
I'm also unable to publish an agent. While publishing within Foundry itself getting the below error. Same error appears while trying to publish the agent to M365 Copilot or Teams. Followed all the steps in official documentation, still getting the same error. Any help or guidelines to resolve this issue would help. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @brendanahart, @chrisbardon, @shweta0310 Are you still experiencing the issue? Also, which platform are you publishing the app from? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Has anyone been able to successfully publish a nocode agent to Teams or Co Pilot. Whenever I try preparing an agent (before publishing), I get this error message:
There was a problem preparing the agentAn error occurred while preparing the agent. Please try again. Status Code: 500 Request ID: 092b2fb0-8b01-4991-be9a-6ba3068f854c
I'm wondering if anyone knows the proper RBAC configuration for the resources
Beta Was this translation helpful? Give feedback.
All reactions