Yes, with less new paperwork than any rival. Microsoft 365 Copilot runs under the Microsoft 365 data protection terms a UK firm already has, does not use prompts, responses or Graph data to train foundation models, and keeps interactions in your tenant under Purview retention. Check two gaps: Microsoft’s residency wording covers the EU Data Boundary, not the UK, and opting in to Anthropic or OpenAI models changes the position. The biggest risk is your own SharePoint permissions.
- Training on your data
- No, prompts and Graph data excluded
- Contract
- Your existing Microsoft 365 DPA
- Watch for
- UK is not in the EU Data Boundary language
Why Copilot starts ahead on compliance
For a firm already on Microsoft 365, Copilot is the only AI assistant that arrives under a contract you have already signed, reviewed and recorded. Microsoft’s documentation states that Copilot is “compliant with our existing privacy, security, and compliance commitments to Microsoft 365 commercial customers, including the General Data Protection Regulation (GDPR)”, and prompts and responses are protected, in Microsoft’s words, by the same contractual terms customers trust for Exchange email and SharePoint files. Your processor record, your DPA reference and your transfer mechanism for Microsoft 365 all extend to Copilot.
That head start is real, and it is also where complacency creeps in. The three places UK firms actually come unstuck with Copilot are not the contract: they are the UK-versus-EU residency language, the new third-party model options, and their own SharePoint permissions. Each gets a section below.
Training: a clean no, with one asterisk
Microsoft’s privacy documentation for Copilot is unambiguous: “Prompts, responses, and data accessed through Microsoft Graph aren’t used to train foundation LLMs, including those used by Microsoft Copilot.” The stored interaction history is encrypted and likewise not used for training, optional feedback is not used to train the foundation models, and personal data from connected experiences is excluded too. That is a stronger blanket statement than the consumer AI tools make, and it covers the Copilot licences with enterprise data protection, which Microsoft applies to Copilot Chat and Microsoft 365 Copilot when users sign in with Entra ID accounts.
The asterisk is sign-in. The protections attach to the Entra ID (work) account. A member of staff using a personal Microsoft account gets a different, consumer arrangement, so the policy point is the same as for every assistant: work happens on work accounts. The second, newer asterisk is third-party models: admins can now choose to let Copilot use Anthropic or OpenAI models for some experiences, additional terms may apply, and the training and boundary position of those models is set by their own notes rather than the headline statement. Read the subprocessor pages before switching them on.
Where the data goes: the EU Data Boundary is not about you
Microsoft’s processing-location story is written for the EU: “EU traffic stays within the EU Data Boundary while worldwide traffic can be sent to the EU and other countries or regions for LLM processing”, and “customers outside the EU may have their queries processed in the US, EU, or other regions.” The UK left the EU, and Microsoft’s Copilot privacy page does not mention the UK, UK GDPR or UK tenants at all. On the page’s own wording, a UK tenant falls in the “outside the EU” sentence, which means Copilot queries may be processed in the US, the EU or elsewhere. That is an inference from Microsoft’s text rather than a statement by Microsoft about the UK, and it is exactly the kind of point to confirm with your licensing partner if a client contract turns on it.
What Microsoft does commit to for everyone is the Product Terms: Copilot was added as a covered workload in the data residency commitments on 1 March 2024, and Advanced Data Residency and Multi-Geo carry data residency commitments for Copilot customers. None of that is a problem under UK GDPR, any more than Exchange Online is: the transfer mechanism in Microsoft’s DPA does the legal work. It only becomes a problem when someone has promised a client that data never leaves the UK, which is a promise Copilot’s documentation does not support. Our data residency guide covers what can honestly be promised, vendor by vendor.
Retention, audit and the controls that answer a SAR
Copilot interactions, the prompt and the response with its citations, are stored in the tenant. Admins view and manage them with Content search and Microsoft Purview, set retention policies for Copilot chat interactions in Purview, and can reach Teams Copilot interactions through the export APIs. Users can delete their own Copilot activity history through the My Account portal. There is no single fixed default retention period to rely on: the honest position is that retention is whatever your Purview policies say, so set them deliberately and match them to your document retention schedule.
This is also the machinery that answers a subject access request that mentions AI: the interaction history is data you hold, Content search finds it, and a retention policy you chose keeps the search manageable. Sensitivity labels and information rights management are honoured, and Copilot’s semantic index respects the user’s identity-based access boundary, which brings us to the control that matters more than any setting.
The biggest Copilot risk is your own permissions
Copilot shows each user what that user can already access through Microsoft Graph, nothing more. In a tenant with twenty years of SharePoint sprawl, that sentence is the risk assessment: the salary spreadsheet shared with “Everyone” in 2019 was always technically visible, and Copilot turns technically visible into one question away. This is not a Microsoft defect, and no Copilot setting fixes it; it is an access-control audit, and it belongs in the DPIA as the main identified risk for most firms.
The practical sequence we run before enabling Copilot broadly: review sharing links and “Everyone except external users” permissions on SharePoint and OneDrive, apply sensitivity labels to the genuinely confidential libraries, pilot Copilot with a group whose permissions are known to be clean, and only then widen it. Microsoft’s admin controls let you remove Copilot access per user and gate features like web search, so a staged rollout is cheap.
What the ICO expects, and what the certifications cover
Microsoft lists GDPR, ISO 27001, ISO 42001 and ISO 27018 among Copilot’s compliance offerings, which answers the supplier-assurance line of a client questionnaire. The controller’s duties remain yours, and the order is the one our other GDPR guides set out: name the tasks, record the processor (already done if Microsoft 365 is in your records: add Copilot to the entry), settle the lawful basis per task, run the DPIA where use is high risk, fix the permissions, update privacy notices, and write the one-page staff policy. For Copilot the policy’s UK-specific lines are about accounts and models: work accounts only, and no third-party model opt-ins without the DPIA being updated.
For a Microsoft-first firm the realistic comparison is not whether Copilot can be compliant, it is whether Copilot, ChatGPT or Claude earns its seat for each team. That is a buying question rather than a legal one, and our comparison guide takes it on directly.
RelatedCopilot, ChatGPT or Claude for a Microsoft 365 firm Microsoft 365 Copilot for a UK small business AI acceptable-use policy template
Common questions
Is Microsoft 365 Copilot GDPR compliant?
Copilot can be used in line with UK GDPR with less new work than rivals: it does not train foundation models on your prompts or Graph data, runs under your existing Microsoft 365 DPA, and is managed through Purview. Compliance itself remains yours: lawful basis, records, a DPIA where needed, and above all permissions hygiene.
Does Copilot train AI models on my company data?
No. Microsoft states that prompts, responses and data accessed through Microsoft Graph are not used to train the foundation models Copilot uses, that stored interactions are encrypted and not used for training, and that feedback is excluded too.
Does Copilot data stay in the UK?
Microsoft does not say that. Its boundary language covers the EU: UK tenants fall under the wording that queries may be processed in the US, EU or other regions, with residency commitments for stored data under the Product Terms, Advanced Data Residency and Multi-Geo. The transfer is lawful under Microsoft’s DPA, but do not promise clients UK-only processing.
Is the UK inside the EU Data Boundary?
The EU Data Boundary is defined for the EU, and Microsoft’s Copilot privacy page does not name the UK. On the page’s own wording a UK tenant is “outside the EU” for LLM processing. If a contract turns on this, confirm the current position with Microsoft or your licensing partner rather than relying on EU-focused marketing.
How long does Copilot keep prompts and responses?
As long as your Microsoft Purview retention policies say. Interactions are stored in the tenant, searchable with Content search, and users can delete their own activity history. Set the policy deliberately; there is no sensible default to inherit.
Do I need a DPIA for Copilot?
Where the use is likely high risk under the ICO’s criteria, yes, and for most firms the honest headline risk is internal: Copilot surfaces whatever SharePoint permissions already allow, so the permissions audit belongs in the DPIA. Everyday drafting with clean permissions is usually not high risk.
What is enterprise data protection in Copilot?
Microsoft’s term for the contractual and security commitments that apply when users sign in with Entra ID work accounts: the same terms that protect Exchange email and SharePoint files, covering Copilot Chat and Microsoft 365 Copilot. Personal Microsoft accounts get consumer terms instead, so keep work on work accounts.
Does using Anthropic or OpenAI models in Copilot change the GDPR position?
It can. Admins choose whether to enable them, additional terms may apply, and Microsoft notes models provided by Anthropic as a subprocessor are currently excluded from the EU Data Boundary. Read the subprocessor terms and update the DPIA before enabling them.
What certifications does Copilot hold?
Microsoft lists broad compliance offerings for Copilot including GDPR commitments, ISO 27001, ISO 42001 (the AI management standard) and ISO 27018, per its privacy documentation read in November 2026.
Is Copilot safer than ChatGPT or Claude for a UK firm?
On paper the three business tiers are close: none trains on your data by default and all offer a DPA. Copilot’s edge is contractual continuity with Microsoft 365; its distinctive risk is that it reads your whole tenant through existing permissions. Which one earns the seat is a buying decision, covered in our comparison guide.
Is Microsoft Copilot Chat GDPR compliant for work?
When staff sign in with Entra ID work accounts, Copilot Chat gets enterprise data protection: the same contractual terms that cover Exchange and SharePoint, and prompts and responses are not used to train foundation models. Signed in with a personal Microsoft account it runs on consumer terms, so the staff policy should say work accounts only.