Azure SQL Server connection error on Power BI service

[jesse_james]

Hi, I have problem with connection with SQL Server. I can connect in Power BI Desktop and SSMS using SQL Basic Authentication but it doesn't work in Power BI Service. Error message:

"Failed to update data source credentials: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."

and SSMS successful login window:

do you know where can be problem?

[GauravKhare7]

Hi @jesse_james ,

I'm having the same isssue, did you manage to get it resolve? 

[v-diye-msft]

Hi  @jesse_james 

Did you try to clear the credentials under the data source setting and try again?

Are you able to connect to SQL Server from SQL Server Management Studio(SSMS)? Ensure that SSMS is installed on the same machine with Power BI Desktop.

Besides, please follow the instructions in the article below to troubleshoot this connection error.
https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/troubleshoot-connecting-to-th...

Also, here's similar solved thread could be your reference:

https://community.powerbi.com/t5/Desktop/Can-t-connect-to-SQL-Server-named-instance/m-p/308006 

[jesse_james]

Hi, 

yes I've just tried with cleared credientials- with the same error.

I manage to log in via SSMS on the same machine like Power BI Desktop.

I also tried to use other machine - still nothing.

[GilbertQ]

Hi there

When using Azure SQL DB you do not need to configure it in the Gateway you can connect to it by going into your dataset, then data source settings and putting in the SQL Authentication details?

[jesse_james]

I tried both options with gateway and without it. Both gave me the same error..