Penn Computing
Computing Menu Computing A-Z
Computing Home Information Systems & Computing Penn

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 Sat Mar 29 03:00:08 2025.

IT1043606 - Admins may see delays with compliance and device configuration reports in the Microsoft Intune admin center

Status:serviceDegradation
Start Time:Fri Mar 28 19:00:00 2025
End Time:N/A
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:advisory
Last Updated:Sat Mar 29 01:35:20 2025
Root Cause:An issue with a portion of infrastructure responsible for processing requests for compliance and device configuration reports is causing delays.
Next Update:Saturday, March 29, 2025, at 9:00 AM UTC

Details

Time:Sat Mar 29 01:29:04 2025
Description:Title: Admins may see delays with compliance and device configuration reports in the Microsoft Intune admin center
User impact: Admins may see delays with compliance and device configuration reports in the Microsoft Intune admin center.
More info: The affected reports could potentially be delayed up to 12 hours.
Current status: We’ve identified an issue with a portion of infrastructure responsible for processing requests for compliance and device configuration reports which is causing delays. We're deploying a fix for the issue and will monitor the reports to ensure this resolves the problem.
Scope of impact: This issue may potentially impact any admins viewing compliance and device configuration reports in the Microsoft Intune admin center.
Start time: Friday, March 28, 2025, at 11:00 PM UTC
Root cause: An issue with a portion of infrastructure responsible for processing requests for compliance and device configuration reports is causing delays.
Next update by: Saturday, March 29, 2025, at 9:00 AM UTC
Time:Sat Mar 29 00:59:21 2025
Description:Title: Admins may see delays with compliance and device configuration reports in the Microsoft Intune admin center
User impact: Admins may see delays with compliance and device configuration reports in the Microsoft Intune admin center.
More info: The affected reports could potentially be delayed up to 12 hours.
Current status: We're investigating a potential issue with Intune and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1043542 - Admins may see delays with multiple Microsoft Copilot (Microsoft 365) related reports in the Microsoft 365 admin center

Status:serviceDegradation
Start Time:Fri Mar 28 23:26:20 2025
End Time:N/A
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Sat Mar 29 00:15:29 2025
Root Cause:An issue with the upstream data source is causing delays with some report data in the Microsoft 365 admin center.
Next Update:Sunday, March 30, 2025, at 5:00 AM UTC

Details

Time:Sat Mar 29 00:15:29 2025
Description:Title: Admins may see delays with multiple Microsoft Copilot (Microsoft 365) related reports in the Microsoft 365 admin center
User impact: Admins may see delays with multiple Copilot related reports in the Microsoft 365 admin center.
More info: The following reports are impacted: -Microsoft 365 Copilot usage report -Microsoft Copilot (Enterprise data protection) usage report -Microsoft 365 Copilot usage report (Graph API) -AI assistance category in Adoption score
Current status: We identified an issue with the upstream data source that is causing delays with some report data in the Microsoft 365 admin center. We're working to repair the issue and will ensure that any delayed report data is backfilled.
Scope of impact: This issue may potentially impact any admin reviewing the affected report data in the Microsoft 365 admin center.
Start time: Saturday, March 29, 2025, at 12:00 AM UTC
Root cause: An issue with the upstream data source is causing delays with some report data in the Microsoft 365 admin center.
Next update by: Sunday, March 30, 2025, at 5:00 AM UTC
Time:Fri Mar 28 23:57:15 2025
Description:Title: Admins may see delays with multiple Microsoft Copilot (Microsoft 365) related reports in the Microsoft 365 admin center
User impact: Admins may see delays with multiple Copilot related reports in the Microsoft 365 admin center.
More info: The following reports are impacted: -Microsoft 365 Copilot usage report -Microsoft Copilot (Enterprise data protection) usage report -Microsoft 365 Copilot usage report (Graph API) -AI assistance category in Adoption score
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.

MO1041132 - Users are unable to use eDiscovery services and features

Status:serviceDegradation
Start Time:Tue Mar 25 14:45:00 2025
End Time:N/A
Service:Microsoft 365 suite
Feature Group:Administration
Classification:incident
Last Updated:Sat Mar 29 00:02:41 2025
Root Cause:N/A
Next Update:Saturday, March 29, 2025, at 11:59 PM UTC

Details

Time:Fri Mar 28 21:54:44 2025
Description:Title: Users are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All users are unable to export search results, or items from a review from eDiscovery.
All users can create a case, search for content, evaluate and refine search results, and use review sets to manage content.
Additionally, existing eDiscovery holds were not impacted by this event and continue to preserve content as configured. However, creating new eDiscovery holds during the impact duration may have failed to complete.
Current Status: We are continuing to make progress on testing in our internal environment. However, out of an abundance of caution, we are conducting extended testing on all critical scenarios. While this thorough validation is delaying our production deployment, it is essential to ensure the export functionality is delivered without issues.
Our engineering team remains fully focused and engaged, and we still anticipate delivering the functionality to production by the end of the day on Saturday, March 29, 2025.
We sincerely appreciate your continued patience and want to assure you that we are taking all necessary actions to restore the remaining critical functionality of our eDiscovery service. We will continue to provide updates as we make progress.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Saturday, March 29, 2025, at 11:59 PM UTC
Time:Fri Mar 28 14:38:04 2025
Description:Title: Users are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All users are unable to export search results, or items from a review from eDiscovery.
All users can create a case, search for content, evaluate and refine search results, and use review sets to manage content.
Current Status: We’ve addressed the previously described challenges we identified during our testing cycle and are proceeding with applying an update intended to comprehensively resolve this issue. This update enables customers to download export search results in both the modern eDiscovery experiences (eDiscovery Standard and eDiscovery Premium) and in the Classic eDiscovery (Premium) experience.
We’re working to complete this process by Saturday, March 29, 2025, at 12:00 AM UTC.
We sincerely appreciate your patience and will continue to share updates as we complete the update application process. We recognize the significant impact this issue is having on your organization, and we remain committed to restoring full functionality as quickly as possible.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Saturday, March 29, 2025, at 2:00 AM UTC
Time:Fri Mar 28 12:02:39 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All users are unable to export search results, or items from a review from eDiscovery.
All users can create a case, search for content, evaluate and refine search results, and use review sets to manage content.
Current Status: We're continuing to work through the issues identified during the validation testing. We're making progress in addressing these challenges, and it is essential for us to thoroughly mitigate each issue to ensure that no additional impact is introduced when the mitigation is applied through the affected environment.
We sincerely appreciate your patience and will continue to share updates as we get closer to finalizing these steps.
Thank you once again for your continued collaboration and understanding as we work diligently to resolve this matter. We recognize the significant impact this issue is having on your organization, and we remain committed to restoring full functionality as quickly as possible.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Friday, March 28, 2025, at 7:00 PM UTC
Time:Fri Mar 28 06:28:14 2025
Description:We're continuing our testing and analysis of the code. Our current ETA to have the mitigation deployed is Friday, March 28, 2025 at 11:00 PM UTC. However, due to the significant complexities involved with these mitigation actions, this estimate may change and we'll update this communication.
This quick update is designed to give the latest information on this issue.
Time:Fri Mar 28 02:10:19 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All users are unable to export search results, or items from a review from eDiscovery.
All users can create a case, search for content, evaluate and refine search results, and use review sets to manage content.
Current Status: We’ve encountered some unexpected results while finalizing our validation tests. These results require additional analysis and follow-up testing to ensure the code will continue through deployment safely and prevent new issues from occurring when deployed. Due to these circumstances and complexity of the unexpected results, we’ve not yet been able to initiate the deployment to production, which we anticipate will take a considerable amount of time to complete. We sincerely appreciate your patience and will continue to share updates as we get closer to finalizing these steps.
Thank you once again for your continued collaboration and understanding as we work diligently to resolve this matter. We recognize the significant impact this issue is having on your organization, and we remain committed to restoring full functionality as quickly as possible.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Friday, March 28, 2025, at 4:00 PM UTC
Time:Fri Mar 28 00:26:31 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All users are unable to export search results, or items from a review from eDiscovery.
All users can create a case, search for content, evaluate and refine search results, and use review sets to manage content.
Current status: We’re making steady progress in our efforts to restore export and search functionality for eDiscovery. We’re refining the current solution and are approaching the validation and deployment phases. We greatly appreciate your patience and understanding as we continue to work towards a resolution for this incident.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Friday, March 28, 2025, at 7:00 AM UTC
Time:Thu Mar 27 20:45:34 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All users are unable to export search results, or items from a review from eDiscovery.
All users can create a case, search for content, evaluate and refine search results, and use review sets to manage content.
Current status: We've restored most functionalities within eDiscovery across commercial and government environments. Users can now create cases, search for content, evaluate and refine search results, and use review sets to manage content. We’re continuing our efforts to restore the ability to export search results and items from a review. Additional time is needed to refine the solution’s contents to optimize performance. Once validation is completed and deemed satisfactory, we will proceed with the deployment.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Friday, March 28, 2025, at 4:30 AM UTC
Time:Thu Mar 27 15:59:32 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All users are unable to export search results, or items from a review from eDiscovery.
All users can create a case, search for content, evaluate and refine search results, and use review sets to manage content.
Current status: We’ve completed deploying the configuration change to the government cloud environments and after a period of monitoring can confirm impact outside of the export scenarios is remediated for all users.
We’re conducting comprehensive testing for our solution to resolve admins’ inability to export search results or export items from a review. We expect we’ll be able to start deploying this update at 1:00 AM UTC. Once deployment starts, we expect full saturation to be completed by Friday, March 28, 2025, at 5:00 PM UTC.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Friday, March 28, 2025, at 1:00 AM UTC
Time:Thu Mar 27 14:29:19 2025
Description:Our deployment of the configuration change to the government cloud environments is proceeding faster than expected and we anticipate government cloud users will now have most eDiscovery functionality restored by 7:00 PM UTC.
Once the deployment is complete, all users will be able to create a case, search for content, evaluate and refine search results, and use review sets to manage content in eDiscovery.
This quick update is designed to give the latest information on this issue.
Time:Thu Mar 27 12:17:36 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All users may be unable to export search results, or items from a review from eDiscovery.
Most users can create a case, search for content, evaluate and refine search results, and use review sets to manage content.
Current status: We previously stated that we restored most of the functionalities within eDiscovery at 10:17 AM UTC. This remains accurate for most users, however, the configuration change has not fully deployed to our government cloud environments, so users within these environments are still experiencing impact. We expect the same eDiscovery functionality to be restored to government cloud users by 8:00 PM UTC.
Additionally, we continue to work on resolving the ability to export search results or export items from a review, and we expect to be able to provide a recovery ETA for standard production environment users by our next update.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Thursday, March 27, 2025, at 8:00 PM UTC
Time:Thu Mar 27 06:17:07 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: Users may be unable to export search results, or items from a review from eDiscovery.
Current status: We've restored most of the functionalities within eDiscovery. Users can now create a case, search for content, evaluate and refine search results, and use review sets to manage content. We're still working on restoring the ability to export search results or export items from a review.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Thursday, March 27, 2025, at 5:00 PM UTC
Time:Thu Mar 27 04:40:20 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All eDiscovery functions are affected by this event.
Current status: We're continuing to restore the eDiscovery functionalities across regions, and are actively making improvements where we can. We understand the impact his has had on your organization, and we appreciate patience as we resolve this incident.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Thursday, March 27, 2025, at 1:00 PM UTC
Time:Thu Mar 27 02:34:43 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All eDiscovery functions are affected by this event.
Current status: We’re currently monitoring the effectiveness of the mitigation strategy and identifying opportunities for optimization. We’ll continue to evaluate service health as adjustments are developed and applied. We know how much impact this has had on your organization, and we sincerely appreciate your patience as we work diligently to resolve this incident.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Thursday, March 27, 2025, at 9:00 AM UTC
Time:Thu Mar 27 01:29:07 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All eDiscovery functions are affected by this event.
Current status: Our implementation to the subset of production has validated our solutions’ effectiveness. We’ll continue applying this mitigation strategy to all affected environments and monitor the service health to ensure no additional impact occurs.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Thursday, March 27, 2025, at 7:00 AM UTC
Time:Wed Mar 26 22:55:48 2025
Description:We’ve deployed the mitigation to our production environment and have a high degree of confidence we’ll see remediation in the coming hours. We’ll continue to monitor and test its effectiveness throughout the saturation process.
This quick update is designed to give the latest information on this issue.
Time:Wed Mar 26 18:43:12 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All eDiscovery functions are affected by this event.
Current status: We've made significant progress in testing and validating our new mitigation strategy. After a thorough evaluation and successful results in our testing environment, we've now expanded the implementation to a subset of our production environment. We'll continue to monitor the progress of our new mitigation strategy closely and share updates as more information becomes available.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Thursday, March 27, 2025, at 5:00 AM UTC
Time:Wed Mar 26 14:42:29 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery.
More info: All eDiscovery functions are affected by this event.
Current status: The configuration change we mentioned in the previous communications did not provide the intended relief. However, alongside application of that configuration change we were also developing a parallel mitigation strategy throughout the event. We’ve made significant progress on testing this new mitigation strategy. Due to the complexity of the strategy, we estimate another three hours of testing is required. Once we've verified that strategy is a comprehensive solution, we'll establish a rollout timeline and will proceed with applying the needed updates to the production environment.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Wednesday, March 26, 2025, at 11:00 PM UTC
Time:Wed Mar 26 08:55:43 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery
More info: All eDiscovery functions are affected by this event.
Current status: We’re actively monitoring the progress of the configuration change, which is taking longer than initially anticipated. Based on our current progress, we expect this process will be completed by our next scheduled update. In addition, we’re exploring if further actions are required to mitigate the impact.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 7:00 PM UTC
Time:Wed Mar 26 03:56:17 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery
More info: All eDiscovery functions are affected by this event.
Current status: We’re continuing to monitor the progress of the configuration change, which is taking longer than we originally expected. We’ll provide an estimated timeline by our next scheduled update.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 1:00 PM UTC
Time:Tue Mar 25 23:52:24 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery
More info: All eDiscovery functions are affected by this event.
Current status: We're continuing to follow our safe change management processes to apply the configuration change. Based on our current progress, we expect this this process will be completed by Wednesday, March 26, 2025, at approximately 8:00 AM UTC.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 8:00 AM UTC
Time:Tue Mar 25 19:39:04 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery
More info: All eDiscovery functions are affected by this event.
Current status: We’ve determined that safely applying our configuration change will take additional time to complete. We project that we’ll complete this process and will fully remediate impact on Wednesday, March 26, 2025 at approximately 4:00 AM UTC.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery are affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 4:00 AM UTC
Time:Tue Mar 25 17:58:11 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery
More info: All eDiscovery functions are affected by this event.
Current status: We’re performing a targeted configuration change to remediate impact. We expect that completing this action and fully restoring the availability of eDiscovery services and features will take approximately three hours to complete.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery may be affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 1:00 AM UTC
Time:Tue Mar 25 15:59:24 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery
More info: All eDiscovery functions are affected by this event.
Current status: We’re analyzing the collected data and the available telemetry as we work toward a comprehensive remediation strategy.
Scope of impact: Any user or admin attempting to perform actions through eDiscovery may be affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Tuesday, March 25, 2025, at 10:00 PM UTC
Time:Tue Mar 25 14:53:56 2025
Description:Title: Users and admins are unable to use eDiscovery services and features
User impact: Users are unable to use eDiscovery services and features in Purview eDiscovery
More info: All eDiscovery functions are affected by this event.
Current status: We’ve identified an issue affecting eDiscovery functionality and are gathering information to further our investigation.
Scope of impact: Any user or admin attempting to perform actions via eDiscovery may be affected.
Next update: Tuesday, March 25, 2025 at 8:00 PM UTC

EX1041375 - Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web

Status:serviceRestored
Start Time:Tue Feb 11 11:00:00 2025
End Time:Thu Mar 27 21:00:00 2025
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:incident
Last Updated:Fri Mar 28 23:21:53 2025
Root Cause:A recent service update, intended to improve code manageability and future feature development, was inadvertently causing impact.
Next Update:N/A

Details

