I have completed the Dual-write setup in the Cloud Hosted Environment, and the initial configuration was successful. I’m currently testing data synchronization from F&O to CRM.
However, I encountered an access token issue after creating a record in F&O. Please refer to the screenshot below for more details.
Hello,
I’m encountering the same error in my environment as well. We’ve tried practically every option we could think of. What’s odd is that the issue only occurs from F&O towards CRM — the other direction works fine.
Both app users in F&O and CRM have full permission roles, and the health check reports everything as correct, though clearly it is not.
Could we please get some support with this issue? We even attempted a workaround by creating a new app user with a certificate and adjusting it accordingly, but the problem persists.
Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/secure-developer-vm#set-up-a-new-application-and-certificate-registration
Thank you in advance.
Hi, Thanks for bringing this up. The access token issue you're encountering during dual-write synchronization from Finance & Operations (F&O) to CRM—particularly when writing to the `msdyn_globalproducts` entity—suggests an authentication failure between environments. Here are a few steps that may help resolve the issue: 1. **Verify application user roles**: Ensure that the application user in Dataverse has the correct security roles assigned, including any custom roles required for entity access. 2. **Check permissions in F&O**: Confirm that the user or service principal used for dual-write has sufficient permissions in F&O to trigger synchronization. 3. **Microsoft Entra ID configuration**: Make sure that the Microsoft-managed applications (like CDS and Dual-write integration apps) are correctly registered and visible in Microsoft Entra ID (formerly Azure AD). 4. **Run health checks**: Use the Dual-write health check tool to identify misconfigurations or missing mappings. This can often highlight issues with entity relationships or authentication. 5. **Entity mappings and job status**: Double-check that the dual-write job is active and that the entity mappings for `msdyn_globalproducts` are correctly configured and published. 6. **Token expiration or caching**: If the issue is intermittent, consider reviewing token lifetimes and whether cached credentials might be causing failures. Please verify if these steps help resolve the issue or narrow down the cause. Thanks and best regards, Daniele **Note: This response was prepared with support from Copilot to ensure clarity and completeness.**
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Andrés Arias as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
DAnny3211 345
Abhilash Warrier 137 Super User 2025 Season 2
Martin Dráb 87 Most Valuable Professional
