Input and output bindings in Azure - Commands & Configuration

Introduction

Input and output bindings in Azure Functions let your function easily connect to other services without writing extra code. They help your function get data from or send data to services like storage or databases automatically.

When you want your function to automatically read messages from a queue without manual polling.

When you want to save processed data to a database without writing database connection code.

When you want to trigger your function when a new file is uploaded to cloud storage.

When you want to send output data to a service like Event Hub or Blob Storage automatically.

When you want to simplify your function code by letting Azure handle service connections.

Config File - function.json

function.json

{
  "bindings": [
    {
      "name": "myQueueItem",
      "type": "queueTrigger",
      "direction": "in",
      "queueName": "myqueue-items",
      "connection": "AzureWebJobsStorage"
    },
    {
      "name": "$return",
      "type": "blob",
      "direction": "out",
      "path": "output-container/{rand-guid}.txt",
      "connection": "AzureWebJobsStorage"
    }
  ]
}

This file defines two bindings for an Azure Function:

• Input binding: Reads messages from the queue named myqueue-items. The function triggers when a new message arrives.
• Output binding: Saves the function's return value as a blob file in output-container with a random GUID filename.
• Connection: Both bindings use the storage account connection string named AzureWebJobsStorage.

Commands

Initialize a new Azure Functions app with the .NET runtime to prepare the environment.

Terminal

func init MyFunctionApp --worker-runtime dotnet

Expected Output

Creating new Azure Functions project in C:\Users\user\MyFunctionApp

Project created successfully.

→

--worker-runtime - Specifies the language runtime for the function app.

Create a new function named QueueTriggerFunction using the queue trigger template with anonymous access.

Terminal

func new --name QueueTriggerFunction --template "Queue trigger" --authlevel anonymous

Expected Output

Created new function 'QueueTriggerFunction' using template 'Queue trigger'.

→

--name - Sets the function name.

→

--template - Specifies the trigger type template.

Start the function app locally to test the input and output bindings in action.

Terminal

func start

Expected Output

Hosting environment: Production

Content root path: C:\Users\user\MyFunctionApp

Now listening on: http://localhost:7071

Application started. Press Ctrl+C to shut down.

Send a test message to the queue to trigger the function and see the output binding save a blob.

Terminal

az storage message put --queue-name myqueue-items --content "Hello from queue" --account-name mystorageaccount

Expected Output

{"messageId":"12345","popReceipt":"abcde"}

→

--queue-name - Specifies the target queue.

→

--content - The message content to send.

Key Concept

If you remember nothing else from this pattern, remember: input and output bindings let your function automatically connect to other services without extra code.

Common Mistakes

Not specifying the correct connection string name in the binding configuration.

The function cannot connect to the service without the right connection string, causing runtime errors.

Always use the exact connection string name defined in your application settings, like AzureWebJobsStorage.

Using the wrong direction (in/out) for a binding.

The function will not trigger or output data correctly if the direction is wrong.

Set input bindings with "direction": "in" and output bindings with "direction": "out".

Forgetting to start the function app locally before testing bindings.

The function won't run and respond to triggers if the app is not running.

Always run 'func start' to launch the function app before sending test messages.

Summary

Initialize an Azure Functions app with the desired runtime.

Create a function with input and output bindings defined in function.json.

Start the function app locally to listen for triggers.

Send test data to the input service to trigger the function and produce output automatically.

Practice

1. What is the main purpose of input and output bindings in Azure Functions?

easy

A. To create user interfaces for Azure Functions

B. To write complex code for cloud service connections

C. To connect your function easily to cloud services without extra code

D. To manage virtual machines in Azure

Solution

1. Step 1: Understand the role of bindings

   Bindings let your function connect to cloud services like queues or blobs without writing extra code.

2. Step 2: Compare options

   Only To connect your function easily to cloud services without extra code describes this easy connection purpose. Others mention unrelated tasks.

3. Final Answer:

   To connect your function easily to cloud services without extra code -> Option C

4. Quick Check:

   Bindings simplify cloud connections = A [OK]

Hint: Bindings simplify cloud connections by reducing code [OK]

Common Mistakes:

• Thinking bindings create user interfaces
• Confusing bindings with VM management
• Assuming bindings require complex code

2. Which of the following is the correct syntax to declare an output binding in an Azure Function JSON configuration?

easy

A. { "type": "blob", "direction": "out", "name": "outputBlob" }

B. { "type": "table", "direction": "in", "name": "inputTable" }

C. { "type": "httpTrigger", "direction": "out", "name": "req" }

D. { "type": "queue", "direction": "in", "name": "myQueueItem" }

Solution

1. Step 1: Identify output binding syntax

   Output bindings use "direction": "out" and specify the resource type and name.

2. Step 2: Check each option

   { "type": "blob", "direction": "out", "name": "outputBlob" } correctly uses "direction": "out" with a blob type. Others either have "in" direction or wrong types for output.

