How can we improve Microsoft Azure Functions?

Don't 'hardcode' the storage account connection string for the storage account that backs azure functions

Currently each Function App has an application setting string "WEBSITE_CONTENTAZUREFILECONNECTIONSTRING"which is a fixed (=hardcoded) connection string. This breaks when performing key rotation on the connection string and is opaque to diagnose since that setting is automatically setup by the portal UI/wizard.

Can you instead just store the subscription ID and storage account name and then fetch the latest connection string for the storage account using the management API? This will make sure that the function app survives storage account key rotations

14 votes
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Sid shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base