Microsoft moves Build from Seattle back to San Francisco, scheduled for June 2-3, instead of May, and invites 2,500 developers, down from the usual 3,000-5,000
Context & Ripple Effects
Build has recently been a May event in Seattle, including the May 2025 Seattle conference, while Microsoft has also used San Francisco for earlier editions. The return to San Francisco changes both the event’s geography and its timing.
The reduced invitation count is a notable break from the conference’s typical 3,000–5,000-developer scale. It follows a period in which Build also shifted online during the pandemic, including the online-only 2021 event, underscoring Microsoft’s willingness to alter the format around its developer outreach.
First-order effects
- Invitees, partners, and speakers must rework travel and launch plans around a June 2–3 event in San Francisco rather than a May gathering in Seattle.
- Microsoft will run Build with 2,500 invited developers, narrowing the in-person audience relative to its usual attendance range.
Second-order effects
- A smaller in-person cohort raises the value of invitations and may push developers who are not selected toward any digital materials or follow-on outreach Microsoft provides.
- San Francisco event vendors and local attendees gain the conference activity, while Seattle’s Build-related hospitality and partner ecosystem loses that near-term draw.
Third-order effects
- If smaller, selectively attended Build events persist, Microsoft’s flagship developer conference could become a more curated relationship and launch venue rather than a broad in-person gathering.
- Repeated changes in Build’s city, calendar slot, and delivery model point to a more flexible conference strategy, though this move alone does not establish a permanent format shift.
The trend: Microsoft is treating its flagship developer event as a flexible, capacity-managed platform rather than a fixed annual gathering in one city and month.