Microsoft Copilot (Microsoft 365): Federated Copilot Connectors will support write, update and delete actions
Why it matters: Breaking change — admin action may be required
From Microsoft's description: “Copilot acts with the user's own account and permissions at the third-party service, and every create, update, or delete action requires the user's explicit confirmation before it runs.”
⏰ Act before October CY2026 · overdue
<p>Federated Copilot connectors (MCP type) currently let Microsoft 365 Copilot read data from third-party services in real time. With this update, the connector tools that create, update, and delete content in those services are unblocked in Copilot Chat, so users can complete work without leaving Copilot. Copilot acts with the user's own account and permissions at the third-party service, and every create, update, or delete action requires the user's explicit confirmation before it runs. Admins can view each connector's read and write/delete tools in the Microsoft 365 admin center and disable connectors that don't meet their organization's policies.</p>
How this was classified (derived by the tracker — not Microsoft's label)
- breaking · 70% confidence · matched breaking-cue
Copilot acts with the user's own account and permissions at the third-party service, and every create, update, or delete action requires the user's explicit confirmation before…
Affected: Microsoft Copilot (Microsoft 365)