Microsoft Moves Build 2026 to San Francisco, Previews Copilot Platform

Microsoft confirmed its annual developer conference, Build 2026, will be held June 2–3 in San Francisco, shifting the event away from its recent Seattle pattern and compressing the program into a two-day, hands‑on format.

The company’s developer site lists the June 2–3 dates and describes Build as a place for “real code, real systems, and real workflows” with teams working on AI.

On and around May 25, 2026 Microsoft and several community outlets highlighted that Build will foreground Copilot and agent tooling, and reported previews of deeper Copilot integrations plus platform and SDK changes aimed at app builders and enterprises.

Microsoft is tightening Copilot access and entry points inside productivity apps while rolling agent features into Word, Excel, and PowerPoint — changes Microsoft has described in Tech Community posts and in its Microsoft 365 blog.

The developer-side work centers on the Copilot runtime and updated SDKs that let applications call local and cloud models more consistently, Microsoft documentation and developer pages say. Those pages position Copilot Runtime as a set of APIs for on‑device and cloud-connected model use.

Copilot Runtime (also called Windows Copilot Runtime in Microsoft materials) exposes higher‑level APIs for chat, vision, OCR and other AI primitives, and is designed to work with Windows App SDKs and model libraries. Microsoft has published guides and demos that show how the runtime plugs into app code.

Reports ahead of Build say Microsoft plans to bundle several pieces — ONNX Runtime, DirectML support and Copilot Runtime hooks — into SDK packages intended to reduce friction for Windows and cross‑platform developers. Independent previews and community writeups have suggested the move aims to simplify local inference and hybrid cloud workflows.

For Microsoft, the platform push is about more than features. Company messaging and outside coverage frame this year’s Build as a test of whether Copilot can become a consolidated developer platform rather than a set of scattered integrations. That framing is visible in Microsoft posts and in analyst and community commentary.

Enterprises will be watching for governance, identity and observability controls tied to these runtime and SDK updates, because agentic features raise new audit and compliance questions for IT teams. Analysts and community posts have highlighted trust and governance as likely themes at the event.

On the productivity front, Microsoft is also streamlining how Copilot is invoked in Office apps — fewer entry points, new keyboard shortcuts and a single floating access point — a user-interface change that has already prompted discussion and some user pushback.

Developers at Build should expect hands‑on sessions, code samples and SDK previews rather than only keynote demos; coverage and community previews describe a denser, workshop‑style program meant to get engineers working with runtime APIs and agent toolkits.

The broader picture is a Microsoft push to consolidate Copilot, GitHub, Windows and Azure tooling into a more coherent developer stack so companies can build agentic apps with clearer upgrade, governance and deployment paths. Microsoft’s documentation and recent posts underline that consolidation as a strategic aim.