Default connection on Semantic Models

[Anonymous]

Hello,

I’m encountering an issue with refreshing a Power BI report that was created using the SQL Analytics endpoint of a Lakehouse. When I uploaded the report to Power BI Fabric, the semantic model automatically generated a Default Connection (SSO). However, I am unable to refresh the model due to the following error:

“We cannot refresh this semantic model because it 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.”

Since I cannot edit the Default Connection, the only solution I see is to create a new connection.

However, I would like to better understand whether this is a limitation of using Import Mode with the Default Connection, or if there are other changes I need to make to resolve this issue.

Additionally, I’m looking for official documentation regarding the relationship between refreshing the semantic model and the Default Connection. Should I enable SSO even though my report is in Import Mode, or is SSO only relevant for DirectQuery connections, as I understand?

Thank you in advance!

[Olayemi_Awofe]

When Power BI report published using a Lakehouse or Warehouse SQL Analytics endpoint, Power BI automatically creates a Default Connection using Single Sign-On (SSO). This works fine in Power BI Desktop, but in the Power BI Service, SSO-based default connections don’t support scheduled refreshes

You need to manually create a new data connection with explicit credentials and bind your semantic model to it:

1. Go to Power BI Service

Open the workspace where your semantic model (dataset) is published.

2. Open the Semantic Model Settings• Click the ellipsis (⋯) next to the dataset.

• Choose Settings.

3. Replace the Default Connection• Under Data source credentials, you’ll see the default connection listed.

• Click Edit credentials.

• If it doesn’t allow editing (common with default connections), proceed to the next step.

4. Create a New Connection• Go to Manage Connections and Gateways in the Power BI Service.

• Create a new Cloud Connection to your Fabric Warehouse or Lakehouse.

• Use OAuth2 or Basic Authentication with explicit credentials.

5. Rebind the Semantic Model• In the dataset settings, map the new connection to the dataset.

• Save changes.

6. Schedule Refresh• Now go to the Scheduled refresh section.

• Set your preferred refresh frequency and time.

If you’re using Import Mode, this fix is essential. For DirectQuery, refresh isn’t needed, but you still need explicit credentials for live queries to work in the service.

[andrewsommer · Accepted solution]

Yes, SSO is mostly only relevant to DirectQuery and you are right that creating a new connection is the correct fix.

To enable refresh for an Import Mode report on Fabric:

1. Create a New Connection in your workspace:

   • Go to Manage Connections and Gateways in the workspace.

   • Click New Connection, choose Lakehouse (or SQL Server if applicable).

   • Configure Azure AD Authentication with a service principal or Managed Identity if available.

2. Bind the Semantic Model to This New Connection:

   • Go to the Semantic Model settings in the workspace.

   • Under Data source credentials, replace the Default Connection with your new one.

   • This enables refresh scheduling.

What is the SQL analytics endpoint for a lakehouse?

Overview of single sign-on for on-premises data gateways in Power BI

Please mark this post as solution if it helps you. Appreciate Kudos.

[Anonymous]

Can we achieve this using API's in python?