BestOnline.ToolsBestOnline.Tools
Automation and agents

Microsoft Copilot Studio

Microsoft Copilot Studio review: business agents and pricing

Microsoft Copilot Studio builds business agents with company knowledge and app tools. Explore its features, runtime options, credit pricing and alternatives.

Business agentsMicrosoft ecosystemManaged deployment

Free trial availableAccount required

Product previewView original
Microsoft’s official Copilot Studio example shows agent creation, business templates and learning resources.
Microsoft’s official Copilot Studio example shows agent creation, business templates and learning resources.Microsoft
Access
Free trial available
Example plan
USD 200 / monthStandalone capacity pack — annual billing
Available on
Web, API
OVERVIEW

Build agents around business knowledge and connected apps

Microsoft Copilot Studio builds agents that combine business knowledge, app tools and automated processes. A maker can describe an agent in natural language and refine its instructions, topics, knowledge and connections. It suits internal service assistants, information lookup and business processes that involve several systems. Its close fit with Microsoft 365 and Power Platform is especially useful when those services already hold the organization’s documents, records and user identities.

The product offers three operating runtimes, called harnesses. The standard harness supports authored topics, flows and generative orchestration: it can choose tools and search knowledge dynamically, or follow explicitly designed paths. The GitHub Copilot harness adds larger shared context, longer tasks, document creation, reusable skills and persistent memory. Copilot chat extends Microsoft Copilot with company knowledge. The GitHub-named harness is part of Copilot Studio, rather than a GitHub Copilot coding subscription.

Knowledge sources give an agent business material to reference, including documents, public websites and supported enterprise sources such as SharePoint and Dataverse. Availability depends on the environment and licensing. In the standard runtime, authenticated SharePoint, Dataverse and enterprise connector searches use the asking user’s access. Uploaded reference documents have a different access basis. A maker-provided knowledge source also differs from a file attached by an end user to one conversation.

Tools let an agent act on information. Power Platform connectors supply app actions, while REST API endpoints and MCP servers extend access to custom services. Standard agents can use prompts and agent flows, and invoke tools explicitly from a topic or let generative orchestration select them. Workflows in the GitHub Copilot experience provide repeatable steps for approvals, transformations and business logic. An organization’s data policies can restrict which connections are available.

Authentication and approval are separate settings. Standard-runtime tools use the end user’s credentials by default, with maker-provided connections available when configured. A tool can ask the chat user for confirmation before running, but this setting defaults to No. Approval and information-request steps can also form part of a process; the Human in the loop connector’s information requests and multistage approvals are in preview. Adding an agent does not automatically put every app action behind a human gate.

Event triggers allow agents to respond to business changes without a person starting a chat. Their configured tools, instructions and permissions define the actions they can take. Agent flows combine repeatable steps with agent calls, but a flow started autonomously has different Microsoft 365 Copilot inclusion rules from one called by an authenticated licensed user. This makes the way work starts relevant to its cost as well as its behavior.

Publishing options depend on the runtime. The current GitHub Copilot experience supports Microsoft Copilot, Teams, demo websites and web embedding. Its SharePoint, external messaging and native-app channels are not all available. MCP and Agent2Agent client channels are previews limited to early-release environments. Standard agents have their own established publishing options, so a broad product-wide channel list does not describe every agent you can build.

Copilot Credits pay for usage rather than seats or a fixed number of successful tasks. Standard-runtime features have different rates and can stack within one interaction; bringing an external model adds its separate provider billing. GitHub Copilot runtime costs include models, tools and the runtime itself, starting during authoring. The $200 capacity pack is a monthly allowance with annual billing, while Azure pay-as-you-go bills actual consumption. Microsoft 365 Copilot inclusion applies to eligible internal scenarios, not every agent or trigger.

Power Platform administrators manage environments, capacity, maker access and sharing controls. Data policies can block tools, and tenant settings can restrict publishing. Agent activity and Monitor views show execution and credit consumption; tenant-level usage is available in the admin center. Purchased capacity has enforcement rules, so unused monthly credits expire and insufficient capacity can prevent further work. Copilot Studio is a managed cloud service, with connected providers and other Power Platform resources forming part of the overall deployment.

Best for

  • Organizations building agents around Microsoft 365 and Power Platform
  • Teams combining business knowledge, app actions and controlled processes
  • Enterprises publishing internal assistants or customer-facing agents

Limitations

Runtime choice changes billing, supported channels and available features. The standard-runtime trial permits building and test-panel use but cannot publish agents. GitHub Copilot runtime authoring and testing consume credits. Microsoft 365 Copilot does not include every agent scenario: external use, autonomous flow triggers and computer use have separate billing rules. Tool confirmation is off by default, and Human in the loop connector actions remain in preview. Prepaid capacity enforcement can interrupt new agent requests; unused monthly pack credits do not roll over.

WHAT YOU CAN DO

Microsoft Copilot Studio features

Low-code business agents

Combine natural-language setup with instructions, authored topics, business knowledge and connected actions.

Three agent runtimes

Use standard topics and generative orchestration, longer-running GitHub Copilot agents, or Copilot chat extensions.

Company knowledge and user access

Reference supported documents and enterprise sources, with source-specific authentication and environment requirements.

Connectors, APIs and MCP tools

Connect Microsoft and third-party services through app actions, REST endpoints and compatible MCP servers.

Agent flows and event-driven work

Combine reusable process steps with agent decisions and configured events that start work outside a conversation.

Tool confirmation and approval steps

Configure confirmation for standard tools and add information requests or multistage approvals where supported.

Files, skills and memory

