From the experiment

Do coding agents recommend Microsoft Azure?

Coding agents raised Microsoft Azure in 105 of 359 judged cloud sessions and chose it in none of them.

Published October 14, 2026 Read as Markdown

Coding agents raised Microsoft Azure in 105 of 359 judged cloud sessions and chose it in none of them.

This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in cloud inside a realistic codebase. Not what a chat assistant says about Microsoft Azure. What an agent actually installed.

The numbers

CategoryCloud
Sessions in the category359
Sessions where Microsoft Azure was chosen0
Install share0%
Raised as a candidate, not chosen105
Chosen when considered0%
Siteazure.microsoft.com

Which agents raised Microsoft Azure

Every agent considered it and none adopted it. Cursor raised it most often, in 56% of its cloud sessions.

AgentSessionsRaised Microsoft AzureChose it
Claude Code9029 (32%)0
Codex10815 (14%)0
Cursor8950 (56%)0
Grok Build CLI184 (22%)0
Muse Code547 (13%)0

Which buyers it came up for

It surfaced most for requests written as enterprise team, in 33% of those sessions. Knowing which buyer already has the product in mind tells you which pages to fix first.

Who is askingSessionsRaised it
Senior engineer23965 (27%)
Enterprise team12040 (33%)

What Microsoft Azure was up against

The full ranking in cloud, from the same sessions:

#ProductRuns wonShare
1AWS22663%
2Google Cloud6017%
3Cloudflare216%
4Upstash185%
5Inngest93%
6Cloudflare + Upstash62%
7Vercel Queues31%
8Built in-house (no product adopted)21%

What this means

Raised 105 times and chosen none is a specific, diagnosable result, and a better starting position than being unknown. The agent has the product in mind. It reached the shortlist 105 times. Something then lost every one of those sessions.

In our data the causes, in the order they occur:

  • The quickstart does not run when pasted, so the agent abandoned it mid-integration.
  • The documentation describes an interface that changed, so the generated code failed.
  • The product name and the package name differ, so the install step went wrong.
  • The fit was genuinely wrong for the repository, which is fine and worth knowing.

All but the last are fixable in days, and the reason is written down in the session transcript.

Where these numbers come from

The 359 sessions in cloud are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.

Every cloud run can be replayed on the board.

If you work on Microsoft Azure: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.

<!-- generated by scripts/write-data-pages.mjs -->

Common questions

Do coding agents recommend Microsoft Azure?

They raise it but do not choose it. Across 105 sessions where Microsoft Azure came up as a candidate, agents chose something else every time.

Does Claude Code recommend Microsoft Azure?

In 0 of the 90 sessions in cloud run with Claude Code, which is 0%.

Do different coding agents treat Microsoft Azure differently?

Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 0% and 0% of their runs.

How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 110 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.

Where this comes from

Armature ran 15,287 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages