Lets an Azure Function receive data from, or send data to, other services just by declaring it (for example reading a blob or putting a message on a queue) rather than writing connection logic. Triggers are really a special case of input binding.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Bindings in context, with comparison tables and the common traps.
Terms in this definition
- BLOB
Short for binary large object: raw binary data, like pictures, audio, video or documents, that only an application can make sense of. Azure keeps these files as blobs in Blob Storage.
- Connection
Resource that attaches a virtual network gateway to its peer, which may be an ExpressRoute circuit, a second VNet gateway (Vnet2Vnet) or a local network gateway over IPsec. Resetting it recovers a single tunnel and avoids rebooting the whole gateway.
- Input binding
An Azure Functions binding that declaratively supplies additional data to a function, so no client code needs writing by hand.
Related terms
- Extension bundle
Non-.NET Azure Functions apps switch this on in host.json to get a tested, versioned collection of binding extensions. Only HTTP and timer bindings ship built in; all others arrive through it.
- Kubernetes RBAC
Authorisation built into Kubernetes, using Roles and ClusterRoles plus bindings. Signing in to AKS with Entra gives no rights on its own; users or groups need a binding first.
- Python v2 programming model
The recommended way to write new Python apps in Azure Functions, using decorators in function_app.py (or blueprints) to declare triggers and bindings rather than function.json files.