Claude Opus 4.8 in Microsoft 365 Copilot: Why a Model That Admits Uncertainty Matters

Claude Opus 4.8 dropped this morning. Same day, it is already live in Microsoft 365 Copilot and Copilot Cowork.

The upgrade that matters is not raw intelligence. It is honesty.

This version is trained to tell you when it is not sure instead of bluffing. For any business putting AI near real work, that is the bit that actually counts.

Why honesty beats horsepower

Most coverage of a new model focuses on benchmarks and capability. For adoption, that is rarely the deciding factor.

The thing that settles a nervous room is never the flashy demo. It is showing people where Copilot confidently gets things wrong, and how to work with it knowing that. A model that flags its own uncertainty makes that job a lot easier, because it does some of that signalling itself.

Confidently wrong answers are what make people quietly give up on these tools. Someone gets burned once by an answer that looked certain and turned out to be wrong, and they stop trusting the tool for anything that matters. A model that says “I am not certain about this, check it” is one people keep using. Trust is not built by the impressive answer. It is built by the model knowing when to say it is not sure, and that is an adoption lever, not a feature note.

This sits alongside a point we make often: the model is only one part of Microsoft 365 Copilot. The value comes from how Copilot uses your work context and how your people use Copilot. A model that is honest about uncertainty helps the second half of that, because it supports the review habits good adoption depends on.

The UK admin point worth checking this week

If your team runs Copilot, one thing is worth checking this week: whether Anthropic models are switched on in your Microsoft 365 admin centre.

In the UK they are off by default, largely for compliance reasons, since the processing sits outside the Microsoft EU data boundary. That is a deliberate setting, not an oversight, and it is the kind of detail that decides whether you can use a model at all in a regulated or client-sensitive context.

Always check with your legal team before enabling them. This is the same discipline that applies to any decision about using Copilot with client data. The question is not only “is the new model good”, it is “are we allowed to route our work through it, and have the right people signed that off”.

A sensible sequence is straightforward:

• Check whether Anthropic models are currently enabled in your Microsoft 365 admin centre.
• Confirm where the processing sits relative to the Microsoft EU data boundary and your own data commitments.
• Get explicit sign-off from your legal or compliance team before turning anything on.
• Decide which users and which work this applies to, rather than enabling it everywhere by default.

What this means for adoption

It is easy to treat each model release as the headline. The models will keep changing. The adoption challenge will not.

A more honest model is genuinely good news, because it nudges users towards the habit we want anyway: treat Copilot’s output as a strong draft and check it before relying on it. But a better model does not fix messy data, unclear governance or staff who were never shown how to work with it. Those are the things that decide whether Copilot earns its place in daily work.

So the practical takeaway is twofold. Make the deliberate, compliant choice about whether Anthropic models belong in your tenant, with legal involved. Then put the effort where it pays off over time, which is adoption and the habits around the tool, not the model name on the box.

The model will keep changing. The adoption challenge will not. That is the part worth getting right.

If you want help making a sensible call on model settings and turning Copilot into everyday usage, our Copilot adoption consultancy and Microsoft 365 Copilot training are built around it. You can also book a consultation to talk it through.