All insights

Copilot Explainers · 6 min read

Copilot Chat vs Cowork: What's Actually Different?

By James Wilkinson 21 August 2026

Microsoft 365 Copilot can already draft emails and manage your calendar. So what does Cowork add? The difference explained, including the agentic harness.

TL;DR
  • Copilot Chat is an assistant. You drive, it responds, one exchange at a time, in the flow of your work.
  • Cowork is an agent. You describe an outcome, it builds a plan, executes the steps across your apps and delivers finished work, checking in with you at key points.
  • The technical difference is the harness: Cowork wraps the AI model in an orchestration layer that can plan, loop, use tools, take actions and keep going until the job is done.
  • Commercially they differ too. Chat usage is included in your Microsoft 365 Copilot licence. Cowork is billed on usage, in Copilot Credits.
  • Use Chat for quick answers and in-the-moment help. Use Cowork when the work spans multiple steps, sources and apps.

A question we get a lot: “We’ve got Microsoft 365 Copilot. It already reads my calendar, drafts my emails and helps in meetings. What does Cowork do that Copilot doesn’t?”

It’s a fair question, because on paper the two overlap. Both are grounded in your work data. Both can draft emails, work with your calendar and pull from your files. The difference isn’t really about what they can touch. It’s about who’s driving, and how long the AI stays on the job.

What premium Copilot already does well

Let’s give Microsoft 365 Copilot its due first, because it’s genuinely capable. With the premium licence, Copilot is grounded in your work data: your emails, calendar, meetings, chats and files. It can draft a reply in Outlook, summarise a meeting you missed, help you find time and schedule with colleagues, rewrite a document section in Word, build a first-pass deck in PowerPoint and answer questions across everything you have access to.

All of that is assistance. You’re in the app, you ask, it responds, you take the output and carry on. Every exchange is one round trip: your prompt in, its answer out. If the task has ten steps, you’re the one holding the plan and prompting your way through each step. Copilot makes each step faster. It doesn’t own the task. Agent Mode in Word, Excel and PowerPoint blurs this line a little, letting Copilot work through a document or spreadsheet build inside the app, but it’s still app-bound assistance rather than cross-app delegation.

What Cowork does differently

Cowork flips that relationship. Instead of prompting your way through a task, you hand the task over. Describe the outcome you want, say preparing for a client meeting, and Cowork turns it into a plan: gather the relevant emails and files, review the last meeting’s notes, draft a briefing document, build a supporting analysis, schedule prep time in the calendar and draft the follow-up email. Then it executes that plan, step by step, across your apps, and comes back with finished artifacts.

Three things make this categorically different from Chat:

It runs long. Cowork tasks aren’t one round trip. The agent works through multi-step workflows over minutes, not seconds, looping back, checking its own work and retrying steps where needed.

It takes actions, not just drafts. Cowork can send emails, schedule meetings, create documents, post updates and manage files on your behalf. It pauses at checkpoints for your approval before anything consequential happens, so you stay in control, but the doing is delegated.

It delivers work products. The output of a Cowork task isn’t a chat reply. It’s the deck, the briefing doc, the analysis, the scheduled time, saved into Microsoft 365 where your team can pick them up.

Microsoft’s own framing is the cleanest summary: use Copilot Chat for quick answers and back-and-forth in the flow of your work, use Cowork when the work spans multiple steps and apps and you want finished artifacts back. We looked at what that shift means for approval and readiness when Cowork was still in preview, in Microsoft Copilot Cowork: from AI chat to AI-supported task completion, and the advice there still holds now it is generally available.

The harness: the technical bit worth understanding

Here’s the part most explanations skip, and it’s the actual answer to “why can’t Chat just do this?”

An AI model on its own is a brain in a jar. It’s brilliant at reasoning over whatever you put in front of it, but it has no hands. It can’t open your calendar, loop through a plan or remember where it got to. What turns a model into an agent is the harness: the software wrapped around the model that gives it a working loop.

In Cowork, the harness is what breaks your request into a plan, decides which tools and apps each step needs, feeds the model the right context at the right moment (that’s Work IQ, Microsoft’s intelligence layer over your work data, doing the grounding), executes actions, checks results, loops back when something fails and pauses at checkpoints for your sign-off. It also picks task-appropriate models along the way, which is why one Cowork job can quietly use different AI models for different steps.

Copilot Chat has a much lighter harness. It grounds your prompt in your data, calls the model once and returns the answer. That’s the right design for its job: instant, conversational, in the flow of what you’re doing. Cowork’s heavier harness is what makes delegation possible, and it’s also why Cowork tasks take longer and cost more to run.

