SharePoint Agent Chat is the new web part that lets page authors put an existing M365 Copilot agent directly on a SharePoint page. Microsoft announced it in Message Center post MC1559633 on 18 November 2026, and the public preview is rolling out now.
It sounds like a small thing. One more web part in the toolbox. But for anyone who has built agents and then watched nobody use them, this is a big step. In this post I explain what changes, when it arrives, who gets it and what I would do before you add the first agent to your intranet.
What is SharePoint Agent Chat?
Until now, people had to go looking for an agent. They opened the Copilot app, searched the agent list, or got a link from a colleague. Most people never did.
With SharePoint Agent Chat, the agent comes to them. A page author edits a modern page, adds the Agent chat (preview) web part and picks an agent. Visitors can then chat with that agent right on the page, next to the instructions, links and content that belong to it. When the conversation gets longer, they can continue in a full screen chat view.
Think about an HR page with the leave policy, plus the HR agent that answers questions about that policy. Or a service desk page where the IT agent sits next to the most common how to articles. That is the idea.
Which agents can you add with SharePoint Agent Chat?
According to Microsoft Support you can add:
- Published, user created Copilot agents
- Custom Copilot Studio agents that are published to M365 Copilot and have been used there
The agent picker shows recently used agents. If your agent is missing, open it once in M365 Copilot, wait a short while and check the picker again.
What changes and what stays the same
The most important part of this announcement is what does not change.
- Permissions stay separate. Page access, agent access and access to the agent’s knowledge sources are managed separately. Sharing the page or site does not share the agent.
- No new access. Adding an agent to a page does not give anyone access to that agent.
- No automatic content sharing. Page content is not passed to the agent automatically. Site or page content only goes to the agent when the agent is grounded on that site, or when a user attaches files to a prompt.
- No new storage. Microsoft says SharePoint does not store the agent chat data and does not change how agent data is processed. Conversations are saved like normal Copilot app chats, but the history is not visible inside the web part.
What does change is visibility. SharePoint Agent Chat turns your pages into a front door for agents.
Timeline
| Phase | Environment | Timing according to Microsoft |
|---|---|---|
| Public Preview | Worldwide | Mid November 2026 to late January 2027 |
| General Availability | Worldwide | Mid January 2027 to late March 2027 |
No admin action is required before rollout. The web part simply shows up when the rollout reaches your tenant.
Who is affected by SharePoint Agent Chat
- Page authors who want to add Copilot agents to pages. They need edit rights on the page and a Microsoft 365 Copilot license.
- Visitors who need page access, agent access, access to the grounding sources and a Microsoft 365 Copilot license.
- Support teams and site owners, because they get the questions when a chat box on the page does not work for someone.
License check for SharePoint Agent Chat
A Microsoft 365 Copilot license is required for both the author and the visitor. Pay as you go billing for the Copilot app does not give access. Visitors without a license don’t see the web part at all. Licensed visitors without access to the agent do see it, but can’t use it.
That last point matters. It is the most likely support ticket you will get.
How to add SharePoint Agent Chat to a page
- Open the SharePoint page and select Edit.
- In the web part toolbox, select Agent chat (preview) where you want it.
- Choose the agent from the picker.
- Set the appearance: Overlay color, Overlay opacity, Show author and Show title.
- Add content around it, like instructions and example prompts, so people know what to ask.
- Check that your audience meets the requirements.
- Select Publish or Republish.
Test as a normal visitor, not only with your own author account. Microsoft also recommends starting with a limited audience first.
Limitations to know
- Not supported in mobile browsers or the SharePoint app in Teams mobile. Use a desktop browser.
- There is no admin control to turn the web part on or off.
- Chat history can’t be opened from the web part.
- It is a preview, so features can still change before general availability.
What admins should do now
Admin tips before you roll out SharePoint Agent Chat
- Inform page authors and support. Microsoft recommends this in the MC post, and I agree. Tell them what the web part does and what the license and access rules are.
- Sort out agent sharing first. Share the agent through Agent Builder or Copilot Studio with the same audience that can see the page. Otherwise people see a chat box they can’t use.
- Check the knowledge sources. An agent is only as good as the content behind it. Old documents on a site become old answers on your homepage.
- Use the controls you already have. Because there is no switch for the web part itself, governance happens on the agent. In the Microsoft 365 admin center you can view and block agents in the Agents section of the Copilot Control System. Site owners can use Site AI settings, and restricted content discovery turns off agent features on a site.
- Pick one pilot page. Start with one page with a clear purpose, a small audience and an owner who keeps the content up to date.
If you want to read more about how agents in SharePoint are changing, see my earlier posts on the SharePoint agents upgrade and on SharePoint Copilot Credits.
Is SharePoint Agent Chat worth it?
Yes, if you do the groundwork. The biggest problem I see with agents is not the technology. It is that people don’t know the agent exists. SharePoint Agent Chat fixes the discovery problem by putting the agent where the question starts.
At the same time, it can also show your content problem faster. If the HR site has three versions of the leave policy, the agent on the HR page will happily answer from the wrong one. So clean up first, then add the agent.
The Paul-Take
This is the missing piece for agent adoption. I see so many tenants with good agents that only the builder uses. Putting SharePoint Agent Chat on the page where people already go is how you get real usage.
But don’t treat it as a quick win you just drop on the homepage. Fix agent sharing, check the content behind it and test as a normal user. And remember there is no admin switch for this web part, so your governance is the agent and its sources, not the web part.
Imagine one agent on your intranet that handles 90% of the questions people ask every day. How cool would that be?
This should be rolling out in November 2026 (Preview) and January 2027 (General Available) according to Microsoft.
Want help picking the right page and agent for your organization? Get in touch.
MVP reference list
- Message Center: MC1559633, Microsoft SharePoint: Agent Chat web part to bring Copilot agents into SharePoint pages (published 18 November 2026)
- Roadmap: 575298
- Microsoft Support: Use the Agent Chat web part
- Microsoft Learn: Manage access to agents in SharePoint
- Microsoft Learn: Get started with Copilot in SharePoint
- Microsoft Learn: Manage Copilot agents in the Microsoft 365 admin center