Microsoft expands Copilot Cowork

Microsoft is trying to turn Copilot from a chatbot into a worker. That is the real story here. On May 5, the company said Copilot Cowork is getting mobile access, reusable skills, and plugin hooks so it can carry out tasks across apps and devices, not just talk about them. But almost at the same moment, Microsoft was dealing wi(github.com)n and AI product fit can break trust fast. (microsoft.com)— basically a version of Copilot that can plan work, run steps in the background, and return with something finished. Microsoft says it sits on top of “Work IQ,” a layer that uses company data, tools, and organizational context so the system can act inside the business instead of just pulling generic answers from the internet. (microsoft.com)t wants people to hand off tasks from anywhere, then let the work continue in the cloud. Second, Microsoft is adding built-in and custom “skills,” which are reusable instructions for recurring jobs like document creation, meeting coordination, and research. Third, plugins widen the set of tools Cowork can touch, pushing it closer to workflow automation instead of chat assistance. (microsoft.com)ecause this is where Copilot stops being a clever autocomplete layer and starts looking like process software. A skill is basically a saved playbook — your structure, your tone, your steps, your approvals. If that works, a team can turn one good workflow into a repeatable one. The catch is that repeatability is exactly where mistakes get expensive. A wrong answer in chat is annoying. A wrong action repeated across a workflow is a real operational problem. (microsoft.com)ue? Because Microsoft just got a reminder that attribution is part of product design, not a footnote. In VS Code, users reported that commit messages were picking up “Co-authored-by: Copilot” even when they said Copilot had not meaningfully contributed — and in some cases when they did not use it at all. The backlash was not just aesthetic. In software teams, commit metadata is accountability metadata. If that gets fuzzy, the tool feels sneaky fast. (github.com). An AI assistant does not. That is why developers quickly started pushing for “Assisted-by” instead — a label that admits machine help without pretending the machine owns the work. This sounds small, but it is not. Enterprise AI lives or dies on whether users feel the system is honestly describing what it did. (github.com) ### What does Xbox have to do with this? Xbox is the other half of the story. On May 5, new Xbox CEO Asha Sharma sai(github.com) development on Copilot for console. That pullback came barely a year after Microsoft pitched Gaming Copilot as a major AI feature. Basically, one part of Microsoft is expanding Copilot deeper into work while another part is deciding a Copilot chatbot was not the right answer for gaming. (polygon.com) ### Is Microsoft retreating from Copilot? Not really — but it is ge(github.com) and more like “AI where it can prove value.” In Xbox, Sharma is redirecting AI toward graphics, discovery, and personalization instead of a visible chatbot. In Microsoft 365, the bet is the opposite: make AI more visible, but also more useful by tying it to actual tasks. (geekwire.com) ### Bottom line? Microsoft’s bet is getting clearer. Copil(polygon.com)nside real workflows, trust details become product details — attribution, consent, control, and whether the feature belongs there at all. Cowork is the expansion story. VS Code and Xbox are the warning label.