Microsoft Build 2026: Copilot Cowork, agents that ship code, the multi-model pivot.
Build moved to San Francisco and compressed to two days. The headline wrote itself in the pre-event signal: Copilot Cowork, agents that build the app, and a multi-model stack that quietly includes Claude. The developer story is loud. The partner-channel story underneath it is the one worth flying for.
Why this one matters
Build is Microsoft's developer-leadership gathering: enterprise and ISV dev leads, Azure customers, and the partner channel that resells the stack. Two changes this year reset the room. It moved from Seattle to San Francisco, and it compressed from four days to two (June 2-3). A shorter Build in the Bay Area means higher density and a harder follow-up problem: the same number of conversations, half the days, in a city full of competing dinners. The session catalog is already live and the keynote is Satya Nadella, so unlike most events two weeks out, the storyline isn't a prediction. It's confirmed.
The year's headline: agentic work, and the quiet multi-model pivot
Microsoft's pre-event signal is unusually explicit. Wave 3 of Microsoft 365 Copilot introduces 'Copilot Cowork,' framed as turning intent into action across Microsoft 365, automating tasks and coordinating workflows. The session catalog includes 'use agents to build WinUI3 apps.' That's the loud story: 2026 is the Build where agents stop assisting and start doing the work. The quieter, more consequential signal is one line in the Frontier Suite announcement: 'expanded model diversity with Claude and next-gen OpenAI models available.' Microsoft is putting Anthropic's Claude inside its own stack, on its own main stage. Read every Copilot demo against that. The feature story is Cowork; the strategic story is that the OpenAI-exclusivity era is over and Microsoft is hedging in public.
Sessions worth showing up for
Catalog is live, so these are real, not predicted. (1) The Nadella keynote: the tell is how much airtime multi-model gets versus Copilot Cowork. If Claude is named on stage, that's the headline confirmed live. (2) The agents-build-WinUI3 sessions: this is where 'agents do the work' gets stress-tested against an actual app, and where the gap between demo and shippable shows. (3) Copilot Cowork deep-dives: watch for pricing and packaging, which is the question every enterprise dev lead actually came to answer and which the keynote will skate past. (4) Anything touching the partner/agent marketplace: Anthropic just put $100M into a Claude Partner Network and AWS launched a wave of partner programs the same quarter, so the channel economics of agents are a live, contested topic, not a footnote.
Breakouts with signal density
Main stage is the narrative; the signal is in the technical rooms and the partner track. Prioritize: the Sovereign Cloud / disconnected-AI sessions (Microsoft has been pushing governance for large AI models running fully disconnected, which is the enterprise-and-government buying signal hiding under the consumer Copilot noise); the Dynamics 365 agent sessions (Expense Agent in Business Central is a small announcement that signals where agentic-AI revenue actually lands first, in finance ops, not codegen); and the partner-enablement breakouts where the reseller margin on agents gets discussed. That last category is where the people who decide whether your product gets carried actually are.
Companies to track at the booths
Build's expo is partner-channel-dense. The pattern to read: Anthropic's posture in Microsoft's house. Anthropic says it's building the Claude Partner Network ('the most committed AI company to the partner ecosystem'); what it's actually doing at a Microsoft event is normalizing Claude as a first-class option inside the Azure-adjacent channel, on Microsoft's stage, which is a remarkable place to be selling. AWS-aligned ISVs (XBOW joined AWS ISV Accelerate for autonomous offensive security the same quarter) will be working the hallway to remind the channel there's a non-Microsoft agent stack. The integrators and Fabric/Power BI ISVs say analytics and workflow; what they're actually selling is the migration path from last year's Copilot pilots to this year's Cowork production, which is the budget that's actually moving. The read: every serious booth is positioning for the post-pilot agent budget, and the partner-network land grab is the real expo floor.
Conversation patterns: three hallway debates, one nobody is saying
Debated in the hallway: (1) Whether Copilot Cowork is production-real or a Wave-3 demo, and what the per-seat economics actually are once the pilot credits run out. (2) Whether 'agents build the app' survives contact with a real enterprise codebase or stays a greenfield WinUI3 stage trick. (3) Whether Microsoft's multi-model move is genuine optionality or a negotiating posture against OpenAI. The thing nobody will say from the stage: Microsoft just publicly de-risked its single biggest AI dependency by putting a direct competitor's model in its own suite, and the entire partner channel now has to re-underwrite which model they build on. Everyone will talk about Cowork features. The room that matters is the hallway argument about whether you still bet your roadmap on one model provider after watching Microsoft decline to.
After the badges come off
A two-day Build in San Francisco is a compression event: more partner and ISV-lead conversations per hour than any other developer show, and a follow-up window that closes faster because everyone flies out Wednesday into a backlog. The booth conversation about whether Claude or OpenAI underpins your integration, the partner-margin chat by the Fabric demo, the dinner where someone offered an intro: those are worth exactly what the follow-up that lands by Thursday is worth, and nothing if it doesn't. Met captures the context while you still know which conversation was the useful one, so the follow-up references the actual thing instead of 'great meeting you at Build.'
Download Met for iPhone
Read by engineering and partner leads heading to San Francisco for Build, pre-event analysis pulled from Microsoft's public signal, the live session catalog, and the enterprise-AI channel cycle. No signup, nothing stored on our servers.
