Last updated: 2026-09-30

Microsoft Scout — the enterprise agent powered by OpenClaw

On June 2, 2026 Microsoft introduced Scout, the first of a category it calls Autopilots: always-on agents that work in the background with their own identity. Microsoft says Scout is "powered by OpenClaw open-source technology". Here is what the announcement actually says, and what it means if you run OpenClaw yourself.

What Microsoft announced

  • What it is: an agent that stays active, learns how you work across your apps, and acts without being prompted each time.
  • Built on OpenClaw: "powered by OpenClaw open-source technology". Microsoft also says it contributes "policy conformance directly upstream to OpenClaw", so organisations running open-source OpenClaw can validate security and compliance configuration.
  • Where it works: Teams, Outlook, OneDrive and SharePoint, across cloud, desktop and web. The desktop app extends it to your browser, local resources and MCP servers.
  • Identity and security: each agent runs under its own governed Entra identity, with credentials scoped to the task and redacted from logs, and data-protection policies and sensitivity labels enforced before anything is sent or written.
  • Availability: an experimental release through private preview and the Frontier program. It needs Frontier enrollment, Intune policy configuration and an opt-in attestation; users with a GitHub Copilot licence can then download and install it.

Microsoft's post doesn't name the model Scout uses. An earlier version of this page claimed GPT-4o and Azure OpenAI models, which we couldn't source, so it's gone.

Update, 2026-09-25: now called Autopilot

OpenClaw's own blog calls the product Microsoft Autopilot (formerly Microsoft Scout) and says Microsoft is "building Autopilot on OpenClaw" with the OpenClaw Foundation. It credits Microsoft contributors with a Policy plugin (describe requirements, compare them with the actual configuration and keep a record of the result), a native Windows companion with guided setup, WinUI chat, inline command approvals and sandbox integration, scheduler and database-recovery fixes, and smaller additions such as Teams message reactions, secret redaction in approval prompts, Azure OpenAI provider support and iMessage approvals. That is OpenClaw's account of the contributions; we haven't checked each against the release notes.

What it changes for self-hosted OpenClaw

  • Nothing you have to do. Scout is Microsoft's product running under Microsoft's controls. Your own Gateway, workspace and skills are unaffected.
  • Upstream security work. The policy-conformance contributions Microsoft describes land in the open-source project, which is worth watching in OpenClaw's release notes.
  • Skills and config portability between Scout and community OpenClaw hasn't been documented by Microsoft or OpenClaw. Don't assume it.

If you want Scout-style "own identity, scoped credentials" discipline in your own install, start with OpenClaw's hardened baseline: loopback bind, token auth, pairing, and restricted tools.

Other coverage: InfoQ, The New Stack, TechCrunch. ← Back to OpenClaw FAQ

Official sources

Checked against the OpenClaw docs, release 2026.9.6. If anything here disagrees with these pages, trust the vendor docs.