Connect with us

NEWS

Microsoft Build 2026 Unbundled Local AI From Copilot+ PCs

Microsoft Build 2026 put Autopilots and Aion models on Windows 11, while Scout stays Frontier and Solara runs on Android.

Published

on

Microsoft Build 2026 spent June 2 and 3 recasting Windows 11 as a host for local agents, not as a new operating system. Satya Nadella opened at Fort Mason in San Francisco with a phrase he had already posted the night before: unmetered intelligence on every desk and in every home.

The session list had already pointed at agentic AI sessions in the catalog, GitHub Copilot, Azure, and on-device Windows models. What the two days actually shipped was a control plane. Agents got identities, sandboxes, and local models that no longer stop at Copilot+ NPUs, while the Autopilot that led the keynote stayed behind a Frontier gate.

Microsoft IQ and Seven MAI Models Landed on Day One

Kyle Daigle, GitHub’s chief operating officer and Microsoft’s developer marketing chief, framed the morning around three ideas: intelligence that belongs to the customer, a stack that runs from silicon to cloud, and agents that move out of demos into science and production. The glue is context.

Microsoft IQ generally available across Copilot, Microsoft Foundry, and Copilot Studio on June 2. Work IQ reads how work actually happens across Microsoft 365. Fabric IQ puts a shared meaning layer on structured business data. Foundry IQ plans retrieval across both of those stores and the live web. Web IQ, new that morning, is a model-agnostic, MCP-native search stack that Microsoft said returns relevant passages at nearly 2.5x the speed of the next best alternative. Work IQ APIs followed on June 16.

The Microsoft AI Superintelligence team also put seven in-house models on the table, led by MAI-Thinking-1, the group’s first reasoning model, trained from scratch with no distillation on licensed data.

THE SEVEN MAI MODELS

Model Job Where it showed up
MAI-Thinking-1 35 billion active parameters, 256K context, multi-step reasoning and code Private preview in Foundry
MAI-Image-2.5 and Flash Text-to-image and image-to-image; Arena ranks 3 and 2, ahead of Nano Banana 2 on the second test Live in PowerPoint, rolling out in OneDrive, landing in Foundry
MAI-Transcribe-1.5 Speech to text across 43 languages, streaming still coming MAI family release
MAI-Voice-2 and Flash Speech in more than 15 extra languages, new voices MAI family release
MAI-Code-1 Coding model tuned for GitHub Copilot and VS Code on day one

Daigle wrote that independent raters prefer MAI-Thinking-1 to Sonnet 4.6 in a blind test, and that it matches Opus 4.6 on SWE Bench Pro. MAI models will also sit on Fireworks AI, Baseten, and Open Router, and Fireworks AI itself went live on Foundry the same day. That is Microsoft building its own model stack beside the partners it still hosts, so a tenant can pick a model without leaving Azure’s residency and audit trail.

Local AI No Longer Needs a Copilot+ PC

Pavan Davuluri, executive vice president for Windows and Devices, spent his Build post on a quieter change that will hit more PCs than any Autopilot demo. Windows AI features that used to demand a Copilot+ NPU now run on a much wider slice of Windows 11 hardware.

Speech-to-text recognition is available on NPUs and CPUs. The inbox small language model expands to capable discrete GPUs for local text work. Video Super Resolution runs on CPUs. Davuluri’s line was blunt: developers can ship local AI without a cloud round trip, and they can target the install base they already have.

WHAT WINDOWS OPENED ON JUNE 2

  • Aion 1.0 Instruct: A smaller on-device model for summary, rewrite, intent, and accessibility, first through Edge Insider channels, with developers invited to build on it from June 22.
  • Aion 1.0 Plan: A 14 billion parameter reasoning and tool-calling model with a 32K context window, meant for fully local agents, due in the months after the show.
  • MXC SDK: Microsoft Execution Containers let an agent declare which files and networks it may touch, with those limits enforced at runtime, in early preview.
  • OpenClaw on Windows: The Windows node and gateway run inside MXC, with NVIDIA bringing OpenShell to the same containment layer.

