Maturity Model for Copilot: Agents
Like what you see??
"Ask Sympraxis" is a bi-weekly webinar series, where we discuss an array of topics and answer your submitted questions. Join us by downloading our recurring calendar event. You can also join us directly in the meeting without downloading the event.
Do you have a challenge similar to this episode and want to learn more? Are you interested in learning more about Sympraxis Consulting and the work we do? Fill in our or Work With Us form and we will get back to you.
See a listing of Ask Sympraxis episodes by topic covered: Topic List, Series List, or a full listing Archive
Exploring the Maturity Model for Copilot Agents
In this episode of Ask Sympraxis, we explore the evolving landscape of Microsoft Copilot Agents - specifically, how organizations can think about Copilot agents through a maturity model lens. Microsoft’s messaging is shifting, focusing more on agents that accomplish specific tasks rather than Copilot as one monolithic thing. This prompted us to consider how teams might approach agent adoption and development in stages.
Maturity model approach to agents
As with many digital tools, we can map the journey of agent adoption across a 100 - 500 maturity model scale. At the 100 level, organizations rely on out-of-the-box solutions, like ChatGPT or Microsoft-provided agents. At 200 users begin creating basic SharePoint agents to meet individual needs. At 300, organizations start thinking more strategically about agent use across teams. The 400 level sees agents embedded into core business workflows, and at 500, a full ecosystem emerges - agents working in tandem to execute tasks and drive process automation.
Level 100: Out of the box & third-party agents (ready made)
Even if you don’t have a Copilot license, agents already exist within your Microsoft 365 ecosystem. Organizations should be mindful of governance, as these tools can impact workflow even without formal rollout. With a Copilot license, additional agents like Analyst, Researcher, and Visual Creator become available, providing users with ready-to-use functionality.
Level 200: SharePoint agents (custom no code agents)
SharePoint agents are a great entry point into building custom solutions without code. Introduced about a year ago, these agents become standard when new sites are created (assuming a Copilot license is present). Users can layer up to 20 knowledge sources - such as files, folders, or libraries - onto a single agent. Anyone with file creation permissions on the site can build one, making them both accessible and manageable. One important tip: always name your agents clearly and specifically for the best results as you don’t want 50 agents called “Documents Agent”.
Level 300: Microsoft Copilot Studio (custom low code agents)
Copilot Studio Agents offers a low-code, visual development environment - like the Power Platform - that allows for the creation of both conversational and non-conversational agents. With drag-and-drop simplicity, users can build custom logic and deploy agents more broadly across interfaces. Unlike SharePoint agents, Copilot Studio Agents enable more flexible and enterprise-level deployments with broader data connectivity and publishing options.
The team revisits the differences between SharePoint agents and Copilot Studio Agents, highlighting the advanced capabilities of the latter. Copilot Studio agents offer a more scalable solution for businesses seeking deeper customization.
Level 500: Declarative and custom engine (custom - pro code)
For those working in pro-code environments, understanding MCP (Model Context Protocol) is key. MCP lets developers connect agents to API endpoints containing toolsets that can evolve over time. As the MCP server updates with new tools, connected agents automatically gain those capabilities. This approach significantly expands what an agent can do without having to rebuild it manually.
Costs & licensing thoughts
Licensing is shifting to include both traditional user-based models and pay-as-you-go (pay-go) options. However, you must have at least one Copilot user license to enable the semantic index feature - after which you can activate pay-go. Microsoft has also introduced a new cost estimator (currently in preview). It’s important to note that pro-code solutions are billed through Azure, so organizations need to be aware of their cloud spend when scaling up.
Takeaway
As Microsoft’s ecosystem evolves, understanding and strategically planning how you adopt Copilot agents is critical. Whether you’re just getting started or already exploring pro-code options, this maturity model helps frame where you are - and where you could go next. For more in-depth discussion, check out the full episode and don’t forget to view the slide deck for a visual summary.
All Resources
- Maturity Model for Microsoft 365
- Get started with SharePoint agents - Microsoft Support
- Ask Sympraxis about SharePoint Agents
- Copilot Developer Camp
Do you have any questions for us? Continue the conversation on BlueSky with the hashtag #AskSympraxis and mention @sympraxisconsulting.com.