Skip to content

Microsoft Brings Copilot Agents Directly Into SharePoint: What the New Agent Chat Web Part Means for Businesses

Microsoft is making it easier for organizations to bring conversational AI into their everyday workplace experiences with a new SharePoint feature: the Agent Chat web part. The upcoming capability will allow SharePoint page authors to embed existing Microsoft 365 Copilot agents directly into SharePoint pages, giving employees a more convenient way to discover and interact with AI assistants without leaving their organization’s intranet.

Announced for a worldwide rollout beginning in November 2026, the feature is expected to reach general availability across commercial and government environments by March 2027. Microsoft says no administrator action will be required, while existing SharePoint and agent permissions will remain separate.

The update reflects Microsoft’s broader effort to make AI agents part of everyday business workflows rather than tools employees must actively search for or access through separate applications.

What Is the Microsoft SharePoint Agent Chat Web Part?

The Agent Chat web part is a new SharePoint component that allows page authors to place Microsoft 365 Copilot agents directly within SharePoint pages.

Instead of directing employees to a separate interface to find an AI assistant, organizations will be able to make agents available alongside relevant intranet content, documentation, instructions, and other business resources.

For example, a company could embed an HR assistant on its employee benefits page, helping staff interact with an existing agent while reviewing information about leave policies, workplace benefits, or internal procedures.

Similarly, an IT department could place a support agent on its technical resources page, allowing employees to ask questions and access assistance from the same environment where they find troubleshooting guides.

The feature is designed to improve agent discovery and accessibility by bringing conversational experiences into familiar SharePoint environments.

How Will the New SharePoint Feature Work?

Microsoft says SharePoint page authors will be able to add the Agent Chat web part through the standard SharePoint page editing experience.

Once the component is available, authors can select published agents that are already accessible to them in Microsoft 365 Copilot.

The experience will support several key capabilities:

  • Direct agent embedding: Authors can place existing published Copilot agents within SharePoint pages.
  • Improved discoverability: Employees can find relevant AI assistants alongside the content they already use.
  • In-page interaction: Users can interact with embedded agents directly from SharePoint.
  • Full-screen conversations: Users can continue their interactions through a full-screen chat experience.
  • Contextual placement: Organizations can position agents alongside relevant instructions, resources, and business information.

This approach gives organizations more flexibility in how they introduce AI assistants to employees.

Rather than relying entirely on employees to know which agent to open, businesses can place relevant assistants exactly where they are likely to be useful.

Microsoft SharePoint Agent Chat Rollout Timeline

Microsoft has outlined a phased rollout covering public preview and general availability across commercial and government cloud environments.

The currently announced schedule is as follows:

Deployment environmentAvailabilityExpected rollout
WorldwidePublic PreviewMid-November 2026 to late January 2027
WorldwideGeneral AvailabilityMid-January to late March 2027
GCCGeneral AvailabilityMid-January to late March 2027
GCC HighGeneral AvailabilityMid-January to late March 2027
DoDGeneral AvailabilityMid-January to late March 2027

The public preview will give eligible organizations an opportunity to explore the feature before its broader commercial release.

General availability is expected to begin in mid-January 2027, with deployment continuing through late March.

Organizations should note that rollout dates represent Microsoft’s expected deployment windows. Actual availability may vary as the phased rollout progresses.

Who Will Be Able to Use the Agent Chat Web Part?

The feature primarily targets SharePoint page authors and employees who already have access to Microsoft 365 Copilot agents.

There are two main groups involved.

SharePoint page authors

Authors will be responsible for adding the Agent Chat web part to relevant pages and selecting published agents they can access.

This gives intranet owners, content managers, and departmental teams another way to organize AI resources around specific employee needs.

Employees using Copilot agents

Users will be able to interact with embedded agents directly from SharePoint pages, provided they have the required Microsoft 365 Copilot license and access to the configured agent.

The distinction is important: embedding an agent in a SharePoint page does not automatically make that agent available to everyone who can view the page.

Organizations will need to manage page access and agent access independently.

An Important Security Detail: SharePoint Permissions and Agent Access Remain Separate

One of the most important aspects of Microsoft’s announcement concerns permissions and access control.

Adding a Copilot agent to a SharePoint page does not automatically grant page visitors permission to use that agent.

SharePoint page permissions and agent access permissions continue to operate independently. Employees must still have the appropriate access to the configured agent before they can interact with it.

This separation is particularly relevant for organizations with multiple departments, restricted business information, or different levels of access across their workforce.

For example, an organization might publish an internal HR page that is accessible to a broad employee audience while embedding an agent that is available only to a particular authorized group.

The SharePoint page itself does not override the agent’s existing access controls.

Microsoft has also clarified another important point: SharePoint page content is not automatically passed to the embedded agent.

This means organizations should not assume that placing an agent next to a document, policy, or knowledge resource automatically gives the agent access to that material.

The agent’s capabilities and information access remain dependent on its existing configuration and permissions.

This distinction will matter when organizations design employee-facing AI experiences and communicate what embedded agents can and cannot do.

What Does This Mean for Businesses Using Microsoft 365 Copilot?

The introduction of the Agent Chat web part could influence how businesses deploy and encourage the adoption of AI assistants across their organizations.

One common challenge with enterprise AI tools is discoverability. Even when organizations invest in AI assistants, employees may not know which agents exist, what they are designed to do, or where to find them.

Embedding agents within SharePoint pages offers a practical way to address that challenge.

1. Better AI Agent Discovery

Organizations can introduce agents in locations employees already visit.

For instance, a finance assistant could appear on a finance resources page, while an IT support assistant could be placed within a technical help center.

This reduces the need for employees to search through separate tools to locate the appropriate assistant.

2. More Contextual Employee Experiences

The ability to position agents alongside relevant resources creates opportunities for more organized digital workplace experiences.

Employees can review company information and interact with an appropriate AI assistant within the same SharePoint environment.

However, organizations should remember that page content is not automatically shared with the agent. Any required knowledge sources and integrations must be configured separately.

3. Greater Flexibility for SharePoint Authors

The feature gives intranet teams another way to structure and present AI capabilities.

Rather than creating a separate destination for every agent, authors can integrate assistants into existing departmental pages and employee resource centers.

This could make it easier to organize an organization’s growing collection of Copilot agents.

4. Potentially Higher Agent Adoption

Making agents easier to find may encourage employees to use them more frequently.

The impact will depend on the usefulness of the agents, the quality of their underlying information, employee training, and the relevance of their placement within SharePoint.

The web part provides a new distribution channel, but successful adoption will still require thoughtful implementation.

Does the Update Require Administrator Action?

According to Microsoft, no administrator action is required before the rollout.

The Agent Chat web part will become available as part of Microsoft’s deployment process, allowing SharePoint authors to use it through the standard page editing experience once it reaches their environment.

However, no required administrative action does not mean organizations should ignore the update.

IT teams, SharePoint administrators, and support departments should prepare for the change by:

  • Informing SharePoint page authors about the new web part.
  • Identifying existing published Copilot agents that could benefit from being embedded in relevant pages.
  • Reviewing agent permissions to ensure only authorized employees can use each assistant.
  • Updating internal documentation to explain how employees can access embedded agents.
  • Helping support teams understand the distinction between SharePoint page access and agent permissions.

Microsoft also recommends reviewing its documentation on the feature: Use Agent Chat web part in SharePoint.

Compliance and Data Protection Considerations

Microsoft does not expect the Agent Chat web part introduction to create a compliance impact.

The company has clarified that SharePoint will not store Copilot agent chat data as a result of this feature, nor will the update change how agent data is processed.

This is an important distinction for organizations operating under internal data governance policies or regulatory requirements.

The new component is intended to provide an additional way to access existing agents rather than introduce a new agent data-processing model.

Still, organizations should continue to evaluate their existing Copilot configurations, agent permissions, data sources, and governance policies.

The absence of an expected compliance impact does not eliminate the need for organizations to maintain appropriate oversight of their AI deployments.

What Organizations Should Expect Next

Microsoft’s Agent Chat web part is scheduled to begin its public preview rollout in mid-November 2026, followed by general availability starting in mid-January 2027.

As the feature becomes available, organizations will have an opportunity to rethink how AI assistants are presented across their SharePoint environments.

The most immediate opportunity is likely to be in departmental intranets, employee self-service portals, IT support centers, and internal knowledge hubs, where employees frequently need guidance or assistance.

For businesses already using Microsoft 365 Copilot, the update offers a new way to connect existing agents with the places where employees work and find information.

The bigger question will be how organizations use this flexibility. Simply embedding more agents will not necessarily improve productivity. Choosing the right agents, placing them in relevant locations, maintaining clear access permissions, and ensuring their knowledge sources are reliable will determine the quality of the experience.

As the rollout progresses through March 2027, organizations will be able to assess how effectively embedded AI assistants fit into their existing SharePoint strategies and broader Microsoft 365 workplace experiences.


Discover more from Dellenny

Subscribe to get the latest posts sent to your email.

Discover more from Dellenny

Subscribe now to keep reading and get access to the full archive.

Continue reading