Microsoft opened its Build 2026 developer conference on June 2 at Fort Mason in San Francisco with a keynote that put Office 365 Copilot Agent Mode at the center. Satya Nadella announced that Agent Mode will be the default mode across Word, Excel, and PowerPoint for Microsoft 365 Copilot subscribers, with the rollout starting in late June 2026. He also previewed the Windows Agent Runtime — a set of native agent APIs in the OS shell — and a Windows Agent Store paying developers an 85% revenue share, with Adobe and Zoom signed on as early partners.
The shift is mechanical, not cosmetic. Default Agent Mode means the user-facing default for these apps becomes an asynchronous coworker that plans, calls tools, and finishes work over minutes or hours, instead of a chat sidebar that waits for the next message. Each agent maintains its own context, permissions, and memory across documents. Office's installed base is roughly 400 million paid seats, so flipping the default mode on a tool that large changes the unit economics of every knowledge-work workflow that touches Word, Excel, or PowerPoint.
Microsoft's Agent 365 enterprise control plane reached general availability on May 1; Build 2026 is the consumer- and developer-facing companion. The keynote landed one day after Anthropic's confidential S-1 filing and is the latest data point in a four-month sprint in which every frontier lab and every platform vendor has converged on the same product framing — agents over chat, persistence over sessions. Microsoft now controls both the desktop OS and the productivity suite that most agents will live inside, which makes the Windows Agent Runtime announcement at least as strategically important as anything in Office.
Takeaway for learners: if you write code or work in spreadsheets for a living, the practical question for the next six months is whether your team's workflow can be expressed as an agent recipe — an inputs-to-outputs sequence with explicit tool calls. Workflows that can be expressed that way will compress fastest; workflows that depend on tacit judgment from a person in the loop will compress slowest. The students and early-career engineers who learn to write good agent specs — not just good code or good prompts — are the ones who will be most valuable on the other side of this rollout.