The “Unable to Connect to Data Source” error occurs in Power Automate when a flow cannot establish a connection with the specified data source. This issue prevents actions from retrieving, updating, or sending data.
Error Message:
"Unable to connect to data source – The flow could not connect to the specified data source."
This error can be caused by:
- Expired or invalid authentication credentials
- Network connectivity issues
- Insufficient permissions to access the data source
- Service outages or restrictions
- Incorrect or outdated connector settings
2. Common Causes and Fixes
| Cause | Description | Fix |
|---|---|---|
| Expired Authentication Token | The connection to the data source has expired and needs re-authentication. | Refresh or reauthenticate the connection. |
| Incorrect Credentials | The provided credentials are incorrect. | Ensure the correct username and password are used. |
| Insufficient Permissions | The flow owner does not have access to the data source. | Grant the necessary permissions to the user. |
| Service Outage or API Limit | The data source is down or has exceeded its usage limit. | Check service status and API quotas. |
| Firewall or Network Restrictions | Corporate firewall or security settings block the connection. | Whitelist Power Automate’s IP addresses in the firewall. |
| Incorrect Connection Settings | The data source URL, environment, or configuration is incorrect. | Verify and update connection settings. |
3. Step-by-Step Troubleshooting Guide
Step 1: Check the Connection Status
- Open Power Automate (https://flow.microsoft.com).
- Go to Data → Connections in the left panel.
- Look for the connection linked to the data source.
- If it shows Needs Attention or Expired, click Fix Connection and sign in again.
Example Fix:
- If the connection to SharePoint, SQL Server, or Dataverse has expired, reauthenticate using your credentials.
- If using OAuth authentication, refresh the token by reconnecting.
Step 2: Verify User Permissions
Some data sources (e.g., SharePoint, Dataverse, SQL Server) require specific permissions for access.
- Check if you have read/write permissions to the data source.
- For SharePoint, ensure you have access to the list or document library.
- For SQL Server, ensure your account has the correct role (e.g., db_reader, db_writer).
Example Fix:
- SharePoint: Ensure your account has at least Edit permissions on the list.
- SQL Server: Ask the database administrator to grant the necessary access.
Step 3: Check for API Rate Limits or Service Outages
If the data source is an external API (e.g., Salesforce, Microsoft Graph, or a third-party service), check if:
✔ The service is down or experiencing issues
✔ You have exceeded API rate limits
How to check service status:
- Microsoft Services: https://status.office365.com
- Azure Services: https://status.azure.com
- Third-party APIs: Visit the provider’s status page.
Example Fix:
- If the service is down, wait for it to be restored.
- If API limits have been exceeded, wait until the quota resets.
Step 4: Verify Firewall and Network Settings
If Power Automate cannot connect to an on-premises data source (SQL Server, SharePoint, File System), check if:
✔ The gateway is running and up to date
✔ The firewall is blocking requests
How to check:
- Open On-Premises Data Gateway on the host machine.
- Ensure it shows “Online” and is connected.
- If using a firewall, whitelist Power Automate’s IP addresses from Microsoft’s documentation:
Example Fix:
- Restart the On-Premises Data Gateway if it’s offline.
- Ensure network firewall settings allow outbound traffic to Power Automate.
Step 5: Verify Connector and Environment Settings
If the connection settings are incorrect, Power Automate may fail to connect.
How to check:
- Open Power Automate → Edit the flow.
- Go to the step where the error occurs.
- Click on the data source and verify:
- The URL or database name is correct
- The environment is correct (especially for Dataverse and Power Apps)
Example Fix:
- Ensure the correct SharePoint site URL is entered.
- For Dataverse, confirm the environment is correctly set.
Step 6: Recreate the Connection
If the connection is still failing, remove and recreate it.
Steps to recreate the connection:
- Go to Power Automate → Data → Connections.
- Find the connection to the data source.
- Click Delete and then click + New Connection.
- Re-add the connection with correct credentials.
Example Fix:
- If the SQL Server connection is broken, remove it and re-add it with updated credentials.
- If using OAuth authentication, ensure the token is refreshed.
Step 7: Test the Flow After Changes
- Click Save after applying fixes.
- Run a Test using sample data.
- If the error persists, check Run History for detailed logs.
If the issue is resolved, ensure all users have updated access and configurations.