ADF - Salesforce Linked Service - difference between SalesforceV2 & SalesforceServiceCloudV2

Question

ADF - Salesforce Linked Service - difference between SalesforceV2 & SalesforceServiceCloudV2

Fatehah L 30

Hello,

In ADF when choosing Salesforce data store there are two options : SalesforceV2 & SalesforceServiceCloudV2. Currently we built our ADF pipeline using the SalesforceV2.

User's image

I am under the impression that the SalesforceV2 is for general objects, while SalesforceService is for Service-specific.

When connecting to the same Salesforce server instance, I found some objects are only available when using the SalesforceService connector, and not the SalesforceV2 (e.g. 'Asset' and 'Order').

Additionally, I also found that all the other tables/objects that are available using the SalesforceV2 connector, are also available when using SalesforceService Connector ('Opportunity', 'SalesAgreement', '__c' custom objects etc.)

Can anyone help point out the difference between the two, and if it is safe for us to change our pipeline to use SalesforceServiceCloudV2 instead? (since all objects are also available there)

I tried searching Microsoft articles on them and found below, but seems like these 2 articles are almost exact copy of each other.

https://dori-uw-1.kuma-moon.com/en-us/azure/data-factory/connector-salesforce?tabs=data-factory

https://dori-uw-1.kuma-moon.com/en-us/azure/data-factory/connector-salesforce-service-cloud?tabs=data-factory

I did ask the Salesforce developer from our side, and he mentioned that it shouldn't matter which connector to use, as long as the connector can give access to all the objects we need.

Thank you in advance!

SAI JAGADEESH KUDIPUDI 1,750 Microsoft External Staff Moderator

Hi Fatehah L,
In Azure Data Factory (ADF), both SalesforceV2 and SalesforceServiceCloudV2 connectors are used to copy data from Salesforce using the Salesforce Bulk API 2.0.

As per Microsoft documentation:

The SalesforceV2 connector uses Bulk API 2.0 to query and ingest data
The SalesforceServiceCloudV2 connector also uses Bulk API 2.0 for data operations

This confirms that both connectors use the same underlying API mechanism for data movement.

Difference Between SalesforceV2 and SalesforceServiceCloudV2

Feature	SalesforceV2	SalesforceServiceCloudV2
Feature	SalesforceV2	SalesforceServiceCloudV2
Intended use	General Salesforce (Sales Cloud + custom objects)	Optimized for Service Cloud scenarios
Object visibility	Limited (based on standard API discovery)	Broader (includes additional objects like Asset, Order)
API behavior	Standard object discovery	Extended metadata projection
Coverage	May miss some standard objects	Superset of SalesforceV2 in most cases

Regarding Missing Objects (e.g., Asset, Order)
Microsoft documentation does not mention any connector-level limitation where certain standard Salesforce objects are unavailable in SalesforceV2.

If objects like Asset or Order are visible only when using SalesforceServiceCloudV2, it may depend on:

Salesforce API permissions
Object-level security
Connected App configuration
Metadata exposure in the Salesforce org

Since both connectors:

Use the same Bulk API 2.0
Support SOQL queries
Support the same Salesforce editions

You can safely switch from SalesforceV2 to SalesforceServiceCloudV2 after validating your pipeline (schema & access).
Official Microsoft Documentation

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

1 answer

Your answer

Answer 1

SalesforceV2 and SalesforceServiceCloudV2 are two separate connectors that target different Salesforce products but share the same underlying technical model in Azure Data Factory.

From the documentation:

SalesforceV2
- type must be SalesforceV2.
- Connects to a Salesforce instance (Sales Cloud/standard Salesforce org).
- Uses OAuth2 client credentials against a Salesforce Connected App (clientId, clientSecret).
- Requires environmentUrl (for example https://<domainName>.my.salesforce.com).
- Requires an apiVersion for Bulk API 2.0 (for example 52.0).
SalesforceServiceCloudV2
- type must be SalesforceServiceCloudV2.
- Connects specifically to a Salesforce Service Cloud instance.
- Uses the same OAuth2 client credentials pattern (clientId, clientSecret).
- Also requires environmentUrl and apiVersion for Bulk API 2.0.

Both connectors:

Support the same core capabilities in ADF: Copy activity (source/sink) and Lookup activity on both Azure IR and self-hosted IR.
Use Bulk API 2.0 when writing data.
Require the same style of linked service configuration (environment URL, OAuth2 client credentials, Bulk API 2.0 version).

The documentation does not list any difference in supported operations or object coverage between SalesforceV2 and SalesforceServiceCloudV2. The distinction is primarily product‑scoping and naming (Sales Cloud vs Service Cloud) rather than different ADF features.

Regarding switching connectors in an existing pipeline:

Since both connectors expose the same authentication model and Bulk API 2.0 behavior, and the objects needed are visible through SalesforceServiceCloudV2 in the environment, it is technically safe at the ADF level to point datasets and linked services to SalesforceServiceCloudV2 instead of SalesforceV2, provided:
- The new linked service is configured with the correct environmentUrl, clientId, clientSecret, and apiVersion.
- Datasets and activities are updated to reference the new linked service type (SalesforceServiceCloudV2).
No additional ADF limitations or behavioral differences are documented between the two V2 connectors.

In practice, for an org that is primarily using Service Cloud objects (like Asset, Order) and where all required objects are visible via SalesforceServiceCloudV2, using SalesforceServiceCloudV2 as the standard connector is aligned with the documented intent of the connector.

References:

Share via

ADF - Salesforce Linked Service - difference between SalesforceV2 & SalesforceServiceCloudV2

1 answer

Your answer