Blog Post

Microsoft Mission Critical Blog
6 MIN READ

SharePoint Agents are changing what customers need to know for preparation

jeresmith's avatar
jeresmith
Icon for Microsoft rankMicrosoft
Oct 30, 2026

SharePoint Agents Are Changing: What Customers Need to Prepare for Now 

Microsoft is moving SharePoint Agents away from the legacy .agent file model and into the broader Microsoft 365 agent platform. The capability is not being retired but the way agents are created, governed, shared, and surfaced is changing. 

As of October 24, 2026, the first phase is scheduled to begin in mid-November, followed by the retirement of .agent based experiences after March 2027. Organizations using SharePoint Agents should treat this as a lifecycle and governance transition not simply a user interface update. 

The transition and its decision points are summarized below. 

 

Figure 1: The transition is not a simple file conversion: each legacy SharePoint Agent needs an owner, a target experience, and validation of permissions, licensing, and access points before support ends. 

New agents will move to Microsoft Copilot Agent Builder 

Beginning in mid-November 2026, creating an agent from SharePoint or OneDrive will open Microsoft Copilot Agent Builder instead of creating another .agent file. New agents will become Microsoft 365 declarative agents and appear through the Microsoft plugin ecosystem. The rollout is expected to complete by early December 2026. 

Users will still be able to start from SharePoint content. Selected sites, libraries, folders, or files become the agent’s initial knowledge scope, but the resulting agent is managed through Agent Builder rather than a file stored in a SharePoint library. Microsoft describes Agent Builder as the lightweight experience for creating declarative agents with dedicated SharePoint knowledge sources, instructions, and scenario specific behavior. 

Why this matters: SharePoint remains the governed knowledge source, while agent creation, sharing, discovery, and lifecycle management move into the Microsoft 365 agent platform.

 

Figure 2: Microsoft Copilot Agent Builder provides the new agent creation experience, allowing users to define agent instructions and add skills to customize the agent for specific scenarios.

 

 

Existing .agent files require a transition decision 

Existing .agent files will continue working through the end of March 2027. Microsoft plans to begin disabling those experiences in early April 2027, with completion expected by mid-April. The retirement affects .agent based experiences in SharePoint, OneDrive, Microsoft Teams, and the Copilot app. 

 

Figure 3: From the Edit agent page, select Upgrade to Microsoft 365 agent to transition an existing agent to the Microsoft 365 agent experience. Microsoft indicates that agents not upgraded by the end of March 2027 will no longer be accessible as agents.
Figure 4: The Upgrade to Microsoft 365 agent confirmation dialog allows users to choose whether the original agent file is moved to the Recycle Bin after the upgrade.
Figure 5: After the upgrade is complete, a confirmation message indicates that the Microsoft 365 agent was successfully upgraded.
Microsoft identifies several transition paths: 
  • Use Copilot in SharePoint for general questions about content on the current site. 
  • Convert the agent to a skill when it supports a focused site-specific task or business outcome. 
  • Upgrade to a Microsoft 365 declarative agent when users need a named, content-grounded conversational experience across Microsoft 365. 
  • Review the publishing configuration of an existing Copilot Studio agent rather than rebuilding it solely because of this change. 
  • Retire or archive the agent if it no longer has a clear purpose or accountable owner. 

Copilot in SharePoint entered general availability rollout on September 30, 2026. Its everyday capabilities require an active Microsoft 365 Copilot license; advanced, large scale work uses Copilot Credits through usage based billing. 

The important customer decision is therefore not simply “How do we convert this file?” It is “Which experience best preserves the agent’s intended business outcome?” 

SharePoint page and Teams placements must be reviewed

Agent access points do not necessarily remain unchanged after an upgrade. As outlined in MC1511052 and MC1511055, upgraded agents may need to be re-added to applicable Microsoft Teams chats or channels, while legacy .agent placements in SharePoint will require review.

To support the new model, Microsoft has announced the Agent Chat web part, which will allow modern SharePoint page editors to configure a page with any Microsoft 365 Copilot agent. Roadmap ID 575298 currently lists a November 2026 preview and January 2027 general availability, with the feature still marked as in development.

