Salesforce connected App suddenly stopped working

Question

Salesforce connected App suddenly stopped working

Balazs Farkas 25

My salesforce linked service in Azure Synapse stopped working on 4th october around 03:00. Here is the error response:

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 valid scopes defined"}

There were no changes done to the Connected APP on our side, any reason why I am not able to access it now?

Beau Chapell 0 Reputation points

2025-10-06T18:18:02.34+00:00

I am also running into the same issue at the same time. Confirmed on V2 connection refreshed client ID and secret, verified scope for the connection.
Maria Gorie 0 Reputation points

2025-10-07T09:47:29.0666667+00:00

same happened to us. how did you fix this? what scope should we use for the app? is this to be mentioned in the linked service as well, under parameters?

Answer accepted by question author

0 additional answers

Your answer

Beau Chapell 0 Reputation points

2025-10-06T18:18:02.34+00:00

I am also running into the same issue at the same time. Confirmed on V2 connection refreshed client ID and secret, verified scope for the connection.
Maria Gorie 0 Reputation points

2025-10-07T09:47:29.0666667+00:00

same happened to us. how did you fix this? what scope should we use for the app? is this to be mentioned in the linked service as well, under parameters?

Answer 1

Vijaya Kumar Adepu 95

This issue is related to Salesforce’s recent security changes for Connected Apps (rolled out in late September / early October 2025).

The “no valid scopes defined” error means the Connected App does not include the OAuth scopes that your Azure Synapse linked service is requesting.

To fix it:

In Salesforce Setup → App Manager, open your Connected App.

Click Edit.

Under Selected OAuth Scopes, add the following (if not already selected):

✅ Access and manage your data (api)

✅ Perform requests on your behalf at any time (refresh_token, offline_access)

Click Save, wait 2–3 minutes, then re-test your Synapse connection.

If your Connected App uses Client Credentials Flow, make sure that:

“Enable Client Credentials Flow” is checked under Edit Policies, and

A Run-As user is assigned.

After saving, re-run the OAuth request or re-test the Synapse linked service connection.

Balazs Farkas 25 Reputation points

2025-10-07T11:12:28.7633333+00:00

Thanks! This solved the issue for me!
Maria Gorie 0 Reputation points

2025-10-07T11:18:13.3266667+00:00

thanks; I just added only the first scope "Access and manage your data" and the connection was successful. My question is, do I need the "Perform requests on your behalf at any time" scope as well? And will this allow ADF to both read and write data to SF?
Vijaya Kumar Adepu 95 Reputation points

2025-10-07T11:22:12.6833333+00:00

If your Synapse or ADF connection only needs to access Salesforce while it’s actively connected (i.e., during pipeline execution using the current access token), then the single scope “Access and manage your data (api)” is sufficient.

That scope gives full API-level read/write access to Salesforce objects and data, so yes, it allows both reading and writing via the API.

You only need “Perform requests on your behalf at any time (refresh_token, offline_access)” if your integration needs to stay authorized after the initial session expires, for example, if you want Salesforce to issue refresh tokens so ADF/Synapse can reconnect automatically without re-authentication.
Maria Gorie 0 Reputation points

2025-10-07T11:24:02.86+00:00

Thank you, this makes it clear. Thanks a mil.
Jason Zech 0 Reputation points

2025-11-17T15:53:33.59+00:00

This also solved the same problem for me, but I had slightly different wording on the scope I needed to add: "Manage user data via APIs (api)" rather than "Access and manage your data (api)". Worked within a few minutes, though, once I added that.