Impact in Azure Logic Apps caused by Salesforce disruption

Koichi Ozawa 1 Reputation point
2026-09-16T23:41:59.16+00:00

Regarding the Salesforce service disruption that began around 17:00 JST yesterday, how would the trigger conditions for the Azure Logic Apps Salesforce connector (which fire when a Salesforce record is created or modified) be affected?

While I understand that I should contact Salesforce directly regarding the impact itself, I would like to know—prior to making that inquiry—exactly which Salesforce features are used to implement these trigger conditions for the Azure Logic Apps Salesforce connector.

Azure Logic Apps
Azure Logic Apps

An Azure service that automates the access and use of data across clouds without writing code.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Tejaswini Billakurthi 760 Reputation points Microsoft External Staff Moderator
    2026-09-17T09:38:55.74+00:00

    Hi @Koichi Ozawa ,

    Thank you for reaching out to Microsoft Q & A !

    The dependency Microsoft’s Salesforce connector reference confirms is Salesforce API access through an authenticated connection. It lists these trigger operations:

    • When a record is created: GetOnNewItems
    • When a record is modified: GetOnUpdatedItems

    The documented default Salesforce API version is v58.0, although the connection can specify another version.

    However, the reference does not identify the exact Salesforce endpoint used internally by these triggers. Its statement about using Salesforce’s Query API applies specifically to the Get records and Execute a SOQL query actions, so that statement does not establish which API the triggers use.

    If the disruption affected your instance’s API access or the authentication used by the connection, it could affect trigger checks. The disruption notice alone is not enough to determine whether your workflow was affected.

    If you want to verify actual impact, review Trigger history during the affected window and open any Failed attempt’s Outputs. A Skipped attempt means no data met the criteria; Succeeded means data was available, not that the entire workflow completed successfully. Check Fired and the resulting run separately, as described in the monitoring guide.

    For your Salesforce inquiry, ask whether the incident affected authenticated API access to the monitored object in your Salesforce instance, rather than only interactive sign-in. Please share the public incident link so we can compare its stated scope with these dependencies.

    Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. 小澤　浩一 0 Reputation points
    2026-09-18T06:21:11.5066667+00:00

    Hi, @Tejaswini Billakurthi .

    Thank you for your comment.

    So, the information is limited to what is in the official documentation.

    I have also asked Salesforce the same question, but their response was that they want to know what specific technologies Azure Logic Apps uses.

    It seems likely that both Microsoft and Salesforce will conclude that they cannot provide an answer because the details are unknown and depend on the other party's specifications.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.