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.
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.
Thanks.
v-cboorla-msft Element115 shared information with me through PM as requested.
I've not yet been through it and will very soon. Dhruv_Ranpura sharing this information can help us troubleshoot what's happening in your specific case.
I'll update the thread with the relevant information as I discover them.
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.
Element115 If I want to check this firewall rule where I can check ? Can you please guide?
I'm the wrong guy to ask tbh. Would be better to ask your sysadmin. Besides we don't all use the same brands of firewalls and there seems to be many differences between them when it comes to UI and settings etc.
Element115 I have a similar issue when trying to import data from sql server to Fabric data warehouse, the error occured during the step of adding destination. I'm not a system admin, so what do I have to tell our system to do regarding opening these endpoints (*.datawarehouse.pbidedicated.windows.net, *.datawarehouse.fabric.microsoft.com, *.dfs.fabric.microsoft.com)? Our IT team told me already that they can not open the whole domain, so what can be done to solve the firewall issue?
You said: "...we specified the 0.0.0.0/TCP/1433 for outgoing traffic and that did the trick." Could you pls explain in more details?
Basically, 0.0.0.0 means any domain.
The main thing is this: outgoing TCP traffic on port 1433 needs to be open. This port is used by MS SQL Server, so implicitly you are telling the firewall let all outgoing MS SQL Server traffic through.
As to the Microsoft wildcard FQDNs, if your IT dept tells you it's a no-go, then I don't know what to tell you. Either you open outgoing traffic on port 1433 to any domain, or to the wildcard FQDNs provided by Microsoft in their documentation. Since Microsoft does not provide non-wildcard FQDNs, you can't specify anything else but these 2 categories of domains I just mentioned.
Dhruv_Ranpura I'm gonna have an update on that info this PM.... waiting for my sysadmin... sounds like there might be an additinal port other than 1433 that needs to be open.
