All insights

Copilot Updates · 6 min read

Claude Fable 5.1 in Copilot Cowork and Copilot Studio: What UK Firms Should Check First

By James Wilkinson 2 September 2026

Microsoft has added Anthropic's Claude Fable 5.1 to Copilot Cowork and Copilot Studio. What it changes for agent builders, and the admin and data questions UK firms need to answer first.

TL;DR
  • Microsoft has added Anthropic's Claude Fable 5.1 to Copilot Cowork and Copilot Studio, pitched at long-running work, financial analysis and front-end visual coding.
  • The Copilot Studio side matters more. Model choice is set per agent when the agent is created, so a frontier model is now a design decision with a real cost attached.
  • Anthropic models ship switched off for UK, EU and EFTA tenants and sit outside the EU Data Boundary. Enabling them is a governance decision before it is an admin one.
  • Fable-class models have their own data retention position. Some firms get Fable 5.1 under Microsoft's terms, others get it as an Anthropic model with data retention under Anthropic's own terms.
  • Set spending limits first, scope access to a pilot group second, choose the model third. Then test one real workflow.

On 1 September 2026, Microsoft announced that Anthropic’s Claude Fable 5.1 has joined the frontier models available in Copilot Cowork and Copilot Studio. The announcement is short. It says Fable 5.1 is built for long-running work, financial analysis and front-end visual coding, that Work IQ grounds it in your files, meetings, chats and business data inside your existing permissions and that availability varies by region and organisation.

That last line is doing more work than it looks like for anyone reading this from a UK tenant. We worked through the same trade when Claude Opus 5 arrived in the Copilot model selector, and most of it carries straight across.

What Fable 5.1 actually is

Fable is Anthropic’s Mythos-class family. Fable 5.1 and Mythos 5.1 are the same underlying model with different levels of safeguards, and Fable is the generally available one. Anthropic positions it as its most advanced model for coding, knowledge work and long-running problem solving.

The numbers Anthropic published on release:

  • Terminal-Bench 4.0 (agentic coding): 55.8%, against 42.0% for Fable 5 and 52.3% for Opus 5
  • AutomationBench (business workflows): 31.4%, against 17.1% for Fable 5 and 26.9% for Opus 5
  • Humanity’s Last Exam (multidisciplinary reasoning, no tools): 60.9%
  • GDPval-AA v2 (knowledge work): 1853, against 1723 for Fable 5

If you build agents rather than write code for a living, AutomationBench is the one to look at. Business workflow performance nearly doubled against Fable 5 and moved clearly past Opus 5. That is the benchmark closest to what a client actually asks an agent to do.

Microsoft’s framing of financial analysis and front-end visual coding is a fair reflection of what early access partners reported rather than Anthropic’s own headline. Financial research firms testing the model reported better grounding in source documents and fewer tokens burned for the same accuracy. The claim about tighter plans and more concise summaries is qualitative too. Several partners said the model communicates more clearly over long tasks, which matters a lot when an agent runs unattended for an hour and you have to review what it did.

On price, Anthropic cut cache read costs by 75% to $0.25 per million tokens, which brings typical workloads down about 25% against Fable 5, and up to around 45% for heavily agentic work. Worth knowing, but do not assume it passes straight through to you. Inside Microsoft you are not billed by token, you are billed in Copilot Credits.

The Copilot Studio half matters more than the Cowork half

Cowork is the headline. Copilot Studio is the part that changes what you can build.

In Copilot Studio the model is chosen when the agent is created, so this is not a background upgrade that quietly improves everything you already shipped. It is a decision you make per agent, and it is a decision you can now get wrong in a more expensive direction. A model built for long-running autonomous work is the right call for an agent that reasons over a messy document set or coordinates a multi-step process. It is the wrong call for an FAQ agent on your website.

The practical shape of this is multi-agent setups where a capable orchestrator plans the work and cheaper models do the repetitive parts. That is now a real design pattern rather than a theoretical one, and it is where most of the cost control lives. The same judgement we set out in our guide to the Copilot model picker applies here, and the harness a Copilot Studio agent is built on sits alongside model choice as the other build-time decision.

