Power BI Enterprise Gateway - Firewall (Wildcard Not Supported)

[cjones]

Hi,

My question is similar to the post below but the solution there is impractical for me:

http://community.powerbi.com/t5/Service/Firewall-Power-BI-Enterprise-Gateway/m-p/19308#M5649

In Power BI Enterprise Gateway installation instructions multiple firewall rules are given as below:

*.powerbi.com	443	HTTPS
*.analysis.windows.net	443	HTTPS
*.login.windows.net	443	HTTPS
*.servicebus.windows.net	5671-5672	Advanced Message Queuing Protocol (AMQP)
*.servicebus.windows.net	443, 9350-9354	Listeners on Service Bus Relay over TCP (requires 443 for Access Control token acquisition)
*.frontend.clouddatahub.net	443	HTTPS
**.core.windows.net	443	HTTPS
login.microsoftonline.com	443	HTTPS
login.windows.net	443	HTTPS

However, our firewall doesn't support wildcards (*) only ip's or the full domain name and 443 is blocked (outbound) by default.

The recommendation in the post was to use the Azure data centre white list but this is quite a hefty list and can change and would be a manual import in our firewall (I'm told) so not preferred.

I want to use the full domain (i.e not *.powerbi.com but xyz.powerbi.com) as the firewall can support this but I can't find an explanation of what the full name is or how is it defined.

For example, is the * in  *.servicebus.windows.net  is it;

a. Something that I can configure myself (on Azure or on the Gateway)

b. Something fixed generated by the Enterprise Gateway that I can retrieve

c. A fixed list of names defined by Microsoft that I could get somehow

d. You've missed the point entirely it is something else

Is it possible to explain if I can get the full name (and how ) or if the only possible solution is to import the white list and update it after each update.

Thanks for your time.

Chris

[cjones · Accepted solution]

I finally managed a workaround from this which I thought I would add back as it might be helpful to someone.

Confirmed with Microsoft that at present only * or full IP whitelist of Azure are the only available options so in the end I routed the connections via our proxy using the guide at https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-proxy/.

[sandeep_nakarmi]

Can you elaborate what actually you had to do in proxy?

[sandeep_nakarmi]

could you elaborate what actually you did on proxy to get it to work?