The official @Microsoft account for updates on certain @Microsoft365 service incidents. Get push notifications on our admin app: aka.ms/M365AdminMobile.
Joined January 2012
- Tweets 6,781
- Following 4
- Followers 306,430
- Likes 1
1 Photos and videos
We're looking into a potential problem impacting Microsoft 365 Copilot chat. For more information, please see CW1387674 in the Microsoft 365 admin center.
16
14
88
36,049
We have successfully reverted the change and confirmed with previously affected users that the issue is resolved. For more information, see MO1387691 in the admin center.
5
7
20
11,729
We’ve identified an issue with a recent deployment for Microsoft Copilot, which impacts users' ability to access Copilot chat and portal.office.com. We’re reverting to a previous build to remediate impact. For more information, please see MO1387691 in the admin center or status.cloud.microsoft/
7
3
16
8,924
We’re investigating an issue where some users may be experiencing app load and timeout errors when accessing Microsoft 365 Copilot. More information is available under CP1329665 in the admin center or at status.cloud.microsoft
14
19
54
36,851
We identified a routing issue which is sending Copilot traffic to a portion of infrastructure that is unhealthy, resulting in access and timeout errors. We're rerouting requests to healthy infrastructure and our telemetry is starting to show quick recovery. More info is available under CP1329665 in the admin center or at msft.it/6010vbrc8.
3
4
12
23,506
We've rerouted requests to healthy infrastructure and confirmed through our telemetry and customer reports that Copilot service health has recovered. More info is available under CP1329665 in the admin center or at status.cloud.microsoft.
2
4
8
19,193
We’re investigating reports that some users are unable to open files in Office for the web or Microsoft Teams. For more information, please see MO1329446 in the admin center.
9
22
80
33,958
We’re analyzing service telemetry and have identified elevated error rates across Office for the web experiences. We’re correlating these error patterns across service dependencies to determine the next steps required. For more information, please see MO1329446 in the admin center.
4
2
21
21,088
We've confirmed that the impact is no longer occurring and the final details are being provided under MO1329446 in the admin center.
5
2
11
15,715
We’re investigating an issue where some users may be unable to setup MFA or access the mysignins.microsoft.com website. For more information, please see MO1329260 in the admin center.
10
19
64
35,708
We’ve completed a failover to alternate healthy infrastructure to mitigate the impact and are closely monitoring service telemetry to ensure full recovery. For more information, please see MO1329260 in the admin center.
3
1
20
19,849
A recent cache configuration change required a failover. During the transition, high EU traffic caused CPU and memory pressure, impacting MySignIn request processing. We’ve rolled back mitigation actions and restored traffic to the original infrastructure. For more information, please see MO1329260 in the admin center.
3
14
14,297
We’re investigating an issue in which some users located in the United States and United Kingdom may be experiencing issues accessing Microsoft 365 Copilot. We’re providing updates under CP1326225 in the admin center.
25
17
66
35,970
Previously, we communicated that impact was specific to the United States and the United Kingdom. Further investigation has confirmed that any user with access to Microsoft 365 Copilot could be impacted by this issue. We’ve taken several mitigation actions and have seen recovery with a portion of affected users. We're continuing to take action and will provide additional updates in the admin center under CP1326225.
3
3
12
17,041
After completing our mitigation actions and a period of extended monitoring, we’ve validated that service has been restored. Additional details can be found in the admin center under CP1326225.
12
10,100
We're investigating an issue affecting Microsoft Teams performance in the Asia-Pacific region and we're applying a fix to restore normal service. More information can be found in the admin center under TM1314397.
5
25
82
64,312
We’ve confirmed service recovery at expected levels across all impacted scenarios and we're continuing to monitor to ensure service stability. Further information can be found in the admin center under TM1314397.
1
3
12
25,669
After a period of extended monitoring and continued service stability, we have declared the issue mitigated. Full details can be found in the admin center under TM1314397.
1
5
13,928