Insights

What is Microsoft Copilot Studio? An honest guide for businesses.

What is Microsoft Copilot Studio? It is Microsoft's low-code platform for building AI agents and automated workflows that connect to your company's data and systems, and for publishing them to Teams, Microsoft 365 Copilot, your website and other channels. It is part of the Power Platform, offers more than 1,500 prebuilt connectors and bills usage in Copilot Credits.

Plan a strategic call
Our automation service

Automation

20 min read

Microsoft uses the word Copilot for a whole family of products, which makes it easy to buy the wrong one. Copilot Studio is the one you build with. Microsoft 365 Copilot is the assistant your employees use, and Copilot Cowork is the newer agent they hand whole tasks to. Mixing them up leads to licences nobody needs and agents that never leave the test panel.

This guide explains what Copilot Studio is, what you can build with it, what it costs, when to use it and where it falls short. Every feature and price below was checked against Microsoft Learn, Microsoft’s licensing guide and its pricing pages in November 2026. Microsoft renames products and changes prices often, so treat the figures as a snapshot and confirm them before you sign anything. We build client automations on n8n and Claude, and our founder is an official n8n Ambassador, so the comparison at the end comes from daily practice, with that bias declared.

What is Microsoft Copilot Studio, in plain terms?

Microsoft Copilot Studio is a graphical, low-code studio for building and managing AI agents and workflows. That is Microsoft’s own definition on Microsoft Learn. You build agents and workflows, connect them to your organisation’s data and systems, and publish them to the channels where people already work.

Copilot Studio is the successor to Power Virtual Agents, which Microsoft folded into it. Since then it has grown well beyond chatbots. App creation is now in preview as well, so you can build an interface, a workflow and an agent in one place.

You work in it through a web app at copilotstudio.microsoft.com. You can start from a blank canvas, but the quickest start is a plain-language description of the goal. Copilot Studio drafts the agent or workflow, and you refine it from there.

An out-of-focus figure at a bright desk sketches connected process steps on paper beside a closed laptop, the planning that comes before building in Microsoft Copilot Studio.

How Copilot Studio differs from Microsoft 365 Copilot

The short version: Microsoft 365 Copilot helps people work, Copilot Studio is where you build what does the work.

ProductWhat it isWho uses itHow you pay (November 2026)
Microsoft 365 CopilotAI assistant inside Word, Excel, PowerPoint, Outlook and TeamsEvery employee who has a licencePer user per month
Copilot ChatSecure AI chat for workEmployees with an eligible Microsoft 365 planNo extra cost, custom agents are metered
Copilot CoworkAgent that plans and completes whole tasks across Microsoft 365Employees with Microsoft 365 CopilotUsage-based, in Copilot Credits
Agent Builder (Copilot Studio Lite)Quick, lightweight agent builder inside Microsoft CopilotBusiness users and small teamsPart of Microsoft Copilot
Copilot StudioPlatform to build, govern and publish agents, workflows and appsMakers, IT teams and developersCopilot Credits, or included for internal use with Microsoft 365 Copilot

Agents you create in Agent Builder can be copied to Copilot Studio when they need more control, governance or channels.

What can you build with Copilot Studio?

Copilot Studio has three main building blocks: agents, workflows and agent flows, with apps added in preview. You can use each one on its own or combine them. A workflow can call an agent to handle one step, and an agent can call a flow as a tool.

Agents

An agent is an AI assistant that follows your instructions, draws on the knowledge you connect and uses tools to take action. Agents work in multiple languages across Teams, Microsoft 365 Copilot, websites, mobile apps and other channels. Some agents can get their own account, so they can work proactively on shared processes such as onboarding a new employee.

Microsoft’s own examples include an IT support agent that handles ticket intake and triage, a recruitment assistant that screens and ranks candidates, a contract review agent that flags risks and a balance sheet reconciliation agent that detects variances.

Topics

