🔒 Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901
Guided PL-400 Domain 6
Domain 6 — Module 2 of 3 67%
25 of 26 overall

PL-400 Study Guide

Domain 1: Create a Technical Design

  • Solution Architecture: What Goes Where Free
  • Security by Design: Auth, Roles & DLP Free
  • Designing UX Components: Canvas, PCF & Client Scripts Free
  • Designing Platform Extensions: Connectors, Plug-ins & APIs Free
  • Integration & Automation Blueprints Free

Domain 2: Build Power Platform Solutions

  • Environment Setup & Security Troubleshooting
  • Solutions & Layers: ALM Foundations
  • CI/CD Pipelines for Power Platform

Domain 3: Implement Power Apps Improvements

  • Advanced Power Fx & Canvas Components
  • Troubleshoot & Optimise Apps

Domain 4: Extend the User Experience

  • Client Scripting: Form Events & the Client API
  • Commands, Buttons & Custom Page Navigation
  • PCF Components: Build & Lifecycle
  • PCF Components: Package, Deploy & Advanced Features

Domain 5: Extend the Platform

  • The Plug-in Pipeline: How Dataverse Processes Events Free
  • Writing Plug-ins: Business Logic, Service & Registration
  • Custom APIs & Business Events
  • Custom Connectors: OpenAPI & Authentication
  • Custom Connectors: Azure, Policies & Code
  • Dataverse APIs: Web API & Organisation Service
  • Azure Functions for Power Platform
  • Cloud Flows: Dataverse Triggers & Expressions
  • Cloud Flows: Security, Errors & Child Flows

Domain 6: Develop Integrations

  • Publishing Dataverse Events
  • Service Endpoints: Webhooks, Service Bus & Event Hub
  • Data Sync: Change Tracking, Alternate Keys & Upsert

PL-400 Study Guide

Domain 1: Create a Technical Design

  • Solution Architecture: What Goes Where Free
  • Security by Design: Auth, Roles & DLP Free
  • Designing UX Components: Canvas, PCF & Client Scripts Free
  • Designing Platform Extensions: Connectors, Plug-ins & APIs Free
  • Integration & Automation Blueprints Free

Domain 2: Build Power Platform Solutions

  • Environment Setup & Security Troubleshooting
  • Solutions & Layers: ALM Foundations
  • CI/CD Pipelines for Power Platform

Domain 3: Implement Power Apps Improvements

  • Advanced Power Fx & Canvas Components
  • Troubleshoot & Optimise Apps

Domain 4: Extend the User Experience

  • Client Scripting: Form Events & the Client API
  • Commands, Buttons & Custom Page Navigation
  • PCF Components: Build & Lifecycle
  • PCF Components: Package, Deploy & Advanced Features

Domain 5: Extend the Platform

  • The Plug-in Pipeline: How Dataverse Processes Events Free
  • Writing Plug-ins: Business Logic, Service & Registration
  • Custom APIs & Business Events
  • Custom Connectors: OpenAPI & Authentication
  • Custom Connectors: Azure, Policies & Code
  • Dataverse APIs: Web API & Organisation Service
  • Azure Functions for Power Platform
  • Cloud Flows: Dataverse Triggers & Expressions
  • Cloud Flows: Security, Errors & Child Flows

Domain 6: Develop Integrations

  • Publishing Dataverse Events
  • Service Endpoints: Webhooks, Service Bus & Event Hub
  • Data Sync: Change Tracking, Alternate Keys & Upsert
Domain 6: Develop Integrations Premium ⏱ ~12 min read

Service Endpoints: Webhooks, Service Bus & Event Hub

Connect Dataverse to Azure messaging services. Register webhooks, configure Service Bus queues and topics, set up Event Hub, and secure each endpoint type.

Wiring up the endpoints

☕ Simple explanation

Think of service endpoints as postal delivery types.

A webhook is a direct letter — fast but lost if nobody is home. Service Bus is a post office box — the letter waits safely. Event Hub is a newspaper distribution centre — same edition to thousands of subscribers.

Service endpoints are external receivers for published events. Webhooks need a URL and authentication method. Service Bus needs a SAS connection string and queue/topic name. Event Hub needs a connection string and hub name. Each has different security, reliability, and throughput characteristics.

Webhook configuration

SettingDetails
URLHTTPS endpoint that receives POST requests
Auth optionsHttpHeader, WebhookKey, or HttpQueryString
PayloadRemoteExecutionContext (JSON) — same context as plug-in

Authentication methods

All require HTTPS; HttpHeader is most flexible
MethodHow It WorksSecurity
HttpHeaderCustom header (e.g., x-api-key: abc123)Good — encrypted in transit
WebhookKeyx-ms-dynamics-key headerGood — Dataverse standard pattern
HttpQueryStringKey appended to URLAcceptable — encrypted by HTTPS

Azure Service Bus

Queue vs topic

FeatureQueueTopic + Subscriptions
ConsumersOne (competing consumers possible)Multiple with filters
Use caseSingle system processingMultiple systems reacting

PRT registration steps

  1. Create Service Bus namespace in Azure
  2. Create queue or topic
  3. Create SAS policy with Send permission only
  4. Copy connection string → Register in PRT as Service Endpoint

Azure Event Hub

Use Event Hub when you need massive throughput (millions of events) with multiple consumers reading the same stream.

Choose Service BusChoose Event Hub
Hundreds to thousands/minuteMillions/minute
Guaranteed ordering within sessionPer partition only
Each message processed onceMultiple consumers read same stream
Transaction processingAnalytics, telemetry
Question

What SAS permission should Dataverse have for Service Bus?

Click or press Enter to reveal answer

Answer

Send only. Dataverse publishes messages; consuming applications need separate Listen policies. This follows least privilege.

Click to flip back

Question

When should you use a Service Bus topic instead of a queue?

Click or press Enter to reveal answer

Answer

When multiple systems need to react to the same event. Each system has its own subscription (with optional filters). A queue delivers each message to only one consumer.

Click to flip back

Knowledge Check

A company needs to send Dataverse order events to three systems: warehouse, analytics, and CRM sync. Each must receive every event. What endpoint?

🎬 Video coming soon

Next up: Data Sync — change tracking, alternate keys, and the UpsertRequest pattern.

← Previous

Publishing Dataverse Events

Next →

Data Sync: Change Tracking, Alternate Keys & Upsert

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.