Head to head · OAuth for agents · October 2026 research run

Microsoft Entra Agent ID vs Proof MCP

Microsoft Entra Agent ID scores 75.7 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in 6 of 7 scored categories. Proof MCP leads on payments & pricing. Both do oauth for agents.

Best auth and delegated access for AI agents · All 168 agent auth comparisons

Best contract, proposal and e-signature APIs for AI agents · All 59 e-signatures comparisons

Which one, for what

Microsoft Entra Agent ID BB

Best for Organisations already on Microsoft Entra that want each agent to be a governed directory identity with tokens for Microsoft Graph, Azure and their own APIs.

Ahead on

  • Reliability, 91 against 60
  • Schema & documentation, 87 against 33
  • Agent ergonomics, 71 against 32
  • Security & auth, 83 against 78
  • Maintenance & community, 80 against 68
  • Transparency & trust, 75 against 52

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Conditional Access, ID Protection and governance for agents need Microsoft Agent 365, listed at $15 a user a month on yearly billing

Proof MCP D

Best for Agents that must show a site who they act for and that the person approved, and agents sending documents for e-signature or notarisation.

Ahead on

  • Payments & pricing, 39 against 30

Watch for

The MCP server answers initialize with 401, and no public page lists its tools or their schemas

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Microsoft Entra Agent ID +54

Microsoft Entra Agent ID 87

agentIdentity is in Microsoft's public Graph v1.0 OpenAPI file (25). learn.microsoft.com returns Markdown when asked with Accept: text/markdown, but learn.microsoft.com/llms.txt returned 404 (8). Concept, design-pattern and best-practice pages say when to use each flow and when to pick the sidecar over the .NET library (16). Graph resources are typed with required fields listed, though agentIdentity is an open type that inherits servicePrincipal properties that don't all apply (12). Request and response examples on each reference page and a list of 17 Agent ID error codes, without the HTTP status for each (11). v1.0 and beta versioning with a monthly dated Graph changelog and Entra release notes (15).

Proof MCP 33

No public tool reference, and initialize answered 401 without a token, so the tools' input schemas couldn't be read (0 of 25, unchecked). llms.txt on dev.proof.com, a Markdown page for agents at api.proof.com/agents and an agent-skills index with digests (10). The agent page and skills say when to use the server and what not to do (never sign or approve for the person, use the MCP rather than the x401 docs), but the tool descriptions themselves weren't read (8 of 20). Typed inputs unread (0 of 15). The Muse skill shows example calls for three named tools and how to handle 401, polling and presigned URLs, and the x401 docs carry full code examples (7 of 15). x401 is versioned (0.1.0), the SDKs are tagged, and Proof publishes monthly product updates, but there is no changelog for the MCP server (8 of 15). 0 + 10 + 8 + 0 + 7 + 8 = 33.

Agent ergonomics Microsoft Entra Agent ID +39

Microsoft Entra Agent ID 71

List calls take $select, $top, $filter, $search and $count, with a default and maximum page of 100 (20). OData paging and filtering work on the main collection, but ownedObjects, deletedItems and owners can't filter by agent type and need client-side filtering (17). Named error codes such as AgentIdentity_CredentialsNotSupported say what to change (16). No idempotency key for creates, and sequential creates need retries. Token requests are safe to repeat (8). Creating an identity needs three fields, but getting a token is a two-step exchange that Microsoft's docs call complex and error-prone by hand, with an in-process library only for .NET and a sidecar container for everything else (10).

Proof MCP 32

Tool count and size unknown, since the list is behind sign-in. Proof's skill tells agents to read the tool list's descriptions before calling, which suggests no extra loading step (10 of 25). Long steps return retry_after_seconds for polling. No pagination or output controls found (5 of 20). The skill documents what a 401 means and what to tell the user. No error reference for the MCP server (5 of 20). Idempotency and tool annotations unread (0 of 20). Nothing for the person to create, and no client ID or secret. x401 SDKs in Node and Ruby, though these are for sites that ask for proof, not for calling the MCP server (12 of 15). 10 + 5 + 5 + 0 + 12 = 32.

Reliability Microsoft Entra Agent ID +31

Microsoft Entra Agent ID 91

