Refresh Failure in power bi workspace : Premium_ASWL_Error

[prasadpatil020]

Hi Community,
Earlire refresh was working fine but once i have published the report and semantic model from my end then I am facing the below issue while refreshing the power bi report, kindly help with the root couse or the solution.
Error : 
Last refresh failed: 11/12/2025, 4:11:11 PM An error occurred while processing the semantic model.Hide details 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 dataset because the dataset contains calculated tables or calculated columns based on data from a Single Sign-on (SSO)-enabled Direct Query data source. Please configure the dataset to use an explicit connection with granular access control to access this data source and then try again."}}],"exceptionCulprit":1}}} Cluster URI: WABI-NORTH-EUROPE-D-PRIMARY-redirect.analysis.windows.net Activity ID: 4c051b7e-c1f1-4203-a4cd-848b862adfac Request ID: 62c95263-ebed-aeb3-17bc-e5d930cf9de3 Time: 2025-11-12 10:41:11Z

[prasadpatil020 · Accepted solution]

Hi @data ,
I had missed to turn it on data connection , now its working fine, thank you so much for your time 

[prasadpatil020]

Hi @DataVitalizer 
Find the below screenshot for your referece.
1. Semantice model with Personal Cloud Connect which is working fine.

2. Below semantic model was not working earlier with Personal Cloud Connect, so I have created multiple connectors that time it has started refreshing currectly.
Here my understanding is , it should work as per the the 1st screenshot with Personal Cloud Connect.
Kindly correct where i am doing wrong.

[DataVitalizer]

I see your point, but the issue is that Personal Cloud Connect works only when there are no calculated tables or columns based on SSO-enabled DirectQuery sources.

In your second model, those calculations are causing the refresh to fail even if it looks similar to the first one.

To make it work like the first, you’ll need to either remove those calculations or change how the data connects (like using explicit credentials instead of SSO).

Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡

🟩 Follow me on LinkedIn

[prasadpatil020]

Hi @DataVitalizer 
Really appreciate your help.
As I am using Google Bigquery as a datasource hence I cannot go with basic authontication , i have to go with OAth2, but still issue persist.

[DataVitalizer]

Hi @prasadpatil020 

Your refresh fails because the dataset has calculated tables or columns built on top of an SSO DirectQuery source, which the Power BI service doesn’t support.

It worked locally with your credentials, but once published you need either to remove those calculated tables or switch the connection to explicit credentials (via gateway or database login), adjusting that setup will allow the refresh to succeed.

Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡

🟩 Follow me on LinkedIn