By Microsoft shipped its full agent stack at Build 2026 today, and it settles a debate that has been dragging on for two years. Windows Agent Framework 1.0 is MIT-licensed, production-ready, and merges Semantic Kernel and AutoGen into a single SDK. Windows Agent Runtime hits preview for Insiders this month. Azure Agent Mesh — a federated control plane that routes agent tasks across laptops, Cloud PCs, and edge devices automatically — targets GA in Q4. If you have been waiting for a stable platform to build serious agent workflows on Windows and Azure, the wait is over.
One SDK to Replace Them All
The Agent Framework 1.0 announcement is less about new features and more about consolidation. AutoGen (50,000+ GitHub stars) and Semantic Kernel (26,000+ stars) were both useful but positioned awkwardly — AutoGen for research-flavored multi-agent experiments, Semantic Kernel for enterprise orchestration. Developers had to pick a lane, and switching lanes was painful. WAF 1.0 ends that.
AutoGen is now in maintenance mode. All new development happens in Agent Framework. Semantic Kernel’s enterprise patterns carry forward. If you are on either framework, Microsoft has published migration guides. The API shape is consistent between Python and .NET — polyglot teams usually end up with two mental models, and WAF 1.0 avoids that.
Installation is straightforward:
# Python
pip install agent-framework
# .NET
dotnet add package Microsoft.Agents.AIThe framework ships with four core primitives — Agent, AgentGroup, AgentRuntime, and ToolRegistry — and five orchestration patterns: sequential, concurrent, handoff, group chat, and Magentic-One for hierarchical multi-agent workflows. Agents are defined declaratively in YAML and version-controlled in Git. MCP is natively supported, which means thousands of existing MCP servers are immediately available as agent tools without additional configuration. Provider support spans six connectors — Azure OpenAI, OpenAI, Anthropic Claude, Amazon Bedrock, Google Gemini, and Ollama — and switching providers is a one-line change.
Windows Agent Runtime: Agents as OS Citizens
The more architecturally interesting announcement is Windows Agent Runtime, entering preview for Windows Insiders in June 2026. Rather than treating agents as application-layer processes, the Runtime integrates them at the OS level — registered as system services with taskbar integration, calendar and file system event subscriptions, and Defender visibility.
The sandboxing model mirrors mobile permissions: capability grants covering file system scope, network access, and application launch permissions, with users reviewing and approving at install time. That UX pattern makes agent capabilities auditable by default — a meaningful security improvement over agents that run as unconstrained background processes.
Two things to be clear-eyed about: the Runtime preview supports only text-based agents operating on JSON, XML, and PDF structured data. Vision-based agents — the kind that read and interact with screen pixels — are slated for 2027. If your use case requires UI automation or screen understanding, Windows Agent Runtime is not your answer yet.
Azure Agent Mesh: Same Code, Federated Execution
Azure Agent Mesh is the control plane that ties the whole story together. Build agents with WAF locally, and the same code runs across on-premises Windows servers, Windows 365 Cloud PCs, and Azure Arc-enabled edge devices — with the Mesh handling routing based on latency and GPU availability. No separate deployment configuration required per environment.
The security model is zero-trust: decentralized identifiers with Ed25519 cryptographic identity per agent, and the Inter-Agent Trust Protocol (IATP) for encrypted agent-to-agent communication. Dynamic trust scoring adjusts based on observed agent behavior over time, which matters as EU AI Act high-risk requirements take effect in August 2026.
The timing caveat: Agent Mesh is in preview now, with GA targeted for Q4 2026. Sign up for preview now — six months of experimentation before committing to production is worth using.
The Agent Store Economics Are Worth Noting
Windows Agent Store ships with an 85/15 revenue split for developers — better than Apple’s 70/30 App Store standard. Microsoft is making the economics case explicitly. The Unified Windows AI SDK consolidates ONNX Runtime, DirectML, and Copilot Runtime into a single NuGet package, ending the fragmented setup that made on-device AI inference on Windows more work than it needed to be.
What to Do This Week
- AutoGen users: Review the official migration guide and map agent boundaries to WAF primitives. Maintenance mode means no new features — plan the transition now rather than under pressure later.
- Semantic Kernel users: Patterns carry forward. Update your dependency to
Microsoft.Agents.AIand review the 1.0 changelog. - AI Credits billing: The shift from per-seat to per-invocation pricing took effect June 1. Run a usage audit. High-volume deployments may see significant cost changes.
- Azure Agent Mesh preview: Sign up now and review the Agent Governance Toolkit for EU AI Act compliance groundwork. Six months of preview before Q4 GA gives you time to validate your deployment topology before it matters in production.
The agent platform Microsoft described at Build 2026 is real and available today — at least the SDK layer. The Runtime and Mesh are previews with clear GA timelines. The question for most development teams is not whether to adopt, but when and in what order.
