# Azure Key Vault Pricing 2026: Standard vs HSM Costs

By Desmond Achebe · 2026-11-19 · Source: https://www.activepieces.com/blog/azure-key-vault-pricing-2026-standard-vs-hsm-costs

---
<aside class="tldr"><p class="tldr-label">Summary</p><p>Azure Key Vault charges $0.03 per 10,000 software operations but $1 to $5 per 10,000 for HSM keys, creating a costly gap to check before scaling secret lookups.</p><ul><li>One million calls cost $3 for software keys, $100 to $500 for HSM keys.</li><li>Fifty million monthly operations: $150 for secrets, $5,000 RSA 2048, $25,000 EC HSM.</li></ul></aside>

According to Microsoft Learn, Key Vault bills $0.03 per 10,000 secret or software-key operations, but $1 to $5 per 10,000 for HSM-protected keys.

So one million calls cost about $3 in software and $100 to $500 in hardware, a gap worth checking before you wire secret lookups into every run of a workflow, whether it's a script or a [Activepieces](https://www.activepieces.com) flow.

![Activepieces workflow builder with HTTP request step selected and its settings panel open showing method, URL, headers, and…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/9e36e973-de4a-435f-8912-12e666216b2d/self-host-mistral-ai-enterprise-deployment-guide-3f7fe28d.webp)

Azure Key Vault pricing is the pay-as-you-go billing model for Microsoft's cloud service that stores secrets, keys and certificates, charging per operation and per key according to the tier (Standard software-protected or Premium and Managed HSM hardware-protected) you choose.

Azure Key Vault is Microsoft's managed store for secrets, certificates and cryptographic keys.

Before you pick a tier, count which kind of call your code makes. The table below was checked against Microsoft's pricing page on 2026-11-19. It shows that the object type, not the vault name, sets the rate.

| Item | Price | What's included | Limits |
|---|---|---|---|
| Standard vault | Billed per operation, no tier fee stated here | Secrets, certificates, software-protected keys | No HSM-protected keys |
| Premium vault | Billed per operation | Everything in Standard, plus HSM-protected keys | Higher rates apply to HSM keys |
| Managed HSM | Priced separately on the pricing page | Dedicated HSM pool | Not comparable per call to vaults |
| Secrets | $0.03 per 10,000 operations | Reads, writes, lists | Throttled per vault |
| Certificates | Priced separately on the pricing page | Issuance and renewal | Throttled per vault |
| Software keys | $0.03 per 10,000 operations | Sign, verify, wrap, unwrap | Throttled per vault |
| HSM keys | $1 (RSA 2048), $5 (RSA 3072/4096 and EC) per 10,000 | Same operations, hardware-protected | Premium or Managed HSM only |

To see what you'll actually pay, start from the per-operation rates, which come from [SatisVault](https://satisvault.com/azure-vault-calculator); the next two sections turn them into numbers.

## Which Key Vault operations cost extra per call

Nothing in the rates above is free per call. A secret read at $0.03 per 10,000 is trivial for one app. A service that fetches a secret on every request, say **50 million times a month, pays $150**.

![A web service box sending a long stream of identical secret cards into one Key Vault box, with a small $150 price tag…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/c7f771d2-082c-4de1-a889-742ba327977e/azure-key-vault-pricing-2026-standard-vs-hsm-cos-113ee27c.webp)

Run that same volume against RSA 2048 HSM keys and it costs $5,000, and against EC keys $25,000, meaning your **cryptographic choice drives operating costs**.

