Dual-write setup from Lifecycle Services

This article explains how to enable dual-write from Microsoft Dynamics 365 Lifecycle Services.

Prerequisites

Customers must complete the Power Platform integration as described in the following topics:

• If you don't yet use Microsoft Power Platform and want to expand your finance and operations environments by adding platform capabilities, see Connect finance and operations apps with a new Microsoft Dataverse instance.
• If you already have Dataverse and Power Platform environments, and want to connect them to finance and operations environments, see Connect finance and operations apps with an existing Microsoft Dataverse instance.

Set up dual-write for new or existing Dataverse environments

Follow these steps to set up dual-write from Lifecycle Services Environment Details page:

1. On the Environment Details page, expand the Power Platform Integration section.

2. Select the Dual-write application button.

   

3. Review the terms and conditions, and then select Configure.

4. Select OK to continue.

5. You can monitor the progress by periodically refreshing the environment details page. Setup typically takes 30 minutes or less.

6. When the setup is complete, a message informs you if the process was successful or if there was a failure. If the setup failed, then a related error message is displayed. You must fix any errors before moving to the next step.

7. Select Link to Power Platform environment to create a link between Dataverse and the current environment's databases. It typically takes less than 5 minutes to create the link.

   

8. When the linking is complete, a hyperlink is displayed. Use the link to sign in to the dual-write administration area in the finance and operations environment. From there, you can set up entity mappings.

Configure app user for one-box environments

Troubleshooting

Linking mismatch

It's possible that your dual-write environment is linked to a Dataverse instance while Lifecycle Services isn't set up for Power Platform integration. This linking mismatch can cause unexpected behavior. It's recommended that Lifecycle Services environment details match what you are connected to in dual-write so the same connection can be used by business events, virtual tables, and add-ins.

If your environment has a linking mismatch, Lifecycle Services shows a warning on your environment details page that resembles the following example: "Microsoft has detected that your environment is linked via Dual-write to a different destination than specified in Power Platform Integration, which isn't recommended."

If you receive this warning, try one of the following solutions:

• If your Lifecycle Services environment hasn't ever been set up for Power Platform integration, you can connect to the Dataverse instance that is configured in dual-write by following the instructions in this article.
• If your Lifecycle Services environment is already set up for Power Platform integration, you should reset your dual-write connection to the one specified by Lifecycle Services using the Reset dual-write connections.

In the past a manual support ticket option was available, but that was before option 1 above existed. Microsoft no longer supports manual relinking requests via Support tickets.

Incorrect permissions on service principal

It's possible to receive the following error while linking the finance and operations environment to the Dataverse environment in Lifecycle Services:

This error indicates that the application users created for dual-write to access data on the target platforms haven't been configured with the appropriate permissions. To resolve this error, ensure the application users are configured correctly following the guidance in System requirements and prerequisites.