• June 16, 2026

Earlier this summer, I was bemoaning what I was calling the Claude-ification of the user experience. And to some extent we have seen a number of Claude Desktop like user agents and that will continue for a while (more announcements coming soon). But what will be key for vendors is not mimicking the Claude experience, but rather setting themselves apart. This brings me to Microsoft Copilot Cowork, which went GA today. So, has Microsoft set itself apart, you ask? I’d say when it comes to enterprise requirements, the answer is a qualified yes with potential for future improvements. Here’s what sets Copilot Cowork apart.

1) Model Choice (sort of) – Depending on the entitlement, you can choose between Claude models and OpenAI. Also, a new Cowork specific model is coming soon. I am hoping to see this expand more over time, and also, hopefully, see the ability to connect it with Frontier Tuning for customer-specific models when Frontier Tuning exits preview. That said, MSFT also claims that this model choice will save 30% to 40% on consumption vs. Claude when using the Microsoft 365 Connector – which it should.

2) A Provisioned and Contained User Experience –  I also like the added security and enterprise controls for governance and context management. There are a lot of people doing shadow AI right now with Cowork-style tools, and I’d much rather see an enterprise-provisioned and controlled model for most users. Claude Cowork is something of a power user tool, especially when you start to mess around with skills and advanced context (such as using an external knowledge base like Obsidian). And Microsoft seems to have a good bead on this and on the cost-control elements.

Despite the promise, there are still a couple of yellow flags that warrant further investigation.

1) All files in the cloud – One of the cool parts of Claude Cowork is that it can work with your local filesystem. I dig that, and given Microsoft’s recent focus on the edge with AI at the Build event, I expected it. A cloud-only stance also prompts me to wonder what the plan is for personal context-setting/second brains (a feature I really value as a power user). So, while Microsoft enforces a stronger security stance, some users may be put off by the lack of local capabilities. Again, most enterprises may prefer this, but the OpenClaw / Local AI devotees will not.

2) A more complex pricing model – You need to buy into a Microsoft 365 Copilot USL plan to access Copilot Cowork and other Microsoft tools, and then pay additional consumption fees on top. The usage model is variable based on the types and complexity of tasks. Now, I’m not saying that is any different than what people with Claude and other tools are doing, and maybe it ends up being a better deal to go with this option, especially given some of the Microsoft based efficiencies mentioned above. Let’s just say the proof will be in the numbers. If MSFT owns the stack, in theory, going all in with Microsoft should have a pricing incentive. We will need to see on that one.

For more information click the link below.

Copilot Cowork is now generally available

Recent Posts