Microsoft 365 Copilot is coming to your business: what do you agree beforehand?
Copilot sits in Word, Outlook, Teams and Excel, and the licences are often arranged quickly. The questions come afterwards: what can Copilot see, what may staff put into it, and what do you do about the free AI tools people already use alongside it? This article is for the owner, office manager or IT lead who switches Copilot on and wants a few things settled first.
Permissions first, then Copilot
Copilot works within the permissions an employee already has in Microsoft 365. It uses the mail, chats, calendars and files that person can already access, and nothing beyond that. That is reassuring, as long as those permissions are right.
In most businesses that have used Microsoft 365 for a few years, they are not quite right. A salary overview once shared with a link for "people in your organisation". A team site from a project three years ago that the whole company is still a member of. An HR folder in someone's OneDrive shared with an entire department. Without Copilot hardly anyone came across those files, because nobody knew they were there. With Copilot one question is enough, such as "what do my colleagues earn?" or "are there plans for a reorganisation?"
So the risk lies mainly in what is already shared too widely, not in Copilot itself. Before you switch Copilot on, check the permissions:
- Find files and folders shared with a link for everyone in the organisation or for anyone with the link, and limit them to the people who actually need them.
- Go through the SharePoint sites and Teams: who is the owner, who is a member, and is the site still used? Archive or close old sites.
- Put HR, salary, contract and management documents in a place with a small, known group of members.
- Ask a few employees from different departments to search the Microsoft 365 search bar for words like salary, dismissal or appraisal. What they find, Copilot can use too.
If needed, start with a small group of users and expand once the permissions are in order.
Which data in which tool
Copilot with the business account is covered by the agreements your business has with Microsoft. A free AI tool with a personal account is not. There the terms the employee accepted themselves apply, and you have no view of what happens to whatever gets pasted into it.
Make the distinction concrete. For example: customer data, staff data, quotes and contracts only in Copilot with the business account. Public information and general texts without names or figures may also go into other tools. Name the tools and give a few examples from your own work, so nobody has to guess.
Check the output before it leaves the building
Copilot writes fluently, and that is exactly why mistakes stand out less. A summary can miss an agreement, a draft email can quote an amount from an outdated file. Agree that everything going to a customer, supplier or authority has been read and checked by a person, and that this person is responsible for the content. Not Copilot.
Announce AI note-takers and recordings up front
Having a meeting summarised is one of the first things people do with Copilot. For that the conversation is often recorded or transcribed. Agree that you announce this at the start, to external participants too, and that anyone can ask for it to be turned off. The same goes for note-takers from other providers that join an online meeting as an extra participant.
Who decides on new AI tools
After Copilot more questions follow: an AI tool for quotes, a plug-in, a transcription app on a phone. Record who decides on those, for example the IT lead together with management, and how an employee requests a tool. Keep a list of approved tools and what they may be used for.
If something goes wrong anyway
Someone pastes a customer file into a free tool, or Copilot shows a document that was not meant for that person. Agree that an employee reports it straight away, to whom, and that reporting does not lead to blame. People who fear the consequences do not report, and then you only hear about it when it is too late.
If personal data is involved and it is a data breach, the 72-hour notification term with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) applies. That term runs from the moment your business becomes aware of the breach. So make sure a report reaches the right person internally quickly, and that this person knows what has to happen next.
Checklist before you switch Copilot on
- Links for everyone in the organisation checked and limited.
- Old SharePoint sites and Teams cleaned up or closed.
- HR, salary and management documents in a restricted place.
- Search test done with a few employees from different departments.
- Agreed which data may go into Copilot and which may not go into other AI tools.
- Agreed that output is checked before it goes out.
- Agreement on recordings and AI note-takers, including towards external participants.
- Recorded who decides on new AI tools and where the list of approved tools is kept.
- Reporting route for incidents known, including the 72 hours for breaches involving personal data.
- Agreements put on paper and shared with all employees.
This article is not legal advice. If you have a concrete question about your own situation, for example a possible data breach, consult a lawyer or privacy adviser.