This differs from the existing Agent Link web part, which provides a link that opens an agent in a side pane. Organizations with agents embedded on high-traffic intranet or business-process pages should inventory those placements early rather than waiting for the legacy agent deadline.

Permissions and licensing remain two separate checks 

Upgrading an agent does not replace SharePoint permissions. Users still require access to the SharePoint content used as knowledge, while access to the agent itself is managed separately. Microsoft specifically notes that Agent Builder does not automatically grant broad access to source files and folders; permissions may need to be updated for the intended audience. 

Licensing also depends on the selected transition path: 

  • For users with a Microsoft 365 Copilot add-on license, access to declarative agents and SharePoint grounded extensibility does not create additional consumption charges. 
  • Eligible Microsoft 365 Copilot Chat users can access declarative agents, but agents using shared tenant data such as SharePoint may incur usage based charges through Copilot Credits. 
  • Copilot in SharePoint requires a Microsoft 365 Copilot license, while its advanced, at-scale capabilities additionally require usage based billing and available Copilot Credits. 

Admins should therefore validate both user eligibility and cost management configuration before communicating that an upgraded agent is ready for production. 

 

What organizations should do now 

  • Inventory existing agents. Use SharePoint search for *.agent, site usage information, Purview audit data, and the SharePoint Agent Insights reporting capabilities to identify agents and where they are being used. 

         Need a way to start finding existing .agent files in your SharePoint environment? Mike Lee has shared two PowerShell scripts that can serve as                   useful resources for agent discovery and inventory: TenantWide_SP_Copilot_Agents_Insights.ps1 and TenantWide_SP_Copilot_Agents.ps1. The                   insights version has specifically been referenced as a script that can help identify .agent files, making it a helpful resource as organizations assess               their existing SharePoint agents. 

  • Leverage the Microsoft 365 Copilot Agent Registry. In addition to SharePoint specific discovery methods, administrators can use the Agent Registry in the Microsoft 365 admin center to gain centralized visibility into agents across their organization. The registry provides a consolidated view of discovered agents, helping administrators understand their agent landscape, review agent details, and support governance and lifecycle management. This reporting capability complements SharePoint search, PowerShell-based inventory scripts, and Agent Insights by providing another valuable resource for identifying and managing agents as organizations prepare for upcoming changes to SharePoint agents.

 

Figure 6: The Microsoft 365 admin center provides a centralized Agent Registry under Agents > All agents > Registry, allowing administrators to discover and manage agents across their organization. Administrators can filter by platform, including SharePoint, to identify registered SharePoint agents, review their status, and gain greater visibility into their agent inventory. This provides an additional resource for agent discovery, governance, and lifecycle management.
Figure 7: This filtered view displays agent names, availability status, and platform information, providing a useful way to review existing SharePoint agents and support ongoing inventory and governance efforts.

Figure 8: The Microsoft 365 admin center Agent Registry provides an export capability that allows administrators to download agent inventory information for further analysis and reporting. Administrators can export all registered agents or select the current filtered view, such as SharePoint agents only. This capability supports agent discovery, inventory documentation, and ongoing governance efforts as organizations prepare for upcoming changes to SharePoint agents.
 
  • Assign an accountable owner. Record the agent’s purpose, audience, knowledge sources, current sharing model, business criticality, and access points. 
  • Choose the destination by outcome. Use Copilot in SharePoint for site-level knowledge, a skill for a focused site task, Agent Builder for a named Microsoft 365 experience, or retirement where the agent no longer delivers measurable value. 
  • Validate access twice. Confirm that intended users can access both the replacement agent and every SharePoint knowledge source required for a complete response. 
  • Test the replacement. Run representative prompts, verify citations and knowledge scope, review licensing or Copilot Credit implications, and confirm SharePoint, Teams, and Copilot access paths. 
  • Complete the transition before March 2027. Leave time for page updates, Teams replacement, user communications, and remediation of permission or content quality issues. 

The central message is straightforward: SharePoint Agents are not going away, but .agent files are. Customers that begin with inventory, ownership, and scenario based decisions will be better positioned to move into the new Microsoft 365 agent model without disrupting trusted knowledge experiences. 

Resources: 

Updated Nov 09, 2026
Version 4.0
No CommentsBe the first to comment