From the experiment

Do coding agents recommend Microsoft Entra ID?

Microsoft Entra ID was chosen in 11% of 724 judged authentication sessions, ranking fourth.

Published October 14, 2026 Read as Markdown

Microsoft Entra ID was chosen in 11% of 724 judged authentication sessions, ranking fourth. It was also raised as a candidate in 45 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 authentication inside a realistic codebase. Not what a chat assistant says about Microsoft Entra ID. What an agent actually installed.

The numbers

CategoryAuthentication
Sessions in the category724
Sessions where Microsoft Entra ID was chosen80
Install share11%
Rank in category4 of 28
Codebases it won in3
Raised as a candidate, not chosen45
Chosen when considered64%
Siteentra.microsoft.com

By agent

Claude Code, Codex, Cursor, Grok Build CLI and Muse Code agree closely on Microsoft Entra ID, choosing it at rates within 2 points of each other.

AgentSessionsChose Microsoft Entra IDShare
Claude Code1331411%
Codex2042110%
Cursor1331411%
Grok Build CLI50612%
Muse Code2042512%

By who was asking

Microsoft Entra ID does much better with one kind of buyer than another. It won 48% of sessions asked as enterprise team and 0% of those asked as junior developer.

Who is askingSessionsChose Microsoft Entra IDShare
Vibe coder9800%
Junior developer22300%
Senior engineer24342%
Enterprise team1607648%

What Microsoft Entra ID was up against

The full ranking in authentication, from the same sessions:

#ProductRuns wonShare
1Auth018025%
2WorkOS AuthKit13118%
3Clerk8612%
4Microsoft Entra ID (this page)8011%
5Built in-house (no product adopted)659%
6Better Auth294%
7Amazon Cognito233%
8Keycloak223%

What this means

Agents almost never raise Microsoft Entra ID without choosing it: 45 sessions raised against 80 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 724 sessions in authentication 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 authentication run can be replayed on the board.

If you work on Microsoft Entra ID: 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 Entra ID?

Yes. Microsoft Entra ID was chosen in 80 of the 724 judged sessions in authentication, a 11% install share, ranking fourth in its category.

Does Claude Code recommend Microsoft Entra ID?

In 14 of the 133 sessions in authentication run with Claude Code, which is 11%.

Do different coding agents treat Microsoft Entra ID differently?

Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 10% and 12% 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 Microsoft Entra ID considered but not chosen?

It was raised as a candidate in 45 sessions without being chosen, and chosen in 80. That is a 64% 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.

Read next

All library pages