Microsoft Scout: First Autopilot agent ships on OpenClaw with enterprise identity, policy conformance at Build 2026

Microsoft announced Scout at Build 2026 (June 2), the first of a new category called "Autopilots"—always-on agents that work continuously in the background with their own governed Entra identity, not waiting to be prompted. Scout is built directly on OpenClaw, the open-source agent framework that went viral in early 2026 (180,000 GitHub stars in three months) and was acquired by OpenAI in February. Instead of competing, Microsoft wrapped OpenClaw with enterprise-grade security and policy controls, then committed to contributing those controls back upstream to OpenClaw. Scout integrates across Microsoft 365 apps (Teams, Outlook, OneDrive, SharePoint), accessing chats, email, calendar, contacts, and can reach external apps and user browsers via Model Context Protocol.

Scout operates under a uniquely named Entra identity (e.g., "Sebastian") rather than a shared service account, so every action is attributable to a known actor in the corporate directory. Each Scout instance has scoped credentials, managed with end-to-end protection, and a built-in policy conformance engine continuously validates actions against company guidelines with immutable audit logs. The agent handles coordination work: scheduling meetings across time zones, flagging stalled decisions, blocking calendar time before deadline conflicts. About 3,000 Microsoft employees are already using Autopilots internally. Scout is available via the Copilot Frontier program (private preview) with no public pricing announced yet, though token-based billing on GitHub Copilot (effective June 1) signals consumption pricing may apply.

For architects evaluating always-on agents in production, Scout's architecture maps a new stack: open base (OpenClaw), enterprise control plane (identity, policy, audit), and enforced containment (Windows Execution Containers). This inverts the pitch from "we built a new agent" to "we wrapped an open-source runtime with governance," reducing Microsoft's surface area for vendor lock-in while maintaining control. The token-consumption billing matters: 24/7 background agents consume tokens continuously, not on-demand like Copilot Chat. Organizations need to model annual token spend differently and watch how Microsoft bundles pricing—whether Scout is bundled with Copilot or metered separately will determine cost per employee.