Build 2026 and the platform that keeps absorbing

Microsoft's developer conference ran this week. The individual announcements matter less than the consistency of the strategy, which has been unchanged for about ten years and keeps working.

the strategy#

1. Meet developers where they are, including on other people's platforms.
2. Adopt other people's standards rather than inventing competing ones.
3. Open-source the layers where control is not worth the friction.
4. Monetize the cloud underneath.

Every Build for a decade has been an execution of that, and the cumulative result is that a company which was actively hostile to open source in 2005 is now the largest corporate contributor to it and owns the default editor, the default code host, and a large share of the developer toolchain.

the agent infrastructure#

The substantive announcements this year continue the theme of putting agent capabilities at the operating system layer rather than in an application: a permission model for what agents may reach, an identity model for agents acting on a user's behalf, and audit surfaces for what they did.

That is the right layer for it. The alternative — every application implementing its own agent permission model — produces exactly the inconsistency that made mobile permissions a mess for a decade before the platforms standardized.

The questions that matter and that a keynote cannot answer:

Granularity. "Filesystem access" is not a permission, it is a surrender. Does the model support "read from this directory for this task"?

Consent fatigue. If the prompts are frequent, users click through them, and the control is theater. The design problem is asking rarely and meaningfully.

Revocation and audit. Can a user see what an agent did and undo it? This is the part that is hardest and gets the least attention.

I will believe the security model when someone publishes an analysis of it, not when it is demonstrated on a stage.

the enterprise angle#

The genuinely differentiating position Microsoft has is that they can offer agent capabilities inside an enterprise's existing identity, compliance, and audit infrastructure.

That is worth more to a large organization than raw capability. An agent that works within the existing access control model, logs to the existing audit system, and is governed by the existing data policies clears procurement. An agent that requires a new trust boundary does not, regardless of how good it is.

This is the same advantage that won enterprise cloud and it is being applied identically.

what a developer should actually do with this#

If you build on Windows: the tooling story is genuinely good now — WSL, the terminal, winget, PowerShell 7 — and if your Windows support has been a grudging afterthought since 2018, it is worth revisiting.

If you build agent-adjacent products: design against the OS permission model rather than around it. Products that require users to disable platform protections do not get enterprise adoption.

If you are evaluating anything announced here: wait for the second version. Microsoft's first releases in a new category are consistently rough and consistently improved within a year. That is a reasonable pattern and it means the launch-day evaluation is not the useful one.

the pattern to watch#

The layer where the industry is currently fighting is not the model. It is the control plane for agents: who they are, what they may do, on whose behalf, with what audit trail.

Every platform vendor is building this. The one that becomes standard will have the same kind of position that identity providers have today, and it will be very durable.

That is the strategic story of the next three years and it is being fought in permission dialogs rather than benchmarks.