Azure Functions v4 isolated worker app targeting .NET 10, using queue and HTTP triggers with Azure Table Storage output.
| Function | Trigger | Description |
|---|---|---|
getHttpData |
HTTP (Anonymous) | Responds to GET/POST requests |
queueAdded |
Queue (salesorders) |
Reads messages from the salesorders queue and writes them to the salesorders Azure Table |
- .NET 10 SDK
- Azure Functions Core Tools v4
- Azurite or an Azure Storage account
Settings are stored in local.settings.json (not committed to source control).
| Setting | Description |
|---|---|
AzureWebJobsStorage |
Storage connection string used by the Functions runtime |
TABLE-CONN |
Connection string for the salesorders queue and table |
FUNCTIONS_WORKER_RUNTIME |
Must be dotnet-isolated |
Example local.settings.json:
{
"IsEncrypted": false,
"Values": {
"AzureWebJobsStorage": "<your-connection-string>",
"TABLE-CONN": "<your-connection-string>",
"FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated"
}
}dotnet buildfunc startThe HTTP function will be available at http://localhost:7071/api/getHttpData.
To trigger queueAdded, add a message to the salesorders queue in the storage account referenced by TABLE-CONN.
dotnet testTo manually test the HTTP trigger:
curl http://localhost:7071/api/getHttpDataTo manually test the queue trigger, use Azure Storage Explorer or the Azure portal to add a message to the salesorders queue.
dotnet publish --configuration Releasefunc azure functionapp publish <your-function-app-name>Or with the Azure CLI:
az functionapp deployment source config-zip \
--resource-group <rg> \
--name <function-app-name> \
--src bin/publish/<app>.zip| Package | Version |
|---|---|
Microsoft.Azure.Functions.Worker |
2.52.0 |
Microsoft.Azure.Functions.Worker.Sdk |
2.0.7 |
Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore |
2.1.0 |
Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues |
5.5.4 |
Microsoft.Azure.Functions.Worker.Extensions.Tables |
1.5.0 |