Nadella told developers they now have the full scope of GPUs when they write to Windows ML, and that every developer can build for onboard AI and have it run across the install base. Copilot+ PCs still have the NPU path. They are no longer the gate.

The hardware that made the phrase “unmetered” land was not a consumer laptop refresh. The Surface RTX Spark Dev Box, powered by NVIDIA RTX Spark silicon, is rated at up to 1 petaflop of AI compute with 128 GB of unified memory shared by CPU and GPU. Davuluri also introduced DGX Station for Windows, a deskside box on NVIDIA’s GB300 Grace Blackwell Ultra Superchip, aimed at local frontier models up to 1 trillion parameters and due in Q4 2026. NVIDIA’s own Build note put RTX Spark laptops and DGX Station on the same Windows stack as Foundry-hosted agents and GitHub Copilot’s OpenShell runtime.

Expanding Windows AI APIs across CPU and GPU is how that silicon reaches code. Coreutils for Windows, a native Linux-like command set, went generally available. Windows Developer Configurations can stand up VS Code, GitHub Copilot, WSL, and PowerShell 7 with one WinGet command. Those are boring tools until an agent needs a shell that does not jump through WSL for every file move.

Scout Runs on OpenClaw With Its Own Entra ID

The product with a name people will remember is Microsoft Scout, and Microsoft did not write the runtime under it. Scout is built on OpenClaw, the open-source agent project from Peter Steinberger, who appeared at the show. Omar Shahine, corporate vice president of Microsoft Scout, put the category definition in the Microsoft 365 blog.

Autopilots are always-on agents that work autonomously, with their own identity, and act on your behalf.

Omar Shahine, Corporate Vice President of Microsoft Scout, Microsoft 365 Blog

Scout sits in Teams, Outlook, OneDrive, and SharePoint, and a desktop app reaches the browser, local files, and MCP servers. It is supposed to prep meetings, park focus time on the calendar, and flag stalled decisions without a fresh prompt each time. Work IQ is the memory. The part that matters to a tenant admin is the identity model. Each agent gets its own governed Entra ID, not a shared service account. Credentials are scoped to the task and redacted from logs. Purview labels and data-loss rules apply before anything is sent or written. Sensitive steps can require a human sign-off.

That is a lot of control for a preview. Access still needs Frontier enrollment, Intune policy, an opt-in attestation, and a GitHub Copilot license. Microsoft staff had been living with an early desktop build. Frontier customers were invited next. Shahine said Microsoft is contributing policy conformance upstream to OpenClaw so organizations running the open project can prove their own setups.

Nadella’s own recap of the Windows half of the keynote sat on X the same afternoon.

https://x.com/satyanadella/status/2061896505481658767

He also told the room that Chat, Cowork, and Code would come together in one Copilot Super App in summer. The app was not demoed. Agent 365 for local agents extends Entra, Defender, and Purview over agents no matter which framework built them. ASSERT and the Agent Control Specification are the open-source half of that trust stack. Codename MDASH fields 100+ agents to hunt exploitable bugs and push fixes into the Defender portal.

The louder objection after the keynote was not that Scout cannot book a room. It was that an always-on agent with a mailbox, a calendar, and a browser is a security product first. Microsoft spent as much of Build on those identities and sandboxes as it did on the meeting-prep reel, because an Autopilot that can act is only shippable if someone can revoke it.

What Microsoft Foundry Shipped for Production Agents

Microsoft Foundry is where those agents are supposed to live once they leave a laptop demo. Nick Brady, a senior program manager for developer experience, recapped a platform that is no longer just a model catalog: runtime, tools, memory, grounding, observability, and controls, with a mix of GA and preview dates attached.

FOUNDRY STATUS ON JUNE 2