Topics are the scripted part of a conversation. On the standard harness, a topic is a piece of dialogue you design with trigger phrases, questions, conditions and steps. The agent uses natural language understanding to match a request to the best topic. When no topic fits, it can still generate an answer from its connected knowledge.

Use topics where the answer must be exactly right every time: a returns procedure, a booking flow, an escalation to a human.

Tools

Tools let an agent act instead of only talk. Older guides call them actions. You can add:

  • Prebuilt connectors to Microsoft and non-Microsoft services, for example to send an email through Outlook or post a message in Teams.
  • Custom connectors to your own systems.
  • Agent flows, predefined sequences of steps the agent can trigger.
  • Prompts, single model calls for a specific task.
  • REST APIs, by selecting the endpoints the agent may call.
  • MCP servers, through the Model Context Protocol.
  • Computer use, which lets the agent operate websites and desktop apps through their interface, clicking buttons and filling in fields.

With generative orchestration switched on (the default for new agents), the agent picks the right tool itself, based on each tool’s name and description. So writing clear tool descriptions is part of the build.

Knowledge

Knowledge grounds an agent’s answers in your own content. Copilot Studio supports public websites, uploaded documents, SharePoint, Dataverse and enterprise data indexed through Microsoft Copilot connectors. For SharePoint and Dataverse, the agent signs in with the user’s own Microsoft Entra ID, so people only get answers from content they are already allowed to see.

Connectors and the Power Platform

Copilot Studio is part of Microsoft’s Power Platform, next to Power Automate and Power Apps, and they share one connector library. Microsoft lists more than 1,500 prebuilt connectors, including Salesforce, Dropbox and Google services, and you can build custom connectors for anything else.

That shared foundation matters. Agents can store structured data in Dataverse, reach on-premises data through Power Platform connectors and are managed from the Power Platform admin center. There, IT sets the data policies that decide which connectors and channels makers may use. If your company already runs Power Automate flows and Power Apps, Copilot Studio fits into an environment, permission model and governance setup your IT team already knows.

Workflows and agent flows

Workflows are automations you build in a drag-and-drop designer, or by describing them so Copilot Studio can generate and validate them. Each step can combine agents, tools and fixed logic, with built-in testing and human approval steps.

Agent flows are the established format. They feel like Power Automate, run as standalone automations or as a tool for an agent, and can include prompts and human review steps.

Harnesses: the engine underneath

Everything you build runs on a harness, the runtime that decides when to call the model, which tools to use and how the work is billed. Microsoft Learn describes three:

HarnessBest forBilling
GitHub Copilot harnessMulti-step business processes that need reasoning across tools and files (Word, Excel, PowerPoint, PDF)Copilot Credits for tokens, tools and the harness, from the moment you build
Customer Conversation harnessCustomer service over website chat or a phone number, with escalation to a humanCopilot Credits, usage-based
Standard harnessRule-based agents and structured conversations built from topicsCopilot Credits per answer and action, after you publish

On top of these, Microsoft’s pricing page lists a Copilot Chat harness for extending Copilot Chat with your own agents, included for internal users with Microsoft 365 Copilot. Despite the name, the GitHub Copilot harness is not the GitHub Copilot service. Microsoft states that customer data is not sent to or processed by GitHub Copilot when agents run in Copilot Studio.

Model choice

Copilot Studio lets you choose the model behind an agent, including OpenAI models and Anthropic’s Claude models. Microsoft’s own billing example even uses Claude Opus 4.7 as a reasoning model. For custom scenarios, Microsoft points to the more than 11,000 models in Azure AI Foundry, which are billed separately from Copilot Credits.

How much does Copilot Studio cost in November 2026?

Copilot Studio is billed in Copilot Credits, a usage currency that replaced “messages” on 1 September 2025. Internal agents used by people with a Microsoft 365 Copilot licence are largely included. Everything else is paid per credit, prepaid or pay-as-you-go. These are Microsoft’s US list prices as of November 2026, from the Copilot Studio pricing page and the Copilot Studio licensing guide, with the euro amounts from Microsoft’s Dutch pricing page.

