SharePoint Agents vs Copilot Studio Agents: Which One to Build

Two people in the same company can look at the same problem, "our team cannot find anything," and walk away with completely different projects. One clicks Copilot on a SharePoint site and has an agent answering questions before lunch. The other opens Copilot Studio and starts a six-week build. Both are using Microsoft's agent tooling. They are not building the same thing, and the difference is worth understanding before you commit a quarter to the wrong one.

Here is what actually separates them, with the numbers Microsoft publishes rather than the ones that circulate on vendor blogs.

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

A SharePoint agent is a retrieval assistant bound to SharePoint content. Microsoft describes agents in SharePoint as helping users quickly find information and insights on SharePoint sites, pages and document libraries, and says they access your organization's data the same way Copilot does in other Microsoft 365 apps, responding to users based on their access permissions to the data. You point it at a site or a set of files, give it a name and instructions, and it answers. There is no design canvas, no topic authoring and no action framework.

A Copilot Studio agent is an authoring environment. You define topics and instructions, attach knowledge from multiple source types, wire in Power Platform connectors, add actions that write to systems, publish to Teams or a website, and manage the whole thing centrally. It is a builder, so it can express far more than retrieval, and it also carries the obligations of anything you build: someone tests it, someone owns it, someone maintains it after the person who made it changes teams.

Do you need a Copilot license to build a SharePoint agent?

To create one, yes. Microsoft's requirements table is explicit: creating an agent needs a user assigned a Copilot license plus the ability to add new files to a SharePoint site. Configuring and interacting with an agent needs either a Copilot license or pay-as-you-go billing set up for that user. Microsoft's own comparison of the two paths says that with no Copilot license and no pay-as-you-go, users cannot create or use agents at all.

There is no activation step, which surprises admins who expect a rollout project. Microsoft states that agents in SharePoint do not require activation, and that once a user is assigned a Copilot license, or the organization has pay-as-you-go billing set up, agents automatically become available on eligible sites where the user has permissions. In practice this means the feature is probably already on in your tenant if you bought Copilot, whether or not anyone told the SharePoint team.

How much do SharePoint agents cost per question?

For a user with a Microsoft 365 Copilot license, nothing extra. Microsoft's billing page states that interactive use of generative answers, tenant graph grounding and agent actions by authenticated Microsoft 365 Copilot users, inside Microsoft 365 apps and services, is included at no extra cost.

For everyone else it runs on the Copilot Studio meter. Microsoft documents the rates directly: a generative answer costs 2 messages, tenant graph grounding costs 10 messages, and because SharePoint agents are grounded in the tenant graph, each interaction with a SharePoint agent uses 12 messages to respond to a single complex prompt. Copilot Studio sells prepaid capacity at $200.00 per pack of 25,000 Copilot Credits per month, which puts a single agent question at roughly ten cents. Microsoft's SharePoint blog on consumption-based pricing quotes the pay-as-you-go meter at $0.01 per message, which is $0.12 per interaction. The Copilot Studio pricing page itself lists only the prepaid pack, so the ten cent figure is the one you can derive from Microsoft's own price list, and $0.12 is the number Microsoft's SharePoint team published.

Ten cents a question sounds trivial until you multiply. A 400-person support team asking five questions a day each is about $200 a week, and unlike a seat license that number moves with adoption, so the more useful the agent becomes the more it costs. The setup path is not free either: pay-as-you-go requires an Azure subscription, an Azure resource group and a billing policy, and the person doing it needs SharePoint administrator rights plus Owner or Contributor on the Azure subscription and resource group. You can create up to 10 billing policies, each assigned to one security group, which is how you contain spend by department.

How many knowledge sources can a SharePoint agent have?

Twenty. Microsoft's Copilot in SharePoint FAQ states that you can currently include up to 20 source items as the knowledge source of an agent, and that those source items can be sites, document libraries, folders and files. A whole site counts as one item, so the cap is more generous than it first reads, and Microsoft's own guidance is that if you need more than 20 source items you can nest the data at a higher level and point the agent at that level instead. In practice the 20 is rarely the thing that stops you. What stops you is that all 20 have to be SharePoint.

Supported file types are Office formats DOC, DOCX, PPT, PPTX and XLSX, plus PDF, TXT and RTF. Images, meeting recordings, videos and OneNote notebooks are listed as coming soon rather than available. If a meaningful share of your institutional knowledge is in recorded calls, that gap decides the project on its own.

