web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Integrations with exte...
Power Apps
Unanswered

Integrations with external datasources - Best Practices

(0) ShareShare
ReportReport
Posted on by 18

Hi there,

 

I'm looking for advice and best practices concerning setting up an integration or even an integration framework between Dataverse and external system(s). Our Dataverse should be seen a the source system which should feed one or more other external systems. We can make the assumption all child systems have REST API available.

 

To give an example:

  • When a record is added to Dataverse entity A it should also be created in System X
  • When a record is updated in Dataverse entity A it should also be updated in System X

Basically all create, update and delete actions should reflect to the downstream systems.

 

Now I'm looking for best practices to set this up in a mature, and scalable way. I know Power Automate provides triggers which can achieve this, but to me this doesn't really qualify as mature and scalable. As monitoring and error handling is still rather limited. Next to this the whole licensing model can be rather cumbersome when we onboard more and more systems to this.

 

I was looking in the direction of putting messages on Azure Service Bus (Walkthrough: Register an Azure-aware plug-in using the Plug-in Registration tool (Microsoft Dataverse) - Power Apps | Microsoft Learn) and handle the messages from there using Logic Apps, Azure Functions or somethings else. But, there must be best practices, what would you recommend?

I have the same question (0)
  • MichaelFP Profile Picture
    1,847 Super User 2025 Season 2 on at

    I recommend to use the OOB integrations between Dataverse and Azure Service Bus. I don't have much details about your integration, but i prefer that because is async and is based on event drive architecture, you don't need to have a scheduled job running all the time to get if a record was updated or created. If something happen Dataverse send the data that was changed.

    Another point that is good with service bus that you can use the same message for multiple subscribers, using the topic. For that case, you don't need build something to send the information across the system.

  • Shashank Bhide Profile Picture
    942 Moderator on at

    I'll go with power automate anytime, they are absolutely scalable, they should be used as different Lego blocks pieced together to achieve certain functionality, I'd create a child power automate to handle errors by making HTTP calls to an azure application insight instance and add custom telemetry. Only place I don't recommend power automate is when huge volume of data needs to be transferred to/from Dataverse, but your use case sounds more like different records getting created across the Dataverse and need to be transferred to external system which is a great power automate use case.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 739 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 343 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard