I look after a lot of SharePoint site collections. Every one of them now ships with a Copilot that can write a Word document, create a list, rename and share a file, generate an image straight into a document library, and stand up a scheduled automation that keeps running long after the person who asked for it has moved on.
Type –agenttools in Copilot in SharePoint, and you get a panel of tool categories, each expanding into the individual capabilities behind it. There are roughly twenty categories. These are the agent tools: the actions a Copilot, or an AI Skill built on top of it, can call.
Some of those actions are now billed. Microsoft has split Copilot in SharePoint into what comes with the license and what consumes Copilot credits, and the metered side is where most of the interesting work lives: large-scale synthesis, creating entire sites and solutions, working at scale across files and lists, multistep AI automations, image generation, site-wide real-time autofill, analytics. Every one of those is one prompt away for anyone who can open Copilot on that site. More to read here:
https://learn.microsoft.com/en-us/sharepoint/copilot-in-sharepoint-get-started
Every tool in the panel is available to everyone who can open Copilot there, free or metered. There is no approved subset, no site where the agent may read but not produce, and no site where the expensive half of the product is simply not on the menu.
What is behind the tool panel, and what it costs
It is worth being precise about what sits behind that panel, because the word “tool” makes them sound like utilities. Most of them are not read operations. They write, and some of them bill.
| Included with the Microsoft 365 Copilot license | Consumes Copilot credits |
| Ask questions, find content, catch up | Large or unbounded content sets, including large-scale synthesis and document review |
| Create HTML, Word, Excel or PowerPoint files | Create entire sites and solutions |
| Create and edit pages, libraries or lists | Create and edit files, pages, libraries and lists at scale |
| Simple rules, approvals and deterministic workflows | Multistep AI workflows, such as skills in scheduled AI automations |
| Rename and share individual files | Generate and edit images in libraries and on pages |
| Create and manage skills; autofill metadata | Site-wide real-time autofill; site and content analytics |
The credit cost of a task varies with complexity and content volume, so the same prompt on two sites produces two different bills. Copilot reports what a task consumed if you prompt /cost, warns when twenty percent of the monthly limit remains, and pauses metered features when the limit is hit. All of it reports on money already spent.
Asking people to request the right entitlement in advance requires them to know what they are about to consume before they know what they are about to ask. Nobody types a prompt thinking, “This one is a large-scale synthesis across an unbounded content set.” They think they asked a question.
Two controls exist today, and neither is the one you need
Restricted Content Discovery and site AI settings work on the site axis, but only as a master switch: Copilot is on there, or it is not. That is the RCD problem in a sentence — the only safe configuration for a sensitive site throws away the entire feature. You can always read more here: https://gokan.studio/2026/05/23/the-hidden-impact-of-rcd-in-sharepoint-when-discovery-controls-disable-productivity/
Cost management spending policies work on the money axis, but they scope by identity: all users or named security groups. Microsoft’s own guidance is to prioritize credits for content managers and site managers, which is sensible advice— that entitlement travels with the person onto every site they touch. It is a budget attached to a person rather than to a place, and there is no way to say that the intranet may burn credits while the ninety thousand project sites may not.
It would be great if we could add SharePoint Sites as an Access scope in our Policies. Being able to give the site or Business Process the Credits it needs is what we need as improvement.
One more cost-management detail is worth discussing. Existing spending policies can automatically pick up newly available services, governed by an option called “Allow new agents and services as they become available.” Microsoft has already built the concept of a default rule for capability that does not exist yet — and pointed it at permissive. That same idea, turned the other way, is most of what this article is asking for.
Microsoft already solved the shape of this
The mechanism isn’t exhaustive; it’s been running in the same cloud for years. In the Power Platform admin center, connectors are sorted into three mutually exclusive groups—Business, Non-Business, and Blocked—and controls below each connector let you allow or deny individual actions rather than the whole connector.
We could borrow the mechanism and improve it. Three decisions in that model matter more than the three-group split itself: a default group that decides what happens to connectors Microsoft adds after the policy was written; scoping by inclusion or exclusion, so one policy covers thousands of targets without a hand-maintained list; and clean precedence,
What an agent tool policy could look like
Concretely, the missing piece is a policy object in the SharePoint (Advanced) admin center.
- A basic tier and an advanced tier (MVP – Drew Madelung): The common case is not a bespoke matrix per site. It is two profiles: included-tier tools everywhere, metered tools only where someone has signed up for the bill. Being able to say “this site is basic” in one click would cover most of a large tenant on day one. According to the documentation, Autofill will have that function, so looking forward to it!
- Three states, plus a cost class. Allowed, Restricted, and Blocked per tool, with every tool showing whether it is included or metered. Restricted is a state that Power Platform lacks, and SharePoint would benefit from: the tool runs, but only for site owners or a named Entra group, or only with an approval attached.
- A credit ceiling per site, not only per person. (MVP – Mike Maadarani) Spending policies already set limits and alerts by security group. The same limits expressed per site would let a project own its AI budget the way it owns its storage.
- Granularity and scoping that survive scale. Block the whole creation category on one site; on another, allow HTML dashboards and nothing else.
- A default for new tools. The direct counterpart to the cost management option above. Microsoft ships new agent tools continuously, and today everyone arrives switched on, everywhere, on the day it lands.
Let’s translate our Policy types into practical examples:
| Site | Policy | Effect on agent tools |
| Project Alpha | Open (Allowed type) | Every tool allowed, metered work included. The site owner has accepted the bill. |
| Project Delta | Controlled authoring (Restricted Type) | Word, Excel and PowerPoint creation blocked, because documents here are meant to originate from the managed template library. Retrieval, list and page work stay on. |
| Project Zeta | Regulated (Restricted Type) | Automations, file and site creation, image generation and agent-initiated sharing blocked. Read, search and summarize stay on, so the site keeps its Copilot value without the agent producing anything new. |
| All other sites | Basic tier (Blocked Type) | Everything metered blocked by default; included-tier tools available. Nothing is dark, and nothing bills until someone asks for it. |
Where it belongs
The natural home is the Copilot in the Admin Center (MVP – Vlad Catrinescu) because that is where administrators already decide what AI may touch.
🚨 Ask for the SharePoint PG – Plugins, the new home for policies?
Enterprise store plugins for Copilot in SharePoint (roadmap ID 567669, preview August 2026, general availability December 2026) bundle skills, MCP servers, and other capabilities into an installable package that administrators deploy organization-wide or users add themselves from the store.
So, the policy model could be extended to plugins, and the cleanest way is to make the policy part of the deployment. The SharePoint Product Team does not need to invent anything here. The mechanism already exists in the same cloud, with the same customers, and is administered by many of the same people.
Connectors become tools, environments become sites, and the three groups stay as they are, but upgraded and evolved to meet the needs of 2026!
The admin surface exists; the enforcement point exists because something already decides which tools to render in that panel; and the billing hooks exist because something already meters them.
Hope that helps!
Renewed Revolution!
Leave a Reply