Copilot for Microsoft 365: what it does, what it costs you, and what to fix first

What Copilot actually is

Copilot combines a large language model with your organisation's own data through Microsoft Graph. When a user asks a question, Copilot retrieves relevant content the user already has access to — emails, documents, chats, meetings — and grounds its response in that material.

In practice the useful applications in a small business are narrow but real: summarising a long email thread or a meeting recording, drafting a first version of a document from existing material, interrogating a spreadsheet in plain language, and finding a decision someone remembers making but cannot locate. The applications that disappoint are the ambitious ones — asking it to produce finished client-ready work, or to reason accurately over numbers.

The oversharing problem, which is the real story

Copilot honours Microsoft 365 permissions exactly. If a user can open a file by navigating to it, Copilot can use it to answer their question. This sounds safe, and technically it is — but it assumes your permissions reflect your intentions, and in most small businesses they do not.

Consider a typical tenant. Someone created a SharePoint site for the leadership team and shared it with 'Everyone except external users' because that was the quickest option. Salary review documents, redundancy plans and the acquisition discussion are in it. Nobody ever found them, because nobody knew the site existed and nobody went looking. Copilot changes that overnight: an employee types 'what is the salary band for my role' and the model dutifully retrieves what it has permission to read.

This is why the sequence matters. Audit sharing before you buy licences. Look specifically for anything shared with 'Everyone except external users', anonymous sharing links that never expire, HR and finance content sitting in general-access sites, and OneDrive folders shared organisation-wide as a convenience.

• Search for sites and files shared with 'Everyone except external users'
• Expire or revoke long-lived anonymous sharing links
• Move HR, payroll, legal and board content into properly restricted sites
• Apply sensitivity labels to the categories that must never be summarised casually
• Consider Restricted SharePoint Search while you remediate, which limits Copilot to an approved set of sites

Licensing and the honest value question

Copilot is a per-user add-on to a qualifying Microsoft 365 plan. Microsoft has removed the minimum-seat requirement that originally excluded small businesses, so you can now buy a handful of licences — and you should, before you buy many.

Copilot is expensive relative to the base licence. The value case is entirely about whether it saves time for the specific people you give it to, and that varies enormously by role. People who spend their day in long email threads, meetings and document drafting tend to find it genuinely useful. People whose work is in a line-of-business system outside Microsoft 365 often find it does nothing, because Copilot cannot see their actual work.

Run a deliberate pilot. Give it to five people across different roles for a month, ask each of them to note where it saved time and where it wasted it, and then decide. Do not roll it out to everyone because it demonstrates well.

Data handling and what Microsoft commits to

Microsoft's commercial data protection commitments state that Copilot prompts, responses and the organisational data accessed through Microsoft Graph are not used to train the foundation models, and that processing stays inside the Microsoft 365 service boundary with existing compliance commitments applying.

This is the answer to the question most UK directors ask first, and it is a reasonable one. The residual risks are not about Microsoft's training data; they are about your own configuration — who can see what, whether output is being checked, and whether staff are pasting Copilot output into client deliverables without review.

Set an internal usage rule before rollout, in writing and in plain language: Copilot output is a draft, a human is accountable for anything sent externally, and numbers must be verified against the source. That single paragraph prevents most of the realistic harm.

A sensible rollout order

The order that works is remediate, restrict, pilot, train, expand. Fix the sharing problems first because they are the only genuinely dangerous part. Restrict Copilot's search scope while remediation is in progress. Pilot with a small, mixed group. Train people on what it is bad at — accuracy on figures, anything requiring current external facts, anything requiring judgement. Then expand only to the roles where the pilot showed real time savings.

Skipping straight to expansion is the common failure: licences bought for everyone, used properly by four people, and quietly cancelled at renewal.