This page is the reference behind our insight What the Microsoft Copilot licence includes, and how to keep the meter off. Part 1 maps the licence; part 2 is the checklist that keeps a tenant from being billed Copilot Credits. Every claim carries a numbered source, listed at the end of each part.

We re-check this page against Microsoft's documentation weekly. The date in each part's heading is the last check.

Part 1 · what the licence includes · as at 30 October 2026

The licence buys everyday AI. Credits buy the rest.

What Microsoft 365 Copilot (now sold as Microsoft Copilot) includes per user, where a published cap applies, what runs on Copilot Credits instead, and what Microsoft still has not put a number on.

User subscription licenceFixed price per user per month. Everyday AI across Chat, the apps and Microsoft's own agents. Fair use applies, and a few features carry a published cap.
Usage-based billingCopilot Credits, pooled at the tenant. Pays for agentic and frontier work: Cowork, Code, Autopilot, at-scale SharePoint, custom agents outside the included patterns. Needs the licence to unlock, then bills on top.
Included

In the licence, no meter, fair use

Nothing here draws Copilot Credits when a licensed person uses it. Microsoft publishes no numeric fair-use threshold for any of it.

Copilot Chat

Work and web grounding, Pages, file upload, image generation, priority access.1

Copilot in the apps

Word, Excel, PowerPoint, Outlook, OneNote, Teams meetings and chat, Loop, Forms.1

Work IQ grounding

Semantic index over mail, calendar, files, people and Teams. The intelligence layer itself is included; only its API is metered.1,2

Copilot Search and Notebooks

Universal search, Copilot Notebooks with files and meetings as references, audio overviews.1

Facilitator and the built-in agents

Microsoft's own agents inside Copilot run on the licence. Researcher and Analyst carry a cap (next band).2

Voice and vision

Real-time voice, and camera or screen vision during a voice session. Licensed users only; no admin toggle for voice today.3

Model picker: Auto, GPT-5.6, Claude Sonnet 5

Auto routes each prompt by accuracy, speed and cost. GPT-5.6 and Sonnet 5 are selectable under fair use.4,5

Copilot Studio agents, standard harness, in Microsoft 365 channels

Classic and generative answers, tenant graph grounding, actions, prompts and workflows are zero-rated when a licensed user runs the agent in Copilot Chat, Teams or SharePoint.6,7

Agent flows the agent calls

Runs on the "When an agent calls the flow" trigger, with a licensed user in the chat, are no charge. Any other trigger bills.6

SharePoint agents and everyday Copilot in SharePoint

Ask, find, catch up; create files, pages, lists, libraries; simple rules and approvals; Autofill metadata that fills over time.8

Declarative agents from the store or Agent Builder

Agents on instructions, public web or tenant data, used by a licensed person: no extra charge.9

Copilot Chat API and Retrieval API

No extra cost for licensed users. The Retrieval API has a pay-as-you-go preview for unlicensed users only.10

Copilot Analytics and SharePoint Advanced Management

Copilot Dashboard, usage reports, oversharing controls and restricted content discovery.7

Interpreter in Teams

Included, with a published monthly allowance (next band).11

Copilot Studio authoring

The licence gives maker access to build standard-harness agents. Building on the GitHub Copilot harness is metered from the first prompt.12

Included, capped

In the licence, with a number Microsoft publishes

These are the only inclusions with a stated allowance. Counts reset on a calendar month.

25queries / user / month

Researcher

The Researcher FAQ states 25 a month. Microsoft's launch note said the 25 is shared with Analyst; the Analyst FAQ no longer states a figure, so treat the pool as shared until Microsoft says otherwise.13,14

20hours / user / month

Interpreter agent in Teams

Real-time speech interpretation in meetings. Past 20 hours, access depends on available capacity rather than stopping outright.11

Limitnumber not published

Claude Opus 5 in the picker

"Included with limits." At the limit you get a warning, then a choice: switch to Auto at no cost, or keep Opus on credits. The threshold is unpublished.4,5

Fair useno threshold published

Standard-harness agents in M365

The zero-rating for licensed users is "limited to fair usage limits" that Microsoft reserves the right to change.6

30days

Teams meeting recap window

Copilot summarises meetings up to 30 days back. A scope on the feature rather than a quota.1

Soonenforcement timing

USL usage limits generally

Microsoft's licensing page lists reaching a USL limit as "coming soon", with in-product warnings before any limit bites.4

Copilot Credits

Not in the licence. Needs usage-based billing switched on

Every item here bills in Copilot Credits, and most need the licence as a prerequisite. In an enterprise tenant nothing bills until an admin creates a spending policy or billing plan.5,15

