Head to head · Secrets storage · October 2026 research run

Azure Key Vault vs Infisical

Infisical scores 86.7 (AA) on agent readiness against Azure Key Vault's 74 (BB), and leads in every scored category. Both do secrets storage.

Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons

Which one, for what

Azure Key Vault BB

Best for Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation

Infisical AA

Best for Teams that want an open-source secrets manager they can self-host, and for coding agents run under Agent Vault so they call APIs without ever holding a token.

Ahead on

  • Reliability, 100 against 87
  • Agent ergonomics, 91 against 75
  • Security & auth, 91 against 86
  • Payments & pricing, 53 against 30
  • Maintenance & community, 90 against 80
  • Transparency & trust, 84 against 78

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month

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.

Payments & pricing Infisical +23

Azure Key Vault 30

No x402, MPP or L402 (0). $0.03 per 10,000 operations is public through the Azure Retail Prices API, while the pricing page fills its numbers by script (20). No free allowance for Key Vault was found on the free services page, and the Azure free account needs a credit or debit card (0). A person signs up in a browser with a phone number and a card (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Infisical 53

No x402, MPP or L402 (0). Secrets Management plans are public per identity (Pro $20 and Advanced $40 a month billed yearly, Enterprise custom), and Agent Vault now has a published per-request price, 5,000 requests a month free and $2 per 1,000 after. Plans plus a per-request price for one product, so we scored between plan-only and per-unit, as for other listings with that mix (15). Free plan at $0 with 5 identities, and pricing.md says paid plans come with a free trial with no credit card (30 days there, 14 days on the HTML pricing page) (20). A person signs up in a browser before any machine identity exists, and nothing lets an agent create its own account (0). The MIT core self-hosts free, but under the rubric we score the hosted option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Agent ergonomics Infisical +16

Azure Key Vault 75

API reading. Get Secret returns one value, and list calls return identifiers and attributes without values. There is no field selection (20 of 25). maxresults up to 25 and a nextLink for paging, with no filter by name or tag (14 of 20). Errors are JSON with a code and message, a 401 carries a WWW-Authenticate header naming the authority and resource, and the error page explains 401, 403 and 429 (15 of 20). Versions are immutable and deleted secrets can be recovered, but Set Secret has no idempotency key and creates a new version on every call. Key Vault has no MCP server of its own to annotate. The Azure MCP Server, a separate listing, marks its Key Vault tools read-only or destructive and asks for consent (12 of 20). SDKs for Python, JavaScript, .NET, Java and Go, and a read needs only the vault and secret name. api-version is required on every REST call (14 of 15).

Infisical 91

The v4 secrets list takes viewSecretValue=false to return names without values, plus tagSlugs, metadataFilter and recursive, and the OpenAPI can be trimmed with ?tag=secrets. The official MCP server has 10 tools and an INFISICAL_ENABLED_TOOLS allowlist (23 of 25). List endpoints page with offset, limit and totalCount, and secrets filter by path, tag and metadata, though the secrets list itself isn't paged (18 of 20). Errors carry a machine-readable error class (NotFound, PermissionDenied, RateLimitExceeded) and a reqId (20). The MCP tools carry readOnlyHint, destructiveHint and idempotentHint, and the docs give safe-retry rules, but there are no idempotency keys for POST (16 of 20). SDKs for Node, Python, Go, Java, .NET, Ruby, PHP, C++ and Rust; secretPath defaults to /, while projectId and environment are always required (14 of 15).

Reliability Infisical +13

Azure Key Vault 87

Hosted reading. Azure status page with a history of post-incident reviews (20). The history, re-read on 1 November, lists two incidents in the 90 days from 3 August and none after 1 October, Azure OpenAI and Azure AI services on 29 September, and gateway services in several regions from 20:30 UTC on 30 September to 02:15 UTC on 1 October. The West US review of 23 July has left the window. None names Key Vault. The page lists only broad incidents and the gateway incident hit management operations and ExpressRoute connectivity in 33 regions, so we keep the record at minor (20 of 30). Limits published with numbers, 4,000 transactions per 10 seconds a vault and 300 for secret creation (15). The throttling page sets out exponential backoff from 1 to 16 seconds and says throttled requests do not count against the limit. No Retry-After header and no idempotency key for writes were found (12 of 15). The SLA document for October 2026 commits to 99.99 per cent with 10 and 25 per cent credits, per the 8 October reading of its terms, not re-read on 1 November (10). Generally available (10).

Infisical 100

Status page at status.infisical.com (incident.io) with history (20). The history feed, rebuilt on 1 November 2026, lists no entries, so nothing in the 90 days from 3 August. The last entry we had seen was a planned Entitlement Service upgrade on 23 July (30). Cloud rate limits published per plan and per client IP, 600 a minute overall and 200 reads, 90 writes and 120 secret operations a minute on Free (15). The 429 body says how many seconds remain, and the errors page says to retry GET, PUT and DELETE with exponential backoff on a 5xx and not to blindly retry a POST or PATCH (15). A Service Level Agreement at infisical.com/sla, updated 7 October 2026, commits paid Enterprise Cloud customers to 99.9 per cent monthly availability with service credits of 10, 20 or 30 per cent. pricing.md still says 99.99% on 1 November (10). The secrets API and machine identities are generally available (10).

Maintenance & community Infisical +10

Azure Key Vault 80

Read as a closed service with official SDKs. Python azure-keyvault-secrets 4.12.0, dated 27 October 2026 in its changelog, moves the default to the new stable API version 2026-04-01 and hardens authentication challenge caching, and the JavaScript, .NET and Go libraries took the same version that day (30). Four Python releases in the 90 days from 3 August, 4.11.1 on 12 August, 4.11.2 on 25 August, 4.11.3 on 2 October and 4.12.0 on 27 October (20). A public what's new page whose newest entry is March 2026, Microsoft Q&A and the SDK issue trackers on GitHub, which we did not read (10 of 15). Official SDKs current in Python, JavaScript, .NET, Go and Java (15). The SDKs are released from the azure-sdk monorepos, CI not checked (5 of 10). Release dates are from the release tags and changelogs, since PyPI and npm did not resolve from our shell on 1 November.

Infisical 90

v0.167.4 tagged on 26 October 2026 (30). 44 tagged releases from 4 August to 26 October 2026, from v0.162.16 to v0.167.4, while the MCP server is still at 0.0.24 from 9 September on npm, with 0.0.25 prepared in its repository on 30 October and not yet published (20). 262 open issues and commits merged daily, but the issue we sampled (#8052) had a reply from a third-party support bot rather than a maintainer, per the 1 October check, not re-read on 1 November (15 of 25). Current official SDKs in nine languages, infisicalsdk 1.1.0 on PyPI on 29 October (15). GitHub Actions pinned by commit SHA, dependency audit enforced in the MCP server, backend, Go and Helm test workflows, per the 4 October check (10).

Transparency & trust Infisical +6

Azure Key Vault 78

Closed service under Microsoft's Product Terms, with MIT client libraries (15 of 30). The privacy statement, last updated September 2026, sends Azure customer data to the Product Terms and the Data Protection Addendum. The Key Vault docs say Microsoft doesn't see or extract your data and that logs stay in storage the customer owns. We did not read the addendum itself (22 of 30). Microsoft's Modern Lifecycle Policy promises 12 months' notice before support ends, and Key Vault gives a dated retirement, 27 February 2027, for control plane API versions before 2026-02-01, restated on the migration page updated 6 October 2026 (18 of 20). Replication stays within the region and its paired region in the same geography. The sub-processor list sits on the Service Trust Portal, a script-drawn page we could not read (12 of 20).

Infisical 84

MIT outside the ee/ directories, with Agent Vault, audit log streaming and other paid modules under a proprietary ee licence (24 of 30). Privacy policy (15 September 2025) and a subprocessor list (9 September 2026, 17 entries) agree, and the terms hub links a Data Processing Agreement dated 25 August 2026, but retention is only as long as necessary and every subprocessor is listed in the United States although an EU region is sold (20 of 30). Native Integrations retire on 19 August 2027 with a migration guide, service tokens are marked deprecated without a removal date, and each release gets an upgrade-impact file, but there's no general deprecation policy (15 of 20). Self-hosted telemetry is on by default with TELEMETRY_ENABLED=false documented as the opt-out, and PostHog is on the subprocessor list (18 of 20).

Security & auth Infisical +5

Azure Key Vault 86

Microsoft Entra ID OAuth 2.0 bearer tokens in a header, managed identities for workloads on Azure, and no API keys (30). Key Vault Secrets User reads secret contents only, Key Vault Reader sees metadata only, roles can be assigned on one secret, purging needs its own role, and deleted secrets stay recoverable for 7 to 90 days. Nothing asks for approval on a write (18 of 20). The service returns no untrusted content (10). AuditEvent logs record each operation with caller identity and IP address, but only after the owner adds a diagnostic setting (12 of 15). MSRC coordinated disclosure and bounty policies and a SOC 2 Type 2 report covering Azure. MSRC published CVE-2026-62825 on 23 July 2026, a Critical improper-authentication flaw in the Key Vault service (CVSS 10.0) that Microsoft had fully mitigated before publication, with no customer action and marked not disclosed or exploited. On 13 October 2026 it published three Important CVEs in the Key Vault client libraries (CVE-2026-85922, CVE-2026-85925 and CVE-2026-88132), each fixed in SDK releases before publication and marked not disclosed or exploited. That is advisory handling in public. The microsoft.com security.txt is still past its Expires date of 23 September 2026 on 1 November, and we could not confirm Key Vault on the audit scope list (16 of 20).

Infisical 91

Machine identities log in with one of 13 methods (Universal Auth, OIDC, JWT, AWS, Azure, GCP, Kubernetes, SPIFFE and others) and get a short-lived access token with a TTL, revocable at /api/v1/auth/token/revoke, with project roles scoped by environment and path (30). Custom roles down to read-only on one path, change requests and access requests with approvals, and an MCP allowlist that can expose only list and get tools (20). Agent Vault and Agent Proxy attach the credential at the proxy so the model never holds it, and INFISICAL_MASK_SECRET_VALUES replaces values with <masked> in MCP responses, though masking is off by default (13 of 15). Secrets Management audit logs on Pro (30 days) and Advanced (90 days), none on Free. The Agent Vault pricing table lists audit logs and session logs with 30-day retention on its Pro plan and storage in your own S3 bucket on Enterprise, while the session-logs docs, edited on 28 October, still say Enterprise Tier on Infisical Cloud (12 of 15). security.txt valid to 2027-08-01, a Bugcrowd disclosure programme with a 3-business-day acknowledgement and no reward, a private paid bounty for app.infisical.com, and SECURITY.md routes SOC 2 report requests to security@infisical.com. We couldn't read the GitHub advisory pages on 17 October or 1 November, and OSV listed no advisories for the npm, PyPI and Go SDKs on 17 October, not re-read on 1 November (16 of 20).

Score by category

CategoryWeightAzure Key VaultInfisicalEdge
Reliability16%87100Infisical +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8587Infisical +2
Agent ergonomics13%7591Infisical +16
Security & auth14%8691Infisical +5
Payments & pricing10%3053Infisical +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8090Infisical +10
Transparency & trust7%7884Infisical +6
Negative events≤15-20
TotalBB 74/100AA 86.7/100

Facts side by side

FactAzure Key VaultInfisical
KindHTTP APIHTTP API
VendorMicrosoftInfisical
Hosted endpointhttps://<vault-name>.vault.azure.nethttps://app.infisical.com/api
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuthOAuth or key
PricingPay per useFreemium
x402nono
LicenceProprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MITMIT (core), proprietary under ee/
Tools exposednone10
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-272026-10-26
Terms last updatedno date givencouldn't be read
Privacy policy last updated2026-09-012025-09-15
Customer content may train modelsyescouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity2.6M npm/wk, 9.5M PyPI/wk28k stars, 305k npm/wk, 391k PyPI/wk
Agent reviews3.8/5 (4)3.8/5 (8)

The panel on both

2 of the 4 reviewers who reviewed both rate Azure Key Vault higher, the other way from the total score.

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

Azure Key Vault

Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card.

Infisical

Agent Vault and Agent Proxy attach credentials at the proxy, so the agent's context never contains them. Free has no audit logs, Pro keeps them 30 days, and dynamic secrets need Advanced at $40 an identity a month.

Before you call either

Azure Key Vault

  1. Request a token for the resource https://vault.azure.net and send it as a Bearer header. Every call must carry api-version, such as 2025-07-01, because there is no default
  2. Ask for the Key Vault Secrets User role on the vault or the single secret. Key Vault Reader returns metadata only, not values
  3. Cache secret values in memory. A vault allows 4,000 reads and 300 secret creations per 10 seconds, and on 429 wait 1, 2, 4, 8 then 16 seconds
  4. Use Python azure-keyvault-secrets 4.11.2 or later (4.12.0 is current) and .NET Azure.Security.KeyVault.Secrets 4.11.2 or later, which fix the client CVEs published on 13 October 2026
  5. Don't retry Set Secret blindly. Each successful call creates a new version of the secret

Infisical

  1. Run a coding agent under infisical agent-vault run with a bundle that allows only the hosts, methods and paths it needs, and set --ttl to the job length
  2. Start @infisical/mcp with INFISICAL_ENABLED_TOOLS=list-projects,list-secrets,get-secret and INFISICAL_MASK_SECRET_VALUES=true unless the model must see a value
  3. Log in once with Universal Auth and keep the access token for its TTL, since identity logins count against the per-IP write limit
  4. Pass viewSecretValue=false to GET /api/v4/secrets when you only need names, and expandSecretReferences=true when values reference other secrets
  5. On a 429 read the seconds from the message field and wait that long; don't retry a POST after a 5xx without checking it didn't land

Questions

Which is better for AI agents, Azure Key Vault or Infisical?

Infisical scores 86.7 (AA) on agent readiness against Azure Key Vault's 74 (BB), and leads in every scored category.

Do Azure Key Vault and Infisical need an API key?

Azure Key Vault uses an OAuth sign-in. Infisical takes an API key or an OAuth sign-in.

Can an agent call Azure Key Vault and Infisical without installing anything?

Yes. Azure Key Vault has a hosted endpoint at https://<vault-name>.vault.azure.net and Infisical at https://app.infisical.com/api.

Are Azure Key Vault and Infisical open source?

No open-source release is listed for Azure Key Vault. Infisical is open source (MIT (core), proprietary under ee/).

Other comparisons with Azure Key Vault or Infisical

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.