If you’ve been following the rapid evolution of the Microsoft 365 ecosystem, you know one thing: Copilot is no longer just a single assistant. It’s becoming an entire family of Copilot agents, each with different capabilities and use cases.

What many people don’t realize is that there are four declarative agent types today that can work with SharePoint content. They all follow the same principle: you describe the agent’s purpose, instructions, and knowledge, and the system handles the reasoning behind the scenes.

Here are the four types:

• SharePoint agents
• Copilot Studio Lite
• Copilot Studio declarative agents
• The M365 Agents Toolkit

Let’s walk through each one and then show you exactly how to get started with the right method for your organization.

1. SharePoint Agents

SharePoint agents are the native Copilot agents built directly into SharePoint. Microsoft may label them as Copilot agents in SharePoint, but “SharePoint agents” is the more intuitive name and the one I prefer.

These agents operate inside SharePoint experiences and rely on the site’s structure, permissions, and content to deliver contextual, grounded responses. Because they inherit SharePoint’s security model automatically, they only surface information users already have permission to access.

SharePoint agents are ideal when:

• You need Copilot help directly inside the SharePoint site where work happens
• Your knowledge base lives in SharePoint libraries, lists, and pages
• You want zero friction in setup or deployment
• You want users to get grounded answers using the content they already work with

SharePoint agents focus on conversational assistance, knowledge interpretation, summarization, navigation guidance, and answering questions grounded in SharePoint content.

How to Get Started With SharePoint Agents

If you’re starting here, you’re choosing the simplest, most integrated path.

Where to begin:

• Learn how agents work inside SharePoint and Microsoft 365 Copilot Chat.
• Review examples and guided experiences that run directly within SharePoint sites.

Official Microsoft Learn Links:

• Get Started With Agents (training module): https://learn.microsoft.com/en-us/training/modules/get-started-no-code-copilot-agents-sharepoint/
• My own SharePoint Agent Quick Start

2. Copilot Studio Lite

Copilot Studio Lite is the renamed successor to what was previously known as Agent Builder. It represents the lightweight, simplified way to build declarative agents without the full surface area of Copilot Studio.

Some organizations need more flexibility than SharePoint agents offer, but not the full feature set of Copilot Studio. That’s where Copilot Studio Lite lands. It gives you simple, standalone conversational agents that can still access SharePoint content through Microsoft 365’s unified data layer.

Use Copilot Studio Lite when:

• You want a simple conversational Copilot agent
• You need SharePoint grounding without the complexity of full Studio
• Your use cases revolve around Q&A, guidance, and content interpretation
• You want something easy to configure, deploy, and maintain

How to Get Started With Copilot Studio Lite

Copilot Studio Lite maps to the current Agent Builder experience inside Microsoft 365 Copilot.

Where to begin:

• Start with Copilot Studio Lite to define your agent’s instructions, tone, and knowledge.
• Use guided prompts to connect your agent to SharePoint content sources.

Official Microsoft Learn Link:

• Agent Builder in Microsoft 365 Copilot: https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/agent-builder
• My own Copilot Studio Lite Quick Start

3. Copilot Studio Declarative Agents

Inside full Copilot Studio, you can create more sophisticated declarative agents with improved instruction design, richer multi-turn dialog structures, and deeper configuration options.

This is still a declarative, no‑code model. It’s just more capable.

You’d choose Copilot Studio declarative agents when:

• You need a more advanced conversational experience
• You want to blend SharePoint content with other Microsoft 365 sources
• You want to shape deeper rules about tone, behavior, and interpretation
• You need more structured guidance for the agent’s reasoning

These agents are ideal for department-wide assistants, specialized knowledge assistants, or any scenario where context spans beyond a single SharePoint site.

How to Get Started With Copilot Studio Declarative Agents

If you’re going deeper into customization, this is the entry point.

Where to begin:

• Review the main Copilot Studio documentation to understand the environment.
• Learn how to add SharePoint as a knowledge source for your agent.
• Explore the guides for building, configuring, and refining declarative agents.

Official Microsoft Learn Links:

• Microsoft Copilot Studio documentation: https://learn.microsoft.com/en-us/microsoft-copilot-studio/
• Add SharePoint as a knowledge source: https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-add-sharepoint

4. M365 Agents Toolkit

The M365 Agents Toolkit is the most advanced and enterprise-ready declarative framework available. It’s designed for organizations that need Copilot agents operating across multiple apps and services, with SharePoint as just one of several knowledge sources.

The toolkit shines when:

• You want cross-app Copilot agents that operate across Microsoft 365
• You need enterprise-grade extensibility, governance, and observability
• Your scenarios require scale beyond a single app or department
• You want to build agents with deep integration into Microsoft’s broader ecosystem

This option gives you the most headroom for growth and the most control over how your Copilot agents behave across the Microsoft 365 environment.

How to Get Started With the M365 Agents Toolkit

For enterprise builders, this is your starting line.

Where to begin:

• Read the toolkit overview to understand its architecture and capabilities.
• Install the toolkit inside Visual Studio Code to start building.
• Explore the Agent 365 SDK for deeper enterprise-level integrations.

Official Microsoft Learn Links:

• Microsoft 365 Agents Toolkit Overview: https://learn.microsoft.com/en-us/microsoft-365/developer/overview-m365-agents-toolkit
• Agents Toolkit fundamentals in VS Code: https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/agents-toolkit-fundamentals
• My own Beyond Low-Code course

Which Declarative Agent Type Should You Use?

Here’s the decision map in plain English:

• SharePoint agents When you want Copilot experiences embedded directly inside SharePoint.
• Copilot Studio Lite When you need a simple, standalone conversational agent with access to SharePoint.
• Copilot Studio declarative agents When you need richer behavior and deeper configuration across Microsoft 365.
• M365 Agents Toolkit When you’re building enterprise-scale agents that span multiple apps.

None of these agents perform task automation or workflow building. They excel at conversation, reasoning, interpretation, summarization, and grounded knowledge retrieval across SharePoint content.

Final Thoughts

SharePoint has always been the backbone of organizational knowledge. Declarative Copilot agents are the bridge that turns that knowledge into something active and interactive.

Whether you need a lightweight helper, a mid-level custom agent, or an enterprise-scale Copilot counterpart, there’s a declarative option that fits your needs… and all four can use SharePoint as a primary knowledge source.

We’re entering a new era where SharePoint isn’t just storing content. It’s powering intelligent experiences across the organization.

Need help solving your business cases with agentic AI? Contact me below!