Skip to main content
    Back to Industry Insights
    Microsoft
    Procurement
    AI

    Microsoft Copilot billing: What the license covers and what gets metered

    Can you be charged beyond the Copilot seat price, and who controls that spend? A product-by-product guide to what Microsoft includes, what it bills in Copilot Credits, and the spending controls admins can use.

    Michael Corey

    Michael Corey

    Co-Founder & COO, LicenseFortress

    November 2026
    7 min read
    Microsoft Copilot billing: What the license covers and what gets metered

    Here's the question I keep hearing from IT and finance teams: can we get charged beyond the seat price, and who controls that spend? Short answer: yes, you can. A Copilot license and Copilot usage charges are now two separate things. Microsoft bills a growing list of AI services by usage, measured in Copilot Credits, on top of the per-user license (Microsoft). The good news is that admins get real controls. The catch is that you have to know where they are, and for some purchases they come switched on with a default limit.

    A quick note on names. Microsoft's newer license pages call the products Microsoft Copilot and Microsoft Copilot Business, while Partner Center still says Microsoft 365 Copilot Business (Microsoft, Microsoft Partner Center). I use the Microsoft 365 names below. They're the same products.

    What each Copilot product covers and what gets metered

    Microsoft 365 CopilotMicrosoft 365 Copilot BusinessCopilot Studio
    What it isPer-user add-on for eligible enterprise, government and education plans. Included in Microsoft 365 E7.Add-on for organizations with up to 300 users on eligible Microsoft 365 Business plans. Same Copilot capabilities, annual commitment, up to 300 licensed users per tenant.The tool for building agents. Access comes through a free Copilot Studio user license (which requires a tenant prepaid Copilot Credit pack), the Copilot Studio authors setting, a Microsoft 365 Copilot license, or a trial.
    What the license includesCopilot for each licensed user. The license also lets that user build agents in Copilot Studio for the Microsoft Copilot harness.The same Copilot capabilities as Microsoft 365 Copilot.Building and running agents draws on Copilot Credits rather than a flat fee.
    What can incur separate usage chargesServices Microsoft bills in Copilot Credits, including Cowork, advanced work in SharePoint and OneDrive, the Work IQ API, and models with usage-based billing in Copilot Chat and Office. Microsoft notes some of these also require a Copilot license.The same Copilot Credit services. For new purchases through a CSP partner, usage-based billing becomes the default from January–March 2027 (details below).Copilot Credits bought through pay-as-you-go meters billed to Azure each month, a one-year prepurchase plan, or prepaid credit packs.
    Spending controlsSpending policies in the Microsoft 365 admin center under Copilot > Cost management: who can use each service, spending limits for users, environments and agents, alerts and threshold notifications.The same admin center controls. CSP purchases also let limits be changed in Partner Center.Billing policies in the Power Platform admin center link environments to an Azure subscription. You can unlink an environment at any time, and usage after that isn't billed. You can also opt in to managing Copilot Studio spend in the Microsoft 365 admin center.
    Who manages themAdmins in the Microsoft 365 admin center. For Copilot pay-as-you-go services, Microsoft lists Global, Billing and AI administrators. Read-only roles can view consumption without changing policies.Your admins, plus your CSP partner in Partner Center.Admins in the Power Platform admin center, or in the Microsoft 365 admin center if you opt in.

    Sources: license options, Copilot Credits billing and cost management, Copilot Studio billing and licensing, pay-as-you-go overview.

    Two details in that table matter more than they look. First, a license alone doesn't settle the bill. Whether a charge applies depends on the user, the feature and where the agent runs. A licensed user running Cowork can still consume credits. Second, spending policies have an Auto-apply new services setting that is on by default, so future Copilot services and agents inherit the policy automatically. That's convenient, but it also means new services can start consuming under limits you set for something else. Microsoft suggests reviewing existing policies and turning the setting off where you want to approve new services first (Microsoft).

    Copilot Chat and SharePoint agents run on pay-as-you-go

    Microsoft runs a separate pay-as-you-go service for Copilot Chat, SharePoint agents and the Copilot Retrieval API (preview). It's off by default. Admins connect a billing policy, can add a budget that sends email alerts at percentage milestones, and can disconnect the policy, which removes access to the metered agents for the users it covered (Microsoft).

    The January–March 2027 change for Copilot Business bought through CSP

    This one applies only to new Microsoft 365 Copilot Business subscriptions purchased through the Cloud Solution Provider (CSP) program. Microsoft originally planned to turn usage-based billing on by default from December 1, 2026. On November 3, 2026, it moved that to a rollout planned to begin during its fiscal Q3, January–March 2027 (Microsoft Partner Center).

    What happens in that scenario:

    • Microsoft creates the Azure setup automatically and applies a default spending limit of 4,000 Copilot Credits per user per month for all users in the organization. Microsoft's own example: 100 Copilot Business users could consume up to 400,000 credits a month under the default limit, billed on actual use.
    • Pay-as-you-go is the default billing setup. It covers Copilot Cowork, Work IQ APIs and GitHub Copilot Harness today, and Microsoft expects to add more services.
    • A new purchase also turns on usage-based billing for existing Copilot Business licenses in the same tenant.
    • Admins can adjust the limit in Partner Center or the Microsoft admin center. Microsoft says disabling usage-based billing might limit access to some AI experiences.

    What's out of scope: Microsoft 365 Copilot (enterprise), education, nonprofit and GCC offers. Upgrades to an eligible Copilot Business offer don't get the setup automatically (Microsoft Partner Center).

    How to see usage before the invoice arrives

    Microsoft gives you a few places to watch consumption before it turns into a bill:

    • Cost management dashboard (Microsoft 365 admin center, Copilot > Cost management): consumption by spending policy, user, group, agent, service and funding source, plus policy alerts and user-level threshold notifications.
    • Pay-as-you-go Cost Management pages for Copilot Chat and SharePoint agents, with a cost breakdown also available in the Azure portal.
    • Copilot Cost Management API through Microsoft Graph. It reports usage in credits only, with no pricing, invoices or currency amounts, so you still need Azure billing to see the dollar figure.

    Sources: Copilot Credits billing and cost management, pay-as-you-go overview.

    Need a refresher on Enterprise Agreements, MCA-E and CSP? See the Microsoft Licensing FAQ. For dated Microsoft announcements, see Vendor Updates.

    What I'd check before renewal

    First, list every Copilot service people are actually using, not just the seats you bought, and match each one to the table above. Then open the cost management dashboard and read your spending policies: what the limits are, who they cover, and whether Auto-apply new services is on. If you buy Copilot Business through a partner, ask them directly whether your next purchase lands in the January–March 2027 rollout and what limit you'll start with. 4,000 credits per user per month is a ceiling, not a budget. Finally, decide who owns the number. Give finance a read-only role so someone outside IT sees consumption before the invoice does.

    FAQ

    About the author

    Michael Corey

    Michael Corey

    Co-Founder & COO, LicenseFortress

    Michael writes on vendor strategy, audit behavior and the business realities of enterprise software agreements.