SharePoint Copilot Agents: Licensing, Limits & Use Cases
What Copilot agents grounded in SharePoint actually are, how Copilot Studio builds them, what they cost, and three real-world use cases you can deploy in weeks.
What Copilot agents grounded in SharePoint actually are, how Copilot Studio builds them, what they cost, and three real-world use cases you can deploy in weeks.
Microsoft 365 Copilot is one form of AI built on your organisation's data. Copilot agents are the next layer — purpose-built AI assistants scoped to a specific domain, data source, or business task. A SharePoint Copilot agent is an agent that knows your SharePoint content and can answer questions about it in natural language, take structured actions (submit forms, update lists), and operate embedded in Teams, SharePoint pages, or as a standalone chatbot. This guide explains what they are, what they cost, and how to build them.
A Copilot agent is an AI assistant with a defined scope, data sources, and behaviour instructions. Unlike Microsoft 365 Copilot — which can see your entire M365 environment — an agent is intentionally focused. You tell it:
| Declarative Agent | Custom Agent (Copilot Studio) | |
|---|---|---|
| Built with | Microsoft 365 Copilot interface or agent builder; no-code configuration | Microsoft Copilot Studio (low-code canvas with topics, entities, Power Automate integration) |
| Grounding | SharePoint sites, documents, and M365 Graph | SharePoint, web URLs, custom APIs, Dataverse, and 1000+ Power Platform connectors |
| Actions | Limited to Microsoft Graph actions; cannot call external APIs without plugins | Full Power Automate integration; can call any connector or HTTP API |
| Complexity | Low — suitable for Q&A over a document corpus | Medium to high — suitable for multi-turn conversations, slot filling, and transactional actions |
| Licence | Best for users with Microsoft 365 Copilot, which provides full agent experiences in supported Microsoft 365 apps | Uses Copilot Studio licensing: prepaid Copilot Credits, pay-as-you-go billing, or zero-rated usage for Microsoft 365 Copilot licensed users in supported Microsoft 365 experiences |
Microsoft Copilot Studio (previously Power Virtual Agents) is the low-code platform for building custom Copilot agents. It provides a canvas-based conversation designer where you define topics (conversation subjects), entities (structured data the agent extracts from user messages), and actions (what the agent does when a topic is resolved).
Copilot Studio connects to SharePoint as a knowledge source through two mechanisms:
Important: Licensing for Copilot agents is a frequently changing area as Microsoft continues to evolve its AI offering. Always verify current pricing at microsoft.com/en-us/microsoft-copilot-studio/pricing before committing to a deployment.
| Licence type | What's included | Best for |
|---|---|---|
| Copilot Studio prepaid Copilot Credits | Prepaid monthly credit capacity, commonly purchased in 25,000-credit packs; unused credits do not carry over | Predictable internal or external agent usage where you want committed capacity |
| Copilot Studio pay-as-you-go | Usage is metered through an Azure subscription and billed based on actual Copilot Credits consumed | Teams that want to start without a large upfront capacity purchase |
| Microsoft 365 Copilot licence | Includes SharePoint agents and Copilot Studio agent capabilities in Microsoft 365 Copilot, Teams, and SharePoint; supported Microsoft 365 usage is zero-rated against Copilot Studio meters | Organisations already deploying Microsoft 365 Copilot who want focused agents over SharePoint and Microsoft Graph content |
| External / anonymous users | Typically uses Copilot Studio prepaid or pay-as-you-go capacity, depending on channel and configuration | Customer-facing chatbots, partner portals, and public website agents |
Microsoft shifted Copilot Studio billing from simple message counts to Copilot Credits. Credits reflect the work an agent performs: retrieving knowledge, generating an answer, calling tools, or completing actions. A simple policy answer usually consumes fewer credits than a multi-step conversation that searches SharePoint, calls a Power Automate flow, and confirms the result. Use Microsoft's Copilot Studio usage estimator and current licensing guide before budgeting.
📄 Copilot Studio licensing requirements — learn.microsoft.comAn agent grounded in the HR SharePoint site that answers employee questions about leave policies, benefits, performance review processes, and onboarding procedures in plain English — without employees having to search the intranet. The agent is embedded as a Teams bot and available 24/7. Questions it cannot answer from the knowledge base are logged and forwarded to the HR inbox as structured tickets via Power Automate.
SharePoint knowledge source: HR Policies library, Benefits site, Employee Handbook pages. Actions: Submit a query to HR (creates a SharePoint list item). Result: ~60% reduction in repetitive HR email volume in the first 90 days post-deployment.
An agent that handles the first-line IT support questions that account for 70% of helpdesk ticket volume: password reset instructions, VPN setup, software installation guides, known issue status. The agent is grounded in the IT Knowledge Base SharePoint site and the IT Wiki. When it cannot resolve an issue, it collects structured information (issue type, priority, affected system) and creates a ServiceNow ticket via a Power Automate flow, returning the ticket number to the user.
SharePoint knowledge source: IT Knowledge Base site, IT Procedures library, Known Issues list. Actions: Create ServiceNow ticket (Power Automate), check ticket status (Power Automate HTTP action). Result: 40% deflection of Level 1 IT tickets from human agents.
An agent embedded in the Procurement SharePoint site that answers questions about purchasing policies, approval thresholds, preferred suppliers, and contract templates. It can look up supplier records from a SharePoint Suppliers list (via Power Automate) and return contact details, contract expiry dates, and preferred status. Procurement staff use it instead of emailing the team for basic lookups, freeing the team for strategic sourcing work.
SharePoint knowledge source: Procurement Policies library, Supplier Contract library. Actions: Look up supplier by name (Get items from Suppliers list via Power Automate). Result: Estimated 3 hours/week saved per procurement manager on information lookup tasks.
OceanCloud designs and deploys Copilot Studio agents grounded in SharePoint — from simple policy Q&A bots to complex multi-action agents integrated with ServiceNow, Salesforce, and Dynamics 365. Typical delivery: 4–6 weeks.
Start Your Copilot Agent Project