6

These 2 libraries seem to serve a similar purpose: to securely store and control the access to tokens, passwords, API keys, and other secrets.

I have been using Microsoft.Azure.KeyVault with some success, not for configuration secrets, but for keys. Not until recently did I discover Azure.Security.KeyVault.Secrets.

In release notes I found this:

Updated Microsoft.Azure.KeyVault with its successor Azure.Security.KeyVault.Secrets to resolve key vault references.

What are the distinguishing attributes of the 2 libraries, and how to determine the appropriate choice.

Should I interpret the release note to imply Microsoft.Azure.KeyVault is obsolete or will be deprecated?

Ivan Glasenberg
  • 29,865
  • 2
  • 44
  • 60
Arthur
  • 143
  • 2
  • 8
  • 2
    Hope this link [Major changes from Microsoft.Azure.KeyVault](https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/keyvault/Azure.Security.KeyVault.Secrets/CHANGELOG.md#major-changes-from-microsoftazurekeyvault) can help you. – Ivan Glasenberg Jan 22 '20 at 01:43

1 Answers1

11

What are the distinguishing attributes of the 2 libraries, and how to determine the appropriate choice.

The package Azure.Security.KeyVault.Secrets is the most up-to-date version of the Key Vault client library, which is recommended to use for any new project. For main differences from the legacy one, see this Major changes from Microsoft.Azure.KeyVault. For usage, please refer to this doc.

The other package Microsoft.Azure.KeyVault is now a legacy one, if you have some old projects which use it, you can keep using it. For usage, please refer to this doc.

You can refer to this article for more details why these new client libraries(including Azure.Security.KeyVault.Secrets) are published.

Should I interpret the release note to imply Microsoft.Azure.KeyVault is obsolete or will be deprecated?

It is hard to say if the old one will be deprecated in the future. At least from the Release History, it says the new one is not a direct replacement for Microsoft.Azure.KeyVault(like other azure services, for example, azure storage service published a new version package recently, but not officially pronounced the old one is deprecated). But we suggest you should use the new one in any new create project like it says in the doc, a screenshot of this:

enter image description here

Hope it helps.

Ivan Glasenberg
  • 29,865
  • 2
  • 44
  • 60