I guess this purpose of this post is to make others aware that the gateway is NOT "enterprise ready", and list the issues we've been having to set it up - hopefully that will save someone time we spent on this:
We're aiming to install the gateway on a Azure VM in a big enterprise (Azure). Due to cyber risks, it was agreed that the VM will not have access to internet, and only the URL's & ports specified as per Microsoft Documentation was allowed through the Firewall and NSG's and traffic flows through ExpressRoute: https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem/
Install package version 14.16.6317.4 downloaded from here: https://www.microsoft.com/en-us/download/details.aspx?id=53127
1) Gateway software installation succeeds. The next step is to "use an account to identify the gateway". Documentation for what priveleges this account should have is non-existant. As our setup is an enterprise we didn't want to use an individual's account
2) The documentation does NOT make provisioning for ADFS authentication. On sign-in, the O365 tenant will block the request as its coming from an untrusted source via Express Route. All traffic is routed via express route so proxy settings won't make a difference
3) Following suggestions on other forums, we then created a user directly in O365 and use it to log on - mixed responses between "Network Requests" errors and blocked sign on. At a point we were able to proceed to configure the gateway, however the gateway application crashed. On PowerBI the gateway was registered as per picture 3, but we're unable to get it started on the VM again. Reinstall is met with blocked sign-on again.
We'll now proceed poking more holes in our NSG's and firewalls to finalise the configuration section of the gateway. It would have been helpful if the documentation made these clear distinctions which is required during configuration. We're still unclear of what will be required in the longer term to maintain the software.