Time:Fri Mar 28 23:21:39 2025
Description:Title: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web
User impact: Users may have been unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web.
Title: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web
User impact: Users may have been unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web.
More info: Users may have seen the following error message when attempting to open PDF attachments in Outlook on the web, "Your message can't be displayed right now."
Final status: We’ve validated that the aforementioned fix has saturated throughout the affected infrastructure and remediated the issue.
Scope of impact: Any user who tried to open PDF attachments in any shared mailbox in Outlook on the web may have been impacted.
Start time: Tuesday, February 11, 2025, at 4:00 PM UTC
End time: Friday, March 28, 2025, at 1:00 AM UTC
Root cause: A recent service update, intended to improve code manageability and future feature development, was inadvertently causing 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:Fri Mar 28 11:36:17 2025
Description:Title: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web
User impact: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web.
More info: Users may see the following error message when attempting to open PDF attachments in Outlook on the web, "Your message can't be displayed right now."
Users may be able to open PDF attachments in other Exchange Online clients to avoid the issue.
Current status: The fix has completed deployment and we're awaiting confirmation from a subset of affected users that this has remediated impact.
Scope of impact: Any user trying to open PDF attachments in any shared mailbox in Outlook on the web may be impacted.
Start time: Tuesday, February 11, 2025, at 4:00 PM UTC
Root cause: A recent service update, intended to improve code manageability and future feature development, is inadvertently causing impact.
Next update by: Saturday, March 29, 2025, at 4:00 AM UTC
Time:Fri Mar 28 04:55:33 2025
Description:Title: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web
User impact: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web.
More info: Users may see the following error message when attempting to open PDF attachments in Outlook on the web, "Your message can't be displayed right now."
Users may be able to open PDF attachments in other Exchange Online clients to avoid the issue.
Current status: We've identified that a recent service update, intended to improve code manageability and future feature development, is inadvertently causing impact. We've developed and have begun deploying a fix to remediate impact.
Scope of impact: Any user trying to open PDF attachments in any shared mailbox in Outlook on the web may be impacted.
Start time: Tuesday, February 11, 2025, at 4:00 PM UTC
Root cause: A recent service update, intended to improve code manageability and future feature development, is inadvertently causing impact.
Next update by: Friday, March 28, 2025, at 4:00 PM UTC
Time:Thu Mar 27 04:47:17 2025
Description:Title: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web
User impact: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web.
More info: Users see the following error message when attempting to open PDF attachments in Outlook on the web, "Your message can't be displayed right now."
Users can open PDF attachments in other Exchange Online clients to avoid the issue.
Current status: We're continuing to work with some affected users to determine whether an already developed fix can address this problem and fully resolve impact.
Scope of impact: Any user trying to open PDF attachments in any shared mailbox in Outlook on the web may be impacted.
Next update by: Friday, March 28, 2025, at 9:00 AM UTC
Time:Wed Mar 26 13:48:36 2025
Description:Title: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web
User impact: Users may be unable to view email content when opening PDF attachments in shared mailboxes in Outlook on the web.
More info: Users see the following error message when attempting to open PDF attachments in Outlook on the web, "Your message can't be displayed right now."
Users can open PDF attachments in other Exchange Online clients to avoid the issue.
Current status: We suspect this issue is impacting any user with specific layout settings. Specifically, users that have their layout settings set to Text Size and Spacing "small", and the Message Organization set to "group messages by conversation" and "all messages from the selected conversation" to be visible in the reading pane. We’re working with some affected users to confirm our findings and determine whether a fix that’s already been developed to address this problem will fully resolve the issue.
Scope of impact: Any user trying to open PDF attachments in any shared mailbox in Outlook on the web may be impacted.
Next update by: Thursday, March 27, 2025, at 9:00 AM UTC
Time:Wed Mar 26 00:17:43 2025
Description:Title: Users can't view email content when opening PDF attachments in shared mailboxes in Outlook on the web
User impact: Users can't view email content when opening PDF attachments in shared mailboxes in Outlook on the web.
More info: Users see the following error message when attempting to open PDF attachments in Outlook on the web, "Your message can't be displayed right now."
Users can open PDF attachments in other Exchange Online clients to avoid the issue.
Current status: We've received additional information regarding the user impact scenario, and edited the statement to accurately reflect the impact users are facing. Additionally, we're continuing to analyze the HAR files to help with isolating the root cause of the issue.
Scope of impact: Your organization is affected by this event, and any user trying to open PDF attachments in any shared mailbox in Outlook on the web are impacted.
Next update by: Wednesday, March 26, 2025, at 6:00 PM UTC
Time:Tue Mar 25 23:27:12 2025
Description:Title: Users can't view email content when opening email attachments in specific shared mailboxes in Exchange Online
User impact: Users can't view email content when opening email attachments in specific shared mailboxes in Exchange Online.
More info: Users see the following error message when attempting to open email attachments, "Your message can't be displayed right now."
Current status: We're analyzing HTTP Archive format (HAR) files to help with the investigation and determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and any user trying to open attachments in specific shared mailboxes are impacted.
Next update by: Wednesday, March 26, 2025, at 4:30 AM UTC
Time:Tue Mar 25 23:10:39 2025
Description:Title: Users can't view email content when clicking email attachments in specific shared mailboxes in Exchange Online
User impact: Users can't view email content when clicking email attachments in specific shared mailboxes 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.

TM1043316 - Users' Notes tabs in Microsoft Teams channels may not open the OneNote notebook or direct to the incorrect section

Status:serviceDegradation
Start Time:Fri Mar 21 11:08:00 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Mar 28 19:30:46 2025
Root Cause:A recently deployed update, designed to update URL handling of OneNote notebooks in Microsoft Teams, introduced a regression that's causing impact
Next Update:Saturday, March 29, 2025, at 5:00 PM UTC

Details

Time:Fri Mar 28 19:30:46 2025
Description:Title: Users' Notes tabs in Microsoft Teams channels may not open the OneNote notebook or direct to the incorrect section
User impact: Users' Notes tabs in Microsoft Teams channels may not open the OneNote notebook or direct to the incorrect section.
More info: When users click on the Notes tab in a Microsoft Teams channel, they may receive an error that states: "There was a problem reaching this app." When users retry, they may be redirected to an unexpected location within the OneNote notebook they’re accessing.
Current status: The deployment of the fix is underway and we're monitoring its progress to the affected environment. We anticipate that the majority of the deployment will have completed by our next scheduled update time.
Scope of impact: Any users attempting to access the Notes tab in Microsoft Teams channels may be impacted.
Start time: Friday, March 21, 2025, at 3:08 PM UTC
Root cause: A recently deployed update, designed to update URL handling of OneNote notebooks in Microsoft Teams, introduced a regression that's causing impact
Next update by: Saturday, March 29, 2025, at 5:00 PM UTC
Time:Fri Mar 28 16:24:18 2025
Description:Title: Users' Notes tabs in Microsoft Teams channels may not open the OneNote notebook or direct to the incorrect section
User impact: Users' Notes tabs in Microsoft Teams channels may not open the OneNote notebook or direct to the incorrect section.
More info: When users click on the Notes tab in a Microsoft Teams channel, they may receive an error that states: "There was a problem reaching this app." When users retry, they may be redirected to an unexpected location within the OneNote notebook they’re accessing.
Current status: We've identified a recently deployed update that was designed to update URL handling of OneNote notebooks within Microsoft Teams introduced a regression that's causing impact. We've begun deployment of a fix to correct the regression and remediate the impact and we’ll provide a progress update on the fix, and an estimated time to address the issue should it be available, by our next scheduled update.
Scope of impact: Any users attempting to access the Notes tab in Microsoft Teams channels may be impacted.
Start time: Friday, March 21, 2025, at 3:08 PM UTC
Root cause: A recently deployed update, designed to update URL handling of OneNote notebooks in Microsoft Teams, introduced a regression that's causing impact
Next update by: Saturday, March 29, 2025, at 1:00 AM UTC
Time:Fri Mar 28 15:47:24 2025
Description:Title: Users' Notes tabs in Microsoft Teams channels may not open the OneNote notebook or direct to the incorrect portion
User impact: Users' Notes tabs in Microsoft Teams channels may not open the OneNote notebook or direct to the incorrect portion.
More info: When users click on the Notes tab in a Microsoft Teams channel, they may receive an error that states: "There was a problem reaching this app." When the users retry, they may be redirected to the unexpected location within the OneNote notebook they are accessing.
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.

MO1040235 - Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services

Status:serviceDegradation
Start Time:Mon Mar 24 11:19:13 2025
End Time:N/A
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Fri Mar 28 16:56:41 2025
Root Cause:N/A
Next Update:Tuesday, April 1, 2025, at 10:00 PM UTC

Details

Time:Fri Mar 28 16:45:08 2025
Description:Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following: - Outlook on the web - Microsoft Teams web client - SharePoint Online web client - Microsoft Word web client - Myaccount.microsoft.com
While we work to resolve impact, affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact. Listed below is documentation on how to change your time zone in Microsoft 365: https://support.microsoft.com/en-us/topic/change-your-display-language-and-time-zone-in-microsoft-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: The patch deployment is taking longer than initially expected to complete. We're continuing to monitor the deployment as it progresses and we'll provide a timeline if one becomes available.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Tuesday, April 1, 2025, at 10:00 PM UTC
Time:Mon Mar 24 17:51:30 2025
Description:Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following: - Outlook on the web - Microsoft Teams web client - SharePoint Online web client - Microsoft Word web client - Myaccount.microsoft.com
While we work to resolve impact, affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact. Listed below is documentation on how to change your time zone in Microsoft 365: https://support.microsoft.com/en-us/topic/change-your-display-language-and-time-zone-in-microsoft-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: We’ve determined that a nation-wide decision regarding the time zone was implemented and the patch to accommodate this change, while being deployed, hasn’t completed its deployment to align with this change. We’re monitoring the ongoing deployment of the patch to address this issue and expect that it should complete to resolve this problem by our next update.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Friday, March 28, 2025, at 10:00 PM UTC
Time:Mon Mar 24 14:17:06 2025
Description:Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following: - Outlook on the web - Microsoft Teams web client - SharePoint Online web client - Microsoft Word web client - Myaccount.microsoft.com
While we work to resolve impact, affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact. Listed below is documentation on how to change your time zone in Microsoft 365: https://support.microsoft.com/en-us/topic/change-your-display-language-and-time-zone-in-microsoft-365-for-business-6f238bff-5252-441e-b32b-655d5d85d15b
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: We're continuing to analyze the impact scenario to better understand the underlying issue. We’re also reviewing recent updates to Microsoft 365 to verify if impact could be caused by a recent update or change. In addition, we’ve verified that affected users can set their time zone to (UTC-03:00) Brasilia to bypass impact and we've provided documentation in the "More info" section of this communication on how to change your time zone in Microsoft 365.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Monday, March 24, 2025, at 10:00 PM UTC
Time:Mon Mar 24 12:21:49 2025
Description:Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected Office 365 web apps may include the following: - Outlook on the web - Microsoft Teams web client - SharePoint Online web client - Microsoft Word web client - Myaccount.microsoft.com
Users located in Paraguay maye see their time as one hour ahead of the current time. While we’re focused on remediation, users that have access to the affected services’ desktop apps can use these to bypass the impact.
Current status: We're reviewing support case information to better understand the underlying impact scenario along with reviewing recent updates to the Microsoft 365 suite to verify if impact could be caused by a recent update or change.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Monday, March 24, 2025, at 6:30 PM UTC
Time:Mon Mar 24 11:20:04 2025
Description:Title: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services
User impact: Users in Paraguay may see an incorrect time in multiple Microsoft 365 apps and services.
More info: Affected apps may include the following: - Outlook on the web - Microsoft Teams web client
Users located in Paraguay may see their time as one hour ahead of the current time.
Current status: We've received reports from multiple users in Paraguay that users see an incorrect time in multiple Microsoft 365 apps and services. We're validating with affected users the list of apps affected to better understand the underlying root cause and what steps we can take to resolve impact as swiftly as possible.
Scope of impact: Users in Paraguay may see an incorrect time that’s one hour ahead of the current time in multiple Microsoft 365 apps and services.
Next update by: Monday, March 24, 2025, at 4:30 PM UTC

TM1000103 - Admins may be unable to enable the function to block external users in the Microsoft Teams admin center

Status:serviceRestored
Start Time:Wed Jan 29 10:11:00 2025
End Time:Fri Mar 28 14:45:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Mar 28 16:22:41 2025
Root Cause:The update to the Microsoft Teams service that introduced the function to block external users contained an error that was leading to impact.
Next Update:N/A

Details

Time:Fri Mar 28 14:59:53 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 have been unable to enable the function to block external users in the Microsoft Teams admin center.
More info: While the function appeared to be enabled, there was no actual effect, and users couldn't be added to the block list.
Final status: We've completed the deployment of our solution to the affected environments and after monitoring the service, we've verified the issue is now resolved.
Scope of impact: Impact may have occurred for any admin that enabled the function to block external users in the Microsoft Teams admin center.
Start time: Wednesday, January 29, 2025, at 3:11 PM UTC
End time: Friday, March 28, 2025, at 6:45 PM UTC
Root cause: The update to the Microsoft Teams service that introduced the function to block external users contained an error that was leading to impact.
Next steps: - We're investigating how the update to the Microsoft Teams service that introduced the function to block external users contained an error that was leading to impact to prevent this problem from happening again.
This is the final update for the event.
Time:Fri Mar 28 06:04: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: The deployment is in the final stages, and we expect to complete full deployment within the next 12 hours.
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: Friday, March 28, 2025, at 7:00 PM UTC
Time:Thu Mar 20 06:57:40 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 experiencing some unexpected delays, we're continuing to monitor the deployment and predict it will be complete 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: Friday, March 28, 2025, at 11:00 AM UTC
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.

TM1009881 - Admins’ block user policies created in the Microsoft Teams admin center or PowerShell may not be blocking users

Status:serviceRestored
Start Time:Fri Feb 7 20:15:00 2025
End Time:Fri Mar 28 14:45:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Mar 28 16:01:55 2025
Root Cause:A code issue present in the feature update was preventing admins' policies from blocking users, resulting in impact.
Next Update:N/A

Details

Time:Fri Mar 28 14:59:21 2025
Description:Title: Admins’ block user policies created in the Microsoft Teams admin center or PowerShell may not be blocking users
User impact: Admins’ block user policies in the Microsoft Teams admin center or PowerShell may not have blocked users.
Final status: Our fix to re-enable the User Block feature has completed deployment, and we’ve successfully restored the feature for all affected admins. This has fully remediated impact and resolved the issue.
Scope of impact: Any admin attempting to create a policy in the Microsoft Teams admin center or PowerShell that blocks users may have been impacted.
Start time: Saturday, February 8, 2025, at 1:15 AM UTC
End time: Friday, March 28, 2025, at 6:45 PM UTC
Root cause: A code issue present in the feature update was preventing admins' policies from blocking users, resulting in impact.
Next steps: - We're investigating how the code issue present in the feature update was preventing admins' policies from blocking users, resulting in impact to prevent this problem from happening again.
This is the final update for the event.
Time:Thu Mar 20 13:37:06 2025
Description:Title: Admins’ block user policies created in the Microsoft Teams admin center or PowerShell may not be blocking users
User impact: Admins’ block user policies in the Microsoft Teams admin center or PowerShell may not have blocked users.
Current status: We've completed the deployment of a fix to the permission service which will remediate impact for admins' block user policies created prior to our disabling of the User Block feature. Our fix deployment to correct the code issue, allowing us to then re-enable the User Block feature, has been initiated. We anticipate it will complete by our next scheduled update, at which time we'll re-enable the User Block feature to remediate impact for all affected admins.
Scope of impact: Any admin attempting to create a policy in the Microsoft Teams admin center or PowerShell that blocks users may be 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: Friday, March 28, 2025, at 7:00 PM UTC
Time:Mon Mar 17 13:31:00 2025
Description:Title: Admins’ block user policies created in the Microsoft Teams admin center or PowerShell may not be blocking users
User impact: Admins’ block user policies in the Microsoft Teams admin center or PowerShell may not have blocked users.
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 may be 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 may not be blocking users
User impact: Admins’ block user policies in the Microsoft Teams admin center or PowerShell may not have blocked users.
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 may be 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 users may be 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

PP1043225 - Copilot Studio - Agents using a public website as a knowledge source may not respond or provide an incorrect response

Status:serviceRestored
Start Time:Wed Mar 19 20:00:00 2025
End Time:Fri Mar 28 15:20:00 2025
Service:Power Platform
Feature Group:Other
Classification:advisory
Last Updated:Fri Mar 28 15:42:28 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Fri Mar 28 15:42:15 2025
Description:Title: Microsoft Copilot Studio - Agents using a public website as a knowledge source may not respond or provide an incorrect response
User impact: Agents using a public website as a knowledge source may not have responded or provided an incorrect response.
Final Status: We have completed the deployment of the hotfix. Following a period of monitoring, we confirmed that functionality for agents using a public website as a knowledge source has been restored.
This is the final update on the incident.
Preliminary Root Cause: A recent configuration change introduced a regression within the underlying service infrastructure supporting the Bing API, impacting knowledge source request results returned from public websites.
Next Steps: We're reviewing our configuration procedures to find ways to prevent this problem from happening again.
Time:Fri Mar 28 14:51:27 2025
Description:Title: Microsoft Copilot Studio - Agents using a public website as a knowledge source may not respond or provide an incorrect response
User impact: Agents using a public website as a knowledge source may not respond or provide an incorrect response.
Current Status: We are continuing to deploy the hotfix to the affected portion of service infrastructure.
Next Update: Friday, March 28, 2025, at 10:00 PM UTC
Time:Fri Mar 28 13:17:59 2025
Description:Title: Microsoft Copilot Studio - Agents using a public website as a knowledge source may not respond or provide an incorrect response
User impact: Agents using a public website as a knowledge source may not respond or provide an incorrect response.
Current Status: We determined that a recent configuration change introduced a regression within the underlying service infrastructure supporting the Bing API, impacting knowledge source request results returned from public websites. We have developed and deployed a hotfix to the affected portion of infrastructure to mitigate this issue, and are monitoring service health to confirm recovery.
Next Update: Friday, March 28, 2025, at 7:00 PM UTC
Time:Fri Mar 28 12:55:44 2025
Description:Title: Microsoft Copilot Studio - Agents using a public website as a knowledge source may not respond or provide an incorrect response
User impact: Agents using a public website as a knowledge source may not respond or provide an incorrect response.
Current Status: We are aware of an emerging issue where Copilot agents that use a public website as a knowledge source may not respond or provide an incorrect response. 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.

MP1005102 - Admins may be unable to export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)

Status:serviceRestored
Start Time:Thu Jan 2 14:26:00 2025
End Time:Fri Mar 28 14:00:00 2025
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:advisory
Last Updated:Fri Mar 28 14:17:51 2025
Root Cause:A build update intended to adjust how we set the value for .zip file headers larger than 4GB introduced a bug in how the file headers were handled, resulting in impact.
Next Update:N/A

Details

Time:Fri Mar 28 14:17:51 2025
Description:Title: Admins may be unable to export data from Microsoft Purview eDiscovery (Classic) or eDiscovery (Preview)
User impact: Admins may have been unable to export data from eDiscovery (Classic) or eDiscovery (Preview).
More info: Exports were performed from the Microsoft Purview compliance portal. Admins saw that eDiscovery (Preview) was exporting corrupted .zip files, and exports were failing in eDiscovery (Classic). While we worked to remediate impact, we recommended affected admins attempt the following to work around this impact.
1. Attempt to re-run the job. This condition didn't happen for each export attempt. Please rerun the job as a first step. 2. We recommended you start with batches 3GB or below. If the export was 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 issues persist, please open a support case.
Final status: We've confirmed that a build update intended to adjust how we set the value for .zip file headers larger than 4GB introduced a bug in how the file headers were handled, resulting in impact. Our previous fix deployment, which increased the allowed file size for exports, was successfully validated in our internal environment and with a subset of affected users, confirming the issue was successfully remediated.
Scope of impact: Any admin exporting data from eDiscovery may have been affected.
Start time: Thursday, January 2, 2025, at 7:26 PM UTC
End time: Monday, February 24, 2025, at 6:00 PM UTC
Root cause: A build update intended to adjust how we set the value for .zip file headers larger than 4GB introduced a bug in how the file headers were handled, resulting in impact.
Next steps: - We're investigating how the impacting bug was missed during 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 28 13:45:58 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: After analyzing additional logs, we've confirmed that our previously deployed fix to increase the allowed size of exported data did successfully resolve the issue. We're confirming further details regarding the root cause of impact in addition to impact timelines to provide in our closure summary.
Scope of impact: Any admin exporting data from eDiscovery may be affected.
Next update by: Friday, March 28, 2025, at 8:00 PM UTC
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.

