Autopilots are here! This was the Build 2026 keynote message from Satya Nadella last week:

So, Microsoft is no longer The Copilot Company that Satya envisioned a couple of years ago. Which makes sense, given how the Copilot brand has not become quite as valuable as the company would have wanted to. While it’s present in most organizations, thanks to the massive distribution power of Microsoft, we’ve seen reports of how when given a choice, users actively pick something other than Copilot.

It’s not yet clear at this point whether Autopilots become a proper brand or just remain a concept used in marketing. In any case, it feels like a missed opportunity to pick a new AI brand that would have carried more positive emotions for many of today’s tech workers that grew up in the 90s (credit to Tim Mayo for the idea):

The flagship Autopilot of this new category of AI agents presented at Build was Microsoft Scout. The subscribers of this newsletter may know it by its former name, ClawPilot, that has been used in context of the MS internal version of Scout.

In this week’s issue, I will take a deeper look at what the official story with Microsoft Scout is and how it differs from the observable reality. The Frontier preview announcement doesn’t quite tell the full story but that’s okay — more material for me to cover in Perspectives, then! But first, let’s zoom out a bit and put all these recent AI pilots into perspective.

Keeping up with Microsoft’s AI agent products is the kind of a task where I personally definitely welcome help from AI tools. Even if I have a good hunch of what I should be looking for and where, it would simply take too much time to manually open the tens or even hundreds of web pages that provide relevant bits of information. So, I once again requested Claude to produce a single HTML page that illustrates the big picture of Autopilots:

Let’s go through the points on this AI treasure map and see how they align with the Autopilot story.

Copilot Studio agents. Most of us know this story already. In Spring 2025, Microsoft published the first and so far only numbers on how much Copilot Studio agents were being used by their customers (equaling roughly 0.04% of Microsoft total revenue). Since then, autonomy has been introduced by adding essentially Power Automate style triggers into Copilot Studio agents. In the very latest twist, such logic is now moved away from agents and into Copilot Studio workflows.

Project Opal. Introduced at Ignite 2025, this was supposed to be “a new AI-powered capability that executes task-based work inside a secure, observable environment you control”. After Microsoft revamped the M365 Copilot app navigation, rediscovering the Opal (Frontier) agent has been challenging. This made me question whether the project was still alive, yet I did manage to re-provision the related Opal Windows 365 cloud PC that had been deleted due to inactivity. Nothing much has been announced after November 2025 around this, though.

Agent 365. I started covering this product a few months before the Ignite 2025 announcement and I’ve been following it closely ever since. What was initially marketed as a complete tools package for autonomous AI teammates was since then reduced to a mere governance layer for agents in your tenant. I blame the commercial rush for getting M365 E7 Frontier Worker Suite out the door before FY26 end for this. Here’s a “tribute” I made to the $99 product rollout strategy of Microsoft:

Copilot Tasks. If you weren’t paying close attention, you might think this was just a regular M365 Copilot feature, a bit like the mysterious scheduled prompts I’ve explored earlier. But it’s nothing like that. Tasks is a consumer Copilot capability that was launched behind a waitlist and has so far not been made available outside the US. There’s very little info or details about this shared online as a result. Recent complaints from paying private Copilot users suggest the capacity for Tasks is not properly reallocated and there’s no news on when the preview period might end.

Copilot Cowork. Anthropic’s victory lap. After Microsoft’s own efforts to use OpenAI’s models to allow Office tools to generate useful documents had failed repeatedly, the solution came from partnering with another AI lab. Licensing the Cowork harness familiar from Claude Desktop and making it run in the cloud as Copilot Cowork has shown itself to be the most applauded tool in M365 Copilot. All of this despite it being built on Linux VMs and leveraging tools like LibreOffice to generate and validate MS Office docs. But it’s the end result that counts. During the Frontier preview phase, there aren’t even any Copilot Credit costs for running the tool — although I certainly wouldn’t bet on it being the commercial model going forward…

