Forum Discussion
Your file has been disconnected and data source credentials greyed out
Hi PBION ,
Thank you for reaching out to Microsoft fabric community forum.
The error message "We are unable to access some data source because the artifact is missing connection details" indicates that the Power BI Service dataset has lost its connection to the original data source. This can happen if SharePoint permissions or data connection ownership change, or if the dataset is republished from Power BI Desktop with updated metadata, causing it to be recognized as a new artifact.
Since your SharePoint list access was recently reduced and you no longer have full edit rights, this is likely causing the issue. Power BI requires at least read and schema-level access to validate and refresh the connection; lower permissions can prevent the dataset from accessing connection details, leading to greyed-out credentials and refresh errors.
To resolve this, check your SharePoint permissions and request temporary Edit or Full Control access if necessary. Power BI needs metadata-level access even if only read access is needed for visuals. Once permissions are restored, go to the dataset in Power BI Service, select Settings > Data source credentials, and re-enter your organizational account to rebind the connection. Also, confirm that both SharePoint List and Access Database sources are mapped to the same gateway cluster under Manage Gateways.
Hope this helps. Please reach out for further assistance.
Thank you.
Super UserHi PBION
You have a report that used to refresh fine through a gateway, but after republishing, Power BI Service shows the dataset as disconnected and the data source credentials are greyed out, even though the same setup worked for over a year. Since the report uses both a SharePoint List and an Access Database, and the credentials issue appears even with a simple test report connected only to the SharePoint list, the problem is likely related to how Power BI Service is now handling those data source authentication types rather than your gateway setup. Clearing permissions and re-adding the sources didn’t help, which reinforces that this isn't a permission cache issue but rather a Service-side change or authentication policy shift—particularly since Access DB over gateway and SharePoint List credentials have recently seen reliability issues. In many cases like this, the fix ends up being re-establishing the connection by editing the data source in the gateway, ensuring the account used is a Microsoft/organizational login, or switching the SharePoint connection method in Desktop (OData feed vs. SharePoint connector) and republishing. If none of those work, it's likely a Power BI Service bug/regression, and opening a support ticket or checking Service Health is the right next step, especially since this behavior started suddenly after republishing and affects multiple reports.
I will likely submit a ticket as nothing has worked thus far. Could it be that I need additional permissions to the SharePoint list itself? This is the only list that I don't have full editing permissions to which I believe could have changed recently.