Where to Install Power BI Gateway?

So you've built a powerful Power BI report connected to data living on a server inside your company's network. The problem? As soon as you publish it to the Power BI service, it becomes a static snapshot. This is where the Power BI Gateway comes in - it’s the secure bridge that lets your cloud-based reports talk to your on-premises data. This guide will walk you through exactly where and how to install the gateway for reliable, high-performance data refreshes.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What is the Power BI Gateway and Why Do You Need It?

Think of the Power BI Gateway as a secure data courier that runs on your local network. When you schedule a data refresh in the Power BI service (the cloud version), the service sends a request down to your gateway. The gateway then queries your local data source (like a SQL Server database), encrypts the results, and securely sends them back up to the Power BI service to update your dataset.

Without a gateway, you simply cannot schedule automatic refreshes for data that lives on-premises. This includes common sources like:

• SQL Server, Oracle, or MySQL databases
• Analysis Services models
• Files (Excel, CSV, etc.) on a local file share
• On-premises SharePoint sites

The gateway is your ticket to keeping cloud dashboards and reports current with the data that powers your business, without manual intervention.

Choosing the Right Gateway: Standard vs. Personal Mode

Before deciding where to install the gateway, you need to decide which one to install. Power BI offers two options, and for nearly all business scenarios, the choice is clear.

Personal Mode

The Personal Mode gateway is designed for a single user. It runs as a regular application, not a background service. This means it only works when you are actively logged into the computer it's installed on. If you log off, shut down, or your laptop goes to sleep, your data refreshes will fail.

Use Personal Mode only if:

• You are the only person who will ever use the connected datasets.
• You are just learning Power BI and doing a proof-of-concept.
• You can guarantee the machine is always on and you are logged in when refreshes happen.

For any serious reporting, especially when a team relies on the data, do not use Personal Mode.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Standard Mode

The Standard Mode Gateway, officially called the "On-premises data gateway," is the enterprise-grade solution. It runs as a Windows Service, meaning it’s always on in the background, even if no one is logged into the machine. This is the crucial difference. It allows multiple users to connect and manage datasets through a single gateway and supports both scheduled refresh and DirectQuery/Live Connection.

Always use Standard Mode for:

• Any reports shared with a team, department, or company.
• Production environments where data reliability is important.
• Connecting data to other services like Power Apps, Power Automate, and Azure Logic Apps.

For the rest of this article, we'll be focusing exclusively on the Standard Mode gateway as it’s the correct choice for practically every business need.

Where Should You Install the Power BI Gateway?

Now for the main event. Choosing the right location for your gateway is critical for performance, reliability, and security. Here are the key rules to follow.

The Golden Rule: Use a Dedicated, Always-On Machine

First and foremost, do not install the gateway on your personal laptop. Laptops get shut down, they hibernate, they connect to different Wi-Fi networks, and they leave the office. A gateway needs a stable, permanent home.

The ideal location is a server that is always running. This could be a physical server in your server room or, more commonly, a Virtual Machine (VM). A VM is often preferred because it's easy to scale its resources (CPU, RAM) if your refresh load increases over time.

Equally important, do not install the gateway on a domain controller. This is a major security risk and is strongly discouraged by Microsoft.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Location, Location, Location: Be Close to Your Data

Network latency is the enemy of fast data refreshes. To minimize it, install the gateway on a machine that has the fastest, most reliable connection to your data sources. For example:

• If your SQL Server is in a data center in Virginia, deploy your gateway on another server or VM within that same Virginia data center.
• Don't install the gateway in your London office if the database it needs to query is hosted in Tokyo. While it might work, the round-trip time for every query will bottleneck your data refreshes.

The gateway itself doesn’t require a super-fast internet connection to talk to the Power BI service, but its connection to the data source needs to be lightning-fast.

Don’t Install it On the Data Source Server (If You Can Avoid It)

While you want the gateway to be close to your data source, you should avoid installing it directly on the same machine (e.g., on the SQL Server itself). The gateway uses CPU and RAM to compress and encrypt data before sending it to the cloud. Running this process on your primary database server can steal resources from the database itself, impacting the performance of other applications that rely on it.

