Copilot Studio Credits: Cost, Packs and Budget Explained

25,000 Copilot Studio credits cost $200 a month, and if you don’t use them by the end of the month, they’re gone. No rollover. That’s the simple part.

It gets more complicated with the three other ways to get credits, with what’s actually new since September 1, 2026, and with the fact that Copilot Cowork now draws from the same wallet. I outlined exactly this model in my talk on the m365 Show in September 2026 (video at the end of this article). Here’s the full version, checked against Microsoft’s current official documentation, including one point that came across a little oversimplified in the short talk version.

What a credit actually costs

Since September 1, 2025, the single billing currency for Copilot Studio agents has been Copilot Credits. Before that, contracts were based on messages or billed sessions. The number of credits per pack and the pay-as-you-go rate stayed the same in the switch; only the unit changed.

Here’s the official consumption table for the standard harness:

• Classic Answer: 1 credit
• Generative Answer: 2 credits
• Agent Action: 5 credits
• Tenant Graph Grounding (access to data across the whole tenant): 10 credits
• Agent flow actions: 13 credits per 100 runs
• AI tools, tiered by quality: Basic 1 credit per 10 responses, Standard 15, Premium 100, Content Processing 8 credits per page
• Voice: Classic 10, GenAI 35, Premium GenAI 75 credits per minute
• Reasoning models: the feature rate plus the premium tool rate of 10 credits per 1,000 tokens on top

If you have a Microsoft 365 Copilot license and use an agent in the standard harness under your own identity, that internal use costs nothing extra. It’s an often-overlooked fourth source of credits, next to the capacity pack, prepaid, and pay-as-you-go. So there are really four ways to get credits, not three. Before you budget credits for a specific idea, you can run the free pre-check at Agent-Architekt (in German) to see whether your agent idea is feasible in Copilot Studio.

Four ways to get credits: capacity packs, prepaid, pay-as-you-go

1. Included at no extra cost for users with their own Microsoft 365 Copilot license, for internal use in the standard harness.
2. Capacity pack: 25,000 credits for $200 a month, licensed tenant-wide. Unused credits expire at the end of the month with no rollover. In the words of Microsoft’s official FAQ: “Credit usage is counted on a monthly basis and resets on the first day of the month.”
3. Pre-Purchase Plan (unit: Copilot Credit Commit Unit, or CCCU): a one-year term with tiered discounts of up to 20% compared to pay-as-you-go, bought as an Azure reservation. Microsoft’s official example: Tier 2 with 15,000 CCCU costs about $14,100 for 1.5 million credits. The lower entry amounts floating around couldn’t be confirmed as official, fixed tier thresholds, so check the Azure portal under Reservations before you buy.
4. Pay-as-you-go: $0.01 per credit with nothing bought upfront, available since December 1, 2024. You turn it on with a billing policy in the Power Platform admin center, which is tied to an Azure subscription and linked to an environment, and which you can unlink again at any time.

What actually happened on September 1, 2026

In the talk, it sounded as if every environment has had to be connected to a credit pool or to pay-as-you-go since September 2026, or its agents would stop working. That’s the gist, but the precise version is narrower. It’s the end of a grace period, specifically for developer and trial environments under the GitHub Copilot harness, the new, agentic third harness in Copilot Studio, alongside the standard harness and classic Copilot Studio. The official docs say it word for word:

“Developer and trial environments moved to usage-based billing on September 1, 2026.”

Until then, building and testing there wasn’t billed. Since September 1, 2026, every build, test, and evaluation run there counts against credits. Without available credits, nothing runs in these environments anymore.

For the standard harness, the broader rule has been in place for longer, since the switch to the credit model on September 1, 2025: an environment without credits or pay-as-you-go runs into overage enforcement, which kicks in at 125 percent of available capacity. At that point, agents are disabled, but conversations already underway are allowed to finish properly. A separate, more granular rule, agent flow enforcement, kicks in earlier and blocks only new flow runs as soon as prepaid capacity is used up.

Cowork and apps: a new cost center with its own controls

