Copilot Cowork could already do things for you. As of July 2026, it can also decide when to start.
Microsoft’s latest Cowork update introduces event-driven tasks: instead of scheduling a job for a fixed time, you describe what to watch for, and Cowork proposes the automation for you to review and confirm before it runs.
What changed
Event-driven tasks sit alongside your scheduled prompts on Cowork’s Scheduled page. You describe a trigger in plain language, a matching email arriving, a Teams message, being @mentioned, and Cowork drafts the automation for your approval rather than running unsupervised from the first attempt.
Plugin tools gained a matching upgrade: they can now accept a file straight from your Cowork session as input, so a connected tool can convert a document, read an image, or attach a file to another system without you exporting it first.
Why this is a bigger shift than it sounds
Copilot Chat answers when asked. Cowork, since its June 2026 general availability, could already run a multi-step process on request. Event-driven tasks move it one step further, from something you operate to something that operates alongside you, watching for a condition and acting once it’s met.
That is useful. It is also exactly the kind of change that deserves a deliberate rollout, not an enthusiastic one. An automation that quietly fires on every matching email is only as safe as the trigger you wrote and the scope you gave it.
Where it fits your governance
Event-driven tasks inherit the same permissions and admin controls as the rest of Cowork, so a task can only see and touch what the person who created it could already access. The new capability is the trigger, not a new set of privileges.
Talk to us about rolling out Cowork responsibly.
Specialists in Business Applications, Modern Workplace and Azure. Let’s grow.
Sources: Microsoft Learn, What’s new in Copilot Cowork (July 2026 update, event-driven tasks and plugin file input). Accurate as of publication and subject to Microsoft’s ongoing updates.
