Microsoft Scout is OpenClaw for Microsoft 365

Microsoft spent the early part of 2026 warning people about OpenClaw. This week it shipped a product built on it. At the Build developer conference in San Francisco on June 2, the company introduced Scout, an always-on AI assistant that runs on the open-source OpenClaw framework and connects into Microsoft 365. If you've been self-hosting OpenClaw since last winter, that turn is worth a quiet smile.

Here's the short version. OpenClaw went from a project that CEO Satya Nadella reportedly compared to a "virus" to the foundation of a flagship Build announcement, all inside about four months. The same capability that made the open-source agent spread so fast is now something Microsoft wants in front of its 1.4 billion Windows users.

What Microsoft Scout is

Scout is what Microsoft calls an "autopilot," an agent that runs in the background and acts on your behalf. Computerworld's write-up of the launch quotes Microsoft VP Omar Shahine describing autopilots that "take action without needing to be prompted each time," which is a tidy summary of the whole pitch. You give it ongoing feedback, it stores patterns as memories and skills, and it gets more useful the longer you use it.

You name your own instance, too. In the demo that TechCrunch saw at Build, the assistant was called Sebastian. Small detail, but it tells you how personal Microsoft wants this to feel.

How Scout works inside Microsoft 365

Scout lives in the cloud and reaches across your desktop and browser, so it can get into your inbox and calendar and reach Model Context Protocol servers when a skill needs them. You interact with it mostly through Teams plus a desktop app. It ships with a few prepackaged skills, calendar management and meeting-agenda drafting being the obvious starters, though Shahine has said the real value will come from the skills people build for themselves. That part should sound familiar to anyone who has written custom OpenClaw skills already.

Scout vs Microsoft 365 Copilot

Copilot answers questions and helps you write. Scout does work while you're not looking. That's the line Microsoft is drawing. Each Scout agent gets its own governed Microsoft Entra identity with scoped credentials, and admins control it through Intune policy plus an opt-in attestation. Access runs through Microsoft's Frontier early-adopter program and needs a GitHub Copilot license, so for now it sits behind the paid Copilot stack (the large-business tier runs around $30 per user a month). This isn't a free consumer toy yet.

Why Microsoft chose OpenClaw

OpenClaw only went public in November 2025, first under the name Clawdbot. If you want the backstory, we covered its days as Clawdbot and Moltbot and the trademark mess that followed. The project's creator, Peter Steinberger, was hired by OpenAI in February, which slowed the open-source momentum but did nothing to dampen the ideas.

And the ideas are the point: Persistent memory, multi-channel messaging, user-written skills, agents that route to other agents. We wrote a short article about what OpenClaw is and how it works back in January, and almost every concept in there shows up in Scout under a Microsoft label. Internally, Microsoft ran Scout as "ClawPilot" inside a program codenamed Project Lobster. According to GeekWire, daily testers inside the company jumped from about 100 to more than 3,000 in a single week this spring. That kind of internal pull is usually a stronger signal than any keynote slide.

Microsoft's own advice on running OpenClaw safely

Now for the part I think matters most. Back in February, Microsoft's security team published guidance on running OpenClaw safely and the wording was blunt: treat it as untrusted code execution with persistent credentials. The runtime can read untrusted text, pull down skills and run them, all using whatever permissions you hand it. So the recommendation was to keep it off your personal or work machine and put it in a fully isolated environment instead, a dedicated VM (virtual machine) or a separate box, with non-privileged credentials and only non-sensitive data nearby.

Read that again and you've basically described a VPS. An agent that executes arbitrary code shouldn't sit next to your tax files and your saved passwords, which is exactly why a lot of people give it its own server. That's the setup our OpenClaw VPS hosting is built for: an isolated AMD EPYC instance with NVMe storage, instant deployment and a 1-click OpenClaw template, on hardware we own and support in-house any time you need us. The agent lives away from your daily driver, and if an experiment goes sideways you rebuild the server and move on. There's a 30-day refund window if it turns out not to be your thing.

If you do self-host, read the fundamentals first. Our notes on how to host OpenClaw securely on a VPS and the deeper OpenClaw security best practices cover the same ground Microsoft's researchers worry about, scoped tokens and isolation and a clean rebuild path. Microsoft even publishes its own OpenClaw build on GitHub if you want to see how the company packages it.

Self-hosting OpenClaw without a Copilot license

So do you need Scout? If you're deep inside Microsoft 365 and want admin-grade governance with audit trails, it's a genuinely interesting option, and the policy conformance checks it runs are a smart answer to the inbox-gone-rogue stories from earlier this year. But it's gated behind Copilot licensing and a private preview, and you don't control the runtime.

The open-source version asks more of you and gives you more back. You pick the model, you own the data, you decide what the agent can touch. Running several agents at once, the same "autopilot" idea Microsoft is selling, is something you can already do yourself, and our guide to running multiple OpenClaw agents walks through it. When you're ready to go from a single bot to a full setup, the complete OpenClaw guide is the one to bookmark.

The bigger takeaway is simple. A trillion-dollar company just validated the exact tool thousands of developers have been running on their own servers for months. The project isn't going anywhere, and it now has Microsoft branding as proof the approach works.

So where will you run yours?