Satya Nadella posted on LinkedIn and X on September 13, nine hours before this post was written, a direct response to Dario Amodei's "We Must Pace the Frontier" published the day before. Nadella is the first head of a major hyperscaler to respond to it in public, and he does it by name-checking Amodei's own term: "We also welcome ideas like 'embedded evaluators' and the broader efforts to develop the mechanisms to make this more than just talk."
He pairs the endorsement with a deliverable. Microsoft, he wrote, will publish "the 'Code of Conduct' that underlies our own first party MAI models" tomorrow — September 14, today — for public consultation. That makes Microsoft's contribution to this week's argument different in kind from anyone else's so far: not another essay, but a governance document with a publication date attached, from the company that supplies the compute and, through Azure, much of the plumbing everyone else in this debate runs on.
The line that qualifies Amodei's own proposal
The post's sharpest sentence is a direct condition on the specific plan Nadella just endorsed: "The key is that this cannot be controlled by a handful of entities, but must have broad representation across the ecosystem, countries, and fields, including academia." Read against Amodei's essay rather than in the abstract, this lands on something concrete: Amodei's own text names exactly one example evaluator, METR, for the "embedded evaluators" role Nadella just welcomed. Nadella's line can be read as agreeing with the mechanism while declining to agree, in advance, that a single named organization should be the one doing it — a real caveat attached to a real endorsement, not a rubber stamp.
This blog noted the same structural concern the day before, via François Chollet's test for whether embedded evaluators risk being indistinguishable from self-regulation if staffed by people aligned with the labs by incentive and ideology — there's no sign Nadella was responding to that post specifically rather than reasoning to a similar place independently, but the two land close enough to be worth naming together. Either way, Nadella's own qualification doesn't resolve the harder question underneath it. Broad representation "across the ecosystem, countries, and fields" describes who should be at the table, not a commitment about who actually will be, and Microsoft's own position in that ecosystem is unusual: it isn't only a frontier lab like Anthropic or OpenAI, it's the infrastructure layer several of them run on, a major OpenAI investor and distribution partner, and now, through MAI, a first-party model developer competing with the labs it also hosts. Whether an oversight body with "broad representation" that still includes Microsoft in three different capacities at once is actually broader than Amodei's single-evaluator example is a question Nadella's post raises without answering.
"Both closed and open-source models can thrive" — checked against Microsoft's own record
Nadella writes that spreading AI's benefits "requires a frontier ecosystem in which both closed and open-source models can thrive." On the ecosystem level, Microsoft's actions back the claim: it was a lead signatory on the industry coalition that fought off a push to ban Chinese open-weight models in July, and it's built its Foundry platform around distributing other labs' open models, expanding a multi-billion-dollar partnership with Mistral the same month specifically so regulated customers could run open weights on infrastructure they control.
Microsoft's own first-party contributions to that ecosystem tell a different story. Every MAI model this blog has tracked has shipped closed, and the most recent one, MAI-Cyber-1-Flash, isn't available as a standalone model at all — it ships bundled inside a product, MDASH, with tenant isolation and no direct model access. "Both closed and open-source models can thrive" is true of the ecosystem Microsoft sells access to. It has not yet been true of anything Microsoft has built itself.
The "hill climbing machine" is a product Microsoft already announced
The paragraph on enterprise control reads, out of context, like a safety principle: "Every organization should be able to build its own continuous learning loop/hill climbing machine, without becoming dependent on any one model provider, and have the ability to embed its own knowledge into models and weights they control." In context, it's closer to a restatement of a product Microsoft AI CEO Mustafa Suleyman announced at Build in June, three months before this week's debate existed. "Hill-climbing machine" was Suleyman's own term then for Microsoft's model-improvement infrastructure, and "continuous learning loop" describes Frontier Tuning, the system Microsoft introduced the same day that lets enterprises train custom versions of MAI models on their own proprietary data, kept inside their own infrastructure.
That doesn't make the underlying point wrong — enterprise lock-in to a single model provider is a real concern, independent of who's raising it — but it's worth naming plainly, the same way this blog has named it for everyone else who's spoken this week. Amodei's own pacing proposal comes from the company that would supply the embedded evaluators. Chollet's ARC-AGI work benefits from a race toward more general, harder-to-game capability benchmarks. And Nadella's safety post arrives with a three-month-old enterprise product already built to match its vocabulary. Everyone arguing about how to pace the frontier this week has also been describing, more or less exactly, what their own company already sells.
The one part of this post that resolves on its own timeline
Unlike most of what's been said this week, the Code of Conduct commitment has a specific, near-term test: it was due today. As of this writing, this post could not confirm the document has been published with visible content — no principles, thresholds, or enforcement mechanism have surfaced in coverage of Nadella's announcement itself. That puts it in the same category as OpenAI's "more to share soon" on embedded evaluators and Meta's repeated, so-far-unfulfilled promises to open Muse's weights covered in this week's other posts: a specific, checkable commitment, not yet checkable, because the thing it commits to hasn't shown up yet.
What would make it worth taking seriously as more than a restated product announcement is exactly what Nadella's own "broad representation" line implies it should have: who actually gets to comment during the "public consultation," whether the resulting document constrains Microsoft's own first-party models in ways that cost it something, and whether it says anything at all about the MAI models that already shipped closed. A code of conduct that only ever describes models Microsoft hasn't built yet would answer none of the questions this week has actually raised.