title: Azure.Security.KeyVault.Secrets vs Microsoft.Azure.KeyVault
body: <p>These 2 libraries seem to serve a similar purpose: to securely store and control the access to tokens, passwords, API keys, and other secrets.</p>
  
  <p>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.</p>
  
  <p>In <a href="https://github.com/Azure/AppConfiguration/blob/master/releaseNotes/MicrosoftExtensionsConfigurationAzureAppConfiguration.md#300-preview-010550001-251---november-22-2019" rel="noreferrer">release notes</a> I found this:</p>
  
  <blockquote>
    <p>Updated Microsoft.Azure.KeyVault with its successor Azure.Security.KeyVault.Secrets to resolve key vault references.</p>
  </blockquote>
  
  <p>What are the distinguishing attributes of the 2 libraries, and how to determine the appropriate choice.  </p>
  
  <p>Should I interpret the release note to imply Microsoft.Azure.KeyVault is obsolete or will be deprecated?</p>