Azure Functions Triggers Complete Guide: HTTP / Timer / Queue / Service Bus / Cosmos DB Change Feed and All Types

Azure Functions Triggers define the conditions that cause a function to run, and they form the core of serverless event-driven architecture. More than 20 Trigger types are available, letting you launch functions from HTTP requests, schedules, queue messages, database changes, and many other events. This article walks through every major Trigger type along with Input and Output Bindings.

Major Triggers at a Glance

HTTP Trigger

Runs a function in response to an HTTP request — ideal for implementing REST APIs and webhooks.

Characteristics

• Supports HTTP methods such as GET / POST / PUT / DELETE
• Route Template (e.g., orders/{orderId}) extracts URL parameters
• Authentication Level: Anonymous (no auth), Function (Function Key required), Admin (Host Key required)
• 240-second timeout on Consumption Plan, 60 minutes on Premium
• OAuth 2.0 is easy to implement via Microsoft Entra ID integration (Easy Auth)

In production, expose functions through Azure API Management; direct exposure is recommended only for internal use. Cold start is 2-10 seconds on Consumption, but 0 seconds with Always Ready on Premium / Flex Consumption.

Timer Trigger

Runs a function on a schedule defined by a CRON expression — the go-to choice for batch processing and scheduled tasks.

CRON Expression

Azure uses an extended 6-field CRON format (second minute hour day month day-of-week).

• 0 0 8 * * *: every day at 8 AM
• 0 */15 * * * *: every 15 minutes
• 0 0 9 * * MON-FRI: weekdays at 9 AM
• 0 0 0 1 * *: midnight on the 1st of each month

Typical Use Cases

• Nightly DB backups and data aggregation
• Hourly API health checks
• Weekly report generation
• Monthly invoice generation

Timer Trigger is guaranteed to run exactly once in a distributed environment (Singleton) and will not double-fire across instances.

Queue Storage vs Service Bus

Event Grid vs Event Hub

Cosmos DB Change Feed Trigger

Runs a function on insert / update events in a Cosmos DB Container.

Typical Use Cases

• Cosmos DB data change → automatic Azure AI Search index update
• Order data insert → triggers an email notification function
• User profile update → cache invalidation
• Real-time analytics pipelines

Characteristics

• Lease Container manages checkpoints
• Parallel processing across instances (leased per partition)
• Processes only deltas since the last insert
• Supports both Pull and Push modes

The standard pattern for real-time Cosmos DB integration, also commonly used as the entry point for AI / ML data pipelines.

Blob Storage Trigger

Fires when a blob is created or updated in Blob Storage.

Typical Use Cases

• Image upload → thumbnail generation
• Video upload → encoding
• Document upload → OCR / full-text search indexing
• Log files → aggregation processing

Caveats

• Polling-based, with a delay of several to tens of seconds
• For high-frequency, low-latency requirements, use Event Grid Trigger instead (push-delivered Blob Created events)
• For large blobs, the Blob Storage Queue Trigger pattern is also effective

Input / Output Binding

Bindings declaratively integrate Triggers with other services — you can implement integration with other Azure services using just JSON configuration, with no SDK code required.

How It Works

• Input Binding: fetches data from another service when the function starts (e.g., retrieve the relevant record from Cosmos DB)
• Output Binding: writes data to another service after the function runs (e.g., send a message to a Storage Queue)

Example: HTTP Trigger + Cosmos DB Input + Service Bus Output

{
  "bindings": [
    {
      "type": "httpTrigger",
      "name": "req",
      "route": "orders/{orderId}",
      "methods": ["get"]
    },
    {
      "type": "cosmosDB",
      "name": "order",
      "direction": "in",
      "databaseName": "Orders",
      "collectionName": "Items",
      "id": "{orderId}",
      "partitionKey": "{orderId}",
      "connectionStringSetting": "CosmosDBConnection"
    },
    {
      "type": "serviceBus",
      "name": "outputMessage",
      "direction": "out",
      "queueName": "processed-orders",
      "connection": "ServiceBusConnection"
    }
  ]
}

Supported Services

• Storage (Blob/Queue/Table)
• Cosmos DB
• Service Bus
• Event Hub
• Event Grid
• SignalR
• SendGrid (email)
• Twilio (SMS)
• GraphQL
• SQL (Preview)

Durable Functions

Durable Functions is an extension of Functions that enables stateful orchestration — long-running workflows, human-approval waits, and complex state transitions.

• Function Chaining: sequential execution (A → B → C)
• Fan-out / Fan-in: parallel execution with result aggregation
• Async HTTP API: async API for long-running processing
• Monitor: periodic status checks
• Human Interaction: approval-wait workflows

Best Practices

1. One Trigger per Function (functions with multiple Triggers are discouraged)
2. Use Input/Output Bindings for cross-service integration; avoid direct SDK calls
3. Expose HTTP Triggers via API Management; direct exposure is for internal use only
4. Timer Trigger prevents duplicate firing in distributed environments (Singleton behavior)
5. Move long-running processing to Durable Functions or Container Apps
6. Service Bus for enterprise, Queue Storage for lightweight tasks
7. Event Hub for high-volume streaming, Event Grid for reactive scenarios
8. Use Change Feed Trigger to make Cosmos DB integration real-time
9. Use Application Insights to observe function executions
10. Use Managed Identity to authenticate to other Azure services (eliminate connection strings)

Related Certifications

• AZ-204 (Developer Associate): the flagship certification — Domain 1 covers this area in depth
• AZ-305 (Solutions Architect Expert): serverless design from an architect's perspective
• AZ-400 (DevOps Engineer Expert): CI/CD pipelines for Functions
• AI-103 (2026-06 GA): AI pipelines built with Cosmos DB Change Feed + Functions

Frequently Asked Questions

The technical information in this article is based on the Azure Functions Documentation. This article is not an official product of Microsoft Corporation and has no affiliation or sponsorship with Microsoft. Microsoft and Azure are trademarks of the Microsoft group of companies. Information is based on official public materials as of May 24, 2026. Always check the official pages for the latest information.