Do coding agents recommend Microsoft 365 eSignature?
Microsoft 365 eSignature was chosen in 9% of 232 judged e-signature sessions, ranking fourth.
Microsoft 365 eSignature was chosen in 9% of 232 judged e-signature sessions, ranking fourth. It was also raised as a candidate in 16 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 e-signature inside a realistic codebase. Not what a chat assistant says about Microsoft 365 eSignature. 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 e-signature in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | E-signature |
| Sessions in the category | 232 |
| Sessions where Microsoft 365 eSignature was chosen | 20 |
| Install share | 9% |
| Rank in category | 4 of 13 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 16 |
| Chosen when considered | 56% |
| Site | microsoft.com |
By agent
Claude Code, Codex, Cursor and Muse Code land within 11 points of each other on Microsoft 365 eSignature, 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 Microsoft 365 eSignature | Share |
|---|---|---|---|
| Claude Code | 44 | 6 | 14% |
| Codex | 71 | 2 | 3% |
| Cursor | 52 | 5 | 10% |
| Grok Build CLI | 15 | 2 | 13% |
| Muse Code | 50 | 5 | 10% |
By who was asking
Microsoft 365 eSignature performs similarly across the four kinds of buyer, from 0% to 11%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.
| Who is asking | Sessions | Chose Microsoft 365 eSignature | Share |
|---|---|---|---|
| Junior developer | 86 | 9 | 10% |
| Senior engineer | 50 | 0 | 0% |
| Enterprise team | 96 | 11 | 11% |
What Microsoft 365 eSignature was up against
The full ranking in e-signature, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | DocuSign | 87 | 38% |
| 2 | Dropbox Sign | 44 | 19% |
| 3 | Built in-house (no product adopted) | 32 | 14% |
| 4 | YouTrust | 23 | 10% |
| 5 | Microsoft 365 eSignature (this page) | 20 | 9% |
| 6 | Documenso | 6 | 3% |
| 7 | Signable | 5 | 2% |
| 8 | SignWell | 4 | 2% |
What this means
Agents almost never raise Microsoft 365 eSignature without choosing it: 16 sessions raised against 20 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 232 sessions in e-signature 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 e-signature run can be replayed on the board.
If you work on Microsoft 365 eSignature: 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 365 eSignature?
Yes. Microsoft 365 eSignature was chosen in 20 of the 232 judged sessions in e-signature, a 9% install share, ranking fourth in its category.
Does Claude Code recommend Microsoft 365 eSignature?
In 6 of the 44 sessions in e-signature run with Claude Code, which is 14%.
Do different coding agents treat Microsoft 365 eSignature differently?
Yes, and by a wide margin. Claude Code chose it in 14% of its runs and Codex in 3%.
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 Microsoft 365 eSignature considered but not chosen?
It was raised as a candidate in 16 sessions without being chosen, and chosen in 20. That is a 56% 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.