Forum Discussion
Power BI Desktop sign-in authentication error
The "We couldn't authenticate your sign-in request" error in Power BI Desktop is typically caused by a conflict between the Windows Web Account Manager (WAM) and the Power BI authentication stack. Since you have already tried the standard cache clearing and credential removal, follow these advanced steps to resolve the issue.
### 1. Force Browser-Based Authentication
Sometimes the internal Power BI sign-in window fails to communicate with the Windows identity provider.
* Open Power BI Desktop and go to **File** > **Options and settings** > **Options**.
* Under the **Global** tab, select **Security**.
* Check the box for **"Use my default web browser"**.
* Close Power BI Desktop and ensure no background processes are running in the Task Manager before trying to sign in again.### 2. Disable WAM via Registry
If the standard fix fails, you may need to prevent Windows from overriding the authentication protocol with WAM.
* Press **Windows + R**, type `regedit`, and hit Enter.
* Navigate to the following path:
`HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity`
* Right-click in the right pane, select **New** > **DWORD (32-bit) Value**.
* Name it `DisableADALatopWAMOverride` and set its value to **1**.
* Create another DWORD named `DisableAADWAM` and set its value to **1**.
* Restart your laptop and attempt to sign in.### 3. Check Windows Account Association
In Windows 11 Home, account conflicts often occur if the account is partially registered in the system settings but not fully authorized.
* Go to **Windows Settings** > **Accounts** > **Access work or school**.
* If your Outlook/Microsoft account appears there, select it and click **Disconnect**.
* Restart Power BI and try to sign in. When the Windows "Stay signed in to all your apps" prompt appears, click **"No, sign in to this app only"**.### 4. Switch Installation Source
The Microsoft Store version and the standalone MSI installer handle permissions differently.
* If you are currently using the version from the **Microsoft Store**, uninstall it and download the **MSI installer** directly from the Microsoft Power BI website (or vice versa). Switching the installation type often bypasses local environment authentication blocks.
### 5. Verify TLS Protocols
Power BI requires TLS 1.2 for secure communication with Azure Active Directory.
* Open **Control Panel** > **Internet Options** > **Advanced**.
* Scroll down to the security section and ensure **"Use TLS 1.2"** is checked. If it is disabled, the authentication request will be rejected by the server.If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Super UserThe "We couldn't authenticate your sign-in request" error in Power BI Desktop is typically caused by a conflict between the Windows Web Account Manager (WAM) and the Power BI authentication stack. Since you have already tried the standard cache clearing and credential removal, follow these advanced steps to resolve the issue.
### 1. Force Browser-Based Authentication
Sometimes the internal Power BI sign-in window fails to communicate with the Windows identity provider.
* Open Power BI Desktop and go to **File** > **Options and settings** > **Options**.
* Under the **Global** tab, select **Security**.
* Check the box for **"Use my default web browser"**.
* Close Power BI Desktop and ensure no background processes are running in the Task Manager before trying to sign in again.
### 2. Disable WAM via Registry
If the standard fix fails, you may need to prevent Windows from overriding the authentication protocol with WAM.
* Press **Windows + R**, type `regedit`, and hit Enter.
* Navigate to the following path:
`HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity`
* Right-click in the right pane, select **New** > **DWORD (32-bit) Value**.
* Name it `DisableADALatopWAMOverride` and set its value to **1**.
* Create another DWORD named `DisableAADWAM` and set its value to **1**.
* Restart your laptop and attempt to sign in.
### 3. Check Windows Account Association
In Windows 11 Home, account conflicts often occur if the account is partially registered in the system settings but not fully authorized.
* Go to **Windows Settings** > **Accounts** > **Access work or school**.
* If your Outlook/Microsoft account appears there, select it and click **Disconnect**.
* Restart Power BI and try to sign in. When the Windows "Stay signed in to all your apps" prompt appears, click **"No, sign in to this app only"**.
### 4. Switch Installation Source
The Microsoft Store version and the standalone MSI installer handle permissions differently.
* If you are currently using the version from the **Microsoft Store**, uninstall it and download the **MSI installer** directly from the Microsoft Power BI website (or vice versa). Switching the installation type often bypasses local environment authentication blocks.
### 5. Verify TLS Protocols
Power BI requires TLS 1.2 for secure communication with Azure Active Directory.
* Open **Control Panel** > **Internet Options** > **Advanced**.
* Scroll down to the security section and ensure **"Use TLS 1.2"** is checked. If it is disabled, the authentication request will be rejected by the server.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly