Dynamics 365: Principal user is missing prvReadAccount privilege
Overview
The error Principal user is missing prvReadAccount privilege is returned by the Dynamics 365 API. It indicates that the user account used for the Skyvia connection lacks the required read-write privileges for one or more entities.
Root Causes
- The user is assigned a security role other than System Administrator and does not have sufficient entity-level privileges.
- Conflicting licenses are assigned in the same environment — for example, a Sales Enterprise license combined with a PowerApps license, where the lower PowerApps privileges may override the higher ones.
Resolution
Option 1: Assign the System Administrator role
Ensure the user account used in your Skyvia connection has the System Administrator security role assigned in Dynamics 365:
- Go to Settings → Security → Users.
- Select the user account used for the Skyvia connection.
- Click Manage Roles.
- Assign the System Administrator role.
- Save and retry the integration in Skyvia.
Option 2: Grant specific entity privileges
If assigning System Administrator is not feasible, grant the user explicit read-write privileges for the affected entity:
- Go to Settings → Security → Security Roles.
- Open the role assigned to the user.
- Find the entity mentioned in the error (e.g., Account).
- Set Read and Write access to Organization level.
- Save and retry.
Option 3: Resolve conflicting licenses
If the user already has the System Administrator role but still encounters the error, check for conflicting licenses:
- Go to Microsoft 365 Admin Center → Users → select the user.
- Review assigned licenses.
- Remove any lower-tier licenses (e.g., PowerApps) that may be overriding Dynamics 365 privileges.
Still Having Issues?
If none of the above resolves the error, contact Microsoft Dynamics 365 support for further assistance with security role configuration.
Related Articles
Salesforce: Inactive User Error
Overview The "inactive user" error occurs at the Salesforce connection level in Skyvia. It means that the Salesforce user account used for the connection is inactive or no longer valid, so Salesforce blocks API authentication. As a result, Skyvia ...
AADSTS650052 Error When Connecting to Dynamics 365 Business Central
Overview When connecting to Microsoft Dynamics 365 Business Central in Skyvia, you may encounter the following error: AADSTS650052: The app is trying to access a service '00000015-0000-0000-c000-000000000000' (Microsoft Dynamics ERP) that your ...
Zoho CRM: Inactive User Cannot Access the API Error
Overview This error is returned by the Zoho CRM API. Skyvia connects to data sources through their APIs and is therefore subject to their features and limitations. Unfortunately, there are no additional details available beyond what the Zoho CRM API ...
Account and Workspace Roles in Skyvia
In Skyvia, we distinguish between account and workspace roles for seamless teamwork: 1. Account Roles The account admin, also known as the account owner, has full control over the account. They can manage subscriptions to Skyvia products, modify ...
QuickBooks Online: Could not start QuickBooks
Overview The "Could not start QuickBooks" error may occur when using QuickBooks Online via Skyvia Agent if QuickBooks and the Skyvia Agent are running with different user permission levels. Resolution Ensure that both QuickBooks and Skyvia Agent are ...