On 9 November 2026, Microsoft announced that Copilot connector write actions are generally available in Copilot Chat and Cowork. Copilot can now create, update and delete data in connected apps such as Jira, Notion or Canva. Copilot has moved from reading to acting, which changes the governance question.

The headlines say little about control. Microsoft Learn says more than I expected, though gaps remain.

What changed

Federated Copilot connectors (built on MCP) used to read third-party data live. Where a publisher exposes the tools, they can now write too (Message Center MC1476316). The Researcher agent stays read-only. Write tools aren’t enabled separately; they come with the connector.

Cowork plugins bundle skills and connectors, packaged like Teams apps and managed with the same admin tools.

Who may do what

Access to Cowork. A spending policy that selects Cowork is the access control. Even a tiny credit limit still grants access. In Microsoft’s example, a tenant-wide one-credit policy gives every user access, whatever the pilot policy says.

Installing plugins. Admins deploy and block plugins under Agents > Tools in the Microsoft 365 admin center (tenant administrator or Copilot administrator role). Users can also upload a plugin and share it with specific colleagues. Organization-wide publication needs admin approval, but Microsoft states there is no single tenant setting that turns plugin sharing off. You can only block or unpublish afterwards.

Enabling connectors. Control sits in several places: Agent and plugin access (by publisher type), User access, and per-connector enablement and staged rollout under Copilot connectors > Your connections. Microsoft-built connectors are available by default; external publishers’ connectors need their own publisher-type option or individual enablement.

Creating, changing, deleting. The user does, with the user’s own permissions in the source system. Each user signs in personally; admins can’t do it for them. Least privilege in Jira, Notion or your CRM becomes your most important write-action control.

How approval works

Write, update and delete tools default to Needs approval. A confirmation card shows the tool, the connector and the data about to be sent. Users choose Allow once, Allow for conversation or Always allow per tool. If a publisher adds or changes a write tool, it returns to Needs approval.

Automated Cowork tasks run with the creator’s permissions and ask before changing a shared system, unless the user pre-authorized it.

I found no documented admin setting that forces approval or disables Always allow. That choice currently sits with each user.

Audit, DLP and the Power Platform gap

Cowork activity, including adding or sharing a plugin, appears in the Purview unified audit log under Audit (Standard). Purview DLP covers Cowork for sensitive prompts, labeled files and web-search grounding. The admin-center Tools view that lists a connector’s write tools is still marked “coming soon”, and users can inspect them under Settings > Sources.

For Power Platform admins, here is the catch: Power Platform data policies are documented for Copilot Studio agents. I found no Microsoft statement that they govern Cowork plugins or federated connectors. You now have two governance planes: the Microsoft 365 admin center with Purview, and the Power Platform admin center. Don’t assume your Power Platform DLP policy covers Cowork.

Who is liable?

The connector terms of use are blunt. By enabling connectors, you authorize Microsoft to send customer data to third-party services and to modify data in them. As data controller, you are “solely and exclusively responsible” for that functionality and for complying with third-party rights. Microsoft “assumes no liability for errors.” Microsoft’s support pages add: “You are responsible for actions Copilot takes on your behalf.”

I’m not a lawyer, so check your contracts. The design is clear, though: the user approves, and the organization that enabled the connector carries the responsibility.

A practical checklist

1. Inventory first. List connectors and their write tools. Consider switching off external publishers by default and enabling connectors one by one.
2. Pilot with groups. Scope the spending policy and each connector’s staged rollout to a security group.
3. Block unneeded tools under Agents > Tools, where supported.
4. Tighten source permissions. Review roles in the target apps.
5. Set an “Always allow” rule. My recommendation: never for delete, rarely for update.
6. Watch plugin sharing. Review pending org-wide requests.
7. Assign owners. Admins run controls, makers build plugins, business owners accept the risk per use case.
8. Re-review regularly. Publishers can add tools at any time.

Cowork governance is a stack of settings across admin centers, and part of it is still undocumented. If you want to map it for your tenant, this is what we cover in our Power Platform and Copilot Agentic AI Governance workshops at HanseVision. Ping me a Direct Message at LinkedIn.

---

Sources:

Primary (Microsoft):

• https://learn.microsoft.com/en-us/copilot/cowork/cowork-admin-governance
• https://learn.microsoft.com/en-us/copilot/cowork/cowork-access
• https://learn.microsoft.com/en-us/copilot/cowork/cowork-manage-plugins
• https://learn.microsoft.com/en-us/copilot/cowork/cowork-faq
• https://learn.microsoft.com/en-us/copilot/cowork/responsible-ai/cowork-responsible-ai-faq
• https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/federated-connectors-overview
• https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/manage-federated-connectors
• https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/terms-of-use
• https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-plugins-skills-mcp-servers?view=o365-worldwide
• https://learn.microsoft.com/en-us/purview/ai-copilot-cowork
• https://learn.microsoft.com/en-us/purview/audit-copilot
• https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot-location-learn-about
• https://learn.microsoft.com/en-us/microsoft-copilot-studio/admin-data-loss-prevention
• https://learn.microsoft.com/en-us/microsoft-365/managed-apps/?view=o365-worldwide
• https://support.microsoft.com/en-us/Microsoft-365-Copilot/get-started-with-cowork

Message Center mirrors and Microsoft Tech Community repost:

• https://mc.ai-news.cz/message/MC1476316 (mirror of MC1476316, full Microsoft text)
• https://mc.merill.net/message/RM570964 (roadmap item 570964, status Launched, GA)
• https://www.worldprogramming.org/posts/turn-copilot-insights-into-action-with-connector-write-capabilities-titif2 (repost of the Microsoft Community Hub article dated 2026-11-09)
• https://www.linkedin.com/posts/petrijamsen_turn-copilot-insights-into-action-with-connector-activity-7526600800530227202-kqHK (Petri Jämsen, summary of the announcement)