Back to the blog

Is Microsoft 365 Copilot GDPR compliant? What the regulators have said

· By Bee Flow · 6 min read

Nobody can declare Copilot GDPR compliant for your firm. What the Dutch privacy regulator and SURF published in 2026, with dates and sources, and what a firm still has to settle itself.

A clipboard with an unticked checklist and a magnifying glass on a desk, next to a traffic light showing amber

Nobody can declare Microsoft 365 Copilot GDPR compliant for your firm. Whether its use is lawful depends on what you do with it: which data goes in, for what purpose, under which agreement and with which settings. What does exist are two Dutch publications from 2026 that show where the open points are. This post sums up both, with dates and sources, and then lists what a firm of 10 to 75 people has to settle itself.

Status of the facts: 21 July 2026. Both organisations update their publications, so open the sources before you rely on a detail.

The short answer

The Dutch Data Protection Authority (Autoriteit Persoonsgegevens, AP) has not banned Copilot and has not approved it. On 13 July 2026 it published a checklist for organisations that want to use generative AI. In the same month it advised one municipality that its planned use of Microsoft 365 Copilot would breach the GDPR unless extra measures were taken. SURF, the IT cooperative of Dutch education and research, finished its assessment in May 2026 and left two risks at orange, which is its word for medium. Microsoft's position is that Copilot can be used in line with the GDPR.

So the honest answer to "is Copilot GDPR compliant?" is: it can be used lawfully, and the work to get there is yours.

What the AP published on 13 July 2026

The AP published two documents on generative AI and the GDPR. The guidance is written for organisations that develop generative AI models or put them into use. The checklist is the practical one. It helps privacy officers, project leads and other responsible people work out step by step whether the organisation can, wants to and may use generative AI.

Two things in it matter for a firm:

  • Start without personal data. The first question is whether the use you have in mind is possible without processing personal data at all. If it is, most of the remaining questions fall away.
  • If personal data is needed, decide that at the start. The checklist then walks through which GDPR obligations apply and which technical and organisational measures you need, before the tool is connected to your files.

The same month, the AP made public its advice to the municipality of Haarlemmermeer, which had asked for a prior consultation on Microsoft 365 Copilot. Binnenlands Bestuur summarised the advice on 20 July 2026. The AP concluded that the processing as the municipality described it would breach the GDPR, and that the municipality may use Copilot once the right measures are in place. The points it named are recognisable for any office:

  • A purpose such as "supporting the employee" is too vague. State what Copilot is used for.
  • Copilot can reach everything the user can reach. Access rights that were set loosely years ago decide what it reads.
  • Documents that AI must not process have to be labelled or kept out of reach.
  • Staff need the knowledge and the time to check an answer, and a person has to keep a real say in decisions about people.
  • A pilot has to meet the GDPR too.

The advice was written for one municipality and one plan. It does not apply automatically to every organisation, but the questions in it do.

What SURF's orange rating means, and for whom

SURF had Privacy Company carry out a data protection impact assessment (DPIA) of Microsoft 365 Copilot for education and research institutions. The first version, from December 2024, found four high risks. After two rounds of changes by Microsoft, SURF published the second update on 27 May 2026. Two risks stay at orange:

  • A filter with undisclosed criteria. Copilot applies a "Workplace Harms" filter to prompts and answers, meant to stop it from judging employees. Microsoft does not disclose the standards and thresholds it uses.
  • Diagnostic data kept for up to 18 months. The data is pseudonymised, and SURF finds the explanation for the retention period insufficient.

Microsoft gave its final answer on these two points on 31 March 2026, so the assessment is closed and no further round is planned. SURF advises institutions to stay cautious, to pick suitable uses and assess the risks per use, and to adopt a policy for responsible AI use if they accept the two remaining risks. SURF also added one low risk: since March 2026 new customers have to check a setting to keep Copilot data traffic inside the EU.

Microsoft reads the same report differently. In its own summary it stresses that the four high risks have been mitigated or reduced and that deployment remains possible.

For whom does this count? The DPIA was made for universities, colleges and research institutes, under their contract terms. An accounting firm is not bound by it. It is still the most thorough public examination of the product, and a privacy officer or a client's auditor will know it.

What that leaves for a firm of 10 to 75 people

You are the controller for your clients' data. Four things are yours to settle, whichever AI tool you choose:

  1. The agreement. Check that the data processing terms cover Copilot, which subprocessors are involved, and where data is processed. Our post on a data processing agreement for AI chat tools lists what to look for.
  2. A DPIA. If staff will use it with client files, payroll data or personnel matters, write one. It can be short. A DPIA for AI chat in a small company shows the size that fits.
  3. Which data may go in. Write down what staff may and may not put into a prompt, and for which tasks. A one-page AI policy is enough to start.
  4. Access rights. Before Copilot is switched on, check who can open which folders, mailboxes and sites. Copilot does not widen access, and it makes loose access visible quickly.

Where Copilot is the right tool

Copilot lives inside Word, Excel, Outlook and Teams, and that is where it is strongest: a first draft in Word, a formula in Excel, a summary of a Teams meeting you attended. If the firm works in Microsoft 365 and the four points above are settled, there is no reason to keep staff away from it for that kind of work.

Another route for work with client data

For work with client data, some firms want a separate place where the rules are set by the firm. That is what we build. Bee Flow is an AI workspace that runs on your own server or on Bee Flow Cloud in the EU. You choose the model, including EU-hosted models or one on your own hardware. With the personal-data filter installed, names, citizen service numbers and IBANs are detected before a prompt leaves, and on the Pro licence they are replaced before the model sees them and put back in the answer. Detection is machine learning and can miss, so the policy and the access rights stay necessary here too. The two can run side by side: Copilot inside the Office apps, a workspace of the firm's own for client files.

Read more

#privacy #gdpr #copilot