What the Power BI On-Premises Data Gateway Does
The Power BI on-premises data gateway is a lightweight service that sits on a machine inside your network and forwards requests between the Power BI cloud service and local data sources such as SQL Server, Oracle, SharePoint, and file shares. It allows datasets hosted in the Power BI service to refresh on a schedule or to support DirectQuery and live connections, without requiring those sources to be placed on a public endpoint or exposed through a firewall.
More from this site
Keep reading the latest coverage
The gateway operates on a machine you control inside your perimeter. It registers with your Power BI tenant using a service principal or an organizational account, and it uses outbound HTTPS (port 443) to communicate with Microsoft endpoints. Inbound connections from the internet are not required, which is one of the main reasons organizations choose it over opening ports to their data servers.
How the Gateway Connects to Data Sources
Once installed, the gateway appears in the Power BI service under Settings > Manage gateways. From there, you can add data sources, assign users and groups permission to use them, and monitor connection activity. The gateway maintains a secure channel to the cloud service and then uses native drivers or connectors on the host machine to reach the local data source.
Users and workspaces do not connect to the gateway directly from their machines. Instead, a dataset configured to use the gateway routes its query or refresh call through the cloud service to the gateway, which executes the request locally and returns the result. This architecture keeps credentials and connection logic inside the network boundary.
Gateway Modes and Licensing
Microsoft offers two primary gateway types: the personal gateway and the enterprise gateway, formerly known as the on-premises data gateway. The personal gateway is intended for individual use, works with Power BI Desktop and the service, and supports a limited set of connectors. The enterprise gateway supports more connectors, can be used by multiple users and workspaces, and is required for many production scenarios.
| Aspect | Personal Gateway | Enterprise Gateway |
|---|---|---|
| Typical use | Individual authoring and refresh | Shared workspaces and production refresh |
| Connector breadth | Limited set | Broad set, including relational and file sources |
| User sharing | Single user | Multiple users and groups |
| High availability | Not built in | Supported via cluster mode |
The enterprise gateway requires a Power BI Premium per-user or Power BI Premium capacity assignment. Microsoft also offers the standard gateway as a separate download in many cases, and licensing details can shift with service updates, so it is worth confirming current requirements in the official documentation before planning a deployment.
Installation and Configuration Considerations
The gateway runs as a Windows service and can be installed on a dedicated server or a shared machine inside the network. Microsoft recommends a stable host with sufficient memory and CPU, especially if the gateway will handle large refresh volumes or many concurrent queries. During setup, you sign in with a work or school account that has permission to manage gateways in the Power BI admin portal.
Key configuration steps include naming the gateway, selecting the data sources it should expose, and assigning users or security groups to each data source. The gateway uses Windows credentials or embedded credentials depending on the connector, and it stores those credentials encrypted on the host machine. For environments with strict security policies, you can also configure the gateway to use a proxy server for outbound connectivity.
Monitoring, Troubleshooting, and Maintenance
The Power BI service provides a gateway cluster portal where administrators can view gateway status, data source health, refresh history, and error details. Common issues include driver mismatches, firewall rules blocking outbound HTTPS, expired credentials, or insufficient permissions on the data source.
- Verify that the gateway service is running on the host machine.
- Confirm outbound HTTPS access to Microsoft endpoints is not blocked.
- Check that the account used to register the gateway has not been disabled or changed.
- Ensure the correct driver or connector is installed on the gateway host.
Microsoft releases updates to the gateway periodically, and it is recommended to keep it current to maintain compatibility with the Power BI service and data source connectors. In clustered deployments, one node acts as the primary and others as secondaries for failover, but the cluster must be managed consistently to avoid configuration drift.
When to Use the Gateway
The gateway is the standard path for organizations that need scheduled dataset refresh or live query connectivity to on-premises systems while keeping those systems inside the network. It is particularly common in regulated industries, on-premises-first estates, and scenarios where data residency or compliance rules prevent moving source data to the cloud.