What's new for Azure Key Vault

Here's what's new with Azure Key Vault. New features and improvements are also announced on the Azure updates Key Vault channel.

April 2022

Automated encryption key rotation in Key Vault is now generally available.

For more information, see Configure key auto-rotation in Key Vault

January 2022

Azure Key Vault service throughput limits have been increased to serve double its previous quota forĀ each vault to help ensure high performance for applications. That is, for secret GET and RSA 2,048-bit software keys, you'll receive 4,000 GET transactions per 10 seconds vs 2,000 per 10 seconds previously. The service quotas are specific to operation type and the entire list can be accessed in Azure Key Vault Service Limits.

For Azure update announcement, see [General availability: Azure Key Vault increased service limits for all its customers] (https://azure.microsoft.com/updates/azurekeyvaultincreasedservicelimits/)

December 2021

Automated encryption key rotation in Key Vault is now in preview. You can set a rotation policy on a key to schedule automated rotation and configure expiry notifications through Event Grid integration.

For more information, see Configure key auto-rotation in Key Vault

October 2021

Integration of Azure Key Vault with Azure Policy has reached general availability and is now ready for production use. This capability is a step towards our commitment to simplifying secure secrets management in Azure, while also enhancing policy enforcements that you can define on Key Vault, keys, secrets and certificates. Azure Policy provides the ability to place guardrails on Key Vault and its objects to ensure they are compliant with your organizations security recommendations and compliance regulations. It allows you to perform real time policy-based enforcement and on-demand compliance assessment of existing secrets in your Azure environment. The results of audits performed by policy will be available to you in a compliance dashboard where you will be able to see a drill down of which resources and components are compliant and which are not. Azure policy for Key Vault will provide you with a full suite of built-in policies offering governance of your keys, secrets, and certificates.

You can learn more about how to Integrate Azure Key Vault with Azure Policy and assign a new policy. Announcement is linked here.

June 2021

Azure Key Vault Managed HSM is generally available. Managed HSM offers a fully managed, highly available, single-tenant, high-throughput, standards-compliant cloud service to safeguard cryptographic keys for your cloud applications, using FIPS 140-2 Level 3 validated HSMs.

For more information, see Azure Key Vault Managed HSM Overview

February 2021

Azure role-based access control (RBAC) for Azure Key Vault data plane authorization is now generally available. With this capability, you can now manage RBAC for Key Vault keys, certificates, and secrets with roles assignment scope available from management group to individual key, certificate, and secret.

For more information, see Provide access to Key Vault keys, certificates, and secrets with an Azure role-based access control

October 2020

Warning

These updates have the potential to impact Azure Key Vault implementations.

To support soft delete now on by default, two changes have been made to Azure Key Vault PowerShell cmdlets:

  • The DisableSoftDelete and EnableSoftDelete parameters of Update-AzKeyVault have been deprecated.
  • The output of the Get-AzKeyVaultSecret cmdlet no longer has the SecretValueText attribute.

July 2020

Warning

These two updates have the potential to impact Azure Key Vault implementations.

Soft delete on by default

Soft-delete is required to be enabled for all key vaults, both new and pre-existing. Over the next few months the ability to opt out of soft delete will be deprecated. For full details on this potentially breaking change, as well as steps to find affected key vaults and update them beforehand, see the article Soft-delete will be enabled on all key vaults.

Azure TLS certificate changes

Microsoft is updating Azure services to use TLS certificates from a different set of Root Certificate Authorities (CAs). This change is being made because the current CA certificates do not comply with one of the CA/Browser Forum Baseline requirements. For full details, see Azure TLS Certificate Changes.

June 2020

Azure Monitor for Key Vault is now in preview. Azure Monitor provides comprehensive monitoring of your key vaults by delivering a unified view of your Key Vault requests, performance, failures, and latency. For more information, see Azure Monitor for Key Vault (preview)..

May 2020

Key Vault "bring your own key" (BYOK) is now generally available. See the Azure Key Vault BYOK specification, and learn how to Import HSM-protected keys to Key Vault (BYOK).

March 2020

Private endpoints now available in preview. Azure Private Link Service enables you to access Azure Key Vault and Azure hosted customer/partner services over a Private Endpoint in your virtual network. Learn how to Integrate Key Vault with Azure Private Link.

2019

2018

New features and integrations released this year:

2016

New features released this year:

  • Managed storage account keys. Storage Account Keys feature added easier integration with Azure Storage. See the overview topic for more information, Managed Storage Account Keys overview.
  • Soft delete. Soft-delete feature improves data protection of your key vaults and key vault objects. See the overview topic for more information, Soft-delete overview.

2015

New features released this year:

  • Certificate management. Added as a feature to the GA version 2015-06-01 on September 26, 2016.

General Availability (version 2015-06-01) was announced on June 24, 2015. The following changes were made at this release:

  • Delete a key - "use" field removed.
  • Get information about a key - "use" field removed.
  • Import a key into a vault - "use" field removed.
  • Restore a key - "use" field removed.
  • Changed "RSA_OAEP" to "RSA-OAEP" for RSA Algorithms. See About keys, secrets, and certificates.

Second preview version (version 2015-02-01-preview) was announced April 20, 2015. For more information, see REST API Update blog post. The following tasks were updated:

  • List the keys in a vault - added pagination support to operation.
  • List the versions of a key - added operation to list the versions of a key.
  • List secrets in a vault - added pagination support.
  • List versions of a secret - add operation to list the versions of a secret.
  • All operations - Added created/updated timestamps to attributes.
  • Create a secret - added Content-Type to secrets.
  • Create a key - added tags as optional information.
  • Create a secret - added tags as optional information.
  • Update a key - added tags as optional information.
  • Update a secret - added tags as optional information.
  • Changed max size for secrets from 10 K to 25 K Bytes. See, About keys, secrets, and certificates.

2014

First preview version (version 2014-12-08-preview) was announced on January 8, 2015.

Next steps

If you have additional questions, please contact us through support.