Issues on connection between Power BI and Azure SQL Database using VNet service endpoints

[marcosdp]

Hi, I'm facing an issue on trying to connect Power BI to Azure SQL Server with Private endpoint activate and public access disable.

After creating an virtual network gateway on Power Platform I could access Azure SQL Server on Power BI DataFlow creation with no issues. However, after saving data flow creation and confim first execution, system displayed "Execution for On-Prem data source failed because it's not registered on a gateway (218884)" message.

Could someone help me to identify the solution for that issue?

[v-cazheng-msft]

Hi @marcosdp,

If you directly register your Azure SQL data source to your VNet gateway, will you see any error? Please create and save your dataflow after you register successfully there.

Best Regards,    

Community Support Team _ Caiyun

[marcosdp]

Hi @v-cazheng-msft,

I've followed all the steps related to this documentation https://www.datahai.co.uk/power-bi/connecting-power-bi-to-azure-sql-database-using-private-endpoints... 

1. Look at bellow that Virtual Network data gateway is online.

2. At the first moment, I can access sql server table with no issues. I'm not sure the reason that Data Gateway option on Project Options has no content to select.

3. The problem starts when I click on Refresh now.

Execution fails with "Error: Execution for On-Prem data source failed because it's not registered on a gateway (218884). Additional details: . Param1 = 218884.Param2 = Request ID: xxxx" message

4. When I edit data flow again, systems ask for credentials as lost it.

So, I inform credentials again just to return to the same point as step 2

Any idea?

Best Regards

[lewisholmes]

I've just had exactly the same problem. Did you find a resolution?

[marcosdp]

Hi, @lewisholmes 

Unfortunately not. I think there is a bug on that power bi feature.

[rwars]

I have the exact same issue, and it's making it very annoying to maintain database-loaded datasets though a vnet gateway.  Will let you know if I find a resolution.

[aksmith]

We are having the same issue also - anyone know if there is a fix?