Do coding agents recommend Azure Blob Storage?
Azure Blob Storage was chosen in 15% of 281 judged file storage sessions, ranking second.
Azure Blob Storage was chosen in 15% of 281 judged file storage sessions, ranking second. It was also raised as a candidate in 59 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in file storage inside a realistic codebase. Not what a chat assistant says about Azure Blob Storage. What an agent actually installed.
One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about file storage in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | File storage |
| Sessions in the category | 281 |
| Sessions where Azure Blob Storage was chosen | 42 |
| Install share | 15% |
| Rank in category | 2 of 6 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 59 |
| Chosen when considered | 42% |
| Site | azure.microsoft.com |
By agent
Claude Code, Codex, Cursor and Muse Code agree closely on Azure Blob Storage, choosing it at rates within 4 points of each other. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose Azure Blob Storage | Share |
|---|---|---|---|
| Claude Code | 54 | 9 | 17% |
| Codex | 78 | 12 | 15% |
| Cursor | 54 | 9 | 17% |
| Grok Build CLI | 23 | 3 | 13% |
| Muse Code | 72 | 9 | 13% |
By who was asking
Azure Blob Storage does much better with one kind of buyer than another. It won 50% of sessions asked as enterprise team and 0% of those asked as senior engineer.
| Who is asking | Sessions | Chose Azure Blob Storage | Share |
|---|---|---|---|
| Vibe coder | 32 | 0 | 0% |
| Junior developer | 66 | 0 | 0% |
| Senior engineer | 99 | 0 | 0% |
| Enterprise team | 84 | 42 | 50% |
What Azure Blob Storage was up against
The full ranking in file storage, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Amazon S3 | 150 | 53% |
| 2 | Azure Blob Storage (this page) | 42 | 15% |
| 3 | Google Cloud Storage | 42 | 15% |
| 4 | Cloudflare R2 | 35 | 12% |
| 5 | Built in-house (no product adopted) | 8 | 3% |
| 6 | Tigris | 2 | 1% |
| 7 | MinIO | 2 | 1% |
What this means
A solid second or third position in a category means the agent is genuinely choosing rather than reaching automatically. That is a winnable position, because the inputs it uses can be changed.
The fastest gains are usually in the sessions that were nearly won: read them, find the step where the agent moved on, and fix that step.
Where these numbers come from
The 281 sessions in file storage 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 file storage run can be replayed on the board.
If you work on Azure Blob Storage: 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 Azure Blob Storage?
Yes. Azure Blob Storage was chosen in 42 of the 281 judged sessions in file storage, a 15% install share, ranking second in its category.
Does Claude Code recommend Azure Blob Storage?
In 9 of the 54 sessions in file storage run with Claude Code, which is 17%.
Do different coding agents treat Azure Blob Storage differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 13% and 17% 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.
How often is Azure Blob Storage considered but not chosen?
It was raised as a candidate in 59 sessions without being chosen, and chosen in 42. That is a 42% conversion from considered to chosen.
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.