| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Secrets management | Identity and access | 3% | 5 of 59 | 13% | 47 | accepted challenger | ▲+2Since September 2026: 2% → 4%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Certificate lifecycle management | Identity and access | 0% | 42 of 104 | 0% | 2 | under 10 labels · led by Sectigo Certificate Manager at 27% | |
| Non-human identity management | Identity and access | 0% | 40 of 128 | 0% | 2 | under 10 labels · led by JumpCloud at 14% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Secrets | 2% | 4% | ▲+2Since September 2026: 2% → 4%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 8 → 5 of 59 |
| Certificate management | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 42 of 104, unchanged |
| NHI management | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 40 of 128, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 2 | 3 | 0 | 5 |
| GPT-5.4 mini | 1 | 3 | 0 | 0 | 4 |
| Gemini 3.5 Flash | 0 | 5 | 1 | 0 | 6 |
| Perplexity Sonar | 0 | 1 | 2 | 1 | 4 |
| Grok 4.20 | 0 | 2 | 1 | 2 | 5 |
| Mistral Small | 1 | 2 | 1 | 0 | 4 |
| DeepSeek V4 Flash | 0 | 3 | 2 | 0 | 5 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 3 | 0 | 0 | 3 |
| Kimi K2 | 0 | 2 | 0 | 1 | 3 |
| GLM 4.7 FlashX | 0 | 0 | 1 | 0 | 1 |
| MiniMax M2.5 | 0 | 2 | 1 | 1 | 4 |
| GPT-6 Luna | 0 | 2 | 0 | 0 | 2 |
| Muse Glimmer 30B | 0 | 3 | 0 | 1 | 4 |
Verbatim evidence the judge attached to positive labels.
“HashiCorp Vault or Azure Key Vault are the most versatile and widely recommended” Mistral Small · Secrets · paraphrase prompt · first choice
“Azure Key Vault if you're mostly on Azure” GPT-5.4 mini · Secrets · direct prompt · first choice
“Tools like AWS Secrets Manager, Azure Key Vault, or GCP Secret Manager handle the storage and dynamic rotation of credentials natively.” Gemini 3.5 Flash · NHI management · budget prompt · alternative
“Use only cloud-native tools like AWS Secrets Manager or Azure Key Vault if your stack is essentially confined to one cloud provider.” Perplexity Sonar · Secrets · paraphrase prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“⚠️ Configuration-Dependent Risks ... Common misconfiguration: Public network access enabled” Kimi K2 · Secrets · negative prompt · soft negative
“Microsoft disclosed a maximum-severity elevation-of-privilege flaw in Azure Key Vault” MiniMax M2.5 · Secrets · negative prompt · soft negative
“Cloud-vendor tools (e.g., ... Azure Key Vault): Why cautious? Strong vendor lock-in” Grok 4.20 · Secrets · negative prompt · soft negative
“Cloud-native secret stores used as a single primary store across multiple clouds” Perplexity Sonar · Secrets · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 136 of the 152 answers that named Azure Key Vault and are not a share of its labels.
486 of the 486 domain citations in answers naming Azure Key Vault came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Azure Key Vault's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Azure Key Vault, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Azure Key Vault by email, built from the raw record of the edition. It shows: