Question

A developer is building an Azure Function that must process a large batch of Dataverse records, calling an external API for each record. The total operation frequently exceeds 10 minutes and must survive host restarts, track progress across steps, and be triggered on demand from a Power Automate flow. The function currently runs on the Consumption plan and times out. Which approach best meets these requirements?

Accepted Answer

Refactor the logic into a Durable Functions orchestration with activity functions, keeping state in the Durable Task framework and exposing an HTTP-trigger starter.

Answer

Increase the functionTimeout setting in host.json to 60 minutes and keep the single HTTP-triggered function on the Consumption plan.

Answer

Move all record processing into a synchronous Dataverse plug-in registered on a custom API so it runs inside the platform transaction.

Answer

Split the work into multiple parallel HTTP requests from Power Automate using an Apply to each loop with concurrency enabled against the same function.