About Azure Key Vault certificates

Key Vault certificates support provides for management of your x509 certificates and the following behaviors:

  • Allows a certificate owner to create a certificate through a Key Vault creation process or through the import of an existing certificate. Includes both self-signed and Certificate Authority generated certificates.
  • Allows a Key Vault certificate owner to implement secure storage and management of X509 certificates without interaction with private key material.
  • Allows a certificate owner to create a policy that directs Key Vault to manage the life-cycle of a certificate.
  • Allows certificate owners to provide contact information for notification about life-cycle events of expiration and renewal of certificate.
  • Supports automatic renewal with selected issuers - Key Vault partner X509 certificate providers / certificate authorities.


Non-partnered providers/authorities are also allowed but, will not support the auto renewal feature.

Composition of a Certificate

When a Key Vault certificate is created, an addressable key and secret are also created with the same name. The Key Vault key allows key operations and the Key Vault secret allows retrieval of the certificate value as a secret. A Key Vault certificate also contains public x509 certificate metadata.

The identifier and version of certificates is similar to that of keys and secrets. A specific version of an addressable key and secret created with the Key Vault certificate version is available in the Key Vault certificate response.

Certificates are complex objects

Exportable or Non-exportable key

When a Key Vault certificate is created, it can be retrieved from the addressable secret with the private key in either PFX or PEM format. The policy used to create the certificate must indicate that the key is exportable. If the policy indicates non-exportable, then the private key isn't a part of the value when retrieved as a secret.

The addressable key becomes more relevant with non-exportable KV certificates. The addressable KV key's operations are mapped from keyusage field of the KV certificate policy used to create the KV Certificate.

The type of key pair to supported for certificates

  • Supported keytypes: RSA, RSA-HSM, EC, EC-HSM, oct (listed here) Exportable is only allowed with RSA, EC. HSM keys would be non-exportable.
Key type About Security
RSA "Software-protected" RSA key FIPS 140-2 Level 1
RSA-HSM "HSM-protected" RSA key (Premium SKU only) FIPS 140-2 Level 2 HSM
EC "Software-protected" Elliptic Curve key FIPS 140-2 Level 1
EC-HSM "HSM-protected" Elliptic Curve key (Premium SKU only) FIPS 140-2 Level 2 HSM

Certificate Attributes and Tags

In addition to certificate metadata, an addressable key and addressable secret, a Key Vault certificate also contains attributes and tags.


The certificate attributes are mirrored to attributes of the addressable key and secret created when KV certificate is created.

A Key Vault certificate has the following attributes:

  • enabled: boolean, optional, default is true. Can be specified to indicate if the certificate data can be retrieved as secret or operable as a key. Also used in conjunction with nbf and exp when an operation occurs between nbf and exp, and will only be permitted if enabled is set to true. Operations outside the nbf and exp window are automatically disallowed.

There are additional read-only attributes that are included in response:

  • created: IntDate: indicates when this version of the certificate was created.
  • updated: IntDate: indicates when this version of the certificate was updated.
  • exp: IntDate: contains the value of the expiry date of the x509 certificate.
  • nbf: IntDate: contains the value of the date of the x509 certificate.


If a Key Vault certificate expires, it's addressable key and secret become inoperable.


Client specified dictionary of key value pairs, similar to tags in keys and secrets.


Tags are readable by a caller if they have the list or get permission to that object type (keys, secrets, or certificates).

Certificate policy

A certificate policy contains information on how to create and manage lifecycle of a Key Vault certificate. When a certificate with private key is imported into the key vault, a default policy is created by reading the x509 certificate.

When a Key Vault certificate is created from scratch, a policy needs to be supplied. The policy specifies how to create this Key Vault certificate version, or the next Key Vault certificate version. Once a policy has been established, it isn't required with successive create operations for future versions. There's only one instance of a policy for all the versions of a Key Vault certificate.

