Is Microsoft 365 Copilot GDPR-compliant?
From a data protection standpoint, Microsoft 365 Copilot is clearly better positioned than the consumer variants of other cloud LLMs: DPA in place, EU Data Boundary available, no model training on customer content. Yet three issues remain: Microsoft is a US corporation (CLOUD Act), Bing Grounding can send data outside the tenant, and for professionals bound by § 203 of the German Criminal Code the combination stays risky.
Realistic to use with an enterprise setup and EU Data Boundary – but not for every use case and not for every industry.
- DPA in the Enterprise Agreement
- EU Data Boundary configurable
- US CLOUD Act still applies
- Bing Grounding sends data outside the tenant
Which Copilot variant do you mean?
„Copilot" is Microsoft's umbrella brand for several products with very different privacy profiles. Confusing them leads straight to a compliance incident.
The classic for businesses: Microsoft 365 E3/E5 plus the Copilot licence. With DPA, tenant binding and EU data processing as an option. For professional use in the DACH region the only seriously auditable variant.
Personal variant for private users. No DPA, no tenant, unsuitable for company use. Anyone typing customer data here regularly breaches the GDPR.
The free web variant. Inputs may be processed in Microsoft cloud services outside the EU. Not intended for professional content.
Tool for building custom AI agents on the Copilot stack. Inherits the privacy properties of the underlying tenant – only as safe as the setup.
Why Microsoft is ahead here from a privacy standpoint
Compared with the consumer tiers of ChatGPT or Claude, Copilot Enterprise offers three hard advantages – and a soft one that only delivers with consistent configuration.
DPA at no extra cost
The Microsoft 365 Enterprise Agreement includes the data processing agreement by default. Unlike ChatGPT Plus or Claude Pro, the „no DPA available" hurdle is gone.
EU Data Boundary
Configurable mode that keeps Microsoft 365 and Copilot data processing primarily in EU data centres. Reduces the third-country risk – but does not fully eliminate it because of the CLOUD Act.
No training on customer content
Microsoft contractually does not train its foundation models on content from your M365 tenant. That is an important difference compared with the consumer plans of other vendors.
Sensitivity Labels & Purview
Microsoft Purview enables classification of documents and emails. Copilot respects these labels and hides protected content accordingly – if Purview is properly set up.
Six GDPR questions that remain open even with Copilot
Even in the Enterprise variant with EU Data Boundary there are residual risks that German supervisory authorities consistently raise.
US CLOUD Act still applies
Microsoft is a US corporation. The CLOUD Act forces US parents to hand over data from their subsidiaries – even when storage is in the EU. The Schrems II ruling remains the underlying problem.
Bing Grounding sends data outside the tenant
When Copilot includes web search results (Bing Grounding), prompt content leaves the protected tenant and is processed in Bing cloud services. On by default, but can be disabled in the admin centre.
A DPIA is mandatory
Before rolling out Copilot, a data protection impact assessment is mandatory. Often skipped in practice – then the justification record vis-à-vis supervisory authorities is missing.
Professional secrecy stays risky
Doctors, lawyers, tax advisors, pharmacists, insurers, banks: even with M365 Copilot Enterprise, third-country transfer in the sense of professional secrecy stays problematic. Criminal liability is not excluded.
Plug-ins and connectors
Copilot extensions (Salesforce, ServiceNow, SAP) forward data to the respective vendors. Each individual extension needs its own legal assessment and DPA.
Information duties towards customers
If customer data is processed in Copilot workflows, data subjects must be transparently informed – about recipients, third-country transfer and legal basis. Most privacy policies do not cover this.
When may I use Copilot – and when not?
A quick self-check: if your configuration and use case fit the left column, Copilot is usually acceptable. If anything in the right column applies, you need a better solution.
Most likely OK
- M365 E3/E5 Enterprise Agreement active
- EU Data Boundary configured, Bing Grounding off
- DPIA performed and documented
- Sensitivity Labels set up via Purview
Not without further measures
- Copilot Pro or Bing consumer variant in use
- Professional secrecy under § 203 StGB involved
- Special categories under Art. 9 GDPR (health etc.)
- Data protection impact assessment pending
What alternatives are there?
Three paths – ranked by protection level. If Copilot doesn't fit or the residual risks are too high, here are your options.
KOSMO on-premise
KOSMO runs on your own hardware. No US corporation, no CLOUD Act, no third-country transfer, full access to internal sources. Also suitable for § 203 StGB professions.
- Data never leaves your network
- No DPA needed (no external processor)
- RAG on your own knowledge sources
M365 Copilot with strict policy
If you keep Copilot: disable Bing Grounding, clear usage policies, employee training, regular spot checks and a documented DPIA.
- Disable Bing Grounding
- Label sensitive content with Purview
- Refresh the DPIA annually
EU vendor with DPA
Specialised European AI vendors hosting in the EU, offering a DPA and transparent model policy. Lower third-country risk than Copilot, but typically more cumbersome to integrate with Microsoft.
- Verify the DPA and EU hosting
- Check the parent company and CLOUD Act exposure
- Opt out of training on your inputs
FAQ – the detailed questions about Copilot
Microsoft 365 Copilot is the Enterprise variant with DPA, tenant binding and EU Data Boundary as an option. Copilot Pro is the consumer variant without a DPA, intended for private users. For professional use with customer data, only M365 Copilot is a serious option – Copilot Pro is practically never GDPR-compatible for companies.
Sources & further reading
This page draws on the following public and official sources:
- Microsoft Learn – Microsoft 365 Copilot: Data, Privacy & Security
- Microsoft – EU Data Boundary for the Microsoft Cloud
- DSK – Orientierungshilfe zu Künstlicher Intelligenz und Datenschutz (Mai 2024, PDF)
- DSK – Technische & organisatorische Maßnahmen für KI-Systeme (Juni 2025, PDF)
- BSI – Generative KI-Modelle: Chancen und Risiken
- EuGH – Urteil C-311/18 „Schrems II" (16. Juli 2020)
- EUR-Lex – Verordnung (EU) 2016/679 (DSGVO) im Volltext
Full control instead of residual risk
KOSMO runs on your own hardware or in sovereign EU data centres. No US corporation, no CLOUD Act, no Bing Grounding – just your data and your knowledge.
This page provides a general overview and is not a substitute for legal advice. For specific cases – particularly involving special category data, professional secrecy or cross-border data transfers – consult your data protection officer or a specialised law firm.
