Spring til indhold

MC1546438: Claude switches on in the EU on 9 December unless you choose

By Michal Lampe Sørensen · 5 min read · 19 November 2026

Verified against Microsoft Learn, October 2026

Contents

In short

If your Microsoft 365 tenant is in the EU or EFTA and you have made no choice for Anthropic, Microsoft turns on the Claude models for all users in Copilot on 9 December 2026 (MC1546438). To decide for yourself, choose in the admin center before then. Copilot Cowork, Copilot's agent for multi-step tasks, requires Anthropic to be enabled and is billed in Copilot Credits. According to Microsoft, processing of Claude moves into the EU Data Boundary in early December. Whether all of Cowork is covered is not confirmed.

What happens on 9 December, and who is affected?

It affects admins of EU and EFTA tenants that have made no choice for Anthropic under the setting "AI providers operating as Microsoft subprocessors". The Claude models are off by default for customers in the region today. On 9 December 2026 Microsoft turns them on.

An existing choice is respected. If Claude is off for you, it stays off. If an admin has already turned it on, you do not need to do anything.

Two details are easy to miss:

  • •The option "only in Copilot in Microsoft 365 apps" is removed. Tenants that chose it move to "all users" on 9 December.
  • •Claude models with Data Retention are governed by a separate setting and are not part of the change.

After the date an admin can turn Claude off or limit access again at any time. MC1546438 mentions no price. Usage arises in features billed in credits, for example Cowork (see below).

How to choose before 9 December

The setting is in the Microsoft 365 admin center. Screens change, so use the steps as a guide:

1. Go to Copilot > Settings > View all 2. Open AI providers operating as Microsoft subprocessors 3. Select Anthropic 4. Choose No users, Specific users and groups or All users, and save

It requires the AI Administrator or Global Administrator role. Ask your IT lead or partner who holds it.

If you do not choose, Claude is turned on for all users. Whether that fits your processor assessment is for you to decide. "Specific users and groups" is an option that limits rollout to a pilot group while the rest wait.

What does Microsoft say about the EU Data Boundary?

The EU Data Boundary is Microsoft's commitment to process and store customer data in the EU and EFTA. Anthropic is a Microsoft subprocessor for Claude, and Microsoft's enterprise data protection applies to Claude in Copilot, unless the model is labeled Data Retention.

MC1546438 says processing of the Claude models moves into the EU Data Boundary in early December, and that existing users move automatically. There is no exact date for the move. The Microsoft Learn page on Anthropic models (updated 19 November) still says Claude is outside the EU Data Boundary. The message is newer, but check whether the page has been corrected before you rely on it in an assessment.

The message covers only the processing of the Claude models. It says nothing about whether the rest of Cowork, for example the runtime and the tools, sits inside the EU Data Boundary. That is not confirmed in Microsoft's documentation, so do not put it in a processor assessment as a fact. It is a question for your Microsoft partner or for Microsoft.

If your data protection adviser previously said no to Claude because processing was outside the EU, the reasoning may change from early December. That can be a reason to revisit the decision.

What is Cowork, and what does it cost?

Copilot Cowork is an agent in Microsoft 365 Copilot that takes a task and carries out several steps across Outlook, Word, Excel and Teams. See the guide to Copilot Cowork. Microsoft's licensing guide lists Anthropic as a prerequisite for Cowork, together with a Copilot license and usage-based billing enabled. If Claude is off, Cowork cannot be used. The default on 9 December therefore opens the door to the feature that creates usage. The link between the message and Cowork is inferred here. MC1546438 does not mention Cowork.

Copilot Credits are Microsoft's unit for AI usage. The rate is $0.01 per credit on PayGo (pay-as-you-go). Credits are pooled at tenant level, so all users draw on the same pool. Microsoft gives these indicative figures for a Cowork task:

Task typeCredits per taskApproximate price (own calculation)
Light100-300$1-3
Medium300-700$3-7
Heavyover 700over $7

The figures are Microsoft's own planning estimates. Usage depends on model, runtime, context and tools. Microsoft's licensing guide mentions no included allowance for Cowork. Cowork is billed in credits on top of the Copilot license.

Set limits with spending policies

Usage is controlled in Copilot > Cost Management in the admin center with spending policies. They work as access control, not only as a budget.

  • •Limit. If an admin chooses a limited monthly budget, the user loses access to agents and services for the rest of the month when the limit is reached. Credits reset on the 1st. The user can request more credits. An unlimited budget is also an option.
  • •Minimum 2,000 credits per user per month when you set a limit. That equals $20 and, with Microsoft's figures, 7 to 20 light tasks or at most just under three heavy ones. Microsoft says the requirements may change.
  • •Per-user cap (optional), so one person does not use the whole pool.
  • •Alerts to administrators. Users only get an email if a per-user cap is set.
  • •Prepaid first. Credits from capacity packs and pre-purchase plans (P3) are used before PayGo.
  • •Departmental billing. Global and Billing administrators can bill a policy against a different Azure subscription.
  • •Model templates for Cowork. You can restrict which models a group may use. A template must contain at least two models.

A policy sets a limit and does not reserve credits for users. A user in several policies gets the one with the highest per-user limit. On a tie the largest overall policy wins, then the newest. Settings are not combined, and the user does not fall over to another policy when the limit is reached.

If you buy Copilot Business through a CSP partner, usage-based billing is enabled by default for new purchases in Microsoft's FY27 Q3 (January-March 2027), with a default limit of 4,000 credits per user per month. It was originally announced for 1 December 2026.

Run a pilot group for a month before you set the cap, and compare usage with the time users save in the Copilot ROI guide.

Sources: Microsoft Message Center MC1546438 (10 November 2026), Anthropic models in Microsoft Online Services (Microsoft Learn), Managing AI experiences enabled by usage-based billing (Microsoft Learn), Partner Center announcements, November 2026 (Microsoft Learn) and Copilot Credits (Microsoft Licensing). This article reflects Microsoft's documentation as of 19 November 2026 and is not legal advice.

Will Cowork be used? Calculate the usage first

The Copilot ROI tool sets license and usage costs against the time users actually save.

Calculate Copilot ROI

Frequently asked questions

Do I need to do anything if we already use Claude in Copilot?+

No. Existing choices are respected, and Microsoft says processing moves automatically to the EU Data Boundary in early December. If you are on the older option "only in Copilot in Microsoft 365 apps", you move to "all users" on 9 December.

What happens if I choose nothing?+

For EU and EFTA tenants with no choice for Anthropic, Claude is turned on for all users on 9 December 2026. An admin can limit it or turn it off afterwards.

Can a spending policy stop a user from using too many credits?+

Yes, if an admin chooses a limited monthly budget. The user then loses access to the selected agents and services for the rest of the month and can request more credits. The minimum is 2,000 credits per user per month. Credits reset on the 1st.