Power Platform Community Forum Thread Details

Good day!

I would like to ask some advice regarding how our power automate citizen developers authenticate to salesforce via the salesforce connector.

Currently users log in with their username and passwords to establish a connection to salesforce.

We would like to introduce the new method of creating a connection to salesforce via the new authentication type: Microsoft Entra ID (SSO), however, I cannot seem to find meaningful articles to properly set this up.

We have app registrations already configured for SSO into salesforce for normal users (SAML), but we are really struggling to get this to work for power automate.

We already have an external client app ready in salesforce with a token exchange handler and an associated apexclass to decode the tokens etc.

My instance URL is correct as well as my salesforce external client app

It seems like we cannot even debug it, since it does not enter salesforce at all.

Can anyone please provide some guidance regarding this issue?

It seems like it should be a easy problem to fix.

I know this is vague, and I apologize in advance. I dont even know where to start looking for the issue.

Appreciate some help or insight in advance!

Thanks so much

Categories:

Using connectors

Since the request never reaches Salesforce, the issue is most likely occurring before the token exchange, either within the Power Automate connector configuration or during Microsoft Entra ID authentication. I would start by checking the Microsoft Entra sign-in logs. If there is no sign-in attempt, the connector is failing before authentication begins. If Entra logs show a successful sign-in but Salesforce logs remain empty, the issue is likely related to the External Client App or OAuth token exchange configuration.

Given that this authentication mode is relatively new, if all configuration appears correct and no diagnostic logs indicate the cause, it would be worthwhile opening a Microsoft support case. They can inspect connector-side logs that aren't available to customers and determine whether the issue is due to configuration or a connector limitation.