Copilot Notebooks: what the knowledge bundle is good for and what it isn't
Copilot Notebooks bundle documents for AI querying. Learn which limits apply to source count and licensing.
SharePoint agents answer questions from your sites. How to set them up, which license you need, what a question costs, and where the limits lie.

A SharePoint agent is an AI assistant that answers questions from the pages, libraries, and files of a SharePoint site, using only what the person asking is allowed to see there. It is created directly on the site, without Copilot Studio, and can be used in SharePoint, Teams, and Microsoft 365 Copilot. For many organizations, this is the fastest way to a knowledge assistant on their own documents. This article explains setup, license, and billing, as well as the limits. As of: September 2026, all information according to the linked pages on Microsoft Learn.
Anyone with a Copilot license who may create files on the site is allowed to create a SharePoint agent. Licensed users can use it at no extra cost, and everyone else via pay-as-you-go, according to Microsoft $0.01 per message at 12 messages per question. The agent sees exactly what the person asking sees.
A SharePoint agent is a so-called declarative agent that uses SharePoint sites, pages, and document libraries as a knowledge source. Microsoft describes in the Agent tool comparison overview that these agents run in SharePoint, Teams, and Microsoft 365 Copilot and are aimed at business users without programming skills.
Every eligible site comes with a ready-made agent, reachable via the agent icon in the header. In addition, you can create your own agents for a specific purpose, for example just for the quality manual or just for the product data sheets. Technically, every custom agent is a file with the .agent extension in the "Site Assets" library. The permissions on this file determine who may use or edit the agent (Microsoft Learn: Manage access to agents).
The difference from Copilot Notebooks: a notebook is a personal topic folder, while a SharePoint agent is attached to a site and is there for everyone who may read on it. More on notebooks is in Copilot Notebooks: what the knowledge bundle is good for.
Setup has one page for administration and one for the site. According to Microsoft Learn, SharePoint agents do not need to be activated: as soon as a person has a Copilot license or pay-as-you-go is set up, they are available on eligible sites.
On the site:
For administration, when users without a Copilot license should use the agent (Microsoft Learn: Set up pay-as-you-go):
To create a SharePoint agent, the person needs a Copilot license and the right to create files on the site. To use it, either a Copilot license or pay-as-you-go billing is enough. Without either, nothing works. This is stated in the comparison table from Microsoft Learn.
With pay-as-you-go, Microsoft bills by message. According to the Microsoft pricing overview for pay-as-you-go, one message costs $0.01, and a successful question with an answer consumes 12 messages: 10 for the search in company knowledge and 2 for the generated answer. A question therefore costs $0.12 in calculation. For users with a Microsoft 365 Copilot license, interactive use is included at no extra cost. The costs appear on the Azure bill under the Copilot Studio meter; budgets and alerts can be set in Azure Cost Management.
From what point a Copilot license pays off compared to individual billing depends on how often someone asks questions. The license prices in euros are in our article Copilot licenses and costs.
SharePoint agents are built for clearly defined questions on a single site, not for large or nested applications. Microsoft itself names these limitations (Agent tool comparison overview):
A dedicated knowledge agent makes more sense when the knowledge is not held on a single site, when many employees without a Copilot license ask regularly, or when the agent should do more than just answer. With Copilot Studio, you can build an agent on SharePoint and Dataverse that also triggers actions, see Building a Copilot Agent. For a medical device supplier, we built an agent like this for item and stock inquiries on Dataverse, because the answers came from master data and not from documents.
In the knowledge agent pilot we build a knowledge area in five days, on SharePoint with Copilot Studio or with n8n on your own server, with test questions, test log, and handover. The pilot costs 5,000 euros net at a fixed price, further expansion afterward 1,000 euros net per day. All prices net, plus travel costs and expenses for on-site appointments. No hidden hours. Whether a SharePoint agent is already enough for your case, we tell you honestly in the free initial consultation, 30 minutes.
To create one, yes: according to Microsoft Learn, the person needs a Copilot license and the right to create files on the site. To use it, pay-as-you-go billing, set up by administration through an Azure subscription, is an alternative.
With pay-as-you-go, a successful question consumes 12 messages at $0.01 each, so $0.12 in calculation (as of September 2026, Microsoft Learn). For users with a Microsoft 365 Copilot license, interactive use is included.
No. The answers depend on the permissions of the person asking. If someone has access to the agent but not to a library it uses, content from that library does not flow into the answer.
As a .agent file in the site's "Site Assets" library. Whoever may open the file can use the agent; whoever may edit it can change it.
Founder of NordFlux. Spent four years automating processes at enterprise scale at Dräger, and now brings that depth to the mid-market — pragmatic and with full data sovereignty.
Certifications
Copilot Notebooks bundle documents for AI querying. Learn which limits apply to source count and licensing.
Copilot reveals SharePoint over-permissions that have accumulated over years. Here's how to prepare the rollout cleanly with SAM and RCD.
Since 2025, Copilot Studio has billed in Copilot Credits instead of Messages. Here's how to calculate your agents' actual consumption.
We review permissions, document landscape, and user base with you, and tell you honestly whether the agent on the site is enough or whether a dedicated knowledge agent makes more sense.