Function execution model in Azure - Step-by-Step Execution

Process Flow - Function execution model

Trigger Event

↓

Function Host Receives Event

↓

Function Runtime Starts

↓

Function Code Executes

↓

Function Returns Result

↓

Host Sends Response or Continues

↓

Function Instance Idle or Terminates

This flow shows how an Azure Function starts from an event trigger, runs the code, returns a result, and then waits or stops.

Execution Sample

Azure

trigger -> function start -> execute code -> return result

This sequence shows the steps Azure Functions follow when triggered by an event.

Process Table

Step	Action	State Before	State After	Notes
1	Trigger event received	No active function	Function host ready	Event triggers function start
2	Function runtime starts	Function host ready	Function code loaded	Runtime prepares environment
3	Function code executes	Code loaded	Code executed	Function logic runs with input
4	Function returns result	Code executed	Result ready	Output prepared for caller
5	Host sends response	Result ready	Response sent	Caller receives function output
6	Function instance idle	Response sent	Waiting or terminated	Function waits for next trigger or stops

💡 Function completes execution and either waits for next event or terminates

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
Function Host	Inactive	Ready	Ready	Ready	Idle or Terminated
Function Code	Not loaded	Loaded	Executed	Executed	Idle or Terminated
Input Event	None	Received	Used	Used	Cleared
Output Result	None	None	None	Ready	Sent

Key Moments - 3 Insights

Why does the function host start before the function code executes?

The function host prepares the environment and runtime needed to run the function code, as shown in steps 1 and 2 of the execution_table.

What happens to the function instance after it returns a result?

After returning a result, the function instance either waits idle for the next trigger or terminates, as shown in step 6 of the execution_table.

Is the input event still available after the function executes?

No, the input event is used during execution and then cleared after the function returns the result, as tracked in variable_tracker.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of the function host after step 2?

A Inactive

B Idle

C Ready

D Terminated

💡 Hint

Check the 'State After' column for step 2 in the execution_table.

At which step does the function code actually run?

A Step 3

B Step 2

C Step 1

D Step 5

💡 Hint

Look for 'Function code executes' in the Action column of the execution_table.

If the function instance terminates immediately after sending the response, which step describes this?

A Step 5

B Step 6

C Step 4

D Step 3

💡 Hint

Step 6 shows the function instance becoming idle or terminated.

Concept Snapshot

Azure Function execution model:
- Trigger event starts function
- Host prepares runtime environment
- Function code runs with input
- Function returns output
- Host sends response
- Function instance waits or stops

Full Transcript

Azure Functions start when an event triggers them. The function host receives this event and prepares the runtime environment. Then, the function code executes using the input from the event. After execution, the function returns a result. The host sends this result back to the caller. Finally, the function instance either waits idle for the next trigger or terminates if no further events occur.

Practice

1. What triggers an Azure Function to run?

easy

A. Only when the server restarts

B. Manual start from the Azure portal only

C. An event like an HTTP request or timer

D. When a user logs into Azure

Solution

1. Step 1: Understand Azure Function triggers

   Azure Functions start running when an event happens, such as an HTTP request or a timer firing.

2. Step 2: Eliminate incorrect options

   Manual starts, server restarts, or user logins are not triggers for Azure Functions.

3. Final Answer:

   An event like an HTTP request or timer -> Option C

4. Quick Check:

   Azure Functions run on events = A [OK]

Hint: Azure Functions run on events, not manual or login actions [OK]

Common Mistakes:

• Thinking functions run only manually
• Confusing server restart with trigger
• Assuming user login triggers function

2. Which of the following is the correct way to define an HTTP trigger in an Azure Function's function.json file?

easy

A. {"bindings": [{"type": "httpTrigger", "direction": "in", "authLevel": "function", "methods": ["get"]}]}

B. {"bindings": [{"type": "timerTrigger", "direction": "out", "schedule": "0 */5 * * * *"}]}

