Forum Discussion
Can't Publish an Agent inside Copilot Studio for Teams
I’m refreshing some Dataverse for Teams demos for a session in about two weeks. Everything works in testing, but I am unable to publish either existing agents or new agents when using Copilot Studio app inside Teams. This happens in multiple Teams and in multiple Tenants. Here’s the screen I get on the Publish tab. Reloading doesn’t help. Is this currently a known issue? No notice of it in M365 admin center on Service status.
Can anyone help?
14 Replies
Just to let you lads know, Publish is working fine for me now, I hope the same for you
Have A great TimeAlso, please have a look into this page,
https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance#data-loss-prevention-and-governance
from what I understand, that the orgnization Admin, can limit the emplyees from Publication ability, Unfortunatly, I have a very strict Admin, and I can't get into getting this permission, but if you can reach out to you orgnization admin, and make him the change it, please reply to me, so I can give it a shot discussing with my Admin to give this idea a chance.
Thank you and Best RegardsIts a good thought, but I am the organization Admin. I have not put limits on Publication.
The same thing has been happening to us over the last few days, and it's really annoying. It also happened about two weeks ago and was resolved two or three days later, but I'm afraid that this time it’s not going to be successful.
The same thing has been happening to us over the last few days, and it's really annoying. It also happened about two weeks ago and was resolved two or three days later, but I'm afraid that this time it’s not going to be successful.
Hi, this seems to be a known issue affecting multiple tenants. Some users report seeing “Publishing could not be completed” in Copilot Studio inside Teams. It may be a backend issue not yet listed in the M365 admin center. Try publishing via Copilot Studio web or check if the agent is added as an app in your Teams tenant. Microsoft may release a fix soon.
I can't use the Copilot Studio web for this since that would invalidate the Dataverse for Teams licensing. That's the whole point of doing it with the App inside Teams. To be clear the app is a rebranded copy of what used to be Power Virtual Agents. It isn't full Copilot Studio.
As gar as I know, this is a known issue with no details published by Microsoft.
if you use the correct user and the correct license for the workload, Microsoft recommends to contact the support:When this is not the way to go for you, I need some more informations. What is the agent for, did you change the group of users to have access to the agent?
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
same thing happened to me just today, and It's really bugging, since it did't happen before
