The error shown is returned by Microsoft Dynamics API, and there is a blocker that is preventing HubSpot from getting access to your Dynamic Instance.
There has been a couple of solutions suggested by external sources:
This link states the user should verify the organization name and try to sign in again and confirm they have a valid license.
This link suggests the application user in your Dynamics CRM should be linked with the application ID used in the client credentials flow. The steps on how to do this are mentioned in the article.
This link states the user should check the permissions and in the end, the user writing the article noticed the solution is to create an application user that is connected to the application ID, similarly to the link above.
I would suggest reviewing the resources and checking with your admin to double-check all of the settings, also since the error is coming sent from Microsoft Dynamics themselves, I would suggest contacting their Support directly for some insight into the error. Here are their Support details https://dynamics.microsoft.com/en-us/support.
The error shown is returned by Microsoft Dynamics API, and there is a blocker that is preventing HubSpot from getting access to your Dynamic Instance.
There has been a couple of solutions suggested by external sources:
This link states the user should verify the organization name and try to sign in again and confirm they have a valid license.
This link suggests the application user in your Dynamics CRM should be linked with the application ID used in the client credentials flow. The steps on how to do this are mentioned in the article.
This link states the user should check the permissions and in the end, the user writing the article noticed the solution is to create an application user that is connected to the application ID, similarly to the link above.
I would suggest reviewing the resources and checking with your admin to double-check all of the settings, also since the error is coming sent from Microsoft Dynamics themselves, I would suggest contacting their Support directly for some insight into the error. Here are their Support details https://dynamics.microsoft.com/en-us/support.
Hi @PamCotton , thanks for the quick response. These purposed solution makes sense. I do think Microsoft should be able to help as it is coming from Dynamics.