What it does

Cowork is Microsoft's framing for agents working alongside people on business processes rather than just answering prompts — agents that pick up multi-step work in Dynamics 365, hand off to colleagues, and keep a human in the loop for judgement calls. It's more a direction of travel than a single toggle.

Key facts

• "Cowork" describes a working model — human-plus-agent collaboration on end-to-end processes — realised through the autonomous agents across the D365 apps and Copilot Studio.
• It's tied to the agent ecosystem, so it inherits their metering, capacity and governance rather than being separately licensed as one product.
• Because it's an evolving concept, exact branding, availability and packaging move between announcements. Treat blog claims as directional until they land in the docs.
• The controls that matter — oversight, escalation, audit — come from the underlying agent platform and admin centre.

When to use / skip

Use the idea to frame a client's automation ambition and plan an agent roadmap. Don't scope a project against "Cowork" as if it were a defined SKU — scope against the concrete agents that deliver it.

Configuration decisions

• Which processes are candidates for human-plus-agent working versus staying manual.
• Oversight, approval and audit expectations for agent-led work.
• How agent capacity and governance are managed across the estate.

Gotchas

• Marketing runs ahead of shipped capability here. Anchor commitments to GA agents, not the vision keynote.
• Without clear escalation and audit, "agents doing work" becomes a governance and trust problem fast.

Consultant notes

• Use Cowork as a conversation-starter for the automation roadmap, then translate it into specific, licensed agents.
• Keep a paper trail: oversight, approvals and audit are what get this past risk and compliance stakeholders.
• Re-verify branding and packaging before quoting — this space is renamed and repackaged often.

---

*Verify