And let’s get to the Solution setup part!

In Part 1, we created a Dynamics 365 Sales environment and added Finance and Operations to it – all from the Power Platform Admin Center. Now, let’s set up Dual-Write so your Accounts flow to Finance and Operations as Customers.

Here’s how I set it up –

1. Setup Dual-Write

1. Back in Power Platform Admin Center, open the environment, go to Resources > Dynamics 365 apps and click Install app. Install the Dual-write packages one at a time, waiting for each to show Installed: first Dual-write core solution, then Dual-write Application Core Solutions (legal entities, currencies), and then Dual Write Finance and Extended Solutions – this one has the Customers V3 map we need for Accounts.
   
   Note: I first tried the all-in-one Dual-write application orchestration solution, but it failed with Cab file required for importing solution with name Dynamics365FinanceAndOperationsAnchor, even after a retry. Microsoft now ships these as separate packages – so install those instead.
   
   Tip: Don’t start the next package until the previous one shows Installed – each one builds on the one before, and running them in parallel in the same environment can make the installs fail. For me, the Dual-write core solution took about 20 minutes, so plan for some waiting time here.
   
2. Now open Finance and Operations and go to Workspaces > Data management and click the Dual-write tile. Since Sales and Finance and Operations are in the same environment, it’s already linked – no linking wizard like the old Lifecycle Services days.
   
   
3. Before applying any maps, check which legal entities are linked. Click Environment details > Legal entities. In my case, only dat was linked, but the Contoso demo data lives in USMF. So click Add Legal Entity, select USMF and Save. Keep Skip initial writes for newly added legal entities checked if you only want new records to sync.
   
   
4. Click Apply solution, select Dual-write application core entity maps and click Apply. Once it’s applied, you’ll see the table maps listed with a status of Not running.
   
   
   Troubleshooting: In my environment, Apply solution came up empty with the error Failed to get solutions containing entity maps … StatusCode=NotFound, and Add table map failed with Failed to get publishers available to user. Here’s what I checked:
   – I ran Health check on the Dual-write page – all 15 checks passed (core solution, orchestration components, app users, plugins, API Hub connection and business unit).
   – Since this was a unified environment where the Dual-write link was created automatically during provisioning, I used Reset link to recreate the connection under my own account – choosing the current Dataverse environment and the dat and USMF legal entities. The reset completed successfully (15/15 checks passed).
   
   – Even after the reset, Apply solution returned the same NotFound error – which points to the Dual-write service side rather than the setup. If you hit the same error, raise a support ticket with Microsoft and include the Session ID and Root Activity ID from the error. I’ll update this post once it’s resolved.
   

So what’s actually going wrong?

At this point everything looks healthy – all three Dual-write packages are installed, the link shows both legal entities, and the Health check passes 15/15 – but Apply solution still returns Failed to get solutions containing entity maps … StatusCode=NotFound. So what gives?

“Apply solution” doesn’t read those entity maps from your environment – it calls a Dual-write backend service that returns the list of solution maps for your two linked environments. A NotFound from that service means the call reached it but it had nothing to hand back – the environment pair isn’t registered on the service side yet, even though the solutions are physically installed in Dataverse.

In my experience this comes down to one of a few things, and it’s worth checking them in this order:

1. The link was created by provisioning, not by you. On a unified environment, the Sales + Finance and Operations link is set up automatically. The account that created it owns it, and other admins can get NotFound / “Failed to get publishers available to user” until they re-create it. Reset link (which I did above) is meant to fix this – it did put the link under my account, but the service still returned NotFound, so for me it wasn’t the whole story.
2. The environment pair is still catching up on the service side. A freshly provisioned Finance and Operations environment (mine finished only hours earlier) can take a while before the Dual-write service recognises the pair. A NotFound that persists right after setup, then clears on its own, usually points here.
3. App registrations / dual-write app users. The Health check lists the two app users and app IDs that let Dataverse and Finance and Operations call each other. If one of those is missing or not consented at the tenant level, the backend call can’t authenticate and returns NotFound rather than a clear auth error.

Since the Health check passed and the Reset didn’t clear it, my case looks like a service-side registration delay (reason 2). The fix there is time plus a Microsoft support ticket with the Session ID and Root Activity ID from the error. I’ll update this post with the map and test steps once Apply solution returns the solutions.

Hope this was helpful!

Here are some more posts you want to check out –

1. Deploying Project Operations Core vs Integrated with ERP
2. Environment Groups in Power Platform Admin Center
3. Preferred Solution in Dataverse | Power Platform Admin Center
4. Enable Copilot for Dynamics 365 Sales environment

And some popular Power Automate posts –

1. Select the item based on a key value using Filter Array in Power Automate
2. Select values from an array using Select action in a Power Automate Flow
3. Call a Flow from Canvas Power App and get back response | Power Platform
4. Asynchronous HTTP Response from a Flow | Power Automate

Thank you!