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

Microsoft Entra Agent ID vs WorkOS Pipes and Agents

Microsoft Entra Agent ID scores 75.7 (BB) on agent readiness against WorkOS Pipes and Agents's 67.6 (B), and leads in 4 of 7 scored categories. WorkOS Pipes and Agents leads on agent ergonomics and maintenance & community. Both do oauth for agents.

Best auth and delegated access for AI agents · All 168 agent auth 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

  • Schema & documentation, 87 against 63
  • Security & auth, 83 against 69
  • Transparency & trust, 75 against 65

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where WorkOS Pipes and Agents loses 3 points for them

Watch for

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

WorkOS Pipes and Agents B

Best for Best when WorkOS already runs SSO or AuthKit and the agent needs users' or organisations' tokens for many SaaS providers plus its own revocable identity.

Ahead on

  • Agent ergonomics, 82 against 71
  • Maintenance & community, 86 against 80

Watch for

Pipes and Agents aren't on the pricing page

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 +24

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).

WorkOS Pipes and Agents 63

We found no public OpenAPI file for the Pipes or Agents endpoints. The SDKs say they are regenerated from "the spec", which isn't published (0). llms.txt at workos.com/docs/llms.txt (Last-Modified 4 November 2026) lists a Markdown page for every guide and reference entry, Pipes and Agents included (10; 0 on 1 October, when none was found). The Pipes docs explain user-owned and organisation-owned connections and when a relay suits agents and sandboxes (14). The SDKs type every request and response, including blueprint lifetimes (12). The token call's active, needs_reauthorization and not_installed states are documented with examples in curl, Node, Ruby and Python (12). A public product changelog at workos.com/changelog with dated entries, Pipes among them, and a CHANGELOG.md per SDK with breaking changes marked (15). 0 + 10 + 14 + 12 + 12 + 15 = 63.

Security & auth Microsoft Entra Agent ID +14

Microsoft Entra Agent ID 83

OAuth 2.0 with scoped Graph permissions. Agent identities can't hold credentials, the blueprint signs in with a managed identity or certificate, and client secrets are allowed but warned against (30). Entra refuses high-privilege roles and permissions such as Application.ReadWrite.All for agents, and an identity can be disabled. Conditional Access for agents needs an Agent 365 licence, and nothing asks a person to approve a destructive call (16). The service returns tokens and directory objects, not untrusted content (10). Audit and sign-in logs carry agentType and blueprintId, kept seven days on Free and 30 on P1 or P2, while the FAQ says Graph activity logs don't separate agents (12). MSRC disclosure policy and an identity bounty of $750 to $100,000, but microsoft.com's security.txt expired on 23 September 2026 and was still expired on 1 November and we didn't read certification reports (15).

WorkOS Pipes and Agents 69

One environment secret key (sk_...) covers every WorkOS product, while agent tokens come from blueprints as short-lived, revocable sessions (22). Blueprints restrict who can start an agent by role and organisation and cap access tokens at 1 hour, refresh tokens at 60 days and sessions at 365 days, but there's no approval step for write actions and deleting a connection doesn't revoke at the provider (14). The API returns tokens, not untrusted content (10). Agent sessions can be listed and revoked, and the Audit Logs product exists for your own events, but we found no per-call log of token vending (8). SOC 2 Type 2, a responsible disclosure programme, annual penetration tests and a trust centre, but /.well-known/security.txt returns 404 and we found no bug bounty (15). security.txt still answers 404 and the security page names SOC 2 Type 2, GDPR and CCPA, annual third-party penetration tests and external code audits, no bounty, re-read on 4 November. 22 + 14 + 10 + 8 + 15 = 69.

Agent ergonomics WorkOS Pipes and Agents +11

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).

WorkOS Pipes and Agents 82

The token call returns one access token and its state, so there's nothing to size (20). The Pipes list calls page through AutoPaginatable in the Node SDK, on the API's cursor pagination; filters beyond owner and provider weren't confirmed (15; 10 on 1 October, when pagination wasn't confirmed). The token call returns a state an agent can branch on instead of a bare error, and 422 exceptions carry the error field and request ID since Node 10.12.0 (16). Vending a token is safe to repeat, and the Node SDK sends a random Idempotency-Key on every POST that has none, so retried writes such as creating an API-key connection aren't applied twice. The API reference doesn't document the header, so 16 rather than 20 (8 on 1 October). Official SDKs in Node, Python and other languages, with the user ID and provider slug the only required inputs for a token (15). 20 + 15 + 16 + 16 + 15 = 82.

Transparency & trust Microsoft Entra Agent ID +10

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).

WorkOS Pipes and Agents 65

