TL;DR: SharePoint agents saved as .agent files keep working until the end of March 2027, then stop responding in SharePoint, Teams and the Copilot app (Microsoft’s switch-off rolls out from early to mid-April 2027). From mid-November 2026, rolling out through early December, new agents are built in Microsoft Copilot Agent Builder. Intranet owners should inventory every agent now, choose an upgrade path for each and update pages that use the Agent Link web part. Unless IT sets up pay-as-you-go billing, upgraded agents only reach Copilot-licensed staff, so make sure each page still answers the common questions on its own.
If your intranet has an “Ask HR” or “IT help” agent on a SharePoint page, it now has an expiry date. On October 16, 2026, Microsoft announced in Message center post MC1511052 that SharePoint agents built in the .agent file format are moving into the wider Microsoft Copilot extensibility ecosystem, with new agents created in Microsoft Copilot Agent Builder.
The good news is that SharePoint agents aren’t going away. Only the file format is. Your job is to decide what each agent should become and fix the pages where people use it. Here’s a practical plan.
What Is Changing with SharePoint Agents?
From mid-November 2026, new SharePoint agents are built in Microsoft Copilot Agent Builder, and existing .agent files stop working after March 2027. Until now, creating a SharePoint agent saved a small .agent file in a document library. Site owners could set it as the site’s “main agent,” open it in the chat pane or drop it onto a page with the Agent Link web part.
According to Microsoft Learn’s Upgrade agents in SharePoint and OneDrive guide, three things change at that point:
- Creating an agent from SharePoint or OneDrive opens Microsoft Copilot Agent Builder, and no .agent file is saved anymore. You can still pick SharePoint and OneDrive content as knowledge sources.
- An Upgrade to Microsoft 365 agent button appears in the existing SharePoint agent builder.
- A new skill, convert-agent-file-to-skill, becomes available in Copilot in SharePoint.
New agents appear in the plugin store in the Copilot app and are governed by admins through Microsoft Agent 365.
For intranet pages, two details matter. Upgraded agents can’t run in the site’s chat pane, so they can’t be the site’s main agent. And Microsoft’s replacement for pages is a new Agent Chat web part, which adds any plugin store agent to a page. Microsoft 365 roadmap item 575298 lists it as in development. Preview is planned for November 2026 and general availability for January 2027, in Worldwide, GCC, GCC High and DoD. Microsoft Learn still calls it “coming soon,” so treat those dates as targets.
What this means for you: Nothing breaks today. But every page with an embedded agent will need editing, because the Agent Link web part won’t serve agents after March 2027. Plan to swap in the Agent Chat web part once it reaches your tenant. If it hasn’t reached your tenant by March, link to the upgraded agent from the page with its share link in the meantime.
When Do .agent Files Stop Working?
Existing .agent files keep working until the end of March 2027, and Microsoft’s switch-off rolls out from early to mid-April 2027. The dates differ slightly between sources, so plan around the earliest one.
- Mid-November to early December 2026: Agent Builder creation, the Upgrade button and the skill for converting agent files roll out (Message center post MC1511052).
- November 2026 to January 2027: Agent Chat web part is planned to move from preview to general availability (roadmap 575298).
- End of March 2027: Existing .agent files keep working until then (Microsoft Learn).
- Early to mid-April 2027: the switch-off rolls out (Message center post MC1511052). Agents in the .agent format stop responding in SharePoint, Teams and the Copilot app. The Agent Link web part, the immersive viewer and the SharePoint chat pane no longer open them, and opening a .agent file shows a message saying an upgrade is required (Microsoft Learn).
There’s no automatic upgrade. An agent owner or site owner must choose a path for every agent; anything left untouched stops answering.
Which Upgrade Path Fits Each SharePoint Agent?
Most intranet agents fit one of four paths: Copilot in SharePoint, a skill, an Agent Builder agent or republishing a Copilot Studio agent. Agents nobody uses can be deleted. Use this table to triage your list:
| Agent scenario on your intranet | Recommended path | Who can use it afterward |
|---|---|---|
| Answers general questions about the content of one site (e.g., “What’s new on the Finance site?”) | Use Copilot in SharePoint directly and set Copilot as the site’s main agent | Users with a Microsoft 365 Copilot license |
| Runs a repeatable task on a site (draft a document from a template, review a file against a policy) | Convert to a skill with convert-agent-file-to-skill, then add a Button web part to the page so people can find it | Users with a Microsoft 365 Copilot license, inside that site |
| A named “expert” with its own instructions and starter prompts, e.g., an HR policy or IT help agent on a hub page | Upgrade to a declarative agent in Copilot Agent Builder, then add it to the page with the Agent Chat web part | Licensed users, plus unlicensed users if your tenant has pay-as-you-go billing (not available in GCC or GCC High) |
| A custom engine agent built in Copilot Studio and published to SharePoint | Don’t rebuild. Publish it to the Microsoft Copilot app and Teams channels so the Agent Chat web part can display it | Depends on your Copilot Studio setup |
| No recent use or no clear owner | Archive or delete it | Nobody, which is fine |
Microsoft’s rule of thumb is to use a skill for a focused task on the site and an agent for a tailored Q&A, retrieval or analysis experience (Microsoft Learn).
Who Can Use Upgraded SharePoint Agents, and What Licensing Do They Need?
Who can use an upgraded agent depends on the path. Copilot in SharePoint and skills need a Microsoft 365 Copilot license, while Agent Builder agents can also reach unlicensed staff through pay-as-you-go billing.
- Agents saved as .agent files could be created by people with a Microsoft Copilot license, or in organizations with pay-as-you-go billing enabled for agents in SharePoint (Microsoft Support). From mid-November 2026, no new .agent files are created.
- Copilot in SharePoint and skills require a Microsoft 365 Copilot license; “advanced work” at scale also uses Copilot Credits (Microsoft Learn).
- Copilot Agent Builder is available with a Microsoft 365 Copilot license or in tenants with pay-as-you-go enabled for Copilot Studio (Agents admin guide). Without either, agents can’t be grounded in SharePoint data (licensing models).
- The SharePoint agents pay-as-you-go meter only covers .agent files. Upgraded agents follow standard Copilot agent licensing, and unlicensed usage of agents on pages “is consolidated under Copilot app pay-as-you-go (PAYG)” (Microsoft Learn).
- Government clouds are in scope for the change, but Copilot in SharePoint, and so the skill path, isn’t available there yet (Microsoft Learn). Pay-as-you-go billing also isn’t supported in GCC or GCC High (licensing models).
What this means for you: If most of your intranet readers don’t have Copilot licenses, the Copilot in SharePoint and skill paths won’t reach them. For a company-wide HR or IT agent in a commercial tenant, the Agent Builder path with pay-as-you-go is usually the only option that serves everyone. Check with IT that a billing policy covers the people who use your intranet before you switch. Either way, design the page so employees without a license still get the most common answers.
How Do You Upgrade the SharePoint Agents on Your Intranet Pages?
This plan follows Microsoft’s checklist, with the intranet page work added in.
- Inventory every agent. Owners see theirs under “Owned by you” in Build in SharePoint; admins can use SharePoint Advanced Management agent reports, the agent registry or search (Microsoft Learn).
- Map where each agent appears. List every page using the Agent Link web part, every site where it’s the main agent and every Teams chat or channel it’s in. Start with your home site and HR, IT and policy hubs.
- Record owner, audience and sharing. Unless a .agent file was shared with everyone in the organization, the upgraded agent starts private, and it can’t be shared to SharePoint groups.
- Pick a path per agent using the table above, and delete the ones nobody uses.
- Export usage data. Usage history doesn’t carry over, so capture any adoption numbers you report on.
- Upgrade and re-share. Select Upgrade to Microsoft 365 agent, then share with the right Microsoft 365 groups. The confirmation dialog offers to move the .agent file to the recycle bin; leave it in place if the old agent must stay on the page or as the site’s main agent until you can switch to the Agent Chat web part. People also need access to the knowledge sources, and Agent Builder agents can use up to 100 SharePoint files as knowledge (Microsoft Learn).
- Update the pages. Replace the Agent Link web part with the Agent Chat web part, then set the site’s main agent back to Copilot in Settings > Site AI. If the Agent Chat web part hasn’t reached your tenant yet, link to the upgraded agent’s share link for now.
- Re-add agents to Teams. Remove the old agent from each chat or channel, then post the upgraded agent’s share link there.
- Test, then tell people. Try familiar prompts with a few real users, including someone without a Copilot license, to check the page still answers the common questions. Then send site owners and agent creators a short note: what’s changing, the deadline and who to contact.
- Delete the old .agent file once the replacement works. Microsoft calls this the easiest way to track progress.
What this means for you: IT can press the upgrade button, but steps 2, 7 and 9 belong to comms and intranet teams, because only page owners know where each agent lives and who relies on it.
What Gets Better with Copilot Agent Builder?
Upgraded agents work across the Copilot app, Teams and SharePoint instead of living in one file in one library. They get central governance through Agent 365, usage analytics, more customization and one plugin store where people find them. Skills give site owners a lighter way to add focused tasks without building a full agent. The change also fits Microsoft’s wider direction. An October 30, 2026 Tech Community post describes SharePoint as the knowledge layer for Copilot and agents, and stresses that answers are only as good as the content’s ownership, currency and permissions.
Why the Page Around Your SharePoint Agent Matters More Than the Agent
The page around an agent should answer the most common questions on its own, with the agent as one section rather than the whole page.
Picture your HR help page in April 2027. Someone forgot to swap the Agent Link web part, or the upgraded agent is still private while sharing gets sorted. Staff without a Copilot license can’t use it at all unless IT has set up pay-as-you-go. On a page built around a single chat box, employees hit an “upgrade required” message or an agent they can’t open, and leave. That’s the risk of treating the agent as the page rather than one element on it.
Now picture the same page designed the other way. The most common questions (“How do I book leave?”, “When is payroll?”) sit in a FAQs design element that expands and collapses, and can be connected to a SharePoint list so HR updates one list instead of the page. Quick Links point to current policies and forms, and Person Cards connected to People Search show named HR contacts straight from your directory. ShortPoint’s Visibility settings can show each region its own contacts by SharePoint or security group, without separate pages. The agent gets its own section. If it’s broken, mid-swap or unavailable to someone without a license, the page still does its job.
ShortPoint is itself a SharePoint web part, so it sits on the same modern page as Microsoft’s web parts, including the agent one. Building a page like this is easier with AI Designer, ShortPoint’s AI-powered design tool, which is included on the Pro and Enterprise plans and doesn’t need a Copilot license. You can also start from the HR Portal or IT Helpdesk template (250+ templates, included with every plan). Then add the Agent Chat web part in its own section and publish.
Our point of view: Microsoft is right to move SharePoint agents into Copilot Agent Builder, and you should upgrade the agents that earn their place. But agents will keep changing format, licensing and web parts. The intranet page is the stable layer every employee relies on, whether or not they have a Copilot license. Design it so the most common answers are visible without a prompt, and let the agent handle the long tail.
Get Your Intranet Pages Ready Before April 2027
To rebuild your HR, IT or policy hubs so they work for every employee, with or without an agent, start a 15-day free trial of ShortPoint (no credit card needed) or browse the ShortPoint template library.
For related reading, see our guides to Copilot in SharePoint general availability and the Copilot readiness checklist for SharePoint intranets.
FAQ
No. Only the .agent file format is being retired. You can still create agents grounded in SharePoint content, but from mid-November 2026 they're built in Microsoft Copilot Agent Builder and appear in the plugin store instead of being saved as .agent files.
Agent Builder is the guided, no-code way to build declarative agents in Microsoft Copilot from instructions and Microsoft 365 knowledge such as SharePoint. Copilot Studio is for agents that need workflows, actions in external services, connectors, external channels or structured development and release. Upgraded SharePoint agents use Agent Builder, and you can copy one to Copilot Studio later if it needs more.
Microsoft says .agent files keep working until the end of March 2027. Message center post MC1511052 says the switch-off rolls out from early April and completes by mid-April 2027, after which agents in the .agent format stop responding in SharePoint, Teams and the Copilot app.
No. There is no automatic upgrade. An agent owner or site owner has to choose a path for each agent: use Copilot in SharePoint, convert it to a skill, upgrade it in Copilot Agent Builder, republish a Copilot Studio agent or delete it.
Microsoft's new Agent Chat web part lets site owners add any agent from the plugin store to a page. The Microsoft 365 roadmap targets preview from November 2026 and general availability in January 2027. Until it reaches your tenant, link to the upgraded agent's share link. Upgraded agents can't run in the site chat pane, so set the site's main agent back to Copilot.
It depends on the path. Copilot in SharePoint and skills require a Microsoft 365 Copilot license. Agents built in Copilot Agent Builder can serve unlicensed users if your tenant has pay-as-you-go billing enabled and a billing policy covers them, with that usage billed under Copilot app pay-as-you-go. Pay-as-you-go isn't supported in GCC or GCC High.
Not automatically. If the .agent file was shared with everyone in the organization, that access can carry over; otherwise the upgraded agent is private until you share it with people or Microsoft 365 groups. Users also need permission to the SharePoint content the agent uses.