Salesforce: Connector Update - BugFix / Multi Salesforce tenant support

[ChristopherFitzsimons]

Required items, please complete

Change(s):

• Updated OAuth authentication for the connector definition to use 2024-09-01 and the blade configuration panel.
• Added a connector table for multiple Salesforce tenants.
• Added a UUID based on the Salesforce domain to allow multiple tenants to be connected.
• Updarted Files:
  • SalesforceServiceCloud_DataConnectorDefinition.json
  • azuredeploy_SalesforceServiceCloud_poller_connector.json

Reason for Change(s):

• Data Connector was broken. It would cause an error when a connection / deployment was attempted.
• The Connector also didn't support multiple Salesforce tenants, so support was added to maintain multiple Connectors.
• Resolves ISSUE Salesforce CCF Connector not deploying (Browser Error and InternalServerError with ARM templates) #13669

Version Updated:

• No

Testing Completed:

• Yes
• Changes have been validated and deployed to multiple Sentinel instances.
• Tested multi-Salesforce tenant deployment on one Sentinel instance.

Checked that the validations are passing and have addressed any issues that are present:

• Yes

[ChristopherFitzsimons]

@microsoft-github-policy-service agree company="CyberCX"

[ChristopherFitzsimons]

@ChristopherFitzsimons please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="CyberCX"

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the Salesforce Service Cloud connector deployment/definition to fix a broken deployment flow and enable connecting multiple Salesforce tenants by moving to the newer OAuth/configuration UX and API version.

Changes:

• Updated ARM/API versions for the connector definition to 2024-09-01.
• Reworked connector configuration UI to a grid + context pane experience and replaced OAuth form fields with explicit Client ID/Secret inputs.
• Adjusted connector naming to incorporate a Salesforce-domain-derived unique identifier to support multi-tenant connections.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
Solutions/Salesforce Service Cloud/Data Connectors/SalesforceSentinelConnector_CCP/azuredeploy_SalesforceServiceCloud_poller_connector.json	Updates Data Connector Definition API version/UI steps and modifies connector resource naming to support multiple tenants.
Solutions/Salesforce Service Cloud/Data Connectors/SalesforceSentinelConnector_CCP/SalesforceServiceCloud_DataConnectorDefinition.json	Updates connector definition API version, UI instruction steps, and dataType queries to match the new table name.

[ChristopherFitzsimons]

I have only modified the template in SalesforceSentinelConnector_CCP.
Do I need to add my changes to the mainTemplate.json and version package in the Package section for these changes to apply? This is my first update so I'm a little new to how these templates apply in the Content Hub when referenced from the formal repo.

[v-maheshbh]

I have only modified the template in SalesforceSentinelConnector_CCP. Do I need to add my changes to the mainTemplate.json and version package in the Package section for these changes to apply? This is my first update so I'm a little new to how these templates apply in the Content Hub when referenced from the formal repo.

Hi @ChristopherFitzsimons

Kindly repackage this solution using the V3 tool and resolve the branch conflict.

https://github.com/Azure/Azure-Sentinel/blob/master/Tools/Create-Azure-Sentinel-Solution/V3/README.md

Thanks!