Microsoft Build 2026 Bets on Windows as an Agent Platform, Unveils Project Polaris and Azure Agent Mesh
At Build 2026 in San Francisco, Microsoft unveiled Project Polaris to replace GPT-4 Turbo in GitHub Copilot, open-sourced the Windows Agent Framework, and previewed the Windows Agent Runtime and Azure Agent Mesh.
Overview
Microsoft opened its annual Build developer conference on June 2, 2026 at Fort Mason Center in San Francisco, with CEO Satya Nadella delivering a keynote that recast Windows and Azure as first-class runtimes for autonomous AI agents. The two-day event, which drew roughly 2,500 developers on-site, centered on a cluster of interlocking announcements: a homegrown AI coding model called Project Polaris that will replace GPT-4 Turbo in GitHub Copilot, a preview of the Windows Agent Runtime, the general availability of Copilot Workspace, and the introduction of Azure Agent Mesh as a federated control plane for enterprise agent deployments, according to ChatForest’s Build 2026 recap.
Project Polaris: Microsoft’s In-House Coding Model
The single most consequential announcement for GitHub Copilot users is Project Polaris, a mixture-of-experts coding model Microsoft has built internally to power Copilot, with specialized sub-modules for different programming languages and frameworks, as Windows News reported. The model was trained on a curated corpus of public and private code repositories, emphasizing security-vetted enterprise codebases.
Starting in August 2026, Polaris will replace GPT-4 Turbo as the default Copilot model for existing subscribers, with an optional three-month fallback period for teams that prefer to remain on GPT-4, according to ChatForest. Microsoft says the model outperforms GPT-4 Turbo on HumanEval and MBPP benchmarks, with particular gains in low-resource languages like Rust and Haskell. An early preview demonstrated autonomous migration of legacy .NET Framework applications to .NET 9, Windows News noted.
Polaris runs on Microsoft’s custom Maia AI accelerators in Azure and is hosted on Azure AI Foundry. A companion fine-tuning service called Turing Forge allows organizations to adapt Polaris to private codebases with as few as 50 examples, according to Windows News.
Alongside Polaris, Microsoft restructured GitHub Copilot into three tiers: a free Copilot Starter tier, a Pro tier with multi-file context windows up to 100,000 lines and autonomous test generation, and a Copilot Enterprise tier that adds custom fine-tuning, private knowledge base integration, and audit-grade explainability, ChatForest reported.
Separately, starting June 1 — the day before Build opened — Microsoft shifted Copilot from per-seat licensing to a per-invocation AI Credits model, a billing transition that had already drawn attention from developers ahead of the conference, according to DEV Community coverage. Multi-Model Copilot, announced at the same event, now routes requests across OpenAI (GPT-5.5+), Anthropic Claude, and on-device models, with Azure AI Foundry handling routing and governance and configuration available at the enterprise tenant level.
Windows as an Agent Platform
Building on the Windows Agent Framework 1.0 that shipped in April, Microsoft at Build previewed the Windows Agent Runtime — a background service that manages agent lifecycles, memory, and permissions using WinRT infrastructure and a rule engine for granular access controls, as Windows News described.
The Windows Agent Framework itself carries an MIT open-source license and defines agent behavior through YAML manifests that are portable across local Windows, Windows 365 Cloud PCs, and Azure Arc-enabled edge devices, ChatForest noted. The framework supports ambient agents capable of running continuously in the background, with demonstrated use cases including email triage, recurring reports, API orchestration, and configuration drift detection.
The Windows Agent Runtime preview, which reaches Windows Insiders in June 2026, initially supports text-based agents operating on JSON, XML, and PDF files, according to AI Tools Recap. Vision-based agents capable of pixel-level screen interaction are on the roadmap but are not expected until 2027, DEV Community reported. Cross-device scenarios require an Azure subscription, while low-traffic agents receive free monthly grants during the public preview period.
A new AgentPolicy API gives IT administrators control over agent permissions, and agents can appear in the Windows taskbar, receive calendar and file system events, schedule background tasks, and have their permissions managed through Intune, AI Tools Recap reported.
Visual Studio 2026 ships with an Agent Designer, a low-code companion that emits YAML-based manifests describing an agent’s intents, actions, and safety constraints. A command-line tool called wagent packages everything into a single executable, while a new AgentOps feature integrates with GitHub Actions for automated agent testing, Windows News described. Early design partners for the Windows Agent Runtime include Adobe for InDesign template automation and Zoom for meeting summarization into Microsoft Planner, ChatForest noted.
A curated Windows Agent Store, where developers retain 85% of revenue — mirroring the Microsoft Store model — will list agent manifests and companion services, with Adobe and Zoom named as launch partners, according to AI Tools Recap. All agents require a security review covering capability disclosure and data handling policies before listing.
Azure Agent Mesh and the Enterprise Stack
For enterprise deployments spanning multiple environments, Microsoft announced Azure Agent Mesh, a control plane that federates agent execution across on-premises Windows servers, Windows 365 Cloud PCs, and Azure Arc-enabled edge devices, as ChatForest and Windows News both reported. The Mesh routes tasks automatically based on latency and GPU availability. It is priced on a consumption-based model with a dedicated agent compute SKU, and general availability is targeted for Q4 2026.
Also reaching GA in May 2026, ahead of Build, were Computer-Using Agents — which interact directly with web applications and desktop UIs without requiring API integrations — and Agent-to-Agent Communication, built on Microsoft’s Work IQ A2A spec and the IETF-draft A2A protocol, DEV Community reported. Microsoft describes Computer-Using Agents as “robotic process automation without the brittle scripts.” Workflow orchestration improvements yielded approximately 20% better evaluation performance and 50% lower token consumption, according to the same report.
The broader agent platform builds on the Microsoft Agent Framework 1.0 that reached general availability in April, which unified AutoGen and Semantic Kernel into a single SDK supporting .NET and Python, with persistent memory backed by Azure Cosmos DB or Redis, as DEV Community noted. Copilot agents can also share tool surfaces with Claude and Gemini agents via the Model Context Protocol, with REST API, CLI, and remote MCP server support now available in Work IQ.
WSL 3 and Developer Infrastructure
Microsoft also previewed Windows Subsystem for Linux 3 at Build, a complete re-architecture with paravirtualized GPU and NPU access, AI Tools Recap reported. According to Windows News, PyTorch training runs only 3–5% slower than bare-metal Linux under WSL 3, with initial hardware support on Qualcomm Snapdragon X Elite and Intel Meteor Lake-Lunar Lake platforms; AMD support is planned for a future update.
A Unified Windows AI SDK — bundling ONNX Runtime, DirectML, and Copilot Runtime into a single NuGet package — addresses SDK fragmentation for .NET developers, AI Tools Recap noted. Microsoft and Nvidia also jointly announced the first Arm-based Nvidia-powered Windows PCs from Microsoft Surface and Dell, with a simultaneous announcement at Computex in Taipei, ChatForest reported.
What We Don’t Know
Several announced products remain at preview stage without firm pricing. Pricing for the MAI v2 model suite — including MAI-Image-2.5, MAI-Voice-2, and MAI-Transcribe-1.5 — was not disclosed at Build and is expected at a separate GA announcement. Azure Agent Mesh pricing details beyond the consumption-based structure have not been published. Windows 12, which Microsoft confirmed internally is in early development under the codename “Hudson Valley,” was not announced at Build and may not preview until late 2026 or early 2027, ChatForest noted.