A company plans to create an order processing app. When orders are created, the app will perform complex business logic and integrate with several…

The requirement specifies that processing can take up to six minutes. Standard Dataverse extensibility points like Plug-ins (synchronous or asynchronous) and Workflows have a hard execution timeout of two minutes (120 seconds). Any process exceeding this limit will be killed by the sandbox service.

By using a webhook to trigger an Azure Function, you offload the long-running "complex business logic" and external integrations to a platform designed for scale and extended execution. While Dataverse transactions cannot span across an external Azure Function call natively, the "one operation" requirement for the external logic is best handled within the Function's own logic (e.g., using a Saga pattern or internal transactions) to ensure the external systems and Dataverse records are synchronized correctly without hitting the 2-minute sandbox platform limit.

A. an asynchronous workflow that uses a custom workflow activity Workflows (including custom activities) are subject to the 2-minute timeout limit of the Dataverse sandbox service; a 6-minute process would result in a timeout error.

B. a real-time workflow that uses a custom action Real-time workflows run synchronously within the main database transaction and are strictly limited to the 2-minute timeout, making them unsuitable for 6-minute operations.

D. an asynchronous plug-in Although asynchronous, plug-ins executed via the sandbox service are still enforced by the 120-second timeout. They cannot sustain a 6-minute execution window.

Microsoft Learn (Power Platform Documentation): "Event framework," Section: Run-time execution constraints. Specifically cites the 2-minute (120-second) timeout for plug-ins and workflow activities.

Microsoft Learn (Dataverse Developer Guide): "Use Webhooks to externalize business logic." Explains using webhooks to send data to external services (like Azure Functions) when processing exceeds sandbox limits.

Azure Docs: "Azure Functions serverless execution." Details the default 5-minute timeout (Consumption plan) and up to 30-minute/unlimited (Premium/App Service plans), accommodating the 6-minute requirement.

Microsoft Learn: "Write a custom workflow activity," Section: Timeouts. Confirms that the sandbox limit applies to all custom code within the Dataverse process execution.