Azure Functions Integration

← Back to DP-420 Terminology Reference

Category: Integration & Analytics

Summary: Serverless compute triggered by Cosmos DB change feed for event-driven processing, denormalization, and data movement.

Overview

Azure Functions is a serverless, event-driven compute platform that integrates natively with Azure Cosmos DB through triggers, input bindings, and output bindings. The Azure Cosmos DB trigger uses the change feed processor under the hood to automatically execute code in response to item inserts and updates across partitions, maintaining state via a leases container. Common architectural patterns tested on the DP-420 exam include using Azure Functions + Change Feed for real-time denormalization, cross-container referential integrity enforcement, materializing aggregates, event streaming to Event Hubs or Service Bus, and archiving historical data to Azure Blob Storage.

Example (C# Isolated Worker): Azure Functions Cosmos DB Trigger with Output Binding

[Function("ProcessOrderChangeFeed")]
[CosmosDBOutput("ecommerce", "orderSummaries", Connection = "CosmosDBConnection")]
public static OrderSummary Run(
    [CosmosDBTrigger(
        databaseName: "ecommerce",
        containerName: "orders",
        Connection = "CosmosDBConnection",
        LeaseContainerName: "leases",
        CreateLeaseContainerIfNotExists = true)] IReadOnlyList<Order> input,
    FunctionContext context)
{
    var logger = context.GetLogger("ProcessOrderChangeFeed");
    logger.LogInformation("Processing {Count} changed orders", input.Count);

    // Compute denormalized summary to write to orderSummaries container via output binding
    return new OrderSummary
    {
        Id = Guid.NewGuid().ToString(),
        CustomerId = input[0].CustomerId,
        LastProcessedUtc = DateTime.UtcNow,
        TotalOrdersCount = input.Count
    };
}

This serverless function triggers on inserts/updates from the orders container using the change feed, processes the batch, and writes a denormalized record to orderSummaries via a declarative CosmosDBOutput binding.

More Info & Links

• Microsoft Learn: Azure Cosmos DB trigger for Azure Functions
• Microsoft Learn: Azure Cosmos DB input and output bindings for Azure Functions
• Microsoft Learn: Serverless computing with Azure Cosmos DB and Azure Functions

DP-420 Style Practice Questions

Q1. What mechanism does the Azure Functions Azure Cosmos DB trigger use to detect data changes across partitions?

• A. The Azure Cosmos DB change feed, managed via a leases container to track state and checkpoints across partitions
• B. Polling SQL API queries executed against the container every 60 seconds
• C. Continuous point-in-time restore transaction logs exported to storage
• D. Server-side JavaScript triggers that invoke an external HTTP webhook

Q2. Which scenario represents a common DP-420 design pattern combining Azure Cosmos DB change feed with Azure Functions?

• A. Materializing and denormalizing data into another container to optimize read queries
• B. Replacing the need for a partition key in large containers
• C. Converting transactional store data directly into column-oriented analytical store format
• D. Generating periodic backup snapshots on a 4-hour schedule

Q3. What happens when an Azure Functions output binding writes to an Azure Cosmos DB container?

• A. It automatically creates or upserts documents using the configured connection and container name without custom SDK boilerplate code
• B. It always forces an expensive cross-partition query before writing
• C. It bypasses RU charges by writing through the analytical store
• D. It automatically migrates the container to autoscale throughput

Answer Key

Answers are listed at the very end so you can attempt the questions first.

• Q1 (Azure Functions Integration): A. The Azure Cosmos DB change feed, managed via a leases container to track state and checkpoints across partitions — The Azure Cosmos DB trigger is built on the Change Feed Processor, which uses a leases container to track checkpoints and distribute partition processing across function instances.
• Q2 (Azure Functions Integration): A. Materializing and denormalizing data into another container to optimize read queries — Change feed-triggered Azure Functions are standard for asynchronous denormalization, cross-container synchronization, and maintaining materialized views.
• Q3 (Azure Functions Integration): A. It automatically creates or upserts documents using the configured connection and container name without custom SDK boilerplate code — Cosmos DB output bindings allow declarative writing/upserting of documents directly from the function return value or out parameters without managing SDK clients manually.

---

DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB — term detail page