Intermittent Connectivity Issues with EllbyConnect
Affected
Degraded performance from 12:11 AM to 11:25 AM
- Resolved · UTC
This incident has been resolved, all systems are functioning as normal.
Microsoft provided Root Cause Analysis :
TRACKING ID:
5Y3C-MLZTYPE:
IncidentSTATUS:
Root Cause AnalysisCOMMUNICATION:
What happened?
Between 18:36 UTC 05 May 2026 and 07:42 UTC on 06 May 2026, a platform issue resulted in an impact to the Logic Apps service in the Australia region. Impacted customers experienced failures when running workflows that connect to SQL through On-Premises Data Gateway, preventing workflows from completing as expected.
What went wrong, and why?
During the deployment of SQL Connector service, an issue was introduced on the backend service that caused connection failures for Logic Apps workflows using SQL connections via Gateway. This issue occurred within the service following the deployment and prevented workflows from establishing or using connections as expected. The problem was identified and addressed by reverting the affected deployment, which restored normal service behavior.
How did we respond?
18:36 UTC on 05 May 2026 – Customer impact began.
07:18 UTC on 06 May 2026 – Correlation with a recent SQL Connector deployment was identified.
07:30 UTC on 06 May 2026 – Rollback of the recent deployment was initiated as the mitigation workstream.
07:42 UTC on 06 May 2026 – Service restored, and customer impact mitigated.
- Monitoring · UTC
We have been advised by Microsoft that this incident has now been resolved. We will monitor the fix to ensure this is the case and will close this incident once we are satisfied with the resolution.
Microsoft tracking ID 5Y3C-MLZ:
"Between 18:36 UTC on 5 May 2026 and 07:42 UTC on 6 May 2026, a platform issue resulted in an impact to the Logic Apps service in the Australia region. Customers may have experienced failures when running workflows that connect to SQL through On-Premises Data Gateway, preventing workflows from completing as expected. This issue is now mitigated" - Update · UTC
Microsoft engineering have informed us that this is a global issue with a connector for SQL. They are currently working on a fix and will let us know when they have an ETA for resolution. We will update when we have further information from them on a fix.
- Identified · UTC
We are continuing to work with Microsoft on a fix for this. The issue has been escalated to their engineering team for further investigation. We will update once we have more information from them on the issue.
- Update · UTC
We are currently working with Microsoft Support to determine the source of the issue. We will update further as we make progress.
- Investigating · UTC
We are currently investigating this issue and will update further as we make progress.