3. Final Answer:

   { "type": "blob", "direction": "out", "name": "outputBlob" } -> Option A

4. Quick Check:

   Output binding = direction: out [OK]

Hint: Output bindings always use "direction": "out" in config [OK]

Common Mistakes:

• Using "in" direction for output bindings
• Confusing trigger types with bindings
• Wrong resource type for output

3. Given this Azure Function code snippet with bindings:

{
  "bindings": [
    { "name": "inputQueueItem", "type": "queueTrigger", "direction": "in", "queueName": "myqueue" },
    { "name": "outputBlob", "type": "blob", "direction": "out", "path": "samples-output/{rand-guid}.txt" }
  ]
}

What happens when a new message arrives in the queue?

medium

A. The function triggers but cannot write to blob because output binding is missing

B. The function triggers and deletes the queue message without output

C. The function does not trigger because queueTrigger is invalid

D. The function triggers, reads the queue message, and writes a new blob file with a random name

Solution

1. Step 1: Understand the bindings

   The queueTrigger input binding triggers the function when a message arrives. The output binding writes a blob file with a random GUID name.

2. Step 2: Analyze the behavior

   When a message arrives, the function runs, reads the message, and writes a blob file as specified.

3. Final Answer:

   The function triggers, reads the queue message, and writes a new blob file with a random name -> Option D

4. Quick Check:

   QueueTrigger input + blob output = trigger and write blob [OK]

Hint: QueueTrigger input starts function; output binding writes data [OK]

Common Mistakes:

• Thinking output binding is missing
• Assuming function does not trigger
• Confusing queueTrigger with other triggers

4. You have this binding configuration in your Azure Function:

{
  "bindings": [
    { "name": "inputBlob", "type": "blob", "direction": "in", "path": "samples/input.txt" },
    { "name": "outputQueueItem", "type": "queue", "direction": "out", "queueName": "outputqueue" }
  ]
}

The function code tries to assign a string to outputQueue, but you get an error. What is the likely cause?

medium

A. The input binding type "blob" cannot be used as input

B. The output binding name does not match the function parameter name

C. The output binding type "queue" requires a special object, not a string

D. The function code must not assign values to output bindings

Solution

1. Step 1: Check binding names and code parameters

   The binding name "outputQueueItem" must exactly match the function parameter name used in code to assign output.

2. Step 2: Identify mismatch cause

   If names differ, the function cannot bind the output correctly, causing errors when assigning values.

3. Final Answer:

   The output binding name does not match the function parameter name -> Option B

4. Quick Check:

   Binding names must match code parameters [OK]

Hint: Binding names must exactly match function parameters [OK]

Common Mistakes:

• Assuming blob input is invalid
• Thinking output queue needs special object
• Believing outputs cannot be assigned in code

5. You want an Azure Function to read messages from a Service Bus queue and write processed results to a Cosmos DB collection. Which binding configuration correctly connects these services?

hard

A. { "name": "msg", "type": "serviceBusTrigger", "direction": "in", "queueName": "inputqueue" }, { "name": "outputDocument", "type": "cosmosDB", "direction": "out", "databaseName": "mydb", "collectionName": "results" }

B. { "name": "msg", "type": "queueTrigger", "direction": "in", "queueName": "inputqueue" }, { "name": "outputDocument", "type": "blob", "direction": "out", "path": "results/{id}.json" }

C. { "name": "msg", "type": "serviceBusTrigger", "direction": "out", "queueName": "inputqueue" }, { "name": "outputDocument", "type": "cosmosDB", "direction": "in", "databaseName": "mydb", "collectionName": "results" }

D. { "name": "msg", "type": "serviceBusTrigger", "direction": "in", "queueName": "inputqueue" }, { "name": "outputDocument", "type": "table", "direction": "out", "tableName": "results" }

Solution

1. Step 1: Identify correct trigger and output types

   Service Bus messages use "serviceBusTrigger" with "direction": "in". Cosmos DB output uses "cosmosDB" with "direction": "out" and database/collection names.

2. Step 2: Check each option

   { "name": "msg", "type": "serviceBusTrigger", "direction": "in", "queueName": "inputqueue" }, { "name": "outputDocument", "type": "cosmosDB", "direction": "out", "databaseName": "mydb", "collectionName": "results" } correctly sets input as Service Bus trigger and output as Cosmos DB. Others have wrong directions or types.

3. Final Answer:

   { "name": "msg", "type": "serviceBusTrigger", "direction": "in", "queueName": "inputqueue" }, { "name": "outputDocument", "type": "cosmosDB", "direction": "out", "databaseName": "mydb", "collectionName": "results" } -> Option A

4. Quick Check:

   ServiceBusTrigger in + CosmosDB out = C [OK]

Hint: Service Bus triggers are input; Cosmos DB bindings are output [OK]

Common Mistakes:

• Swapping input/output directions
• Using wrong binding types for services
• Confusing queueTrigger with serviceBusTrigger