Microsoft just shipped a new category of AI agent for the workplace. Scout, unveiled at Microsoft Build on June 2, 2026, is an always-on autonomous agent that works across Microsoft 365 without needing to be prompted each time it acts. That shift from reactive to proactive is the key architectural change worth understanding.
Microsoft calls this class of agent an "autopilot." Scout is the first of this breed. It runs in the background continuously, understands how work gets done across apps and systems, and takes action independently. Omar Shahine, corporate vice president at Microsoft, described it that way in the Build announcement.
Scout connects to Teams, Outlook, OneDrive, and SharePoint. It pulls context from chat, email, calendar, and contacts. The primary access point is Teams, but it also reaches into the user's browser and connects to external apps via Model Context Protocol (MCP). It works across cloud, desktop, and the web.
The identity model matters for builders. Scout operates with its own governed Entra identity. That means it is not acting as an anonymous service process. It has a distinct, auditable principal in the directory. For teams building compliance-sensitive workflows, that is a meaningful design choice to note.
Scout is built on OpenClaw, the agent framework Microsoft has been developing. Shahine leads a team specifically focused on bringing OpenClaw-based personal assistants to Microsoft 365 apps, a role he recently announced. Scout represents the first public output from that effort.
The initial task focus is mundane but high-frequency. Scout can coordinate and schedule meetings with colleagues, and block time on a calendar based on upcoming work commitments. These are low-stakes, high-volume tasks, exactly the kind where always-on autonomous execution makes sense before expanding scope.
There are no pricing details or API specifics in the announcement yet. What is clear is the integration surface: MCP for external app connectivity, Entra for identity, and the core M365 graph of Teams, Outlook, OneDrive, and SharePoint for context.
If you are building agents or workflows on top of Microsoft 365 today, the concrete next step is to review your MCP server implementation. Scout's ability to reach external apps through MCP means a well-formed MCP endpoint is your path to interoperability with this agent class. Check whether your app exposes the right context and actions for an autopilot agent to call without human intervention, and verify your Entra permissions model is ready for agent identities, not just user identities.