Microsoft documents admin controls for Copilot Cowork rollout
Reviewed by Helen Jones
Microsoft's Copilot Cowork admin guidance was updated on 17 June 2026. It explains how administrators control access, discoverability, plugins, model availability, browser use, security and compliance, data residency, and usage-based billing. Cowork requires usage-based billing before users can access it. Admins can make the experience discoverable, approve requests, choose which plugins are available, turn off individual models, control local browser use, and set per-user or per-group consumption limits. The guidance also links Cowork to Microsoft Purview protections and the existing Microsoft 365 Copilot data residency model.
Before Cowork reached general availability, many admin teams could treat it as a preview feature and wait for the control surface to settle. That is no longer the comfortable position: users can now request access and every enabled task can create usage-based spend. The practical work is therefore not deciding whether Cowork is interesting. It is deciding who can test it, which plugins and models are allowed, whether browser use is appropriate, and how quickly spending alerts reach the people accountable for the budget.
Analysis
Before enabling Cowork, create a small pilot group in the Microsoft 365 admin center, turn off browser use until policy is reviewed, and set user-level Copilot Credit limits for the first month.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Microsoft documents admin controls for Copilot Cowork rollout", Collab365 Spaces. 2 sources referenced.