Powerbi Gateway IP and Port Configuration

[Rinaldi]

Hi.

I have a PowerBI Gateway server configured for the ip / domain destination based on this link https://docs.microsoft.com/en-us/data-integration/gateway/service-gateway-communication#ports. When I try to refresh pbix on a cloud connected to the Powerbi gateway, several times it works but sometimes an error (unreachable).

I tried to make changes with the IT team, to open all destination IP/domains but ports are limited based on the links I mentioned. And it running well.

My question is there any changes/additions to the IP/domain destination? if yes, may I know the list what ip/domain apart from the documentation on the link I mentioned earlier. And about the port, are there any changes/additions apart from the link too?

Or I just provide access to the IP in this below.

g0-prod-hk2-005-sb.servicebus.windows.net 13.88.223.182
g1-prod-hk2-005-sb.servicebus.windows.net 13.88.223.39
g2-prod-hk2-005-sb.servicebus.windows.net 13.88.219.94
g3-prod-hk2-005-sb.servicebus.windows.net 13.88.222.94
g4-prod-hk2-005-sb.servicebus.windows.net 13.88.220.115
g5-prod-hk2-005-sb.servicebus.windows.net 13.88.223.84
g6-prod-hk2-005-sb.servicebus.windows.net 13.88.223.157
g7-prod-hk2-005-sb.servicebus.windows.net 13.88.220.199
g8-prod-hk2-005-sb.servicebus.windows.net 13.88.219.204
g9-prod-hk2-005-sb.servicebus.windows.net 13.88.218.189
g10-prod-hk2-005-sb.servicebus.windows.net 13.88.220.22
g11-prod-hk2-005-sb.servicebus.windows.net 13.88.220.123
g12-prod-hk2-005-sb.servicebus.windows.net 13.88.220.183
g13-prod-hk2-005-sb.servicebus.windows.net 13.88.217.107
g14-prod-hk2-005-sb.servicebus.windows.net 13.88.217.225
g15-prod-hk2-005-sb.servicebus.windows.net 13.88.219.200
g16-prod-hk2-005-sb.servicebus.windows.net 23.98.34.184
g17-prod-hk2-005-sb.servicebus.windows.net 23.98.36.251
g18-prod-hk2-005-sb.servicebus.windows.net 23.98.37.139
g19-prod-hk2-005-sb.servicebus.windows.net 23.98.35.4
g20-prod-hk2-005-sb.servicebus.windows.net 23.98.38.134
g21-prod-hk2-005-sb.servicebus.windows.net 23.98.37.129
g22-prod-hk2-005-sb.servicebus.windows.net 23.98.32.166
g23-prod-hk2-005-sb.servicebus.windows.net 23.98.35.235
g24-prod-hk2-005-sb.servicebus.windows.net 23.98.34.236
g25-prod-hk2-005-sb.servicebus.windows.net 23.98.33.151
g26-prod-hk2-005-sb.servicebus.windows.net 23.98.39.199
g27-prod-hk2-005-sb.servicebus.windows.net 23.98.37.16
g28-prod-hk2-005-sb.servicebus.windows.net 23.98.39.58
g29-prod-hk2-005-sb.servicebus.windows.net 23.98.37.18
g30-prod-hk2-005-sb.servicebus.windows.net 23.98.33.25
g31-prod-hk2-005-sb.servicebus.windows.net 23.98.36.236
g58-prod-hk2-005-sb.servicebus.windows.net 13.70.6.195

Thank you, please help.

[v-xicai]

Hi  @Rinaldi  ,

Do the suggestions from engineers make sense? If so, kindly mark the proper reply as a solution to help others having the similar issue and close the case. If not, let me know and I'll try to help you further.

Best regards

Amy

[RakeshSinghr]

If its working atleast once that means the connection has been established and no other ports to be opened.

I'd look at your proxy server to see if incoming request is being blocked during the failure time.

Also, enable verbose logging and check the errors logs.

Track the time it takes to error out, for example erroring out immediately when refresh starts versus consistent error out time for example say after 1 min or so to discount internet speed/network bandwidth issues

[Rinaldi]

Hi Rakesh Singh r,

Enable verbose logging you mean is "additional logging" at powerbi gateway application"?

And how can you see our proxy server?

But based on my previous question, because our network IT team limit the network, which IP destinations can I open? because since the gateway application is used on the server, there is a limited role by our network team.

Thanks.

[RakeshSinghr · Accepted solution]

ip addresses for azure data centers are constantly changed. You'll need exception rules or whitlist FQDN's.

Get your network team to run wire shark and see where the packet is being blocked.

Perform network test inside of the gateway app to see if you get any more info

[Rinaldi]

Hi.

Thanks to @RakeshSinghr. That's good solution. 

I'm discussing this to the network team.

But my last question. "need exception rule" you mean is open all the ip destination right? or create FQDN's whitlist. And about FQDN's whitlist, can I download the list IP from this link https://www.microsoft.com/download/details.aspx?id=41653? or just run wire shark to check where the packet is being blocked and check network ports test. Just to make sure it.

Thanks.

[RakeshSinghr]

If you download ip list today and create exception rules based on those ip's what will you do when ip's are changed next week?  Hope you got the point. Better to use FQDN's 

[Rinaldi]

OK Thanks @RakeshSinghr