The short answer
Microsoft 365 Copilot and Copilot Studio are different products with different licenses. Microsoft 365 Copilot is a per-user add-on at $30 per user per month on an annual commitment. Copilot Studio is a tenant-wide license that includes Copilot Credit capacity packs of 25,000 credits each at $200.00 per pack per month, or pay as you go on consumption. One is a finished assistant you assign to people. The other is a builder you use to create agents. Buying one does not give you the other, and most organizations that need custom agents end up paying for both.
Last updated: July 2026. Sources: Microsoft 365 Copilot pricing pages and Microsoft licensing announcements.
Copilot licensing generates more confused procurement threads than any other Microsoft product line right now, and the reason is simple. Microsoft attached one brand to at least four things that price completely differently. When a CFO asks "what does Copilot cost," there is no single correct answer, and the person answering usually picks the wrong one for the question being asked.
This breaks the family apart, explains which license does what, and shows where the real cost sits for the use case that drives most Copilot purchases: helping people find answers in company content.
What is the difference between Microsoft 365 Copilot and Copilot Studio?
Microsoft 365 Copilot is a finished product. You license it per user, and that user gets Copilot inside Word, Excel, PowerPoint, Outlook and Teams, grounded in your Microsoft 365 tenant. There is nothing to build. You assign the license and the capability appears.
Copilot Studio is a low-code development environment. You use it to design custom agents, connect them to knowledge sources, give them actions, publish them to a channel like Teams or a website, and govern them centrally. It produces something. It is not something.
The mistake that costs money is treating Copilot Studio as the cheap way to get Copilot. It is not cheaper and it is not the same thing. It is the way to get behavior Microsoft 365 Copilot does not have out of the box, and it comes with build effort, ongoing maintenance and a consumption meter.
| Product | What it is | How it is priced |
|---|---|---|
| Microsoft 365 Copilot | Assistant inside the Office apps, grounded in your tenant | $30 per user per month, annual commitment, requires a qualifying base plan |
| Copilot Business | Bundled Copilot for smaller Microsoft 365 Business customers | $21 per user per month from July 1, 2026, after the $18 promotional rate ended |
| Copilot Chat | Chat experience grounded on web content, not your tenant data | Included with eligible Microsoft 365 subscriptions |
| Copilot Studio | Low-code builder for custom agents | Tenant-wide license, $200.00 per 25,000 Copilot Credits per month, or pay as you go |
| Microsoft 365 E7 | Top enterprise suite with Copilot bundled in | $99 per user per month |
What is a Copilot Credit?
Microsoft describes Copilot Credits as a flexible, usage-based system that powers Copilot experiences and agents, consumed whenever Copilot or an agent performs a task or generates a response, whether that is summarizing, answering a question, generating content or completing an action. Until September 2025 the same unit was called a message. Same plumbing, new name.
Different actions consume different amounts. A simple scripted answer is cheap. A generative answer costs more. Grounding a response in your tenant graph costs meaningfully more again, and an autonomous agent action is the most expensive class. Microsoft's public pricing page confirms that a varying number of credits is billed depending on the specific usage but does not publish a per-action table, so the specific multipliers you will see quoted in blog posts are secondary sourced. Treat them as directional and instrument your own usage.
The budgeting consequence is what matters. A consumption meter means your bill rises with adoption. If the agent is unpopular, you overpaid for capacity. If the agent is a hit, the finance conversation you have in month four is not the one you had in month one. Neither outcome is a disaster, but neither is what most people think they are signing up for when they read "$200 a pack."
Do I need a Microsoft 365 Copilot license to use Copilot Studio?
They are licensed separately, so strictly no. In practice the two interact. Microsoft's guidance has been that internal agent interactions by users who already hold a Microsoft 365 Copilot license do not draw down Copilot Credits, which is a significant cost lever if most of your agent users are already licensed. Because the details here have shifted more than once since the credits rename, confirm the current rule with your licensing partner rather than trusting a blog post, including this one.
Where organizations get caught is the external or unlicensed audience. An agent published to a public website, or used by frontline staff who do not hold a Copilot seat, consumes credits for every interaction. That is the scenario where a successful pilot produces an unwelcome invoice.
Can Copilot Studio search Slack, Notion or Google Drive?
Not the way it reaches Microsoft 365 content. Copilot and Copilot Studio are Microsoft-first by design, and the deep, permission-aware grounding is in SharePoint, OneDrive, Teams and Exchange. Reaching outside that boundary means Microsoft Graph connectors or custom connections you build and maintain in Copilot Studio.
That is not a criticism of the product, it is a scoping fact that decides projects. If 80 percent of your institutional knowledge sits in Microsoft 365, Copilot reaches it and the license does its job. If a meaningful share lives in Slack threads, Notion pages, Google Drive folders, Jira tickets or Salesforce records, the license alone will not produce the outcome people expect, and the gap gets filled with engineering time. Price that time. It is usually the largest line in the project and it is almost never in the quote. The same trap shows up whenever a team tries to unify sources by hand instead of using something purpose-built to keep apps, APIs and databases connected without a bespoke integration for each one.
Which Copilot should I buy for finding answers in company content?
Work backwards from where the content is.
If everything lives in Microsoft 365 and your users are already in Word and Outlook all day, Microsoft 365 Copilot at $30 per user per month is a reasonable buy, and E7 at $99 is worth pricing against E5 plus the add-on because the bundle sometimes wins.
If you need bespoke agent behavior, custom actions or a workflow that ends in something being done rather than said, Copilot Studio is the right tool and the credits model is the price of that flexibility.
If what you need is that anyone can ask a question in plain language and get a trustworthy, cited answer drawn from every app the company runs, neither one is a clean fit. That job wants a finished enterprise search product, not an assistant scoped to one vendor's cloud or a builder you have to staff. The full pricing breakdown sits on our Microsoft Copilot pricing page, and the scope comparison against the builder is on the Copilot Studio alternative page.
How to compare the real numbers
Build a three-year total for each option and include four things the quote will not: the base license each Copilot seat requires underneath it, the credit consumption you expect once adoption is real rather than pilot-sized, the engineering days to connect non-Microsoft sources, and the ongoing owner for those connections after launch. Then compare that number to a flat per-seat product that covers every app on day one.
Sometimes Microsoft still wins, particularly in a pure Microsoft shop where the drafting features carry real value on their own. Often it does not, because the reason you started this project was coverage, and coverage is exactly what the seat price does not buy.
InSearch is built for the coverage case. One query across Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce. A written answer with inline citations to the exact source, so people can verify instead of trusting. Item-level permissions inherited from each app and enforced at query time. One transparent per-seat price, no consumption meter, and nothing to build. Ask it something in the box above.