14 comments

Add a comment…

Sign in

prestine

Your name

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Abdullah Kuzhan commented  ·  August 02, 2017 01:21  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  Hi, is there any update on this?

• Steve Velcev commented  ·  July 24, 2017 02:22  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  Hello Microsoft, please could you provide your clients with an update to if this feature has been implemented yet?

• Henrik Gundersen commented  ·  July 21, 2017 05:48  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  Any change in status for this? Almost a year since "under review".

• Dimka M commented  ·  June 29, 2017 17:00  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  This is really needed. More importantly a caching mechanism is required so that keyvault does not get overwhelmed with requests when function infinitely scales. (see discussion here: https://github.com/Azure/azure-webjobs-sdk/issues/746)

• Nathan Anderson commented  ·  June 27, 2017 03:14  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  ping for update.

• Anonymous commented  ·  June 09, 2017 06:45  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  Has this been implemented by any chance. All clients want to maintain their security information in Key Vault

• Ahmet Arsan commented  ·  May 21, 2017 06:32  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  Can't use Functions without this. This is an absolute must. ETA?

• Adam Modlin commented  ·  May 16, 2017 13:34  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  Any updates here? My customer requires all connection strings be stored in KeyVault and this is a problem for using functions.

• Parry Kitchner commented  ·  May 11, 2017 04:01  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  Add this binding and Azure Function usage will hit an all new high! It would be great not to have to re-store the secrets in the App Config.

• Gary Mitchell commented  ·  April 17, 2017 09:07  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  Any idea when this might become available? I really need it. The cert approach didn't get approved by IT Security.

• Henrik Gundersen commented  ·  April 06, 2017 06:24  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  A necessary feature, and overall great idea. Examples of securables are tokens (like Github, Slack) and certificates.

• Joshua Toon commented  ·  March 17, 2017 10:43  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  This would be great.

• Gerald Wiltse commented  ·  February 17, 2017 21:02  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  Food for thought, this recent development in .NET Core might reduce the amount of custom code you need for this.

  https://docs.microsoft.com/en-us/aspnet/core/security/key-vault-configuration#controlling-access-to-the-clientsecret

• Gerald Wiltse commented  ·  January 18, 2017 22:12  ·  Flag as inappropriateFlag as inappropriate  ·  Delete…

  I believe I read somewhere that this had basically been accepted and if so, this is just a ping to update status here.