How to Get Recovery Key for Power BI Gateway

Locked out of your Power BI on-premises data gateway and need to restore it? Discovering you don't have the recovery key can feel like a major roadblock, but it's a fixable problem. This guide will walk you through exactly what the recovery key is, how to get a new one if you've lost it, and the steps to get your data flowing again.

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 the Power BI Gateway Recovery Key?

Before diving into the fix, it's helpful to understand what you're dealing with. The on-premises data gateway acts as a secure bridge, connecting your data sources that live on your company's network (like a local SQL Server) to cloud services like Power BI, Power Apps, and Azure Logic Apps.

When you first set up the gateway, you were prompted to create a Recovery Key. This key is essentially a master password for your gateway instance. It encrypts the credentials you use for your data sources, and Microsoft does not store this key. This is a security measure to ensure only you can access your encrypted data source connections.

You need this key for three critical actions:

• Restoring a Gateway: If the machine your gateway is on fails, you can reinstall the gateway on a new machine and use the recovery key to restore all of your existing connections without re-entering credentials for every single one.
• Migrating a Gateway: Similar to a restore, you can use the key to move your gateway from one machine to another.
• Taking Over a Gateway: If the original gateway administrator leaves the company, a new admin can take ownership of the gateway using the recovery key.

Essentially, it’s your main tool for disaster recovery. So, what happens when it goes missing?

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

What to Do When Your Recovery Key is Lost

Let's get the bad news out of the way first: you cannot recover a lost key. Since Microsoft doesn't store it, there's no "Forgot My Password" link to click. It’s designed to be unrecoverable for security purposes.

The good news is that you don't have to start your entire Power BI setup from scratch. The solution involves creating a totally new Gateway configuration, which will generate a new recovery key. This means you will have to uninstall the old gateway and reinstall it. While it sounds drastic, it's a straightforward process if you follow a plan.

Step-by-Step: Generating a New Key by Reinstalling the Gateway

To get a new key, you need to treat this as a fresh installation. This process will cause a temporary interruption in data refreshes, so it's best to perform these steps during a low-traffic period if possible.

Step 1: Document Your Current Setup

Before you uninstall anything, you need to know what you're rebuilding. Since you can't restore the old configuration without the key, you'll have to manually re-create your data source connections in the new gateway.

Go to the Power BI Service:

1. Click the Settings gear icon in the top right corner.
2. Select Manage connections and gateways.
3. Click on the On-premises data gateways tab.
4. Select the gateway you need to replace.
5. Take screenshots or detailed notes of every data source listed. You'll need the server names, database names, and authentication methods. You should also check which reports rely on these connections.

Documenting first transforms the process from a potential mess into a simple checklist exercise.

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 2: Uninstall the Old Gateway

Now, log in to the Windows machine or server where the gateway software is currently installed.

1. Open the Control Panel or go to Settings > Apps.
2. Find "On-premises data gateway" in the list of installed programs.
3. Click Uninstall and follow the prompts to remove the software completely.

This breaks the connection with the Power BI service, but that's what we want. The old, inaccessible gateway is now gone from your machine.

Step 3: Download and Install the New Gateway

Head back to the Power BI service to get the latest installer.

1. Click the Download icon (a downward arrow) in the top-right menu of the Power BI service.
2. Select Data Gateway.
3. Download the recommended standard mode gateway and run the GatewayInstall.exe file on your server.
4. Follow the on-screen prompts for the setup. Accept the terms and installation path.

Step 4: Register the Gateway and Create Your New Key

This is the most important part. During the installation process, you'll be prompted to configure the gateway.

1. First, sign in with the same Power BI account you used previously.
2. You'll be presented with two options: 'Register a new gateway on this computer' or 'Migrate, restore, or take over an existing gateway'. Since you don't have the old key, you must select Register a new gateway...
3. Give your new gateway a name. It’s a good practice to use a slightly different name than the old one to avoid confusion.
4. You’ll then be asked to create and confirm a new Recovery Key. This is your chance to start fresh. Create a strong, unique key.

Step 5: SAVE Your New Recovery Key!

Do not skip this. The moment you create the key, save it somewhere secure but accessible to your team. Don't repeat the original mistake. The best places to store it include:

• A team password manager like 1Password or Bitwarden.
• A secure, shared company vault or documentation space like Confluence or SharePoint, with limited access.

Do not save it in a text file on your desktop. Write it down, email it to your work account for safe-keeping — do whatever you need to do to make sure you won't lose it this time.

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

Step 6: Re-Create Your Data Source Connections

With the new gateway installed and registered, it will appear in the "Manage connections and gateways" section of the Power BI service. Now you need to hook it up to your data.

1. Select your new gateway.
2. Click the + New button to start adding your data sources.
3. Refer to the notes and screenshots you took in Step 1. Re-create each data source connection one by one, entering the server details and credentials for each.
4. Once your data sources are created, you need to go to your Datasets and map them to the new gateway source. Open the settings of each dataset that was using the old gateway and under the "Gateway connection" section, map it to the newly created source.

After re-linking your datasets, trigger a manual refresh on a report to confirm that everything is working correctly.

Best Practices for Managing Your Power BI Gateway Key

To avoid this situation in the future, adopt these simple habits:

• Centralize and Secure Key Storage: Store the key in a shared, secure location where key personnel can find it. A team password manager is ideal for this.
• Document the Owner: Your documentation should not only include the key but also who the primary admin for the gateway is. This clarifies responsibility.
• Perform Recovery Drills: For larger organizations, having a simple disaster recovery plan is wise. Once a year, you could practice migrating or restoring a gateway in a test environment to ensure the process works and your key is accessible.

Final Thoughts

Forgetting or losing your Power BI Gateway recovery key is a common hiccup, but it's not a disaster. Although you can't retrieve a lost key, you can always generate a new one by reinstalling the gateway and diligently re-configuring your data sources. The key takeaway is that prevention through proper documentation and storage is always the best strategy.

Troubleshooting intricate setups like gateways often serves as a reminder of the inherent friction in traditional business intelligence workflows. At Graphed we aim to eliminate this complexity. Instead of wrestling with on-premises connectors and manual configurations, we connect seamlessly to your cloud data sources like Shopify, Google Analytics, and Hubspot, allowing you to build real-time dashboards just by asking questions in plain English. We believe you should spend your time acting on insights, not managing infrastructure.