Forum Discussion
Can't Publish an Agent inside Copilot Studio for Teams
The agent is for a demonstration of how to use Dataverse for Teams. That's why it has to be built in the Copilot Studio app inside Teams. The agent works fine in testing. Its a demo so its basically just the built-in default Topic set. Everything works til you try to hit the Publish tab in the agent. Then you get a non-descript error as I've shown in the original post.
I've been through the troubleshooting link you listed. Its not a permissions issue. Based on responses I'm seeing elsewhere it seems to be a current issue in some legacy software that MS isn't actively pursuing a fix for. Unfortunately, there is no work around and it breaks the functionality of the product entirely.
Hey Paul, I have tried to export and improt my agent into another environment, It worked fine, and it was Published succefully, I think there might be a permissions issue with the Admin, however MS devs might not have scripted the error message yet, again, that's just a personal opinion, the workaround, is try to export the agent and import it into different environment, Best of Luck
Did you import it into a Teams based environment or a regular environment? It works in a regular environment. It doesn't work in a Teams environment from the Teams Copilot Studio app. I just heard back from someone on the Team at Microsoft that this is a known issue they are currently working on. They hope to have a resolution soon.
answeing to your question, The Environment is Not Teams based
I had to open it on the web copilot page, there only the export option apeared, then it took me to the agent soultion page, expoted it unmanaged and downloaded it, then from the web copilot studio page, I changed to my orgnization default environment, then from the import option, selected the downloaded zip folder, then it was imported to the default environment, then it was published successfuly
I am glad you could've reach Microsoft team, because I can't reach my org Admin to take this step, Thank you for the good news, I hope it's resolved soon