Until now, Copilot did one thing: it answered when you asked. On 2 June, at its Build conference, Microsoft changed the rule. It announced a new category of agents called Autopilots, and the first one is Scout — an agent that works in the background and acts on its own, without being prompted each time.

Scout works across the Microsoft 365 apps your teams already use — Teams, Outlook, OneDrive, SharePoint — along with the email, calendar and contacts behind your day. It spots what needs a decision from you, flags it, and helps make sure approvals and follow-ups don’t slip. You interact with it in Teams, and a desktop app extends it to the browser and local resources.

The real shift isn’t “more AI”. It’s a change of role: today’s Copilot waits for a prompt and responds. Scout monitors continuously and acts.

Each Scout agent operates with its own governed identity in Microsoft Entra, strictly within the permissions and policies your organization sets. It also ships with a policy-conformance system that continuously checks it is working within your guidelines, and every check leaves an audit trail. For anyone accountable under NIS2 or GDPR, that isn’t a footnote — it’s the whole point. An assistant that answers questions can’t get you into trouble. An agent that acts on your behalf, with access to email, files and calendars, can — if the foundation underneath isn’t in order.

And to be precise: Scout isn’t available to everyone tomorrow. It’s currently in preview, for a limited set of organizations, gated behind Frontier enrollment, an Intune policy, an attestation step and a dedicated license. This isn’t “install and go”. It’s the direction Microsoft 365 is taking — which is exactly why it matters now, not in a year.

An agent that acts on its own is only as safe and as useful as the foundation it stands on. The questions that decide whether such an agent helps you or exposes you are the ones you should be asking anyway:

• Who has access to what, right now? Are permissions clean, or have they piled up over the years?
• Is your Entra identity tidy — active accounts, clear roles, no orphaned access?
• Are SharePoint and your files structured, or would an agent “see” things it shouldn’t?
• Are there data-governance policies an agent would automatically respect?

If the answer is “not sure”, an autonomous agent won’t accelerate the work — it will amplify the disorder already there. The upside: everything you do to be ready for Scout is worth doing anyway, agent or no agent.

You don’t need general availability to start moving. The practical order:

1. Get the foundation in order — identity, permissions, SharePoint access. This is where everything downstream is won or lost.
2. Clean up and structure your data and documents, so any automation layer runs on something solid.
3. Start with the automation that pays off today — Power Automate flows for approvals, notifications, recurring reporting. That’s your training ground for the agentic layer ahead.

Ready for the agentic layer?

The Microsoft 365 workplace is going agentic — that’s no longer an assumption, it’s the official roadmap. The question is no longer if, but whether you’ll be ready. We build exactly the automation and AI layer that gets you there, on a clean, governed foundation.

See how intelligent process automation works in Microsoft 365 →