Copilot Cowork has been generally available since June 16, 2026, and fully billable since July 1, 2026. Microsoft officially lists “Cowork, Apps built with Copilot Cowork, Work IQ API” as services that run on usage-based billing. That’s the same credit currency as Copilot Studio, but with its own cost unit for building apps inside Cowork. Its rollout roughly coincided with the talk (early to mid-September 2026, according to third-party sources; not confirmed on a dated official Microsoft page).

What matters for governance: it’s the same currency, but a different management layer. You manage classic Copilot Studio agents in the Power Platform admin center. Cowork, apps built in Cowork, and the Work IQ API, on the other hand, are handled through Cost Management in the Microsoft 365 admin center. That’s where you’ll find spending policies per user or group, threshold alerts, a workflow for credit requests, and a /cost slash command right in Cowork that shows the live cost of a running task. Both layers draw from the same tenant pool: capacity pack credits you assign to an environment in Power Platform are no longer available to Cowork in the Microsoft 365 admin center. What cost management in the Microsoft 365 admin center has covered since September 25, 2026 (Code, Managed Runtime, and Copilot Studio agents from October 2026), and what the license includes, is explained in the article on Copilot’s new pricing.

What to set up as an admin this week

For classic Copilot Studio agents, the Power Platform admin center has three tabs under Licensing → Copilot Studio that together give you cost control:

• Summary: a tenant-wide capacity overview with prepaid and pay-as-you-go figures and a three-month trend.
• Environments: credit consumption per environment, status (within capacity or in overage), and whether an allocation or pay-as-you-go is active.
• Manage Agents: every billable agent in the tenant, one by one, with month-to-date consumption and status (Within limit, Nearing limit, Over limit). This is where you set a monthly credit limit per agent, a notification threshold, and optionally a hard stop (“Stop usage”).

There is no tenant-wide default limit. Microsoft’s own docs state that the Power Platform admin center doesn’t provide a default agent limit. You have to set one per agent yourself or automate it through the Power Platform API.

Just as important: Azure budget alerts don’t stop anything. They notify you, with a delay, but the environment keeps running. The only real stop is the agent limit with “Stop usage.” For a rough estimate before you even start testing live, Microsoft offers the official Copilot Studio Agent Usage Estimator.

As a foundation for governance that lasts, Microsoft itself suggests a four-layer model: Tenant (who is allowed to allocate capacity at all), Environment (allocation, access to the tenant pool, pay-as-you-go), Agent (monthly limit, notification, hard stop), and Process (a named cost owner, an escalation path for alerts, an approval step before the next environment). It also helps to classify environments by purpose from day one (exploration, test/validation, funded production) instead of bolting governance on later.

Your checklist for this week

1. In the Power Platform admin center, check under Manage Agents which agents are currently running without a monthly limit.
2. Set a limit with a notification threshold for every production agent, and for critical cases, add “Stop usage.”
3. Before anyone keeps building there, find out whether dev and trial environments on the GitHub Copilot harness have had a valid credit source since September 1, 2026.
4. Check in the Microsoft 365 admin center whether Cowork and its apps already have their own spending policies, or whether they’re drawing on the same tenant pool as your Copilot Studio environments with no controls.
5. Name a cost owner for each environment before the next team starts testing, not after.

If you want to set up exactly this kind of credit and environment management for your Copilot Studio rollout, that’s a job for coaching for IT teams and admins.

The full talk, with the complete ten-step model for agent readiness, is on YouTube (in German): “Copilot Studio & Agents: So bereitest du dein Unternehmen vor” (m365 Show, Mirko Peters’ channel).

Sources: Microsoft Learn — Billing and licensing, Requirements and messages management, Billing FAQ, Billing credit overview (Agents experience), Enforcement policy for credits, Govern credit consumption, Manage usage – GitHub Copilot harness, Pay-as-you-go overview, Copilot Credit Pre-Purchase Plan, Usage-based billing overview; Microsoft — Copilot Studio Pricing, Copilot Cowork GA announcement. As of September 15, 2026. In my experience, Microsoft changes prices, quotas, and thresholds several times a year.