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 for using Microsoft Fabric Community.
Apologies for the inconvenience that you are facing here.
The error you are encountering when trying to retrieve the list of tables in Microsoft Fabric Dataflow Gen2 could be due to a due to Gateway Configuration.
Ensure that the gateway is correctly configured with an open port 1433, as this is necessary for the gateway to send data to the Lakehouse this might help you.
For details please refer : Network issues with port 1433
If the issue still persists please do let us know. Glad to help.
I hope this information helps.
Thanks
I got a question re this GW config business. In another thread, pqian_MSFT explained how the data flows between a datasource, the GW, and the destination when the source is an on-prem DB.
Now, I remember reading somewhere that there might be issued arising because of some protocol called TLS. I didn't see anything in the GW to address potential TLS issues.
Is there something we need to configure re the TLS protocol either at the GW or firewall level? Or the TLS payload is simply encapsulated in a TCP/IP packet and all we need worry about (firewall-wise) is the TCP rule?