Question

Your Dataverse environment must offload heavy order-processing logic to Azure. When an order record reaches the 'Approved' status, a message should be sent to an Azure resource that reliably queues the work, and an Azure Function must automatically process each message as it arrives without polling or a schedule. You need to choose the trigger type for the Azure Function and the mechanism to deliver Dataverse events to it. Which approach meets these requirements with the least custom code?

Accepted Answer

Register a Dataverse service endpoint (Azure Service Bus) via the Plug-in Registration Tool and use a Service Bus queue trigger on the Azure Function.

Answer

Create an Azure Function with a Timer trigger that queries Dataverse every minute for approved orders using the Web API.

Answer

Register a synchronous plug-in on Update that calls the Azure Function's HTTP endpoint directly during the Dataverse transaction.

Answer

Configure a Power Automate cloud flow with a recurrence trigger that reads approved orders and posts them to an HTTP-triggered Azure Function.