Forum Discussion

SMich's avatar
SMich
New Member
4 years ago

Gateway resides on different network

Hello,

I have an issue publishing to a gateway because our databases and Power BI Gateway are on two different networks. Users connect to network alpha by VPN and create reports. The firewall rules on alpha allow users to:

  • connect by VPN using an internal/non-public IP address
  • or connect while not on the VPN using a public IP address

The Power BI Gateway we publish to is on network beta. Alpha's firewall rules allow the gateway to connect using the public IP address. A user can successfully connect to the public IP of the databases, query, and publish the report. However, that user cannot be on the Alpha VPN, which is where they do most of their work.

 

We have been unable to change the IP address of reports/data sets after they are published.

We are trying to create a computer on the beta network where a user would edit the report, changing the data source's IP. This has been more difficult than we first thought. There are security and firewall rules that interfere.

 

Can anyone think of another way to allow the user to author reports while on the alpha network, but easily publish them to the gateway on beta?

Thanks you

Need Help

2 Replies

  • v-zhangti's avatar
    v-zhangti
    Icon for Community Support rankCommunity Support
    4 years ago

    Hi, SMich 

     

    Where to Install the On-Premises Data Gateway
    The following are some considerations for where to install the data gateway.

    • The machine should always remain powered on, with near full-time uptime.

    • The gateway server should reside as close to the data sources as practical to minimize

      network latency.

    • An Azure virtual machine can be a good option to install a gateway if on-premises equipment is not available. In this situation, the VM should reside in the same region as the Power BI tenant unless there are other considerations such as proximity to the data

      or minimizing data egress charges.

    • The gateway must reside in the same domain as the data source(s), or in another domain which is trusted.

    • The gateway server requires strong network connectivity (preferably not wireless), high bandwidth, and consistent internet access. ExpressRoute or Azure Private Link is highly recommended. The Azure Speed Test site can be used to check network latency between a client machine and an Azure region.
    • A potential starting point for a gateway server is 8 CPU cores and 16GB RAM, as noted in the Gateway Best Practices. Plan to scale up on CPU and/or RAM if bottlenecks present themselves, and/or scale out to multiple gateways if the volume of traffic becomes heavier than one data gateway can handle.

    https://docs.microsoft.com/en-us/power-bi/connect-data/service-gateway-power-bi-faq 

     

    Best Regards,

    Community Support Team _Charlotte

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.