Copilot Studio's newest agent-building experience bills Copilot Credits for both building and running an agent, and a Microsoft 365 Copilot license does not exempt that usage. This is the change most teams missed in 2026: agents and workflows built on the new GitHub Copilot harness consume credits during authoring, preview, and evaluation, not only when an end user talks to them, and the license exemption that covers the older harnesses does not apply. If you have been assuming your Copilot seats already paid for Copilot Studio, that assumption is now wrong for the new experience.

This guide is for IT directors, platform owners, and finance partners who need a straight answer on what actually consumes Copilot Credits, why the new interface behaves differently from the one your team learned on, and what the September 1, 2026 deadline means for agents you already have running. It explains the mechanics, the real numbers Microsoft has published, and the controls that keep consumption intentional instead of surprising.

Key takeaways

• The new GitHub Copilot harness bills during build and run. On the new experience, natural-language authoring, preview chats, and evaluation runs all consume Copilot Credits before an agent is ever published.
• A Microsoft 365 Copilot license does not exempt the new harness. The business-to-employee (B2E) exemption that covers licensed internal users applies to the classic Standard and Copilot Chat harnesses, not to the GitHub Copilot harness.
• September 1, 2026 ends the grace period. GitHub Copilot harness agents and workflows created before August 3, 2026, including those in Dev and Trial environments, begin consuming credits on that date under Microsoft message MC1461678.
• Credits are a shared, tenant-level meter. One Copilot Credit costs $0.01, and the same pool is drawn down across Copilot Studio, Copilot Cowork, Dynamics 365 agents, and Work IQ APIs.
• Microsoft has not published per-action rates for the new harness yet. The documented classic rates and the build-phase estimate ranges are the only defensible planning numbers available today.
• Consumption is governable. Environment-level credit allocation, control of the shared tenant pool, and Azure budgets and alerts turn an open meter into a bounded, monitored cost.

The short answer: what changed and who pays

Copilot Studio moved to usage-based Copilot Credits billing on August 3, 2026, and it now supports three agent-building experiences, called harnesses, that bill differently. The short version:

• Standard and Copilot Chat harnesses (classic): Internal users with a Microsoft 365 Copilot license are exempt from credit billing in authenticated internal scenarios, the B2E exemption documented in Microsoft's billing and licensing FAQ.
• GitHub Copilot harness (the new experience): No such exemption. You pay Copilot Credits during both building and runtime, license or not, and preview and evaluation are billed like production usage.
• The deadline: Agents and workflows created before August 3, 2026 kept the old model during a grace period that ends September 1, 2026, after which the new-harness rules apply to them too.

If your team built experimental agents on the new interface during the grace period, that previously non-billed usage becomes measurable consumption on September 1. The practical risk is not one expensive agent; it is a forgotten Dev-environment experiment quietly drawing from a shared tenant credit pool.

What is the GitHub Copilot harness, and why does it bill differently?

A harness is the underlying agent-building and runtime experience Copilot Studio uses, and it determines how Copilot Credits are consumed. Microsoft now runs three of them, and the newest one changes the cost model in a way that catches teams off guard.

Copilot Studio harnesses compared

Standard harness

• Billing: Copilot Credits in applicable scenarios, at the documented rates.
• License exemption: Yes. Authenticated Microsoft 365 Copilot users in internal (B2E) scenarios are not billed.
• Build phase: Test chat in the embedded editor is not billed.

Copilot Chat harness

• Billing: Copilot Credits in applicable scenarios.
• License exemption: Yes, same B2E treatment for licensed internal users.
• Build phase: Not the focus of the September 1 change; unaffected by it.

GitHub Copilot harness (new experience)

• Billing: Copilot Credits during both creation and runtime execution.
• License exemption: None. A Microsoft 365 Copilot license does not exempt usage.
• Build phase: Natural-language authoring, preview chats, and evaluations all consume credits, and preview and evaluation are billed equivalent to runtime.

The reason this matters is that the new harness reached general availability for production use, and Microsoft moved its billing from a grace period into live consumption. The building blocks that used to feel free during a proof of concept, iterating on instructions, previewing responses, running evaluations, now register against your tenant credit pool.

Does my Microsoft 365 Copilot license cover Copilot Studio?

Only partially, and the boundary is where most of the confusion lives. Microsoft 365 Copilot remains a per-user subscription, and it continues to include a defined set of experiences at no extra credit charge. What it does not do is create a transferable pool of credits you can spend anywhere, and it does not cover the new harness at all.

Included in Microsoft 365 Copilot versus metered by Copilot Credits

Included in the Microsoft 365 Copilot subscription

