Azure Functions, durable functions

Explore Azure functions in the Azure portal, comparing consumption and premium plans, auto-scaling and execution time limits, with http and timer triggers and binding examples.

Explore http trigger bindings in Azure Functions, including function.json and test scenarios for get, post, and put requests, with name handling and 200 or 404 responses.

Learn the time trigger in Azure Functions, using cron expressions to schedule every minute, log timestamps, and fix configuration by setting the Azure Web Jobs Storage connection string.

Create an Azure blob storage trigger by setting the container and storage account. Inspect function.json for the input binding and blob name expression, then upload files and monitor logs.

Develop and deploy Azure Functions locally with Core Tools across platforms, then initialize a dotnet function app in the current folder using func init.

Create a new function using the Cosmos DB trigger template, name the function, and review the populated file showing the function name, run method, database name, and container name.

Create an Azure function in Visual Studio 2022 using an empty template with dotnet 6.0, targeting function version 4, and configure host.json and local.settings.json for development using the storage emulator.

Create an http trigger in Visual Studio Code using C# and .NET 6 with the Azure extension; scaffold a new anonymous http function, then run, debug, and test with Postman.

Install the Azure Functions extension in Visual Studio Code to create an HTTP trigger in TypeScript, then test locally with Postman by passing a name in query or body.

Create an http trigger in an Azure function using Visual Studio and TypeScript, set anonymous authorization, run locally, and test with Postman to verify a 200 response.

Explore how Azure Functions automate processing of user generated content—upload, resize and encode media, analyze with cognitive services, and publish results to a social platform via blob storage triggers.

Create a blob trigger azure function that resizes images uploaded to the normal size container and stores them in the reduced size container using a connection string in local settings.

Create an Azure Functions blob-trigger project in Visual Studio, configure the connection in local settings, implement an image resizer service, and install the ImageSharp library to resize uploaded images.

implement a blob-trigger image resize function by loading an image from the Emma Sharpe Library, resizing it, and saving the output with a jpeg encoder; configure dependency injection via startup.

Add the startup attribute to specify the startup name, implement configure to register the image resizer interface for injection, and inject it into the class.

Implement a blob-trigger image resize in Azure Functions, wiring input and output blobs to a reduced size container, with a try block and breakpoints for debugging.

Deploy the blob trigger image resize function by publishing to a Windows virtual machine and selecting storage.

Monitor a blob-triggered image resize function in an Azure Functions app by configuring Application Insights, reviewing logs and success/error counts, and adding environment settings with the connection string.

Upload an image to the normal size container and press F5 to see it reduced to about four kilo in the reduced size container, versus 13 in the original.

Create a new Azure Cosmos DB account for the project in the Azure portal by selecting NoSQL, naming the data account, and initiating deployment.

Use data explorer in Azure portal to create a test db and container, set a partition key, add items, and copy the connection string for local settings in Visual Studio.

Set up an http trigger binding to Cosmos DB in function.json, configuring database and container names, and a binding parameter for the id query, using wizard or manual setup.

Learn to generate local.settings.json automatically in Visual Studio Code for Azure Functions, populating the cosmos database connection string and Azure WebJobs storage by downloading remote settings from Azure Functions.

Refactor Azure Functions to fetch a Cosmos DB document by id using Postman, returning 200 with the record or 404 when not found.

Create a queue trigger function named read message from q, configure the q trigger and connection string from account storage, update local settings, and verify the project builds without errors.

Demonstrates handling an exception during trigger execution by pushing the message to the queue, retrying reads until a threshold, and moving to a Poisson queue after five dequeue attempts.

Demonstrates building an ASP.NET core web api with get and post methods, swagger integration, and posting weather forecast data to an Azure trigger function via HTTP client.

Learn to configure a Cosmos DB trigger with a leases collection, monitor document changes, and publish updated items to an Azure Event Hub using the Event Hubs extension.

Configure an event hub trigger in a logic app using the event hub name and connection string, decode base64 content from cosmos db events, and verify logs.