Microsoft 365 Copilot in law firms: what to settle now that the legal plugin is on by default

On 15 October 2026 Microsoft made more than twenty legal skills generally available in Microsoft 365 Copilot (1). For most law firms the sentence that matters is in the administrator notice that came with them: in Word desktop, "the legal plugin is enabled by default" for users with a Microsoft 365 Copilot commercial licence, no administrator setup is required, and the rollout is expected to be complete by mid-December 2026 (2). A lawyer with a Copilot licence who opens a share purchase agreement in Word next month will find that Copilot can review it against a playbook and propose tracked changes, whether or not anyone at the firm decided that it should.

Microsoft is the fourth large AI company in five months to launch a product built for lawyers, after Anthropic's Claude for Legal in May, Google's Gemini Enterprise for Legal in August and OpenAI's Astra for Law in September (3). The other three have to persuade a firm to adopt something new. Microsoft's arrives in a program lawyers already use all day, and part of it runs on another company's models: Copilot Cowork, the workspace where Microsoft's second legal plugin operates, uses Anthropic models (4).

No binding professional rule in the Netherlands, Germany or France forbids a lawyer to use these tools. But the rules on secrecy, outsourcing and conflicts assume that the lawyer chose the provider and knows what happens to client information. A default setting reverses that order: the tool arrives first, and the firm has to make its choices afterwards, preferably before the rollout is complete.

What Microsoft switched on

Microsoft describes the release as "more than 20 purpose-built legal skills", packaged in two plugins, one for Word and one for Cowork. They build on the Legal Agent, which Microsoft first offered as a preview to users of its Frontier programme in April, and replace it (1) (2). In Word, Copilot reviews an agreement against a playbook and applies its suggestions as native tracked changes, and drafts new agreements from approved precedents stored in SharePoint (1); according to the administrator notice, the skills also compare a contract with precedents, templates and policies and explain tracked changes (2). In Cowork, Microsoft's agent workspace, the legal plugin takes on longer tasks "across agreements, emails, meetings and files": tracking obligations and deadlines across a contract portfolio, comparing key terms across agreements and building case chronologies. Microsoft groups the skills under five headings, one of which is "Turn research into guidance" (1).

The administrator notice (Message Center item MC1509799) adds the details a managing partner needs (2):

Alongside its own skills, Microsoft announced partner plugins that are "beginning to roll out" through its plugin registry: research services (Bloomberg Law, Trellis, Descrybe, Legal Data Hunter, Courtroom5, Lawstronaut), document and matter management (iManage, NetDocuments, Box, Litera, HighQ and others), signature tools such as Docusign, the legal AI products Harvey, Legora and DeepJudge, and the e-discovery platforms Everlaw and Relativity (1). Each comes from a different company, with its own terms.

The evidence of quality is Microsoft's own. Since April, it says, more than 1,800 users generated nearly 100,000 edits and kept roughly seven in ten suggestions, and internal evaluations scored the edits above 90 per cent for fluency, above 95 per cent for conciseness and above 85 per cent for relevance (1). Microsoft released no results on any independent legal benchmark (3). None of the three measures, as Microsoft names them, tests whether a proposed change is legally right.

Four suites, one pattern

Anthropic's Claude for Legal, announced on 12 May 2026, consists of twelve practice-area plugins and more than twenty connectors to legal software, working inside Word, Outlook, Excel and PowerPoint and in Claude Cowork; the plugins are published as open source, and Anthropic states in the repository that every output "is a draft for attorney review" (5) (6). Google announced Gemini Enterprise for Legal on 25 August 2026 as a preview, naming Cleary Gottlieb, Freshfields, Weil and Williams & Connolly among the firms it is working with (7). OpenAI's Astra for Law, announced on 17 September 2026, combines its GPT-6 Astra model with a legal search index and is offered at first to selected firms (8). Bob Ambrogi's summary at LawSites fits all four launches: legal skills or agents, connectors into the specialist products lawyers already use, and the promise that lawyers can get more done without leaving the platform (3).

For a European firm, then, the useful question is not which model writes the better first draft. It is what each suite brings with it: whose servers the documents pass through, under which contract, and which legal sources the suite can actually consult.

Where client information goes

A lawyer who asks the Word legal plugin to review a draft does not see the infrastructure behind the answer. Depending on how the firm's tenant is configured, client material can take four routes, each on different terms.