OptionPrice (November 2026)What you get
Included with Microsoft 365 CopilotMicrosoft 365 Copilot from $30 per user per month, paid yearly (from €26 excluding VAT on Microsoft’s Dutch page)Build and use internal agents inside Microsoft 365 on the Copilot Chat and standard harness at no extra cost
Copilot Credit pack$200 per pack per month (€173.30 on Microsoft’s Dutch page)25,000 Copilot Credits a month, pooled across your tenant
Pay-as-you-go$0.01 per creditBilled monthly to an Azure subscription, no commitment
Pre-purchase plan5% to 20% discount, by tierOne year of prepaid Copilot Credit Commit Units
TrialFreeBuild and test agents, but you cannot publish them

Smaller organisations, up to 300 users, can choose Microsoft 365 Copilot Business instead. It is an add-on to an eligible Microsoft 365 business plan, listed from $21 per user per month, with a first-year promotional price of $18 on annual plans bought between 1 July and 31 December 2026.

Two details in the fine print deserve attention. Unused credits do not roll over, because Microsoft enforces prepaid capacity per month. And overspending switches agents off: when a tenant reaches 125% of its prepaid capacity, its agents are blocked, even mid-conversation, and most users see “This agent is currently unavailable. It has reached its usage limit. Please try again later.” Linking a pay-as-you-go meter prevents this, at pay-as-you-go prices.

What one credit buys

On the standard harness, Microsoft charges a fixed number of credits per activity. From the Copilot Credits billing rates:

Agent activityCopilot Credits
Classic answer (a reply you wrote yourself)1
Generative answer2
Agent action, for example a trigger, reasoning step or tool call5
Tenant graph grounding (search across your Microsoft 365 data)10
Agent flow, per 100 actions13

A reasoning model adds a premium of 10 credits per 1,000 billed tokens on top of the activity rate, and one answer can involve thousands of tokens. In Microsoft’s own example, a single follow-up question to a website support agent running on a reasoning model costs 141 credits in premium alone, against 2 credits for a plain generative answer.

For employees with a Microsoft 365 Copilot licence, these activities cost nothing when the agent runs under their identity inside Microsoft 365. There are exceptions: agent flows are only free when an agent triggers them for a licensed user, and computer-using agents are not covered by the licence.

The GitHub Copilot harness works differently. It charges credits for model tokens, tools (including knowledge and MCP) and the harness itself, and billing starts while you build. Generating an agent from a description, testing it and running evaluations all consume credits.

A worked example: a support agent on your website

Microsoft’s own billing example is a customer support agent on a website that answers questions from return policies and product manuals. An average conversation uses four classic answers and two generative answers, and 900 customers use it every day.

That comes to (4 x 1 + 2 x 2) x 900 = 7,200 credits a day, or 216,000 credits in a 30-day month. On pay-as-you-go at $0.01 per credit, that is about $2,160 a month. With prepaid packs of 25,000 credits you need nine packs, which costs $1,800 a month.

Change the volumes to see how the bill moves. Agent actions, such as a tool call or a reasoning step, cost 5 credits each, so a few per conversation raise the total quickly.

Copilot Studio credit estimateEnter your daily conversations and what an average conversation uses on the standard harness. Rates: classic answer 1 credit, generative answer 2, agent action 5.
Credits per day
7,200
Credits per 30-day month
216,000
Pay-as-you-go per month
$ 2,160
Packs of 25,000 credits
9

Worked example based on Microsoft's own billing example. US list prices as of November 2026: $0.01 per credit on pay-as-you-go, $200 per pack of 25,000 credits. Usage by licensed internal users and reasoning-model premiums are left out.

For a busy service channel, that can be reasonable. The lesson is that the bill grows with every answer and every action, so model your volumes before you launch. Microsoft offers a Copilot Studio agent usage estimator for exactly this.

