How to build a Copilot Studio agentHow to build an agent with Copilot Studio

Updated October 2026. Written by Power Platform MS.

What Copilot Studio is

Microsoft Copilot Studio is the low-code tool for building agents: conversational assistants that answer questions from content you choose and, where you allow it, take actions in other systems. It sits alongside Power Apps and Power Automate, uses the same connectors and is governed through the same Power Platform admin controls.

An agent is made of four parts:

• Knowledge: the sources it answers from, such as SharePoint sites, uploaded documents, public web pages or Dataverse tables.
• Topics: structured conversations for things that must happen the same way every time, such as collecting details for a request.
• Actions: Power Automate flows and connectors that let the agent look something up or create a record.
• Channels: where people use it, typically Microsoft Teams, a website or a customer app.

Step 1: Pick one job, not ten

The most common reason agents disappoint is scope. Start with one job that has a clear audience, a reliable source of answers and a measurable result. Good first candidates include:

• HR and policy questions for staff, grounded on the current handbook
• IT service desk questions and standard requests in Teams
• Customer questions answered from approved help articles, with handover to a person

Before building, write down:

• Who will use it and where they already work
• The ten questions it must answer well
• Which sources are approved and who owns them
• What should happen when it cannot help
• How you will judge success after a month

Step 2: Get the content right first

An agent is only as good as what it is grounded on. Out-of-date or contradictory documents produce out-of-date or contradictory answers. Put approved content in one controlled location, remove superseded versions and give each source an owner. This step often takes longer than the build and is worth every hour.

Step 3: Build the agent

1. Create the agent in the right environment (not the default one) so it can be managed and moved between development, test and production.
2. Write clear instructions: its purpose, tone, what it must not do and when to hand over.
3. Add knowledge sources and turn off general web knowledge unless you genuinely want it.
4. Add topics for anything that must follow a fixed path, such as collecting details for a request.
5. Add actions through Power Automate for lookups or record creation, with the minimum permissions needed.
6. Configure authentication so internal agents use the signed-in user's identity.

Step 4: Test like a sceptical user

Test with the real questions people ask, not the ones you hope they ask. Check:

• Answers are correct and cite the right source
• The agent says it does not know rather than guessing
• Permissions hold: test with accounts that should not see certain content
• Actions fail gracefully when a connected system is unavailable
• Handover to a person includes the conversation so far

Copilot Studio includes evaluation tools for running a set of test questions repeatedly. Build that test set early and re-run it after every change.

Step 5: Roll out in stages

Launch to a pilot group of perhaps 10 to 30 people first. Review conversation analytics weekly: unanswered questions show where content is missing, and abandoned conversations show where the design is wrong. Widen access once the agent is answering the pilot group reliably.

Licensing and cost

Copilot Studio is licensed mainly on the capacity your agents consume, rather than purely per user, and some use is included for people with Microsoft 365 Copilot licences. Premium connectors used by actions can carry their own licensing. Microsoft revises these models often, so treat any figure you read online with caution and check current Microsoft pricing for your scenario.

Build cost depends mostly on the number of actions and integrations, not the number of questions. A knowledge-only agent is the cheapest starting point. Our packages page lists from-prices in GBP, and a licensing review will tell you what you need to buy, if anything.

Mistakes to avoid

• Grounding on everything. Pointing an agent at a whole intranet guarantees confident answers from outdated pages.
• No owner. Content changes. Without a named owner reviewing unanswered questions, quality drifts within months.
• Building in the default environment. It makes governance and moving to production harder later.
• Skipping handover. An agent that cannot pass someone to a person creates frustration, especially with customers.
• Too many jobs at once. Prove one, then add the next.

When Copilot Studio is the wrong tool

If people mainly need help with their own email, documents and meetings, Microsoft 365 Copilot may serve them better. If you need a highly customised AI application with your own models or complex orchestration, a pro-code approach on Azure may fit better. An honest scoping call will tell you which.

Read more on the Copilot Studio service page, see how we build a Copilot Studio HR agent or an IT helpdesk agent, read Copilot Studio pricing explained, or download our free getting started with Copilot Studio guide.