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.
Dhruv_Ranpura I see... so it issues the same error msg + now the handshake error. The latter then could mean it's not able to see your on-prem DB through the gateway.
When you are inside Power Query/Dataflow Gen2, in your first dataflow, can you see the data come in, that is, does Power Query show you a table of your data?
Yes, Element115 when I created first DFGen2 I am able to see the data . It is showing the tables.
Then I created another DFGen2 and while selecting the Dataflow 1 as a input option getting the error of pre-login hanshake error.
OK so the DF is able to talk to the DB successfully via the GW, otherwise there wouldn't be any data coming through to the first DF. So it's when it goes back to the GW and to the data destination that something funky happens with the TLS protocol. In other words,
DF2--->GW--->LH
which is weird because it doesn't do that for me, and I use the exact same architecture, which in my case got rid of all these weird errors:
on-prem DB--->GW--->DF1 ---> DF2--->GW--->LH
Also, from what I have seen, there is no real tweaking available at the GW UI for TLS. Only the firewall rules. Speaking of which, my sysadmin couldn't get this endpoint to respond: *.dfs.fabric.microsoft.com, as if it were misconfigured. But ETL still works, so not sure how essential it is to have this endpoint in the firewall rules.
I sure wish Microsoft would provide some in detail and specific guidance on this, if only with a detailed and cleared doc write-up, ie more than just what can be found here: On-premises data gateway considerations for data destinations in Dataflow Gen2 - Microsoft Fabric | Microsoft Learn I mean, we are in the weeds here, and if this product is meant for BI or data people but NOT network engineers, well then... we got a problem now, don't we?