• Experiences: Copilot Chat, Copilot across the Microsoft 365 apps, and Microsoft-built agents such as Researcher, Analyst, and Facilitator.
• Grounding and models: Work IQ grounding inside Microsoft 365 Copilot experiences and access to multiple models.
• Classic-harness internal use: Authenticated, licensed users of a Standard or Copilot Chat agent on an internal channel.

Metered by Copilot Credits

• The new harness: Any GitHub Copilot harness agent or workflow, during both building and runtime, regardless of license.
• Outside the boundary: Classic-harness agents used on external or public channels, agents set to no authentication, and autonomous or background-triggered runs where no human license covers the session.
• Unlicensed users: Every interaction from a user without a Microsoft 365 Copilot license draws from your capacity pack.

A useful rule of thumb for the classic harnesses: a licensed user, authenticated, on an internal channel, is covered; an unlicensed user, an external channel, or an autonomous trigger consumes credits. On the new harness, none of that shelters you, because the exemption does not exist there in the first place.

Why does building and testing now cost credits?

On the new experience, the maker is a consumer of AI, too. Writing an agent's instructions in natural language, previewing how it responds, and running evaluations are all LLM-powered activities, and Microsoft now meters them. Microsoft's Copilot Credits Guide publishes planning ranges for the creation phase measured in conversation turns, the number of messages a maker sends in a single build session.

• Light creation: 1 to 2 turns, roughly 1 to 20 credits.
• Medium creation: 3 to 5 turns, roughly 21 to 60 credits.
• Heavy creation: 6 or more turns, 61 credits and up.

Preview and evaluation are billed equivalent to agent runtime usage, so a rigorous test cycle before launch is not free. This is the single most counterintuitive part of the change: an agent that never ships can still generate a bill, and a team iterating hard on prompt quality can spend more building than the agent will cost in its first month of light production.

The trap is not the agent you deployed; it is the one you are still tinkering with, quietly metering every preview against a pool you share with the rest of the tenant.

Scoping this well before you build is exactly the kind of decision that pays for itself. BabyBots runs fixed-fee Copilot Studio cost and governance assessments that map your agent portfolio to a harness, forecast credit consumption from real traffic, and set the environment controls before the meter starts, so the architecture decides the bill rather than a surprise invoice.

What does the new experience actually cost?

Copilot Credits are Microsoft's common billing unit across Copilot Studio, Copilot Cowork, Dynamics 365 agents, and Work IQ, pooled at the tenant level. One credit costs one cent by default, and there are three ways to buy them, described on the Azure Copilot Studio pricing page and the licensing documentation.

Three ways to buy Copilot Credits

Pay-as-you-go

• Rate: $0.01 per credit, billed at the end of the month.
• Commitment: None, and no waste because you pay only for what you consume.
• Best for: Environments under roughly 20,000 credits per month.

Capacity pack

• Rate: 25,000 credits for $200 per month, about $0.008 per credit.
• Commitment: Monthly, and unused credits reset with no carryover.
• Best for: Steady consumption above roughly 20,000 credits per month.

Pre-Purchase Plan (P3)

• Rate: Annual prepay with a 5 to 20 percent volume discount, tiers starting at 300,000 credits.
• Commitment: One year, and unused credits expire at the end of the term.
• Best for: Enterprise-scale, predictable programs.

For per-action planning, Microsoft has published rates for the classic harnesses but not yet for the GitHub Copilot harness. The documented classic rates are the best available proxy: tenant graph grounding costs 12 credits per response, other knowledge sources cost 2 credits per response, each tool invocation costs 5 credits, and standalone agent flows cost 13 credits per 100 actions. As a worked example, 100 users running 20 conversations a month with moderate knowledge and tool use lands near 15,000 credits, about $150 a month, for a single agent. Treat any new-harness figure as an estimate until Microsoft publishes concrete rates. For the full rate-card breakdown, see our guide on what AI agents actually cost in Microsoft 365.

What happens to my existing agents on September 1, 2026?

The September 1, 2026 date is the end of a transition period, not a shutdown. Microsoft message MC1461678, surfaced in the admin notice, states that GitHub Copilot harness agents and workflows created before August 3, 2026, including those in Dev and Trial environments, begin consuming Copilot Credits on that date. Both maker authoring activity and runtime execution are included. Standard and Copilot Chat harness agents are not affected by this specific transition.

No migration is required, and Microsoft frames the notice as awareness rather than mandatory action. The sensible move is a short review before the date: identify every GitHub Copilot harness agent and workflow, check Dev and Trial environments for forgotten experiments, and read historical, non-billed consumption in the Power Platform admin center under Licensing, Copilot Studio, Manage Agents. Microsoft labels that historical data as directional only, so use it to find the agents that deserve attention, not as a billing forecast.