Copilot Cowork

The agentic system that runs multi-step work. Model responses, tool and skill calls, image generation and browser tasks all count. Access is granted only by a spending policy.16Light task tens of credits; heavy tasks hundreds

Copilot Code (Frontier)

Build dashboards, trackers and apps from plain language. Metered through the same spending policies as Cowork.17

Autopilot

Named by Microsoft as a usage-based experience alongside Cowork and Code.4

Frontier models

GPT Astra and Claude Fable class models run on credits, not the licence, in any surface.4,5

Copilot in SharePoint, at scale

Large or unbounded content sets, whole-site creation, bulk edits, scheduled AI workflows, real-time Advanced Autofill, image generation into libraries, site analytics. Copilot asks the user to confirm before credits are spent.8

Advanced work in OneDrive

Listed as a usage-based service in Cost management. Licence required to use it.15

Work IQ API

Grounding, retrieval and reasoning for custom apps and agents, on any platform. Not an entitlement of the licence.2Tools API 0.1 credit per call; chat and context variable, roughly 15 to 100 credits a task

Copilot Managed Runtime

Hosting and running apps built in Cowork, Code or Copilot Studio. Power Apps Premium users are covered within their request limits.20.1 credit per API call

Copilot Studio, GitHub Copilot harness

Agents, workflows and apps on this harness bill for everything, including natural-language authoring, preview and evals, whatever licence the user holds. Developer and trial environments bill since 1 September 2026.12,18

Computer-use agents

Never covered by the licence.6

Agent flows on other triggers

Scheduled, event or autonomous runs bill at the standard rate for every action, agent calls included.613 credits per 100 actions

Standard-harness agents outside Microsoft 365

The same agent on a website, a custom app, a phone line or any non-M365 channel bills per feature.121 classic · 2 generative · 5 action · 10 graph grounding

Agents used by people without the licence

Copilot Chat users can run metered agents that touch SharePoint or connector data only if an admin has turned on pay-as-you-go. Off by default.9,19About 12 credits for a grounded answer

Customer-facing voice and contact centre

Teams Phone Agent, the customer conversation harness and Contact Center Intelligence bill per call or conversation.2Phone calls 5 to 40+ credits each

Dynamics 365 agents and business-application MCP tools

Prebuilt and custom Dynamics agents, and MCP tool calls into Dataverse, Sales and Service, consume credits on top of their own licences.2

Not published

Still grey

Where Microsoft says a limit exists but has not printed the number, or where the documentation is silent.

The Opus allowance

How many Opus prompts a licensed user gets before the Auto-or-credits choice. Reports describe a weekly cap, but no Microsoft page states one.5

Fair use for Chat, voice and vision

"Fair use" and "subject to capacity" appear throughout. No figures.3,4

Audio overviews and Notebook generation counts

Older summaries quoted a daily cap. No current Microsoft documentation states one, so do not promise one.

Standard-harness fair use for agents

The zero-rating is fair-use limited; the threshold is undefined and changeable.6

Which capped features move to credits next

Microsoft says some capabilities start on usage-based billing and move into the licence later, sometimes arriving with a limit first.5

Copilot Business defaults in Australia

From 1 December 2026 new Copilot Business CSP subscriptions ship with usage-based billing on at 4,000 credits per user per month. Australia is excluded at launch; the date for Australia is not published.20

A licensed person is not billed when they

  • use Chat, the apps, Pages, Notebooks, Search, Researcher, Analyst or Facilitator
  • pick Auto, GPT-5.6 or Sonnet 5
  • run a standard-harness or declarative agent inside Copilot Chat, Teams or SharePoint
  • trigger an agent flow from that agent
  • do everyday work with Copilot in SharePoint

Credits are consumed when anyone

  • opens Cowork, Code or Autopilot
  • selects a frontier model, or keeps using Opus past its limit
  • confirms an at-scale SharePoint or OneDrive task
  • builds or runs on the GitHub Copilot harness, uses computer use, or calls the Work IQ API
  • runs an agent outside Microsoft 365, on a non-agent trigger, or without a licence against tenant data
USD 0.01per Copilot Credit on pay-as-you-go, billed in arrears through an Azure subscription.2
25,000credits per month in a prepaid Copilot Studio capacity pack, pooled across the tenant; unused credits do not roll over.21
5% to 20%discount on a one-year Copilot Credit Pre-Purchase Plan, from 300,000 to 300 million credits. Unused credits expire at term end.2
1st of monthprepaid consumption counts reset. Spending-policy limits reset the same day.21,22

The simple takeaway

Included is broad. Unlimited is a word Microsoft never uses.

