Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
Hi Phemant,
Kindly guide me on what should we put on the call back URL?
and is it the same URL to be use for the Environment URL?
Salesforce connection failed in ADF due to authentication failure
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 68%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMN%3C/text%3E%3C/svg%3E)
Mazlan, Noor
0
Reputation points
Hi support team,
I am creating a new connection Salesforce to our Sandbox Salesforce in ADF Linked Services using the Salesforce connector V2.
But we are facing an error of :-
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":"authentication failure"}
This is the details that am using for my connection:-
- Environment URL : https://jdep--slsvonage.sandbox.my.salesforce.com
- Client ID
- Client Secret
- Salesforce API Version: 54.0
We have setup the Connected App on the Salesforce side as turning on whatever being told on the manual for the setup connected app in Salesforce.
Can you help to guide us what went wrong?
Azure Data Factory
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous2025-03-27T06:01:02.2266667+00:00 It looks like you're encountering an authentication issue while trying to connect Salesforce to Azure Data Factory (ADF).
The error message
{"error":"invalid_grant","error_description":"authentication failure"}typically indicates an issue with the authentication credentials or the OAuth flow.Please check the below steps and confirm us if issue persists:
- Ensure that the Client ID and Client Secret you are using are correct and match the ones generated in Salesforce for your Connected App.
- Make sure that the OAuth settings in your Connected App are correctly configured. This includes ensuring that the callback URL is correctly set and that the necessary OAuth scopes are enabled.
- Sometimes, the tokens might expire or become invalid. Try regenerating the tokens and updating them in your ADF configuration.
- Ensure that the user associated with the Client ID has the necessary permissions to access the Salesforce API.
- Confirm that the API version you are using (54.0) is supported and correctly configured in both Salesforce and ADF.
- Double-check the environment URL to ensure it is correct and accessible. please refer the link; https://help.salesforce.com/s/articleView?id=xcloud.remoteaccess_oauth_flow_errors.htm&type=5
Hope this helps. Do let us know if you any further queries.
-
Mazlan, Noor 0 Reputation points
2025-03-27T06:07:08.4333333+00:00 Hi Phemant,
Kindly guide me on what should we put on the call back URL?
and is it the same URL to be use for the Environment URL?
-
Anonymous
2025-03-27T06:24:58.6566667+00:00 The callback URL in Salesforce is the endpoint that Salesforce calls back to your application during the OAuth flow.
Callback URL: This URL is typically the one that a user’s browser is redirected to after successful authorization. It must be a secure URL (using HTTPS) and should be accessible from the internet. For example, if your application is hosted at
https://myapp.example.com, your callback URL might be something likehttps://myapp.example.com/oauth/callbackEnvironment URL: This is the URL of your Salesforce environment (e.g., your Salesforce sandbox or production instance). It is different from the callback URL. In your case, the environment URL is
https://jdep--slsvonage.sandbox.my.salesforce.com.refer :https://help.salesforce.com/s/articleView?id=xcloud.connected_app_create_api_integration.htm&type=5
To summarize:
- Callback URL: The URL where Salesforce will redirect the user after authorization (e.g.,
https://myapp.example.com/oauth/callback). - Environment URL: The URL of your Salesforce instance (e.g.,
https://jdep--slsvonage.sandbox.my.salesforce.com).
Make sure to configure the callback URL in your Salesforce Connected App settings and use the correct environment URL in your ADF configuration
- Callback URL: The URL where Salesforce will redirect the user after authorization (e.g.,
-
Anonymous
2025-03-28T05:51:29.5966667+00:00 @Mazlan, Noor We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
-
Anonymous
2025-03-31T03:24:45.76+00:00 Check the below additional troubleshooting steps which you might missed.
- Use the Correct Token Endpoint:
- Ensure that the token request is going to the correct endpoint: For Sandbox:
https://test.salesforce.com/services/oauth2/tokenFor Production:https://login.salesforce.com/services/oauth2/token - If you're using the full instance URL (
https://jdep--slsvonage.sandbox.my.salesforce.com), try switching tohttps://test.salesforce.com.
- Ensure that the token request is going to the correct endpoint: For Sandbox:
- Check Salesforce Connected App Login Restrictions:
- Go to Setup → Connected Apps OAuth Usage and check if the app is being blocked.
- In the Connected App settings, change Permitted Users to
All users may self-authorize.
- Whitelist ADF IPs (If IP Restrictions Exist):
- If your Salesforce org enforces IP Whitelisting, ensure that Azure Data Factory’s IP ranges are added under Setup → Network Access.
- Check ADF Logs for More Details:
- Run a Test Connection and check the exact error response.
- Sometimes, the issue is a missing
refresh_tokendue to improper OAuth settings.
- Confirm Authentication Flow (Password vs. Refresh Token Flow):
- If you're using the username-password OAuth flow, ensure that the security token is appended to the password (unless the org uses IP whitelisting).
- If using the OAuth 2.0 refresh token flow, confirm that
offline_accessis enabled.
- Manually Test Authentication Using Postman or Curl:
- Try sending a manual authentication request using Postman or
curlto confirm if the issue is with ADF or Salesforce configuration.
- Try sending a manual authentication request using Postman or
Hope this helps. Do let us know if you any further queries.
- Use the Correct Token Endpoint:
-
Anonymous
2025-03-31T09:33:37.8666667+00:00 @Mazlan, Noor We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Sign in to comment