AI FinOps · Copilot Studio
When do Copilot Studio agents consume Copilot Credits?
A Microsoft 365 Copilot license does not automatically mean that every use of a Copilot Studio agent is covered without additional Copilot Credits. At the same time, not every agent built in Copilot Studio automatically consumes additional Copilot Credits.
At a glance
The full use case matters.
Copilot Credit consumption is not determined solely by where an agent was created. A Copilot Studio agent can have qualifying runtime usage included in Microsoft 365 Copilot. Conversely, a licensed user can still trigger Copilot Credit consumption.
- 01Which harness powers the agent?
- 02Who uses the agent?
- 03Through which channel and under whose identity?
- 04What triggers the activity?
Interactive guidance
When is a Microsoft 365 Copilot license not enough?
Look at the whole picture and consider the full use case.
Select the four characteristics of your scenario. The result is simplified professional guidance and does not replace a review of the exact configuration.
Which harness?
Who uses the agent?
Where is the agent used?
What starts the activity?
GUIDANCE FOR THIS SCENARIO
May be included in Microsoft 365 Copilot*
The scenario meets key conditions for employee-facing included usage. The exact configuration, invoked capabilities, fair-use limits, and current Microsoft terms must still be checked.
* Simplified professional guidance. The current Microsoft documentation, Product Terms, and exact technical configuration remain authoritative.Start with the architecture
Three harnesses with different purposes and billing models
A harness is the software scaffolding that enables an agent to plan, reason, maintain context, call tools, and complete tasks. The selected harness affects how the agent works, which capabilities it can use, and how usage is billed.
Structured and predictable
For rule-based agents, defined topics, and repeatable processes—such as internal knowledge agents, IT help-desk agents, and agent flows.
Knowledge in the flow of work
For agents that extend Microsoft 365 Copilot Chat with an organization's knowledge in supported Microsoft channels.
Complex and multistep
For reasoning-heavy agents and workflows that break goals into steps, call tools, adapt to changing conditions, and execute complex processes.
Copilot Credits may be consumed by natural-language authoring, Preview, Evaluation, and production runtime. Manual, non-LLM configuration—including manual work in the Build and Monitor tabs—does not consume Copilot Credits. The harness is also not the same as a traditional GitHub Copilot user license.
Then check the license and maker access
Similar names—with different purposes
Microsoft 365 Copilot
A per-user subscription license. It may cover qualifying employee-facing use of agents powered by the standard or Copilot Chat harness when the licensed user works under their own authenticated identity in a supported Microsoft channel.
- Included usage follows the qualifying user and scenario
- Authenticated employee-facing use in supported Microsoft channels
- Fair-use limits, exclusions, and invoked capabilities still matter
Copilot Studio User License / Author role
These are ways to grant maker access. The capacity-pack model uses a Copilot Studio User License. Pay-as-you-go and eligible pre-purchase models use the Copilot Studio Author role.
- Access to create and manage agents
- No personal monthly Copilot Credit allowance
- Copilot Credit capacity or pay-as-you-go is provided separately
Maker access is the general ability to access Copilot Studio and create or manage agents. A Copilot Studio User License or Author role is a concrete way to grant that access, depending on the purchasing model. Maker access is not the same as Copilot Credit capacity: the credits fund usage-based activity. Capacity can be provided through Copilot Studio capacity packs, eligible pre-purchase plans, or pay-as-you-go billing through an Azure subscription.
Four questions for assessing cost
The license is only one of four checks
Which harness?
Standard, Copilot Chat, or GitHub Copilot? Agents and workflows powered by the GitHub Copilot harness use Copilot Credits for usage-based billing.
Who uses the agent?
An internal user with or without Microsoft 365 Copilot, an external user, or a technical account? Maker access alone does not give an end user included runtime usage.
Where—and under whose identity?
Microsoft 365 Copilot, Teams, SharePoint, an external website, or a custom channel? Included employee-facing use requires the appropriately licensed user's authenticated identity.
What triggers the activity?
A direct user request, autonomous trigger, schedule, event, API call, or service account? Not every technical trigger qualifies as user-initiated included usage.
For agent flows, the no-charge inclusion applies only when the flow is triggered through “When an agent calls the flow” and the user interacting with the agent is authenticated with a Microsoft 365 Copilot license. Other triggers consume Copilot Credits at the standard rate. Work IQ APIs, Computer-Using Agents, and certain other metered capabilities are not included in the Microsoft 365 Copilot user subscription license.
Four practical scenarios
Same agent. Different cost profile.
An employee asks the agent directly
Standard harness · supported Microsoft channel · authenticated employee with Microsoft 365 Copilot · user-initiated request.
Qualifying runtime usage may be covered by Microsoft 365 Copilot.The employee has no Copilot license
The agent and its capabilities remain unchanged, but employee-facing inclusion does not apply to this user.
Usage is generally billed through Copilot Credits.The agent plans several steps
GitHub Copilot harness · review documents · compare purchase order and invoice · call tools · route an exception for approval.
Credits may be consumed during AI-powered authoring, Preview, Evaluation, and runtime.The report starts on a schedule
An agent or agent flow runs automatically. No licensed user directly initiates that specific execution.
Copilot Credits are generally required for the execution.* Simplified assessment of typical scenarios. The exact configuration, capabilities, fair-use limits, and current Microsoft terms must still be checked.
Estimating Copilot Credits: What the Microsoft Estimator can - and cannot - tell you
Estimate monthly credit volume, identify cost drivers, and turn assumptions into a practical FinOps process.
Official Microsoft sources
Last checked: August 2026
Licensing and billing rules may change. For a specific decision, always check the current documentation, Product Terms, and the customer's applicable agreement.
This page provides a simplified professional overview and does not replace binding licensing advice. The current Microsoft Product Terms, licensing guides, official product documentation, and the customer's applicable agreement remain authoritative.