How are other companies publishing their agents for company use in Microsoft Teams?

(0) Share

Report

Posted on by SM-06101152-0

We are getting ready to rollout Copilot Studio to the entire company in the next couple weeks and I am struggling to come up with a proven, and easy solution for users to share their Agents to others in Teams.

Microsoft removed the Ability to embed a Copilot Agent in a Power App, which was our preferred method as it worked flawlessly.

Using the Built in Channel to publish to Teams as a basic Chatbot has many flaws including inconsistent responses, Topic Triggering correctly, etc.

Not to mention that since it is a persistent chat, you have to add an Inactivity Topic to basically force a time out, then give instructions to users on how to restart their conversation.

These types of steps I have found from others struggling as well:
https://mattruma.com/adventures-with-copilot-studio-teams-and-microsoft-365-copilot-channel-challenges/?utm_source=substack&utm_medium=email
https://microsoft.github.io/mcscatblog/posts/copilot-studio-teams-deployment-ux/

Today, to prepare for the Company wide announcement, I wanted to get our Agent published and hopefully shared to others before the communication and found another issue.

Our agent starts with a very basic Adaptive card asking users what type of information they are looking for. If they select the 3rd option to calculate costs, which calls a 2nd agent, it generates errors in Teams that are not there in the Test Pane:

As you can see in the Screen shot, it does connect to the 2nd agent and prompt questions. But it will be VERY Embarrassing to share an Agent to everyone and have all 58,000+ people see an error generated on their very first attempt to use an Agent.

So, back to my Topic..
How are you all getting around this VERY limiting process?

Categories:

Publish & channel management

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Prasad-MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
We understand the issue you’re facing with multi-agent orchestration in Microsoft Copilot Studio when used in Microsoft Teams, where errors are shown despite successful execution.

What you're seeing in Microsoft Copilot Studio → Microsoft Teams is expected due to current platform limitations.
⚠️ Key Issues

Test pane ≠ Teams behavior

Multi-agent calls cause errors in Teams

Adaptive cards + orchestration are unstable

No true session reset (persistent chat)

✅ What to Do

Use single agent only (avoid agent-to-agent calls)

Move logic to Power Automate / APIs

Avoid first-message adaptive cards

Add a simple “restart” command

Always test in Teams (not just test pane)

---------------------------------------------------------------------------------------------------------------------------

We have highlighted this concern with the engineering team for further investigation, as it appears to be related to runtime behavior in the Teams channel.

We will keep you posted as soon as we receive any updates or guidance from engineering.

Was this reply helpful? Yes No
SM-06101152-0 22 on at

Like (0)

Report
Copy link

Link copied!

Following the steps you outlined would really handcuffs the use of Copilot Studio Agent.
Basically, it sounds like basic Q&A Agents will only work to publish to Teams as you can't connect multiple agents, can't use Adaptive Cards, etc..

We have many Developers right now creating agents in the Developer environment that connect to multiple agents.
I have one person right now that has 5 "Child Agents"

If we follow this advice, they'd have to share out 6 Agents, people will have to navigate to each individual agent to get their work done, defeating any time savings the agent is meant to provide.

Mainly, I am hoping to find out how others are sharing their agents out to companies to use since this option has a lot of bugs and issues.

Was this reply helpful? Yes No