The bit the announcement does not spell out for UK readers

Anthropic models are switched off by default in EU, EFTA and UK tenants. The setting exists in the Microsoft 365 admin centre, but it shows as No users until somebody changes it.

More importantly, Microsoft’s documentation states that Anthropic models in Copilot, Researcher, Copilot Studio, Power Platform and Copilot in Microsoft 365 apps are currently excluded from the EU Data Boundary and, where applicable, from in-country processing commitments. If your firm has told clients that its data stays inside a particular boundary, that is a sentence to read twice before anyone flips a toggle. It is the same discipline we describe in our guide to using Copilot with client data.

To turn it on you need the AI Administrator or Global Administrator role, and the path is Microsoft 365 admin centre, Copilot, Settings, View all, then AI providers operating as Microsoft subprocessors. You then choose which users or groups get access, so this does not have to be an all-staff decision.

For Copilot Studio and Power Platform there is a second gate. Once Anthropic is enabled at tenant level, external large language models still have to be allowed in the Power Platform admin centre. Two switches, two admin centres.

One more trap. If your firm opted in to Anthropic models previously under Anthropic’s own separate terms, you need to opt in again. The toggle went back to off.

Data retention is where Fable is genuinely different

Microsoft updated its Anthropic subprocessor guidance on 1 September, and it now treats Fable-class models as their own category.

Depending on eligibility, some organisations get Fable 5.1 with Anthropic acting as a Microsoft subprocessor, covered by Microsoft’s Product Terms and Data Protection Addendum. In that case no extra opt-in is needed beyond the main Anthropic setting. Microsoft’s Customer Copyright Commitment also applies to Anthropic models used inside covered products, including Copilot and Copilot Studio.

Other organisations get it as an Anthropic model with data retention. That is a separate control, off by default everywhere, and in that mode Anthropic acts as an independent processor under its own commercial terms rather than your Microsoft agreement. Anthropic stores most inputs and outputs for up to 30 days. Content flagged by its trust and safety classifiers can be held for up to two years. Classification scores can be kept for up to seven years. Retained data is not used for training without your permission.

Anthropic is addressing this with Enterprise Frontier Safeguards, which keeps data in cloud infrastructure the customer controls while still allowing automated safety monitoring. It rolls out in phases from this autumn, and eligible customers can use Fable 5.1 with zero data retention in the meantime.

For a professional services firm handling client confidential material, that is a partner-level conversation and a data protection assessment. It is not an IT toggle.

What it costs to run

Cowork is not a separate licence. It sits on top of Microsoft 365 Copilot, an admin has to enable it, usage-based billing has to be switched on and a spending limit has to be set before anything will run. Usage is paid in Copilot Credits.

Copilot Studio agents are metered too. If you are enabling a frontier model for long-running autonomous work, the sensible order is spending limits first, pilot group second, model choice third. Check your consumption in the admin dashboards after a week of real use rather than modelling it on a spreadsheet beforehand. Our ten habits for keeping Copilot Credits under control and the Cowork effort selector both matter more once a stronger model makes bigger jobs tempting.

What we would tell a firm this week

  1. Find out whether Anthropic is enabled in your tenant at all. In most UK tenants it is not.
  2. Decide who gets access. Scope it to a group, not the whole firm.
  3. Read the data retention position that applies to your organisation and get it signed off by whoever owns client confidentiality.
  4. Set a spending limit before anyone runs a Cowork task.
  5. Pick one real workflow and test it properly. Model choice only pays off where the work is genuinely long, multi-step and grounded in your own data.

The bottom line

The interesting part of this announcement is not that Copilot has another model in the list. It is that model choice has become a design decision for anyone building agents, with a real cost and a real governance path attached. That decision now sits with the people building the agents, which in most firms of the size we work with means nobody has been given it yet.

That is the work we do at FiveForward: designing and building agents in Copilot Studio and the Power Platform, and running agent workshops for the people who will build and look after them. The Agent Journey shows where Cowork and purpose-built agents sit on that path, and pricing is fixed and published. If you are working out where agents fit in your firm, and what you would need in place before you could safely run one, book a free 30 minute consultation.

