The steps
From Microsoft’s documentation, November 2026:
- Publish the agent at least once in Copilot Studio. The Teams channel needs a published version.
- Go to Channels and select the Microsoft 365 and Microsoft Teams tile.
- Select Make agent available in Microsoft Copilot if colleagues should also be able to use it in the Microsoft Copilot app, then Add channel.
- Optionally choose Edit details to set the details people see in Teams.
- Select See agent in Teams and then Add to try it yourself.
Your organization must allow Power Platform apps in Teams; otherwise the agent can’t be added.
Who gets to see it
Under Availability options there are four ways to share:
| Option | Who sees it | Approval needed |
|---|---|---|
| Copy link | Anyone you send the link to (doesn’t work on Teams mobile) | No |
| Show to my teammates and shared users | People you shared the agent with, in the Shared with you section of the Microsoft 365 Agent Store | No |
| Show to everyone in my org > Submit to org catalog | Everyone, under Built for your org | Yes, an admin in the Teams admin center |
| Download .zip | Whoever installs the manifest, for example an admin | Depends on how it is installed |
Two settings decide where the agent can live: Users can add this agent to a team and Use this agent for group and meeting chats.
After approval, content updates go live without new approval. Changing the agent’s details does need approval again.
Admins can also limit who shares what. Per Microsoft’s sharing-controls page, the limits are a Managed Environments setting in the Power Platform admin center: an Editor can edit, configure, share and publish an agent, a Viewer can only chat with it, and Editor permission can only be given to individual users, never to a security group. Microsoft adds that these limits apply only to agents that require authentication, and that new rules can take up to an hour to be enforced.
The common mistake: building a team agent that can’t read in a team
Most people build an agent over a SharePoint site, test it in personal chat, then add it to the team channel, and the answers stop. That is a documented limit: in group chats and channels the agent can’t use SharePoint or other knowledge that needs end-user authentication. Plan for this up front:
- For knowledge that needs per-user access, keep the agent in personal chat or Microsoft Copilot.
- For a channel agent, use knowledge that doesn’t need user authentication, such as public websites or the agent’s instructions.
- Mind Teams rate limiting if the agent is busy in a large channel.
Two more limits from the documentation: in the Microsoft Copilot channel the Conversation Start topic doesn’t fire, and after republishing a SystemError can occur, for which Microsoft documents a workaround.
The Teams-only plan
Some Microsoft 365 subscriptions include Copilot Studio for Teams. It is enough for a simple rule-based agent inside Teams, but it has no generative orchestration, publishes only to Teams, has no premium connectors and stores data in Dataverse for Teams. For anything else you need regular Copilot Studio licensing, see What license do you need for Copilot Studio?.
What this means for a team
Publishing to Teams is the step where an agent goes from a maker’s experiment to something the team relies on. Decide beforehand who owns it, who may change it after approval, and what the agent may know in a channel versus a personal chat. The difference between Copilot and Copilot Studio is on What is the difference between Microsoft Copilot and Copilot Studio?.
Where Bombos fits
A Teams agent knows what its maker gave it, and in a channel even less. Bombos is a plugin that gives Copilot, your Studio agents and the other AI tools your team uses (Claude, ChatGPT, Codex, Cursor, your own agents) one shared memory of team knowledge, learned rules, mail and documents, traceable, in the cloud or on your own server. One person can try it first with their own agents.
Related questions
Do I need admin approval to share an agent in Teams?
Only for the whole organization. Sharing by link or with chosen teammates works without approval. Submitting to the org catalog sends the agent to an admin, who approves it in the Teams admin center.
Do updates need approval again?
Content updates to an approved agent don't need re-approval. Changing its details, such as name or description, does.
Can the agent use SharePoint knowledge in a Teams channel?
No. In group chats and channels the agent can't use SharePoint or other knowledge sources that require end-user authentication. It works in personal chat.
What is the Copilot Studio for Teams plan?
A limited plan included in some Microsoft 365 subscriptions. It has no generative orchestration, publishes only to Teams, has no premium connectors and uses Dataverse for Teams.
