May 16, 2026

Microsoft Copilot Cowork: From Chat to Doing the Work

A practical look at Microsoft Copilot Cowork for UK professional services. Real use cases for finance, legal, HR, marketing and sales teams.

For two years your team has been using Copilot as a smart text generator. It writes summaries. It tidies up emails. It explains formulas. Useful, but the human still does the work of stitching tasks together.

Cowork is the bit that changes that. It is Microsoft's new agentic mode for M365 Copilot, built in partnership with Anthropic, and it moves Copilot from drafting one email to running multi-step jobs across Outlook, Word, Excel, Teams and SharePoint. The unit of output is a completed job, not a paragraph.

Key takeaways

  • Cowork is Microsoft's new agentic mode for M365 Copilot, built in partnership with Anthropic and running on Claude models.
  • It moves Copilot from drafting one email to running multi-step jobs across Outlook, Word, Excel, Teams and SharePoint.
  • It uses your real Microsoft 365 context through the Work IQ layer and saves outputs to a OneDrive folder per task.
  • It sits on top of a Microsoft 365 Copilot licence and is currently delivered through Microsoft's Frontier early access programme.
  • Best fit today: repeatable, structured workflows where a human still approves the external actions.

What Cowork actually is

Strip away the marketing and Cowork is a long-running agent that lives inside M365 Copilot. You give it a goal. It plans the steps. It uses skills (read a Word document, edit an Excel file, draft a PowerPoint, schedule a meeting, send a Teams message) to execute. It asks you to approve anything that touches the outside world.

Two things make it different from the Copilot most firms have already deployed.

It is built with Anthropic. Cowork is the Microsoft 365 implementation of Claude Cowork, using Anthropic's models as the engine. At time of writing the picker offers Sonnet and Opus 4.7. Microsoft co-developed Cowork with Anthropic rather than building it on their own foundation models. That matters because Claude is strong at the kind of multi-step planning Cowork is built for.

It actually does the work. Standard Copilot drafts the email. Cowork drafts the email, opens your drafts folder, attaches the report it generated from the Excel file you uploaded, asks who you want it sent to and waits for you to hit send. The unit of output is a completed job, not a paragraph.

The talking-to-doing shift

This is the bit that matters commercially. Cowork closes the gap between briefing Copilot one thing at a time and handing it the assignment.

Review my Q1 expense report, flag anything that breaches our policy, draft an approval request to Finance for the items that need sign-off and create a summary deck for the partner meeting.

That single sentence used to be half a day of work for a finance manager. Or four separate Copilot prompts followed by manual stitching. Cowork treats it as one job, runs the skills it needs in sequence and comes back with everything in a OneDrive folder with the draft email queued in Outlook.

The question is no longer whether your people can use Copilot to write a better email. It is which recurring workflows you can hand to Cowork and free up billable hours.

Use cases by profession

Cowork is good at things that look like processes. Inputs, a defined output and a chain of steps in between. Here is what we have seen work in training and pilot sessions.

Finance and accountancy

  • Expense and policy review. Upload a messy expenses workbook with policy thresholds. Cowork categorises spend, flags items above your approval limit and drafts the request emails to the budget holders.
  • Client research and snapshot decks. With the new plugins feature, you can bundle skills with data connectors. A financial research plugin that pulls 10-K data from SEC Edgar and produces a one-page client briefing is now a build job rather than a research project.
  • Workforce analysis. Hand it an HR export. Get back a workforce briefing deck, branded to your firm, attached to a draft email to the practice manager.

Legal

  • SOW and engagement letter drafting from meeting transcripts. Drop a Teams transcript and your standard SOW template into Cowork. It produces a draft with the right structure, scope, deliverables and milestones. We have built deeper versions of this pattern at Goodman Jones using Power Automate and Word content controls for firms that need iManage or Dynamics integration, but Cowork is the lighter-weight version deployable in days.
  • Contract triage. A multi-page services agreement summarised into a three-bullet executive overview, with calendar reminders created for every key date in the contract.
  • Email thread synthesis. A messy approval thread with five participants, three scope changes and a missed question becomes a clean summary with open items, owners and a drafted reply.

