Fixing Internal_CompanyNotFound in CRM to BC integration

This post discusses how to resolve the Internal_CompanyNotFound error that arises when attempting to integrate Dynamics 365 CE and Business Central using the V2.0 API endpoints. The author provides details on a recent project he worked on, where the goal was to test integration using V2.0 endpoints. Microsoft documentation provides the standard URL format for V2.0 API, which includes the environment (dev, test, or production) and tenant parameters. However, when attempting to implement the integration, they encountered the Internal_CompanyNotFound error.

To fix this issue, the author details the steps they followed to identify and correct the problem. This involved checking the permissions on the Business Central APIs and ensuring the correct permissions were granted to the user account accessing the APIs. With the permission issue resolved, they were able to successfully integrate Dynamics 365 CE and Business Central using the V2.0 API endpoints.

If you are facing the Internal_CompanyNotFound error in your Dynamics 365 CE and Business Central integration project, this post offers a helpful guide to troubleshooting and resolving the issue.

Read more on https://himbap.com/blog.