The Power BI gateway is a piece of software that acts as a secure bridge between the cloud-based Power BI service and data that lives outside the cloud, such as on-premises databases and files on a company network. Its official Microsoft name is the on-premises data gateway.
What the Power BI gateway is
The Power BI gateway is a small program you install on a machine inside your own network. It gives the Power BI service a safe, controlled way to reach data that is not in the cloud, so a report published online can still draw on a database or files held in your office.
Microsoft's name for it is the on-premises data gateway. Most people call it the Power BI gateway because Power BI is the usual reason to install one, but the same gateway also serves Power Apps, Power Automate and other Power Platform services. Microsoft's on-premises data gateway guide describes it as the bridge that "provides quick and secure data transfer between on-premises data and several Microsoft cloud services".
Why you need a gateway
The Power BI service, the cloud half of Power BI, runs in the Microsoft cloud. When you publish a report, the report and its semantic model live online, not on your computer.
That's fine while the data is also in the cloud. The problem appears when a report needs data that sits behind your company firewall, such as a SQL Server database in a server room or a spreadsheet on a network share. The cloud service has no direct route to a private network, so it can't reach that source on its own.
The gateway closes that gap. It sits inside the network, where it can see the on-premises data, and it stays in contact with the Power BI service, so the service has a trusted path to data it could otherwise never touch.
How the Power BI gateway works
You install the gateway on a machine inside your network, ideally an always-on server so it is available whenever a report needs it. Once installed, the gateway keeps an outbound connection open to the Power BI service.
When a report needs on-premises data, the request flows in a clear sequence:
- The Power BI service sends the refresh or query request down the existing connection to the gateway.
- The gateway fetches the data from the on-premises source on the service's behalf.
- It returns the results to the service, encrypted in transit.
Because the gateway reaches out to the cloud rather than waiting to be contacted, there's no need to open inbound ports through the company firewall. That's what makes the design secure: data moves through a connection your network started, not through a hole left open for the internet.
Standard mode and personal mode
The gateway comes in two modes, and the right one depends on whether it serves an organisation or a single person.
- Standard mode: installed centrally and shared by many users and reports, normally set up and managed by IT. It supports scheduled refresh, live DirectQuery connections and other Power Platform services. This is the usual choice for a business.
- Personal mode: tied to one user, simpler to set up and needs no administrator. It supports only Power BI scheduled refresh, so it suits an individual keeping their own reports current rather than a shared, organisation-wide setup.
With a standard-mode gateway, the data-source connection details and credentials are configured in the Power BI service against the gateway, rather than on the gateway machine itself. Microsoft's guide to managing a gateway data source covers how those credentials are added and who can use them.
When you do not need a gateway
A gateway is not always required. It earns its place only when a report needs data that is not in the cloud. If a published report draws solely on cloud-hosted sources, the Power BI service reaches them directly and no gateway is involved.
The two jobs a gateway exists for are clear. The first is scheduled refresh of an Import-mode semantic model that pulls from on-premises data, so the published copy stays current. The second is a live DirectQuery connection from a report to an on-premises source. If a report does neither, it can run quite happily without one.
A useful way to decide: if the data lives on your own network and a published report has to read it, you need a gateway. If the data's already in the cloud, you don't.
Getting data into Power BI is a practical skill worth learning properly Reading about the gateway is a useful start; connecting reports to real data and keeping them refreshed reliably is a skill worth investing in. Our two-day, hands-on Power BI Masterclass covers data sources, refresh and publishing the practical way, working with real reports rather than learning the theory in the abstract. If you are still comparing courses, our guide to choosing Power BI training in the UK sets out what to look for.
