Microsoft announced on 5 November 2026 that Claude models in Copilot would enter the EU Data Boundary by the end of 2026 for organizations in the EU and EFTA. This is a future commitment; EU Data Boundary processing for Claude is not live yet. If your Microsoft 365 approval, data protection impact assessment or internal policy depends on that commitment, keep Claude disabled for broad use. A selected group can still run a controlled pilot on low-sensitivity work.
The 5 November announcement changes the processing-location commitment. It makes no new claim about Claude’s capabilities.
The announcement does not make EU Data Boundary processing available today
Microsoft says organizations in the EU and EFTA will be able to use Claude across Copilot experiences, including Copilot Cowork, with processing inside the EU Data Boundary by the end of 2026. The company presents this as removing the choice between using Claude and relying on its regional processing commitment.
The announcement gives no launch day, and further details are due closer to availability. A buyer therefore needs answers to two questions before final approval: when support becomes available for the tenant, and which Copilot experiences and data flows fall within the contractual scope.
Claude is disabled by default in the EU and EFTA. An administrator can enable it for the whole organization or restrict access to selected users and groups. This keeps a limited evaluation separate from organization-wide deployment. The company also says that, once available, processing for tenants already using Claude will move into the EU Data Boundary automatically.
The EU Data Boundary and in-country residency are separate commitments
The EU Data Boundary is Microsoft’s commitment to store and process covered data for Microsoft 365 and other online services within the EU and EFTA. According to the November announcement, it is included in the contractual terms for eligible Microsoft 365 customers without an additional purchase or opt-in.
In-country data residency is a separate option. The company says it is available in ten EU and EFTA countries. For a tenant based in Hungary, the EU-wide boundary does not by itself establish that data is stored in Hungary.
The company also states that customer data passed to Claude within Copilot is not used to train generative AI foundation models. This is a useful vendor commitment, but it does not replace the organization’s data inventory, permission review or DPIA update.
Cowork usage is billed on top of the user licence
Copilot Cowork performs long-running, multi-step work inside Microsoft 365. The April 2026 demonstration shows Work IQ retrieving information from email, calendars, Teams transcripts and SharePoint, then creating Word documents, presentations and Excel files. At that time, some multi-model Cowork and Researcher features still required the Frontier Program.
Cowork became available worldwide on 16 June 2026. At launch it ran on Anthropic models including Opus 4.8 and Sonnet 4.6. This makes the EU Data Boundary commitment directly relevant to those workflows.
Microsoft’s 16 June announcement says Cowork requires a Microsoft 365 Copilot User Subscription License and adds usage-based billing in Copilot Credits. The PayGo rate published on 16 June was $0.01 per Copilot Credit.
Task charges depend on model use, context retrieval, tool calls and runtime. Because Cowork is billed by usage, the user licence alone does not create a fixed monthly cost ceiling. Administrators can set spending limits at tenant, group and user level. Separate usage alerts can be configured for the organization and groups.
The internal test described in the announcement found Copilot Cowork to be 30–40% cheaper per prompt on average than Claude Cowork using its Microsoft 365 connector. The study covered 125 runs across 12 light, medium and heavy prompts, with Opus 4.8 on both sides. Copilot Cowork costs came from internal logs, while Claude Cowork costs were calculated from public API rates. This was a vendor-run comparison, and actual cost varies with configuration and task design. Procurement should compare the current rate card and cost per accepted task on the organization’s own workflow. Broader contract considerations appear in the Microsoft AI procurement guide for 2027.
If Copilot’s data or integration boundaries require a custom setup, the enterprise AI platforms page outlines the available architectures. Enterprise AI platforms
Start the pilot with a verifiable low-sensitivity workflow
Choose a Microsoft 365 task whose result is straightforward to review. Suitable starting points include a meeting brief, presentation outline or spreadsheet summary created from approved SharePoint material. Exclude special-category personal data, trade secrets and documents whose handling policy depends on the EU Data Boundary.
Evaluate five parts of the workflow:
- whether Claude can reach any file or message for which the user lacks permission;
- whether it uses approved sources correctly;
- whether every material statement in the generated document can be checked;
- what an accepted result costs in Copilot Credits;
- whether the task and result appear in the required audit logs and follow retention rules.
When work remains within Teams, SharePoint and other Microsoft 365 services, the guide to deciding when Copilot is sufficient helps separate packaged functionality from work that needs a custom integration.
Which situations justify enabling Claude now?
| Situation | Recommended decision | Reason |
|---|---|---|
| The DPIA or contract requires EU Data Boundary processing | Wait for confirmed availability | The November announcement commits to delivery by year-end 2026 |
| You want to compare Claude and GPT on low-sensitivity office work | Run a pilot with a selected group | Access can be limited by user or group |
| Cowork already processes business information | Review the current data flow | Cowork ran on Anthropic models at launch, while the new regional commitment is not yet in effect |
| You plan organization-wide deployment | Require written approval before launch | Contractual coverage must include the services being used |
| Cost per completed task is unknown | Apply a pilot spending limit | Cowork uses consumption-based billing |
Regulated organizations and public bodies should hold broad deployment where EU Data Boundary processing is an approval condition. Teams evaluating model quality on low-sensitivity documents can run a restricted pilot now. Broad deployment should follow confirmed availability and an update to the organization’s documentation.
Use these steps to prepare the approval decision
- Check the tenant region, contractual eligibility and current Microsoft 365 processing terms.
- List the Copilot experiences in which Claude would be used and the data entering each workflow.
- Keep organization-wide access disabled; create a separate pilot group with approved data sources.
- Measure task success, permission enforcement, audit coverage and cost per accepted result.
- Make broad enablement conditional on confirmed EU Data Boundary processing, then update the DPIA, processing records and procurement documents.