Route one: Microsoft's own processing

For Copilot itself, Microsoft acts as the firm's processor. It says that Copilot "processes prompts and responses within the Microsoft 365 service boundary", works only with content each user can access, honours sensitivity labels, and "does not use prompts, responses, or documents to train the underlying foundation models" (1). For EU customers Microsoft describes Copilot as an EU Data Boundary service (9). Under that commitment, which applies to Microsoft 365 customers whose sign-up location is in the EU or EFTA, customer data and pseudonymised personal data are stored and processed in datacentres in the EU and EFTA, subject to limited exceptions that Microsoft documents (10). This is the route most firms assume they are on.

Route two: Anthropic models, outside the EU Data Boundary

Anthropic is now a Microsoft subprocessor, working under Microsoft's Product Terms and Data Protection Addendum, and Claude models are offered across Microsoft's Copilot products, including Researcher, Copilot Studio and Copilot in the Microsoft 365 apps (11). Microsoft's documentation is explicit about what that means for location: Claude models in these products "are currently excluded from the EU Data Boundary, and when applicable, in-country processing commitments". For customers in the EU Data Boundary and in the United Kingdom, the general setting that enables Anthropic as a subprocessor is off by default (11).

That default is less reassuring than it looks, for two reasons. First, a separate setting lets Copilot in Word, Excel and PowerPoint use Anthropic models by default in European and UK tenants. It "is on by default for tenants in the EU, EFTA, and UK that were created after March 25, 2026", and when Anthropic models are used there, "data processing for these models occurs outside of the Microsoft EU Data Boundary". For older tenants Microsoft refers administrators to the Message Center for their tenant's default, and it encourages every administrator to check the setting (12). Microsoft describes this setting as separate from the general subprocessor setting, yet the same page states that Anthropic models are unavailable unless Anthropic is enabled as a subprocessor (12). The page does not reconcile the two statements, so both settings need checking. Second, Copilot Cowork "uses Anthropic models" (4), and Microsoft warns that some features are only available when Claude models are enabled (11). Our reading of the documentation: a European firm that wants the Cowork legal plugin has to decide first whether to allow Anthropic, as Microsoft's subprocessor, to process firm data outside the EU Data Boundary.

A third category is different in kind. Microsoft also offers certain advanced Anthropic models as "Anthropic models with Data Retention". For these, data is stored by Anthropic and is "not subject to your Microsoft Customer Agreement including commitments in the Product Terms and DPA"; Anthropic acts under its own commercial terms and data protection addendum and keeps most inputs and outputs for up to 30 days. These models are off by default everywhere and require a separate opt-in by an administrator (11). In our view client material does not belong there.

Route three: web search, with Microsoft as controller

When web search is enabled, Copilot turns part of the user's request into a short search query and sends it to Bing. The query is not the whole prompt, and identifiers such as user name and tenant are removed, but it may be "informed by data within a Microsoft 365 document" when the user is working in an open document or refers to one, and the user's IP address is sent with it (13). For these queries Microsoft acts as a controller, not as the firm's processor. Its documentation states that the Data Protection Addendum "doesn't apply to the use of generated web search queries", and that the EU Data Boundary does not apply to them either. The Product Terms add commitments that the queries are not used to improve Bing, for advertising or to train foundation models, and are treated as confidential information (13).

Microsoft's own example shows how much a few words can carry: asked about the user's manager, Copilot sends the manager's name to Bing (13). A lawyer who asks Copilot, inside a draft settlement agreement, what is publicly known about the counterparty may send that counterparty's name, with a few words drawn from the draft, to a search engine on terms to which the firm's data protection addendum does not apply. Web search, too, is a default: unless an administrator has configured the "Allow web search in Copilot" policy in the Cloud Policy service, or has disabled optional connected experiences across Office, it is available to users. The same page says that its rules also apply to Researcher, Analyst and Cowork, that Cowork has no web search switch for users, and that the policy option disabling web search in Copilot's work mode also disables it in Researcher and Cowork (13). Whether Cowork searches the web is therefore an administrator's decision.

Route four: partner plugins

