What the Microsoft 365 Copilot price list doesn't tell you

The decision about Copilot usually happens in a single meeting. Someone brings the price list, there’s a number per user per month on the table, you multiply it by headcount and say yes or no. It’s a legitimate way to decide about a purchase — we’ve been doing it with licences for years.

But with Copilot, that single number tells you almost nothing about what living with it for a year will be like. The terms of the commitment, how quickly it sees new content, and what can and can’t be excluded from it are all things the price list doesn’t mention — and they’re precisely what determines whether the rollout is calm or turns into a series of unpleasant surprises.

This isn’t an argument against Copilot. It’s an excellent tool and it makes sense for plenty of organisations. Everything below comes from Microsoft’s own documentation, and none of it is a defect — these are characteristics you can plan around, provided you know about them in advance.

The annual commitment has a seven-day window

The enterprise edition of Copilot is sold as an add-on to Microsoft 365 at USD 30 per user per month with an annual commitment. That much is well known. What’s less known is what “annual commitment” means in practice.

Under the rules of the New Commerce Experience, the model most subscriptions are sold through today:

• For the first seven days after activation you can cancel the subscription or reduce the number of licences, with a prorated refund.
• After seven days, you can’t. No cancellation, no reduction. You pay until the anniversary.
• You can add licences at any time — and each newly added licence gets its own seven-day window.
• Leaving or shrinking the order is only possible at the anniversary, by turning off auto-renewal before the term ends.

That asymmetry matters more than it looks: licences can only go up during the year, never down. Buy a hundred licences in January, discover in March that you actually need thirty, and you’ll pay for a hundred until December. An overestimate can’t be corrected for a whole year.

If you buy through an Enterprise Agreement, your terms are negotiated individually and this may not apply literally. For ordinary purchases through a partner or directly on the web, it does.

Monthly payment is not a monthly commitment

This is the most common misunderstanding I come across. The Copilot page also shows an option to pay monthly, at USD 31.50. It looks like flexibility. It isn’t.

Microsoft states it directly in the footnote: “Or $31.50 paid monthly (Annual commitment).” In other words, you spread the payment across twelve instalments and pay five per cent extra for the privilege, but the commitment stays annual. You don’t get the option to leave; you get a different payment schedule.

A genuine monthly subscription you can cancel at any time exists only in the Copilot Business edition for organisations of up to 300 users. There the price list looks like this:

Edition	Price per user per month	Commitment
Annual, paid yearly	USD 18 (promotional, normally USD 21)	annual
Monthly subscription	USD 25.20	none, cancel anytime

So the ability to walk away costs roughly a fifth more than the standard price — and about forty per cent more than the promotional one. That promotional price, according to the small print, applies only to the first year.

For completeness: Copilot also has a route without per-user licences, through agents billed by consumption. That’s a different category of tool, which we wrote about in Paying for outcomes, not headcount — not a substitute for the full licence.

The semantic index only appears with the first licence

Copilot doesn’t search your data by keywords. It builds on a semantic index — a vector representation of your content that lets it understand the meaning of a question, not just word matches.

Here’s what tends to surprise people: not every tenant has this index automatically. It’s created only once you assign at least one paid Copilot licence in the tenant. Until then you have the classic Microsoft Search index and nothing more. Indexing then happens on its own; the administrator does nothing.

The practical implication for decision-making: a pilot with five licences doesn’t start an index just for those five people — the tenant-level layer of the index is created for the organisation as a whole. It’s worth knowing that before someone in the room says “let’s just try it out.”

Copilot usually sees new content the next day

This is the most practical piece of information in the whole article, and it’s certainly not on the price list. Microsoft puts it in the semantic indexing documentation like this:

“New documents that are added to SharePoint Online sites that are accessible, via site inheritance, by two or more users are indexed daily. When an indexed user and tenant level document is updated, the changes are immediately indexed.”

Translated into practice:

• A new document in SharePoint reaches the index in a daily batch. Upload a policy on Monday afternoon and Copilot may not know about it until Tuesday. With large libraries it can take longer.
• A change to an already indexed document is reflected immediately. Correct an existing policy and Copilot knows straight away.

That difference is counter-intuitive and worth telling people up front. The worst possible first experience with enterprise AI is the one where a user uploads a document, asks about it immediately, and gets back “I didn’t find anything.” It isn’t a fault or a permissions error — indexing simply hasn’t run yet.

