Is Microsoft Copilot GDPR Compliant? Work Accounts vs Personal Accounts

A finance controller in Vienna asks Copilot in Outlook to summarize a thread about a late payment, with the customer's name, IBAN and a disputed amount of EUR 2,400 in it. On her work account, that request is covered by her company's Microsoft contract. If she pastes the same thread into the Copilot app on her phone, signed in with the personal Microsoft account she uses for Xbox, it isn't.

Microsoft has made this harder to explain by renaming things. Microsoft 365 Copilot is now called Microsoft Copilot, and Microsoft 365 Copilot Chat is now Microsoft Copilot Chat, so "Copilot" names both the consumer app and the work product. The account you're signed in with is what decides the GDPR position.

Is Microsoft Copilot GDPR compliant?

No AI product is compliant on its own; GDPR applies to how your company processes personal data. When staff use Copilot for work, your company is normally the controller. With a work (Entra ID) account, Microsoft says Copilot and Copilot Chat are covered by its Products and Services Data Protection Addendum and Product Terms, with Microsoft acting as processor. With a personal Microsoft account, Microsoft deals with the individual under the Microsoft Services Agreement and its privacy statement.

What does enterprise data protection actually cover?

Microsoft's enterprise data protection page (updated August 2026) lists the commitments for work accounts:

• Prompts and responses get the same contractual protection as email in Exchange and files in SharePoint, under the DPA and Product Terms.
• Prompts, responses and data accessed through Microsoft Graph aren't used to train foundation models.
• Copilot respects your permissions, inherits sensitivity labels, applies your retention policies and supports audit, with controls varying by plan.
• Microsoft lists support for GDPR, the EU Data Boundary, ISO/IEC 27018 and its DPA among its privacy commitments.

There are three exceptions an EU company needs to know about. Web search queries sent to Bing are handled under the Microsoft Services Agreement, with Microsoft as an independent controller, and the EU Data Boundary doesn't apply to them. Anthropic models available in Copilot are, in Microsoft's words, currently excluded from the EU Data Boundary and in-country processing commitments. And since spring 2026 there's flex routing.

What is Copilot flex routing, and should EU admins turn it off?

Flex routing lets Microsoft process Copilot's model inference outside the EU Data Boundary, reportedly in the US, Canada or Australia, during periods of peak demand. Data at rest stays in the EU. Reporting by Office 365 for IT Pros describes it as on by default for EU and EFTA tenants created after 25 March 2026, with existing tenants defaulting on from 17 April 2026; a later Message Center update quoted by readers said it would be off by default. Because the reports conflict, check your own tenant.

The setting is in the Microsoft 365 admin center under Copilot settings, "Flexible inferencing during peak load periods". If your transfer assessment assumes processing stays in the EU, choosing not to allow flex routing keeps it consistent with that assumption. Review the Anthropic model setting at the same time.

Work Copilot vs consumer Copilot: what's different?

On the consumer side, Microsoft's privacy FAQ for Copilot says signed-in users can opt out of model training, conversations are kept for 18 months by default, and some conversations get automated and human review, with no opt-out from human review. In August 2024 Microsoft said it wouldn't train on consumer data from the EEA until further notice; the FAQ now also notes that an updated Copilot app shipped in August 2026 with its own data overview. Treat the consumer app as outside your control.

What does GDPR ask of you when staff use Copilot?

1. A lawful basis (Art. 6) for each use involving personal data, plus an Art. 9 condition for special categories.
2. A processor agreement (Art. 28). The Microsoft DPA covers work-account Copilot. Note that Bing web queries sit outside it.
3. A transfer assessment (Chapter V) that reflects your actual settings: the EU Data Boundary, flex routing, Anthropic models and web search.
4. Data minimization (Art. 5(1)(c)). Copilot sees what the user can see in Microsoft 365, so oversharing in SharePoint becomes a Copilot problem. Fix permissions before rollout.
5. Transparency and records (Art. 13, 14 and 30) covering Copilot's access to mail, files and chats.
6. A DPIA (Art. 35). Copilot reading every mailbox and Teams chat in a company is the kind of processing most regulators would expect to be assessed, and the assessment has to reflect your tenant's actual settings.

How do you set up Copilot for GDPR?

• Make work accounts the only route. Block or discourage the consumer Copilot app for work data, and make sure staff sign in with Entra ID.
• Review the EU-specific settings: flex routing, Anthropic models and web search grounding, and record what you chose in your transfer assessment.
• Clean up permissions and labels first. Copilot inherits sensitivity labels and respects access rights, so a labeled, well-permissioned tenant is the main data protection control.
• Set retention for Copilot interactions and confirm audit logging is on.
• Mask Copilot and every other AI tool under one policy. Most companies use more than one AI tool. Maskflare masks prompts and attachments in ChatGPT, Claude, Gemini, DeepSeek, Perplexity, Mistral Le Chat and Microsoft 365 Copilot in the browser, and API traffic from your own applications to the providers it supports, through the AI gateway.

What can't settings fix?

• Copilot reads what's already in Microsoft 365. No setting changes the fact that an over-shared folder becomes searchable through Copilot.
• Users with two accounts. The work and personal Copilot apps look alike. Training and clear device policy matter as much as tenant settings.
• Conflicting documentation. Microsoft's rename and the flex routing reports show how fast this changes. Re-check settings after major Copilot updates.

What about the EU AI Act?

The EU AI Act sits alongside GDPR. As a company deploying Copilot, your main duties are AI literacy for staff (Article 4, applying since February 2025) and transparency where people interact with AI on your behalf. Microsoft and the model providers behind Copilot carry the general-purpose model obligations in force since August 2025. Personal data in Copilot remains a GDPR matter, and specific high-risk uses need legal review.

This article is general information, not legal advice. Facts are as of October 2026; check Microsoft's current documentation before relying on them.