Azure SQL Connection on Gateway cannot be used

[Data-Crunch]

Hi community

I have a report for which I connected to Azure SQL in Power BI Desktop and I was able to authenticate normally using Basic Credentials while being in the VPN (Due to firewall settings). Upon upload to the service, for some reason, even though it is a Azure Instance, it wants me to create a "normal" SQL Connection in the Enterprise Gateway. The connection then, obviously, fails. If I create a new connection from scratch for Azure SQL Managed Instance, it connects just fine, however, I cannot point the semntic model to use that connection for the refresh...

Managed Instance works fine, but cannot be used then in the semantic model

Adding a new connection directly from the semantic model will try to create an SQL Connection instead:

What is happening here? Anyone came across the same issue? Am I missing something?

Thanks for the help!

[Data-Crunch · Accepted solution]

Hi @blopez11
Thanks for the help, I figured out what the problem was! The port which I had added at the end of the string (not visible in the screenshots since I blacked it out, sorry!) seemed like it provoked that behaviour. So note to self: Azure SQL in the Gateway with Port does not seem to work, at least it does have problems recognizinig it as such...
Without the port I can add the cloud connection and use it just fine.

[Data-Crunch]

Hi @blopez11 Thanks for the reply, no unfortunately it only shows the other connection, which is indeed a cloud connection but not a SQL Instance on Azure:

[blopez11]

In the "Gateway and cloud connections" section, maybe toggle the "Use an On-premises or VNet data gateway"  button to Off.  If not, can you send a screenshot of the whole "Gateway and cloud connections" section?

[blopez11]

The first screenshot is cut off.  So you do not have the option to create a cloud connection in the model settings?