Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.

Start free today

Managing User Secrets

Sign in to queue

The Discussion

  • User profile image

    I do not have this context menu entry on my Xamarin projects.

  • User profile image
    Sergio Terenas

    I’m using VS 15.8.1 and the context menus don’t show these new options on my winforms project.
    Adding a connected service doesn’t show Azure Vault either.
    Am I missing something?

  • User profile image

    Secrets management is currently for .NET Core projects. Support for WinForms and other .NET Framework projects is coming. Azure Key Vaults and Connected Services is currently available for ASP.NET and ASP.NET Core projects. 

    Sorry if that wasn't clear in the video. I thought we covered it. 

  • User profile image

    Hi I am using VS 15.8.1 community edition. I have setup the key vault as mentioned in the video and created core application. I do not see any squiggly line to select for the InstrumentationKey and hence be able to select Azure Key vault. I tried to highlight and right click and options there also.

    "Logging": {
    "IncludeScopes": false,
    "LogLevel": {
    "Default": "Warning"
    "ApplicationInsights": {
    "InstrumentationKey": "dummyaapinsightkey-cxds3-4001-953f-sf323sdfw32d"

  • User profile image


    In the video it has been said that version 15.8.1 would have the cited menus available for Winforms projects.

    It is OK if this is not the case, but, if you review the video, you will see this.



    Eduardo Quintana

  • User profile image

    Does this flow always create a new keyvault when I tried it does not show existing keyvalult

  • User profile image

    Hello all,

    I've published my Article by explaining this in detail. You can find the article below




  • User profile image

    I'd love to see this feature being used in the build process for desktop apps. The build server needs to have access of private keys for the copy protection system to work. But we definitely do not want to commit these secrets in our source.

  • User profile image

    I currently use appSettings to store connection strings.  Having the appSettings.Development.json and appSettings.Staging.json makes it easy to store different connection strings for Dev, Test, and Prod environments.  How would I replicate this same functionality using Azure Key vault?

  • User profile image

    Maybe adjust the video title to "Managing User Secrets with Azure Key Vault". From the title I thought this was more generalized and going to cover a few different methods of managing user secret information (web.config, app.config, config encryption for sections, windows data protection api, et cetera). At work, we develop an enterprise intranet application for banks where Azure is not an option, so we have to use other methods of securing information.

    The release timeframe for the right-click menu was covered, but I think those who may not have been so intently focused might have missed it because it was very brief, but it will come in a future release is what I gathered.

    Good video though. We use Azure for DevTest heavily - using user secrets for some of that might be applicable. I thought I heard him say 3 cents per transaction though? That can get very costly!

  • User profile image

    It would be useful if you show how authentication to the vault is working.  This video makes it look like magic, but then when things don't work, then what?  For example on premise you would need to use security principal or certificate to authenticate to the vault.  In the vault you have to add into access policies these permissions.  Secondly when using secrets.json locally, when you grab a solution fresh from Git, obviously this doesn't exist locally, does this have to be created manually?  How do I know all the configuration key/values I need to put in here?  That appears to be magic also in this video.

  • User profile image

    @kumarAzure: The flow that we walked through in the video allows you to attach a Key Vault (new or existing) to the project.  When you publish your application, you will be prompted to attach that same Key Vault to your published application.  

  • User profile image

    @jkruer01:One way you can do this is to create a separate Key Vaults for your dev, test, and prod environments.  You can then store the connection strings to your environments in the respective Key Vaults.  The Key Vault configuration can be modified to point to the correct vault in the launchSettings.json file.  Please let me know if you have any further questions!

Add Your 2 Cents