How to create Salesforce ADF Linked Service to connect to a Salesforce Sandbox instance

Sanjay Anantha Ragavan 45

As Per documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-salesforce?tabs=data-factory While creating the Linked service the Environment URL should be in the format https://<domainName>.my.salesforce.com, with this format restriction we would not be able to connect to sandbox environments, could you please help in understanding how to connect to sandbox with the new BULK API 2.0 salesforce ADF connector. If it's a bug/refinement, could you, please help raise a ticket.

phemanth 11,125 Reputation points Microsoft Vendor

2024-01-23T12:45:34.4966667+00:00
@Sanjay Anantha Ragavan

Thanks for reaching MS Q&A

According to the Salesforce documentation, the environment URL for the Salesforce connector in Azure Data Factory should be in the format https://<domainName>.my.salesforce.com. However, this format restriction makes it impossible to connect to sandbox environments.

To connect to a sandbox environment using the new BULK API 2.0 Salesforce ADF connector, you can use the following steps:

In the Linked Service configuration, set the Environment URL to https://test.salesforce.com instead of https://<domainName>.my.salesforce.com.

In the Additional Settings section, set the API Version to v50.0.

Save the changes and test the connection.

These steps should allow you to connect to your Salesforce sandbox environment using the new BULK API 2.0 Salesforce ADF connector. If you continue to experience issues, please refer to the Salesforce documentation or raise a ticket with the Azure support team.

I hope this helps! Let us know if you have any other questions.
Sanjay Anantha Ragavan 45 Reputation points

2024-01-23T13:18:58.16+00:00

Hello Hemanth, Above mentioned format https://test.salesforce.com would still not work, neither will https://test.my.salesforce.com, getting the same error. Will raise a support ticket. Thank you.
Andrew Sullivan 0 Reputation points

2024-01-23T20:17:21.7066667+00:00
I'm experiencing the same issue. As a workaround I was able to do the following (unfortunately not using OAuth):

Go to the Manage tab -> Linked services

Create a Salesforce linked service if you haven't saved one already (enter some placeholders for Environment URL / Client ID / Secret

Click the "Code" button ({ }) next to the linked service and change the "type" from SalesforceV2 to Salesforce and click Apply

That should switch the "Type" to "Salesforce (Legacy)" in the UI and you can then edit the linked service and enter a "sandbox.my.salesforce.com" URL, but unfortunately are forced to use Username/Password/Security Token auth instead of ClientID/Secret
Sanjay Anantha Ragavan 45 Reputation points

2024-01-24T09:23:00.9833333+00:00

Hi Andrew, Though it's a workaround and answers part of my question above, changing the connector to type Salesforce (Legacy) would be using Salesforce BULK API 1.0 which our processes are already on, our other mandated requirement is to leverage Salesforce BULK API 2.0 for large data loads, which is only possible with the latest connector, with the latest version of connector it does not allow the sandbox URL format to be used. Migrating from BULK API 1.0 to 2.0 required various types of testing to performed, and cannot be done directly in production environment, hence the need for Sandbox connectivity.
phemanth 11,125 Reputation points Microsoft Vendor

2024-01-24T11:19:04.3033333+00:00

@Sanjay Anantha Ragavan checking with the internal team will get back to you shortly
Jim McBrayer 5 Reputation points

2024-01-24T21:16:28.74+00:00

Has anyone solved this? We still cannot connect to staging environment.
Jim McBrayer 5 Reputation points

2024-01-24T21:20:05.8933333+00:00

Do we have an answer to this yet? We still cannot connect to Staging environments
Jim McBrayer 5 Reputation points

2024-01-24T23:24:10.4533333+00:00

@phemanth I got it to work by clicking the "Add Dynamic Content" and pasting the staging URL, then hitting "Test connection" However, when I save it, it reverts back to "this url should be formatted as <domain>.my.salesforce.com. It's a front end validation rule.
phemanth 11,125 Reputation points Microsoft Vendor

