Installing Power BI On-Premises Data Gateway in another Region

Hi CHAUHAN812 

The warning you’re seeing is expected behavior and confirms that Power BI gateways can only operate within your tenant’s data region, which in your case is North Europe (Ireland). Even if you install the gateway on an Azure VM hosted in East US, Power BI will still bind it to the Ireland region automatically — this setting cannot be overridden. The reason is that Power BI enforces strict regional binding between gateways and tenant data to maintain compliance, performance, and data sovereignty guarantees. Opening specific network ports on your Azure VM won’t resolve this issue; those are only required to allow secure outbound communication from the gateway to the Power BI service.

If your goal is simply to connect to US-based data sources (like SQL, Databricks, or Azure resources in East US), the correct and supported approach is to install the gateway on that US VM but let it remain bound to the North Europe region — Power BI will still work correctly. The gateway acts as a secure bridge, transferring data from the US location to your tenant in Ireland, though with potential latency. If your intent is to host and process Power BI content entirely within the US (to meet compliance or performance goals), you’d need a separate Power BI tenant with its home region set to the US, since each tenant’s gateways and datasets are region-locked. In summary, you cannot assign a Power BI gateway to a different region than your tenant’s; network port changes won’t bypass this, and the only architectural alternative is to use or request a tenant in the desired region.