A user licence is no longer enough to explain the cost of a Copilot project: some tasks, agents and API calls also consume credits. To build a reliable budget, you need to distinguish between entitlements included in licences, usage billed by consumption and the controls that authorise that consumption.
Copilot Credits: a shared unit, not a licence
Copilot Credits are the consumption unit used for several Microsoft AI capabilities. The number consumed depends on the work performed: a simple action and an autonomous task involving multiple models, context sources and tools do not necessarily cost the same. Credits consumed by supported experiences feed into a shared model across the tenant.
This model supplements per-user subscriptions; it does not replace them. A Microsoft Copilot licence, called Microsoft 365 Copilot before August 2026, covers, among other things, the intended Copilot experiences in Microsoft 365 apps and built-in Microsoft agents. It does not, however, grant unlimited use of Copilot Cowork, Work IQ APIs or every creation in Microsoft Copilot Studio without usage-based billing.
For an architect, the first question is therefore not âhow much does a prompt cost?â, but which operation is being performed, in which product and under which usage entitlement? This distinction prevents two opposing mistakes: budgeting credits for a feature already included in a licence, or enabling a billable service without assigning it a financial owner.
Prices and usage entitlements must be checked against the contractual terms applicable to the organisation. Consumption estimates help size a project; they do not guarantee either the number of credits ultimately used or the amount billed.
Which activities consume credits?
Credits apply in particular to Copilot Cowork, Work IQ APIs, certain creation and execution activities in Microsoft Copilot Studio, applications hosted in Copilot Managed Runtime, and some AI features in Dynamics 365 or Power Platform. The exact trigger varies by product: an executed task, an API call, AI-assisted creation, an agent action or usage beyond an included entitlement.
| Usage | What may be billed in credits | Distinction to check |
|---|---|---|
| Copilot Cowork | Autonomous tasks and, in the Frontier program, app creation | A user licence and a spending policy that authorises Cowork are still required |
| Work IQ APIs | Context queries and tool calls | The Microsoft Copilot licence does not include these API calls |
| Microsoft Copilot Studio | Certain AI-assisted creation activities and agent executions | The harness and execution channel change the applicable entitlement |
| Copilot Managed Runtime | Hosting, management and execution depending on usage | Power Apps Premium does not automatically cover AI or all hosting costs |
| Dynamics 365 and Power Platform | Agents and AI features depending on included entitlements | Check licences, environments and overages |
Native Work IQ and Work IQ APIs: two different situations
Work IQ is the work context layer that makes it possible to reason over an organisationâs information and tools while respecting permissions. When an included Microsoft Copilot experience uses this context natively, that does not mean a separate Work IQ API call is billed. By contrast, the Work IQ API documentation specifies that use by a solution developed for the organisation is billed by usage, whether or not the user has a Microsoft Copilot licence.
Three access methods are documented: A2A, remote MCP server and REST API. Conversation or context queries have variable consumption; Microsoft lists Work IQ Tools API calls for actions and tools at 0.1 Copilot Credit per call. To forecast an agentâs cost, count context queries and the actions it triggers separately: a single user journey may combine both.
According to Microsoft, the older Retrieval API and Chat API retain their current licensing model for users with Microsoft Copilot. It would therefore be unwise to infer an integrationâs bill from the name âWork IQâ alone: identify the exact API being called.
Copilot Cowork: why the bill depends on the task
Copilot Cowork carries out multi-step work based on an outcome requested by the user. A task may involve models, execution orchestration, context drawn from work data and tools that act within applications. The combination of these elementsânot simply the number of requests enteredâdrives consumption.
Consider an example: a team first requests a document based on existing files, then asks Cowork to prepare meetings, messages and document updates. Although each request starts with a single instruction, the second involves more potential steps and actions. An average cost per prompt is therefore only a planning assumption, not a uniform rate.
To build an initial budget, group users by profile, estimate each profileâs task volume, then distinguish between light, intermediate and complex tasks. Compare these assumptions with a real pilot and adjust them: the mix of tasks matters more than a single overall average.
Access to Cowork requires, among other things, a Microsoft Copilot user licence, Cowork enabled in the Microsoft Copilot environment, Copilot Credits usage-based billing and Anthropic enabled in the tenant. According to Microsoft Learn documentation on Cowork governance, Cowork is generally available and access is now managed through spending policies that select the service.
A Cowork estimate is not a substitute for the bill
In Cowork, the /cost command provides a free estimate of a taskâs credits and the monthly balance. Microsoft specifies that this figure is not authoritative for reconciling billed amounts.
App creation in Cowork, meanwhile, falls under the Microsoft Frontier Program. Evaluate it separately from generally available Cowork tasks: creating an app can consume credits during generation and iteration, while hosting and running it introduce additional areas of consumption.
Copilot Studio and apps: separate creation from execution
In Microsoft Copilot Studio, a harness is the software structure that helps an agent plan, retain context and use tools. The choice of harness affects the available scenarios and, in some cases, when credits are consumed. The three options described by Microsoft are GitHub Copilot Harness, Standard Harness and Copilot Chat Harness.
With GitHub Copilot Harness, natural-language creation, evaluation and preview that invoke a model may consume credits; manual configuration that does not use a model does not require them. At runtime, autonomous tasks may involve models, orchestration, context and tools. By contrast, agents and flows based on Standard Harness and Copilot Chat Harness agents running in Microsoft channels are included in the Microsoft Copilot user licence, subject to fair-use limits; in other cases, credits are required.
An app introduces another useful distinction: building, hosting and running it are not the same activity. Copilot Managed Runtime provides a managed environment for apps created with Cowork, Copilot Studio or third-party development tools. Its hosting, management and execution may consume credits; the relevant app scenarios still need to be assessed according to their preview status.
For a user with Power Apps Premium, execution in Copilot Managed Runtime benefits from the entitlements provided by that licence, within the applicable request limits. Overages may be billed in credits. That does not make hosting and management free, nor AI components such as agents or Work IQ APIs: include these items separately in the estimate.
The same discipline applies to Dynamics 365 and Power Platform. Prebuilt or custom agents may consume credits; in Power Apps or Power Automate, pay particular attention to the AI or agent features invoked and any usage beyond included entitlements. To extend this mapping, see our guide to Copilot costs across licences, credits and agents.
Choosing between pay-as-you-go and P3 pre-purchase
Microsoft offers two main ways to fund consumption: the Microsoft Copilot Studio pay-as-you-go Copilot Credit meter and the Copilot Credit Pre-Purchase Plan (P3). The Microsoft Copilot user licence is a separate decision: it provides access to defined experiences, but is not a pool of credits for every service.
| Option | How it works | When to consider it | Watch out for |
|---|---|---|---|
| Pay-as-you-go | Consumption billed after the month of use; Microsoft states USD 0.01 per credit | Pilots, variable volume or no upfront commitment | Set spending policies and monitor consumption |
| Copilot Credit P3 | A pool of credits paid for upfront for one year | Predictable volume and the ability to use the pool | Unused credits expire at the end of the term, and renewal is on by default |
| Microsoft Copilot licence | Per-user subscription for the capabilities it includes | Everyday productivity and Copilot experiences covered by the licence | Does not replace billing for separate usage |
Microsoft lists P3 tiers ranging from 300,000 credits with a 5% discount to 300,000,000 credits with a 20% discount. These tiers should not be read as a purchase recommendation: a discount does not offset credits left unused at the end of the term. The Azure documentation on Copilot Credit P3 also states that the plan lasts one year, renews by default and cannot be combined with other discounts.
If the pool is exhausted, the organisation can purchase additional credits or use pay-as-you-go. Do not assume a switch is already configured: check the intended billing plan and desired behaviour before the balance reaches zero. Microsoft also states that both mechanisms can contribute to the Microsoft Azure Consumption Commitment, or MACC; confirm the contractual implications with the procurement team.
Strengths
- Pay-as-you-go avoids pre-purchasing a volume that is still unknown
- P3 provides an identifiable pool for sufficiently predictable consumption
Limitations
- Pay-as-you-go requires regular monitoring
- P3 carries the risk of unused credits expiring and renews by default
Licences and prerequisites to check before granting access
A spending policy does not replace a required licence, service activation or checks on the userâs data permissions. Before choosing a budget, connect each use case to its technical and contractual prerequisites.
Checks before a Copilot Credits pilot
- Identify the experiences being tested: Cowork, Work IQ APIs, agents, apps, or Dynamics 365 and Power Platform features.
- For Cowork, check the Microsoft Copilot user licence, activation of Cowork and Anthropic in the tenant, and Copilot Credits billing.
- For Work IQ APIs, check tenant activation and usage-based billing; do not assume a Copilot licence covers the calls.
- For Microsoft Copilot Studio, check product access, the chosen harness and the entitlements applicable to the execution channel.
- For Copilot Credit P3, confirm the Azure subscription, the person authorised to buy and the renewal date to monitor.
- Assign owners for the budget, spending policies, environments and invoice reconciliation.
To purchase P3 on an Azure subscription, Microsoft Learn lists the subscription owner or someone with the âreservation purchaserâ role, among others. Grant this right only to designated purchasers: the ability to commit spending and the ability to view usage statistics serve different purposes.
A purchase may go through a CSP partner, Microsoft commercial channels or Microsoft directly, depending on the option chosen. Before comparing offers, check the terms that actually apply to your contract and each productâs licences; the indicative USD price of the pay-as-you-go meter does not describe every scenario.
Deploying controlled billing
The safest deployment starts with a defined scope: a team, documented use cases and an owner who can explain consumption variances. It does not require enabling Cowork for the entire tenant or immediately applying the same funding model to every agent.
Define the pilotâs use cases and users
List Cowork tasks, agents, apps and any Work IQ API calls. For each, record the licence, environment, business owner and proposed billing method.
Set up the chosen payment method
The Microsoft Copilot Studio pay-as-you-go meter is provisioned in the Power Platform admin center; P3 is purchased through Azure. Before enabling either, obtain approval for the financial scope and the risk of exhausting or renewing the pool.
Define the scope of spending policies
In the Microsoft 365 admin center, assign the intended services and users to your spending policies. To allow Cowork, an applicable policy must select Cowork; to deny it to a user, exclude them from every policy that selects it.
Control environments and agents separately
Review detailed Copilot Studio and Power Platform consumption in the Power Platform admin center. If Dynamics 365 agents or multiple environments are part of the pilot, plan for their allocation and tracking in the budget.
Test, measure and adjust
Run representative tasks, record the available estimates, then compare them with observed consumption in the appropriate dashboards. Adjust policy scope and volume assumptions before expanding the pilot.
In an organisation piloting Cowork to prepare internal files, the financial owner can track a category of tasks while the Microsoft 365 team checks which users are authorised. If the same team then adds a Copilot Studio agent that calls Work IQ, it should create a separate tracking line: the fact that both solutions support the same process does not mean they consume credits in the same way.
Governing access and protecting data
Cowork access control changed with general availability. Microsoft Learn specifies that the former agent control in âAll Agentsâ, used during preview, no longer affects access rights. A review based on that old setting would therefore provide false assurance.
A near-zero cap is not equivalent to denying access either. A policy limited to a single credit still lets the user open Cowork and start a task. To prevent a user from accessing Cowork, check that they are excluded from every spending policy that selects the service.
An existing policy may cover a future service
Microsoft states that the âAuto-apply new servicesâ option is enabled by default in spending policies. Review each existing policy if automatically adding future Copilot services does not match your governance approach.
Budget control does not replace data governance. Cowork operates within Microsoft 365 security and governance boundaries, and Copilot Managed Runtime uses Microsoft Entra ID authentication, formerly Azure AD. Before allowing an agent to act on files, messages or tools, check its effective permissions, the need for each action and who is responsible for reviewing the results.
This review also applies to an app built with natural language. Describe what it may read and modify, then separate permissions for building, operating and administering it. Our article on Copilot Cowork billing and monitoring extends this analysis to operations.
Measuring, reconciling and troubleshooting consumption
No single screen answers every financial question. The Microsoft 365 admin center helps track spending policies and usage of the relevant experiences, while details for Copilot Studio and Power Platform are available in the Power Platform admin center. Microsoft Learn compares these views and specifies that the Azure bill groups Cowork, Copilot Studio and Work IQ API consumption under the âMicrosoft Copilot Studioâ service.
To explain a bill, start with the Azure amount, then find the breakdown in the dashboards for the workloads that ran. The estimate displayed by /cost in Cowork helps a user assess a task, but does not replace invoice reconciliation. If a variance is unexpected, first check policy scope, active agents, environments and API calls before concluding that there is a billing error.
Timing also matters when deciding whether to purchase credits or enable a service:
September 2026
Apps and Copilot Managed Runtime presented in preview
App creation and managed-environment hosting scenarios require a check of their preview terms before production deployment.
November 2, 2026
Announced change for new Copilot Business licences
Microsoft announces that usage-based billing will be enabled by default for new Microsoft 365 Copilot Business licences from this date. As of September 30, 2026, this is an announced change, not one already in effect.
For sustained monitoring, keep the pilotâs assumptions documented internally: task types, billing methods, environments and owners. Without this reference, an increase in credits may be visible on the bill yet impossible to attribute to a specific business decision. Our guide to measuring the value of Copilot Credits in the enterprise helps connect consumption to expected outcomes.
Frequently asked questions
Does a Microsoft Copilot licence include the Work IQ APIs?
No. Work IQ API calls made by agents or applications are billed by usage, regardless of whether the user has a Microsoft Copilot licence. This does not mean that Work IQ context used natively by included Microsoft Copilot experiences incurs the same API billing.
How do I deny a user access to Copilot Cowork?
Exclude the user from every spending policy that selects Cowork. The former agent control in âAll Agentsâ no longer governs this access, and a cap of just one credit does not prevent the user from opening Cowork or starting a task.
Does Power Apps Premium make Copilot Managed Runtime free?
No. The licence includes execution within the applicable request limits, but overages may consume credits. Hosting, management and AI usage such as agents or Work IQ APIs must be assessed separately.
Where can I find Cowork consumption on the Azure bill?
The Azure bill shows Cowork, Copilot Studio and Work IQ API consumption under the âMicrosoft Copilot Studioâ service. To understand the details, reconcile that line with the Microsoft 365 and Power Platform usage views; the estimate provided by /cost is not an accounting reconciliation record.
Decide and act before expanding the scope
Start with an inventory of billable operations, not the purchase of a large volume of credits. If usage remains experimental or irregular, assess pay-as-you-go first with targeted spending policies; if consumption becomes predictable, compare P3 with the expected cost of credits actually used over its one-year term.
Next decisions
- Validate the licences and prerequisites for each pilot scenario.
- Check which policies select Cowork and the value of âAuto-apply new servicesâ.
- Assign an owner to reconcile detailed usage with the Azure bill.
- Set a date to review volumes before any pre-purchase or expansion of access.
Further reading
- Manage Copilot Cowork access and spending â to apply the current access control and avoid the minimal-cap trap.
- Compare Copilot dashboards and the Azure bill â to locate usage details and reconcile amounts.
- Understand the Copilot Credit P3 pre-purchase plan â to check purchasing, expiry and discount terms.
- Check your estimated cost in Copilot Cowork â to understand the
/costcommand and its limitations.



