From the experiment

Do coding agents recommend Azure Communication Services Email?

Azure Communication Services Email was chosen in 14% of 208 judged email sending sessions, ranking third. Measured with Claude Code, Codex and Cursor.

Published September 3, 2026 Read as Markdown

Azure Communication Services Email was chosen in 14% of 208 judged email sending sessions, ranking third. It was also raised as a candidate in 13 further sessions without being chosen.

This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in email sending inside a realistic codebase. Not what a chat assistant says about Azure Communication Services Email. What an agent actually installed.

The numbers

CategoryEmail sending
Sessions in the category208
Sessions where Azure Communication Services Email was chosen29
Install share14%
Rank in category3 of 6
Codebases it won in2
Raised as a candidate, not chosen13
Chosen when considered69%
Siteazure.microsoft.com

By agent

The three agents land within 6 points of each other on Azure Communication Services Email, which is closer than most products in this experiment manage.

AgentSessionsChose Azure Communication Services EmailShare
Claude Code65914%
Codex71811%
Cursor721217%

By who was asking

Azure Communication Services Email does much better with one kind of buyer than another. It won 50% of sessions asked as enterprise team and 4% of those asked as senior engineer.

Who is askingSessionsChose Azure Communication Services EmailShare
Senior engineer16474%
Enterprise team442250%

What Azure Communication Services Email was up against

The full ranking in email sending, from the same sessions:

#ProductRuns wonShare
1Resend7436%
2Postmark5727%
3Azure Communication Services Email (this page)2914%
4Amazon SES2412%
5SendGrid2311%
6Generic SMTP10%

What this means

Agents almost never raise Azure Communication Services Email without choosing it: 13 sessions raised against 29 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 208 sessions in email sending are part of a published set of 5,292, 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 Email: 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 Email?

Yes. Azure Communication Services Email was chosen in 29 of the 208 judged sessions in email sending, a 14% install share, ranking third in its category.

Does Claude Code recommend Azure Communication Services Email?

In 9 of the 65 sessions in email sending run with Claude Code, which is 14%.

Do different coding agents treat Azure Communication Services Email differently?

Not much. The three agents chose it at similar rates, between 11% and 17% of their runs.

How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 51 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 Email considered but not chosen?

It was raised as a candidate in 13 sessions without being chosen, and chosen in 29. That is a 69% conversion from considered to chosen.

Where this comes from

Armature ran 5,292 judged sessions with Claude Code, Codex and Cursor inside 51 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages