If you have been pitched Microsoft AI in the last year, you have probably heard "Copilot" used to mean five different products with five different price structures. That is the first problem to solve. You cannot build a budget until you know which product is on the table, and the answer changes whether you are buying seats, buying capacity, or buying nothing up front.
This guide covers how each one is licensed, what triggers a charge, and the readiness work that determines whether the spend returns anything. We do not quote prices. Microsoft changes them, and a number in a blog post ages badly. Every section links to the official pricing page where the current figure lives.
The Copilot naming problem
Microsoft has attached the Copilot name to products that have almost nothing in common commercially. Here is the untangling.
Microsoft Copilot is the consumer experience, used by signing in with a personal Microsoft account. It is free, it is not connected to your company's data, and it is not something you buy. Microsoft's admin guidance draws a firm line: the personal app does not work for users signing in with a work account.
Microsoft 365 Copilot Chat is the work-account chat experience, included at no extra cost with a long list of Microsoft 365 and Office 365 subscriptions. It grounds answers in the web rather than in your company's files. If your team is "already using Copilot" and nobody bought anything, this is almost certainly what they are using.
Microsoft 365 Copilot is the paid per-user add-on. This is the one that reads your organization's own email, documents, chats, and meetings, and the one that appears inside Word, Excel, Outlook, and Teams. When a salesperson quotes a per-seat figure, this is the product.
Copilot in Dynamics 365 refers to AI features inside the Dynamics 365 business applications. Basic capabilities come with the application license. Agents built on top consume a separate meter.
Copilot Studio is the tool for building custom agents, sold as consumption rather than per seat.
GitHub Copilot is for software developers writing code. It is licensed and billed entirely separately, and as of June 2026 it moved to usage-based billing on AI Credits. If your business does not employ developers, set this one aside.
Microsoft Foundry is the platform for building custom AI applications. It was called Azure AI Foundry until Microsoft renamed it in November 2025. There is no seat license at all.
Microsoft 365 Copilot: the per-user add-on
Microsoft 365 Copilot sits on top of an existing subscription rather than replacing one. You keep paying for your base Microsoft 365 plan and add a second per-user charge alongside it.
Prerequisites. Every user who gets Copilot needs a qualifying base license first. Microsoft's license options page lists the full set, which includes Microsoft 365 E3, E5, F1, F3, Business Basic, Business Standard, Business Premium, Office 365 E1, E3, E5, and F3, plus standalone Exchange, SharePoint, OneDrive, Teams, Visio, and Project plans. Check the list rather than assuming, because the plan you are on may qualify even if you did not expect it to.
Seat minimums. There is no longer a minimum seat count. Microsoft required 300 seats when the product first launched, and that requirement is gone. You can buy one license.
The small business version. A separate add-on, Microsoft 365 Copilot Business, serves organizations on a Microsoft 365 Business plan. Per Microsoft's Copilot Business FAQ, it delivers the same capabilities, requires Business Basic, Business Standard, or Business Premium underneath, and supports up to 300 seats per tenant. Above 300 users, you move to the standard Microsoft 365 Copilot add-on.
Commitment terms. Copilot Business is sold on an annual commitment with a choice of monthly or annual billing, with no month-to-month option. The enterprise add-on is offered on both annual and monthly terms; the current structure is on the Microsoft 365 Copilot pricing page. Take the annual term and the annual billing option on both. The annual term is the cheaper rate, paying up front is one invoice a year instead of 12, and because seats cannot be reduced mid-term either way, the monthly premium buys you very little here.
Where it works. Rather than list features, think about who gets time back. The service description covers Word, Excel, PowerPoint, OneNote, Outlook, Teams, SharePoint, and OneDrive, plus a dedicated Microsoft 365 Copilot app containing Chat, Search, Notebooks, Pages, Researcher, and Analyst. The roles that report the clearest return are the ones carrying the most written material: a controller who stops rebuilding the same variance commentary every month, an operations manager who gets a missed Teams meeting summarized with the decisions pulled out, and an account manager who walks into a renewal with a year of correspondence condensed into a page.
One newer wrinkle. Microsoft introduced Microsoft 365 E7 on 1 May 2026, bundling Microsoft 365 E5, Microsoft 365 Copilot, the Entra Suite, and Agent 365 into a single plan. If you are already at E5 and heading toward Copilot everywhere, ask your partner to price the bundle against the components.
The readiness gotchas that decide whether it is worth buying
This is the section that matters most for a company under a few hundred people, and it is the part most often skipped in a demo.
Copilot inherits each user's existing permissions
Microsoft states it directly in its data and privacy documentation: Copilot "only surfaces organizational data to which individual users have at least view permissions."
That design has a practical consequence. Copilot grants nobody new access, and it makes existing access much easier to use. A file in a SharePoint site shared with "everyone in the organization" three years ago has always been findable. Search was a clumsy way to find it. Ask a natural-language question and the same file surfaces in a sentence.
So the question to answer before you buy is whether your current sharing settings match what you would choose today. Most organizations that have used SharePoint, OneDrive, and Teams for several years have accumulated some broad sharing that nobody would set up deliberately now. That is normal, measurable, and fixable.
The good news on tooling
A Microsoft 365 Copilot license includes SharePoint Advanced Management, the tool for exactly this. Microsoft's readiness guidance covers an oversharing baseline report, a permissioned user report showing who can reach a given site, and site-level access restriction to hold a sensitive site out of search results while you review it. Microsoft also publishes a foundational deployment guide for the sequence. Copilot honors Microsoft Purview sensitivity labels and the encryption applied through them.
The order of operations is: run the reports, look at the sites that show up as broadly shared, fix the ones that should not be, then roll out. For a company of 50 to 200 people this is usually days of work, not months.
Value depends on where your content lives
Copilot reads what is in Microsoft 365. If your working documents sit on an office file server, in a shared Dropbox, or in a line-of-business system, Copilot cannot see them by default. Companies that moved to SharePoint and Teams years ago tend to get value on day one. Companies still running on mapped network drives get a thin experience and conclude the product does not work, when the content was not there to read.
Partial rollouts are normal
Because it is licensed per user, you are not obliged to buy for everyone. Buying a first block for the roles with the heaviest writing and meeting load, running it for a quarter, then measuring before expanding is the sensible pattern, and the cheapest way to find out whether the answer for your business is yes.
Copilot Studio: capacity, not seats
Copilot Studio is where you build a custom agent, for instance one that answers customer questions on your website or handles an internal request arriving 40 times a week.
The unit of measure changed. This trips up anyone working from older material. Microsoft's licensing documentation states that on 1 September 2025 the currency changed from messages to Copilot Credits, with no change to the quantity in a prepaid pack or the pay-as-you-go rate. If a proposal in front of you still says "messages," it uses retired terminology.
What consumes a credit. Different agent activities cost different amounts. Microsoft's billing rates page is the authoritative table, and its shape is worth understanding even without the numbers:
| Activity | Relative cost |
|---|---|
| A scripted, pre-written answer | Lowest |
| An AI-generated answer | Roughly double a scripted answer |
| An agent action, such as calling a system or completing a step | Higher again |
| Grounding an answer across your whole Microsoft 365 tenant | Highest of the common four |
A single question can trigger several of these at once, so a complex question costs meaningfully more than a simple one. Microsoft publishes an agent usage estimator that models expected consumption from traffic volume and agent design. Run it before committing to anything.
Capacity is pooled at the tenant level. You buy credits for the organization, not per person or per agent. Administrators then allocate portions to specific environments and set per-agent monthly caps in the Power Platform admin center.
Three ways to pay.
- Prepaid capacity packs. A fixed block of credits per tenant per month. Unused credits do not roll over.
- Pay-as-you-go. Billed through an Azure subscription with no upfront commitment. You link an environment to the subscription with a billing policy and pay for what was consumed at month end. This is the low-risk way to start.
- A pre-purchase plan. A one-year prepaid commitment, bought through the Azure portal, that draws down across eligible Microsoft products.
Current figures are on the Copilot Studio pricing page.
What happens when you run out. On prepaid capacity, Microsoft allows a grace margin rather than cutting you off at your exact limit. Enforcement triggers when a tenant reaches 125% of prepaid capacity, at which point custom agents are disabled and an email goes to the administrator. An in-progress conversation is allowed to finish. Agent flows are handled separately and stop starting new runs once prepaid capacity is exhausted, while the agent keeps answering questions normally. Pay-as-you-go is not subject to this enforcement, because overage bills to your Azure subscription. That trade-off is the real decision: prepaid gives you a hard ceiling and a risk of interruption, pay-as-you-go gives you continuity and a variable bill.
The inclusion that people misread. If a user holds a Microsoft 365 Copilot license, their use of agents inside Microsoft 365, Teams, and SharePoint does not draw down Copilot Studio capacity for the common activity types. Read the boundary carefully, because Microsoft defines it as employee-facing usage. An agent answering questions for your own licensed staff is covered. An agent on your public website talking to customers is not, and it consumes credits regardless of how your staff are licensed.
Microsoft Foundry: consumption, no seats
Microsoft Foundry is where a custom AI application gets built. There is no user license. You pay for what the models process.
Tokens. Model usage is measured in tokens, the small chunks of text (roughly a short word or part of one) that a model reads and produces. You are billed for what goes in and what comes out.
Four ways to deploy. Microsoft's provisioned throughput documentation sets out the options:
- Standard. Pay per token, no commitment, capacity shared with other customers. The right default for development, testing, and variable traffic.
- Priority processing. Per token at a priority rate, with a defined latency target.
- Provisioned. You reserve dedicated capacity measured in provisioned throughput units, billed per unit per hour whether or not you send traffic, with Azure Reservations on one-month or one-year terms for a lower effective rate.
- Batch. A discounted rate for bulk work processed asynchronously.
Two cautions on provisioned capacity: holding quota does not guarantee capacity is available in your region when you deploy, and a reservation is a billing discount rather than a capacity guarantee. Microsoft's guidance is to confirm a deployment works first and buy the reservation afterward.
A proof of concept costs very little. Production needs a forecast. Testing an idea with a few hundred queries is inexpensive. A customer-facing workload running continuously is a different exercise, and it needs a real volume estimate before anyone signs anything.
The cost lines people forget. The model is rarely the whole bill. Budget also for the storage holding your documents, the search and retrieval index that finds the right passage before the model answers (typically Azure AI Search, billed on its own meter), and the hosting, networking, and monitoring around the application. On small workloads these supporting services can exceed the model spend. Current rates are on the Foundry Models pricing page and the Azure OpenAI pricing page.
Copilot in Dynamics 365 and the Power Platform
Two layers, billed differently.
Included in the base license. Core Copilot capabilities inside the Dynamics 365 applications come with the application license at no separate charge. Summarizing a record, drafting an email from within the system, and similar assistive features fall here.
Metered separately. Prebuilt and custom agents, including the autonomous kind that trigger on an event rather than waiting for someone to ask, consume Copilot Credits on the same meter as Copilot Studio. Those credits pool at the tenant level and are allocated out to environments.
One boundary worth noting: Power Automate cloud flows are licensed under Power Automate and are not billed as Copilot Credits, while agent flows built in Copilot Studio are. Power Platform licenses are not included with a Microsoft 365 Copilot license.
Some Dynamics 365 plans are reported to include a monthly credit allotment per user that pools across the tenant. We could not confirm that allotment in Microsoft's own published Copilot Credits guidance, so verify any figure quoted to you in writing against the current licensing terms before it goes into a budget.
Data residency, tenant boundaries, and model training
Microsoft's data, privacy, and security documentation for Microsoft 365 Copilot states the commitments plainly, and it is a short enough page to read yourself:
- Prompts, responses, and data accessed through Microsoft Graph are not used to train the foundation models, including the ones Copilot uses.
- Copilot carries the same privacy, security, and compliance commitments as the rest of Microsoft 365, including the General Data Protection Regulation and the EU Data Boundary. For customers in the European Union, Copilot is an EU Data Boundary service. Customers elsewhere may have queries processed in the United States, the EU, or other regions.
- Data residency commitments live in the Microsoft Product Terms and the Data Protection Addendum at the Microsoft licensing terms site. Copilot became a covered workload on 1 March 2024.
- Tenant isolation runs on Microsoft Entra authorization and role-based access control, the same controls as the rest of Microsoft 365.
- The Copilot Copyright Commitment covers commercial customers who use the built-in guardrails and content filters.
Two details for a compliance-minded buyer: models supplied by Anthropic as a subprocessor are currently excluded from the EU Data Boundary, and administrators choose whether third-party models are used at all.
Commitment terms, mid-term changes, and how you buy
Annual versus monthly. Annual commitments carry a lower effective rate. Monthly costs more per seat and lets you stop. For a first rollout where you are still testing the case, the monthly premium often buys useful flexibility.
Mid-term changes are limited. Microsoft's Copilot Business FAQ is explicit that an existing Microsoft 365 Copilot customer must wait until the annual commitment ends before changing plans, that licenses do not convert automatically at renewal, and that a Business plan carrying Copilot Business cannot be upgraded to an Enterprise plan until the commitment date. You can add seats at any time. Reducing them or switching plans waits for the anniversary. Size the first purchase to the people you are confident about, because adding is easy and unwinding is not.
Cloud Solution Provider versus direct. You can buy through the Microsoft 365 admin center, direct from Microsoft, or through a Cloud Solution Provider partner. The licensing terms are the same either way. What differs is who handles the administration, who advises on which plan fits, and who you call when a license assignment does not behave. Copilot Studio pay-as-you-go additionally requires an Azure subscription with a billing policy attached, which is one more thing to set up correctly before the first invoice arrives.
A short decision guide
"I want to give my finance team time back." Microsoft 365 Copilot, per user, for the finance team only. Confirm your base licenses qualify, run the SharePoint oversharing reports first, and start with a small block on a term you can exit. The measurable outcome is hours returned on month-end commentary, reconciliation write-ups, and meeting follow-up.
"I want an agent answering customer questions on our website." Copilot Studio, billed as consumption. Start on pay-as-you-go so you are not guessing at capacity, model the volume with Microsoft's estimator, and remember that customer-facing traffic consumes credits regardless of how your staff are licensed. Move to prepaid capacity once you have real usage to size against.
"I want a custom AI application built around our own data." Microsoft Foundry, consumption billing, no seats. Budget the proof of concept as a small number and do not extrapolate from it. When it works, forecast the production workload properly and include storage, the search index, and hosting alongside the model.
Where to start
The cost surprises here come from one of three places: buying seats before the content and permissions were ready, sizing a prepaid capacity pack from a guess, or forecasting a custom application on the model rate alone. All three are avoidable with a couple of hours of work up front.
If you are weighing a Microsoft AI proposal, bring us the quote and a list of what your team is licensed for today. We will map it against what your tenant already includes, what the readiness work would involve, and which of the three licensing shapes your use case calls for.