A partner plugin connects Copilot to another company's service: a research database, a document management system, an e-discovery platform (1). For agents that extend Copilot, Microsoft advises customers to check the privacy statement and terms of use of each agent to see how it will handle the organisation's data; administrators can see those terms and the data access an agent requires, and choose which agents are allowed, under "Integrated apps" in the Microsoft 365 admin center (9). Microsoft's announcement does not say that partner plugins fall under its own processor terms. Until a vendor's documentation says otherwise, the prudent assumption in our view is that whatever passes through a plugin is governed by the firm's terms with that vendor, not by its Microsoft agreement. A firm that already uses iManage or NetDocuments will have such a contract; some of the newer research services on the list may be vendors it has never assessed.

What the GDPR adds

The firm is the controller for client personal data and Microsoft its processor. Under Article 28 GDPR a processor may engage sub-processors only with the controller's prior specific or general written authorisation, and where the authorisation is general, it must inform the controller of any intended addition or replacement so that the controller can object (14). In our reading, Microsoft's onboarding of Anthropic is such a change. Microsoft lets customers subscribe to notifications of changes to its subprocessor list (4); a firm that does not follow them has a right to object that it cannot use in practice.

Processing outside the EU Data Boundary may take place outside the EU and EFTA, and where it does, the transfer rules of Chapter V apply. Microsoft's pages do not say where Anthropic processes the data. If it is in the United States, the transfer can rest on the EU-US Data Privacy Framework where the recipient is certified, or on standard contractual clauses (14) (15). The General Court dismissed an action for annulment of the Framework in September 2025 in Latombe v Commission; the appeal against that judgment was still pending before the Court of Justice on 8 November 2026 (16) (17). A firm relying on the Framework should know that its foundation is still in litigation.

Finally, Article 35 requires a data protection impact assessment where processing is likely to result in a high risk (14). In our view a tool that can draw on every matter a lawyer can open, and can send parts of it to a subprocessor or a search engine, meets that threshold in most firms. The Dutch government's experience shows what such an assessment can turn up, and what it leaves out. In December 2024 its strategic supplier management office (SLM Rijk) found four high risks in Microsoft 365 Copilot, mainly caused by insufficient transparency from Microsoft about its processing of personal data, and concluded that on those findings Copilot could not yet be used in a compliant way (18). A first update published in September 2025 brought this down to two medium risks (19). The second update, of 27 May 2026, records that Microsoft "did not provide any relevant new information about the 2 medium risks" and ends at "2 medium and 9 low data protection risks". Among the measures it recommends are licensing only accounts without access to sensitive data, disabling access to Bing and enabling audit logging (20). Microsoft presented the reassessment as confirming that responsible use remains possible (21). In July 2026 the office, now called SLM Cloud, nonetheless advised restraint in deploying Copilot, partly in light of digital autonomy and sovereignty (22).

Two limits matter for a law firm reading these documents. The assessment tested Copilot in Word, Excel, PowerPoint and Outlook, tested no third-party applications and placed Anthropic models outside its scope (20), so it says nothing about Cowork, the Anthropic route or the legal plugins. Separately, the Dutch data protection authority (Autoriteit Persoonsgegevens) advised a municipality on its planned use of Copilot in a prior consultation requested in June 2025 and published in July 2026. Drawing on the municipality's own DPIA and on the government's reference DPIA of December 2024, not the 2026 update, it concluded that the use as described "would infringe the GDPR" unless further measures were taken, and that the reference DPIA does not meet the requirements of Article 35 for an individual organisation (23). A public-sector assessment is useful material, not a substitute for a firm's own.

Professional secrecy in the Netherlands, Germany and France

The Council of Bars and Law Societies of Europe (CCBE) put the starting point plainly in its October 2025 guide on generative AI: "The professional rules apply to all client data." The same guide anticipated the Copilot situation: generative AI has been built into many everyday tools lawyers use, "it may be that users (lawyers) do not realise that the tools use AI", and "the same care should be taken with confidential information when using these tools" (24). The three national frameworks put the same practical question in their own terms: may a lawyer let an outside provider handle client information, and on what conditions?

The Netherlands

The Advocatenwet lists confidentiality among the core values of the profession (article 10a) and imposes a statutory duty of secrecy that extends to the advocaat's staff and "other persons involved in the practice" (article 11a) (25). Rule 3 of the Code of Conduct requires "appropriate measures" to protect confidentiality, in particular in the choice of the means of communication, data processing and data storage the advocaat uses and their level of security; the commentary expects "care and professionalism" in choosing a medium or a provider (26). For automated tools the commentary to rule 13 is more specific: the duty to perform the work personally does not exclude the use of staff, "automated systems, robots and so on", but that "will require consultation with the client" (27). The Netherlands Bar's recommendations on AI, published at the end of 2025, add that an advocaat should know where data are stored and processed, including the country and the subcontractors, should carry out a DPIA where personal data are processed, and should ask the client's consent for the use of AI in the file (28). The Journal's article on the Bar's AI recommendations covers them in full.

