Trigger types (HTTP, Timer, Blob, Queue) in Azure - Mini Project: Build & Apply

Azure Function Trigger Types

📖 Scenario: You are building an Azure Function app that responds to different events in the cloud. These events include HTTP requests, scheduled timer events, new files uploaded to storage, and messages added to a queue.This project will guide you to create simple Azure Functions with four different trigger types: HTTP trigger, Timer trigger, Blob trigger, and Queue trigger.

🎯 Goal: Create four Azure Functions each with a different trigger type: HTTP, Timer, Blob, and Queue. Each function should have the correct trigger configuration in the function.json file.

📋 What You'll Learn

Create an HTTP triggered Azure Function named HttpTriggerFunction

Create a Timer triggered Azure Function named TimerTriggerFunction that runs every 5 minutes

Create a Blob triggered Azure Function named BlobTriggerFunction that triggers on new blobs in container sample-container

Create a Queue triggered Azure Function named QueueTriggerFunction that triggers on messages in queue sample-queue

💡 Why This Matters

🌍 Real World

Azure Functions are used to run small pieces of code in response to events like web requests, scheduled jobs, file uploads, or queue messages without managing servers.

💼 Career

Understanding Azure Function triggers is essential for cloud developers and architects to build scalable, event-driven applications on Microsoft Azure.

1

Create HTTP Trigger Function Configuration

Create a file named function.json for the HTTP triggered Azure Function called HttpTriggerFunction. The trigger type must be httpTrigger with methods get and post. The authLevel must be function.

Azure

{
  // Your code here
}

Need a hint?

Use httpTrigger as the type and specify methods as ["get", "post"].

2

Add Timer Trigger Function Configuration

Add a new function.json configuration for the Timer triggered Azure Function named TimerTriggerFunction. Use trigger type timerTrigger with a schedule that runs every 5 minutes using a CRON expression. The direction must be in and the name must be myTimer.

Azure

{
  "bindings": [
    {
      "authLevel": "function",
      "type": "httpTrigger",
      "direction": "in",
      "name": "req",
      "methods": ["get", "post"]
    },
    {
      "type": "http",
      "direction": "out",
      "name": "res"
    },
    {
      // Your code here for timer trigger
    }
  ]
}

Need a hint?

The CRON expression 0 */5 * * * * runs every 5 minutes.

3

Add Blob Trigger Function Configuration

Add a new function.json configuration for the Blob triggered Azure Function named BlobTriggerFunction. Use trigger type blobTrigger with the path set to sample-container/{name}. The direction must be in and the name must be myBlob.

Azure

{
  "bindings": [
    {
      "authLevel": "function",
      "type": "httpTrigger",
      "direction": "in",
      "name": "req",
      "methods": ["get", "post"]
    },
    {
      "type": "http",
      "direction": "out",
      "name": "res"
    },
    {
      "type": "timerTrigger",
      "direction": "in",
      "name": "myTimer",
      "schedule": "0 */5 * * * *"
    },
    {
      // Your code here for blob trigger
    }
  ]
}

Need a hint?

Use blobTrigger type and set path to sample-container/{name}.

4

Add Queue Trigger Function Configuration

Add a new function.json configuration for the Queue triggered Azure Function named QueueTriggerFunction. Use trigger type queueTrigger with the queue name set to sample-queue. The direction must be in and the name must be myQueueItem.

Azure

{
  "bindings": [
    {
      "authLevel": "function",
      "type": "httpTrigger",
      "direction": "in",
      "name": "req",
      "methods": ["get", "post"]
    },
    {
      "type": "http",
      "direction": "out",
      "name": "res"
    },
    {
      "type": "timerTrigger",
      "direction": "in",
      "name": "myTimer",
      "schedule": "0 */5 * * * *"
    },
    {
      "type": "blobTrigger",
      "direction": "in",
      "name": "myBlob",
      "path": "sample-container/{name}"
    },
    {
      // Your code here for queue trigger
    }
  ]
}

Need a hint?

Use queueTrigger type and set queueName to sample-queue.