Quantcast
Channel: Service topics
Viewing all articles
Browse latest Browse all 61862

Power BI Enterprise Gateway - Firewall (Wildcard Not Supported)

$
0
0

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.com443HTTPS
*.analysis.windows.net443HTTPS
*.login.windows.net443HTTPS
*.servicebus.windows.net5671-5672Advanced Message Queuing Protocol (AMQP)
*.servicebus.windows.net443, 9350-9354Listeners on Service Bus Relay over TCP (requires 443 for Access Control token acquisition)
*.frontend.clouddatahub.net443HTTPS
**.core.windows.net443HTTPS
login.microsoftonline.com443HTTPS
login.windows.net443HTTPS

 

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 Smiley Happy) or if the only possible solution is to import the white list and update it after each update.

 

Thanks for your time.


Chris


Viewing all articles
Browse latest Browse all 61862

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>