SharePoint Agents: Licensing, Setup and Governance

A SharePoint agent is a Copilot chat scoped to the sites, pages and files you choose, answering only from content each user already has permission to see. Using one needs a Microsoft 365 Copilot license or pay-as-you-go billing through Azure. Microsoft is retiring the .agent file format: existing files stop working after March 2027.

Agents are the fastest way for a small business to get a useful answer out of years of SharePoint documents, and the fastest way to discover that those documents were shared too widely. This guide covers what agents are, what they cost under Microsoft's current licensing and metered model, how to create and scope one, how permissions carry over, and the upgrade Microsoft is rolling out as this is written. Everything here was read on Microsoft's pages on November 7, 2026; this area changes quickly, so check the sources before you commit budget. If your sites are not in order yet, start with how to set up SharePoint for a small business.

What is a SharePoint agent?

Microsoft describes agents in SharePoint as AI that helps "users quickly find information and insights on SharePoint sites, pages, and document libraries," accessing data "the same way Copilot in other Microsoft 365 apps does, responding to users based on their access permissions to the data" (Get started with agents in SharePoint, Microsoft Learn, checked on November 7, 2026). There are two layers. Copilot in SharePoint is the ready-made assistant on every site that answers questions about that site's content; Microsoft notes its general availability began rolling out on September 30, 2026 (Get started with Copilot in SharePoint, Microsoft Learn, checked on November 7, 2026). A custom agent is one you build with a name, a purpose and a chosen set of sources, historically saved as a .agent file in the site.

What does a SharePoint agent cost?

Microsoft's licensing table is the clearest summary (same Get started page):

Microsoft 365 Copilot license	Pay-as-you-go enabled	What the user gets
No	No	"Cannot create or use agents."
No	Yes	"All unlicensed users can use agents and are billed per pay-as-you-go billing."
Yes	No	Licensed users can create and use agents; unlicensed users cannot.

Creating an agent requires a Copilot license plus the ability to add files to the site; configuring and chatting with one requires a Copilot license or pay-as-you-go. The metered model works in messages: Microsoft's billing page states that a generative answer is billed as 2 messages and tenant graph grounding as 10, so "each interaction with a SharePoint agent uses 12 messages" for one complex prompt from an unlicensed user, and that interactive use by licensed Copilot users is included at no extra cost. Charges appear under the Copilot Studio meter on your Azure invoice (Set up SharePoint agents for pay-as-you-go billing, Microsoft Learn, checked on November 7, 2026). The page gives message counts, not a dollar rate; the per-message price is set by the Copilot Studio meter, so confirm the current rate with your reseller before estimating.

Two more facts shape the budget. Microsoft states that "SharePoint Agents pay-as-you-go only applies to .agent files" and that upgraded agents follow the licensing model for agents in the Copilot app (Upgrade agents in SharePoint and OneDrive, Microsoft Learn, checked on November 7, 2026). And Copilot in SharePoint itself splits into everyday capabilities included with the Copilot license and "advanced work" (large-scale synthesis, creating whole sites, scheduled automations) that consumes Copilot Credits through usage-based billing (Get started with Copilot in SharePoint, cited above). For how Copilot licensing fits the rest of Microsoft 365, see our Copilot plans guide.

How do you set up pay-as-you-go billing for agents?

Microsoft's steps, condensed (Set up SharePoint agents for pay-as-you-go billing, cited above):

1. Have an Azure subscription and create a resource group for SharePoint agents. The person doing this needs to be a SharePoint administrator and hold the Owner or Contributor role on both the subscription and the resource group, only for the duration of setup.
2. In the Microsoft 365 admin center, create a pay-as-you-go billing policy in the Copilot node (Copilot > Billing & usage), following Microsoft's Copilot billing setup page.
3. On the Billing & usage page select Connect a service, choose SharePoint agents, select the policy, then Save and Done.
4. Assign a security group to the policy. Microsoft notes that only users in that group get access to SharePoint agents, that each policy currently takes one security group, and that you can create up to 10 policies.
5. In Microsoft Cost Management, create a budget with alert conditions so someone is emailed before the monthly spend surprises you.

