Microsoft Open-Sources Windows Agent Framework, Declares Windows an AI Agent Platform

Microsoft released Windows Agent Framework (WAF) 1.0 under the MIT license at Build 2026 today, giving developers a free, open toolkit to build AI agents that run on local PCs, cloud desktops, and edge devices from a single configuration file. Satya Nadella's keynote made the underlying thesis explicit: Windows is no longer a platform built only for human users — software agents are now treated as first-class residents of the operating system.

Windows Agent Framework (WAF) is a developer SDK that lets builders define, deploy, and manage AI agents using a declarative YAML manifest. One manifest describes the agent; the framework handles where it runs — a local Windows machine, a Windows 365 Cloud PC, or an Azure Arc-enabled edge device. Developers don't write separate deployment logic for each environment.

What Microsoft Shipped at Build 2026

Microsoft's Build 2026 keynote introduced a cluster of interconnected announcements centered on the agent-first Windows vision:

• Windows Agent Framework 1.0 — MIT-licensed, open-source SDK for building cross-environment agents from a single YAML manifest
• Azure Agent Mesh — Microsoft's orchestration layer for managing multiple agents working together across Azure services and Windows endpoints
• Windows Agent Store — a new distribution channel inside the Microsoft Store dedicated to agent-based applications
• Unified runtime targets: local Windows machines, Windows 365 Cloud PCs, and Azure Arc-enabled edge devices all supported from the same manifest

The MIT license is a deliberate developer acquisition move. It lowers the cost and risk of building on WAF compared to a proprietary SDK, and signals Microsoft isn't trying to lock builders into a closed ecosystem — at least at the framework layer.

Context: The Shift Agents Force on Operating Systems

Traditional operating systems were built around one model: a human at a keyboard issuing instructions. AI agents break that assumption. They run autonomously, trigger actions without direct user input, need access to files and APIs, and may run continuously in the background or on a schedule.

Windows has been retrofitting agent-friendly primitives — background execution, sandboxed app permissions, local model inference via Copilot+ PC hardware — but WAF is the first time Microsoft has shipped an opinionated, end-to-end framework for agent development rather than a collection of isolated capabilities.

Nadella's framing of agents as "first-class citizens in the runtime, tooling, and distribution model" is a meaningful shift in how Microsoft positions the OS to enterprise buyers and developers.

What This Means for Businesses and Developers

For enterprise IT teams, the Azure Agent Mesh is the more immediately relevant piece. It provides a centralized orchestration and observability layer for managing fleets of agents across an organization — something IT departments have been demanding as agent sprawl becomes a governance problem. Agents that run on laptops, cloud VMs, and edge hardware under one management plane is a meaningful operational simplification.

For developers, WAF's cross-environment portability is the headline value. Building an agent that works on an employee's laptop and in a cloud VM and on a factory floor terminal without rewriting deployment logic cuts significant engineering time. The YAML-manifest approach mirrors patterns developers already use in container orchestration (Kubernetes) and CI/CD pipelines — the learning curve is low for anyone already in that ecosystem.

For the Windows Store, a dedicated agent distribution channel creates a new software category Microsoft can own. App stores for traditional software are mature and slow-growing; an agent store is a greenfield market Microsoft is positioning itself to define before competitors can establish their own distribution model.

What to Watch

WAF 1.0 is the framework — the ecosystem around it will define whether it matters. Watch for third-party agent developers adopting the YAML manifest standard, and whether enterprise software vendors (SAP, ServiceNow, Salesforce) build WAF-native agents or continue routing through their own agentic SDKs. Microsoft's bet is that Windows as the deployment substrate, combined with Azure as the orchestration layer, is sticky enough to become the default agent platform for enterprise developers. That thesis gets tested over the next 12 months.

— Hector Herrera