Key Vault pricing

You can store the following types of keys and secrets in Key Vault:

• Keys can be imported or generated in HSMs, and are always locked to the boundary of the HSM. When you ask the Key Vault service to decrypt or sign with a key, the operation is performed inside an HSM.
• You can also encrypt using keys in HSMs. In this case, cryptographic operations are performed in software, as opposed to being inside of an HSM. These computations are performed in Azure compute roles.
• Secrets are data (under 10_KB) such as passwords or .PFX files that your application can store and retrieve in plaintext. The Key Vault service persists secrets encrypted using an HSM-backed key, and provides an access control layer over them.

In addition to keys and secrets, you can also store and manage SSL/TLS certificates that you've purchased from public CAs, and automatically enrol or renew them via Key Vault if the public CA is currently supported by Key Vault.

Every successfully authenticated REST API call counts as one operation.

Examples of operations for keys—create, import, get, list, back up, restore, delete, update, sign, verify, wrap, unwrap, encrypt and decrypt. Note that the price charged for an operation may vary based on the type of key (for example, operations performed on a 2048-bit RSA key vs a 4096-bit RSA key are billed against different metres with different prices, as described in the pricing section above).

Examples of operations for secrets—create/update, get, list.

Examples of operations for certificates—create, update policy, contacts, import, renewal or update of certificates. Note that a certificate renewal operation has a separate cost from all other operations on certificates.

Operations against all keys (software-protected keys and HSM-protected keys), secrets, and certificates are billed at a flat rate of $- per 10,000 operations, except certificate renewal requests, which are billed at a rate of $- per renewal. Examples—A) You perform 2,000 operations with HSM-protected keys, 1,000 operations with software-protected keys, and 500 operations with secrets during a billing cycle. You will be billed for 3,500 operations during that billing cycle. B) In a given billing cycle, you perform 500 operations on 20 certificates, and 2 of these certificates are also renewed by Key Vault. You will be billed for 500 operations and 2 certificate renewal requests.

Each key that you generate or import in an Azure Key Vault HSM will be charged as a separate key. You will get charged for a key only if it was used at least once in the previous 30 days (based on the key’s creation anniversary date). Note that if you store multiple (historical) versions of a given key, then each version is treated as a separate key for billing purposes.

Examples:

• You add three HSM protected keys in your key vault. Over the next 30 days, you use the first key 10,000 times, the second key once, and you do not use the third key at all. For this 30-day period, you will get billed for 2 HSM key units. For e.g. if these are 2048-bit RSA keys, you will get billed 2 x $-/key/month = $-, and if these are 3072-bit RSA keys, you will get billed 2 x $-/key/month = $-.
• You have 1 HSM protected key in your key vault. You have 5 historical versions of that key because you have changed the value of the key four times. In the last 30 days, you used 2 of those versions, and did not touch the other three. For a 2048-bit RSA key, you will get billed $- in this example, while for advanced key type, you will get billed $- in this example.
• Note that any operations performed on HSM-protected keys will be charged separately and will apply in addition to the HSM key charges.

No, there is no set up fee for Azure Key Vault.

HSM key charges are not pro-rated based on length of time it is enabled. We will charge for an HSM key only if it is used at least once in the previous 30 days, based on the key’s creation anniversary date.

Yes, you can grant use of keys stored in Key Vault to any app, hosted anywhere (Microsoft Azure, third-party cloud, on-premises).

No. Only the key owner gets billed.