Germany

German law has the most explicit rule. Section 43e of the Federal Lawyers' Act (BRAO) allows a Rechtsanwalt to give a service provider access to confidential information so far as the service requires it. The provider must be chosen carefully, and the contract must be in text form, bind the provider to secrecy with a warning about the criminal consequences of a breach, limit its access to what the contract needs, and state whether it may use subcontractors, who must in turn be bound to secrecy in text form (29). For services provided abroad, access is allowed only where the protection of secrets there is comparable to protection in Germany, unless the protection of the secrets does not require it (section 43e(4)); for services that directly serve a single mandate, the client must consent (section 43e(5)) (29). Section 203 of the Criminal Code allows disclosure to such "other persons involved" only so far as necessary, and makes the lawyer criminally liable if such a person, never bound to secrecy, then discloses a secret (30). The Federal Bar (BRAK) applied this framework to AI providers in its guidance of December 2024. It regards it as unsettled whether, for providers based in the United States, comparable protection under section 43e(4) can be established by reference to data protection standards, and recommends preferring providers with servers in Germany or Europe where possible (31). The German Bar Association (DAV), a voluntary association, takes the more permissive view that practice assesses section 43e(4) by data protection standards, and treats a tool adopted firm-wide as a general working instrument outside the consent rule of section 43e(5) (32). Our reading for Copilot: Microsoft is the provider the firm has engaged, and Anthropic is a further person within section 43e(3) no. 3, so the contract must allow Microsoft to use it and oblige Microsoft to bind it to secrecy in text form. Processing outside the EU Data Boundary also raises the section 43e(4) question that the BRAK leaves open. The "with Data Retention" models go further: they put Anthropic in a direct relationship with the firm under Anthropic's own terms, which would have to meet section 43e on their own before any client material reached them.

France

Article 66-5 of the 1971 Act covers consultations, correspondence between client and avocat, interview notes and "all the documents in the file", in advisory and litigation work alike (33). The 2023 code of conduct makes the secret a matter of public policy, "absolute, general and unlimited in time", from which neither the client nor any authority can release the avocat, save where the law provides (34). Article 2.3 of the national rules (RIN) requires the avocat to ensure that the secret is respected by the firm's staff "and by any person who cooperates with him in his professional activity", and makes the avocat answerable for any breach (35). None of these texts sets specific conditions for using an IT provider.

The national bar council (CNB) goes further in its practical guide on ethics and AI, adopted in March 2026. It states as a fundamental principle that avocats must never communicate data relating to their files or clients to generative AI, and among its criteria for choosing a legal AI tool it lists the nationality of the company holding the servers, excluding any company subject to extraterritorial provisions that let its state's authorities access the data, "such as American companies under their current legislation" (36). The same concern surfaced before a Senate committee of inquiry in June 2025. Asked whether he could guarantee under oath that French citizens' data entrusted to Microsoft through UGAP, the central public purchasing body, would never be handed over following a US order without the French authorities' explicit consent, Microsoft France's director of public and legal affairs replied: "No, I cannot guarantee it", adding that it had never yet happened (37). The Paris Bar's digital strategy of May 2026 is more pragmatic: the aim is "not to exclude certain technologies on principle" but to build control, reversibility and independence over time (38). In our view a French firm that lets Copilot work on its files departs from the CNB's recommendation, which is guidance rather than a binding rule, and should record why and on what terms.

Telling the client

On transparency, the CCBE's test is practical: if it can reasonably be assumed that an informed client "would object, make conditions, or otherwise have reservations" about the use of generative AI for the purpose in question, the lawyer should be transparent with the client (24). Some corporate clients answer that question for the firm in their outside counsel guidelines, for example by requiring notice or approval before an AI tool is used on their files. A firm that leaves a default on without checking those guidelines may breach an instruction it has accepted. The Journal's article on client consent before using AI covers the national rules in more detail.

Conflicts and information walls

