Dataverse is configured with a service endpoint that posts the execution context to an Azure Service Bus queue whenever an order row is updated. The developer must process each message in an Azure Function with built-in retry and dead-lettering for poisoned messages. Which trigger should the function use?

When Dataverse posts to an Azure Service Bus queue through a registered service endpoint, each message contains the serialized RemoteExecutionContext describing the operation, including the target, images, and user information. An Azure Function with a Service Bus trigger bound to that queue receives each message, and the developer deserializes the body into the execution context type from the Dataverse SDK to read the changed values. The Service Bus binding handles peek-lock, completes messages on success, abandons them on failure so delivery is retried, and moves messages that exceed the maximum delivery count to the dead-letter queue. An Event Hubs trigger reads from an event hub, a separate partitioned streaming service; it cannot bind to a Service Bus queue, even though Dataverse can post to either service through different endpoint types. Dataverse does not write posted messages to Blob storage, so a Blob trigger would never fire. Service Bus queues do not push messages to an arbitrary HTTP URL; auto-forwarding moves messages only to another queue or topic, so an HTTP trigger cannot be registered that way. Exam caveat: choose a topic with subscriptions when several independent consumers each need a copy of the same event. Operational check: update an order row, confirm the function logs the message ID and table name, and verify that a deliberately failing message lands in the dead-letter queue.