Build 2026: Microsoft scales down its event to target the AI elite in San Francisco

Build 2026: Microsoft reduces the size of its event to target AI elites in San Francisco

Microsoft is changing its scenery — and its approach. For the 2026 edition of Build, the developer conference is moving from Seattle to San Francisco, specifically to the unique venue of Fort Mason. This decision is intentional: to capture the AI energy of the Bay Area while downsizing the event to put developers back at the forefront.

Return to San Francisco: A location that reflects the strategy

The Build 2026 will take place from June 2 to 3 at Fort Mason, a former military site transformed into a cultural and event space. Microsoft plans for 2,500 attendees, compared to 3,000 to 5,000 in previous years, and has shifted the event out of its usual May timeframe.

Kyle Daigle (COO of GitHub) summarizes the intention: to avoid both the unmanageable “megaconference” and the exclusive micro-event, aiming for a balance where networking is as valuable as the keynotes. In this spirit, the format is designed so attendees can experience an announcement, try a demo, and engage immediately, laptop at hand, without navigating through an expansive convention center.

A Build 2026 less about Windows showcase, more about builders’ tools

The change of city reflects a shift in posture. Microsoft implicitly acknowledges that Build has sometimes served as a platform for broad announcements — Windows, products, vision — not always tailored to the developer audience. The stated goal is to return to something more tangible: what Microsoft is building, what developers have already created on top of it, and how to leverage it without piling on repetitive “visionary” speeches.

buildlogo

This is an interesting shift in the era of Copilot: as AI becomes the interface for everything, the competition is not only won on the stage but also on APIs, SDKs, tools, workflows, and the quality of day-to-day experiences. San Francisco, whether we like it or not, remains the ecosystem where these conversations happen quickly — and spread even faster.

More external voices, more sessions: the “ecosystem” effect

Another sign: Microsoft is inviting more external voices. Among the announced speakers are Simon Willison (Datasette), Priyanka Sharma (Thiink), and Shawn Wang, alongside company figures such as Satya Nadella, Jared Palmer (GitHub), and Scott Hanselman.

This mix is far from trivial: it signals that Microsoft wants Build 2026 to feel less like an “editor” conference and more like a gathering where practical ideas are discussed — not just a roadmap is presented.

Seattle is not “canceled,” but Microsoft is testing something new

The move from Seattle does not signify a permanent split. Build has changed cities over the years, having moved to Seattle in 2017 after several editions in San Francisco. And while speculation has circulated regarding reasons tied to the downtown experience, Daigle dismisses the notion that this relocation was prompted by such stories: the company frames this choice as a logic of iteration — “navigating to learn” — applied … to an event. We move, we observe, we adjust.

Ultimately, Build 2026 resembles a product test: smaller, denser, more social, in a city where AI is not just a theme — it’s the background noise. If this experience works, Microsoft might have found the missing formula for its major gatherings: less stage, more code.


Scroll to Top