---
title: "Discussion on \"Plugin + Azure Function + Service Bus: async integration at scale\" | Hashnode"
description: "Discussion on \"Plugin + Azure Function + Service Bus: async integration at scale\". A Dataverse row change has to propagate to an ERP, a search index, and a notification service. Six months of us shipping exactly this pattern on enterprise projects, with the architecture, code, and failure-handling decisions that make it r"
url: "https://hashnode.com/posts/plugin-azure-function-service-bus-async-integration-at-scale/6a127c9cba30e45856c3b7ad"
---

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

Discussion

# [Plugin + Azure Function + Service Bus: async integration at scale](https://sapotacorpvn.hashnode.dev/plugin-azure-function-service-bus-async-integration-at-scale?utm_source=hashnode&utm_medium=feed)

A Dataverse row change has to propagate to an ERP, a search index, and a notification service. Six months of us shipping exactly this pattern on enterprise projects, with the architecture, code, and failure-handling decisions that make it r

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-function](https://hashnode.com/tag/azure-function)
-   [#service-bus](https://hashnode.com/tag/service-bus)
-   [#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.