Do coding agents recommend Azure Communication Services?
Azure Communication Services was chosen in 14% of 351 judged email sending sessions, ranking third.
Azure Communication Services was chosen in 14% of 351 judged email sending sessions, ranking third. It was also raised as a candidate in 22 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 email sending inside a realistic codebase. Not what a chat assistant says about Azure Communication Services. What an agent actually installed.
The numbers
| Category | Email sending |
| Sessions in the category | 351 |
| Sessions where Azure Communication Services was chosen | 49 |
| Install share | 14% |
| Rank in category | 3 of 7 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 22 |
| Chosen when considered | 69% |
| Site | azure.microsoft.com |
By agent
Claude Code, Codex, Cursor and Muse Code land within 7 points of each other on Azure Communication Services, which is closer than most products in this experiment manage. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose Azure Communication Services | Share |
|---|---|---|---|
| Claude Code | 83 | 12 | 14% |
| Codex | 107 | 11 | 10% |
| Cursor | 90 | 14 | 16% |
| Grok Build CLI | 18 | 3 | 17% |
| Muse Code | 53 | 9 | 17% |
By who was asking
Azure Communication Services does much better with one kind of buyer than another. It won 46% of sessions asked as enterprise team and 5% of those asked as senior engineer.
| Who is asking | Sessions | Chose Azure Communication Services | Share |
|---|---|---|---|
| Senior engineer | 275 | 14 | 5% |
| Enterprise team | 76 | 35 | 46% |
What Azure Communication Services was up against
The full ranking in email sending, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Resend | 115 | 33% |
| 2 | Postmark | 95 | 27% |
| 3 | Azure Communication Services (this page) | 49 | 14% |
| 4 | SendGrid | 44 | 13% |
| 5 | Amazon SES | 41 | 12% |
| 6 | Generic SMTP | 4 | 1% |
| 7 | Built in-house (no product adopted) | 2 | 1% |
| 8 | Paubox | 1 | 0% |
What this means
Agents almost never raise Azure Communication Services without choosing it: 22 sessions raised against 49 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 351 sessions in email sending are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every email sending run can be replayed on the board.
If you work on Azure Communication Services: 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 Communication Services?
Yes. Azure Communication Services was chosen in 49 of the 351 judged sessions in email sending, a 14% install share, ranking third in its category.
Does Claude Code recommend Azure Communication Services?
In 12 of the 83 sessions in email sending run with Claude Code, which is 14%.
Do different coding agents treat Azure Communication Services differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 10% and 17% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 92 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 Communication Services considered but not chosen?
It was raised as a candidate in 22 sessions without being chosen, and chosen in 49. That is a 69% conversion from considered to chosen.
Where this comes from
Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.