Piece Status called at Build Use
Foundry Toolkit for VS Code Generally available Templates, local traces, deploy to Foundry Agent Service
Agent Framework harness, Copilot SDK and Claude Agent SDK, Magentic-One patterns Stable Orchestration building blocks
Hosted agents General availability targeted for early July 2026 Sandboxed sessions, state, filesystem, framework choice
Toolboxes, memory, routines Public preview One governed tool endpoint; procedural, user, and session memory; scheduled runs
Voice Live prompt agents Generally available Real-time voice
Teams and Microsoft 365 Copilot publishing Planned GA in June 2026 Put a Foundry agent where people already work

Frontier Tuning, in private preview, applies reinforcement learning inside a customer’s compliance boundary so an agent can learn how that business actually runs. Windows 365 for Agents, a pool of managed Cloud PCs for computer-using agents, went generally available at the show. Agent 365’s native hook into MXC was slated for preview in July, so a local OpenClaw node and a cloud agent show up in the same admin plane.

The GitHub Copilot app, in preview, is the desktop face of the same idea for developers. Cassidy Williams, senior director of developer advocacy at GitHub, showed parallel agent sessions on separate git worktrees so two jobs do not overwrite each other. Copilot in Visual Studio is moving the same way, from chat and completions toward agents that join the work instead of sitting beside it.

Project Solara Puts Agents on Android Gadgets

The strangest Build beat is the one that is not Windows. Steven Bathiche, a Microsoft technical fellow, introduced Project Solara as a chip-to-cloud platform for devices that run agents instead of apps. The OS layer is a customized Android stack, not a Windows SKU. The shell is an Agent Shell with just-in-time UI, so the interface is supposed to generate itself for a badge, a desk slab, or whatever form factor a partner ships.

Microsoft showed two reference designs and said it does not plan to sell them itself.

THE TWO SOLARA CONCEPTS

  • Desk hub: A display that signs a user in with a face, talks to agents by voice, and can attach a monitor to become a full Windows session running in the cloud.
  • Wearable badge: An employee-card shape with a camera, a fingerprint button, and a tap-to-record path that transcribes a conversation and lets the agent see what the wearer sees.

Bathiche described Solara as built for an open, multiple-agent world, with Intune and Entra in the management path. Names around the briefing included Target, Best Buy, and CVS Healthcare as early pilot candidates, plus weather and retail partners on MediaTek Genio-class silicon. The desk slab can wake a Windows 365 session when a legacy app is the only way through a task, which is a tell. Solara is the agent face. Windows remains the place old software goes to die quietly in a Cloud PC.

That split is the second-order move the preview never quite named. Nadella opened on Windows as the agent platform. The gadget OS that is actually agent-first sits on Android. Windows 11 keeps the desktop, the NPU and GPU APIs, MXC, and the developer configuration. Solara keeps the badge and the kitchen-counter slab. Nobody on stage needed a Windows 12 splash screen to make that division of labor stick.

Three Months Later, Most Autopilots Stay in Preview

By early September, the catalog from June had sorted itself into things developers can install and things that still need a program manager’s blessing.

THE BUILD-TO-SEPTEMBER CLOCK

  1. May 29, 2026: Davuluri posts that something new is coming for developers, and that it is not a new OS version.
  2. June 2, 2026: Keynote day. Microsoft IQ, Scout, MAI models, MXC, Aion, RTX Spark Dev Box, Solara, Foundry Toolkit GA, Windows 365 for Agents GA.
  3. June 16, 2026: Work IQ APIs go generally available.
  4. June 22, 2026: Windows Developer says developers can build with Aion 1.0 Instruct for everyday text work, including inside Edge.
  5. Early July 2026: Hosted agents were due for general availability; Agent 365 plus MXC was due in preview; Aion Instruct open weights were due on Hugging Face.
  6. September 1, 2026: Microsoft Learn still lists Scout as a Frontier preview that needs an opt-in and may never ship in that form.
  7. September 7, 2026: Microsoft Mechanics shows Scout working on a Windows 365 Cloud PC from a Teams message on a phone, laptop lid closed.

