Add binding to Key Vault
Functions often need password, API keys, and connection strings to connect to other services and retrieve data. It would be great if those secrets could easily be obtained from Key Vault.
Anonymous
shared this idea
This is a good idea. We’ll look at this later when we’re ready to start adding more bindings (likely after we GA).
9 comments
-
Anonymous
commented
Has this been implemented by any chance. All clients want to maintain their security information in Key Vault
-
Ahmet Arsan
commented
Can't use Functions without this. This is an absolute must. ETA?
-
Adam Modlin
commented
Any updates here? My customer requires all connection strings be stored in KeyVault and this is a problem for using functions.
-
Parry Kitchner
commented
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
Any idea when this might become available? I really need it. The cert approach didn't get approved by IT Security.
-
Henrik Gundersen
commented
A necessary feature, and overall great idea. Examples of securables are tokens (like Github, Slack) and certificates.
-
Joshua Toon
commented
This would be great.
-
Gerald Wiltse
commented
Food for thought, this recent development in .NET Core might reduce the amount of custom code you need for this.
-
Gerald Wiltse
commented
I believe I read somewhere that this had basically been accepted and if so, this is just a ping to update status here.
