Microsoft reports continued recovery of Microsoft 365, with email queues returning to normal levels in North America and Europe.
Since 10:00 UTC (07:00 GMT-3) on November 13, we have seen a sharp decrease in failures on pipeline steps that call Microsoft endpoints. Connection refusals from Microsoft mail servers have stopped, and only occasional timeouts on Microsoft Graph calls remain.
The Digibee Integration Platform continues to operate normally.
We recommend reviewing executions that failed on Microsoft-dependent steps between November 12, 17:00 UTC and November 13, 14:00 UTC, and reprocessing them where needed. If your pipelines send alert emails through Microsoft 365, please also check whether any alerts from that period were not delivered.
We’ll move this incident to Resolved once Microsoft confirms full recovery and our monitoring shows no further related failures.
No components marked as affected
Monitoring
Microsoft reports continued recovery of Microsoft 365, with email queues returning to normal levels in North America and Europe.
Since 10:00 UTC (07:00 GMT-3) on November 13, we have seen a sharp decrease in failures on pipeline steps that call Microsoft endpoints. Connection refusals from Microsoft mail servers have stopped, and only occasional timeouts on Microsoft Graph calls remain.
The Digibee Integration Platform continues to operate normally.
We recommend reviewing executions that failed on Microsoft-dependent steps between November 12, 17:00 UTC and November 13, 14:00 UTC, and reprocessing them where needed. If your pipelines send alert emails through Microsoft 365, please also check whether any alerts from that period were not delivered.
We’ll move this incident to Resolved once Microsoft confirms full recovery and our monitoring shows no further related failures.
Monitoring
Microsoft is experiencing a global Microsoft 365 service degradation that began on November 12, 2026 at approximately 17:00 UTC (Microsoft incidents EX1550543 and MO1550821). It mainly affects Exchange Online/Outlook, along with dependent services such as Microsoft Graph, Entra ID sign-in, and SharePoint Online.
We are seeing failures in pipeline executions that call Microsoft endpoints. The most common are:
Connections refused or timed out when sending email through Outlook / Office 365 SMTP servers
Temporary rejections returned by Microsoft mail servers (for example, “451 4.7.0 Temporary server error”)
Timeouts on calls to Microsoft Graph and Entra ID token endpoints
The Digibee Integration Platform is operating normally. Pipeline execution, triggers, deployments, and monitoring are not affected. We see no impact on integrations with other systems. Failures are limited to steps that call Microsoft services, and they come from the Microsoft outage.
Recommendations while Microsoft completes its recovery:
If your pipelines send error alerts or notifications by email through Microsoft 365, some alerts may not have been delivered since the incident began. Please review recent executions in Digibee Monitor.
Executions that failed on Microsoft-dependent steps can be reprocessed once Microsoft confirms recovery.
Microsoft reports gradual recovery, but intermittent failures may continue for some time.
We are monitoring this incident and will post updates as it develops. For questions about a specific pipeline, please contact Digibee Support.