A quiet inflection in 2025
Somewhere between Build 2025 and Ignite 2025, agents stopped being a niche concern. Microsoft told its earnings call that customers had built more than a million custom agents in a single quarter — up 130% on the previous one — and that 230,000 organisations, including 90% of the Fortune 500, were now using Copilot Studio. Agents weren't a Microsoft demo any more. They were the Microsoft demo.
Most of the people I work with — adoption leads, IT managers, training functions — are still slightly behind that curve. They've heard the word, they've seen Researcher and Analyst, and they've been told their team will eventually need to build their own. What they don't have yet is a clean mental model for what an agent is, when one is the right answer, and how to govern the explosion that's coming.
Here's the simplest framing that's held up.
An agent is a small, scoped colleague
Copilot is a generalist. It does a bit of everything — drafting, summarising, querying — and you have to remind it of context every time you open a new chat. An agent is the opposite. It's narrow on purpose. It knows one job, has access to a small set of files or systems, and gets called whenever that job needs doing.
Microsoft's own role-based agents are useful examples:
- Researcher is built on OpenAI's deep research model. It writes long-form reports with citations.
- Analyst runs on the o3-mini reasoning model. It does structured data analysis and writes the Python under the hood.
- Facilitator sits in Teams meetings, takes notes in real time, captures decisions and assigns tasks.
- Sales lives in Outlook, Teams and the Copilot pane, and brings CRM-grounded insights to whatever conversation you're in.
Each one is a tightly scoped colleague. None of them tries to be everything.
The two kinds of agent your org will build
Once you start looking, the agents your business actually wants split into two clean categories.
Knowledge agents are grounded in a body of content — a SharePoint site, a Notebook, a few key files — and exist to answer questions about it. The HR policy agent. The sales playbook agent. The bid-writing agent. These are easy to build, often in five minutes, and most of the value is in picking the right content rather than in any clever prompt engineering.
Workflow agents do something. They run a process, call a Power Automate flow, update a record, send a confirmation, escalate when a threshold is breached. These take longer to build, need more thinking about edge cases, and quietly replace half the meetings your team has.
Most teams should start with knowledge agents and graduate to workflow agents only once they've felt the difference between answering and acting.
Building one without writing code
The Agent Builder in Copilot Studio and inside Microsoft 365 Copilot Chat now lets you describe what you want in plain English. I want an agent that answers questions about our supplier onboarding process, using the documents in this SharePoint site, and refuses to answer anything outside that scope. Type that in, point it at the site, name it, ship it.
The instinct most enterprises have when they hear that is to lock it down. Resist that instinct slightly. The whole point of low-friction agent building is that hundreds of small, useful agents emerge from teams who would never have written a Power Automate flow. Lock down the platform too tightly and you kill the upside.
Where governance has caught up
Microsoft's answer to but where does it all end up? is Agent 365, announced at Ignite 2025 and now in public preview through Frontier. It's the control plane for AI agents in Microsoft 365 — registry, access control, visualisation, interoperability and security — sitting on top of Defender, Entra and Purview. If you've been waiting to see what enterprise-grade agent governance looks like, it looks like this.
The practical implication: by the end of 2026, most large enterprises will have a single inventory of every agent running in their tenant, who built it, what it can see, and what it has done. That's a healthier baseline than the world we're in now, where SharePoint agents proliferate quietly and nobody quite knows the count.
A small certification worth knowing about
Microsoft also introduced the AI Agent Builder Associate certification in 2026 (exam AB-620, currently in beta). It's the first certification aimed squarely at the people who are going to build production agents using Copilot Studio. If you have technical staff who keep volunteering to help, it's worth steering one or two of them at it.
What to do this quarter
Three small bets.
- Pick one knowledge agent and ship it. A policy agent, a product FAQ agent, a finance approvals agent. Five minutes to build, three weeks of feedback.
- Stand up a light review process. Not a CAB. A weekly fifteen-minute call where new agents get a quick check before they go wide.
- Make Agent 365 someone's job. Even if it's a fraction of someone's job. The org that wins the next year of AI inside M365 won't be the one with the most agents — it'll be the one that knows where they all are.