In a small business environment with limited hardware, you might have to install them on the same machine. It's not the end of the world, but it’s not best practice. The ideal setup is Gateway on Server A, Data Source on Server B, both in the same data center.

Hardware and System Requirements

You don't need a supercomputer to run the gateway, but you shouldn't skimp on resources either. Here are the practical recommendations from Microsoft:

• Operating System: Windows Server 2016 or newer (64-bit). You can run it on Windows 10/11, but a server OS is designed for always-on services and is strongly recommended for production.
• .NET Framework: Version 4.7.2 or later is required (the installer will check for you).
• CPU: Minimum of 8 cores.
• RAM: Minimum of 8 GB. This is a floor, not ceiling. If you have many large datasets refreshing concurrently, you will want 16 GB or even 32 GB of RAM to avoid bottlenecks. The gateway can "spool" data to the disk if it runs out of memory, which drastically slows down refreshes. More RAM prevents this.
• Disk: A solid-state drive (SSD) is recommended for the operating system and gateway installation to improve spooling performance if it occurs.

A Quick Guide to Installation & Configuration

The installation itself is straightforward. What's more important is having the right accounts and information ready.

1. Download the Gateway: Get the latest version directly from the Microsoft Power BI Gateway page. Download the Standard Mode.
2. Run the Installer: Launch the installer and select "On-premises data gateway (recommended)."
3. Sign In: You will be prompted to sign in. Use a stable organizational account, preferably a dedicated service account like powerbi-gateway@yourcompany.com rather than your personal named user account. If you leave the company, tying the gateway to your personal account creates huge headaches.
4. Register a New Gateway: Since this is your first one, choose to register a new gateway. Give it a descriptive name that tells you its purpose and location (e.g., PROD-Gateway-EastUS-IT).
5. Create a Recovery Key: This is absolutely critical. The recovery key is the password needed to restore, migrate, or take over your gateway on another machine. You cannot retrieve a lost key. Save this key in a secure password manager like 1Password or LastPass. Treat it like a master password.
6. Verify Network Settings: The gateway communicates with Azure Service Bus over specific outbound ports (TCP 443, 5671, 5672, and 9350-9354). In most corporate networks, these are already open. If your refreshes fail with network errors, this is the first thing to check with your IT/network team.

Once installed, you can manage it from the “Manage connections and gateways” section of the Power BI service online. This is where you will add your specific data sources (e.g., the connection string for your SQL Server) to the gateway itself.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Advanced Topic: Gateways in a Cluster for High Availability

What happens if your gateway machine needs to restart for Windows Updates or suffers hardware failure? All your data refreshes will stop. For mission-critical reports, this isn't acceptable. The solution is a gateway cluster. You can install multiple Standard Mode gateways on different machines and group them into a single logical cluster.

With a cluster:

• Redundancy: If one gateway (the primary) goes offline, requests are automatically routed to a different gateway in the cluster. Your scheduled refreshes will still succeed.
• Load Balancing: For environments with very heavy refresh workloads, Power BI can distribute the traffic across the available gateways, preventing a single machine from becoming a bottleneck.

Setting up a cluster is simple: install a second gateway on a new machine, but during setup, choose to "Add to an existing gateway group" instead of registering a new one, providing the aforementioned recovery key.

Final Thoughts

Choosing where to install your Power BI Gateway boils down to finding a stable, dedicated, and always-on home for it. For rock-solid performance, place it on a server or VM with enough RAM that's as close as possible on the network to your on-premises data sources. This ensures a reliable connection that keeps your business-critical cloud reports refreshed and up-to-date.

While the gateway handles the technical plumbing of connecting Power BI to stubborn on-premise data, it's just one part of the data analysis puzzle. Creating insightful BI dashboards often involves countless clicks, configurations, and a steep learning curve. At our company, we created Graphed to simplify this entire workflow. It lets you connect all your data sources - in the cloud or through spreadsheets - and build entire dashboards just by describing what you want to see in plain English. We turn hours of manual setup into a conversation, so you can spend less time wrangling tools and more time finding insights.