Azure Serverless Functions

Explore Azure serverless compute options, including the Agio function, surveillance computer services and app services, with function-like execution comparable to lambda or GCP cloud functions, and surveillance capabilities.

Identify two surveillance databases, Cervalis and the actual Cause Postmus database, and pair them with a storage account (including blob storage) to build a complete surveillance application.

Provide a brief, concise definition of an Azure function, emphasizing that it runs code without provisioning servers, with support for dot net, JavaScript, Java, and Python.

Explore practical use cases for Azure functions, including HTTP-triggered surveillance APIs, microservices, static web apps, and workflows for machine learning and cloud automation.

Explore the differences between consumption, premium, and dedicated plans for Azure serverless functions. Learn about auto-scaling, cost, timeouts, virtual network access, and suitability for long-running or specific image deployments.

Discover how the trigger, input binding, and output binding orchestrate Azure serverless functions, with an endpoint triggering the function, a table as input, and JSON output sent in the response.

Learn to set up Visual Studio Code, install the Azure Functions extension, create and deploy a new function with an HTTP trigger, and redeploy updates.

Create an Azure serverless function with a blob storage trigger that copies an uploaded blob from input to an output blob folder, using bindings and a test upload.

Create an http trigger function that accepts a user id from the endpoint and passes the input value to the output, returning that user's data from a table named person.

Use an http trigger in Azure serverless functions to post data into a table and return a message that the user has been added to the database.

Learn how the host.json file provides global configuration for all functions, including function timeouts, retry policy, and http binding options, with examples of adjusting root prefixes and custom response headers.

Change the host file and the http trigger’s endpoint, remove the old prefix, and add a simple custom header to responses, then test the endpoint.

Create and link a new storage account to your function by configuring application settings and providing the storage account connection string. Test the function using the updated storage connection.

Create a new application setting named environment, set its value to broad, then build an http-triggered function that outputs that environment variable to demonstrate simple configuration.

Explore how to schedule an Azure function with a timer trigger, run a cron-like job at set intervals, and automatically send an email to an administrator when the job completes.