Costs outside the credit price

Power Automate cloud flows use Power Automate licensing, not Copilot Credits. Dataverse storage above the included capacity is billed separately: on pay-as-you-go, database storage above 1 GB per environment costs $48 per GB per month, according to Microsoft’s pay-as-you-go meters. Your own models from Azure AI Foundry are billed separately as well. And somebody has to own the environments, data policies and capacity, which costs administration time even if it never appears on an invoice.

What are the strengths of Copilot Studio?

Copilot Studio’s biggest strength is that it lives where Microsoft 365 users already work, under the security model IT already runs. There is no new app to roll out: agents appear in Teams and Microsoft 365 Copilot, so adoption starts in a familiar place. Security and governance come from the Microsoft stack, with Microsoft Entra ID, Defender, conditional access, audit logs in Microsoft Purview and per-environment data policies built in. Microsoft states that Copilot Studio supports data residency alignment and major compliance standards.

If your employees already have Microsoft 365 Copilot, many internal agent interactions cost nothing extra. The low-code tooling also goes deeper than it first looks, with natural-language building for speed, topics for control, evaluations before and after publishing, and release pipelines with approval gates for development, test and production. On top of that you get the mature connector library it shares with Power Automate and Power Apps, and a choice of models from OpenAI, Anthropic and Azure AI Foundry.

What are the limits of Copilot Studio?

The main limits are licensing complexity, costs that scale with usage and a firm tie to Microsoft’s cloud.

Licensing is hard to read. There are several harnesses with different billing, credit packs, pay-as-you-go, pre-purchase units and inclusion rules that depend on the licence, the trigger and the channel, and Microsoft itself refers readers to a separate licensing guide for the complete picture. Costs scale with every interaction, because answers, actions and reasoning tokens are all metered. That is fine for internal use under Microsoft 365 Copilot, but customer-facing agents and high-volume automations need a careful budget. On the GitHub Copilot harness you even pay while you build, since building and testing consume credits too.

Then there is the tie to Microsoft. You cannot run Copilot Studio on your own servers: your agents, flows and Dataverse tables live on Microsoft’s platform, and moving away later means rebuilding them. Connectors reach other vendors, but features such as tenant graph grounding and user-level permissions on knowledge assume your data lives in Microsoft 365.

The product also changes fast. Power Virtual Agents became Copilot Studio, actions became tools, messages became Copilot Credits, Agent Builder became Copilot Studio Lite, harnesses arrived and apps are in preview. That is good for features and harder for documentation, training and budgets.

When to use Copilot Studio, and when not to

Use Copilot Studio when a recurring process inside Microsoft 365 needs a conversational front door: approved knowledge, a few controlled actions and people who already work in Teams. Skip it, or start elsewhere, when the process itself is unclear, the data is messy or the work is fully predictable.

Microsoft’s own product page draws the line well: combine traditional workflow automation for deterministic processes with agentic reasoning for non-deterministic ones. A leave request that always follows the same five steps is a flow. A question about which leave rules apply to a part-time employee abroad is an agent.

Two open notebooks on a linen-covered table, one with a strict grid of identical boxes and one with loose handwritten notes, the choice between a fixed flow and an agent in Copilot Studio.

Copilot Studio fits best when:

  • You are a Microsoft 365 company and many people already have Microsoft 365 Copilot licences, so internal agents in Teams and SharePoint add little extra cost.
  • Your knowledge lives in SharePoint, Dataverse or Dynamics 365 and every answer must respect each user’s own permissions.
  • IT wants one governance plane: Entra ID, Purview audit logs and Power Platform data policies for everything.
  • Business teams will build and maintain simple agents themselves, without developers.

