Question

You are registering an Azure Service Bus service endpoint using the Plug-in Registration Tool to publish Dataverse Account events to a downstream integration. Testing reveals that some messages containing large custom entity payloads fail to post while smaller ones succeed. The team confirms the Service Bus queue and credentials are correct. Which explanation and remediation should you present?

Accepted Answer

The Dataverse asynchronous service enforces a message size limit on the serialized execution context; register the step to post only the entity ID (or a reduced payload) and have the listener retrieve full data via the Web API.

Answer

Service Bus endpoints cannot carry custom entity data at all; switch the endpoint to an Azure Event Hub, which has no message size restrictions.

Answer

The plug-in step must be registered in the synchronous pipeline so the full context is delivered before the transaction completes.

Answer

You must enable change tracking on the entity so that large payloads are automatically chunked across multiple Service Bus messages.