Microsoft Build 2026 (June 2–3, San Francisco) developer guide: Windows Agent Runtime, Agent Framework GA, multi-model Copilot, and Azure AI Foundry.
Microsoft Build 2026 runs June 2–3 at Fort Mason Center in San Francisco, and the pre-conference disclosures make clear this is the most architecturally significant Build since Satya Nadella reoriented the company around cloud infrastructure over a decade ago. The theme is not incremental Copilot improvements or another layer of AI assistant features added to Office 365. It is Windows becoming a first-class runtime for autonomous AI agents, the Microsoft Agent Framework reaching production status, and Copilot being rebuilt as a multi-model platform that routes work across OpenAI, Anthropic, and open-source models simultaneously.
For developers, the question is not whether to pay attention. It is where to focus, because the announcement surface area is enormous. This guide organizes what is confirmed shipping, what is in developer preview, and what the changes mean for anyone building production software on Microsoft’s stack today.
Copilot Studio May 2026: What Already Shipped Before Build
Microsoft’s most consequential agentic announcements this cycle did not wait for the keynote. Copilot Studio’s May 2026 update reached general availability on three features that fundamentally raise the architecture ceiling for what Copilot-based systems can do — and most enterprise developers have not yet integrated them.
Computer-Using Agents Are GA
Computer-Using Agents in Copilot Studio can now interact directly with web applications and desktop software through their UI layers, not through brittle API integrations. This matters because most enterprise software does not expose a documented API for the operations employees actually perform day-to-day. The GA release ships with enterprise-grade credential management that eliminates the need to embed credentials in agent definitions, and adaptive interface recovery: when a target application changes its UI layout, the agent re-learns the interaction pattern rather than silently breaking. Microsoft describes this as “robotic process automation without the brittle scripts” — and the framing is accurate.
Agent-to-Agent Communication Is GA
Agent-to-agent (A2A) communication also graduated to general availability in the May Copilot Studio update. Agents can now exchange structured messages, delegate subtasks, and coordinate across systems using shared organizational context. The underlying protocol is Microsoft’s Work IQ A2A spec, built on top of the IETF-draft A2A protocol that Google co-developed in early 2026. For developers, the practical implication is that multi-agent orchestration is now a first-class capability in the Copilot Studio visual designer — no SDK required to wire agents together. Agents built with the Microsoft Agent Framework SDK are also wire-compatible with Copilot Studio A2A, meaning SDK-built agents and Studio-built agents can communicate directly in mixed deployments without custom adapters.
Redesigned Workflows and a Faster Orchestration Layer
The May update ships a redesigned Workflows experience with a unified visual canvas that combines deterministic actions, conditional branching, and AI-powered steps in a single editing surface. The critical architectural improvement is that agent nodes can now be embedded directly inside workflow graphs, eliminating the split between Power Automate flows and Copilot agent actions that previously required two separate tooling surfaces to manage. The upgraded AI orchestration layer delivers approximately 20% better evaluation performance at 50% lower token consumption — meaningful economics for enterprise deployments running high volumes of agent invocations per day.
Work IQ, Microsoft’s enterprise agent intelligence layer, added REST API access, a CLI, and remote Model Context Protocol (MCP) server support in the same May update. If you are building integrations against Copilot Studio agents from external systems, the REST API is now the correct integration path rather than Power Automate connectors. The MCP server support means Copilot agents can share the same tool surface as Claude and Gemini agents — a significant interoperability improvement for organizations running mixed-provider AI stacks. For the broader context on MCP production patterns, the MCP developer guide covers the production hardening patterns that matter most heading into the second half of 2026.
Microsoft Agent Framework: AutoGen Meets Semantic Kernel
The headline developer announcement at Build 2026 is the production release of the Microsoft Agent Framework — the formal convergence of AutoGen and Semantic Kernel into a single, commercially supported SDK for building multi-agent systems. Both projects have been in active development since 2024. AutoGen contributed multi-agent orchestration patterns and research-grade coordination protocols. Semantic Kernel contributed enterprise-grade memory management, plugin architecture, and the integration connectors that .NET shops actually use in production. The unified framework inherits both codebases under a stable, versioned release with commercial SLA support.
Core Primitives and Supported Languages
The Agent Framework GA release supports .NET (C# primary) and Python with consistent APIs across both runtimes. The core programming model is built around four primitives:
- Agent — the base execution unit with a defined role, tool access, memory configuration, and optional model selection override
- AgentGroup — an orchestrated collection of agents with configurable communication topology: broadcast, hierarchical, or peer-to-peer
- AgentRuntime — the execution host supporting local process, containerized, and Azure-managed deployment targets
- ToolRegistry — declarative registration of MCP servers, REST endpoints, function tools, and OpenAPI-described services
The framework ships with built-in persistent memory backed by Azure Cosmos DB or Redis, circuit breakers for agent failure recovery, and structured observability logging that integrates with Application Insights out of the box. The agent-to-agent communication protocol is wire-compatible with the Copilot Studio A2A implementation, so agents built with the SDK can communicate with Copilot Studio agents in mixed deployments without custom adapters or message translation layers.
Deployment and Pricing
Local execution is free. Azure-hosted AgentRuntime, managed through Azure AI Foundry, is priced on consumption: per-agent invocation and per tool call resolved through the Foundry layer. Exact per-invocation rates are expected to be announced at the June 2 keynote. Teams planning high-volume agentic workloads should audit usage under the AI Credits billing model that transitions on June 1 — the day before Build — to avoid unexpected cost surprises in the first week of production deployments.
Comments · 0
No comments yet. Be the first to share your thoughts.