Copilot "works only with content each user can access" (1). That is the right design, but it moves the whole weight of confidentiality inside the firm onto permissions. Cowork works across Outlook, Teams, Word, Excel, SharePoint and OneDrive (4): a request to build a chronology or compare terms across agreements can draw on any document the lawyer is able to open, including documents the lawyer has never seen because they sit on a site shared too widely years ago. Microsoft acknowledges the point in its own compliance documentation, noting that generative AI "amplifies the problem and risk of oversharing", and publishes a deployment blueprint whose first pillar is remediating oversharing (39) (40).

The CCBE warns that AI systems with access to information from several clients of one firm can lead to inadvertent information sharing or conflicts, and gives an example that will be familiar to any conflicts partner: a former client's data, still stored at the firm, used by the AI system in a case against that former client (24). All three national systems extend conflict rules to the whole firm. Dutch rule 15 applies the prohibition to the partnership the advocaat belongs to (27), and the Hof van Discipline has held that where a lawyer who acted for the other side joins the firm, the advocaat handling the case must immediately screen the newcomer off from all written and oral information about it (41). In Germany, section 43a(4) BRAO extends the prohibition to colleagues but lifts that extension where the clients concerned consent in text form after full information and suitable arrangements secure confidentiality; section 3(4) of the Rules of Professional Practice (BORA) requires those arrangements to exclude mutual access to paper files "and to electronic data", and their observance to be documented for each mandate (42) (43). In France, article 7 of the 2023 code applies the conflict rules to the structure as a whole and all its members (44). Whichever system applies, a wall that exists in a memo but not in the permissions is no wall for Copilot.

Microsoft's information barriers restrict communication and collaboration between defined groups in Teams, SharePoint and OneDrive, and Microsoft states that they cannot restrict communication in email, including Exchange Online (45). Cowork works with Outlook, so in our view mail is where a wall built with information barriers is weakest. A firm that relies on barriers should test, surface by surface, what a Cowork task can reach for a lawyer behind a wall before the legal plugin is offered to that lawyer. The Journal's guide to ethical walls in legal AI systems sets out the control stack in more detail.

Research and citations: what the suites do not bring

Most of the skills Microsoft and Anthropic describe are document work on the firm's own material: redlining against a playbook, drafting from precedents, extracting obligations, building chronologies (1) (5). For the law itself, Microsoft's and Anthropic's suites rely on research connectors and OpenAI adds an index of its own; for European law the offering is thin.

That is a starting point, not an answer. A Dutch, German or French matter usually needs more than consolidated EU law and supreme-court rulings: the national statute in the wording that applied on the relevant date, decisions of first-instance and appeal courts, judgments of the Court of Justice and the European Court of Human Rights, and, above all, the ability to open the passage a statement relies on. Before lawyers rely on any connector for research, a firm should test it on a handful of its own recent matters and ask four questions. Does it hold the courts and the legislation the firm actually cites? Can it show a statute as it stood on a past date? Does every citation open the passage relied on, not just the document? And does the suite flag when it answers without having consulted a source at all?

Courts and disciplinary bodies have already seen what happens otherwise. In July 2026 a Dutch disciplinary council, at first instance, reprimanded an advocaat, among other things for citing case law whose ECLI numbers did not exist or led to different decisions, "without checking the references for accuracy or even reading the decisions" (46). In Germany the Amtsgericht Köln noted in July 2025 that requirements set out in a brief were "apparently generated by artificial intelligence and invented" (47), and the CNB's guide lists several French decisions on the same problem between December 2025 and February 2026 (36). The Journal has followed the pattern in its articles on AI-generated fake cases and on checking that an authority is still good law. A skill that redlines fluently in Word does not reduce that risk. It can increase it, because the output looks finished.

What to settle now

