Microsoft Build Moves to San Francisco for a More Intimate, Developer-Focused Experience
Microsoft is shifting its annual Build conference from Seattle to Fort Mason in the San Francisco Bay Area, aiming to ride the AI buzz and create a more hands-on, community-driven atmosphere. The venue choice signals a deliberate pivot toward closer attendee engagement and practical demos rather than broad, megaphone-style presentations.
Key notes from the change:
- A more intimate setting: The event will emphasize developer interaction, with attendees able to attend keynotes, stroll into halls, and directly engage with demos and colleagues.
- Timing and size: Build is scheduled for June 2–3 this year, with about 2,500 developers invited to register, a smaller footprint than the roughly 3,000–5,000 participants in prior years.
- Why SF and Fort Mason: Microsoft is leveraging the Bay Area’s AI momentum and the venue’s smaller scale to emphasize attendee-centric experiences and meaningful collaboration over purely expansive programming.
A sharper developer focus:
- Microsoft intends Build to be more about developers and practical usage—showing what teams are building and how others can leverage the technology—rather than repeatedly propping up Vision slides or third-party pitches.
- The conference will feature more external voices alongside Microsoft’s own lineup, highlighting a broader ecosystem of ideas and use cases.
Notable speakers and lineups:
- External speakers include Simon Willison (Datasette), Priyanka Sharma (Thiink), and AI engineer Shawn Wang, among others.
- Microsoft’s lineup highlights include CEO Satya Nadella, GitHub SVP Jared Palmer, and Scott Hanselman, VP of Developer Communities.
A different kind of Build experience:
- Attendees are encouraged to come ready to code, with laptops in hand and a focus on hands-on learning and peer-to-peer exchange. Officials describe the format as more community-centric, enabling attendees to learn from one another in a collaborative space.
Context and outlook:
- This move does not necessarily mark a permanent relocation away from Seattle. Build originally shifted from San Francisco to Seattle in 2017, and organizers say the decision to try San Francisco this year is about learning from a new audience and environment.
- Microsoft’s team has downplayed any connection between the Seattle experience and the relocation, framing it instead as an experiment to see what the SF setting can teach the conference and its participants.
Overall, Build’s shift to Fort Mason signals a refreshed emphasis on direct developer engagement, hands-on demos, and a tighter, more community-focused experience, with an eye toward what developers are building today and how Microsoft’s tools fit into that work.