Input/Output Binding on Azure Durable Activity Function

Ana 136 Reputation points

I need to update Azure Table from Azure Durable Function.

The code works nicely if I put it in the HTTP trigger.


Push-OutputBinding -Name TableBinding -Value @{
        PartitionKey            =   $partitionKey
        RowKey                  =   $rowkey
        SomeData              =   $SomeData



  "bindings": [
      "authLevel": "function",
      "name": "Request",
      "type": "httpTrigger",
      "direction": "in",
      "route": "orchestrators/{FunctionName}",
      "methods": [
      "type": "http",
      "direction": "out",
      "name": "Response"
      "name": "starter",
      "type": "orchestrationClient",
      "direction": "in"
      "tableName": "myTable",
      "connection": "MYCONNECTIONSTRING",
      "name": "TableBinding",
      "type": "table",
      "direction": "out"

It doesn't do ANYTHING if I put it in Activity Function. No error and no entry in the table. Nothing happens. Stream log glides through as if everything executed correctly, but there are no entries in the table.

Do Durable Activity Functions support extra input/output bindings?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
3,994 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Mike Urnun 9,001 Reputation points Microsoft Employee

    @Ana You can trigger an activity function only from an orchestrator function. If you had it already working with the HTTP Trigger and you needed to incorporate more stateful workflows to it, Logic Apps might be a good and easy way to do it: Call functions from Azure Logic Apps

  2. Luc Bergeron 11 Reputation points

    I'm getting the same issue while using an queue as output. Durable function documentation state that it's possible to use them :

    @Ana have you been able to fix this?

    0 comments No comments

  3. alex 1 Reputation point

    I know this is an older question but I am too having issues with CosmosDB output bindings, experiencing the exact same behavior that @Ana and @Luc Bergeron described. This is only in true when I try this binding using a durable (activity) functions. Are output bindings for cosmos, queues, etc supported at all using activity functions?

    0 comments No comments