Sources checked

Last checked: 2 September 2026.

Related reading

More on Copilot Updates

Copilot Updates Claude Opus 5 in Microsoft 365 Copilot: Should UK Businesses Switch It On? Claude Opus 5 is live in the Microsoft 365 Copilot model selector. When it beats GPT-5.6, why UK tenants have it switched off and what enabling it involves. Copilot Updates Claude Opus 4.8 in Microsoft 365 Copilot: Why a Model That Admits Uncertainty Matters Claude Opus 4.8 is live in Microsoft 365 Copilot and Copilot Cowork. The upgrade that matters is honesty about uncertainty, plus a UK admin point to check. Copilot Updates GPT-5.6 Arrives in Microsoft 365 Copilot: What It Changes for UK Businesses GPT-5.6 is rolling out across Microsoft 365 Copilot including Cowork. What it changes about model choice for firms that keep client work inside Microsoft. Copilot Explainers The Copilot Model Picker Nobody Switches: When to Use Default, GPT-5.5 or Claude Opus Microsoft 365 Copilot has a model picker most teams never touch. When to use the default, GPT-5.5 or Claude Opus, and why you never leave Microsoft. Copilot Licensing Cowork's New Effort Selector: You Now Decide How Hard Your Agent Works Copilot Cowork's new effort selector lets you decide how hard an AI agent works and what it costs. What it signals about the agentic era and how to use it well. Copilot Licensing Copilot Cowork Costs: Ten Habits That Keep Copilot Credits Under Control Copilot Cowork now bills every task in Copilot Credits. Ten working habits that keep spend sensible, from tighter briefs to the /cost command. Copilot Governance Can You Use Microsoft Copilot with Client Data? A Practical Governance Guide Can you use Microsoft Copilot with client data? Yes, but only inside clear governance, approved tools and a review process built around risk levels. Automation Which Copilot Studio Harness Should Your Agent Be Built On? An agent harness explained in plain English, why the GitHub Copilot harness costs more and how to decide which harness each agent build belongs on. Agents Microsoft Copilot agents Plain-English guidance on where Microsoft Copilot agents fit, how to govern them and when to build. Capability map The Agent Journey Five stages from using your first Copilot agent to running a team of agents, with two doors at every stage. Service Copilot Studio consultancy Agents that start on their own, act in your systems and stop for one of your team to approve, built in Copilot Studio inside your Microsoft 365. Next step Pricing Fixed prices for AI agent work: Discover, fixed-price builds, agent workshops and the Embed retainer. Next step Book a free consultation A free 30-minute call about the work an agent could take off your team, and whether Discover is the right next step.

Common questions

Questions about Claude Fable 5.1 in Copilot

Is Claude Fable 5.1 available in Microsoft 365 Copilot?
Microsoft announced on 1 September 2026 that Claude Fable 5.1 is available in Copilot Cowork and Copilot Studio. Availability varies by region and organisation, and for UK, EU and EFTA tenants Anthropic models are switched off by default until an administrator enables them.
Why are Anthropic models switched off by default for UK tenants?
Because the processing sits outside the Microsoft EU Data Boundary, and where applicable outside in-country processing commitments. Microsoft's documentation currently excludes Anthropic models in Copilot, Researcher, Copilot Studio, Power Platform and Copilot in Microsoft 365 apps from those boundaries, so the decision belongs with whoever owns client confidentiality.
What is an Anthropic model with data retention?
It is a separate control, off by default everywhere. In that mode Anthropic acts as an independent processor under its own commercial terms rather than under your Microsoft agreement. Anthropic stores most inputs and outputs for up to 30 days, with longer retention for content flagged by its trust and safety classifiers. Eligible customers can use Fable 5.1 with zero data retention in the meantime.
How do we enable Anthropic models for Copilot Studio?
There are two gates. An AI Administrator or Global Administrator enables Anthropic in the Microsoft 365 admin centre under AI providers operating as Microsoft subprocessors, then scopes access to chosen users or groups. For Copilot Studio and Power Platform, external large language models also have to be allowed in the Power Platform admin centre.