🚨 Mission 12: Understanding Licensing
🎯 Mission Brief
Welcome, Recruit. Before you deploy agents into production, you need more than working prompts and polished responses. You need a clear picture of how those agents are measured and billed. Licensing surprises tend to show up after an agent goes live, when usage scales and costs climb faster than expected.
This mission exists to prevent that moment. You'll learn how Copilot Studio usage is tracked, how different deployment choices affect cost, and why planning before publishing matters. Get this right and you'll design agents that are not only effective, but sustainable.
Think of it as your cost-control briefing.
🔎 Objectives
In this lesson, you'll learn:
- How Copilot Studio licensing works using the Copilot Credits consumption model
- How Copilot Credits are acquired through pay-as-you-go, capacity packs, and prepaid commitments
- What Microsoft 365 Copilot user licenses include and where Copilot Studio credits are still required
- How different agent scenarios (internal, external, automated, and integrated) affect credit consumption
- How licensing differs across Agent Builder, Copilot Studio, and Foundry and why cost is a build-surface decision factor
- How to plan, estimate, and monitor usage to avoid unexpected costs when deploying agents at scale
🔎 What are Copilot Credits?
Copilot Credits are the currency used to measure usage in Copilot Studio. Think of them like a utility meter: the more work your agent does, the more the meter runs.
Copilot Credits measure the time and effort your agent needs to retrieve information, respond to prompts, and use any actions or custom skills. Credits are consumed whenever an agent looks up information, answers a question, or runs workflows and actions. Every topic invocation, tool call, grounding operation, and custom skill uses Copilot Credits. Simple answers cost less than complex multi-step actions.
With the exception of testing in the embedded test chat, every time your agent does real work, it uses Copilot Credits.
How Copilot Studio Licensing Works
1. Copilot Studio Pay-As-You-Go (PAYGO) Meter
Pay-as-you-go is a way to pay for Copilot Studio using an Azure subscription, which allows you to get started building agents without any license commitment or upfront purchasing. At the end of each month, your organization pays only for the actual Copilot Credits its agents used.
- No upfront commitment
- Billed at $0.01 per Copilot Credit via Azure
- Requires an active Azure subscription linked to your Power Platform environment via a billing policy
- Good fit for early development, variable usage, or when you are not ready to predict monthly volume
2. Copilot Studio License (Copilot Credit Capacity Pack)
- Monthly subscription: 25,000 Copilot Credits per pack at $200/pack/month
- Capacity pools at the tenant level; multiple packs can be purchased and stacked
- Unused credits do not roll over month to month
- Works best for predictable, production-level usage
- Microsoft strongly recommends also setting up PAYGO as a backup, so agents keep running if you exceed pack capacity mid-month
3. Copilot Credit Pre-Purchase Plan (P3)
This is a one-year, prepaid option for Copilot Credits. A pool of Copilot Credit Commit Units (CCCUs) is usable across Microsoft eligible products. This includes Copilot Studio, Dynamics 365 first-party agents, and Copilot Chat.
- Credits are purchased as Copilot Credit Commit Units (CCCUs)
- Each CCCU is worth $1 and converts to 100 Copilot Credits
- Annual tiered discounts make this the most cost-effective option at scale
- Unused CCCUs expire at the end of the annual term (different from capacity packs, which expire monthly)
- Best for large agent fleets or organizations that want simplified governance across multiple workloads
📌 Copilot Studio User Licenses
Even with capacity in place, your makers need the right access:
- Copilot Studio Tenant License (credit capacity pack or pay-as-you-go) enables Copilot Studio in your tenant
- Copilot Studio User License (no cost) must be assigned to any person who will create or manage agents
This separation lets admins control capacity while individual makers build agents independently.
Note for P3 customers: When using the Pre-Purchase Plan, builder access is granted through the Copilot Studio Author setting in the Power Platform Admin Center. You create a security group in Azure/Entra, assign your makers to it, and then assign that group to the Copilot Studio Author setting. No individual user licenses are assigned.
🧠 What Microsoft 365 Copilot Licenses Include
Microsoft 365 Copilot ($30/user/month) gives licensed users:
- Copilot access in Word, Teams, Outlook, Excel, and other Microsoft 365 apps
- Agent capabilities in Copilot Studio when used in Microsoft 365 Copilot, Teams, or SharePoint at no additional cost, subject to fair use limits
When is usage actually free for M365 Copilot licensed users?
The billing rates table on Microsoft Learn shows "No charge" across every feature type — classic answers, generative answers, agent actions, agent flows, AI tools, all of it. That might look like a blanket free pass, but there is an important footnote attached to that column.
The "No charge" rate applies to employee-facing (Business to Employee) scenarios when both of the following are true: the user interacting with the agent is licensed with Microsoft 365 Copilot, and the agent is operating using that user's authenticated Microsoft 365 Copilot identity. Usage is also subject to fair use limits.
So the question is not "what feature is being used?" but "who is using the agent, and under what identity?"
Copilot Studio credits are consumed when:
- The user interacting with the agent does not have an M365 Copilot license
- The agent is published to an external channel (a website, app, or social platform) where it cannot operate under an authenticated M365 Copilot user identity
- The agent is running autonomously (not triggered by a licensed user's interaction)
No Copilot Studio credits are consumed when:
- An M365 Copilot-licensed user is interacting with the agent through Teams, SharePoint, or Microsoft 365 Copilot Chat, using their authenticated identity — regardless of whether the agent uses classic answers, generative answers, agent flows, or AI tools
Simple rule of thumb
- M365 Copilot-licensed user, authenticated, internal channel → no Copilot Studio credits (fair use applies)
- Unlicensed user, external channel, or autonomous trigger → consumes Copilot Studio credits
💰 Credit Billing Rates at a Glance
The number of Copilot Credits an agent consumes depends on the design of the agent, how often customers interact with it, and the features they use. Here is what each feature type costs:
| Agent Feature | Cost | M365 Copilot Licensed User |
|---|---|---|
| Classic answer | 1 credit | No charge |
| Generative answer | 2 credits | No charge |
| Agent action | 5 credits | No charge |
| Tenant graph grounding | 10 credits | No charge |
| Agent flow actions (per 100 actions) | 13 credits | No charge |
| AI tools: basic (per 10 responses) | 1 credit | No charge |
| AI tools: standard (per 10 responses) | 15 credits | No charge |
| AI tools: premium / reasoning (per 10 responses) | 100 credits | No charge |
| Content processing tools (per page) | 8 credits | No charge |
A single agent interaction can hit multiple billing lines at once. For example, an agent grounded in a tenant graph could use 12 Copilot Credits (10 for tenant graph grounding and 2 for a generative answer) to respond to a single complex prompt.
Note on reasoning models: When an agent uses a reasoning-capable model, billing applies two meters: the standard feature rate for the action performed, plus the premium AI tools rate (100 credits per 10 responses) for the additional compute required for deep reasoning and multi-step inference.Note on bring-your-own models: Azure Foundry (custom) models are billed separately and are not covered by these rates.
⚠️ Overage Enforcement
Capacity is enforced monthly. If you exceed your purchased credits:
- Enforcement is triggered when a tenant reaches 125% of their prepaid capacity.
- Custom agents are disabled. Active conversations finish, but all subsequent invocations are rejected until capacity is increased or reset.
- End users see a message like "This agent is currently unavailable. It has reached its usage limit."
- The tenant admin receives an email notification and a notice in the Power Platform Admin Center.
The fix: reallocate existing tenant capacity, purchase more packs, or set up PAYGO as a safety net so overages are billed rather than blocked.
📊 Capacity Planning Tips
Before you launch an agent:
- Estimate consumption using the Copilot Studio Agent Usage Estimator to forecast credits per agent per month
- Disable unused tools: tools you are not using still cost credits if left enabled
- Combine credit packs + PAYGO to avoid service interruptions if a pack runs dry mid-month
- Assign Copilot Studio User Licenses to all builders before they try to access the tool
- Monitor consumption in the Power Platform Admin Center under Billing > Licenses > Copilot Studio
TIP
✅ Run the Usage Estimator early in planning, then again after building your agent to compare projected vs. actual usage. The gap is usually instructive.
🧠 Real-World Licensing Scenarios
| Scenario | Licensing / Credits |
|---|---|
| M365 Copilot-licensed user interacting with an internal Teams agent (classic or generative answers, tenant graph grounding) | Covered by M365 Copilot license (fair use limits apply) |
| Agent with Power Automate/connector actions, used by M365 Copilot-licensed user in internal channel | No charge (fair use applies) |
| Agent with Power Automate/connector actions, used by unlicensed user or on external channel | Uses Copilot Credits |
| Autonomous agents (no authenticated M365 Copilot user identity) | Uses Copilot Credits |
| Published on external web or system | Uses Copilot Credits |
| Non-M365 Copilot licensed users interacting with any agent | Uses Copilot Credits |
| Agent using a reasoning model | Uses standard feature rate + premium AI tools rate |
| Maker building agents | Requires Copilot Studio User License (no cost) |
🧭 Licensing Across the Agent Stack
Everything above is the Copilot Studio cost model. But back in Mission 03 you learned that Copilot Studio isn't the only place to build an agent—Agent Builder (inside Microsoft 365 Copilot) and Microsoft Foundry sit on either side of it. Each bills differently, and that difference is a real decision factor, not an afterthought. Pick the wrong surface and you either overpay or hit a wall.
The one-sentence version
Agent Builder rides on the Microsoft 365 Copilot license you may already own; Copilot Studio runs on Copilot Credits (capacity packs, PAYGO, or prepaid); Foundry is billed as raw Azure consumption.
| Agent Builder (in M365 Copilot) | Copilot Studio | Microsoft Foundry | |
|---|---|---|---|
| Cost currency | M365 Copilot license, or Copilot Credits if unlicensed | Copilot Credits (packs / PAYGO / P3) | Azure consumption (pay-as-you-go) |
| Included with M365 Copilot? | ✅ Yes, for authenticated users | Internal authenticated use = no charge (fair use) | ❌ No — billed separately in Azure |
| A genuinely free path? | ✅ Web-knowledge-only agents are free | Embedded test chat only | Azure free trial credits only |
| You pay separately for | Nothing if licensed + internal | External / unlicensed / autonomous usage | Model tokens, tools, knowledge, hosting, memory |
| Billing home | Microsoft 365 admin center | Power Platform admin center | Azure |
| Cheapest when… | Internal Q&A, users already licensed | Departmental or external business agents | Pro-code custom apps you cost-optimize yourself |
Agent Builder: cheapest floor, narrowest ceiling
Both Agent Builder and Copilot Studio are included with a Microsoft 365 Copilot add-on license for authenticated users. If your audience already has M365 Copilot and your agent stays internal, an Agent Builder agent is effectively covered (subject to fair use), and agents grounded on web knowledge only are free. The catch is the same as its capability ceiling: Agent Builder lives inside Microsoft 365 Copilot, so the "free" path doesn't extend to external customers or autonomous runs. No Copilot license? You fall back to Copilot Credits / PAYGO to use it.
Copilot Studio: tenant capacity you plan for
This is the model the rest of this mission covers. Internal, authenticated M365 Copilot users cost nothing (fair use); the meter runs for external channels, unlicensed users, and autonomous agents. You're buying tenant capacity—via 25,000-credit packs, PAYGO at $0.01/credit, or a prepaid P3 pool. This is the surface where cost planning matters most, because the very things that make an agent valuable at scale (a public-facing bot, an agent that runs on a schedule) are exactly what consume credits.
Foundry: Azure consumption
Foundry is a different billing universe, raw Azure consumption, decoupled from Copilot Credits and from the M365 Copilot license entirely. There's no charge to create or run a Foundry-native agent's prompts and workflows, but you pay Azure directly for the parts that do work: model tokens, built-in tools (e.g., File Search vector storage, Code Interpreter sessions, Web Search transactions), knowledge/IQ connections (Azure AI Search, SharePoint, Fabric, Grounding with Bing, your own licensed data), hosted-agent container compute, and memory. That's maximum granularity and control which is ideal when you're pro-code and want to own and optimize cloud spend—but you also own the Azure billing complexity. (Exact rates live on the Azure pricing page and are subject to change.)
🏁 Mission Complete
You now understand:
- How Copilot Credits work and what changed in September 2025
- What Microsoft 365 Copilot licenses include and where they stop
- How to choose between capacity packs, pay-as-you-go, and the Pre-Purchase Plan
- What each feature type costs and how overage enforcement works
- How billing differs across Agent Builder, Copilot Studio, and Foundry — and how to let cost inform your build-surface choice
With this in place, you can design agents with cost in mind from the start, not after the bill arrives.
📚 Tactical Resources
- 📄 Copilot Studio Licensing & Billing
- 📄 Billing Rates and Management
- 📘 Power Platform Licensing Guide (November 2025)
- 📊 Message Management & Capacity Monitoring
- 🧭 Choose between Agent Builder and Copilot Studio — includes licensing requirements for each
- 💸 Foundry Agent Service Pricing — the Azure consumption model