Budget the licence for everyday work and expect it to hold. Treat Cowork, Code, frontier models, at-scale SharePoint and custom agentic builds as a second, metered line in the plan, and decide before rollout whether that meter is switched on at all.

Part 1 sources, Microsoft Learn unless noted, read 30 October 2026

  1. Microsoft Copilot overview: licence comparison and app features
  2. Copilot Credits Guide, October 2026 (PDF)
  3. Copilot Chat FAQ; Voice in Microsoft Copilot
  4. Understanding the USL and usage-based billing
  5. Evolution of the Copilot pricing model, Microsoft, 25 September 2026
  6. Copilot Studio billing rates and management
  7. Licensing for agents powered by the standard harness
  8. Get started with Copilot in SharePoint
  9. Plan licensing and cost (extensibility)
  10. Copilot Chat API; Retrieval API pay-as-you-go
  11. Manage Interpreter agent for your organization
  12. Manage costs for agents powered by the GitHub Copilot harness
  13. Researcher agent FAQ
  14. Researcher and Analyst are now generally available, Microsoft, June 2025
  15. Usage-based billing and cost management for Copilot Credits
  16. Manage Copilot Cowork; How access to Cowork is determined
  17. Manage Copilot Code (Frontier)
  18. Overview of usage-based billing (GitHub Copilot harness)
  19. Agents admin guide for Microsoft 365
  20. Partner Center announcements, October 2026
  21. Copilot Studio capacity packs; Copilot Studio billing FAQ
  22. Managing AI experiences enabled by usage-based billing

Part 2 · lock the meter · as at 30 October 2026

Run Copilot on the licence alone. Zero Copilot Credits.

The levers that decide whether a tenant can ever be billed for Copilot Credits, where each one lives, and the setting that keeps it shut. Everything a licensed person does in Chat, the apps and standard agents stays inside the licence; this page keeps the meter from starting.

One principle Credits can only be charged through a billing object you create: a spending policy or billing plan in the Microsoft 365 admin centre, a billing plan or credit allocation in the Power Platform admin centre, or a linked Azure subscription behind either. No object, no meter. Everything else on this page is making sure none of those objects exists by accident.1,2

How the meter starts

Four things have to be true before a single credit is billed. Break the chain at the first link and the rest never matters.

1 · FundingAn Azure subscription, capacity pack or pre-purchase plan is attachedPay-as-you-go needs an Azure subscription and resource group; packs and P3 plans are purchases.
2 · PolicyA spending policy or billing plan existsM365 admin centre: Copilot › Cost management. Power Platform: Licensing › Pay-as-you-go plans, or an environment credit allocation.
3 · ScopeThe user, group or environment is inside itDefault scope is All users. A policy with a 1-credit limit still grants access.3
4 · UseSomeone uses a metered experienceCowork, Code, Autopilot, frontier models, at-scale SharePoint, GitHub Copilot harness agents, agents outside M365, unlicensed users on tenant data.
M365 admin centre

Copilot cost management and settings

admin.microsoft.com. Global or Billing administrator to change billing; AI administrator for the settings. Nothing in this node bills until an admin presses Get started, so the first job is proving nobody has.1,2

No spending policy exists, and the default policy was never activated

Copilot › Cost management › Configuration

The Get started wizard creates the default policy. If a list of policies shows here, delete each one. Deleting stops future billing at once; usage already accrued is still owed. A policy is an access grant, not just a budget: scope and services matter, limits do not keep people out.2,3
Leak: a 1-credit All-users policy opens Cowork to the whole tenant

If a policy must stay, its scope is a named security group and Auto-apply new services is off

Spending policy › Scope · Select agents and services

Auto-apply is on by default and adds every future metered service to the policy without review. Per-user limits must be at least 2,000 credits a month, so a "tiny" policy is never a lock.2
Minimum per-user limit 2,000 credits

Users cannot request a spending policy

Copilot › Settings › All settings › Access to usage-based billing experiences › No users

Default is All users can request. With No users they see a learn-more link instead of a request that lands in an admin's queue. Takes up to 24 hours.4

Discovery of usage-based experiences is off

Copilot › Settings › AI experiences enabled by usage-based billing

Controls visibility only. Microsoft is retiring it in favour of the request setting above, so set both while both exist.5

No pay-as-you-go service is connected and no classic billing policy exists

Copilot › Cost management › Classic Billing & usage › Pay-as-you-go services · Billing policies

This is the older route that meters Copilot Chat agents, SharePoint agents and the Retrieval API for people without the licence. Toggle each service to disconnected, then delete the policy.6

Nothing Copilot-related under the Billing pay-as-you-go node either

