What is Microsoft Scout and how can you use it?

Microsoft's first always-on "Autopilot" agent. It runs on the exact open harness operators here already build with, OpenCLAW. The enterprise, IT-governed cousin of Google Spark.

For a year I have been telling CEOs the same thing: the leverage is not in the model, it is in the harness, and the harness most operators graduate to is the open-source one called OpenCLAW. I run two companies on it. On June 2, at Build 2026, Microsoft stood on stage and shipped its biggest agent bet of the year, Microsoft Scout, and told the room it is powered by OpenCLAW open-source technology. The harness this site has been telling you to learn is now the engine under a Microsoft flagship. That is the headline, and it is worth understanding even if you never turn Scout on.

What it is (in plain English)

Microsoft Scout is an always-on personal agent for work. Satya Nadella introduced it as the first of a new product category Microsoft calls "Autopilots": agents that work autonomously, in the background, with their own identity, and take action on your behalf without you prompting them each time.

The normal Copilot is reactive. You ask, it answers, it waits for the next ask. Scout is the opposite. It runs continuously, watches your work across Microsoft 365, and acts. It joins your Teams group chats, follows your Outlook email threads, reads your calendar, contacts, OneDrive, and SharePoint, and a desktop app extends its reach to your browser and local files. It reaches outside tools the same way an open harness does, through MCP servers, the open standard for plugging an agent into your real systems.

A context layer Microsoft calls Work IQ is what makes it proactive. Work IQ learns your priorities and what comes next, so Scout can coordinate and schedule meetings across time zones, flag the meetings that actually matter, generate your prep materials, spot a deliverable coming and block time on your calendar for it, and surface a stalled decision before it becomes a fire. Omar Shahine, the Corporate VP who leads Scout, put it plainly: they built it to learn how always-on agents show up in real work, and they are "seeing it take on coordination, surface risks earlier, and keep work moving without constant prompting."

One thing Microsoft did not say: which model runs underneath. Scout is the harness and the governance; the model behind it went unnamed at launch.

The part that matters for this audience

Strip the branding and Scout is the model-plus-harness pattern this site teaches, wearing a Microsoft uniform. Microsoft did not invent a new agent stack. It took the open harness, OpenCLAW, and wrapped it in enterprise identity and policy.

The people closest to it say so out loud. Peter Steinberger, who created OpenCLAW, called it "a privilege to work with Microsoft to bring claws to enterprises" and spent the week shipping observability and verifiable workspaces into the open project alongside Microsoft's team. One operator on X summed up the whole thing better than any analyst: "Peter built OpenCLAW. Omar put a Scout uniform on it and shipped it at Microsoft. And I've been running it as my own digital chief of staff for months."

That last clause is the point. The thing Microsoft just made a flagship is the thing a determined operator can already run, free, today. Microsoft even brought OpenCLAW natively into Windows at the same event, running it inside new secure containers with a setup companion. When a trillion-dollar company builds its agent future on an open harness and ships that harness into its operating system, the "is this real" question is settled. The harness is the platform now.

What changed, and what didn't

The reactions tell the real story, and they split clean.

The optimists read it as a posture shift. "Microsoft just went from Copilot to Autopilot" was the line going around, and it is accurate. For three years the Microsoft answer to AI was a chat box that waited for a prompt. Scout is the first time the default is an agent that acts without one.

The skeptics went straight to the obvious place: a thing that is always on, with standing access to your inbox, files, and calendar, "based on your corporate policy," is also a large new attack surface. A widely-followed security account called it "the best news for threat actors in a long time." The Register noted, fairly, that OpenCLAW does not yet have a long enterprise security track record. The blunt enterprise read came from a reply that will sound familiar to anyone who has sat in a vendor review: the first thing a big regulated org asks about a new always-on agent is "how do we turn it off." Both halves are true. Hold them together.

