Forum Discussion
Power BI Desktop sign-in authentication error
Hello,
I am unable to sign in to Power BI Desktop.
Error: "We couldn't authenticate your sign-in request"
My system:
- Windows 11 Home Single Language
- Power BI Desktop (latest version)
- Using Outlook account
I tried:
- Retry without Web Account Manager
- Cleared TokenBroker cache
- Removed credentials from Credential Manager
- Restarted laptop
- Enabled default browser sign-in
Still facing the issue.
Please help me fix this.
Thank you.
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
4 Replies
- Ritaf1983
Super User
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
Hi Vishaladata63 ,
Thank you Ritaf1983 for the response provided!
Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Thank you.Hi Vishaladata63 ,
I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.
Thank you.
- MohdZaid_
Hey Vishaladata63 ,
If you're seeing the error “We couldn't authenticate your sign-in request” in Power BI Desktop even after clearing cache and credentials, the issue is usually related to Web Account Manager (WAM), browser authentication settings, or account type restrictions.
Since you're using Windows 11 Home and an Outlook (personal) account, first confirm that you're signing in with a work or school account, not a personal Microsoft account. Power BI Service does not support personal Outlook/Hotmail accounts for sign-in it requires an organizational (Azure AD / Entra ID) account.
If you are using a work account, try these additional steps:
- Completely uninstall Power BI Desktop, then reinstall the latest version directly from Microsoft (not the Microsoft Store version).
- Go to Settings → Accounts → Access work or school, and remove any stale work accounts, then re-add your account.
- Ensure Internet Explorer mode / Edge WebView2 runtime is installed and updated (Power BI relies on WebView2 for authentication).
- Temporarily disable VPN, proxy, or antivirus to rule out network blocking.
- Check system date/time is correct and set automatically.
If the issue still persists after reinstalling and confirming you’re using a work account, it’s most likely a tenant-level authentication policy or Conditional Access restriction, and your Microsoft 365 admin may need to review sign-in logs in Entra ID.
In most cases, this error happens because a personal Outlook account is being used instead of a work or school account, so I’d verify that first.
If this explanation helped, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.
Thanks for being part of the discussion!
