Understanding the user experience of using an agent in SharePoint in Teams chat

Introduction

Starting with the first post of 2025 and found a nice surprise whilst exploring some of the updates in the features for “Agents in SharePoint”. For those with a Microsoft 365 Copilot license, there are options to add an agent in SharePoint to use the contents of the library or site to use as a data source when interacting with the agent.

I have written a introductory blog post here, for those that have not yet seen this capability: Taking a peek at the new Agents in SharePoint features

When checking for updates on the feature, as this is an evolving set of features, some new capabilities have been introduced that allow you to use the agent from SharePoint outside the context of SharePoint, for example, Teams Chat.

For me, I found this to be super cool and again another super easy experience with enabling and using this within Teams. It is relatively quick to create an agent in SharePoint, 2 clicks in fact (if you have read my post), one to Create an Agent, on the library toolbar, and the other to either accept default settings or customise them.

So what’s this capability in Teams?

So when I was exploring the SharePoint settings for the agent, I discovered a new option to Copy link for Teams

This triggers the standard file sharing dialog you would expect for sharing other files. For me, the default was Organizational wide Sharing, as my tenant is relatively vanilla. Microsoft have released Best practices with SharePoint for Copilot | Microsoft Learn article on the topic.

Now, let’s head over to Teams.

Moving over to Teams Chat experience

In my tenant, I have a user called “Normal User” (not particularly imaginative lol!), for a one-to-one chat. When I paste the link into the chat experience, the file link presented as a card that was automatically shown to describe the link in more detail.

Of course, there is a button presented Add to this chat which I clicked to add, I am presented in the chat experience a welcome message.

Let’s query it and see the experience

You might expect just a simple response but there is a nice scenario that is handled where the sharing link is only for the agent file NOT the files the agent reference files as its data source, as my content resides in a private Microsoft 365 Group.

Therefore, Copilot has an extra step to check and confirm sharing a responsing using that content source since, I have access to the data, but the recipient user does not.

With the prompt @Documents agent please summarize the hardware request process? triggers the experience:

Here the agent is requesting that you review the response before posting in the chat to the recipient.

In the preview, you can see, the response, reference files and sensitivity labels if assigned to the content that the agent is referring to. You can choose to Send or Don’t send the response.

On clicking send, you can see the response pasted in the chat to the recipient:

Very cool!

What if you add multiple agents?

The feature for the same site will only support a single agent, e.g. either a site agent or documents agent. When you try to add another, the experience will prompt to remove the other agent.

Areas of consideration

There are some considerations when using this feature:

• Proper Naming - When creating these agents, to ensure Title, Description are carefully created having many Document agent as the default could cause some confusion when chatting to folks using multiple agents.
• Agent Contact Card - The agent itself, will have a contact card that you can message, I have found this not to respond to queries in this manner.
• No squeezing more out of the agent - I have tried to log into the normal user and query the other files, this will not work as the user will not have access to all the other files that the agent references, respecting the security of the site.
• List of Agents - you can see what agents have been added over time, in the chat, under the Shared files, look for .agent files, other than that there is NO interface to list these explicitly.

Conclusion

This is a great feature, I can see use for this in conversations and provides that extra surface to discuss around content on the site. I really like the thought and process being considered in the agent for SharePoint features. Keep them coming!

Resources

The following resource could be useful for you to learn further:

• Best practices of SharePoint for Copilot | Microsoft Learn
• Oversight of Sharing Information in SharePoint sites using PowerShell with CSOM, REST and PnP PowerShell by Reshmee Auckloo
• Manage Access to SharePoint Agents | Microsoft Learn

Enjoy!