MO1042719 - Users see the Threat analytics page crash within the Microsoft Defender XDR service

Status:serviceRestored
Start Time:Wed Mar 19 09:05:00 2025
End Time:Fri Mar 28 02:30:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Fri Mar 28 11:26:39 2025
Root Cause:A recent service update to a portion of the Microsoft Defender XDR service infrastructure contained a code misconfiguration, resulting in impact.
Next Update:N/A

Details

Time:Fri Mar 28 11:25:49 2025
Description:Title: Users see the Threat analytics page crash within the Microsoft Defender XDR service
User impact: Users saw the Threat analytics page crash within the Microsoft Defender XDR service.
Final status: We've deployed the solution to the affected environments and after monitoring the service, we've verified that that the issue is now successfully resolved.
Scope of impact: Your organization was affected by this event, and all users who utilized the Threat analytics page within the Microsoft Defender XDR service were impacted.
Start time: Wednesday, March 19, 2025, at 1:05 PM UTC
End time: Friday, March 28, 2025, at 6:30 AM UTC
Root cause: A recent service update to a portion of the Microsoft Defender XDR service infrastructure contained a code misconfiguration, resulting in impact.
Next steps: - We're investigating how the recent service update to a portion of the Microsoft Defender XDR service infrastructure contained a code misconfiguration to prevent this problem from happening again.
This is the final update for the event.
Time:Thu Mar 27 21:31:22 2025
Description:Title: Users see the Threat analytics page crash within the Microsoft Defender XDR service
User impact: Users see the Threat analytics page crash within the Microsoft Defender XDR service.
Current status: There are delays with the deployment of the fix to address the code misconfiguration, which we're correcting. After those steps are completed, we'll initiate the fix deployment and provide an update on the expected timeline once one is available.
Scope of impact: Your organization is affected by this event, and all users who utilize the Threat analytics page within the Microsoft Defender XDR service are impacted.
Start time: Wednesday, March 19, 2025, at 1:05 PM UTC
Root cause: A recent service update to a portion of the Microsoft Defender XDR service infrastructure contains a code misconfiguration, resulting in impact.
Next update by: Friday, March 28, 2025, at 5:00 PM UTC
Time:Thu Mar 27 19:58:08 2025
Description:Title: Users see the Threat analytics page crash within the Microsoft Defender XDR service
User impact: Users see the Threat analytics page crash within the Microsoft Defender XDR service.
Current status: We're working to start the deployment process of the fix to address the code misconfiguration and resolve impact. We'll provide an estimated timeline once one begins available.
Scope of impact: Your organization is affected by this event, and all users who utilize the Threat analytics page within the Microsoft Defender XDR service are impacted.
Start time: Wednesday, March 19, 2025, at 1:05 PM UTC
Root cause: A recent service update to a portion of the Microsoft Defender XDR service infrastructure contains a code misconfiguration, resulting in impact.
Next update by: Friday, March 28, 2025, at 3:00 AM UTC
Time:Thu Mar 27 18:11:09 2025
Description:Title: Users see the Threat analytics page crash within the Microsoft Defender XDR service
User impact: Users see the Threat analytics page crash within the Microsoft Defender XDR service.
Current status: We've identified that a recent service update to a portion of the Microsoft Defender XDR service infrastructure contains a code misconfiguration, resulting in impact. We've developed and validated a fix to address the code misconfiguration which we're preparing to deploy to the affected infrastructure. We'll aim to provide a timeline for the deployment to begin by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and all users who utilize the Threat analytics page within the Microsoft Defender XDR service are impacted.
Start time: Wednesday, March 19, 2025, at 1:05 PM UTC
Root cause: A recent service update to a portion of the Microsoft Defender XDR service infrastructure contains a code misconfiguration, resulting in impact.
Next update by: Friday, March 28, 2025, at 1:30 AM UTC
Time:Thu Mar 27 17:57:37 2025
Description:Title: Users see the Threat analytics page crash within the Microsoft Defender XDR service
User impact: Users see the Threat analytics page crash within the Microsoft Defender XDR service.
Current status: We're investigating a potential issue with users seeing the Threat analytics page crash within the Microsoft Defender XDR service. and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1040692 - Admins may see higher than actual active user numbers in the Microsoft Copilot (Microsoft 365) usage report

Status:serviceDegradation
Start Time:Tue Mar 25 00:15:03 2025
End Time:N/A
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Fri Mar 28 05:50:27 2025
Root Cause:A logic configuration issue with our service telemetry is causing some non-user actions to be added to the metric for Copilot active user numbers, causing inaccuracies in the Copilot usage reports.
Next Update:Monday, April 7, 2025, at 10:00 AM UTC

Details

Time:Fri Mar 28 05:50:27 2025
Description:Title: Admins may see higher than actual active user numbers in the Microsoft Copilot (Microsoft 365) usage report
User impact: Admins may see higher than actual active user numbers in the Copilot usage report.
More info: This issue affects the Copilot usage report in the Microsoft 365 admin center. Admins may see higher than expected numbers for: - Outlook Copilot active users count - Any app Copilot active users count - Last activity date - Last activity date of Outlook Copilot
Current status: We've implemented the fix to update the telemetry and are now awaiting for the report data to backfill. We anticipate impact will be fully resolved by our next scheduled update.
Scope of impact: This issue may potentially affect any admin viewing the Copilot usage report in the Microsoft 365 admin center.
Start time: Friday, January 31, 2025, at 12:00 AM UTC
Root cause: A logic configuration issue with our service telemetry is causing some non-user actions to be added to the metric for Copilot active user numbers, causing inaccuracies in the Copilot usage reports.
Next update by: Monday, April 7, 2025, at 10:00 AM UTC
Time:Tue Mar 25 00:35:16 2025
Description:Title: Admins may see higher than actual active user numbers in the Microsoft Copilot (Microsoft 365) usage report
User impact: Admins may see higher than actual active user numbers in the Copilot usage report.
More info: This issue affects the Copilot usage report in the Microsoft 365 admin center. Admins may see higher than expected numbers for: -Outlook Copilot active users count -Any app Copilot active users count
In addition, admins may see more recent dates than the selected time period they are expected for: -Last activity date -Last activity date of Outlook Copilot
Current status: We identified a logic configuration issue with our service telemetry that is causing inaccuracies in the Microsoft 365 usage report. We're working on a fix to update the telemetry and remediate impact.
Scope of impact: This issue may potentially affect any admin viewing the Copilot usage report in the Microsoft 365 admin center.
Start time: Friday, January 31, 2025, at 12:00 AM UTC
Root cause: A logic configuration issue with our service telemetry is causing some non-user actions to be added to the metric for Copilot active user numbers, causing inaccuracies in the Copilot usage reports.
Next update by: Friday, March 28, 2025, at 10:00 AM UTC
Time:Tue Mar 25 00:15:55 2025
Description:Title: Admins may see higher than actual active user numbers in the Microsoft Copilot (Microsoft 365) usage report
User impact: Admins may see higher than actual active user numbers in the Copilot usage report.
More info: This issue affects the Copilot usage report in the Microsoft 365 admin center. Admins may see higher than expected numbers for: -Outlook Copilot active users count -Any app Copilot active users count -Last activity date -Last activity date of Outlook Copilot
Current status: We're investigating a potential issue with the Microsoft 365 admin center and are checking for impact to your organization. We'll provide an update within 30 minutes.

MO1042853 - Users may be visiting legacy content at the MicrosoftStream.com domain

Status:serviceDegradation
Start Time:Thu Mar 27 19:16:15 2025
End Time:N/A
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Fri Mar 28 00:27:01 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Thu Mar 27 23:31:10 2025
Description:Title: Users may be visiting legacy content at the MicrosoftStream.com domain
User impact: Users may be visiting legacy content at the MicrosoftStream.com domain.
As we have communicated previously Microsoft Stream (Classic) was retired in 2024 and as of March 2025, MicrosoftStream.com address no longer redirects users to their videos. We have noticed that some of your users are still accessing this address.
Going forward, users who visit MicrosoftStream.com will be redirected to the new combined landing page for Clipchamp and Stream. This new platform offers enhanced features and a more integrated experience for video creation and management.
We encourage you to tell your users to update their bookmarks and explore the new Clipchamp/Stream landing page and take advantage of its improved functionalities.
This communication will expire in fourteen days and is scheduled to remain active for the full duration.

TM1040294 - Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings

Status:serviceDegradation
Start Time:Mon Mar 24 12:38:38 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu Mar 27 15:06:07 2025
Root Cause:A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next Update:Monday, March 31, 2025, at 11:00 PM UTC

Details

Time:Wed Mar 26 16:37:58 2025
Description:Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating "invalid image size" and the upload fails. Users can avoid this issue by resizing the desired image to below the aforementioned dimensions.
Current status: Our fix to revert the strict size check logic has been validated and we're expecting deployment to start by Monday, March 31, 2025, which is when we anticipate providing an updated timeline for impact remediation.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Monday, March 31, 2025, at 11:00 PM UTC
Time:Tue Mar 25 17:17:10 2025
Description:Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating ""invalid image size" and the upload fails.
Current status: We're completing the final testing and validations of our fix before initiating its deployment. We expect to provide a timeline for the fix deployment with our next scheduled update.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Wednesday, March 26, 2025, at 11:00 PM UTC
Time:Mon Mar 24 17:48:04 2025
Description:Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating ""invalid image size" and the upload fails.
Current status: We've developed a fix for the solution to remove the restriction on background image size in order to remediate impact for all users. We're working to confirm a timeline for our fix deployment to provide with our next scheduled update.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Start time: Tuesday, March 18, 2025, at 2:13 AM UTC
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Tuesday, March 25, 2025, at 11:00 PM UTC
Time:Mon Mar 24 15:52:14 2025
Description:Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
More info: When attempting to upload a background image larger than 1800x1800, users receive an error message stating ""invalid image size" and the upload fails.
Current status: We've identified a recent change instituted a restriction on image size for background image uploads in Microsoft Teams. While we work towards developing a fix for the issue, impacted users can manually resize their background images to "1800x1800" height and width dimensions, or smaller, for the upload to complete successfully.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Root cause: A recent change instituted a restriction on image size for background image uploads in Microsoft Teams.
Next update by: Monday, March 24, 2025, at 10:00 PM UTC
Time:Mon Mar 24 13:36:42 2025
Description:Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
Current status: We're reviewing user reports of the problem while collecting internal service data for this scenario to isolate what may be causing the impact.
Scope of impact: This issue may affect any user attempting to upload a background image larger than 1800x1800 during any Microsoft Teams meeting.
Next update by: Monday, March 24, 2025, at 8:00 PM UTC
Time:Mon Mar 24 12:38:39 2025
Description:Title: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings
User impact: Users may be unable to upload background images larger than 1800x1800 during Microsoft Teams meetings.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.

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:Thu Mar 27 13:46:40 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:Monday, March 31, 2025, at 6:30 PM UTC

Details

Time:Thu Mar 27 13:46:40 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: Our operation to validate the previously mentioned code fix for efficacy is in its final stages. We anticipate that the process will be complete by our next scheduled communications update, at which time we'll prepare the fix for deployment to the impacted service environment.
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: Monday, March 31, 2025, at 6:30 PM UTC
Time:Mon Mar 24 13:27:21 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: Our efforts to validate and review the efficacy of our code fix before initiating deployment are ongoing. We'll provide a timeline for deployment and remediation as it becomes available.
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: Thursday, March 27, 2025, at 7:30 PM UTC
Time:Wed Mar 19 14:26:25 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: We're continuing to validate and review the efficacy of our code fix before potential deployment to affected users. Due to the complexity of the aforementioned code fix designed to correct the authentication configuration, additional time is needed to verify the code fix will resolve all reported impact scenarios for affected tenants.
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: Monday, March 24, 2025, at 7:00 PM UTC
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.

TM1041927 - Users may see their camera self-view presenting upside-down in Microsoft Teams meetings using some iPad OS devices

Status:serviceRestored
Start Time:Wed Mar 12 03:00:00 2025
End Time:Wed Mar 26 15:58:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu Mar 27 13:08:56 2025
Root Cause:A recent change to the API responsible for facilitating the camera signal in Microsoft Teams meetings introduced a compatibility issue that prevented the service from orienting the incoming camera signal correctly, leading to impact.
Next Update:N/A

Details

Time:Wed Mar 26 19:09:32 2025
Description:Title: Users may see their camera self-view presenting upside-down in Microsoft Teams meetings using some iPad OS devices
User impact: Users may have seen their camera self-view presenting upside-down in Microsoft Teams meetings using iPad OS devices.
More info: This issue specifically affected the iPad OS devices that were released in 2025 and are leveraging iPad OS version 18.3.0 or later. This includes the following devices:
iPad 11th Gen (WiFi) iPad 11th Gen (WiFi+Cellular) iPad Air 11-inch 7th Gen (WiFi) (M3) iPad Air 11-inch 7th Gen (WiFi+Cellular) (M3) iPad Air 13-inch 7th Gen (WiFi) (M3) iPad Air 13-inch 7th Gen (WiFi+Cellular) (M3)
Other devices, including other iPad OS devices, weren't impacted.
Final status: Our investigation has determined that a recent change to the API responsible for facilitating the camera signal in Microsoft Teams meetings introduced a compatibility issue that prevented the service from orienting the incoming camera signal correctly, leading to impact. We've developed and deployed a fix to restore compatibility with this API and repair the issue, and we've monitored our service health telemetry to confirm that the previously affected self-views are now oriented correctly and impact is remediated. We recommend that any user still seeing the impact restart their Microsoft Teams app on the affected device to ensure they've received the fix.
Scope of impact: Any user viewing their camera self-view in Microsoft Teams meetings using an iPad OS device that was released in 2025 and is leveraging iPad OS version 18.3.0 or later may have been impacted.
Start time: Wednesday, March 12, 2025, at 7:00 AM UTC
End time: Wednesday, March 26, 2025, at 7:58 PM UTC
Root cause: A recent change to the API responsible for facilitating the camera signal in Microsoft Teams meetings introduced a compatibility issue that prevented the service from orienting the incoming camera signal correctly, leading to impact.
Next steps: - We're reviewing the API change that led to the issue to assist us in reinforcing our services against similar future changes and preventing compatibility issues before they lead to impact.
This is the final update for the event.
Time:Wed Mar 26 18:53:25 2025
Description:Title: Users may see their camera self-view presenting upside-down in Microsoft Teams meetings using some iPad OS devices
User impact: Users may have seen their camera self-view presenting upside-down in Microsoft Teams meetings using iPad OS devices.
We've investigated a problem in which users may have seen their camera self-view presenting upside-down in Microsoft Teams meetings using iPad OS devices, 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.

MP1041264 - Users and admins cannot use several features within Microsoft Purview

Status:serviceRestored
Start Time:Tue Mar 25 14:45:00 2025
End Time:Wed Mar 26 20:23:00 2025
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:incident
Last Updated:Thu Mar 27 01:17:26 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Thu Mar 27 01:17:26 2025
Description:Title: Users and admins cannot use several features within Microsoft Purview
User impact: Users received an error when attempting to use multiple Microsoft Purview features.
More info: Insider Risk Management, Microsoft Information Protection Server-Side Auto Labeling, Data Loss Prevention, Communication Compliance services, Data Lifecycle Management and Priva Subject Right Requests, and the ability to select and find certain mailboxes were affected by this event.
Final status: We’ve successfully implemented the mitigation strategy, and confirmed the service has been restored to a healthy state.
Scope of impact: Any user or admin attempting to use Purview Risk Management services or access the Communication Compliance Center was affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
End time: Thursday, March 27, 2025, at 12:23 AM UTC
Preliminary root cause: A recent change meant to improve the portion of infrastructure responsible for Purview functionality became degraded and resulted in impact.
Next steps: - We're assessing our service monitoring of this impact scenario to implement improvements for detecting similar events and reduce our time to identify, mitigate, or prevent this type of impact.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Wed Mar 26 20:23:40 2025
Description:We’ve confirmed the deployment has achieved 100 percent saturation in production, and we’re currently testing and monitoring to verify that the impact is remediated.
This quick update is designed to give the latest information on this issue.
Time:Wed Mar 26 19:58:17 2025
Description:We’ve also validated our solution will remediate impact for issues with MIP & DLP simulations modes as well as Priva Subject Right Requests. We will keep testing and validating to make sure all scenarios affected by this event are properly remediated.
This quick update is designed to give the latest information on this issue.
Time:Wed Mar 26 19:29:06 2025
Description:We've validated our solution will remediate impact for issues with Insider Risk Management and Communication Compliance services and are proceeding to deploy our solution to the broader production environment. We'll continue to test and validate to confirm all scenarios impacted by this event will be remediated.
This quick update is designed to give the latest information on this issue.
Time:Wed Mar 26 18:44:22 2025
Description:Title: Users and admins cannot use several features within Microsoft Purview
User impact: Users receive an error when attempting to use multiple Microsoft Purview features.
More info: Insider Risk Management, Microsoft Information Protection Server-Side Auto Labeling, Data Loss Prevention, Communication Compliance services, Data Lifecycle Management and Priva Subject Right Requests, and the ability to select and find certain mailboxes are affected by this event.
Current status: We've made significant progress in testing and validating our new mitigation strategy. After a thorough evaluation and successful results in our testing environment, we've now expanded the implementation to a subset of our production environment. We'll continue to monitor the progress of our new mitigation strategy closely and share updates as more information becomes available.
Scope of impact: Any user or admin attempting to use Purview Risk Management services or access the Communication Compliance Center is affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Thursday, March 27, 2025, at 5:00 AM UTC
Time:Wed Mar 26 14:40:39 2025
Description:Title: Users and admins cannot use several features within Microsoft Purview
User impact: Users receive an error when attempting to use multiple Microsoft Purview features.
More info: Insider Risk Management, Communication Compliance services, Data Lifecycle Management and Priva Subject Right Requests are affected by this event.
Current status: The configuration change we mentioned in the previous communications did not provide the intended relief. However, alongside application of that configuration change we were also developing a parallel mitigation strategy throughout the event. We’ve made significant progress on testing this new mitigation strategy. Due to the complexity of the strategy, we estimate another three hours of testing is required. Once we've verified that strategy is a comprehensive solution, we'll establish a rollout timeline and will proceed with applying the needed updates to the production environment.
Scope of impact: Any user or admin attempting to use Purview Risk Management services or access the Communication Compliance Center is affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update by: Wednesday, March 26, 2025, at 11:00 PM UTC
Time:Wed Mar 26 12:43:31 2025
Description:We've confirmed that Data Lifecycle Management features are affected by this issue and we're updating the Title and User Impact sections to reflect this.
This quick update is designed to give the latest information on this issue.
Time:Wed Mar 26 08:56:05 2025
Description:Title: Users and admins cannot use several features within Microsoft Purview
User impact: Users receive an error when attempting to use multiple Microsoft Purview features.
More info: Insider Risk Management, Communication Compliance services, and Data Lifecycle Management are affected by this event.
Current status: We’re actively monitoring the progress of the configuration change, which is taking longer than initially anticipated. Based on our current progress, we expect this process will be completed by our next scheduled update. In addition, we’re exploring if further actions are required to mitigate the impact.
Scope of impact: Any user or admin attempting to use Purview Risk Management services or access the Communication Compliance Center is affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 7:00 PM UTC
Time:Wed Mar 26 03:57:26 2025
Description:Title: Users and admins are unable to use Purview Communication Compliance or Insider Risk Management services.
User impact: Users receive an error when attempting to use Purview Insider Risk Management or Communication Compliance services.
Current status: We’re continuing to monitor the progress of the configuration change, which is taking longer than we originally expected. We’ll provide an estimated timeline by our next scheduled update.
Scope of impact: Any user or admin attempting to use Purview Risk Management services or access the Communication Compliance Center is affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 1:00 PM UTC
Time:Tue Mar 25 23:52:41 2025
Description:Title: Users and admins are unable to use Purview Communication Compliance or Insider Risk Management services.
User impact: Users receive an error when attempting to use Purview Insider Risk Management or Communication Compliance services.
Current status: We're continuing to follow our safe change management processes to apply the configuration change. Based on our current progress, we expect this this process will be completed by Wednesday, March 26, 2025, at approximately 8:00 AM UTC.
Scope of impact: Any user or admin attempting to use Purview Risk Management services or access the Communication Compliance Center is affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 8:00 AM UTC
Time:Tue Mar 25 19:39:26 2025
Description:Title: Users and admins are unable to use Purview Communication Compliance or Insider Risk Management services.
User impact: Users receive an error when attempting to use Purview Insider Risk Management or Communication Compliance services.
Current status: We’ve determined that safely applying our configuration change will take additional time to complete. We project that we’ll complete this process and will fully remediate impact on Wednesday, March 26, 2025 at approximately 4:00 AM UTC.
Scope of impact: Any user or admin attempting to use Purview Risk Management services or access the Communication Compliance Center is affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 4:00 AM UTC
Time:Tue Mar 25 19:10:08 2025
Description:Title: Users and admins are unable to use Purview Communication Compliance or Insider Risk Management services.
User impact: Users receive an error when attempting to use Purview Insider Risk Management or Communication Compliance services.
Current status: We’re performing a targeted configuration change to remediate impact. We expect that completing this action and fully restoring the availability of the affected Purview services and features will take approximately two hours to complete.
Scope of impact: Any user or admin attempting to use Purview Communication Compliance or Risk Management services is affected.
Start time: Tuesday, March 25, 2025, at 6:45 PM UTC
Next update: Wednesday, March 26, 2025, at 1:00 AM UTC

TM1041913 - Some users may be unable to retrieve the attendance list for Microsoft Teams meetings

Status:serviceRestored
Start Time:Wed Mar 26 15:52:00 2025
End Time:Wed Mar 26 20:28:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed Mar 26 22:14:43 2025
Root Cause:A portion of Microsoft Teams service infrastructure, which is responsible for processing the attendance list for Microsoft Teams meetings, was unable to process the volume of requests and became unhealthy.
Next Update:N/A

Details

Time:Wed Mar 26 22:14:35 2025
Description:Title: Some users may be unable to retrieve the attendance list for Microsoft Teams meetings
User impact: Users may have been unable to retrieve the attendance list for Microsoft Teams meetings.
Final status: We've confirmed through further monitoring that our rerouting of affected traffic to alternate portions of healthy infrastructure was successful in resolving the issue and verified that impact is fully remediated.
Scope of impact: Impact was specific to some users located in the East US region who were attempting to retrieve the attendance list for Microsoft Teams meetings.
Start time: Wednesday, March 26, 2025, at 7:52 PM UTC
End time: Thursday, March 27, 2025, at 12:28 AM UTC
Root cause: A portion of Microsoft Teams service infrastructure, which is responsible for processing the attendance list for Microsoft Teams meetings, was unable to process the volume of requests and became unhealthy.
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 bolster the service so we can prevent the potential for similar impact in the future.
This is the final update for the event.
Time:Wed Mar 26 19:01:51 2025
Description:Title: Some users may be unable to retrieve the attendance list for Microsoft Teams meetings
User impact: Users may be unable to retrieve the attendance list for Microsoft Teams meetings.
Current status: After reviewing returned failures when attempting to retrieve the attendance list, we've confirmed that a portion of Microsoft Teams service infrastructure, which is responsible for processing the attendance list for Microsoft Teams meetings, was unable to process the volume of requests and became unhealthy. This resulted in users being unable to retrieve the attendance list for Microsoft Teams meetings. We've moved affected traffic to healthy portions of service infrastructure to resolve impact while we investigate the affected infrastructure further. Simultaneously, we're processing the backlog of requests to retrieve attendance reports for affected meetings and we anticipate this process will be complete by our next scheduled update.
Scope of impact: Impact is specific to users located in the East US region who are attempting to retrieve the attendance list for Microsoft Teams meetings.
Start time: Wednesday, March 26, 2025, at 7:52 PM UTC
Root cause: A portion of Microsoft Teams service infrastructure, which is responsible for processing the attendance list for Microsoft Teams meetings, was unable to process the volume of requests and became unhealthy.
Next update by: Thursday, March 27, 2025, at 4:00 AM UTC
Time:Wed Mar 26 18:18:48 2025
Description:Title: Some users may be unable to retrieve the attendance list for Microsoft Teams meetings
User impact: Users may be unable to retrieve the attendance list for Microsoft Teams meetings.
Current status: We're reviewing service health logistics and metrics, along with returned failures when attempting to retrieve the attendance list, to better understand the underlying root cause of impact and determine what steps we can take to resolve impact.
Scope of impact: Impact is specific to users located in the East US region who are attempting to retrieve the attendance list for Microsoft Teams meetings.
Next update by: Wednesday, March 26, 2025, at 11:30 PM UTC

DZ1041341 - Users may experience crashes on Resilient File System (ReFS) enabled devices in Microsoft Defender

Status:serviceDegradation
Start Time:Tue Mar 11 03:00:00 2025
End Time:N/A
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Wed Mar 26 22:12:19 2025
Root Cause:A recent update to the Microsoft Defender for Endpoint service contained a code issue that affects ReFS enabled devices, leading to impact.
Next Update:Friday, April 4, 2025, at 12:00 PM UTC

Details

Time:Wed Mar 26 22:12:19 2025
Description:Title: Users may experience crashes on Resilient File System (ReFS) enabled devices in Microsoft Defender
User impact: Users may experience crashes on ReFS enabled devices in Microsoft Defender.
More info: This impact is sporadic and may be causing a system failure on ReFS enabled devices on the latest update.
To resolve impact in the meantime, we recommend for all devices with ReFS enabled, to revert back to the previous update, and not utilize the KB5053606, KB5053643, KB5053602, KB5053657, KB5053603, KB5053598 or KB5053596 updates.
Current status: We implemented a code change to reduce the occurrence of the crashes. In addition, we've developed a long-term solution for the issue and are preparing for its deployment in the next major update. We expect that the deployment to the affected environments will take time to complete and will monitor the progress closely.
Scope of impact: Any user may be affected by this event and experience crashes on ReFS enabled devices.
Start time: Tuesday, March 11, 2025, at 7:00 AM UTC
Root cause: A recent update to the Microsoft Defender for Endpoint service contained a code issue that affects ReFS enabled devices, leading to impact.
Next update by: Friday, April 4, 2025, at 12:00 PM UTC
Time:Tue Mar 25 21:48:07 2025
Description:Title: Users may experience crashes on Resilient File System (ReFS) enabled devices in Microsoft Defender
User impact: Users may experience crashes on ReFS enabled devices in Microsoft Defender.
More info: This impact is sporadic and may be causing a system failure on ReFS enabled devices on the latest update.
To resolve impact in the meantime, we recommend for all devices with ReFS enabled, to revert back to the previous update, and not utilize the KB5053606, KB5053643, KB5053602, KB5053657, KB5053603, KB5053598 or KB5053596 updates.
Current status: We were alerted to this issue internally and upon investigation, we identified a recent update to the Microsoft Defender for Endpoint service contained a code issue that affects ReFS enabled devices, leading to impact. We recommend any users with ReFS enabled to not download the affected KB5053606, KB5053643, KB5053602, KB5053657, KB5053603, KB5053598 or KB5053596 updates, and revert back to the previous update version. In addition, we're working on a code change to help dramatically lower the occurrence of this issue while we also work on a long-term fix solution set to release in the next major update.
Scope of impact: Any user may be affected by this event and experience crashes on ReFS enabled devices.
Start time: Tuesday, March 11, 2025, at 7:00 AM UTC
Root cause: A recent update to the Microsoft Defender for Endpoint service contained a code issue that affects ReFS enabled devices, leading to impact.
Next update by: Thursday, March 27, 2025, at 3:30 AM UTC

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 26 21:38:32 2025
Root Cause:A recent deployment incorrectly enabled this feature in the affected environment.
Next Update:Thursday, April 10, 2025, at 5:00 AM UTC

Details

Time:Wed Mar 26 21:38:32 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 completed validating our fix to remove the "Content Freshness" template and have initiated the deployment to the impacted environments. Based on the complexity of the fix, we're deploying it at a slow monitored pace to ensure it doesn't adversely impact other aspects of the service. We anticipate it may take approximately four weeks for the deployment to complete, and we'll aim to provide a resolution timeline once available.
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, April 10, 2025, at 5:00 AM UTC
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

EX1030895 - Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages

Status:postIncidentReviewPublished
Start Time:Sun Mar 9 08:07:00 2025
End Time:Mon Mar 24 16:41:06 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Wed Mar 26 20:04:13 2025
Root Cause:A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next Update:N/A

Details

Time:Wed Mar 26 20:04:13 2025
Description:A post-incident report has been published.
Time:Mon Mar 24 16:42:07 2025
Description:Title: Some users may encounter Non-Delivery Report (NDR) failures when sending or receiving email messages
User impact: Some users may have encountered NDR failures when sending or receiving email messages in Exchange Online.
More info: Users may have received an NDR containing an error stating "554 5.6.0 Corrupt message content".
Additionally, users may have intermittently received calendar invite email messages as a plain text message containing winmail.dat attachments.
Users may have been able to send affected messages by attempting to resend.
Final status: We've completed our work to replay affected email messages and confirmed through service telemetry that NDR failure rates have returned to pre-incident thresholds; the service is maintaining a 99.99 percent success rate. If your organization continues to experience NDRs when sending email messages, we recommend contacting your support representative for further assistance.
Scope of impact: Some users serviced by the impacted portion of infrastructure sending or receiving email in Exchange Online may have been affected, although impact is limited to a small subset of messages.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
End time: Monday, March 24, 2025, at 7:06 PM UTC
Preliminary root cause: A recent change to caching logic introduced a condition where messages with specific properties were cached, and subsequent messages containing those same cached properties were then rejected, resulting in NDR errors.
Next steps: -We're examining the process by which we test and introduce changes to our caching logic to ensure caching issues aren't introduced in future updates.
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 24 09:30:13 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 an 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 proceeding with reviewing and monitoring the email replay process to validate that impact has been successfully remediated. However, we're also assessing potential options to expedite the remaining remediation 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
Root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 8:30 PM UTC
Time:Mon Mar 24 03:09:59 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 an 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 observed that the email replay process is ongoing and that most email messages have been resent at this time. We're continuing to monitor the progress until completion. In parallel, we're investigating potential options to expedite the remaining remediation 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
Root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 3:00 PM UTC
Time:Mon Mar 24 00:56:06 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 an 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 initiated the process to resend all remaining affected email messages. While the email replay process is ongoing, we've determined that these steps have not yet occurred for all of the remaining impacted infrastructure. We're continuing to monitor the progress in the affected environment to address any unforeseen issue that may arise.
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
Root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 8:00 AM UTC
Time:Sun Mar 23 19:30: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: 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 an 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 determined that resending email messages for a limited set of customers has been successful. We're now preparing the remaining affected infrastructure to apply the same steps. Once preparation is complete, we'll proceed with resending all remaining affected messages.
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
Preliminary root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 5:00 AM UTC
Time:Sun Mar 23 17:13:29 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 an 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: Due to our solution saturating the majority of our internal infrastructure, we're resending affected messages directed to internal and external recipients for a limited set of customers. We estimate this will take a couple hours to complete, and once we've validated its success we'll proceed with resending affected messages for all other customers. If a recipient didn't receive a message previously, they will receive it as a new email. In instances of previously sent email that was delivered to some but not all recipients, users that previously received the email will be sent a duplicate copy. Upon completion, we'll validate if any email is routed through the small subset of infrastructure that has yet to receive the fix, and we'll resubmit email destined for internal recipients within affected customer tenants to ensure they're delivered as expected.
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
Root cause: Preliminary root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Next update by: Monday, March 24, 2025, at 2:00 AM UTC
Time:Sat Mar 22 17:58:45 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 an 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 roll out of our updated solution has saturated across the vast majority of our internal infrastructure, and we've confirmed that there's no additional impact and the issue no longer occurs. We're continuing the deployment to the affected environment to restore service and are monitoring its progress to determine an estimated timeline to resolution.
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.
Preliminary root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Sunday, March 23, 2025, at 10:30 PM UTC
Time:Fri Mar 21 17:52: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: 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 an 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 discovered our initial fix unintentionally caused duplicate messages to be sent to external users. We stopped the initial fix and are rolling out the updated solution to our internal infrastructure to validate there is no additional impact. We’ll provide an estimated deployment timeline once one becomes 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.
Preliminary root cause: A recent change to caching logic introduced a condition where messages with specific properties are cached, and subsequent messages containing those same cached properties are then rejected, resulting in NDR errors.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Saturday, March 22, 2025, at 10:00 PM UTC
Time:Thu Mar 20 18:11:55 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 an 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 to address the underlying issues is in the final stages of validation in our internal environment, and we anticipate that this process will complete by our next scheduled update. We'll aim to provide an estimated deployment timeline at this time.
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 21, 2025, at 10:00 PM UTC
Time:Wed Mar 19 21:48:38 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 an 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 making steady progress with the development of the change to address the underlying issues. The fix has been developed and is currently being tested in our internal environment to monitor its effectiveness and minimize potential impact. Once we confirm that the fix is optimized to fully remediate the issue, we’ll proceed with a broader deployment.
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: Thursday, March 20, 2025, at 10:30 PM UTC
Time:Wed Mar 19 16:01:28 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 investigating a change to background caching logic as a potential underlying cause of impact. While our current mitigations have effectively eliminated the impact from this issue, we’re creating an additional change to address the underlying problem, which is expected to completely remediate the issue. We’ll continue to provide updates on the build progress and closely monitor the service 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.
Start time: Sunday, March 9, 2025, at 12:07 PM UTC
Next update by: Thursday, March 20, 2025, at 3:00 AM UTC
Time:Wed Mar 19 06:06:46 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: While we continue our investigation into the root cause of the impact, we’re monitoring the volume of intermittent failing messages, which continues to gradually decrease, and applying additional settings changes as required. We will continue to closely monitor the service for an extended period to ensure the fix is mitigating the issue for all impacted users.
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 8:00 PM UTC
Time:Tue Mar 18 20:10:51 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 configuration changes we’ve made are having the intended effect of reducing the volume of intermittent message failures. We’re continuing to apply some additional settings changes in the impacted infrastructure to further stabilize the environment. We’ll remain in a period of extended close monitoring of the service.
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 10:30 AM UTC
Time:Tue Mar 18 14:56:17 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 see a sustained reduction in NDR errors as our fix has reached 99.4% saturation. We've observed a small number of intermittent message failures post fix deployment, and we're working to adjust some additional backend configurations to prevent this from occurring. We’ll continue to carefully monitor service performance and open any necessary workstreams to fully remediate the impact.
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 1:30 AM UTC
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

EX1027675 - Users may encounter delays or failures when sending or receiving email messages in Exchange Online

Status:postIncidentReviewPublished
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:Wed Mar 26 20:03:44 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:Wed Mar 26 20:03:44 2025
Description:A post-incident report has been published.
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.

EX1036356 - Some users may be unable to access Outlook on the web

Status:postIncidentReviewPublished
Start Time:Wed Mar 19 12:51:00 2025
End Time:Wed Mar 19 14:55:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Wed Mar 26 19:52:18 2025
Root Cause:As part of our ongoing improvements to the use of browser content policies within Outlook in the web, we implemented two changes. These two changes would deploy one after another and combine to provide the expected results. The second change relied on the first change being completed. - Change 1 – Set the client policy verification mode for new policies to be in audit mode instead of enforce mode. - Change 2 – Add an approved client policy to the list of policies to audit.
Next Update:N/A

Details

Time:Wed Mar 26 19:52:18 2025
Description:A post-incident report has been published.
Time:Fri Mar 21 14:58:22 2025
Description:A post-incident report has been published.
Time:Wed Mar 19 15:50:57 2025
Description:Title: Some users may be unable to access Outlook on the web
User impact: Users may have been unable to access Outlook on the web.
More info: Impacted users may have experienced a "Something went wrong" error message.
Final status: We've successfully reverted the problematic code change and verified the issue has been remediated through customer confirmation and service health telemetry.
Scope of impact: Any user routed through the affected infrastructure attempting to access Outlook on the web may have been impacted.
Start time: Wednesday, March 19, 2025, at 4:51 PM UTC
End time: Wednesday, March 19, 2025, at 6:55 PM UTC
Root cause: As part of our ongoing improvements to the use of browser content policies within Outlook in the web, we implemented two changes. These two changes would deploy one after another and combine to provide the expected results. The second change relied on the first change being completed. - Change 1 – Set the client policy verification mode for new policies to be in audit mode instead of enforce mode. - Change 2 – Add an approved client policy to the list of policies to audit.
On March 6, 2025, we started to deploy the first change (referred to as Change 1) that set the verification mode for new policies to be “Audit”. This deployment went through our Safe Deployment Processes (SDP) and at the time of impact, the change had been deployed to 80% of the standard production environment, and had not yet started to deploy to the Government Cloud environments.
On March 19, 2025, the second change (referred to as Change 2) was inadvertently started early. As Change 1 had not been deployed to 20% of the standard production components or any of the Government cloud components, as soon as Change 2 was activated, the new policy was enforced on the components which hadn’t received Change 1. The enforcement of the policy, enabled on March 19, blocked core application logic from working correctly in the client application, preventing Outlook on the web from loading.
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 Mar 19 15:19:37 2025
Description:Title: Some users may be unable to access Outlook on the web
User impact: Users may be unable to access Outlook on the web.
More info: Impacted users may experience a "Something went wrong" error message.
Current status: We're reverting the problematic code change and our service health telemetry is showing improvements to service health. We will continue monitor telemetry to track the progress of recovery and pursue any additional workstreams to expedite recovery.
Scope of impact: Any user attempting to access Outlook on the web may be impacted.
Start time: Wednesday, March 19, 2025, at 4:51 PM UTC
Preliminary root cause: A recent configuration change made to a portion of Outlook on the web infrastructure, introduced a code regression, resulting in impact.
Next update by: Wednesday, March 19, 2025, at 8:00 PM UTC
Time:Wed Mar 19 14:49:29 2025
Description:We've identified a portion of code which is throwing an error. We're working to revert the recent code change and reviewing data from the reproduction to determine any additional next steps.
This quick update is designed to give the latest information on this issue.
Time:Wed Mar 19 14:48:37 2025
Description:Title: Some users may be unable to access Outlook on the web
User impact: Users may be unable to access Outlook on the web.
More info: Impacted users may experience a "Something went wrong" error message.
Current status: We've reproduced the issue and gathered diagnostic data for analysis into the underlying root cause.
Scope of impact: Any user attempting to access Outlook on the web may be impacted.
Next update by: Wednesday, March 19, 2025, at 7:30 PM UTC
Time:Wed Mar 19 14:06:14 2025
Description:Title: Users may be unable to access Outlook on the web
User impact: Users may be unable to access Outlook on the web.
More info: Users encounter a "Something went wrong" error.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 60 minutes.

EX1037867 - Some users are receiving a misleading error when replying to or forwarding email through Outlook on the web

Status:serviceRestored
Start Time:Wed Mar 19 00:26:00 2025
End Time:Mon Mar 24 11:54:00 2025
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Wed Mar 26 16:41:37 2025
Root Cause:A code change that was intended to improve service performance introduced an impacting code regression.
Next Update:N/A

Details

Time:Wed Mar 26 16:26:50 2025
Description:Title: Some users are receiving a misleading error when replying to or forwarding email through Outlook on the web
User impact: Users were receiving a misleading error when replying to or forwarding email through Outlook on the web.
More info: The error was misleading and didn't prevent users from replying to or forwarding email through Outlook on the web.
Final status: We've confirmed with affected users that our fix deployment has resolved the issue. Previously affected users may need to restart Outlook on the web to ensure that our fix has been implemented.
Scope of impact: Impact was specific to some users, who were served through the affected infrastructure, attempting to reply to or forward email messages through Outlook on the web.
Start time: Wednesday, February 19, 2025, at 4:26 AM UTC
End time: Monday, March 24, 2025, at 3:54 PM UTC
Root cause: A code change that was intended to improve service performance introduced an impacting code regression.
Next steps: - We're continuing to evaluate and analyze the affected code change to better understand why impact wasn't caught during the update testing and validation phase. This is to ensure similar impact doesn't occur 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:Mon Mar 24 16:17:00 2025
Description:Title: Some users are receiving a misleading error when replying to or forwarding email through Outlook on the web
User impact: Users are receiving a misleading error when replying to or forwarding email through Outlook on the web.
More info: The error is misleading and doesn't prevent users from replying to or forwarding email through Outlook on the web.
Affected users are seeing the following error message:
"This message can't be saved right now. Please try again later."
Current status: Our additional analysis into the aforementioned error has helped us isolate a code regression that was introduced by an update to help improve service performance. We highly suspect this regression is producing errors for users when replying to or forwarding email through Outlook on the web. We're deploying a fix to address the isolated code regression and have post deployment testing scheduled with affected users to help us confirm if impact has been remediated.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to reply to or forward email messages through Outlook on the web.
Start time: Wednesday, February 19, 2025, at 4:26 AM UTC
Root cause: A code change that intended to improve service performance has introduced an impacting code regression.
Next update by: Wednesday, March 26, 2025, at 9:00 PM UTC
Time:Fri Mar 21 15:10:51 2025
Description:Title: Some users are receiving a misleading error when replying to or forwarding email through Outlook on the web
User impact: Users are receiving a misleading error when replying to or forwarding email through Outlook on the web.
More info: The error is misleading and doesn't prevent users from replying to or forwarding email through Outlook on the web.
Affected users are seeing the following error message:
"This message can't be saved right now. Please try again later."
Current status: We're continuing to assess the aforementioned error to pinpoint its origin and identify the best course of action for remediation. Additionally, we've requested that your representatives gather new network traces to aid in our ongoing investigation.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to reply to or forward email messages through Outlook on the web.
Next update by: Monday, March 24, 2025, at 9:00 PM UTC
Time:Fri Mar 21 01:37:13 2025
Description:Title: Some users are receiving a misleading error when replying to or forwarding email through Outlook on the web
User impact: Users are receiving a misleading error when replying to or forwarding email through Outlook on the web.
More info: The error is misleading and doesn't prevent users from replying to or forwarding email through Outlook on the web.
Affected users are seeing the following error message:
"This message can't be saved right now. Please try again later."
Current status: We're continuing to analyze the aforementioned error so that we can pinpoint its origin and identify the best course of action to remediate the issue.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to reply to or forward email messages through Outlook on the web.
Next update by: Friday, March 21, 2025, at 8:00 PM UTC
Time:Thu Mar 20 23:58:59 2025
Description:Title: Some users are receiving a misleading error when replying to or forwarding email through Outlook on the web
User impact: Users are receiving a misleading error when replying to or forwarding email through Outlook on the web.
More info: The error is misleading and doesn't prevent users from replying to or forwarding email through Outlook on the web.
Affected users are seeing the following error message:
"This message can't be saved right now. Please try again later."
Current status: We've reviewed the HAR files and isolated an internal server error related to a portion of mailbox infrastructure. We're analyzing the error to identify the reason behind its occurrence and to develop a potential remediation strategy.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to reply to or forward email messages through Outlook on the web.
Next update by: Friday, March 21, 2025, at 6:00 AM UTC
Time:Thu Mar 20 22:55:33 2025
Description:Title: Some users are receiving an erroneous error when replying to or forwarding email through Outlook on the web
User impact: Users are receiving an erroneous error when replying to or forwarding email through Outlook on the web.
More info: The error is erroneous and doesn't prevent users from replying to or forwarding email through Outlook on the web.
Affected users are seeing the following error message:
"This message can't be saved right now. Please try again later."
Current status: We're reviewing the HTTP Archive format (HAR) files provided by your organization so that we can understand what's causing the error to occur and to identify our next troubleshooting steps.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to reply to or forward email messages through Outlook on the web.
Next update by: Friday, March 21, 2025, at 4:00 AM UTC
Time:Thu Mar 20 22:28:07 2025
Description:Title: Some users are receiving an error when replying to or forwarding an email through Outlook on the web
User impact: Users are receiving an error when replying to or forwarding an email through Outlook on the web.
Current status: We're investigating a potential issue with Outlook on the web and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1040621 - Users may see intermittent call issues with some SIP phone devices

Status:serviceRestored
Start Time:Wed Mar 19 08:45:00 2025
End Time:Mon Mar 24 08:24:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Mar 25 11:21:06 2025
Root Cause:A processing configuration issue for a partner service team was intermittently producing call issues for some users SIP phone devices.
Next Update:N/A

Details

Time:Tue Mar 25 11:21:06 2025
Description:Title: Users may see intermittent call issues with some SIP phone devices
User impact: Users may have seen intermittent call issues with some SIP phone devices.
More info: The issue was impacting some Session Initiation Protocol (SIP) phone devices ringing for agents configured for call queues and auto attendants.
Final status: We've determined that a partner service team that Microsoft Teams relies on for SIP phone device functionality had experienced an impacting processing configuration issue that was intermittently producing call issues for some users SIP phone devices. After our partner service updated the affected configuration, we've confirmed that impact has been remediated.
Scope of impact: This issue may have intermittently impacted users utilizing SIP phone devices.
Start time: Wednesday, March 19, 2025, at 12:45 PM UTC
End time: Monday, March 24, 2025, at 12:24 PM UTC
Root cause: A processing configuration issue for a partner service team was intermittently producing call issues for some users SIP phone devices.
Next steps: - We're working with our partner service team to better understand the source of the impacting processing configuration issue so we can help prevent similar issues in the future.
This is the final update for the event.
Time:Tue Mar 25 01:42:11 2025
Description:Title: Users may see intermittent call issues with some SIP phone devices
User impact: Users may see intermittent call issues with some SIP phone devices.
More info: The issue is impacting some Session Initiation Protocol (SIP) phone devices ringing for agents configured for call queues and auto attendants.
Current status: The investigation with our partner team is taking time. We expect to have updates on the status of the investigation and mitigation efforts by our next scheduled update time.
Scope of impact: This issue may intermittently impact users utilizing SIP phone devices.
Next update by: Tuesday, March 25, 2025, at 5:00 PM UTC
Time:Mon Mar 24 22:56:01 2025
Description:Title: Users may see intermittent call issues with some SIP phone devices
User impact: Users may see intermittent call issues with some SIP phone devices.
More info: The issue is impacting some Session Initiation Protocol (SIP) phone devices ringing for agents configured for call queues and auto attendants.
Current status: We're continuing to work alongside our partner team to identify the source of the call failures and determine our next steps.
Scope of impact: This issue may intermittently impact users utilizing SIP phone devices.
Next update by: Tuesday, March 25, 2025, at 7:00 AM UTC
Time:Mon Mar 24 22:02:45 2025
Description:Title: Users may see intermittent call issues with some SIP phone devices
User impact: Users may see intermittent call issues with some SIP phone devices.
More info: The issue is impacting some Session Initiation Protocol (SIP) phone devices ringing for agents configured for call queues and auto attendants.
Current status: We identified an issue with a partner service that Microsoft Teams relies on for SIP phone device functionality. We're working with the partner team to isolate the source of the issue, which will help determine the next troubleshooting steps.
Scope of impact: This issue may intermittently impact users utilizing SIP phone devices.
Next update by: Tuesday, March 25, 2025, at 4:00 AM UTC
Time:Mon Mar 24 21:33:18 2025
Description:Title: Users may see intermittent call issues with some SIP phones devices
User impact: Users may see intermittent call issues with some SIP phones devices.
More info: The issue is impacting some Session Initiation Protocol (SIP) phone devices ringing for agents configured for call queues and auto attendants.
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.

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:Tue Mar 25 09:29:16 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.

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:Tue Mar 25 09:29:14 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.

IS1040491 - Some users may be unable to use MSOnline PowerShell or perform operations using the Microsoft Entra Connect wizard

Status:serviceRestored
Start Time:Wed Mar 12 02:14:00 2025
End Time:Mon Mar 24 14:50:00 2025
Service:Microsoft Entra
Feature Group:Microsoft Entra ID
Classification:advisory
Last Updated:Mon Mar 24 19:36:04 2025
Root Cause:Requests from MSOnline PowerShell and Microsoft Entra Connect and Microsoft Entra Connect wizard in versions before 2.4.18.0 were being rejected with a token validation failures error due to a recent configuration change introduced to Microsoft Entra ID.
Next Update:N/A

Details

Time:Mon Mar 24 17:22:23 2025
Description:Title: Some users may be unable to use MSOnline PowerShell or perform operations using the Microsoft Entra Connect wizard
User impact: Users may have been unable to use MSOnline PowerShell or perform operations using the Microsoft Entra Connect wizard.
More info: Users of the Microsoft Entra Connect wizard in versions before 2.4.18.0 may have experienced failures when performing operations on the Microsoft Entra Connect wizard.
Affected users were unable to open the Entra Connect wizard or perform any configuration updates, including operations needed to upgrade their installation.
This issue wasn't related to the ongoing temporary outage tests being ran prior to the retirement of MSOnline PowerShell. More details on this can be found in the listed document below: https://aka.ms/msonlineretirement
Final status: We've determined that requests from MSOnline PowerShell and Microsoft Entra Connect and Microsoft Entra Connect wizard in versions before 2.4.18.0 were being rejected with a token validation failures error due to a recent configuration change introduced to Microsoft Entra ID, which resulted in users of MSOnline PowerShell for Microsoft Entra ID experiencing failures executing PowerShell cmdlets. We've rolled back the most recent changes to the Microsoft Entra ID service to resolve impact. We've confirmed via internal service monitoring and validating with a subset of affected users that impact resolved.
Scope of impact: Your organization is affected by this event, and some users of MSOnline PowerShell for Microsoft Entra ID may have experienced failures executing PowerShell cmdlets and users of the Microsoft Entra Connect wizard in versions before 2.4.18.0 may have experienced failures when performing operations on the Microsoft Entra Connect wizard.
Start time: Wednesday, March 12, 2025, at 6:14 AM UTC
End time: Monday, March 24, 2025, at 6:50 PM UTC
Root cause: Requests from MSOnline PowerShell and Microsoft Entra Connect and Microsoft Entra Connect wizard in versions before 2.4.18.0 were being rejected with a token validation failures error due to a recent configuration change introduced to Microsoft Entra ID.
Next steps: - We're analyzing and reviewing the offending configuration change to better understand why impact was not caught during the testing and validation phase. This is to ensure similar impact does not occur in future and to continue our ongoing push to improve the resiliency of our service for all users.
This is the final update for the event.
Time:Mon Mar 24 16:46:29 2025
Description:Title: Some users of MSOnline PowerShell for Microsoft Entra ID may experience failures executing PowerShell cmdlets
User impact: Users of MSOnline PowerShell for Microsoft Entra ID may have experienced failures executing PowerShell cmdlets.
Current status: We've investigated a problem in which some users of MSOnline PowerShell for Microsoft Entra ID may have experienced failures executing PowerShell cmdlets and users of the Microsoft Entra Connect wizard in versions before 2.4.18.0 may have experienced failures when performing operations on the Microsoft Entra Connect wizard 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.

MO1039281 - Admins' Microsoft 365 Apps usage reports and Microsoft Copilot (Microsoft 365) readiness reports may be delayed

Status:serviceRestored
Start Time:Sat Mar 22 20:00:00 2025
End Time:Mon Mar 24 06:30:00 2025
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Mon Mar 24 19:08:04 2025
Root Cause:A data pipeline issue was resulting in impact.
Next Update:N/A

Details

Time:Mon Mar 24 19:08:04 2025
Description:Title: Admins' Microsoft 365 Apps usage reports and Microsoft Copilot (Microsoft 365) readiness reports may be delayed
User impact: Admins' Microsoft 365 Apps usage reports and Copilot readiness reports may have been delayed.
Final status: We've completed our manual re-execution of the data pipeline, and after a period of monitoring, we've confirmed impact was remediated.
Scope of impact: Admins attempting to get their Microsoft 365 Apps usage reports and Copilot readiness reports may have experienced delays.
Start time: Sunday, March 23, 2025, at 12:00 AM UTC
End time: Monday, March 24, 2025, at 10:00 AM UTC
Root cause: A data pipeline issue was resulting in impact.
Next steps: - To help prevent similar impact in the future, we're further reviewing the underlying cause of the data pipeline issue.
This is the final update for the event.
Time:Sat Mar 22 22:46:13 2025
Description:Title: Admins' Microsoft 365 Apps usage reports and Microsoft Copilot (Microsoft 365) readiness reports may be delayed
User impact: Admins' Microsoft 365 Apps usage reports and Copilot readiness reports may be delayed.
Current status: We've identified a data pipeline issue that's resulting in impact. We're working to manually re-execute this data pipeline in an effort to alleviate impact.
Scope of impact: Admins attempting to get their Microsoft 365 Apps usage reports and Copilot readiness reports may experience delays.
Start time: Sunday, March 23, 2025, at 12:00 AM UTC
Root cause: A data pipeline issue is resulting in impact.
Next update by: Tuesday, March 25, 2025, at 6:00 AM UTC
Time:Sat Mar 22 22:20:51 2025
Description:Title: Admins' Microsoft 365 Apps usage reports and Microsoft Copilot (Microsoft 365) readiness reports may be delayed
User impact: Admins' Microsoft 365 Apps usage reports and Copilot readiness reports may be delayed.
Current status: We're investigating a potential issue in which admins' Microsoft 365 Apps usage reports and Copilot readiness reports may be delayed. 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:serviceRestored
Start Time:Mon Mar 10 04:00:00 2025
End Time:Mon Mar 24 17:22:45 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Mon Mar 24 18:06:48 2025
Root Cause:Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services were operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next Update:N/A

Details

Time:Mon Mar 24 17:22:52 2025
Description:Title: Some users may be unable to search or see recommendations in multiple Microsoft 365 services
User impact: Users may have been unable to search or see recommendations in multiple Microsoft 365 services.
More info: Impacted services included but weren't limited to: - Outlook on the web and desktop client - Microsoft Teams - OneDrive for Business - SharePoint Online
Final status: We've confirmed through our deployment telemetry that the fix has reached all remaining affected users and the impact is remediated.
Scope of impact: Some users attempting to search or see recommendations in any of the Microsoft 365 services noted in the "More info" section of this communication may have been impacted.
Start time: Monday, March 10, 2025, at 8:00 AM UTC
End time: Friday, March 21, 2025, at 6:00 PM UTC
Root cause: Processing components responsible for regulating functionality related to search and suggestions in multiple Microsoft 365 services were operating below acceptable thresholds due to an unexpected increase in inbound request traffic.
Next steps: - We're continuing to review the affected processing components to determine the cause for the increased request traffic, so that we can prevent similar impact from occurring in the future.
This is the final update for the event.
Time:Fri Mar 21 17:28:08 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 addressed the issue halting deployment and we're monitoring the deployment as it reaches the remaining affected infrastructure. 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 or see recommendations in any of the Microsoft 365 services noted in the "More info" section of this communication may be impacted.
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 24, 2025, at 11:00 PM UTC
Time:Thu Mar 20 17:35:27 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 addressing an issue that's halted the deployment of the fix to the remaining affected infrastructure. We'll aim to provide a timeline for the issue to be address and the deployment resumed by our next scheduled communications update.
Scope of impact: Some users attempting to search or see recommendations in any of the Microsoft 365 services noted in the "More info" section of this communication may be impacted.
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: Friday, March 21, 2025, at 11:00 PM UTC
Time:Wed Mar 19 18:14:46 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 the deployment of the fix which is taking longer than initially anticipated. 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 or see recommendations in any of the Microsoft 365 services noted in the "More info" section of this communication may be impacted.
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 20, 2025, at 11:00 PM UTC
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

SP1038113 - Users' SharePoint Online column filter may auto-fill the incorrect term

Status:serviceRestored
Start Time:Thu Mar 13 14:26:00 2025
End Time:Mon Mar 24 12:30:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Mon Mar 24 14:03:52 2025
Root Cause:A recent service update included a change, designed to fix another issue, which introduced a regression in the filter pane component and caused impact.
Next Update:N/A

Details

Time:Mon Mar 24 14:03:52 2025
Description:Title: Users' SharePoint Online column filter may auto-fill the incorrect term
User impact: Users' SharePoint Online column filter may have auto-filled the incorrect term.
More info: When affected users attempted to adjust the list or library column filter, it may have auto-filled the first matching term after they typed the first letter in the text box. Users may have had to delete the auto-filled entry to select another term. This may also have impacted Managed Metadata or Taxonomy columns..
Final status: We've deployed a new build that reverses the offending change, and we confirmed through internal testing that the impact is remediated.
Scope of impact: Any user attempting to adjust a column filter may have been impacted.
Start time: Thursday, March 13, 2025, at 6:26 PM UTC
End time: Monday, March 24, 2025, at 4:30 PM UTC
Root cause: A recent service update included a change, designed to fix another issue, which introduced a regression in the filter pane component and caused impact.
Next steps: - We're reviewing our service update testing and validation procedures to identify and prevent similar regressions in deployments moving forward.
This is the final update for the event.
Time:Fri Mar 21 06:09:14 2025
Description:Title: SharePoint Online column filter is not working as expected
User impact: Users' SharePoint Online column filter is not working as expected.
More info: When filling out the list/library column filter text box after typing the first letter the first matching term automatically auto-fills, requiring the users to delete the auto-fill if they want to select another term. It also affects Managed Metadata / Taxonomy columns.
Current status: We've determined that a regression in the filter pane component is causing impact to occur. We've created a fix which we expect to deploy by Friday, March 21, 2025 and estimate to complete by Sunday, March 30, 2025.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, March 13, 2025, at 6:26 PM UTC
Estimated time to resolve: Sunday, March 30, 2025
Root cause: A regression in the filter pane component is causing impact to occur.
Next update by: Monday, March 24, 2025, at 7:30 PM UTC

TM1037538 - Users are experiencing failures when attempting to join channel meetings in Microsoft Teams

Status:serviceDegradation
Start Time:Wed Mar 5 07:00:00 2025
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon Mar 24 11:45:41 2025
Root Cause:A recent update contains a code regression, resulting in impact.
Next Update:Monday, March 31, 2025, at 8:00 PM UTC

Details

Time:Thu Mar 20 16:11:33 2025
Description:Title: Users are experiencing failures when attempting to join channel meetings in Microsoft Teams
User impact: Users are experiencing failures when attempting to join channel meetings.
More info: Impact is specific to users on the desktop client or web app that are joining channel meetings from the new calendar experience, or users being nudged into these channel meetings.
Users aren't seeing an error, the action simply fails.
While we're working to remediate impact, affected users can still join channel meetings using the classic Teams calendar or the Teams mobile apps.
Current status: We've completed the development of the fix and have initiated the validation process. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Your organization is affected by this event, and any user attempting to join Microsoft Teams channel meetings using the new calendar experience or nudge from the Microsoft Teams desktop and web clients is impacted.
Start time: Wednesday, March 5, 2025, at 12:00 PM UTC
Root cause: A recent update contains a code regression, resulting in impact.
Next update by: Monday, March 31, 2025, at 8:00 PM UTC
Time:Thu Mar 20 14:55:25 2025
Description:Title: Users are experiencing failures when attempting to join channel meetings in Microsoft Teams
User impact: Users are experiencing failures when attempting to join channel meetings.
More info: Impact is specific to users on the desktop client or web app that are joining channel meetings from the new calendar experience, or users being nudged into these channel meetings.
Users aren't seeing an error, the action simply fails.
While we're working to remediate impact, affected users can still join channel meetings using the classic Teams calendar or the Teams mobile apps.
Current status: Our monitoring has identified an increase in join failures for channel meetings in Microsoft Teams. We've reviewed recent service updates and identified that a code regression is resulting in impact. We're in the process of validating a fix to remediate this issue.
Scope of impact: Your organization is affected by this event, and any user attempting to join Microsoft Teams channel meetings using the new calendar experience or nudge from the Microsoft Teams desktop and web clients is impacted.
Start time: Wednesday, March 5, 2025, at 12:00 PM UTC
Root cause: A recent update contains a code regression, resulting in impact.
Next update by: Thursday, March 20, 2025, at 9:00 PM UTC

TM1037560 - Some users can't place calls or join meetings in the Microsoft Teams web client

Status:serviceRestored
Start Time:Wed Mar 19 14:02:00 2025
End Time:Fri Mar 21 20:40:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Mon Mar 24 11:45:04 2025
Root Cause:A recent change to improve authentication efficiency was producing failures for users joining calls or meetings.
Next Update:N/A

Details

Time:Mon Mar 24 11:45:04 2025
Description:Title: Some users can't place calls or join meetings in the Microsoft Teams web client
User impact: Users couldn't place calls or join meetings in the Microsoft Teams web client.
Final status: Following our extended service monitoring, our internal service telemetry has verified that users restarting their Microsoft Teams clients has successfully remediated the impact.
Scope of impact: Your organization was affected by this event, and some users couldn't place calls or join meetings through the Microsoft Teams web client.
Start time: Wednesday, March 19, 2025, at 6:02 PM UTC
End time: Saturday, March 22, 2025, at 12:40 AM UTC
Root cause: A recent change to improve authentication efficiency was producing failures for users joining calls or meetings.
Next steps: - We're further analyzing the offending authentication improvement to help us isolate similar problems during our pre-deployment testing and validation processes.
This is the final update for the event.
Time:Fri Mar 21 11:59:02 2025
Description:Title: Some users can't place calls or join meetings in Microsoft Teams web client
User impact: Users can't place calls or join meetings in Microsoft Teams web client.
Current status: We're continuing to monitor service health metrics to ensure users are remediated after restarting their browser. Affected users will need to restart their client to pick up the authentication optimization change that prevents this issue.
Scope of impact: Your organization is affected by this event, and some users can't place calls or join meetings through the Microsoft Teams web client.
Root cause: A recent change to improve authentication efficiency requires a client restart, and a failure to do so results in issues joining calls or meetings.
Next update by: Monday, March 24, 2025, at 5:00 PM UTC
Time:Thu Mar 20 16:59:05 2025
Description:Title: Some users can't place calls or join meetings in Microsoft Teams web client
User impact: Users can't place calls or join meetings in Microsoft Teams web client.
More info: As a workaround, affected users can restart their browser and sign back in to resolve the issue.
Current status: We've confirmed that a recent change to improve authentication efficiency requires a client restart, and a failure to do so results in the impact. If your users are having issues with placing calls or joining meetings, please have them restart their clients and perform a cache clear. We're monitoring service health metrics to ensure users are remediated after restarting their browser.
Scope of impact: Your organization is affected by this event, and some users can't place calls or join meetings through the Microsoft Teams web client.
Root cause: A recent change to improve authentication efficiency requires a client restart, and a failure to do so results in issues joining calls or meetings.
Next update by: Friday, March 21, 2025, at 5:00 PM UTC
Time:Thu Mar 20 15:50:48 2025
Description:Title: Some users may be unable to place calls or join meetings in Microsoft Teams web client
User impact: Users may be unable to place calls or join meetings in Microsoft Teams web client.
More info: As a workaround, affected users can restart their browser and log back in to resolve the issue.
Current status: We suspect a recent change is resulting in the impact, and we're reviewing our options to determine the best path towards mitigation.
Scope of impact: Some users may be unable to place calls or join meetings in Microsoft Teams web client.
Next update by: Thursday, March 20, 2025, at 9:00 PM UTC
Time:Thu Mar 20 15:32:17 2025
Description:Title: Some users may be unable to place calls or join meetings in Microsoft Teams web client
User impact: Users may be unable to place calls or join meetings in 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.

EX1038119 - Some users' Exchange Online email messages may be unexpectedly quarantined

Status:serviceRestored
Start Time:Thu Mar 20 07:40:00 2025
End Time:Fri Mar 21 17:35:00 2025
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:incident
Last Updated:Fri Mar 21 18:17:11 2025
Root Cause:Specific URLs were miscategorized and quarantined by our anti-spam systems, causing impact.
Next Update:N/A

Details

Time:Fri Mar 21 18:17:11 2025
Description:Title: Some users' Exchange Online email messages may be unexpectedly quarantined
User impact: Users' Exchange Online email messages may have been unexpectedly quarantined.
Final status: We've manually reallocated the remainder of the affected messages and confirmed that this issue is resolved.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Thursday, March 20, 2025, at 11:40 PM UTC
End time: Friday, March 21, 2025, at 9:35 PM UTC
Root cause: Specific URLs were miscategorized and quarantined by our anti-spam systems, causing impact.
Next steps: - We’re continuing our investigation to determine the reason why the affected URLs were being miscategorized to better detect and prevent issues like this from occurring in the future.
This is the final update for the event.
Time:Fri Mar 21 15:05:05 2025
Description:Title: Some users' Exchange Online email messages may be unexpectedly quarantined
User impact: Users' Exchange Online email messages may be unexpectedly quarantined.
Current status: We've manually reallocated a majority of affected email messages and are correcting the remaining items to completely remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Thursday, March 20, 2025, at 11:40 PM UTC
Root cause: Specific URLs are being miscategorized and quarantined by our anti-spam systems, causing impact.
Next update by: Friday, March 21, 2025, at 11:30 PM UTC
Time:Fri Mar 21 12:05:47 2025
Description:Title: Some users' Exchange Online email messages may be unexpectedly quarantined
User impact: Users' Exchange Online email messages may be unexpectedly quarantined.
Current status: We're continuing our efforts to manually correct affected email message locations to remediate impact while we review for more offending URLs.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: Specific URLs are being miscategorized and quarantined by our anti-spam systems, causing impact.
Next update by: Friday, March 21, 2025, at 7:30 PM UTC
Time:Fri Mar 21 10:19:00 2025
Description:Title: Some users' Exchange Online email messages may be unexpectedly quarantined
User impact: Users' Exchange Online email messages may be unexpectedly quarantined.
Current status: Efforts to alleviate impact by adding the affected URLs to the appropriate allow list have so far been unsuccessful. We're attempting to manually correct affected email message locations to remediate impact while we review for more offending URLs.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: Specific URLs are being miscategorised and quarantined by our anti-spam systems, causing impact.
Next update by: Friday, March 21, 2025, at 4:30 PM UTC
Time:Fri Mar 21 08:26:18 2025
Description:Title: Some users' Exchange Online email messages may be unexpectedly quarantined
User impact: Users' Exchange Online email messages may be unexpectedly quarantined.
Current status: We've identified that specific URLs are being miscategorised and quarantined by our anti-spam systems, causing impact. We've added the URLs to an allow list to remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Root cause: Specific URLs are being miscategorised and quarantined by our anti-spam systems, causing impact.
Next update by: Friday, March 21, 2025, at 2:30 PM UTC
Time:Fri Mar 21 06:12:20 2025
Description:Title: Some users' Exchange Online email messages may be unexpectedly quarantined
User impact: Users' Exchange Online email messages may be unexpectedly quarantined.
Current status: We're analyzing trends in diagnostic telemetry to correlate specific affected URLs and determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Friday, March 21, 2025, at 12:30 PM UTC

CP1029739 - Users may be intermittently unable to leverage Microsoft Copilot (Microsoft 365) agents through any connection method

Status:postIncidentReviewPublished
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 21 14:31:24 2025
Root Cause:A change introduced a mismatch with the mechanism responsible for allowing the service to parse models between systems, resulting in impact. The change was made to a shared package utilized by two index services (A and B). However, deployments of service A to the Worldwide Production environment were paused for an extended period, allowing service B deployments to run ahead of it. This led to mismatches between the services. Consequently, these mismatches resulted in the service occasionally incorrectly indicating that Copilot Extensibility had been disabled by the tenant administrator.
Next Update:N/A

Details

Time:Fri Mar 21 14:31:24 2025
Description:A post-incident report has been published.
Time:Tue Mar 18 17:14:24 2025
Description:A post-incident report has been published.
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
Root cause: A change introduced a mismatch with the mechanism responsible for allowing the service to parse models between systems, resulting in impact. The change was made to a shared package utilized by two index services (A and B). However, deployments of service A to the Worldwide Production environment were paused for an extended period, allowing service B deployments to run ahead of it. This led to mismatches between the services. Consequently, these mismatches resulted in the service occasionally incorrectly indicating that Copilot Extensibility had been disabled by the tenant administrator.
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 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.

CP1031818 - Some users are unable to access Copilot in the Edge sidebar with Edge versions 133 and 132

Status:postIncidentReviewPublished
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 21 14:15:40 2025
Root Cause:Copilot in the Edge sidebar had background dependencies on Microsoft Search in Bing, for multiple functionalities. As communicated in the Message Center under MC961557, Microsoft Search in Bing (MSB) is being retired on March 31. 2025. To avoid impact to Copilot in Edge sidebar functionality when MSB is retired, the related dependencies had been moved to a new Edge operating system (OS) that started in Edge version 134.
Next Update:N/A

Details

Time:Fri Mar 21 14:15:40 2025
Description:A post-incident report has been published.
Time:Tue Mar 18 14:45:38 2025
Description:A post-incident report has been published.
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’ve provided a new Message Center communication (MC1034570) providing more details about this required change.
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: Copilot in the Edge sidebar had background dependencies on Microsoft Search in Bing, for multiple functionalities. As communicated in the Message Center under MC961557, Microsoft Search in Bing (MSB) is being retired on March 31. 2025. To avoid impact to Copilot in Edge sidebar functionality when MSB is retired, the related dependencies had been moved to a new Edge operating system (OS) that started in Edge version 134.
On Thursday, March 13, at 10:00 PM UTC, in preparation for the MSB retirement, a configuration change was implemented to enforce the use of Edge version 134 for Copilot in the Edge sidebar.
A miss within the communication process meant that no customer facing messaging was provided prior to this change, to highlight that users would be required to update to the Edge version 134 if they wanted to continue to use Copilot in the Edge sidebar.
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: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

EX1038200 - Users may be unable to access 'Review' page under the Email and Collaboration section in the Defender portal

Status:serviceRestored
Start Time:Thu Mar 20 20:00:00 2025
End Time:Fri Mar 21 11:45:00 2025
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Fri Mar 21 13:40:55 2025
Root Cause:A recent change to our authentication configurations broke a pathway utilized when calling APIs supporting the authentication process, resulting in impact.
Next Update:N/A

Details

Time:Fri Mar 21 13:40:55 2025
Description:Title: Users may be unable to access 'Review' page under the Email and Collaboration section in the Defender portal
User impact: Users may have been unable to access 'Review' page under the Email and Collaboration section in the Defender portal.
More info: The 'Review' page under the Email and Collaboration section in the Microsoft Defender portal wasn't accessible, displaying a blank page and not loading any data.
Final status: We've completed reverting the affecting change and confirmed with a subset of users and admins that impact was successfully resolved.
Scope of impact: The problem may have impacted users and admins trying to access the 'Review' page under the Email and Collaboration section in the Microsoft Defender portal.
Start time: Friday, March 21, 2025, at 12:00 AM UTC
End time: Friday, March 21, 2025, at 3:45 PM UTC
Root cause: A recent change to our authentication configurations broke a pathway utilized when calling APIs supporting the authentication process, resulting in impact.
Next steps: - We're reviewing our change testing and validation procedures to identify opportunities to better detect and prevent similar future impact.
This is the final update for the event.
Time:Fri Mar 21 12:21:57 2025
Description:Title: Users may be unable to access 'Review' page under the Email and Collaboration section in the Defender portal
User impact: Users may be unable to access 'Review' page under the Email and Collaboration section in the Defender portal.
More info: The 'Review' page under the Email and Collaboration section in the Microsoft Defender portal isn’t accessible, displaying a blank page and not loading any data.
Current status: We've identified a recent change to our authentication configurations broke a pathway utilized when calling APIs supporting the authentication process, resulting in impact. We've reverted this change and are reaching out to a subset of affected users to confirm impact remediation.
Scope of impact: The problem may impact users and admins trying to access the 'Review' page under the Email and Collaboration section in the Microsoft Defender portal.
Start time: Friday, March 21, 2025, at 12:00 AM UTC
Root cause: A recent change to our authentication configurations broke a pathway utilized when calling APIs supporting the authentication process, resulting in impact.
Next update by: Friday, March 21, 2025, at 6:30 PM UTC
Time:Fri Mar 21 10:30:11 2025
Description:Title: Users may be unable to access 'Review' page under the Email and Collaboration section in the Defender portal
User impact: Users may be unable to access 'Review' page under the Email and Collaboration section in the Defender portal.
More info: The 'Review' page under the Email and Collaboration section in the Microsoft Defender portal isn’t accessible, displaying a blank page and not loading any data.
Current status: We're reviewing diagnostic data from our telemetry to understand the underlying root cause of the issue and to formulate a mitigation plan.
Scope of impact: The problem may impact users and admins trying to access the 'Review' page under the Email and Collaboration section in the Microsoft Defender portal.
Next update by: Friday, March 21, 2025, at 4:30 PM UTC
Time:Fri Mar 21 08:38:54 2025
Description:Title: Users may be unable to access 'Review' page under the Email and Collaboration section in the Defender portal
User impact: Users may be unable to access 'Review' page under the Email and Collaboration section in the Defender portal.
More info: The 'Review' page under the Email and Collaboration section in the Microsoft Defender portal isn’t accessible, displaying a blank page and not loading any data.
Current status: We’re reviewing details provided in the support case to determine the next steps needed to resolve this issue.
Scope of impact: The problem may impact users and admins trying to access the 'Review' page under the Email and Collaboration section in the Microsoft Defender portal.
Next update by: Friday, March 21, 2025, at 2:30 PM UTC

TM1037727 - Users can't see other users' profiles or perform searches in Microsoft Teams

Status:serviceRestored
Start Time:Thu Mar 20 15:38:00 2025
End Time:Thu Mar 20 16:55:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Fri Mar 21 12:28:11 2025
Root Cause:An increased number of requests wasn't being efficiently handled in the environment that processes Microsoft Teams traffic, resulting in impact.
Next Update:N/A

Details

Time:Fri Mar 21 12:28:11 2025
Description:Title: Users can't see other users' profiles or perform searches in Microsoft Teams
User impact: Users couldn't see other users' profiles or perform searches in Microsoft Teams.
Final status: We've completed our monitoring to ensure moving traffic to a healthy set of infrastructure has remediated impact and verified that the issue is resolved.
Scope of impact: Your organization was affected by this event, and any user attempting to see other users' profiles or perform searches in Microsoft Teams was impacted.
Start time: Thursday, March 20, 2025, at 7:38 PM UTC
End time: Thursday, March 20, 2025, at 8:55 PM UTC
Root cause: An increased number of requests wasn't being efficiently handled in the environment that processes Microsoft Teams traffic, resulting in impact.
Next steps: - We're continuing to analyze the environment that processes Microsoft Teams traffic so we can better understand why it wasn't handling the increasing request numbers efficiently to determine the best way to bolster the infrastructure so this doesn't happen again.
This is the final update for the event.
Time:Thu Mar 20 18:46:12 2025
Description:Title: Users can't see other users' profiles or perform searches in Microsoft Teams
User impact: Users can't see other users' profiles or perform searches in Microsoft Teams.
Current status: We investigated our internal telemetry data and identified that an increased number of requests aren't being efficiently handled in the environment that processes Microsoft Teams traffic. We've moved traffic to a healthy set of infrastructure to handle the excess traffic and are monitoring to confirm if this has remediated impact.
Scope of impact: Your organization is affected by this event, and any user attempting to see other users' profiles or perform searches in Microsoft Teams is impacted.
Start time: Thursday, March 20, 2025, at 7:38 PM UTC
Root cause: An increased number of requests isn't being efficiently handled in the environment that processes Microsoft Teams traffic, resulting in impact.
Next update by: Friday, March 21, 2025, at 5:30 PM UTC
Time:Thu Mar 20 18:12:47 2025
Description:Title: Users can't see other users' profiles or perform searches in Microsoft Teams
User impact: Users can't see other users' profiles or perform searches in Microsoft Teams.
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.

TM1037342 - Some users' apps, such as the Calendar and OneDrive, aren't appearing in the Microsoft Teams sidebar

Status:serviceRestored
Start Time:Tue Mar 18 14:14:00 2025
End Time:Thu Mar 20 16:07:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu Mar 20 20:36:15 2025
Root Cause:A portion of Microsoft Teams service infrastructure, which facilitates populating the app sidebar, had a misconfiguration that resulted in users whose requests were processed through the affected infrastructure to not be populated or supported.
Next Update:N/A

Details

Time:Thu Mar 20 20:31:42 2025
Description:Title: Some users' apps, such as the Calendar and OneDrive, aren't appearing in the Microsoft Teams sidebar
User impact: Users' apps, such as the Calendar and OneDrive, weren't appearing in the Microsoft Teams sidebar.
Final status: We've completed restarting the cache of users on affected portions of Microsoft Teams service infrastructure and received confirmation from some users who initially reported the issue that the impact is remediated.
Scope of impact: Users whose requests were processed through the affected portion of infrastructure may not have been presented with some side bar apps, such as Calendar and OneDrive, in the Microsoft Teams sidebar of the Microsoft Teams web client and desktop app.
Start time: Tuesday, March 18, 2025, at 6:14 PM UTC
End time: Thursday, March 20, 2025, at 8:07 PM UTC
Root cause: A portion of Microsoft Teams service infrastructure, which facilitates populating the app sidebar, had a misconfiguration that resulted in users whose requests were processed through the affected infrastructure to not be populated or supported.
Next steps: - We're further reviewing the portion of Microsoft Teams service infrastructure to identify what caused the misconfiguration, and to prevent similar impact scenarios from reoccurring.
This is the final update for the event.
Time:Thu Mar 20 17:11:49 2025
Description:Title: Some users' apps, such as the Calendar and OneDrive, aren't appearing in the Microsoft Teams sidebar
User impact: Users' apps, such as the Calendar and OneDrive, aren't appearing in the Microsoft Teams sidebar.
More info: Impact is specific to the Microsoft Teams desktop and web client. Affected users can utilize the Microsoft Teams mobile app to bypass impact.
Affected users can clear their Microsoft Teams cache to restore the Calendar app to the Microsoft Teams sidebar in the desktop app. Directions for clearing Microsoft Teams cache can be found here: https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache
Current status: We've isolated an affecting Enhanced Configuration Service (ECS) change that was recently introduced to Microsoft Teams that aligns with impact. We've reverted the offending ECS change and are validating with a subset of affected users that impact is resolved. Simultaneously, we're working to restart the cache of users on affected portions of Microsoft Teams service infrastructure to ensure our fix is pushed to all users in a timely manner.
Scope of impact: Users whose requests are processes through the affected portion of infrastructure may not be presented with some side bar apps, such as Calendar and OneDrive, in the Microsoft Teams sidebar of the Microsoft Teams web client and desktop app.
Start time: Tuesday, March 18, 2025, at 6:14 PM UTC
Root cause: A portion of Microsoft Teams service infrastructure, which facilitates populating the app sidebar, has a misconfiguration which causes affected users whose requests are processed through the affected infrastructure to not be populated or supported.
Next update by: Friday, March 21, 2025, at 2:00 AM UTC
Time:Thu Mar 20 15:03:26 2025
Description:Title: Some users' apps, such as the Calendar and OneDrive, aren't appearing in the Microsoft Teams sidebar
User impact: Users' apps, such as the Calendar and OneDrive, aren't appearing in the Microsoft Teams sidebar.
More info: Impact is specific to the Microsoft Teams desktop and web client. Affected users can utilize the Microsoft Teams mobile app to bypass impact.
Affected users can clear their Microsoft Teams cache to restore the Calendar app to the Microsoft Teams sidebar in the desktop app. Directions for clearing Microsoft Teams cache can be found here: https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache
Current status: We've determined that a portion of Microsoft Teams service infrastructure, which facilitates populating the app sidebar, has a misconfiguration which causes affected users whose requests are processed through the affected infrastructure to not be populated or supported. We're discussing internally mitigation strategies to resolve this misconfiguration and address the issue as swiftly as possible.
Scope of impact: Users who requests are processes through the affected portion of infrastructure may not be presented with some side bar apps, such as Calendar and OneDrive, in the Microsoft Teams sidebar of the Microsoft Teams web client and desktop app.
Root cause: A portion of Microsoft Teams service infrastructure, which facilitates populating the app sidebar, has a misconfiguration which causes affected users whose requests are processed through the affected infrastructure to not be populated or supported.
Next update by: Thursday, March 20, 2025, at 9:00 PM UTC
Time:Thu Mar 20 13:28:57 2025
Description:Title: Some users may be unable to see the Calendar icon or Files tab in the Microsoft Teams sidebar
User impact: Users may be unable to see the Calendar icon or Files tab in the Microsoft Teams sidebar.
More info: Impact is specific to the Microsoft Teams desktop and web client. Affected users can utilize the Microsoft Teams mobile app to bypass impact.
Affected users can clear their Microsoft Teams cache to restore the Calendar icon to the Microsoft Teams sidebar in the desktop app. Directions for clearing Microsoft Teams cache can be found here: https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache
Current status: We've received additional reports from affected users that they’re also unable to see the Files tab in Microsoft Teams and that impact is specific to the Microsoft Teams desktop client. We've updated the "Title", "User impact", and "More info" sections of this communication to reflect this. We're analyzing affected userIDs and examining the most recent version of Microsoft Teams the users were utilizing and their app cache responses to better understand the underlying root cause.
Scope of impact: Some users may be unable to see the Calendar icon or the Files tab in the Microsoft Teams sidebar of the Microsoft Teams web client and desktop app.
Next update by: Thursday, March 20, 2025, at 7:00 PM UTC
Time:Thu Mar 20 13:16:02 2025
Description:Title: Some users may be unable to see the Calendar icon or Files tab in the Microsoft Teams sidebar
User impact: Users may be unable to see the Calendar icon or Files tab in the Microsoft Teams sidebar.
More info: Impact is specific to the Microsoft Teams desktop and web client. Affected users can utilize the Microsoft Teams mobile app to bypass impact.
Affected users can clear their Microsoft Teams cache to restore the Calendar icon to the Microsoft Teams sidebar in the desktop app. Directions for clearing Microsoft Teams cache can be found here: https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache
Current status: We've received additional reports from affected users that they’re also unable to see the Files tab in Microsoft Teams and that impact is specific to the Microsoft Teams desktop client. We've updated the "Title", "User impact", and "More info" sections of this communication to reflect this. We're analyzing affected userIDs and examining the most recent version of Microsoft Teams the users were utilizing and their app cache responses to better understand the underlying root cause.
Scope of impact: Some users may be unable to see the Calendar icon or the Files tab in the Microsoft Teams sidebar of the Microsoft Teams web client and desktop app.
Next update by: Thursday, March 20, 2025, at 7:00 PM UTC
Time:Thu Mar 20 12:06:38 2025
Description:Title: Some users may be unable to see the Calendar icon in the Microsoft Teams sidebar
User impact: Users may be unable to see the Calendar icon in the Microsoft Teams sidebar.
More info: Affected users can clear their Microsoft Teams cache to restore the Calendar icon to the Microsoft Teams sidebar.
Current status: We're reviewing reproductions of the problem along with client and web logs to better understand the underlying impact scenario. Simultaneously, we're reaching out to a subset of affected users to validate if additional icons may be missing from the Microsoft Teams sidebar.
Scope of impact: Users who are processed through the affected portions of Microsoft Teams service infrastructure may be unable to see the Calendar icon in the Microsoft Teams sidebar.
Next update by: Thursday, March 20, 2025, at 5:30 PM UTC
Time:Thu Mar 20 11:37:20 2025
Description:Title: Users can't see the Calendar icon in the Microsoft Teams dashboard
User impact: Users can't see the Calendar icon in the Microsoft Teams dashboard.
More info: Affected users can clear their Microsoft Teams cache to restore the Calendar icon to the Microsoft Teams dashboard.
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.

DZ1036884 - Users may see delays in alerts for some kinds of activity in the Microsoft Defender portal

Status:serviceRestored
Start Time:Wed Mar 19 18:00:00 2025
End Time:Thu Mar 20 00:42:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Thu Mar 20 01:41:39 2025
Root Cause:A recent change made to the affected infrastructure that supports alerts contained a code issue, which led to impact.
Next Update:N/A

Details

Time:Thu Mar 20 01:41:39 2025
Description:Title: Users may see delays in alerts for some kinds of activity in the Microsoft Defender portal
User impact: Users may have seen delays in alerts for some kinds of activity in the Microsoft Defender portal.
Final status: We were alerted to an issue by our internal monitoring systems for Microsoft Defender. Upon investigating the service, we determined that a recent change made to the affected infrastructure that supports alerts contained a code issue, which led to impact. We reverted this code change and after monitoring our service telemetry, we confirmed that delays had decreased and service health returned to normal.
Scope of impact: Any users serviced by the affected infrastructure may have seen delays in specific security alerts for some kinds of activity in the Microsoft Defender portal.
Start time: Wednesday, March 19, 2025, at 10:00 PM UTC
End time: Thursday, March 20, 2025, at 4:42 AM UTC
Root cause: A recent change made to the affected infrastructure that supports alerts contained a code issue, which led to impact.
Next steps: - We're reviewing the affected service infrastructure to identify improvements that can be made to detection, testing, and validation, to help prevent similar issues from occurring in the future.
This is the final update for the event.
Time:Thu Mar 20 01:15:44 2025
Description:Title: Users may see delays in alerts for some kinds of activity in the Microsoft Defender portal
User impact: Users may see delays in alerts for some kinds of activity in the Microsoft Defender portal.
Current status: We've investigated a problem in which some alerts for activity in the Microsoft Defender portal may be delayed. We've confirmed that service is now restored and we'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.

MP1036709 - Users may see failures when interacting with Insider Risk Management in the Microsoft Purview compliance portal

Status:serviceRestored
Start Time:Wed Mar 19 16:41:00 2025
End Time:Wed Mar 19 21:59:06 2025
Service:Microsoft Purview
Feature Group:Microsoft Purview
Classification:advisory
Last Updated:Wed Mar 19 22:01:40 2025
Root Cause:A recent service update deployment caused intermittent failures with Insider Risk Management in the compliance portal.
Next Update:N/A

Details

Time:Wed Mar 19 21:59:15 2025
Description:Title: Users may see failures when interacting with Insider Risk Management in the Microsoft Purview compliance portal
User impact: Users may have seen intermittent failures when interacting with Insider Risk Management in the compliance portal.
Final status: We identified that a recent service update deployment was causing intermittent failures with Insider Risk Management in the compliance portal. We reverted the update and monitored the telemetry to validate that the impact was remediated.
Scope of impact: This issue may have intermittently impacted any user attempting to interact with Insider Risk Management in the compliance portal.
Start time: Wednesday, March 19, 2025, at 8:41 PM UTC
End time: Thursday, March 20, 2025, at 1:08 AM UTC
Root cause: A recent service update deployment caused intermittent failures with Insider Risk Management in the compliance portal.
Next steps: - We're reviewing our standard service update procedures to help develop ways to better identify and prevent similar deployments from causing impact in the future.
This is the final update for the event.
Time:Wed Mar 19 21:33:47 2025
Description:Title: Users may see failures when interacting with Insider Risk Management in the Microsoft Purview compliance portal
User impact: Users may have seen intermittent failures when interacting with Insider Risk Management in the compliance portal.
Current status: We've investigated a problem in which Microsoft Purview 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.

DZ1036496 - Users may encounter delays for some alerts and behaviors in Microsoft Defender for Cloud Apps and Microsoft Sentinel

Status:serviceRestored
Start Time:Wed Mar 19 16:30:00 2025
End Time:Wed Mar 19 17:40:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Cloud Apps
Classification:advisory
Last Updated:Wed Mar 19 18:31:11 2025
Root Cause:A section of infrastructure, responsible for regulating alerts and behaviors in Anomaly Threat Detection for the Microsoft Defender for Cloud Apps service, was performing below acceptable performance thresholds, which caused delays.
Next Update:N/A

Details

Time:Wed Mar 19 18:31:11 2025
Description:Title: Users may encounter delays for some alerts and behaviors in Microsoft Defender for Cloud Apps and Microsoft Sentinel
User impact: Users may have seen delays for some alerts and behaviors in Microsoft Defender for Cloud Apps and Microsoft Sentinel.
More Info: Affected users may have seen delays of up to 2.5 hours. Impact was specific to Anomaly Threat Detection alerts and behaviors generated by the Microsoft Defender for Cloud Apps service and Microsoft Sentinel.
Final status: We've confirmed through our observation of service telemetry that this issue has been resolved following our mitigating actions and the processing of backlogged data.
Scope of Impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Wednesday, March 19, 2025, at 8:30 PM UTC
End time: Wednesday, March 19, 2025, at 9:40 PM UTC
Root cause: A section of infrastructure, responsible for regulating alerts and behaviors in Anomaly Threat Detection for the Microsoft Defender for Cloud Apps service, was performing below acceptable performance thresholds, which caused delays.
Next steps: - We're continuing to review the section of affected infrastructure to better understand how it came to be performing suboptimally so we can prevent similar issues from occurring in the future.
This is the final update for the event.
Time:Wed Mar 19 17:37:09 2025
Description:Title: Users may encounter delays for some alerts and behaviors in Microsoft Defender for Cloud Apps and Microsoft Sentinel
User impact: Users may encounter delays for some alerts and behaviors in Microsoft Defender for Cloud Apps and Microsoft Sentinel.
More Info: Affected users may see delays of up to 2.5 hours. Impact is specific to Anomaly Threat Detection alerts and behaviors generated by the Microsoft Defender for Cloud Apps service and Microsoft Sentinel.
Current status: Our investigation has identified that a section of infrastructure, responsible for regulating alerts and behaviors in Anomaly Threat Detection for the Microsoft Defender for Cloud Apps service, is performing below acceptable performance thresholds, causing delays. We've restarted the service, which we've confirmed has sufficiently addressed the issue, and we're monitoring as the backlog of data is processed. We're reviewing potential actions to expedite this process, but we anticipate that this should complete and fully remediate the problem by our next scheduled communications update.
Scope of Impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Wednesday, March 19, 2025, at 8:30 PM UTC
Root cause: A section of infrastructure, responsible for regulating alerts and behaviors in Anomaly Threat Detection for the Microsoft Defender for Cloud Apps service, is performing below acceptable performance thresholds, causing delays.
Next update by: Wednesday, March 19, 2025, at 11:30 PM UTC
Time:Wed Mar 19 17:25:02 2025
Description:Title: Users may encounter delays for some alerts and behaviors in Microsoft Defender for Cloud Apps and Microsoft Sentinel
User impact: Users may encounter delays for some alerts and behaviors in Microsoft Defender for Cloud Apps and Microsoft Sentinel.
More Info: Affected users may see delays of up to 2.5 hours. Impact is specific to Anomaly Threat Detection alerts and behaviors generated by the Microsoft Defender for Cloud Apps service and Microsoft Sentinel.
Current status: We're investigating a potential issue with users encountering delays for some alerts and behaviors in Microsoft Defender for Cloud Apps and Microsoft Sentinel. We're checking for impact to your organization, and we'll provide an update within 30 minutes.
Scope of Impact: Impact is specific to some users who are served through the affected infrastructure.

EX1035922 - Some users may be unable to search in Exchange Online using Outlook on the web or the new Outlook client

Status:serviceRestored
Start Time:Mon Mar 17 22:00:00 2025
End Time:Wed Mar 19 16:05:00 2025
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Wed Mar 19 18:13:58 2025
Root Cause:A recent Exchange Online update introduced a code error, which caused some users to have been unable to search in Exchange Online using Outlook on the web or the new Outlook client.
Next Update:N/A

Details

Time:Wed Mar 19 17:25:50 2025
Description:Title: Some users may be unable to search in Exchange Online using Outlook on the web or the new Outlook client
User impact: Users may have been unable to search in Exchange Online using Outlook on the web or the new Outlook client.
More info: Affected users may have seen the following error message "We didn't find anything, try a different keyword" when performing searches in Exchange Online.
As a workaround, users may have been able to yield results using a filter in their search criteria i.e. 'Inbox' under folder names, in addition to a string query.
Final status: After validating with a subset of affected users, we've confirmed that impact is resolved. For affected users that are still experiencing search failures, restarting or refreshing Outlook on the web or the new Outlook client will resolve any lingering search issues.
Scope of impact: Impact was specific to some users, who were served through the affected infrastructure, attempting to search in Exchange Online.
Start time: Thursday, March 13, 2025, at 3:34 AM UTC
End time: Wednesday, March 19, 2025, at 8:05 PM UTC
Root cause: A recent Exchange Online update introduced a code error, which caused some users to have been unable to search in Exchange Online using Outlook on the web or the new Outlook client.
Next steps: - We're continuing to analyze and evaluate the affected Exchange Online update that introduced the code error to understand why impact wasn't caught during the update testing and validation phase. This will help 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:Wed Mar 19 16:34:03 2025
Description:Title: Some users may be unable to search in Exchange Online using Outlook on the web or the new Outlook client
User impact: Users may be unable to search in Exchange Online using Outlook on the web or the new Outlook client.
More info: Affected users may see the following error message "We didn't find anything, try a different keyword" when performing searches in Exchange Online.
As a workaround, users may be able to yield results using a filter in their search criteria i.e. 'Inbox' under folder names, in addition to a string query.
Current status: Our rollback of the affecting update has completed across all affected portions of Exchange Online infrastructure. We're reaching out to a subset of affected users to validate that impact is remediated.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to search in Exchange Online.
Start time: Thursday, March 13, 2025, at 3:34 AM UTC
Root cause: A recent Exchange Online update introduced a code error, which caused some users to be unable to search in Exchange Online using Outlook on the web or the new Outlook client.
Next update by: Wednesday, March 19, 2025, at 10:30 PM UTC
Time:Wed Mar 19 14:52:52 2025
Description:Title: Some users may be unable to search in Exchange Online using Outlook on the web or the new Outlook client
User impact: Users may be unable to search in Exchange Online using Outlook on the web or the new Outlook client.
More info: Affected users may see the following error message "We didn't find anything, try a different keyword" when performing searches in Exchange Online.
As a workaround, users may be able to yield results using a filter in their search criteria i.e. 'Inbox' under folder names, in addition to a string query.
Current status: After further analysis, we've determined that a recent Exchange Online update may have introduced a code error, which is causing some users to be unable to search in Exchange Online using Outlook on the web or the new Outlook client. We're reverting this update in an attempt to resolve impact as swiftly as possible for affected users.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to search in Exchange Online.
Next update by: Wednesday, March 19, 2025, at 9:00 PM UTC
Time:Wed Mar 19 12:54:40 2025
Description:Title: Some users may be unable to search in Exchange Online using Outlook on the web or the new Outlook client
User impact: Users may be unable to search in Exchange Online using Outlook on the web or the new Outlook client.
More info: Affected users may see the following error message "We didn't find anything, try a different keyword" when performing searches in Exchange Online.
As a workaround, users may be able to yield results using a filter in their search criteria i.e. 'Inbox' under folder names, in addition to a string query.
Current status: Based on our review of customer reports, we've determined that the classic Outlook desktop client isn’t impacted and this issue is specific to the new Outlook client and Outlook on the web. We've updated the "Title" and "User impact" sections of communications to reflect this. Regarding our investigation into the cause of this problem, we're analyzing an extra configuration for search queries which could potentially be resulting in the service returning empty search results when users are searching without a specific filter. This will help us to better understand the underlying root cause and what steps we can take to address impact.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to search in Exchange Online.
Next update by: Wednesday, March 19, 2025, at 7:00 PM UTC
Time:Wed Mar 19 09:25:03 2025
Description:Title: Some users may be unable to search in Exchange Online using Outlook on the web or the desktop client
User impact: Users may be unable to search in Exchange Online using Outlook on the web or the desktop client.
More info: Affected users may see the following error message "We didn't find anything, try different keyword" when performing searches in Exchange Online.
As a workaround, users may be able to search using a filter in their search criteria ie 'Inbox' under folder names, in addition to a string query may yield results.
Current status: We've reviewed recent client side changes that may be causing impact, but so far none have been identified. We're analyzing search configuration settings to assist us in identifying why search results aren't working as expected.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to search in Exchange Online.
Next update by: Wednesday, March 19, 2025, at 5:00 PM UTC
Time:Wed Mar 19 07:25:08 2025
Description:Title: Some users may be unable to search in Exchange Online using Outlook on the web or the desktop client
User impact: Users may be unable to search in Exchange Online using Outlook on the web or the desktop client.
More info: Affected users may see the following error message "We didn't find anything, try different keyword" when performing searches in Exchange Online.
Current status: We're continuing to analyze server logs to help identify any exceptions or errors that may be causing impact to occur.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to search in Exchange Online.
Next update by: Wednesday, March 19, 2025, at 1:30 PM UTC
Time:Wed Mar 19 05:29:52 2025
Description:Title: Some users may be unable to search in Exchange Online using Outlook on the web or the desktop client
User impact: Users may be unable to search in Exchange Online using Outlook on the web or the desktop client.
More info: Affected users may see the following error message "We didn't find anything, try different keyword" when performing searches in Exchange Online.
Current status: Our review of HAR logs and recordings has so far proved inconclusive. We're analyzing server logs to help identify any exceptions or errors that may be causing impact to occur.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to search in Exchange Online.
Next update by: Wednesday, March 19, 2025, at 11:30 AM UTC
Time:Wed Mar 19 03:19:12 2025
Description:Title: Some users may be unable to search in Exchange Online using Outlook on the web or desktop client
User impact: Users may be unable to search in Exchange Online using Outlook on the web or desktop client..
More info: Affected users may see the following error message "We didn't find anything, try different keyword" when performing searches in Exchange Online.
Current status: We're analyzing HTTP Archive format (HAR) logs and recordings provided by affected users to determine our next troubleshooting steps.
Scope of impact:Impact is specific to some users, who are served through the affected infrastructure, attempting to search in Exchange Online.
Next update by: Wednesday, March 19, 2025, at 9:30 AM UTC

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:Wed Mar 19 14:35: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: Thursday, February 27, 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.

EX1015252 - Users with apostrophes in their surname in Exchange Online may be unable to search for other users

Status:serviceRestored
Start Time:Wed Feb 5 11:50:00 2025
End Time:Tue Mar 18 15:00:00 2025
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Wed Mar 19 12:49:38 2025
Root Cause:The URL utilized by the Outlook service when performing searches was malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next Update:N/A

Details

Time:Wed Mar 19 12:41:48 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 were unable to search for other users.
Final status: We've completed deployment of our solution throughout the affected environments, and after monitoring the service, we've verified that this action has successfully remediated the problem.
Scope of impact: This issue may have impacted any user with an apostrophe in their surname in Exchange Online that was searching for other users.
Start time: Wednesday, February 5, 2025, at 4:50 PM UTC
End time: Tuesday, March 18, 2025, at 7:00 PM UTC
Root cause: The URL utilized by the Outlook service when performing searches was malformed due to the code not providing the full email address of users with apostrophes in their address when submitting the request.
Next steps: - We're investigating why the URL used by the Outlook service for searches was malformed to help us avoid similar impact in the future.
This is the final update for the event.
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

SP1035795 - Some users may have intermittently seen search page load failures in SharePoint Online

Status:serviceRestored
Start Time:Mon Mar 17 20:00:00 2025
End Time:Tue Mar 18 20:00:00 2025
Service:SharePoint Online
Feature Group:Search and Delve
Classification:advisory
Last Updated:Wed Mar 19 08:37:12 2025
Root Cause:A recent service update contained a change for search functionality that was impacting searches in SharePoint Online.
Next Update:N/A

Details

Time:Wed Mar 19 08:37:12 2025
Description:Title: Some users may have intermittently seen search page load failures in SharePoint Online
User impact: Users may have intermittently seen search page load failures in SharePoint Online.
Final status: We've confirmed the reversion has completed and impact is no longer occurring.
Scope of impact: This issue may have intermittently impacted some users performing searches in SharePoint Online.
Start time: Tuesday, March 18, 2025, at 12:00 AM UTC
End time: Wednesday, March 19, 2025, at 12:00 AM UTC
Root cause: A recent service update contained a change for search functionality that was impacting searches in SharePoint Online.
Next steps: - We're reviewing our recent service update procedures to help prevent similar impact from happening again.
This is the final update for the event.
Time:Wed Mar 19 02:17:06 2025
Description:Title: Some users may intermittently see search page load failures in SharePoint Online
User impact: Users may intermittently see search page load failures in SharePoint Online.
Current status: Our telemetry indicates that the majority of the rollback to revert the changes has completed. We'll continue monitoring the remainder of the rollback to validate that the impact is remediated.
Scope of impact: This issue may intermittently impact some users performing searches in SharePoint Online.
Start time: Tuesday, March 18, 2025, at 12:00 AM UTC
Root cause: A recent service update contains a change for search functionality that is impacting searches in SharePoint Online.
Next update by: Wednesday, March 19, 2025, at 2:00 PM UTC
Time:Wed Mar 19 01:42:15 2025
Description:Title: Some users may intermittently see search page load failures in SharePoint Online
User impact: Users may intermittently see search page load failures in SharePoint Online.
Current status: We've stopped the deployment of the service update causing the impact and are reverting the changes to remediate the impact. We'll provide an estimate on the timeline to revert the update when it one becomes available.
Scope of impact: This issue may intermittently impact some users performing searches in SharePoint Online.
Start time: Tuesday, March 18, 2025, at 12:00 AM UTC
Root cause: A recent service update contains a change for search functionality that is impacting searches in SharePoint Online.
Next update by: Wednesday, March 19, 2025, at 8:00 AM UTC
Time:Tue Mar 18 23:21:45 2025
Description:Title: Some users may intermittently see search page load failures in SharePoint Online
User impact: Users may intermittently see search page load failures in SharePoint Online.
Current status: We identified a recent service update that contained a change for search functionality that is impacting searches in SharePoint Online. We're working to revert the update to remediate the impact.
Scope of impact: This issue may intermittently impact some users performing searches in SharePoint Online.
Start time: Tuesday, March 18, 2025, at 12:00 AM UTC
Root cause: A recent service update contains a change for search functionality that is impacting searches in SharePoint Online.
Next update by: Wednesday, March 19, 2025, at 5:30 AM UTC

TM1035611 - Admins may have seen an incorrect authentication status for devices within the Microsoft Teams admin center

Status:serviceRestored
Start Time:Mon Mar 17 02:30:00 2025
End Time:Wed Mar 19 01:00:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed Mar 19 04:23:00 2025
Root Cause:An authentication configuration issue within a previous update, led to impact.
Next Update:N/A

Details

Time:Wed Mar 19 04:05:50 2025
Description:Title: Admins may have seen an incorrect authentication status for devices within the Microsoft Teams admin center
User impact: Admins may have seen an incorrect authentication status for devices within the Microsoft Teams admin center.
More info: Affected admins may have seen the health status of some devices as "critical."
Final status: We’ve deployed the additional fix to address the remaining impact on affected devices and confirmed that impact has been fully remediated, after monitoring the environment.
Scope of impact: Any admin who attempted to view the health status for devices within the Microsoft Teams admin center may have been impacted.
Start time: Monday, March 17, 2025, at 6:30 AM UTC
End time: Wednesday, March 19, 2025, at 5:00 AM UTC
Root cause: An authentication configuration issue within a previous update, led to impact.
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:Tue Mar 18 20:23:50 2025
Description:Title: Admins may see an incorrect authentication status for devices within the Microsoft Teams admin center
User impact: Admins may see an incorrect authentication status for devices within the Microsoft Teams admin center.
More info: Affected admins may see the health status of some devices as "critical."
Current status: Our investigation has uncovered an authentication configuration issue within a previous update, which is leading to impact. To address this issue, we've reverted this update to prevent future impact to additional devices. To address the remaining impact on affected devices, we're creating, testing, and subsequently deploying an additional fix.
Scope of impact: Any admin attempting to view the health status for devices within the Microsoft Teams admin center may be impacted.
Root cause: An authentication configuration issue within a previous update is leading to impact.
Next update by: Wednesday, March 19, 2025, at 9:30 AM UTC
Time:Tue Mar 18 18:25:37 2025
Description:Title: Admins may see an incorrect authentication status for devices within the Microsoft Teams admin center
User impact: Admins may see an incorrect authentication status for devices within the Microsoft Teams admin center.
More info: Affected admins may see the health status of some devices as "critical."
Current status: We're reviewing service logs to identify the root cause of this event, so we can determine our next troubleshooting steps.
Scope of impact: Any admin attempting to view the health status for devices within the Microsoft Teams admin center may be impacted.
Next update by: Wednesday, March 19, 2025, at 12:30 AM UTC
Time:Tue Mar 18 18:03:54 2025
Description:Title: Admins may see an incorrect health status for devices within the Microsoft Teams admin center
User impact: Admins may see an incorrect health status for devices within the Microsoft Teams admin center.
More info: Affected admins may see the health status of some devices as "critical."
Current status: We're investigating a potential issue where admins may see an incorrect health status for devices within the Microsoft Teams admin center, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

IT1035735 - Users may experience errors or failures when leveraging multiple Microsoft Intune functions

Status:serviceRestored
Start Time:Tue Mar 18 20:20:00 2025
End Time:Tue Mar 18 20:30:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:incident
Last Updated:Tue Mar 18 22:09:49 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Tue Mar 18 22:09:49 2025
Description:Title: Users may experience errors or failures when leveraging multiple Microsoft Intune functions
User impact: Users may have experienced errors or failures when leveraging multiple Microsoft Intune functions.
More info: The impacted functions included, but may have not been limited to, device check-in and device enrollment.
Final status: While we were investigating the service health telemetry, our continued monitoring has affirmed that the service has returned to normal health without any additional actions required. We've completed our period of monitoring and have since confirmed that the issue is no longer occurring and that impact is fully resolved.
Scope of impact: Any Microsoft Intune user served through the affected section of infrastructure in North America may have been impacted.
Start time: Wednesday, March 19, 2025, at 12:20 AM UTC
End time: Wednesday, March 19, 2025, at 12:30 AM UTC
This is the final update for the event.
Time:Tue Mar 18 20:45:13 2025
Description:Title: Users may experience errors or failures when leveraging multiple Microsoft Intune functions
User impact: Users may experience errors or failures when leveraging multiple Microsoft Intune functions.
More info: The impacted functions include, but may not be limited to, device check-in and device enrollment.
Current status: While our investigation into the components of Microsoft Intune infrastructure responsible for facilitating the impacted functions is ongoing, our service health telemetry indicates that the service is recovering. We're continuing to monitor for recovery while our investigation proceeds.
Scope of impact: Any Microsoft Intune user served through the affected section of infrastructure in North America may be impacted.
Start time: Wednesday, March 19, 2025, at 12:20 AM UTC
Next update by: Wednesday, March 19, 2025, at 6:00 AM UTC
Time:Tue Mar 18 20:44:20 2025
Description:Title: Users may experience errors or failures when leveraging multiple Microsoft Intune functions
User impact: Users may experience errors or failures when leveraging multiple Microsoft Intune functions.
More info: The impacted functions include, but may not be limited to, device check-in and device enrollment.
Current status: We're investigating a potential issue with the Microsoft Intune 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:serviceRestored
Start Time:Wed Jan 15 12:00:00 2025
End Time:Tue Mar 18 14:50:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Mar 18 17:11:54 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, was causing impact.
Next Update:N/A

Details

Time:Tue Mar 18 17:09:00 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 have received a cancellation email when the attendees list was edited for existing town hall meetings.
More info: To bypass the issue, meeting organizers should have avoided making edits that only change the co-organizers, presenters, or attendees. Making other edits in addition to edits to these categories may have allowed meeting organizers to avoid the impact.
The town hall meetings weren’t canceled and users who received this email could still attend the meeting as expected using the previously provided details.
Final status: Our deployment to revert the recent update has completed across all impacted infrastructure. After a period of internal service monitoring, we've confirmed that user impact is resolved.
Scope of impact: Some users who were added as attendees to Microsoft Teams town halls and had previously accepted the invitation may have been impacted.
Start time: Wednesday, January 15, 2025, at 5:00 PM UTC
End time: Tuesday, March 18, 2025, at 6:50 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, was causing impact.
Next steps: - We're continuing to analyze and review the affecting service change to better understand why impact wasn’t caught during the testing and validation phase. This is to ensure that similar impact doesn’t occur again 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: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.

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.

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

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.

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.

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

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.

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.