Microsoft Just Blocked Claude Fable 5 Internally Over a 30-Day Data Retention Rule
Quick verdict
The Claude Fable 5 launch story moved on from benchmarks to governance fast. Anthropic reversed the covert capability throttling that researchers had flagged, doing it within about a day of the backlash. But the part that actually hits paying enterprise customers is separate and still in place: Fable 5 and its Mythos-class siblings carry a 30-day data retention requirement that overrides zero-data-retention contracts. Microsoft has restricted the model for its own employees while legal reviews it, and some AWS Bedrock customers are pulling it for the same reason.
What happened
Two things ran in parallel. The first was the climbdown. Anthropic had shipped Fable 5 with a safeguard that could quietly weaken the model on tasks it read as frontier AI research, without telling the user. After days of criticism from researchers, the company reversed course. Simon Willison welcomed the rollback, and others framed it as a retreat under pressure. The strongest objection was never that safeguards exist. It was that hiding them breaks the basic contract between a paid provider and its users, since you can no longer tell whether a weak answer came from the model, your prompt, or an intervention you were not shown.
The second thread did not get reversed, and it is the one with contracts attached. Anthropic's data retention policy for Mythos-class models says prompts and outputs are kept for 30 days for trust-and-safety review, with policy-flagged data held for as long as two years. The wording matters because it applies even to customers who had configured zero data retention through Claude Console, Claude Enterprise, Claude Code, AWS Bedrock, Google Cloud Agent Platform, or Microsoft Foundry. Teams that built their compliance posture around a non-retention guarantee suddenly did not have one for this model.
Microsoft and AWS customers are pulling it
The clearest reaction came from Microsoft. According to The Verge, Microsoft restricted internal employee access to Claude Fable 5 in the GitHub Copilot model picker while its legal team reviews the Mythos-class retention terms. The blocker is not model quality. It is that Fable 5 is not covered by the same zero-retention posture as other Claude models the company already ships to Copilot and Foundry customers.
It is not only Microsoft. On Reddit, an engineer reported their company disabled the model through AWS Bedrock despite an existing zero-retention agreement, after internal guidance concluded the 30-day requirement effectively bypassed the contract. The pattern is the same wherever sensitive data is involved: during a mandatory retention window, the safest call is to keep the model out of production and limit it to controlled trials with non-sensitive prompts.
This sits on top of a model that is already expensive to run. Fable 5 lists at $10 per million input tokens and $50 per million output, and it is bundled into paid plans only through June 22 before moving to usage credits. So the enterprise pitch right now is a pricey frontier model that you also cannot point at confidential work until legal signs off. That is a hard sell.
Why it matters
The reason enterprises pay for an enterprise plan is to keep the provider out of their data. When a retention rule quietly overrides that, the value of the plan drops, and a blanket internal block becomes the simplest fix. Ryan Greenblatt argued the better path is a real access program with KYC and monitoring for legitimate researchers, rather than broad restrictions or hidden ones. Nathan Lambert's read was that the core mistake was an uneven, misleading rollout that cost Anthropic trust.
The practical lesson builders keep repeating is portability. Gergely Orosz put it as an engineering recommendation: keep your models behind a provider-agnostic router so you can switch vendors quickly when terms or behavior change in a way you cannot accept. When a single model's data policy can force a company-wide block overnight, depending on one provider's subscription looks like a liability. That is the same case we make in one subscription for all AI models and the best app for running multiple AI models, and it is part of why open weights keep gaining ground, which we cover in OpenAI vs Anthropic vs Google.
None of this means Fable 5 is a bad model. The launch numbers were real, and we walk through them in our Claude Fable 5 launch breakdown. It means the model and the contract are two different products, and right now the contract is the one keeping it out of a lot of enterprises.
Video: AI data retention and why enterprises care
A general primer on AI data privacy and retention rules, which is the exact concern driving these enterprise blocks.
FAQ
Did Anthropic actually reverse the silent capability nerf?
Yes. After researchers objected to Fable 5 quietly degrading answers on frontier AI research tasks without notice, Anthropic rolled the policy back within roughly a day. The separate 30-day data retention requirement was not reversed.
Why did Microsoft block Claude Fable 5 for employees?
Microsoft restricted it in the GitHub Copilot model picker while legal reviews the Mythos-class retention policy. Fable 5 keeps prompts and outputs for 30 days, which is not covered by the zero-retention posture Microsoft relies on for other Claude models.
Does the retention rule affect zero-data-retention customers?
It can. Anthropic's policy applies the 30-day retention even to organizations that configured zero data retention through Claude Console, Claude Enterprise, Claude Code, AWS Bedrock, Google Cloud Agent Platform, or Microsoft Foundry. If your compliance depends on non-retention, check before using Fable 5 on sensitive data, and consider keeping models portable as we describe in Claude Code alternatives.
Sources
- The Verge - Microsoft restricts Claude Fable 5 internally
- Anthropic - data retention practices for Mythos-class models
- @simonw - welcoming the rollback of the silent degradation policy
- @kimmonismus - Anthropic retreating after researcher criticism
- @RyanPGreenblatt - the case for KYC-gated access over hidden sandbagging
- @GergelyOrosz - put models behind provider-agnostic routers
- r/ClaudeAI - Microsoft restricting employees from using Claude Fable 5
Further reading
Try all the models mentioned in this article
Admix gives you GPT-5, Claude, Gemini, and 350+ AI models in one app. Compare responses side by side. Free to start.
Start free on Admix