KeyVault cannot be used by multiple function apps

[sherman89]

Bringing much needed attention to: #2305

I'm sorry for the duplicate, but I cannot believe such an issue is still open (and assigned!) after 2 years!

At least allow us to configure custom names for the secrets or something, that actually would be ideal. Using a KV per function app is terrible design!

Thank you!

[JAdluri]

Thank you @sherman89 for reporting. Please let us know steps to repro the issue .

[JAdluri]

As there is no recent activity , couldnt keep this opened .

[sherman89]

@JAdluri Open the link #2305 ...

[JAdluri]

Could you please elaborate the need.

[sherman89]

@JAdluri Basically multiple Azure Functions cannot use the same Key Vault for storing the function key because the key name is not unique per function app, which causes conflicts.

It would be nice if each key includes some unique identifier for the function app to avoid this conflict.

Thanks!

[JAdluri]

Will look into the issue and let you know furtherly

[sherman89]

@JAdluri Sorry but any news on this? or maybe at least a workaround? I need to add KV authorization to my Function App, and have to decide whether I do it by hand due to this limitation, or am I able to confidently use the built-in mechanism without having to later worry about conflicts.

Thank you!

[JAdluri]

Hello @sherman89 Please add KV authorization in your function apps for better work feasibility