Forum Discussion
Mass IP Whitelisting for Azure Datacenter
Hi All,
Found a solution to my problem.
Downloading the newest version of the Power BI Gateway (or at least something from Februrary 2017 onwards) and setting the ServiceBusSystemConnectivityModeString to Https will force the Gateway to use Fully Qualified Domain Names (FQDN) instead of the IP addresses. These FQDN's are a part of the initial whitelist of proxies found in the on prem how to guide provided by Microsoft.
This also has the advantage of being future proof as the chaging IP addresses will still point to the same FQDNs.
Thanks Microsoft for providing this functionality.
Cheers.
Hi Mmeyers,
We were also in this pickle, although in this scenario I am in the position of your redshift partner. Annoyingly, PowerBI service isn`t split by region in the list of IP`s (lots of other products are like PowerQueryOnline and ADF) so what we had to do is download the list of IP`s, geolocate the IP addresses from the country\azure region where we know the PowerBI tenant is (we know this, there`s only 3) then white list the CIDR ranges from there. All this is done in an automated fashion as the list of IP addresses is published every so often. It`s the only way we could figure out how to do it. Microsofts usual response is to use a gateway but a gateway won`t work if you want to push a dashboard out as a PowerBI app.
Why would a gateway not suffice for delivering content via a PBI app? Is it because you are a partner and not on the customer's tenant?
why create/maintain a gateway when powerbi service has the ability to connect to amazon redshift directly?
Exactly my point too. Another cloud BI tool I work with (Qliksense) can supply 2 static IP addresses for whitelisting.
Template apps don`t support the use of either personal or enterprise gateways.
