6.4. Microsoft Copilot Cowork
💡 First Principle: Delegating to a capable assistant works because of three things: a clear brief, visible progress, and a rule that they check with you before anything goes out in your name. Microsoft Copilot Cowork is built on the same three things. You describe the outcome, Cowork plans and works through the steps where you can see them, and it stops for your approval before it sends, posts, schedules or changes files. Your job shifts from doing the work to supervising it.
This matters because Cowork is the first Copilot experience that acts in your apps on your behalf. That raises the stakes on everything earlier phases covered: a vague brief now produces wrong actions, not just a weak draft, and an approval you click without reading has real consequences. Cowork is generally available for work and school accounts and requires a Microsoft Copilot (formerly Microsoft 365 Copilot) license plus usage-based billing (2.3.2). Microsoft describes it as an agentic system, which is different from an agent: it combines planning, skills for each type of task, and your approvals into one supervised workflow that can run for minutes or hours.
Mental model: the delegation loop
| You stay responsible for… | Cowork takes care of… |
|---|---|
| A clear, specific brief | Breaking the brief into steps |
| Approving each sensitive action | Loading the right skills and doing the steps |
| Steering, pausing or cancelling | Showing progress, inputs and outputs |
| Reviewing the final results | Saving outputs to OneDrive |
⚠️ Common Misconception: "Cowork is autonomous, so once it starts I'm out of the loop." The opposite is the design. Cowork asks you to approve actions like sending an email or posting in Teams before they happen, asks multiple-choice questions when it needs input, and can be paused or cancelled at any time. Even scheduled and event-driven tasks default to draft and approve. Treating Cowork as "fire and forget" is exactly the over-reliance risk from Phase 3.