The list assumes a firm that has Microsoft 365 Copilot licences and has not yet taken a position. The first three items are settings an administrator can change in an afternoon; the rest take longer.

  1. Decide who gets the legal plugin. Until that is decided, an administrator can turn off "Legal Skills in M365 Copilot in Word" and the "Cowork for Legal plugin" (2). A pilot group with a named supervising partner is better than a firm-wide default.
  2. Check both Anthropic settings. Look at the general setting for AI providers operating as Microsoft subprocessors and, separately, the setting for Anthropic models in Word, Excel and PowerPoint, whose default depends on when the tenant was created (11) (12). Decide whether Cowork is in scope, knowing that it uses Anthropic models, and keep "Anthropic models with Data Retention" off.
  3. Decide on web search. Unless the "Allow web search in Copilot" policy is configured, web search is available to users, and Cowork offers users no switch of their own (13). The Dutch government's DPIA recommends disabling access to Bing (20). Many firms will want web search off for matter work, or at least for practice groups that handle sensitive transactions and investigations.
  4. Clean up permissions before Cowork. Matter sites restricted to the matter team, no firm-wide sharing links on client folders, information barriers where the firm uses them, and a review of old sites that nobody owns (40) (45).
  5. Label privileged and highly confidential material. Copilot honours sensitivity labels (1). Where a label applies encryption, Copilot returns the content only to users who hold both the view and the extract usage rights. Microsoft also recommends enabling sensitivity labels for SharePoint and OneDrive; without them, the encrypted files Copilot can work with in those locations are limited (39).
  6. Set retention for Copilot interactions. Prompts and responses can be audited, searched in eDiscovery and retained or deleted under Purview policies (39). They are records of the firm's work, and in some proceedings they may be disclosable; see the Journal's article on AI chats and legal privilege.
  7. Paper the engagement. Read Microsoft's data protection terms as they apply to Copilot, subscribe to subprocessor notifications so that the right to object under Article 28(2) GDPR can actually be used, carry out a DPIA, and, in Germany, check the contract against section 43e(3) BRAO (14) (4) (29). The Journal's vendor due diligence checklist covers the rest.
  8. Approve partner plugins one by one. Each is a separate vendor with its own terms and its own data flows; read them before allowing the plugin under "Integrated apps" (9).
  9. Check client instructions. Review outside counsel guidelines, engagement letters and any client-specific restrictions on AI tools, and decide when the firm will tell clients, or ask them, before using the plugin on their matters.
  10. Adopt a verification rule. No authority goes into work product unless a lawyer has opened the source and read the passage. Fluent tracked changes are a draft, not a review.
  11. Train the people who will use it. Since 2 February 2025, Article 4 of the AI Act has required deployers to take measures to ensure, to their best extent, a sufficient level of AI literacy among their staff (48); the Journal's article on AI literacy for law firms explains what that means in practice.
  12. Decide how saved time is billed. A Microsoft in-house lawyer quoted in the announcement says a first review that might take an hour can often take several minutes (1). Clients will ask how that shows on the invoice; see AI and the billable hour.

How LexVera fits

The suites are built to work inside a firm's own documents and the software it already runs, and for redlining, drafting from precedents and organising a data room that is where the work is. LexVera is built for a different part of the job: legal research in Dutch law, EU law and the case law of the European Court of Human Rights. German and French national law are outside its scope. It answers from official sources and keeps each statement tied to the passage it rests on, so that a lawyer opens the judgment or the article before relying on it. Where a matter turns on a date, Dutch legislation can be read in the wording that applied on that date rather than today's. The two kinds of tool answer different questions, and many firms will use both.

A firm's documents stay within its workspace, under the access rules it sets for its matters and teams. LexVera supports the preparation; a qualified lawyer decides what becomes advice, which is the standard set out in our editorial policy.

Frequently asked questions

Are lawyers allowed to use Microsoft 365 Copilot?

Yes. No binding professional rule in the Netherlands, Germany or France prohibits it, although the French national bar council's guidance advises avocats never to give client data to generative AI. Using Copilot means engaging an outside service provider, so the firm must choose it deliberately, agree terms that meet the professional rules (in Germany, section 43e BRAO), understand where client data is processed, carry out a data protection impact assessment where the risk is likely to be high, respect client instructions and have a lawyer check the output before anything relies on it.

Is the Copilot legal plugin switched on by default?

In Word desktop, yes, for users with a Microsoft 365 Copilot commercial licence, according to Microsoft's administrator notice MC1509799 of 15 October 2026. The rollout is expected to finish by mid-December 2026. In Cowork, users must add the legal plugin themselves. Administrators can turn off "Legal Skills in M365 Copilot in Word" in the Microsoft 365 Apps admin center and the "Cowork for Legal plugin" in the Microsoft 365 admin center.

Does Microsoft 365 Copilot keep client data in the EU?