Hold off when:

  • The process is undocumented. An agent cannot follow a process the business has not agreed on. Write down the steps, owners and exceptions first.
  • Permissions are messy. An agent surfaces whatever users can already reach, so overshared SharePoint sites become visible fast.
  • Decisions are high-stakes. Hiring, lending, legal and medical decisions belong with trained people; use the agent for intake and routing.
  • The work is a fixed sequence. A deterministic job needs a workflow tool, such as Power Automate or n8n, not a conversation.
  • Nobody owns it after launch. Agents need content upkeep, analytics review and cost monitoring.

Copilot Studio vs n8n: an honest comparison

Full disclosure: our founder Marrallisa Kreijkes is an official n8n Ambassador, so we have a bias, and we have worked to keep this comparison fair.

Copilot Studio and n8n solve overlapping problems from opposite ends. Copilot Studio starts from conversational agents inside Microsoft 365. n8n starts from workflow automation across any system, with AI agents as one of its building blocks.

Copilot Studion8n
Starting pointAI agents and workflows inside Microsoft 365Workflow automation across any system, with AI agent nodes
HostingMicrosoft’s cloud onlyn8n Cloud, or self-hosted on your own server or a European host
Pricing modelCopilot Credits per answer, action and token, included for internal use with Microsoft 365 CopilotCloud plans priced per complete workflow execution, regardless of the number of steps, with unlimited users and workflows; self-hosted Community Edition free for internal use
AI modelsOpenAI, Anthropic and Azure AI Foundry modelsAny provider you connect, including self-hosted models, paid directly to the provider
Integrations1,500+ Power Platform connectors, deepest across MicrosoftHundreds of integrations, plus HTTP requests and JavaScript or Python code for any API
GovernanceEntra ID, Purview and Power Platform data policies built inSSO, multiple environments and Git version control on the Business and Enterprise plans, log streaming on Enterprise
Who buildsBusiness makers and IT inside the Power PlatformTechnical teams or an automation partner

The n8n details come from its pricing page and licence FAQ, as of November 2026.

When n8n fits better

The strongest argument for n8n is self-hosting and data control. You can run n8n on your own infrastructure or with a European host, so you decide where workflow data lives and which AI provider sees it. For sensitive data, that alone can settle the choice.

Cost at volume comes next. n8n Cloud charges per complete workflow run, however many steps it has. A self-hosted instance has no per-run licence fee at all: you pay for the server and for the AI tokens you use, directly to the provider. A high-volume process that would consume credits for every answer and action can cost considerably less this way.

n8n is also built for a multi-vendor stack: HubSpot, Shopify, Notion, Slack, Google Workspace, your accounting package and a custom API in one flow. And it leaves you free to pick a different model per step, drop into code where low-code stops and keep workflows in Git.

n8n has honest downsides too. Self-hosting means you own updates, backups and security, or hand them to a hosting partner. It is less native inside Teams, building it well takes technical skill, and SSO and Git require paid plans. The free Community Edition licence also does not allow you to let clients build their own workflows on your instance.

If you go this route, pick a partner who designs from your processes instead of reselling templates. Here is what a real automation agency does. Already running it? Our free upgrade checklist for version 3.0 shows what to check before you update.

Or use both

Many Microsoft companies do not need to choose. A Copilot Studio agent can be the front door in Teams, while n8n does the heavy lifting across non-Microsoft systems. Copilot Studio agents can call REST APIs and MCP servers as tools, and n8n can expose a workflow through a webhook or its MCP Server Trigger. The agent asks, the workflow executes. See how the MCP Server Trigger works.

How to choose: five questions

  1. Where does your data live? Mostly in Microsoft 365 points to Copilot Studio. Spread across many vendors points to n8n, or to both.
  2. Who will use it? Employees with Microsoft 365 Copilot licences get included usage. Customers on your website are paid per credit.
  3. How many runs a month? Model the credits with Microsoft’s estimator, then compare them with an execution-based price.
  4. Where must the data be processed? If it has to stay on your own infrastructure, Copilot Studio is not an option.
  5. Who maintains it after launch? Power Platform makers in-house, or a technical owner or partner?

