Update
Latest from MS:
We’re opening all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. We found a core process on affected servers is becoming overwhelmed, causing capacity loss. To validate a potential recovery, we're isolating a portion of infrastructure, restarting affected components, and reintroducing traffic to confirm the services remain stable before applying the change more broadly. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available to you.
We’re opening all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. We found a core process on affected servers is becoming overwhelmed, causing capacity loss. To validate a potential recovery, we're isolating a portion of infrastructure, restarting affected components, and reintroducing traffic to confirm the services remain stable before applying the change more broadly. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available to you.
Update
We are continuing to monitor for any further issues.
Monitoring
Microsoft Outage Impacting M365 Services Across America. This is impacing XTIUM's ability to send/recieve email which also impacts tickets coming into ServiceNow Ticketing Platform.
From Microsoft:
We've validated an alternative service health check method, which allowed a subset of affected servers to successfully return to service. We're now applying this change more broadly. We're also preparing automated recovery systems to continually detect and restart unresponsive servers, to maintain service stability while this change progresses. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available to you.
From Microsoft:
We've validated an alternative service health check method, which allowed a subset of affected servers to successfully return to service. We're now applying this change more broadly. We're also preparing automated recovery systems to continually detect and restart unresponsive servers, to maintain service stability while this change progresses. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available to you.
This incident affects: Ticketing (ServiceNow), ITOPS (Other), and Collaboration (Microsoft Teams Direct Routing (third-party)).