Insights

Microsoft 365 Copilot for a small office: what to check before you switch it on

18 November 2026 · Daniel Haviar

Copilot in Microsoft 365 is tempting for an obvious reason. It summarises a long mail thread, drafts the minutes and finds in seconds what would take half an hour in shared files. One thing still needs saying before you buy licences: Copilot sees what the signed-in user sees.

If someone can open a folder they shouldn’t, Copilot will happily summarise it for them. This happens often in small firms: a case-file folder shared with the whole team “just for a moment”, a forgotten Teams link, a former colleague’s account nobody closed. Copilot doesn’t create this mess. It only makes it visible.

Permissions first, then licences

Before you deploy it, go through SharePoint, OneDrive and the teams in Teams: who has access to which space, which links are still open, and which libraries inherited permissions from an old file share. Material meant for leadership, for finance or for a legal file has to be separated from what the whole office may see. Only once that is right does it make sense to turn Copilot on.

The same step includes a clean-up of accounts. Anyone who has left the firm must lose access on the day they go. A guest account for a supplier should not hang around for months after the job ends. Administrator rights belong on a separate account, not on everyday mail. If you do not have that foundation, Copilot is not another tool. It is a magnifying glass placed on the mess.

What Copilot will see, and what it will do with it

Copilot works with your data in Microsoft 365. That is both the advantage and the risk. The advantage is that you do not have to paste case files into a third-party chat. The risk is that the answer is only as sound as the permissions and the quality of the material. If three versions of the same contract sit in a library, it may reach for the wrong one. If a note marked “for the director only” lives in a space the whole team can open, Copilot may use it in an answer for anyone in that team.

So it is worth deciding up front what you want to use it for first: summarising mail, drafting minutes or searching internal policies. Start with one team and one kind of task, not the whole firm at once. A pilot will show whether the time saving is real, and where the model reaches for files you did not expect in the answer. Only then do you widen it.

People, rules, and what stays outside

Even after Copilot is switched on, people will try other tools. Public chatbots are fast, and nobody sees them on a private phone. If someone pastes a draft contract or a client list into one of them, the data has left your tenant. A policy does not have to be a long document. It does have to say which data may go into approved tools, which may not, and what to do when someone is unsure. Add a short training session built on your own examples, not a general presentation about artificial intelligence.

The licences you buy should match the people who will actually get something from the tool. Not everyone in the office needs Copilot on day one. It is more sensible to give it to those who spend the most time in mail and documents, prove the benefit, and only then decide. There is more on how I roll out Copilot and AI agents in practice on the AI for business page.

If you are considering Copilot and want to know first whether you can turn it on safely, I will go through permissions, accounts and the places where sensitive files sit today. Only then does a conversation about licences make sense.

I want to know whether we are ready for Copilot

An AI consultation starts with an audit of permissions, data and licences. I switch Copilot on only once it can no longer reach folders that should stay closed.