---
title: "Discussion on \"Dataverse webhooks to Service Bus: retry and dead-lettering\" | Hashnode"
description: "Discussion on \"Dataverse webhooks to Service Bus: retry and dead-lettering\". Dataverse can call a webhook on every table change. Azure Service Bus can accept that webhook and buffer it for downstream consumers. Plugging them together correctly - with retry on transient failures and dead-letter on permanent ones - is"
url: "https://hashnode.com/posts/dataverse-webhooks-to-service-bus-retry-and-dead-lettering/6a127cf6ba30e45856c53de0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Dataverse webhooks to Service Bus: retry and dead-lettering](https://sapotacorpvn.hashnode.dev/dataverse-webhooks-to-service-bus-retry-and-dead-lettering?utm_source=hashnode&utm_medium=feed)

Dataverse can call a webhook on every table change. Azure Service Bus can accept that webhook and buffer it for downstream consumers. Plugging them together correctly - with retry on transient failures and dead-letter on permanent ones - is

May 24 · 6 min read · sapotacorpvn.hashnode.dev  
Read the article

-   [#power-platform](https://hashnode.com/tag/power-platform)
-   [#dataverse](https://hashnode.com/tag/dataverse)
-   [#azure-service-bus](https://hashnode.com/tag/azure-service-bus)
-   [#webhook](https://hashnode.com/tag/webhook)
-   [#integration](https://hashnode.com/tag/integration)

## Written by

[SapotaCorp](https://hashnode.com/@sapotacorpvn)

@sapotacorpvn · Hanoi, Vietnam

  
[View profile](https://hashnode.com/@sapotacorpvn)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
