Forum Discussion
Error when trying to create a dataflow gen 2.
Guys.... it is fixed
My bad... after all.
It IS all about the fire wall.
We open it on the on-prem server BUT it is not enough!
AS we are hosting it on some data center, THEY have to open the firewall and it will work.
The biggest problem now is that they are not happy about it as we open another port in thier firewall, and they cannot do the *.domainname roles apperently so they open for all!!!
Microsoft support - is there any way to give them a specific address/s to open?
Glad to hear that it's firewall after all. For specific IP addresses, you can check the PowerBI service tag - Power BI\Fabric uses specific preallocated IP addresses for inbound and outbound connectivity, the entire range is listed here:
Download Azure IP Ranges and Service Tags – Public Cloud from Official Microsoft Download Center
You can probably narrow it down to your specific cluster region instead of the entire range. Find out which FQDN you had to allowlist for this to work, and then nslookup on it. Then you can find the PowerBI's IP addresses in that region in the document above.
What is i put in the firewall role the urls of the end point of the lakehouse, warehouse and the staging DB's?
Will that be enough?
pqian_MSFT have you seen my question?
That should be enough but it won't be scalable, since these are per workspace. If you or anyone in your org in the future creates more workspaces or dbs, they will also need allowlisting.
This is also assume you can even do FQDN at the firewall level. Usually L2 firewalls do not allow FQDNs.