For tenants in the EU and EFTA, Copilot's own processing falls under Microsoft's EU Data Boundary, but three routes do not. Anthropic models, used by Copilot Cowork and, in some tenants, by Copilot in Word, Excel and PowerPoint, are excluded from the EU Data Boundary. Web search queries sent to Bing fall outside both the Data Protection Addendum and the EU Data Boundary. Partner plugins connect to other companies' services, so each vendor's terms and data locations have to be checked separately.

Does Microsoft train its AI models on our documents?

Microsoft states that Copilot does not use prompts, responses or documents to train the underlying foundation models, and that Anthropic, acting as its subprocessor, operates under Microsoft's Product Terms and Data Protection Addendum. Models offered as "Anthropic models with Data Retention" are different: Anthropic stores most inputs and outputs for up to 30 days, under its own terms rather than Microsoft's agreement. They are off by default and, in our view, should stay off for client work.

Do we need client consent before using Copilot on a matter?

It depends on the jurisdiction. In the Netherlands, the commentary to rule 13 of the Code of Conduct expects consultation with the client when automated systems are used, and the Bar's AI recommendations advise asking the client's consent for AI use in the file. In Germany, section 43e(5) BRAO requires consent only for services that directly serve a single mandate. In France, neither the 1971 Act nor the national rules set a specific consent requirement for IT providers. The CCBE advises transparency wherever an informed client would object, and some corporate clients set conditions in outside counsel guidelines.

Can Copilot or Claude for Legal replace a legal research database?

Not on their own. Microsoft's and Anthropic's suites work mainly on the firm's own documents and rely on connectors for the law; OpenAI adds an index of its own. OpenAI's legal index covers US law, Anthropic's repository warns that citations are unverified without a research connector, and Legal Data Hunter, available for both Claude and Copilot, is described as covering consolidated EU law and the case law of supreme and constitutional courts. Test any source on your own matters before relying on it.

Sources and methodology

