Microsoft had the engineers to build its own agent runtime. At Build 2026, it chose not to — shipping Scout, its first always-on work agent, on top of OpenClaw. A weekend project from an Austrian developer in late 2025 is now the foundation under a product from a company worth more than $3 trillion.
That's the through-line in a sharp analysis by Janakiram MSV at The New Stack, published today: Microsoft just made the agent runtime free — and kept everything around it.
The Android Parallel
The analogy MSV draws is Android. Google released the Android Open Source Project as a free common base, and every dollar followed the layers above it: managed identity, the device-management console, Play services, and eventually the silicon. Android made handset makers ubiquitous without ever making the base itself a business.
OpenClaw is on the same trajectory. Microsoft took the runtime, wrapped it in enterprise governance, and left the runtime open. "OpenClaw now runs natively on Windows inside Microsoft Execution Containers," MSV writes, "the kernel-level sandbox Microsoft built for agents." Nvidia is bringing its OpenShell runtime to the same containment layer. Nous Research says its Hermes Agent will integrate both. Five months after launch, OpenClaw is the common base that Microsoft, Nvidia, and a row of agent startups are simultaneously building on.
What Microsoft Actually Shipped
Scout connects to Microsoft 365 data, runs continuously in the background, and can reach a user's browser and external apps through the Model Context Protocol. The OpenClaw runtime executes the agent loop. Everything Microsoft charged for sits above it:
Identity. Every Scout agent gets its own governed Entra identity — not a shared service account. Each action traces back to a named actor in the corporate directory. This directly addresses what the industry has been calling the "agentic identity crisis": autonomous agents acting on borrowed or anonymous credentials that nobody can audit.
Governance and policy. Scout ships with a policy-conformance system that continuously checks whether the agent is operating within set guidelines, and each check leaves an audit trail. Microsoft is contributing that conformance work upstream to OpenClaw so organizations running the open project can validate their own deployments.
Agent 365. Microsoft's control plane discovers and manages local agents on a managed device — starting with OpenClaw, but extending to GitHub Copilot CLI and Claude Code. Agents Microsoft didn't build surface in its console.
Work IQ. The proprietary grounding layer that lets Scout learn who you work with, which projects are live, and when a decision has stalled — from signals already inside Microsoft 365. The runtime executes the loop; Work IQ makes the loop useful inside a specific company.
Why This Matters for OpenClaw Users
For the self-hosted OpenClaw community, the headline is that Microsoft is now contributing enterprise policy controls back to the OpenClaw project itself. That's governance tooling being written by a $3T company and landing in the same open-source repo you can npm install today.
The pattern MSV identifies — free runtime, paid stack — mirrors how the broader infrastructure industry evolved: Linux, Kubernetes, Android all free; the services, consoles, and compliance layers above them worth hundreds of billions. OpenClaw is tracking the same arc, except on a timeline measured in months instead of years.
The more interesting question is what OpenClaw's own governance looks like when it becomes the substrate for enterprise agents at scale. Microsoft is betting the answer to that question is its own control plane. The open-source community has its own ideas, and projects like Clawcenter and BetterClaw are already building open alternatives.
For now: the OpenClaw runtime is the new Android base. The battle for the control plane is just getting started.
Source: The New Stack, Janakiram MSV, June 7, 2026.