If you set up the older org-settings policy in 2025, Microsoft asks you to disconnect it first before linking agents to a new policy.

How do you create and scope an agent?

From a library or list, select Copilot > Create an agent on the command bar, or select specific files and choose Create an agent from their menu so the selection becomes the initial scope. You need edit permissions on the site and either a Copilot license or an organization with pay-as-you-go enabled. In the builder you name the agent, describe its purpose, and add or remove sites, pages and files as knowledge sources; agents you create are listed in the Plugin store (Create and edit an agent, Microsoft Support, checked on November 7, 2026). To share one, open the agent chat pane, select the ellipsis, then Share and Copy link; Microsoft notes you can share only agents you built, not the site's Copilot.

Site owners choose which agent opens from the Agent icon in the site header through Settings > Site AI: Copilot by default, or any agent on the site. Microsoft is clear that agents "aren't automatically listed or published anywhere" and that no approval step is required; it suggests a Site Assets folder structure for tracking approved agents. Deleting an agent means deleting its .agent file (Manage agents in SharePoint, Microsoft Support, checked on November 7, 2026).

Scope narrowly. An agent for "all our policies" should point at the policy library and the HR site's pages, not the whole tenant. Narrow scope gives better answers and a smaller blast radius if a library turns out to be overshared.

How do permissions work with SharePoint agents?

Two permission sets apply. The .agent file's own permissions decide who can open or edit the agent. The agent's answers depend on each user's permissions to the sources: Microsoft's note says that if a user "has access to the agent but not to the site or document library it references, the agent's responses for this user don't include content from those restricted sources" (Manage access to agents in SharePoint, Microsoft Learn, checked on November 7, 2026). The same page lists the admin controls: a per-user service plan toggle, Microsoft Copilot for SharePoint, inside the Copilot license; restricted access control policies through SharePoint Advanced Management; restricted content discovery, which removes the Agent icon from a site and keeps its content out of agents; and Purview DLP rules with sensitivity labels that exclude labeled files from responses while leaving the citation.

The lesson every business learns the same way: an agent does not create oversharing, it reveals it. A finance spreadsheet shared with "Everyone except external users" in 2021 is one question away from the whole company. Run the review in our SharePoint permissions worksheet before you scope an agent at a site, and read Copilot oversharing for the admin reports that find the worst cases.

What is changing with SharePoint agents in 2026 and 2027?

Microsoft is retiring the .agent file format, not agents. From its upgrade page (cited above): existing .agent files "will continue to work across SharePoint, Microsoft Teams, and the Copilot app until the end of March 2027" and stop responding after that; "Starting in mid-November 2026" creating an agent from SharePoint or OneDrive uses Microsoft Copilot Agent Builder and "no longer saves a .agent file"; an Upgrade to Microsoft 365 agent button and a convert-agent-file-to-skill skill arrive on the same timeline; an Agent Chat web part is coming for placing agents on pages; and "There's no automatic upgrade." Microsoft's recommended paths:

What the agent does today	Microsoft's recommended path
Answers questions about the current site's content	Use Copilot in SharePoint directly and set it as the site's main agent
Performs a repeatable task or workflow within the site	Convert the agent to a skill for Copilot in SharePoint
Provides a named, customized Q&A or analysis experience	Upgrade it with Microsoft Copilot Agent Builder
Is a Copilot Studio custom engine agent published to SharePoint	Publish it to the Microsoft Copilot app

Two consequences for a small business. Sharing changes: an upgraded agent uses agent-level sharing to people, groups and email addresses, not SharePoint groups, and is private until its owner shares it unless the original was shared with everyone. And billing changes: pay-as-you-go for SharePoint agents covers only .agent files, so an upgraded agent used by unlicensed staff falls under the Copilot app's pay-as-you-go instead. Inventory your agents now; Microsoft points to the Owned by you section of Build in SharePoint, SharePoint Advanced Management reports and the agent registry.

