Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello Power BI Community,
I am facing this data refresh error as below ( randomly). This is cloud connection to SQL database using service principal - I am using any gateway. what am I missing here?
Processing Error: We are unable to access some data source because the artifact is missing connection details. Please contact the artifact owner to bind the data source to a data connection or use default connection settings for the unbound data source.
Cluster URI:WABI-US-NORTH-CENTRAL-B-redirect.analysis.windows.net
Solved! Go to Solution.
Hi @lakedrivedirect , Thank you for reaching out to the Microsoft Community Forum.
The randomness suggests token caching or an expired secret. Go to Azure Portal, under Entra ID -> App registrations -> Your service principal -> Certificates & secrets, and check the client secret’s expiry. If it’s old or near done, generate a new one. Then, in Power BI Service, hit Dataset Settings -> Data source credentials, and update it with the new secret. If the UI won’t let you, use the REST API: send a POST to https://api.powerbi.com/v1.0/myorg/groups/{workspaceId}/datasets/{datasetId}/datasources with {"credentialData":[{"name":"clientId","value":"your-client-id"},{"name":"clientSecret","value":"new-secret"},{"name":"tenantId","value":"your-tenant-id"}]}. This rebinds the credentials explicitly and kills any caching quirks. Try a refresh after, it’ll work.
Next, let’s fix any dataset misalignment, since “missing connection details” often means the dataset’s lost its link to the data source. Open your PBIX in Power BI Desktop, head to Data Source Settings, and verify the SQL connection works with the service principal. Republish it to the Power BI Service to overwrite any stale configuration. Then, in the service, go to Settings -> Data connections, ensure the connection’s listed and link it to your dataset if it’s not. This forces a clean binding, and your refreshes will stabilize immediately.
If the above don’t fully solve it or you suspect a Power BI service glitch in the North Central US cluster, In Power BI Service, check Dataset -> Refresh history for exact error codes. For a rock-solid test, run this PowerShell snippet to trigger a refresh and log details: $workspaceId = "<your-workspace-id>"; $datasetId = "<your-dataset-id>"; Invoke-PowerBIRestMethod -Url "groups/$workspaceId/datasets/$datasetId/refreshes" -Method POST. If it’s a regional hiccup, publish the dataset to another region and retry. This pins down any service-side issues, but the first two steps should already resolve it.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi @lakedrivedirect , Please let us know if your issue is solved. If it is, consider marking the answers that helped 'Accept as Solution', so others with similar queries can find them easily. If not, please share the details.
Thank you.
Hi @lakedrivedirect , Please let us know if your issue is solved. If it is, consider marking the answers that helped 'Accept as Solution', so others with similar queries can find them easily. If not, please share the details.
Thank you.
Hi @lakedrivedirect , Thank you for reaching out to the Microsoft Community Forum.
Please let us know if your issue is solved. If it is, consider marking the answers that helped 'Accept as Solution', so others with similar queries can find them easily. If not, please share the details.
Thank you.
Hi @lakedrivedirect , Thank you for reaching out to the Microsoft Community Forum.
The randomness suggests token caching or an expired secret. Go to Azure Portal, under Entra ID -> App registrations -> Your service principal -> Certificates & secrets, and check the client secret’s expiry. If it’s old or near done, generate a new one. Then, in Power BI Service, hit Dataset Settings -> Data source credentials, and update it with the new secret. If the UI won’t let you, use the REST API: send a POST to https://api.powerbi.com/v1.0/myorg/groups/{workspaceId}/datasets/{datasetId}/datasources with {"credentialData":[{"name":"clientId","value":"your-client-id"},{"name":"clientSecret","value":"new-secret"},{"name":"tenantId","value":"your-tenant-id"}]}. This rebinds the credentials explicitly and kills any caching quirks. Try a refresh after, it’ll work.
Next, let’s fix any dataset misalignment, since “missing connection details” often means the dataset’s lost its link to the data source. Open your PBIX in Power BI Desktop, head to Data Source Settings, and verify the SQL connection works with the service principal. Republish it to the Power BI Service to overwrite any stale configuration. Then, in the service, go to Settings -> Data connections, ensure the connection’s listed and link it to your dataset if it’s not. This forces a clean binding, and your refreshes will stabilize immediately.
If the above don’t fully solve it or you suspect a Power BI service glitch in the North Central US cluster, In Power BI Service, check Dataset -> Refresh history for exact error codes. For a rock-solid test, run this PowerShell snippet to trigger a refresh and log details: $workspaceId = "<your-workspace-id>"; $datasetId = "<your-dataset-id>"; Invoke-PowerBIRestMethod -Url "groups/$workspaceId/datasets/$datasetId/refreshes" -Method POST. If it’s a regional hiccup, publish the dataset to another region and retry. This pins down any service-side issues, but the first two steps should already resolve it.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
I'm suddenly getting a similar error. Similar setup too using gateway. Never had this error before.
Check out the July 2025 Power BI update to learn about new features.
User | Count |
---|---|
24 | |
20 | |
18 | |
15 | |
13 |
User | Count |
---|---|
37 | |
23 | |
21 | |
18 | |
12 |