The GitHub Copilot runtime can create and edit business documents, reuse skills and retain context across tasks.

Managed publishing and usage controls

Publish to runtime-supported channels and administer environments, sharing, data policies and credit capacity.

PLANS & PRICING

Microsoft Copilot Studio pricing

Standalone capacity packs cost $200 per pack per month, billed annually, with 25,000 monthly Copilot Credits pooled across the tenant. Pay-as-you-go is $0.01 per credit through Azure; prepaid commitment options are also available. Credits measure feature usage rather than complete conversations or tasks. The GitHub Copilot runtime also charges for building, previews, testing and evaluations, while standard-runtime test-panel usage is not billed. Eligible internal use by authenticated Microsoft 365 Copilot subscribers has separate inclusion rules. Unused capacity-pack credits expire monthly; additional provider, Dataverse or other service usage can add costs.

Example plans.

Standalone capacity pack — annual billing

USD 200 / month

Current documented product

Plan details

One tenant-wide pack with 25,000 Copilot Credits per month, USD 200/month billed annually. Unused monthly credits do not roll over. Credits measure feature usage, not a fixed number of complete tasks. Other billing routes and additional service charges apply.

Pricing updated 2026-10-10. Prices may change.View current pricing →
Technical specifications

Automation and agents

FeatureMicrosoft Copilot Studio
Connectors and tool access
Power Platform connectors, REST endpoints, MCP tools and agent flows/workflows. Standard tools can run under end-user or maker-provided credentials; policies can restrict availability.Configured runtime, environment, authentication and data policies
Triggers and scheduling
Conversation requests and configured event triggers. Agent-flow billing inclusion differs between an authenticated licensed agent-call trigger and other triggers.Configured events, permissions and licensing scope
Human approval controls
Standard tool confirmation defaults to No and can be enabled. Human in the loop information requests and multistage approvals are preview process steps.Configured per-tool confirmation or process approvals
Hosting and deployment
Managed cloud environments. GitHub Copilot runtime supports Copilot, Teams, demo websites and web embedding; MCP/A2A publication is early-release preview. Standard channels differ.Runtime-specific publishing and early-release channel scope
Execution accounting
Tenant credits: standard feature rates can combine per interaction; GitHub Copilot runtime consumes credits during building, testing, evaluation and use. Eligible Microsoft 365 internal usage has separate rules; external model costs are separate.Capacity packs billed annually, monthly credit expiry, or Azure consumption/commit routes
API access
SupportedREST API and MCP tool connections; external MCP/A2A agent channels are runtime-specific preview
MORE AI TOOLS

Microsoft Copilot Studio alternatives

Explore platforms for enterprise agents, visual AI applications and app automation.

Gemini Enterprise Agent Platform

Gemini Enterprise Agent Platform

Google Cloud agent development and runtime services for technical teams.

Dify

Dify

Visual AI applications with managed Cloud or self-hosted Community deployment.

n8n

n8n

Connected workflows and AI agents with Cloud or self-hosted operation.

COMMON QUESTIONS

Microsoft Copilot Studio FAQs

Is Microsoft Copilot Studio free?

The standard-runtime trial lets you create agents and use the test chat panel, but it does not allow publishing. Eligible Microsoft 365 Copilot users have included internal capabilities. Standalone production use requires the relevant capacity, consumption or licensing arrangement.

How much does Microsoft Copilot Studio cost?

A tenant-wide pack costs $200 per month, billed annually, for 25,000 monthly Copilot Credits. Azure pay-as-you-go is $0.01 per credit, and prepaid commitment plans are available. Unused monthly pack credits do not roll over. Actual consumption depends on the runtime, models and features used; a credit is not a complete task.

Is Copilot Studio included with Microsoft 365 Copilot?

Eligible employee-facing standard and Copilot chat usage can be included when the user is authenticated with a Microsoft 365 Copilot license, subject to fair use. External agents, the GitHub Copilot runtime and computer use have separate billing. Agent-flow inclusion applies to the agent-call trigger for an authenticated licensed user, not every autonomous trigger.

What is the difference between Copilot Studio harnesses?

Standard supports authored topics, flows and dynamic generative orchestration. GitHub Copilot supports longer tasks, larger shared context, files, skills and memory. Copilot chat extends Microsoft Copilot with company knowledge. They differ in channels and billing: GitHub Copilot runtime authoring, previews and evaluations also consume credits.

Can Copilot Studio require approval before an action?

Yes. A standard-runtime tool can ask the end user before running, although confirmation is off by default. Processes can also contain information requests or approval steps. The Human in the loop connector’s information requests and multistage approvals are preview actions; approval must be configured rather than assumed for every action.

Can Copilot Studio use SharePoint and company documents?

Yes. It supports business knowledge sources including documents and SharePoint, with other sources dependent on runtime, environment and licensing. Standard-runtime SharePoint and supported enterprise searches use user authentication to respect the asking person’s source access. Uploaded reference files and files attached to one conversation have different scope.

Does Microsoft Copilot Studio support MCP?

Yes. MCP servers can provide tools to agents, alongside connectors and REST APIs. Publishing a GitHub Copilot-runtime agent for an external MCP or Agent2Agent client is a separate preview capability available only in early-release environments.

What are the best Microsoft Copilot Studio alternatives?

Gemini Enterprise Agent Platform provides Google Cloud agent development and runtime services. Dify focuses on visual AI applications and knowledge workflows, with Cloud or Community deployment. n8n combines app workflows and AI with Cloud or self-hosted operation. Copilot Studio is particularly attractive when Microsoft 365 data and Power Platform administration are central to the project.

Is this your product? Claim this page to update your listing.