A rotation workflow built in [Activepieces](https://www.activepieces.com) is metered differently: it costs 1 credit per run however many steps it has, so splitting a ten-step rotation into small, separate checks costs the same as the two-step shortcut, while the Key Vault calls inside it still bill at the rates above.

Past the per-region throttle, excess calls fail with HTTP 429 instead of costing more. That protects your bill but not your uptime, so cache secrets in the application rather than reading them on every request.

## What Key Vault costs at three realistic sizes

At small sizes the operation count is nearly the whole bill, and caching keeps it low. As keys and certificates multiply, the tier and the number of HSM-protected keys take over.

The table shows which line dominates at each size. Multiply your own counts by the rates on Microsoft's Key Vault pricing page, because the dominant line, not the total, tells you where to cut.

| Size | Keys | Secrets | Certificates | Monthly operations | Arithmetic per line | Monthly total | Dominant cost line |
|---|---|---|---|---|---|---|---|
| Small app | Few, software-protected | A few dozen | None | Low, cached | Operations × per-operation rate | Negligible | Operations |
| Mid-size platform | Some, software-protected | Hundreds | Several, renewing | Steady, high | Operations × rate, plus certificate operations × rate | Modest, rising with traffic | Certificate operations and request volume |
| Regulated HSM workload | Many, HSM-protected | Hundreds | Several | Steady, high | HSM keys × per-key rate, plus operations × rate | Large, mostly fixed | HSM key charges |

![What Azure Key Vault charges per 10,000 operations](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/a940b3b3-e199-4cc5-b69b-8c919ea14704/azure-key-vault-pricing-2026-standard-vs-hsm-cos-c767c006.svg "Source: SatisVault")

Read the totals as a direction, not a quote. The first row barely registers, and the last's a different kind of bill, which the following subsections explain.

With software-protected keys, no certificates and cached reads, you pay only for operations, and a cached app makes few. Uncached code's the one way to turn this row into a surprise, which is why the caching advice comes first.

When traffic is steady, everything multiplies, and certificates add their own operations and renewals on top. The bill's still modest, but now it moves with load, so a retry loop or a cold-start storm shows up as money.

Here the per-key charge for HSM protection outweighs request volume, so you count keys, not calls. Managed HSM's billed differently again, as a dedicated pool, so price it against your key count before assuming it's the upgrade.

## Spot hidden Key Vault costs and limits

The price you pay for a vault is rarely the price of the vault itself, because five charges and limits sit outside the headline rate. Each has a trigger you can check before you commit.

- Chatty apps that fetch a secret on every request pay per operation, so cost scales with traffic rather than with secret count.
- Request bursts past the per-vault limit return throttling errors instead of data.
- A Managed HSM pool bills every hour it's provisioned, including hours with no traffic.
- A Private Link endpoint adds its own hourly and data charges on top of the vault.
- Diagnostic logs sent to Log Analytics are billed by ingested volume, and audit logging every read can cost more than the reads.

![Azure Key Vault throttling limits by object type](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/88008794-4d9f-4423-895e-fdaf69ae3f2c/azure-key-vault-pricing-2026-standard-vs-hsm-cos-607e587a.svg "Source: Microsoft Learn")

Fix the first two by caching in the application; the sections below size the rest.

<blockquote class="pull"><p>Diagnostic logs sent to Log Analytics are billed by ingested volume, and audit logging every read can cost more than the reads.</p></blockquote>

### Key Vault request limits and throttling

300 to 4,000 transactions per 10 seconds per vault is the range Microsoft Learn sets for secrets, depending on the operation. That means one vault can serve a burst of reads but not a burst of creates.

Software keys run from 20 to 4,000, so heavy signing from one vault needs spreading across several. HSM keys run from 10 to 2,000, so an HSM-backed key's the first place a busy service hits the ceiling.

Leave a test pool running and it costs the same as a busy one, because a Managed HSM pool **bills for every hour it's provisioned**. Delete or avoid idle pools, and price it against your key count first.

![A Managed HSM pool as a hardware cabinet with no activity lights and a clock beside it, next to a busy identical cabinet…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/5951c8b1-45bc-4875-a509-9c888cb89afa/azure-key-vault-pricing-2026-standard-vs-hsm-cos-596a6821.webp)

If you give each environment its own vault, Private Link multiplies the fixed cost, since it bills the endpoint hourly plus data processed. Egress applies when traffic leaves the region. Log Analytics ingestion grows with request volume, which means chatty apps pay twice.

If a rebuild script reuses the name of a deleted vault, it fails until retention ends, because a deleted vault's name stays reserved meanwhile. Soft-delete keeps deleted vaults and objects recoverable for a retention period you set, and purge protection stops anyone emptying them early.

## Choosing between Standard, Premium and Managed HSM

**Start on Standard, and move up only when a named compliance requirement says your keys must sit in hardware.** The tier's as sticky as the vault name, and a wrong guess costs you a migration, not just a line item.

![A rebuild script page with an arrow blocked from a new vault, because the vault name sits in a soft-delete recovery bin…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/2d8f2525-0873-48c3-badb-9504b4e11a00/azure-key-vault-pricing-2026-standard-vs-hsm-cos-b1f6201c.webp)

To compare the tiers on protection, validation, cost at 10 and 1,000 keys, and upkeep, use the table. Read the cost columns for shape: Standard stays cheap at both sizes, Premium grows with key count, and Managed HSM starts high and flattens.

| Tier | Key protection | FIPS 140 level | Cost at 10 keys | Cost at 1,000 keys | Operational burden |
|---|---|---|---|---|---|
| Standard | Software | Lowest of the three | Negligible; requests dominate | Modest; scales with request volume | Minimal |
| Premium | Shared HSM, per key | Higher than Standard | Small surcharge per HSM key | Key count becomes the main line item | Minimal |
| Managed HSM | Dedicated HSM pool you control | Highest of the three | Fixed pool charge dominates | Pool charge spread across many keys | Highest: you manage the pool and its security domain |

Confirm the current rates and certificate levels on Microsoft's pricing and compliance pages before you commit. What follows is how to decide.

If no auditor or contract names hardware-protected keys, Standard covers you. Most application secrets, connection strings and encryption keys fall here. You pay mostly for requests, so your real bill's a function of call volume, not key count.

Choose Premium when a requirement says keys must be HSM-protected but doesn't demand single-tenant hardware. Each HSM-backed key carries a surcharge, so the count of such keys is your cost driver.

Keep only the keys the requirement covers in Premium, and leave everything else on Standard.

Choose Managed HSM when a regulation or customer contract demands dedicated hardware and your own control of the security domain. The fixed pool charge makes it poor value at a handful of keys.

It improves per key as the count grows, but you also take on backup, recovery and domain-key custody yourself.

## Compare Key Vault against AWS and others

None of the four's cheaper in general. Each one meters a different unit, so the bill is secrets × a storage rate, plus calls ÷ 10,000 × an operations rate, plus keys × a key rate.

Which term dominates decides the winner. That's the same count-and-multiply discipline as the HSM key math before it, applied across vendors.

To see which of your counts (secrets, calls or keys) will move the bill, look at what each service actually meters in the table. Check every rate against the vendor's pricing page before committing, since none are quoted here.

| | Price per secret | Price per 10,000 operations | Key price | Free tier | Lock-in |
|---|---|---|---|---|---|
| Key Vault | No separate stored-secret charge; you pay for operations | Metered per 10,000 operations | Software keys and HSM-protected keys priced differently | Little beyond Azure's account-wide free offers | Medium: Azure identity and access model |
| AWS Secrets Manager and KMS | Charged per secret per month | Metered on secret API calls and on KMS requests | Charged per key per month | Monthly KMS request allowance; trial period for Secrets Manager | Medium: IAM-bound |
| Google Secret Manager and Cloud KMS | Charged per active secret version | Metered on secret access operations | Charged per key version | Monthly allowance on secret versions and access | Medium: Google IAM-bound |
| HCP Vault | Not metered per secret on dedicated clusters | Not metered per call | Included in the cluster | Entry-level options vary by plan | Lowest: runs across clouds |

Read the table by your largest count: many small secrets punish per-secret pricing, and chatty applications punish per-operation pricing.

Choose another service when your workloads already run in that cloud, because crossing clouds adds latency, egress and a second identity system.

Choose HCP Vault when portability matters more than the lowest bill, since its cluster pricing ignores secret and call counts but you pay for capacity whether you use it or not.

## Automate Key Vault expiry alerts with Activepieces

To catch secrets and certificates nearing expiry, use Activepieces, an automation tool that can watch your vault and tell the right person in time.

A daily check is one run, so 1 credit however many steps it has, about 30 credits a month against the 1,000 on the free plan, which also allows unlimited flows.

Here the cost logic's the same as everywhere else in this article. A check that runs once a day's a handful of list calls, which barely registers next to an outage caused by an expired certificate that nobody was told about.

### What a rotation-reminder workflow looks like

Only the last two steps involve people. The flow's short, and the numbered list below shows the order a run takes; everything before those last two steps is a read against the Azure API.

1. Trigger the workflow on a schedule, or on a near-expiry event published by Key Vault.
2. List the secrets and certificates in the vault through the Azure API.
3. Filter to the items that expire within 30 days.
4. Look up the owner of each one, from a tag on the item or a small mapping table you maintain.
5. Notify that owner, or open a ticket if your team tracks rotation as work.

If an item has no owner tag, the alert lands in a shared channel and everyone assumes someone else will act. That is why the owner lookup in step four decides whether this works.

Tag at creation, and the workflow stays quiet except when it matters.

Next comes the boundary, because the workflow only reads dates and sends messages.

### What Key Vault expiry alerts don't replace

It doesn't rotate anything. Key Vault's own rotation policies and the services that consume the secrets still do that work. Activepieces tells a person the date's coming; it doesn't issue the new certificate or update the app that uses it.

If the reminders have to stay inside your own network, the MIT-licensed core can be self-hosted.

It also doesn't change your Key Vault bill. Tier, HSM-protected key count and request volume still drive the cost, and a daily listing adds only a trivial number of calls.

Treat it as a complement to the vault, and keep counting keys and calls as before.

## Your Key Vault bill checklist

Counting keys and calls comes down to seven steps, run in this order, because each one shrinks the number the next one has to measure. Start with what you own, then measure what it does, then cut.

The sequence below puts the cheap, reversible fixes ahead of the ones that touch production.

1. Inventory every vault and its tier across all subscriptions. Record which are Standard and which are Premium, since Premium's where HSM-protected keys live and where the per-key charge starts.
2. Pull operation counts per vault from Azure Monitor metrics. Look for the vaults with the highest request volume, because those are where a caching change pays back first.
3. Cache secrets in the application. A service that fetches the same secret on every request's paying for a lookup it could do once at startup and refresh on a schedule. Rotation still works if you set a sensible refresh interval.
4. Consolidate vaults where the access boundary allows it. Several small vaults for one team, one environment and one application rarely buy you any isolation, yet they multiply what you have to inventory and monitor.
5. Remove HSM-protected keys nobody uses. Check key last-used activity in your logs, disable a suspect key before deleting it, and move any key that never needed hardware protection to a software-protected one.
6. Set budget alerts on the subscriptions that hold your vaults. A runaway loop hammering a vault shows up as a bill, so make it show up as an email first.
7. Re-verify regional prices on Microsoft's pricing page before you commit to a region. The same vault can cost differently depending on where you deploy it, and your last check may be stale.

Once the list's done, rerun step two a month later. The change in operation counts tells you whether the caching held, and that comparison's the evidence for your next tier decision.

## Frequently asked questions

Once you have counted operations, most tier decisions are settled, but five smaller questions keep surfacing after the count is done.

### Is Azure Key Vault free?

Not as a standing plan. Key Vault bills on usage, so there's no permanent free tier to lean on.

Any free allowance comes from the Azure free account offer, which has its own terms and expiry. Check those terms before you budget around them, because a bill that starts at zero can stop being zero without any change in your code.

Does Azure Key Vault charge per secret stored? No. Secrets are billed by the operations performed on them, not by how many you keep. Hundreds of idle secrets cost you nothing extra.

Costs come from reads, writes and renewals, so audit your call patterns, not your inventory. Keys and certificates are different: HSM-protected keys carry a per-key charge, and certificate renewals are billed separately.

Are Key Vault prices the same in every Azure region? Don't assume so. Rates can differ by region and by billing currency, so a vault in a second region for disaster recovery can price differently from your primary.

Read the pricing page for each region you deploy to, then multiply by your own key and call counts.

### Can I move keys from Standard to Premium later?

Plan for new keys, not conversions. HSM-protected keys need a Premium vault, and an existing software-protected key doesn't become HSM-protected by moving it. You create or import new HSM keys and repoint your applications.

Whether a vault's tier can be changed in place is worth confirming in the current documentation. Either way, budget the migration effort as well as the price difference.

Do I pay for Key Vault when I only read a secret once at startup? Yes, but the amount is trivial. Each read's a billable operation.

One read per process start is negligible, unless hundreds of instances restart often or every request bypasses your cache. That's where startup reads turn into real volume.

## Related reading

- [Azure OpenAI Pricing in 2026: Batch, Standard & PTU](https://www.activepieces.com/blog/azure-openai-pricing-in-2026-batch-standard-ptu)
- [Azure Cosmos DB Pricing: A 2026 Guide to Costs](https://www.activepieces.com/blog/azure-cosmos-db-pricing-a-2026-guide-to-costs)
- [Azure Functions Pricing: All Plans Compared (2026)](https://www.activepieces.com/blog/azure-functions-pricing-all-plans-compared-2026)

## References

- [Microsoft Learn](https://learn.microsoft.com/en-us/azure/key-vault/general/service-limits)
- [SatisVault](https://satisvault.com/azure-vault-calculator)
