Microsoft's Incident Report for PennO365
Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within
the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh
this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this
list. Additionally you can check Microsoft's
status page for current service status messages.
The last extract was taken on Tue Mar 18 12:30:07 2025.
EX1030895 - Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
| Status: | serviceDegradation |
|---|
| Start Time: | Sun Mar 9 08:07:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Mar 18 11:34:26 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Tuesday, March 18, 2025, at 7:30 PM UTC |
|---|
|
Details
| Time: | Tue Mar 18 09:54:48 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We're continuing to monitor the deployment of the fix as it progresses throughout the affected environment and the current saturation level is at 99.3%. While the majority of impact is mitigated, users may still see some NDRs until the fix is fully deployed across the infrastructure. We'll keep this notification active and provide an immediate update should there be a substantial change in service performance, otherwise the next update will be provided at 7:30 PM UTC.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Tuesday, March 18, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Mar 18 00:48:01 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We have confirmed that the deployment of the fix is progressing as expected. In parallel, we have exhausted manual efforts to safely expedite the deployment and expect the remaining affected infrastructure to take an extended period to complete. We still remain confident that a majority of the impact has been mitigated. If your organization continues to see high impact related to this event, please work with your support representative to gather the relevant diagnostic data so we may explore avenues to address the impact being experienced.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Wednesday, March 19, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Mar 17 21:13:52 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: Our worldwide patch has exceeded well above 95 percent saturation across the affected infrastructure and our internal testing continues to affirm that the fix is addressing the issue as expected. We’ll continue monitoring the saturation of the fix as it continues its progression, and we’ll provide updates as they become available.
In addition, our reproductions of impact have been helpful in our investigation to identify a potential root cause. We’ll continue working on this investigation in parallel with our monitoring.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Tuesday, March 18, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Mar 17 17:58:22 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The worldwide patch is moving along as anticipated and has saturated to over 90% of environments. Our telemetry indicates that the fix is working as expected. We predict that there may be certain portions of the affected infrastructure that may still take several hours to receive the fix. We’ll continue to closely monitor the impacted environments while the patch deployment completes.
In parallel we’re continuing to focus on internal reproductions of impact in order to isolate the root cause of the incident.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Tuesday, March 18, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Mar 17 14:53:31 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: After some additional validations, we’ve begun a worldwide rollout of our patch and anticipate it will take up to twelve hours to fully saturate all environments. We expect users to experience relief from impact as they receive the fix. We’ll continue to closely monitor the service health during this rollout.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Mar 17 11:38:52 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We’ve deployed the secondary fix via an emergency patch to a small portion of production infrastructure and have validated that email replay is successful as expected and that NDR errors have been eliminated in this environment. We're now preparing to release this fix more broadly.
Additionally, we’ve gathered additional trace logs from internal reproductions that we are analyzing to isolate a potential root cause.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Mar 17 06:22:41 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The targeted deployment has completed; however, a separate issue has been highlighted with a code path for a specific property which is also contributing to the NDR failures. We’re testing a fix for this issue internally and are conducting thorough checks to ensure full recovery.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Mar 17 04:30:37 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We're continuing targeted deployments to address residual NDRs, which is completing as expected. To understand the more recent increasing NDRs, we’re reproducing the issue internally to get a better understanding of the next steps required to resolve the NDRs.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Mon Mar 17 01:53:44 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: Our targeted deployment efforts are progressing steadily and safely across the remaining impacted infrastructure as a result of prioritization efforts. Concurrently, we’ve received reports of an increase in NDRs that may be causing additional impact. We’re investigating these reports and available telemetry to develop a new mitigation strategy.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Mar 16 19:33:12 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: We expect the impact to be mitigated for a majority of our users; however, we remain focused on ensuring this incident is fully resolved.
Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We’re continuing to perform targeted deployments of the fix to the remaining affected service infrastructure. We'll be treating this process with the highest priority and urgency to ensure that users are no longer impacted by this event. If your organizations continue to experience impact, please file a support ticket so we can work directly work with your representatives and address the issue. We deeply appreciate your organization’s continued patience while we progress the deployments of the fix.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Sun Mar 16 15:03:49 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: Our fix has saturated 98 percent of all affected regions, and a majority of customers should be experiencing relief. Users who received NDR messages should now be able to resend them. For the remaining two percent of the affected infrastructure, we’re reviewing our targeted deployment options to determine if we can help to expedite the process to fully resolve the impact. We understand the impact this has on your organization and appreciate your patience while we focus on our fix.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Monday, March 17, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Sat Mar 15 22:56:10 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We’re continuing our monitoring of the fix deployment. We've seen a substantial surge in the fix’s saturation of the environment within the last few hours, as we're now above 80 percent deployment across all regions, which is much sooner than expected. In addition, our telemetry also shows an increase in service health and reduced error rates, which corresponds to our deployment efforts. We're closely monitoring error rates to ensure continued recovery and readiness for any necessary mitigation actions.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Sunday, March 16, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Sat Mar 15 19:22:48 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We're closely monitoring the propagation of the fix, which remains steadily on track with our original estimation towards full saturation. In addition, our telemetry aligns with the fix path and continues to show improvement in the error rate trajectory.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Sunday, March 16, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sat Mar 15 17:17:29 2025 |
|---|
| Description: | Our deployment is in progress and has reached approximately 26 percent saturation to affected infrastructure.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sat Mar 15 12:26:20 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: Our main fix deployment has completed on a limited portion of the infrastructure and is showing a marked improvement in the error rate. We have started expanding this deployment to the rest of the affected infrastructure and expect this will propagate over the next day.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Sunday, March 16, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sat Mar 15 00:19:42 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The fix deployment continues to saturate within our internal infrastructure, and telemetry data remains positive. Additionally, we're identifying infrastructure optimized for fix integration to enhance opportunities for seamless implementation. We’ll continue to monitor the status of all deployments, identify opportunities for enhancements, and provide status updates as they become available.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 15, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Mar 14 22:20:53 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The deployment of the potential fix has successfully reached over 30 percent saturation across our internal infrastructure. Telemetry data continues to indicate that the deployment is healthy and error-free. Concurrently, we're assessing the effectiveness of additional fixes, isolating potential errors, and making refinements to address identified issues. We’ll maintain the momentum of all rollouts and deployments and keep you informed with updates as they become available.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 15, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Fri Mar 14 20:26:47 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The deployment of the potential fix is 22 percent saturated within our internal infrastructure. Our telemetry indicates no errors associated with NDRs from our internal infrastructure with the potential fix. Our parallel deployment of the potential fix to a subset of service infrastructure is 60 percent saturated. Collecting trace data of the failures continues to be a challenge. We plan to continue our rollout of the potential fix as our deployments complete, if telemetry indicates the infrastructure with the fix is in a healthy state.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 15, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Mar 14 18:26:31 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: The deployment of the potential fix has reached ten percent saturation within our internal infrastructure. We're continuing to monitor telemetry and use trace data to determine the root cause. We've had difficulty collecting trace data of the failures due to the transient nature of this incident. We've started deploying the potential fix to a subset of service infrastructure to help with collecting this trace data to assist our investigation.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 15, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Mar 14 16:29:58 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite emails as a plain text message containing winmail.dat attachments.
Users may be able to send affected messages by attempting to resend. This may not be effective for all users.
Current status: We've expanded deploying our potential fix to our entire internal infrastructure and continue to monitor targeted restarts of machines with the fix to ensure relief is resilient. Concurrently, we've deployed updates to our tooling that provide us with additional telemetry which we're using with additional NDR trace data to continue to investigate and provide a more detailed diagnosis of the root cause.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Friday, March 14, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Mar 14 13:07:31 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite emails as a plain text message containing winmail.dat attachments.
Current status: We're continuing to verify the effectiveness of the potential fix deployed to an isolated section of our internal infrastructure. We're conducting multiple targeted restarts of machines containing the fix to ensure the expected relief is achieved. Additionally, we're closely monitoring our diagnostic telemetry data to isolate the root cause of the issue, and we're reviewing the overall service health during this process. Once we've determined the effectiveness of the fix, we'll begin deploying it to the wider environment.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Next update by: Friday, March 14, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Mar 14 11:34:51 2025 |
|---|
| Description: | We've completed the deployment of the fix within an isolated section of our internal infrastructure. We're now conducting targeted restarts of machines containing the fix to verify its effectiveness. Early indications suggest the fix is producing the desired effect but we're closely monitoring our diagnostic telemetry to ensure impact is being fully mitigated. Once we're satisfied the fix is providing the expected relief, we'll begin deploying the fix to the wider environment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Mar 14 10:29:55 2025 |
|---|
| Description: | We're closely monitoring the deployment of the fix within an isolated section of our internal infrastructure, and it is nearing completion. Once the deployment completes, we'll conduct targeted reboots of machines containing the fix as part of the process to verify the effectiveness of the fix. As previously mentioned, if effective, the fix will then be deployed to the wider environment. Additionally, we're continuing to analyze telemetry data to isolate the root cause of the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Mar 14 09:12:12 2025 |
|---|
| Description: | We're continuing to analyze diagnostic telemetry data to isolate the root cause of the issue. In parallel, we've developed a fix and we're currently testing the effectiveness of the fix within an isolated section of our internal infrastructure to ensure the it provides the expected relief from impact. If effective, the fix will be deployed to the wider environment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Mar 14 08:25:27 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may intermittently receive calendar invite emails as a plain text message containing winmail.dat attachments.
Current status: In addition to our other work streams, we believe a recent update that contains a code issue is causing the message delivery failures, due to the content not being processed as expected. To aid our mitigation efforts, we’ve halted the update to prevent additional users from becoming affected by the issue. We’re continuing to analyze diagnostic data to validate the root cause of the issue.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Next update by: Friday, March 14, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Mar 14 00:03:27 2025 |
|---|
| Description: | Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may encounter NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've identified that impact is not limited to users sending IRM protected email as we previously communicated. We've updated the title, user impact, more info and scope of impact sections of this communication to reflect that new information. Our previously stated fix will continue deploying to affected infrastructure while we continue monitoring its efficacy as it progresses. Concurrently, we’ve shifted attention to our reproduction efforts and deeper log analysis to further isolate the cause of impact and identify new mitigation strategies.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected, although impact is limited to a small subset of messages.
Next update by: Friday, March 14, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Mar 13 21:36:07 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving email messages protected by Information Rights Management (IRM)
User impact: Users may encounter failures when sending or receiving IRM protected email messages in Exchange Online.
More info: Users sending IRM protected email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've developed and subsequently deployed the aforementioned potential fix and are monitoring the affected service environment while reaching out to some affected users for testing to ensure that it has the desired results and to determine whether any additional mitigating actions are required.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving IRM protected email in Exchange Online may be affected.
Next update by: Friday, March 14, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Mar 13 19:32:36 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving email messages protected by Information Rights Management (IRM)
User impact: Users may encounter failures when sending or receiving IRM protected email messages in Exchange Online.
More info: Users sending IRM protected email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: Although our efforts to reproduce this issue have been inconclusive so far, we're in the process of developing a potential fix for this issue which will undergo our internal validation tests before being applied throughout the affected environments. Additionally, we're attempting to gather dump logs which we anticipate will aid in expediting our understanding of the underlying cause of impact.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving IRM protected email in Exchange Online may be affected.
Next update by: Friday, March 14, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Mar 13 17:13:36 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving email messages protected by Information Rights Management (IRM)
User impact: Users may encounter failures when sending or receiving IRM protected email messages in Exchange Online.
More info: Users sending IRM protected email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've determined this is impacting email messages protected by IRM, and we've updated the Title, User impact, More info, and Scope of impact sections to reflect this. We're continuing our efforts to reproduce this issue to help us further our investigation into the root cause of impact.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving IRM protected email in Exchange Online may be affected.
Next update by: Thursday, March 13, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Mar 13 15:57:24 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving some email messages in Exchange Online
User impact: Users may encounter failures when sending or receiving some email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've identified that a recent update may have introduced inaccurate content conversion logic which is preventing some email from being sent or received. We're attempting to reproduce this issue so we can test a potential code fix to this logic that we expect will remediate impact.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving some email in Exchange Online may be affected.
Next update by: Thursday, March 13, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Mar 13 13:31:38 2025 |
|---|
| Description: | Title: Users may encounter failures when sending or receiving some email messages in Exchange Online
User impact: Users may encounter failures when sending or receiving some email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We're reviewing Non-Delivery Reports (NDRs) gathered from impacted users to identify why users may encounter failures when sending or receiving some email messages in Exchange Online.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving some email in Exchange Online may be affected.
Next update by: Thursday, March 13, 2025, at 7:30 PM UTC
|
|---|
|
TM1000103 - Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Jan 29 10:11:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 18 07:09:37 2025 |
|---|
| Root Cause: | The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact. |
|---|
| Next Update: | Thursday, March 20, 2025, at 11:00 AM UTC |
|---|
|
Details
| Time: | Tue Mar 18 07:05:17 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: The deployment is taking longer than expected to complete and we anticipate it will complete by Thursday, March 20, 2025.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Microsoft Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Thursday, March 20, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Mar 13 06:47:04 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: We've completed our testing and validation phase of the proposed fix. We're now commencing with the deployment which will be deployed in phases. We predict that the fix will be fully deployed and completed by Tuesday, March 18, 2025.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Microsoft Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Tuesday, March 18, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Mar 12 06:52:56 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: We're continuing our in depth testing and validation phase for our fix to ensure the deployments saturates successfully. We aim to finish the testing phase by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Microsoft Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Thursday, March 13, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Mar 11 06:50:29 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: The testing and validation phase for our fix is taking longer to complete than initially anticipated. We expect to be able to provide an approximate deployment timeline as part of our next scheduled update.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Microsoft Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Wednesday, March 12, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Mar 10 14:12:33 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: We expect our testing to validate the fix developed to fully resolve the issue will complete by our next scheduled update. Once the fix has been validated, we'll provide a timeline for remediation.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Microsoft Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Tuesday, March 11, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Mar 4 12:41:06 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: We're in the final stages of validating the fix to fully resolve this issue. Once completed, we will provide a remediation timeline.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Microsoft Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Monday, March 10, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 12:30:09 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: We’ve disabled the affected feature, and are developing and testing a potential fix to fully resolve the issue. We’ll provide a resolution timeline as soon as it becomes available.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Microsoft Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Tuesday, March 4, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Feb 18 12:50:01 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: During the process of deploying our fix to resolve this issue, we’ve identified some additional issues that will require a more comprehensive change to address. We've halted the ongoing deployment and are reviewing options to potentially disable the affected feature as develop another fix, with the expectation that we’ll have an estimated timeline for impact resolution by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Tuesday, February 25, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Feb 10 05:31:57 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: We've developed and validated a fix to repair the error, and begun deployment to the affected environment. We expect the fix to fully saturate and remediate impact to end users by the time of our next scheduled update.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Tuesday, February 18, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Feb 7 14:19:22 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appears to be enabled, there is no actual effect and users can't be added to the block list.
Current status: Our service health telemetry has alerted us to an issue affecting the Microsoft Teams service in which admins may be unable to block external users in the Teams admin center. Our investigation has determined that the update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact. We're developing a fix to repair the error, and we'll provide a timeline for the development and deployment of this fix as it becomes available.
Scope of impact: Your organization is affected by this event, and any admin that enables the function to block external users in the Teams admin center is impacted.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contains an error that's leading to impact.
Next update by: Monday, February 10, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Fri Feb 7 13:52:50 2025 |
|---|
| Description: | Title: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center
User impact: Admins may be unable to enable the function to block external users in the Microsoft Teams admin center.
Current status: We're investigating a potential issue with the Microsoft Teams service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1029706 - Some users may receive a cancellation email when the attendees list is edited for existing town hall meetings
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Jan 15 12:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 17 22:48:24 2025 |
|---|
| Root Cause: | A service change, meant to improve the editing experience for meeting invites by ensuring that only added or removed attendees receive notifications of the change to their email, is causing impact. |
|---|
| Next Update: | Tuesday, March 18, 2025, at 11:00 PM UTC |
|---|
|
Details
| Time: | Mon Mar 17 22:48:24 2025 |
|---|
| Description: | Title: Some users may receive a cancellation email when the attendees list is edited for existing town hall meetings
User impact: Users may receive a cancellation email when the attendees list is edited for existing town hall meetings
More info: To bypass the issue, meeting organizers should avoid making edits that only change the co-organizers, presenters, or attendees. Making other edits in addition to edits to these categories may allow meeting organizers to avoid the impact.
The town hall meetings aren’t canceled and users who receive this email can still attend the meeting as expected using the previously provided details.
Current status: The deployment to revert the recent update has completed on the majority of the impacted infrastructure and we expect that most users are no longer experiencing the issue. We'll continue monitoring the remainder of the deployment to ensure that the impact is remediated for all users.
Scope of impact: Some users who are added as attendees to Microsoft Teams town halls and have previously accepted the invitation may be impacted.
Start time: Wednesday, January 15, 2025, at 5:00 PM UTC
Root cause: A service change, meant to improve the editing experience for meeting invites by ensuring that only added or removed attendees receive notifications of the change to their email, is causing impact.
Next update by: Tuesday, March 18, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Mar 17 17:55:55 2025 |
|---|
| Description: | Title: Some users may receive a cancellation email when the attendees list is edited for existing town hall meetings
User impact: Users may receive a cancellation email when the attendees list is edited for existing town hall meetings
More info: To bypass the issue, meeting organizers should avoid making edits that only change the co-organizers, presenters, or attendees. Making other edits in addition to edits to these categories may allow meeting organizers to avoid the impact.
The town hall meetings aren’t canceled and users who receive this email can still attend the meeting as expected using the previously provided details.
Current status: We've completed reverting the offending deployment on a portion of impacted infrastructure and validated that the impact is remediated for users served by that infrastructure. We're continuing our reversion process and anticipate the impact will be resolved for the remaining impacted users by our next scheduled update.
Scope of impact: Some users who are added as attendees to Microsoft Teams town halls and have previously accepted the invitation may be impacted.
Start time: Wednesday, January 15, 2025, at 5:00 PM UTC
Root cause: A service change, meant to improve the editing experience for meeting invites by ensuring that only added or removed attendees receive notifications of the change to their email, is causing impact.
Next update by: Tuesday, March 18, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Mar 12 16:29:46 2025 |
|---|
| Description: | Title: Some users may receive a cancellation email when the attendees list is edited for existing town hall meetings
User impact: Users may receive a cancellation email when the attendees list is edited for existing town hall meetings
More info: To bypass the issue, meeting organizers should avoid making edits that only change the co-organizers, presenters, or attendees. Making other edits in addition to edits to these categories may allow meeting organizers to avoid the impact.
The town hall meetings aren’t canceled and users who receive this email can still attend the meeting as expected using the previously provided details.
Current status: We're continuing to reverse the offending service change and expect that the reversal process should complete and remediate impact by the time of our next communication update.
Scope of impact: Some users who are added as attendees to Microsoft Teams town halls and have previously accepted the invitation may be impacted.
Start time: Wednesday, January 15, 2025, at 5:00 PM UTC
Root cause: A service change, meant to improve the editing experience for meeting invites by ensuring that only added or removed attendees receive notifications of the change to their email, is causing impact.
Next update by: Monday, March 17, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Mar 12 16:03:29 2025 |
|---|
| Description: | Title: Some users may receive a cancellation email when the attendees list is edited for existing town hall meetings
User impact: Users may receive a cancellation email when the attendees list is edited for existing town hall meetings
More info: To bypass the issue, meeting organizers should avoid making edits that only change the co-organizers, presenters, or attendees. Making other edits in addition to edits to these categories may allow meeting organizers to avoid the impact.
The town hall meetings aren’t canceled and users who receive this email can still attend the meeting as expected using the previously provided details.
Current status: We've identified a service change, meant to improve the editing experience for meeting invites by ensuring that only added or removed attendees receive notifications of the change to their email, which is resulting in impact. We're reversing the problematic change to remediate the impact. Additionally, we’ve determined that the issue may occur when the attendees list is edited for existing town hall meetings, not just when distribution lists are added as attendees, and we’ve adjusted our “Title” and “User impact” fields accordingly.
Scope of impact: Some users who are added as attendees to Microsoft Teams town halls and have previously accepted the invitation may be impacted.
Start time: Wednesday, January 15, 2025, at 5:00 PM UTC
Root cause: A service change, meant to improve the editing experience for meeting invites by ensuring that only added or removed attendees receive notifications of the change to their email, is causing impact.
Next update by: Wednesday, March 12, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Mar 12 13:55:28 2025 |
|---|
| Description: | Title: Some users may receive cancellation email when distribution lists are added as attendees to town hall meetings
User impact: Users may receive cancellation email when distribution lists are added as attendees to town hall meetings.
More info: The town hall meetings aren’t canceled and users who receive this email can still attend the meeting as expected using the previously provided details.
Current status: We're continuing to review recent service changes to isolate the source of the issue and determine possible options to remediate the impact.
Scope of impact: Some users who are included in distribution lists that are added as attendees to Microsoft Teams town halls and have previously accepted the invitation may be impacted.
Next update by: Wednesday, March 12, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Mar 12 13:30:15 2025 |
|---|
| Description: | Title: Some users receive cancellation email when distribution lists are added as attendees to town hall meetings
User impact: Users receive cancellation email when distribution lists are added as attendees to Microsoft Teams town hall meetings.
More info: The town hall meetings aren’t canceled and users who receive this email can still attend the meeting as expected using the previously provided details.
Current status: We're reviewing recent service changes to determine whether any may be contributing to the impact.
Scope of impact: Your organization is affected by this event, and some users are impacted when distribution lists are added as attendees to Microsoft Teams town halls.
Next update by: Wednesday, March 12, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Mar 12 13:17:53 2025 |
|---|
| Description: | Title: Some users receive cancellation email when distribution lists are added as attendees to Town Hall meetings
User impact: Users receive cancellation email when distribution lists are added as attendees to Microsoft Teams Town Hall meetings.
More info: The Town Hall meeting isn't canceled and users who receive this email can still attend the meeting as expected using the previously provided details.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1034502 - Some users may be unable to access the Visual Creator agent in Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Thu Mar 13 23:45:00 2025 |
|---|
| End Time: | Mon Mar 17 18:00:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 17 18:47:20 2025 |
|---|
| Root Cause: | A recently implemented service change, designed to adjust the frequency that the Copilot service updates the agent build within the portion of storage infrastructure responsible for indexing agent builds, caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 17 18:47:20 2025 |
|---|
| Description: | Title: Some users may be unable to access the Visual Creator agent in Microsoft Copilot (Microsoft 365)
User impact: Users may have been unable to access the Visual Creator agent in Copilot.
Final status: We've confirmed through service health telemetry that reversing the service change remediated the impact.
Scope of impact: Some users who attempted to access agents in the Microsoft Copilot (Microsoft 365) may have been impacted.
Start time: Friday, March 14, 2025, at 3:45 AM UTC
End time: Monday, March 17, 2025, at 10:00 PM UTC
Root cause: A recently implemented service change, designed to adjust the frequency that the Copilot service updates the agent build within the portion of storage infrastructure responsible for indexing agent builds, caused impact.
Next steps:
- We're reviewing the offending service change to determine why it caused impact, so that we can prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 17 18:19:31 2025 |
|---|
| Description: | Title: Users can't access agents in Microsoft Copilot (Microsoft 365)
User impact: Users can't access agents in Copilot.
Current status: We've identified a recently implemented service change, designed to adjust the frequency with which the Copilot service updates the agent build within the portion of storage infrastructure responsible for indexing agent builds, that's causing impact. We're reversing the change to remediate the issue.
Scope of impact: Your organization is affected by this event, and any user attempting to access agents in the Microsoft Copilot (Microsoft 365) is impacted.
Root cause: A recently implemented service change, designed to adjust the frequency that the Copilot service updates the agent build within the portion of storage infrastructure responsible for indexing agent builds, is causing impact.
Next update by: Tuesday, March 18, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Mar 17 17:50:42 2025 |
|---|
| Description: | Title: Users can't access agents in Microsoft Copilot (Microsoft 365)
User impact: Users can't access agents in Copilot.
Current status: We're investigating a potential issue with Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1009881 - Admins’ block user policies created in the Microsoft Teams admin center or PowerShell aren’t blocking users as expected
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Feb 18 18:49:48 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 17 17:15:00 2025 |
|---|
| Root Cause: | A code issue present in the feature update is preventing admins' policies from blocking users, resulting in impact. |
|---|
| Next Update: | Thursday, March 20, 2025, at 7:00 PM UTC |
|---|
|
Details
| Time: | Mon Mar 17 13:31:00 2025 |
|---|
| Description: | Title: Admins’ block user policies created in the Microsoft Teams admin center or PowerShell aren’t blocking users as expected
User impact: Admins’ block user policies created in the Microsoft Teams admin center or PowerShell aren’t blocking users as expected.
Current status: We've determined that an additional round of validations were needed to ensure our code fix would correct the issue for all affected users and we now anticipate our deployment to begin on Thursday, March 20, 2025. Following the deployment of our code fix, we'll re-enable the User Block feature so it can be utilized through PowerShell and the Teams admin center. We anticipate that this final process should complete and fully resolve the issue for all affected admins by Friday, March 28, 2025. We aim to provide updates on our timeline to mitigation as they become available.
Scope of impact: Any admin attempting to create a policy in the Microsoft Teams admin center or PowerShell that blocks users is impacted.
Start time: Saturday, February 8, 2025, at 1:15 AM UTC
Root cause: A code issue present in the feature update is preventing admins' policies from blocking users, resulting in impact.
Next update by: Thursday, March 20, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Mar 4 15:05:00 2025 |
|---|
| Description: | Title: Admins’ block user policies created in the Microsoft Teams admin center or PowerShell aren’t blocking users as expected
User impact: Admins’ block user policies created in the Microsoft Teams admin center or PowerShell aren’t blocking users as expected.
Current status: While we're continuing our validations of our code fix to correct the issue, we anticipate that this should begin deployment on Monday, March 10, 2025, and complete by our next scheduled communications update. At that point, any policies that were created prior to our disabling of the impacted feature should begin to be enforced. Following the deployment of our code fix, we'll re-enable the User Block feature so it can be utilized through PowerShell and the Teams admin center. We anticipate that this final process should complete and fully resolve the issue for all affected admins on Friday, March 21, 2025.
Scope of impact: Any admin attempting to create a policy in the Microsoft Teams admin center or PowerShell that blocks users is impacted.
Start time: Saturday, February 8, 2025, at 1:15 AM UTC
Root cause: A code issue present in the feature update is preventing admins' policies from blocking users, resulting in impact.
Next update by: Monday, March 17, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Feb 18 18:58:17 2025 |
|---|
| Description: | Title: Admins’ block user policies created in the Microsoft Teams admin center or PowerShell aren’t blocking users as expected
User impact: Admins’ block user policies created in the Microsoft Teams admin center or PowerShell aren’t blocking users as expected.
Current status: We've identified that a code issue present in the feature update is preventing admins' policies from blocking users, resulting in impact. We're disabling this feature to prevent these faulty policies from being created and are internally validating a code fix to remediate impact. While this policy is disabled, admins will no longer be able to create these policies. The code fix validation process may take a few weeks to complete and we'll provide a timeline for remediation once one becomes available.
Scope of impact: Any admin attempting to create a policy in the Microsoft Teams admin center or PowerShell that blocks a users is impacted.
Start time: Saturday, February 8, 2025, at 1:15 AM UTC
Root cause: A code issue present in the feature update is preventing admins' policies from blocking users, resulting in impact.
Next update by: Tuesday, March 4, 2025, at 8:30 PM UTC
|
|---|
|
EX1026017 - Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Mar 7 16:54:35 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 17 15:46:50 2025 |
|---|
| Root Cause: | An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact. |
|---|
| Next Update: | Wednesday, March 19, 2025, at 8:00 PM UTC |
|---|
|
Details
| Time: | Mon Mar 17 15:46:50 2025 |
|---|
| Description: | Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following:
- OneDrive for Business content
- SharePoint Online site links
- Loop components
- Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web
- Classic Outlook
- Outlook desktop clients
- Outlook mobile
Current status: Due to the complexity of the aforementioned code fix designed to correct the authentication configuration, additional time is needed to complete its development. We expect to have a timeline for its completion by the time of our next update.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Root cause: An authentication misconfiguration on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows is causing impact.
Next update by: Wednesday, March 19, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Mar 13 13:36:44 2025 |
|---|
| Description: | Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following:
- OneDrive for Business content
- SharePoint Online site links
- Loop components
- Copilot output
Affected users may receive the following error: "Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web
- Classic Outlook
- Outlook desktop clients
- Outlook mobile
Current status: Development of our potential code fix is progressing as expected. In parallel, we're continuing our investigation into the previously mentioned authentication issue that we suspect is leading to impact to assist us in confirming our root cause theory.
Scope of impact: Some users attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Next update by: Monday, March 17, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 17:53:36 2025 |
|---|
| Description: | Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following:
- OneDrive for Business content
- SharePoint Online site links
- Loop components
- Copilot output
Affected users may see the following error -
"Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web
- Classic Outlook
- Outlook desktop clients
- Outlook mobile
Current status: We've identified an authentication issue on a portion of impacted infrastructure responsible for attaching Microsoft 365 data to email messages using the new Outlook for Windows. We're developing a code fix to resolve the underlying issue while simultaneously further reviewing the authentication issue to understand how it was introduced.
Scope of impact: Some user attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Next update by: Thursday, March 13, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Mar 7 18:06:36 2025 |
|---|
| Description: | Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following:
- OneDrive for Business content
- SharePoint Online site links
- Loop components
- Copilot output
Affected users are seeing the following error -
"Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- Outlook on the web
- Classic Outlook
- Outlook desktop clients
- Outlook mobile
Current status: Our initial review of support case information indicates that an authentication issue is preventing requests from completing as expected. We're working with affected users to gather additional browser captures of the issue in progress to develop a remediation strategy.
Scope of impact: Some user attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Next update by: Monday, March 10, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Mar 7 17:22:36 2025 |
|---|
| Description: | Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
More info: Impact includes, but is not limited to attaching the following:
- OneDrive for Business content
- SharePoint Online site links
- Loop components
- Copilot output
Affected users are seeing the following error -
"Need more information. To satisfy your organization's security policy, an additional step is required."
While we're working to remediate this issue, affected users can attach these items using other connection methods, including:
- classic Outlook on the web
- Outlook desktop clients
- Outlook mobile
Current status: We're reviewing support case details to better understand the impact scenario and determine our next steps.
Scope of impact: Some user attempting to attach certain Microsoft 365 content to email messages using new Outlook for Windows may be affected.
Next update by: Friday, March 7, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Mar 7 16:55:57 2025 |
|---|
| Description: | Title: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows
User impact: Users may see an error and can't attach Microsoft 365 data to email messages using the new Outlook for Windows.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1021490 - Users may be experiencing issues with accessing email messages on the iOS native mail app
| Status: | investigationSuspended |
|---|
| Start Time: | Sun Mar 2 19:10:00 2025 |
|---|
| End Time: | Sat Mar 15 10:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 17 15:19:05 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 17 15:16:30 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may have been experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may have been able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users weren't prompted but were still experiencing impact, they may have followed the steps in the following link:
https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e
The problem was specific to the native mail app on iOS devices. Microsoft Outlook for mobile was not affected and could have been used without issue.
Impacted users were encouraged to file a support ticket with Apple to provide valuable logging information to assist with our continued joint investigation with Apple into the source of impact.
Final status: We've confirmed after monitoring service health telemetry that errors associated with impact have reduced to pre-impact thresholds as of Saturday, March 15, 2025, at 2:00 PM UTC. This confirms that the majority of users are no longer affected by this event and that additional remediation efforts within the Microsoft-managed environment aren't required. As previously mentioned, users whose impact persists should follow the steps outlined in the "More info" of this communication to remediate impact.
Scope of impact: Some users accessing their email from the native iOS email app may have been affected.
Start time: Monday, March 3, 2025, at 12:10 AM UTC
Next steps:
- We’ll continue partnering with Apple to gain root cause insights, though this is a best-effort as the underlying issue didn’t reside within the Microsoft-managed environment.
- Follow the steps outlined in the “More info” of this communication in the event you’re still affected.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 13 14:58:08 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users aren't prompted but are still experiencing impact, please follow the steps in the following link:
https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e
The problem is specific to the native mail app on iOS devices. Microsoft Outlook for mobile is not affected and can be used without issue.
Impacted users are encouraged file a support ticket with Apple to provide valuable logging information to assist with our continued joint investigation with Apple into the source of impact.
Current status: After monitoring telemetry, we've confirmed that as affected users continue taking the actions outlined in the "More Info" section of this communication, errors associated with impact are reducing and thus additional remediation efforts within the Microsoft-managed environment aren’t required. We're continuing to monitor telemetry to ensure that errors and the number of affected users decreases to pre-event levels.
As previously mentioned, please follow the steps outlined in the "More info" of this communication to remediate impact.
Scope of impact: Some users accessing their email from the native iOS email app may be affected.
Next update by: Monday, March 17, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 15:02:56 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users aren't prompted but are still experiencing impact, please follow the steps in the following link:
https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e
Current status: While we continue to communicate with the third-party organization to isolate the source of impact, our telemetry indicates that the impact is receding as the affected users use the actions outlined in the article listed in the "More Info" section. We're monitoring the telemetry to ensure that the impact continues to decrease.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Thursday, March 13, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Mar 7 21:56:41 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users aren't prompted but are still experiencing impact, please follow the steps in the following link:
https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e
Current status: Our joint investigation with the third-party is progressing, though it's taking an extended period of time due to the complexity of the issue. We'll provide an update on the status of the investigation, including our findings if pertinent, by our next scheduled update.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 10, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Mar 7 14:43:38 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users aren't prompted but are still experiencing impact, please follow the steps in the following link:
https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e
Current status: Our joint investigation with the third-party to isolate the source for this event is ongoing. Please note that a support article outlining mitigation steps users can take while we work to address the underlying issue has been provided in the More info of this communication.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Saturday, March 8, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Mar 6 17:58:15 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact. If users aren't prompted but are still experiencing impact, please follow the steps in the following link:
https://support.microsoft.com/en-us/office/reconnecting-your-microsoft-365-account-to-apple-mail-83df246e-34d2-4dbb-8e37-23a90c13e16e
Current status: We're continuing our investigation with the third-party as we isolate the source for this event. Once the root cause is understood, we'll continue this collaboration toward a solution for this issue.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Friday, March 7, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Mar 5 21:02:15 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: Our collaboration efforts with the third-party are progressing as we continue to collect and analyze logs from affected users. We fully understand the significant impact this incident has had on those affected, and we are treating this matter with the utmost priority and consideration.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Thursday, March 6, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Mar 5 18:09:13 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: We're continuing to collaborate and investigate this issue with our third-party partner, along with collecting logs from a subset of affected users, to better understand the underlying root cause. This will help us determine what steps we can take to resolve the impact as swiftly as possible for affected users.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Thursday, March 6, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Mar 5 14:42:52 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: We're collaborating with our third-party partner and collecting logs from a subset of affected users to help us determine our next troubleshooting steps for remediating the impact.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Thursday, March 6, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Mar 4 22:20:01 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: After monitoring the affected infrastructure, we've determined that reverting the aforementioned update was not a viable mitigation strategy. We're now in the process of gather logs from a subset of affected users to refine our understanding of impact and formulate our remediation strategy.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Wednesday, March 5, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Mar 4 17:16:09 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: We're continuing to assess if the aforementioned update we reverted was responsible for impact, while simultaneously exploring other potential causes for this event.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Wednesday, March 5, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Mar 3 22:47:04 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: We've reverted a standard service update that we anticipate is resulting in impact. We're reaching out to a subset of affected users to gather a reproduction of impact, which will help validate that the issue is mitigated after the aforementioned change to the affected infrastructure.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Tuesday, March 4, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Mar 3 14:47:49 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: Our investigation into the authentication failures has so far revealed that there is an issue with the authentication tokens being sent from the iOS native mail app. We're continuing to investigate and determine the next steps to troubleshoot the issue.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Tuesday, March 4, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Mar 3 13:44:35 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: Our analysis of the diagnostics logs has identified authentication failures, which we're continuing to investigate so that we can isolate the source of the impact.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 10:35:05 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: We're progressing with our review of the aforementioned diagnostic logs to isolate the root cause and confirm our next steps. In parallel, we've received additional feedback from some affected users' Support resources that the steps provided in the above "More info" section have successfully alleviated the issue in the short-term.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 08:54:08 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: We're conducting analysis of authenticator logs from sample affected devices to confirm whether an issue with Microsoft 365 or a third-party application is responsible for causing impact.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 06:58:19 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: We've so far been unable to identify any Microsoft service updates which we believe are contributing towards impact. However, we've observed through analysis of telemetry that an accumulation of authentication token errors associated with a third-party application may be causing the issue. We're continuing our review of available diagnostic data to confirm the root cause.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 04:54:37 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: We're progressing with our review of recent scheduled service updates and diagnostic monitoring to isolate the root cause, before we begin assessing potential mitigation options.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 02:37:56 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Additionally, some users may be able to bypass the prompt to sign-in by clicking "edit settings" and then entering into the app.
Current status: We're continuing to assess and analyze our service logs, as well as monitor the service health and check for any changes that were made recently to the service, to understand the root cause of impact.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Mar 3 00:55:08 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Current status: The review of the failures and service logs is ongoing. We're continuing our analysis to help understand the root cause of impact.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Sun Mar 2 22:56:12 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Current status: We identified some failures present in our service logs and we're continuing to review these, along with additional support case details, to help identify the cause of impact and develop our next troubleshooting steps.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Sun Mar 2 20:53:06 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
More info: Users may be able to click "continue" when prompted and navigate back to re-entering their password to attempt to resolve impact.
Current status: We're continuing to review our service logs, along with provided screenshots, to better understand the cause of impact.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Sun Mar 2 19:49:55 2025 |
|---|
| Description: | Title: Users may be experiencing issues with accessing email messages on the iOS native mail app
User impact: Users may be experiencing issues with accessing email messages on the iOS native mail app.
Current status: We're reviewing our service logs to aid in understanding the cause of impact and to develop our next steps.
Scope of impact: Any user serviced by the affected infrastructure may experience issues with accessing email messages on the iOS native mail app.
Next update by: Monday, March 3, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Sun Mar 2 19:22:56 2025 |
|---|
| Description: | Title: Users are experiencing issues with accessing emails on the iOS native mail app
User impact: Users are experiencing issues with accessing emails on the iOS native mail app.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PL1032400 - Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner
| Status: | falsePositive |
|---|
| Start Time: | Thu Feb 20 11:55:00 2025 |
|---|
| End Time: | Sun Mar 16 13:15:00 2025 |
|---|
| Service: | Planner |
|---|
| Feature Group: | Planner |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 17 13:49:36 2025 |
|---|
| Root Cause: | A recent service update contained a code regression, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 17 13:39:55 2025 |
|---|
| Description: | Title: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner
User impact: Users experienced delays or errors when opening or interacting with some tasks in Microsoft Planner.
More info: This issue specifically affected users that were opening tasks which had comments associated with them, or that were interacting with comments within a task. Other tasks and interactions weren't impacted.
Final status: We've confirmed that our fix has fully saturated the affected environment, and we've verified with some affected users that the issue has been resolved.
Scope of impact: Your organization was affected by this event, and any user who opened or interacted with some tasks in Microsoft Planner was impacted.
Start time: Thursday, February 20, 2025, at 4:55 PM UTC
End time: Sunday, March 16, 2025, at 5:15 PM UTC
Root cause: A recent service update contained a code regression, which resulted in impact.
Next steps:
- We're reviewing our service update processes so we can better identify similar code regressions during our testing and development cycles and avoid comparable impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat Mar 15 11:49:54 2025 |
|---|
| Description: | Title: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner
User impact: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner.
More info: This issue specifically affects users that are opening tasks which have comments associated with them, or that are interacting with comments within a task. Other tasks and interactions aren't impacted.
Current status: We've confirmed that the fix has saturated to approximately 50 percent of the impacted environment, and some users may see relief at this time after closing and re-opening. While a remediation timeline isn't available at this time, we're attempting to isolate reporting users who have the fix to validate that the issue is no longer occurring.
Scope of impact: Your organization is affected by this event, and any user opening or interacting with some tasks in Microsoft Planner are impacted.
Start time: Thursday, February 20, 2025, at 4:55 PM UTC
Root cause: A recent service update contains a code regression, which is resulting in impact.
Next update by: Monday, March 17, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Mar 14 22:37:09 2025 |
|---|
| Description: | Title: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner
User impact: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner.
More info: This issue specifically affects users that are opening tasks which have comments associated with them, or that are interacting with comments within a task. Other tasks and interactions aren't impacted.
Current status: After reviewing the affected portions of service infrastructure, we've found a code regression contained in a recent standard service update. We've developed and deployed a targeted fix to repair the code regression and we're monitoring as the fix saturates throughout the affected environment. Additionally, we anticipate that a remediation timeline will be provided by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any user opening or interacting with some tasks in Microsoft Planner are impacted.
Start time: Thursday, February 20, 2025, at 4:55 PM UTC
Root cause: A recent standard service update contained a code regression, which is resulting in impact.
Next update by: Saturday, March 15, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Mar 14 20:02:52 2025 |
|---|
| Description: | Title: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner
User impact: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner.
More info: This issue specifically affects users that are opening tasks which have comments associated with them, or that are interacting with comments within a task. Other tasks and interactions aren't impacted.
Current status: We're continuing our investigation of the components of Microsoft Planner infrastructure responsible for facilitating the affected interactions in the impacted environment to assist us in isolating the root cause of the issue and identifying a path to remediation.
Scope of impact: Your organization is affected by this event, and any user opening or interacting with some tasks in Microsoft Planner are impacted.
Next update by: Saturday, March 15, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Fri Mar 14 19:17:53 2025 |
|---|
| Description: | Title: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner
User impact: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner.
More info: This issue specifically affects users that are opening tasks which have comments associated with them, or that are interacting with comments within a task. Other tasks and interactions aren't impacted.
Current status: We're investigating the components of Microsoft Planner infrastructure responsible for facilitating the affected interactions in the impacted environment to direct our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and any user opening or interacting with some tasks in Microsoft Planner are impacted.
Next update by: Saturday, March 15, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Mar 14 18:54:15 2025 |
|---|
| Description: | Title: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner
User impact: Users experience delays or errors when opening or interacting with some tasks in Microsoft Planner.
More info: This issue specifically affects users that are opening tasks which have comments associated with them, or that are interacting with comments within a task. Other tasks and interactions aren't impacted.
Current status: We're investigating a potential issue with the Microsoft Planner service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1015252 - Users with apostrophes in their surname in Exchange Online may be unable to search for other users
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Feb 5 11:50:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 17 13:08:12 2025 |
|---|
| Root Cause: | The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request |
|---|
| Next Update: | Wednesday, March 19, 2025, at 6:00 PM UTC |
|---|
|
Details
| Time: | Mon Mar 17 13:08:12 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: The fix to correct the offending URL is continuing to deploy, and the majority of the users should see the search functionality restored. Our earliest deployment estimates expect that the fix will reach the remaining affected users by our next update, though this may be subject to change as the deployment progresses.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request
Next update by: Wednesday, March 19, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Mar 14 13:20:47 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We've confirmed with affected users that the fix is successful in remediating this issue and we're continuing our staged rollout of the fix and are monitoring as it progresses. We will provide a complete remediation timeline once one is available.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Monday, March 17, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Mar 13 13:05:23 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: As we continue our efforts to confirm impact remediation with users who have already received the solution, we're expecting an updated timeline for the fix deployment and the remediation of impact for all users to be available by our next scheduled update.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Friday, March 14, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Mar 12 14:51:27 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We've initiated the deployment of our fix to users and are monitoring the deployment to ensure no further delays are encountered. As the fix beings to saturate, we'll reach out to subsets of reporting users as the deployment reaches them to verify they're experiencing relief and the issue is resolved.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Thursday, March 13, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 15:35:17 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We're resuming deployment of the fix, and we're monitoring closely to ensure no further delays are encountered. In parallel, we'll begin reaching out to a subset of affected users as the deployment reaches them to verify they're experiencing relief and the issue is resolved.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Wednesday, March 12, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Mar 6 16:17:36 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We’ve encountered some delays with the fix deployment. We’re continuously monitoring the situation to determine whether any action may be necessary for the deployment to resume, with the expectation that we’ll have a better understanding of the timeline for completion by our next update.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Monday, March 10, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 19:34:38 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We've validated the fix internally and have begun deploying it to the affected environments. We'll provide a timeline to resolution as one becomes available.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Thursday, March 6, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 15:40:05 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We're in the final stages of validating the additional fix to correct the URL and expect to have a release timeline by the next scheduled update.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Tuesday, March 4, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Feb 27 15:26:42 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We've completed the validation of our previously mentioned fix, but have determined that impact is ongoing after the fix is applied. We've developed a new fix which will replace the addresses leveraged by the Outlook service to generate the URLs used to perform searches, and we're validating this fix for efficacy in our testing environment before deploying it to the impacted infrastructure.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Monday, March 3, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 15:37:19 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: While we've completed the development of our fix, we're validating its efficacy in a test environment before we apply it broadly. We anticipate that our validation process should be complete by the time of our next scheduled communications update, at which point we'll be better equipped to provide an expected remediation timeline.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Thursday, February 27, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 18:26:00 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We've confirmed that the issue is the result of the URL utilized by the Outlook service when performing searches being malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request. We're preparing a fix that will force the URL to encode the User Principal Name (UPN) in the URL before sending the request to the service responsible for performing the search in order to resolve the issue. Once this code update is developed, we'll prepare a timeline for the deployment of the new code and impact resolution.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches is malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next update by: Tuesday, February 25, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 16:51:27 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: As we continue to investigate the potentially impacting change, we've identified further that the URL utilized by the Outlook service may be malformed, resulting in the impact. This may be due to the code not providing the full email address of users with apostrophes in their address when submitting the request. We're working to confirm this theory as well to determine the source of the issue and assist our remediation efforts.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Next update by: Tuesday, February 25, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Feb 24 14:36:29 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We've identified that the requests to authenticate are delivered to the responsible API as expected, however the API fails to respond. We suspect this may be due to a recent configuration change regarding how authentication requests are processed. We're reviewing this change while performing additional reproductions to confirm our theory and determine our next steps.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Next update by: Monday, February 24, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 12:49:23 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We've successfully reproduced the issue in our internal testing environment. After analyzing the results of our reproduction, we've confirmed the request to get search results fails during the authentication process. We're investigating the source of this failure to assist with determining the root of the issue and formulating potential remediation options.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Next update by: Monday, February 24, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 07:34:00 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We're analyzing HTTP Archive format (HAR) files to isolate the root cause and develop a mitigation plan. In parallel, we've requested provision of network trace logs and additional contextual details from your representatives to aid our investigation.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Next update by: Monday, February 24, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 06:28:18 2025 |
|---|
| Description: | Title: Users with apostrophes in their surname in Exchange Online may be unable to search for other users
User impact: Users with apostrophes in their surname in Exchange Online may be unable to search for other users.
Current status: We've identified that some impact associated with EX1012721 persists. We're reviewing the information provided in the support case to isolate the root cause, and determine the next steps needed to resolve this issue.
Scope of impact: This issue may impact any user with an apostrophe in their surname in Exchange Online that's searching for other users.
Next update by: Monday, February 24, 2025, at 1:30 PM UTC
|
|---|
|
DZ1027606 - Some users may have been unable to respond to Microsoft Defender automated investigation and response (AIR) actions
| Status: | serviceRestored |
|---|
| Start Time: | Thu Mar 6 12:51:00 2025 |
|---|
| End Time: | Wed Mar 12 20:05:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 17 08:07:21 2025 |
|---|
| Root Cause: | A recent change, applied to a section of infrastructure responsible for functionality related to AIR action responses, was inadvertently causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 17 08:07:21 2025 |
|---|
| Description: | Title: Some users may have been unable to respond to Microsoft Defender automated investigation and response (AIR) actions
User impact: Users may have been unable to respond to Microsoft Defender AIR actions.
More info: While we focused on remediation, users may have been able to leverage threat explorer or advanced hunting to circumvent the issue.
Final status: We've concluded the reversion of the change, and confirmed following an extended period monitoring the service environment that impact is remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Thursday, March 6, 2025, at 5:51 PM UTC
End time: Thursday, March 13, 2025, at 12:05 AM UTC
Root cause: A recent change, applied to a section of infrastructure responsible for functionality related to AIR action responses, was inadvertently causing impact.
Next steps:
- We're reviewing our standard service update procedures to reduce or avoid reoccurrence of similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 13 06:11:28 2025 |
|---|
| Description: | Title: Some users may be unable to respond to Microsoft Defender automated investigation and response (AIR) actions
User impact: Users may be unable to respond to Microsoft Defender AIR actions.
More info: While we focus on remediation, users may be able to leverage threat explorer or advanced hunting to circumvent the issue.
Current status: We've confirmed that the reversion has reached approximately 85% of the affected environment. We're expecting the reversion to complete and impact to be fully remediated by Monday, March 17, 2025.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, March 6, 2025, at 5:51 PM UTC
Root cause: A recent change, applied to a section of infrastructure responsible for functionality related to AIR action responses, is inadvertently causing impact.
Next update by: Monday, March 17, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Mar 11 08:51:08 2025 |
|---|
| Description: | Title: Some users may be unable to respond to Microsoft Defender automated investigation and response (AIR) actions
User impact: Users may be unable to respond to Microsoft Defender AIR actions.
More info: While we focus on remediation, users may be able to leverage threat explorer or advanced hunting to circumvent the issue.
Current status: We've confirmed that the fix to revert the change continues to deploy to the affected environment as expected.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, March 6, 2025, at 5:51 PM UTC
Root cause: A recent change, applied to a section of infrastructure responsible for functionality related to AIR action responses, is inadvertently causing impact.
Next update by: Thursday, March 13, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Mar 11 00:56:15 2025 |
|---|
| Description: | Title: Some users may be unable to respond to Microsoft Defender automated investigation and response (AIR) actions
User impact: Users may be unable to respond to Microsoft Defender AIR actions.
More info: While we focus on remediation, users may be able to leverage threat explorer or advanced hunting to circumvent the issue.
Current status: The fix to revert the change and remediate impact is in the process of deploying. This fix has already processed through and saturated a significant amount of the affected environment, with error rates decreasing. We anticipate this process may complete by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, March 6, 2025, at 5:51 PM UTC
Root cause: A recent change, applied to a section of infrastructure responsible for functionality related to AIR action responses, is inadvertently causing impact.
Next update by: Tuesday, March 11, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 10:09:16 2025 |
|---|
| Description: | Title: Some users may be unable to respond to Microsoft Defender automated investigation and response (AIR) actions
User impact: Users may be unable to respond to Microsoft Defender AIR actions.
More info: While we focus on remediation, users may be able to leverage threat explorer or advanced hunting to circumvent the issue.
Current status: We've identified that a recent change, applied to a section of infrastructure responsible for functionality related to AIR action responses, is inadvertently causing impact. We're preparing a fix to revert the change to remediate impact, and expect to be able to provide an approximate remediation time as part of our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, March 6, 2025, at 5:51 PM UTC
Root cause: A recent change, applied to a section of infrastructure responsible for functionality related to AIR action responses, is inadvertently causing impact.
Next update by: Tuesday, March 11, 2025, at 6:30 AM UTC
|
|---|
|
CP1031818 - Some users are unable to access Copilot in the Edge sidebar with Edge versions 133 and 132
| Status: | serviceRestored |
|---|
| Start Time: | Thu Mar 13 18:00:00 2025 |
|---|
| End Time: | Fri Mar 14 09:50:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Mar 14 14:38:12 2025 |
|---|
| Root Cause: | A recent change to the Copilot within the Edge sidebar feature, intended to update the Copilot platform and related to the ongoing retirement of Microsoft Search in Bing (previously communicated in the Message Center under MC961557), impacted users that are using older versions of Edge. The Copilot update had dependencies on new features that were contained within Edge versions 134 or later, resulting in compatibility issues with the previous Edge versions 132 and 133. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 14 10:16:21 2025 |
|---|
| Description: | Title: Some users are unable to access Copilot in the Edge sidebar with Edge versions 133 and 132
User impact: Users are unable to access Copilot in the Edge sidebar with Edge versions 133 and 132.
More info: Impacted users may see the error message "Update to the latest version of Edge to continue using Copilot."
Impacted users will need to update to Edge version 134 to continue using Copilot within the Edge browser.
Impacted users who have access to other Copilot applications can access Copilot using those methods.
Final status: After some testing, we’ve confirmed that we’re unable to revert the change, as this would result in users experiencing errors using Copilot within the Edge side bar as multiple dependencies no longer exist in the older Edge versions. To continue using Copilot within the Edge browser, users will need to update to Edge version 134. We’ll be closing this communication and we’ll be providing a new Message Center communication to provide more details about this required change. We’ll update this communication to provide the MC post ID once it is published.
Scope of impact: Impact is specific to users who leverage Edge versions 133 and 132.
Start time: Thursday, March 13, 2025, at 10:00 PM UTC
End time: Friday, March 14, 2025, at 1:50 PM UTC
Root cause: A recent change to the Copilot within the Edge sidebar feature, intended to update the Copilot platform and related to the ongoing retirement of Microsoft Search in Bing (previously communicated in the Message Center under MC961557), impacted users that are using older versions of Edge. The Copilot update had dependencies on new features that were contained within Edge versions 134 or later, resulting in compatibility issues with the previous Edge versions 132 and 133.
Next steps:
- We'll be publishing a Message Center communication explaining the required change.
- We're reviewing why this change communication was not published prior to the impacting change being deployed.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Fri Mar 14 09:20:12 2025 |
|---|
| Description: | Title: Some users are unable to access Copilot in the Edge sidebar with Edge versions 133 and 132
User impact: Users are unable to access Copilot in the Edge sidebar with Edge versions 133 and 132.
More info: Impacted users may see the error message "Update to the latest version of Edge to continue using Copilot."
This issue does not impact users who are using Edge Version 134.
Impacted users who have access to other Copilot applications can access Copilot using those methods.
Current status: We’ve identified that a recent change to the Copilot within the Edge sidebar feature, intended to update the Copilot platform and related to the ongoing retirement of Microsoft Search in Bing (previously communicated in the Message Center under MC961557), impacted users that are using older versions of Edge. The Copilot update had dependencies on new features that were contained within Edge versions 134 or later, resulting in compatibility issues with the previous Edge versions 132 and 133. We’re reviewing options to revert the update and are currently validating a rollback within a testing environment to confirm that it does not cause additional impact. Whilst this revert would mitigate impact, we still recommend that users update to the latest version of Edge as a best practice.
Scope of impact: Impact is specific to users who leverage Edge versions 133 and 132.
Next update by: Friday, March 14, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Mar 14 07:26:11 2025 |
|---|
| Description: | Title: Some users are unable to access Copilot in the Edge Sidebar with Edge Versions 133 and 132
User impact: Users are unable to access Copilot in the Edge Sidebar with Edge Versions 133 and 132.
More info: This issue does not impact users who are using Edge Version 134. Impacted users who have access to other Copilot applications are able to access Copilot using those methods.
Current status: We're reviewing support case details to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to access Copilot in the Edge Sidebar with Edge Versions 133 and 132.
Next update by: Friday, March 14, 2025, at 1:30 PM UTC
|
|---|
|
MP1005102 - Admins may be unable to export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Feb 13 11:42:34 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Mar 14 14:12:40 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Friday, March 28, 2025, at 6:00 PM UTC |
|---|
|
Details
| Time: | Fri Mar 14 14:12:40 2025 |
|---|
| Description: | Title: Admins may be unable to export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Exports are performed from the Microsoft Purview compliance portal. Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we work to remediate impact, we recommend affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition does not happen for each export attempt. Please rerun the job as a first step.
2. We recommend you start with batches 3GB or below. If the export is larger than 3GB, please break up the job into multiple parts to reduce the size.
3. If you still experience the issue, please try to use the features under the "Class eDiscovery" tab.
If you are still experiencing issues, please open a support case.
Current status: We're continuing our analysis of gathered logs and comparing other applications' handling of the affected .zip files to assist in the root cause investigation and develop a remediation strategy.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Friday, March 28, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Feb 28 13:23:36 2025 |
|---|
| Description: | Title: Admins may be unable to export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Exports are performed from the Microsoft Purview compliance portal. Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we work to remediate impact, we recommend affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition does not happen for each export attempt. Please rerun the job as a first step.
2. We recommend you start with batches 3GB or below. If the export is larger than 3GB, please break up the job into multiple parts to reduce the size.
3. If you still experience the issue, please try to use the features under the "Class eDiscovery" tab.
If you are still experiencing issues, please open a support case.
Current status: We've completed our internal validations and deployed the fix to the affected environments. We've confirmed through testing with affected users that the fix has restored the functionality of some third-party file archiving apps regardless of job size. We're continuing our analysis into the underlying cause of this issue, which will inform our next steps in developing a long-term fix to restore the functionality of all third-part file archiving apps.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Friday, March 14, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Feb 27 15:16:02 2025 |
|---|
| Description: | Title: Admins may be unable to export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we work to remediate impact, we recommend affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition does not happen for each export attempt. Please rerun the job as a first step.
2. We recommend you start with batches 3GB or below. If the export is larger than 3GB, please break up the job into multiple parts to reduce the size.
3. If you still experience the issue, please try to use the features under the "Class eDiscovery" tab.
If you are still experiencing issues, please open a support case.
Current status: As we continue our analysis into the source of the 3GB size limitations that are preventing admins from exporting data from eDiscovery (Classic) or eDiscovery (Preview), we're internally validating our fix that is designed to remediate the impact. We'll provide an updated timeline for our fix deployment once validations have completed.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Friday, February 28, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 15:40:56 2025 |
|---|
| Description: | Title: Admins may be unable to export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we work to remediate impact, we recommend affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition does not happen for each export attempt. Please rerun the job as a first step.
2. We recommend you start with batches 3GB or below. If the export is larger than 3GB, please break up the job into multiple parts to reduce the size.
3. If you still experience the issue, please try to use the features under the "Class eDiscovery" tab.
If you are still experiencing issues, please open a support case.
Current status: While we're continuing to develop a fix for the remaining impacted file archiving app, our investigation into the cause of the 3GB limitation is ongoing.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Thursday, February 27, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Feb 24 15:15:31 2025 |
|---|
| Description: | Title: Admins may be unable to export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we work to remediate impact, we recommend affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition does not happen for each export attempt. Please rerun the job as a first step.
2. We recommend you start with batches 3GB or below. If the export is larger than 3GB, please break up the job into multiple parts to reduce the size.
3. If you still experience the issue, please try to use the features under the "Class eDiscovery" tab.
If you are still experiencing issues, please open a support case.
Current status: We’ve completed deploying the fix to address file size limitations for the majority of impacted third-party file archiving apps. We've identified impact is still occurring for batches greater than 3GB for one specific third-party file archiving app. We’re further investigating the configurations of the impacted specific third-party file archiving app to isolate the root cause and formulate a secondary fix to resolve the underlying issue. Due to the complexity of the issue, we anticipate it may take several weeks for a secondary fix to be identified and developed and recommend impact users continue to use the workaround we provided in the More info section of the communication.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Wednesday, February 26, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Feb 21 16:12:33 2025 |
|---|
| Description: | Title: Admins may be unable to export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we work to remediate impact, we recommend affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition does not happen for each export attempt. Please rerun the job as a first step.
2. We recommend you start with batches 3GB or below. If the export is larger than 3GB, please break up the job into multiple parts to reduce the size.
3. If you still experience the issue, please try to use the features under the "Class eDiscovery" tab.
If you are still experiencing issues, please open a support case.
Current status: We’ve developed and are initiating the deployment of a fix to address some file size limitations that we’ve confirmed are impacting some specific third-party file archiving apps. We’re continuing to review various reproductions of the issue occurring with different configurations and applications to develop a fix that will fully resolve the functionality for any scenario.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Monday, February 24, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Feb 20 14:03:22 2025 |
|---|
| Description: | Title: Admins can’t export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we work to remediate impact, we recommend affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition does not happen for each export attempt. Please rerun the job as a first step.
2. We recommend you start with batches 3GB or below. If the export is larger than 3GB, please break up the job into multiple parts to reduce the size.
3. If you still experience the issue, please try to use the features under the "Class eDiscovery" tab.
If you are still experiencing issues, please open a support case.
Current status: After collecting additional captures from affected admins, we've focused our investigation to a possible metadata configuration problem which could be preventing exports for admins from eDiscovery (Classic) or eDiscovery (Preview). We're further analyzing a reproduction of the problem alongside the associated metadata configurations to help us confirm the source for the problem and to determine our troubleshooting steps for remediating the impact.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Friday, February 21, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Feb 18 13:45:10 2025 |
|---|
| Description: | Title: Admins can’t export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we work to remediate impact, we recommend affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition does not happen for each export attempt. Please rerun the job as a first step.
2. We recommend you start with batches 3GB or below. If the export is larger than 3GB, please break up the job into multiple parts to reduce the size.
3. If you still experience the issue, please try to use the features under the "Class eDiscovery" tab.
If you are still experiencing issues, please open a support case.
Current status: We've been unable to identify the root cause of the event at this time. We're working with affected admins to gather additional captures to further narrow down what within the service is causing impact to occur, which will inform our next steps regarding impact remediation.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Thursday, February 20, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Feb 13 14:32:36 2025 |
|---|
| Description: | Title: Admins can’t export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we work to remediate impact, we recommend affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition does not happen for each export attempt. Please rerun the job as a first step.
2. We recommend you start with batches 3GB or below. If the export is larger than 3GB, please break up the job into multiple parts to reduce the size.
3. If you still experience the issue, please try to use the features under the "Class eDiscovery" tab.
If you are still experiencing issues, please open a support case.
Current status: We're continuing our analysis of provided captures while expanding our investigation to include recent service updates which may be contributing to impact.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Tuesday, February 18, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Feb 13 12:07:01 2025 |
|---|
| Description: | Title: Admins can’t export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may be unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
While we're working to remediate this issue, affected admins can work around this issue by using smaller export batches from eDiscovery (Classic).
Current status: We're continuing our analysis of admin provided browser captures and service side telemetry to assist in the root cause investigation.
Scope of impact: Any admins exporting data from eDiscovery may be affected.
Next update by: Thursday, February 13, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Feb 13 11:43:39 2025 |
|---|
| Description: | Title: Admins can’t export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins can’t export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview).
More info: Admins see that eDiscovery (Preview) is exporting corrupted .zip files, and exports are failing in eDiscovery (Classic).
Current status: We're investigating a potential issue with Microsoft Purview and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1029739 - Users may be intermittently unable to leverage Microsoft Copilot (Microsoft 365) agents through any connection method
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 27 11:00:00 2025 |
|---|
| End Time: | Thu Mar 13 23:42:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Mar 14 01:25:34 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 14 01:24:27 2025 |
|---|
| Description: | Title: Users may be intermittently unable to leverage Microsoft Copilot (Microsoft 365) agents through any connection method
User impact: Users may have intermittently been unable to leverage Copilot agents through any connection method.
More info: Users may have noticed that the Copilot agent either failed to load or disappeared after initially appearing in Copilot.
If accessing Copilot through a web browser, users may refresh the browser to experience relief. If accessing through the Teams client, users may sign out and sign back in.
Final status: We've completed deploying our fix to the service environment and have confirmed through telemetry that impact was successfully remediated. Users may need to refresh their browser if accessing Copilot through a web browser or sign out and sign back in if accessing through the Teams client to experience relief.
Scope of impact: This issue may have affected any user that attempted to leverage Copilot agents.
Start time: Thursday, February 27, 2025, at 4:00 PM UTC
End time: Friday, March 14, 2025, at 3:42 AM UTC
Preliminary root cause: A recent change introduced a misalignment with the mechanism responsible for allowing the service to parse models between systems, resulting in impact.
Next steps:
- We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Mar 13 13:03:15 2025 |
|---|
| Description: | Title: Users may be intermittently unable to leverage Microsoft Copilot (Microsoft 365) agents through any connection method
User impact: Users may be intermittently unable to leverage Copilot agents through any connection method.
More info: Users may notice that the Copilot agent either fails to load or disappears after initially appearing in Copilot.
If accessing Copilot through a web browser, users may refresh the browser to experience relief. If accessing through the Teams client, users may sign out and sign back in.
Current status: We've started the deployment of our fix to the entire service environment and have confirmed it is 85 percent complete. Users will experience relief as the fix is rolled out. We expect the deployment to be complete for all users by our next scheduled update.
Scope of impact: This issue may affect any user attempting to leverage Copilot agents.
Start time: Thursday, February 27, 2025, at 4:00 PM UTC
Preliminary root cause: A recent change introduced a misalignment with the mechanism responsible for allowing the service to parse models between systems, resulting in impact.
Next update by: Friday, March 14, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Wed Mar 12 23:13:07 2025 |
|---|
| Description: | Title: Users may be intermittently unable to leverage Microsoft Copilot (Microsoft 365) agents through any connection method
User impact: Users may be intermittently unable to leverage Copilot agents through any connection method.
More info: Users may notice that the Copilot agent either fails to load or disappears after initially appearing in Copilot.
Current status: We have validated efficacy of our fix within a small portion of our service infrastructure. We are preparing the entirety of our service environment for deployment which we expect to initiate within the next hour. We expect the deployment to complete within the next 36 hours.
Scope of impact: This issue may affect any user attempting to leverage Copilot agents.
Start time: Thursday, February 27, 2025, at 4:00 PM UTC
Preliminary root cause: A recent change introduced a misalignment with the mechanism responsible for allowing the service to parse models between systems, resulting in impact.
Next update by: Thursday, March 13, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Mar 12 17:28:21 2025 |
|---|
| Description: | Title: Users may be intermittently unable to leverage Microsoft Copilot (Microsoft 365) agents through any connection method
User impact: Users may be intermittently unable to leverage Copilot agents through any connection method.
More info: Users may notice that the Copilot agent either fails to load or disappears after initially appearing in Copilot.
Current status: Deployment of our fix to the subset of the affected service environment is proceeding as expected. We anticipate the deployment to the subset of infrastructure will be complete by our next scheduled update.
Scope of impact: This issue may affect any user attempting to leverage Copilot agents.
Start time: Thursday, February 27, 2025, at 4:00 PM UTC
Preliminary root cause: A recent change introduced a misalignment with the mechanism responsible for allowing the service to parse models between systems, resulting in impact.
Next update by: Thursday, March 13, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Mar 12 15:51:30 2025 |
|---|
| Description: | Title: Users may be intermittently unable to leverage Microsoft Copilot (Microsoft 365) agents through any connection method
User impact: Users may be intermittently unable to leverage Copilot agents through any connection method.
More info: Users may notice that the Copilot agent either fails to load or disappears after initially appearing in Copilot.
Current status: We've started deploying our fix to a subset of the affected service environment, which we'll monitor to confirm resolves impact as expected prior to deploying broadly.
Scope of impact: This issue may affect any user attempting to leverage Copilot agents.
Start time: Thursday, February 27, 2025, at 4:00 PM UTC
Preliminary root cause: A recent change introduced a misalignment with the mechanism responsible for allowing the service to parse models between systems, resulting in impact.
Next update by: Wednesday, March 12, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Mar 12 15:32:02 2025 |
|---|
| Description: | We've finalized the validation of our code fix and are now preparing to initiate its deployment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Mar 12 14:32:18 2025 |
|---|
| Description: | Title: Users may be intermittently unable to leverage Microsoft Copilot (Microsoft 365) agents through any connection method
User impact: Users may be intermittently unable to leverage Copilot agents through any connection method.
More info: Users may notice that the Copilot agent either fails to load or disappears after initially appearing in Copilot.
Current status: We've identified a misalignment in the server where agents are not able to parse the models. We've developed and completed the initial testing of our code fix and are finalizing its validation before deploying it to the affected service environment.
Scope of impact: This issue may affect any user attempting to leverage Copilot agents.
Preliminary root cause: There is a misalignment with the mechanism responsible for allowing the service to parse models between systems, resulting in impact.
Next update by: Wednesday, March 12, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Mar 12 14:08:54 2025 |
|---|
| Description: | Title: Users may be unable to leverage Microsoft Copilot (Microsoft 365) agents through any Copilot connection method
User impact: Users may be unable to leverage Copilot agents through any Copilot connection method.
More info: Users may notice that the Copilot agent either fails to load or disappears after initially appearing in Copilot.
Current status: We're reviewing support case details and recent service updates to determine the source of impact.
Scope of impact: This issue may affect any user attempting to leverage Copilot agents.
Next update by: Wednesday, March 12, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Mar 12 13:55:53 2025 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Copilot (Microsoft 365)
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft Copilot (Microsoft 365) and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1023316 - Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 19 00:27:00 2025 |
|---|
| End Time: | Thu Mar 13 17:30:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 13 20:09:03 2025 |
|---|
| Root Cause: | A recent configuration change to the component of infrastructure responsible for facilitating access to the Cloud Policies page introduced a logic error that was preventing the page from loading correctly. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 13 20:04:33 2025 |
|---|
| Description: | Title: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Admins may have seen an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Affected admins received the following error message when they attempted to access the Cloud Policies page: "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
The error didn’t prevent admins from accessing the page and they could still have leveraged all the functions on the Cloud Policies page as expected.
Final status: We've completed deploying a code fix and validated with internal testing that the impact is remediated.
Scope of impact: Any admin that attempted to access the Cloud Policies page in the Microsoft Intune admin center may have been impacted.
Start time: Wednesday, February 19, 2025, at 5:27 AM UTC
End time: Thursday, March 13, 2025, at 9:30 PM UTC
Root cause: A recent configuration change to the component of infrastructure responsible for facilitating access to the Cloud Policies page introduced a logic error that was preventing the page from loading correctly.
Next steps:
- We're further reviewing the recent configuration change to understand how the logic error was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 10 20:03:58 2025 |
|---|
| Description: | Title: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Affected admins receive the follwing error message when accessing the Cloud Policies page: "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
The error doesn’t prevent admins from accessing the page and they can still leverage all the functions on the Cloud Policies page as expected.
Current status: Our investigation has determined that a recent configuration change to the component of infrastructure responsible for facilitating access to the Cloud Policies page introduced a logic error that's preventing the page from loading correctly, leading to impact. We've developed and begun deployment of a fix to correct this error, and we're aiming to provide a timeline for full deployment and remediation in our next scheduled communications update.
Scope of impact: Any admin attempting to access the Cloud Policies page in the Microsoft Intune admin center is impacted.
Root cause: A recent configuration change to the component of infrastructure responsible for facilitating access to the Cloud Policies page introduced a logic error that's preventing the page from loading correctly, leading to impact.
Next update by: Friday, March 14, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Mar 7 19:52:39 2025 |
|---|
| Description: | Title: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Users receive an error message that states, "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
The error doesn’t prevent admins from accessing the page and they can still leverage all the functions on the Cloud Policies page as expected.
Current status: We're continuing our analysis of the previously mentioned service update that's potentially contributing to impact to assist us in isolating the root cause of the issue and identifying a path to remediation.
Scope of impact: Any admin attempting to access the Cloud Policies page in the Microsoft Intune admin center is impacted.
Next update by: Tuesday, March 11, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Mar 7 13:51:56 2025 |
|---|
| Description: | Title: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Users receive an error message that states, "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
The error doesn’t prevent admins from accessing the page and they can still leverage all the functions on the Cloud Policies page as expected.
Current status: We're narrowing down the origin of the error message and continuing to analyze the previously mentioned service update so we can confirm both the source for this event along with our next steps for remediating the impact.
Scope of impact: Any admin attempting to access the Cloud Policies page in the Microsoft Intune admin center is impacted.
Next update by: Saturday, March 8, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Mar 6 13:31:40 2025 |
|---|
| Description: | Title: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Users receive an error message that states, "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
The error doesn’t prevent admins from accessing the page and they can still leverage all the functions on the Cloud Policies page as expected.
Current status: We're progressing with our analysis into the previously mentioned service update so we can confirm both the source for this event along with our next steps for remediating the impact.
Scope of impact: Any admin attempting to access the Cloud Policies page in the Microsoft Intune admin center is impacted.
Next update by: Friday, March 7, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Mar 5 20:54:31 2025 |
|---|
| Description: | Title: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Users receive an error message that states, "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
The error doesn’t prevent admins from accessing the page and they can still leverage all the functions on the Cloud Policies page as expected.
Current status: Our review of the previously mentioned HAR logs has helped us isolate a potential change in how the Microsoft Intune Iframe for Microsoft 365 applications portion of the Microsoft Endpoint Manager admin center page is calling the Cloud policies. We're analyzing this suspected change to determine if it's the culprit behind the impact and to develop a strategy for remediating the issue.
Scope of impact: Any admin attempting to access the Cloud Policies page in the Microsoft Intune admin center is impacted.
Next update by: Thursday, March 6, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Mar 5 13:22:43 2025 |
|---|
| Description: | Title: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Users receive an error message that states, "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
The error doesn’t prevent admins from accessing the page and they can still leverage all the functions on the Cloud Policies page as expected.
Current status: We've been unable to identify the root cause of the event at this time. We're continuing our review of HAR network trace logs to progress our investigation into the underlying cause of this issue, so we can determine our next steps regarding impact remediation.
Scope of impact: Any admin attempting to access the Cloud Policies page in the Microsoft Intune admin center is impacted.
Next update by: Thursday, March 6, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Mar 4 19:43:42 2025 |
|---|
| Description: | Title: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Users receive an error message that states "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
Admins can still leverage all the functions on the Cloud Policies page as expected.
Current status: We're continuing our review of the latest gathered HTTP Archive format (HAR) network trace logs to gain further insight into the underlying source of impact and determine our next investigative steps.
Scope of impact: Any admin attempting to access the Cloud Policies page in the Microsoft Intune admin center is impacted.
Next update by: Wednesday, March 5, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Mar 4 14:51:55 2025 |
|---|
| Description: | Title: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Admins may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Users receive an error message that states "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
Admins can still leverage all the functions on the Cloud Policies page as expected.
Current status: We're reviewing HTTP Archive format (HAR) logs to identify why admins are seeing this error in the Cloud Policies page in the Microsoft Intune admin center.
Scope of impact: Any admin attempting to access the Cloud Policies page in the Microsoft Intune admin center is impacted.
Next update by: Wednesday, March 5, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Tue Mar 4 14:29:26 2025 |
|---|
| Description: | Title: Users may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center
User impact: Users may see an error when accessing the Cloud Policies page in the Microsoft Intune admin center.
More info: Users receive an error message that states "Couldn't retrieve data for 'OfficeSettingsContainer'. Use '00000000-0000-0000-0000-000000000000' to report this issue to Microsoft."
Users can still leverage all the functions on the Cloud Policies page as expected.
Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1027699 - Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 9 15:36:00 2025 |
|---|
| End Time: | Thu Mar 13 16:15:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 13 18:07:41 2025 |
|---|
| Root Cause: | A service update to a portion of service infrastructure that facilitates identification of which add-ins are enabled for users in Outlook on the web and the Outlook desktop client contained an impacting code issue. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 13 18:01:24 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may have seen add-ins in Outlook desktop and Outlook on the web that weren't installed or removable.
More info: As a temporary workaround, affected users could have disabled ‘Show Apps in Outlook’ for relief, but this only applied to classic Outlook on Windows. There was no workaround for Outlook on the web, new Outlook on Windows, or Outlook for Mac.
Final status: Following the deployment of our fix, our internal tests and validations from affected users have confirmed that the code problems have been addressed, and that impact has been remediated.
Scope of impact: Some users may have seen add-ins in the Outlook desktop client and Outlook on the web which weren't installed and couldn't be removed.
Start time: Thursday, January 9, 2025, at 8:36 PM UTC
End time: Thursday, March 13, 2025, at 8:15 PM UTC
Root cause: A service update to a portion of service infrastructure that facilitates identification of which add-ins are enabled for users in Outlook on the web and the Outlook desktop client contained an impacting code issue.
Next steps:
- We're further analyzing the offending service update so we can help identify similar issues during our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 13 17:48:42 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may have seen add-ins in Outlook desktop and Outlook on the web that weren't installed or removable.
More info: As a temporary workaround, affected users could have disabled ‘Show Apps in Outlook’ for relief, but this only applied to classic Outlook on Windows. There was no workaround for Outlook on the web, new Outlook on Windows, or Outlook for Mac.
Final status: Following the deployment of our fix, our internal tests and validations from affected users have confirmed that the code problems have been addressed, and that impact has been remediated.
Scope of impact: Some users may have seen add-ins in the Outlook desktop client and Outlook on the web which weren't installed and couldn't be removed.
Start time: Thursday, January 9, 2025, at 8:36 PM UTC
End time: Thursday, March 13, 2025, at 8:15 PM UTC
Root cause: A service update to a portion of service infrastructure that facilitates identification of which add-ins are enabled for users in Outlook on the web and the Outlook desktop client contained an impacting code issue.
Next steps:
- We're further analyzing the offending service update so we can help identify similar issues during our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 13 13:44:07 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable.
More info: As a temporary workaround, affected users can disable ‘Show Apps in Outlook’ for relief, but this only applies to classic Outlook on Windows. There is no workaround for Outlook on the web, new Outlook on Windows, or Outlook for Mac.
Current status: We've completed the development of our code fix, and we’ve confirmed through our testing and validation that it successfully remediates the issue. We've initiated the deployment of the fix and are monitoring as it saturates through the affected environment to confirm successful impact remediation.
Scope of impact: Some users may see add-ins in the Outlook desktop client and Outlook on the web which aren't installed and can't be removed.
Start time: Thursday, January 9, 2025, at 8:36 PM UTC
Root cause: A service update to a portion of service infrastructure that facilitates identification of which add-ins are enabled for users in Outlook on the web and the Outlook desktop client contains a code issue, resulting in impact.
Next update by: Thursday, March 13, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Mar 12 14:24:54 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable.
More info: As a temporary workaround, affected users can disable ‘Show Apps in Outlook’ for relief, but this only applies to classic Outlook on Windows. There is no workaround for Outlook on the web, new Outlook on Windows, or Outlook for Mac.
Current status: We're continuing to develop a fix for the code issue and will provide a timeline for completing the development process once it's available.
Scope of impact: Some users may see add-ins in the Outlook desktop client and Outlook on the web which aren't installed and can't be removed.
Start time: Thursday, January 9, 2025, at 8:36 PM UTC
Root cause: A service update to a portion of service infrastructure that facilitates identification of which add-ins are enabled for users in Outlook on the web and the Outlook desktop client contains a code issue, resulting in impact.
Next update by: Thursday, March 13, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Mar 11 18:17:16 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable.
More info: As a temporary workaround, affected users can disable ‘Show Apps in Outlook’ for relief, but this only applies to classic Outlook on Windows. There is no workaround for Outlook on the web, new Outlook on Windows, or Outlook for Mac.
Current status: We've completed our review of the HAR log traces and identified that a service update to a portion of service infrastructure that facilitates identification of which add-ins are enabled for users in Outlook on the web and the Outlook desktop client contains a code issue, resulting in impact. We're developing a fix to address the code issue, and we'll aim to provide a timeline for the development process to complete by our next scheduled communications update.
Scope of impact: Some users may see add-ins in the Outlook desktop client and Outlook on the web which aren't installed and can't be removed.
Start time: Thursday, January 9, 2025, at 8:36 PM UTC
Root cause: A service update to a portion of service infrastructure that facilitates identification of which add-ins are enabled for users in Outlook on the web and the Outlook desktop client contains a code issue, resulting in impact.
Next update by: Wednesday, March 12, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Mar 11 17:26:02 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable.
Current status: We've continuing to review the fresh HAR log traces in parallel with recent changes made to the service to progress our investigation into the root cause of this event, so we can formulate a mitigation strategy to resolve the issue.
Scope of impact: Some users may see add-ins in the Outlook desktop client and Outlook on the web which aren't installed and can't be removed.
Next update by: Tuesday, March 11, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Mar 11 15:15:03 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable.
Current status: We're reviewing the fresh HAR log traces provided by your representatives to progress our investigation into the underlying cause of this issue, so we can determine our next steps regarding impact remediation.
Scope of impact: Some users may see add-ins in the Outlook desktop client and Outlook on the web which aren't installed and can't be removed.
Next update by: Tuesday, March 11, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Mar 10 14:04:25 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable.
Current status: Our review of the code flow has not identified any issues that could be occurring at this time. We're awaiting additional information requested from your organization's representatives, including HTTP Archive format (HAR) log traces captured from the Exchange admin center when setting add-ins to be deployed using the Available method, and a Fiddler trace captured from the Outlook desktop client by an affected user to assist our efforts to identify the source of the issue and formulate remediation strategies.
Scope of impact: Some users may see add-ins in the Outlook desktop client and Outlook on the web which aren't installed and can't be removed.
Next update by: Tuesday, March 11, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Mar 10 11:51:32 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable.
Current status: We're reaching out to request Fiddler trace logs capturing impact from affected users in the Outlook desktop client, instead of Outlook on the web, for insight into how APIs are responding to calls to populate add-ins.
Scope of impact: Some users may see add-ins in the Outlook desktop client and Outlook on the web which aren't installed and can't be removed.
Next update by: Monday, March 10, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 11:30:39 2025 |
|---|
| Description: | Title: Some users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable
User impact: Users may see add-ins in Outlook desktop and Outlook on the web that aren't installed or removable.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1027537 - Some users may be unable to search or see recommendations in multiple Microsoft 365 services
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Mar 10 08:43:47 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 13 17:51:37 2025 |
|---|
| Root Cause: | Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic. |
|---|
| Next Update: | Wednesday, March 19, 2025, at 11:00 PM UTC |
|---|
|
Details
| Time: | Thu Mar 13 17:51:37 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We’ve initiated the deployment of our fix and we’re monitoring its progress to ensure it completes as expected to resolve this issue by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Wednesday, March 19, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Mar 11 20:22:45 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We've completed validating our fix and confirmed that it successfully remediates impact without causing further service complications. We're preparing to deploy the fix to the impacted environment and anticipate being able to provide a resolution timeline by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Thursday, March 13, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Mar 11 18:28:40 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We're continuing our analysis and testing of further optimizations in a subset of the affected environments to confirm these are remediating impact as planned before implementing them across the remaining affected environments. We aim to provide a timeline for resolution as one becomes available.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Wednesday, March 12, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Mar 11 14:52:20 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We've completed the implementation of further optimizations in a subset of the affected environments and we're conducting testing to confirm these are remediating impact as planned before implementing them across the remaining affected environments.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Wednesday, March 12, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Mar 11 10:26:09 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We're continuing our efforts to implement further optimizations in affected environments to fully remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Tuesday, March 11, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Mar 11 08:31:32 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We're implementing further optimizations in affected environments to fully resolve impact. Additionally, monitoring continues to indicate that impact is subsiding.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Tuesday, March 11, 2025, at 2:30 PM UTC
|
|---|
|
| Time: | Mon Mar 10 18:59:20 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We're continuing to see impact subsiding, as we suspect the issue is a result of higher than expected inbound request traffic. We'll continue to monitor the service telemetry during a period of higher traffic to assess whether additional actions need to be taken to resolve impact. We're also continuing to work to gather additional logs to better understand how we can implement a permanent remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Tuesday, March 11, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Mon Mar 10 17:12:44 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We’re continuing to monitor service telemetry as the issue appears to have largely subsided as a result of lessened overall traffic. The process of pulling additional logs from the affected subset of service infrastructure to further our root cause investigation and formulate permanent remediation plan is ongoing.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Monday, March 10, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 15:07:10 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We’ve observed continued improvement to service health as a result of our initial optimizations, coupled with less traffic occurring during off-hours in one of the affected regions. We’re pulling some additional logs from the affected subset of service infrastructure to further our understanding of what we suspect is a memory regression that’s leading to the impact, and to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Monday, March 10, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 13:06:32 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
- SharePoint Online
Current status: We’re monitoring service telemetry to ensure we’re seeing continued signs of improvement to service health. Additionally, we’re analyzing affected subsets of service infrastructure to understand what’s causing higher-than-expected resource utilization and determine whether any additional remediation steps are required.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services are operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Monday, March 10, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 10:37:32 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include, but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
Current status: We're continuing to monitor the affected environment for signs of recovery. In parallel, we're applying additional infrastructure optimizations to expedite remediation.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: A specific processing component, responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services, is operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Monday, March 10, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 08:44:48 2025 |
|---|
| Description: | Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may be unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services include, but aren't limited to:
- Outlook on the web and desktop client
- Microsoft Teams
- OneDrive for Business
Current status: We've identified that a specific processing component, responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services, is operating below acceptable thresholds due to an unexpected increase in inbound request traffic. We've applied performance optimizations and restarted affected infrastructures to reduce the incoming load and remediate impact, and we're actively monitoring the environment for signs of recovery.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
Root cause: A specific processing component, responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services, is operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next update by: Monday, March 10, 2025, at 3:00 PM UTC
|
|---|
|
MO1031068 - Users may be unable to load Office Scripts in Excel or Excel for the web
| Status: | serviceRestored |
|---|
| Start Time: | Thu Mar 13 13:30:00 2025 |
|---|
| End Time: | Thu Mar 13 16:33:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 13 17:16:34 2025 |
|---|
| Root Cause: | A feature update to improve Office Scripts resilience, which was in the process of rolling out, had caused an adverse response for Office Scripts scenarios. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 13 17:05:03 2025 |
|---|
| Description: | Title: Users may be unable to load Office Scripts in Excel or Excel for the web
User impact: Users may have been unable to load Office Scripts in Excel or Excel for the web.
More info: Users encountering this issue may have seen an error that stated, "Office Scripts service is unreachable. Please check network and firewall settings."
Final status: We've disabled the update deployment, which was a feature for service resilience improvements that we identified had adversely affected the backing service for Office Scripts, and confirmed through telemetry and testing that this has resolved the impact.
Scope of impact: This may have affected users served through East US, West US, North Europe, West Europe, and Southeast Asia.
Start time: Thursday, March 13, 2025, at 5:30 PM UTC
End time: Thursday, March 13, 2025, at 8:33 PM UTC
Root cause: A feature update to improve Office Scripts resilience, which was in the process of rolling out, had caused an adverse response for Office Scripts scenarios.
Next steps:
- We're continuing to review the feature in conjunction with the impact it introduced to Office Scripts to improve our understanding of how it led to this problem. Based on our findings we'll implement additional testing and validation measures in future feature deployments to prevent similar impact from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 13 16:28:36 2025 |
|---|
| Description: | Title: Users may be unable to load Office Scripts in Excel or Excel for the web
User impact: Users may be unable to load Office Scripts in Excel or Excel for the web.
More info: Users encountering this issue may see an error that states, "Office Scripts service is unreachable. Please check network and firewall settings."
Current status: We're seeing an increase in errors and a drop in traffic for the Office Scripts service that correlate with the reports of impact. We're proactively taking steps to disable a recent update to assess if that helps to address the issue while reviewing available data to understand the underlying cause of the impact.
Scope of impact: This may affect users served through East US, West US, North Europe, West Europe, and Southeast Asia may be affected.
Next update by: Thursday, March 13, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Mar 13 15:47:55 2025 |
|---|
| Description: | Title: Users may be unable to load Office Scripts in Excel or Excel for the web
User impact: Users may be unable to load Office Scripts in Excel or Excel for the web.
More info: Users encountering this issue may see an error that states, "Office Scripts service is unreachable. Please check network and firewall settings."
Current status: We're investigating a potential issue with Office Scripts and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
EX1027675 - Users may encounter delays or failures when sending or receiving email messages in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Fri Mar 7 12:30:00 2025 |
|---|
| End Time: | Thu Mar 13 13:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Mar 13 14:05:58 2025 |
|---|
| Root Cause: | A recent service update, intended to improve our message transport services, introduced a code issue that resulted in impact for a portion of service infrastructure. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 13 14:05:58 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may have encountered delays or failures when sending or receiving email messages in Exchange Online.
Final status: We've identified that the remaining impact relates to a separate issue which exhibits a nearly identical impact to users. We've confirmed that our fix completed in the affected environment and impact for this issue is remediated based on our internal monitoring. We'll continue investigating the root cause of the remaining impact and supplying further updates in EX1030895.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving some email in Exchange Online may have been affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
End time: Thursday, March 13, 2025, at 5:00 PM UTC
Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that resulted in impact for a portion of service infrastructure.
Next steps:
- We're reviewing our service update validation procedures to detect and prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 13 12:05:05 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may be unable to send email messages with attached files in any connection method of Exchange Online. Sending attachments as ZIP files allows the email messages to be delivered as expected, serving as a method by which to bypass the issue while we continue to investigate.
Current status: Though we've deployed the fix to 95 percent of the affected environment, we've received continued reports of impact that indicate our fix may not have corrected this issue as expected. We've halted the fix deployment and are reviewing these reports to determine our next steps.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving some email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that's resulting in impact for a portion of service infrastructure.
Next update by: Thursday, March 13, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Mar 13 05:30:46 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may be unable to send email messages with attached files in any connection method of Exchange Online. Sending attachments as ZIP files allows the email messages to be delivered as expected, serving as a method by which to bypass the issue while we continue to investigate.
Current status: We've successfully deployed the fix to 95% of the affected environment and the majority of users should start seeing improvements. We're actively monitoring the deployment and will provide a completion timeline in our next scheduled update.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that's resulting in impact for a portion of service infrastructure.
Next update by: Friday, March 14, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Mar 12 11:24:24 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may be unable to send email messages with attached files in any connection method of Exchange Online. Sending attachments as ZIP files allows the email messages to be delivered as expected, serving as a method by which to bypass the issue while we continue to investigate.
Current status: The fix has saturated across approximately 42 percent of the affected environment, and we're monitoring its progress to ensure it completes without issue. We expect the deployment should complete by the time of our next scheduled update.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that's resulting in impact for a portion of service infrastructure.
Next update by: Thursday, March 13, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Mar 12 07:42:09 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may be unable to send email messages with attached files in any connection method of Exchange Online. Sending attachments as ZIP files allows the email messages to be delivered as expected, serving as a method by which to bypass the issue while we continue to investigate.
Current status: We've initiated the deployment of the fix through an alternate deployment method to expedite recovery. As the fix deploys through the affected infrastructure users should begin to experience relief. We expect to provide estimated completion timeline by our next scheduled update.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that's resulting in impact for a portion of service infrastructure.
Next update by: Wednesday, March 12, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Mar 12 02:26:04 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may be unable to send email messages with attached files in any connection method of Exchange Online. Sending attachments as ZIP files allows the email messages to be delivered as expected, serving as a method by which to bypass the issue while we continue to investigate.
Current status: We've identified that our fix deployment has encountered an issue that is resulting in some delays. We're working to correct the problem and ensure no other problems arise.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that's resulting in impact for a portion of service infrastructure.
Next update by: Wednesday, March 12, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Mar 11 18:27:58 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may be unable to send email messages with attached files in any connection method of Exchange Online. Sending attachments as ZIP files allows the email messages to be delivered as expected, serving as a method by which to bypass the issue while we continue to investigate.
Current status: We've initiated the deployment of the fix and are monitoring as it progresses. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that's resulting in impact for a portion of service infrastructure.
Next update by: Wednesday, March 12, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Mar 11 13:37:46 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've completed our final validations and have initiated the deployment of our fix to affected portions of service infrastructure. We aim to provide a timeline to mitigation after we complete our review of the initial deployment progress.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that's resulting in impact for a portion of service infrastructure.
Next update by: Tuesday, March 11, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Mar 11 11:52:41 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: Our final validations and review of the fix prior to deployment is continuing to progress, albeit at a slower than initially anticipated pace. Once the deployment is finalized and initiated, we'll review its initial progress to determine a timeline to remediation.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update, intended to improve our message transport services, introduced a code issue that's resulting in impact for a portion of service infrastructure.
Next update by: Tuesday, March 11, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Mar 11 09:49:08 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've completed the validation of the fix and begun the deployment process to mitigate impact. We're reviewing the deployment details to provide an estimated completion timeline in our next update.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update intended to improve our message transport services introduced a code issue resulting in impact for a portion of service infrastructure.
Next update by: Tuesday, March 11, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 14:50:58 2025 |
|---|
| Description: | Title: Users may encounter delays or failures when sending or receiving email messages in Exchange Online
User impact: Users may encounter delays or failures when sending or receiving email messages in Exchange Online.
More info: Users encountering failures when sending email messages receive a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content".
Current status: We've identified that users serviced by the impacted portion of infrastructure may also be seeing outbound message sending failures, upon which a Non-Delivery Report (NDR) containing an error stating "554 5.6.0 Corrupt message content" is returned. We're finalizing the validation process of our fix in preparation for its deployment throughout the affected service environment and anticipate we'll have an updated timeline for full remediation by our next communications update.
Scope of impact: Any user serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update intended to improve our message transport services introduced a code issue resulting in impact for a portion of service infrastructure.
Next update by: Tuesday, March 11, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 12:50:14 2025 |
|---|
| Description: | Title: Users may encounter delays when sending or receiving email messages
User impact: Users may encounter delays when sending or receiving email messages.
Current status: Our investigation has identified that a recent service update to improve transport services contains an error, resulting in impact. We're continuing our analysis of service telemetry to determine the best path to remediate this issue.
Scope of impact: Any user hosted on the on the impacted infrastructure may be affected.
Start time: Friday, March 7, 2025, at 5:30 PM UTC
Root cause: A recent service update to improve transport services contains an error, resulting in impact.
Next update by: Monday, March 10, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 11:44:24 2025 |
|---|
| Description: | Title: Users may encounter delays when sending or receiving email messages
User impact: Users may encounter delays when sending or receiving email messages.
Current status: We're reviewing service telemetry to better understand the impact scenario and determine the root cause of impact.
Scope of impact: Any user hosted on the on the impacted infrastructure may be affected.
Next update by: Monday, March 10, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 11:14:09 2025 |
|---|
| Description: | Title: Users may encounter delays when sending or receiving email messages
User impact: Users may encounter delays when sending or receiving email messages.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1024791 - Updated attack simulations and training (AST) URL endpoint
| Status: | investigationSuspended |
|---|
| Start Time: | Thu Mar 6 08:57:43 2025 |
|---|
| End Time: | Thu Mar 13 07:34:30 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 13 07:35:42 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 13 07:34:35 2025 |
|---|
| Description: | Title: Updated attack simulations and training (AST) URL endpoint
User impact: If no action is taken, users may be unable to view assigned attack simulations and trainings.
Final Status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 6 08:58:43 2025 |
|---|
| Description: | Title: Updated attack simulations and training (AST) URL endpoint
User impact: If no action is taken, users may be unable to view assigned attack simulations and trainings.
Current status: We've made an update to the training URL endpoint that is used as part of the training player for end users. In organizations with the Microsoft Defender for Office 365 Plan 2 license (either through add-on or included in subscriptions like Microsoft 365 E5), you can use attack simulation training in the Microsoft Defender portal to run user simulations and assign training to your end users. If you are using firewalls or third-party filtering security solutions, you should allow the updated URL to ensure that the training content isn't blocked by your solution.
This communication will expire in seven days and is scheduled to remain active for the full duration.
|
|---|
|
SP1030180 - Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Mar 12 23:33:44 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 12 23:57:12 2025 |
|---|
| Root Cause: | A recent deployment incorrectly enabled this feature in the affected environment. |
|---|
| Next Update: | Thursday, March 27, 2025, at 5:00 AM UTC |
|---|
|
Details
| Time: | Wed Mar 12 23:48:34 2025 |
|---|
| Description: | Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've identified an issue in which users may see a new "Content Freshness" template option when creating pages in SharePoint Online. We've determined a recent deployment incorrectly enabled this feature in the affected environment. We're developing a fix to remove the "Content Freshness" template and in the meantime, we advise users to ignore the "Content Freshness" template option.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, March 27, 2025, at 5:00 AM UTC
|
|---|
|
TM1027077 - Users' calls disconnect with an error when they are made using an extension in the Microsoft Teams desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 24 12:18:00 2025 |
|---|
| End Time: | Mon Mar 10 21:29:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 12 14:13:53 2025 |
|---|
| Root Cause: | A recent code change intended to improve service performance and reliability contained a code regression that resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 12 14:09:05 2025 |
|---|
| Description: | Title: Users' calls disconnect with an error when they are made using an extension in the Microsoft Teams desktop client
User impact: Users' calls may have disconnected with an error when made using an extension in the Microsoft Teams desktop client.
More info: Calls made with extensions may have disconnected with the following error: "BackToBackOfferDeclinedByPeer".
Users could bypass the impact where possible by using the Microsoft Teams web client.
Final status: We've completed the reversion of the code change leading to impact, and we've monitored our service health telemetry to confirm that impact is remediated.
Scope of impact: This issue may have impacted any user leveraging an extension to make calls in the Microsoft Teams desktop client.
Start time: Monday, February 24, 2025, at 5:18 PM UTC
End time: Tuesday, March 11, 2025, at 1:29 AM UTC
Root cause: A recent code change intended to improve service performance and reliability contained a code regression that resulted in impact.
Next steps:
- We're reviewing our Microsoft Teams service update procedures pertaining to the code base responsible for facilitating calls made using extensions to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Sun Mar 9 17:16:20 2025 |
|---|
| Description: | Title: Users' calls may disconnect with an error when they are made using an extension in the Microsoft Teams desktop client
User impact: Users' calls may disconnect with an error when they are made using an extension in the Microsoft Teams desktop client.
More info: Calls made with extensions may be disconnected with an error that states "BackToBackOfferDeclinedByPeer".
Users can successfully use the Microsoft Teams web client as a workaround.
Current status: We've isolated a recent update that intended to improve service performance and reliability that contained a code regression causing some users' calls to disconnect when using an extension in the Microsoft Teams desktop client. After reverting the updates containing the regression for a subset of users to ensure its effectiveness, we've confirmed with those users that this has remediated the impact. We're continuing to revert this update for all affected users.
Scope of impact: This issue may impact any user when using an extension in the Microsoft Teams desktop client.
Start time: Monday, February 24, 2025, at 5:18 PM UTC
Root cause: A recent code change that intended to improve service performance and reliability contained a code regression that resulted in impact.
Next update by: Wednesday, March 12, 2025, at 7:00 PM UTC
|
|---|
|
EX1025615 - Users opening a published Exchange Online calendar may see incorrect dates when opening the HTML link
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 3 09:00:00 2025 |
|---|
| End Time: | Mon Mar 10 19:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 11 17:23:05 2025 |
|---|
| Root Cause: | A fix to correct an issue with an unrelated feature has introduced a code issue which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 11 16:59:38 2025 |
|---|
| Description: | Title: Users opening a published Exchange Online calendar may see incorrect dates when opening the HTML link
User impact: Users opening a published Exchange Online calendar may have seen incorrect dates when opening the HTML link.
More info: This issue impacted calendar appointments opened through HTML links in any Exchange Online connection method.
Final status: Our deployment of the previously mentioned fix is complete, and we've monitored our service health telemetry to confirm that impact is remediated.
Scope of impact: Any user attempting to open a published Exchange Online calendar by leveraging the HTML link may have been impacted.
Start time: Monday, February 3, 2025, at 2:00 PM UTC
End time: Monday, March 10, 2025, at 11:00 PM UTC
Root cause: A fix to correct an issue with an unrelated feature has introduced a code issue which resulted in impact.
Next steps:
- We're reviewing our Exchange Online code fix development and testing procedures pertaining to the code base responsible for syncing the date in Exchange Online calendar items to prevent similar issues in future repair actions.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 10 15:26:50 2025 |
|---|
| Description: | Title: Users opening a published Exchange Online calendar may see incorrect dates when opening the HTML link
User impact: Users opening a published Exchange Online calendar may see incorrect dates when opening the HTML link.
More info: This issue impacts calendar appointment opened through the HTML link in any Exchange Online connection method.
Current status: Our fix is continuing to progress as expected, and we anticipate that it may complete and remediate the issue for all users by our next scheduled communications update.
Scope of impact: Any user attempting to open a published Exchange Online calendar by leveraging the HTML link may be impacted.
Start time: Monday, February 3, 2025, at 2:00 PM UTC
Root cause: A fix to correct an issue with an unrelated feature has introduced a code issue which is resulting in impact.
Next update by: Tuesday, March 11, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Mar 7 14:32:30 2025 |
|---|
| Description: | Title: Users opening a published Exchange Online calendar may see incorrect dates when opening the HTML link
User impact: Users opening a published Exchange Online calendar may see incorrect dates when opening the HTML link.
More info: This issue impacts calendar appointment opened through the HTML link in any Exchange Online connection method.
Current status: We're continuing to monitor as the fix to mitigate impact is progressing and expect to have a remediation timeline by the next scheduled update.
Scope of impact: Any user attempting to open a published Exchange Online calendar by leveraging the HTML link may be impacted.
Root cause: A fix to correct an issue with an unrelated feature has introduced a code issue which is resulting in impact.
Next update by: Monday, March 10, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Mar 7 08:02:46 2025 |
|---|
| Description: | Title: Users opening a published Exchange Online calendar may see incorrect dates when opening the HTML link
User impact: Users opening a published Exchange Online calendar may see incorrect dates when opening the HTML link.
More info: This issue impacts calendar appointment opened through the HTML link in any Exchange Online connection method.
Current status: We've identified that a fix to correct an issue with an unrelated feature has inadvertently caused impact. We're reverting the offending fix and monitoring as it saturates throughout the affected environments.
Scope of impact: Any user attempting to open a published Exchange Online calendar by leveraging the HTML link may be impacted.
Root cause: A fix to correct an issue with an unrelated feature has introduced a code issue which is resulting in impact.
Next update by: Friday, March 7, 2025, at 8:30 PM UTC
|
|---|
|
EX1028129 - Some users' inbound email messages may be delayed up to 10 hours in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 10 10:03:00 2025 |
|---|
| End Time: | Mon Mar 10 19:45:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 10 20:15:23 2025 |
|---|
| Root Cause: | A portion of infrastructure leveraged to facilitate email delivery in Exchange Online entered an unhealthy state, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 10 20:15:23 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be delayed up to 10 hours in Exchange Online
User impact: Users' inbound email messages may have been delayed up to 10 hours in Exchange Online.
Final status: We've confirmed through user testing and additional monitoring that our rerouting of affected requests was successful in remediating the impact. Additionally, we've identified that delays may have been up to ten hours.
Scope of impact: Some users serviced by the affected portion of infrastructure receiving email messages in Exchange Online may have been impacted.
Start time: Monday, March 10, 2025, at 2:03 PM UTC
End time: Monday, March 10, 2025, at 11:45 PM UTC
Root cause: A portion of infrastructure leveraged to facilitate email delivery in Exchange Online entered an unhealthy state, resulting in impact.
Next steps:
- We're continuing to monitor the affected infrastructure closely to gain further insight into the source of the underlying issue and identify ways to better prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 10 19:45:44 2025 |
|---|
| Description: | Title: Some users' inbound email messages may be delayed by 12 hours or more in Exchange Online
User impact: Users' inbound email messages may be delayed by 12 hours or more in Exchange Online.
Current status: We've identified that a portion of infrastructure leveraged to facilitate email delivery in Exchange Online entered an unhealthy state, resulting in impact. We've manually redirected requests to an alternate portion of infrastructure to resolve the issue and are monitoring internal telemetry to validate that impact is resolved.
Scope of impact: Some users serviced by the affected portion of infrastructure receiving email messages in Exchange Online may be impacted.
Root cause: A portion of infrastructure leveraged to facilitate email delivery in Exchange Online entered an unhealthy state, resulting in impact.
Next update by: Tuesday, March 11, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Mar 10 19:24:16 2025 |
|---|
| Description: | Title: Several users aren't receiving email in Exchange Online
User impact: Users aren't receiving email in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1022107 - Users may not be able to receive calls placed through Microsoft Teams-provisioned auto attendants and call queues
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Mar 3 11:00:00 2025 |
|---|
| End Time: | Mon Mar 3 15:19:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Mar 10 19:14:32 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 10 19:14:32 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Mar 5 18:45:45 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Mar 3 15:50:51 2025 |
|---|
| Description: | Title: Users may not be able to receive calls placed through Microsoft Teams-provisioned auto attendants and call queues
User impact: Users may not have been able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues
More info: Callers routed through call queues may have heard a busy signal or the call may have rung for 45+ seconds and then ended.
Final status: Our fix was successfully deployed. After an extended period of monitoring, we’ve confirmed through telemetry that service is restored and impact has been fully remediated.
Scope of impact: Users who expected to make or receive calls routed through Microsoft Teams provisioned auto attendants and call queues may have been affected.
Start time: Monday, March 3, 2025, at 4:00 PM UTC
End time: Monday, March 3, 2025, at 8:19 PM UTC
Preliminary root case: A configuration change to an auto-attendant app ID record that matches inbound calls with users in call queues was preventing users from receiving calls and caused the impact.
Next steps:
- We’re reviewing our testing and validation processes to understand how the impact of the configuration change wasn’t identified prior to implementation so that we can improve our testing and validation procedures and avoid similar issues in the future.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Mar 3 15:20:32 2025 |
|---|
| Description: | Title: Users may not be able to receive calls placed through Microsoft Teams-provisioned auto attendants and call queues
User impact: Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues.
More info: Callers routed through call queues may hear a busy signal or the call may ring for 45+ seconds and then end.
Current status: We’ve deployed the configuration to the auto-attendant app and are seeing service functionality improvements as expected. We’re continuing to monitor to confirm the fix is mitigating impact.
Scope of impact: Users expecting to make or receive calls routed through Microsoft Teams-provisioned auto attendants and call queues may be affected.
Start time: Monday, March 3, 2025, at 4:00 PM UTC
Preliminary root case: A configuration change to an auto-attendant app ID record that matches inbound calls with users in call queues is preventing users from receiving calls and causing the impact.
Next update by: Monday, March 3, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Mar 3 14:33:15 2025 |
|---|
| Description: | Title: Users may not be able to receive calls placed through Microsoft Teams-provisioned auto attendants and call queues
User impact: Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues.
More info: Callers routed through call queues may hear a busy signal or the call may ring for 45+ seconds and then end.
Current status: We've discovered that a modification to an auto attendant application ID record is rejecting Microsoft Teams call queues. We've deployed a fix to update the affected application ID record, which will mitigate impact.
Scope of impact: Users expecting to make or receive calls routed through Microsoft Teams-provisioned auto attendants and call queues may be affected.
Start time: Monday, March 3, 2025, at 4:00 PM UTC
Preliminary root case: A configuration change to an auto-attendant app ID record that matches inbound calls with users in call queues is preventing users from receiving calls and causing the impact.
Next update by: Monday, March 3, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Mar 3 13:01:51 2025 |
|---|
| Description: | Title: Users may not be able to receive calls placed through Microsoft Teams-provisioned auto attendants and call queues
User impact: Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues.
Current status: We've detected a potential authentication token issue that may be contributing to impact, and we're further examining this pathway to determine our next troubleshooting steps.
Scope of impact: Users expecting to make or receive calls routed through Microsoft Teams-provisioned auto attendants and call queues may be affected.
Start time: Monday, March 3, 2025, at 4:00 PM UTC
Next update by: Monday, March 3, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Mar 3 12:11:25 2025 |
|---|
| Description: | Title: Users may not be able to receive calls placed through Microsoft Teams-provisioned auto attendants and call queues
User impact: Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues.
Current status: Our monitoring has identified an increase in call failures for Microsoft Teams auto attendants and call queues. We're analyzing service telemetry and call metadata to better understand the nature of impact and determine our next steps.
Scope of impact: Users expecting to make or receive calls routed through Microsoft Teams-provisioned auto attendants and call queues may be affected.
Start time: Monday, March 3, 2025, at 4:00 PM UTC
Next update by: Monday, March 3, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Mar 3 11:46:57 2025 |
|---|
| Description: | Title: Users may not be able to receive calls placed through Microsoft Teams-provisioned auto attendants and call queues
User impact: Users may not be able to receive calls placed through Microsoft Teams provisioned auto attendants and call queues.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1027387 - Some users may receive an error when attempting to share to Outlook in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 26 15:40:00 2025 |
|---|
| End Time: | Mon Mar 10 14:58:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 10 15:33:08 2025 |
|---|
| Root Cause: | A recent update to the Microsoft Teams code base that facilitates sharing to Outlook introduced a code error that prevented share requests from being fulfilled, leading to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 10 15:33:08 2025 |
|---|
| Description: | Title: Some users may receive an error when attempting to share to Outlook in Microsoft Teams
User impact: Users may have received an error when attempting to share to Outlook in Microsoft Teams.
More info: The right-click menu containing the "Share in Outlook" feature may not have been available for the affected users in Microsoft Teams.
Final status: We've completed deploying the previously mentioned fix to the impacted service environments, and we've subsequently monitored our service health telemetry to confirm that the impact is remediated.
Scope of impact: Some users attempting to share to Outlook in Microsoft Teams by utilizing the "Share in Outlook" feature may have been impacted.
Start time: Wednesday, February 26, 2025, at 8:40 AM UTC
End time: Monday, March 10, 2025, at 6:58 PM UTC
Root cause: A recent update to the Microsoft Teams code base that facilitates sharing to Outlook introduced a code error that prevented share requests from being fulfilled, leading to impact.
Next steps:
- We're reviewing our Microsoft Teams service update procedures pertaining to the code base responsible for fulfilling the impacted share requests to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 10 13:21:55 2025 |
|---|
| Description: | Title: Some users may receive an error when attempting to share to Outlook in Microsoft Teams
User impact: Users may receive an error when attempting to share to Outlook in Microsoft Teams.
More info: The right-click menu containing the "Share in Outlook" feature may not be available for the affected users in Microsoft Teams.
Current status: Our investigation has determined that a recent update to the Microsoft Teams code base that facilitates sharing to Outlook introduced a code error that's preventing share requests from being filled, leading to impact. We're developed a fix to revert the offending update and repair this error, and we're initiating deployment to the impacted service environments. We anticipate that the fix will complete deployment by our next scheduled communications update, at which time we'll monitor our service health telemetry to confirm that impact is remediated.
Scope of impact: Some users attempting to share to Outlook in Microsoft Teams by utilizing the "Share in Outlook" feature may be impacted.
Start time: Wednesday, February 26, 2025, at 8:40 AM UTC
Estimated time to resolve: We anticipate that the fix will complete deployment, remediating impact by Monday, March 10, 2025, at 7:30 PM UTC.
Root cause: A recent update to the Microsoft Teams code base that facilitates sharing to Outlook introduced a code error that's preventing share requests from being filled, leading to impact.
Next update by: Monday, March 10, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Mar 10 08:47:39 2025 |
|---|
| Description: | Title: Some users are receiving an error when attempting to share to Outlook in Microsoft Teams
User impact: Users are receiving an error when attempting to share to Outlook in Microsoft Teams.
More info: The right-click menu containing the "Share in Outlook" feature is not available for the affected users in Microsoft Teams.
Current status: Our investigation into the HTTP Archive format (HAR) logs has so far proved inconclusive. We're analyzing a reproduction of the issue in our internal testing environments, to diagnose the underlying root cause and formulate a plan to remediate impact.
Scope of impact: Your organization is affected by this event, and some users attempting to share to Outlook in Microsoft Teams by utilizing the "Share in Outlook" feature are impacted.
Next update by: Monday, March 10, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Mar 10 07:19:02 2025 |
|---|
| Description: | Title: Some users are receiving an error when attempting to share to Outlook in Microsoft Teams
User impact: Users are receiving an error when attempting to share to Outlook in Microsoft Teams.
More info: The right-click menu containing the "Share in Outlook" feature is not available for the affected users in Microsoft Teams.
Current status: We're continuing to review support provided information, alongside HTTP Archive format (HAR) logs, to isolate the root cause and establish a fix.
Scope of impact: Your organization is affected by this event, and some users attempting to share to Outlook in Microsoft Teams by utilizing the "Share in Outlook" feature are impacted.
Next update by: Monday, March 10, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Mar 10 05:10:32 2025 |
|---|
| Description: | Title: Some users are receiving an error when attempting to share to Outlook in Microsoft Teams
User impact: Users are receiving an error when attempting to share to Outlook in Microsoft Teams.
More info: The right-click menu containing the "Share in Outlook" feature is not available for the affected users in Microsoft Teams.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to share to Outlook in Microsoft Teams by utilizing the "Share in Outlook" feature are impacted.
Next update by: Monday, March 10, 2025, at 11:30 AM UTC
|
|---|
|
OD1017081 - Some users may have been unable to edit their OneDrive for Business content as they were in a read-only state
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jan 27 07:00:00 2025 |
|---|
| End Time: | Mon Mar 3 03:09:00 2025 |
|---|
| Service: | OneDrive for Business |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Mar 10 15:29:23 2025 |
|---|
| Root Cause: | A recent policy enforcement rollout interacted negatively with a configuration leveraged by your organization. The policy check looked for a parameter match between the user’s account, and the primary site collection ownership account of the user’s OneDrive, to validate if the user had a valid license. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 10 15:29:23 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Mar 5 13:41:05 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Mar 3 14:39:21 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message stated that "You can't edit your files because your license to use OneDrive ended over a month ago."
To mitigate the issue, admins should have updated user OneDrive configurations from unsupported states into supported states, as described here: https://learn.microsoft.com/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive
Specifically, IT admins should have ensured that the owner (also known as the primary site collection administrator) of every OneDrive account is assigned to the correct user who owns that account and not a service account or group account.
As an optional workaround, admins could have removed the read-only lock via PowerShell by following the instructions here: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status. Please note: The read-only notification remained visible until full mitigation had been completed, however no archiving actions took place.
Information about our enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts
Final status: We've completed deploying the permanent fix to the affected infrastructure, and after a period of monitoring, we've determined impact is now resolved.
Scope of impact: A subset of users who had recently been configured in the unsupported scenario or who had recently been licensed may have been affected.
Start time: Monday, January 27, 2025, at 12:00 PM UTC
End time: Monday, March 3, 2025, at 8:09 AM UTC
Root cause: A recent policy enforcement rollout interacted negatively with a configuration leveraged by your organization. The policy check looked for a parameter match between the user’s account, and the primary site collection ownership account of the user’s OneDrive, to validate if the user had a valid license.
Specifically, this problem occurred when OneDrive for Business ownership was applied to a group or service account, rather than their own account. This is an unsupported scenario. As the accounts between the two parameters did not match, the policy verification request failed, resulting in the service flagging the account as unlicensed. This is an unsupported scenario, because not having the user as the admin of their own OneDrive can leave the OneDrive is a state where multiple types of issues can occur.
In our efforts to address the initial impact, we disabled some relevant code paths as troubleshooting/mitigation tests. This inadvertently created a secondary impacting issue, in which the service didn’t process recently applied licenses, so the users remained in a read-only state.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We’ll produce a preliminary post-incident report in two business days, and a final post-incident report in five business days.
|
|---|
|
| Time: | Fri Feb 28 20:41:09 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
To mitigate the issue, admins should update user OneDrive configurations from unsupported states into supported states, as described here: https://learn.microsoft.com/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive
Specifically, IT admins should ensure that the owner (also known as the primary site collection administrator) of every OneDrive account is assigned to the correct user who owns that account and not a service account or group account.
As an optional workaround, admins can remove the read-only lock via PowerShell by following the instructions here: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status Please note: the read-only notification will remain visible until full mitigation has been completed, however no archiving actions will take place.
Information about our enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts
Current status: We’ve successfully deployed the permanent fix and anticipate it will be completed by Monday, March 3, 2025. Additionally, the targeted rollouts intended to provide immediate relief for the second scenario are currently 93 percent complete.
Scope of impact: A subset of users who have recently been configured in the unsupported scenario or who have recently been licensed may be affected.
Start time: Monday, January 27, 2025, at 12:00 AM UTC
Preliminary root cause: A recent policy enforcement rollout interacted negatively with a configuration leveraged by your organization. Specifically, this problem occurs when OneDrive for Business ownership is applied to a group or service account, which is an unsupported scenario. Our efforts to address this impact introduced a secondary issue in which recently licensed users are registering as unlicensed users in our systems, also resulting in read-only states for users.
Next update by: Monday, March 3, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Feb 28 12:53:41 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
To mitigate the issue, admins should update user OneDrive configurations from unsupported states into supported states, as described here: https://learn.microsoft.com/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive
Specifically, IT admins should ensure that the owner (also known as the primary site collection administrator) of every OneDrive account is assigned to the correct user who owns that account.
As an optional workaround, admins can remove the read-only lock via PowerShell by following the instructions here: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status Please note: the read-only notification will remain visible until full mitigation has been completed, however no archiving actions will take place.
Information about our enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts
Current status: We've initiated the targeted rollouts for immediate relief for the second scenario, which are currently 50 percent complete. In addition, we've completed development for our permanent fix which is undergoing deployment with an expected completion date of Monday, March 3, 2025.
Scope of impact: A subset of users who have recently been configured in the unsupported scenario or who have recently been licensed may be affected.
Start time: Monday, January 27, 2025, at 12:00 AM UTC
Preliminary root cause: A recent policy enforcement rollout interacted negatively with a configuration leveraged by your organization. Specifically, this problem occurs when OneDrive for Business ownership is applied to a group or service account, which is an unsupported scenario. Our efforts to address this impact introduced a secondary issue in which recently licensed users are registering as unlicensed users in our systems, also resulting in read-only states for users.
Next update by: Saturday, March 1, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Feb 27 20:02:55 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
To mitigate the issue, admins should update user OneDrive configurations from unsupported states into supported states, as described here: https://learn.microsoft.com/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive
Specifically, IT admins should ensure that the owner (also known as the primary site collection administrator) of every OneDrive account is assigned to the correct user who owns that account.
As an optional workaround, admins can remove the read-only lock via PowerShell by following the instructions here: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status Please note: the read-only notification will remain visible until full mitigation has been completed, however no archiving actions will take place.
Information about our enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts
Current status: We're continuing to validate our interim fix for scenario 2 and are in the process of initiating our first wave of targeted rollouts. In parallel, we're developing and testing our permanent fix which will address this issue for all users. We'll aim to establish an estimated time to deploy the fix in our next scheduled update.
Scope of impact: A subset of users who have recently been configured in the unsupported scenario or who have recently been licensed may be affected.
Start time: Monday, January 27, 2025, at 12:00 AM UTC
Preliminary root cause: A recent policy enforcement rollout interacted negatively with a configuration leveraged by your organization. Specifically, this problem occurs when OneDrive for Business ownership is applied to a group or service account, which is an unsupported scenario. Our efforts to address this impact introduced a secondary issue in which recently licensed users are registering as unlicensed users in our systems, also resulting in read-only states for users.
Next update by: Friday, February 28, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Feb 27 17:56:51 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
To mitigate the issue, admins should update user OneDrive configurations from unsupported states into supported states, as described here: https://learn.microsoft.com/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive
Specifically, IT admins should ensure that the owner (also known as the primary site collection administrator) of every OneDrive account is assigned to the correct user who owns that account.
As an optional workaround, admins can remove the read-only lock via PowerShell by following the instructions here: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status Please note: the read-only notification will remain visible until full mitigation has been completed, however no archiving actions will take place.
Information about our enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts
Current status: We've developed a fix to address scenario 2, in which newly licensed accounts aren't registering in our internal systems as expected, and we're performing internal validations before applying it more broadly. We expect that this process will begin by our next scheduled update. In parallel, we're continuing to monitor responses confirming resolution from users who received our fix for scenario 1, which addressed the unsupported configuration we outlined in our last communication.
Scope of impact: A subset of users who have recently been configured in the unsupported scenario or who have recently been licensed may be affected.
Start time: Monday, January 27, 2025, at 12:00 AM UTC
Preliminary root cause: A recent policy enforcement rollout interacted negatively with a configuration leveraged by your organization. Specifically, this problem occurs when OneDrive for Business ownership is applied to a group or service account, which is an unsupported scenario. Our efforts to address this impact introduced a secondary issue in which recently licensed users are registering as unlicensed users in our systems, also resulting in read-only states for users.
Next update by: Friday, February 28, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Feb 27 13:35:06 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
To mitigate the issue, admins should update user OneDrive configurations from unsupported states into supported states, as described here: https://learn.microsoft.com/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive Specifically, IT admins should ensure that the owner (also known as the primary site collection administrator) of every OneDrive account is assigned to the correct user who owns that account.
As an optional workaround, admins can remove the read-only lock via PowerShell by following the instructions here: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status Please note, the read-only notification will remain visible until full mitigation has been completed, however no archiving actions will take place.
Information about our enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts
Current status: We've investigated further and determined that your users may experience impact behavior due to several scenarios, which require separate mitigations.
Scenario 1 - Users may be in a read-only state due to account ownership being moved from an individual to a group, which is an unsupported state. This state can be mitigated by following the instructions outlined in the 'More info' section of this communication. If you've followed these steps then, while the banner informing users that they're in a read-only state remains, users can edit content as expected. The fix we've been tracking has also been specifically targeting this scenario, and we've fixed approximately 93 percent of accounts in this state. These accounts will no longer see the read-only banner.
Scenario 2 - Users may be in a read-only state due to issues registering licenses for accounts that were recently licensed. Since accounts are perceived as unlicensed, users are put in a read-only state. This issue was introduced when we reverted a portion of code in an attempt to remediate the first scenario, and we're working to develop a remediation strategy to address this secondary impact.
Scope of impact: A subset of users who have recently been configured in the unsupported scenario or who have recently been licensed may be affected.
Start time: Monday, January 27, 2025, at 12:00 AM UTC
Preliminary root cause: A recent policy enforcement rollout interacted negatively with a configuration leveraged by your organization. Specifically, this problem occurs when OneDrive for Business ownership is applied to a group or service account, which is an unsupported scenario. Our efforts to address this impact introduced a secondary issue in which recently licensed users are registering as unlicensed users in our systems, also resulting in read-only states for users.
Next update by: Friday, February 28, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Feb 26 19:06:06 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
Admins can remove the read-only lock via PowerShell by following the instructions here: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status
Please note: the read-only notification will remain visible until full mitigation has been completed, however no archiving actions will take place.
Admins should permanently change configurations from their unsupported states as described here: https://learn.microsoft.com/en-us/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive
Information about our enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts
Current status: We've confirmed with some sample affected users that our change successfully provides relief, and we're in the process of applying it more broadly. We anticipate that our fix will complete and remediate the issue by our next scheduled communications update.
Scope of impact: Any organization may be affected by this event if configured in the unsupported scenario.
Start time: Monday, January 27, 2025, at 12:00 AM UTC
Preliminary root cause: A recent policy enforcement rollout interacted negatively with a configuration leveraged by your organization. Specifically, this problem occurs when OneDrive for Business ownership is applied to a group or service account, which is an unsupported scenario.
Next update by: Thursday, February 27, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 15:23:09 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
Admins can remove the read-only lock by following the instructions on this link via PowerShell: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status
Please note: the read-only notification will remain visible until full mitigation has been completed, however no archiving actions will take place.
Admins should permanently change configurations from their unsupported states as described here: https://learn.microsoft.com/en-us/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive
Information about our Enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts
Current status: We've collected a preliminary list of accounts in unsupported states and we're validating our change, which will be applied to these accounts to alleviate impact by reversing the policy enforcement rollout. This alleviation is temporary, as the configuration our policy rollout interacted negatively with is an unsupported scenario. Please refer to https://learn.microsoft.com/en-us/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive to ensure account ownership is properly configured to prevent future impact. We'll aim to provide an estimated timeline to resolution in our next scheduled update.
Scope of impact: Any organization may be affected by this event if configured in the unsupported scenario.
Preliminary root cause: A recent policy enforcement rollout interacted negatively with a configuration made by your organization, in which admins changed OneDrive for Business owners from a dedicated person to a group or service account, which is an unsupported scenario.
Next update by: Thursday, February 27, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Feb 26 02:53:21 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
Admins can remove the read-only lock by following the instructions on this link via PowerShell: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status. Please note: the read-only notification will remain visible until full mitigation has been completed next week, however no archiving actions will take place.
Admins should permanently change configurations from their unsupported states as described here: https://learn.microsoft.com/en-us/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive.
Information about our Enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts.
Current status: Our rollback of read-only sites is progressing as expected in a thorough and secure pace for our previously identified use cases. While we continue our mitigation efforts, we strongly recommend admins to take prompt action and perform the self-mitigation steps outlined in our “More Info” section as our changes may not address every unique configuration of OneDrive owners who have been changed from the correct Entra ID owner. We’ll continue rollbacks and provide another update on Wednesday, February 26, 2025, at 10:00 PM UTC.
Scope of impact: Any organization may be affected by this event, and some users' OneDrive for Business content may be in read-only mode.
Root cause: A recent policy enforcement rollout is unintentionally resulting in read-only mode of OneDrive for Business when admins have modified their users OneDrive for Business owners from a dedicated person to a group or service account which is a strictly unsupported state.
Next update by: Wednesday, February 26, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 00:24:03 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
Admins can remove the read-only lock by following the instructions on this link via PowerShell: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status. Please note: the read-only notification will remain visible until full mitigation has been completed next week, however no archiving actions will take place.
Admins should permanently change configurations from their unsupported states as described here: https://learn.microsoft.com/en-us/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive.
Information about our Enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts.
Current status: We’re continuing our rollback to remove affected users and sites from the read-only state that they are in. In addition, we’ve expanded our initial use case scenarios to include other potential scenarios that may result in similar impact. Interim, admins should change their configurations from unsupported states as described in the more info section.
We’ll provide a more definitive timeline in our next update.
Scope of impact: Any organization may be affected by this event, and some users' OneDrive for Business content may be in read-only mode.
Root cause: A recent policy enforcement rollout is unintentionally resulting in read-only mode of OneDrive for Business when admins have modified their users OneDrive for Business owners from a dedicated person to a group or service account which is a strictly unsupported state.
Next update by: Wednesday, February 26, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 23:39:53 2025 |
|---|
| Description: | We’re analyzing and expanding additional use case scenarios where this read-only issue can affect users to ensure they're included in our mitigation efforts.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Feb 25 22:45:36 2025 |
|---|
| Description: | Title: Some users may be unable to edit their OneDrive for Business content as they are in a read-only state
User impact: Users may be unable to edit their OneDrive for Business content as they are in a read-only state.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
Admins can remove the read-only lock by following the instructions on this link via PowerShell: https://learn.microsoft.com/en-us/sharepoint/manage-lock-status. Please note: the read-only notification will remain visible until full mitigation has been completed next week, however no archiving actions will take place.
Admins should permanently change configurations from their unsupported states as described here: https://learn.microsoft.com/en-us/sharepoint/manage-user-profiles#add-and-remove-admins-for-a-users-onedrive.
Information about our Enforcement of policy changes for unlicensed OneDrive accounts:
https://learn.microsoft.com/en-us/sharepoint/unlicensed-onedrive-accounts.
Current status: We’ve confirmed the cause of this issue was as a result of a recent policy change in our enforcement of unlicensed OneDrive user accounts, which uncovered unsupported instances of users being removed as admins from their own OneDrive accounts and further resulting in read-only status.
We’ve paused the rollout of this enforcement change to prevent new users from entering this bad state or being archived and are working on rolling back affected users, which we anticipate completing within the next week. In addition, we’ve provided links with instructions in the more info section if you would like to manually revert the read-only state and resolve these unsupported states within your organization more quickly.
Scope of impact: Any organization may be affected by this event, and some users' OneDrive for Business content may be in read-only mode.
Root cause: A recent policy enforcement rollout is unintentionally resulting in read-only mode of OneDrive for Business when admins have modified their users OneDrive for Business owners from a dedicated person to a group or service account which is a strictly unsupported state.
Next update by: Wednesday, February 26, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 18:39:15 2025 |
|---|
| Description: | Title: Some users' OneDrive for Business content is in read-only mode and an error states their licenses ended over a month ago
User impact: Users' OneDrive for Business content is in read-only mode and an error states their licenses ended over a month ago.
More info: The error message states that "You can't edit your files because your license to use OneDrive ended over a month ago."
Current status: We received reports of an issue where some users' OneDrive for Business content is in read-only mode and an error states "You can't edit your files because your license to use OneDrive ended over a month ago." We're reviewing these reports to determine our next steps.
Scope of impact: Your organization is affected by this event, and some users' OneDrive for Business content is in read-only mode.
Next update by: Wednesday, February 26, 2025, at 10:00 PM UTC
|
|---|
|
PP1024526 - Copilot for Sales - Users are receiving an error when generating email summaries and drafts
| Status: | serviceRestored |
|---|
| Start Time: | Wed Mar 5 13:00:00 2025 |
|---|
| End Time: | Mon Mar 10 12:00:00 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 10 13:59:38 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 10 13:59:38 2025 |
|---|
| Description: | Title: Copilot for Sales - Users are receiving an error when generating email summaries and drafts
User impact: Users received an error when generating email summaries and drafts.
Final Status: After a period of service health monitoring, we have confirmed that functionality has been restored.
This is the final update on the incident.
Preliminary Root Cause: A service update contained a misconfiguration.
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|---|
|
| Time: | Fri Mar 7 15:34:27 2025 |
|---|
| Description: | Title: Copilot for Sales - Users are receiving an error when generating email summaries and drafts
User impact: Users are receiving an error when generating email summaries and drafts.
More Info: Impact is limited to actions performed inside of the Copilot window in Outlook. The following error message will be encountered when generating email summaries and drafts:
"There was a problem connecting to Copilot. Try again later."
As a workaround, users may utilize the Outlook on the web (OWA) to generate email summaries and drafts.
Current Status: We completed rolling back the deployment and are monitoring service health for recovery.
Next Update: Monday, March 10, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Mar 7 01:53:32 2025 |
|---|
| Description: | Title: Copilot for Sales - Users are receiving an error when generating email summaries and drafts
User impact: Users are receiving an error when generating email summaries and drafts.
More Info: Impact is limited to actions performed inside of the Copilot window in Outlook. The following error message will be encountered when generating email summaries and drafts:
"There was a problem connecting to Copilot. Try again later."
Current Status: The deployment rollback is ongoing, and we are monitoring telemetry for signs of recovery as the changes propagate throughout our infrastructure.
Next Update: Friday, March 7, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Mar 6 18:23:32 2025 |
|---|
| Description: | Title: Copilot for Sales - Users are receiving an error when generating email summaries and drafts
User impact: Users are receiving an error when generating email summaries and drafts.
More Info: Impact is limited to actions performed inside of the Copilot window in Outlook. The following error message will be encountered when generating email summaries and drafts:
"There was a problem connecting to Copilot. Try again later."
Current Status: The deployment rollback is ongoing.
Next Update: Friday, March 7, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Mar 6 13:59:31 2025 |
|---|
| Description: | Title: Copilot for Sales - Users are receiving an error when generating email summaries and drafts
User impact: Users are receiving an error when generating email summaries and drafts.
More Info: Impact is limited to actions performed inside of the Copilot window in Outlook. The following error message will be encountered when generating email summaries and drafts:
"There was a problem connecting to Copilot. Try again later."
Current Status: After further investigation, we have identified an offending change within a recent service deployment to a portion of the application service supporting integration between Copilot for Sales and Outlook. We are rolling back this deployment to mitigate the issue.
Next Update: Friday, March 7, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Mar 6 04:25:15 2025 |
|---|
| Description: | Title: Copilot for Sales - Users are receiving an error when generating email summaries and drafts
User impact: Users are receiving an error when generating email summaries and drafts.
More Info: Impact is limited to actions performed inside of the Copilot window in Outlook. The following error message will be encountered when generating email summaries and drafts:
"There was a problem connecting to Copilot. Try again later."
Current Status: Following completion of the hotfix deployment, we confirmed that the impact involving the Teams app has been resolved, however Outlook remains impacted. We are engaging additional resources and continuing to investigate this impact to determine our next mitigation steps.
Next Update: Thursday, March 6, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Mar 6 00:56:59 2025 |
|---|
| Description: | Title: Copilot for Sales - Users are receiving an error when generating email summaries and drafts
User impact: Users are receiving an error when generating email summaries and drafts.
More Info: Impact is limited to actions performed inside of the Copilot window. The following error message will be encountered when generating email summaries and drafts:
"There was a problem connecting to Copilot. Try again later."
Current Status: Our investigation identified that an application failed to publish following a recent service update. We have created a hotfix to address this issue and are preparing it for deployment to your environment.
Next Update: Thursday, March 6, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Mar 6 00:38:37 2025 |
|---|
| Description: | Title: Copilot for Sales - Users are receiving an error when generating email summaries and drafts
User impact: Users are receiving an error when generating email summaries and drafts.
Current Status: We are aware of an emerging issue where users are receiving an error when generating email summaries and drafts. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
TM1024881 - Admins or those with the Guest inviter role may be unable to add guest users as members in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 25 07:00:00 2025 |
|---|
| End Time: | Fri Mar 7 23:24:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 10 12:08:48 2025 |
|---|
| Root Cause: | A recent optimization update removed a portion of code necessary to allow admins and Guest inviters the ability to add guest users as members in Microsoft Teams, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 10 12:08:48 2025 |
|---|
| Description: | Title: Admins or those with the Guest inviter role may be unable to add guest users as members in Microsoft Teams
User impact: Admins or those with the Guest inviter role may have been unable to add guest users as members in Microsoft Teams.
More info: Admins could have modified the guest invite settings to allow anyone to add guest users as members as a work around to this issue.
Final status: We've completed the deployment of our fix and confirmed after monitoring service health telemetry that errors associated with impact have ceased, confirming impact remediation.
Scope of impact: Impact was specific to admins who were served through the affected infrastructure and were attempting to add guest users as members within Microsoft Teams.
Start time: Tuesday, February 25, 2025, at 12:00 PM UTC
End time: Saturday, March 8, 2025, at 4:24 AM UTC
Root cause: A recent optimization update removed a portion of code necessary to allow admins and Guest inviters the ability to add guest users as members in Microsoft Teams, resulting in impact.
Next steps:
- We're reviewing our update testing and validation procedures to identify opportunities to improve impact detection and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Mar 7 13:45:02 2025 |
|---|
| Description: | Title: Admins or those with the Guest inviter role may be unable to add guest users as members in Microsoft Teams
User impact: Admins or those with the Guest inviter role may be unable to add guest users as members in Microsoft Teams.
More info: Admins modify the guest invite settings to allow anyone to add guest users as members as a work around to this issue.
Current status: We've completed development of the previously mentioned fix, and we're initiating deployment to the impacted service environments. We anticipate that the fix will be fully deployed by our next scheduled communications update, at which time we'll monitor our service health telemetry to confirm that impact is remediated.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure and are attempting to add guest users as members within Microsoft Teams.
Start time: Tuesday, February 25, 2025, at 12:00 PM UTC
Estimated time to resolve: We anticipate that the fix will be fully deployed, remediating the impact by Monday, March 10, 2025, at 6:00 PM UTC.
Root cause: A recent optimization update removed a portion of code necessary to allow admins and Guest inviters the ability to add guest users as members in Microsoft Teams, resulting in impact.
Next update by: Monday, March 10, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Mar 6 13:39:52 2025 |
|---|
| Description: | Title: Admins or those with the Guest inviter role may be unable to add guest users as members in Microsoft Teams
User impact: Admins or those with the Guest inviter role may be unable to add guest users as members in Microsoft Teams.
More info: Admins modify the guest invite settings to allow anyone to add guest users as members as a work around to this issue.
Current status: We're creating a code fix that will reimplement the missing portion of code needed to allow admins and Guest inviters to add guest users as members in Microsoft Teams. Once this code fix is created we'll provide a timeline for deployment if one becomes available.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure and are attempting to add guest users as members within Microsoft Teams.
Start time: Tuesday, February 25, 2025, at 12:00 PM UTC
Root cause: A recent optimization update removed a portion of code necessary to allow admins and Guest inviters the ability to add guest users as member in Microsoft Teams, resulting in impact.
Next update by: Friday, March 7, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Mar 6 11:20:33 2025 |
|---|
| Description: | Title: Admins or those with the Guest inviter role may be unable to add guest users as members in Microsoft Teams
User impact: Admins or those with the Guest inviter role may be unable to add guest users as members in Microsoft Teams.
Current status: We've determined that a recent optimization update removed a portion of code necessary to allow admins and Guest inviters the ability to add guest users as members in Microsoft Teams, resulting in impact. We're evaluating if reimplementing the code is the most viable solution or if it rolling back the update is the best option.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure and are attempting to add guest users as members within Microsoft Teams.
Root cause: A recent optimization update removed a portion of code necessary to allow admins and Guest inviters the ability to add guest users as member in Microsoft Teams, resulting in impact.
Next update by: Thursday, March 6, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Mar 6 10:33:19 2025 |
|---|
| Description: | Title: Some admins may be unable to add guest users as a member within Microsoft Teams
User impact: Admins may be unable to add guest users as a member within Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure, attempting to add guest users as member within Microsoft Teams.
Next update by: Thursday, March 6, 2025, at 5:30 PM UTC
|
|---|
|
MO1022159 - Users located in Canada and the Northeast US may experience issues accessing Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Mar 3 12:45:32 2025 |
|---|
| End Time: | Mon Mar 3 15:44:29 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Mar 10 12:04:39 2025 |
|---|
| Root Cause: | Our global network connects the datacenters across Azure regions with our large network of edge sites. Our edge location in Toronto has paired network devices for redundancy. On Monday, March 3, 2025, at 10:58 AM UTC, one of the network devices within the pair experienced hardware failures and our automation successfully removed the device from active rotation. While we were performing an investigation into the cause of device failure, at 4:22 PM UTC the redundant device also experienced a hardware failure which led to network packets being dropped. We have identified that the hardware failure was due to a memory increase on the line cards of the device. This was triggered due to an increase in the number of connections through the device. Due to inbuilt safety checks in our automation systems, at the time of the failure the redundant device could not be taken out of rotation and required human intervention. Since the hardware failure was on part of the device, our network engineers isolated the faulty line card from the device, which restored connectivity at 6:37 PM UTC. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 10 12:04:39 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Mar 5 14:27:16 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Mar 3 15:44:51 2025 |
|---|
| Description: | Title: Users located in Canada and the Northeast US may experience issues accessing Microsoft 365 services
User impact: Users may have experienced issues accessing Microsoft 365 services.
More info: The following list isn't exhaustive, but provides examples of how users may have been impacted by this event:
- Exchange Online: Users may have been unable to connect to Exchange online through the Outlook desktop client, Outlook on the web, or Outlook mobile. Users may have seen an endless loading screen or an error.
- Microsoft 365 admin center: Admins may have been unable to connect to the admin center through admin.microsoft.com.
- Microsoft Teams: Users may have been unable to access Microsoft Teams.
Users may have experienced authentication issues that prevented them from accessing other Microsoft 365 apps.
Final status: After extended monitoring, we've confirmed the service has fully recovered.
Scope of impact: Any user located in Canada, or whose network traffic was directed through the unhealthy infrastructure in Canada and the Northeast US, attempting to access Microsoft 365 services may have been affected.
Start time: Monday, March 3, 2025, at 4:22 PM UTC
End time: Monday, March 3, 2025, at 6:39 PM UTC
Root cause: Our global network connects the datacenters across Azure regions with our large network of edge sites. Our edge location in Toronto has paired network devices for redundancy. On Monday, March 3, 2025, at 10:58 AM UTC, one of the network devices within the pair experienced hardware failures and our automation successfully removed the device from active rotation. While we were performing an investigation into the cause of device failure, at 4:22 PM UTC the redundant device also experienced a hardware failure which led to network packets being dropped. We have identified that the hardware failure was due to a memory increase on the line cards of the device. This was triggered due to an increase in the number of connections through the device. Due to inbuilt safety checks in our automation systems, at the time of the failure the redundant device could not be taken out of rotation and required human intervention. Since the hardware failure was on part of the device, our network engineers isolated the faulty line card from the device, which restored connectivity at 6:37 PM UTC.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll update the Post-Incident Report (PIR) again by Monday, March 17, 2025.
|
|---|
|
| Time: | Mon Mar 3 14:59:49 2025 |
|---|
| Description: | Title: Users located in Canada may experience issues accessing Microsoft 365 services
User impact: Users may experience issues accessing Microsoft 365 services.
More info: The following list isn't exhaustive, but provides examples of how users may be impacted by this event:
Exchange Online: Users may be unable to connect to Exchange online through the Outlook desktop client, Outlook on the web, or Outlook mobile. Users may see an endless loading screen or an error.
Microsoft 365 admin center: Admins may be unable to connect to the admin center through admin.microsoft.com.
Microsoft Teams: Users may be unable to access Microsoft Teams.
Users may experience authentication issues that prevent them from accessing other Microsoft 365 apps.
Current status: The service is continuing to recover, and we're monitoring for an extended period to ensure complete restoration.
Scope of impact: Any user located in Canada attempting to access Microsoft 365 services may be affected.
Start time: Monday, March 3, 2025, at 4:22 PM UTC
Preliminary root cause: A portion of networking infrastructure entered an unhealthy state in Canada, which prevented users located in this region, or users whose traffic was routed through this region, from accessing Microsoft 365 services as expected.
Next update by: Monday, March 3, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Mar 3 14:15:18 2025 |
|---|
| Description: | Title: Users located in Canada may experience issues accessing Microsoft 365 services
User impact: Users may experience issues accessing Microsoft 365 services.
More info: Users may experience impact in the following services:
Exchange Online: Users may be unable to connect to Exchange online through the Outlook desktop client, Outlook on the web, or Outlook mobile. Users may see an endless loading screen or an error.
Microsoft 365 admin center: Admins may be unable to connect to the admin center through admin.microsoft.com.
Microsoft Teams: Users may be unable to access Microsoft Teams.
Users may experience authentication issues that prevent them from accessing other Microsoft 365 apps.
Current status: We identified a networking issue in Canada that caused Microsoft 365 services to enter an unhealthy state. We're continuing to investigate what initially caused this issue, and in parallel we've applied a mitigation, which has begun to restore service functionality. We're continuing to monitor our telemetry to ensure the service fully recovers as expected.
Scope of impact: Any user located in Canada attempting to access Microsoft 365 services may be affected.
Next update by: Monday, March 3, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 12:48:07 2025 |
|---|
| Description: | Title: Users located in Canada may experience issues accessing Microsoft 365 services
User impact: Users may experience issues accessing Microsoft 365 services.
Current status: We're investigating user reports of issues accessing various Microsoft 365 services. We've detected a potential authentication token problem, and we're further examining this pathway to confirm it as the cause of impact and determine our next troubleshooting steps.
Scope of impact: Any user located in Canada attempting to access Microsoft 365 services may be affected.
Next update by: Monday, March 3, 2025, at 7:00 PM UTC
|
|---|
|
MO1009364 - Some users may have experienced issues with multiple Microsoft 365 features or services
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 3 17:00:00 2025 |
|---|
| End Time: | Tue Mar 4 05:09:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 10 07:45:41 2025 |
|---|
| Root Cause: | A recent update to improve governance was causing impact to multiple Microsoft 365 services. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 10 07:45:41 2025 |
|---|
| Description: | Title: Some users may have experienced issues with multiple Microsoft 365 features or services
User impact: Users may have experienced issues with multiple Microsoft 365 features or services.
More info: Impacted Microsoft 365 services and scenarios included:
Microsoft Viva Engage impacted scenario:
- Users may have been able to use the Import from CSV functionality to add members to Microsoft Viva Engage communities.
Microsoft Teams impacted scenario:
- When the Microsoft Teams groups are about to expire, owners may have received an alert to inform them of the expiration.
General impact:
- When Microsoft 365 groups become ownerless it will notify the group members via email, but users may have been able to click on the accept button to become the new owner.
Final status: We've confirmed impact is no longer occurring after an extended period of monitoring.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Monday, February 3, 2025, at 10:00 PM UTC
End time: Tuesday, March 4, 2025 at 10:09 AM UTC
Root cause: A recent update to improve governance was causing impact to multiple Microsoft 365 services.
Next steps:
- We're reviewing our standard service update procedures to better identify similar issues during our development and testing cycles.
This is the final update for this event.
|
|---|
|
| Time: | Wed Feb 26 05:53:38 2025 |
|---|
| Description: | Title: Some users may experience issues with multiple Microsoft 365 features or services
User impact: Users may experience issues with multiple Microsoft 365 features or services.
More info: Impacted Microsoft 365 services and scenarios are listed below:
Microsoft Viva Engage impacted scenario:
- Users may not be able to use the Import from CSV functionality to add members to Microsoft Viva Engage communities.
Microsoft Teams impacted scenario:
- When the Microsoft Teams groups are about to expire, owners may not receive an alert to inform them of the expiration.
General impact:
- When Microsoft 365 groups become ownerless it will notify the group members via email, but users may not be able to click on the accept button to become the new owner.
Current status: We've successfully restarted the reversion process in our internal environment, which will then automatically roll out to our production environments. We're expecting the deployment to be completed in our production environments by Sunday, March 9, 2025. After this, we will monitor the affected environments for an extended period to ensure that the impact has been fully remediated.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, February 3, 2025, at 10:00 PM UTC
Root cause: A recent update to improve governance is causing impact to multiple Microsoft 365 services.
Next update by: Monday, March 10, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 07:22:49 2025 |
|---|
| Description: | Title: Some users may experience issues with multiple Microsoft 365 features or services
User impact: Users may experience issues with multiple Microsoft 365 features or services.
More info: Impacted Microsoft 365 services and scenarios are listed below:
- When Microsoft 365 groups become ownerless it will notify the group members via email, but users may not be able to click on the accept button to become the new owner.
Microsoft Teams impacted scenario:
- When the Microsoft Teams groups are about to expire, owners may not receive an alert to inform them of the expiration.
Microsoft Viva Engage impacted scenario:
- Users may be unable to use the bulk import functionality in Microsoft Viva Engage.
Current status: We're continuing to attempt the reversion and progressing with exploring alternative actions to speed up the process.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, February 3, 2025, at 10:00 PM UTC
Root cause: A recent Azure library update to improve our governance alerts is inadvertently breaking the flows for multiple Microsoft 365 services.
Next update by: Wednesday, February 26, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 04:46:07 2025 |
|---|
| Description: | Title: Some users may experience issues with multiple Microsoft 365 features or services
User impact: Users may experience issues with multiple Microsoft 365 features or services.
More info: Impacted Microsoft 365 services and scenarios are listed below:
- When Microsoft 365 groups become ownerless it will notify the group members via email, but users may not be able to click on the accept button to become the new owner.
Microsoft Teams impacted scenario:
- When the Microsoft Teams groups are about to expire, owners may not receive an alert to inform them of the expiration.
Microsoft Viva Engage impacted scenario:
- Users may be unable to use the bulk import functionality in Microsoft Viva Engage.
Current status: We're continuing to revert the update but due to some unexpected failures, it is taking longer than anticipated. We're continuing to attempt the reversion and exploring alternative actions to speed up the process.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, February 3, 2025, at 10:00 PM UTC
Root cause: A recent Azure library update to improve our governance alerts is inadvertently breaking the flows for multiple Microsoft 365 services.
Next update by: Tuesday, February 25, 2025, at 2:30 PM UTC
|
|---|
|
| Time: | Tue Feb 18 10:10:33 2025 |
|---|
| Description: | Title: Some users may experience issues with multiple Microsoft 365 features or services
User impact: Users may experience issues with multiple Microsoft 365 features or services.
More info: Impacted Microsoft 365 services and scenarios, include but aren't limited to:
- When Microsoft 365 groups become ownerless it will notify the group members via email, but users may not be able to click on the accept button to become the new owner.
Microsoft Teams impacted scenario:
- When the Microsoft Teams groups are about to expire, owners may not receive an alert to inform them of the expiration.
Microsoft Viva Engage impacted scenario:
- Users may be unable to use the bulk import functionality in Microsoft Viva Engage.
Current status: We're continuing to revert the update which is expected to be complete in our testing environment by Tuesday, February 25, 2025. Once completed, we'll initiate the reversion for affected users.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, February 3, 2025, at 10:00 PM UTC
Root cause: A recent Azure library update to improve our governance alerts is inadvertently breaking the flows for multiple Microsoft 365 services.
Next update by: Tuesday, February 25, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Feb 18 08:51:19 2025 |
|---|
| Description: | Title: Some users may experience issues with multiple Microsoft 365 features or services
User impact: Users may experience issues with multiple Microsoft 365 features or services.
More info: Impacted Microsoft 365 services and scenarios, include but aren't limited to:
- When Microsoft 365 groups become ownerless it will notify the group members via email, but users may not be able to click on the accept button to become the new owner.
Microsoft Teams impacted scenario:
- When the Microsoft Teams groups are about to expire, owners may not receive an alert to inform them of the expiration.
Microsoft Viva Engage impacted scenario:
- Users may be unable to use the bulk import functionality in Microsoft Viva Engage.
Current status: We've identified that a standard service update, intended to enhance various Microsoft 365 services, has unintentionally caused impact. We're reverting the aforementioned update to mitigate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, February 3, 2025, at 10:00 PM UTC
Root cause: A standard service update, intended to enhance various Microsoft 365 services, has unintentionally caused impact.
Next update by: Tuesday, February 18, 2025, at 4:00 PM UTC
|
|---|
|
MO1024621 - Some admins may experience delays in receiving some reports from the admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Mar 5 19:00:00 2025 |
|---|
| End Time: | Fri Mar 7 03:52:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Mar 7 22:34:11 2025 |
|---|
| Root Cause: | A service responsible for importing data didn't start correctly during a recent standard routine service deployment. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 7 22:34:11 2025 |
|---|
| Description: | Title: Some admins may experience delays in receiving some reports from the admin center
User impact: Admins may have experienced delays in receiving some reports from the admin center.
More info: The affected reports consisted of the following:
- Microsoft 365 Apps Usage
- Mailbox Usage
- SharePoint Site Usage
- OneDrive for Business Usage
- SharePoint Activity
Final status: We've observed that the remaining backlog for affected reports has completed draining and after a period of monitoring, we've confirmed impact was remediated.
Scope of impact: Impact was specific to admins located in Europe who were served through the affected infrastructure, attempting to receive some reports from the admin center.
Start time: Thursday, March 6, 2025, at 12:00 AM UTC
End time: Friday, March 7, 2025, at 8:52 AM UTC
Root cause: A service responsible for importing data didn't start correctly during a recent standard routine service deployment.
Next steps:
- To help prevent similar impact in the future, we're further reviewing the underlying cause of the service responsible for importing data not starting correctly.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 6 23:22:59 2025 |
|---|
| Description: | Title: Some admins may experience delays in receiving some reports from the admin center
User impact: Admins may experience delays in receiving some reports from the admin center.
More info: The affected reports consist of the following:
- Microsoft 365 Apps Usage
- Mailbox Usage
- SharePoint Site Usage
- OneDrive for Business Usage
- SharePoint Activity
Current status: After receiving further clarification on the type of reports affected, we've updated the Title, User Impact, and Scope of impact fields to accurately reflect the impact scenario. The backlog of Microsoft 365 Apps Usage report data has completed draining; however, we're continuing to await for the backlog for the rest of the affected report data to complete draining, which we anticipate will occur by our next scheduled update.
Scope of impact: Impact is specific to admins located in Europe who are served through the affected infrastructure, attempting to receive some reports from the admin center.
Start time: Thursday, March 6, 2025, at 12:00 AM UTC
Root cause: A service responsible for importing data didn't start correctly during a recent standard routine service deployment.
Next update by: Saturday, March 8, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Mar 6 05:41:50 2025 |
|---|
| Description: | Title: Some admins may experience delays in receiving Microsoft 365 Apps Usage reports from the admin center
User impact: Admins may experience delays in receiving Microsoft 365 Apps Usage reports from the admin center.
Current status: We've identified that a service responsible for data importing didn't start correctly during a recent standard routine service deployment. We've ensured the service has now started and we're now awaiting for a backlog of usage report data to drain for impact to be fully resolved.
Start time: Thursday, March 6, 2025, at 12:00 AM UTC
Scope of impact: Impact is specific to admins who are served through the affected infrastructure, attempting to receive Microsoft 365 Apps Usage reports from the admin center.
Root cause: A service responsible for data importing didn't start correctly during a recent standard routine service deployment.
Next update by: Friday, March 7, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Mar 6 03:59:19 2025 |
|---|
| Description: | Title: Some admins may experience delays in receiving Microsoft 365 Apps Usage reports from the admin center
User impact: Admins may experience delays in receiving Microsoft 365 Apps Usage reports from the admin center.
Current status: We're analyzing trends in service monitoring telemetry to determine our next troubleshooting steps.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure, attempting to receive Microsoft 365 Apps Usage reports from the admin center.
Next update by: Thursday, March 6, 2025, at 11:00 AM UTC
|
|---|
|
MO1021402 - Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Sun Mar 2 06:30:00 2025 |
|---|
| End Time: | Thu Mar 6 01:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Mar 7 16:47:16 2025 |
|---|
| Root Cause: | A service update intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that required an additional configuration change that wasn’t implemented ahead of time. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 7 16:47:16 2025 |
|---|
| Description: | Title: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center
User impact: Admins may be unable to create new Graph connections via the Microsoft 365 admin center.
More info: Additionally, current search index crawl schedules may not have been met, leading to stale items returned in Microsoft 365 search results.
Final status: Our fix deployment is complete, and we’ve confirmed from service telemetry that this issue is resolved.
Scope of impact: This issue may have produced Graph connection or search index crawl scheduling problems for any admin serviced by the affected portions of infrastructure in the Microsoft 365 admin center.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
End time: Thursday, March 6, 2025, at 6:00 AM UTC
Root cause: A service update intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that required an additional configuration change that wasn’t implemented ahead of time.
Next steps:
- We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Mar 5 16:56:32 2025 |
|---|
| Description: | Title: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center
User impact: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center.
More info: Additionally, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: Our deployment is continuing to progress across all impacted regions. We’re internally reviewing and analyzing ways to accelerate our fix while ensuring it successfully remediates impact, and we will provide an estimated completion timeline once one becomes available.
Scope of impact: This issue may be producing Graph connection or search index crawl scheduling problems for any admin serviced by the affected portions of infrastructure in the Microsoft 365 admin center.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that was intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Friday, March 7, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Mar 4 19:46:26 2025 |
|---|
| Description: | Title: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center
User impact: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center.
More info: Additionally, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: Our deployment of the fix within the affected region is still progressing. We're assessing options for accelerating this fix while ensuring it successfully remediates impact, and we will provide an estimated completion timeline once one becomes available.
Scope of impact: This issue may be producing Graph connection or search index crawl scheduling problems for any admin serviced by the affected portions of infrastructure in the Microsoft 365 admin center.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that was intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Wednesday, March 5, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Mar 4 11:56:05 2025 |
|---|
| Description: | Title: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center
User impact: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center.
More info: Additionally, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: After verifying the viability of our solution for remediating the impact, we're progressing with our deployment within the affected region, and we’ll provide an updated timeline for its completion and the remediation of impact once it becomes available.
Scope of impact: This issue may be producing Graph connection or search index crawl scheduling problems for any admin serviced by the affected portions of infrastructure in the Microsoft 365 admin center.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that was intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Wednesday, March 5, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Mar 4 09:22:51 2025 |
|---|
| Description: | Title: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center
User impact: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center.
More info: Additionally, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: The deployment of the fix to the remaining impacted service environments has reached the final stages of validation and deployment. We'll continue to monitor its progress to ensure impact is remediated as expected.
Scope of impact: This issue may be producing Graph connection or search index crawl scheduling problems for any admin serviced by the affected portions of infrastructure in the Microsoft 365 admin center.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that was intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Tuesday, March 4, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Mar 4 02:15:20 2025 |
|---|
| Description: | Title: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center
User impact: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center.
More info: Additionally, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: The deployment of the fix to the remaining impacted service environments is steadily progressing and has reached the final stages of validation and deployment. We're continuing to monitor its progress and we'll provide a timeline for completion once one becomes available.
Scope of impact: This issue may be producing Graph connection or search index crawl scheduling problems for any admin serviced by the affected portions of infrastructure in the Microsoft 365 admin center.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that was intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Tuesday, March 4, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 21:59:26 2025 |
|---|
| Description: | Title: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center
User impact: Admins may be unable to create new Graph connections or update current connections via the Microsoft 365 admin center.
More info: Additionally, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: We've determined that the fix deployment has completed throughout the bulk of the affected service environment. We're continuing to roll out our deployment to the remaining impacted service environments and are working towards confirming an updated timeline for overall remediation.
Scope of impact: This issue may be producing Graph connection or search index crawl scheduling problems for any admin serviced by the affected portions of infrastructure in the Microsoft 365 admin center.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that was intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Tuesday, March 4, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Mon Mar 3 12:09:24 2025 |
|---|
| Description: | Title: Admins can't create new Graph connections or update current connections via Microsoft 365 admin center
User impact: Admins may be unable create new Graph connections or update current connections via Microsoft 365 admin center.
More info: In addition, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: Our deployment is ongoing, and we’ve confirmed that it has saturated 12 percent of the affected environment. We'll provide updates on our timeline to mitigation as a better estimate becomes available.
Scope of impact: This issue may be producing Graph connection problems for any admin in the Microsoft 365 admin center, as well as may be affecting any search index crawl schedule.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Tuesday, March 4, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Mar 3 06:53:03 2025 |
|---|
| Description: | Title: Admins can't create new Graph connections or update current connections via Microsoft 365 admin center
User impact: Admins may be unable create new Graph connections or update current connections via Microsoft 365 admin center.
More info: In addition, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: We're proceeding with the deployment to all affected environments and we'll continue to monitor the fix as it propagates throughout the infrastructure.
Scope of impact: This issue may be producing Graph connection problems for any admin in the Microsoft 365 admin center, as well as may be affecting any search index crawl schedule.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Monday, March 3, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sun Mar 2 23:36:28 2025 |
|---|
| Description: | Title: Admins can't create new Graph connections or update current connections via Microsoft 365 admin center
User impact: Admins may be unable create new Graph connections or update current connections via Microsoft 365 admin center.
More info: In addition, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: We're continuing to monitor the deployment of our solution as it saturates to all affected environments. We expect some users to see impact remediation as the fix makes its way throughout the affected environments. We'll provide an update on the timeline during our next scheduled update.
Scope of impact: This issue may be producing Graph connection problems for any admin in the Microsoft 365 admin center, as well as may be affecting any search index crawl schedule.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Monday, March 3, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Sun Mar 2 18:33:18 2025 |
|---|
| Description: | Title: Admins can't create new Graph connections or update current connections via Microsoft 365 admin center
User impact: Admins may be unable create new Graph connections or update current connections via Microsoft 365 admin center.
More info: In addition, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: We’re monitoring the deployment of our solution, which is expected to remediate the impact. A timeline for the completion of the deployment has been difficult to confirm, but we're expecting an updated timeline will be available by our next scheduled update.
Scope of impact: This issue may be producing Graph connection problems for any admin in the Microsoft 365 admin center, as well as may be affecting any search index crawl schedule.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Monday, March 3, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Sun Mar 2 17:23:56 2025 |
|---|
| Description: | Title: Admins can't create new Graph connections or update current connections via Microsoft 365 admin center
User impact: Admins may be unable create new Graph connections or update current connections via Microsoft 365 admin center.
More info: In addition, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: Our internal validations have confirmed that our fix will be viable for addressing both impact scenarios without introducing any unexpected problems to affected services. We're deploying our fix, and we’ll provide an updated timeline for the remediation of impact once it has become available.
Scope of impact: This issue may be producing Graph connection problems for any admin in the Microsoft 365 admin center, as well as may be affecting any search index crawl schedule.
Start time: Sunday, March 2, 2025, at 11:30 AM UTC
Root cause: A service update that intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Monday, March 3, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Sun Mar 2 15:20:47 2025 |
|---|
| Description: | Title: Admins can't create new Graph connections or update current connections via Microsoft 365 admin center
User impact: Admins may be unable create new Graph connections or update current connections via Microsoft 365 admin center.
More info: In addition, current search index crawl schedules may not be met, leading to stale items returned in Microsoft 365 search results.
Current status: We've isolated a service update that has introduced a policy configuration issue, which is producing problems for admins when creating or updating Graph connections and search index crawl schedules. We're deploying a fix that will update the policy configuration, which we're expecting will remediate the impact.
Scope of impact: This issue may be producing Graph connection problems for any admin in the Microsoft 365 admin center, as well as may be affecting any search index crawl schedule.
Root cause: A service update that intended to address an unrelated issue had an unexpected side effect to Graph connectors and search index crawls that requires an additional configuration change that wasn’t implemented ahead of time.
Next update by: Sunday, March 2, 2025, at 10:30 PM UTC
|
|---|
|
PP1000005 - Microsoft Copilot Studio - Conversation transcripts may not be archived
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 6 18:15:00 2025 |
|---|
| End Time: | Thu Mar 6 17:56:00 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Mar 7 16:16:18 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 7 16:16:18 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Conversation transcripts may not be archived
User impact: Conversation transcripts may not have been archived.
Final Status: We completed restoring affected conversation transcripts and, following a period of monitoring, we confirmed that conversation transcripts are now being archived as expected.
This is the final update on the incident.
Preliminary Root Cause: A misconfiguration that was introduced as part of a recent service update.
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|---|
|
| Time: | Mon Mar 3 16:50:26 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Conversation transcripts may not be archived
User impact: Conversation transcripts may not be archived.
More info: Impact is limited to transcripts for conversations which took place between Wednesday, February 5, 2025, and Friday, February 7, 2025.
As we progress through the conversation transcript restoration process, some users may begin to have access to the affected conversation transcripts.
Current Status: We are continuing to restore affected conversation transcripts.
Next Update: Monday, March 10, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Feb 28 16:15:46 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Conversation transcripts may not be archived
User impact: Conversation transcripts may not be archived.
More info: Impact is limited to transcripts for conversations which took place between Wednesday, February 5, 2025, and Friday, February 7, 2025.
Current Status: We are continuing to restore affected conversation transcripts.
Next Update: Monday, March 3, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 16:15:29 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Conversation transcripts may not be archived
User impact: Conversation transcripts may not be archived.
More info: Impact is limited to transcripts for conversations which took place between Wednesday, February 5, 2025, and Friday, February 7, 2025.
Current Status: We are continuing to restore affected conversation transcripts.
Next Update: Friday, February 28, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Feb 21 16:16:04 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Conversation transcripts may not be archived
User impact: Conversation transcripts may not be archived.
More info: Impact is limited to transcripts for conversations which took place between Wednesday, February 5, 2025, and Friday, February 7, 2025.
Current Status: We are continuing to restore affected conversation transcripts.
Next Update: Tuesday, February 25, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Feb 14 16:15:52 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Conversation transcripts may not be archived
User impact: Conversation transcripts may not be archived.
More info: Impact is limited to transcripts for conversations which took place between Wednesday, February 5, 2025, and Friday, February 7, 2025.
Current Status: We are continuing to restore affected conversation transcripts.
Next Update: Friday, February 21, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Feb 10 16:21:18 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Conversation transcripts may not be archived
User impact: Conversation transcripts may not be archived.
More info: Impact is limited to transcripts for conversations which took place between Wednesday, February 5, 2025, and Friday, February 7, 2025.
Current Status: We are proceeding with the process to restore conversation transcripts.
Next Update: Friday, February 14, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Feb 7 12:46:02 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Conversation transcripts may not be archived
User impact: Conversation transcripts may not be archived.
More info: Impact is limited to transcripts for conversations which took place between Wednesday, February 5, 2025, and Friday, February 7, 2025.
Current Status: After our investigation, we identified a misconfiguration that was introduced as part of a recent service update as the source of impact. We applied a configuration change to prevent additional impact, and we are now developing a process to backfill conversation transcripts which were not archived during the period of impact.
Next Update: Monday, February 10, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Feb 7 12:25:22 2025 |
|---|
| Description: | Title: Microsoft Copilot Studio - Conversation transcripts may not be archived
User impact: Conversation transcripts may not be archived.
More info: Impact is limited to transcripts for conversations which took place between Wednesday, February 5, 2025, and Friday, February 7, 2025.
Current Status: We are aware of an emerging issue where conversation transcripts may not be archived. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
MO1025065 - Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 25 19:00:00 2025 |
|---|
| End Time: | Fri Mar 7 14:30:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Mar 7 15:18:38 2025 |
|---|
| Root Cause: | A recent service update, intended to improve user verification efficiency in a portion of service infrastructure that facilitates the authentication functionality for multiple Microsoft 365 services, introduced a code issue that was causing authentication issues for multiple functionalities, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 7 15:14:49 2025 |
|---|
| Description: | Title: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services
User impact: Users may have experienced intermittent issues syncing policies and other data in various Microsoft 365 services.
More info: Syncing for Data Loss Prevention (DLP) policies, label configurations, custom classifications, and tenant policy settings intermittently failed in clients leveraging the Messaging Identity and Provisioning (MIP) software development kit (SDK), such as the Microsoft 365 desktop clients, Microsoft Fabric, and Microsoft Defender Advanced Threat Protection.
These policy sync issues also prevented user policies that had Safe Links enabled from being honored, which caused Safe Links to be disabled.
Final status: The deployment of the code change has completed, and after monitoring telemetry to ensure service is healthy, we've verified the impact is remediated.
Scope of impact: Any user expecting their DLP policies, label configurations, custom classifications, or tenant policy settings to sync appropriately for services leveraging the Messaging Identity and Provisioning MIP SDK may have been intermittently impacted.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
End time: Friday, March 7, 2025, at 7:30 PM UTC
Root cause: A recent service update, intended to improve user verification efficiency in a portion of service infrastructure that facilitates the authentication functionality for multiple Microsoft 365 services, introduced a code issue that was causing authentication issues for multiple functionalities, resulting in impact.
Next steps:
- We're evaluating our update process to ensure adequate testing is performed on proposed changes and similar issues are caught and addressed before being deployed so this doesn't happen again.
This is the final update for the event.
|
|---|
|
| Time: | Fri Mar 7 12:38:14 2025 |
|---|
| Description: | Title: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services
User impact: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services.
More info: Syncing for Data Loss Prevention (DLP) policies, label configurations, custom classifications, and tenant policy settings intermittently fail in clients leveraging the Messaging Identity and Provisioning (MIP) software development kit (SDK), such as the Microsoft 365 desktop clients, Microsoft Fabric, and Microsoft Defender Advanced Threat Protection.
These policy sync issues also prevent user policies that have Safe Links enabled from being honored, which causes Safe Links to be disabled.
Current status: We've deployed the code change to a portion of the affected environment and confirmed through monitoring service telemetry that our fix restores the service to expected functionality. We've begun deploying the code change to the remaining affected infrastructure, and we anticipate this process will complete by our next scheduled communications update.
Scope of impact: Any user expecting their DLP policies, label configurations, custom classifications, or tenant policy settings to sync appropriately for services leveraging the Messaging Identity and Provisioning MIP SDK may be intermittently impacted.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
Estimated time to resolve: We anticipate the code change will be deployed to all affected users by Friday, March 7, 2025, at 9:30 PM UTC.
Root cause: A recent service update to a portion of service infrastructure that facilitates the authentication functionality for multiple Microsoft 365 services introduced a code issue that is causing authentication issues for multiple functionalities, resulting in impact.
Next update by: Friday, March 7, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Mar 7 07:00:49 2025 |
|---|
| Description: | Title: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services
User impact: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services.
More info: Syncing for Data Loss Prevention (DLP) policies, label configurations, custom classifications, and tenant policy settings intermittently fail in clients leveraging the Messaging Identity and Provisioning (MIP) software development kit (SDK), such as the Microsoft 365 desktop clients, Microsoft Fabric, and Microsoft Defender Advanced Threat Protection.
These policy sync issues also prevent user policies that have Safe Links enabled from being honored, which causes Safe Links to be disabled.
Current status: We're in the process of applying the code change across all affected environments and will provide a completion timeline in our next scheduled update.
Scope of impact: Any user expecting their DLP policies, label configurations, custom classifications, or tenant policy settings to sync appropriately for services leveraging the Messaging Identity and Provisioning MIP SDK may be intermittently impacted.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
Root cause: A recently deployed feature update is causing authentication issues that are resulting in impact.
Next update by: Friday, March 7, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Mar 7 00:03:16 2025 |
|---|
| Description: | Title: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services
User impact: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services.
More info: Syncing for Data Loss Prevention (DLP) policies, label configurations, custom classifications, and tenant policy settings intermittently fail in clients leveraging the Messaging Identity and Provisioning (MIP) software development kit (SDK), such as the Microsoft 365 desktop clients, Microsoft Fabric, and Microsoft Defender Advanced Threat Protection.
These policy sync issues also prevent user policies that have Safe Links enabled from being honored, which causes Safe Links to be disabled.
Current status: We've finished validating the code change and confirmed that the recently deployed feature update is causing authentication issues, leading to impact. We're initiating the process of applying this code change broadly to all affected environments. We'll provide a completion timeline when one becomes available.
Scope of impact: Any user expecting their DLP policies, label configurations, custom classifications, or tenant policy settings to sync appropriately for services leveraging the Messaging Identity and Provisioning MIP SDK may be intermittently impacted.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
Root cause: A recently deployed feature update is causing authentication issues that are resulting in impact.
Next update by: Friday, March 7, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Mar 6 22:20:04 2025 |
|---|
| Description: | Title: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services
User impact: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services.
More info: Syncing for Data Loss Prevention (DLP) policies, label configurations, custom classifications, and tenant policy settings intermittently fail in clients leveraging the Messaging Identity and Provisioning (MIP) software development kit (SDK), such as the Microsoft 365 desktop clients, Microsoft Fabric, and Microsoft Defender Advanced Threat Protection.
These policy sync issues also prevent user policies that have Safe Links enabled from being honored, which causes Safe Links to be disabled.
Current status: Our efforts to test and validate a code change to confirm our root cause theory are taking longer than anticipated but are ongoing.
Scope of impact: Any user expecting their DLP policies, label configurations, custom classifications, or tenant policy settings to sync appropriately for services leveraging the Messaging Identity and Provisioning MIP SDK may be intermittently impacted.
Next update by: Friday, March 7, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Thu Mar 6 20:10:07 2025 |
|---|
| Description: | Title: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services
User impact: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services.
More info: Syncing for Data Loss Prevention (DLP) policies, label configurations, custom classifications, and tenant policy settings intermittently fail in clients leveraging the Messaging Identity and Provisioning (MIP) software development kit (SDK), such as the Microsoft 365 desktop clients, Microsoft Fabric, and Microsoft Defender Advanced Threat Protection.
These policy sync issues also prevent user policies that have Safe Links enabled from being honored, which causes Safe Links to be disabled.
Current status: We're continuing our efforts to test a code change and validate our theory that a recently deployed feature update is the source of impact.
Scope of impact: Any user expecting their DLP policies, label configurations, custom classifications, or tenant policy settings to sync appropriately for services leveraging the Messaging Identity and Provisioning MIP SDK may be intermittently impacted.
Next update by: Friday, March 7, 2025, at 3:30 AM UTC
|
|---|
|
| Time: | Thu Mar 6 17:33:49 2025 |
|---|
| Description: | Title: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services
User impact: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services.
More info: Syncing for Data Loss Prevention (DLP) policies, label configurations, custom classifications, and tenant policy settings intermittently fail in clients leveraging the Messaging Identity and Provisioning (MIP) software development kit (SDK), such as the Microsoft 365 desktop clients, Microsoft Fabric, and Microsoft Defender Advanced Threat Protection.
These policy sync issues also prevent user policies that have Safe Links enabled from being honored, which causes Safe Links to be disabled.
Current status: We've identified that a recently deployed feature update may be causing authentication issues that are resulting in impact. We're validating this suspicion by testing a code change in a limited environment. If this proved to be a viable solution that remediates impact, we'll apply this code change to all impacted users.
Scope of impact: Any user expecting their DLP policies, label configurations, custom classifications, or tenant policy settings to sync appropriately for services leveraging the Messaging Identity and Provisioning MIP SDK may be intermittently impacted.
Next update by: Friday, March 7, 2025, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Mar 6 16:03:45 2025 |
|---|
| Description: | Title: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services
User impact: Users may experience intermittent issues syncing policies and other data in various Microsoft 365 services.
More info: Syncing for Data Loss Prevention (DLP) policies, label configurations, custom classifications, and tenant policy settings intermittently fail in clients leveraging the Messaging Identity and Provisioning (MIP) SDK, such as the Microsoft 365 desktop clients, Microsoft Fabric, and Microsoft Defender Advanced Threat Protection.
Current status: We suspect this impact may be occurring due to an authentication issue, and we're reviewing internal telemetry data to identify what is preventing these services from syncing data within an appropriate timeframe.
Scope of impact: Any user expecting their DLP policies, label configurations, custom classifications, or tenant policy settings to sync appropriately for services leveraging the Messaging Identity and Provisioning MIP SDK may be intermittently impacted.
Next update by: Thursday, March 6, 2025, at 11:00 PM UTC
|
|---|
|
MO1020913 - Some users may experience issues with one or more Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sat Mar 1 15:36:00 2025 |
|---|
| End Time: | Sat Mar 1 16:45:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Mar 7 15:01:41 2025 |
|---|
| Root Cause: | A recent configuration change, intended to implement additional telemetry within the service, contained a bug that had unintended effects on a broader authentication policy evaluation code, resulting in impact to some Microsoft 365 services and features. Specifically, this bug occurred due to a rare issue with combining different logic paths that resulted in unexpected behavior during configuration rollout process, which went undetected by our change process validation testing. Once impact was identified, we reverted the change to remediate the authentication issues. We’ve since developed and deployed a new more targeted set of changes to accomplish the intended purpose of our initial code change and have additionally revised our validation methodology to test for this scenario in future changes. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 7 15:01:41 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Mar 4 18:56:27 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sat Mar 1 18:57:34 2025 |
|---|
| Description: | Title: Some users may experience issues with one or more Microsoft 365 services
User impact: Users may have experienced issues with one or more Microsoft 365 services.
More info:
Impact scenarios from this event included:
- Users were unable to authenticate to Microsoft 365 services, including Exchange and Outlook.
- Users were able to authenticate to Microsoft Teams; however, users experienced degraded functionality including impact to chat/team creation and search.
- Users experienced issues with connectors/flows in the Microsoft Power Platform and logic apps.
- Users received 500 errors and were unable to access the Purview service.
Final status: Following our reversion of the problematic code change, we’ve monitored service telemetry and worked with previously impacted customers to confirm that service is restored.
Scope of impact: Any user attempting to access or use the services and features outlined within the 'More info' section of this communication were impacted.
Start Time: Saturday, March 1, at 8:36 PM UTC
End Time: Saturday, March 1, at 9:45 PM UTC
Root cause: A recent configuration change, intended to implement additional telemetry within the service, contained a bug that had unintended effects on a broader authentication policy evaluation code, resulting in impact to some Microsoft 365 services and features. Specifically, this bug occurred due to a rare issue with combining different logic paths that resulted in unexpected behavior during configuration rollout process, which went undetected by our change process validation testing. Once impact was identified, we reverted the change to remediate the authentication issues. We’ve since developed and deployed a new more targeted set of changes to accomplish the intended purpose of our initial code change and have additionally revised our validation methodology to test for this scenario in future changes.
Next Steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We’ll produce a preliminary post-incident report in two business days, and a final post-incident report in five business days.
|
|---|
|
| Time: | Sat Mar 1 17:49:35 2025 |
|---|
| Description: | Title: Some users may experience issues with one or more Microsoft 365 services
User impact: Users may experience issues with one or more Microsoft 365 services.
More info: Affected users may be unable to access the following Microsoft 365 services:
- Microsoft Teams
- Exchange Online and Outlook
Additionally, users may experience the following impact scenarios:
- Office 365 and Outlook connectors are unable to run flows or solutions within Microsoft Power Platform and Logic Apps.
Current status: We’ve reverted the code change and have confirmed that the service has returned to a healthy state. We’ve entered a period of extended monitoring to ensure that the service remains stable, and to address any outstanding impact to other Microsoft 365 services.
Scope of impact: Users attempting to access one or more Microsoft 365 services may be impacted.
Root Cause: A recent update to our authentication systems contained a code issue, resulting in impact.
Next update: Sunday, March 2, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Sat Mar 1 16:50:38 2025 |
|---|
| Description: | Title: Some users may experience issues with one or more Microsoft 365 services
User impact: Users may experience issues with one or more Microsoft 365 services.
More info: Affected users may be unable to access the following Microsoft 365 services:
- Microsoft Teams
- Exchange Online
Additionally, users may experience the following impact scenarios:
- Office 365 and Outlook connectors are unable to run flows or solutions within Microsoft Power Platform and Logic Apps.
Current status: We've identified a recent code change to a portion of service infrastructure that we suspect is causing impact. We've reverted the code change, and we're monitoring service health telemetry to confirm if the reversion is returning service to expected functionality.
Scope of impact: Some users attempting to access one or more Microsoft 365 services may be impacted.
Next update by: Saturday, March 1, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Sat Mar 1 16:29:53 2025 |
|---|
| Description: | Title: Some users may experience issues with one or more Microsoft 365 services
User impact: Users may experience issues with one or more Microsoft 365 services.
Current status: We're investigating a potential issue with some users being unable to access one or more Microsoft 365 services, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1012033 - Upcoming Exchange Web Services (EWS) Role Based Access Control (RBAC) changes
| Status: | investigationSuspended |
|---|
| Start Time: | Thu Feb 20 15:08:46 2025 |
|---|
| End Time: | Thu Mar 6 15:53:44 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 6 15:53:50 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 6 15:53:50 2025 |
|---|
| Description: | Title: Upcoming Exchange Web Services (EWS) Role Based Access Control (RBAC) changes
User impact: If action isn't taken, applications that leverage ApplicationImpersonation RBAC will fail.
Final Status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 20 15:14:44 2025 |
|---|
| Description: | Title: Upcoming Exchange Web Services (EWS) Role Based Access Control (RBAC) changes
User impact: If action isn't taken, applications that leverage ApplicationImpersonation RBAC will fail.
Current status: Due to the upcoming ApplicationImpersonation RBAC Role Deprecation in Exchange Online as communicated via Message Center posts MC724116, MC718746, and MC718754, applications still using this feature will no longer work starting on Monday, February 24, 2025.
This communication will expire in 14 days and remain active for the duration.
|
|---|
|
MO1017192 - Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Feb 25 19:00:00 2025 |
|---|
| End Time: | Wed Feb 26 21:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Mar 6 12:24:31 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 6 12:21:16 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Mar 3 10:05:43 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Feb 27 13:57:41 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may have been unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Final status: We’ve completed the targeted restarts on the remaining subset of affected infrastructure. We’ve verified the issue has been remediated by monitoring service health telemetry.
Scope of impact: Some users may have been unable to use features or access files which leverage Information Protection labels.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
End time: Thursday, February 27, 2025, at 2:00 AM UTC
Preliminary root cause: A recent change to Entra ID tokens, which are issued to clients for calls to the Rights Management Service (RMS), inadvertently introduced a validation issue due to a specific property containing an unexpected value. Due to this unexpected value, requests made were unable to be validated and the Entra ID tokens provided to RMS were rejected, returning a 401 error. This issue caused approximately 10% of requests to fail and resulted in users being unable to open files with Information Protection labels applied.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Feb 26 18:19:43 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: There's a small subset of remaining infrastructure that we are applying targeted restarts to. The service remains healthy for nearly all previously impacted environments. We will continue to carefully monitor this service while we complete the remaining repairs.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
Preliminary root cause: A recent change, to Entra ID tokens, that are issued to clients for calls to the Rights Management Service (RMS), contained a validation logic issue. After the change, tokens provided to RMS were rejected. This issue is causing a subset of users to experience issues opening files with Information Protection labels applied.
Next update by: Thursday, February 27, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Feb 26 14:32:44 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: We’ve observed no new instances of impact, and the service remains healthy. We're entering a period of extended monitoring to ensure there are no recurrences for the rest of peak business hours in North America.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
Preliminary root cause: A recent change, to Entra ID tokens, that are issued to clients for calls to the Rights Management Service (RMS), contained a validation logic issue. After the change, tokens provided to RMS were rejected. This issue is causing a subset of users to experience issues opening files with Information Protection labels applied.
Next update by: Wednesday, February 26, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 11:50:46 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: We’ve observed the desired effect to service health after our targeted restarts in the caching infrastructure. The majority of customer impact has been mitigated; however, we are still monitoring for any potential impact throughout peak North American business hours.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
Preliminary root cause: A recent change, to Entra ID tokens, that are issued to clients for calls to the Rights Management Service (RMS), contained a validation logic issue. After the change, tokens provided to RMS were rejected. This issue is causing a subset of users to experience issues opening files with Information Protection labels applied.
Next update by: Wednesday, February 26, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 09:01:45 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: We’ve completed the proactive restarts in the caching infrastructure to expedite service recovery. Additionally, many of the affected tokens have automatically expired, which has remediated impact for the majority of users. We’re continuing to monitor the service as the users in North American start the business day.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels. The change that caused impact was deployed to ten percent of our Worldwide infrastructure.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
Preliminary root cause: A recent change, to Entra ID tokens, that are issued to clients for calls to the Rights Management Service (RMS), contained a validation logic issue. After the change, tokens provided to RMS were rejected. This issue is causing a subset of users to experience issues opening files with Information Protection labels applied.
Next update by: Wednesday, February 26, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 04:19:58 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: Telemetry shows that our targeted restarts of caching components is having the desired effect. We’re continuing to proactively perform restarts in the caching infrastructure to expedite service recovery. Along with our proactive efforts to mitigate impact, many the affected tokens are due to automatically expire, causing new tokens to be generated, fixing the issue for the majority of users. We expect these to take an extended period of time.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels. The change that caused impact was deployed to ten percent of our Worldwide infrastructure.
Start time: Wednesday, February 26, 2025, at 12:00 AM UTC
Preliminary root cause: A recent change, to Entra ID tokens, that are issued to clients for calls to the Rights Management Service (RMS), contained a validation logic issue. After the change, tokens provided to RMS were rejected. This issue is causing a subset of users to experience issues opening files with Information Protection labels applied.
Next update by: Wednesday, February 26, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 02:28:18 2025 |
|---|
| Description: | Based on our internal telemetry and customer feedback, a majority of the impacted scenarios for this incident should be mitigated. We are continuing to address residual impact and taking proactive steps to prevent impact as we approach European business hours.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 26 02:16:37 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: We're continuing to restart the impacted service systems to ensure the cache is properly cleared and it properly updates to the correct token. We expect this process to take an extended period.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels. The offending change was deployed to ten percent of our Worldwide infrastructure.
Preliminary root cause: A recent change for Entra ID tokens issued to clients for calls the Rights Management Service (RMS) contained a validation logic issue. After the change, tokens provided to RMS were rejected. This issue is causing a subset of users to experience issues opening files with Information Protection labels applied.
Next update by: Wednesday, February 26, 2025, at 9:30 AM UTC
|
|---|
|
| Time: | Wed Feb 26 00:23:31 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: We confirmed that a recent change to the service was inadvertently impacting the Information Protection labels service and we have reverted this change. We are restarting the affected infrastructure to ensure that that reversion takes effect. In parallel, we have started to receive confirmation from reporting customers that the issue has been mitigated.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels. The offending change was deployed to ten percent of our Worldwide infrastructure.
Preliminary root cause: A recent change for Entra ID tokens issued to clients for calls the Rights Management Service (RMS) contained a validation logic issue. After the change, tokens provided to RMS were rejected. This issue is causing a subset of users to experience issues opening files with Information Protection labels applied.
Next update by: Wednesday, February 26, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Tue Feb 25 22:31:49 2025 |
|---|
| Description: | A recent change to the authentication service may be inadvertently contributing to this issue. We've reverted this change and are monitoring the service to confirm efficacy.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Feb 25 21:50:57 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: We're continuing to review our internal telemetry and data from reporting customers to determine the source of the problem.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels. Our internal telemetry indicates that this issue primarily affects users in the Asia Pacific region.
Next update by: Wednesday, February 26, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Tue Feb 25 21:18:24 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: We've received several reports of an issue impacting users' abilities to use features or access files with leverage Information Protection labels. We're reviewing diagnostic data from the affected services to better understand the cause of the issue and determine our mitigation steps.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels. Our internal telemetry indicates that this issue primarily affects users in the Asia Pacific region.
Next update by: Wednesday, February 26, 2025, at 3:30 AM UTC
|
|---|
|
TM1023171 - Users may be unable to screenshare after freshly installing Microsoft Teams for macOS version 15.x
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 24 18:24:00 2025 |
|---|
| End Time: | Thu Mar 6 06:55:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 6 12:10:31 2025 |
|---|
| Root Cause: | A recent code change for Microsoft Teams had introduced a code error for devices on macOS versions 15 and above that prevented a popup to enable screensharing from being presented to affected users. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 6 12:10:31 2025 |
|---|
| Description: | Title: Users may be unable to screenshare after freshly installing Microsoft Teams for macOS version 15.x
User impact: Users may have been unable to screenshare after freshly installing Microsoft Teams for macOS version 15.x.
More info: Affected users may have utilized the following workaround to re-enable screensharing:
1. Open System Settings
2. Select Privacy & Security
3. Select Screen & System Audio Recording
4. If Microsoft Teams was available on the list of applications, delete it by selecting it and clicking -.
5. Click on + and select Microsoft Teams from the Application folder.
6. Click on Quit & Reopen.
7. Verify Microsoft Teams was enabled in the Screen & System Audio Recording tab.
8. Relaunch Microsoft Teams.
If users were unable to directly grant these permissions, users could have contacted their admin to allow users to change screensharing permissions and they will have been able to follow the listed guidance.
Final status: We've completed the deployment of our code fix and confirmed in our service health telemetry that impact was successfully resolved.
Scope of impact: Some users may have been unable to screenshare after newly installing Microsoft Teams for macOS version 15.X.
Start time: Monday, February 24, 2025, at 11:24 PM UTC
End time: Thursday, March 6, 2025, at 11:55 AM UTC
Root cause: A recent code change for Microsoft Teams had introduced a code error for devices on macOS versions 15 and above that prevented a popup to enable screensharing from being presented to affected users.
Next steps:
- We're reviewing our code change testing and validation procedures to identify how impact was missed to better prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Mar 5 12:22:18 2025 |
|---|
| Description: | Title: Users may be unable to screenshare after freshly installing Microsoft Teams for macOS version 15.x
User impact: Users may be unable to screenshare after freshly installing Microsoft Teams for macOS version 15.x.
More info: Affected users may utilize the following workaround to re-enable screensharing:
1. Open System Settings
2. Select Privacy & Security
3. Select Screen & System Audio Recording
4. If Microsoft Teams is available on the list of applications, delete it by selecting it and clicking -.
5. Click on + and select Microsoft Teams from the Application folder.
6. Click on Quit & Reopen.
7. Verify Microsoft Teams is enabled in the Screen & System Audio Recording tab.
8. Relaunch Microsoft Teams.
If users are unable to directly grant these permissions, contact your admin to allow you to change screensharing permissions and they will be able to follow the listed guidance.
Current status: We've created and are deploying a code fix that we expect will complete and remediate impact by our next scheduled update.
Scope of impact: Some users may be unable to screenshare after newly installing Microsoft Teams for macOS version 15.X.
Root cause: A recent code change for Microsoft Teams has introduced a code error for devices on macOS versions 15 and above that prevents a popup to enable screensharing from being presented to affected users.
Next update by: Thursday, March 6, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Mar 4 11:53:54 2025 |
|---|
| Description: | Title: Users may be unable to screenshare after freshly installing Microsoft Teams for macOS version 15.x
User impact: Users may be unable to screenshare after freshly installing Microsoft Teams for macOS version 15.x.
More info: Affected users may utilize the following workaround to re-enable screensharing:
1. Open System Settings
2. Select Privacy & Security
3. Select Screen & System Audio Recording
4. If Microsoft Teams is available on the list of applications, delete it by selecting it and clicking -.
5. Click on + and select Microsoft Teams from the Application folder.
6. Click on Quit & Reopen.
7. Verify Microsoft Teams is enabled in the Screen & System Audio Recording tab.
8. Relaunch Microsoft Teams.
If users are unable to directly grant these permissions, contact your admin to allow you to change screensharing permissions and they will be able to follow the listed guidance.
Current status: We've identified that a recent code change for Microsoft Teams has introduced a code error for devices on macOS versions 15 and above that prevents a popup to enable screensharing from being presented to affected users. We're considering our options to correct the issue and remediate impact.
Scope of impact: Some users may be unable to screenshare after newly installing Microsoft Teams for macOS version 15.X.
Root cause: A recent code change for Microsoft Teams has introduced a code error for devices on macOS versions 15 and above that prevents a popup to enable screensharing from being presented to affected users.
Next update by: Wednesday, March 5, 2025, at 7:00 PM UTC
|
|---|
|
DZ1011622 - Updated attack simulations and training (AST) URL endpoint
| Status: | investigationSuspended |
|---|
| Start Time: | Thu Feb 20 07:07:21 2025 |
|---|
| End Time: | Thu Mar 6 08:56:40 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 6 08:56:47 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 6 08:56:47 2025 |
|---|
| Description: | Title: Updated attack simulations and training (AST) URL endpoint
User impact: If no action is taken, users may be unable to view assigned attack simulations and trainings.
Final Status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 20 08:02:26 2025 |
|---|
| Description: | Title: Updated attack simulations and training (AST) URL endpoint
User impact: If no action is taken, users may be unable to view assigned attack simulations and trainings.
Current status: We've made an update to the training URL endpoint that is used as part of the training player for end users. In organizations with the Microsoft Defender for Office 365 Plan 2 license (either through add-on or included in subscriptions like Microsoft 365 E5), you can use attack simulation training in the Microsoft Defender portal to run user simulations and assign training to your end users. If you are using firewalls or third-party filtering security solutions, you should allow the updated URL to ensure that the training content isn't blocked by your solution.
This communication will expire in 14 days and is scheduled to remain active for the full duration.
|
|---|
|
DZ1024627 - Some users were unable to see targeted devices while configuring specific Microsoft Defender for Endpoint policies
| Status: | serviceRestored |
|---|
| Start Time: | Sun Feb 23 23:00:00 2025 |
|---|
| End Time: | Thu Mar 6 07:18:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 6 08:14:34 2025 |
|---|
| Root Cause: | A recently applied service feature, intended to improve functionality relating to Microsoft Defender for Endpoint Asset Rule Management policies, inadvertently introduced a regression which was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 6 08:14:34 2025 |
|---|
| Description: | Title: Some users were unable to see targeted devices while configuring specific Microsoft Defender for Endpoint policies
User impact: Users were unable to see targeted devices while configuring specific Microsoft Defender for Endpoint policies.
More info: Specifically, some users may have been unable to see the targeted devices or device counts for all Microsoft Defender for Endpoint Asset Rule Management policies while attempting to configure them. Rule configuration and application itself was unaffected, however, users were unable to identify the devices or see device counts.
Final status: We've concluded the deployment of our fix, and confirmed following a monitoring period that impact to end users is remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Monday, February 24, 2025, at 4:00 AM UTC
End time: Thursday, March 6, 2025, at 12:18 PM UTC
Root cause: A recently applied service feature, intended to improve functionality relating to Microsoft Defender for Endpoint Asset Rule Management policies, inadvertently introduced a regression which was causing impact.
Next steps:
- We're reviewing upcoming service feature updates for similar regressions to minimize or prevent reoccurrence of impact.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 6 06:21:43 2025 |
|---|
| Description: | Title: Some users are unable to see targeted devices while configuring specific Microsoft Defender for Endpoint policies
User impact: Users are unable to see targeted devices while configuring specific Microsoft Defender for Endpoint policies.
More info: Specifically, some users may be unable to see the targeted devices or device counts for all Microsoft Defender for Endpoint Asset Rule Management policies while attempting to configure them. Rule configuration and application itself is unaffected, however, users are unable to identify the devices or see device counts.
Current status: We've identified that a recently applied service feature, intended to improve functionality relating to Microsoft Defender for Endpoint Asset Rule Management policies, inadvertently introduced a regression which is causing impact. We've developed and are applying a fix to correct the regression, to remediate impact. We expect to complete the deployment of our fix by the time of our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, February 24, 2025, at 12:00 AM UTC
Root cause: A recently applied service feature, intended to improve functionality relating to Microsoft Defender for Endpoint Asset Rule Management policies, inadvertently introduced a regression which is causing impact.
Next update by: Thursday, March 6, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Thu Mar 6 04:08:59 2025 |
|---|
| Description: | Title: Some users are unable to see targeted devices while configuring specific Microsoft Defender for Endpoint policies
User impact: Users are unable to see targeted devices while configuring specific Microsoft Defender for Endpoint policies.
More info: Specifically, some users may be unable to see the targeted devices or device counts for all Microsoft Defender for Endpoint Asset Rule Management policies while attempting to configure them. Rule configuration and application itself is unaffected, however, users are unable to identify the devices or see device counts.
Current status: We're conducting analysis of provided HTTP Archive HTTP Archive format (HAR) logs to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, February 24, 2025, at 12:00 AM UTC
Next update by: Thursday, March 6, 2025, at 11:30 AM UTC
|
|---|
|
DZ1024301 - Users may have seen delays up to three hours for various activity processing in Microsoft Defender for Cloud Apps
| Status: | serviceRestored |
|---|
| Start Time: | Wed Mar 5 13:00:00 2025 |
|---|
| End Time: | Wed Mar 5 19:30:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 6 03:57:34 2025 |
|---|
| Root Cause: | An issue affecting the infrastructure that facilitates the ingestion and real-time data streaming for Microsoft Defender for Cloud Apps was causing a backlog of service requests to accumulate, which resulted in the observed delays. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 6 03:57:34 2025 |
|---|
| Description: | Title: Users may have seen delays up to three hours for various activity processing in Microsoft Defender for Cloud Apps
User impact: Users may have seen delays up to three hours for various activity processing in Microsoft Defender for Cloud Apps.
More info: Uses may have experienced delays of up to three hours for activity processing in Microsoft Defender for Cloud apps, which may have affected the following scenarios:
- Alerts
- Anomaly detection
- Activity policy
- Activities for hunting
- Activities showing in the user interface (UI)
- CloudAppEvents are delayed, and custom detections might be inaccurate in Microsoft Sentinel
Final status: We’ve successfully processed the backlogged requests, and confirmed that impact has been remediated.
Scope of impact: Any user hosted on the affected infrastructure may have been impacted.
Start time: Wednesday, March 5, 2025, at 6:00 PM UTC
End time: Thursday, March 6, 2025, at 12:30 AM UTC
Root cause: An issue affecting the infrastructure that facilitates the ingestion and real-time data streaming for Microsoft Defender for Cloud Apps was causing a backlog of service requests to accumulate, which resulted in the observed delays.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed Mar 5 18:14:11 2025 |
|---|
| Description: | Title: Users may see delays up to three hours for various activity processing in Microsoft Defender for Cloud Apps
User impact: Users may see delays up to three hours for various activity processing in Microsoft Defender for Cloud Apps.
More info: Uses may see delays up to three hours for activity processing in Microsoft Defender for Cloud apps affecting the following scenarios:
- Alerts
- Anomaly detection
- Activity policy
- Activities for hunting
- Activities showing in the user interface (UI)
- CloudAppEvents are delayed, and custom detections might be inaccurate in Microsoft Sentinel
Current status: We’ve determined that an issue affecting the infrastructure that facilitates the ingestion and real-time data streaming for Microsoft Defender for Cloud Apps is causing a backlog of service requests to accumulate and is resulting in the observed delays. We’ve disabled the process of publishing requests to the affected infrastructure to mitigate the impact and we’re monitoring the processing of the backlogged requests to assess and determine an ETA for impact remediation.
Scope of impact: Any user hosted on the affected infrastructure may be impacted.
Start time: Wednesday, March 5, 2025, at 6:00 PM UTC
Root cause: An issue affecting the infrastructure that facilitates the ingestion and real-time data streaming for Microsoft Defender for Cloud Apps is causing a backlog of service requests to accumulate and resulting in the observed delays.
Next update by: Thursday, March 6, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Mar 5 16:32:56 2025 |
|---|
| Description: | Title: Users may see delays up to two hours for various activity processing in Microsoft Defender for Cloud Apps
User impact: Users may see delays up to two hours for various activity processing in Microsoft Defender for Cloud Apps.
More info: Uses may see delays up to two hours for activity processing in Microsoft Defender for Cloud apps affecting the following scenarios:
- Anomaly detection
- Activity policy
- Activities for hunting
- Activities showing in the user interface (UI)
- CloudAppEvents are delayed, and custom detections might be inaccurate in Microsoft Sentinel
Current status: We’re reviewing system logs to isolate the origin of this issue.
Scope of impact: Any user hosted on the affected infrastructure may be impacted.
Next update by: Wednesday, March 5, 2025, at 11:30 PM UTC
|
|---|
|
EX1015484 - Admins provisioning guest users in Exchange Online may see that duplicate objects are created
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 20 10:38:00 2025 |
|---|
| End Time: | Thu Feb 27 08:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 5 15:55:14 2025 |
|---|
| Root Cause: | A recent feature update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that caused some guest user data to be duplicated during provisioning, which led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 5 15:55:14 2025 |
|---|
| Description: | Title: Admins provisioning guest users in Exchange Online may see that duplicate objects are created
User impact: Admins who provisioned guest users in Exchange Online may have seen that duplicate objects were created.
More info: As a result of the duplicate objects which were provisioned, user email addressed to the newly created guest users may have failed to deliver.
Final status: While we've confirmed that our fix has sufficiently saturated enough of the environment to remediate the issue, we've also disabled the offending feature portion of the update, which mitigated impact prior to the full deployment of our fix. We've confirmed with some affected users that the issue has been resolved.
Scope of impact: Any admin who provisioned guest users in Exchange Online may have been impacted.
Start time: Thursday, February 20, 2025, at 3:38 PM UTC
End time: Thursday, February 27, 2025, at 1:00 PM UTC
Root cause: A recent feature update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that caused some guest user data to be duplicated during provisioning, which led to impact.
Next steps:
- We're continuing to review our update processes so we can better identify similar errors during our testing and development cycles and avoid comparable impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 3 15:09:08 2025 |
|---|
| Description: | Title: Admins provisioning guest users in Exchange Online may see that duplicate objects are created
User impact: Admins provisioning guest users in Exchange Online may see that duplicate objects are created.
More info: As a result of duplicate objects being provisioned, user email addressed to the newly created guest users may fail to deliver.
Current status: We've identified the saturation of the fix is taking longer than anticipated and is currently 95 percent saturated. We anticipate the majority of admins are experiencing relieve while the remaining impacted admins will be remediated by our next scheduled update.
Scope of impact: Any admin provisioning guest users in Exchange Online may be impacted.
Start time: Thursday, February 20, 2025, at 3:38 PM UTC
Root cause: A recent update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that's causing some guest user data to be duplicated during provisioning, leading to impact.
Next update by: Wednesday, March 5, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Feb 28 03:45:15 2025 |
|---|
| Description: | Title: Admins provisioning guest users in Exchange Online may see that duplicate objects are created
User impact: Admins provisioning guest users in Exchange Online may see that duplicate objects are created.
More info: As a result of duplicate objects being provisioned, user email addressed to the newly created guest users may fail to deliver.
Current status: We're in the final stages of deploying the fix and anticipate completion by Monday, March 3, 2025.
Scope of impact: Any admin provisioning guest users in Exchange Online may be impacted.
Start time: Thursday, February 20, 2025, at 3:38 PM UTC
Root cause: A recent update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that's causing some guest user data to be duplicated during provisioning, leading to impact.
Next update by: Monday, March 3, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Feb 27 05:06:31 2025 |
|---|
| Description: | Title: Admins provisioning guest users in Exchange Online may see that duplicate objects are created
User impact: Admins provisioning guest users in Exchange Online may see that duplicate objects are created.
More info: As a result of duplicate objects being provisioned, user email addressed to the newly created guest users may fail to deliver.
Current status: The fix continues to deploy to all impacted environments. We're continuing to monitor this deployment and we aim to provide an estimated completion timeline once one becomes available.
Scope of impact: Any admin provisioning guest users in Exchange Online may be impacted.
Start time: Thursday, February 20, 2025, at 3:38 PM UTC
Root cause: A recent update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that's causing some guest user data to be duplicated during provisioning, leading to impact.
Next update by: Friday, February 28, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Feb 26 02:22:10 2025 |
|---|
| Description: | Title: Admins provisioning guest users in Exchange Online may see that duplicate objects are created
User impact: Admins provisioning guest users in Exchange Online may see that duplicate objects are created.
More info: As a result of duplicate objects being provisioned, user email addressed to the newly created guest users may fail to deliver.
Current status: Our review of the recent update identified a code issue that was present, causing the increased occurrences of guest users seeing duplicate objects created. We've developed, tested, and verified a fix to address this issue, which is in the process of deploying to all impacted environments. We're monitoring this deployment and we'll provide an ETA for its completion once one becomes available.
Scope of impact: Any admin provisioning guest users in Exchange Online may be impacted.
Start time: Thursday, February 20, 2025, at 3:38 PM UTC
Root cause: A recent update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that's causing some guest user data to be duplicated during provisioning, leading to impact.
Next update by: Thursday, February 27, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Feb 25 02:19:14 2025 |
|---|
| Description: | Title: Admins provisioning guest users in Exchange Online may see that duplicate objects are created
User impact: Admins provisioning guest users in Exchange Online may see that duplicate objects are created.
More info: As a result of duplicate objects being provisioned, user email addressed to the newly created guest users may fail to deliver.
Current status: Based on feedback from affected users, this communication and previous communications have been updated for accuracy regarding guest users. Our efforts to determine the most expedient method to remediate impact are ongoing.
Scope of impact: Any admin provisioning guest users in Exchange Online may be impacted.
Start time: Thursday, February 20, 2025, at 3:38 PM UTC
Root cause: A recent update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that's causing some guest user data to be duplicated during provisioning, leading to impact.
Next update by: Wednesday, February 26, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Mon Feb 24 13:27:07 2025 |
|---|
| Description: | Title: Admins provisioning guest users in Exchange Online may see that duplicate objects are created
User impact: Admins provisioning guest users in Exchange Online may see that duplicate objects are created.
More info: As a result of duplicate objects being provisioned, user email addressed to the newly created guest users may fail to deliver.
Current status: We're continuing our efforts to identify the most expedient method to address the provisioning error leading to impact.
Scope of impact: Any admin provisioning guest users in Exchange Online may be impacted.
Start time: Thursday, February 20, 2025, at 3:38 PM UTC
Root cause: A recent update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that's causing some guest user data to be duplicated during provisioning, leading to impact.
Next update by: Tuesday, February 25, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Mon Feb 24 12:13:28 2025 |
|---|
| Description: | Title: Admins provisioning guest users in Exchange Online may see that duplicate objects are created
User impact: Admins provisioning guest users in Exchange Online may see that duplicate objects are created.
More info: As a result of duplicate objects being provisioned, user email addressed to the newly created guest users may fail to deliver.
Current status: Our investigation has determined that a recent update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that's causing some guest user data to be duplicated during provisioning, leading to impact. We're evaluating potential methods to address the provisioning error and resolve this issue.
Scope of impact: Any admin provisioning guest users in Exchange Online may be impacted.
Root cause: A recent update to the data pathways leveraged to provision new guest users in Exchange Online exposed an error that's causing some guest user data to be duplicated during provisioning, leading to impact.
Next update by: Monday, February 24, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Feb 24 11:29:35 2025 |
|---|
| Description: | Title: Admins provisioning guest users in Exchange Online may see that duplicate objects are created
User impact: Admins provisioning guest users in Exchange Online may see that duplicate objects are created.
More info: As a result of duplicate objects being provisioned, user email addressed to the newly created guest users may fail to deliver.
Current status: We're investigating a potential issue with the Exchange Online service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1020077 - Users may be unable to open some attachments from email messages in some Exchange Online connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 6 00:00:00 2025 |
|---|
| End Time: | Wed Mar 5 02:20:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 5 12:59:30 2025 |
|---|
| Root Cause: | A recent service update contained a code regression that resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 5 12:59:30 2025 |
|---|
| Description: | Title: Users may be unable to open some attachments from email messages in some Exchange Online connection methods
User impact: Users may have been unable to open some attachments from email in some Exchange Online connection methods.
More info: Files attached directly to the emails as invite attachments were affected. Cloud file attachments appeared to be unaffected by this issue. This issue also appeared to be limited to the Outlook mobile app for iOS and Android as well as Outlook for Mac.
Final status: The process of reverting the problematic service update is complete, and our telemetry confirms that this issue is resolved.
Scope of impact: Some users may have been affected when trying to open some attachments from email messages in Exchange Online.
Start time: Thursday, February 6, 2025, at 5:00 AM UTC
End time: Wednesday, March 5, 2025, at 7:20 AM UTC
Root cause: A recent service update contained a code regression that resulted in impact.
Next steps:
- We’re reviewing our service update testing and validation procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 3 11:38:19 2025 |
|---|
| Description: | Title: Users may be unable to open some attachments from email messages in some Exchange Online connection methods
User impact: Users may be unable to open some attachments from email messages in some Exchange Online connection methods.
More info: Files attached directly to the emails as invite attachments are affected. Cloud file attachments appear to be unaffected by this issue. This issue also appears to be limited to the Outlook mobile app for iOS and Android as well as Outlook for Mac.
Current status: As we continue to monitor the final stages of the roll back of the offending update, we're noting service health improving, and some users should be experiencing relief. We expect the roll back will be complete by the time of our next scheduled communication.
Scope of impact: Some users may be affected when trying to open some attachments from email messages in Exchange Online.
Start time: Thursday, February 6, 2025, at 5:00 AM UTC
Root cause: A recent service update contained a code regression that is resulting in impact.
Next update by: Wednesday, March 5, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Feb 28 19:44:14 2025 |
|---|
| Description: | Title: Users may be unable to open some attachments from email messages in some Exchange Online connection methods
User impact: Users may be unable to open some attachments from email messages in some Exchange Online connection methods.
More info: Files attached directly to the emails as invite attachments are affected. Cloud file attachments appear to be unaffected by this issue. This issue also appears to be limited to the Outlook mobile app for iOS and Android as well as Outlook for Mac.
Current status: We've confirmed that the offending update has been successfully rolled back throughout the majority of the affected service environment. We’re continuing to monitor as the reversion of the offending update completes and resolves the issue for all impacted users. We're anticipating that we'll have a precise remediation timeline by our next scheduled communications update.
Scope of impact: Some users may be affected when trying to open some attachments from email messages in Exchange Online.
Start time: Thursday, February 6, 2025, at 5:00 AM UTC
Root cause: A recent service update contained a code regression that is resulting in impact.
Next update by: Monday, March 3, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Feb 28 18:53:43 2025 |
|---|
| Description: | Title: Users may be unable to open some attachments from email messages in some Exchange Online connection methods
User impact: Users may be unable to open some attachments from email messages in some Exchange Online connection methods.
More info: Files attached directly to the emails as invite attachments are affected. Cloud file attachments appear to be unaffected by this issue. This issue also appears to be limited to the Outlook mobile app for iOS and Android as well as Outlook for Mac.
Current status: We're monitoring as the reversion of the offending update progresses, and we anticipate this should complete by the time of our next scheduled communications update.
Scope of impact: Some users may be affected when trying to open some attachments from email messages in Exchange Online.
Start time: Thursday, February 6, 2025, at 5:00 AM UTC
Root cause: A recent service update contained a code regression that is resulting in impact.
Next update by: Saturday, March 1, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Feb 28 16:37:18 2025 |
|---|
| Description: | Title: Users may be unable to open some attachments from email messages in some Exchange Online connection methods
User impact: Users may be unable to open some attachments from email messages in some Exchange Online connection methods.
More info: Files attached directly to the emails as invite attachments are affected. Cloud file attachments appear to be unaffected by this issue. This issue also appears to be limited to the Outlook mobile app for iOS and Android as well as Outlook for Mac.
Current status: We're reverting the recent service update as we've confirmed that it contains a regression. We'll provide a timeline for this process as one becomes available.
Scope of impact: Some users may be affected when trying to open some attachments from email messages in Exchange Online.
Root cause: A recent service update contained a code regression that is resulting in impact.
Next update by: Saturday, March 1, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Feb 28 15:29:35 2025 |
|---|
| Description: | Title: Some users may be unable to open some attachments from email messages in Exchange Online
User impact: Users may be unable to open some attachments from email messages in Exchange Online.
More info: Cloud attachments appear to be unaffected by this issue.
Current status: We've identified an issue in which users may be unable to open attachments from email messages in Exchange Online. We’re reviewing a recent service update to determine if this may be responsible for introducing the problem.
Scope of impact: Some users may be affected when trying to open some attachments from email messages in Exchange Online.
Next update by: Friday, February 28, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Feb 28 15:19:52 2025 |
|---|
| Description: | Title: Users may be unable to open some attachments from email messages in Exchange Online
User impact: Users may be unable to open some attachments from email messages in Exchange Online
More info: Cloud attachments appear to be unaffected by this issue.
Current status: We're investigating a potential issue in which users may be unable to open attachments from email messages in Exchange Online on iOS, Mac or Android devices. We'll provide an update within 30 minutes.
|
|---|
|
CP1012268 - Users in all regions may encounter issues with Microsoft Copilot
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Feb 20 19:22:00 2025 |
|---|
| End Time: | Thu Feb 20 22:10:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Mar 5 12:29:11 2025 |
|---|
| Root Cause: | A configuration service reference was inadvertently removed from the code, which led to access issues for certain scenarios. This missing reference resulted in the system failing to fetch the correct configuration, resulting in unauthorized errors. Engineers reverted the configuration change to a previous state to resolve the issue. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 15:39:04 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Feb 25 11:43:10 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Feb 20 23:00:11 2025 |
|---|
| Description: | Title: Users in all regions may encounter issues with Microsoft Copilot
User impact: Users in all regions may have encountered issues with Microsoft Copilot.
More info: Users may have encountered errors when submitting requests through multiple Copilot services including:
- Microsoft Bing
- Microsoft Outlook
- Microsoft Planner
- Microsoft PowerPoint
- Microsoft Teams
- Microsoft Word
- Viva Engage
- Viva Insights
Final status: We’ve completed the rollback and confirmed the issue has been remediated.
Scope of impact: Any user may have encountered errors when submitting Copilot requests across a variety of Copilot services.
Start time: Friday, February 21, 2025, at 12:22 AM UTC
End time: Friday, February 21, 2025, at 3:10 AM UTC
Root cause: A configuration service reference was inadvertently removed from the code, which led to access issues for certain scenarios. This missing reference resulted in the system failing to fetch the correct configuration, resulting in unauthorized errors. Engineers reverted the configuration change to a previous state to resolve the issue.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Feb 20 21:53:22 2025 |
|---|
| Description: | Title: Users in all regions may encounter issues with Microsoft Copilot
User impact: Users in all regions may encounter issues with Microsoft Copilot.
More info: Users are encountering “Can you try again” errors when submitting requests.
Current status: We’ve identified the potential cause of the issue and are in the process of rolling back a recent code change. We will monitor the progress of the rollout and verify it mitigates the issue.
Scope of impact: Any user may encounter errors when submitting Copilot requests.
Next update by: Friday, February 21, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Thu Feb 20 20:52:40 2025 |
|---|
| Description: | Title: Users in Australia, Japan, and North America may encounter issues with Microsoft Copilot
User impact: Users in Australia, Japan, and North America may encounter issues with Microsoft Copilot.
More info: Users are encountering “Can you try again” errors when submitting requests.
Current status: We are reviewing service telemetry and available information to determine the cause of the issue, More information can be found in the admin center under: CP1012268.
Scope of impact: Your organization is affected by this event and may encounter errors when submitting Copilot requests.
Next update by: Friday, February 21, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Feb 20 20:30:30 2025 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Copilot (Microsoft 365)
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft Copilot (Microsoft 365) and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO986359 - Some users may be unable to authenticate to Microsoft 365 apps via My Apps
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 22 14:16:00 2025 |
|---|
| End Time: | Wed Jan 22 16:40:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Mar 5 11:22:55 2025 |
|---|
| Root Cause: | Due to a recent configuration change, some service traffic routing data intended for specific internal endpoints became stale. When a SSO service call hit an affected endpoint, the request wasn't successful and caused an authentication error for the user. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jan 22 18:05:54 2025 |
|---|
| Description: | Title: Some users may be unable to authenticate to Microsoft 365 apps via My Apps
User impact: Users may have been unable to authenticate to Microsoft 365 apps through My Apps.
More info: Affected users may have seen issues while using Microsoft 365 apps through the My Apps Single Sign On (SSO) method (https://myapplications.microsoft.com/). When authenticating with SSO, impacted users may have received a message stating, "Something went wrong... Authentication error".
Final status: After a period of extended monitoring, we’ve confirmed with service health telemetry and previously affected users that reverting the recent change resolved the issue.
Scope of impact: This issue could have potentially affected any user that attempted to authenticate to Microsoft 365 through the My Apps Single Sign On (SSO) flow.
Start time: Wednesday, January 22, 2025, at 7:16 PM UTC
End time: Wednesday, January 22, 2025, at 9:40 PM UTC
Root cause: Due to a recent configuration change, some service traffic routing data intended for specific internal endpoints became stale. When a SSO service call hit an affected endpoint, the request wasn't successful and caused an authentication error for the user.
Next steps:
- We're evaluating the impacting configuration change to understand how this issue wasn't identified during our pre-deployment checks so we can avoid similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jan 22 17:04:33 2025 |
|---|
| Description: | Title: Some users may be unable to authenticate to Microsoft 365 apps
User impact: Users may be unable to authenticate to Microsoft 365 apps.
More info: Affected users may see issues while using Single Sign On (SSO) applications. When authenticating with SSO, users receive a "Something went wrong... Authentication error" message.
Current status: We're seeing recovery to the Microsoft 365 authentication infrastructure after a recent change was reverted. We're analyzing service health telemetry to confirm full resolution.
Scope of impact: This issue can potentially affect any user that's attempting to authenticate to Microsoft 365 apps when using SSO applications.
Next update by: Wednesday, January 22, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jan 22 16:47:30 2025 |
|---|
| Description: | Title: Some users may be unable to authenticate to Microsoft 365 apps
User impact: Users may be unable to authenticate to Microsoft 365 apps.
More info: It's suspected that this predominantly impacts authentication using Single Sign On (SSO) through the MyApps portal. When authenticating with SSO, users receive a "Something went wrong... Authentication error" message.
Current status: We're investigating a potential issue with the Microsoft 365 service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1018082 - Users' Microsoft Copilot (Microsoft 365) prompts may fail with an error
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Feb 26 12:56:00 2025 |
|---|
| End Time: | Wed Feb 26 13:52:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Mar 5 10:16:57 2025 |
|---|
| Root Cause: | Microsoft Copilot (Microsoft 365) leverages two different model infrastructures within Azure OpenAI (AOAI), one that is shared and one dedicated to Microsoft 365. There had been a surge in traffic to the shared infrastructure, so a change was made to implement throttling for a specific pattern that was performing the high usage requests within the shared infrastructure. The aim was to provide better service stability and protection to the shared infrastructure. This throttle change was implemented at the incorrect subscription level, which resulted in the throttle being applied within both the shared and dedicated infrastructures. This throttle was too aggressive for the dedicated infrastructure, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 5 10:16:57 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Feb 28 13:32:29 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Feb 26 14:24:24 2025 |
|---|
| Description: | Title: Users' Microsoft Copilot (Microsoft 365) prompts may fail with an error
User impact: Users' Microsoft Copilot (Microsoft 365) prompts or Copilot Agent actions may have failed with an error.
Final status: Our investigation determined that a recent internal traffic routing change intended to support Copilot traffic, caused the impact. We reverted the change and the issue has been confirmed mitigated by monitoring our service health telemetry and customers reports.
Scope of impact: Any user running prompts in Microsoft Copilot (Microsoft 365) across any protocol may have been impacted.
Start time: Wednesday, February 26, 2025, at 5:56 PM UTC
End time: Wednesday, February 26, 2025, at 6:52 PM UTC
Root cause: Microsoft Copilot (Microsoft 365) leverages two different model infrastructures within Azure OpenAI (AOAI), one that is shared and one dedicated to Microsoft 365. There had been a surge in traffic to the shared infrastructure, so a change was made to implement throttling for a specific pattern that was performing the high usage requests within the shared infrastructure. The aim was to provide better service stability and protection to the shared infrastructure. This throttle change was implemented at the incorrect subscription level, which resulted in the throttle being applied within both the shared and dedicated infrastructures. This throttle was too aggressive for the dedicated infrastructure, resulting in impact.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Feb 26 14:05:45 2025 |
|---|
| Description: | Title: Users' Microsoft Copilot (Microsoft 365) prompts may fail with an error
User impact: Users' Microsoft Copilot (Microsoft 365) prompts may fail with an error.
More Info: This issue could affect user interactions with Copilot across any connection method or protocol.
Current status: We're currently investigating the issue and all available signals to determine the next steps needed to restore the availability of the service.
Scope of impact: Any user running prompts in Microsoft Copilot (Microsoft 365) may be impacted.
Next update by: Wednesday, February 26, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Feb 26 13:39:16 2025 |
|---|
| Description: | Title: Users' Microsoft Copilot (Microsoft 365) prompts may fail with an error
User impact: Users' Copilot prompts may fail with an error.
Current status: We're investigating a potential issue with Copilot prompt failures and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1023896 - Some users may be unable to approve or reject email message soft delete actions in the Microsoft Defender XDR Action
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 3 09:00:00 2025 |
|---|
| End Time: | Wed Mar 5 07:25:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 5 08:54:29 2025 |
|---|
| Root Cause: | A recent service update, part of a scheduled routine maintenance, was inadvertently causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 5 08:53:00 2025 |
|---|
| Description: | Title: Some users may have been unable to approve or reject email message soft delete actions in the Microsoft Defender XDR Action center
User impact: Users may have been unable to approve or reject email message soft delete actions in the Microsoft Defender XDR Action center.
More info: Affected users may have seen a 404 error when attempting to perform soft delete actions. Impacted Microsoft Defender for Office scenarios included, but weren't limited to: Proposed remediation and Automated investigation and response (AIR) action approvals. As a workaround for AIR actions, users may have been able to approve actions from the Investigations page in the Microsoft Defender portal. Normal remediation flow was unaffected.
Final status: We've identified that a recently scheduled service update as part of routine maintenance had inadvertently casued impact. We've reverted the offending update, and have confirmed by monitoring service telemetry that the impact has been resolved.
Scope of impact: Impact was specific to some users, who were served through the affected infrastructure, attempting to approve or reject email message soft delete actions in the Microsoft Defender XDR Action center.
Start time: Monday, March 3, 2025 at 2:00 PM UTC
End time: Wednesday, March 5, 2025 at 12:25 PM UTC
Root cause: A recent service update, part of a scheduled routine maintenance, was inadvertently causing impact.
Next steps:
- We're reviewing our standard service update procedures to avoid similar impact in the future.
This is the final update for this event.
|
|---|
|
| Time: | Wed Mar 5 07:14:02 2025 |
|---|
| Description: | Title: Some users may be unable to approve or reject email message soft delete actions in the Microsoft Defender XDR Action center
User impact: Users may be unable to approve or reject email message soft delete actions in the Microsoft Defender XDR Action center.
More info: Affected users may see a 404 error when attempting to perform soft delete actions. Impacted Microsoft Defender for Office scenarios include, but aren't limited to: Proposed remediation and Automated investigation and response (AIR) action approvals. As a workaround for AIR actions, users may be able to approve actions from the Investigations page in the Microsoft Defender portal. Normal remediation flow is unaffected.
Current status: We're reviewing service telemetry details to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to approve or reject email message soft delete actions in the Microsoft Defender XDR Action center.
Next update by: Wednesday, March 5, 2025, at 2:30 PM UTC
|
|---|
|
MB1017050 - Some users may be unable to book appointments in Microsoft Bookings
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 25 15:05:00 2025 |
|---|
| End Time: | Tue Mar 4 04:00:00 2025 |
|---|
| Service: | Microsoft Bookings |
|---|
| Feature Group: | Microsoft Bookings |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 5 02:35:37 2025 |
|---|
| Root Cause: | A recent code change made to the Microsoft Bookings service mailbox caused the Simple Mail Transfer Protocol (SMTP) extraction from Bookings page URL to return malformed. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 5 02:25:00 2025 |
|---|
| Description: | Title: Some users may be unable to book appointments in Microsoft Bookings
User impact: Users may have been unable to book appointments in Microsoft Bookings.
Final status: After further investigating the HAR trace logs, we've determined that a recent code change made to the Microsoft Bookings service mailbox caused the Simple Mail Transfer Protocol (SMTP) extraction from Bookings page URL to return malformed. Our aforementioned two permanent fixes are currently still deploying to the affected environments, and in the meantime, we've disabled the problematic code change to quickly address the impact while our solutions finish deploying. We've received feedback from some users that disabling the change has restored the service functionality.
Scope of impact: Some users may have been unable to book appointments in Microsoft Bookings.
Start time: Tuesday, February 25, 2025, at 8:05 PM UTC
End time: Tuesday, March 4, 2025, at 9:00 AM UTC
Root cause: A recent code change made to the Microsoft Bookings service mailbox caused the Simple Mail Transfer Protocol (SMTP) extraction from Bookings page URL to return malformed.
Next steps:
- We're continuing to oversee the deployment of our two permanent fixes to ensure they complete which will help prevent similar impact from reoccurring.
This is the final update for this event.
|
|---|
|
| Time: | Wed Feb 26 02:31:05 2025 |
|---|
| Description: | Title: Some users may be unable to book appointments in Microsoft Bookings
User impact: Users may be unable to book appointments in Microsoft Bookings.
Current status: We're continuing to investigate the aforementioned HAR trace logs to identify the root cause. In the interim, we've developed two solutions that will fix the 'At sign' split error that's occurring and handle the exception in the schedule notification to mitigate the impact. Our solutions are currently being prepared for deployment, which we anticipate will have begun and completed by Wednesday, March 5, 2025.
Scope of impact: Some users may be unable to book appointments in Microsoft Bookings.
Next update by: Wednesday, March 5, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Feb 25 18:15:58 2025 |
|---|
| Description: | Title: Some users may be unable to book appointments in Microsoft Bookings
User impact: Users may be unable to book appointments in Microsoft Bookings.
Current status: We're investigating HTTP Archive (HAR) trace logs provided by affected users in order to develop a plan to mitigate impact.
Scope of impact: Some users may be unable to book appointments in Microsoft Bookings.
Next update by: Wednesday, February 26, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Feb 25 17:54:26 2025 |
|---|
| Description: | Title: Some users may be unable to book appointments in Microsoft Bookings
User impact: Users may be unable to book appointments in Microsoft Bookings.
Current status: We're investigating a potential issue with Microsoft Bookings and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1022611 - Admins may experience delays in receiving Microsoft Copilot (Microsoft 365) related reports
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 3 19:00:00 2025 |
|---|
| End Time: | Tue Mar 4 06:50:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 4 22:46:58 2025 |
|---|
| Root Cause: | An issue with the infrastructure that facilitates access to the usage reports was causing requests to get stuck and not process, which caused delays and led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 4 22:46:58 2025 |
|---|
| Description: | Title: Admins may experience delays in receiving Microsoft Copilot (Microsoft 365) related reports
User impact: Admins may have experienced delays in receiving Copilot related reports from the Microsoft 365 admin center.
More info: The impacted reports were located in the Microsoft 365 admin center and included the following reports:
- Microsoft 365 Copilot readiness report in the Usage report section
- Microsoft Usage report in the Usage report section
- Microsoft 365 Copilot Chat report in the Usage report section
- AI assistance category report in the Adoption Score section
Final status: Our investigation into the affected infrastructure's service logs determined that the issue with the infrastructure that facilitates access to the usage reports was causing requests to get stuck and not process, leading to delays. We deployed a fix to unblock the infrastructure and after a period of monitoring, we've confirmed through our logs that Copilot reports are now being delivered without delays and impact has been remediated.
Scope of impact: Any admin may have been impacted by this event and experienced delays in receiving Copilot related reports from the Microsoft 365 admin center.
Start time: Tuesday, March 4, 2025, at 12:00 AM UTC
End time: Tuesday, March 4, 2025, at 11:50 AM UTC
Root cause: An issue with the infrastructure that facilitates access to the usage reports was causing requests to get stuck and not process, which caused delays and led to impact.
Next steps:
- We're reviewing and analyzing the portion of affected infrastructure to identify changes we can make to more quickly detect and help prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 3 22:23:48 2025 |
|---|
| Description: | Title: Admins may experience delays in receiving Microsoft Copilot (Microsoft 365) related reports
User impact: Admins may experience delays in receiving Copilot related reports from the Microsoft 365 admin center.
More info: The impacted reports are located in the Microsoft 365 admin center and include the following reports:
- Microsoft 365 Copilot readiness report in the Usage report section
- Microsoft Usage report in the Usage report section
- Microsoft 365 Copilot Chat report in the Usage report section
- AI assistance category report in the Adoption Score section
Current status: Our internal monitoring systems detected latency issues with Copilot readiness reports. Our investigation has uncovered an issue within the infrastructure that facilitates access to the usage reports is causing delays, leading to impact. We're investigating the service logs now, along with monitoring the service health telemetry, which is seeing positive recovery.
Scope of impact: Any admin may be impacted by this event and experience delays in receiving Copilot related reports from the Microsoft 365 admin center.
Start time: Tuesday, March 4, 2025, at 12:00 AM UTC
Root cause: An issue with the infrastructure that facilitates access to the usage reports is causing delays, leading to impact.
Next update by: Wednesday, March 5, 2025, at 5:00 AM UTC
|
|---|
|
TM1023166 - Some users may be unable to load images within Microsoft Teams chats or channels
| Status: | serviceRestored |
|---|
| Start Time: | Tue Mar 4 10:15:00 2025 |
|---|
| End Time: | Tue Mar 4 12:15:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 4 12:52:10 2025 |
|---|
| Root Cause: | A recent service update to a portion of the Microsoft Teams service infrastructure introduced a new feature into the service that was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 4 12:40:55 2025 |
|---|
| Description: | Title: Some users may be unable to load images within Microsoft Teams chats or channels
User impact: Users may have been unable to load images within Microsoft Teams chats or channels.
Final status: We've identified a recent service update to a portion of the Microsoft Teams service infrastructure, that introduced a new feature into the service that was causing impact. We've reverted the impacting service update, and confirmed through monitoring service health telemetry that impact has been remediated.
Scope of impact: Some users hosted in the North America region attempting to load images within Microsoft Teams chats or channels may have been impacted.
Start time: Tuesday, March 4, 2025, at 3:15 PM UTC
End time: Tuesday, March 4, 2025, at 5:15 PM UTC
Root cause: A recent service update to a portion of the Microsoft Teams service infrastructure introduced a new feature into the service that was causing impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to image generation prior to deployment to prevent similar impact in the future, and to improve our pre-deployment update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 4 12:00:57 2025 |
|---|
| Description: | Title: Some users may be unable to load images within Microsoft Teams chats or channels
User impact: Users may be unable to load images within Microsoft Teams chats or channels.
Current status: We're reviewing service logging to identify the root cause of this event, so we can determine our next troubleshooting steps.
Scope of impact: Some users hosted in the North America region attempting to load images within Microsoft Teams chats or channels may be impacted.
Start time: Tuesday, March 4, 2025, at 3:15 PM UTC
Next update by: Tuesday, March 4, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Mar 4 11:45:11 2025 |
|---|
| Description: | Title: Some users may be unable to load images within Microsoft Teams chats or channels
User impact: Users may be unable to load images within Microsoft Teams chats or channels.
Current status: We're investigating a potential issue with some users being unable to load images within Microsoft Teams chats or channels, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1022875 - Some admins may be unable to access the Exchange admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Mar 4 01:58:00 2025 |
|---|
| End Time: | Tue Mar 4 08:20:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 4 12:04:17 2025 |
|---|
| Root Cause: | A section of infrastructure responsible for processing Exchange admin center access requests became unresponsive and caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 4 12:02:06 2025 |
|---|
| Description: | Title: Some admins may be unable to access the Exchange admin center
User impact: Admins may have been unable to access the Exchange admin center.
Final status: After redirecting traffic to a healthy portion of infrastructure, we confirmed through service health monitoring that impact is remediated.
Scope of impact: Impact was specific to admins who were served through the affected infrastructure and who attempted to access the Exchange admin center.
Start time: Tuesday, March 4, 2025, at 6:58 AM UTC
End time: Tuesday, March 4, 2025, at 1:20 PM UTC
Root cause: A section of infrastructure responsible for processing Exchange admin center access requests became unresponsive and caused impact.
Next steps:
- We're reviewing the portion of affected infrastructure to identify why it was unresponsive, so that we can restore its functionality and improve its resiliency against this issue to prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 4 09:34:00 2025 |
|---|
| Description: | Title: Admins may be unable to access the Exchange admin center
User impact: Admins may be unable to access the Exchange admin center.
Current status: We've identified that a section of infrastructure, responsible for processing Exchange admin center access requests, became unresponsive and resulted in impact. We've rerouted affected traffic to alternate infrastructure and are reaching out to some affected users to confirm that impact has been remediated.
Scope of impact: Impact is specific to admins, who are served through the affected infrastructure, attempting to access the Exchange admin center.
Root cause: A section of infrastructure, responsible for processing Exchange admin center access requests, became unresponsive and resulted in impact.
Next update by: Tuesday, March 4, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Mar 4 08:01:16 2025 |
|---|
| Description: | Title: Admins may be unable to access the Exchange admin center
User impact: Admins may be unable to access the Exchange admin center.
Current status: We're continuing our investigation to confirm the underlying root cause of an error in a section of infrastructure that may be causing impact to occur.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure, attempting to access the Exchange Admin Center.
Next update by: Tuesday, March 4, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Tue Mar 4 05:59:38 2025 |
|---|
| Description: | Title: Admins may be unable to access the Exchange admin center
User impact: Admins may be unable to access the Exchange admin center.
Current status: We're suspecting that an error in a section of infrastructure may be causing impact to occur. We've applied changes to the aforementioned infrastructure to validate our root cause theory, in order to develop a remediation plan.
Scope of impact: Impact is specific to admins who are served through the affected infrastructure, attempting to access the Exchange Admin Center.
Next update by: Tuesday, March 4, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Mar 4 03:54:23 2025 |
|---|
| Description: | Title: Admins are unable to access the Exchange Admin Center
User impact: Admins are unable to access the Exchange Admin Center.
Current status: We’re reviewing details provided in the support case to determine the next steps needed to resolve this issue.
Scope of impact: Your organization is affected by this event, and any admin attempting to access the Exchange Admin Center is impacted.
Next update by: Tuesday, March 4, 2025, at 11:00 AM UTC
|
|---|
|
CR1015440 - Users may be unable to create a new email template or insert dynamic text
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 13 19:00:00 2025 |
|---|
| End Time: | Mon Mar 3 03:08:00 2025 |
|---|
| Service: | Dynamics 365 Apps |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 4 06:48:24 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 4 06:48:24 2025 |
|---|
| Description: | Title: Users may be unable to create a new email template or insert dynamic text
User impact: Users may be unable to create a new email template or insert dynamic text.
Final Status: Deployment of the fix has been completed. We have confirmed via service diagnostic review that users are no longer receiving errors when creating new templates or inserting dynamics text.
This is the final update on this incident.
Preliminary Root Cause: A recent service update introduced a code regression that has led to impact.
Next Steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
|
|---|
|
| Time: | Wed Feb 26 06:51:18 2025 |
|---|
| Description: | Title: Users may be unable to create a new email template or insert dynamic text
User impact: Users may be unable to create a new email template or insert dynamic text.
More Info: Users can create new email templates by performing the following steps:
1. Click on the settings icon
2. Choose "Personalization Settings"
3. Select the email templates tab and click the "New" button.
In order to insert dynamic text, users may use the dynamic text syntax instead of the button. An example format of the dynamic text syntax:
{!entityLogicalName: fieldLogicalName;}
In the following example, the case entity logicalName is “incident.” The title filed inside the case entity logicalName is “title.” The resulting format would be:
{!incident:title;}
This will work for both custom entities and out-of-box entities. For more information on dynamic text, please visit: https://learn.microsoft.com/power-apps/user/email-dynamic-text
Current Status: Testing and validations of the hotfix have been completed. We are now finalizing the deployment schedule and are preparing for deployment.
Next Update: Tuesday, March 4, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Feb 24 10:59:05 2025 |
|---|
| Description: | Title: Users may be unable to create a new email template or insert dynamic text
User impact: Users may be unable to create a new email template or insert dynamic text.
More Info: Users can create new email templates by performing the following steps:
1. Click on the settings icon
2. Choose "Personalization Settings"
3. Select the email templates tab and click the "New" button.
In order to insert dynamic text, users may use the dynamic text syntax instead of the button. An example format of the dynamic text syntax:
{!entityLogicalName: fieldLogicalName;}
In the following example, the case entity logicalName is “incident.” The title filed inside the case entity logicalName is “title.” The resulting format would be:
{!incident:title;}
This will work for both custom entities and out-of-box entities. For more information on dynamic text, please visit: https://learn.microsoft.com/power-apps/user/email-dynamic-text
Current Status: Our investigation determined that a recent service update introduced a code regression that has led to impact. We have developed a hotfix for this issue, for which we are currently performing testing and validation before finalizing a deployment schedule.
Next Update: Wednesday, February 26, 2025, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Feb 24 10:37:44 2025 |
|---|
| Description: | Title: Users may be unable to create a new email template or insert dynamic text
User impact: Users may be unable to create a new email template or insert dynamic text.
More Info: As a workaround, users can create new email templates by performing the following steps:
1. Click on the settings icon
2. Choose "Personalization Settings"
3. Select the email templates tab and click the "New" button.
In order to insert dynamic text, users may use the dynamic text syntax instead of the button. An example format of the dynamic text syntax:
{!entityLogicalName: fieldLogicalName;}
In the following example, the case entity logicalName is “incident.” The title filed inside the case entity logicalName is “title.” The resulting format would be:
{!incident:title;}
This will work for both custom entities and out-of-box entities. For more information on dynamic text, please visit: https://learn.microsoft.com/en-us/power-apps/user/email-dynamic-text
Current Status: We are aware of an emerging issue where users encounter an error when attempting to create a new email template, and when attempting to insert dynamic text. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
DZ1021942 - Some users may observe delays for Microsoft Defender for Office 365 reporting data
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 3 01:00:00 2025 |
|---|
| End Time: | Mon Mar 3 11:12:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 3 22:37:42 2025 |
|---|
| Root Cause: | A recent change, applied to a section of infrastructure responsible for regulating report and Advanced Hunting data population, was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 3 22:37:42 2025 |
|---|
| Description: | Title: Some users may observe delays for Microsoft Defender for Office 365 reporting data
User impact: Users may have observed delays for Microsoft Defender for Office 365 reporting data.
More info: Affected users may have also observed delays to the following:
- Advanced Hunting data
- Sentinel report data
Final status: We've confirmed through an additional period of monitoring that the accumulated backlog of delayed alert data has been fully processed and the residual impact is remediated.
Scope of impact: Impact was specific to some users served through the affected infrastructure.
Start time: Monday, March 3, 2025, at 6:00 AM UTC
End time: Monday, March 3, 2025, at 4:12 PM UTC
Root cause: A recent change, applied to a section of infrastructure responsible for regulating report and Advanced Hunting data population, was resulting in impact.
Next steps:
- We're reviewing our update testing and validation methods to better identify issues such as this prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 3 10:25:53 2025 |
|---|
| Description: | Title: Some users may observe delays for Microsoft Defender for Office 365 reporting data
User impact: Users may observe delays for Microsoft Defender for Office 365 reporting data.
More info: Affected users may also observe delays to the following;
- Advanced Hunting data
- Sentinel report data
Current status: We've confirmed that our mitigation was effective, and the service has returned to expected performance levels. We're processing the accumulated backlog of a delayed alert data and we expect this process to complete, and remediate impact, by the time of our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 3, 2025, at 6:00 AM UTC
Root cause: A recent change, applied to a section of infrastructure responsible for regulating report and Advanced Hunting data population, is inadvertently causing impact.
Next update by: Tuesday, March 4, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Mon Mar 3 08:17:22 2025 |
|---|
| Description: | Title: Some users may observe delays for Microsoft Defender for Office 365 reporting data
User impact: Users may observe delays for Microsoft Defender for Office 365 reporting data.
More info: Affected users may also observe delays to the following;
- Advanced Hunting data
- Sentinel report data
Current status: We've identified that a recent change, applied to a section of infrastructure responsible for regulating report and Advanced Hunting data population, is inadvertently causing impact. We've reverted the change and have applied traffic processing capacity optimizations to remediate impact, and we're actively monitoring the service environment for signs of improvement.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 3, 2025, at 6:00 AM UTC
Root cause: A recent change, applied to a section of infrastructure responsible for regulating report and Advanced Hunting data population, is inadvertently causing impact.
Next update by: Monday, March 3, 2025, at 3:30 PM UTC
|
|---|
|
TM1019459 - Users may be unable to start live transcription during Microsoft Teams meetings
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 27 15:00:00 2025 |
|---|
| End Time: | Sat Mar 1 13:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 3 19:12:09 2025 |
|---|
| Root Cause: | A recent change has updated the default transcription policy settings, causing the allow transcription settings to get changed to false, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 3 18:04:49 2025 |
|---|
| Description: | Title: Users may be unable to start live transcription during Microsoft Teams meetings
User impact: Users may have been unable to start live transcription during Microsoft Teams meetings.
More Info: The problem was only impacting users who had changed a setting within any Microsoft Teams meetings policy from the default value.
A portion of Teams meeting policies including transcription policy weren't being enforced for Teams meetings.
This issue may have also prevented users from utilizing Copilot features within Microsoft Teams meetings.
As a workaround, admins could have tried running the following script in PowerShell and then waited for 15 minutes for the changes to take effect:
# Policy Name
$policyName =
# Get the meeting policy
$policy = Get-CsTeamsMeetingPolicy -Identity $policyName
# Update the policy with the same description to refresh
Set-CsTeamsMeetingPolicy -Identity $policyName -Description $policy.Description
Final Status: Following our final service configuration change, our testing with affected users has confirmed that impact has been remediated.
Scope of impact: This issue may have potentially impacted any user who had changed any Microsoft Teams meeting policy setting from a default value when attempting to start live transcription or when utilizing Copilot features within Microsoft Teams meetings.
Start time: Thursday, February 27, 2025, at 8:00 PM UTC
End time: Saturday, March 1, 2025, at 6:00 PM UTC
Root cause: A recent change has updated the default transcription policy settings, causing the allow transcription settings to get changed to false, resulting in impact.
Next steps:
- We're further analyzing the offending service update to help us improve our pre-deployment testing and validation processes.
This is the final update for this event.
|
|---|
|
| Time: | Sat Mar 1 15:14:21 2025 |
|---|
| Description: | Title: Users may be unable to start live transcription during Microsoft Teams meetings
User impact: Users may be unable to start live transcription during Microsoft Teams meetings.
More info: A portion of Teams meeting policies including transcription policy isn't being enforced for Teams meetings.
As a workaround, admins can try running the following script in PowerShell and then wait for 15 minutes for the changes to take effect:
# Policy Name
$policyName =
# Get the meeting policy
$policy = Get-CsTeamsMeetingPolicy -Identity $policyName
# Update the policy with the same description to refresh
Set-CsTeamsMeetingPolicy -Identity $policyName -Description $policy.Description
Current status: We've applied the final service configuration changes to fully remediate the issue. We're now awaiting verification from some of the remaining affected users that this action has successfully resolved the problem.
Scope of impact: This issue may potentially impact any user attempting to start live transcription during Microsoft Teams meetings.
Start time: Thursday, February 27, 2025, at 8:00 PM UTC
Root cause: A recent change has updated the default transcription policy settings, causing the allow transcription settings to get changed to false unexpectedly.
Next update by: Tuesday, March 4, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Sat Mar 1 01:09:41 2025 |
|---|
| Description: | Title: Users may be unable to start live transcription during Microsoft Teams meetings
User impact: Users may be unable to start live transcription during Microsoft Teams meetings.
More info: A portion of Teams meeting policies including transcription policy isn't being enforced for Teams meetings.
As a workaround, admins can try running the following script in PowerShell and then wait for 15 minutes for the changes to take a effect:
# Policy Name
$policyName =
# Get the meeting policy
$policy = Get-CsTeamsMeetingPolicy -Identity $policyName
# Update the policy with the same description to refresh
Set-CsTeamsMeetingPolicy -Identity $policyName -Description $policy.Description
Current status: We've recycled the affected caches and confirmed that over 99 percent of transcription requests are no longer impacted. However, we've identified that a small subset of users are still seeing some persistent residual impact from this issue. We're rolling out some final service configuration changes that we're anticipating will fully remediate impact for the remaining affected users and expect this may complete by our next update.
Scope of impact: This issue may potentially impact any user attempting to start live transcription during Microsoft Teams meetings.
Start time: Thursday, February 27, 2025, at 8:00 PM UTC
Root cause: A recent change has updated the default transcription policy settings, causing the allow transcription settings to get changed to false unexpectedly.
Next update by: Sunday, March 2, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Feb 28 16:22:59 2025 |
|---|
| Description: | Title: Users may be unable to start live transcription during Microsoft Teams meetings
User impact: Users may be unable to start live transcription during Microsoft Teams meetings.
More info: A portion of Teams meeting policies including transcription policy isn't being enforced for Teams meetings.
As a workaround, admins can try running the following script in PowerShell and then wait for 15 minutes for the changes to take a effect:
# Policy Name
$policyName =
# Get the meeting policy
$policy = Get-CsTeamsMeetingPolicy -Identity $policyName
# Update the policy with the same description to refresh
Set-CsTeamsMeetingPolicy -Identity $policyName -Description $policy.Description
Current status: We've further identified that two different cache services involved during the process of setting the transcription policy settings are retaining these settings even after our reversion of the impacting change. We've begun manually recycling these caches, one of which is dependent on the other, and have identified an overall reduction in errors, such that we’re seeing only five percent of requests to start live transcription hitting the issue at this time. We're running a script to manually recycle these caches, and once these cache recycles are complete, we anticipate the issue will be fully resolved. We're working to determine a timeline for remediation for all users.
Scope of impact: This issue may potentially impact any user attempting to start live transcription during Microsoft Teams meetings.
Start time: Thursday, February 27, 2025, at 8:00 PM UTC
Root cause: A recent change has updated the default transcription policy settings, causing the allow transcription settings to get changed to false unexpectedly.
Next update by: Saturday, March 1, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Fri Feb 28 11:19:18 2025 |
|---|
| Description: | Title: Users may be unable to start live transcription during Microsoft Teams meetings
User impact: Users may be unable to start live transcription during Microsoft Teams meetings.
More info: A portion of Teams meeting policies including transcription policy isn't being enforced for Teams meetings.
As a workaround, admins can try running the following script in PowerShell and then wait for 15 minutes for the changes to take a effect:
# Policy Name
$policyName =
# Get the meeting policy
$policy = Get-CsTeamsMeetingPolicy -Identity $policyName
# Update the policy with the same description to refresh
Set-CsTeamsMeetingPolicy -Identity $policyName -Description $policy.Description
Current status: We're continuing to work with affected users and monitor service health telemetry to confirm if the reversion of the impacting service update has remediated the impact.
Scope of impact: This issue may potentially impact any user attempting to start live transcription during Microsoft Teams meetings.
Start time: Thursday, February 27, 2025, at 8:00 PM UTC
Root cause: A recent change has updated the default transcription policy settings, causing the allow transcription settings to get changed to false unexpectedly.
Next update by: Friday, February 28, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Feb 28 05:51:50 2025 |
|---|
| Description: | Title: Users may be unable to start live transcription during Microsoft Teams meetings
User impact: Users may be unable to start live transcription during Microsoft Teams meetings.
More info: A portion of Teams meeting policies including transcription policy is not being enforced for Teams meetings.
As a workaround, admins can try running the following script in PowerShell and then wait for 15 minutes for the changes to take a effect:
# Policy Name
$policyName =
# Get the meeting policy
$policy = Get-CsTeamsMeetingPolicy -Identity $policyName
# Update the policy with the same description to refresh
Set-CsTeamsMeetingPolicy -Identity $policyName -Description $policy.Description
Current status: We've finished reverting the offending change and are now testing with affected users to confirm that impact has been resolved.
Scope of impact: This issue may potentially impact any user attempting to start live transcription during Microsoft Teams meetings.
Root cause: A recent change has updated the default transcription policy settings, causing the allow transcription settings to get changed to false unexpectedly.
Next update by: Friday, February 28, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Feb 28 04:12:49 2025 |
|---|
| Description: | Title: Users may be unable to start live transcription during Microsoft Teams meetings
User impact: Users may be unable to start live transcription during Microsoft Teams meetings.
More info: A portion of Teams meeting policies including transcription policy is not being enforced for Teams meetings.
Current status: We've confirmed that the recent policy change previously mentioned is the source of the issue. We're preparing to revert the offending change to resolve impact for affected users.
Scope of impact: This issue may potentially impact any user attempting to start live transcription during Microsoft Teams meetings.
Root cause: A recent change has updated the default transcription policy settings is causing the allow transcription settings to get changed to false unexpectedly.
Next update by: Friday, February 28, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Fri Feb 28 02:02:52 2025 |
|---|
| Description: | Title: Users may be unable to start live transcription during Microsoft Teams meetings
User impact: Users may be unable to start live transcription during Microsoft Teams meetings.
Current status: We can see in the logs that the allow transcription policy settings are showing correctly, however we've identified a recent change that may have updated the default transcription policy settings, potentially causing the allow transcription settings to get changed to false unexpectedly. We're reviewing the recent update to confirm if there were any updates to the allow transcription policy settings.
Scope of impact: This issue may potentially impact any user attempting to start live transcription during Microsoft Teams meetings.
Next update by: Friday, February 28, 2025, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Feb 27 23:53:42 2025 |
|---|
| Description: | Title: Users are unable to start live transcription during Microsoft Teams meetings
User impact: Users are unable to start live transcription during Microsoft Teams meetings.
Current status: We're analyzing system logs to identify any issues with the transcription policy settings, which will help us determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and the issue may impact any user attempting to start live transcription during Microsoft Teams meetings.
Next update by: Friday, February 28, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Thu Feb 27 23:31:14 2025 |
|---|
| Description: | Title: Users are unable to start live transcription during Microsoft Teams meetings
User impact: Users are unable to start live transcription during Microsoft Teams meetings.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1022146 - Users may see delays for multiple scenarios in Microsoft Defender for Cloud Apps
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 3 05:15:00 2025 |
|---|
| End Time: | Mon Mar 3 15:30:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 3 16:34:11 2025 |
|---|
| Root Cause: | The deployment of a recent service update in parallel with an issue occurring on infrastructure responsible for publishing events to Microsoft Defender for Cloud apps introduced latency, creating delays in processing and a backlog of events. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 3 16:30:34 2025 |
|---|
| Description: | Title: Users may see delays for multiple scenarios in Microsoft Defender for Cloud Apps
User impact: Users may have seen delays for multiple scenarios in Microsoft Defender for Cloud Apps.
More info: Impacted scenarios included:
- Anomaly detection wasn't triggering alerts
- Activity policy wasn't triggering alerts
- Activities weren't available for hunting
- Activities weren't showing in User Interface (UI)
- CloudAppEvents were delayed, and custom detections might have been inaccurate in Microsoft Sentinel
Final status: After our reallocation of resources to the impacted infrastructure, and our processing of a collection of backlogged requests, our internal telemetry has verified that impact has been remediated.
Scope of impact: This issue may have impacted any user attempting to view the impacted scenarios in Microsoft Defender for Cloud Apps.
Start time: Monday, March 3, 2025, at 10:15 AM UTC
End time: Monday, March 3, 2025, at 8:30 PM UTC
Root cause: The deployment of a recent service update in parallel with an issue occurring on infrastructure responsible for publishing events to Microsoft Defender for Cloud apps introduced latency, creating delays in processing and a backlog of events.
Next steps:
- We're further analyzing the recent service update deployment so we can help isolate and address similar problems during our pre-deployment testing and validation processes.
This is the final update for this event.
|
|---|
|
| Time: | Mon Mar 3 12:47:55 2025 |
|---|
| Description: | Title: Users may see delays for multiple scenarios in Microsoft Defender for Cloud Apps
User impact: Users may see delays for multiple scenarios in Microsoft Defender for Cloud Apps.
More info: Impacted scenarios include:
- Anomaly detection is not triggering alerts
- Activity policy is not triggering alerts
- Activities aren't available for hunting
- Activities aren't showing in User Interface (UI)
- CloudAppEvents are delayed and custom detections might be inaccurate in Microsoft Sentinel
Current status: We've identified that the deployment of a recent service update in parallel with an issue occurring on infrastructure responsible for publishing events to Microsoft Defender for Cloud apps introduced latency; creating delays in processing and a backlog of events. We've reallocated resources to the impacted processing infrastructure as a means of remediating impact. Additionally, we've restarted the impacted infrastructure in an effort to ensure the additional resources are picked up as expected. We're monitoring the service to confirm that the backlog processes as expected and impact is remediated.
Scope of impact: This issue may impact any user attempting to view the impacted scenarios in Microsoft Defender for Cloud Apps.
Start time: Monday, March 3, 2025, at 10:15 AM UTC
Root cause: The deployment of a recent service update in parallel with an issue occurring on infrastructure responsible for publishing events to Microsoft Defender for Cloud apps introduced latency; creating delays in processing and a backlog of events.
Next update by: Monday, March 3, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 3 12:36:08 2025 |
|---|
| Description: | Title: Users may see delays for multiple scenarios in Microsoft Defender for Cloud Apps
User impact: Users may see delays for multiple scenarios in Microsoft Defender for Cloud Apps.
More info: Impacted scenarios include:
- Anomaly detection is not triggering alerts
- Activity policy is not triggering alerts
- Activities aren't available for hunting
- Activities aren't showing in User Interface (UI)
- CloudAppEvents are delayed and custom detections might be inaccurate in Microsoft Sentinel
Current status: We're investigating a potential issue with Microsoft Defender for Cloud Apps and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1015106 - Some users may experience default language setting changes and issues downloading attachments in Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 21 21:00:00 2025 |
|---|
| End Time: | Mon Mar 3 11:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 3 15:55:54 2025 |
|---|
| Root Cause: | A recent service update meant to change how the language setting is stored in Outlook on the web was causing the service to identify the setting as not configured and introduces a conflict. This conflict may have prevented users from downloading attachments from shared mailboxes or if their default language was set to a non-English option; the language setting would default to English. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 3 15:54:57 2025 |
|---|
| Description: | Title: Some users may experience default language setting changes and issues downloading attachments in Outlook on the web
User impact: Users may have experienced issues with language settings and downloading attachments in Outlook on the web.
More info: Users were automatically defaulted to English for Outlook on the web when their default language setting was set to a non-English language. Users could manually reset their desired language as a temporary workaround. However, upon refreshing, signing out, or closing their tab, the language was reverted back to English.
In addition, users may have been unable to download or preview attachments from shared mailboxes in Outlook on the web. The Outlook desktop client and mobile apps were unaffected by this issue. Users that downloaded attachments from their own mailbox or any non-shared mailbox were unaffected.
Final status: We've confirmed that the saturation of the fix completed and validated with internal testing that the impact is remediated.
Scope of impact: Some users may have been impacted if their default language was set to a non-English option in Outlook on the web, or if they were attempting to download or preview attachments from a shared mailbox.
Start time: Saturday, February 22, 2025, at 2:00 AM UTC
End time: Monday, March 3, 2025, at 4:00 PM UTC
Root cause: A recent service update meant to change how the language setting is stored in Outlook on the web was causing the service to identify the setting as not configured and introduces a conflict. This conflict may have prevented users from downloading attachments from shared mailboxes or if their default language was set to a non-English option; the language setting would default to English.
Next steps:
- We're further reviewing the service update to understand what specific aspect of the code caused the service to identify the setting as not configured, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 28 14:13:04 2025 |
|---|
| Description: | Title: Some users may experience default language setting changes and issues downloading attachments in Outlook on the web
User impact: Users may experience issues with language settings and downloading attachments in Outlook on the web.
More info: Users are automatically defaulted to English for Outlook on the web when their default language setting is set to a non-English language. Users can manually reset their desired language as a temporary workaround. However, upon refreshing, signing out, or closing their tab, the language is reverted back to English.
In addition, users may be unable to download or preview attachments from shared mailboxes in Outlook on the web. The Outlook desktop client and mobile apps are unaffected by this issue. Users downloading attachments from their own mailbox or any non-shared mailbox are also unaffected.
Current status: Our fix has now reached approximately 85 percent of the impacted environment. We're monitoring its progress as it continues to saturate to the affected environment. At this time, the majority of affected users should be experiencing remediation.
Scope of impact: Some users may be impacted if their default language is set to a non-English option in Outlook on the web, or if they're attempting to download or preview attachments from a shared mailbox.
Start time: Saturday, February 22, 2025, at 2:00 AM UTC
Root cause: A recent service update meant to change how the language setting is stored in Outlook on the web is causing the service to identify the setting as not configured and introduces a conflict. This conflict may prevent users from downloading attachments from shared mailboxes or if their default language is set to a non-English option; the language setting will default to English.
Next update by: Monday, March 3, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Feb 27 18:39:28 2025 |
|---|
| Description: | Title: Some users may experience default language setting changes and issues downloading attachments in Outlook on the web
User impact: Users may experience issues with language settings and downloading attachments in Outlook on the web.
More info: Users are automatically defaulted to English for Outlook on the web when their default language setting is set to a non-English language. Users can manually reset their desired language as a temporary workaround. However, upon refreshing, signing out, or closing their tab, the language is reverted back to English.
In addition, users may be unable to download or preview attachments from shared mailboxes in Outlook on the web. The Outlook desktop client and mobile apps are unaffected by this issue. Users downloading attachments from their own mailbox or any non-shared mailbox are also unaffected.
Current status: We've confirmed that our fix has saturated approximately 70 percent of the affected environment, and the majority of affected users should be experiencing relief at this time. We're continuing to monitor to ensure that our fix's saturation completes and resolves the issue as expected.
Scope of impact: Some users may be impacted if their default language is set to a non-English option in Outlook on the web, or if they're attempting to download or preview attachments from a shared mailbox.
Start time: Saturday, February 22, 2025, at 2:00 AM UTC
Root cause: A recent service update meant to change how the language setting is stored in Outlook on the web is causing the service to identify the setting as not configured and introduces a conflict. This conflict may prevent users from downloading attachments from shared mailboxes or if their default language is set to a non-English option; the language setting will default to English.
Next update by: Friday, February 28, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 20:36:53 2025 |
|---|
| Description: | Title: Some users may experience default language setting changes and issues downloading attachments in Outlook on the web
User impact: Users may experience issues with language settings and downloading attachments in Outlook on the web.
More info: Users are automatically defaulted to English for Outlook on the web when their default language setting is set to a non-English language. Users can manually reset their desired language as a temporary workaround. However, upon refreshing, signing out, or closing their tab, the language is reverted back to English.
In addition, users may be unable to download or preview attachments from shared mailboxes in Outlook on the web. The Outlook desktop client and mobile apps are unaffected by this issue. Users downloading attachments from their own mailbox or any non-shared mailbox are also unaffected.
Current status: Our fix's deployment is taking longer than originally anticipated, and we've observed that it's approximately 30 percent complete. We're continuing to monitor its progress so we can provide a revised resolution timeline.
Scope of impact: Some users may be impacted if their default language is set to a non-English option in Outlook on the web, or if they're attempting to download or preview attachments from a shared mailbox.
Start time: Saturday, February 22, 2025, at 2:00 AM UTC
Root cause: A recent service update meant to change how the language setting is stored in Outlook on the web is causing the service to identify the setting as not configured and introduces a conflict. This conflict may prevent users from downloading attachments from shared mailboxes or if their default language is set to a non-English option; the language setting will default to English.
Next update by: Friday, February 28, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Feb 26 14:53:15 2025 |
|---|
| Description: | Title: Some users may experience default language setting changes and issues downloading attachments in Outlook on the web
User impact: Users may experience issues with language settings and downloading attachments in Outlook on the web.
More info: Users are automatically defaulted to English for Outlook on the web when their default language setting is set to a non-English language. Users can manually reset their desired language as a temporary workaround. However, upon refreshing, signing out, or closing their tab, the language is reverted back to English.
In addition, users may be unable to download or preview attachments from shared mailboxes in Outlook on the web. The Outlook desktop client and mobile apps are unaffected by this issue. Users downloading attachments from their own mailbox or any non-shared mailbox are also unaffected.
Current status: Our deployment of the fixed build to the affected service environment is ongoing and we anticipate this process to be completed by the time of our next scheduled update where we then aim to test if impact is resolved. Some users may currently experience early relief due to the reversion being complete in the impacted environment.
Scope of impact: Some users may be impacted if their default language is set to a non-English option in Outlook on the web, or if they're attempting to download or preview attachments from a shared mailbox.
Start time: Saturday, February 22, 2025, at 2:00 AM UTC
Root cause: A recent service update meant to change how the language setting is stored in Outlook on the web is causing the service to identify the setting as not configured and introduces a conflict, which may prevent users from downloading attachments from shared mailboxes or if their default language is set to a non-English option.
Next update by: Thursday, February 27, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Feb 25 14:42:02 2025 |
|---|
| Description: | Title: Some users may experience default language setting changes and issues downloading attachments in Outlook on the web
User impact: Users may experience issues with language settings and downloading attachments in Outlook on the web.
More info: Users are automatically defaulted to English for Outlook on the web when their default language setting is set to a non-English language. Users can manually reset their desired language as a temporary workaround. However, upon refreshing, signing out, or closing their tab, the language is reverted back to English.
In addition, users may be unable to download or preview attachments from shared mailboxes in Outlook on the web. The Outlook desktop client and mobile apps are unaffected by this issue. Users downloading attachments from their own mailbox or any non-shared mailbox are also unaffected.
Current status: We've completed our development of the previously mentioned reversion for the impacting update, and we're initiating deployment to the affected service environment. We're aiming to provide a timeline to remediation in our next scheduled communications update. Some users may experience early relief as the reversion progresses throughout the impacted environment.
Scope of impact: Some users may be impacted if their default language is set to a non-English option in Outlook on the web, or if they're attempting to download or preview attachments from a shared mailbox.
Start time: Saturday, February 22, 2025, at 2:00 AM UTC
Root cause: A recent service update meant to change how the language setting is stored in Outlook on the web is causing the service to identify the setting as not configured and introduces a conflict, which may prevent users from downloading attachments from shared mailboxes or if their default language is set to a non-English option.
Next update by: Wednesday, February 26, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 12:21:21 2025 |
|---|
| Description: | Title: Some users may experience default language setting changes and issues downloading attachments in Outlook on the web
User impact: Users may experience issues with language settings and downloading attachments in Outlook on the web.
More info: Users are automatically defaulted to English for Outlook on the web when their default language setting is set to a non-English language. Users can manually reset their desired language as a temporary workaround. However, upon refreshing, signing out, or closing their tab, the language is reverted back to English.
In addition, users may be unable to download or preview attachments from shared mailboxes in Outlook on the web. The Outlook desktop client and mobile apps are unaffected by this issue. Users downloading attachments from their own mailbox or any non-shared mailbox are also unaffected.
Current status: We've determined that this issue also impacts the default language setting if a user is set to a non-English language, and have updated the Title, User impact, More info, and Scope of impact sections to reflect this. While we were preparing the code fix for deployment, we determined that reverting the impacting update is a more expedient option for remediation and have started the reversion process.
Scope of impact: Some users may be impacted if their default language is set to a non-English option in Outlook on the web, or if they're attempting to download or preview attachments from a shared mailbox.
Root cause: A recent service update meant to change how the language setting is stored in Outlook on the web is causing the service to identify the setting as not configured and introduces a conflict, which may prevent users from downloading attachments from shared mailboxes or if their default language is set to a non-English option.
Next update by: Tuesday, February 25, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 17:04:11 2025 |
|---|
| Description: | Title: Some users may be unable download attachments from shared mailboxes via Outlook on the web
User impact: Users may be unable download attachments from shared mailboxes via Outlook on the web.
Current status: We're continuing to prepare our code fix for deployment. We expect the code fix will begin deployment by the end of Wednesday, February 26, 2025, and remediate impact by the end of the following day, Thursday, February 27, 2025.
Scope of impact: Some users attempting to download attachments from shared mailboxes via Outlook on the web may be impacted.
Root cause: A recent service update meant to change how the language setting is stored in Outlook on the web is causing the service to identify the setting as not configured and introduces a conflict, which may prevent users from downloading attachments from shared mailboxes.
Next update by: Wednesday, February 26, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 16:02:05 2025 |
|---|
| Description: | Title: Some users may be unable download attachments from shared mailboxes via Outlook on the web
User impact: Users may be unable download attachments from shared mailboxes via Outlook on the web.
Current status: We've identified that a recent service update meant to change how the language setting is stored in Outlook on the web is causing the service to identify the setting as not configured and introduces a conflict, which may prevent users from downloading attachments from shared mailboxes. We're created a code fix that is being prepared for deployment and we'll provide a timeline for remediation if one becomes available.
Scope of impact: Some users attempting to download attachments from shared mailboxes via Outlook on the web may be impacted.
Root cause: A recent service update meant to change how the language setting is stored in Outlook on the web is causing the service to identify the setting as not configured and introduces a conflict, which may prevent users from downloading attachments from shared mailboxes.
Next update by: Monday, February 24, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 11:04:35 2025 |
|---|
| Description: | Title: Some users may be unable download attachments from shared mailboxes via Outlook on the web
User impact: Users may be unable download attachments from shared mailboxes via Outlook on the web.
Current status: We're continuing our investigation into diagnostic data as we isolate the source for this event, so we can determine our next troubleshooting steps for remediating the impact.
Scope of impact: Some users attempting to download attachments from shared mailboxes via Outlook on the web may be impacted.
Next update by: Monday, February 24, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 09:29:17 2025 |
|---|
| Description: | Title: Some users may be unable download attachments from shared mailboxes via Outlook on the web
User impact: Users may be unable download attachments from shared mailboxes via Outlook on the web.
Current status: Following analysis of Torus server and network trace logs, we've identified a number of 400, 404 and 500 error codes which may be contributing towards impact. We're working to determine the cause of the observed error exceptions, before we assess potential mitigation options.
Scope of impact: Some users attempting to download attachments from shared mailboxes via Outlook on the web may be impacted.
Next update by: Monday, February 24, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Mon Feb 24 07:15:59 2025 |
|---|
| Description: | Title: Some users may be unable download attachments from shared mailboxes via Outlook on the web
User impact: Users may be unable download attachments from shared mailboxes via Outlook on the web.
Current status: We're progressing with our review of the aforementioned diagnostic data to identify the cause of impact.
Scope of impact: Some users attempting to download attachments from shared mailboxes via Outlook on the web may be impacted.
Next update by: Monday, February 24, 2025, at 2:30 PM UTC
|
|---|
|
| Time: | Mon Feb 24 05:41:19 2025 |
|---|
| Description: | Title: Some users may be unable download attachments from shared mailboxes via Outlook on the web
User impact: Users may be unable download attachments from shared mailboxes via Outlook on the web.
Current status: We're conducting analysis of HTTP Archive format (HAR) logs and screenshots of the issue provided by some reporting users to isolate the root cause and formulate a mitigation plan.
Scope of impact: Some users attempting to download attachments from shared mailboxes via Outlook on the web may be impacted.
Next update by: Monday, February 24, 2025, at 12:30 PM UTC
|
|---|
|
| Time: | Mon Feb 24 03:09:13 2025 |
|---|
| Description: | Title: Some users may be unable download attachments from shared mailboxes via Outlook on the web
User impact: Users may be unable download attachments from shared mailboxes via Outlook on the web.
Current status: We're reviewing support case details to understand more about the issue, and inform our next troubleshooting steps.
Scope of impact: Some users attempting to download attachments from shared mailboxes via Outlook on the web may be impacted.
Next update by: Monday, February 24, 2025, at 10:30 AM UTC
|
|---|
|
FL1022347 - Users received intermittent 401 errors when running flows that utilized a subset of connectors
| Status: | serviceRestored |
|---|
| Start Time: | Sat Mar 1 15:40:00 2025 |
|---|
| End Time: | Sat Mar 1 16:50:00 2025 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 3 15:23:23 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 3 15:16:13 2025 |
|---|
| Description: | Title: Users received intermittent 401 errors when running flows that utilized a subset of connectors
User impact: Users received intermittent 401 errors when running flows that utilized a subset of connectors.
More Info: This issue affected the following connectors:
-Office 365
-Office 365 Users
-Office 365 Groups Mail
-OneDrive for Business
-Outlook.com
Final Status: Our internal monitoring alerted us to a spike in connector request errors, leading to intermittent failures when users attempted to run flows that utilized a subset of Power Platform connectors. Our investigation determined that a code regression contained in a recent change to a portion of the service infrastructure responsible for processing these requests as the cause of the failures. We performed a rollback of this change, restoring functionality.
This is the final update on the incident.
Preliminary Root Cause: A code regression contained in a recent change.
Next Steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
|
|---|
|
DZ1021186 - Some users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 12 19:00:00 2025 |
|---|
| End Time: | Mon Mar 3 03:14:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 3 11:14:41 2025 |
|---|
| Root Cause: | A recent service update, which was intended to change certain back-end endpoints for Microsoft Defender Vulnerability Management, resulted in impact due to a missing configuration change that was not transferred over when the endpoints were changed. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 3 11:14:41 2025 |
|---|
| Description: | Title: Some users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale
User impact: Users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may have been stale.
Final status: We've confirmed that our deployment of the new configuration fix has completed in all affected environments. After a period of monitoring internal service telemetry to ensure new data was being provided to the Vulnerability Devices Report page, we confirmed the impact is resolved.
Scope of impact: Impact was specific to some users who are served through the affected infrastructure.
Start time: Thursday, February 13, 2025, at 12:00 AM UTC
End time: Monday, March 3, 2025, at 8:14 AM UTC
Root cause: A recent service update, which was intended to change certain back-end endpoints for Microsoft Defender Vulnerability Management, resulted in impact due to a missing configuration change that was not transferred over when the endpoints were changed.
Next steps:
- We're continuing to analyze and review the affected service update to better understand why impact wasn’t caught during the testing and validation phase in order to prevent similar impact from occurring in future and to continue our ongoing efforts to improve the resiliency of our service for all users.
This is the final update for the event.
|
|---|
|
| Time: | Sun Mar 2 13:59:00 2025 |
|---|
| Description: | Title: Some users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale
User impact: Users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale.
Current status: Our deployment of the new configuration fix is progressing to all affected environments, and we anticipate this process will be complete by the time of our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, February 13, 2025, at 12:00 AM UTC
Estimated time to resolve: We anticipate impact to be resolved by the time of our next scheduled update on Monday, March 3, 2025, at 7:30 PM UTC.
Root cause: A recent service update, which was intended to change certain back-end endpoints for Microsoft Defender Vulnerability Management, resulted in impact due to a missing configuration change that was not transferred over when the endpoints were changed.
Next update by: Monday, March 3, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Sun Mar 2 13:11:03 2025 |
|---|
| Description: | Title: Some users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale
User impact: Users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale.
Current status: We've determined that a recent service update, which was intended to change certain back-end endpoints for Microsoft Defender Vulnerability Management, resulted in impact due to a missing configuration change that was not transferred over when the endpoints were changed. We're deploying a new configuration fix to resolve the missing change and to ensure all endpoints are being called correctly for user data.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, February 13, 2025, at 12:00 AM UTC
Root cause: A recent service update, which was intended to change certain back-end endpoints for Microsoft Defender Vulnerability Management, resulted in impact due to a missing configuration change that was not transferred over when the endpoints were changed.
Next update by: Sunday, March 2, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Sun Mar 2 07:40:28 2025 |
|---|
| Description: | Title: Some users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale
User impact: Users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale.
Current status: We've identified that a recent change is causing impact to occur. We're reviewing the recent change to identify why it was introduced and develop a mitigation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Sunday, March 2, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Sun Mar 2 06:05:37 2025 |
|---|
| Description: | Title: Some users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale
User impact: Users' Microsoft Defender Vulnerability Management data in the Vulnerability Devices Report page may be stale.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Sunday, March 2, 2025, at 1:30 PM UTC
|
|---|
|
TM1021256 - Some users’ location status may have appeared incorrect in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Sun Mar 2 02:30:00 2025 |
|---|
| End Time: | Mon Mar 3 04:05:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Mar 3 09:35:24 2025 |
|---|
| Root Cause: | A recent service update, intended to resolve an unrelated issue, caused a section of service infrastructure that facilitates location statuses in Microsoft Teams to fail. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 3 09:31:30 2025 |
|---|
| Description: | Title: Some users’ location statuses may have appeared incorrect in Microsoft Teams
User impact: Users’ location statuses may have appeared incorrect in Microsoft Teams.
More info: Real-time work location updates weren't working for users. Work location status displayed user locations (Office, Remote) within the Microsoft Teams client.
Final status: We've deployed the fix and confirmed after a period of monitoring that impact is no longer occurring.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Sunday, March 2, 2025, at 7:30 AM UTC
End time: Monday, March 3, 2025, at 9:05 PM UTC
Root cause: A recent service update, intended to resolve an unrelated issue, caused a section of service infrastructure that facilitates location statuses in Microsoft Teams to fail.
Next steps:
- We're reviewing our service update procedures to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Sun Mar 2 13:37:21 2025 |
|---|
| Description: | Title: Some users’ location status may be appearing incorrect in Microsoft Teams
User impact: Users’ location status may be appearing incorrect in Microsoft Teams.
More info: Real- time work location updates aren’t working for users. Work location status displays user locations (Office, Remote) within the Microsoft Teams client.
Current status: Our additional analysis into the problem has determined that user presence statuses aren’t affected by the isolated service update, and only users' location statuses are appearing incorrectly in Microsoft Teams. We've updated the Title, User Impact, More Info, and Root cause portions of our communications to reflect this new understanding. After developing a fix to address the impacted subset of service infrastructure that’s producing incorrect location statuses for Microsoft Teams, we're monitoring the deployment to verify that its completion remediates impact as expected. Our fix deployment timeline expects for the deployment will have completed and that impact will be remediated by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Sunday, March 2, 2025, at 7:30 AM UTC
Root cause: A recent service update, intended to resolve an unrelated issue, caused a section of service infrastructure that facilitates location statuses in Microsoft Teams to fail.
Next update by: Monday, March 3, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Sun Mar 2 09:43:33 2025 |
|---|
| Description: | Title: Some users’ location or presence statuses may be appearing incorrect in Microsoft Teams
User impact: Users’ location or presence statuses may be appearing incorrect in Microsoft Teams.
Current status: We've identified that a recent service update, intended to resolve an unrelated issue, inadvertently caused a section of service infrastructure that facilitates location or presence statuses in Microsoft Teams to fail. We're developing a fix in order to remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Sunday, March 2, 2025, at 7:30 AM UTC
Root cause: A recent service update, intended to resolve an unrelated issue, inadvertently caused a section of service infrastructure that facilitates location or presence statuses in Microsoft Teams to fail.
Next update by: Sunday, March 2, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Sun Mar 2 09:14:06 2025 |
|---|
| Description: | Title: Some users’ location or presence statuses may be appearing incorrect in Microsoft Teams
User impact: Users’ location or presence statuses may be appearing incorrect in Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Sunday, March 2, 2025, at 4:30 PM UTC
|
|---|
|
TM1021519 - Some users may be unable to create new chats in Microsoft Teams iOS client on certain iPhone models
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 12 19:00:00 2025 |
|---|
| End Time: | Mon Mar 3 00:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Mar 3 01:37:38 2025 |
|---|
| Root Cause: | A recent configuration change update to the Microsoft Teams iOS client contained a code issue that prevented users from creating new chats as expected on certain iPhone models. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 3 01:34:27 2025 |
|---|
| Description: | Title: Some users may be unable to create new chats in Microsoft Teams iOS client on certain iPhone models
User impact: Users may have been unable to create new chats in Microsoft Teams iOS client on certain iPhone models.
Final status: We've completed reverting the offending configuration change to disable the offending code and validated with internal testing that the impact is remediated.
Start time: Thursday, February 13, 2025, at 12:00 AM UTC
End time: Monday, March 3, 2025, at 5:30 AM UTC
Root cause: A recent configuration change update to the Microsoft Teams iOS client contained a code issue that prevented users from creating new chats as expected on certain iPhone models.
Scope of impact: Some users on certain iPhone devices that were attempting to create new chats in the Microsoft Teams iOS client may have been impacted.
Next steps:
- We're further reviewing the recent update to understand how the code issue was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 3 00:34:38 2025 |
|---|
| Description: | Title: Some users may be unable to create new chats in Microsoft Teams iOS client on iPhone SE devices
User impact: Users may be unable to create new chats in Microsoft Teams iOS client on iPhone SE devices.
More info: As a way to avoid this issue, users can rotate their phone to appear in landscape mode and tap on the user to successfully start a new chat.
Current status: We've identified a recent configuration change update to the Microsoft Teams iOS client contains a code issue that's preventing users from creating new chats as expected on iPhone SE devices. We're reverting the offending configuration change to disable the offending code and anticipate the impact will be remediated and the service functionality will be restored by our next scheduled update.
Start time: Thursday, February 13, 2025, at 12:00 AM UTC
Root cause: A recent configuration change update to the Microsoft Teams iOS client contains a code issue that's preventing users from creating new chats as expected on iPhone SE devices.
Scope of impact: Some users on iPhone SE devices that are attempting to create new chats in the Microsoft Teams iOS client may be impacted.
Next update by: Monday, March 3, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Sun Mar 2 22:52:10 2025 |
|---|
| Description: | Title: Users may be unable to create new chats in the Microsoft Teams mobile client
User impact: Users may be unable to create new chats in the Microsoft Teams mobile client.
More info: As a way to avoid this issue, users can rotate their phone to appear in landscape mode and tap on the user to successfully start a new chat.
Current status: We're continuing to investigate if any recent updates may be contributing to impact to help isolate the root cause.
Scope of impact: Some users on specific iOS device that are attempting to create new chats in the Microsoft Teams mobile client may be impacted.
Next update by: Monday, March 3, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Sun Mar 2 21:58:29 2025 |
|---|
| Description: | Title: Users may be unable to create new chats in the Microsoft Teams mobile client
User impact: Users may be unable to create new chats in the Microsoft Teams mobile client.
More info: As a way to avoid this issue, users can rotate their phone to appear in landscape mode and tap on the user to successfully start a new chat.
Current status: We've received reports of an issue in which users may be unable to create new chats in the Microsoft Teams mobile client. We've been able to reproduce the issue on mobile devices in our testing environment and are reviewing if any recent updates may be contributing to impact.
Scope of impact: Some users on specific iOS device that are attempting to create new chats in the Microsoft Teams mobile client may be impacted.
Next update by: Monday, March 3, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Sun Mar 2 21:31:23 2025 |
|---|
| Description: | Title: Users may be unable to create new chats in the Microsoft Teams mobile client
User impact: Users may be unable to create new chats in the Microsoft Teams mobile client.
More info: As a way to avoid this issue, users can rotate their phone to appear in landscape mode and tap on the user to successfully start a new chat.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PL1019250 - Some users may be missing a certain filter option and user details in Microsoft Planner
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 20 15:22:00 2025 |
|---|
| End Time: | Fri Feb 28 15:37:00 2025 |
|---|
| Service: | Planner |
|---|
| Feature Group: | Planner |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 28 21:40:59 2025 |
|---|
| Root Cause: | Some configuration changes contained within a recent regularly scheduled service update intended to improve the user experience were resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 21:10:15 2025 |
|---|
| Description: | Title: Some users may be missing a certain filter option and user details in Microsoft Planner
User impact: Users may have been missing a certain filter option and user details in Microsoft Planner.
More info: Users couldn't use the “Filter by keyword” option when they attempted to access Microsoft Planner from Microsoft Teams. Additionally, users' profile pictures and initials were not always shown on Basic Microsoft Planner tasks or when assigning tasks to users.
The user detail impact may have affected users leveraging any Microsoft Planner access method, including Planner on the web or Microsoft Planner within Microsoft Teams.
Final status: We've confirmed via internal validations and an extended period of monitoring that the service rollback has completed and has successfully resolved the issue.
Scope of impact: Users serviced by the affected portions of infrastructure who utilized Microsoft Planner for the involved scenarios may have been impacted.
Start time: Thursday, February 20, 2025, at 8:22 PM UTC
End time: Friday, February 28, 2025, at 8:37 PM UTC
Root cause: Some configuration changes contained within a recent regularly scheduled service update intended to improve the user experience were resulting in impact.
Next steps:
- We'll review our service update validation process to identify possible refinements in order to prevent similar instances of this issue in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 27 19:29:50 2025 |
|---|
| Description: | Title: Some users may be missing a certain filter option and user details in Microsoft Planner
User impact: Users may be missing a certain filter option and user details in Microsoft Planner.
More info: Users can't use the “Filter by keyword” option when accessing Microsoft Planner from Microsoft Teams. Additionally, users' profile pictures and initials are not always shown on Basic Microsoft Planner tasks or when assigning tasks to users.
The user detail impact may affect users leveraging any Microsoft Planner access method, including Planner on the web or Microsoft Planner within Microsoft Teams.
Current status: We've identified that some configuration changes contained within a recent regularly scheduled service update intended to improve the user experience are resulting in impact. We've taken action to roll back the offending changes throughout the affected environment and anticipate this process will complete by the time of our next scheduled update, at which point we'll test to confirm impact is fully remediated.
Scope of impact: Users serviced by the affected portions of infrastructure utilizing Microsoft Planner for the involved scenarios may be impacted.
Start time: Thursday, February 20, 2025, at 8:22 PM UTC
Root cause: Some configuration changes contained within a recent regularly scheduled service update intended to improve the user experience are resulting in impact.
Next update by: Saturday, March 1, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Feb 27 19:09:33 2025 |
|---|
| Description: | Title: Some users may be missing a certain filter option and user details in Microsoft Planner
User impact: Users may be missing a certain filter option and user details in Microsoft Planner.
More info: Users can't use the “Filter by keyword” option when accessing Microsoft Planner from Microsoft Teams channels. Additionally, users' profile pictures and initials are not always shown on Basic Microsoft Planner tasks.
The user detail impact may affect users leveraging any Microsoft Planner access method, including Planner on the web or the Microsoft Planner app within Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Planner and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1012469 - Some users' calendars may not be synced with delegates' calendars in Exchange Online
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sat Feb 15 02:32:00 2025 |
|---|
| End Time: | Fri Feb 21 22:25:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 28 16:42:13 2025 |
|---|
| Root Cause: | We've provided details of the root cause within the Post-Incident Report (PIR). |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 16:42:13 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Feb 21 23:39:55 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may have not been synced with delegates' calendars in Exchange Online.
Final status: We've determined that the fix deployment completed, and after a period of monitoring, we confirmed impact was remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure that were attempting to view their calendars synced with delegates' calendars in Exchange Online.
Start time: Saturday, February 15, 2025, at 7:32 AM UTC
End time: Saturday, February 22, 2025, at 3:25 AM UTC
Root cause: We've provided details of the root cause within the Post-Incident Report (PIR).
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 21 18:47:44 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may not be synced with delegates' calendars in Exchange Online.
Current status: While our deployment of the fix to the remaining portions of affected telemetry progresses, we're monitoring our service health telemetry and will provide a timeline for the completion of the deployment as one becomes available.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that are attempting to view their calendars synced with delegates' calendars in Exchange Online.
Start time: Saturday, February 15, 2025, at 7:32 AM UTC
Root cause: A recent deployment contains a code issue that introduced a compatibility problem that's preventing calendars from syncing as expected.
Next update by: Saturday, February 22, 2025, at 5:30 AM UTC
|
|---|
|
| Time: | Fri Feb 21 17:31:37 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may not be synced with delegates' calendars in Exchange Online.
Current status: Our service health monitoring shows recovery within the infrastructure we've deployed our solution to and we expect that service is now restored for some users. We've initiated the deployment to the remaining portions of affected infrastructure and are monitoring our deployment telemetry to confirm that the fix continues to progress as expected.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that are attempting to view their calendars synced with delegates' calendars in Exchange Online.
Start time: Saturday, February 15, 2025, at 7:32 AM UTC
Root cause: A recent deployment contains a code issue that introduced a compatibility problem that's preventing calendars from syncing as expected.
Next update by: Saturday, February 22, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Feb 21 15:36:54 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may not be synced with delegates' calendars in Exchange Online.
Current status: We’re seeing positive progress with the expedited deployments to a subset of service infrastructure. We’re continuing to monitor service health telemetry to verify recovery within the infrastructure we've applied our solution to. Once we've verified the fix, we will deploy broadly to all affected infrastructure.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that are attempting to view their calendars synced with delegates' calendars in Exchange Online.
Start time: Saturday, February 15, 2025, at 7:32 AM UTC
Root cause: A recent deployment contains a code issue that introduced a compatibility problem that's preventing calendars from syncing as expected.
Next update by: Friday, February 21, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Feb 21 13:23:59 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may not be synced with delegates' calendars in Exchange Online.
More info: While we work towards resolution, affected delegates can mitigate impact by navigating in the Outlook desktop client to File > Account Settings > their delegate account > More Settings > Advanced and turning off the "Turn on shared calendar improvements" setting. This will revert those delegates to using a shared calendar model utilizing Messaging API (MAPI) components to bypass impact.
Current status: We’ve deployed the fix to an additional subset of service infrastructure to further validate the fix's efficacy directly with impacted users. We’re performing expedited deployments to speed up this process, and we’re continuing to monitor service health telemetry to verify recovery within the infrastructure we've applied our solution to.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that are attempting to view their calendars synced with delegates' calendars in Exchange Online.
Start time: Saturday, February 15, 2025, at 7:32 AM UTC
Root cause: A recent deployment contains a code issue that introduced a compatibility problem that's preventing calendars from syncing as expected.
Next update by: Friday, February 21, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Feb 21 11:53:25 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may not be synced with delegates' calendars in Exchange Online.
More info: While we work towards resolution, affected delegates can mitigate impact by navigating in the Outlook desktop client to File > Account Settings > their delegate account > More Settings > Advanced and turning off the "Turn on shared calendar improvements" setting. This will revert those delegates to using a shared calendar model utilizing Messaging API (MAPI) components to bypass impact.
Current status: We've monitored service health telemetry which indicates a positive trend towards service recovery in the portion of the service we've deployed the fix to. We're preparing to deploy the fix to an additional subset of service infrastructure to further validate the fix's efficacy directly with impacted users to confirm mitigation prior to broad deployment.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, that are attempting to view their calendars synced with delegates' calendars in Exchange Online.
Start time: Saturday, February 15, 2025, at 7:32 AM UTC
Root cause: A recent deployment contains a code issue that introduced a compatibility problem that's preventing calendars from syncing as expected.
Next update by: Friday, February 21, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Feb 21 10:27:00 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may not be synced with delegates' calendars in Exchange Online.
More info: While we work towards resolution, affected delegates can mitigate impact by navigating in the Outlook desktop client to File > Account Settings > their delegate account > More Settings > Advanced and turning off the "Turn on shared calendar improvements" setting. This will revert those delegates to using a shared calendar model utilizing Messaging API (MAPI) components to bypass impact.
Current status: We're continuing to validate the fix on a small portion of the service to ensure its effectiveness. If successful, we'll begin deployment to the remaining affected infrastructure. Additionally, we're reviewing options to expedite the deployment where possible.
Root cause: A recent deployment contained a code issue that introduced a compatibility problem that's preventing calendars from syncing as expected.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, that are attempting to view their calendars synced with delegates' calendars in Exchange Online.
Next update by: Friday, February 21, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Feb 21 07:11:20 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may not be synced with delegates' calendars in Exchange Online.
More info: While we work towards resolution, affected delegates can mitigate impact by navigating in the Outlook desktop client to File > Account Settings > their delegate account > More Settings > Advanced and turning off the "Turn on shared calendar improvements" setting. This will revert those delegates to using a shared calendar model utilizing Messaging API (MAPI) components to bypass impact.
Current status: We've identified that a change within a recently applied service update, intended to improve request management to calendar synchronization, is causing impact. We've validated a fix and have started deploying it to a section of affected infrastructure to validate its effectiveness. If it successfully mitigates impact, we will deploy the fix to the remaining affected infrastructure
Root cause: A recent deployment contained a code issue that introduced a compatibility problem that's preventing calendars from syncing as expected.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, that are attempting to view their calendars synced with delegates' calendars in Exchange Online.
Next update by: Friday, February 21, 2025, at 4:00 PM UTC
|
|---|
|
| Time: | Fri Feb 21 01:48:19 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may not be synced with delegates' calendars in Exchange Online.
More info: While we work towards resolution, affected delegates can mitigate impact by navigating in the Outlook desktop client to File > Account Settings > their delegate account > More Settings > Advanced and turning off the "Turn on shared calendar improvements" setting. This will revert those delegates to using a shared calendar model utilizing Messaging API (MAPI) components to bypass impact.
Current status: We've received reports of an issue in which some users' calendars may not be synced with delegates' calendars in Exchange Online. Our investigation determined that a recent deployment contained a code issue that introduced a compatibility problem that's preventing calendars from syncing as expected. We've reverted the offending deployment and identified an increase in backlog data that's continuously preventing the calendars from syncing. We're further investigating the source of the increase in backlog to identify an efficient remediation plan to restore service functionality. We anticipate being able to provide a resolution timeline by our next scheduled update.
Root cause: A recent deployment contained a code issue that introduced a compatibility problem that's preventing calendars from syncing as expected.
Scope of impact: Some users that are attempting to view their calendars synced with delegates' calendars in Exchange Online may be impacted.
Next update by: Monday, February 24, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Fri Feb 21 01:26:17 2025 |
|---|
| Description: | Title: Some users' calendars may not be synced with delegates' calendars in Exchange Online
User impact: Users' calendars may not be synced with delegates' calendars in Exchange Online.
More info: While we work towards resolution, affected delegates can mitigate impact by navigating in the Outlook desktop client to File > Account Settings > their delegate account > More Settings > Advanced and turning off the "Turn on shared calendar improvements" setting. This will revert those delegates to using a shared calendar model utilizing Messaging API (MAPI) components to bypass impact.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1010087 - Some users' Exchange Online shared calendars may be out of sync
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Feb 10 14:33:00 2025 |
|---|
| End Time: | Thu Feb 20 17:13:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 28 16:40:35 2025 |
|---|
| Root Cause: | We've provided details of the root cause within the Post-Incident Report (PIR). |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 16:40:35 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Feb 20 19:33:40 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may have been out of sync.
Final status: After monitoring and reviewing our service telemetry, we've confirmed that our deployment successfully completed its release and impact has been remediated.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars were out of sync may have been impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
End time: Thursday, February 20, 2025, at 10:15 PM UTC
Root cause: We've provided details of the root cause within the Post-Incident Report (PIR).
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 20 17:21:51 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: Our telemetry has validated that the errors have decreased in the applicable environments. We're continuing to monitor as the deployment completes its release.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Friday, February 21, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Feb 20 12:46:01 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: While we continue to deploy the fix to the remaining affected users, some users may already experience their services restored. Our service health monitors indicate a steady decrease in errors, and we expect the impact to be remediated by the time of our next update.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Thursday, February 20, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Feb 20 10:01:53 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: The deployment of the fix to the remaining affected environments continues and we're also conducting monitoring to ensure it's effectively mitigating impact for end users.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Thursday, February 20, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Feb 20 08:48:47 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: We've successfully validated the effectiveness of the fix in a section of infrastructure and are now proceeding with a deployment to the remaining affected environments.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Thursday, February 20, 2025, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Feb 20 05:20:40 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: The issue with our deployment pipelines has been mitigated. We've started to deploy the fix to a section of infrastructure to validate the fix's efficacy, which we expect will be completed by our next scheduled update. Once validated, we'll start deploying the fix to the remaining affected infrastructures to fully remediate impact.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Thursday, February 20, 2025, at 2:30 PM UTC
|
|---|
|
| Time: | Wed Feb 19 20:46:36 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: Our operation to deploy the previously mentioned fix is taking longer than expected due to an unrelated issue within our deployment pipelines. We're working to resolve this issue as quickly as possible, after which we'll initiate the deployment and provide a timeline to remediation.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Thursday, February 20, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Wed Feb 19 16:28:14 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: After initially deploying the fix to a small portion of the affected environment for validations, which were positive, we're continuing with deployment of the fix to the North America region. We'll perform additional validations to ensure the fix continues to work as expected with no adverse impacts while determining a timeline for the overall deployment.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Thursday, February 20, 2025, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Feb 19 07:52:13 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: We’ve identified that an additional fix is required to fully remediate impact. We've developed and are validating it's efficacy prior to starting a deployment to affected users.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Wednesday, February 19, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Feb 19 03:53:44 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: Our fix has been applied to the majority of affected users, for whom we anticipate the issue should no longer occur. We're continuing to monitor the deployment of our fix to ensure it applies to the remaining affected infrastructure without issue.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Wednesday, February 19, 2025, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Feb 18 23:57:37 2025 |
|---|
| Description: | Title: Some users' Exchange Online shared calendars may be out of sync
User impact: Users' Exchange Online shared calendars between principal and delegates may be out of sync.
Current status: We've been alerted through our monitoring system and received customer reports indicating that a calendar sync issue is occurring. We've identified an impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars. We're reverting this impacting configuration change to remediate impact and anticipate this process will be completed by our next scheduled update.
Scope of impact: Some users serviced by the affected infrastructure whose shared calendars are out of sync may be impacted by this event.
Start time: Monday, February 10, 2025, at 7:33 PM UTC
Root cause: An impacting traffic management configuration change to the Calendar Replication service, which is responsible for facilitating the sync process between the principal and delegate calendars, is leading to impact.
Next update by: Wednesday, February 19, 2025, at 9:30 AM UTC
|
|---|
|
MO941162 - Users may be unable to access or use some Microsoft 365 services and features
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sun Nov 24 20:20:00 2024 |
|---|
| End Time: | Tue Nov 26 06:00:00 2024 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Feb 28 16:03:02 2025 |
|---|
| Root Cause: | Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and affected servers' processing capabilities, which led to impact. More details is provided within the Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 16:02:19 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jan 31 14:22:22 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Dec 31 13:22:31 2024 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Dec 3 16:50:02 2024 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Dec 2 13:33:40 2024 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Nov 27 20:11:12 2024 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Nov 26 14:51:32 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact scenarios were as follows:
Exchange Online
- Users may have been unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may have experienced mail transport delays.
Microsoft Teams
- Users may have been unable to create or update Virtual Events, including webinars and Town Halls.
- Users may have been unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users may have been unable to create chat, add users and create or edited meetings.
- Users may have been unable to create or modify new teams and channels.
- Users may have been unable to update presence.
- Users may have been unable to use the search function.
- Users may not have seen an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may have been unable to access the Purview Portal, or Purview Solutions.
- Users may have experienced delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may have been unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may have been unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may have been unable to use the search feature.
Microsoft Defender for Office365 and the XDR portal
- Users may have been unable to create simulations, simulation payloads or end user notifications.
- Users may have experienced issues with delivery for end user notifications and simulation messages.
- Some users may have experienced failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may have experienced issues with viewing simulation reports, and content.
- Users may have received a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may have been unable to Print via Universal Print.
- Users may have been unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may have been unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may have experienced errors when running flows that utilize cloud connectors.
Microsoft Bookings
- Users may have been unable to access their bookings.
Microsoft Viva Engage
- Users may have been unable to load topics in feeds and threads.
- Users may have seen searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not have shown user names.
- Users may not have been able to load their home feeds.
Microsoft Copilot
- Users may have been unable to use the personal Copilot panel in meetings and post meetings.
- Users may have been unable to see historic Copilot conversation history in meetings and post meetings.
- Users may have been unable to load Copilot experiences within the Viva Engage service.
- Users may have been unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may have received an apology or "at capacity" message.
Final Status: After a period of extended monitoring, we’ve confirmed through customer reports and service health telemetry that the issue is resolved.
Scope of impact: This issue could have impacted any user hosted globally; however, users experienced varying degrees of impact depending on how they were routed through the affected infrastructure and what action they were trying to perform. Impacted users who attempted to use the functionalities outlined in the More info section of this communication may have been affected by this event
Start time: Monday, November 25, 2024, at 1:20 AM UTC
End time: Tuesday, November 26, 2024, at 11:00 AM UTC
Root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and affected servers' processing capabilities, which led to impact. More details is provided within the Post-Incident Report.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We've provided a Post-Incident Report for this incident. Additionally, we'll be updating the Post-Incident Report on a monthly basis, for the next six months, to show the status of the Next Steps. The third update was provided on February 28, 2025. The next update will be provided by March 31, 2025.
|
|---|
|
| Time: | Tue Nov 26 12:57:25 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature.
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experience issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: We’re continuing to conduct additional optimizations to further improve service availability, which remains in a healthy state. We're monitoring telemetry closely while this work progresses to ensure service availability is fully restored.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Nov 26 10:58:10 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature.
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experience issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: We’re conducting additional optimizations to further improve service availability, which remains healthy. We're closing in on a full mitigation to address any remaining impact and we're closely monitoring telemetry to ensure this trend continues.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Nov 26 07:53:55 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature.
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experience issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: We’re continuing our period of monitoring service telemetry, which shows the service availability has remained healthy.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Nov 26 05:59:36 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature.
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experience issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: From monitoring service telemetry, most users should now experience relief. We’ve completed our optimizations and we're continuing our period of extended monitoring to ensure the availability remains stable.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Nov 26 05:02:46 2024 |
|---|
| Description: | While we continue our period of extended monitoring, the availability of the Outlook on the Web service has reached expected availability levels. We’re continuing to optimize the environment to address the remaining impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Nov 26 04:03:46 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature.
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experience issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current Status: We're still addressing the remaining impact to the Outlook on the web service that is affecting some users. We’ve applied mitigation actions to reduce the mail queues and we’re continuing the extended period of monitoring to ensure stability continues.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Nov 26 03:04:35 2024 |
|---|
| Description: | We’ve isolated the cause of mail queue delays and have restarted the affected infrastructure to drain stalled queues. We’ll remain in an extended monitoring phase until this draining is completed and we can consider the incident fully recovered.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Nov 26 00:04:19 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature.
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experience issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: We're continuing to address lingering impact to the Outlook on the web service that is still affecting some users. In parallel, we're investigating some mail queuing delays that is resulting in mail taking longer than expected to be delivered. Due to the impact of this incident, we will enter a period of extended monitoring prior to declaring this issue resolved.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Nov 25 23:32:26 2024 |
|---|
| Description: | Impact to core services have been restored with the exception of Outlook on the web, which we’ll continue to monitor and actively troubleshoot until full recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Nov 25 22:31:02 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature.
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experience issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: We’ve successfully restored functionality for all previously impacted services and users with the exception of Outlook on the web, which is showing prolonged impact for a small number of users. We’ll continue carefully monitoring the service health and focus on troubleshooting this persisting impact to fully recover for the remaining affected users. We'll provide a new timeline within the next update.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Nov 25 21:10:49 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading the calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see an updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature.
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experience issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors when running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: Our monitoring indicates that a large portion of affected users and services are seeing recovery following our mitigation efforts. We're working on addressing the lingering regions that are still seeing small impact to fully restore service availability, which we still expect to complete by Tuesday, November 26, 2024, at 3:00 AM UTC.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Estimated time to resolve: We estimate full recovery by Tuesday, November 26, 2024, at 3:00 AM UTC.
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 3:30 AM UTC
|
|---|
|
| Time: | Mon Nov 25 19:01:40 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels.
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature.
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experiences issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: The service is continuing to incrementally recover. We're forecasting that impact will be fully remediated by Tuesday, November 26, 2024, at 3:00 AM UTC, though we're closely monitoring our progress and will provide an updated timeline should the estimate change.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Estimated time to resolve: We estimate full recovery by Tuesday, November 26, 2024, at 3:00 AM UTC.
Preliminary root cause: Due to a recent change that decommissioned a backend service, requests were directed to an incorrect endpoint. This resulted in request handling issues and ultimately affected machines' processing capabilities, which led to impact.
Next update by: Tuesday, November 26, 2024, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Nov 25 17:09:45 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels within
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature within
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experiences issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: We identified a change in the environment that resulted in an influx in request retries routed through affected servers. Our optimizations, which enhanced the infrastructure's processing capabilities, continue to provide incremental relief. We're monitoring the service and continuing our work to perform any follow-up actions or opening additional workstreams needed to fully resolve the problem.
We understand the significant impact of this event to your organization, we're treating this issue with the highest priority, and we're working to provide relief as soon as possible.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change resulted in a portion of infrastructure not operating as expected.
Next update by: Tuesday, November 26, 2024, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Nov 25 15:25:12 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels within
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature within
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experiences issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Viva Engage
- Users may be unable to load topics in feeds and threads.
- Users may see searches or autocomplete fail for topic experiences.
- Users’ Microsoft Teams Q&A experiences may not show user names.
- Users may not be able to load their home feeds.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
- Users may not be able to load Copilot experiences within the Viva Engage service.
- Users may be unable to submit queries to Copilot within OneNote through the chat pane and context menu. Users may receive an apology or "at capacity" message."
Current status: Services are showing significant signs of restoration following our infrastructure optimizations to redistribute traffic and restart affected servers, upwards of 90 percent recovery as we continue to increase processing capability. We're continuing to perform appropriate optimizations on the subset of remaining affected machines to resolve the issue for all users.
Scope of impact: This issue could impact any user hosted globally; however, users are experiencing varying degrees of impact depending on how they are routed through the affected infrastructure and what action they are trying to perform. Impacted users attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Nov 25 14:52:51 2024 |
|---|
| Description: | We're continuing to redirect traffic and apply targeted remediation to impacted servers. We've observed initially positive results in some areas, and we're monitoring service health closely as our mitigation workstreams continue in parallel.
We understand the significant impact of this event to your organization, we're treating this issue with the highest priority, and we're working to provide relief as soon as possible.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Nov 25 14:15:19 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels within
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature within
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experiences issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
Current status: Our mitigative actions haven't provided relief as expected, and a portion of infrastructure remains in an unhealthy state. We determined that some of the targeted server restarts did not succeed due to processing issues, which are under investigation. We’re currently focused on spreading traffic to healthy infrastructure, and we're seeing some recovery.
Scope of impact: Any user routed through affected infrastructure and attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change has resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Nov 25 12:37:21 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The impacted services and their impact are as follows:
Exchange Online
- Users may be unable to access using the following impacted connection methods: Outlook on the web, Outlook desktop client, Representational State Transfer (REST), Exchange ActiveSync (EAS)
- Users may experience mail transport delays.
Microsoft Teams
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.
Microsoft Purview
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Microsoft Fabric
- Users may be unable to export content or set and view labels within
- Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
SharePoint Online
- Users may be unable to use the search feature within
Microsoft Defender for Office365
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experiences issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Universal Print
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Power Automate for Desktop
- Users may experience errors running flows that utilize cloud connectors.
Microsoft Bookings
- Users may be unable to access their bookings.
Microsoft Copilot
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
Current status: We're continuing to reroute traffic to alternate infrastructure and have reinitiated targeted server restarts to ensure the fix takes effect as expected. We're monitoring to confirm the restarts proceed successfully. We don't yet have an estimated time to resolution; however, we'll provide one as soon as it becomes available.
Scope of impact: Any user routed through affected infrastructure and attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change has resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Nov 25 11:44:41 2024 |
|---|
| Description: | We're rerouting traffic to alternate infrastructure to expedite mitigation. In parallel, we're resolving complications leading to the delays in targeted server restarts.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Nov 25 11:15:43 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Users may be unable to use the following features within Microsoft Teams:
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.
Users may experience the following issues with Microsoft Purview:
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Users may be unable to export content or set and view labels within Microsoft Fabric.
Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
Users may be unable to use the search feature within SharePoint Online.
Users may be unable to perform the following actions within Microsoft Defender for Office365:
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experiences issues with viewing simulation reports, and content.
- Users may get a “You can’t access this section” error when accessing sections of the Defender XDR portal, such as the Incidents and Alerts pages, that include affected Defender for Office 365 shared components.
Users leveraging Universal Print may experience the following issues:
- Users may be unable to Print via Universal Print.
- Users may be unable to list Printers/Printer Shares on the Azure Portal Universal Print blade.
- Users may be unable to Register Printers via Universal Print.
Users may experience errors running flows that utilize cloud connectors in Power Automate for Desktop.
Users may be unable to access their bookings within Microsoft Bookings.
Users may be unable to use some Microsoft Copilot features including:
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
Current status: The fix which is addressing impact is continuing to deploy and has now reached 98 percent of the affected environment. Regarding recovery, we've encountered delays in our targeted restarts; however, we're identifying alternative options to expedite recovery of the affected infrastructure.
Scope of impact: Any user routed through affected infrastructure and attempting to use the functionalities outlined in the More info section of this communication may be affected by this event.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change has resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Nov 25 11:02:35 2024 |
|---|
| Description: | The patch has deployed 90 percent, and according to telemetry, service availability is recovering. An estimated time to completion of the fix is not yet available. Targeted server restarts are underway to address routing service issues, with priority on customers who are currently in business hours or beginning their business day.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Nov 25 09:27:54 2024 |
|---|
| Description: | We’re monitoring the progress of the fix, which has been deployed to approximately 60% of the affected environments. We’re continuing our manual restarts on the remaining impacted machines.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Nov 25 08:58:32 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Users may be unable to use the following features within Microsoft Teams:
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.
Users may experience the following issues with Microsoft Purview:
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Users may be unable to export content or set and view labels within Microsoft Fabric.
Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
Users may be unable to use the search feature within SharePoint Online.
Users may be unable to perform the following actions within Microsoft Defender for Office365.
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
- Users may experiences issues with viewing simulation reports, and content.
Users may also be unable to print via Universal Print.
Users may experience errors running flows that utilize cloud connectors in Power Automate for Desktop.
Users may be unable to access their bookings within Microsoft Bookings.
Users may be unable to use some Microsoft Copilot features including:
- Users are unable to use the personal Copilot panel in meetings and post meetings.
- Users are unable to see historic Copilot conversation history in meetings and post meetings.
Current status: We’ve started to deploy the fix which is currently progressing through the affected environment. While this progresses, we’re beginning manual restarts on a subset of machines that are in an unhealthy state.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A recent change has resulted in a portion of infrastructure not operating as expected.
Next update by: Monday, November 25, 2024, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Nov 25 08:30:08 2024 |
|---|
| Description: | We've isolated the root cause and have developed a patch, which we're testing on a subset of components before full deployment. We're making sure that once we deploy the script, we're able to ensure a full recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Nov 25 06:50:56 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Users may be unable to use the following features within Microsoft Teams:
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.
Users may experience the following issues with Microsoft Purview:
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Users may be unable to export content or set and view labels within Microsoft Fabric.
Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
Users may be unable to use the search feature within SharePoint Online.
Users may be unable to perform the following actions within Microsoft Defender for Office365.
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages
- Users may experiences issues with viewing simulation reports, and content.
- Some users may experience failures in manual or AIR approved Remediation Actions submitted through ThreatExplorer, Advanced Hunting or the Action Center.
Users may also be unable to print via Universal Print.
Users may experience errors running flows that utilize cloud connectors in Power Automate for Desktop.
Users may be unable to access their bookings within Microsoft Bookings.
Current status: We’ve identified a recent change which we believe has resulted in impact. We’ve begun to revert the change and are investigating what additional actions are required to mitigate the issue.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Nov 25 05:35:21 2024 |
|---|
| Description: | Title: Users may be unable to access or use some Microsoft 365 services and features
User impact: Users may be unable to access or use some Microsoft 365 services and features.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Users may be unable to use the following features within Microsoft Teams:
- Users are unable to create or update Virtual Events, including webinars and Town Halls.
- Users may be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
- Users are unable to create chat, add users and create or edited meetings.
- Users are unable to create or modify new teams and channels.
- Users may be unable to update presence.
- Users may be unable to use the search function.
- Users may not see updated list of files and links failing to load within the Chat shared tab.
Users may experience the following issues with Microsoft Purview:
- Users may be unable to access the Purview Portal, or Purview Solutions.
- Users may experience delays in policy stamping and with Adaptive Scope Evaluations.
Users may be unable to export content or set and view labels within Microsoft Fabric.
Some Microsoft Fabric users with Purview Information Protection Policies with sensitivity labels enabled, may be unable to use interactive operations on Power BI Desktop format files and reports, including export operations on Fabric artifacts with Sensitivity labels applied.
Users may be unable to use the search feature within SharePoint Online.
Users may be unable to perform the following actions within Microsoft Defender for Office365.
- Users may be unable to create simulations, simulation payloads or end user notifications.
- Users may experience issues with delivery for end user notifications and simulation messages
- Users may experiences issues with viewing simulation reports, and content.
Current status: We’ve updated the More Info section to include a list of impacted services and scenarios. We’re continuing to investigate recent changes, service telemetry and the failure paths to determine the root cause of impact.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Nov 25 03:54:09 2024 |
|---|
| Description: | Title: Users unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: While we’re continuing the restarts to improve service availability, we’re thoroughly analyzing recent changes and the specific failure path to determine the next steps required to resolve the issue.
Scope of impact: Some users may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Nov 25 03:18:34 2024 |
|---|
| Description: | We are systematically restarting the affected components while continuing our investigation into the cause of the errors.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Nov 25 02:21:19 2024 |
|---|
| Description: | Title: Users unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: Our ongoing service monitoring has determined that the issue is not limited to users in Asia Pacific, and instead that all users worldwide could be intermittently impacted. As such, we're expanding our restart efforts to ensure the issue is resolved for all users.
Scope of impact: Some users may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Nov 25 00:46:21 2024 |
|---|
| Description: | Title: Users in Asia Pacific unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: We're continuing to work to restart the small subset of machines which have previously failed to restart. We're also continuing to add additional capacity to the affected environment to mitigate impact as quickly as possible. At this time, we expect the majority of users will experience relief from impact as we work to address the remaining issues.
Scope of impact: Some users in the Asia Pacific region may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 8:00 AM UTC
|
|---|
|
| Time: | Sun Nov 24 23:56:48 2024 |
|---|
| Description: | Title: Users in Asia Pacific unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: We've identified a small subset of machines which are failing to restart, resulting in persisting impact. We're further investigating what is causing the restarts to fail to determine our next steps.
Scope of impact: Some users in the Asia Pacific region may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Preliminary root cause: A portion of infrastructure which supports mailbox and calendar functionality isn't operating as expected, resulting in impact.
Next update by: Monday, November 25, 2024, at 6:00 AM UTC
|
|---|
|
| Time: | Sun Nov 24 23:18:21 2024 |
|---|
| Description: | In addition to the infrastructure restarts, we're also working to add additional capacity to the affected environment to further assist in our impact mitigation efforts.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sun Nov 24 22:50:26 2024 |
|---|
| Description: | Title: Users in Asia Pacific unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: The affected scenarios are as follows:
Users may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Users may also be unable to access or modify their calendar in Microsoft Teams. This would include loading calendar, viewing meetings, creating/updating meetings and joining meetings.
Current status: We've determined via our internal telemetry that the impact to Microsoft Teams calendars has self-recovered. To fully resolve the issue, we initiated restarts on affected infrastructure and are monitoring further to determine whether additional steps are required. We're also continuing our investigation into the root cause of this issue.
Scope of impact: Some users in the Asia Pacific region may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempting to use their calendar in Microsoft Teams.
Start time: Monday, November 25, 2024, at 1:20 AM UTC
Next update by: Monday, November 25, 2024, at 5:00 AM UTC
|
|---|
|
| Time: | Sun Nov 24 22:29:51 2024 |
|---|
| Description: | While we continue to investigate the source of the issue, we're restarting affected machines in an attempt to mitigate the user impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Sun Nov 24 22:00:50 2024 |
|---|
| Description: | Title: Users in Asia Pacific unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Team
User impact: Users may be unable to access their Exchange Online mailboxes or their calendar functionality in Microsoft Teams.
More info: Here are the service impact scenarios affected:
Exchange Online may be unable to access Exchange Online using the following impacted connection methods:
- Outlook on the web
- Outlook desktop client
- Representational State Transfer (REST)
- Exchange ActiveSync (EAS)
Current status: Our automated systems alerted us to an issue in which some users may be intermittently unable to access their mailboxes in Exchange Online using any connection method or their calendar functionality in Microsoft Teams. We're analyzing a portion of Exchange Online infrastructure responsible for accessing mailboxes to understand the root cause of the issue and determine our next troubleshooting steps.
Scope of impact: Some users in the Asia Pacific region may intermittently be affected by this issue when attempting to access their mailboxes using any connection method in Exchange Online or attempt to use their calendar in Microsoft Teams.
Next update by: Monday, November 25, 2024, at 4:00 AM UTC
|
|---|
|
TM1019821 - Users may be unable to access Webinar registration links with Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 25 12:52:00 2025 |
|---|
| End Time: | Fri Feb 28 12:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 28 14:39:58 2025 |
|---|
| Root Cause: | A routine service update to a portion of the Microsoft Teams service infrastructure contained a code issue, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 13:37:35 2025 |
|---|
| Description: | Title: Users may be unable to access Webinar registration links with Microsoft Teams
User impact: Users may have been unable to access Webinar registration links within Microsoft Teams.
More info: Users may have also been unable to access the event landing page.
Final status: The reversion process for the impacting service update has completed, and we've confirmed through monitoring service health telemetry that impact has been remediated.
Scope of impact: Impact was specific to users who were served through the affected infrastructure attempting to access Webinar registration lings within Microsoft Teams.
Start time: Tuesday, February 25, 2025, at 5:42 PM UTC
End time: Friday, February 28, 2025, at 5:00 PM UTC
Root cause: A routine service update to a portion of the Microsoft Teams service infrastructure contained a code issue, resulting in impact.
Next steps:
- We're reviewing our update procedures to understand why impact to Webinar registration link access wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 28 12:30:02 2025 |
|---|
| Description: | Title: Users may be unable to access Webinar registration links with Microsoft Teams
User impact: Users may be unable to access Webinar registration links with Microsoft Teams.
More info: Users may also be unable to access the event landing page.
Current status: We're continuing to monitor the reversion of the impacting code change, which we anticipate will complete by our next scheduled communications update.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Root cause: A recent code change that was part of a scheduled maintenance update is causing the impact.
Next update by: Friday, February 28, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Feb 28 09:33:13 2025 |
|---|
| Description: | Title: Users may be unable to access Webinar registration links with Microsoft Teams
User impact: Users may be unable to access Webinar registration links with Microsoft Teams.
More info: Users may also be unable to access the event landing page.
Current status: We've determined that a recent code change, part of a scheduled maintenance update, is inadvertently causing impact. We're reverting the offending change to remediate impact.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Root cause: A recent code change, part of a scheduled maintenance update, is inadvertently causing impact.
Next update by: Friday, February 28, 2025, at 4:30 PM UTC
|
|---|
|
CP1018733 - Some users may see a loading screen when creating or updating an agent in Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Sat Feb 15 11:16:00 2025 |
|---|
| End Time: | Thu Feb 27 12:13:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 28 13:33:25 2025 |
|---|
| Root Cause: | A recent standard service update contained a code regression, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 13:33:25 2025 |
|---|
| Description: | Title: Some users may see a loading screen when creating or updating an agent in Microsoft Copilot (Microsoft 365)
User impact: Users may have seen a loading screen when creating or updating an agent in Copilot.
More info: As a workaround, users may be able to refresh their screen to reflect the changes made.
Final status: Following our deployment to correct the code issue, we've received confirmation from users that the impact is no longer occurring.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Saturday, February 15, 2025, at 4:16 PM UTC
End time: Thursday, February 27, 2025, at 5:13 PM UTC
Root cause: A recent standard service update contained a code regression, resulting in impact.
Next steps:
- We're continuing to analyze and investigate the affected service update to better understand why impact wasn't caught during the update testing and validation phase so that we can prevent similar impact from occurring in future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 27 13:13:49 2025 |
|---|
| Description: | Title: Some users may see a loading screen when creating or updating an agent in Microsoft Copilot (Microsoft 365)
User impact: Users may see a loading screen when creating or updating an agent in Copilot.
More info: As a workaround, users may be able to refresh their screen to reflect the changes made.
Current status: We've completed development and deployment of our fix for this issue. We're confirming with some users that this has resolved the issue.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Saturday, February 15, 2025, at 4:16 PM UTC
Root cause: A recent standard service update contains a code regression, which is resulting in impact.
Next update by: Friday, February 28, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Feb 27 07:04:02 2025 |
|---|
| Description: | Title: Some users may see a loading screen when creating or updating an agent in Microsoft Copilot (Microsoft 365)
User impact: Users may see a loading screen when creating or updating an agent in Copilot.
More info: As a workaround, users may be able to refresh their screen to reflect the changes made.
Current status: We've determined that a recent standard service update inadvertently contains a code regression, which is resulting in impact. We're developing a fix to remediate impact for all affected users.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: A recent standard service update inadvertently contains a code regression, which is resulting in impact.
Next update by: Thursday, February 27, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Feb 27 06:02:58 2025 |
|---|
| Description: | Title: Some users may see a loading screen when creating or updating an agent in Microsoft Copilot (Microsoft 365)
User impact: Users may see a loading screen when creating or updating an agent in Copilot.
More info: As a workaround, users may be able to refresh their screen to reflect the changes made.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Thursday, February 27, 2025, at 1:00 PM UTC
|
|---|
|
TM1019957 - Some users may experience delays or failures performing various chat operations in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 28 10:12:00 2025 |
|---|
| End Time: | Fri Feb 28 11:14:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 28 13:11:21 2025 |
|---|
| Root Cause: | A recent power disturbance affected a portion of infrastructure responsible for processing various chat operations, which resulted in the impacting delays and failures. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 13:11:21 2025 |
|---|
| Description: | Title: Some users may experience delays or failures performing various chat operations in Microsoft Teams
User impact: Users may have experienced delays or failures performing various chat operations in Microsoft Teams.
Final status: A recent power disturbance affected a portion of infrastructure responsible for processing various chat operations, which resulted in the impacting delays and failures. We manually restarted the service and monitored telemetry to confirm this remediated the issue.
Scope of impact: Some users may have experienced delays or failures performing various chat operations in Microsoft Teams.
Start time: Friday, February 28, 2025, at 3:12 PM UTC
End time: Friday, February 28, 2025, at 4:14 PM UTC
Root cause: A recent power disturbance affected a portion of infrastructure responsible for processing various chat operations, which resulted in the impacting delays and failures.
Next steps:
- We're continuing to monitor the affected infrastructure to ensure the service remains healthy so this issue doesn't happen again.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 28 12:54:07 2025 |
|---|
| Description: | Title: Some users may experience delays or failures performing various chat operations in Microsoft Teams
User impact: Users may have experienced delays or failures performing various chat operations in Microsoft Teams.
Current status: We've investigated a problem with the Microsoft Teams service in which users may have experienced delays or failures performing various chat operations, and we’ve confirmed that service is now restored. We'll provide additional information in a closure summary within the “History” section of the “Service health” dashboard shortly.
|
|---|
|
WP1012846 - Some users may have been intermittently unable to connect to their Cloud PCs in the Windows 365 web client
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Feb 21 01:00:00 2025 |
|---|
| End Time: | Fri Feb 21 11:27:00 2025 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Feb 28 10:54:04 2025 |
|---|
| Root Cause: | At the start of a session, the Microsoft 365 web client for Cloud PC loads a static Web Assembly File that contains the application content. If the static file exceeds 8MB, which is the caching limit of Azure CDN, the CDN requests the app service to retrieve the remaining contents. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 10:54:04 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Feb 25 19:21:32 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Feb 21 13:39:48 2025 |
|---|
| Description: | Title: Some users may have been intermittently unable to connect to their Cloud PCs in the Windows 365 web client
User impact: Users may have been intermittently unable to connect to their Cloud PCs in the Windows 365 web client.
More info: As a workaround, users were able to connect to their Cloud PCs using the full version of the app instead of using the browser. Additionally, some customers may also have been able to use the Remote Desktop Web client (RDweb.wvd.microsoft.com) from a browser.
If any user is still experiencing impact, we request that the user close all browser sessions and retry.
Final status: After an extended period of monitoring, and additional reports from users that the issue is no longer occurring, we've confirmed that the issue is resolved.
Scope of impact: This issue may have affected some users attempting to connect to their Cloud PCs in Windows 365 web client.
Start time: Friday, February 21, 2025, at 6:00 AM UTC
End time: Friday, February 21, 2025, at 4:29 PM UTC
Root cause: At the start of a session, the Microsoft 365 web client for Cloud PC loads a static Web Assembly File that contains the application content. If the static file exceeds 8MB, which is the caching limit of Azure CDN, the CDN requests the app service to retrieve the remaining contents.
The app service experienced an issue and did not send the uncached content in the expected file size format, so the CDN rejected the process. Our current understanding is that multiple factors led to the impacting scenario. The issue may have been caused by a combination of a new deployment and an invalid File size range request response from the service. As a result, the Web client continued to wait for the remaining content that never arrived, leaving the user stuck in a connecting state.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report (PIR) within two business days, and a final PIR within 5 business days.
|
|---|
|
| Time: | Fri Feb 21 12:49:18 2025 |
|---|
| Description: | We continue to receive reports from users that the impact is no longer occurring. For any user still experiencing impact, we request users to close all browser sessions and retry.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Feb 21 12:24:54 2025 |
|---|
| Description: | Title: Some users are intermittently unable to connect to their Cloud PCs in the Windows 365 web client
User impact: Users are intermittently unable to connect to their Cloud PCs in the Windows 365 web client.
More info: As a workaround, users are able to connect to their Cloud PCs using the full version of the app instead of using the browser. Additionally, some customers may also be able to use the Remote Desktop Web client (RDweb.wvd.microsoft.com) from a browser.
Current status: We’ve reverted the Cloud PC in Windows 365 web client to a previous version and flushed the CDN cache as a mitigation. We’ve received confirmation from multiple users that the issue is no longer occurring after our actions. We’re entering an extended period of monitoring to confirm resolution. In parallel, we continue to analyze browser logs and review network routing and CDN caches to fully understand the root cause.
Scope of impact: This issue may affect some users attempting to connect to their Cloud PCs in Windows 365 web client.
Next update by: Friday, February 21, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Feb 21 11:37:24 2025 |
|---|
| Description: | Our review of service telemetry and error logs has led us to investigate Content Delivery Network (CDN) and network routing caches as we work to isolate the cause of impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Feb 21 11:01:24 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to connect to their Cloud PCs in the Windows 365 web client
User impact: Users may be intermittently unable to connect to their Cloud PCs in the Windows 365 web client.
More info: As a workaround, users are able to connect to their Cloud PCs using the full version of the app instead of using the browser.
Current status: We identified that impact started around the same time as a recent service update. Out of an abundance of caution, we’ve reverted the service update back to the previous version, however, this hasn't remediated impact. We’re reviewing telemetry and error logs to better understand the issue and determine next steps.
Scope of impact: This issue may affect some users attempting to connect to their Cloud PCs in Windows 365 web client.
Next update by: Friday, February 21, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Feb 21 09:22:21 2025 |
|---|
| Description: | Title: Some users may be intermittently unable to connect to their Cloud PCs in the Windows 365 web client
User impact: Users may be intermittently unable to connect to their Cloud PCs in the Windows 365 web client.
More info: As a workaround, users are able to connect to their Cloud PCs using the full version of the app instead of using the browser.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: This issue may affect some users attempting to connect to their Cloud PCs in Windows 365 web client.
Next update by: Friday, February 21, 2025, at 5:00 PM UTC
|
|---|
|
MO987576 - Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 8 19:00:00 2025 |
|---|
| End Time: | Fri Feb 28 00:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 28 04:16:43 2025 |
|---|
| Root Cause: | A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre was inadvertently causing the agent list to show as empty. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 28 04:13:40 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may have seen an empty agent list in the Microsoft 65 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may have not been impacted.
Final status: We've confirmed that the deployment of the fix has completed and impact is no longer occurring.
Scope of impact: Admins who were served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may have been impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
End time: Friday, February 28, 2025, at 5:00 AM UTC
Root cause: A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre was inadvertently causing the agent list to show as empty.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 20 03:54:48 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may see an empty agent list under agent details in the Microsoft 365 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may not be impacted.
Current status: We've successfully validated our fix by deploying it to a section of test users. We're now initiating the deployment to the affected infrastructure and anticipate its completion by our next scheduled update.
Scope of impact: Admins who are served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may be impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
Root cause: A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre is inadvertently causing the agent list to show as empty.
Next update by: Friday, February 28, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Feb 19 04:50:37 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may see an empty agent list under agent details in the Microsoft 365 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may not be impacted.
Current status: We're continuing to deploy the fix to a section of test users to ensure it successfully mitigates impact. Once confirmed, we're expecting the deployment to the remaining affected users to be complete by Monday, March 3, 2025.
Scope of impact: Admins who are served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may be impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
Root cause: A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre is inadvertently causing the agent list to show as empty.
Next update by: Thursday, February 20, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Feb 11 04:56:16 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may see an empty agent list under agent details in the Microsoft 365 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may not be impacted.
Current status: We're deploying the fix to a subset of users to ensure it successfully mitigates impact. Once confirmed, we're expecting the deployment to the remaining affected users to be complete by Monday, March 3, 2025.
Scope of impact: Admins who are served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may be impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
Root cause: A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre is inadvertently causing the agent list to show as empty.
Next update by: Wednesday, February 19, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Feb 10 06:35:54 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may see an empty agent list under agent details in the Microsoft 365 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may not be impacted.
Current status: We're continuing to actively monitor the rollout of our fix, to ensure it completes without issue. We require additional time to confirm the estimated resolution time, which we expect to be able to provide as part of our next scheduled update.
Scope of impact: Admins who are served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may be impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
Root cause: A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre is inadvertently causing the agent list to show as empty.
Next update by: Tuesday, February 11, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Feb 10 04:58:18 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may see an empty agent list under agent details in the Microsoft 365 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may not be impacted.
Current status: We've initiated the deployment of our fix to the affected environment, and are actively monitoring the early rollout to confirm and share an estimated completion time as part of our next update.
Scope of impact: Admins who are served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may be impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
Root cause: A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre is inadvertently causing the agent list to show as empty.
Next update by: Monday, February 10, 2025, at 12:00 PM UTC
|
|---|
|
| Time: | Fri Feb 7 03:07:02 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may see an empty agent list under agent details in the Microsoft 365 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may not be impacted.
Current status: We're working on a solution to address the issue with the usage report in the affected infrastructure. Once the fix is developed, we will begin testing it in our internal environment to ensure it effectively mitigates impact before deploying it to the affected infrastructure.
Scope of impact: Admins who are served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may be impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
Root cause: A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre is inadvertently causing the agent list to show as empty.
Next update by: Monday, February 10, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Jan 30 04:39:36 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may see an empty agent list under agent details in the Microsoft 365 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may not be impacted.
Current status: We’re continuing to evaluate mitigation options to remediate impact.
Scope of impact: Admins who are served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may be impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
Root cause: A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre is inadvertently causing the agent list to show as empty.
Next update by: Friday, February 7, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Jan 24 05:49:39 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may see an empty agent list under agent details in the Microsoft 365 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may not be impacted.
Current status: We've identified that a section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre, inadvertently caused the agent list showing as empty. We're assessing available mitigation actions to perform in order to remediate impact.
Scope of impact: Admins who are served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may be impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
Root cause: A section of infrastructure responsible for populating usage reports within the Microsoft 365 admin centre, inadvertently caused the agent list showing as empty.
Next update by: Thursday, January 30, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Jan 24 03:54:34 2025 |
|---|
| Description: | Title: Empty Microsoft 365 Copilot agent usage reports within Microsoft 365 admin center
User impact: Admins may see an empty agent list under agent details in the Microsoft 365 Copilot usage report within the agent page.
More info: Active agent counts and trend charts may not be impacted.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Admins who are served through the affected infrastructure, attempting to view the Microsoft 365 reports in the admin center may be impacted.
Start time: Thursday, January 9, 2025, at 12:00 AM UTC
Next update by: Friday, January 24, 2025, at 11:00 AM UTC
|
|---|
|
EX1017243 - Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 13 05:04:00 2025 |
|---|
| End Time: | Thu Feb 27 16:40:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 27 18:22:23 2025 |
|---|
| Root Cause: | A recent service update that intended to improve the functionality of the calendar event body read/write process contains a code issue, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 27 18:22:23 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may have been unable to view or update the body of some recurring calendar events in multiple connection methods.
More info: This event specifically impacted users attempting to view or update the body of calendar events that were an exception in a series. An exception in this case was defined as a calendar event that was edited to an alternate time from when the recurring meeting typically meets.
Some users may have seen various additional symptoms if they were leveraging automations or third-party apps that rely on the presence of message body content.
This event impacted all Outlook clients excluding the classic Outlook desktop client.
Final status: We've confirmed with affected users that reverting the offending service update has remediated the impact.
Scope of impact: Some users attempting to view or update the body of recurring calendar events that were exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may have been affected.
Start time: Thursday, February 13, 2025, at 10:04 AM UTC
End time: Thursday, February 27, 2025, at 9:40 PM UTC
Root cause: A recent service update that intended to improve the functionality of the calendar event body read/write process contains a code issue, resulting in impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to calendar events prior to deployment to prevent similar impact in the future, and to improve our pre-deployment update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 27 17:17:16 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
More info: This event specifically impacts users attempting to view or update the body of calendar events that are an exception in a series. An exception in this case is defined as a calendar event that has been edited to an alternate time from when the recurring meeting typically meets.
Some users may see various additional symptoms if they are leveraging automations or third-party apps that rely on the presence of message body content.
This event impacts all Outlook clients excluding the classic Outlook desktop client.
Current status: The process of reverting the impacting service update has completed and we've confirmed the issue is no longer occurring within our internal test environment. We're testing with affected users to confirm the impact has been remediated in all affected environments.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Start time: Thursday, February 13, 2025, at 10:04 AM UTC
Root cause: A recent service update that intended to improve the functionality of the calendar event body read/write process contains a code issue, resulting in impact.
Next update by: Friday, February 28, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Feb 27 15:28:21 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
More info: This event specifically impacts users attempting to view or update the body of calendar events that are an exception in a series. An exception in this case is defined as a calendar event that has been edited to an alternate time from when the recurring meeting typically meets.
This event impacts all Outlook clients excluding the classic Outlook desktop client.
Current status: We've reviewed further details associated with the body read/write process and determined a recent service update that intended to improve the process's functionality contains a code issue, resulting impact. We're reverting the recent service update within our internal test environment to confirm if this action remediated the impact prior to any broad mitigative actions.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Start time: Thursday, February 13, 2025, at 10:04 AM UTC
Root cause: A recent service update that intended to improve the functionality of the calendar event body read/write process contains a code issue, resulting in impact.
Next update by: Thursday, February 27, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Feb 27 13:31:53 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
More info: This event specifically impacts users attempting to view or update the body of calendar events that are an exception in a series. An exception in this case is defined as a calendar event that has been edited to an alternate time from when the recurring meeting typically meets.
This event impacts all Outlook clients excluding the classic Outlook desktop client.
Current status: We've updated the Title, User impact, and Scope of impact sections to reflect the accurate impact scenario.
We're continuing to review recent service changes to the message body read/write process to confirm our hypothesis, so we can determine our next steps regarding impact remediation.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Thursday, February 27, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Feb 27 07:54:22 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
Current status: Our previous hypothesis of root cause has been inconclusive. We're suspecting that a recent change within message body read/write may be causing impact. We're reviewing further details associated with the change to validate our root cause theory and formulate a mitigation plan.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Thursday, February 27, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Feb 27 05:58:14 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
Current status: We're continuing our investigation into a section of storage infrastructure to confirm our aforementioned root cause theory and formulate a remediation plan.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Thursday, February 27, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Feb 27 01:42:06 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
Current status: We suspect a potential sync issue may be occurring and preventing the meeting data from being properly communicated within the portion of storage infrastructure responsible for facilitating meetings in Outlook on the web. We're further reviewing the portion of storage infrastructure to confirm our root cause theory and formulate a remediation plan.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Thursday, February 27, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Feb 26 15:27:09 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
Current status: We're reviewing newly provided reproductions of the issue from affected users and our testing environment, so that we can determine whether the meeting data is being properly communicated within the portion of storage infrastructure responsible for facilitating meetings in Outlook on the web.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Thursday, February 27, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Feb 26 12:30:42 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
Current status: We're continuing our analysis of recent service changes and network traces to better understand the underlying root cause. Simultaneously, we're working with affected users to gather additional information pertaining to whether the issue is reproduced only in new or existing meetings or both to help confirm what components of service infrastructure could be causing impact.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Wednesday, February 26, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 09:36:39 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
Current status: We've been able to reproduce impact in our internal environments which'll aid our investigation into the root cause. In parallel, we're reviewing HTTP Archive format (HAR) logs, network traces, reproduction data and recent service changes to isolate the source of impact.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Wednesday, February 26, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Feb 26 02:08:55 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
Current status: We're working with affected users to perform additional testing on the affected infrastructure, which will aid in refining our understanding of the impacted scenario and expedite our remediating actions.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Wednesday, February 26, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 00:58:45 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
Current status: We're continuing to review the aforementioned logs in order to help determine our troubleshooting steps in relation to resolving the issue.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Wednesday, February 26, 2025, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Feb 25 23:24:46 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
Current status: We're reviewing Fiddler trace logs gathered from affected users as well as service side logs to help determine the cause of impact, which will guide us toward our remediating actions.
Scope of impact: Users attempting to view or update the body of recurring calendar events that are exceptions in a series in the new Outlook desktop client, Outlook on the web, or Outlook mobile may be affected.
Next update by: Wednesday, February 26, 2025, at 6:00 AM UTC
|
|---|
|
| Time: | Tue Feb 25 23:04:57 2025 |
|---|
| Description: | Title: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods
User impact: Users may be unable to view or update the body of some recurring calendar events in multiple connection methods.
We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1016036 - Some users may be unable to see recent file activity history for document libraries in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 24 23:26:53 2025 |
|---|
| End Time: | Wed Feb 26 16:10:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 27 14:28:02 2025 |
|---|
| Root Cause: | A recent change intended to add additional functionality to the file activity feature introduced a code issue, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 27 14:28:02 2025 |
|---|
| Description: | Title: Some users may be unable to see recent file activity history for document libraries in SharePoint Online
User impact: Users may have been unable to see recent file activity history for document libraries in SharePoint Online.
More info: Affected users may have seen that the details panel was unexpectedly blank when browsing activity history for document libraries in SharePoint Online. When a file was selected, some details appeared, but recent activity didn't.
While we're focused on remediation, our testing indicates that some users may have been able to bypass impact by refreshing the affected page.
Final status: The fix has fully saturated, and we've confirmed with affected users that this has resolved the issue.
Scope of impact: Users serviced by the affected portions of infrastructure attempting to view file activity for document libraries in SharePoint Online may have been impacted.
Start time: Friday, February 14, 2025, at 7:23 PM UTC
End time: Wednesday, February 26, 2025, at 9:10 PM UTC
Root cause: A recent change intended to add additional functionality to the file activity feature introduced a code issue, resulting in impact.
Next steps:
- We're reviewing our update process to understand how this impact wasn't caught during testing so we can improve our protocols to ensure similar issues are identified and addressed before deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 26 14:39:19 2025 |
|---|
| Description: | Title: Some users may be unable to see recent file activity history for document libraries in SharePoint Online
User impact: Users may be unable to see recent file activity history for document libraries in SharePoint Online.
More info: Affected users may see that the details panel is unexpectedly blank when browsing activity history for document libraries in SharePoint Online. When a file is selected, some details appear, but recent activity does not.
While we're focused on remediation, our testing indicates that some users may be able to bypass impact by refreshing the affected page.
Current status: We've completed the validations for the fix and have begun deploying it to all affected environments. The fix has reached 50 percent saturation in the affected environment, and some affected users will begin experiencing impact remediation as the fix reaches them. We anticipate the deployment will complete by our next communications update, at which time we'll confirm with affected users that the issue is fully resolved.
Scope of impact: Users serviced by the affected portions of infrastructure attempting to view file activity for document libraries in SharePoint Online may be impacted.
Start time: Friday, February 14, 2025, at 7:23 PM UTC
Estimated time to resolve: We anticipate the deployment of the fix will complete by Thursday, February 27, 2025, at 9:00 PM UTC.
Root cause: A recent change, intended to add additional functionality to the file activity feature, introduced a code issue that's causing impact.
Next update by: Thursday, February 27, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 14:15:57 2025 |
|---|
| Description: | Title: Some users may be unable to see recent file activity history for document libraries in SharePoint Online
User impact: Users may be unable to see recent file activity history for document libraries in SharePoint Online.
More info: Affected users may see that the details panel is unexpectedly blank when browsing activity history for document libraries in SharePoint Online. When a file is selected, some details appear, but recent activity does not.
While we're focused on remediation, our testing indicates that some users may be able to bypass impact by refreshing the affected page.
Current status: We've developed a fix to correct the code issue that was introduced by the offending change and are validating its efficacy. We'll provide an updated timeline for the validation and deployment as one becomes available.
Scope of impact: Users serviced by the affected portions of infrastructure attempting to view file activity for document libraries in SharePoint Online may be impacted.
Root cause: A recent change, intended to add additional functionality to the file activity feature, introduced a code issue that's causing impact.
Next update by: Wednesday, February 26, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 25 02:04:19 2025 |
|---|
| Description: | Title: Some users may be unable to see recent file activity history for document libraries in SharePoint Online
User impact: Users may be unable to see recent file activity history for document libraries in SharePoint Online.
More info: Affected users may see that the details panel is unexpectedly blank when browsing activity history for document libraries in SharePoint Online. When a file is selected, some details appear, but recent activity does not.
While we're focused on remediation, our testing indicates that some users may be able to bypass impact by refreshing the affected page.
Current status: We've confirmed that a recent change intended to add additional functionality to the file activity feature is resulting in impact. We're preparing a solution for the issue that we anticipate we can begin deploying by the time of our next scheduled update, at which point we'll test to confirm whether impact is resolved.
Scope of impact: Users serviced by the affected portions of infrastructure attempting to view file activity for document libraries in SharePoint Online may be impacted.
Root cause: A recent change intended to add additional functionality to the file activity feature is resulting in impact.
Next update by: Tuesday, February 25, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Feb 25 01:22:44 2025 |
|---|
| Description: | Title: Users are unable to see recent file activity history for document libraries in SharePoint Online
User impact: Users are unable to see recent file activity history for document libraries in SharePoint Online.
More info: Affected users see that the details panel is unexpectedly blank when browsing activity history for document libraries in SharePoint Online. When a file is selected, some details appear, but recent activity does not.
Current status: We've identified that a recent change intended to add additional functionality to the file activity history feature may be contributing to impact. We're proceeding with further testing and investigation to validate our findings and are assessing our options to disable the change as a potential path to remediation.
Scope of impact: Your organization is affected by this event, and users attempting to view file activity for document libraries in SharePoint Online are impacted.
Next update by: Tuesday, February 25, 2025, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Feb 25 00:05:45 2025 |
|---|
| Description: | Title: Users are unable to see recent file activity history for document libraries in SharePoint Online
User impact: Users are unable to see recent file activity history for document libraries in SharePoint Online.
More info: Affected users see that the details panel is unexpectedly blank when browsing activity history for document libraries in SharePoint Online. When a file is selected, some details appear, but recent activity does not.
Current status: We're reviewing an internal reproduction of the issue in conjunction with contextual details provided by affected users to gain insight into the underlying source of impact and determine our next investigative steps.
Scope of impact: Your organization is affected by this event, and users attempting to view file activity for document libraries in SharePoint Online are impacted.
Next update by: Tuesday, February 25, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Mon Feb 24 23:31:56 2025 |
|---|
| Description: | Title: Users are unable to see recent file activity history for document libraries in SharePoint Online
User impact: Users are unable to see recent file activity history for document libraries in SharePoint Online.
More info: Affected users see that the details panel is unexpectedly blank when browsing activity history for document libraries in SharePoint Online. When a file is selected, some details appear, but recent activity does not.
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MV1019071 - Users in the North America region may be unable to interact with feeds and see blank or stale feeds within Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 27 12:31:00 2025 |
|---|
| End Time: | Thu Feb 27 12:53:00 2025 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 27 14:00:59 2025 |
|---|
| Root Cause: | A portion of infrastructure that facilitates feed interaction and loading encountered a replication issue, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 27 14:00:59 2025 |
|---|
| Description: | Title: Users in the North America region may be unable to interact with feeds and see blank or stale feeds within Viva Engage
User impact: Users may have been unable to interact with feeds and saw blank or stale feeds within Viva Engage.
Final status: Our monitoring identified a portion of infrastructure that facilitates feed interaction and loading encountered a replication issue, resulting in impact. We rebalanced load to alternate infrastructure and confirmed this has remediated impact using service telemetry.
Scope of impact: Impact was a specific to a subset of users hosted in the North America region that were trying to interact with or view feeds in Viva Engage.
Start time: Thursday, February 27, 2025, at 5:31 PM UTC
End time: Thursday, February 27, 2025, at 5:53 PM UTC
Root cause: A portion of infrastructure that facilitates feed interaction and loading encountered a replication issue, resulting in impact.
Next steps:
- We're continuing our analysis of service telemetry to better understand what caused the replication issue and how it caused impact to prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 27 13:46:17 2025 |
|---|
| Description: | Title: Users in the North America region may be unable to interact with feeds and see blank or stale feeds within Viva Engage
User impact: Users may have been unable to interact with feeds and saw blank or stale feeds within Viva Engage.
Current status: We've investigated a problem in which users may have encountered blank or stale feeds within Viva Engage and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
CP1013567 - Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 21 21:41:37 2025 |
|---|
| End Time: | Thu Feb 27 00:24:56 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 27 00:25:06 2025 |
|---|
| Root Cause: | An issue occurred within our database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 27 00:25:06 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may have experienced delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may have experienced report update delays when viewing the following reports:
- Microsoft 365 Copilot usage report
- Microsoft Copilot Chat report
Final status: We can confirm that the backlog has completely been repopulated and that the service is restored.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may have been impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
End time: Thursday, February 27, 2025, at 4:00 AM UTC
Root cause: An issue occurred within our database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next steps:
- We're investigating to identify the underlying cause of the data pipeline issue to help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 26 20:10:00 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may experience delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may experience report update delays when viewing the following reports:
- Microsoft 365 Copilot usage report
- Microsoft Copilot Chat report
Current status: Most of the backlog has now been repopulated and only two reports remain impacted. We're continuing to monitor as the remaining backlog completes, and we anticipate this will have finished by our next scheduled update.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
Root cause: An issue occurred within our database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next update by: Thursday, February 27, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 04:38:24 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may experience delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may experience report update delays when viewing the following reports:
- Microsoft 365 Copilot usage report
- Microsoft Copilot Chat report
- Microsoft 365 Copilot readiness report
- Microsoft 365 Apps usage report
- SharePoint activity report
- SharePoint site usage report
- Mailbox usage report
- Microsoft 365 groups report
- Email activity report
- OneDrive for Business user activity report
- OneDrive for Business usage report
- Office activations report
- Skype for Business report
- Viva Engage activity report
- Viva Engage device usage report
- Microsoft 365 Active Users report
- Microsoft Teams team activity report
Current status: We're continuing to monitor and process the increasing backlog as it repopulates. We aim to provide an estimated time of completion by our next scheduled update.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
Root cause: An issue occurred within backend database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next update by: Thursday, February 27, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Feb 25 22:28:18 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may experience delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may experience report update delays when viewing the following reports:
- Microsoft 365 Copilot usage report
- Microsoft Copilot Chat report
- Microsoft 365 Copilot readiness report
- Microsoft 365 Apps usage report
- SharePoint activity report
- SharePoint site usage report
- Mailbox usage report
- Microsoft 365 groups report
- Email activity report
- OneDrive for Business user activity report
- OneDrive for Business usage report
- Office activations report
- Skype for Business report
- Viva Engage activity report
- Viva Engage device usage report
- Microsoft 365 Active Users report
- Microsoft Teams team activity report
Current status: We're continuing our efforts to monitor and process the increasing backlog as it repopulates.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
Root cause: An issue occurred within backend database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next update by: Wednesday, February 26, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Feb 25 06:54:50 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may experience delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may experience report update delays when viewing the following reports:
- Microsoft 365 Apps usage report
- Forms activity report
- Dynamics 365 Customer Voice activity report
- Project activity report
- Viva Goals activity report
- Microsoft 365 Copilot usage report
- Microsoft Copilot Chat report
- Microsoft 365 Copilot readiness report
- Mailbox usage report
- Microsoft Teams user activity report
- Email activity report
- Microsoft 365 Active Users report
Current status: We're proceeding with monitoring and processing the increasing backlog as it repopulates to ensure impact is remediated as expected.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
Root cause: An issue occurred within backend database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next update by: Wednesday, February 26, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Feb 24 21:06:04 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may experience delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may experience report update delays when viewing the following reports:
- Microsoft 365 Apps usage report
- Forms activity report
- Dynamics 365 Customer Voice activity report
- Project activity report
- Viva Goals activity report
- Microsoft 365 Copilot usage report
- Microsoft Copilot Chat report
- Microsoft 365 Copilot readiness report
- Mailbox usage report
- Microsoft Teams user activity report
- Email activity report
- Microsoft 365 Active Users report
Current status: We continue to monitor and process the increasing backlog as it repopulates and mitigates impact.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
Root cause: An issue occurred within backend database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next update by: Tuesday, February 25, 2025, at 11:30 AM UTC
|
|---|
|
| Time: | Mon Feb 24 05:35:38 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may experience delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may experience report update delays when viewing the following reports:
- Microsoft 365 Copilot Chat report
- Microsoft 365 Copilot Readiness report
- Microsoft 365 Copilot Usage report
- Microsoft 365 groups report
- Microsoft Teams team activity report
- Adoption Score group level aggregates
- Microsoft 365 Apps usage report
- Microsoft Teams user activity report
- Microsoft 365 Active Users report
- Mailbox usage report
Current status: We're continuing to monitor the service as the backlog is processed and repopulated, in order to ensure impact is remediated as expected.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
Root cause: An issue occurred within backend database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next update by: Tuesday, February 25, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Sun Feb 23 20:56:06 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may experience delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may experience report update delays when viewing the following reports:
- Microsoft 365 Copilot Chat report
- Microsoft 365 Copilot Readiness report
- Microsoft 365 Copilot Usage report
- Microsoft 365 groups report
- Microsoft Teams team activity report
- Adoption Score group level aggregates
- Microsoft 365 Apps usage report
- Microsoft Teams user activity report
- Microsoft 365 Active Users report
- Mailbox usage report
Current status: We've confirmed that our previously deployed script to correct the data pipeline delay was successfully deployed, and future usage data reports are no longer affected. We're now monitoring an increase in data backlogs processes to ensure the previously impacted usage data reports are processed and repopulated. We anticipate the majority of Copilot related reports will be repopulated by our next scheduled update, while we expect it will take additional time for the remaining impacted usage data reports to fully repopulate.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
Root cause: An issue occurred within backend database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next update by: Monday, February 24, 2025, at 11:00 AM UTC
|
|---|
|
| Time: | Fri Feb 21 22:27:59 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may experience delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may experience report update delays when viewing the following reports:
-Microsoft 365 Copilot Chat report
-Microsoft 365 Copilot Readiness report
-Microsoft 365 Copilot Usage report
-Adoption Score group level aggregates
Current status: We've developed a script to correct the data pipeline delay and are now performing extended validations to ensure that the script performs as expected when introduced throughout the affected environment. We anticipate that these final steps should be completed and implemented for affected admins by our next scheduled update.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
Root cause: An issue occurred within backend database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next update by: Monday, February 24, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Feb 21 21:49:20 2025 |
|---|
| Description: | Title: Admins may experience delays receiving metrics from Microsoft Copilot (Microsoft 365) reports in the admin center
User impact: Admins may experience delays in receiving latest metrics from Copilot reports in the Microsoft 365 admin center.
More info: Admins may experience report update delays when viewing the following reports:
-Microsoft 365 Copilot Chat report
-Microsoft 365 Copilot Readiness report
-Microsoft 365 Copilot Usage report
-Adoption Score group level aggregates
Current status: We've determined that an issue occurred within backend database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which is resulting in a data pipeline delay. We're currently reviewing mitigation strategies to ensure that the issue is resolved as soon as possible.
Scope of impact: Admins attempting to receive metrics from Copilot reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 22, 2025, at 12:00 AM UTC
Root cause: An issue occurred within backend database infrastructure, responsible for regulating specific Microsoft 365 admin center reports, which resulted in a data pipeline delay.
Next update by: Saturday, February 22, 2025, at 4:00 AM UTC
|
|---|
|
EX1017872 - Users may be unable to access the Exchange Online service through Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 26 10:23:00 2025 |
|---|
| End Time: | Wed Feb 26 11:47:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Feb 26 13:12:48 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 26 13:12:48 2025 |
|---|
| Description: | Title: Users may be unable to access the Exchange Online service through Outlook on the web
User impact: Users may have been unable to access the Exchange Online service through Outlook on the web.
Final status: While we were in the process of analyzing timeout errors occurring during the transport of user access requests, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: This issue may have affected any user in North America attempting to access Exchange Online through Outlook on the web.
Start time: Wednesday, February 26, 2025, at 3:23 PM UTC
End time: Wednesday, February 26, 2025, at 4:47 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 26 11:01:13 2025 |
|---|
| Description: | Title: Users may be unable to access the Exchange Online service through Outlook on the web
User impact: Users may be unable to access the Exchange Online service through Outlook on the web.
Current status: We're reviewing service health telemetry information to identify and isolate any errors which may potentially be contributing to impact for further investigation.
Scope of impact: This issue may affect any user in North America attempting to access Exchange Online through Outlook on the web.
Next update by: Wednesday, February 26, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Feb 26 10:38:36 2025 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
SP1017629 - Users may have been unable to navigate advanced permissions settings for some SharePoint Online sites
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 19 22:04:00 2025 |
|---|
| End Time: | Wed Feb 26 07:40:00 2025 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 26 09:26:41 2025 |
|---|
| Root Cause: | A recent standard service update inadvertently contained a code regression, which is preventing users from being able to manage permissions for some SharePoint Online sites. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 26 09:25:08 2025 |
|---|
| Description: | Title: Users may have been unable to navigate advanced permissions settings for some SharePoint Online sites
User impact: Users may have been unable to navigate advanced permissions settings for some SharePoint Online sites.
More info: Affected users may have been unable to navigate to '_layouts/15/user.aspx' on some SharePoint Online sites.
Final status: We've confirmed that after reverting the offending update, impact has been remediated.
Scope of impact: Impact was specific to users, who were served through the affected infrastructure, attempting to navigate advanced permission settings.
Start time: Thursday, February 20, 2025, at 3:04 AM UTC
End time: Wednesday, February 26, 2025, at 12:40 PM UTC
Root cause: A recent standard service update inadvertently contained a code regression, which is preventing users from being able to manage permissions for some SharePoint Online sites.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 26 07:59:16 2025 |
|---|
| Description: | Title: Users may be unable to navigate advanced permissions settings for some SharePoint Online sites
User impact: Users may be unable to navigate advanced permissions settings for some SharePoint Online sites.
More info: Affected users may be unable to navigate to '_layouts/15/user.aspx' on some SharePoint Online sites.
Current status: We've identified that a recent standard service update inadvertently contained a code regression, which is preventing users from being able to manage permissions for some SharePoint Online sites. We’re reverting the update to mitigate impact.
Scope of impact: Impact is specific to users, who are served through the affected infrastructure, attempting to navigate advanced permission settings.
Root cause: A recent standard service update inadvertently contained a code regression, which is preventing users from being able to manage permissions for some SharePoint Online sites.
Next update by: Wednesday, February 26, 2025, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Feb 26 06:06:43 2025 |
|---|
| Description: | Title: Users may be unable to navigate advanced permissions settings for some SharePoint Online sites
User impact: Users may be unable to navigate advanced permissions settings for some SharePoint Online sites.
More info: Affected users may be unable to navigate to '_layouts/15/user.aspx' on some SharePoint Online sites.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to users, who are served through the affected infrastructure, attempting to navigate advanced permission settings.
Next update by: Wednesday, February 26, 2025, at 1:00 PM UTC
|
|---|
|
DZ1016529 - Some users may encounter failures or delays for some Microsoft Defender for Endpoint response capabilities
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 25 07:00:00 2025 |
|---|
| End Time: | Tue Feb 25 14:40:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 25 15:32:06 2025 |
|---|
| Root Cause: | A section of service infrastructure that facilitates Microsoft Defender for Endpoint response capabilities was operating below our manageable service performance thresholds, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 25 15:32:06 2025 |
|---|
| Description: | Title: Some users may encounter failures or delays for some Microsoft Defender for Endpoint response capabilities
User impact: Users may have encountered failures or delays for some Microsoft Defender for Endpoint response capabilities.
More info: Specifically, the Microsoft Defender for Endpoint response capabilities affected were live response and automation investigation.
In addition, users may have noticed delays for other response capabilities, such as:
- Collect investigation package
- Run antivirus scan
- Restrict app execution
- Isolate device
Final status: The previously mentioned performance optimizations are complete, and we've monitored our service health telemetry to confirm that the previously affected components of infrastructure are restored to full operational capability and impact is remediated.
Scope of impact: Impact was specific to some users located, or served by the affected infrastructure, in West Europe.
Start time: Tuesday, February 25, 2025, at 12:00 PM UTC
End time: Tuesday, February 25, 2025, at 7:40 PM UTC
Root cause: A section of service infrastructure that facilitates Microsoft Defender for Endpoint response capabilities was operating below our manageable service performance thresholds, resulting in impact.
Next steps:
- We're continuing our investigation into the performance degradation that led to impact to determine precisely what went wrong and to assist us in reinforcing our services against similar future issues.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 25 11:13:21 2025 |
|---|
| Description: | Title: Some users may encounter failures or delays for some Microsoft Defender for Endpoint response capabilities
User impact: Users may encounter failures or delays for some Microsoft Defender for Endpoint response capabilities.
More info: Specifically, the Microsoft Defender for Endpoint response capabilities affected are live response and automation investigation.
In addition, users may notice delays for other response capabilities, such as:
- Collect investigation package
- Run antivirus scan
- Restrict app execution
- Isolate device
Current status: We're continuing to optimize the affected environment to handle requests more efficiently and remediate impact. We anticipate this process to be complete and impact to be resolved by the time of our next scheduled communications update.
Scope of impact: Impact is specific to some users located or served by the affected infrastructure in West Europe.
Start time: Tuesday, February 25, 2025, at 12:00 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by our next scheduled update on Tuesday, February 25, 2025, at 10:30 PM UTC.
Root cause: A section of service infrastructure, that facilitates Microsoft Defender for Endpoint response capabilities, has fallen below our manageable service performance thresholds, resulting in impact.
Next update by: Tuesday, February 25, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Feb 25 10:26:45 2025 |
|---|
| Description: | Title: Some users may encounter failures or delays for some Microsoft Defender for Endpoint response capabilities
User impact: Users may encounter failures or delays for some Microsoft Defender for Endpoint response capabilities.
More info: Specifically, the Microsoft Defender for Endpoint response capabilities affected are live response and automation investigation.
In addition, users may notice delays for other response capabilities, such as:
- Collect investigation package
- Run antivirus scan
- Restrict app execution
- Isolate device
Current status: We've determined that a section of service infrastructure, that facilitates Microsoft Defender for Endpoint response capabilities, has fallen below our manageable service performance thresholds, resulting in impact. We're optimizing the environment to handle requests more efficiently and remediate impact.
Scope of impact: Impact is specific to some users located or served by the affected infrastructure in West Europe.
Start time: Tuesday, February 25, 2025, at 12:00 PM UTC
Root cause: A section of service infrastructure, that facilitates Microsoft Defender for Endpoint response capabilities, has fallen below our manageable service performance thresholds, resulting in impact.
Next update by: Tuesday, February 25, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Feb 25 08:57:40 2025 |
|---|
| Description: | Title: Some users may encounter failures or delays for some Microsoft Defender for Endpoint response capabilities
User impact: Users may encounter failures or delays for some Microsoft Defender for Endpoint response capabilities.
More info: Specifically, the Microsoft Defender for Endpoint response capabilities affected are live response and automation investigation.
In addition, users may notice delays for other response capabilities, such as:
- Collect investigation package
- Run antivirus scan
- Restrict app execution
- Isolate device
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users located or served by the affected infrastructure in West Europe.
Next update by: Tuesday, February 25, 2025, at 4:00 PM UTC
|
|---|
|
PP1016712 - Copilot Studio – Users may have been unable to access the Microsoft Copilot Studio portal
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 24 15:00:00 2025 |
|---|
| End Time: | Mon Feb 24 20:30:00 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 25 12:24:21 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 25 12:00:29 2025 |
|---|
| Description: | Title: Copilot Studio – Users may have been unable to access the Microsoft Copilot Studio portal
User impact: Users may have been unable to access the Microsoft Copilot Studio portal
Final Status: We identified that high memory consumption on a portion of supporting infrastructure resulted in slowness that prevented users from accessing copilotstudio.microsoft.com. We restarted the management service on the affected infrastructure and confirmed via service health diagnostics that functionality was restored.
This is the final update on the incident.
Preliminary Root Cause: High memory consumption on a portion of supporting infrastructure.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
DZ1016446 - Users may have seen submission verdicts as 'Unknown' for some messages in Microsoft Defender for Office 365
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 24 08:00:00 2025 |
|---|
| End Time: | Mon Feb 24 23:00:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 25 09:28:15 2025 |
|---|
| Root Cause: | A section of storage layer infrastructure responsible for processing submission messages was performing below performing thresholds. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 25 07:52:11 2025 |
|---|
| Description: | Title: Users may have seen submission verdicts as 'Unknown' for some messages in Microsoft Defender for Office 365
User impact: Users may have seen submission verdicts as 'Unknown' for some messages in Microsoft Defender for Office 365.
More info: Affected users could have resubmitted their emails to receive the correct verdict.
Final status: We've identified that a section of storage layer infrastructure responsible for processing submission messages was performing below acceptable performing thresholds, resulting in impact. While we were working on mitigation, our automated recovery systems returned the service within acceptable performance thresholds and we've confirmed that impact is no longer occurring.
Scope of impact: Your organization was affected by this event, and some users attempting to view correct submission verdicts for some messages in Microsoft Defender for Office 365 may have been impacted.
Start time: Monday, February 24, 2025, at 1:00 PM UTC
End time: Tuesday, February 25, 2025, at 4:00 AM UTC
Root cause: A section of storage layer infrastructure responsible for processing submission messages was performing below performing thresholds.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
MO1004518 - Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Feb 12 18:50:00 2025 |
|---|
| End Time: | Thu Feb 13 00:20:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Feb 25 05:29:56 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 25 05:29:56 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Feb 19 18:20:35 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Feb 14 09:36:27 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Feb 13 01:03:02 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Users were unable to use features or access files which leveraged Information Protection labels.
More info: Impact included but was not limited to the following scenarios:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
- Synchronizing browser roaming data and opening protected PDFs in Microsoft Edge.
Final status: After an extended period of monitoring, we've confirmed that the issue is now resolved.
Scope of impact: Some users may have been unable to use features or access files which leverage Information Protection labels. This issue primarily affected users in the Asia Pacific region. Users outside of the Asia Pacific region could have been affected at a marginal rate if their traffic request was routed through the affected area.
Start time: Wednesday, February 12, 2025, at 11:50 PM UTC
End time: Thursday, February 13, 2025, at 5:20 AM UTC
Preliminary root cause: A recent change to a widely-deployed client application caused a denial-of-service condition on the Azure Rights Management Service (RMS), the service that facilitates protection functionality for Information Protection labels, leading to impact to customers. The application uses RMS to protect user data which is synchronized to cloud storage. An application update triggered a reprotection and resync of this data. The resync resulted in a sustained high volume of calls to RMS which exceeded operational thresholds in the Asia Pacific region, resulting in throttling of additional requests. Given the volume and install base of the application, scale up and recovery took several hours.
Next steps:
- We’re implementing throttling with configurable limits in an efficient manner to not impact quality of service. We expect this repair items to take an extended period to fully implement to ensure these limits do not negatively impact the service.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Feb 13 00:41:06 2025 |
|---|
| Description: | Our internal telemetry indicates that the service has fully recovered following our traffic management changes. We're monitoring for an additional period of time to ensure no further action is required.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 12 23:32:13 2025 |
|---|
| Description: | As our mitigation efforts progress, we've confirmed users may see relief when retrying the impacted actions.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 12 23:17:47 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: As we've seen the desired effect to service health from our traffic management change, we're continuing to apply it in additional phases to the affected infrastructure to achieve full impact resolution. As previously mentioned, while this work continues, we're exploring other actions we can take to resolve the issue as soon as possible.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels. Our internal telemetry indicates that this issue primarily affects users in the Asia Pacific region.
Start time: Wednesday, February 12, 2025, at 11:50 PM UTC
Preliminary root cause: A recent change to a downstream service which facilitates Information Protection labels is causing a traffic processing imbalance and leading to impact.
Next update by: Thursday, February 13, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Feb 12 22:03:47 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
- Opening email messages with Information Protection labels
- Accessing labeled files in SharePoint Online sites or OneDrive for Business
- Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
- Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
- Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: We've observed some improvement to the overall service health as our traffic management change is applied. We're continuing to monitor internal telemetry while also reviewing additional actions we can take to expedite impact resolution.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels. Our internal telemetry indicates that this issue primarily affects users in the Asia Pacific region.
Start time: Wednesday, February 12, 2025, at 11:50 PM UTC
Preliminary root cause: A recent change to a downstream service which facilitates Information Protection labels is causing a traffic processing imbalance and leading to impact.
Next update by: Thursday, February 13, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Wed Feb 12 21:40:11 2025 |
|---|
| Description: | We've confirmed that this issue primarily affects users in the Asia Pacific region. We're focusing our mitigation efforts on infrastructure in this region in an attempt to resolve the impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 12 21:18:38 2025 |
|---|
| Description: | Title: Some users may be unable to use features or access files which leverage Microsoft Purview Information Protection labels
User impact: Some users may be unable to use features or access files which leverage Information Protection labels.
More info: Some impacted scenarios may include:
-Opening email messages with Information Protection labels
-Accessing labeled files in SharePoint Online sites or OneDrive for Business
-Opening files or content in Microsoft 365 apps, such as Word, Excel, PowerPoint, and OneNote
-Accessing and exporting labeled artifacts in Microsoft Fabric and Power BI
-Using Microsoft Copilot (Microsoft 365) to reference or access labeled files
Current status: We've identified that a recent change to a downstream service is causing a traffic processing imbalance leading to impact. We're applying a targeted traffic management change to alleviate the impact.
Scope of impact: Some users may be unable to use features or access files which leverage Information Protection labels.
Start time: Wednesday, February 12, 2025, at 11:50 PM UTC
Next update by: Thursday, February 13, 2025, at 4:30 AM UTC
|
|---|
|
IT1015926 - Users' Apple devices may have seen failures when attempting to enroll through Mobile Device Management
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 15 10:26:00 2024 |
|---|
| End Time: | Tue Feb 25 02:25:00 2025 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Feb 25 05:29:36 2025 |
|---|
| Root Cause: | An error in code in Intune infrastructure had led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 25 05:01:14 2025 |
|---|
| Description: | Title: Users' Apple devices may have seen failures when attempting to enroll through Mobile Device Management
User impact: Users' Apple devices may have seen failures when attempting to enroll through Mobile Device Management.
More info: This affected MacOS, iOS, and iPadOS.
Users could've attempted to retry the enrollment but it may have continued to fail.
Final status: We've confirmed the deployment of the fix has completed and that impact has been remediated.
Scope of impact: Any user attempting to enroll their Apple device through MDM may have seen a failure.
Start time: Tuesday, October 15, 2024, at 2:26 PM UTC
End time: Tuesday, February 25, 2025, at 7:25 AM UTC
Root cause: An error in code in Intune infrastructure had led to impact.
Next steps:
- We're reviewing the infrastructure code error details to further understand how it was introduced and why it caused impact, in order to prevent similar impact from happening again.
This is the final update for this event.
|
|---|
|
| Time: | Tue Feb 25 01:22:57 2025 |
|---|
| Description: | Title: Users' Apple devices may see failures when attempting to enroll through Mobile Device Management
User impact: Users' Apple devices may see failures when attempting to enroll through Mobile Device Management.
More info: This affects MacOS, iOS, and iPadOS.
Users can attempt to retry the enrollment but may continue to fail.
Current status: Our fix deployment is taking longer than anticipated. We'll provide an updated timeline when one becomes available.
Scope of impact: Any user attempting to enroll their Apple device through MDM may see a failure.
Start time: Tuesday, October 15, 2024, at 2:26 PM UTC
Root cause: An error in code in Intune infrastructure that is leading to impact.
Next update by: Tuesday, February 25, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Feb 24 23:13:54 2025 |
|---|
| Description: | Title: Users' Apple devices may see failures when attempting to enroll through Mobile Device Management
User impact: Users' Apple devices may see failures when attempting to enroll through Mobile Device Management.
More info: This affects MacOS, iOS, and iPadOS.
Users can attempt to retry the enrollment but may continue to fail.
Current status: We've initiated our fix deployment and anticipate it will have completed by our next scheduled update.
Scope of impact: Any user attempting to enroll their Apple device through MDM may see a failure.
Start time: Tuesday, October 15, 2024, at 2:26 PM UTC
Root cause: An error in code in Intune infrastructure that is leading to impact.
Next update by: Tuesday, February 25, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Mon Feb 24 21:13:08 2025 |
|---|
| Description: | Title: Users' Apple devices may see failures when attempting to enroll through Mobile Device Management
User impact: Users' Apple devices may see failures when attempting to enroll through Mobile Device Management.
More info: This affects MacOS, iOS, and iPadOS.
Users can attempt to retry the enrollment but may continue to fail.
Current status: We're continuing to prepare our fix for deployment. We'll provide a deployment timeline when one is available.
Scope of impact: Any user attempting to enroll their Apple device through MDM may see a failure.
Start time: Tuesday, October 15, 2024, at 2:26 PM UTC
Root cause: An error in code in Intune infrastructure that is leading to impact.
Next update by: Tuesday, February 25, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Mon Feb 24 20:15:10 2025 |
|---|
| Description: | Title: Users' Apple devices may see failures when attempting to enroll through Mobile Device Management
User impact: Users' Apple devices may see failures when attempting to enroll through Mobile Device Management.
More info: This affects MacOS, iOS, and iPadOS.
Users can attempt to retry the enrollment but may continue to fail.
Current status: We've been alerted to an issue where users may see failures when attempting to enroll their Apple devices through Mobile Device Management (MDM). We've identified an error in code in Intune infrastructure that is leading to impact. We've developed and are in the preliminary stages of deploying a fix to restore service.
Scope of impact: Any user attempting to enroll their Apple device through MDM may see a failure.
Start time: Tuesday, October 15, 2024, at 2:26 PM UTC
Root cause: An error in code in Intune infrastructure that is leading to impact.
Next update by: Tuesday, February 25, 2025, at 2:30 AM UTC
|
|---|
|
MO1015679 - Some users may be unable to use Microsoft Security Exposure Management (MSEM) in multiple Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 24 14:17:47 2025 |
|---|
| End Time: | Tue Feb 25 01:35:37 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 25 01:35:49 2025 |
|---|
| Root Cause: | A recent change to the components of Microsoft Defender services responsible for facilitating service notifications introduced an error that prevented the MSEM UX from rendering, leading to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 25 01:35:49 2025 |
|---|
| Description: | Title: Some users may be unable to use Microsoft Security Exposure Management (MSEM) in multiple Microsoft 365 services
User impact: Users may have been unable to use the MSEM feature in multiple Microsoft 365 services.
More info: This issue affected the MSEM feature in the North Europe and West Europe regions within all Microsoft 365 services where the feature was implemented. This included the following:
- Microsoft Defender for Endpoint
- Microsoft Defender for Identity
- Microsoft Defender for Cloud Apps
Final status: We can confirm that the deployment of the fix has completed and that the impact is remediated.
Scope of impact: Any user attempting to use the MSEM feature in multiple Microsoft 365 services may have been impacted.
Start time: Monday, February 24, 2025, at 4:20 PM UTC
End time: Tuesday, February 25, 2025, at 12:17 AM UTC
Root cause: A recent change to the components of Microsoft Defender services responsible for facilitating service notifications introduced an error that prevented the MSEM UX from rendering, leading to impact.
Next steps:
- We're investigating why the change resulted in impact to help identify these types of problems before implementing potentially impacting changes.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 24 20:17:44 2025 |
|---|
| Description: | Title: Some users may be unable to use Microsoft Security Exposure Management (MSEM) in multiple Microsoft 365 services
User impact: Users may be unable to use the MSEM feature in multiple Microsoft 365 services.
More info: This issue affects the MSEM feature in the North Europe and West Europe regions within all Microsoft 365 services where the feature has been implemented. This includes the following:
- Microsoft Defender for Endpoint
- Microsoft Defender for Identity
- Microsoft Defender for Cloud Apps
Current status: The deployment of the fix is ongoing. We're continuing to monitor it's progress; however, more time is needed to complete the deployment. We'll provide an ETA on its completion once one becomes available.
Scope of impact: Any user attempting to use the MSEM feature in multiple Microsoft 365 services may be impacted.
Start time: Monday, February 24, 2025, at 4:20 PM UTC
Root cause: A recent change to the components of Microsoft Defender services responsible for facilitating service notifications introduced an error that's preventing the MSEM UX from rendering, leading to impact.
Next update by: Tuesday, February 25, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 18:01:54 2025 |
|---|
| Description: | Title: Some users may be unable to use Microsoft Security Exposure Management (MSEM) in multiple Microsoft 365 services
User impact: Users may be unable to use the MSEM feature in multiple Microsoft 365 services.
More info: This issue affects the MSEM feature in the North Europe and West Europe regions within all Microsoft 365 services where the feature has been implemented. This includes the following:
- Microsoft Defender for Endpoint
- Microsoft Defender for Identity
- Microsoft Defender for Cloud Apps
Current status: Our deployment of the previously mentioned fix is progressing, but taking longer than expected. We'll provide a new timeline to deployment and remediation as it becomes available.
Scope of impact: Any user attempting to use the MSEM feature in multiple Microsoft 365 services may be impacted.
Start time: Monday, February 24, 2025, at 4:20 PM UTC
Root cause: A recent change to the components of Microsoft Defender services responsible for facilitating service notifications introduced an error that's preventing the MSEM UX from rendering, leading to impact.
Next update by: Tuesday, February 25, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Feb 24 16:51:14 2025 |
|---|
| Description: | Title: Some users may be unable to use Microsoft Security Exposure Management (MSEM) in multiple Microsoft 365 services
User impact: Users may be unable to use the MSEM feature in multiple Microsoft 365 services.
More info: This issue affects the MSEM feature in the North Europe and West Europe regions within all Microsoft 365 services where the feature has been implemented. This includes the following:
- Microsoft Defender for Endpoint
- Microsoft Defender for Identity
- Microsoft Defender for Cloud Apps
Current status: We've developed and begun deployment of a fix to resolve the previously mentioned infrastructure error leading to impact. We anticipate that the deployment will be complete by our next scheduled communications update, at which time we'll monitor our service health telemetry to confirm that impact is remediated.
Scope of impact: Any user attempting to use the MSEM feature in multiple Microsoft 365 services may be impacted.
Start time: Monday, February 24, 2025, at 4:20 PM UTC
Root cause: A recent change to the components of Microsoft Defender services responsible for facilitating service notifications introduced an error that's preventing the MSEM UX from rendering, leading to impact.
Next update by: Tuesday, February 25, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Feb 24 15:02:02 2025 |
|---|
| Description: | Title: Some users may be unable to use Microsoft Security Exposure Management (MSEM) in multiple Microsoft 365 services
User impact: Users may be unable to use the MSEM feature in multiple Microsoft 365 services.
More info: This issue affects the MSEM feature in the North Europe and West Europe regions within all Microsoft 365 services where the feature has been implemented. This includes the following:
- Microsoft Defender for Endpoint
- Microsoft Defender for Identity
- Microsoft Defender for Cloud Apps
Current status: Our investigation has determined that a recent change to the components of Microsoft Defender services responsible for facilitating service notifications introduced an error that's preventing the MSEM user experience (UX) from rendering, leading to impact. We're evaluating potential methods to repair the error leading to impact and resolve this issue.
Scope of impact: Any user attempting to use the MSEM feature in multiple Microsoft 365 services may be impacted.
Start time: Monday, February 24, 2025, at 4:20 PM UTC
Root cause: A recent change to the components of Microsoft Defender services responsible for facilitating service notifications introduced an error that's preventing the MSEM UX from rendering, leading to impact.
Next update by: Monday, February 24, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Feb 24 14:47:42 2025 |
|---|
| Description: | Title: Some users may be unable to use Microsoft Security Exposure Management (MSEM) in multiple Microsoft 365 services
User impact: Users may be unable to use the MSEM feature in multiple Microsoft 365 services.
More info: This issue affects the MSEM feature in the North Europe and West Europe regions within all Microsoft 365 services where the feature has been implemented. This includes the following:
- Microsoft Defender for Endpoint
- Microsoft Defender for Identity
- Microsoft Defender for Cloud Apps
Current status: We're investigating a potential issue with the Microsoft Security Exposure Management (MSEM) feature and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1009639 - Users may be unable to view rooms using Room Finder in the classic Outlook desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 10 09:30:00 2025 |
|---|
| End Time: | Fri Feb 21 16:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 24 13:19:40 2025 |
|---|
| Root Cause: | A recent change aimed at addressing a service infrastructure level issue introduced an impacting code regression. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 24 13:19:40 2025 |
|---|
| Description: | Title: Users may be unable to view rooms using Room Finder in the classic Outlook desktop client
User impact: Users may have been unable to view rooms using Room Finder in the classic Outlook desktop client.
More info: While we were working to remediate the impact, and as a way to circumvent the problem, users could have viewed rooms in Room Finder in the new Outlook desktop client, Outlook on the web, or add additional filters when searching.
Final status: Following the deployment of our fix, we've confirmed with affected users that our reversion of the offending service update has successfully remediated the impact.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may have been impacted.
Start time: Monday, February 10, 2025, at 2:30 PM UTC
End time: Friday, February 21, 2025, at 9:00 PM UTC
Root cause: A recent change aimed at addressing a service infrastructure level issue introduced an impacting code regression.
Next steps:
- We're further analyzing the offending service update and the affected service infrastructure, so we can help isolate similar issues during our pre-deployment testing and validations processes.
This is the final update for this event.
|
|---|
|
| Time: | Fri Feb 21 15:17:49 2025 |
|---|
| Description: | Title: Users may be unable to view rooms using Room Finder in the classic Outlook desktop client
User impact: Users may be unable to view rooms using Room Finder in the classic Outlook desktop client.
More info: As a way to circumvent impact, users can view rooms in Room Finder in the new Outlook desktop client, Outlook on the web, or add additional filters when searching.
Current status: We've identified that a recent change aimed at addressing an infrastructure level issue introduced a regression which is resulting in impact. We've reverted the offending portion of this update and deployed a fix to remediate the impact. Affected users may need to restart the Outlook desktop client to receive the fix. We're reaching out to some affected users to confirm that the issue has been resolved.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may be impacted.
Start time: Monday, February 10, 2025, at 2:30 PM UTC
Root cause: A recent change aimed at addressing an infrastructure level issue introduced a regression which is resulting in impact.
Next update by: Monday, February 24, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Feb 20 14:23:21 2025 |
|---|
| Description: | Title: Users may be unable to view rooms using Room Finder in the classic Outlook desktop client
User impact: Users may be unable to view rooms using Room Finder in the classic Outlook desktop client.
More info: As a way to circumvent impact, users can view rooms in Room Finder in the new Outlook desktop client, Outlook on the web, or add additional filters when searching.
Current status: We're continuing our analysis of recent service updates which may be contributing to impact. In parallel, we're investigating the authentication pathways responsible for facilitating room finder requests to isolate the root cause and identify a path to remediation.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may be impacted.
Next update by: Friday, February 21, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Feb 19 14:19:42 2025 |
|---|
| Description: | Title: Users can't view rooms using Room Finder in the classic Outlook desktop client
User impact: Users may be unable to view rooms using Room Finder in the classic Outlook desktop client.
More info: As a way to circumvent impact, users can view rooms in Room Finder in the new Outlook desktop client, Outlook on the web, or add additional filters when searching.
Current status: We're continuing our analysis of recent service updates which may be contributing to impact.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may be impacted.
Next update by: Thursday, February 20, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 18 22:37:14 2025 |
|---|
| Description: | Title: Users can't view rooms using Room Finder in the classic Outlook desktop client
User impact: Users may be unable to view rooms using Room Finder in the classic Outlook desktop client.
More info: As a way to circumvent impact, users can view rooms in Room Finder in the new Outlook desktop client, Outlook on the web, or add additional filters when searching.
Current status: Our analysis of the code responsible for facilitating room finder requests is ongoing. This data will help us identify the manifestation point of impact and determine the next steps in our plan to alleviate impact.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may be impacted.
Next update by: Wednesday, February 19, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Feb 18 20:58:50 2025 |
|---|
| Description: | Title: Users can't view rooms using Room Finder in the classic Outlook desktop client
User impact: Users may be unable to view rooms using Room Finder in the classic Outlook desktop client.
More info: As a way to circumvent impact, users can view rooms in Room Finder in the new Outlook desktop client, Outlook on the web, or add additional filters when searching.
Current status: Our analysis of the code responsible for facilitating room finder requests continues. This data will aid us in pinpointing the origin of impact.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may be impacted.
Next update by: Wednesday, February 19, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Feb 18 18:29:07 2025 |
|---|
| Description: | Title: Users can't view rooms using Room Finder in the old Outlook desktop client
User impact: Users may be unable to view rooms using Room Finder in the old Outlook desktop client.
More info: As a workaround, users can view rooms in Room Finder in the New Outlook desktop client, Outlook on the web, or add additional filters when searching.
Current status: Our investigation into the code responsible for facilitating room finder suggests is still ongoing. Our findings will assist us in identifying where the failures are occurring and determine our next troubleshooting steps.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may be impacted.
Next update by: Wednesday, February 19, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Feb 18 16:48:49 2025 |
|---|
| Description: | Title: Users can't view rooms using Room Finder in the old Outlook desktop client
User impact: Users may be unable to view rooms using Room Finder in the old Outlook desktop client.
More info: As a workaround, users can view rooms in Room Finder in the New Outlook desktop client, Outlook on the web, or add additional filters when searching.
Current status: Our investigation of the Fiddler trace logs has remained inconclusive. We're continuing to investigate the code responsible for facilitating room finder in the Outlook desktop client to isolate the reason that the rooms are failing to display.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may be impacted.
Next update by: Wednesday, February 19, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Feb 18 14:55:02 2025 |
|---|
| Description: | Title: Users can't view rooms using Room Finder in Exchange Online
User impact: Users may be unable to view rooms using Room Finder in Exchange Online.
Current status: Our review of the provided Fiddler trace logs and request IDs indicates that the request calls to display rooms in Room Finder are successful. We're continuing to analyze the logs to determine the next steps to isolate the source of the impact.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may be impacted.
Next update by: Tuesday, February 18, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Feb 18 13:53:02 2025 |
|---|
| Description: | Title: Users can't view rooms using Room Finder in Exchange Online
User impact: Users may be unable to view rooms using Room Finder in Exchange Online.
Current status: We're reviewing the provided Fiddler trace logs and request IDs to identify any abnormalities that may indicate the root cause.
Scope of impact: Any user attempting to view rooms using Room Finder in Exchange Online may be impacted.
Next update by: Tuesday, February 18, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Feb 18 13:43:58 2025 |
|---|
| Description: | Title: Users can't view rooms using Room Finder in Exchange Online
User impact: Users can't view rooms using Room Finder in Exchange Online.
Current status: We're investigating a potential issue with Room Finder in Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MP1014784 - Users may not receive Endpoint Data Loss Prevention (DLP) alerts in the Microsoft Purview portal
| Status: | serviceRestored |
|---|
| Start Time: | Sun Feb 23 17:50:31 2025 |
|---|
| End Time: | Sun Feb 23 21:15:05 2025 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Feb 23 21:15:46 2025 |
|---|
| Root Cause: | A recent configuration change made to infrastructure supporting Endpoint DLP alerts resulted in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Feb 23 21:15:46 2025 |
|---|
| Description: | Title: Users may not receive Endpoint Data Loss Prevention (DLP) alerts in the Microsoft Purview portal
User impact: Users may not have received Endpoint DLP alerts in the Microsoft Purview portal.
Final status: We identified and rolled back a configuration change to our infrastructure supporting Endpoint DLP alerts that resulted in impact. This change was successfully rolled back, and we have confirmed that Endpoint DLP alerts are being received as expected in the Microsoft Purview portal.
Scope of impact: Any user may have been prevented from receiving Endpoint DLP alerts in the Microsoft Purview portal.
Start time: Saturday, February 22, 2025, at 12:35 PM UTC
End time: Monday, February 24, 2025, at 1:15 AM UTC
Root cause: A recent configuration change made to infrastructure supporting Endpoint DLP alerts resulted in the impact.
Next steps:
- We're investigating why the configuration change in question resulted in impact and are identifying ways to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sun Feb 23 18:05:52 2025 |
|---|
| Description: | Title: Users may not receive Endpoint Data Loss Prevention (DLP) alerts in the Microsoft Purview portal
User impact: Users may not receive Endpoint DLP alerts in the Microsoft Purview portal.
Current status: We've isolated an issue that prevents any user from receiving Endpoint DLP alerts in the Microsoft Purview portal. We're further analyzing recent service updates that could have introduced the problem, so we can determine our next troubleshooting steps for remediating the impact.
Scope of impact: Any user may be prevented from receiving Endpoint DLP alerts in the Microsoft Purview portal.
Next update by: Monday, February 24, 2025, at 5:00 AM UTC
|
|---|
|
PP994722 - Microsoft 365 Copilot for Sales - Users may be unable to access your environment
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sat Feb 1 06:00:00 2025 |
|---|
| End Time: | Sat Feb 1 10:33:00 2025 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Other |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sun Feb 23 15:32:28 2025 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Feb 23 15:32:28 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Feb 6 21:10:25 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sat Feb 1 11:51:22 2025 |
|---|
| Description: | Title: Microsoft 365 Copilot for Sales - Users may be unable to access your environment
User impact: Users may have been unable to access your environment.
Final Status: After further investigation, we determined that a clean-up operation associated with the affected service dependency resulted in a DNS misconfiguration, causing host resolution issues for certain clients. We corrected the misconfiguration and, following a period of monitoring, we confirmed that environment access was restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A clean-up operation associated with the affected service dependency resulted in a DNS misconfiguration, causing host resolution issues for certain clients.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Sat Feb 1 09:53:55 2025 |
|---|
| Description: | Title: Microsoft 365 Copilot for Sales - Users may be unable to access your environment
User impact: Users may be unable to access your environment.
More Info: Users who are already signed in with an active connection, and remain signed in, may continue to access your environment.
Current Status: After our investigation, we identified request failures to a service dependency for Microsoft 365 Copilot for Sales. We are gathering service health diagnostics to isolate the root cause of the issue and determine our initial troubleshooting steps.
Next Update: Saturday, February 1, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Sat Feb 1 09:36:34 2025 |
|---|
| Description: | Title: Microsoft 365 Copilot for Sales - Users may be unable to access your environment
User impact: Users may be unable to access your environment.
Current Status: We are aware of an emerging issue where users may be unable to access your Microsoft 365 Copilot for Sales environment. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
DZ1014488 - Some users may have encountered delays of up to four hours for anomaly detection alerts in Microsoft Sentinel
| Status: | serviceRestored |
|---|
| Start Time: | Sun Feb 23 05:30:00 2025 |
|---|
| End Time: | Sun Feb 23 10:00:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Feb 23 10:29:58 2025 |
|---|
| Root Cause: | A recent standard service update inadvertently contained a code regression, which caused malformed events that interfered with processing and resulted in unexpected delays. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Feb 23 10:29:41 2025 |
|---|
| Description: | Title: Some users may have encountered delays of up to four hours for anomaly detection alerts in Microsoft Sentinel
User impact: Users may have encountered delays of up to four hours for anomaly detection alerts in Microsoft Sentinel.
More info: Impacted scenarios included, but weren’t limited to:
- Advanced hunting
- Custom detections
- CloudAppEvents
- AppLogonEvents
- BehaviorInfo
- BehaviorEntities
- IdentityLogonEvents
- AlertInfo
- AlertEvidence tables
Final status: We've deployed the fix to remove the malformed events, and confirmed after monitoring that impact has been remediated.
Scope of Impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Sunday, February 23, 2025, at 10:30 AM UTC
End time: Sunday, February 23, 2025, at 3:00 PM UTC
Root cause: A recent standard service update inadvertently contained a code regression, which caused malformed events that interfered with processing and resulted in unexpected delays.
Next steps:
- We're reviewing our standard service update procedures to avoid similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sun Feb 23 09:38:48 2025 |
|---|
| Description: | Title: Some users may encounter delays of up to four hours for anomaly detection alerts in Microsoft Sentinel
User impact: Users may encounter delays of up to four hours for anomaly detection alerts in Microsoft Sentinel.
More info: Impacted scenarios include, but aren’t limited to:
- Advanced hunting
- Custom detections
- CloudAppEvents
- AppLogonEvents
- BehaviorInfo
- BehaviorEntities
- IdentityLogonEvents
- AlertInfo
- AlertEvidence tables
Current status: We've determined that a recent standard service update inadvertently contains a code regression, which caused malformed events that interfered with processing and is resulting in unexpected delays. We've reverted the offending change and are deploying a fix to remove the already created malformed events, to fully remediate impact.
Scope of Impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Sunday, February 23, 2025, at 10:30 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression, which caused malformed events that interfered with processing and is resulting in unexpected delays.
Next update Sunday, February 23, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Sun Feb 23 07:53:31 2025 |
|---|
| Description: | Title: Some users may encounter delays of up to two hours for anomaly detection alerts in Microsoft Sentinel
User Impact: Users may encounter delays of up to two hours for anomaly detection alerts in Microsoft Sentinel.
More info: Impacted scenarios include, but aren’t limited to:
- Advanced hunting
- Custom detections
- CloudAppEvents
- AppLogonEvents
- BehaviorInfo
- BehaviorEntities
- IdentityLogonEvents
- AlertInfo
- AlertEvidence tables
Current status: We’re reviewing service telemetry and system logs to identify the root cause, in order to develop a remediation plan.
Scope of Impact: Impact is specific to some users who are served through the affected infrastructure.
Next update Sunday, February 23, 2025, at 3:00 PM UTC
|
|---|
|
MO1011218 - Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 19 19:00:00 2025 |
|---|
| End Time: | Fri Feb 21 10:00:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 21 21:54:26 2025 |
|---|
| Root Cause: | A data pipeline issue was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 21 21:54:26 2025 |
|---|
| Description: | Title: Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center
User impact: Admins may have seen delays of at least 2.5 hours for some reports in the Microsoft 365 admin center.
More info: Delays may have been observed in the following reports:
-Microsoft 365 groups report
-Viva Engage activity report
-Viva Engage device usage report
-Microsoft Teams user activity report
-Microsoft 365 Active Users report
-Microsoft 365 Apps usage report
Final status: We've validated that the fix to clear the backlog of data in the affected pipeline has done so successfully and that impact has been fully alleviated.
Scope of impact: Admins may have seen delays of at least 2.5 hours for some reports in the Microsoft 365 admin center.
Start time: Thursday, February 20, 2025, at 12:00 AM UTC
End time: Friday, February 21, 2025, at 3:00 PM UTC
Root cause: A data pipeline issue was resulting in impact.
Next steps:
- We're analyzing the data pipeline to determine why this issue occurred in order to avoid impact like this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 20 21:56:08 2025 |
|---|
| Description: | Title: Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center
User impact: Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center.
More info: Delays may be observed in the following reports:
-Microsoft 365 groups report
-Viva Engage activity report
-Viva Engage device usage report
-Microsoft Teams user activity report
-Microsoft 365 Active Users report
-Microsoft 365 Apps usage report
Current status: We've developed and deployed a fix to clear the backlog of data in the affected pipeline. We're monitoring as it progresses to ensure completion and remediation. Users may start to see relief as the fix saturates their environment. We'll provide a completion timeline when one becomes available.
Scope of impact: Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center.
Start time: Thursday, February 20, 2025, at 12:00 AM UTC
Root cause: A data pipeline issue is resulting in impact.
Next update by: Saturday, February 22, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Wed Feb 19 22:07:22 2025 |
|---|
| Description: | Title: Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center
User impact: Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center.
More info: Delays may be observed in the following reports:
-Microsoft 365 groups report
-Viva Engage activity report
-Viva Engage device usage report
-Viva Engage groups activity report
-Microsoft 365 Active Users report
Current status: We've identified a data pipeline issue that's resulting in impact. We're analyzing the service health telemetry in order to determine the most expedient way to alleviate.
Scope of impact: Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center.
Start time: Thursday, February 20, 2025, at 12:00 AM UTC
Root cause: A data pipeline issue is resulting in impact.
Next update by: Friday, February 21, 2025, at 4:30 AM UTC
|
|---|
|
| Time: | Wed Feb 19 21:45:21 2025 |
|---|
| Description: | Title: Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center
User impact: Admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center.
Current status: We're investigating a potential issue in which admins may see delays of at least 2.5 hours for some reports in the Microsoft 365 admin center. We'll provide an update within 30 minutes.
|
|---|
|
WP1013244 - Some users' Cloud PCs intermittently aren't showing in Windows 365 Web Experience
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 21 14:19:00 2025 |
|---|
| End Time: | Fri Feb 21 19:36:00 2025 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 21 20:21:20 2025 |
|---|
| Root Cause: | The dependent service that facilitates Cloud PC population in the Windows 365 Web Experience wasn't processing API requests as efficiently as expected, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 21 20:21:20 2025 |
|---|
| Description: | Title: Some users' Cloud PCs intermittently aren't showing in Windows 365 Web Experience
User impact: Users' Cloud PCs intermittently weren't showing in Windows 365 Web Experience.
More info: Users weren't able to find their Cloud PCs through https://windows365.microsoft.com and therefore weren't able to connect with them through that method. As a workaround, users were able to connect using the following URL -https://windows365.microsoft.com/ent#/ or the Windows App.
Final status: We've analyzed the failed requests and identified that some of the requests were taking up to 90 seconds to complete. Therefore, we've increased the number of resources allocated to the dependent service to handle the API requests successfully and restarted the service to remediate the issue. We've confirmed with our internal logs that the API requests are processing as expected again.
Scope of impact: Some users served through the affected infrastructure weren't finding their Cloud PCs in Windows 365 Web Experience.
Start time: Friday, February 21, 2025, at 7:19 PM UTC
End time: Saturday, February 22, 2025, at 12:36 AM UTC
Root cause: The dependent service that facilitates Cloud PC population in the Windows 365 Web Experience wasn't processing API requests as efficiently as expected, which resulted in impact.
Next steps:
- We're collecting logs from the dependent service during the impacted timeframe so we can look for the underlying reason why the API requests weren't processing as efficiently as expected.
This is the final update for this event.
|
|---|
|
| Time: | Fri Feb 21 18:34:36 2025 |
|---|
| Description: | Title: Some users' Cloud PCs intermittently aren't showing in Windows 365 Web Experience
User impact: Users' Cloud PCs intermittently aren't showing in Windows 365 Web Experience.
More info: Users won't find their Cloud PCs through https://windows365.microsoft.com and therefore won't be able to connect with them through that method. As a workaround, users can connect using the following URL -https://windows365.microsoft.com/ent#/ or the Windows App. Users will be able to see Cloud PCs but some remote actions may not be available.
Current status: We've determined the dependent service that facilitates Cloud PC population in the Windows 365 Web Experience isn't processing API requests as efficiently as expected, resulting in impact. We're analyzing the failed requests to develop mitigations options for this impact.
Scope of impact: Some users served through the affected infrastructure aren't finding their Cloud PCs in Windows 365 Web Experience.
Root cause: The dependent service that facilitates Cloud PC population in the Windows 365 Web Experience isn't processing API requests as efficiently as expected, resulting in impact.
Next update by: Saturday, February 22, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Feb 21 17:10:40 2025 |
|---|
| Description: | Title: Some users' Cloud PCs aren't showing in Windows 365 Web Experience
User impact: Users' Cloud PCs aren't showing in Windows 365 Web Experience.
More info: Users won't find their Cloud PCs through https://windows365.microsoft.com and therefore won't be able to connect with them through that method. As a workaround, users can connect using the following URL -https://windows365.microsoft.com/ent#/ or the Windows App. Users will be able to see Cloud PCs but some remote actions may not be available.
Current status: We're analyzing service data and logs from a portion of infrastructure where the issue is reflecting to form a better understanding of the impact and formulate our next steps towards mitigating the issue.
Scope of impact: Some users served through the affected infrastructure aren't finding their Cloud PCs in Windows 365 Web Experience.
Next update by: Friday, February 21, 2025, at 11:30 PM UTC
|
|---|
|
TM1005182 - Some users' calls may crash if they utilize a firewall and place calls from the Microsoft Teams desktop client
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Feb 11 19:39:00 2025 |
|---|
| End Time: | Fri Feb 14 18:43:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Feb 21 19:56:54 2025 |
|---|
| Root Cause: | A misconfigured authentication component is causing some call traffic from the Microsoft Teams desktop client to fail, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 21 19:56:54 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Feb 18 18:54:26 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Feb 14 19:30:08 2025 |
|---|
| Description: | Title: Some users' calls may crash if they utilize a firewall and place calls from the Microsoft Teams desktop client
User impact: Users' calls would crash if they utilized a firewall and placed calls from the Microsoft Teams desktop client.
More info: Affected users may have been unable to join Microsoft Teams meetings. Only users within organizations that utilize a firewall were affected.
Final status: We’ve successfully deployed the fix and have validated that service has been restored.
Scope of impact: Some users may have been unable to join Microsoft Teams meetings or may have experienced their calls crashing if they placed them from the Microsoft Teams desktop client and their organization uses a firewall.
Start time: Wednesday, February 12, 2025, at 12:39 AM UTC
End time: Friday, February 14, 2025, at 11:43 PM UTC
Preliminary root cause: A misconfigured authentication component caused some firewalls, VPN and proxy setups to block traffic from the Microsoft Teams desktop client, which caused calls to fail.
Next steps:
- We're continuing to investigate why some firewalls, VPN and proxy setups were blocking Microsoft Teams calls following a recent change.
- We’re continuing to analyze the network configurations of impacted customers to fully understand the root cause.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Fri Feb 14 14:49:42 2025 |
|---|
| Description: | Title: Some users' calls may crash if they utilize a firewall and place calls from the Microsoft Teams desktop client
User impact: Users' calls may crash if they utilize a firewall and place calls from the Microsoft Teams desktop client.
More info: Affected users may also be unable to join Microsoft Teams meetings. Only users within organizations that utilize a firewall may be affected.
Current status: Our investigation has determined that a misconfigured authentication component is the true underlying issue leading to this impact, and it only affects users within organizations that utilize a firewall. We're working on a fix to correct this misconfiguration and we'll provide a timeline to resolution once available.
Scope of impact: Some users may be unable to join Microsoft Teams meetings or may experience their calls crashing if they place them from the Microsoft Teams desktop client and their organization uses a firewall.
Root cause: A misconfigured authentication component is causing some call traffic from the Microsoft Teams desktop client to fail, resulting in impact.
Next update by: Saturday, February 15, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Feb 13 18:35:23 2025 |
|---|
| Description: | Title: Some users' calls may crash if they're in a firewall and place them from the Microsoft Teams desktop client
User impact: Users' calls may crash if they're in a firewall and place them from the Microsoft Teams desktop client.
Current status: We've identified that disabling the offending change will remediate the issue, and we are working to disable it for all affected users. As our efforts progress, some users may begin to experience relief from the impact.
Scope of impact: Some users may be unable to join Microsoft Teams meetings or may experience their calls crashing if they place them from the Microsoft Teams desktop client and their organization uses a firewall.
Start time: Tuesday, February 11, 2025, at 12:00 AM UTC
Root cause: A network misconfiguration within the primary communication channel utilized by some users is resulting in impact.
Next update by: Friday, February 14, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Feb 13 14:22:08 2025 |
|---|
| Description: | Title: Some users' calls may crash if they're in a firewall and place them from the Microsoft Teams desktop client
User impact: Users' calls may crash if they're in a firewall and place them from the Microsoft Teams desktop client.
Current status: We've determined a network misconfiguration within the primary communication channel utilized by some users is resulting in impact. While we investigate the origin of this misconfiguration, we're redirecting all calls to a separate channel to remediate impact.
Scope of impact: Some users may be unable to join Microsoft Teams meetings or may experience their calls crashing if they place them from the Microsoft Teams desktop client and their organization uses a firewall.
Root cause: A network misconfiguration within the primary communication channel utilized by some users is resulting in impact.
Next update by: Thursday, February 14, 2025, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Feb 13 13:32:41 2025 |
|---|
| Description: | Title: Some users' calls may crash if they're in a firewall and place them from the Microsoft Teams desktop client
User impact: Users' calls may crash if they're in a firewall and place them from the Microsoft Teams desktop client.
Current status: We're reviewing the data provided by some affected users to help determine our next steps.
Scope of impact: Some users may be unable to join Microsoft Teams meetings or may experience their calls crashing if they place them from the Microsoft Teams desktop client and their organization uses a firewall.
Next update by: Thursday, February 13, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Feb 13 13:18:19 2025 |
|---|
| Description: | Title: Some users' calls may crash if they're in a firewall and place them from the Microsoft Teams desktop client
User impact: Users' calls may crash if they're in a firewall and place them from the Microsoft Teams desktop client.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1012913 - Users in North America may receive duplicate email notifications for sharing scenarios in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 20 10:20:00 2025 |
|---|
| End Time: | Fri Feb 21 02:30:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 21 16:11:07 2025 |
|---|
| Root Cause: | An issue occurred where latency in services responsible for delivering email notifications resulted in timeouts. This affected both the delivery of the email notifications and our deduping service, resulting in notifications re-queuing for delivery multiple times in error. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 21 14:53:47 2025 |
|---|
| Description: | Title: Users in North America may receive duplicate email notifications for sharing scenarios in SharePoint Online
User impact: Users may have received duplicate email notifications for sharing scenarios in SharePoint Online.
More info: Users may have received duplicate email notifications for scenarios such as Share, File/Page comments, mentions, tasks, likes, news, or migration flows.
Final status: We’ve confirmed with affected users that this issue is no longer occurring and that the issue is resolved.
Scope of impact: Any user may have received duplicate email notifications for sharing scenarios in SharePoint Online.
Start time: Thursday, February 20, 2025, at 3:20 PM UTC
End time: Friday, February 21, 2025, at 7:30 AM UTC
Root cause: An issue occurred where latency in services responsible for delivering email notifications resulted in timeouts. This affected both the delivery of the email notifications and our deduping service, resulting in notifications re-queuing for delivery multiple times in error.
Next steps:
- We’re continuing our investigation to determine the underlying cause of the timeout on the latency service to better detect and prevent issues like this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 21 12:09:45 2025 |
|---|
| Description: | Title: Users may receive duplicate email notifications for sharing scenarios in SharePoint Online
User impact: Users may receive duplicate email notifications for sharing scenarios in SharePoint Online.
More info: Users may receive duplicate email notifications for scenarios such as Share, File/Page comments, mentions, tasks, likes, news, or migration flows.
Current status: We've confirmed that previous mitigating actions taken to resolve the latency issue involved rerouting email notification request traffic were successful, email delivery queues have drained, and no further duplicate emails should be sent. We're continuing to test with a subset of users to confirm that the impacted scenarios no longer result in duplicate email notification deliveries.
Scope of impact: Users may receive duplicate email notifications for sharing scenarios in SharePoint Online.
Start time: Thursday, February 20, 2025, at 3:20 PM UTC
Root cause: An issue occurred where latency in services responsible for delivering email notifications resulted in timeouts. This affected both the delivery of the email notifications and our deduping service, resulting in notifications re-queuing for delivery multiple times in error.
Next update by: Friday, February 21, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Feb 21 11:21:53 2025 |
|---|
| Description: | Title: Users may receive duplicate email notifications for sharing scenarios in SharePoint Online
User impact: Users may receive duplicate email notifications for sharing scenarios in SharePoint Online.
More info: Users may receive duplicate email notifications for scenarios such as Share, File/Page comments, mentions, tasks, likes, news, or migration flows.
Current status: We've identified an issue which occurred where latency in services responsible for delivering email notifications resulted in timeouts. This affected both the delivery of the email notifications and our deduping service, resulting in notifications re-queuing for delivery multiple times in error. After resolving the previous issue, we suspect that duplicate email have been delivered, draining the queue and resolving the issue. We're reaching out to a subset of users to confirm the issue is no longer occurring.
Scope of impact: Users may receive duplicate email notifications for sharing scenarios in SharePoint Online.
Start time: Thursday, February 20, 2025, at 3:20 PM UTC
Next update by: Friday, February 21, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Feb 21 10:59:58 2025 |
|---|
| Description: | Title: Users may receive duplicate email notifications for sharing scenarios in SharePoint Online
User impact: Users may receive duplicate email notifications for sharing scenarios in SharePoint Online.
More info: Users may receive duplicate email notifications for scenarios such as having a file shared with them, or having list comments shared to them.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MP1010823 - Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 12 09:28:00 2025 |
|---|
| End Time: | Thu Feb 20 19:00:00 2025 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 21 15:25:38 2025 |
|---|
| Root Cause: | A portion of database infrastructure that facilitates admin access to eDiscovery (Premium) cases in the compliance portal became unbalanced stemming from latent code issues that caused impact during periods of higher traffic to the service. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 20 23:51:23 2025 |
|---|
| Description: | Title: Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
User impact: Admins may have experienced failures and slowness accessing eDiscovery (Premium) cases in the compliance portal.
Final status: We've successfully rerouted traffic to alternate infrastructure, and after reviewing our service telemetry we've confirmed that impact has been remediated. If any admins are still experiencing impact, we recommend signing out, clearing their browser cache, and then starting a new browser session to resolve the issue.
Scope of impact: Any admin serviced by the affected infrastructure attempting access to eDiscovery (Premium) cases in the compliance portal may have been intermittently impacted.
Start time: Wednesday, February 12, 2025, at 2:28 PM UTC
End time: Friday, February 21, 2025, at 12:00 AM UTC
Root cause: A portion of database infrastructure that facilitates admin access to eDiscovery (Premium) cases in the compliance portal became unbalanced stemming from latent code issues that caused impact during periods of higher traffic to the service.
Next steps:
- We're analyzing the affected infrastructure to determine if any additional changes or improvements can be made to help detect sooner and prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 20 18:43:25 2025 |
|---|
| Description: | Title: Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
User impact: Admins may experience intermittent failures and slowness accessing eDiscovery (Premium) cases in the compliance portal.
Current status: While our fix to optimize the database infrastructure so that it supports higher levels of traffic has been deployed, we've received reports that impact may be persisting for some admins. We're routing the traffic to alternate infrastructure with a greater ability to process traffic to remediate the issue more quickly.
Scope of impact: Any admin serviced by the affected infrastructure attempting access to eDiscovery (Premium) cases in the compliance portal may be impacted.
Root cause: A portion of database infrastructure that facilitates admin access to eDiscovery (Premium) cases in the compliance portal has become unbalanced stemming from latent code issues that cause impact from higher traffic to the service.
Next update by: Friday, February 21, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Feb 20 13:18:02 2025 |
|---|
| Description: | Title: Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
User impact: Admins may experience intermittent failures and slowness accessing eDiscovery (Premium) cases in the compliance portal.
Current status: We're deploying the code fix to optimize the database infrastructure so that it supports higher levels of traffic. We expect this will complete and remediate impact by our next scheduled update.
Scope of impact: Any admin serviced by the affected infrastructure may be impacted by this event, and any admin attempting to eDiscovery (Premium) cases in the compliance portal may be impacted.
Root cause: A portion of database infrastructure that facilitates admin access to eDiscovery (Premium) cases in the compliance portal has become unbalanced stemming from latent code issues that cause impact from higher traffic to the service.
Next update by: Friday, February 21, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Feb 19 22:50:20 2025 |
|---|
| Description: | Title: Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
User impact: Admins may not be able to access eDiscovery (Premium) cases in the compliance portal.
More info: Affected admins may see slowness or an error when navigating the Cases dashboard in the compliance portal.
Current status: We've analyzed the service infrastructure and identified that the portion of database infrastructure that facilitates admin access to eDiscovery (Premium) cases in the compliance portal has become unbalanced, stemming from latent code issues that cause impact from higher traffic to the service. We're working on testing and validating a code fix to optimize the database infrastructure, to support the higher traffic, and remediate impact.
Scope of impact: Any admin serviced by the affected infrastructure may be impacted by this event, and any admin attempting to eDiscovery (Premium) cases in the compliance portal may be impacted.
Root cause: A portion of database infrastructure that facilitates admin access to eDiscovery (Premium) cases in the compliance portal has become unbalanced stemming from latent code issues that cause impact from higher traffic to the service.
Next update by: Thursday, February 20, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Feb 19 20:31:38 2025 |
|---|
| Description: | Title: Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
User impact: Admins may not be able to access eDiscovery (Premium) cases in the compliance portal.
More info: Affected admins may see slowness or an error when navigating the Cases dashboard in the compliance portal.
Current status: We're continuing our analysis of the portion of database infrastructure which we've observed performing below service performance thresholds so we can understand the root cause of this issue and identify a solution.
Scope of impact: Any admin serviced by the affected infrastructure may be impacted by this event, and any admin attempting to eDiscovery (Premium) cases in the compliance portal may be impacted.
Next update by: Thursday, February 20, 2025, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Feb 19 18:16:46 2025 |
|---|
| Description: | Title: Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
User impact: Admins may not be able to access eDiscovery (Premium) cases in the compliance portal.
More info: Affected admins may see slowness or an error when navigating the Cases dashboard in the compliance portal.
Current status: We've observed through our investigation that a portion of database infrastructure which is leveraged during the access of eDiscovery (Premium) cases is performing below service performance thresholds. We're further analyzing this portion of infrastructure to better understand the issue and determine a viable mitigation strategy.
Scope of impact: Any admin serviced by the affected infrastructure may be impacted by this event, and any admin attempting to eDiscovery (Premium) cases in the compliance portal may be impacted.
Next update by: Thursday, February 20, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Feb 19 15:50:39 2025 |
|---|
| Description: | Title: Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
User impact: Admins may not be able to access eDiscovery (Premium) cases in the compliance portal.
More info: Affected admins may see slowness or an error when navigating the Cases dashboard in the compliance portal.
Current status: We're continuing to review the available data provided by affected admins so we can isolate the root cause of this issue and identify our next troubleshooting steps.
Scope of impact: Any admin serviced by the affected infrastructure may be impacted by this event, and any admin attempting to eDiscovery (Premium) cases in the compliance portal may be impacted.
Next update by: Wednesday, February 19, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Feb 19 14:20:48 2025 |
|---|
| Description: | Title: Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
User impact: Admins may not be able to access eDiscovery (Premium) cases in the compliance portal.
More info: Affected admins may see slowness or an error when navigating the Cases dashboard in the compliance portal.
Current status: We're reviewing the provided impact details shared by some affected admins to help us better understand the underlying root cause of this issue and determine our next investigative steps.
Scope of impact: Any admin serviced by the affected infrastructure may be impacted by this event, and any admin attempting to eDiscovery (Premium) cases in the compliance portal may be impacted.
Next update by: Wednesday, February 19, 2025, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Feb 19 13:51:59 2025 |
|---|
| Description: | Title: Admins may not be able to access Microsoft Purview eDiscovery (Premium) cases in the Microsoft Purview compliance portal
User impact: Admins may not be able to access eDiscovery (Premium) cases in the compliance portal.
Current status: We're investigating a potential issue with admins being unable to access eDiscovery (Premium) cases in the Microsoft Purview admin center, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
Scope of impact: Any admin serviced by the affected infrastructure may be impacted by this event, and any admin attempting to eDiscovery (Premium) cases in the compliance portal may be impacted.
|
|---|
|
EX999898 - Some users may be unable to utilize the search function in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 30 13:55:00 2025 |
|---|
| End Time: | Fri Feb 14 17:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Feb 18 19:53:17 2025 |
|---|
| Root Cause: | A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 18 19:53:17 2025 |
|---|
| Description: | Title: Some users may be unable to utilize the search function in Exchange Online
User impact: Users may have been unable to utilize the search function in Exchange Online.
Final status: We've confirmed that the reversion of the problematic update has completed, resolving the impact.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
End time: Friday, February 14, 2025, at 10:00 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next steps:
- We're reviewing and assessing our deployment testing to identifying changes that can be made to prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 18 17:20:31 2025 |
|---|
| Description: | Title: Some users may be unable to utilize the search function in Exchange Online
User impact: Users may be unable to utilize the search function in Exchange Online.
Current status: We're continuing to monitor the reversion of the problematic update as it propagates. We'll aim to provide a timeline for this process to complete by our next scheduled communications update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next update by: Friday, February 21, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Feb 14 15:40:49 2025 |
|---|
| Description: | Title: Some users may be unable to utilize the search function in Exchange Online
User impact: Users may be unable to utilize the search function in Exchange Online.
Current status: We’re continuing to monitor the process of reverting the problematic update to ensure it completes as expected. Some users may experience impact remediation as the deployment reaches them, and we’ll continue monitoring the deployment until it’s reached all affected users.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next update by: Tuesday, February 18, 2025, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Feb 13 21:33:24 2025 |
|---|
| Description: | Title: Some users may be unable to utilize the search function in Exchange Online
User impact: Users may be unable to utilize the search function in Exchange Online.
Current status: The previously mentioned reversion of the update leading to impact has reached approximately 50 percent of the affected service infrastructure. Some users may experience early relief as the fix progresses throughout the impacted environments.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next update by: Friday, February 14, 2025, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Feb 13 13:30:14 2025 |
|---|
| Description: | Title: Some users may be unable to utilize the search function in Exchange Online
User impact: Users may be unable to utilize the search function in Exchange Online.
Current status: The previously mentioned reversion of the update leading to impact has reached approximately 23 percent of the affected service infrastructure. We're aiming provide a timeline to remediation as full saturation approaches. Some users may experience early relief as the fix progresses throughout the impacted environments.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next update by: Friday, February 14, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Feb 12 12:01:18 2025 |
|---|
| Description: | Title: Some users may be unable to utilize the search function in Exchange Online
User impact: Users may be unable to utilize the search function in Exchange Online.
Current status: We’re seeing continued signs of improvement to service telemetry as the process of reverting the problematic deployment is ongoing. We’ll continue monitoring the reversion processes as we determine an estimated timeline for impact remediation by our next update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next update by: Thursday, February 13, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Feb 11 18:38:21 2025 |
|---|
| Description: | Title: Some users may be unable to utilize the search function in Exchange Online
User impact: Users may be unable to utilize the search function in Exchange Online.
Current status: Our service health telemetry indicates that while the previously mentioned rebalancing operation has reduced instances of the issue, some impact is ongoing. We're proceeding with a complete reversion of the deployment that's leading to impact to restore the affected Exchange Online infrastructure to its most recent healthy state, which we believe will fully remediate the issue. We'll provide a timeline for the reversion and remediation as it becomes available.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next update by: Wednesday, February 12, 2025, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Feb 11 12:39:56 2025 |
|---|
| Description: | Title: Some users may be unable to utilize the search function in Exchange Online
User impact: Users may be unable to utilize the search function in Exchange Online.
Current status: We've completed our rebalancing and telemetry indicates improvement. We're continuing to monitor the environment while reviewing recent service updates which may be contributing to impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next update by: Wednesday, February 12, 2025, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Feb 11 00:46:05 2025 |
|---|
| Description: | Title: Some users may be unable to utilize the search function in Exchange Online
User impact: Users may be unable to utilize the search function in Exchange Online.
Current status: We're finalizing the process of rerouting affected requests to alternate portions of service infrastructure to resolve the remaining impact. In parallel, we're assessing to confirm whether a separate search component issue may be resulting in similar impact for a subset of users who reported the issue.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next update by: Tuesday, February 11, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Feb 7 14:00:06 2025 |
|---|
| Description: | Title: Some users can't search for any email messages within Exchange Online
User impact: Users can't search for any email messages within Exchange Online.
More info: Additionally, some users don't receive results for People search in Outlook on the web and receive the following error message, "Something went wrong".
Current status: We've identified a recent deployment to a portion of the service infrastructure that supports search functionality within Exchange Online, that correlates to when impact initially began for this event. While this deployment was running, a portion of the supporting service infrastructure operated inefficiently as the changes saturated. We've monitored service health telemetry, which indicates a majority of the affected service infrastructure has recovered as the deployment has completed. A portion of the affected infrastructure still remains impacted, and we're working to route service requests to a healthy portion of service infrastructure to fully remediate impact.
Scope of impact: Your organization is affected by this event, and some users attempting to search for email messages within Exchange Online are impacted.
Start time: Thursday, January 30, 2025, at 6:55 PM UTC
Root cause: A recent deployment to a portion of the service infrastructure that supports search functionality was causing the service infrastructure to operate inefficiently while the changes from the deployment saturated, resulting in impact.
Next update by: Tuesday, February 11, 2025, at 6:30 AM UTC
|
|---|
|
| Time: | Fri Feb 7 11:50:26 2025 |
|---|
| Description: | Title: Some users can't search for any email messages within Exchange Online
User impact: Users can't search for any email messages within Exchange Online.
Current status: We've updated the Title, User impact, and Scope of impact sections of the communication based on further elaboration of the impact scenario. We're reviewing error logs to confirm if impact is correlated to any recent changes made to the Exchange Online service so we can develop our plan for mitigative actions.
Scope of impact: Your organization is affected by this event, and some users attempting to search for email messages within Exchange Online are impacted.
Next update by: Friday, February 7, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Feb 7 09:13:46 2025 |
|---|
| Description: | Title: Some users experience failures when attempting to search in Exchange Online
User impact: Users experience failures when attempting to search in Exchange Online.
Current status: We're analyzing sample provided timeout error messages alongside details alongside the support case, to inform our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to search in Exchange Online are impacted.
Next update by: Friday, February 7, 2025, at 5:00 PM UTC
|
|---|
|
CP1007802 - Admins' Microsoft Copilot (Microsoft 365) readiness reports may be delayed in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Sun Feb 16 19:00:00 2025 |
|---|
| End Time: | Mon Feb 17 14:00:00 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 17 21:57:27 2025 |
|---|
| Root Cause: | A data pipeline issue occurred on a portion of infrastructure responsible for populating Copilot readiness reports in the Microsoft 365 admin center and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 17 21:56:49 2025 |
|---|
| Description: | Title: Admins' Microsoft Copilot (Microsoft 365) readiness reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Copilot readiness reports may have been delayed in the Microsoft 365 admin center.
Final status: We've implemented a fix to reprocess the necessary pipeline data on the affected portion of infrastructure and confirmed with our internal telemetry that the impact is remediated.
Scope of impact: Any admin that attempted to review Copilot readiness reports in the Microsoft 365 admin center may have experienced impact.
Start time: Monday, February 17, 2025, at 12:00 AM UTC
End time: Monday, February 17, 2025, at 7:00 PM UTC
Root cause: A data pipeline issue occurred on a portion of infrastructure responsible for populating Copilot readiness reports in the Microsoft 365 admin center and resulted in impact.
Next steps:
- We're further reviewing the affected portion of infrastructure to understand the underlying cause of the data pipeline issue, and to prevent similar impact scenarios from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Sun Feb 16 22:25:01 2025 |
|---|
| Description: | Title: Admins' Microsoft Copilot (Microsoft 365) readiness reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Copilot readiness reports may be delayed in the Microsoft 365 admin center.
Current status: We've identified that the Copilot readiness report from the Microsoft 365 admin center may be delayed for admins. Additionally, we've determined that the impact has been caused by a data pipeline issue, which we're actively working on resolving and to minimize the impact.
Scope of impact: Any admin attempting to review Copilot readiness reports in the Microsoft 365 admin center may experience impact.
Start time: Monday, February 17, 2025, at 12:00 AM UTC
Next update by: Tuesday, February 18, 2025, at 5:00 AM UTC
|
|---|
|
DZ1004831 - Some admins may have received delayed telemetry and alerts in the Microsoft 365 Defender portal
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 28 04:00:00 2025 |
|---|
| End Time: | Mon Feb 17 06:10:00 2025 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 17 08:50:03 2025 |
|---|
| Root Cause: | A regression in the authentication component, responsible for handling VDI machines' telemetry and alerts caused impact to occur. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 17 08:49:08 2025 |
|---|
| Description: | Title: Some admins may have received delayed telemetry and alerts in the Microsoft 365 Defender portal
User impact: Admins may have received delayed telemetry and alerts in the Microsoft 365 Defender portal.
Final status: We’ve processed the backlogged telemetry and alerts, and confirmed after a period of monitoring that impact has been remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Tuesday, January 28, 2025, at 9:00 AM UTC
End time: Monday, February 17, 2025, at 11:10 AM UTC
Root cause: A regression in the authentication component, responsible for handling VDI machines' telemetry and alerts caused impact to occur.
Next steps:
- We're continuing to review the authentication component and service monitoring telemetry, to identify the underlying root cause and prevent this issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Sun Feb 16 06:46:59 2025 |
|---|
| Description: | Title: Some admins may receive delayed telemetry and alerts in the Microsoft 365 Defender portal
User impact: Admins may receive delayed telemetry and alerts in the Microsoft 365 Defender portal.
Current status: We're continuing to process the backlogged telemetry and alerts to fully remediate the impact, and expect this process will be complete by Monday, February 17, 2025.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Tuesday, January 28, 2025, at 9:00 AM UTC
Root cause: A regression in the authentication component responsible for handling VDI machines' telemetry and alerts has caused impact.
Next update by: Monday, February 17, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Thu Feb 13 05:02:52 2025 |
|---|
| Description: | Title: Some admins may receive delayed telemetry and alerts in the Microsoft 365 Defender portal
User impact: Admins may receive delayed telemetry and alerts in the Microsoft 365 Defender portal.
More info: Specifically, admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts for Virtual Desktop Infrastructure (VDI) machines in the Microsoft 365 Defender portal.
Current status: We've identified that a regression in the authentication component responsible for handling VDI machines' telemetry and alerts has caused impact. To mitigate impact, we've reverted the authentication component to the last known functional version. We're now processing the backlogged telemetry and alerts to fully remediate the impact, and expect this process will be complete by Monday, February 17, 2025.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Tuesday, January 28, 2025, at 9:00 AM UTC
Root cause: A regression in the authentication component responsible for handling VDI machines' telemetry and alerts has caused impact.
Next update by: Sunday, February 16, 2025, at 12:00 PM UTC
|
|---|
|
MO1005641 - Admins may have seen delays with report data in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 13 19:01:00 2025 |
|---|
| End Time: | Sat Feb 15 03:40:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Feb 15 07:48:52 2025 |
|---|
| Root Cause: | A recent update to a setting for generating report data was causing delays with propagating the report data to the Microsoft 365 admin center. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Feb 15 07:48:52 2025 |
|---|
| Description: | Title: Admins may have seen delays with report data in the Microsoft 365 admin center
User impact: Admins may have seen delays with report data in the Microsoft 365 admin center.
More info: The impacted reports included:
-Project activity
-Microsoft 365 Apps usage
-Active Users
-Email activity
-Mailbox usage
Final status: We've successfully processed the backlogged report data and confirmed that impact is no longer occurring.
Scope of impact: This issue may have potentially impacted any admin viewing the impacted report data in the Microsoft 365 admin center.
Start time: Friday, February 14, 2025, at 12:01 AM UTC
End time: Saturday, February 15, 2025, at 8:40 AM UTC
Root cause: A recent update to a setting for generating report data was causing delays with propagating the report data to the Microsoft 365 admin center.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 14 01:04:39 2025 |
|---|
| Description: | Title: Admins may see delays with report data in the Microsoft 365 admin center
User impact: Admins may see delays with report data in the Microsoft 365 admin center.
More info: The impacted reports include:
-Project activity
-Microsoft 365 Apps usage
-Active Users
-Email activity
-Mailbox usage
Current status: We identified a recent update to a setting for generating report data is causing delays with propagating the report data to the Microsoft 365 admin center. We've corrected the setting and are waiting for the backfill of the report data to complete to confirm the impact is remediated.
Scope of impact: This issue may potentially impact any admin viewing the impacted report data in the Microsoft 365 admin center.
Start time: Friday, February 14, 2025, at 12:01 AM UTC
Root cause: A recent update to a setting for generating report data is causing delays with propagating the report data to the Microsoft 365 admin center.
Next update by: Monday, February 17, 2025, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Feb 14 00:38:19 2025 |
|---|
| Description: | Title: Admins may see delays with report data in the Microsoft 365 admin center
User impact: Admins may see delays with report data in the Microsoft 365 admin center.
More info: The impacted reports include:
-Project activity
-Microsoft 365 Apps usage
-Active Users
-Email activity
-Mailbox usage
Current status: We're investigating a potential issue with the Microsoft 365 suite and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX989566 - Some users may not see sender names in the search results of the Outlook 2016 MSI client
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 15 07:00:00 2025 |
|---|
| End Time: | Thu Feb 13 07:00:00 2025 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 14 12:03:41 2025 |
|---|
| Root Cause: | A recent service update contained a code error that prevented search results from loading successfully, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 14 12:03:41 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may have not seen sender names in the search results of the Outlook 2016 MSI client.
More info: Additionally, some users may have seen items in search results displayed as unread.
Final status: We've confirmed that the fix has completed deployment to the impacted infrastructure and validated this has remediated impact using service telemetry.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may have been impacted.
Start time: Wednesday, January 15, 2025, at 12:00 PM UTC
End time: Thursday, February 13, 2025, at 8:00 PM UTC
Root cause: A recent service update contained a code error that prevented search results from loading successfully, resulting in impact.
Next steps:
- We're continuing our analysis of the impacting code error to better identify and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 13 12:43:52 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
More info: Additionally, some users may see items in search results displayed as unread.
Current status: We've verified that the solution is propagating throughout the affected environments, and as it saturates, affected users may experience impact relief. Once available, we'll provide a resolution timeline.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Start time: Wednesday, January 15, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code error that's preventing search results from loading successfully, resulting in impact.
Next update by: Friday, February 14, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Feb 6 12:39:28 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
More info: Additionally, some users may see items in search results displayed as unread.
Current status: The deployment of the fix is taking longer than initially estimated due to some issues that needed to be addressed that were halting progress. We addressed those issues and have resumed the deployment. We'll aim to provide a timeline for the deployment to complete by our next scheduled communications update.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Start time: Wednesday, January 15, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code error that's preventing search results from loading successfully, resulting in impact.
Next update by: Thursday, February 13, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jan 30 11:28:11 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
More info: Additionally, some users may see items in search results displayed as unread.
Current status: We're reverting the code change and applying a fix. Our initial estimate of the deployment progress suggests this should complete by the end of next week. We're monitoring the fix propagation to refine our assessment of when the issue will be fully resolved.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Start time: Wednesday, January 15, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code error that's preventing search results from loading successfully, resulting in impact.
Next update by: Thursday, February 6, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jan 29 12:39:54 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
More info: Additionally, some users may see items in search results displayed as unread.
Current status: We've confirmed that reverting the impacting change has remediated the issue in our test environments and are working to initiate the revert more broadly. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Start time: Wednesday, January 15, 2025, at 12:00 PM UTC
Root cause: A recent service update contains a code error that's preventing search results from loading successfully, resulting in impact.
Next update by: Friday, January 31, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jan 28 19:52:40 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
More info: Additionally, some users may see items in search results displayed as unread.
Current status: We've identified a recent code change through our review of network trace logs that appears to be resulting in impact. We're in the process of reverting this change within our internal testing environment to validate our theory, at which point we will deploy the fix throughout the affected environment.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Next update by: Wednesday, January 29, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jan 28 13:54:08 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
More info: Additionally, some users may see items in search results displayed as unread.
Current status: We've reproduced the issue within our internal test environment and we're reviewing the reproduction in parallel with the network trace logging to progress our investigation into root cause, which will inform our next steps regarding impact remediation.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Next update by: Wednesday, January 29, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Jan 27 20:00:56 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
Current status: We're continuing to review network trace logs to isolate the source of impact. In parallel, we're attempting to reproduce the issue to aid in the investigating and help us determine our next steps.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Next update by: Tuesday, January 28, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Jan 27 14:48:16 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
Current status: Our investigation into the network trace logs is taking longer than anticipated, but we're continuing to make progress identifying the root cause and strategy that remediates impact.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Next update by: Tuesday, January 28, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Jan 27 12:51:31 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
Current status: We're reviewing network trace logs to determine the root cause and a strategy that remediates impact.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Next update by: Monday, January 27, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Jan 27 10:44:14 2025 |
|---|
| Description: | Title: Some users may not see sender names in the search results of the Outlook 2016 MSI client
User impact: Users may not see sender names in the search results of the Outlook 2016 MSI client.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users attempting to search in the Outlook 2016 MSI client may be impacted.
Next update by: Monday, January 27, 2025, at 6:00 PM UTC
|
|---|
|
TM1003261 - Users may encounter call failures when placing calls or joining meetings using the Microsoft Teams web client
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 11 11:00:00 2025 |
|---|
| End Time: | Thu Feb 13 13:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 13 14:16:37 2025 |
|---|
| Root Cause: | A recent service optimization release contained an error, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 13 14:16:37 2025 |
|---|
| Description: | Title: Users may encounter call failures when placing calls or joining meetings using the Microsoft Teams web client
User impact: Users may have encountered call failures when placing calls or joining meetings using the Microsoft Teams web client.
More info: While we were working to remediate impact, affected users were able to bypass the issue by refreshing the web client, or using the Microsoft Teams desktop client or mobile apps.
Final status: Our deployment of the fix to disable the impacting change is complete, and our service health telemetry confirms that impact is remediated.
Scope of impact: Your organization was impacted by this event, and all users joining meetings or placing calls using the Microsoft Teams web client were impacted.
Start time: Tuesday, February 11, 2025, at 4:00 PM UTC
End time: Thursday, February 13, 2025, at 6:30 PM UTC
Root cause: A recent service optimization release contained an error, resulting in impact.
Next steps:
- We're reviewing our Microsoft Teams code base update procedures pertaining to service optimization to prevent similar impact in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 12 14:16:55 2025 |
|---|
| Description: | Title: Users may encounter call failures when placing calls or joining meetings using the Microsoft Teams web client
User impact: Users may encounter call failures when placing calls or joining meetings using the Microsoft Teams web client.
More info: While we're working to remediate impact, affected users are able to bypass the issue by refreshing the web client, or using the Microsoft Teams desktop client or mobile apps.
Current status: Our ongoing monitoring indicates that while service has been restored for the majority of affected users, some call failures are still intermittently occurring. We're continuing our extended monitoring period to ensure that the previously mentioned fix to disable the impacting change fully saturates the affected environment and that impact is remediated for all users.
Scope of impact: Your organization is impacted by this event and all users joining meetings or placing calls using the Microsoft Teams web client are impacted.
Start time: Tuesday, February 11, 2025, at 4:00 PM UTC
Root cause: A recent service optimization release contains an error, resulting in impact.
Next update by: Thursday, February 13, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Feb 11 21:32:28 2025 |
|---|
| Description: | Title: Users may encounter call failures when placing calls or joining meetings using the Microsoft Teams web client
User impact: Users may encounter call failures when placing calls or joining meetings using the Microsoft Teams web client.
More info: While we're working to remediate impact, affected users are able to bypass the issue by refreshing the web client, or using the Microsoft Teams desktop client or mobile apps.
Current status: Our monitoring indicates that most users will see relief now. We're continuing to monitor telemetry to confirm when service health is back to normal levels for all users.
Scope of impact: Your organization is impacted by this event and all users joining meetings or placing calls using the Microsoft Teams web client are impacted.
Start time: Tuesday, February 11, 2025, at 4:00 PM UTC
Root cause: A recent service optimization release contains an error, resulting in impact.
Next update by: Wednesday, February 12, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Feb 11 17:07:01 2025 |
|---|
| Description: | Title: Users may encounter call failures when placing calls or joining meetings using the Microsoft Teams web client
User impact: Users may encounter call failures when placing calls or joining meetings using the Microsoft Teams web client.
More info: While we're working to remediate impact, affected users are able to bypass the issue by refreshing the web client, or using the Microsoft Teams desktop client or mobile apps.
Current status: Our monitoring has identified an unexpected increase in call failures with users joining meetings or placing calls using the Microsoft Teams web client. We've determined that a recent service optimization release contains an error, resulting in impact. We've disabled the impacting change and are monitoring as our telemetry shows improvement.
Scope of impact: Your organization is impacted by this event and all users joining meetings or placing calls using the Microsoft Teams web client are impacted.
Start time: Tuesday, February 11, 2025, at 4:00 PM UTC
Root cause: A recent service optimization release contains an error, resulting in impact.
Next update by: Wednesday, February 12, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Feb 11 16:51:58 2025 |
|---|
| Description: | Title: Users may encounter call failures when placing calls using the Microsoft Teams web client
User impact: Users may encounter call failures when placing calls using the Microsoft Teams web client.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM996209 - Some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X
| Status: | serviceRestored |
|---|
| Start Time: | Sun Dec 1 19:00:00 2024 |
|---|
| End Time: | Tue Feb 11 19:30:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 13 12:34:42 2025 |
|---|
| Root Cause: | A recent code change for Microsoft Teams introduced a code error for devices on macOS versions 15 and above that prevented a popup to enable screensharing from being presented to affected users. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 13 12:34:42 2025 |
|---|
| Description: | Title: Some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X
User impact: Users may have been unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
Final status: The deployment of the fix has completed and we've confirmed with previously affected users that impact is remediated.
Scope of impact: Your organization was affected by this event, and some users may have been unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
Start time: Monday, December 2, 2024, at 12:00 AM UTC
End time: Wednesday, February 12, 2025, at 12:30 AM UTC
Root cause: A recent code change for Microsoft Teams introduced a code error for devices on macOS versions 15 and above that prevented a popup to enable screensharing from being presented to affected users.
Next steps:
- We're reviewing our code change validation procedures to identify improvements that can detect and prevent similar code issues from causing impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 11 12:11:26 2025 |
|---|
| Description: | Title: Some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X
User impact: Users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
More info: Affected users may utilize the following workaround to re-enable screensharing:
1. Open System Settings
2. Select Privacy & Security
3. Select Screen & System Audio Recording
4. If Microsoft Teams is available on the list of applications, delete it by selecting it and clicking -.
5. Click on + and select Microsoft Teams from the Application folder.
6. Click on Quit & Reopen.
7. Verify Microsoft Teams is enabled in the Screen & System Audio Recording tab.
8. Relaunch Microsoft Teams.
If users are unable to directly grant these permissions, contact your admin to allow you to change screensharing permissions and they will be able to follow the listed guidance.
Current status: We're monitoring the deployment of the fix as it nears completion. We anticipate the fix will be available to all affected users by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
Start time: Monday, December 2, 2024, at 12:00 AM UTC
Estimated time to resolve: We anticipate the deployment of the fix will complete by Thursday, February 13, 2025, at 6:30 PM UTC.
Root cause: A recent code change for Microsoft Teams has introduced a code error for devices on macOS versions 15 and above that prevents a popup to enable screensharing from being presented to affected users.
Next update by: Thursday, February 13, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Feb 4 13:06:07 2025 |
|---|
| Description: | Title: Some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X
User impact: Users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
More info: Affected users may utilize the following workaround to re-enable screensharing:
1. Open System Settings
2. Select Privacy & Security
3. Select Screen & System Audio Recording
4. If Microsoft Teams is available on the list of applications, delete it by selecting it and clicking -.
5. Click on + and select Microsoft Teams from the Application folder.
6. Click on Quit & Reopen.
7. Verify Microsoft Teams is enabled in the Screen & System Audio Recording tab.
8. Relaunch Microsoft Teams.
If users are unable to directly grant these permissions, contact your admin to allow you to change screensharing permissions and they will be able to follow the listed guidance.
Current status: We've begun deploying the fix to all affected environments. We'll aim to provide a timeline for the deployment to complete by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
Start time: Monday, December 2, 2024, at 12:00 AM UTC
Root cause: A recent code change for Microsoft Teams has introduced a code error for devices on macOS versions 15 and above that prevents a popup to enable screensharing from being presented to affected users.
Next update by: Tuesday, February 11, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Feb 4 11:45:24 2025 |
|---|
| Description: | Title: Some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X
User impact: Users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
More info: Affected users may utilize the following workaround to re-enable screensharing:
1. Open System Settings
2. Select Privacy & Security
3. Select Screen & System Audio Recording
4. If Microsoft Teams is available on the list of applications, delete it by selecting it and clicking -.
5. Click on + and select Microsoft Teams from the Application folder.
6. Click on Quit & Reopen.
7. Verify Microsoft Teams is enabled in the Screen & System Audio Recording tab.
8. Relaunch Microsoft Teams.
If users are unable to directly grant these permissions, contact your admin to allow you to change screensharing permissions and they will be able to follow the listed guidance.
Current status: We've validated the fix's efficacy in remediating the impact within our internal test environment and we're preparing to begin the deployment to all affected environments. We'll aim to provide a timeline for deployment to begin by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
Start time: Monday, December 2, 2024, at 12:00 AM UTC
Root cause: A recent code change for Microsoft Teams has introduced a code error for devices on macOS versions 15 and above that prevents a popup to enable screensharing from being presented to affected users.
Next update by: Thursday, February 6, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Feb 3 11:54:15 2025 |
|---|
| Description: | Title: Some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X
User impact: Users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
More info: Affected users may utilize the following workaround to re-enable screensharing:
1. Open System Settings
2. Select Privacy & Security
3. Select Screen & System Audio Recording
4. If Microsoft Teams is available on the list of applications, delete it by selecting it and clicking -.
5. Click on + and select Microsoft Teams from the Application folder.
6. Click on Quit & Reopen.
7. Verify Microsoft Teams is enabled in the Screen & System Audio Recording tab.
8. Relaunch Microsoft Teams.
If users are unable to directly grant these permissions, contact your admin to allow you to change screensharing permissions and they will be able to follow the listed guidance.
Current status: We've determined that a recent code change for Microsoft Teams has introduced a code error for devices on macOS versions 15 and above that prevents a popup to enable screensharing from being presented to affected users. We're developing a fix to address the code misconfiguration, and we anticipate we'll begin deployment of our fix by our next scheduled communications update on Monday, February 4, 2025, at 6:30 PM UTC.
Scope of impact: Your organization is affected by this event, and some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
Start time: Monday, December 2, 2024, at 12:00 AM UTC
Root cause: A recent code change for Microsoft Teams has introduced a code error for devices on macOS versions 15 and above that prevents a popup to enable screensharing from being presented to affected users.
Next update by: Tuesday, February 4, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Feb 3 11:08:37 2025 |
|---|
| Description: | Title: Some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X
User impact: Users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
More info: Affected users may utilize the following workaround to re-enable screensharing:
1. Open System Settings
2. Select Privacy & Security
3. Select Screen & System Audio Recording
4. If Microsoft Teams is available on the list of applications, delete it by selecting it and clicking -.
5. Click on + and select Microsoft Teams from the Application folder.
6. Click on Quit & Reopen.
7. Verify Microsoft Teams is enabled in the Screen & System Audio Recording tab.
8. Relaunch Microsoft Teams.
If users are unable to directly grant these permissions, contact your admin to allow you to change screensharing permissions and they will be able to follow the listed guidance.
Current status: We're analyzing reproductions of impact to determine the root cause behind why screensharing permissions are disabled for some users. As we continue to verify the root cause, affected users can utilize the workaround provided in the More info section of communications to resolve the permissions issue.
Scope of impact: Your organization is affected by this event, and some users may be unable to screenshare in Microsoft Teams after upgrading to macOS version 15.X.
Next update by: Monday, February 3, 2025, at 5:30 PM UTC
|
|---|
|
CP979721 - Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 14 17:56:10 2025 |
|---|
| End Time: | Wed Feb 12 17:24:17 2025 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 12 23:53:05 2025 |
|---|
| Root Cause: | An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 12 17:25:08 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users couldn't access the Copilot app in Microsoft Teams classic and received an error.
More info: When users selected the Copilot app from the sidebar in the Microsoft Teams classic, they received an error which stated, "Sorry, we ran into a problem. Please reload or try again later."
Final status: We've completed the deployment of the fix, and we've confirmed this has remediated impact.
Scope of impact: Your organization was affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic was impacted.
Start time: Tuesday, January 14, 2025, at 2:38 PM UTC
End time: Tuesday, February 11, 2025, at 6:20 PM UTC
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic.
Next steps:
- We're reviewing authentication component extension processes to ensure to that similar issues affecting Copilot access in Microsoft Teams are prevented in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 10 17:54:59 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states, "Sorry, we ran into a problem. Please reload or try again later."
Current status: The deployment of the fix is progressing more slowly than expected, though it’s 50 percent complete. We’re now projecting that the impact will be remediated by Wednesday, February 12, 2025.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Start time: Tuesday, January 14, 2025, at 2:38 PM UTC
Estimated time to resolve: We’re expecting that the solution will be fully deployed and impact remediated by Wednesday, February 12, 2025.
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic.
Next update by: Wednesday, February 12, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Feb 5 16:29:27 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states, "Sorry, we ran into a problem. Please reload or try again later."
Current status: We're initiating the deployment of our fix to the affected environment. We expect it will complete deployment, resolving the issue for all impacted users, by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Start time: Tuesday, January 14, 2025, at 5:18 PM UTC
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic.
Next update by: Monday, February 10, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jan 29 17:25:32 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states, "Sorry, we ran into a problem. Please reload or try again later."
Current status: The extension of the organizational eligibility for the Microsoft Teams classic version is requiring more time than originally anticipated. In parallel, we're continuing to confirm if any additional remediation actions are required once our extension is complete. We'll provide an updated timeline for extending the organizational eligibility for the classic version of Microsoft Teams and the remediation of impact once it has become available.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Start time: Tuesday, January 14, 2025, at 5:18 PM UTC
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic.
Next update by: Wednesday, February 5, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Jan 24 16:43:06 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states, "Sorry, we ran into a problem. Please reload or try again later."
Current status: We’re continuing the process of extending the organizational eligibility for Microsoft Teams classic version and validating to ensure that no additional remediation steps will be required to resolve this issue for affected users.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Start time: Tuesday, January 14, 2025, at 5:18 PM UTC
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic.
Next update by: Wednesday, January 29, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jan 22 17:00:37 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states, "Sorry, we ran into a problem. Please reload or try again later."
Current status: The process of extending organizational eligibility for Microsoft Teams classic version is ongoing; however, taking more time than initially expected to complete. We’ll continue monitoring this process with the expectation that it should complete to resolve this issue by Friday, January 24, 2025.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Start time: Tuesday, January 14, 2025, at 5:18 PM UTC
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic.
Next update by: Friday, January 24, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jan 21 12:52:23 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states, "Sorry, we ran into a problem. Please reload or try again later."
Current status: We're continuing to extend organizational eligibility for Microsoft Teams classic version, and we expect that this will complete by our next scheduled update, resolving the issue for all impacted users.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Start time: Tuesday, January 14, 2025, at 5:18 PM UTC
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic.
Next update by: Wednesday, January 22, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Jan 17 13:14:14 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states, "Sorry, we ran into a problem. Please reload or try again later."
Current status: After extensive testing, we've determined that extending organizational eligibility for Microsoft Teams classic is a viable long-term solution, and we're applying that change to all affected organizations. This solution is being progressively deployed to affected organizations, and we anticipate that the problem will be largely remediated by our next scheduled update. In the event the solution is still being applied to affected organizations by our next update, we’ll aim to provide an estimated time to resolve the issue.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Start time: Tuesday, January 14, 2025, at 5:18 PM UTC
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic.
Next update by: Tuesday, January 21, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jan 15 17:41:20 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states the following:
"Sorry, we ran into a problem. Please reload or try again later."
Current status: We’ve determined that an authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic, causing the observed errors and resulting in the impact. We’ve applied a temporary mitigation to some affected users to remediate the impact as we review options to deploy a long-term solution. We anticipate the fix deployment should begin prior to our next update, and we’ll provide the deployment timeline when it's available.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Start time: Tuesday, January 14, 2025, at 5:18 PM UTC
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Microsoft Teams classic.
Next update by: Tuesday, January 21, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jan 15 14:15:46 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states the following:
"Sorry, we ran into a problem. Please reload or try again later."
Current status: We’ve confirmed that extending your organization's eligibility to Microsoft Teams classic has alleviated the impact in the short term as we await the permanent solution. We’ve developed and are reviewing options to deploy the permanent fix and will provide a timeline once it's available.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Start time: Tuesday, January 14, 2025, at 5:18 PM UTC
Root cause: An authentication component that facilitates users' access to the app wasn't extended to Teams classic.
Next update by: Tuesday, January 21, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jan 14 19:52:55 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states the following:
"Sorry, we ran into a problem. Please reload or try again later."
Current status: We've identified that an authentication component that determines users' access to the app wasn't extended to Teams classic. We're extending the eligibility in an effort to alleviate impact and are reaching out to representatives from your organization to validate if this action resolves impact as expected.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Root cause: An authentication component that determines users' access to the app wasn't extended to Teams classic.
Next update by: Wednesday, January 15, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jan 14 18:53:25 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states the following:
"Sorry, we ran into a problem. Please reload or try again later."
Current status: We're reviewing service side logs to isolate any errors that may aid us in locating the source of the impact.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Next update by: Wednesday, January 15, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jan 14 17:59:51 2025 |
|---|
| Description: | Title: Users can't access the Microsoft Copilot (Microsoft 365) app in Microsoft Teams classic and receive an error
User impact: Users can't access the Copilot app in Microsoft Teams classic and receive an error.
More info: When users select the Copilot app from the sidebar in the Microsoft Teams classic, they receive an error which states the following:
"Sorry, we ran into a problem. Please reload or try again later."
Current status: We're reviewing the provided error message to gain clarity on the impact and determine the next steps to isolate the root cause.
Scope of impact: Your organization is affected by this event, and any user attempting access to the Copilot app in Microsoft Teams classic is impacted.
Next update by: Wednesday, January 15, 2025, at 12:00 AM UTC
|
|---|
|
TM962326 - Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 6 14:18:00 2024 |
|---|
| End Time: | Wed Feb 12 15:00:00 2025 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 12 17:25:11 2025 |
|---|
| Root Cause: | A code change, meant to improve the rendering logic, prevented the adaptive card messages from rendering correctly and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 12 17:25:11 2025 |
|---|
| Description: | Title: Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
User impact: Users may have seen adaptive card messages were incorrectly rendering on multiple lines in Microsoft Teams.
More info: If you're using RichTextBlock in your adaptive cards with TextRuns that have their selectAction property set, unwanted line breaks appeared. Your card, however, remained fully functional.
Final status: We've discovered that the adaptive action definition weren't incorrect. Instead, a code change meant to improve rendering logic prevented the adaptive card messages from rendering correctly, resulting in impact. We've deployed the fixed build of Microsoft Teams to the affected environment and users should update Microsoft Teams to the latest version to remediate impact.
Scope of impact: This issue potentially impacted any user that viewed adaptive card messages in any Microsoft Teams connection method.
Start time: Wednesday, November 6, 2024, at 7:18 PM UTC
End time: Wednesday, February 12, 2025, at 8:00 PM UTC
Root cause: A code change, meant to improve the rendering logic, prevented the adaptive card messages from rendering correctly and resulted in impact.
Next steps:
- We're reviewing our code change validation procedure so we can detect and remediate similar code issues prior to deployment and prevent similar issues from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 5 17:02:50 2025 |
|---|
| Description: | Title: Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
User impact: Users may see adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams.
More info: If you're using RichTextBlock in your adaptive cards with TextRuns that have their selectAction property set, unwanted line breaks show up. Your card, however, remains fully functional.
Current status: The deployment of the aforementioned fix is progressing but continuing to take longer than previously anticipated. We're continuing to monitor the deployment and will provide a timeline for remediation as it becomes available.
Scope of impact: This issue can potentially affect any user that's viewing adaptive card messages in any Microsoft Teams connection method.
Start time: Wednesday, November 6, 2024, at 7:18 PM UTC
Root cause: The library used by Microsoft Teams to pull the adaptive card messages has an incorrect action definition, resulting in impact.
Next update by: Wednesday, February 12, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jan 29 17:06:44 2025 |
|---|
| Description: | Title: Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
User impact: Users may see adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams.
More info: If you're using RichTextBlock in your adaptive cards with TextRuns that have their selectAction property set, unwanted line breaks show up. Your card, however, remains fully functional.
Current status: The deployment of the aforementioned fix is taking longer than initially anticipated. We're continuing to monitor the deployment and will provide an updated timeline as one becomes available.
Scope of impact: This issue can potentially affect any user that's viewing adaptive card messages in any Microsoft Teams connection method.
Start time: Wednesday, November 6, 2024, at 7:18 PM UTC
Root cause: The library used by Microsoft Teams to pull the adaptive card messages has an incorrect action definition, resulting in impact.
Next update by: Wednesday, February 5, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jan 22 17:10:14 2025 |
|---|
| Description: | Title: Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
User impact: Users may see adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams.
More info: If you're using RichTextBlock in your adaptive cards with TextRuns that have their selectAction property set, unwanted line breaks show up. Your card, however, remains fully functional.
Current status: While we anticipate that many affected users should see resolution by the end of January 2025, we're continuing to monitor our deployment's progress so we can provide a timeline to full remediation.
Scope of impact: This issue can potentially affect any user that's viewing adaptive card messages in any Microsoft Teams connection method.
Start time: Wednesday, November 6, 2024, at 7:18 PM UTC
Root cause: The library used by Microsoft Teams to pull the adaptive card messages has an incorrect action definition, resulting in impact.
Next update by: Wednesday, January 29, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jan 15 16:52:58 2025 |
|---|
| Description: | Title: Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
User impact: Users may see adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams.
More info: If you're using RichTextBlock in your adaptive cards with TextRuns that have their selectAction property set, unwanted line breaks show up. Your card, however, remains fully functional.
Current status: We've confirmed that the deployment of our fix is underway, and we're monitoring its progress with the aim of providing an estimated remediation timeline once it becomes available.
Scope of impact: This issue can potentially affect any user that's viewing adaptive card messages in any Microsoft Teams connection method.
Start time: Wednesday, November 6, 2024, at 7:18 PM UTC
Root cause: The library used by Microsoft Teams to pull the adaptive card messages has an incorrect action definition, resulting in impact.
Next update by: Wednesday, January 22, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jan 8 16:47:11 2025 |
|---|
| Description: | Title: Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
User impact: Users may see adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams.
More info: If you're using RichTextBlock in your adaptive cards with TextRuns that have their selectAction property set, unwanted line breaks show up. Your card, however, remains fully functional.
Current status: Development of our previously mentioned fix is complete, and we've begun deployment to the impacted service environments. We're aiming to provide a timeline for full deployment and remediation in our next scheduled communications update.
Scope of impact: This issue can potentially affect any user that's viewing adaptive card messages in any Microsoft Teams connection method.
Start time: Wednesday, November 6, 2024, at 7:18 PM UTC
Root cause: The library used by Microsoft Teams to pull the adaptive card messages has an incorrect action definition, resulting in impact.
Next update by: Wednesday, January 15, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Jan 3 11:40:25 2025 |
|---|
| Description: | Title: Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
User impact: Users may see adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams.
More info: If you're using RichTextBlock in your adaptive cards with TextRuns that have their selectAction property set, unwanted line breaks show up. Your card, however, remains fully functional.
Current status: We're continuing to work on the fix and are preparing a new Microsoft Teams build for deployment. A timeline for deployment and resolution will be provided once available.
Scope of impact: This issue can potentially affect any user that's viewing adaptive card messages in any Microsoft Teams connection method.
Root cause: The library used by Microsoft Teams to pull the adaptive card messages has an incorrect action definition, resulting in impact.
Next update by: Wednesday, January 8, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Dec 20 14:56:49 2024 |
|---|
| Description: | Title: Some users may see that adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams
User impact: Users may see adaptive card messages are incorrectly rendering on multiple lines in Microsoft Teams.
More info: If you're using RichTextBlock in your adaptive cards with TextRuns that have their selectAction property set, unwanted line breaks show up. Your card, however, remains fully functional.
Current status: We've discovered the library used by Microsoft Teams to pull the adaptive card messages has an incorrect action definition, resulting in impact once the library version was updated. We've updated the library and are working on a new Microsoft Teams build to deploy this fix in. We expect to have a timeline for deployment by our next scheduled update.
Scope of impact: This issue can potentially affect any user that's viewing adaptive card messages in any Microsoft Teams connection method.
Root cause: The library used by Microsoft Teams to pull the adaptive card messages has an incorrect action definition, resulting in impact.
Next update by: Friday, January 3, 2025, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Dec 20 13:47:38 2024 |
|---|
| Description: | Title: Some users see that the formatting on some messages is incorrect in Microsoft Teams
User impact: Users see that the formatting on some messages is incorrect in Microsoft Teams.
Current status: We're investigating an issue with formatting on Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OP997892 - Some users may have been unable to create or run Office scripts in Excel and Power Automate
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Feb 4 19:30:00 2025 |
|---|
| End Time: | Wed Feb 5 10:23:00 2025 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Feb 12 13:00:01 2025 |
|---|
| Root Cause: | When the Office Script processing service attempted to make an internal service-to-service request to the Directory Service API, it failed with an ‘Invalid Token’ error, resulting in impact. The policy failure occurred during the token validation stages, due to the incoming IP addresses being outside of the expected ranges. This was a transient issue that happened after a recent deployment. The transient issue corrected itself after the same service was removed and redeployed. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 12 12:58:28 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Feb 7 18:32:27 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Feb 5 10:56:29 2025 |
|---|
| Description: | Title: Some users may have been unable to create or run Office scripts in Excel and Power Automate
User impact: Users may have been unable to create or run Office scripts in Excel and Power Automate
More info: Impact occurred in both the Excel web and desktop applications.
Final status: We've rerouted requests to alternate infrastructure, and confirmed that the issue has been remediated after an extended period of monitoring.
Scope of impact: This issue impacted a specific data center within the EMEA region, and could have impacted any requests served through that data center.
Start time: Wednesday, February 5, 2025, at 12:30 AM UTC
End time: Wednesday, February 5, 2025, at 3:23 PM UTC
Root cause: When the Office Script processing service attempted to make an internal service-to-service request to the Directory Service API, it failed with an ‘Invalid Token’ error, resulting in impact. The policy failure occurred during the token validation stages, due to the incoming IP addresses being outside of the expected ranges. This was a transient issue that happened after a recent deployment. The transient issue corrected itself after the same service was removed and redeployed.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary PIR within 2 business days, and a final PIR within 5 business days.
|
|---|
|
| Time: | Wed Feb 5 10:33:51 2025 |
|---|
| Description: | Telemetry shows a reduction in errors on the affected infrastructure as the traffic rerouting process continues. We expect the rerouting to compete within the next 30 minutes.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 5 10:14:45 2025 |
|---|
| Description: | Title: Some users may be unable to create or run Office scripts in Excel and Power Automate
User impact: Users may be unable to create or run Office scripts in Excel and Power Automate
More info: Impact may occur in both the Excel web and desktop applications.
Current status: From the internal reproduction for the issue, we’re continuing to investigate the source of the issue and are specifically focused on Directory services that are generating 403 errors. We’re rerouting requests within our Europe, Middle East, and Africa (EMEA) region to mitigate impact and provide relief.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure. Initial indications are that this is impacting a specific data center within the EMEA region, however, analysis is still ongoing.
Next update by: Wednesday, February 5, 2025, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Feb 5 09:26:28 2025 |
|---|
| Description: | Title: Some users may be unable to create or run Office scripts in Excel
User impact: Users may be unable to create or run Office scripts in Excel.
More info: Impact may occur in both the Excel web and desktop applications.
Current status: We've successfully reproduced the issue internally and collected additional troubleshooting details. We're conducting a review of system logs, telemetry and obtained reproduction data to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Wednesday, February 5, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Feb 5 07:27:03 2025 |
|---|
| Description: | Title: Some users may be unable to create or run Office scripts in Excel
User impact: Users may be unable to create or run Office scripts in Excel.
More info: Impact may occur in both the Excel web and desktop applications.
Current status: We're continuing to review system logs and telemetry to isolate the root cause. In parallel, we're checking to see if any recent updates may be contributing to impact alongside attempting to internally reproduce impact for further troubleshooting details.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Wednesday, February 5, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Feb 5 06:15:52 2025 |
|---|
| Description: | Title: Some users are unable to create or run Excel Automate Office scripts
User impact: Users are unable to create or run Excel Automate Office scripts.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to create or run Excel Automate Office scripts are impacted.
Next update by: Wednesday, February 5, 2025, at 1:30 PM UTC
|
|---|
|
|