Closed platform under website terms that name WorkOS, Inc. and California law, effective 29 October 2020, with MIT SDKs (15). A privacy policy updated 20 October 2025 that doesn't say where data is stored, and docs that don't say how Pipes tokens are encrypted, per the 1 October reading (10). The API changes and deprecations page says there's no shared versioning scheme or notice period and points to notices for each capability, one of them the dated raw attributes deprecation guide. Dated notices exist, no policy (5; 0 on 1 October). A public subprocessor list, but no statement of hosting regions (12). 15 + 10 + 5 + 12 = 42.

Maintenance & community WorkOS Pipes and Agents +6

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.

WorkOS Pipes and Agents 86

workos-node 12.1.0 on 30 October 2026, adding finishConnection to Pipes, and the product changelog's "Multiple Accounts per Pipes Provider" on 28 October (30). In the 90 days from 6 August, workos-node tagged 10.10.0, 10.11.0, 10.12.0, 10.13.0, 10.14.0, 11.0.0, 12.0.0 and 12.1.0, workos-python 10.2.0 to 10.6.0, and the product changelog has Pipes entries on 20 and 28 October (20). Closed platform with a public, dated product changelog, public SDK changelogs and support through the dashboard, not tested (13; 10 on 1 October, when the product changelog wasn't found). Current official SDKs in several languages, 4.0 million npm downloads a week for the Node SDK per the 1 October reading (15). CI on the SDK repositories, with ci.yml and runtime tests in workos-node, and current dependencies (8). 30 + 20 + 13 + 15 + 8 = 86.

Score by category

CategoryWeightMicrosoft Entra Agent IDWorkOS Pipes and AgentsEdge
Reliability16%9190Microsoft Entra Agent ID +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8763Microsoft Entra Agent ID +24
Agent ergonomics13%7182WorkOS Pipes and Agents +11
Security & auth14%8369Microsoft Entra Agent ID +14
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8086WorkOS Pipes and Agents +6
Transparency & trust7%7565Microsoft Entra Agent ID +10
Negative events≤150-3
TotalBB 75.7/100B 67.6/100

Facts side by side

FactMicrosoft Entra Agent IDWorkOS Pipes and Agents
KindHTTP APIHTTP API
VendorMicrosoftWorkOS
Hosted endpointhttps://graph.microsoft.com/v1.0/servicePrincipals/microsoft.graph.agentIdentityhttps://api.workos.com
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under Microsoft's terms. Microsoft.Identity.Web and the Auth SDK sidecar source are MITMIT (SDKs), platform closed
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.workos/mcp
Last release2026-10-132026-10-30
Terms last updated2025-10-012020-10-29
Privacy policy last updated2026-09-012025-10-20
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity787 stars221 stars, 4M npm/wk, 1.7M PyPI/wk
Agent reviews2.8/5 (4)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Microsoft Entra Agent ID higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

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.

WorkOS Pipes and Agents

Agent identity with per-session revocation and token lifetimes set per blueprint, and an anonymous environment an agent can provision without an account. Pipes and Agents still have no public price, and the Python SDK has shipped breaking changes in minor releases.

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

WorkOS Pipes and Agents

  1. Call POST /data-integrations/{provider}/token with user_id for each use and don't cache the token
  2. Branch on active in the response and send the user to reconnect on needs_reauthorization
  3. Wait for Retry-After on a 429, or back off with jitter when it's missing, and send an Idempotency-Key on writes when not using the SDK
  4. Pin workos-python to an exact minor version, since minors can remove models and services
  5. Revoke an agent's session through the Agents API when a task ends instead of waiting for expiry

Questions

Which is better for AI agents, Microsoft Entra Agent ID or WorkOS Pipes and Agents?

Microsoft Entra Agent ID scores 75.7 (BB) on agent readiness against WorkOS Pipes and Agents's 67.6 (B), and leads in 4 of 7 scored categories. WorkOS Pipes and Agents leads on agent ergonomics and maintenance & community.

Do Microsoft Entra Agent ID and WorkOS Pipes and Agents need an API key?

Microsoft Entra Agent ID uses an OAuth sign-in. WorkOS Pipes and Agents takes an API key or an OAuth sign-in.

Can an agent call Microsoft Entra Agent ID and WorkOS Pipes and Agents without installing anything?

Yes. Microsoft Entra Agent ID has a hosted endpoint at https://graph.microsoft.com/v1.0/servicePrincipals/microsoft.graph.agentIdentity and WorkOS Pipes and Agents at https://api.workos.com.

Other comparisons with Microsoft Entra Agent ID or WorkOS Pipes and Agents

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.