The HR manager answers the same twenty questions every week: how many vacation days do I have left, where's the leave form, when does the bonus get paid. Someone in IT built an agent in an afternoon, pointed it at the policies folder in SharePoint and published it in Teams. It worked. Two months later there were eleven more agents, nobody knew who maintained them, and one of them was reading a folder it shouldn't have.
Building Copilot Studio agents no longer takes code, and that's exactly why you need some order first. Copilot Studio agents can answer questions about your documents, serve customers on your website or run multi-step processes. This article covers the kinds of agents you can build today, how they're licensed and the minimum governance worth putting in place before you publish the first one.
What Copilot Studio is today
Copilot Studio is Microsoft's tool for building AI agents and workflows in a visual editor, on top of Power Platform. You can start by describing in plain language what the agent should do, add knowledge sources (SharePoint, websites, files, Dataverse) and connect it to other systems through connectors, MCP or other agents.
One recent change matters when deciding what to build. Microsoft now runs everything built in Copilot Studio on one of three "harnesses", the runtime that sits between your design and the AI model. According to the Microsoft Learn documentation on harnesses, updated in October 2026, the harness you pick changes what the agent can do and how it's billed.
For very simple agents, for personal use or a small team, there's also Agent Builder, an experience inside Microsoft Copilot for putting together lightweight agents without leaving the chat.
Types of agents you can build
| Harness | What it's for | Example |
|---|---|---|
| Standard | Agents built on topics and rules you define, with predictable answers | Internal help desk that answers common questions and routes simple requests |
| GitHub Copilot | Multi-step processes: the agent takes a goal, breaks it into tasks, uses tools and recovers when something fails. Creates and edits Word, Excel, PowerPoint and PDF files | Accounts payable: read invoices, match them to purchase orders and route exceptions for approval |
| Customer Conversation | Customer service over chat or voice, with sub-agents and handoff to a person | Agent on the website or on a phone number that hands off to a rep when it can't solve the issue |
One point that tends to confuse people: the "GitHub Copilot" harness is an orchestration framework inside Copilot Studio. Microsoft states that customer data isn't sent to the GitHub Copilot service and that Copilot Studio's privacy and data residency commitments still apply.
In practice, most companies start with standard harness agents: questions about internal policies, the product catalog, procedures. They're cheap to maintain and easy to audit. Agents that run whole processes have more impact, but also more risk, because they act on real systems.
Copilot Studio licensing: how you pay
This is where budgets most often go wrong. Copilot Studio isn't charged per maker. It's charged by consumption, and the unit is Copilot Credits, which replaced "messages" on September 1, 2025 with no change to quantities or rates, according to the licensing guide on Microsoft Learn.
Current payment options, at list prices in US dollars from the official Copilot Studio pricing page:
- Capacity pack: 25,000 Copilot Credits for US$200 a month, tenant-wide.
- Pay-as-you-go: US$0.01 per credit according to the Azure pricing page, billed to an Azure subscription linked to the environment.
- Pre-purchase plan: credits prepaid for one year, with discounts of up to 20% depending on volume.
Each response or action uses a different number of credits depending on how complex it is. That's why Microsoft publishes an agent usage estimator, and it's worth running before you commit budget. Watch two rules: unused credits don't carry over to the next month, and if you go over the capacity you bought, the service can be blocked.
What Microsoft 365 Copilot includes
If your company already pays for Microsoft 365 Copilot (US$30 per user per month on annual billing, list price), those users can build and use internal agents inside Microsoft 365 on the standard harness at no extra cost. And when they use agents in Copilot Chat, Teams or SharePoint, generative answers and searches over tenant data don't consume credits.
You need a separate Copilot Studio license when you want to:
- publish agents to external channels, such as your website, an app or social platforms;
- let people without a Microsoft 365 Copilot license use them;
- build autonomous agents or use the GitHub Copilot harness, which consumes credits.
For makers, the Copilot Studio user license is free, but the tenant needs a prepaid credit subscription. The trial license lets you build and test agents, not publish them. If you've already read how Microsoft Copilot is licensed for business, this is the missing piece.
Prices in Chile can vary with your agreement type with Microsoft and the exchange rate, so treat them as a reference and get a quote before deciding.
Minimum governance before you publish
Letting anyone build agents is good for adoption and bad for control. The scene at the top happens faster than you'd think. This is the minimum we'd set up before the first agent goes to production:
- Decide who can build. In the Power Platform admin center you can assign the Copilot Studio authors role to an Entra security group. Admins can also block self-service trial sign-ups.
- Separate environments. One for testing and one for production, with someone responsible for promoting agents between them.
- Set up data policies. Data policies for agents sort connectors into business, non-business and blocked, and let you require user authentication and restrict channels and triggers.
- Review permissions on your sources. An agent connected to SharePoint answers with whatever the user can see. If permissions are a mess, the agent will make that obvious.
- Keep an inventory. Agent name, owner, sources it reads, channel where it's published and date of the last review. A spreadsheet is fine to start.
- Monitor consumption. The Power Platform admin center shows agent usage and costs. Check it monthly, especially on pay-as-you-go.
If the agent will handle personal data about customers or employees, add what Chile's Law 21.719 requires on purpose and security. We go into more detail in enterprise AI agents: security and minimum governance.
Where to start
Pick a narrow case with repeated questions and tidy sources. HR, the IT help desk and sales support are usually good candidates. Build the agent in a test environment, ask five people to use it for two weeks and look at the questions it couldn't answer. Often those failures point to outdated documents more than to the agent.
Only with that learning in hand does it make sense to think about agents that take actions or serve customers. And when you get there, estimate credit consumption before the first invoice, not after.
Frequently asked questions
Do I need to know how to code to use Copilot Studio?
No. You can build agents by describing them in plain language and configuring them in a visual editor. For integrations with your own systems or custom connectors, it helps to have someone technical involved.
Does Microsoft 365 Copilot include Copilot Studio?
It includes building and using internal agents inside Microsoft 365 on the standard harness. To publish outside Microsoft 365, give access to unlicensed users or use the GitHub Copilot harness, you need Copilot Studio with credits.
How much does a Copilot Studio agent cost?
It depends on consumption. The 25,000-credit pack costs US$200 a month and pay-as-you-go is US$0.01 per credit, at list price. What each response uses varies with its complexity, so the official estimator is the place to start.
Build your first agent the right way
At Disrupsoft we assess which scenarios will have the most impact in your company, set up Copilot in your Microsoft 365 environment and train your teams so agents get used and maintained. If you want to start with a concrete case, let's talk about Copilot and Microsoft 365.
