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.
Cues: "publish events" = IServiceEndpointNotificationService. "POST to any HTTP endpoint" = webhook. "loosely coupled, reliable async messaging" = Azure Service Bus. "high-throughput event stream/telemetry" = Azure Event Hub. "one-to-one" = queue; "pub-sub" = topic. Register in the Plug-in Registration Tool.
Watch the mix-ups: (1) webhook (direct HTTP) vs Service Bus (queues/topics) vs Event Hub (streams). (2) Service Bus = reliable messaging / Event Hub = high-throughput streams—different uses. (3) Queue (one-to-one) vs topic (pub-sub). (4) Register in the Plug-in Registration Tool.
5.1.3Section summary
- Publish via IServiceEndpointNotificationService to webhook/Service Bus/Event Hub
- Service Bus=reliable messaging (queue one-to-one/topic pub-sub); Event Hub=high-throughput streams
- Register in the Plug-in Registration Tool; choose the listener by use case
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want to send Dataverse events to loosely coupled, reliable async messaging that retains messages even if the receiver is temporarily down. Best?
Q2. You want to POST Dataverse changes to any HTTP endpoint in real time. Best?
Q3. You want to ingest many events as a high-throughput stream for telemetry analytics. Best?
Q4. Which service publishes events from Dataverse to a service endpoint (e.g., Service Bus)?
Q5. Which correctly distinguishes Azure Service Bus queues from topics?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.