Unable to access data from Azure SQL Database in Power BI Service

[Anonymous]

Hi all,

I was creating and publishing reports in power bi by connecting to Azure SQL Database instance. Due to security restrictions, we use VPN and created the reports in Power BI Desktop inside a VM environment. 

Everything worked fine in the Desktop.  When I published the reports to Service, Power BI Service prompted me to whitelist the Power BI Service Client IP.  I did the same by raising request to IT team and all worked fine.

Recently we were required to switch between servers (data table names and labels remain the same) and the migrated reports worked well in the Power BI Desktop (installed in the VM). When I published the same to Power BI Service, it prompted to whitelist the Client IP, as usual, and I configured the same for the port number 1433. But this time, I encountered an instance related error as follows:

But the server is very much running and could be accessed by SSMS inside the VM. The Client IP is whitelisted so shouldn't it be able to access data from Azure SQL DB? Or is there a separate step/setting to configure the Server to allow remote connections?

Please advise me what should be the next step.

Thanks in advance,

Cheers,

BRP

[Icey]

Hi @Anonymous ,

Is this problem solved?

If it is solved, please always accept the replies making sense as solution to your question so that people who may have the same question can get the solution directly.

If not, please let me know.

Best Regards
Icey

[nkuppili]

@Icey Thanks for your inputs, Do you think this is best way (via gateway route) to make secure and successful connection when source is on private network (in my case Azure SQL)?

[Icey]

Hi @Anonymous ,

1. Do you enable VPN to keep the connection?

If not, please enable VPN and try it again.

2. Was your Azure SQL Database set secure connection to Power BI Service?

If it was, I suggest you to use an Enterprise gateway, even the data source is in cloud. 

The Power BI Gateway server runs on a private Azure VNet, and the SQL Server's firewall is configured to allow connections from this VNet.

Best Regards,

Icey

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