Microsoft Dynamics 365 | Integration, Dataverse...

Dual Write - Organization does not match actual Dataverse Organization

(5) Share

Report

Posted on by alexwright132

Hello,

We have recently completed an environment restore from both CE and F&O environments over to Test instances. Within Dual Write bot connections look to be pointing to the correct newly restored environments however get the below error when saving a record in Dataverse.

Oddly our Service Administrator account can save records but Users with the System Administrator security role cannot. Any help would be greatly appreciated.

Categories:

Power Platform integration

I have the same question (0)

All responses (4)

Answers (0)

CU13031731-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hellow, can you fix it?

Was this reply helpful? Yes No
Griet 31 on at

Like (0)

Report
Copy link

Link copied!

We are experiencing the same error after a data restore. Were you able to resolve this issue?

Was this reply helpful? Yes No
DB-23071443-0 2 on at

Like (0)

Report
Copy link

Link copied!

This fixed it for me

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,407 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi,

This error typically occurs when the Dual Write Secure Configuration still references the original Dataverse environment ID after a restore. Since the organization ID in the SecureConfig doesn’t match the current Dataverse environment, Dual Write throws a validation error.

Here’s what you can try:

Reset the Secure Configuration:

Go to F&O > Dual Write > Linked Environments.

Unlink and then relink the environment to refresh the SecureConfig with the correct organization ID.

Re-run the Dual Write setup wizard:

This will regenerate the SecureConfig and re-establish trust between the environments.

Check the SecureConfig table in Dataverse:

If you have access, inspect the msdyn_dualsecureconfig table and verify that the OrganizationId matches the current environment.

If not, you may need to delete and regenerate the config (only do this if you're familiar with the implications or under Microsoft support guidance).

Permissions:

The fact that the Service Admin can save records suggests a permission or plugin execution context issue. Make sure the affected users have the correct roles and that no custom plugins are enforcing organization checks.

If the issue persists, I’d recommend opening a support ticket with Microsoft, especially if this is a production-like test environment.

Hope this helps!

Best regards,
Daniele

Was this reply helpful? Yes No