KeyVault reference not being resolved at startup, does work when runnning

[tomkuijsten]

I'm using KeyVault references in the configuration for my functionapp and it's working fine. But I noticed that during a restart, my application insights is ingested with an exception for all my CosmosFeed functions (where the KeyVault reference is used for the connectionstring), stating: "Error indexing method 'xxxx'" and the innermostMessage "The connection string for the monitored collection is in an invalid format, please use AccountEndpoint".

Using Function App V3, on a Windows Consumption plan.

Is this something I can ignore? The functions work fine anyhow.

[v-bbalaiagar]

Hi @tomkuijsten , Thank you for your feedback! We will check for the possibilities internally and update you with the findings.

[v-bbalaiagar]

Hi @mattchenderson, Could you provide any inputs on this.

[MathieuDiepman]

I have the same issue, except that the value that I pull from keyvault is required for function startup (client secret) so my function does not work fine. During deployment the secret is updated in keyvault but the function uses an old secret during startup and crashes.

I have a manual workaround through the Azure portal. Starting and stopping the function app does not trigger a KeyVault refresh, but adding a dummy config parameter and saving it on the function app does.

[shaneholder]

I just encountered this on a Linux function app. Updating the secret in KeyVault and restarting the app does not refresh the secrets. It is not practical to wait 24 hours or change the App Configuration to force a re-read of the vault.