Microsoft 365 Status (@MSFT365Status) header
Microsoft 365 Status (@MSFT365Status) profile picture

The official @Microsoft account for updates on certain @Microsoft365 service incidents. Get push notifications on our admin app: https://xitter.twitterapi.xyz/t.co/pGaOsdAblF.

Redmond, WA
Joined January 2012
Photo by Microsoft 365 Status (@MSFT365Status)
We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. More details can be found in the Microsoft 365 admin center under EX1550543.
2,018
3,179
2,221
17,651
5,324,606
We're testing a configuration change to address a problem that's causing servers to fail automated health checks and become unavailable. In parallel, we've initiated a restart of all affected servers and are monitoring health as they return to service. 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.
206
82
84
737
503,605
We've not identified any recent change correlated with the start of impact; however, our investigation indicates the failed health checks may originate from a specific component that's responsible for processing server health. We've taken steps to prevent additional servers from being impacted while we work to return the affected servers to service. 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.
222
81
66
603
352,509
We're investigating reports of users experiencing issues when accessing or using Microsoft Teams functionality in North America, and more details can be found in the Microsoft 365 admin center under TM1550488.
100
175
42
1,363
858,997
We've confirmed related impact scenarios and have updated TM1550488. Our automated recovery features have taken action to restore service, and our telemetry indicates that these actions are effectively reducing impact. More details can be found in the Microsoft 365 admin center.
22
17
2
178
564,420
Our mitigative actions have successfully restored service health and functionality. Customer impact is now fully resolved. Additional information can be found under TM1550488 in the Microsoft 365 admin center.
117
8
11
53
90,813
We're investigating a potential issue for Microsoft Teams, affecting some users in the United States. For more information, see TM1526111 in the Microsoft 365 admin center.
25
68
9
409
424,818
We've confirmed after monitoring our telemetry that the automatic scaling efforts to increase processing throughput were successful and the service has returned to healthy levels. For more information, see TM1526111 in the admin center.
2
10
15,160
We're beginning to observe restoration as our automated recovery actions take effect. We're monitoring to ensure full recovery, and in parallel, we're continuing to investigate the initial cause of impact. For more information, see TM1526111 in the admin center.
1
6
24
251,964
We're investigating an issue affecting model selection options in Copilot Chat. We're currently reviewing service telemetry to isolate the root cause and determine our next troubleshooting steps. For more information, please see CW1507178 in the admin center.
5
32
3
108
232,374
We've identified a component responsible for producing the model selection options in Copilot chat was not functioning correctly. We're deploying a fix to the affected infrastructure to mitigate impact. For more information, please see CW1507178 in the admin center.
1
1
25
139,153
We've completed deploying the fix to the affected infrastructure and we've verified with previously impacted users that the issue is now resolved. For more information, please see CW1507178 in the admin center.
1
4
18
10,196
We're investigating an issue in which some admins may be unable to access the Exchange admin center (EAC) and may encounter an “Internal Server Error” message. For more information, please see EX1500900 in the admin center.
6
35
2
147
159,865
We’re rolling back a recent change to the Exchange Admin Center (EAC) to determine if this resolves the impact. While we're closely monitoring for improvement we're continuing to investigate the source of the issue. For more information, please see EX1500900 in the admin center or via admin.microsoft.com.
7
4
24
92,292
We’ve rolled back the change and confirmed through service telemetry and impacted users that the issue is now resolved. For more information, please see EX1500900 in the admin center or via admin.microsoft.com.
1
4
17
11,862