Databook C4S - Dynamics 365 CRM
Document v1.0a
This document contains instructions for granting Databook C4S permissions to read data from Dynamics 365. The document is an adaptation of the official documentation on Microsoft Entra.
Prerequisites
A Microsoft Entra user account with one of the following roles:
Privileged Role Administrator, for granting consent for apps requesting any permission, for any API.
Cloud Application Administrator or Application Administrator, for granting consent for apps requesting any permission for any API, except Microsoft Graph app roles (application permissions).
A custom directory role that includes the permission to grant permissions to applications, for the permissions required by the application.
Permission Setup
Go to https://entra.microsoft.com/#home and sign in using your account.
Click on Applications β Enterprise Application in the sidepanel.
You should now see all Enterprise Applications in your organization.
Find
Databook Copilot Integration API
with search, and click Databook Copilot Integration API.
You should now see the Databook Copilot Integration API overview page.
Click on Security β Permissions in the nested sidepanel.
You should now see all permissions that are granted for Databook Copilot Integration API.
Click on the Grant Admin Consent button to start the authorization flow.
In the authorization flow, select an account that meets the Prerequisites (refer to start document).
In the authorization flow, approve the requested permissions by clicking on the Accept button.
Wait a minute, then click on the Refresh button in the Databook Copilot Integration API permissions.
Verify that permissions are granted - pay attention to
dataverse:user_impersonation
permission.
Troubleshooting
We are seeing a
Failure exchanging connector token to Dynamics365 token.
error message.Verify that permissions are granted - pay attention to
dataverse:user_impersonation
permission.This permission is critical and enables Databook C4S to retrieve CRM data.
If the permission is there, and you still see the error message. Try removing any and all existing connections associated with the application. Then re-add the connections after permission update.
This should be possible through, e.g., https://make.powerautomate.com/ β Connections.