At a high level, a certificate policy contains the following information (their definitions can be found here):

  • X509 certificate properties: Contains subject name, subject alternate names, and other properties used to create an x509 certificate request.

  • Key Properties: contains key type, key length, exportable, and ReuseKeyOnRenewal fields. These fields instruct key vault on how to generate a key.

    • Supported keytypes: RSA, RSA-HSM, EC, EC-HSM, oct (listed here)
  • Secret properties: contains secret properties such as content type of addressable secret to generate the secret value, for retrieving certificate as a secret.

  • Lifetime Actions: contains lifetime actions for the KV Certificate. Each lifetime action contains:

    • Trigger: specified via days before expiry or lifetime span percentage

    • Action: specifying action type – emailContacts or autoRenew

  • Issuer: Parameters about the certificate issuer to use to issue x509 certificates.

  • Policy Attributes: contains attributes associated with the policy

X509 to Key Vault usage mapping

The following table represents the mapping of x509 key usage policy to effective key operations of a key created as part of a Key Vault certificate creation.

X509 Key Usage flags Key Vault key ops Default behavior
DataEncipherment encrypt, decrypt N/A
DecipherOnly decrypt N/A
DigitalSignature sign, verify Key Vault default without a usage specification at certificate creation time
EncipherOnly encrypt N/A
KeyCertSign sign, verify N/A
KeyEncipherment wrapKey, unwrapKey Key Vault default without a usage specification at certificate creation time
NonRepudiation sign, verify N/A
crlsign sign, verify N/A

Certificate Issuer

A Key Vault certificate object holds a configuration used to communicate with a selected certificate issuer provider to order x509 certificates.

  • Key Vault partners with following certificate issuer providers for TLS/SSL certificates
Provider Name Locations
DigiCert Supported in all key vault service locations in public cloud and Azure Government
GlobalSign Supported in all key vault service locations in public cloud and Azure Government

Before a certificate issuer can be created in a Key Vault, following prerequisite steps 1 and 2 must be successfully accomplished.

  1. Onboard to Certificate Authority (CA) Providers

    • An organization administrator must on-board their company (ex. Contoso) with at least one CA provider.
  2. Admin creates requester credentials for Key Vault to enroll (and renew) TLS/SSL certificates

    • Provides the configuration to be used to create an issuer object of the provider in the key vault

For more information on creating Issuer objects from the Certificates portal, see the Key Vault Certificates blog

Key Vault allows for creation of multiple issuer objects with different issuer provider configuration. Once an issuer object is created, its name can be referenced in one or multiple certificate policies. Referencing the issuer object instructs Key Vault to use configuration as specified in the issuer object when requesting the x509 certificate from CA provider during the certificate creation and renewal.

Issuer objects are created in the vault and can only be used with KV certificates in the same vault.

Certificate contacts

Certificate contacts contain contact information to send notifications triggered by certificate lifetime events. The contacts information is shared by all the certificates in the key vault. A notification is sent to all the specified contacts for an event for any certificate in the key vault. For information on how to set Certificate contact, see here

Certificate Access Control

Access control for certificates is managed by Key Vault, and is provided by the Key Vault that contains those certificates. The access control policy for certificates is distinct from the access control policies for keys and secrets in the same Key Vault. Users may create one or more vaults to hold certificates, to maintain scenario appropriate segmentation and management of certificates. For more information on certificate access control, see here

Certificate Use Cases

Secure communication and authentication

TLS certificates can help encrypt communications over the internet and establish the identity of websites, making the entry point and mode of communication secure. Additionally, a chained certificate signed by a public CA can help verify that the entities holding the certificates are whom they claim to be. As an example, the following are some excellent use cases of using certificates to secure communication and enable authentication:

  • Intranet/Internet websites: protect access to your intranet site and ensure encrypted data transfer over the internet using TLS certificates.
  • IoT and Networking devices: protect and secure your devices by using certificates for authentication and communication.
  • Cloud/Multi-Cloud: secure cloud-based applications on-prem, cross-cloud, or in your cloud provider's tenant.

Code signing

A certificate can help secure the code/script of software, thereby ensuring that the author can share the software over the internet without being changed by malicious entities. Furthermore, once the author signs the code using a certificate leveraging the code signing technology, the software is marked with a stamp of authentication displaying the author and their website. Therefore, the certificate used in code signing helps validate the software's authenticity, promoting end-to-end security.

Next steps