The demo is the tell. Scout can find a file on a Cloud PC, summarize it, and draft mail for review, and it still needs the Frontier path, Intune, and a Copilot license to get there. Aion 1.0 Plan had been promised in the months after June and had not been put on every capable Windows 11 PC as a default inbox model. Nadella’s Copilot Super App, promised for summer, was not a public, everyday replacement for Chat, Cowork, and Code on ordinary tenants. DGX Station for Windows remained a Q4 machine.

Hobbyists did the part that did not need a keynote. Foundry Local, already generally available around the show, is what people actually installed: one WinGet command, an OpenAI-compatible endpoint on localhost, and an NPU that finally runs an inference. That is the unmetered idea at human scale. It is also not Scout booking your week.

Frequently Asked Questions

Did Microsoft Announce Windows 12 at Build 2026?

No. Four days before the show, Pavan Davuluri said the developer surprise was not a new OS version, and the keynote stayed on Windows 11 quality, local APIs, MXC, and the RTX Spark Dev Box. Build has rarely been the venue for a consumer SKU launch, and nothing on stage walked that back.

What Is Microsoft Scout and Who Can Use It?

Scout is a desktop Autopilot for Windows and macOS that reads and writes files, runs shell commands, drives a browser, and queries Microsoft 365 data, with approval required before sensitive actions. It is an experimental Frontier release: you need Frontier enrollment, Intune policy, an attestation, and a GitHub Copilot license before the installer is even offered.

What Is Project Solara?

Solara is Microsoft’s agent-first device platform, built on a customized Android stack rather than Windows, with an Agent Shell that is supposed to draw just-in-time UI for each form factor. The desk hub and wearable badge shown at Fort Mason are reference designs; Microsoft said it will not ship those two objects as its own products.

What Are Aion 1.0 Instruct and Aion 1.0 Plan?

They are on-device small models for Windows. Instruct handles everyday text, runs even on CPU-class machines, and opened to developers through Edge Insider builds in June, with open weights planned for Hugging Face in July. Plan is the 14 billion parameter, 32K-context reasoner that can call tools and run a local agent loop, scheduled for capable devices in the months after Build rather than on June 2.

How Does an Autopilot Differ From Copilot Chat?

Copilot chat still waits for a prompt in a side pane. An Autopilot stays running, holds its own Entra identity, and takes actions inside the permissions you already set, including on a heartbeat every 15 to 120 minutes in Scout’s preview. Copilot Cowork, which Microsoft had already put into general availability in June, sits between those two modes: it finishes a scoped job, then stops.

The Fort Mason keynote changed the map of where Windows AI is allowed to run. It did not put an Autopilot on every Start menu. Until Scout leaves Frontier and Aion Plan is an inbox model, the agent OS Microsoft described is still something you opt into with a Copilot license and a Cloud PC, not something the rest of the Windows 11 install base already has.

Harry edits WinAddons, an independent news site that he owns and runs, covering Windows, Xbox, Azure, Microsoft 365, Teams, OneDrive, Outlook, the software built around them and Microsoft's business. His method comes from ten years in journalism, a reporter's years followed by an editor's, and the bulk of that decade has been spent watching Microsoft ship. His reporting starts with what Microsoft publishes: release notes and KB articles read in full, build numbers checked on an installed machine, MSRC advisories and the CVE records behind them, the Azure status history, lifecycle pages, store listings in the market they apply to, and the earnings releases and filings that carry the company's numbers. Every figure is checked against its source before publication, and a public corrections policy explains how mistakes are fixed and labelled. On security stories he does not publish exploit details before a fix is available, reporting what is affected and what to do instead. Pre-release features are labelled by channel and build, and a rumour is called a rumour. Readers can reach Harry at support@winaddons.com.

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending