Microsoft blog (Oct. 30): SharePoint Agents move to Microsoft Copilot Agent Builder from mid-November 2026; legacy .agent files stop working after March 2027, and Copilot Chat users may incur Copilot Credit charges

Microsoft (Microsoft Mission Critical Blog, Tech Community) · Cross-sector (state and local government, higher education, K-12 IT) · Global (no US government cloud dates given)

Microsoft

Publisher: Microsoft Tech Community
Original publication: 2026-10-30
Source retrieved: 2026-11-02
Event date: 2026-11-15

Read original source

What happened

A Microsoft blog post says that, as of Oct. 24, creating an agent from SharePoint or OneDrive will open Microsoft Copilot Agent Builder from mid-November 2026, with rollout complete by early December. New agents become Microsoft 365 declarative agents. Existing .agent files keep working through March 2027; Microsoft plans to disable them from early April, and agents not upgraded will no longer be accessible. Upgraded agents must be re-added to Teams chats and channels. Agent Builder does not automatically grant access to source files. Eligible Copilot Chat users can access declarative agents, but agents using shared tenant data such as SharePoint may incur usage-based Copilot Credit charges. Copilot in SharePoint requires a Copilot licence.

Why it matters

Universities, districts and agencies that let staff build SharePoint agents now have a forced migration with a March 2027 deadline and a possible cost change for Copilot Chat-only users, who are the majority in many SLED tenants.

Evidence and measured results

Vendor-authored blog post summarising Microsoft's own schedule and licensing; no customer data. It cites a roadmap item (575298) still marked in development.

Limitations and uncertainty

Vendor source; dates are Microsoft's and may slip. The post gives no GCC or GCC High timing, so US government tenants should confirm their own dates. Credit costs are not quantified.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-02; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway

Customer problem: Institutions with staff-built SharePoint agents face a forced migration and possible new metered costs.
Stakeholders: Microsoft 365 / collaboration service owner
CIO and IT security
Finance or licensing manager
Departmental agent owners
Discovery questions: How many SharePoint agents exist and who owns them?
Which agents are used by Copilot Chat-only users?
Is Copilot Credit billing configured and capped?
What is your GCC or GCC High timing for this change?
Value hypothesis: An early agent inventory and migration plan may avoid broken agents after March 2027 and surprise credit charges.
Potential engagement: A fixed-scope agent inventory and migration-readiness review ahead of the mid-November change.
Unsupported claims: That the migration adds value for users
Any cost figure for Copilot Credits
That GCC tenants follow the same dates

Pre-sales engineering

Role takeaway

Fit: Relevant to any SLED tenant where staff created SharePoint agents.
Architecture and integration: Move .agent files to Microsoft 365 declarative agents via Agent Builder, Copilot in SharePoint or skills; rebuild Teams and page placements.
Prerequisites: Agent inventory
Owner for each agent
Copilot Credit billing setup
Permission review of knowledge sources
Constraints: Dates are vendor-stated and may slip
No US government cloud timing given
Agent Chat web part still in development
Security: Re-check source permissions separately from agent sharing to avoid oversharing during upgrade.
Proof of value: Test representative prompts and citations before and after upgrade
Confirm Copilot Chat-only users' credit consumption in a pilot group

Delivery

Role takeaway

Work: Inventory, re-home or retire SharePoint agents before the March 2027 deadline.
Dependencies: Microsoft rollout from mid-November
Billing configuration
Department owners' availability
Ownership: Microsoft 365 service owner, with department agent owners for each agent.
Skills and adoption: Train agent builders on Agent Builder; give users updated access points.
Governance checkpoints: Inventory complete before rollout
Each agent has an owner and destination
Credit caps approved by finance
Acceptance criteria: Proposed: 100% of discovered agents assigned an owner or retired
Proposed: upgraded agents pass a prompt and citation test set
Proposed: no unbudgeted Copilot Credit charges in the first billing cycle
Risks: Agents break after April 2027
Oversharing from permission changes
Unexpected metered costs

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Agents move from files stored in SharePoint libraries to declarative agents managed in the Microsoft 365 agent platform. SharePoint stays the knowledge source, but placements in pages and Teams must be rebuilt.

Governance

Who approves, reviews and stays accountable for outcomes?

Each legacy agent needs an owner, purpose and destination (Copilot in SharePoint, a skill, a declarative agent, or retirement). That forces an agent inventory many institutions do not have.

Security and privacy

What data, permissions and controls need testing?

Agent access and content permissions are separate checks; permissions may need to change for the intended audience, which risks oversharing if done hastily.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Staff who built agents need retraining on Agent Builder; users need new access points in Teams and SharePoint pages.

Procurement

What should contracts, pricing and exit terms secure?

Copilot Chat-only populations using SharePoint-grounded agents may shift from free use to metered Copilot Credits, which needs budget and cost controls.

Operating model

Which teams own the service once it runs?

Agent lifecycle moves into central Microsoft 365 agent management, which pushes institutions to assign owners and review agents regularly.

Publication history

2026-11-01Microsoft · Issue 043 resources

Read preserved resource versions (JSON)

Stable resource ID: microsoft-sharepoint-agents-move-to-agent-builder-mid-nov-agent-files-retire-march-2027-20261030