Directquery connection keeps mentioning gateway, but I dont have one!

[Anonymous]

Hi there!

I'm very confused about some of the behaviour that powerBI is showing. When I create a new file, connect using directquery to our Azure database in the cloud, and then publish that file, I see the following warning:

"Publishing succeeded, but the published report can't connect to the data source because we were unable to find a gateway. Please install and configure an enterprise gateway."

However, my data does not need a gateway because it is in the cloud. After publishing this report, the proof is right there, because when logging in with my account, the report works perfectly. However, when I then share this report with an external user, they see an error message about missing credentials for the data source ("The data source loyaltybi is missing credentials and cannot be accessed",which isn't correct either).

What part of DirectQuery do I not understand? Why is it warning me about gateways that I shouldn't need? Why do the users I share the report with see only errors?

Any help is appreciated!

Jaap

[v-cherch-msft]

Hi @Anonymous 

Based on my test, it doesn’t require gateway when refreshing data from Azure SQL database, when you publish the Power BI Desktop file to Service, you will find “Connect Directly” in the settings for the dataset. To share with an external user, try publish to web .

https://docs.microsoft.com/en-us/power-bi/service-azure-sql-database-with-direct-connect

https://docs.microsoft.com/en-us/power-bi/whitepaper-azure-b2b-power-bi

Regards,

[Anonymous]

 Thanks for the reply Cherie!

I agree that it does not require a gateway, the problem is that PowerBI desktop still tells me I need one. I believe this could be a bug. I have tested and verified that it does actually work fine, but PowerBI just told me it wouldnt 😛

[Anonymous]

Oh and as for the sharing of the report, that was my mistake. We actually have 2 domains and I was publishing my new report to 1 domain, while checking if it worked on another. D'oh!

[v-cherch-msft]

Hi @Anonymous 

It seems you've solved it,right? If so,kindly mark the solution to close this thread.

Regards,

[Anonymous · Accepted solution]

Hey Cherie, I'm afraid the problem is not really solved, I just ignore the error message. PowerBI displays an error message that doesn't apply. I just ignored the error message and it ended up working just fine. I'd say this is a bug in PowerBI. 

Jaap