Microsoft's SLA page for Entra ID points to the Azure status history for incidents, and that page was readable with dated entries and reviews (20). The 90 days to 1 November show two Azure incidents, on 29 September (Azure OpenAI and AI services) and 30 September 2026 (networking gateways, 20:30 UTC to 02:15 UTC on 1 October), and none after 30 September when the page was re-read on 1 November. The 23 July West US network fault, which listed Azure AD B2C, has left the window. Neither names Entra ID, and Microsoft's SLA performance page, updated 7 October and re-read on 1 November, reports 99.999 per cent authentication availability for July, August and September 2026. We scored between clean and minor because the page lists only wide incidents (25). Graph identity limits are published as numbers, such as 3,000 writes per 2 minutes 30 seconds per app and tenant, per the 8 October check (15). 429 carries Retry-After and the FAQ asks for exponential backoff, but there is no idempotency key and back-to-back creates can fail with 400 during replication (11). An SLA for Microsoft Entra ID is published and attainment is reported monthly. The SLA document itself didn't load for us (10). Agent ID has been generally available since April 2026 and the agentIdentity API is on Graph v1.0 (10). 20+25+15+11+10+10 = 91.

Proof MCP 60

An Atlassian Statuspage at status.proof.com, linked from the Trust Centre, with an incident history feed (20). The feed's latest incident is 20 July 2026, so the 90 days to 18 November 2026 are clean. The page covers the Proof platform, not the MCP server by name (30). No rate limits found for the MCP server or the REST API's error pages (0). No 429 or Retry-After guidance. The Muse skill documents polling with retry_after_seconds and one retry with a fresh credential after a 401 (5 of 15). Premium and Enterprise plans list dedicated SLAs, but no SLA terms are published (0). Proof calls the 18 November 2026 release the first version of the Proof MCP, and the x401 page marks the protocol as in active development (5 of 10). 20 + 30 + 0 + 5 + 0 + 5 = 60.

Transparency & trust Microsoft Entra Agent ID +23

Microsoft Entra Agent ID 75

Closed service under the Microsoft APIs terms of use, last updated October 2025, with MIT SDK source (15). The privacy statement was updated in September 2026, Entra publishes a data residency page and log retention periods, and we didn't read the DPA (20). Microsoft Graph gives at least 24 months' notice before retiring a GA API or version, while several Agent ID operations are still on /beta, which can change without notice (18). Entra documents where tenant data is stored by geography. We didn't read the sub-processor list (10).

Proof MCP 52

The MCP server is closed, under Proof's general terms (Delaware law). The x401 specification and SDKs are Apache-2.0 (20 of 30). The privacy policy (Notarize, Inc. dba Proof.com) lists what is collected and gives retention by category for California residents, but says Proof may use the information people give to train, fine-tune or enhance AI systems, with consent taken by use (12 of 30). No deprecation policy or dated notice found (0). Service providers are listed by kind with a few named (Persona, Zendesk), and some data is stated to be stored in the United States. No full subprocessor list was read (10 of 20). 20 + 12 + 0 + 10 = 42.

Maintenance & community Microsoft Entra Agent ID +12

Microsoft Entra Agent ID 80

Microsoft.Identity.Web.AgentIdentities 4.16.1 was published to NuGet on 13 October 2026, 19 days before this check, a release the changelog describes as security fixes and reliability improvements (30). Three releases in the 90 days from 3 August, 4.15.0 (21 September), 4.16.0 (1 October) and 4.16.1 (13 October), and Graph changelog entries for agent identities in September and October (agentUser managerApplications promoted to v1.0). The repository's changelog has 4.17.0 notes from 30 October that weren't on NuGet on 1 November (20). A closed service with public release notes and a public SDK tracker that showed 340 open issues on 8 October, not re-read on 1 November. We didn't read reply times (10). The current in-process SDK is .NET only, with the sidecar container for other languages (12). Azure Pipelines and CodeQL are configured, a 14 October commit updates cryptography packages for security advisories, and a 28 October commit raises dependency minimums to address vulnerabilities (8). 30+20+10+12+8 = 80.

Proof MCP 68

