Forum Discussion
Getting On-Prem data from SQL Server to Microsoft Fabric using Dataflow (gen2)
Dhruv_Ranpura so guys, ok so here's the deal (I am learning a lot about all this firewall stuff, hence why all the back and forth).
port 1434 is irrelevant.
One more thing for future readers: The endpoint listed on the MS doc page (*.datawarehouse.pbidedicated.windows.net, *.datawarehouse.fabric.microsoft.com, *.dfs.fabric.microsoft.com) are wildcard FQDNs. So it depends on the firewall what you can or cannot setup from what I've been told.
In our case, we specified the 0.0.0.0/TCP/1433 for outgoing traffic and that did the trick.
Oh man, what confusion... finally we got to an understanding. 😥 The Microsoft documentation should seriously be rewritten on this point, because the people who are going to read it are Fabric users, not network admins.
Thanks Element115 for your response.
I have been trying the method suggested by you. I have created one Dataflow(Gen2) with no data destination selection and published it. Now, I created another Dataflow(Gen2) and choose source as Dataflows (Fabric) and selected Dataflow1 and its table and when click on next I am getting this error.
I have checked that my SQL server is working fine on port 1433. So, why I am getting this error? Please guide.
Dhruv_Ranpura Also, in your firewall rules, do you have this:
- Protocol: TCP
- Endpoints: *.datawarehouse.pbidedicated.windows.net, *.datawarehouse.fabric.microsoft.com, *.dfs.fabric.microsoft.com
- Port: 1433
Dhruv_Ranpura anros Please ignore this previous msg. I just found out that by deleting all the endpoints from the firewall, and replacing the respective rules with only one rule opening TCP/1433 for MS-SQL Server service, it fixed all this connectivity nightmare. (DATAFLOW and ON-PREM DB connectivity solution - Microsoft Fabric Community)
Why does the doc say to add the endpoints, I have no idea. Delete is your friend in this case.