2024-02-02T15:02:58.8866667+00:00

@Sanjay Anantha Ragavan I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us? In case if you don't have a support plan please let us know here.
Kyle Salata 0 Reputation points

2024-02-26T16:56:33.98+00:00

@phemanth I am having the same issue. "Value should be in the form of https://<domainName>.my.salesforce.com". Is there a workaround for this?
phemanth 11,125 Reputation points Microsoft Vendor

2024-02-29T04:32:58.6766667+00:00

@Kyle Salata Please follow the solution mentioned above. If that doesn't work, you should raise a support ticket for a more thorough investigation.
Sanjay Anantha Ragavan 45 Reputation points

2024-02-29T06:11:45.15+00:00

Hello, Support ticket was raised, the issue has been resolved, Able to connect to sandbox from new Salesforce connector with the GUI. but few workarounds suggested was to edit the JSON configure the environment URL. or create a global variable and use that in the dynamic content.
phemanth 11,125 Reputation points Microsoft Vendor

2024-03-01T07:04:24.7266667+00:00

@Sanjay Anantha Ragavan Glad to know your issue has been resolved. Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others "I'll repost your solution in case you'd like to accept the answer.

Accepted answer

phemanth 11,125 Reputation points Microsoft Vendor

2024-03-01T07:03:36.1966667+00:00

@Sanjay Anantha Ragavan Welcome to Microsoft Q&A platform and thanks for posting your question.

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others "I'll repost your solution in case you'd like to accept the answer.

Ask: As Per documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-salesforce?tabs=data-factory While creating the Linked service the Environment URL should be in the format https://<domainName>.my.salesforce.com, with this format restriction we would not be able to connect to sandbox environments, could you please help in understanding how to connect to sandbox with the new BULK API 2.0 salesforce ADF connector. If it's a bug/refinement, could you, please help raise a ticket.

Solution:. Hello, Support ticket was raised, the issue has been resolved, Able to connect to sandbox from new Salesforce connector with the GUI. but few workarounds suggested was to edit the JSON configure the environment URL. or create a global variable and use that in the dynamic content.

If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.
Sam Rosentel [SFPH] 0 Reputation points

2024-07-24T21:03:53.63+00:00

Able to connect to sandbox from new Salesforce connector with the GUI. but few workarounds suggested was to edit the JSON configure the environment URL. or create a global variable and use that in the dynamic content.

Shouldn't this read "unable to connect to sandbox from new Salesforce connector with the GUI"?

If they were able to connect through the GUI, please let us know how.

If anyone else is trying to parse this, there are two proposed work arounds:

Open the linked connection as code and manually edit the url there. This bypasses the restriction on the url format.

Add the url as a global variable in your pipeline and read it as dynamic content.

Sam Rosentel [SFPH] 0 Reputation points

2024-07-24T21:29:52.6233333+00:00

TLDR: you've got to use dynamic content to get this connector working with a sandbox URL.

Additional info: editing the url in the code directly results in the following error:

Failed to decrypt sub-resource 'None' payload on cloud with error: Failed to decrypt sub-resource payload { "name": "Salesforce_Full", "properties": { "annotations": [], "type": "SalesforceV2", "typeProperties": { "environmentUrl": "", "clientId": "", "apiVersion": "", "authenticationType": "", "encryptedCredential": "********************" } } } and error is: Failed to validate the signature because the content is tampered, the expect context is '{"clientId":"abcd","environmentUrl":"https://domain.my.salesforce.com","dataFactoryName":"df-dev"}' and the runtime context is '{"clientId":"abcd","environmentUrl":"https://domain.sandbox.my.salesforce.com","dataFactoryName":"df-dev"}'.., status code: BadRequest.

The error number links to https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-guide#error-code-9070 which is unhelpful as this code does not appear in the guide.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to create Salesforce ADF Linked Service to connect to a Salesforce Sandbox instance

0 additional answers

Your answer