Onelake datasource (Datawarehouse) is showing up as a SQLserver datasource within on-premise gateway

[LuukSteenbergen]

This is an interesting issue, I published a PowerBI report within a Fabric workspace. The report has 2 sources, an on-premise SQL server, which connects fine and is also recognised and accepted with the gateway i've installed. the 2nd is a DWH within Fabric(OneLake). however, the Onelake DWH source shows up as a SQLserver datasource when trying to setup the gateway connections to be able to setup scheduled refresh. (see picture)

It does however. also shows it to be a cloud connection: 

This seems really odd to me, and i can't find the reason why this is happening, hopefully someone can help me out! TY

[v-menakakota · Accepted solution]

Hi @LuukSteenbergen,

Thank you for reaching out to the Microsoft Fabric Community Forum.

We really apologies for the inconvenience, after reviewing the issue of one lake data source data warehouse is showing up as a SQL server data source within on premises gateway, here are few steps which may resolve the issue.

• Navigate to power bi service → click on settings → manage connections and gateways. Identify the one lake data warehouse source incorrectly classified under the on-premises data gateway as sql server. Remove this incorrect mapping and ensure that the one lake data warehouse is not configured under the gateway. Save your changes to apply the updates.
• Please remain in the power bi service and navigate to settings → manage connections and gateways → cloud connections. Ensure that the one lake data warehouse is listed as a cloud data source and mapped to default.
• If a one lake data warehouse is missing, please re-add it by clicking add data source, selecting azure data warehouse / one lake data warehouse, setting authentication to single sign on, and clicking save to apply the changes.
• Please navigate to the power bi service and go to the datasets section. Select the dataset associated with the power bi report, then click on settings and scroll to data source credentials. Ensure that the on premises sql server is mapped to the gateway and that the one lake data warehouse is mapped to the cloud connection with single sign-on enabled.
• If there are any mistakes, please update them accordingly and apply the changes. In the dataset settings, navigate to the scheduled refresh section. Enable the refresh option and click refresh now to test. If successful, proceed to schedule periodic refreshes as needed.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Best Regards.

[v-menakakota]

Hi @LuukSteenbergen ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Regards,
Menaka.

[v-menakakota]

Hi @LuukSteenbergen ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-menakakota]

Hi @LuukSteenbergen ,

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.

Thank you.

[nilendraFabric]

Hi @LuukSteenbergen 

The Fabric data warehouse appears as a SQL Server data source because it exposes a SQL endpoint that Power BI uses to connect to the data.
Gateway is not needed for Fabric WH.
In PBI dekstop :

• Go to Data Source Settings
• Select your Fabric/OneLake data source
• Edit Credentials
• Switch from 'Windows' to 'MS Account' and log in
  

Hope this works

Thanks 

[LuukSteenbergen]

Hi @nilendraFabric ,

I checked and the credentials was already my Microsoft account. So that did not appear to be the issue.. Thanks anyways