The “Data Source Permissions Error” occurs when a Power Automate flow cannot access or modify a data source due to insufficient user permissions.
Error Message:
"Data source permissions error – Insufficient permissions to access or modify the data source."
This issue can arise due to:
- Lack of read/write permissions on the data source
- Changes in security roles or access levels
- Data source ownership restrictions
- Guest or external user limitations
2. Common Causes and Fixes
| Cause | Description | Fix |
|---|---|---|
| Insufficient Permissions | The user does not have required access rights. | Grant appropriate permissions in the data source settings. |
| Changed Security Roles | An admin modified security settings, limiting access. | Verify and update roles for the user. |
| Guest/External User Restriction | Some data sources block access to guest users. | Use an internal account with full permissions. |
| Flow Running with Wrong Credentials | The flow uses a connection with a different or restricted account. | Re-authenticate using an account with the required permissions. |
| Power Automate Not Listed as an Approved App | Organization policies block Power Automate access. | Request admin approval for Power Automate to interact with the data source. |
3. Step-by-Step Troubleshooting Guide
Step 1: Verify Your Permissions on the Data Source
Ensure that the connected user has the correct access level.
Steps to check permissions:
- Identify the data source (e.g., SharePoint, SQL, Dataverse, OneDrive).
- Open the data source and navigate to Permissions or Access Control.
- Ensure the user has the required access (Read, Edit, Full Control).
- If permissions are missing, request an admin to grant access.
Example Fix:
- If a SharePoint list is blocked, assign the user “Edit” or “Contribute” permissions.
Step 2: Check the Flow Owner and Run-As User
If a flow was created by another user, your access might be restricted.
Steps to fix:
- Open Power Automate.
- Check Flow Details to see who owns the flow.
- If the flow is owned by someone else, request co-ownership or shared access.
- Re-run the flow under an account with full access.
Example Fix:
- If a Power Automate flow is using a guest account, switch to an internal user with admin rights.
Step 3: Verify Connection Credentials in Power Automate
If the flow is using an incorrect or expired connection, authentication may fail.
Steps to fix:
- Open Power Automate.
- Go to Data → Connections.
- Find the connection related to the failing flow.
- Click Fix Connection or Re-authenticate with an account that has the right permissions.
Example Fix:
- If a SQL database connection is failing, update the credentials to use a database admin account.
Step 4: Check Organizational Security Policies
Some companies enforce strict policies that block access to external services.
Steps to check security policies:
- Contact your IT administrator.
- Ask if Conditional Access Policies or DLP (Data Loss Prevention) policies are blocking Power Automate.
- Request approval for Power Automate to access the data source.
Example Fix:
- If an Office 365 security policy prevents access, request an exemption for your Power Automate flow.
Step 5: Ensure the Data Source Allows External Users (if applicable)
Some data sources, like SharePoint Online, limit access for guest users.
Steps to fix:
- Check if Guest Access is enabled in the Microsoft 365 Admin Center.
- If necessary, use an internal account instead of an external one.
Example Fix:
- If an external consultant is trying to run a Dataverse flow, add them as a licensed user in Azure AD.
Step 6: Test Access Using Another Account
If you’re unsure whether the issue is with your account, try another one.
Steps to test:
- Ask a colleague with full access to test the same flow.
- If it works for them but not you, request a role upgrade.
Example Fix:
- If a Dataverse table is restricted, have an admin assign a higher security role.