A SharePoint agent answers questions about selected sites, pages and document libraries. Our recommendation from Copilot and agent pilot projects: start directly in SharePoint, with the site agent or an FAQ agent for a single, well-maintained library such as the current travel-expense rules, and bring in Copilot Studio only when the use case requires it. Before that, sort out tenant hygiene, licensing and access.
1. Clarify the prerequisites
SharePoint agents are a cloud feature of Microsoft 365, meaning SharePoint Online, not SharePoint Server on-premises. Three things should be in place before the first agent:
- Structure: Agents only work with what they find and adopt the existing permissions. Sites and libraries therefore need a clear structure.
- Classification: Sensitivity labels and DLP policies are maintained. Sensitive content that is misclassified can find its way into agent answers.
- Knowledge area: For the first agent there is a site or library with a clear owner, current documents and clear permissions. Outdated versions have been removed from the visible knowledge base.
Tenant hygiene comes first. It is the lever with the greatest effect.
2. Clarify licensing
Microsoft licenses agents in several ways. Prices and regional availability change; Microsoft lists current prices on its Microsoft 365 Copilot pricing page. The logic:
- With a Microsoft 365 Copilot licence: creating and using agents is covered.
- Pay-as-you-go: For users without a Copilot licence there is a usage-based model, billed through an Azure subscription and Microsoft Cost Management. They get access through a configured pay-as-you-go policy. This makes sense when only part of the workforce works with agents regularly.
- Microsoft 365 Copilot Chat: Microsoft provides Microsoft 365 tenants with a Copilot Chat experience at no additional cost. Which agent scenarios it includes depends on the licence mix.
You can see which licences are active in the Microsoft 365 admin centre under “Billing > Your products”. Users also need access to the agent file and to the underlying content.
3. Control availability
According to Microsoft, agents in SharePoint need no separate activation. Control sits in three places:
- Microsoft 365 admin centre: check the assigned licences.
- SharePoint admin centre: under “Settings > Microsoft 365 Copilot and AI”, check availability for sites. Pay-as-you-go additionally requires an Azure subscription.
- Site: The site agent is available by default. Site owners can switch it off per site or release it specifically.
Microsoft describes the current conditions in its administration guide for agents in SharePoint.
4. Control access
- Permissions: Agents inherit the existing site and item permissions. Anyone without access to a source gets no answer from it through the agent; an agent does not grant new read permissions.
- Agent file: The agent is stored as an
.agentfile in SharePoint. File permissions determine who can use or edit it. - Restricted Access Control (RAC): Restrict access to sensitive sites specifically so that their content does not appear in Copilot and agent answers.
- DLP through Microsoft Purview: DLP policies prevent agents from processing classified content.
- Approved agents: Site owners mark approved
.agentfiles as “approved” so that they appear in the site's agent picker.
5. Create the agent: two routes
Route A: directly in SharePoint
This route is enough for most use cases. Every modern site has a Copilot icon at the top right with a preconfigured site agent that is ready to use. With edit rights, you create your own agent directly in the site or library via “Create an agent”; this creates an .agent file that you can share. You need neither a separate tool nor code.
Route B: through Copilot Studio
If an agent is to use external connectors, have its own topics or custom actions, or be integrated into Power Automate flows, Copilot Studio is the tool. It brings more options, more effort and its own licensing logic.
Our rule: start with route A. Switch to route B when the use case really requires it, not as a precaution.
6. Test the agent
- 1Describe the agent's purpose and sources in a few sentences.
- 2Test five real questions, including one that cannot be answered. A question such as “Which expense rule applies to rail travel?” can only be answered reliably if the source is clear.
- 3Check answers and sources with two accounts that have different permissions.
- 4Decide who updates the sources and re-checks answers after changes.
Add further sites only once these checks work.
What to bear in mind
Menu paths, licensing models and prices change; Microsoft's administration guide and the current pricing page are authoritative. An agent respects existing permissions but does not correct them: overly broad sharing remains a risk and should be cleaned up before the pilot.

