Back to library
Advanced & governed: Cowork, enterprise automation and agent governanceHigh - action-taking, multi-source work needs review, spend controls and sensitive-data boundaries riskUpdated 5 SeptAI requiredExtra credits needed

Delegate a board pack preparation task with Cowork

A senior leader asks Cowork to gather approved source documents, draft a board-paper outline, create a PowerPoint summary and prepare a draft stakeholder email, with approval before sending or posting.

Where the action happens

Copilot Cowork / Microsoft 365 Copilot app

Product or feature needed

Copilot Cowork, Microsoft 365 Copilot, Work IQ, action approvals

AI required

Yes

Extra credits

Yes - Microsoft says Cowork is usage-billed in Copilot Credits

Technical skill

Medium

Risk level

High - action-taking, multi-source work needs review, spend controls and sensitive-data boundaries

Licence dependency

Advanced & governed stage — Microsoft 365 Copilot plus admin-enabled Cowork access and usage-based billing are required.

Credit dependency

Yes — Cowork tasks consume Copilot Credits; user/group limits and /cost should be used to manage consumption.

UK availability

available

Watch-outs for Advanced & governed

  • Cowork has been generally available worldwide since 16 June 2026 for Microsoft 365 Copilot customers, but admins still control discoverability and must enable usage-based billing before users can run tasks.
  • Cowork consumption is measured in Copilot Credits; organisations can set user or group limits and users can check approximate task cost with /cost.
  • UK Cowork does not require Anthropic/Claude. Microsoft separates Cowork access from model availability; if Anthropic is disabled, Cowork users can continue with allowed non-Anthropic models such as GPT models.
  • For UK organisations, model-provider choice should be recorded as a governance/configuration decision because Anthropic availability has separate admin and data-processing considerations.
  • For Work IQ or other connected agent tools, start read-only where possible and enable write operations only for a justified use case with appropriate identity and approval controls.
  • Treat Cowork access like any other temporary or role-based capability: record owner, purpose, limit and review date, and remove access when the user or project no longer needs it.
  • Agent governance becomes more important as shared, action-taking and connected Agents accumulate; maintain an inventory before the estate becomes hard to understand.
  • Use human approval or an equivalent controlled handoff before high-impact actions where the technology supports it, and keep human accountability for regulated AO decisions.

Last checked: 2026-09-05

Disclaimer: Always follow your organisation's internal guidance and policies regarding AI usage. The suggestions in this guide have been created to the best of accuracy, but Microsoft licensing, pricing and feature availability change frequently — treat them as a planning baseline, not a procurement quote.

Community feedback

Has your organisation tried this? Confirm whether it's possible, whether it's useful, and share any tips.

0

Confirmed possible

0

Reported not possible

0

Found it useful

0

Not useful

Add your feedback

Used to verify feedback comes from a real organisation. Never displayed publicly.

Is this possible in practice?

Is it useful?

Loading feedback…