Microsoft Build 2026 arrives in five days with a clear message: the era of experimental AI agents is over, and the era of deploying them at scale has begun. The developer conference runs June 2 and 3 at Fort Mason in San Francisco, marking the first time in a decade that Microsoft has moved Build outside of Seattle. The shift reflects where the company's priorities lie: closer to the Bay Area's AI and startup community, and focused on hands-on developer access rather than conference spectacle.

The conference will draw roughly 2,500 developers in person, a deliberate reduction from the 3,000 to 5,000 attendees of previous years. Microsoft is trading scale for intensity. The keynote, delivered by CEO Satya Nadella, will stream free online at build.microsoft.com, but the smaller in-person format prioritizes direct access to Microsoft engineering teams and hands-on lab sessions over the polished announcements that have traditionally defined the event.

What Makes Build 2026 Different From Previous Years?

Build has been running since 2011, and over 16 years it has evolved from a Windows-focused developer event into Microsoft's primary venue for signaling the company's direction across cloud, AI, and developer tools. The 2026 edition marks a turning point in how Microsoft approaches AI announcements.

In 2025, Microsoft spent Build announcing agents as a concept. This year, the focus shifts to what happens after the announcement: production-ready APIs, enterprise integrations, and real deployment data from customers already running AI agents in their workflows. The theme, according to the session catalog, is agents that are no longer proof-of-concept but infrastructure you can deploy on Monday.

GitHub COO Kyle Daigle will share keynote stage time with Nadella and Scott Guthrie, a placement that signals GitHub's central role in Microsoft's AI strategy. GitHub Copilot, the company's AI coding assistant, has 4.7 million paid subscribers and generates 46% of code in repositories where it's installed. But adoption tells only part of the story. In a JetBrains developer survey from April 2026, only 9% of developers named Copilot their most-loved coding tool, compared to 46% for Claude Code, Anthropic's competing product. Build 2026 is where Microsoft attempts to close that gap.

What AI and Developer Tools Will Microsoft Announce?

The session catalog spans seven tracks, each revealing where Microsoft expects developer attention to focus over the next year. Understanding these tracks provides a roadmap of what to expect from the keynote and breakout sessions:

• Agents and Apps: Multi-agent workflows inside Visual Studio Code, deeper integration between GitHub and Azure, and updates on how the June 1 AI Credits billing transition will work for teams running heavy agentic workloads.
• Azure AI Platform and Azure AI Foundry: Enterprise integrations, combined routing across OpenAI models and open-source alternatives, and small language models optimized for Windows on-device inference.
• GitHub and Developer Productivity: GitHub Copilot's autonomous coding agent, which launched at Build 2025 with the ability to fix bugs, write tests, and open pull requests without developer prompting, will receive a next-generation release with real deployment data.
• Responsible AI: AI safety frameworks, compliance tooling, and developer-facing governance controls, now running as a dedicated track rather than bolted onto security sessions.
• Windows: A unified AI software development kit (SDK) for Windows developers, bundling the ONNX Runtime, DirectML, and the Copilot Runtime into a single package.
• Working with Models: Guidance on integrating and deploying language models across Microsoft's platform.
• Microsoft Fabric: Updates to Microsoft's data and analytics platform.

The Windows track deserves particular attention. Microsoft is expected to announce a unified AI SDK that ends the fragmentation that has made on-device AI development on Windows harder than it should be. Copilot+ PCs already ship with neural processing units (NPUs) capable of 40 or more trillion operations per second, yet most applications never use them. Recent Windows updates added finer NPU scheduling APIs, and the new SDK will wrap all of this into a single NuGet package, making local AI inference a straightforward installation rather than a multi-library integration project.

Agent 365, Microsoft's enterprise control plane for AI agents, reached general availability on May 1, 2026. This platform centralizes governance across Microsoft and third-party agents, including those running on AWS Bedrock and Google Cloud deployments. Defender and Intune can now detect unmanaged agents running on employee devices. Build 2026 will give Agent 365 its first major developer platform moment, with sessions on how teams integrate it into production workflows.

How to Prepare for Microsoft Build 2026

Whether you're attending in person or joining online, here are the practical steps to get the most from the conference:

• Register for the free online stream: The keynote and all sessions stream free at build.microsoft.com. Registration opens immediately, and the session catalog is already live, allowing you to add sessions to your scheduler in advance.
• Browse the session catalog early: The Agents and Apps and GitHub productivity tracks fill up fast in on-demand queues, so reviewing the full catalog and scheduling sessions now ensures you don't miss the sessions most relevant to your work.
• Attend the Dev Your Own Way event if in San Francisco: Microsoft for Startups is running a separate event on June 2 focused on connecting founders and developers with Microsoft engineering teams, free to attend and separate from the main Build conference.

Copilot CLI reached general availability in March 2026, bringing agentic coding to the terminal. Build 2026 will expand on that foundation with deeper integrations and new capabilities. The Azure AI Foundry Agent Service reached general availability at Build 2025, and this year's announcements will focus on what happens after launch: deeper enterprise integrations, combined routing across different AI models, and small language models optimized for inference on Windows devices.

The decision to move Build to San Francisco and reduce in-person attendance reflects a broader shift in how Microsoft views developer conferences. Rather than a spectacle event where thousands gather to hear announcements, Build 2026 is designed as a working session for developers who need to understand what the Microsoft platform will look like for the next year. The smaller format prioritizes hands-on access to AI systems and direct time with product engineers over polished keynote presentations.

For developers building on anything in the Microsoft stack, whether Visual Studio Code, Azure, or GitHub, Build 2026 is where the next year of your toolchain gets announced. The conference opens June 2 with Satya Nadella's keynote. Five days is enough time to clear your calendar.