How to get it (and why most CEOs can't yet)

Here is where Scout is the opposite of Google Spark. Spark is a consumer toggle: pay for Google AI Ultra, flip a switch in the Gemini app, done. Scout is locked behind an enterprise gauntlet, and for most companies it is not turn-on-this-week.

What it actually takes right now:

• A GitHub Copilot license to download and install the experience at all.
• Enrollment in Frontier, Microsoft's experimental-release program. Scout is shipping as a private preview to a select group, not general availability.
• Intune policy configuration and an opt-in attestation, which means your IT admin has to deliberately turn it on for your tenant. There is an admin-access setup process on Microsoft Learn; it is not a one-click affair.
• Patience on governance. Microsoft has said full tenant-level controls are still in development and expected later in 2026.

The security model, to Microsoft's credit, is serious. Every Scout agent runs under its own governed Entra identity (a real, named identity in your company directory, not an anonymous shared service account), its credentials are scoped to the task and redacted from logs, it enforces your existing Microsoft Purview data-protection policies, and sensitive actions still require a human to approve. That is genuinely more enterprise-grade than a consumer toggle. It is also why you cannot just switch it on over coffee.

Scout vs. Google Spark

A week before Scout, Google shipped Spark, its own always-on personal agent. One French analyst captured the moment: Scout is "the equivalent of OpenCLAW, or of Spark announced by Google last week." Two giants, same week, same idea, opposite on-ramps.

• Spark is consumer-first. It lives in your personal Gmail and Calendar, turns on with a Google AI Ultra subscription, and is built for the individual who wants an agent today.
• Scout is enterprise-first. It lives in your company's Microsoft 365 tenant, turns on through IT, and is built for the org that wants agents under directory identity and data-loss policy.
• Both are managed wrappers around an open harness. Spark runs on Google's stack; Scout runs on OpenCLAW. Neither is a harness you own; both are a harness someone else operates for you.

If your company lives in Microsoft 365 and your IT team is forward-leaning, Scout is the one to watch. If you live in Google Workspace, Spark is the easier yes. If you want leverage that does not depend on either vendor's preview schedule, read on.

Scout vs. the harness you'd run yourself

Because Scout literally runs on OpenCLAW, the build-versus-buy question is unusually clean here. You are not choosing between Microsoft's secret sauce and a hobbyist alternative. You are choosing between the same open engine, governed by Microsoft and gated behind a preview, or the same open engine, owned and run by you, available today. The honest comparison:

• Standing access. Scout needs continuous, policy-bounded access to your whole M365 tenant to do its job. That is the "impressive and terrifying" tradeoff in three words. With your own harness you decide exactly which inbox, which folder, which CRM the agent touches, and you can keep it air-gapped from everything else.
• Control and portability. OpenCLAW's creator says it best: "The idea of OpenCLAW is always that it should be yours." Run it yourself and you own every memory file, every skill, every routine. Switch models next quarter without rebuilding. With Scout, the governance, the rollout pace, and the off switch belong to Microsoft and your IT department.
• Availability. This is the unusual part. The managed version is the one you have to wait for. The open version you can install this weekend.

These are not mutually exclusive. Plenty of operators will happily let Scout coordinate their corporate Teams and Outlook once it clears IT, while their own OpenCLAW agent runs the parts of the business they want to keep entirely in their own hands.

Where you'll see it

• In the Build 2026 coverage, as the centerpiece of Microsoft's shift from Copilot to "Autopilots," sitting next to its new in-house models and its Windows-native OpenCLAW push.
• In your IT team's roadmap, as a private preview your admins are evaluating before any wider rollout.
• In the agent conversation generally, as the enterprise face of the model-plus-harness shift, paired with Google Spark on the consumer side and Claude Code plus OpenCLAW on the operator side.
• In the open-source numbers. OpenCLAW's own maintainer says downloads spiked into the millions per week around launch. Microsoft picking it up is both a cause and a symptom.

What to do next

The lesson of Scout is not "wait for Microsoft." It is that the open harness is now provably the center of gravity, and you do not need a Frontier invite to run it. Start where every workflow here begins: Granola to markdown, the pipeline your agent reads from. Then read why CEOs should use Claude Code in the terminal for the strategic case, and What is OpenCLAW for the harness Microsoft just bet on. The operator's manual for installing it yourself is The Complete Guide to OpenCLAW for CEOs. Scout is the proof. The harness you control is the move.