Billing › Pay-as-you-go

The same screen carries Microsoft 365 Backup, storage and high-volume email meters. Confirm no Copilot service is listed.1

Self-service trials and purchases are blocked per product

Settings › Org settings › Services › Self-service trials and purchases › Do not allow

There is no tenant-wide switch; set each product, Copilot Studio and Microsoft 365 Copilot included. Pair it with AllowAdHocSubscriptions off in Entra so viral trials cannot start.7

Copilot Business bought through CSP after 1 December 2026: delete the default policy on day one

Copilot › Cost management › Configuration

New Copilot Business subscriptions arrive with usage-based billing on and 4,000 credits per user per month. Partner Center creates that policy only if the tenant has none, so an existing empty tenant gets one. Not yet in Australia; watch the message centre.8
100 users × 4,000 = 400,000 credits a month exposure

Model families are set the way you want, knowing they are not a cost control

Copilot › Settings › AI providers operating as Microsoft subprocessors

Turning Anthropic off removes Claude from the picker; it does not stop credits and does not block Cowork. Opus has a licence limit; past it the user is offered Auto for free or credits, and credits only work if a policy exists.9

Power Platform admin centre

Copilot Studio credits, environments and agents

admin.powerplatform.microsoft.com. Power Platform or Global administrator. Credits here are charged to the environment an agent runs in, not to the person using it, so the controls are environmental.10

No pay-as-you-go billing plan, and no environment linked to one

Licensing › Pay-as-you-go plans

A billing plan links environments to an Azure subscription. Remove the environment from the plan or delete the plan; billing stops at that moment. The special Microsoft 365 Copilot Chat plan creates an environment that cannot be deleted, only unlinked.11

Every environment has Draw from the available capacity in my tenant cleared

Licensing › Copilot Studio › Manage Copilot Credits › environment › Capacity overages

On by default for eligible environments with no allocation. With it on, an environment spends any unallocated prepaid credits in the tenant. Publish the environment-group rule Cost controls - Draw from tenant credit pool to lock the setting across a group.10,12
New environments arrive with this on

No prepaid credits are allocated to any environment you do not intend to spend

Licensing › Copilot Studio › Manage Copilot Credits

If you own no capacity packs this is already zero. If you do, an allocation of zero plus no tenant draw means metered features in that environment stop with a "You need credits to continue" message rather than billing.13

Any agent that must stay running has a monthly limit with Stop usage on

Licensing › Copilot Studio › Manage Agents › Set limit

Hard stop turns the agent off at the limit. Limits apply with a delay, so leave a margin, and they do not stop agent flows the agent calls.12

Only tenant admins can allocate capacity, and makers are a named group

Manage › Tenant settings › Add-on capacity assignment · Copilot Studio authors

Letting environment admins allocate gives them allocation rights across every environment. The authors group limits who can build under pay-as-you-go; it does not revoke access from licensed users, so manage environment roles as well.10,14

No agent is on the GitHub Copilot harness unless you have chosen to pay for it

Manage › Copilot Studio › Harness column › GitHub Copilot

These agents bill for authoring, preview, evals and runtime regardless of licence, including developer and trial environments since 1 September 2026. With no funding attached they simply cannot be built.10
Billing starts at the first natural-language prompt, not at publish

Data policies block the channels and features that only bill

Policies › Data policies

Block publishing to non-M365 channels (website, custom app, phone) and computer use where you do not want them. Standard-harness agents are zero-rated only inside Copilot Chat, Teams and SharePoint for licensed users.15

Azure

The subscription behind the meter

portal.azure.com. Owner or Contributor on the subscription. Pay-as-you-go can only bill a subscription someone with these rights attached.

No Power Platform account resource exists in any subscription

Resource search › type "Power Platform account"

Creating a billing plan in either admin centre creates this resource. Deleting the plan does not delete it, so a leftover resource is the fingerprint of a plan that once existed. Confirm the plan is gone, then remove the resource.11

No Copilot Credit or Microsoft Agent pre-purchase plan has been bought

Cost Management + Billing › Reservations

P3 plans show as a reservation benefit. They are only consumed through a policy, but a bought plan is money already spent.16

The admin-centre wizard was never allowed to create a subscription for you

Subscriptions list

If a Global administrator has no Azure subscription, the Cost management wizard offers to create one from the M365 billing account. Look for one you did not plan.1

Budgets and alerts are understood as alarms, not brakes

Cost Management › Budgets

Azure budgets notify; they never stop Copilot Studio or Cowork consumption. The stopping points are policy scope, environment allocation and agent hard stops.10

Design rules