The Proof MCP's first release in ChatGPT was announced on 18 November 2026 (30). x401-node has tags up to v0.3.4 (commit of 17 November 2026) and proof-vc-common up to v0.7.1, with 24 and 39 commits since 20 August 2026 (20). A support site and monthly product updates. GitHub issue response wasn't checked (8 of 25). Not in the official MCP registry (searches for mcp.proof.com and com.proof found nothing of Proof's) (0). x401-node and proof-vc-common run CI and Dependabot (10). 30 + 20 + 8 + 0 + 10 = 68.

Payments & pricing Proof MCP +9

Microsoft Entra Agent ID 30

No x402, MPP or L402 (0). Agent 365 is listed at $15 a user a month and Microsoft 365 E7 at $99, and the docs say Agent ID is available to all Entra customers, but no page gives a per-agent price or says plainly which parts are free (10). Entra ID Free comes with a Microsoft cloud subscription. We didn't establish whether a new tenant can be opened without a card, so this line gets half (10). A person creates the tenant, holds an Agent ID role and creates the blueprint before any agent can act (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Proof MCP 39

x402 (v2, exact scheme, USDC on Base) only on the x401 signatures endpoint, which a verifier with no card on file pays per presentation. Nothing the MCP server does is paid by x402 (4 of 10). Business plan prices are public per transaction ($25 a notarisation meeting, $15 an extra seal, $4 an e-signature, $4 an identity check), but no price for an x401 presentation or for a person using the MCP was found (20 of 30). Business Pro costs $0 a month plus transaction fees, with a 14-day trial of Pro+. Whether a person pays to set up the Proof credential wasn't found (15 of 30). A person must sign in and verify their identity, by design (0 of 30). 4 + 20 + 15 + 0 = 39.

Score by category

CategoryWeightMicrosoft Entra Agent IDProof MCPEdge
Reliability16%9160Microsoft Entra Agent ID +31
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8733Microsoft Entra Agent ID +54
Agent ergonomics13%7132Microsoft Entra Agent ID +39
Security & auth14%8378Microsoft Entra Agent ID +5
Payments & pricing10%3039Proof MCP +9
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8068Microsoft Entra Agent ID +12
Transparency & trust7%7552Microsoft Entra Agent ID +23
Negative events≤1500
TotalBB 75.7/100D 51.6/100

Facts side by side

FactMicrosoft Entra Agent IDProof MCP
KindHTTP APIMCP server
VendorMicrosoftProof
Hosted endpointhttps://graph.microsoft.com/v1.0/servicePrincipals/microsoft.graph.agentIdentityhttps://mcp.proof.com/mcp
TransportsHTTPStreamable HTTP
AuthOAuthOAuth
PricingFreemiumPay per use
x402noon some endpoints
LicenceProprietary service under Microsoft's terms. Microsoft.Identity.Web and the Auth SDK sidecar source are MITProprietary (MCP server), x401 specification and SDKs Apache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-132026-11-18
Terms last updated2025-10-01no date given
Privacy policy last updated2026-09-01no date given
Customer content may train modelsyesyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity787 starsnone
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

Microsoft Entra Agent ID

Agent identities hold no credentials of their own, and Entra refuses high-privilege roles and Graph permissions for them. The token flow is a two-step exchange that Microsoft's own docs call complex and error-prone to implement by hand, and Conditional Access, risk detection and governance for agents need a paid Agent 365 licence.

Proof MCP

Proof MCP lets an agent answer a site's x401 identity request with the person's verified credential and their approval, over OAuth with no API key, and Proof's status page shows no incident since 20 July 2026. Its tool list sits behind sign-in, no tool reference or rate limits are published, and the privacy policy allows training AI on user data.

Before you call either

Microsoft Entra Agent ID

  1. Request tokens in two steps. The blueprint gets an exchange token with fmi_path set to the agent identity's client ID, then the agent identity trades it for a resource token
  2. Retry with exponential backoff when a create returns 400 Object with id not found straight after creating its parent object
  3. Send displayName, agentIdentityBlueprintId and a sponsor reference when creating an agent identity. All three are required
  4. Don't use the interactive /authorize flow. Agent identities are confidential clients and can't sign in to a page
  5. Keep the sidecar off any public network. Its /AuthorizationHeader endpoint hands out tokens to whoever can reach it

Proof MCP

  1. Read the server instructions and every tool description before your first call, as Proof's skill asks
  2. If a site returns 401 with a PROOF-REQUEST header, pass the header value unchanged to x401_start_presentation
  3. Show the person any approval link first, then poll x401_get_presentation or get_transaction_status after each retry_after_seconds
  4. Never ask the user for a Proof API key or token. The client registers itself with OAuth, scope mcp.read
  5. Share a presigned download URL only with the user, since anyone holding it can download the file until it expires

Questions

Which is better for AI agents, Microsoft Entra Agent ID or Proof MCP?

Microsoft Entra Agent ID scores 75.7 (BB) on agent readiness against Proof MCP's 51.6 (D), and leads in 6 of 7 scored categories. Proof MCP leads on payments & pricing.

Do Microsoft Entra Agent ID and Proof MCP need an API key?

Both use an OAuth sign-in.

Can an agent call Microsoft Entra Agent ID and Proof MCP without installing anything?

Yes. Microsoft Entra Agent ID has a hosted endpoint at https://graph.microsoft.com/v1.0/servicePrincipals/microsoft.graph.agentIdentity and Proof MCP at https://mcp.proof.com/mcp.

Other comparisons with Microsoft Entra Agent ID or Proof MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.