Add a SharePoint agent to a Microsoft Teams channel: bring answers to where your team already works

By João Ferreira Feb 3, 2026 Copilot, SharePoint 0 Comments

A SharePoint agent becomes far more powerful when you bring it into Microsoft Teams, where your team already collaborates every day. Instead of switching between browser tabs, libraries, and chat threads, adding a SharePoint agent directly to a Teams channel lets users ask questions in natural language and get grounded, permission‑aware answers right in the conversation. It’s one of the easiest ways to surface intranet knowledge where work actually happens and is a feature every Microsoft 365 admin or power user should consider enabling in their tenant.

To show how impactful this can be, let’s look at a real scenario from my demo environment. Explorer is an outdoor‑adventure company used in my articles and presentations. Their intranet stores everything from route documentation to safety procedures, permits, content drafts, and seasonal plans. As the team prepares a new Grand Canyon activity for the upcoming season, most discussions naturally happen in Microsoft Teams, but the authoritative information still lives in SharePoint. By adding the Explorer Activities Agent to the planning channel, the team can instantly ask for summaries, safety notes, past trip insights, and related documents without leaving the discussion.

This guide walks you through exactly how to add a SharePoint agent to a Microsoft Teams channel, the benefits for end users, and the limitations you need to be aware of so you can confidently roll it out in your own tenant.

What this looks like in the channel

@Explorer Activities Agent summarize everything we already have about Grand Canyon trips

Short overview with links to permits, safety checklist, last season’s incident review, and marketing draft. Want a kickoff agenda?

It feels simple because it is the same intranet content, just available where the team already collaborates.

Before you start

• You need a custom‑built SharePoint agent; the built‑in “ready‑made” site agent can’t be shared to Teams.  
• Works in Teams chats, meetings, and standard channels. Private and shared channels aren’t supported yet.
• Answers are permission‑aware; sharing an agent does not grant access to content. If others need broader coverage, update the SharePoint sharing on the underlying sources.
• Licensing: users need Microsoft 365 Copilot or your org must enable pay‑as‑you‑go for SharePoint agents. Editors need site edit permissions to build or adjust the agent.

If you still need to build your first agent, start here: How to create your first Copilot agent in SharePoint (my previous guide).

How to add a SharePoint agent to a Teams channel

1. On the SharePoint site where your agent lives, open Agents from the top right.
2. In the agent picker, find your custom agent,
   

   

3. Choose More (…), then Copy link for Teams.
   

   

4. Paste the link in your Teams channel and send it. Teams will prompt you to Add to this channel. Confirm it.
• If you don’t add it, people will see the link but won’t be able to interact with the agent in Teams.
5. The agent posts a short intro with your sample prompts. Teammates can now @mention the agent in conversations.
   
6. Review the reply from the agent, if it aligns with your request publish it to make it available to everyone.
   

Considerations and limitations

• Guests/external users: if a chat or channel includes external/guest users, the agent won’t answer.
• Channels: supported in standard channels; private and shared channels are not supported yet. When added to a channel, the agent is added to the underlying team.
• 1:1 chat: not available for SharePoint agents yet.
• Mobile: some features are limited on Teams mobile; more support will roll out over time.
• Permissions still apply: sharing an agent doesn’t change access to sites, pages, or files. Adjust sharing if teammates need to see specific sources.
• Licensing: users need Copilot or your tenant must enable pay‑as‑you‑go for SharePoint agents.

Conclusion

Bringing a SharePoint agent into a Microsoft Teams channel may look like a small change, but it fundamentally shifts how people access information in the flow of work. In the Explorer scenario, the team gained instant access to everything they had already documented about the new Grand Canyon activity, without breaking the conversation or jumping across tabs. That same impact translates directly to any organization, regardless of industry.

If your teams rely on SharePoint for project documentation, procedures, policies, product knowledge, or customer files, adding a SharePoint agent to Teams can make that information feel closer and more actionable. Instead of searching libraries, bookmarking pages, or asking the same questions repeatedly, your users can simply @mention the agent and get grounded, permission‑aware answers on the spot.

And the best part? You don’t need to redesign your intranet or restructure your content. If the information already exists in SharePoint, a custom agent can bring it forward.