System requirements for dual-write

What regions are available?

Currently, we support dual-write in the following regions:

Note

There are currently no plans to support more regions.

The setup of a dual-write connection has the following requirements:

finance and operations apps that have build version 10.0.9 (10.0.383.20013) (Quality update) and platform update 33 or later
Customer engagement apps that have platform version 9.1.0000.11732 or later

Dual-write has these limitations:

You can't run dual-write and the Prospect to cash solution for Data integrator side by side. If you're running the Prospect to cash solution for Data integrator, you must uninstall it.
Dual-write setup is not supported on trial instances of finance and operations apps.
Dual-write must be used to integrate a single finance and operations app instance and a single customer engagement app instance.
Dual-write currently has an initial synchronization limit of 40 legal entities.
Dual-write live synchronization has a limit of 250 legal entities.
Dual-write does not support cross-company data sharing.
Dual-write requires that the finance and operations app and the customer engagement app must be in the same Microsoft Microsoft Entra tenant.
Dual-write requires that the finance and operations app and the customer engagement app must be deployed in the same Microsoft Azure datacenter.
Dual-write is not triggered by the doInsert, doUpdate, and doDelete events of finance and operations apps. Use the Insert, Update, and Delete events in finance and operations apps when you want to trigger dual-write.
Dual-write doesn't support distributed transactions. For example, if the product receipt posting process is cancelled, dual-write might create the product receipt in Dataverse but not create it in Supply Chain Management.

Future updates of the dual-write solution will be available through One Version.