How to Delete Gateway Cluster in Power BI

Removing a Power BI gateway cluster from your environment is an essential housekeeping task that often gets overlooked. It isn’t just about deleting something old, it's a strategic move to streamline your data management, secure your architecture, and declutter your Power BI Service. This article provides a clear, step-by-step guide to removing a gateway cluster safely and efficiently, ensuring your reports stay live and your data connections stay healthy.

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

First, Why Delete a Gateway Cluster at All?

You might think, "If it's not broken, why fix it?" But letting unused or redundant gateways sit in your Power BI environment can lead to confusion, security vulnerabilities, and management overhead. Knowing when to decommission one is the first step.

Common scenarios for deleting a gateway cluster include:

• Server Decommissioning: The physical machine or virtual server hosting the gateway is being retired. Leaving the associated gateway cluster in Power BI will result in failed refreshes and orphaned data sources.
• Architectural Restructuring: Your organization might be moving from on-premises servers to cloud-based data sources, consolidating data centers, or simply redesigning its data infrastructure. Removing old gateways ensures your Power BI setup mirrors your current architecture.
• Gateway Consolidation: You may have started with several single gateways spread across different departments. As your organization's Power BI usage matures, it's common practice to consolidate these into a single, robust high-availability cluster for easier management and improved reliability.
• General Housekeeping and Security: Every active gateway is a potential bridge between your on-premises network and the cloud. Removing unused gateways reduces your organization's security footprint and makes your environment cleaner and easier to manage for other admins.
• Test or Duplicate Clusters: You may have created a gateway for a temporary project, a training session, or a proof-of-concept. Once these are no longer needed, they should be removed to avoid confusion.

The Pre-Deletion Checklist: What to Do Before You Click "Remove"

"Measure twice, cut once" is the perfect motto here. Casually deleting a gateway cluster without checking its dependencies is a guaranteed way to break reports and dashboards across your organization. Before you remove anything, perform this critical pre-flight check to ensure a smooth transition.

1. Identify All Dependent Reports and Data Sources

You need to know exactly what will be impacted. A single gateway cluster could be feeding data to dozens of reports, dataflows, and semantic models. Finding them is straightforward:

• Sign in to the Power BI Service.
• Click the Settings gear icon in the top-right corner.
• Select Manage connections and gateways.
• Find the gateway cluster you plan to delete and click its name.
• On the gateway cluster details page, you should see a list of all data sources connected to it.

This list is your impact analysis. Review each data source carefully. Visit the workspaces and reports that use these connections to understand the full scope of what you are about to change.

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

2. Communicate With Stakeholders

Data analytics is a team sport. Once you've identified which reports will be affected, reach out to the report owners and key users. Let them know you're making a change to the underlying data infrastructure. Inform them of any potential (even brief) downtime and a specific timeline for the change. Good communication prevents panic and frustrated support tickets.

3. Migrate Your Data Connections to a New Gateway

Don't just delete — migrate. Your goal is to keep reports refreshing without interruption. To do this, you'll need to point the existing data sources to a different, active gateway cluster.

In the Power BI settings, navigate back to your semantic models that are connected to the gateway. For each model:

• Go to the scheduling and credentials section for each affected dataset.
• Open the Gateway connection dropdown menu.
• Select the new, target gateway cluster that should handle the refresh. Power BI may ask you to re-enter credentials for the data source to establish the new path.
• Run a manual refresh to test the new connection and ensure everything works correctly.

Only after you've successfully migrated all dependent data sources and tested them should you proceed with deleting the old cluster.

4. Backup Your Configuration (Just in Case)

While you won't need a formal backup file, it's wise to take a few screenshots of the gateway cluster’s settings and its associated data source configurations. This includes server names, database names, and any specific authentication details. If anything goes unexpectedly wrong, this documentation can save you a lot of time troubleshooting or recreating connections.

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

How to Delete a Power BI Gateway Cluster: The Step-by-Step Process

An interesting quirk of Power BI is that you don't actually delete a "cluster." Instead, a cluster is defined by its members. You remove all the individual gateways from the cluster, and once the last gateway is gone, the cluster effectively dissolves and disappears from the interface.

Heads up: To remove a gateway from a cluster, the gateway service must be running and online. Power BI needs to be able to communicate with the member to successfully remove it.

Here’s how to do it:

Step 1: Navigate to the Gateway Management Area

Log in to your Power BI Service account. Click the Settings gear icon in the upper-right corner and choose Manage connections and gateways.

Step 2: Select the Target Gateway Cluster

On the "On-premises data gateways" tab, you'll see a list of all clusters. Click on the name of the cluster you wish to remove.

Step 3: Remove Each Gateway Member Individually

Inside the cluster details page, you will see the individual gateways that make up the cluster underneath the Status section. For each gateway member:

• Check the box next to the gateway's name.
• Click the Remove button that appears at the top of the list.
• A confirmation prompt will appear, warning you that this action cannot be undone. Confirm the removal.

Repeat this process for every gateway in the cluster. Once the final member is removed, the cluster itself will vanish from your list. That's it! The cluster is gone from the Power BI Service.

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

Final Cleanup Step: Uninstalling the On-Premises Software

Removing the cluster from the Power BI Service doesn't remove the gateway software from your server. For security and system hygiene, you should complete the process by uninstalling the application from the source machine.

• Log into the server where the gateway software is installed (via Remote Desktop or direct access).
• Open the Control Panel.
• Go to Programs and Features (or "Add or Remove Programs" on older Windows versions).
• Find On-premises data gateway in the list of installed applications.
• Select it, and click Uninstall.
• Follow the on-screen prompts to complete the uninstallation.

Repeat this on every server that was part of the deleted cluster.

Troubleshooting Common Problems

Things don't always go according to plan. Here are a few common issues and how to resolve them:

• The "Remove" Button is Grayed Out: This almost always means you are not an administrator of that specific gateway. You need to be assigned the "Admin" role for each gateway member to remove it. Contact the current admin to either get permissions or have them perform the removal.
• A Gateway Member is Offline: You cannot remove an offline gateway from a cluster through the Power BI Service. The most common fix is to get the server back online so the gateway service starts running again. If the server is permanently destroyed and cannot be brought back online, you'll have to use more advanced methods involving PowerShell scripts executed by a Power Platform or Global Admin to forcefully remove the orphaned entry.
• Error Message About Active Dependencies: If you get an error saying the gateway is still in use, it means you missed a dependency during your pre-flight check. Go back through your data source settings for all workspaces and make sure every connection has been remapped to a new gateway.

Final Thoughts

Deleting a Power BI gateway cluster isn't difficult, but it does require careful planning. By following a clear process — auditing dependencies, migrating connections, removing each gateway piece by piece, and finally uninstalling the software — you can confidently clean up your Power BI environment and ensure your data infrastructure remains efficient and secure.

We know that managing data gateways and on-premises infrastructure is often just one piece of a larger data puzzle. Much of the pain comes from trying to stitch together reports from scattered cloud platforms like Shopify, Google Ads, Salesforce, and Facebook Ads. As we've worked to eliminate reporting busywork, we've found that giving teams the ability to connect to these cloud sources without any technical hassle is a game changer. We built Graphed to do exactly that, letting you connect all of your marketing and sales apps with a few clicks and build real-time dashboards by simply describing what you want in plain English. It automates the entire reporting pipeline, giving you back time to focus on analyzing the insights, not just chasing down the data.