Forum Discussion
Adobe Analytics connector OAuth failure in Power BI Desktop (CSRF / state mismatch)
We are facing an issue with the Adobe Analytics connector in Power BI Desktop (June 2026 version). All users are unable to authenticate when using the connector.
- Steps: - Click Sign in for Adobe Analytics
- Adobe login window opens (adobelogin.com)
- After login attempt, it redirects to: https://oauth.powerbi.com/views/oauthredirect.html - This page loads blank - Then Power BI throws: "The service returned a state value that doesn't match the value that was sent. This might indicate cross-site request forgery."
- Observations: - Issue is affecting all users - Reproducible across machines - Cache and permissions cleared - Adobe API is working fine - Connection works via Power BI Service (web) Conclusion: OAuth redirect is failing in Power BI Desktop (embedded browser), causing authentication failure.
Hi Siva, we didnt do anything it was a problem between Adobe and Microsoft, it is not solved in your side? the only thing that we did special is open a ticket with adobe, but I thought that it will be a global fix.
Sorry I cant help you more.
17 Replies
- Omkar_1712
Solution Specialist
Hello Siva_Kumar_M,
Based on your testing, this does not appear to be an Adobe Analytics configuration issue.
The fact that:
Multiple users are affected
The issue is reproducible across different machines
Adobe authentication itself succeeds
Power BI Service authentication works
The failure occurs during the redirect to oauth.powerbi.com/views/oauthredirect.html
suggests the problem is occurring in the OAuth handshake within Power BI Desktop.
The error: "The service returned a state value that doesn't match the value that was sent"
typically indicates that the OAuth state token generated by Power BI Desktop is not being returned correctly after authentication.
This can happen due to:A regression in the Adobe Analytics connector
Embedded browser/WebView issues in the current Power BI Desktop release
Security software, browser policies, or network devices modifying OAuth redirects or cookies
Changes in Adobe's OAuth implementation that are incompatible with the Desktop connector
As a troubleshooting step, I would suggest:
Testing with an earlier Power BI Desktop version (if available) to determine whether the issue is specific to the June 2026 release.
Checking whether the issue occurs on a machine outside the corporate network (to eliminate proxy/security appliance interference).
Capturing a network trace (Fiddler/Browser Developer Tools) during authentication to identify where the OAuth state value is being lost.
Opening a Microsoft support ticket, as the evidence points toward a connector or OAuth redirect issue within Power BI Desktop rather than an Adobe Analytics configuration problem.
Since Power BI Service continues to authenticate successfully, this further suggests the issue is isolated to the Desktop authentication flow.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community. 
v-menakakotaCommunity Support
Hi Siva_Kumar_M ,
Thanks for reaching out to the Microsoft fabric community forum.Since multiple users are reporting the same behavior with Power BI Desktop (June 2026), this does not appear to be an isolated issue.
If you haven't already, please open a Microsoft Support ticket and include the Power BI Desktop version, the exact error message, and a Frown Snapshot.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
If I misunderstand your needs or you still have problems on it, please feel free to let us know. 
Best Regards,
Community Support Team.- Done v-menakakota, I have raised a Microsoft Support ticket, and below is the response. Please let me know if it works for anyone.
Issue: Adobe Analytics connector OAuth failure in Power BI Desktop (CSRF / state mismatch)
Analysis and Resolution:
We have gone through the issue, but we need few more information, could you please provide the below details:
Was this scenario working with any previous (excluding current version you mentioned june 2026) version of Power BI Desktop? If yes, kindly confirm the version details.
As a test, please install a previous stable version of Power BI Desktop and check if the Adobe Analytics connection works successfully. This will help us identify if the issue is version-specific.
Please sign out completely from Power BI Desktop and restart the application before attempting to sign in again.
Could you confirm which authentication browser environment is being used within Power BI Desktop? Specifically, whether the embedded browser (WebView2) is being used for authentication.
Kindly clear all cached credentials and permissions to remove any stale OAuth tokens or mismatched session state:
Go to File → Options and Settings → Data Source Settings
Select the data source and click Clear Permissions
Retry the sign-in process after clearing the permissions
These steps will help validate whether the issue is related to cached authentication data, Desktop version behavior, or the embedded browser session handling.
Please share the results after performing the above steps so we can proceed with further analysis.
To get a clear understanding of the issue could you please let us know your multiple feasible time and time zone for screen share session to troubleshoot the issue?
Please let us know how would you like to assist on this issue using Teams call or quick assist?
Thank you again for contacting Microsoft Technical support. I would be your point of contact for any kind of issues related to Power BI. You can always reach out to me via email or teams and we would be contacting you as soon as possible to address your issue.
Have a nice day! Stay safe and stay healthy!
JoeH3 mdias drog Omkar_1712- v-menakakota
Hi mperez ,
Thank you for sharing the response from Microsoft Support.As you already have an active support case, please provide the requested information and perform the suggested troubleshooting steps. This will help the support team continue their investigation and assist you in resolving the issue.
Best Regards,
Community Support Team.
My organization is having the same issue. Also tried outside the company network with same results.
I can confirm the same issue at my org. Connection works fine is service, only get the error in desktop.
Any update on this issue? Our issues are identical.
Hello,
Same problema here, in more than 5 desktops that I tried, with de june 2026 version and even with a version from 2021, got the same problem.
I tried it installed by the store, and with the exe file too, and the same results. Clear all caches and connections and nothings work.
In the services is working as the login is going by https://europe.prod.powerquery.microsoft.com/MashupEditor/postMessageOauthStartLogin.html?loginId=.....
But int he desktop it goes by https://oauth.powerbi.com/views/oauthredirect.html or by https://marketing.adobe.com (doesnt response neither)
This was working perfectly 2 weeks ago with the same versions on PowerBI, something must be change in the redirections of the login.Same issue in our organization
Hi all,
Looping in a few experts for visibility, as this appears to be a widespread and recent issue impacting multiple users/tenants, with no confirmed resolution so far:
MFelix Shai_Karmani amitchandak Greg_Deckler parry2k tamerj1 Parchitect GilbertQ danextian om8604 ibarrau
Many people have reported the same problem, and it is still happening even after trying all the steps shared by Microsoft Support (clearing cache, testing different versions, checking authentication).
So this looks more like a system issue in Power BI Desktop OAuth, not something specific to one setup.
If you’ve seen this before or have any idea what could be causing it, or what we should try next, your input would really help.
Thanks in advance!
It is finally working:
mperez could you please share the fix or changes applied? We are currently blocked on this.
Hi Siva, we didnt do anything it was a problem between Adobe and Microsoft, it is not solved in your side? the only thing that we did special is open a ticket with adobe, but I thought that it will be a global fix.
Sorry I cant help you more.
mdias JoeH3 v-menakakota bi_trax87 mperez Hi,
any idea what could be causing it, or what we should try next, your input would really help.
Thanks in advance!
Hi Siva,
It was a problem between Adobe and Microsoft they had to update the certificates they had to comunicate to each other, they could be faster anyway...
Regards
