A compost-yard Function’s queue binding currently embeds the storage account key directly in function.json. What change correctly supplies the connection?
Select an answer to reveal the explanation.
Short Explanation
Bindings don’t want the raw key tattooed on them—they want the name of a setting. Point connection at AzureWebJobsStorage (or your custom app setting) and keep secrets out of function.json.
Full Explanation
Function bindings resolve storage connections through application settings. The connection property should name a setting (commonly AzureWebJobsStorage or a custom setting) rather than embed account keys in function.json or attributes. Putting secrets in queueName, routes, or public gists does not follow the binding connection model and increases exposure risk.