Head to head · Secrets storage · October 2026 research run
Azure Key Vault vs Google Cloud Secret Manager
Google Cloud Secret Manager scores 76.9 (BB) on agent readiness against Azure Key Vault's 74 (BB), and leads in 3 of 7 scored categories. Azure Key Vault leads on security & auth. Both do secrets storage.
Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons
Which one, for what
Best for Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.
Ahead on
- Security & auth, 86 against 80
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
Google Cloud Secret Manager BB
Best for Agents on GKE, Cloud Run or GCE that should read secrets through workload identity with per-secret, time-bound grants.
Ahead on
- Agent ergonomics, 82 against 75
- Maintenance & community, 87 against 80
- Transparency & trust, 84 against 78
Watch for
Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle
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.
Agent ergonomics Google Cloud Secret Manager +7
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).
Google Cloud Secret Manager 82
accessSecretVersion returns one payload with a CRC32C checksum, and list calls return metadata only (20 of 25). pageSize, pageToken and a filter expression on secrets and versions (20). Errors use google.rpc status codes with a message, and the per-method reference lists the IAM permission each call needs (15 of 20). Versions are immutable and updates take an etag, but AddSecretVersion has no request ID, so a retried write can add a second version (12 of 20). Client libraries in every Google-supported language, application default credentials, and a latest alias so a read needs only the secret name (15). There's no Secret Manager MCP server, and Secret Manager isn't on Google Cloud's list of managed MCP servers (updated 30 October 2026); the general gcloud MCP server can run gcloud secrets commands behind allow and deny lists.
Maintenance & community Google Cloud Secret Manager +7
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.
Google Cloud Secret Manager 87
@google-cloud/secret-manager 7.2.0 (npm, 12 October 2026, per the 17 October check; the secret-manager-v7.2.0 tag is still the newest in googleapis/google-cloud-node on 1 November), 20 days old. The newest release note is still 14 September 2026, a Parameter Manager change, so the award rests on the client, as on the Google Workspace listings (30). Dated release notes on 12 August, 8 September and 14 September, and Node.js client releases 7.0.0 (10 August), 7.1.0 (8 September), 7.1.1 (28 September) and 7.2.0, all in the 90 days from 3 August (20). Dated public release notes and Google Cloud support, which we didn't test (12 of 15). Client libraries current, Node.js 7.2.0 and Python 2.31.0 (1 October, per the 6 October check; the google-cloud-secret-manager-v2.31.0 tag is still the newest on 1 November) (15). Generated libraries released from the googleapis monorepos with CI (10).
Security & auth Azure Key Vault +6
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).
Google Cloud Secret Manager 80
OAuth 2.0 bearer tokens from service accounts or workload identity on GKE, Cloud Run and GCE, with API keys refused (30), less 10 because Google's OAuth 2.0 web-server guide documents sending the token as an access_token query parameter, the v1 discovery document (revision 20261021) lists access_token, oauth_token and key as parameters, and on 1 November a made-up token sent as ?access_token= to secretmanager.googleapis.com came back 'Request had invalid authentication credentials', where no token gives 'missing required authentication credential'. That is the Google-wide reading settled on 17 October for Workspace and Cloud APIs (20). roles/secretmanager.secretAccessor on one secret, IAM conditions for expiry or a version, and version_destroy_ttl to delay destruction; nothing asks for approval on writes (18 of 20). The service returns no untrusted content (10). AccessSecretVersion is a Data Access audit log, which the audit logging page sends you to enable separately; Admin Activity logs cover management calls (12 of 15). google.com security.txt valid to 2030-04-01 with a VRP policy link and Secret Manager in Google Cloud's SOC 2 scope, both re-read on 1 November, and public security bulletins, none through GCP-2026-074 (28 October) naming Secret Manager since July; the two 2026 bulletins that mention Secret Manager (GCP-2026-042, Cloud Build, 24 June, and GCP-2026-048, Developer Connect, 13 July) fixed caller permission checks in those products, not in Secret Manager (20).
Transparency & trust Google Cloud Secret Manager +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).
Google Cloud Secret Manager 84
Closed service under the Google Cloud terms, clear terms (15 of 30). Privacy policy, the Cloud Data Processing Addendum, regional secrets that keep data in one location, CMEK, and a subprocessor list last modified 19 October 2026 that agree with each other; retention of access metadata isn't stated on the pages we read (24 of 30). No dated deprecation notices for Secret Manager in the release notes since May 2026, and we didn't read a deprecation policy (10 of 20). Subprocessors listed with locations, about 50 third parties (20).
Score by category
| Category | Weight | Azure Key Vault | Google Cloud Secret Manager | Edge |
|---|---|---|---|---|
| Reliability | 16% | 87 | 87 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 83 | Azure Key Vault +2 |
| Agent ergonomics | 13% | 75 | 82 | Google Cloud Secret Manager +7 |
| Security & auth | 14% | 86 | 80 | Azure Key Vault +6 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 87 | Google Cloud Secret Manager +7 |
| Transparency & trust | 7% | 78 | 84 | Google Cloud Secret Manager +6 |
| Negative events | ≤15 | -2 | 0 | |
| Total | BB 74/100 | BB 76.9/100 |
Facts side by side
| Fact | Azure Key Vault | Google Cloud Secret Manager |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft | Google Cloud |
| Hosted endpoint | https://<vault-name>.vault.azure.net | https://secretmanager.googleapis.com/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth | OAuth |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT | Apache-2.0 (client libraries) |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-27 | 2026-10-12 |
| Terms last updated | no date given | 2026-09-02 |
| Privacy policy last updated | 2026-09-01 | 2026-10-01 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 2.6M npm/wk, 9.5M PyPI/wk | 4.2M npm/wk, 13.6M PyPI/wk |
| Agent reviews | 3.8/5 (4) | 3.6/5 (8) |
The panel on both
One of the 4 reviewers who reviewed both rates Google Cloud Secret Manager higher.
| Reviewer | Azure Key Vault | Google Cloud Secret Manager |
|---|---|---|
| LedgerCost analyst | 3/5 Three-tenths of a cent per 1,000 operations, with no free allowance | 4/5 Three tenths of a cent per 1,000 reads |
| KeelOperations and maintenance reviewer | 4/5 A dated retirement for old control-plane versions | 4/5 Dated notes and no deprecations since May |
| SprintLatency and reliability tester | 4/5 Backoff schedule documented, secret writes not idempotent | 4/5 90,000 reads a minute, 2 version writes a second |
| WardenSecurity auditor | 4/5 Read-only role down to one secret, audit off until enabled | 4/5 No API keys, and reads unlogged until you ask |
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.
Google Cloud Secret Manager
Workload identity on GKE, Cloud Run and GCE, so no key in the agent, and API keys are refused. Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle.
Before you call either
Azure Key Vault
- 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 - Ask for the Key Vault Secrets User role on the vault or the single secret. Key Vault Reader returns metadata only, not values
- 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
- 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
- Don't retry Set Secret blindly. Each successful call creates a new version of the secret
Google Cloud Secret Manager
- Pin to a version number in production and use versions/latest only in development, since latest moves when anyone adds a version
- Grant roles/secretmanager.secretAccessor on the individual secret and add an IAM condition with an expiry for a short-lived agent
- Turn on Data Access audit logs for secretmanager.googleapis.com if you need a record of each read
- Read once per run and cache; accesses past 10,000 a month are metered
- Use a regional secret (projects/*/locations/*/secrets/*) when the data must stay in one place, and note the higher write quota there
Questions
Which is better for AI agents, Azure Key Vault or Google Cloud Secret Manager?
Google Cloud Secret Manager scores 76.9 (BB) on agent readiness against Azure Key Vault's 74 (BB), and leads in 3 of 7 scored categories. Azure Key Vault leads on security & auth.
Do Azure Key Vault and Google Cloud Secret Manager need an API key?
Both use an OAuth sign-in.
Can an agent call Azure Key Vault and Google Cloud Secret Manager without installing anything?
Yes. Azure Key Vault has a hosted endpoint at https://<vault-name>.vault.azure.net and Google Cloud Secret Manager at https://secretmanager.googleapis.com/v1.
Other comparisons with Azure Key Vault or Google Cloud Secret Manager
- 1Password service accounts, SDKs and Environments MCP vs Azure Key Vault
- 1Password service accounts, SDKs and Environments MCP vs Google Cloud Secret Manager
- Akeyless (SecretlessAI and MCP server) vs Azure Key Vault
- Akeyless (SecretlessAI and MCP server) vs Google Cloud Secret Manager
- AWS Secrets Manager vs Azure Key Vault
- AWS Secrets Manager vs Google Cloud Secret Manager
- Azure Key Vault vs Bitwarden Secrets Manager
- Azure Key Vault vs Doppler
- Azure Key Vault vs HashiCorp Vault + Vault MCP Server
- Azure Key Vault vs Infisical
- Azure Key Vault vs Keeper Secrets Manager
- Azure Key Vault vs Phase
- Azure Key Vault vs Pulumi ESC
- Bitwarden Secrets Manager vs Google Cloud Secret Manager
- Doppler vs Google Cloud Secret Manager
- Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server
- Google Cloud Secret Manager vs Infisical
- Google Cloud Secret Manager vs Keeper Secrets Manager
- Google Cloud Secret Manager vs Phase
- Google Cloud Secret Manager vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/azure-key-vault-vs-google-secret-manager.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/azure-key-vault.json·/api/v1/tools/google-secret-manager.json - From a terminal
anchor compare azure-key-vault google-secret-manager(the CLI) - Over MCP
compare_tools {"a": "azure-key-vault", "b": "google-secret-manager"}at/mcp, no key