A city radio-archive Function needs a Blob Storage API that the available input binding does not expose. A teammate insists every Blob call must go through a binding. What is the correct guidance?
Select an answer to reveal the explanation.
Short Explanation
Bindings are power tools, not handcuffs. When the binding surface is too thin, open a Blob SDK client in code and get the job done—Functions never made bindings mandatory.
Full Explanation
Official Azure Functions guidance treats input and output bindings as optional helpers that avoid hard-coded clients when they fit the scenario. Developers may instantiate service SDKs inside a function when a needed API is not available through a binding. Host validation does not ban SDK usage; VMs and Durable-only rules are incorrect for this AZ-204 Functions binding topic.