Azure Functions Overview
Azure Functions Overview
Pay per use pricing model Pay for only run time of the function
02
01 Triggers 01
03 03
04 04
Integration
Azure functions integrate with
several Azure and 3rd Party
services. They can trigger your
05 functions or serve as input and 05
output for your code
Scaling & Hosting
Azure Functions runs in two modes
• Consumption plan
• This is a serverless plan that scales automatically and you are charged for compute resources
only when your functions are running.
• Billing is based on number of executions, execution time, and memory used. Billing is
aggregated across all functions within a function app
• Your function apps run on dedicated VMs on Basic, Standard, Premium, and Isolated SKUs,
which is the same as other App Service apps.
• Go for it when you have underutilized VMs, function apps that run continuously, code runs for
longer than 10 minutes etc.
Triggers & Bindings
• Trigger - A trigger defines how a function is invoked. A function can have only one trigger. Triggers
have associated data, which is usually the payload that triggered the function.
• Bindings - Input and output bindings provide a declarative way to connect to data from within your
code. Bindings are optional and a function can have multiple input and output bindings.
• Azure portal - Triggers and bindings are configured in a function.json file. The portal provides
a UI for this configuration but you can edit directly.
• Visual studio - You configure triggers and bindings by decorating methods and parameters
with attributes.