Do coding agents recommend Azure AI Content Understanding?
Azure AI Content Understanding was chosen in 3% of 360 judged document processing sessions, ranking eighth. Measured with Claude Code, Codex and Cursor.
Azure AI Content Understanding was chosen in 3% of 360 judged document processing sessions, ranking eighth. It was also raised as a candidate in 9 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in document processing inside a realistic codebase. Not what a chat assistant says about Azure AI Content Understanding. What an agent actually installed.
The numbers
| Category | Document processing |
| Sessions in the category | 360 |
| Sessions where Azure AI Content Understanding was chosen | 11 |
| Install share | 3% |
| Rank in category | 8 of 30 |
| Codebases it won in | 4 |
| Raised as a candidate, not chosen | 9 |
| Chosen when considered | 55% |
| Site | azure.microsoft.com |
By agent
With 11 wins spread across three agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.
| Agent | Sessions | Chose Azure AI Content Understanding | Share |
|---|---|---|---|
| Claude Code | 120 | 0 | 0% |
| Codex | 120 | 11 | 9% |
| Cursor | 120 | 0 | 0% |
By who was asking
Azure AI Content Understanding performs similarly across the four kinds of buyer, from 0% to 7%. That is unusual: the category leader changed with the persona in 21 of the 26 categories we measured.
| Who is asking | Sessions | Chose Azure AI Content Understanding | Share |
|---|---|---|---|
| Vibe coder | 30 | 0 | 0% |
| Junior developer | 180 | 3 | 2% |
| Senior engineer | 120 | 8 | 7% |
| Enterprise team | 30 | 0 | 0% |
What Azure AI Content Understanding was up against
The full ranking in document processing, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Anthropic Claude | 87 | 24% |
| 2 | Azure AI Document Intelligence | 76 | 21% |
| 3 | Amazon Textract | 37 | 10% |
| 4 | Google Cloud Document AI | 31 | 9% |
| 5 | Google Gemini | 17 | 5% |
| 6 | Ocrolus | 15 | 4% |
| 7 | Reducto | 13 | 4% |
| 8 | Azure AI Content Understanding (this page) | 11 | 3% |
What this means
Agents almost never raise Azure AI Content Understanding without choosing it: 9 sessions raised against 11 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 360 sessions in document processing are part of a published set of 7,385, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every document processing run can be replayed on the board.
If you work on Azure AI Content Understanding: 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 AI Content Understanding?
Yes. Azure AI Content Understanding was chosen in 11 of the 360 judged sessions in document processing, a 3% install share, ranking eighth in its category.
Does Claude Code recommend Azure AI Content Understanding?
In 0 of the 120 sessions in document processing run with Claude Code, which is 0%.
Do different coding agents treat Azure AI Content Understanding differently?
Not much. The three agents chose it at similar rates, between 0% and 9% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 84 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 AI Content Understanding considered but not chosen?
It was raised as a candidate in 9 sessions without being chosen, and chosen in 11. That is a 55% conversion from considered to chosen.
Where this comes from
Armature ran 7,385 judged sessions with Claude Code, Codex and Cursor inside 84 realistic codebases, and published every run. The numbers on this page come from that work.