This applies, incidentally, to any solution built on search over SharePoint, including ours. The only difference is how many layers sit between the content and the answer.

You can exclude a site, not a library

The second question everyone with something sensitive in their tenant asks: how do I keep a specific library out of the AI?

The answer is uncomfortable. The tools Microsoft offers for limiting Copilot’s reach — Restricted SharePoint Search, Restricted Content Discovery and Restricted Access Control — all work at site level, not library level. For one specific library, two routes remain and both come at a cost:

1. Turn off search for the library (Library settings → Advanced settings → Allow items from this document library to appear in search results = No). It works reliably, but the content also disappears from ordinary search for your own people. Microsoft itself recommends this only for genuinely sensitive data, typically payroll or HR.
2. A sensitivity label plus a DLP policy with an action that stops Copilot processing the content. A cleaner solution — the content stays discoverable for people — but automatic labelling and DLP for Copilot belong to E5. We’ve written separate instalments on how labels and DLP work: Sensitivity labels and DLP.

And one more limitation worth remembering: the exclusion applies to both at once. The documentation is unambiguous — there is no option to remove content from the semantic index only and leave it in Microsoft Search, or the other way round. Whatever you hide from the AI, you hide from your own employees’ search as well.

A final note on this point, because it gets forgotten regularly: none of this is a security boundary. Anyone with permissions to the library will open the file directly, index or no index. Security is a matter of permissions, not invisibility.

The index can’t be turned off, and Excel isn’t in it

Two details that surprise even experienced administrators.

Semantic indexing cannot be disabled. The documentation says so plainly — it is an improvement to Microsoft Search, Microsoft enables it, and the administrator cannot turn it off. You can exclude specific sites, but not the capability itself.

Excel isn’t in the semantic index. The table of supported content types lists Word, PowerPoint, PDF, pages (aspx), OneNote and connector data. Workbooks (.xlsx) aren’t among them. Excel is still found by classic search and Copilot will read it when you point at it directly in a prompt — but it won’t be captured semantically. For organisations whose key data sits in price lists and registers, that isn’t a detail.

Where the model runs, and where data may travel

The last point is more for those dealing with compliance. The semantic index and your interaction history stay inside your tenant’s boundary, for European tenants within the EU Data Boundary by default, and the source content isn’t copied anywhere — Copilot reads it in place. That’s good news and worth saying out loud, because a lot of inaccuracy circulates on the subject.

Two things do apply, though:

• The model inference itself runs on Microsoft’s infrastructure, not in your Azure subscription. You don’t choose the model.
• Since 17 April 2026, so-called Flex Routing is in effect: at times of high demand, inference may take place outside the EU Data Boundary. Data at rest stays in the EU, but the setting is enabled by default and the administrator has to switch it off if regulation demands it. If you fall under stricter processing-location requirements, check this one.

What to do about it in practice

None of the above is a reason not to buy Copilot. It’s a reason to buy it with your eyes open:

• Don’t licence the whole organisation on day one. Since the number can only go up, start lower and add. The other direction won’t be available for a year.
• Day seven is the last chance to change your mind. Plan the pilot so it gives you an answer about whether to continue before then.
• Tell people about daily indexing before they run into it. You’ll save yourself a queue of “the AI can’t see my document” tickets.
• Review permissions before licences. If your tenant holds content shared with everyone, Copilot will surface it faster than you can find it. We covered this in detail in SharePoint Online and AI readiness.
• Check Flex Routing if the processing location of your data means anything to you.

What to take away

1. An annual commitment means a year. The seven-day window after activation is the only moment you can back out or reduce licences — after that, you can only add.
2. Monthly payment isn’t a monthly commitment. In the enterprise edition, five per cent buys you a payment schedule, not freedom. The only genuinely cancellable option is the Copilot Business subscription for organisations up to 300 people, at a premium of around twenty per cent.
3. Operational limits are settled before licences. Daily indexing of new content, exclusions that only work per site, and Excel sitting outside the semantic index aren’t obstacles — but there’s a difference between knowing about them in advance and discovering them in front of your users.

---

At EP365 we help organisations decide about enterprise AI before the order is placed — we go through permissions, content readiness and how many licences you actually need. We most often handle it as an environment audit or a governance design. If you’re facing a decision about Copilot, drop us a line — we’ll go through it over your specific tenant.

In the next instalment we’ll look at what happens to content at the end of its life — retention, archiving, and why lifecycle decides whether your AI answers from valid documents or from ones that should have disappeared three years ago.