How to sync two Dataverse environments in two different Tenants

(0) Share

Report

Posted on by David Pezzoli

230

Hi Folks!

Given 2 environments, one in a different Tenant from the other, in your opinion, what is the best practice to set-up a Tenant-To-Tenant data synchronization beetween the two Dataverse environmets?
The most performant way LOW-CODE/NO-CODE to synchronize data between the two environments (batch scheduled synchronization).

For e.g. I need to keep always on synced Account Table data between two Dataverse environments:

Dataverse A Tenant A => Dataverse B Tenant B

Which connector or Web integration (batch o scheduled process) LOWCODE/NOCODE can I use to pass data from one environment to another, please?
Uni-Directional or Bi-Directional integration, for the moment it is indifferent.

Many Thx!

David

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

ivan_apps 2,187 Moderator on at

Like (2)

Report

I’ve come across this scenario before… I can tell you what you can try that should work ‘in theory’. But I have not gone through the steps in practice.

Set up an HTTP listening power automate flow. Basically your trigger is an HTTP connector. Once you save it, it should generate a URL that it is listening on. Set up your connector to authorize as needed.

Create an App Registration that you will give to the other tenant. Set up a secret based authentication or Certificate, your choice (secret is easier). Grant it the appropriate permissions that you need to connect to your tenant. Probably just user.read on graph api.

Create a second App Registration that will connect to your Dataverse instance. Don’t share this with the other tenant. You will connect to your DV using this Service Principal so make sure you create the user account in Dataverse as well. Grant it the appropriate security roles to be able to access the tables you want to sync. Your flow will authorize the connection via the App Registration you gave out, but will perform the sync tasks via the App Registration you created the user with. This will allow you to only perform the actions you expose to the other tenant.

Create your synchronization steps in the flow, or create multiple flows if you want to create an external API. Dataverse has the ability to create an API as well but that is more ProCode rather than low code.

Repeat the steps above in the other tenant to create a bi-directional connection.

You can then create an additional flow that runs on a schedule to call the other tenant’s HTTP connector flow via the URL it generates, pass in the App Registration credentials, and trigger the sync.

thats it! Hopefully it makes sense. Again I’ve thought of it in theory but haven’t created all the steps myself for this purpose, but HTTP connector works well from what I can see.

Was this reply helpful? Yes No
David Pezzoli 230 on at

Like (1)

Report

Many Thanks Ivan, good idea using Power Automate flows! But I never used them to set up a connection across Tenant.
So I ask to everyone if exists a simplest solution...

Was this reply helpful? Yes No
David Pezzoli 230 on at

Like (0)

Report

Maybe also a Microsoft standard or ISV connector to sync across Tenants.

Was this reply helpful? Yes No
ivan_apps 2,187 Moderator on at

Like (1)

Report

Yea Power Automate will likely be the most "Low Code" solution. I'm sure there are others, but likely more developer intensive.
Your biggest hurdle is going to be authentication across tenants no matter the method. App Registrations should solve that hurdle. I wouldn't recommend any unauthenticated data syncs.

Was this reply helpful? Yes No
David Pezzoli 230 on at

Like (0)

Report

Ok, sorry but... is there a a simplest solution with standard connector o ISV connector, please?

Was this reply helpful? Yes No