Once you see the harness, the whole agent landscape makes sense. The models across the industry are increasingly similar. The differences you actually feel between AI products are mostly differences in harness: what the AI is allowed to do, how it plans, how it’s grounded and where the human checkpoints sit. The same idea now runs through Copilot Studio too, where the harness you build an agent on decides what it can do and what it costs.

The commercial difference

The two are also priced differently, and it follows directly from the architecture.

Chat usage is included in your Microsoft 365 Copilot licence. Ask it a hundred things a day, the price doesn’t move.

Cowork requires that same licence as a prerequisite but includes no usage. Every Cowork task is metered in Copilot Credits, and consumption scales with the job: the models used, the context retrieved, the actions taken and how long the agent runs. A light task costs little, a deep multi-source job costs a lot. You’re paying for work performed, which is exactly how you’d expect delegated work to be priced. Our ten habits that keep Copilot Credits under control covers the planning bands and the admin controls in detail.

That’s also why Cowork now gives users an effort selector, a slider that controls how hard the agent thinks on each task, and a /cost command to see what a task consumed. We’ve covered that feature and how to build sensible credit habits around it in Cowork’s new effort selector: you now decide how hard your agent works.

Which should your firm use?

Both, for different jobs, and the split is easy to teach.

Reach for Chat when you’re in the middle of something and need help now: a draft, a summary, an answer, a rewrite. It’s the assistant at your elbow. If you want to get more from it, the model picker most people never switch is the first thing to learn.

Reach for Cowork when you’d otherwise block out an afternoon: meeting prep, research across multiple sources, producing a connected set of deliverables, workflows that touch several apps. It’s the colleague you delegate to, with you signing off at the checkpoints.

The firms getting the most from Microsoft’s AI stack right now are the ones teaching their people that distinction early, because the failure modes run both ways: people prompting Chat through fifty steps of a task Cowork would have owned, and people burning credits sending Cowork to do what Chat answers for free.

Want help working out where each fits?

Chat and Cowork are the general-purpose ends of Microsoft’s agent story. Beyond them sit purpose-built agents grounded in your own documents and workflows, which is where Copilot Studio agent builds come in. If you’re working out where each layer fits in your firm, that’s what we do at FiveForward, and the Agent Journey maps the stages most firms move through. Book a free 30 minute consultation, no pitch, no obligation.

Sources checked

Last checked: 21 August 2026.

Related reading

More on Copilot Explainers

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. 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. Automation Copilot Studio's New Engine: What the GitHub Copilot Harness Changes and What It Costs Copilot Studio's default is now the GitHub Copilot harness, the engine behind Copilot Cowork. What changes, what the credits cover and the checks before you build. Copilot Agents Microsoft Copilot Cowork: From AI Chat to AI-Supported Task Completion Microsoft Copilot Cowork moves from asking questions to delegating repeatable tasks. A guide to readiness, approval steps and where humans must decide. 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 Readiness Microsoft Work IQ and Copilot Context: Why Your Microsoft 365 Data Setup Matters Microsoft Work IQ is the context layer behind Copilot and agents. Your Microsoft 365 data, permissions and content ownership now decide how useful AI can be. 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. 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 Agent Builds Custom agents grounded in the right knowledge and built for defined jobs, in your own tenant. 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 Copilot Chat vs Cowork

What is the difference between Copilot Chat and Copilot Cowork?
Copilot Chat is an assistant. You prompt, it answers, one round trip at a time, inside the app you are working in. Cowork is an agent. You describe an outcome, it builds a plan, works through the steps across your Microsoft 365 apps, pauses at checkpoints for approval and hands back finished work such as a briefing document, a deck or scheduled time.
Why can't Copilot Chat just do what Cowork does?
Because of the harness. Chat grounds your prompt in your work data, calls the model once and returns an answer. Cowork wraps the model in an orchestration layer that plans, picks tools, retrieves context through Work IQ, takes actions, checks results, loops back when a step fails and pauses for your sign-off. That heavier harness is what makes delegation possible.
Is Cowork included in the Microsoft 365 Copilot licence?
No. Cowork requires a Microsoft 365 Copilot licence as a prerequisite but the licence includes no Cowork usage. Every Cowork task is metered in Copilot Credits, and consumption scales with the models used, the context retrieved, the actions taken and how long the agent runs. Chat usage is included in the licence.
When should our firm use Chat and when should it use Cowork?
Reach for Chat when you are in the middle of something and need help now, such as a draft, a summary or a rewrite. Reach for Cowork when you would otherwise block out an afternoon, such as meeting prep, research across several sources or a connected set of deliverables that touches several apps.