Forum Discussion

Elina_Mirin's avatar
Elina_Mirin
Icon for Advocate II rankAdvocate II
10 months ago
Solved

Powwer BI Desktop - Salesforce connector error

Hello! I am facing some issue with the Salesforce connector in Power BI Desktop. It gives me this error: "We can't log you in because of an issue with single sign-on. Contact your Salesforce admin for help." I didn't have any issue with the SFDC connector and sign in until 2-3 days ago. Anyone has any idea what is happening?

 

  • Hi Elina_Mirin ,

    This issue might be caused by Salesforce’s recent MFA or SSO enforcement or expired cached credentials in Power BI Desktop application. Please check the below points :

    1. Expired or Invalid Cached Credentials

    Go to Power BI Desktop then→ File → Options and settings → Data source settings

    Select your Salesforce connection → Clear Permissions → Close & Reconnect Again

    Then again try using salesforce creds.

    1. MFA or SSO Policy Change in Salesforce

    Salesforce enforces Multi-Factor Authentication (MFA) and SSO token requirements time to time.

    Check with Salesforce admin to confirm whether SSO settings or Connected App permissions were updated or not.

     The Power BI connector must be whitelisted as a trusted connected application.

    1. Power BI Connector Update

    Microsoft has updated several OAuth connectors (including Salesforce).

    Please update the latest Power BI Desktop version.

    Then remove and re-add the Salesforce connection.

     

    🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

    💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

    🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

    🔗 Curious to explore more? [Discover here].

    Let’s keep building smarter solutions together!

     

6 Replies

  • Hi Elina_Mirin ,

    This issue might be caused by Salesforce’s recent MFA or SSO enforcement or expired cached credentials in Power BI Desktop application. Please check the below points :

    1. Expired or Invalid Cached Credentials

    Go to Power BI Desktop then→ File → Options and settings → Data source settings

    Select your Salesforce connection → Clear Permissions → Close & Reconnect Again

    Then again try using salesforce creds.

    1. MFA or SSO Policy Change in Salesforce

    Salesforce enforces Multi-Factor Authentication (MFA) and SSO token requirements time to time.

    Check with Salesforce admin to confirm whether SSO settings or Connected App permissions were updated or not.

     The Power BI connector must be whitelisted as a trusted connected application.

    1. Power BI Connector Update

    Microsoft has updated several OAuth connectors (including Salesforce).

    Please update the latest Power BI Desktop version.

    Then remove and re-add the Salesforce connection.

     

    🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

    💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

    🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

    🔗 Curious to explore more? [Discover here].

    Let’s keep building smarter solutions together!

     

    • Elina_Mirin's avatar
      Elina_Mirin
      Icon for Advocate II rankAdvocate II

      grazitti_sapna thank you for your detailed message - I  really appreciate it. I have tried 1 and 3 and the issue still persist. Now I am trying to get in touch with a Salesforce admin to confirm point 2.

       

      cc: v-ssriganesh 

      • v-ssriganesh's avatar
        v-ssriganesh
        Icon for Community Support rankCommunity Support

        Hello Elina_Mirin,

        Hope everything’s going great with you. Just checking in has the issue been resolved or are you still running into problems? Sharing an update can really help others facing the same thing.

        Thank you.

  • v-ssriganesh's avatar
    v-ssriganesh
    Icon for Community Support rankCommunity Support

    Hi Elina_Mirin,

    Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to grazitti_sapna for sharing valuable insights.

     

    Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

     

    Thank you for being part of the Microsoft Fabric Community.

  • Hi Elina_Mirin 

     

    If you're still stuck after the Salesforce admin checks, this kind of "single sign-on" error tends to come back periodically with the native connector - every time Salesforce tightens MFA/SSO policies or rotates Connected App permissions, the OAuth flow can break for whole tenants at once. Frustrating, especially when nothing changed on your side.

     

    Worth knowing about as a fallback - there's an app on Salesforce AppExchange called Power BI Connector for Salesforce that uses its own Connected App on the Salesforce side, so it's not affected by the same SSO/Connected App resets that hit the native connector:

     

    🔗 AppExchange listing: https://appexchange.salesforce.com/appxListingDetail?listingId=31526f0e-abd8-4cb5-bd1a-3bd56b5c0577

    A few things relevant to this exact pain point:

    Happy to set up a quick demo if it's useful — we can walk through the SSO-independent setup and how to migrate existing reports. Just reach out via the support link.

     

    Cheers,

    Metrica team

    • Elina_Mirin's avatar
      Elina_Mirin
      Icon for Advocate II rankAdvocate II

      Hi, metrica! Thank you for your message! I have resolved this issue with the SFDC admin team - the issue was that when trying to login into Power BI Desktop, my contractor credentials were overlapping with my client's account credentials. So even though I logged in with my client's credentials, somewhere in the backend it was reading my contractor's credentials.