MC1559633: SharePoint Adds Agent Chat Web Part to Embed Microsoft 365 Copilot Agents in Pages

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
41
0 25 50 75 100
MODERATE IMPACT • ASSESS BUSINESS IMPACT
Recommended Action:
Take a look and decide whether this affects your tenant, users or support teams.
▶ What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

SharePoint AdminsMicrosoft 365 AdminsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
This is a new SharePoint feature allowing page authors to embed Copilot agents using an Agent Chat web part, rolling out from November 2026. No admin configuration is required, but admins should brief site owners and authors about its availability and governance considerations. User impact is moderate since it affects content and interaction experience on pages, while administrative effort centres on awareness and internal communication planning.
40
🛡️ Admin Impact
45
👥 User Impact
40
⚡ Urgency
35
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

A new Agent Chat web part lets SharePoint authors embed Copilot agents directly into pages, making them easier for users to find and interact with.
👥

END USERS

Users may see embedded Copilot chat boxes within SharePoint pages.
🛡️

IT ADMINS

Inform SharePoint page authors and support teams about this new web part and review related documentation.
📅

ROLLOUT TIMELINE

Rolling out:
Public Preview

📢 Official Microsoft Message Center Announcement


Microsoft SharePoint: Agent Chat web part to bring Copilot agents into SharePoint pages
Message ID: MC1559633

[What and Why:]

We’re introducing the Agent Chat web part in SharePoint, allowing organizations to embed their existing Microsoft 365 Copilot agents directly into SharePoint pages. This helps organizations make agents easier to discover and use by bringing conversational AI into familiar intranet experiences, alongside relevant information, instructions, and resources.

[Rollout Schedule:]

Public Preview (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by late January 2027.

General Availability (Worldwide): We will begin rolling out in mid-January 2027 and expect to complete by late March 2027.

General Availability (GCC): We will begin rolling out in mid-January 2027 and expect to complete by late March 2027.

General Availability (GCC High): We will begin rolling out in mid-January 2027 and expect to complete by late March 2027.

General Availability (DoD): We will begin rolling out in mid-January 2027 and expect to complete by late March 2027.

[Impact on Your Organization:]

Who is affected: SharePoint page authors who want to embed Copilot agents. Users with a Microsoft 365 Copilot license and access to the configured agent.

Platforms/Services: SharePoint Online, Microsoft 365 Copilot, Microsoft Copilot Studio.

What will happen: SharePoint page authors can add the Agent Chat web part to pages using the standard page editing experience. Authors can select published agents already available to them in Microsoft 365 Copilot. Users can interact with agents directly from SharePoint pages and continue conversations in a full-screen chat experience. Organizations can place agents alongside relevant SharePoint content to help users discover and engage with them. Existing SharePoint page permissions and agent access permissions remain independent. Adding an agent to a page does not automatically grant users access to that agent. SharePoint page content is not automatically passed to the agent.

[Action Required/Recommendations:]

No admin action is required before rollout. The Agent Chat web part becomes available as part of the rollout.We recommend informing SharePoint page authors and support teams about this capability and reviewing the documentation: Use Agent Chat web part in SharePoint.

[Compliance considerations:]

No compliance impact is expected for this change. SharePoint does not store Copilot agent chat data or change how agent data is processed.

Source: Microsoft Message Center • Analysed by MWPro