Copilot Studio is Microsoft’s tool for building your own AI agents: assistants that answer from your SharePoint files, take actions in Outlook or Dynamics 365, and increasingly run on their own when something happens, such as a new file landing in a folder. If your company already pays for Microsoft 365 Copilot, it is the most direct way to turn those licences into automation. This guide covers what to build first, how the billing works, and the mistakes we see in Malaysian teams.
Two kinds of agent, and why the difference matters
Microsoft now draws a clear line between two agent types.
- Declarative agents run on Copilot’s own models and orchestration. You build them in Agent Builder inside Microsoft 365 Copilot, with no code, and they live in Copilot, Teams, Word, Excel and Outlook. They only act when a user asks.
- Custom agents are built in Copilot Studio proper. They can use your own orchestration and models, call other agents, run outside Microsoft 365, and act without a user through event triggers: a new SharePoint item, a new OneDrive file, a completed Planner task, or a schedule.
My rule of thumb: start in Agent Builder for a knowledge assistant, move to Copilot Studio the moment you need a trigger, an external channel or an action in another system.
What it costs in 2026
Microsoft 365 Copilot is listed at US$30 per user per month on annual billing for enterprise plans. Microsoft’s Malaysian page quotes business plans in US dollars too, with the Copilot Business add-on at US$18 on promotion (normally US$21). Copilot Studio usage is metered in Copilot Credits, which replaced “messages” in September 2025. A prepaid pack is US$200 a month for 25,000 credits, or you can pay as you go through an Azure subscription.
| What the agent does | Credits used |
|---|---|
| Classic answer (scripted topic) | 1 |
| Generative answer | 2 |
| Agent action (calls a tool or flow) | 5 |
| Tenant graph grounding (searches your M365 data) | 10 |
| Agent flow, per 100 actions | 13 |
Source: Microsoft Learn, Copilot Studio billing, September 2026.
The detail that saves money: when an employee who holds a Microsoft 365 Copilot licence uses an agent under their own identity, most of these actions are not charged, within fair-use limits. Autonomous agents and agents published to a public website or app are different; they need Copilot Studio capacity. We cover the full maths in our Copilot Credits pricing guide.
Your first agent: a SharePoint policy assistant
A first build that pays back in a week
- 1Pick one document libraryHR policies or SOPs in a single SharePoint site. Clean, current, owned by one person.
- 2Create the agent in Agent BuilderDescribe its job in plain language, add the SharePoint site as knowledge, and write three example questions.
- 3Test with ten real questionsUse the questions staff actually send HR on WhatsApp. Note every wrong or vague answer and fix the source document, not the prompt.
- 4Publish to Teams for one departmentStart with 20 people. Watch which questions it cannot answer.
- 5Add an action in Copilot StudioOnce trusted, let it create a leave request or raise a ticket. This is where credits start to matter.
Autonomous agents: powerful, and easy to get wrong
Event triggers are what make Copilot Studio more than a chatbot. An agent can read every invoice PDF dropped into a folder, extract the fields and post them to a list. Two cautions from Microsoft’s own documentation are worth repeating. Every trigger payload is billed as usage, so a noisy folder can burn credits quietly. And triggers run on the agent maker’s credentials, so an agent built by a finance manager can see what that manager can see. Build production agents under a service account, and ask IT to review connector policies before anything goes live.
Malaysian compliance note. If an agent processes customer or employee personal data, the PDPA amendments in force since 2025 apply: mandatory breach notification and, for larger data sets, a Data Protection Officer. See our PDPA and AI guide.
Where Copilot Studio is not the answer
If most of your work lives outside Microsoft 365, in Shopee, a local accounting package, WhatsApp and Google Sheets, a model-agnostic platform such as n8n will connect more of it for less money. Copilot Studio shines when your data already sits in SharePoint, Outlook, Teams and Dynamics. For a broader view of the Microsoft stack, read how Copilot fits the Microsoft 365 ecosystem.
Two days building governed agents in Copilot Studio and Agent 365 across Outlook, Teams, SharePoint and Excel. Limited to 20 participants.
Next public class: 5–6 November 2026 at Worq TTDI · seats available
HRD Corp claimable. AITraining2U is an HRD Corp registered training provider. Our public and in-house courses are claimable under the HRD Corp Claimable Courses (SBL-KHAS) scheme, and we prepare the grant paperwork with you. See HRDC-claimable AI training: courses, costs and how to claim.