How do I control and monitor Copilot Credit consumption?

Because the meter is now always on for the new harness, governance is the difference between a predictable line item and a surprise. The controls are straightforward, and they belong in place before the September deadline rather than after the first invoice.

1. Allocate credits to environments. Assign Copilot Credits at the environment level so a single team or experiment cannot draw down the whole tenant pool.
2. Control access to the shared tenant pool. Use environment group rules and the draw-from-tenant-credit-pool setting to decide which environments can spend shared credits at all.
3. Monitor in the Power Platform admin center. Track tenant consumption under Licensing, Products, Summary, and review agent-level activity under Manage Agents.
4. Set Azure budgets and alerts. For pay-as-you-go, wire up Azure budgets and alerts so spending crosses a threshold with a notification rather than a bill.
5. Assign an owner to every agent. Tie each agent to a named owner and a retirement path so orphaned experiments do not keep metering. Our Copilot Studio agent governance guide covers the identity and lifecycle model in depth.

Frequently asked questions

Does my Microsoft 365 Copilot license cover Copilot Studio agents?

Only partly. On the classic Standard and Copilot Chat harnesses, authenticated internal users with a Microsoft 365 Copilot license are exempt from credit billing under the B2E exemption. On the new GitHub Copilot harness, that exemption does not exist, so you pay credits during both building and runtime regardless of license.

What is the GitHub Copilot harness in Copilot Studio?

It is Copilot Studio's newest agent-building experience, sometimes called the new experience, now generally available for production. Unlike the classic harnesses, it consumes Copilot Credits during creation as well as runtime, including natural-language authoring, preview chats, and evaluation runs.

Do I really pay Copilot Credits just to build and test an agent?

On the GitHub Copilot harness, yes. Microsoft's Copilot Credits Guide bills preview and evaluation equivalent to runtime and meters natural-language authoring in conversation turns, with published ranges from roughly 1 to 20 credits for a light build up to 61 or more for a heavy one. On the classic harnesses, the embedded test chat is not billed.

What exactly changes on September 1, 2026?

GitHub Copilot harness agents and workflows created before August 3, 2026, including those in Dev and Trial environments, lose their grace period and begin consuming Copilot Credits under both authoring and runtime. Standard and Copilot Chat harness agents are not affected by this change, per Microsoft message MC1461678.

How much does a Copilot Credit cost, and do unused credits carry over?

A Copilot Credit costs $0.01 on pay-as-you-go. A capacity pack is 25,000 credits for $200 per month, and its credits reset monthly with no carryover; Pre-Purchase Plan credits expire at the end of the annual term. Only pay-as-you-go has no waste, because you pay only for actual consumption.

Has Microsoft published the exact per-action rates for the new harness?

Not yet. Microsoft has published rates for the classic harnesses, such as 12 credits per tenant-graph-grounded response and 5 credits per tool invocation, but concrete GitHub Copilot harness rates were not available at the time of writing. Use the classic rates and the build-phase ranges as planning proxies and confirm against the current Copilot Credits Guide before you commit budget.

Where this is heading

Copilot Credits are becoming the universal meter under most of Microsoft's AI stack, spanning Copilot Studio, Cowork, Dynamics 365, and Work IQ, all drawing from one tenant pool. As the newest harnesses drop their grace periods, the question for IT and finance shifts from whether an agent can be built to how agent consumption is forecast, allocated, and monitored across the tenant. The organizations that treat credit governance as a first-class discipline, owners, allocations, budgets, and monitoring, will scale agents without invoice shock; the ones that treat it as an afterthought will keep discovering forgotten experiments on their bill.

Get ahead of the meter

If you are building on the new Copilot Studio experience or have grace-period agents about to flip to billing, book a BabyBots Copilot Studio billing and governance assessment. In a single working session we inventory your agents by harness, forecast Copilot Credit consumption from your real traffic, and stand up the environment allocations, tenant-pool controls, and Azure budgets that keep spending intentional. Start a conversation with BabyBots and we will map your exposure before the next billing cycle does it for you.

Sources

• Microsoft Learn — FAQ for Copilot Studio billing and licensing (updated August 2026)
• Microsoft Learn — Billing rates and management, Copilot Studio
• Microsoft Learn — Standard harness licensing, Copilot Studio
• Microsoft — Copilot Credits Guide (PDF)
• Microsoft — Copilot Studio Licensing Guidance
• Microsoft Message Center MC1461678 — GitHub Copilot harness billing begins September 1, 2026
• Microsoft Azure — Copilot Studio pricing
• Cloud Revolution — Microsoft Copilot Credits: The Complete Guide for 2026
• Anders Jensen — Copilot Studio Pricing 2026: Credits Explained