Install the Plug-in Registration Tool (available in the Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool NuGet package) and connect it to your Dataverse environment.
In the tool, select Register > Register New WebHook; enter a name, the external HTTPS endpoint URL, and choose an authentication type (HttpHeader, WebhookKey, or HttpQueryString) and supply the secret value.
After registering the webhook, right-click it and select Register New Step; specify the message (e.g., Create, Update, Delete), the primary entity, execution mode (synchronous or asynchronous), and stage (PostOperation for most integrations).
Configure any filtering attributes on the step to limit event delivery to specific field changes; this reduces noise and webhook call volume.
Test delivery by triggering the registered event in Dynamics 365 and verifying that your endpoint receives a POST request with the Dataverse event payload as JSON.
Webhooks can also be registered programmatically by creating records in the ServiceEndpoint table (Contract=8, ConnectionMode=2, Url=<endpoint>) and SdkMessageProcessingStep table via the Web API or SDK.
Known gotchas
The external endpoint must respond with HTTP 200 within the Dataverse timeout (default 60 seconds for synchronous steps); a slow or non-responding endpoint blocks the triggering operation for synchronous mode webhooks.
Webhook payloads do not include all record fields by default — they contain only the fields specified in the step's filtering attributes plus pre-image/post-image data if you configure images; register pre/post images in the step if you need more field context.
Only HTTPS endpoints on port 443 are supported; HTTP and non-standard ports are rejected at registration time.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp