Copilot agents explained: what they are and which ones a small business needs.

What are Copilot agents?

Copilot agents are focused AI assistants that run inside Microsoft 365. Each one has its own instructions, its own knowledge (such as a SharePoint folder) and sometimes actions it can take, like sending an email or updating a record. You use them in Copilot Chat, Teams and the Office apps, alongside general Copilot.

Think of plain Copilot as a smart generalist who knows a bit about everything in your Microsoft account. An agent is the same engine given one job, one set of documents and one set of rules. A quoting agent only reads your price lists and past quotes. An onboarding agent only answers from your staff handbook. That narrowness is the point: it gives better answers on its job and stays out of everything else.

Microsoft's own developer documentation describes agents as assistants that "retrieve information, summarize data, or even take actions like sending emails or updating records". Some are built by Microsoft and come ready to use. The rest you build yourself, either in a few minutes in Agent Builder or properly in Copilot Studio.

What types of Copilot agent are there?

There are three kinds a business owner will meet: agents Microsoft has already built, like Researcher and Analyst; simple agents you build yourself in Agent Builder, which Microsoft calls declarative agents; and fuller agents built in Copilot Studio, which can connect to other systems, run on triggers and work outside Microsoft 365.

Under the hood Microsoft splits agents into two technical families. Declarative agents use Copilot's own model and engine, so they inherit Microsoft 365's security and compliance settings and need no hosting. Custom engine agents bring their own logic and sometimes their own AI model, can act on a schedule without anyone asking, and can live outside Microsoft 365. You do not need to remember the terms. You need to know that the first kind is quick and contained, and the second kind is a proper build.

Which licence do you need for Copilot agents?

With only the free Copilot Chat that comes with Microsoft 365, simple agents built on instructions or public websites cost nothing extra, but any agent reading your company's SharePoint is charged per use in Copilot Credits. With a paid Microsoft 365 Copilot licence, using agents carries no extra usage charge.

That split matters more than most owners realise. The agents that are actually useful nearly always read your own files, which is exactly the part that is metered on the free tier. Microsoft sets this out in its licensing and cost guide for Copilot extensibility.

Prices are from Microsoft's Australian Microsoft 365 Copilot pricing page and Copilot Studio pricing page. Enterprise plans are quoted separately. For a fuller breakdown of every Copilot plan, see our Microsoft Copilot pricing guide for Australia.

Can you build a Copilot agent without Copilot Studio?

Yes. Agent Builder sits inside Microsoft 365 Copilot Chat and Teams, and you build an agent by describing what you want in plain English, pointing it at some SharePoint files or websites, and testing it. It cannot take actions in other systems. For that, Microsoft has you copy the agent across to Copilot Studio.

Agent Builder works from microsoft365.com/chat, office.com/chat and the Teams desktop and web apps, but not on mobile. A few limits worth knowing before you start, all from Microsoft's Agent Builder overview:

• No actions. It can answer and draft. It cannot update your CRM, send a quote or create a job.
• Not in Teams chats. You cannot drop an Agent Builder agent into a Teams group chat or a one-on-one chat.
• Permissions are manual. If you share an agent with the whole organisation, you still have to make sure everyone can open the SharePoint files it reads, or it will quietly answer with less.
• Your admin decides. An administrator can switch Agent Builder off for everyone, so check before you promise staff anything.

For a sole trader or a small office, this is the right place to start. Build one agent for one boring, repeated question, see if staff use it, then decide whether anything deserves a bigger build.

When do you need a Copilot Studio agent instead?

You need Copilot Studio when the agent must do something, not just answer: read a new document as it arrives, update a SharePoint list, call another system through a connector, run on a schedule, or talk to customers on your website. Those jobs are beyond Agent Builder and need a proper build, testing and someone who owns it.

Copilot Studio is Microsoft's low-code tool for agents and workflows. It connects to other systems through prebuilt or custom connectors, combines agents with automations, and publishes to Teams, Copilot, websites and other channels. Microsoft also lets some agents run with their own account, so they can work through a recurring job without someone typing a prompt.

Low-code does not mean no work. A Studio agent that touches live data needs the same things any business system needs: clear rules, tested edge cases, someone to fix it when a connector breaks, and a running cost you understand before you switch it on. That is the work our Copilot Studio builds take on, inside the Microsoft account you already own.

What are good Copilot agent examples for a small business?

The best first agents answer a question staff ask every week from documents you already have: a policy and handbook agent, a house-style writing agent, a quoting assistant reading your price lists, or a job-history agent over past projects. Start with one, prove it gets used, then build the next.

• Handbook and policy agent (Agent Builder). Answers "how many days' notice for leave?" or "what is our process for a site incident?" from the documents in SharePoint, with a link to the source.
• House-style writer (Agent Builder). Drafts proposals, tender responses and client emails in your tone, from your best past examples.
• Quoting assistant (Copilot Studio). Reads an incoming enquiry, checks it against your price lists, and drafts a quote for a person to approve.
• Compliance register (Copilot Studio). Reads each new permit or contract and logs the obligations and due dates in one list, with reminders.
• Enquiry triage (Copilot Studio). Sorts the shared inbox, flags the urgent ones and drafts first replies.

If you want more worked examples, our Copilot Studio examples for small businesses go through real builds step by step. And if your systems sit outside Microsoft, like Xero, ServiceM8 or a trade job app, an agent built on another platform may fit better. Our page on AI agents for Australian businesses covers those.

Are Copilot agents safe for business data?

Declarative agents, the kind you build in Agent Builder, run on Copilot's own engine and inherit Microsoft 365's security, compliance and permission settings. They only see what the person using them can already open. Custom agents that run outside Microsoft 365 put more of the security responsibility back on whoever builds them.

The bigger risk in a small business is usually permissions, not Microsoft. If a SharePoint site is shared with everyone, any agent reading it will happily show it to everyone. Tidy who can see what before you point an agent at a folder. And if you work under a regime like defence security, NDIS or health privacy, settle where the data is allowed to go before you choose a tool, not after.