How to Create a Gateway Cluster in Power BI

If your Power BI reports are refreshing from on-premises data and depend on a single gateway, you're at risk of a single point of failure. A server reboot, a network hiccup, or a required update can bring your entire reporting system to a halt until it's fixed. This article will show you how to eliminate that risk by setting up a high-availability gateway cluster in Power BI. We'll walk you through the entire process, step-by-step, to build a more resilient and reliable data connection for your business.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

What is a Power BI Gateway?

Before diving into clusters, let's quickly review the standard gateway. In simple terms, the Power BI on-premises data gateway acts as a secure bridge. It connects your data that lives inside your company's network (like a SQL Server database, an Analysis Services model, or a local file) to the Power BI Service, which lives in the cloud.

Without this bridge, Power BI can't access your private data to refresh your datasets, meaning your reports quickly become outdated. A single gateway works fine for small-scale operations or development environments. But when critical business decisions rely on those reports being live and accurate, depending on a single gateway machine is a risky proposition.

Understanding Gateway Clusters: Why You Need More Than One

A gateway cluster is simply a group of two or more gateways working together to handle data requests. By creating a cluster, you're immediately upgrading your data infrastructure with two major benefits: high availability and load balancing.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

High Availability (Failover)

This is the primary reason for setting up a cluster. Imagine you have two gateways, A and B, in a cluster. If Gateway A goes offline for any reason - a scheduled Windows update, hardware failure, or an accidental shutdown - Power BI doesn't panic. It sees that Gateway A is unavailable and automatically reroutes all data refresh requests to Gateway B.

Your reports continue to refresh, dashboards update on schedule, and your end-users won't even notice a problem. The single point of failure is gone. As soon as Gateway A comes back online, it will rejoin the cluster and be ready to handle requests again.

Load Balancing

If you have a high volume of data refreshes, a single gateway can get overwhelmed, leading to slow performance and queued jobs. A gateway cluster can distribute this workload across all active gateways.

Instead of one machine doing all the heavy lifting, Power BI will spread the requests evenly among the healthy servers in your cluster. This results in faster refresh times, reduced queuing, and a much smoother experience, especially during peak usage times like the start of the business day when everyone is looking for their updated reports.

Prerequisites for Creating Your Gateway Cluster

Before you get started, you'll need a few things in place to ensure a smooth setup. Running through this checklist first will save you from hitting roadblocks later.

• Admin Permissions: You must be an administrator of the primary gateway you plan to use for the cluster. You'll also need Power BI Service administrator rights or be a Gateway administrator.
• Multiple Machines: You need at least two separate computers (preferably servers) where the gateways can be installed. For true high availability, these should be on different physical or virtual hosts.
• Standard Gateway Installation: You must use the on-premises data gateway (standard mode). The personal mode gateway cannot be used in a cluster.
• Consistent Gateway Version: All gateways within a cluster must be running the same version. It's best practice to always download the latest version from the Power BI website for all installations.
• The Recovery Key: When you installed your first (primary) gateway, you were prompted to save a Recovery Key. You absolutely need this key to add a second gateway to the cluster. If you've lost it, you'll need to restore the primary gateway to generate a new key before proceeding.

Step-by-Step Guide: Creating a Power BI Gateway Cluster

Now, let's walk through the exact steps to create your cluster. This process assumes you already have a single, primary gateway installed and configured on your first machine.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Step 1: Get the Gateway Installer

First, log in to the machine where you want to install your second gateway. Go to the Power BI Service, click the download icon in the top right corner, and select "Data Gateway." Download the latest version of the standard mode gateway installer.

Step 2: Install the Gateway on the Second Machine

Run the installer on your second server. Accept the terms of use and click "Install." The initial installation process is identical to setting up a standalone gateway.

Step 3: Begin the Configuration

Once the installation finishes, the configuration wizard will open. Enter the email address of the administrator account you use for the Power BI service and sign in.

Step 4: Add the New Gateway to an Existing Cluster

This is the most critical step. Instead of registering a new gateway, you will see an option to "Add to an existing gateway cluster." Select this option.

The screen will then show you a list of available gateway clusters that your account manages. Choose the primary gateway cluster you want this new gateway to join.

Step 5: Provide the Recovery Key

You’ll now be prompted to enter the name for this new gateway instance (e.g., "Gateway-Server-02") and, most importantly, the Recovery Key for the cluster. This is the key you saved when you installed the primary gateway. Carefully type or paste it into the field.

Click "Configure" to proceed. The wizard will use the key to encrypt the gateway credentials and securely join the cluster.

Step 6: Verify the Cluster in Power BI Service

Once the configuration is successful, it's time to check your work. Log in to the Power BI Service.

1. Click the Settings gear icon in the top-right corner.
2. Select Manage connections and gateways.
3. On the "On-premises data gateways" tab, you should now see your gateway cluster. Click it to expand the details.
4. You will see both of your gateway instances listed, each with its own online status indicator. Congratulations, your cluster is live!

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

How to Manage Your Gateway Cluster

Your work isn't quite done. Now you need to manage your cluster's behavior, particularly how it handles client requests.

Go to your gateway cluster's settings page (Settings > Manage connections and gateways). At the top, you will see a toggle switch:

<em>Distribute requests across all active gateways in this cluster.</em>

This single setting controls whether you prioritize load balancing or simple failover.

• Setting ON (Recommended): This enables load balancing. Traffic will be distributed evenly to all online gateways in the cluster. This is the best option for performance and high availability. The primary gateway will be used unless it's offline.
• Setting OFF: This puts the cluster in a passive failover mode. All requests will be directed to the primary instance. The second member of the cluster will only take on traffic if the primary goes down. This is useful for disaster recovery scenarios but doesn't improve everyday performance.

You can also manually disable a gateway from the cluster on this management page. This is incredibly useful when you need to perform maintenance or apply updates to one machine without disrupting the entire service. Just toggle the gateway offline, do your work, and then toggle it back on when you're finished. The cluster will handle the traffic shift automatically.

Best Practices for a Healthy Cluster

To keep your reporting pipeline running smoothly, follow these simple best practices for managing your gateway cluster:

• Geographic and Hardware Diversity: Install cluster members on separate physical hardware. If using VMs, make sure they are on different hosts. This protects you from a single hardware failure taking down your entire cluster.
• Regular Updates: Keep all gateway instances updated to the latest version. Microsoft regularly releases performance improvements and security patches. Plan to perform staggered updates, take one member offline, update it, bring it back online, then repeat for the other members.
• Monitor Performance: Keep an eye on the CPU and memory usage of your gateway machines. If they are consistently maxed out, it may be time to scale up the hardware or even add another gateway to the cluster.
• Document Your Recovery Key: Store your recovery key in a secure location like a password manager. If you ever need to restore the cluster or add a new gateway, you will need it. Losing this key can cause a major headache.

Final Thoughts

Setting up a Power BI gateway cluster is a fundamental step toward building a truly professional and reliable business intelligence environment. By moving beyond a single gateway, you create a robust, fault-tolerant system that ensures your critical data refreshes continue uninterrupted, providing better performance and peace of mind.

We understand that connecting data sources, managing infrastructure like gateways, and wrangling different reporting tools can eat up countless hours. That's why we built Graphed . We automate the connection to all your critical marketing and sales platforms - like Google Analytics, Shopify, Facebook Ads, and Salesforce - and let you create real-time dashboards just by asking questions in plain English. There’s no complex setup or maintenance, just instant access to the insights you need.