How we help

So, what is Microsoft Copilot Studio for your business: the right platform, or one licence too many? Viralistic is a strategic digital partner in Amsterdam, and we answer that question from your process, not from a product sheet: first the work and the value you want from it, then the platform. We build automations with n8n and Claude, govern them from day one, and tell you plainly when a Microsoft tool you already pay for is the better fit. When the real gap is how your team works with AI, we also run AI trainings and adoption sessions. Explore our automation service, see how we govern automations and AI agents, or plan a strategic call to map your first use case.

Frequently asked questions

Is Microsoft Copilot Studio free?

Not for production use. A free trial lets you build and test agents, but you cannot publish them. People with a Microsoft 365 Copilot licence can build and use internal agents on the Copilot Chat and standard harness at no extra cost. Everything else runs on Copilot Credits: $200 for 25,000 a month, or $0.01 each on pay-as-you-go.

Is Copilot Studio included in Microsoft 365?

Only with a Microsoft 365 Copilot licence, which includes Copilot Studio for internal agents used inside Microsoft 365 at no extra cost. Without it, staff can still use agents, but their usage is paid in Copilot Credits. Publishing to external channels, serving unlicensed users or using the GitHub Copilot harness needs Copilot Credits from a standalone plan.

What’s the difference between Microsoft Copilot and Copilot Studio?

Microsoft 365 Copilot is the assistant employees use inside Word, Excel, Outlook and Teams, paid per user. Copilot Studio is the platform where you build your own agents and workflows, which can then appear inside Microsoft 365 Copilot, Teams or your website. Most companies start with Copilot and add Studio when a process needs its own agent.

What is Copilot Studio used for?

Copilot Studio is used to build AI agents and automations for specific business processes. Microsoft’s own examples include IT support agents that handle ticket intake and triage, recruitment assistants that screen candidates, contract review agents and balance sheet reconciliation. It suits structured, repeatable work where answers come from your own documents and people already work in Microsoft 365.

What is the downside of using Copilot Studio?

The main downsides are complex licensing, costs that grow with every answer and action, and lock-in to Microsoft’s cloud. Customer-facing agents and reasoning models can become expensive without capacity planning, and agents stop at 125% of prepaid capacity unless pay-as-you-go is linked. It also needs Power Platform governance from the start.

What is the pay-as-you-go pricing for Copilot Studio?

It is $0.01 per Copilot Credit, as of November 2026. You link an Azure subscription to a Power Platform environment through a billing policy, and Microsoft bills the credits your agents used at the end of each month, with no upfront commitment. A generative answer costs 2 credits, so 1,000 generative answers cost about $20.

What are workflows in Copilot Studio?

Workflows are automations you build in a drag-and-drop designer or by describing them in plain language. Each step can combine agents, tools and fixed logic, with built-in testing and human approval steps. Agent flows are the older format: they resemble Power Automate and can run on their own or as a tool for an agent.

Do you need to code to use Copilot Studio?

No. Copilot Studio is low-code: business users can describe an agent in plain language, add SharePoint or website knowledge and publish to Teams without writing code. Integrations with custom APIs, data policies, environments and production governance still need IT or a technical partner, especially once an agent can change data in other systems.

How do I build an agent using Copilot Studio?

Open copilotstudio.microsoft.com and describe the agent you want in plain language, and Copilot Studio drafts it. Add knowledge such as SharePoint sites, public websites or files, then add tools: connectors, agent flows, a REST API or an MCP server. Write topics where answers must be exact. Test it, run evaluations, then publish to Teams, Microsoft 365 Copilot or your website.

Written by

Marrallisa Kreijkes

Founder of Viralistic and official n8n Ambassador

Marrallisa leads strategy, design, search and automation for premium brands from Amsterdam. She has trained teams at Volkswagen and speaks at n8n and Anthropic events. Want to talk through your situation? Book a call with her directly.

Keep reading
All insights ↗