What's changed: Created PL-400 Chapter 5, completing the textbook (domain: Develop integrations): publishing/consuming Dataverse events (IServiceEndpointNotificationService, webhook registration in the Plug-in Registration Tool, Azure Service Bus queues/topics, Azure Event Hub, choosing listening options) and data synchronization with Dataverse (change tracking delta retrieval, alternate keys, the UpsertRequest message).
5.1Publish and consume Dataverse events
Understand publishing events via IServiceEndpointNotificationService, registering webhooks in the Plug-in Registration Tool, Azure Service Bus and Azure Event Hub, and choosing listening options.
Communicate Dataverse changes to external systems loosely coupled for scalable integration. The key is choosing the destination and mechanism.
5.1.1Publishing events (webhook and Azure messaging)
Send Dataverse events to a service endpoint via IServiceEndpointNotificationService. In the Plug-in Registration Tool, register the destination as a webhook (POST to any HTTP endpoint, sync/async), Azure Service Bus (queues/topics for loosely coupled, reliable async messaging), or Azure Event Hub (for high-throughput event streams/telemetry). Use webhook for real-time HTTP, Service Bus for reliable messaging, Event Hub for high-volume streams.
5.1.2Service Bus queues and topics
Azure Service Bus offers queues (one-to-one, a single receiver processes in order) and topics/subscriptions (pub-sub, multiple subscribers receive the same message). Placing Dataverse events on Service Bus gives reliability—messages are retained and processed later even if the receiver is down. Event Hub targets throughput for streaming over strict ordering.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.