Unable to create new linked service for salesforce. As it changed from username password to Client ID and Client secret

Question

Unable to establish connection to the Salesforce environment using provided client id and client secret, please verify the details. Error message: {"error":"invalid_grant","error_description":"no client credentials user enabled"}

Answer 1

@Manikanta Naluvala - Thanks for the question and using MS Q&A platform.

It seems like you are having trouble creating a new linked service for Salesforce in Azure Data Factory. I understand that Salesforce has changed its authentication method from username and password to client ID and client secret. The error message you received indicates that there is an issue with the client credentials you provided.

To resolve this issue, please follow the steps below:

• Make sure that you have created a connected app in Salesforce and obtained the client ID and client secret. If you have not done so, please follow the instructions in this Salesforce documentation to create a connected app.

• In Azure Data Factory, create a new linked service for Salesforce.
• Configure the service details, test the connection, and create the new linked service.Enter the client ID and client secret that you obtained from Salesforce in the corresponding fields and save the linked service and test the connection.

• The following properties are supported for the Salesforce linked service.

For more details, refer to Copy data from and to Salesforce using Azure Data Factory or Azure Synapse Analytics.

If you are still unable to establish a connection, please double-check that the client ID and client secret are correct and that the connected app has the necessary permissions to access the Salesforce environment. If you continue to experience issues, please let me know and I will do my best to assist you further.

Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

I believe this issue is related to the use of "OAuth 2.0 Username-Password" in salesforce backend, if we move it to "OAuth 2.0 Client Credentials". That should solve the issue. Kindly reach out to relevant salesforce teams in your org.

Answer 3

Be sure to assign a user to the correct "Run As" field on the connected app in Salesforce. My issue was that I added the user to the first "Run As" field I saw and it was for Custom Connected App Handler when it is supposed to be the one for Client Credentials Flow. :-)