Is Microsoft 365 Copilot GDPR-compliant? 7 points to check before deployment

Is Microsoft 365 Copilot GDPR-compliant? 7 points to check before deployment

In brief

  • Microsoft 365 Copilot can be deployed in compliance with the GDPR: Microsoft acts as a processor, is contractually committed not to train its foundation models on your tenant data and offers processing within the European data boundary. The real risk is internal: Copilot inherits existing permissions and instantly reveals all over-shared documents. Before activation, you must audit access rights, frame the processing (DPIA, employee information, consultation with the works council) and train users.

Understanding what Copilot actually does with your data

Copilot combines three elements: the large language models hosted by Microsoft, your tenant content accessible via Microsoft Graph (emails, SharePoint and OneDrive files, Teams conversations, calendars) and the user's prompt. Three properties to remember:

  1. Copilot only sees what the user can see: it respects Graph permissions. This is both the guarantee and the trap (next point).
  2. Tenant data is not used to train foundation models: contractual commitment by Microsoft, which processes as a processor under its Data Protection Addendum (DPA).
  3. Interactions are retained: prompts and responses are stored in the tenant (history, compliance, eDiscovery) according to your retention policies; it is up to you to configure them.

Risk no. 1: permission inheritance and oversharing

In most organisations, years of 'share with everyone', 'entire organisation' links and poorly closed SharePoint sites have created invisible oversharing: documents are accessible, but nobody finds them. Copilot changes the game: it finds them. The salary grid left on an open site, the misplaced dismissal file, the social plan in preparation become accessible with a single natural language question to anyone who unknowingly had read rights.

The risk treatment is well-known and must precede activation:

  1. Audit of permissions and sharing links (SharePoint Advanced Management reports, inventory tools).
  2. Temporary restriction of the search scope (Restricted SharePoint Search) during the clean-up period.
  3. Microsoft Purview sensitivity labels on sensitive content, with exclusion of labelled content from Copilot results if necessary.
  4. DLP rules and review of default 'entire organisation' links.
  5. Phased deployment, starting with pilot teams outside sensitive data.

GDPR obligations of the deployment

  • DPIA: an AI assistant plugged into all documents and communications of thousands of employees ticks several high-risk criteria (large-scale data, innovative technology, data of vulnerable persons in certain contexts). The impact assessment is in practice unavoidable for a general deployment, and it is the document that records configuration choices.
  • Information to employees (Articles 12 and 13): update of the HR privacy policy and IT charter: what data Copilot uses, what happens to prompts, retention periods, rights.
  • Consultation of the works council: in France, the introduction of new technology of this scale falls under the information-consultation requirement (Article L.2312-8 of the French Labour Code).
  • Retention periods: configure retention of Copilot interactions like any other processing, not by default.
  • Framework for monitoring: Copilot logs must not become a tool for individual employee monitoring outside a framework; purpose and proportionality apply.

And the AI Act?

Your company is a deployer: obligation for AI literacy for users (Article 4, see our guide to AI training) and transparency if generated content goes out to the public. Particular vigilance on HR uses that spontaneously emerge (interview summaries, evaluation preparation): they foreshadow the 'high-risk' regime applicable to HR systems from the December 2027 deadline and must be framed by the charter now.

The deployment checklist in 10 points

  1. Audit of permissions and clean-up of oversharing before activation.
  2. Purview labelling of sensitive data and exclusion rules.
  3. Documented DPIA, with decided and residual measures.
  4. Microsoft DPA and EU data boundary verified in the contract.
  5. Retention of Copilot interactions defined and applied.
  6. Information to employees updated, works council consulted.
  7. AI charter completed: authorised uses, prohibited data, human review.
  8. User training tracked (Article 4 AI Act), enhanced module for HR and legal.
  9. Phased deployment with incident review at 30 days.
  10. Ongoing governance: quarterly review of permissions, logs and new uses.

Take action

Manage your compliance with Data Comply One: all-in-one software and outsourced DPO/CISO experts.

Discover the AI Act software →Test my AI compliance →

Sources

  • Regulation (EU) 2016/679 (GDPR), Articles 5, 12, 13, 28, 32 and 35, EUR-Lex.
  • Regulation (EU) 2024/1689 (AI Act), Articles 4, 26 and 50, EUR-Lex.
  • Microsoft Learn, 'Data, privacy and security for Microsoft 365 Copilot'; Microsoft, Data Protection Addendum (DPA) and EU Data Boundary.
  • French Labour Code, Article L.2312-8 (information-consultation of the works council), Légifrance.

Frequently asked questions

Does Microsoft use our data to train its models?

No for tenant data in the context of Microsoft 365 Copilot: the contractual commitment not to train appears in the documentation and the DPA. This does not exempt you from checking the options of related products and preview features.

Is Copilot different from ChatGPT for compliance?

Yes on one key point: Copilot operates within your tenant, under your enterprise contract and your permissions, whereas consumer ChatGPT operates outside your perimeter. The dominant risk changes in nature: external leak for one, internal overexposure for the other (see our article ChatGPT in the enterprise).

Is a DPIA required even for a 50-user pilot?

A limited pilot, excluding sensitive data, can precede the final DPIA, but the analysis must be initiated from the decision in principle: it is what determines the configuration of the general deployment.

Can certain content be excluded from Copilot?

Yes: exclusion of sites and libraries from the search scope, sensitivity labels with extraction restrictions, and control of licences assigned user by user.

Are employee prompts accessible to the employer?

They are logged in the tenant and accessible via administration and eDiscovery tools, within the limits of employment law and the GDPR: legitimate purpose, proportionality, prior information. Routine access to individual prompts would be disproportionate.