What makers and users do that keeps usage inside the licence

With the three planes locked, metered features fail closed. These rules keep the things that still work from ever needing credits.

Everyone who touches agents holds the licence

Zero-rating applies when the person in the chat is authenticated with a Microsoft Copilot licence. Unlicensed colleagues get web-only Chat and instruction-only agents.15,17

Build on the standard harness

Topics, generative answers, tenant grounding, actions, prompts and workflows inside the agent are included. The GitHub Copilot harness never is.10

Publish only to Copilot Chat, Teams and SharePoint

The same agent on a website, phone line or custom app bills per answer.15

Agent flows use the "When an agent calls the flow" trigger

Scheduled, event-driven and autonomous runs bill 13 credits per 100 actions, including the calls back to the agent.15

Stay on Auto, GPT-5.6 or Sonnet 5

Opus is included to a limit, then it is Auto or credits. Frontier models are credits from the first prompt. With no policy, the credits option is dead.9,18

Decline the at-scale prompt in SharePoint

Copilot asks before it spends credits on unbounded or scheduled work. Without a policy it explains what it cannot complete and stops.19

No Work IQ API, no computer use, no Managed Runtime

All three bill for every call. Copilot's own Work IQ grounding in Chat and the apps is included and is not the API.20

Use Agent Builder for simple agents

Agent Builder agents incur no generative-answer charge unless they use tenant graph grounding for an unlicensed user.15

Use Copilot Studio for Teams for Teams-only bots

Agents created in a Teams environment with Copilot Studio for Teams do not consume credits, whoever uses them.21

Prove it, monthly

  • Copilot › Cost management › Overview shows zero credits used and no policies. If the node still says Get started, nothing has ever been configured.1
  • Reports › Usage › Microsoft Copilot › Credits is empty for pay-as-you-go consumption.22
  • Power Platform › Licensing › Copilot Studio › Summary shows billed credits at zero; non-billed credits from licensed users are normal and cost nothing.12
  • Message centre: new metered features are announced there and ship off by default; a tenant with no policy inherits nothing.6
  • Power Platform inventory: query environments for tenant-draw enabled and compare to your register, since new environments arrive with it on.10

What the lockdown gives up

  • Cowork, Copilot Code and Autopilot are unavailable to everyone, however licensed.
  • Opus stops at its limit; frontier models (Astra, Fable) are never offered.
  • SharePoint and OneDrive at-scale automation stays off; everyday Copilot in SharePoint keeps working.
  • Custom agents live only on the standard harness, inside Microsoft 365, for licensed users.
  • People without the licence get web Chat and instruction-only agents, nothing grounded in tenant data.
  • Reopen one lever at a time, with a named group, a per-user cap, alerts and Auto-apply off, when a business case is ready to fund it.

The simple takeaway

No policy, no plan, no subscription. No bill.

Microsoft built the credits model so that it is off until an administrator turns it on. Check the three admin planes, delete what should not be there, lock the environment defaults, and the licence covers everything your people can still reach.

Part 2 sources, Microsoft Learn unless noted, read 30 October 2026

  1. Set up usage-based billing for Copilot Credits
  2. Managing AI experiences enabled by usage-based billing
  3. Determine access controls for Copilot Cowork
  4. Access requests to usage-based billing experiences
  5. Discovery setting for AI experiences enabled by usage-based billing
  6. Microsoft Copilot pay-as-you-go service overview; Set up and manage pay-as-you-go in the Copilot node
  7. Manage self-service purchases and trials; Block unauthorized self-service sign-ups (Copilot Studio)
  8. Partner Center announcements, October 2026; Usage-based billing for Copilot Business in Partner Center
  9. Anthropic models in Microsoft Online Services; Manage Copilot Cowork
  10. Manage costs for agents powered by the GitHub Copilot harness
  11. Set up pay-as-you-go (Power Platform); Pay-as-you-go plan
  12. Manage Copilot Credits and capacity for Copilot Studio
  13. Enforcement policy for agents consuming Copilot Credits
  14. Users outside the Copilot Studio authors group can access Copilot Studio
  15. Copilot Studio billing rates and management
  16. Usage-based billing: admin centre vs the Azure bill
  17. Plan licensing and cost (extensibility)
  18. Understanding the USL and usage-based billing
  19. Get started with Copilot in SharePoint
  20. Copilot Credits Guide, October 2026 (PDF)
  21. Copilot Studio billing and licensing FAQ
  22. Microsoft Copilot Credits report

Work out which meter your plan needs before rollout

Our Governance Audit covers the Copilot cost controls on this page. There are four ways to work with us, and the first conversation is thirty minutes.