Dataverse Azure integration: Service Bus vs Event Hubs vs webhook listeners
Verdict: Publish Dataverse events to Azure Service Bus, Event Hubs or a webhook. Service Bus and Event Hubs triggers give a function reliable, retry-capable processing. A Service Bus payload over 192 KB has properties stripped or the send fails.
| Criterion | Azure Service Bus | Azure Event Hubs | Webhook |
|---|---|---|---|
| Listener shape | App on a queue, topic or relay endpoint | App consuming from an Event Hubs solution | Web service receiving an HTTP POST with JSON |
| Best for | High-throughput queuing | Streaming, telemetry-style ingestion | Simple HTTP consumers hosted anywhere |
Rules
- Dataverse publishes events to three listener types through a registered service endpoint: Azure Service Bus, a webhook over HTTP, and Azure Event Hubs.
- For reliable message processing with platform-handled retries, use a Queue Storage, Service Bus or Event Hubs trigger on the Azure Function, not a timer or HTTP-polling trigger.
Traps
- When a Service Bus payload exceeds 192 KB, InputParameters and PreEntityImages are removed; if it still exceeds 192 KB the send fails. There is no gzip compression or message splitting.
- There is no automatic failover from Service Bus to Event Hubs; they are separate, independently configured integration targets.