C. {"bindings": [{"type": "queueTrigger", "direction": "in", "queueName": "myqueue"}]}

D. {"bindings": [{"type": "httpOutput", "direction": "in"}]}

Solution

1. Step 1: Identify HTTP trigger binding

   The correct binding for an HTTP trigger uses "type": "httpTrigger", "direction": "in", and specifies methods like "get".

2. Step 2: Check other options for errors

   {"bindings": [{"type": "timerTrigger", "direction": "out", "schedule": "0 */5 * * * *"}]} is a timer trigger with wrong direction; {"bindings": [{"type": "queueTrigger", "direction": "in", "queueName": "myqueue"}]} is a queue trigger; {"bindings": [{"type": "httpOutput", "direction": "in"}]} uses invalid "httpOutput" type with wrong direction.

3. Final Answer:

   {"bindings": [{"type": "httpTrigger", "direction": "in", "authLevel": "function", "methods": ["get"]}]} -> Option A

4. Quick Check:

   HTTP trigger binding = {"bindings": [{"type": "httpTrigger", "direction": "in", "authLevel": "function", "methods": ["get"]}]} [OK]

Hint: HTTP triggers use "httpTrigger" type with "in" direction [OK]

Common Mistakes:

• Confusing trigger type with output binding
• Using wrong direction for triggers
• Mixing trigger types like queue or timer

3. Given this Azure Function code snippet triggered by an HTTP request:

module.exports = async function (context, req) {
  context.log('Function started');
  context.res = { status: 200, body: 'Hello ' + (req.query.name || 'world') };
};

What will be the HTTP response body if the request URL is http://example.com/api?name=Alice?

medium

A. "Error: name not found"

B. "Hello world"

C. "Hello undefined"

D. "Hello Alice"

Solution

1. Step 1: Understand the code logic

   The function reads the query parameter "name" from the request. If "name" exists, it uses it; otherwise, it defaults to "world".

2. Step 2: Apply the input URL query

   The URL has "name=Alice", so the response body becomes "Hello Alice".

3. Final Answer:

   "Hello Alice" -> Option D

4. Quick Check:

   Query name present = "Hello Alice" [OK]

Hint: Check if query parameter exists; else use default [OK]

Common Mistakes:

• Ignoring query parameters
• Assuming default always used
• Confusing response body with error

4. You deployed an Azure Function with a timer trigger but it never runs. Which of these is the most likely cause?

medium

A. The schedule expression in function.json is incorrect

B. The function app is running and healthy

C. The HTTP trigger is missing

D. The function code has no output binding

Solution

1. Step 1: Check timer trigger configuration

   If the schedule expression is wrong, the timer never fires, so the function won't run.

2. Step 2: Evaluate other options

   Running app is good; missing HTTP trigger is irrelevant for timer trigger; output binding absence doesn't stop trigger execution.

3. Final Answer:

   The schedule expression in function.json is incorrect -> Option A

4. Quick Check:

   Wrong schedule = no timer run [OK]

Hint: Check cron schedule syntax for timer triggers [OK]

Common Mistakes:

• Confusing trigger types
• Ignoring schedule format errors
• Assuming output binding affects trigger

5. You want an Azure Function to process messages from a queue and then send results to a database without writing extra code to connect to the database. Which feature should you use to achieve this?

hard

A. Manually call the database API from the function

B. Use an output binding for the database

C. Use a timer trigger to poll the database

D. Write database connection code inside the function

Solution

1. Step 1: Understand output bindings

   Output bindings let functions send data to other services automatically without extra connection code.

2. Step 2: Match requirement to feature

   Using an output binding for the database allows sending results directly after processing queue messages.

3. Final Answer:

   Use an output binding for the database -> Option B

4. Quick Check:

   Output binding sends data without extra code [OK]

Hint: Output bindings connect services without manual code [OK]

Common Mistakes:

• Thinking manual code is always needed
• Confusing triggers with output bindings
• Using timer triggers incorrectly