Forum Discussion
Premium_ASWL_Error with Azure Sharepoint and Lakehouse import data
Hello,
I made a report that combines data from Azure Sharepoint and Lakehouse sources.
Both of them using import.
There has been issues with on-premise Sharepoint:
But have these issues spread to Azure Sharepoint now?
The error I get is
- Data source error{"error":{"code":"Premium_ASWL_Error","pbi.error":{"code":"Premium_ASWL_Error","parameters":{},"details":[{"code":"Premium_ASWL_Error_Details_Label","detail":{"type":1,"value":"We cannot refresh this semantic model because this semantic model uses a default data connection without explicit connection credentials. Please replace the default data connection in the semantic model settings with an explicit cloud or gateway data connection."}}],"exceptionCulprit":1}}}
- Cluster URIWABI-NORTH-EUROPE-H-PRIMARY-redirect.analysis.windows.net
Misc info:
- This has worked a couple of months ago
- There are no issues on Desktop
- SqlServer connection maps to Single Sign-On
- SharePointList connection maps to Personal Cloud Connect - I have admin permissions, so I can change this if needed
I succeeded to fix this though:
I changed the SQL connection from OAuth2 to service principal / workspace identity.
Sharepoint worked fine with Personal Cloud Connect setting.
4 Replies
- Zanqueta
Super User
Hi TimoRiikonen,
I'm in your message error and find this explanation, maybe can be usefull:
The error Premium_ASWL_Error is related to how credentials are configured for the data sources in the Power BI Service (Fabric). The message states:“We cannot refresh this semantic model because this semantic model uses a default data connection without explicit connection credentials. Please replace the default data connection in the semantic model settings with an explicit cloud or gateway data connection.”This happens because:- When you publish a model that combines Azure SharePoint and Lakehouse, the service attempts to use a default connection without explicit credentials.
- Previously, the service allowed legacy connections, but now it requires explicit credentials defined in the service, not just in Desktop.
- The issue is common when:
- The SharePoint source is configured as Personal Cloud Connection.
- There is no Gateway or Cloud Connection explicitly defined for each source.
How to Resolve It
1. Check Credentials in the Service
- Go to Dataset Settings → Data Source Credentials.
- For each source (SharePoint and Lakehouse), set explicit credentials:
- SharePoint: choose OAuth2 and enter your credentials.
- Lakehouse: use Organisational Account or Single Sign-On if available.
2. Avoid “Default Data Connection”
- In Power BI Desktop, remove any legacy or default connections.
- Ensure each source is configured with an explicit connection before publishing.
3. If Using a Gateway
- Configure a Personal or Enterprise Gateway for SharePoint if OAuth2 cannot be used.
- Map the credentials in the Gateway for the SharePoint source.
4. Republish the Model
- After adjusting the credentials, publish the report again.
- Test a manual refresh in the service.
Official Reference:
https://learn.microsoft.com/power-bi/connect-data/service-gateway-onpremIf this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.
Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.
- TimoRiikonen
Advocate V
1) SharePoint has been set. Lakehouse is not visible here.
2) The report has only two connections: Azure Sharepoint and Lakehouse that uses SQL connection.
Here is my SQL connection as M code:
let
Source = Sql.Databases("1234.datawarehouse.fabric.microsoft.com"),
gold = Source{[Name="gold"]}[Data],
#"Filtered Rows" = Table.SelectRows(gold, each ([Item] = "ourdata")),
3) I have tested a few options for the Azure Sharepoint but I always get still the same error.Credentials mapped.
4) Done. Breaks still when doing the manual refresh.
> https://learn.microsoft.com/power-bi/connect-data/service-gateway-onprem
We are not using onprem systems, so I did not find anything that I thought would be relevant in this document.
- TimoRiikonen
Advocate V
I succeeded to fix this though:
I changed the SQL connection from OAuth2 to service principal / workspace identity.
Sharepoint worked fine with Personal Cloud Connect setting.
- TimoRiikonen
Advocate V
Zanqueta <
This part "In Power BI Desktop, remove any default connections" is difficult to understand.
You can change default connections in service after you have published, but changing it before publishing...I don't know how to do that.
Also "Lakehouse: use Single Sign-On if available."I succeeded after I changed from Single Sign-On OAuth2 to service principle, which is opposite to instructions.
So it looks to me like either instructions or functionality is not correct right now.