What Changed

The Salesforce Audit Logs connector (SalesforceAuditLogsConnector_CCF) has been marked as generally available (isPreview: false) in v3.5.0 of the Salesforce Service Cloud solution.

Two additional changes were made to the polling configuration:

  • Poller resource names made unique per connection: Both SalesforceAuditTrailPoller and SalesforceLoginHistoryPoller resource names are now generated via uniqueString(parameters(friendlyName)) to prevent resource name collisions when deploying multiple instances.
  • Sample query placeholder replaced: The graphQueriesTableName placeholder in the connector UI sample query was hardcoded to SalesforceAuditTrail.

Security Impact (Visibility & Fidelity)

The GA promotion itself does not change ingestion logic – SetupAuditTrails and LoginHistory logs continue flowing as in v3.3.0 when this connector was first introduced. No data fidelity gap is introduced or closed by this change.

Deployment risk – ARM expression syntax: The Copilot reviewer flagged that both new poller name fields embed parameters(workspace) as a quoted string literal rather than as an ARM function call. The resulting concat expressions may fail ARM template validation at deployment time. Environments deploying connector version 3.5.0 should verify the template parses correctly before deploying. If deployment fails, the connector will not be created and no Salesforce audit data will be ingested.

Per PR discussion: a contributor confirmed the connector was successfully connected in testing, though the ARM expression issue was raised post-review and may affect environments with stricter ARM validation.

Affected Files

Solutions/Salesforce Service Cloud/Data Connectors/SalesforceAuditLogsConnector_CCF/SalesforceAuditLogs_DataConnectorDefinition.json
Solutions/Salesforce Service Cloud/Data Connectors/SalesforceAuditLogsConnector_CCF/SalesforceAuditLogs_PollingConfig.json
(packaging artefacts: 3.5.0.zip, ReleaseNotes.md, Solution_TSalesforceCloudtemplateSpec.json, mainTemplate.json)