Microsoft is rebuilding Copilot around a simple but big idea. Agents that do not wait for you to ask. The company is folding its scattered Copilot apps into one and adding Autopilot, a new class of agent that runs continuously in the background. The first named one is Microsoft Scout.
From assistant to Autopilot
A normal Copilot waits for a prompt. An Autopilot does not. It gets its own persistent identity and watches signals across Teams, Outlook, OneDrive, and SharePoint through Microsoft Graph. When a trigger condition is met, it acts on its own, inside the permissions you and your org have set, across cloud, desktop, and web at once. Microsoft is also cutting underused pieces like Podcasts and Labs, and putting these background agents behind a paid tier. The direction is clear. The assistant becomes a coworker that notices things.
What builders should take from this
Two things. First, the design shift matters more than the brand. We are moving from request response to event driven agents, where the hard problems are triggers, identity, and permission scoping, not the chat box. If you build agents, model them as services that subscribe to events, not functions that wait for input. Second, watch the permission surface. An agent that acts across your whole Microsoft Graph without a prompt is powerful and risky in equal measure. Decide what it is allowed to touch, log every autonomous action, and make the off switch obvious. Proactive is the future, but only if you can audit it.