How should a small business govern agents?

1. Decide who may create agents. Creation needs a Copilot license and edit rights, so license assignment is your first control.
2. Fix permissions before scope. No agent on a site until the site passes the permissions review.
3. Name an owner for every agent and record its sources, audience and purpose; Microsoft's upgrade page asks for exactly this inventory.
4. Flag sensitive sites with restricted content discovery so they never appear in any agent.
5. Label confidential files and add the DLP rule that keeps labeled content out of responses.
6. If you use pay-as-you-go, scope the billing policy to a security group and set a Cost Management budget alert.
7. Review usage quarterly with the SharePoint Advanced Management agent reports, and delete agents nobody uses rather than upgrading them.

Where agents stop and custom development begins, our SharePoint API guide explains what to ask; where the knowledge itself is the problem, see building a SharePoint knowledge base.

What this does not do, and the limits to plan around

• An agent cannot show a user content they lack permission to see; it also cannot fix the oversharing it exposes.
• Pay-as-you-go requires an Azure subscription and admin roles; it is not a toggle in SharePoint.
• Microsoft's billing page states message counts (12 per interaction), not a price; the rate comes from the Copilot Studio meter.
• Agents are not published anywhere automatically; discovery is by link, the site's Agent icon, Teams or the Plugin store.
• Existing .agent files stop working after March 2027, and there is no automatic upgrade.
• Government clouds lag: Microsoft notes Copilot in SharePoint is not yet available in GCC, GCC High and DoD.

Frequently asked questions

Do SharePoint agents need a Microsoft 365 Copilot license?

To create one, yes. To use one, either a Copilot license or an organization that has set up pay-as-you-go billing through Azure; without either, Microsoft states the user cannot create or use agents.

Can an agent show me files I cannot open?

No. Microsoft states that responses depend on each user's permissions to the agent's data sources, and content from sources the user cannot access is excluded. The risk is the reverse: it will surface files you can open but should not have been able to.

How is pay-as-you-go measured?

In messages. Microsoft bills a generative answer as 2 messages and tenant graph grounding as 10, so one complex prompt from an unlicensed user consumes 12 messages, charged under the Copilot Studio meter in Azure. Licensed Copilot users are not charged for interactive use.

Can I turn agents off for one site?

Yes. Flag the site with restricted content discovery and the Agent icon disappears, the ready-made agent is unavailable and the site's content cannot be added to other agents. Restricted access control narrows a site to a named group instead.

What is the difference between a SharePoint agent and Copilot in SharePoint?

Copilot in SharePoint is the built-in assistant on every site for Copilot-licensed users, answering about that site's content and, with Copilot Credits, doing larger automated work. A SharePoint agent is a custom-scoped, named assistant you build over chosen sources.

Will my existing SharePoint agents stop working?

Agents saved as .agent files keep working until the end of March 2027, then stop responding. Microsoft provides upgrade paths (Copilot in SharePoint, a skill, or Copilot Agent Builder) but no automatic conversion.

Sources

Checked on November 7, 2026.

• Get started with agents in SharePoint, Microsoft Learn: what agents are and the licensing comparison table.
• Set up SharePoint agents for pay-as-you-go billing, Microsoft Learn: Azure prerequisites, billing policies, message counts and Cost Management.
• Create and edit an agent, Microsoft Support: creating, scoping and sharing an agent.
• Manage agents in SharePoint, Microsoft Support: the main agent, approval and deletion.
• Manage access to agents in SharePoint, Microsoft Learn: permissions, service plan toggle, restricted content discovery and DLP.
• Upgrade agents in SharePoint and OneDrive, Microsoft Learn: the .agent retirement timeline, upgrade paths and billing changes.
• Get started with Copilot in SharePoint, Microsoft Learn: general availability, Copilot Credits and Site AI settings.