HR

  • CV screening. Upload a job description and a candidate CV. Cowork identifies the top skills required, scores the match, rewrites the candidate's summary against the role and produces interview question suggestions.
  • Internal talent search. Point it at your consultant or engineer CV library in SharePoint. Ask which people have Power BI or IFRS experience. Get a ranked list and a draft Teams message to the resource manager.
  • Onboarding pack assembly. Combine policies, role briefs and reading lists into a branded onboarding document. A repeatable job that currently takes HR coordinators half a day.

Marketing

  • Vendor and tool comparisons. Three quotes in a SharePoint folder become a scored comparison with risk flags and a recommendation deck.
  • Content repurposing. A long-form report becomes a five-slide summary deck with executive language, then a LinkedIn-ready summary, then an internal Teams message.

Sales and business development

  • Daily account briefings. Schedule Cowork to scan emails, meetings and Teams messages each morning for activity from a named client. Receive a Teams message with what has moved and suggested next steps.
  • Pipeline housekeeping. Trigger Cowork to review the week's deal correspondence, flag stalled threads and draft the follow-up emails for your approval.

Where Cowork fits today, honestly

A few things to be straight about, because the demos are slick and the reality has edges.

It is still in Frontier. Cowork is delivered through Microsoft's early access programme. That means an enterprise admin has to enable it and you should expect features to move. Treat this as a rolling capability rather than a finished product.

Licensing depends on your SKU. Cowork needs Microsoft 365 Copilot. If your firm is on E7, Copilot is included. On other SKUs (E3, E5, Business Premium) Copilot is a per-user add-on, and Cowork sits on top of that. If your firm has not yet committed to Copilot licensing, that is the first commercial decision. For the licensing detail and how this fits with Agent 365 and the E7 SKU, our Cowork, Agent 365 and E7 explainer for UK organisations has the commercial breakdown.

Anthropic, data residency and your compliance team. Cowork runs on Claude. Anthropic operates as a Microsoft subprocessor (covered under M365 Product Terms and the DPA, no model training on your data), but Claude processing happens outside the EU Data Boundary. For UK and EU tenants, Microsoft sets the Anthropic toggle to Off by default. An admin has to opt in, and most professional services firms will want a DPIA on file before they do. The pillar post walks through this in detail.

Approval gates are a feature, not friction. Every external action (sending an email, creating a meeting, posting a Teams message) requires user confirmation. Compliance officers like this. End users sometimes grumble at the friction. For professional services firms with regulatory obligations, this is exactly the trade-off you want.

Quality varies with input quality. Cowork is at its best when given clean inputs and well-defined goals. Vague prompts produce vague output. The firms we have seen get the most from it are the ones who define their top recurring workflows before going anywhere near rolling it out to their teams.

The OneDrive output can get messy. Cowork saves every task's inputs and outputs to a folder in your OneDrive. Useful for traceability. Less useful when twenty tasks in you are scrolling through folders trying to find the right deck. Build a habit of renaming or moving the outputs you want to keep, and set a tidy-up routine before the folder count gets away from you.

The plugins layer is where this gets serious. Users can build their own personal skills directly from a prompt. Admins can go further and bundle skills plus data connectors into a plugin, then ship it firm-wide through Agent 365. That is the difference between Cowork as a productivity toy and Cowork as the foundation for firm-wide automation. Most firms have not engaged with the plugins capability yet, and that is where the early-mover advantage sits.

What to do next

Two practical recommendations.

If you already have Copilot licences. Pick one workflow per practice area and run a short pilot in Cowork. Measure time saved, error rate and user satisfaction. Do not roll wide until you have a process for governance and approval review.

If you have not licensed Copilot yet. The Cowork capability changes the ROI calculation. The old question of whether Copilot is worth the per-user cost was answered by counting emails and Excel formulas. The new question is which firm workflows you can hand to Cowork over the next twelve months. That is a different conversation, and your competitors are starting to have it.

At IQIT we work with UK professional services firms on Copilot adoption, including hands-on Cowork training and workshops to identify the highest-value workflows in your firm to automate first. If you want to see Cowork running against your real processes rather than a Microsoft demo tenant, get in touch.

Ready to get more from Microsoft 365?

Book a free consultation to talk through where you are and where you want to be. No pressure, no hard sell. Just an honest conversation.