The checklist at a glance
- Decide who needs a Copilot licence and who can work with Copilot Chat.
- Review permissions in SharePoint, OneDrive and Teams.
- Settle data protection: contract, data location, web search, records.
- Inform the works council during planning and agree how usage data is used.
- Add Copilot to your AI usage policy.
- Train people and keep a record.
- Start with a small pilot group.
- Measure, then expand.
1. Licences: who needs Copilot and who can use Copilot Chat
You don't need to license everyone, and for most firms of this size you shouldn't.
Copilot Chat comes with your subscription. According to Microsoft's Copilot Chat overview, users with an eligible Microsoft 365 subscription can use Copilot Chat without a Copilot licence. It works mainly from the web and from what the user gives it, such as pasted text and uploaded files. Inside Outlook it can also draw on the user's mailbox, calendar, meetings and chats. Users signed in with their work account get enterprise data protection, which step 3 covers.
The licence adds your company's data. With a Copilot licence, the same page says, Copilot reasons across the emails, meetings, calendars, chats, documents, sites and files a user has permission to access. Licensed users also get the full Copilot experience in Word, Excel, PowerPoint and OneNote, plus priority access to the models built for harder tasks.
Which base plan you need. Microsoft Copilot Business is an add-on for organisations with up to 300 users. Microsoft's licence options page lists Microsoft 365 Business Basic, Business Standard, Business Premium, Microsoft 365 Apps for business and Teams Essentials as eligible plans. Copilot Business comes with an annual commitment and supports up to 300 licensed users per tenant. Microsoft 365 E3 and E5 are also eligible prerequisites for a Copilot licence. Microsoft publishes the price on its pricing page, which the licence article links to. I don't quote one here.
What that means for the decision. The licence pays off for people whose work lives in email, meetings and documents, such as project leads, executive assistants and inside sales. Someone who mostly rewrites text or researches on the web gets far with Copilot Chat. On Copilot Business, the annual commitment means even pilot licences are a twelve-month purchase, so decide up front who the licences go to after the pilot. Licences can be assigned and unassigned per user in the Microsoft 365 admin center.
Once you start that list, you're planning. If you have staff in Germany with a works council, now is when you inform it. Step 4 explains why.
2. Fix permissions before Copilot starts looking
This is the step most rollouts skip and the one that saves the most trouble. Microsoft's page on data, privacy and security for Copilot says Copilot surfaces only data each user can at least view. Microsoft also says it's important to use the permission models in services like SharePoint so that the right people have access to the right content, including permissions given to outside users through shared channels in Teams.
What you'll typically find. Microsoft's guide to configuring a secure and governed foundation lists the findings to look for: sites with oversized audiences, sharing with company-wide groups such as "Everyone except external users", or EEEU for short, broken permission inheritance on libraries and folders, inappropriate sharing links, and sites that are inactive or have no owner. Old company-wide sharing links from OneDrive belong on that list as well.
Start with what must never be shared widely. HR, payroll, the board, finance, the works council's own files, anything with health data. For each of those sites, ask the owner who should have access and compare it with what's actually set. A site without an owner gets one first.
Use the tools that come with the licence. Microsoft says SharePoint Advanced Management is included with Copilot licences. It runs a content management assessment that reports exactly the findings above, and its site access reviews let site owners clean up access themselves. At tenant level, Microsoft recommends disabling or restricting company-wide sharing groups and Anyone links so new sites don't start out wide open.
A temporary block while you review. Restricted Content Discovery takes selected SharePoint sites out of organisation-wide search and Copilot while you work through their permissions. It doesn't change anyone's access. People who can open a file today can still open it directly. It doesn't work on OneDrive, and it needs a Copilot licence. Microsoft describes it as a temporary control and warns against overusing it. You switch it on per site in the SharePoint admin center under Sites > Active sites, on the site's Settings tab, or with PowerShell. On very large sites the change can take more than a week to reach search and Copilot.
The groundwork for any AI assistant that reads company files is covered in more detail in the piece on an AI assistant for company documents.
3. Data protection: contract, data location, web search
Copilot's contract position is simpler than for most AI tools, because Microsoft 365 already comes with one. That covers Microsoft's side and nothing more.
The contract. Article 28(3) of the GDPR requires a contract whenever a processor handles personal data for you. According to Microsoft's page on enterprise data protection, organisational use of Copilot and Copilot Chat is covered by the Microsoft Products and Services Data Protection Addendum and the Product Terms, with Microsoft acting as processor. File the current version of the DPA with your records.
What happens to prompts. Microsoft states that prompts, responses and data accessed through Microsoft Graph aren't used to train foundation models. They are stored, though, as each user's Copilot activity history, under the same contractual commitments as the rest of your Microsoft 365 content. Admins can set retention policies for that history in Microsoft Purview, and users can delete their own history at myaccount.microsoft.com.
The EU Data Boundary. For EU customers, Microsoft's page on data, privacy and security for Copilot says Copilot is an EU Data Boundary service and EU traffic stays within the boundary. The EU Data Boundary covers the EU and EFTA countries. For Microsoft 365, tenants with a sign-up location in an EU or EFTA country are in scope. That page also documents the limited cases in which data still leaves the boundary. The boundary is an EU commitment. For customers outside the EU, such as a UK or US firm, Microsoft says queries may be processed in the US, the EU or other regions.
Two exceptions to know about. The first is web search. When Copilot is allowed to search the web, it turns the prompt into a short query and sends it to Bing with user and tenant identifiers removed. For those queries Microsoft acts as an independent controller under the Microsoft Services Agreement, and the EU Data Boundary doesn't apply. Admins can manage web search through a Copilot policy. The second is Anthropic's models, which Microsoft offers as a subprocessor inside Copilot. Microsoft says they are currently excluded from the EU Data Boundary, and admins decide whether the organisation uses them. Put both in front of your data protection officer before launch.
What stays with you. An entry in your record of processing, telling staff what data their use creates, and checking whether you need a data protection impact assessment. Article 35(1) GDPR requires one where processing, in particular with new technologies, is likely to result in a high risk to people's rights and freedoms. Write down the preliminary check even if the answer is no. These duties are laid out in the ChatGPT GDPR checklist, and the same list applies to Copilot.
4. Works council: inform early, agree on usage data
If none of your staff work under German works council rules, skim this step and read the last paragraph. If they do, the works council sets your timeline.
Inform while you're still planning. Under section 90(1) BetrVG, Germany's Works Constitution Act, the employer must inform the works council in good time, with the necessary documents, about planned technical installations, work processes and workflows, including the use of artificial intelligence. Section 90(2) requires consultation early enough that the council's suggestions and concerns can still shape the plan. That means before the order, not with the launch email.
Co-determination if the tool can monitor people. Section 87(1) no. 6 BetrVG gives the works council co-determination over the introduction and use of technical devices designed to monitor employees' behaviour or performance. Copilot produces that kind of data. The Copilot usage report in the Microsoft 365 admin center lists, per user, the number of prompts, active days and the last activity date in each app. User names are hidden by default but can be shown. In Microsoft Purview, authorised admins can review prompts and responses. And if you want Copilot to work with meetings after they end, Microsoft's requirements page says you need to set up transcription or recording in Teams. How German courts read "designed to" and what follows for AI tools is in the piece on AI and works councils. Whether your rollout falls under no. 6 is a question for an employment lawyer. If the two sides can't agree, section 87(2) sends the matter to the conciliation board.
What the agreement should settle. Who may see the usage report, and whether names stay hidden. That prompts are never used to assess performance. When anyone may look at content in Purview, for example only for a documented reason and with the council present. How long activity history is kept. Whether meetings may be transcribed and who decides that for each meeting. And how new Copilot features that arrive with an ordinary update are handled.
Without a works council. There's no co-determination. Telling staff what's logged and who sees it still belongs in step 3, and saying it plainly heads off rumours about the boss reading everyone's prompts.
5. Add Copilot to your AI usage policy
If you already have an AI policy, extend it. If you don't, start from the AI usage policy template with its ten clauses and add Copilot to the approved tools. Copilot needs a few points of its own.
Work account only. People can sign in to the Copilot app with a personal Microsoft account too, according to Microsoft's page on managing Copilot Chat. Chats, files and protections then stay separate, and enterprise data protection applies only to the work account. Microsoft recommends telling staff to sign in with their work account, which they can recognise by the "Work" label and the green data protection shield. Whether personal accounts can sign in at all is something you control with tenant restrictions in Microsoft Entra.
A person checks every answer. Microsoft says outright that generative AI responses aren't guaranteed to be 100% factual and that users should review them before sending them on. Make that a rule. Whoever passes on a Copilot answer owns it.
Agents need approval. For agents in Copilot, Microsoft points to each agent's own privacy statement and terms of use. Decide who approves agents, and allow only approved ones in the admin center.
No side tools for company data. Once people have Copilot under a contract, they don't need a personal ChatGPT account for work. Say so explicitly. How to find out what else is already in use, and why a ban on its own fails, is in the piece on shadow AI.
6. AI literacy: train people and write it down
Article 4 of the EU AI Act has applied since 2 February 2025, and it covers companies that only use AI. The Digital Omnibus, Regulation (EU) 2026/1744, amended it in summer 2026. Per the European Commission's AI literacy questions and answers, deployers must now take measures to support the development of AI literacy, taking into account their staff's technical knowledge, experience, education and training. No specific level is required. The Commission says no certificate is needed and organisations can keep an internal record of trainings, and it gives 2 August 2026 as the start of supervision and enforcement. The piece on the AI literacy obligation under Article 4 covers the details.
For Copilot, the training needs four things. Copilot sees what the user can see, so anyone who finds something in an answer they shouldn't have reports it instead of forwarding it. Copilot sometimes makes things up, and the Commission names hallucination as a risk users should be told about. Show it live with a question from your own work, and practise clicking through to the cited sources. Staff also need to hear what's logged and who sees it, as set out in the works agreement or staff notice. Last, give them the name of the person who answers questions.
Record who got which session and when. A spreadsheet is enough, and there's a template in the piece on the AI literacy training record.
7. Start with a small pilot group
A pilot answers one question: for which tasks does Copilot save your people time, and for which doesn't it? Eight to twelve people is enough, picked for their tasks and not for their enthusiasm.
Tasks first, then people. Write down three to five recurring tasks where Copilot might help, such as meeting minutes, replies to customer enquiries or a weekly report. Then pick the people who do those tasks. Include one sceptic, because otherwise their objections only surface at the big rollout.
Measure the baseline before the licences arrive. For two weeks, the group notes how often each task comes up and how long it takes. Without that number you finish the pilot with impressions. The piece on measuring before you build shows how to do it without much effort.
Time-box it and get it agreed. Fix a duration, such as four weeks with licences. If Copilot falls under section 87(1) no. 6 BetrVG in your case, the pilot needs the works council's consent too, because the text covers introduction and use and makes no exception for trial runs. A time-limited pilot agreement is often quicker to reach than the final one.
Write the decision rule down first. For example, a role gets licences if Copilot saves measurable time on its tasks and the reviews catch the errors. A rule written after the pilot tends to bend towards the result.
8. Measure, then expand
The usage report in the admin center counts enabled users, active users, the share of enabled users who are active and the number of prompts submitted, over 7, 28, 90 or 180 days. Microsoft counts a user as active after an intentional action such as submitting a prompt. Opening the Copilot pane doesn't count. Data for a given day usually appears within 48 hours.
The report tells you whether Copilot is being used. It can't tell you whether it's worth the money. For that, measure the same tasks as in the baseline, with the same notes, and also count how often an answer needed correcting in review. Totals per task are enough. You don't need names for this, which your works council will be glad to see.
A worked example: a 60-person firm's pilot
The firm is invented, but the arithmetic holds. An engineering consultancy with 60 staff buys ten Copilot licences: four project leads, four customer service staff, one executive assistant and one controller. It measures three tasks, two weeks without Copilot and four weeks with it. The table shows weekly averages for the whole group.
| Task | Per week | Minutes before | Minutes with Copilot | Weekly effect |
|---|
| Meeting minutes from Teams | 12 | 30 | 15 | 180 minutes saved |
| Customer enquiry that needs a lookup | 40 | 8 | 9 | 40 minutes added |
| Report to management | 2 | 90 | 70 | 40 minutes saved |
The net result is 180 − 40 + 40 = 180 minutes a week, or three hours. Spread over ten licences, that's 18 minutes per person, and the average hides what actually happened. The four project leads write all the minutes, three each per week, so each of them saves 45 minutes a week. In customer service every reply took a minute longer, because staff double-checked every delivery date and price Copilot gave them, which was the right call. Across the 48 sets of minutes in the four weeks, the project leads found six errors, mostly a statement attributed to the wrong person. That's 12.5%, and all six were caught in review.
The decision follows the rule written before the pilot. The four customer service licences are reassigned to four of the six other project leads, and the firm buys two more for the last two, making twelve. Customer service stays on Copilot Chat, which needs no licence. After three months the firm measures the minutes again.
Common rollout mistakes
Licensing everyone on day one. You lose any baseline, and with an annual commitment you pay twelve months for accounts nobody opens after week three.
Checking permissions after something leaks. Once a salary table has turned up in a Copilot answer, you can't take it back. The review in step 2 costs less than the conversation afterwards.
Telling the works council with the launch email. Section 90 BetrVG puts the timing in the planning stage. Informing them at launch usually costs the very weeks you hoped to save.
Reading the usage report as a success measure. Lots of prompts doesn't mean lots of time saved. In the example above, customer service used Copilot most often and still got slower.
Ignoring web search and Anthropic models. Both sit outside the EU Data Boundary. That can be acceptable, but it should be a decision rather than an accident.
caadoo handles the technical side of a rollout like this as part of a subscription: the sharing review, the settings in the admin center and Purview, the training and the documentation. The legal sign-off stays with your data protection officer and your lawyer. If your rollout is stuck on one of these steps, tell me which one.
Frequently asked questions
What do you need before rolling out Microsoft 365 Copilot?
On the technical side, an eligible Microsoft 365 plan, user accounts in Microsoft Entra ID and, for anything that uses email, a mailbox in Exchange Online. Each person who should use Copilot with company data needs a Copilot licence on top. On the organisational side, you need cleaned-up permissions, an entry in your record of processing, a usage policy, training and, where there is one, the works council on board.
Is Microsoft 365 Copilot GDPR compliant?
A product can't be GDPR compliant on its own, because the GDPR judges what your company does with it. Microsoft provides the processor contract through its Data Protection Addendum, doesn't train foundation models on your prompts and, for EU customers, processes the data within the EU Data Boundary. Web search and Anthropic's models are the exceptions. The record of processing, informing staff and checking whether you need a DPIA stay with you.
Does a German works council have to approve Copilot?
It has to be informed in any case, under section 90 BetrVG, and during planning. Its consent is required under section 87(1) no. 6 BetrVG if Copilot counts as a technical device for monitoring behaviour or performance. Copilot produces per-person usage data, which makes a strong case that it does. Settle the question with an employment lawyer before you buy licences.
Does Copilot give employees access to every file in the company?
No. Copilot shows each person only content they already have at least view permission for. The risk is permissions that reach further than anyone realised, such as sites shared with the whole company or old OneDrive links. That's why you review permissions before launch and, where needed, take sensitive SharePoint sites out of search for a while.
Is Copilot Chat enough without a licence?
For web research, rewriting text and working with uploaded files, often yes. Inside Outlook, Copilot Chat can also draw on the mailbox and calendar. If people need answers that pull together their emails, meetings, chats and documents, they need the licence.