There is a quieter constraint that catches teams later. Microsoft's guidance for agents grounded in SharePoint content says Copilot is currently unable to parse tables and other special formatting, and recommends removing tables before referencing content. It also advises keeping referenced files under about 36,000 characters, roughly 15 to 20 pages, and limiting the total page count across specified files to no more than 300 pages for full-content search. If the number your team keeps asking for is trapped in a table inside a scanned PDF, you will get better results by converting that PDF into a clean spreadsheet and letting the agent read structured rows instead of a page image.

When should you build in Copilot Studio instead?

Three signals, and any one of them is enough.

The agent needs knowledge that is not in SharePoint. A SharePoint agent has no path to Slack, Jira, Salesforce or a third-party wiki. Copilot Studio can get there through connectors, though you own the configuration and the maintenance.

The agent needs to do something, not just say something. Filing the ticket, updating the record, kicking off the approval. SharePoint agents answer; they do not act.

You are heading for many agents rather than one. Once a dozen departments each want their own assistant, the central lifecycle, DLP and environment controls in Copilot Studio are what stop it becoming shadow IT. That governance layer is the real argument for the heavier tool, and it is why the licensing split matters: the two products are priced and administered separately, which we break down in detail in our comparison of Copilot Studio and Microsoft 365 Copilot licensing.

Which one should you pick?

Start from the question set, not the tool. Write down the twenty questions people actually ask most often, then mark where each answer lives. If eighteen of them point at two or three SharePoint sites, build a SharePoint agent this afternoon and stop there. It is the cheapest correct answer and it takes minutes.

If the list scatters across Slack threads, Google Docs, Jira tickets, Confluence pages and email, neither Microsoft tool solves it cleanly. A SharePoint agent cannot reach that content at all. A Copilot Studio agent can, in the sense that you can build and maintain the connections yourself, but at that point you are staffing an internal search product rather than buying one, and the hard parts are the ones nobody scopes: permission fidelity, revocation latency, connector drift and relevance tuning.

What neither tool covers

Both Microsoft options share one boundary. They are excellent inside Microsoft 365 and they stop at its edge. That is a reasonable design choice for Microsoft and an expensive one for a company whose knowledge does not respect that boundary, which is most companies. A decision gets made in Slack, the reasoning lands in a Google Doc, the implementation detail sits in a Jira ticket and the customer-facing wording ends up in Confluence. An agent reading SharePoint alone answers confidently from one quarter of the evidence, and a confident partial answer is more dangerous than no answer.

That gap is what InSearch fills. One query across Google Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce, returning a written answer with inline citations back to the exact source documents so anyone can verify in five seconds. Item-level permissions are inherited from each connected app and enforced live at query time, so a revoked permission takes effect immediately rather than at the next scheduled reindex. Nothing to build, no meter, and a published per-seat price. If you want the full side-by-side on scope and licensing, the SharePoint agents alternative page has the comparison table, and the Copilot Studio alternative page covers the builder path. For SharePoint content specifically, our SharePoint search page explains how cross-app answers work when SharePoint is one source among many.

Frequently asked questions

Is a SharePoint agent the same as a Copilot Studio agent? No. A SharePoint agent is a retrieval assistant created directly on a SharePoint site and limited to up to 20 SharePoint knowledge sources. A Copilot Studio agent is built in a separate low-code authoring environment, can use connectors and actions, and is governed tenant-wide. They share the same underlying billing meter but they are different products for different jobs.

Can unlicensed users use SharePoint agents? Only if an admin sets up pay-as-you-go billing. Microsoft's comparison table shows that without a Copilot license and without pay-as-you-go enabled, users cannot create or use agents. With pay-as-you-go enabled, all unlicensed users can use agents and are billed accordingly.

Do SharePoint agents use Microsoft Graph? Yes. Microsoft documents that SharePoint agents are grounded in the tenant graph, which is why each interaction consumes 10 messages for tenant graph grounding on top of 2 messages for the generative answer. Tenant graph grounding is optional per agent and can be turned on or off.

Can I convert a SharePoint agent into a Copilot Studio agent? Microsoft has signalled that deeper integration with Copilot Studio is on the roadmap, which would allow richer configuration and additional data sources. Until that ships, treat them as separate builds and do not plan a migration you cannot schedule.

How do I control what a SharePoint agent can see? Through the site's existing permissions and the source items you select. Microsoft states that if you do not have permission to specific content, even if that content is included in the agent's sources, you will not see information from it in your chat with the agent. The agent adds no new access.

Ask the box at the top of this page anything you would ask a colleague, and see what a cited, cross-app answer looks like before you commit to a build.