This guide reflects the documents listed below as available on 8 November 2026. Product facts come from Microsoft's, Anthropic's, Google's and OpenAI's own announcements and documentation. These products and their default settings change frequently, so the settings described here should be checked in the firm's own tenant. Microsoft's administrator notice MC1509799 is quoted from a public archive of the Microsoft 365 Message Center. Dutch, German and French legal texts were read in the original language, and English quotations from them are our renderings. We did not establish whether the Raad van Discipline decision of July 2026 or the Amtsgericht Köln order of July 2025 was appealed. Statements on how the rules apply to these tools are our analysis. This is general professional information, not advice on a specific matter.

  1. Microsoft, "Introducing Microsoft Copilot for legal", Microsoft Copilot Blog, 15 October 2026
  2. Microsoft 365 Message Center, MC1509799, "Microsoft 365 Copilot: Legal plugins in Word and Cowork", published 15 October 2026 (public archive copy; Microsoft 365 roadmap ID 571884)
  3. Bob Ambrogi, "Microsoft Launches Copilot for Legal, Becoming the Fourth AI Giant in Five Months to Build Out a Legal Vertical", LawSites, 15 October 2026
  4. Microsoft Learn, "Overview of AI Subprocessors", updated 3 November 2026
  5. Anthropic, "Claude for the legal industry", 12 May 2026 (with later update)
  6. Anthropic, claude-for-legal repository, README (Apache 2.0), consulted 8 November 2026
  7. Thomas Kurian, Google Cloud, "Now introducing Gemini Enterprise for Legal", Google Cloud blog, 25 August 2026
  8. OpenAI, "Introducing Astra for Law", 17 September 2026
  9. Microsoft Learn, "Data, Privacy, and Security for Microsoft Copilot", updated 3 November 2026
  10. Microsoft Learn, "What is the EU Data Boundary?", updated 22 July 2026
  11. Microsoft Learn, "Claude models from Anthropic in Microsoft Online Services", updated 4 November 2026
  12. Microsoft Learn, "Copilot in Microsoft 365 apps with Anthropic models", updated 3 November 2026
  13. Microsoft Learn, "Data, privacy, and security for web search in Microsoft Copilot and Microsoft Copilot Chat", updated 3 November 2026
  14. Regulation (EU) 2016/679 (General Data Protection Regulation), Articles 28, 35 and 44 to 46
  15. Commission Implementing Decision (EU) 2023/1795 of 10 July 2023 on the adequate level of protection of personal data under the EU-US Data Privacy Framework
  16. General Court, judgment of 3 September 2025, Latombe v Commission, T-553/23
  17. Court of Justice, Case C-703/25 P, Latombe v Commission, appeal lodged on 31 October 2025, OJ C/2025/6610 (pending on 8 November 2026)
  18. SLM Rijk, "Memo toelichting bij DPIA Microsoft 365 Copilot", 18 December 2024, with the DPIA and FRAIA report of 17 December 2024
  19. Dutch Ministry of Justice and Security, Strategic Supplier Management (SLM Rijk), "Stand van zaken SLM december 2025", 15 December 2025, section on Microsoft 365 Copilot
  20. Privacy Company for SLM Rijk, "DPIA Microsoft 365 Copilot", 2nd update, version 1.8, public version of 27 May 2026, summary and scope (pp. 6 to 18)
  21. Microsoft Netherlands, "Update: DPIA Microsoft 365 Copilot afgerond: implementatie in de publieke sector mogelijk", 27 May 2026
  22. Dutch Ministry of Justice and Security, SLM Cloud, "Stand van zaken SLM Cloud juli 2026", 30 July 2026, pp. 3 and 4
  23. Autoriteit Persoonsgegevens (Dutch data protection authority), advice under Article 36(2) GDPR on the planned use of Microsoft 365 Copilot by the municipality of Haarlemmermeer (2025-018225), published 13 July 2026
  24. CCBE, "CCBE guide on the use of generative AI by lawyers", 2 October 2025, sections 4.1 (p. 17), 4.4 and 4.5 (p. 20)
  25. Advocatenwet (Dutch Act on Advocates), articles 10a and 11a
  26. Netherlands Bar (NOvA), Code of Conduct for Advocates 2018 (Gedragsregels advocatuur), rule 3 and commentary
  27. Netherlands Bar (NOvA), Code of Conduct for Advocates 2018, rules 13 and 15 and commentary
  28. Netherlands Bar (NOvA), Aanbevelingen AI in de advocatuur (recommendations on AI, published at the end of 2025)
  29. Bundesrechtsanwaltsordnung (German Federal Lawyers' Act), section 43e
  30. Strafgesetzbuch (German Criminal Code), section 203(3) and (4)
  31. Bundesrechtsanwaltskammer (German Federal Bar), Hinweise zum Einsatz von künstlicher Intelligenz (KI), December 2024, published 8 January 2025
  32. Deutscher Anwaltverein (German Bar Association), Statement no. 32/2025 on the use of AI in the legal profession, July 2025
  33. French Law no. 71-1130 of 31 December 1971, Article 66-5
  34. French Decree no. 2023-552 of 30 June 2023 (code of conduct for avocats), Article 4
  35. Conseil national des barreaux, Règlement intérieur national (RIN), consolidated version of 5 November 2026, Article 2.3
  36. Conseil national des barreaux, "La déontologie et l'intelligence artificielle", practical guide, 1st edition, April 2026 (adopted at the general assembly of 12 and 13 March 2026), pp. 15, 26, 28 and 29
  37. French Senate, committee of inquiry on public procurement, hearing of Anton Carniaux and Pierre Lagarde (Microsoft France), 10 June 2025
  38. Paris Bar, "Vers un barreau souverain", press release, 21 May 2026
  39. Microsoft Learn, "Microsoft Purview data security and compliance protections for Microsoft 365 Copilot and other generative AI apps", updated 27 May 2026
  40. Microsoft Learn, "Secure and govern Microsoft Copilot: Foundational deployment guidance", updated 3 November 2026
  41. Hof van Discipline (Dutch disciplinary court of appeal for advocates), 13 December 2019, ECLI:NL:TAHVD:2019:235, paragraphs 5.12 to 5.18
  42. Bundesrechtsanwaltsordnung, section 43a(4)
  43. Berufsordnung für Rechtsanwälte (BORA), version of 1 December 2025, section 3(4)
  44. French Decree no. 2023-552 of 30 June 2023, Article 7
  45. Microsoft Learn, "Learn about Information Barriers", updated 17 September 2026
  46. Raad van Discipline 's-Hertogenbosch, 27 July 2026, ECLI:NL:TADRSHE:2026:93, paragraphs 5.3 to 5.6 (first instance)
  47. Amtsgericht Köln, order of 2 July 2025, 312 F 130/25, paragraphs 23 and 24
  48. Regulation (EU) 2024/1689 (AI Act), Article 4 and Article 113