Microsoft Scout. Taking OpenClaw, a thing Satya Nadella once compared to a virus, and deploying it inside your Microsoft 365 tenant. This is now positioned as the new era of truly autonomous AI agents and the whole Autopilot story basically relies on Microsoft getting it right. There’s certainly a lot of synergy in how the enterprise giant could potentially tame the wild beast of OpenClaw and make 2025 2026 the year of AI agents for real.

Before anyone even had a chance to try it, there was already controversy online about the new Scout product. 404 Media had received the internal strategy document that outlined how Microsoft wanted to “make people addicted” to the tool before rolling out additional functionality. While it is hardly a secret that software vendors would want their customers to crave for their products, this kind of language easily raises concerns about the AI addiction phenomenon that has been getting more and more coverage in the media.

For Microsoft in particular, this image does not align well with the humanist superintelligence message recently promoted by their AI CEO, Mustafa Suleyman. Perhaps this was one reason why Satya Nadella’s reaction to the addiction headlines was so strong: “Not sure what this document is or who is writing and leaking this nonsense! They may want to go work elsewhere.” This, in turn, resulted in an even better headline for the follow-up article on 404 Media:

“The guy” is of course Omar Shahine. After many long-time Microsoft senior leaders recently decided to leave the company, this has given room for new rising stars. Alongside the certified superstar Charles Lamanna, the former Corporate Vice President of Word, Omar, is certainly one to watch for. Sure, he’s been at MSFT since 1999 already, but I feel there are big things ahead for his new team that’s bringing OpenClaw to M365.

What started as Omar’s personal project of running a local OpenClaw deployment on a MacBook in his home office, then evolved into a vibe-coded home automation integration with OpenClaw, has turned into a big bet for Microsoft. Back when Project Lobster was originally published, I found myself wondering: “hmm, is this fully aligned with Microsoft’s internal information security policy for their product leaders?” Well, obviously it was perfectly fine to wire up the physical sensors of your home office with an autonomous LLM agent and let it observe any meetings the CVP was having.

Anyway, let’s circle back to that addiction part. We know Satya was also an early follower of the OpenClaw project, which could be justified by the business potential and technological novelty. At some point, though, things may get too intimate between tech geeks and AI agents. Wikipedia says: “AI anthropomorphism is the attribution of human-like feelings, mental states, and behavioral characteristics to artificial intelligence systems.” Now, if there was a picture in that article, it might as well be something like what Omar posted:

You may not see your Copilot as a lovable person when opening M365 tools. Yet the design of Microsoft Scout and how it is marketed is definitely maximizing the chances of humans mistaking AI for an actual person. It goes well beyond giving Copilot a face and calling it “your AI companion”. Rather than being an app you need to proactively launch, Scout is designed to be a thing that reaches out to you when there are signals and decisions requiring your attention. It will live in the same chats as messages from your real colleagues and friends. In the increasingly digital world that surrounds us, forgetting that Sebastian isn’t real is becoming all too easy.

Finally, let’s look at what is real and available today. As is often the case, what the Microsoft marketing blog posts say and what the docs actually reveal are two different things. Rarely has it been as obvious as it is with Microsoft Scout, though. This is what the marketing team would like you to think Scout is:

Notice how even the URL in the video’s mock UI points to the consumer version of Copilot, not the M365 work version? Who cares, we are reimagining autopilots here! On the bright side (for Microsoft), most people watching the video will not even have the technical ability to try the Frontier preview, so they won’t know it’s just aspirational animations rather than a real product at this point.

So, what are the prerequisites? The fun part is, not even Microsoft seems to agree on them. The docs page for getting started with Scout has gone through multiple revisions over the first few days. The requirements for Microsoft 365 Copilot license have gone on, off, and then on again. Similarly, the GitHub Copilot Business or Enterprise license requirement was added there after the launch.

Upon testing it with my demo user account (I ain’t gonna let this thing access my real customer data!), there didn’t seem to be any license enforcement for the M365 Copilot license. Activation on a Windows 365 machine in my tenant went through just fine without it. And why wouldn’t it, because this thing doesn’t run on Copilot Credits. Instead, it burns GitHub Copilot AI Credits like there’s no tomorrow.🔥