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 Mon Oct 5 06:00:06 2026.
TM1483625 - Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Sep 28 09:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 5 04:00:16 2026 |
|---|
| Root Cause: | A subset of networking service infrastructure that helps facilitate access to PowerPoint Live content has fallen below our manageable service performance thresholds, resulting in impact.
|
|---|
| Next Update: | Tuesday, October 6, 2026, at 10:00 AM UTC |
|---|
|
Details
| Time: | Mon Oct 5 04:00:16 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: We're implementing additional optimizations and traffic management controls to mitigate impact. We're continuing to assess progress and expect to provide an estimated completion timeline in our next update.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Start time: Monday, September 28, 2026, at 1:00 PM UTC
Root cause: A subset of networking service infrastructure that helps facilitate access to PowerPoint Live content has fallen below our manageable service performance thresholds, resulting in impact.
Next update by: Tuesday, October 6, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Sun Oct 4 19:25:24 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: We've monitored service health telemetry and determined that additional mitigation actions are required to fully remediate the issue. We're actively evaluating available mitigation options and working to expedite resolution.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Start time: Monday, September 28, 2026, at 1:00 PM UTC
Root cause: A subset of networking service infrastructure that helps facilitate access to PowerPoint Live content has fallen below our manageable service performance thresholds, resulting in impact.
Next update by: Monday, October 5, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Thu Oct 1 13:42:57 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: Following out latest traffic optimizations and subsequent service restarts, we're monitoring a vast reduction in failures on the affected subset of networking service infrastructure. While impact is expected to be resolved for a majority of users, we're conducting a period of service health monitoring to verify if any additional mitigation efforts will be required.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Start time: Monday, September 28, 2026, at 1:00 PM UTC
Root cause: A subset of networking service infrastructure that helps facilitate access to PowerPoint Live content has fallen below our manageable service performance thresholds, resulting in impact.
Next update by: Friday, October 2, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Oct 1 11:29:14 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: We're restarting system services and monitoring peak traffic patterns after conducting our traffic distribution changes, to determine if additional mitigation actions will be needed.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Start time: Monday, September 28, 2026, at 1:00 PM UTC
Root cause: A subset of networking service infrastructure that helps facilitate access to PowerPoint Live content has fallen below our manageable service performance thresholds, resulting in impact.
Next update by: Thursday, October 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Oct 1 09:49:57 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: We're monitoring service behavior during peak usage periods to measure the impact of the traffic-distribution changes that were recently applied. This analysis is helping us determine why download activity and retries increased and whether additional adjustments are needed to reduce latency and timeout-related impact.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Oct 1 07:46:25 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: We're continuing to analyze the traffic patterns associated with downloading PowerPoint Live content to better understand why some requests are exceeding platform protection thresholds during peak usage periods. We're refining our mitigation actions and reviewing the conditions that are causing cross-region requests to experience increased latency and intermittent timeouts so that we can further reduce impact.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Thu Oct 1 05:45:54 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: We've confirmed that an increased amount of user requests exceeded platform protection thresholds on a component used to download presentation content, resulting in restrictions, packet drops and increased latency that caused some download attempts to timeout before completion. We're applying traffic and performance optimizations to mitigate impact while continuing to investigate the source of the traffic increase.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Oct 1 03:48:30 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: We've determined that packet retransmissions and latency within the data-transfer path used to download presentation content may be causing some download attempts to time out before completion. We're performing targeted diagnostics to further isolate the affected network path and identify the most effective remediation strategy.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Oct 1 01:52:28 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: Our investigation into the additional logs to refine our understanding of why the issue may be occurring is progressing as expected.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Wed Sep 30 23:52:06 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: Further analysis shows that the aforementioned recent request routing change may not be the only factor contributing to impact. We're investigating additional logs to refine our understanding of why the issue may be occurring so that we can identify the best path towards remediation.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Wed Sep 30 21:56:36 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: Based on our review of the telemetry data, failure logs, and correlation IDs, we suspect that there may be a latency issue potentially related to a recent request routing change. We're assessing potential remediation options to determine the best path towards resolving this issue.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Sep 30 19:48:02 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: Our review of the telemetry data, failure logs, and correlation IDs to pinpoint the root cause and a remediation strategy is progressing as expected.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Sep 30 17:51:17 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: We're continuing to review monitoring telemetry data along with failure logs and correlation IDs to determine the root cause and a strategy that remediates impact.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Sep 30 16:39:18 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Current status: We're reviewing monitoring telemetry data to determine why users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
Scope of impact: Users recording PowerPoint Live in Microsoft Teams presentations may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, September 30, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Sep 30 16:22:26 2026 |
|---|
| Description: | Title: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
User impact: Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides.
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.
|
|---|
|
EX1483540 - Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Sep 30 12:54:26 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Oct 4 23:15:03 2026 |
|---|
| Root Cause: | The issue is related to the calendar cache state following a refresh, where the event-loading process may continue referencing outdated calendar data after the folder information is updated.
|
|---|
| Next Update: | Friday, October 9, 2026, at 5:30 PM UTC |
|---|
|
Details
| Time: | Thu Oct 1 10:30:38 2026 |
|---|
| Description: | Title: Users may be intermittently unable to access their calendars in Outlook on the web and the new Outlook desktop client
User impact: Users may be intermittently unable to access their calendars in Outlook on the web and the new Outlook desktop client.
More info: Impacted users may receive the following error message:
“Can’t retrieve calendar events right now. Refresh the browser and try again.”
As a workaround, impacted users can access their calendar in the classic Outlook desktop client or through Microsoft Teams.
Current status: We’ve identified that the issue is related to the calendar cache state following a refresh, where the event-loading process may continue referencing outdated calendar data after the folder information is updated. We’ve implemented and merged a fix to ensure the refreshed calendar data is correctly used when loading subsequent events. The fix is expected to reach affected users by October 9, 2026.
Scope of impact: Some users attempting to access their calendars through Outlook on the web or the new Outlook desktop client may intermittently be impacted.
Estimated time to resolve: Friday October 9, 2026
Root cause: The issue is related to the calendar cache state following a refresh, where the event-loading process may continue referencing outdated calendar data after the folder information is updated.
Next update by: Friday, October 9, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Oct 1 02:24:52 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client
User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.
More info: Users get the error message, “Can’t retrieve calendar events right now. Refresh the browser and try again.” Users can work around this issue by accessing their calendar in classic Outlook or through Microsoft Teams.
Current status: We’re continuing to review service health telemetry and HAR logs to investigate what we suspect is a caching issue that’s leading to the impact. We’re also testing potential solutions to confirm our findings and determine our next steps.
Scope of impact: Some users that attempt to access their calendars through Outlook on the web and new Outlook may be intermittently affected.
|
|---|
|
| Time: | Wed Sep 30 14:22:38 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client
User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.
More info: Users get the error message, “Can’t retrieve calendar events right now. Refresh the browser and try again.” Users can work around this issue by accessing their calendar in classic Outlook or through Microsoft Teams.
Current status: Our review of service health telemetry and the HAR logs persists as we continue to isolate the source of this issue.
Scope of impact: Some users that attempt to access their calendars through Outlook on the web and new Outlook may be intermittently affected.
Next update by: Thursday, October 1, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Sep 30 13:27:14 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client
User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.
More info: Users get the error message, “Can’t retrieve calendar events right now. Refresh the browser and try again.” Users can work around this issue by accessing their calendar in classic Outlook or through Microsoft Teams.
Current status: We're currently reviewing telemetry and HTTP Archive format (HAR) log information as we investigate the cause of impact.
Scope of impact: Some users that attempt to access their calendars through Outlook on the web and new Outlook may be intermittently affected.
Next update by: Wednesday, September 30, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 30 13:04:20 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client
User impact: Users may intermittently be unable to access their calendars in Outlook on the web and the new Outlook desktop client.
More info: Users get the error message, “Can’t retrieve calendar events right now. Refresh the browser and try again.”
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.
|
|---|
|
MO1481173 - Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Sep 28 18:36:21 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 2 22:04:42 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Monday, October 5, 2026, at 9:00 PM UTC |
|---|
|
Details
| Time: | Fri Oct 2 13:24:22 2026 |
|---|
| Description: | Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center
User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.
As of Friday, October 2, 2026, the following usage report types are no longer delayed:
- Active User reports
- Email Activity reports
- Email Apps usage reports
- Mailbox usage reports
- M365 Apps usage reports
- Group Activity reports
-Teams Activity reports
As of Wednesday, September 23, 2026, the following usage report types are no longer delayed:
- Microsoft Teams usage reports
- Group Activity reports
As of Sunday, September 20, 2026, the following usage report types are no longer delayed:
-Adoption Score reports
Current status: We've verified that a significant portion of the scenarios listed in the "More info" section have recovered. We're continuing to monitor the remaining impacted report types, which we anticipate will recover by the time of our next scheduled communications update on Monday, October 5, 2026.
Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.
Next update by: Monday, October 5, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Oct 1 14:49:02 2026 |
|---|
| Description: | Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center
User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.
More info: The following usage report types are delayed since September 19, 2026:
- Microsoft Teams usage reports
- Group Activity reports
- Mailbox usage reports
The following report types are delayed since September 23, 2026:
- Email Activity reports
- Email Apps usage reports
- Active User reports
- Copilot Readiness reports
- M365 Apps usage reports
Current status: While our investigation into the combination of issues that are resulting in impact is ongoing, we're continuing to monitor as additional reporting is generated and made available to admins. Most scenarios are showing improvement, and we'll provide a complete remediation timeline once available.
Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.
Next update by: Friday, October 2, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Sep 30 12:21:49 2026 |
|---|
| Description: | Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center
User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.
More info: The following usage report types are delayed since September 19, 2026:
- Microsoft Teams usage reports
- Group Activity reports
- Mailbox usage reports
The following report types are delayed since September 23, 2026:
- Email Activity reports
- Email Apps usage reports
- Active User reports
- Copilot Readiness reports
- M365 Apps usage reports
Current status: We've identified that there are multiple issues impacting different groups of usage report types in the Microsoft 365 admin center. We're working to isolate all underlying causes of impact, and at this time, we're aware of a code issue occurring within an upstream dependency service that's causing impact to a portion of the affected reports. While we work to confirm which reports are affected by the upstream code issue, we've successfully implemented mitigation and restored Email Activity reports, Email Apps usage reports, and Active User reports to expected functionality. Our investigation is still ongoing to identify what caused these three reports to be impacted, and which other reports are facing a similar issue where this mitigation strategy can be implemented.
Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.
Next update by: Thursday, October 1, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Sep 29 17:57:03 2026 |
|---|
| Description: | Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center
User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.
More info: The following usage report types are delayed since September 19, 2026:
- Microsoft Teams usage reports
- Group Activity reports
- Mailbox usage reports
The following report types are delayed since September 23, 2026:
- Email Activity reports
- Email Apps usage reports
- Active User reports
- Copilot Readiness reports
- M365 Apps usage reports
Current status: Our investigation into the underlying cause is ongoing, while in parallel looking into methods to improve reporting throughput.
Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.
Next update by: Wednesday, September 30, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Sep 28 19:27:50 2026 |
|---|
| Description: | Title: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center
User impact: Admins may see multiple usage report types experiencing varying delays in the Microsoft 365 admin center.
More info: The following usage report types are delayed since September 19, 2026:
- Microsoft Teams usage reports
- Group Activity reports
- Mailbox usage reports
The following report types are delayed since September 23, 2026:
- Email Activity reports
- Email Apps usage reports
- Active User reports
- Copilot Readiness reports
- M365 Apps usage reports
Current status: After further review, we've validated that more tenants are impacted than initially diagnosed, and we've expanded communications to all potentially affected tenants. We've updated the "Title", "User impact", and "Scope of impact" fields of our communications to reflect this change and we've outlined the delayed usage report types in the "More info" section of this communication. We're analyzing delayed report types to isolated potential discrepancies and to determine our next troubleshooting steps.
Scope of impact: Some admins may not see updated usage reports in the Microsoft 365 admin center with varying delays. This section may be updated as the investigation progresses.
Next update by: Tuesday, September 29, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Sep 28 18:45:24 2026 |
|---|
| Description: | Title: Admins see Microsoft Teams usage reports not being updated since September 1, 2026, in the Microsoft 365 admin center
User impact: Admins see Microsoft Teams usage reports not being updated since September 1, 2026, in the Microsoft 365 admin center.
Current status: We've received reports from your representatives that the impact scenario documented in MO1476333 is still ongoing. We're reviewing the latest reports of impact to further our understanding of the current impact scenario and to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and your admins don’t see updated Microsoft Teams usage reports in the Microsoft 365 admin center since September 1, 2026. This section may be updated as the investigation progresses.
Next update by: Tuesday, September 29, 2026, at 5:00 PM UTC
|
|---|
|
TM1486352 - Users' audio quality may be degraded during Microsoft Teams calls that have video or screensharing enabled
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Oct 2 18:58:23 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 2 20:27:11 2026 |
|---|
| Root Cause: | A recent Microsoft Teams service update introduced an issue in which users' audio quality may be degraded. |
|---|
| Next Update: | Monday, October 5, 2026, at 11:00 PM UTC |
|---|
|
Details
| Time: | Fri Oct 2 20:21:37 2026 |
|---|
| Description: | Title: Users' audio quality may be degraded during Microsoft Teams calls that have video or screensharing enabled
User impact: Users' audio quality may be degraded during Microsoft Teams calls that have video or screensharing enabled.
More info: Impact is specific to Microsoft Teams builds 26225.1806 and newer and may occur when users are on a call or meeting that uses video or screensharing. Users may be able to avoid degraded audio by disabling video or screenshare.
Current status: We've determined that reverting the update is not the most effective remediation approach at this time. We're continuing to investigate the issue so we can determine the most effective method to restore expected audio quality and remediate impact.
Scope of impact: Any user that's joined a Microsoft Teams meeting or call that has video or screensharing enabled may be impacted. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams service update introduced an issue in which users' audio quality may be degraded.
Next update by: Monday, October 5, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Oct 2 19:25:01 2026 |
|---|
| Description: | Title: Users' audio quality may be degraded during Microsoft Teams calls that have video or screensharing enabled
User impact: Users' audio quality may be degraded during Microsoft Teams calls that have video or screensharing enabled.
More info: Impact is specific to Microsoft Teams builds 26225.1806 and newer and may when users are on a call or meeting that uses video or screensharing. Users may be able to avoid degraded audio by disabling video or screenshare.
Current status: We've identified that a recent Microsoft Teams service update introduced an issue in which users' audio quality may be degraded. We're determining the most efficient method to reverse the update and remediate the impact.
Scope of impact: Any user that's joined a Microsoft Teams meeting or call that has video or screensharing enabled may be impacted. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams service update introduced an issue in which users' audio quality may be degraded.
Next update by: Saturday, October 3, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Oct 2 19:03:48 2026 |
|---|
| Description: | Title: Users' audio quality may be degraded during Microsoft Teams calls
User impact: Users' audio quality may be degraded during Microsoft Teams calls.
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.
|
|---|
|
EX1478163 - Users may be unable to update calendar delegates in the classic Outlook desktop client
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Sep 23 03:13:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 2 20:24:30 2026 |
|---|
| Root Cause: | A recent update to the service contained a regression, resulting in this impact.
|
|---|
| Next Update: | Tuesday, October 6, 2026, at 2:00 AM UTC |
|---|
|
Details
| Time: | Fri Oct 2 20:24:30 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: Our fix has saturated 95 percent of the affected environment and we'll continue to monitor its progress to ensure it completes successfully. We anticipate that it'll reach full percent saturation and resolve this issue by our next scheduled communications update.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client. This information may be updated as our investigation continues.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
Root cause: A recent update to the service contained a regression, resulting in this impact.
Next update by: Tuesday, October 6, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Oct 1 21:01:13 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: We're still monitoring the deployment of our fix, and more time is needed to ensure it fully saturates across all affected environments before confirming impact remediation. We will share an updated estimate of completion once one becomes available.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client. This information may be updated as our investigation continues.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
Root cause: A recent update to the service contained a regression, resulting in this impact.
Next update by: Saturday, October 3, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Oct 1 17:11:14 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: While the deployment of our fix will take longer than previously expected, we've confirmed that saturation is currently at 93 percent. We anticipate that deployment will reach full saturation by the time of our next scheduled communications update.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client. This information may be updated as our investigation continues.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
Estimated time to resolve: Our updated timeline for full remediation is Friday, October 2, 2026, at 12:00 AM UTC.
Root cause: A recent update to the service contained a regression, resulting in this impact.
Next update by: Friday, October 2, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Sep 30 16:28:55 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: Our deployment is at 62 percent saturation, and we anticipate deployment to be complete by our next scheduled update.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client. This information may be updated as our investigation continues.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
Estimated time to resolve: We anticipate impact to be resolved by our next scheduled update on Thursday, October 1, 2026, at 10:00 PM
Root cause: A recent update to the service contained a regression, resulting in this impact.
Next update by: Thursday, October 1, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Sep 28 16:28:42 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: We’ve validated our fix and started the deployment to the affected environment. We'll provide a timeline for the complete saturation of this fix if one becomes available.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client. This information may be updated as our investigation continues.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
Root cause: A recent update to the service contained a regression, resulting in this impact.
Next update by: Wednesday, September 30, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Sep 28 16:28:33 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: We’ve validated our fix and started the deployment to the affected environment. We'll provide a timeline for the complete saturation of this fix if one becomes available.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client. This information may be updated as our investigation continues.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
Root cause: A recent update to the service contained a regression, resulting in this impact.
Next update by: Wednesday, September 30, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Sep 25 19:54:56 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: We’re in the testing and validation stages of our fix deployment procedures and we anticipate that these actions will be completed, as well as the subsequent deployment process prior to our next scheduled update. At which point, we aim to provide a remediation timeline.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
Root cause: A recent update to the service contained a regression, resulting in this impact.
Next update by: Monday, September 28, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Sep 25 19:54:49 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: We’re in the testing and validation stages of our fix deployment procedures and we anticipate that these actions will be completed, as well as the subsequent deployment process prior to our next scheduled update. At which point, we aim to provide a remediation timeline.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
Root cause: A recent update to the service contained a regression, resulting in this impact.
Next update by: Monday, September 28, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Sep 25 16:12:30 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: We've confirmed that reverting the responsible change is not a valid remediation pathway for this event and have instead developed a code fix to address the regression. We'll provide an update remediation timeline once we start deploying this fix.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
Root cause: A recent update to the service contained a regression, resulting in this impact.
Next update by: Saturday, September 26, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Sep 24 12:27:39 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: We're continuing our plan to revert the change while also looking for methods of expediting the process. Once complete, we'll validate using service telemetry to confirm recovery for all affected users.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client.
Next update by: Friday, September 25, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 12:27:30 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: We're continuing our plan to revert the change while also looking for methods of expediting the process. Once complete, we'll validate using service telemetry to confirm recovery for all affected users.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client.
Next update by: Friday, September 25, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 10:28:15 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may be unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users can manage delegate changes through Outlook on the web.
Current status: We've identified that a recently enabled change may be causing authentication failures affecting delegate permission modification requests. We're reverting the change and are validating service telemetry to confirm recovery for affected users.
Scope of impact: Impact is specific to users that are unable to update calendar delegates in the classic Outlook desktop client.
Next update by: Thursday, September 24, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 09:41:29 2026 |
|---|
| Description: | Title: Users can't update delegates in their calendar within the classic Outlook desktop client
User impact: Users can't update delegates in their calendar within the classic Outlook desktop client.
Current status: We've identified that a recently enabled change may be causing authentication failures affecting delegate permission modification requests. We're reverting the change and are validating service telemetry to confirm recovery for affected users.
Scope of impact: Your organization is affected by this event, and users who are attempting to update delegates in their calendar within the classic Outlook desktop client are impacted. This section may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 08:10:10 2026 |
|---|
| Description: | Title: Users can't update delegates in their calendar within the classic Outlook desktop client
User impact: Users can't update delegates in their calendar within the classic Outlook desktop client.
Current status: We've identified authentication failures affecting delegate permission modification requests. Analysis shows that affected requests are being rejected with unauthorized responses, resulting in access denied errors. We're investigating why authentication tokens are being rejected and working to identify an appropriate mitigation path.
Scope of impact: Your organization is affected by this event, and users who are attempting to update delegates in their calendar within the classic Outlook desktop client are impacted. This section may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 04:44:21 2026 |
|---|
| Description: | Title: Users can't update delegates in their calendar within the classic Outlook desktop client
User impact: Users can't update delegates in their calendar within the classic Outlook desktop client.
Current status: We're reaching out to your organization to request additional network traces and Outlook client logs to support our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and users who are attempting to update delegates in their calendar within the classic Outlook desktop client are impacted. This section may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 02:15:36 2026 |
|---|
| Description: | Title: Users can't update delegates in their calendar within the classic Outlook desktop client
User impact: Users can't update delegates in their calendar within the classic Outlook desktop client.
Current status: We're reviewing support provided logs and available service side data to refine our understanding of the underlying cause of impact so we can determine our next troubleshooting steps.
Scope of impact: Your organization is impacted by this event, and users who are attempting to update delegates in their calendar within the classic Outlook desktop client are impacted. This section may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Sep 24 02:15:35 2026 |
|---|
| Description: | Title: Users can't update delegates in their calendar within the classic Outlook desktop client
User impact: Users can't update delegates in their calendar within the classic Outlook desktop client.
Current status: We're reviewing support provided logs and available service side data to refine our understanding of the underlying cause of impact so we can determine our next troubleshooting steps.
Scope of impact: Your organization is impacted by this event, and users who are attempting to update delegates in their calendar within the classic Outlook desktop client are impacted. This section may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Sep 24 01:47:06 2026 |
|---|
| Description: | Title: Users can't update delegates in their calendar within the classic Outlook desktop client
User impact: Users can't update delegates in their calendar within the classic Outlook desktop client.
Current status: We're investigating a potential issue with users being unable to update delegates in their calendar within the classic Outlook desktop client, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1483380 - Some admins may be unable to register new Windows Autopilot devices or update Autopilot group tags in Microsoft Intune
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Sep 30 09:17:38 2026 |
|---|
| End Time: | Wed Sep 30 10:30:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Oct 2 18:31:17 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 2 18:31:17 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Sep 30 11:14:32 2026 |
|---|
| Description: | Title: Some admins may have been unable to register new Windows Autopilot devices or update Autopilot group tags in Microsoft Intune
User impact: Admins may have been unable to register new Windows Autopilot devices or update Autopilot group tags in Microsoft Intune.
More info: Affected admins may have observed that Windows Autopilot group tag updates didn’t persist after saving, and hardware hash imports were in an incomplete or processing state while the event was ongoing. As a result, profile assignments that relied on Autopilot group tags may not have applied as expected, and registration of new Windows Autopilot devices may have failed.
Final status: We’ve identified and reverted a change in the Intune service, and telemetry confirms that the service has returned to normal functionality and that customer impact has resolved.
Scope of impact: Some admins attempting to register new Windows Autopilot devices or update Autopilot group tags in Microsoft Intune may have been impacted.
Start time: Tuesday, September 29. 2026, at 5:42 PM UTC
End time: Wednesday, September 30, 2026, at 2:30 PM UTC
Preliminary root cause: A change that was intended to update network traffic routing configurations interrupted Admins ability to register new Windows Autopilot devices or update Autopilot group tags in Microsoft Intune.
Next steps:
- We’re reviewing internal processes related to the configuration change pipeline to avoid similar impact 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: | Wed Sep 30 09:19:08 2026 |
|---|
| Description: | Title: Some admins may be unable to register new Windows Autopilot devices or update Autopilot group tags in Microsoft Intune.
User impact: Admins may be unable to register new Windows Autopilot devices or update Autopilot group tags in Microsoft Intune.
More info: Affected admins may observe that Windows Autopilot group tag updates don't persist after saving, and hardware hash imports remain in an incomplete or processing state indefinitely. As a result, profile assignments that rely on Autopilot group tags may not apply as expected, and registration of new Windows Autopilot devices may fail.
Current status: We've identified that requests to update Autopilot group tags are returning successful responses but aren't being applied as expected. We're analyzing service telemetry and recent platform activity to identify the root cause and next steps required to mitigate impact.
Scope of impact: Some admins attempting to register new Windows Autopilot devices or update Autopilot group tags in Microsoft Intune may be impacted.
Next update by: Wednesday, September 30, 2026, at 3:30 PM UTC
|
|---|
|
CP1482212 - Some admins may see stale data in the Microsoft 365 Copilot Health page in the Microsoft 365 admin center
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Sep 29 12:33:38 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 2 16:39:15 2026 |
|---|
| Root Cause: | An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
|
|---|
| Next Update: | Monday, October 5, 2026, at 11:00 AM UTC |
|---|
|
Details
| Time: | Fri Oct 2 16:39:15 2026 |
|---|
| Description: | Title: Some admins may see stale data in the Microsoft 365 Copilot Health page in the Microsoft 365 admin center
User impact: Admins may see stale data in the Copilot Health page in the Microsoft 365 admin center.
More info: Specifically, the tenant readiness-score data after September 8, 2026, may be stale.
Current status: We've re-enabled the upstream process, and we're monitoring service health telemetry to confirm if the issue is resolved.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted.
Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
Next update by: Monday, October 5, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Oct 1 13:16:45 2026 |
|---|
| Description: | Title: Some admins may see stale data in the Microsoft 365 Copilot Health page in the Microsoft 365 admin center
User impact: Admins may see stale data in the Copilot Health page in the Microsoft 365 admin center.
More info: Specifically, the tenant readiness-score data after September 8, 2026, may be stale.
Current status: We're assessing whether re-enabling the upstream process or implementing an alternative remediation option will be the safest and most efficient method for addressing the impact.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted.
Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
Next update by: Friday, October 2, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Oct 1 06:46:02 2026 |
|---|
| Description: | Title: Some admins may see stale data in the Microsoft 365 Copilot Health page in the Microsoft 365 admin center
User impact: Admins may see stale data in the Copilot Health page in the Microsoft 365 admin center.
More info: Specifically, the tenant readiness-score data after September 8, 2026, may be stale.
Current status: Our efforts to restore the upstream process are progressing, with the immediate focus on resuming the generation of new data. In parallel, we’re evaluating the appropriate recovery strategy for the missing data.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted.
Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
Next update by: Thursday, October 1, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 30 06:26:04 2026 |
|---|
| Description: | Title: Some admins may see stale data in the Microsoft 365 Copilot Health page in the Microsoft 365 admin center
User impact: Admins may see stale data in the Copilot Health page in the Microsoft 365 admin center.
More info: Specifically, the tenant readiness-score data after September 8, 2026, may be stale.
Current status: We're continuing our focus on restoring the upstream process to ensure new data is generated while developing a strategy to restore the missing data.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted.
Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
Next update by: Thursday, October 1, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Sep 29 12:52:38 2026 |
|---|
| Description: | Title: Some admins may see stale data in the Microsoft 365 Copilot Health page in the Microsoft 365 admin center
User impact: Admins may see stale data in the Copilot Health page in the Microsoft 365 admin center.
More info: Specifically, the tenant readiness-score data after September 8, 2026, may be stale.
Current status: We've identified an upstream process responsible for Copilot Health data was disabled, resulting in the impact. We're focusing on restoring this process to ensure new data is generated while developing a strategy to restore the missing data.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted.
Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
Next update by: Wednesday, September 30, 2026, at 12:00 PM UTC
|
|---|
|
EX1478331 - Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 22 20:56:00 2026 |
|---|
| End Time: | Fri Oct 2 04:24:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Oct 2 13:47:41 2026 |
|---|
| Root Cause: | A recent service-side update introduced a code error that caused this impacting event.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 2 13:46:47 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not have been quarantined and failed to be stored in the quarantine folder.
More info: The following error appeared in message trace: '550 5.1.10 Failed to deliver to Quarantine store'.
Final status: We completed deployment of our fix to the affected environments and confirmed with affected users that this action successfully resolved the problem.
Scope of impact: This issue impacted users attempting to have email messages quarantined in Exchange Online.
Start time: Wednesday, September 23, 2026, at 12:56 AM UTC
End time: Friday, October 2, 2026, at 8:24 AM UTC
Root cause: A recent service-side update introduced a code error that caused this impacting event.
Next steps: We're reviewing the service-side update that introduced the code error to understand why it resulted in this impact and help prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 1 18:01:11 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: The following error appears in message trace: '550 5.1.10 Failed to deliver to Quarantine store'.
Current status: We're continuing to monitor the deployment of our fix, which has reached 88 percent saturation to the affected environment. We anticipate the deployment will complete by our next scheduled communications update.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Start time: Wednesday, September 23, 2026, at 12:56 AM UTC
Estimated time to resolve: We anticipate the fix will complete deployment by Friday, October 2, 2026, at 7:00 PM UTC.
Root cause: A recent service-side update introduced a code error that has caused this impacting event.
Next update by: Friday, October 2, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Oct 1 13:35:22 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: The following error appears in message trace: '550 5.1.10 Failed to deliver to Quarantine store'.
Current status: We've initiated the fix release and are monitoring as it progresses. We expect to have a completion timeline by the next scheduled update.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Root cause: A recent service-side update introduced a code error that has caused this impacting event.
Next update by: Thursday, October 1, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Sep 30 21:02:16 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: The following error appears in message trace: '550 5.1.10 Failed to deliver to Quarantine store'.
Current status: Validation of our fix is in its final stages, and we expect to begin deploying it to the affected environment by our next scheduled update. We’ll provide an estimated completion timeline once available.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Root cause: A recent service-side updated unintentionally introduced a code error that has caused this impacting event.
Next update by: Thursday, October 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Sep 30 21:02:09 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: The following error appears in message trace: '550 5.1.10 Failed to deliver to Quarantine store'.
Current status: Validation of our fix is in its final stages, and we expect to begin deploying it to the affected environment by our next scheduled update. We’ll provide an estimated completion timeline once available.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Root cause: A recent service-side updated unintentionally introduced a code error that has caused this impacting event.
Next update by: Thursday, October 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Sep 30 14:20:02 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: The following error appears in message trace: '550 5.1.10 Failed to deliver to Quarantine store'.
Current status: We've identified a recent service-side update that introduced an impacting code error that's causing some email messages to not be quarantined and fail to be stored in the quarantine folder. As we develop a code fix to remediate the impact, we're exploring a secondary potential mitigation option involving moving affected service traffic. We're expecting more clarity into our mitigation action plan by our next scheduled communication update.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Root cause: A recent service-side updated unintentionally introduced a code error that has caused this impacting event.
Next update by: Thursday, October 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Sep 24 17:49:37 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: Affected emails cannot be released through the standard Microsoft Defender quarantine workflow. The following error appears in message trace: '550 5.1.10 Failed to deliver to Quarantine store'.
Current status: A recent service-side update unintentionally introduced a code error that is causing legitimate email messages to be incorrectly quarantined and not delivered to recipients. We're developing a code fix and actively validating and testing the remediation in our test environment before broader deployment. We expect this validation work to be completed before our next scheduled communication update.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Start time: Wednesday, September 23, 2026, at 12:56 AM UTC
Root cause: A recent service-side updated unintentionally introduced a code error that has caused this impacting event.
Next update by: Thursday, October 1, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 14:40:23 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: Affected email can’t be released through the normal Microsoft Defender quarantine workflow.
Current status: We've received the requested network message IDs (NMIDs) for failing email deliveries and are analyzing them in order to assist with our ongoing root cause investigation.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Next update by: Thursday, September 24, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 10:58:30 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: Affected email can’t be released through the normal Microsoft Defender quarantine workflow.
Current status: We're analyzing potential email processing failures from the provided message IDs. We're working with some reporting users to collect and provide network message IDs (NMIDs) from failing email deliveries to assist with our troubleshooting analysis.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Next update by: Thursday, September 24, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 09:17:04 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: Some legitimate email messages are not being delivered to the intended recipient and cannot be released through the normal Microsoft Defender quarantine workflow.
Current status: We're reviewing message IDs to help determine the next steps to reach a mitigation plan and root cause analysis.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Next update by: Thursday, September 24, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 07:41:29 2026 |
|---|
| Description: | Title: Some users’ email messages may not be quarantined and fail to be stored in the quarantine folder
User impact: Users’ email messages may not be quarantined and might fail to be stored in the quarantine folder.
More info: Some legitimate email messages are not being delivered to the intended recipient and cannot be released through the normal Microsoft Defender quarantine workflow.
Current status: We're reviewing support case details to determine our next troubleshooting steps.
Scope of impact: This issue may impact users attempting to have email messages quarantined in Exchange Online. This section may be updated as the investigation progresses.
Next update by: Thursday, September 24, 2026, at 1:30 PM UTC
|
|---|
|
EX1473834 - Some users may be unable to search for email in Outlook desktop and Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 17 22:36:00 2026 |
|---|
| End Time: | Thu Oct 1 21:24:05 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Oct 1 23:27:18 2026 |
|---|
| Root Cause: | The portion of service infrastructure responsible for facilitating the Outlook search was receiving increased request traffic preventing the service from being able to handle the traffic in an efficient manner, causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 1 21:25:49 2026 |
|---|
| Description: | Title: Some users may be unable to search for email in Outlook desktop and Outlook on the web
User impact: Users may have been unable to search for email in Outlook desktop and Outlook on the web.
Final status: We've validated through our extended monitoring that the errors associated with impact have not reoccurred and confirmed that impact is remediated.
Scope of impact: Some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web may have been impacted.
Start time: Friday, September 18, 2026, at 2:36 AM UTC
End time: Thursday, October 1, 2026, at 7:01 PM UTC
Root cause: The portion of service infrastructure responsible for facilitating the Outlook search was receiving increased request traffic preventing the service from being able to handle the traffic in an efficient manner, causing impact.
Next steps:
- We've deployed our remediation to all environments to ensure that this issue does not reoccur.
- We're continuing to optimize our response to user needs by prioritizing important feature adaptations and improvements.
|
|---|
|
| Time: | Thu Oct 1 19:31:23 2026 |
|---|
| Description: | Title: Some users may be unable to search for email in Outlook desktop and Outlook on the web
User impact: Users may be unable to search for email in Outlook desktop and Outlook on the web.
Current status: As we continue to monitor the progress of our deployment, we've observed that the occurrences of the error code generated by this issue have dropped significantly. We're conducting a period of extended monitoring to validate this trend and ensure remediation.
Scope of impact: Some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Root cause: The portion of service infrastructure responsible for facilitating the Outlook search is receiving increased request traffic, which is preventing the service from being able to handle the traffic in an efficient manner and is causing impact.
Next update by: Friday, October 2, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Oct 1 15:57:49 2026 |
|---|
| Description: | Title: Some users may be unable to search for email in Outlook desktop and Outlook on the web
User impact: Users may be unable to search for email in Outlook desktop and Outlook on the web.
Current status: We've observed positive trends in telemetry after deploying our fix for this issue and are continuing to monitor to ensure full remediation for all affected users.
Scope of impact: Some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Root cause: The portion of service infrastructure responsible for facilitating the Outlook search is receiving increased request traffic, which is preventing the service from being able to handle the traffic in an efficient manner and is causing impact.
Next update by: Friday, October 2, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Sep 29 15:11:09 2026 |
|---|
| Description: | Title: Some users may be unable to search for email in Outlook desktop and Outlook on the web
User impact: Users may be unable to search for email in Outlook desktop and Outlook on the web.
Current status: Our deployment of configuration changes to remediate impact is continuing and taking slightly longer to fully saturate than anticipated. We'll continue to monitor its deployment and provide an updated remediation timeline as soon as one becomes available.
Scope of impact: Some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Root cause: The portion of service infrastructure responsible for facilitating the Outlook search is receiving increased request traffic, which is preventing the service from being able to handle the traffic in an efficient manner and is causing impact.
Next update by: Thursday, October 1, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Sep 28 16:13:00 2026 |
|---|
| Description: | Title: Some users may be unable to search for email in Outlook desktop and Outlook on the web
User impact: Users may be unable to search for email in Outlook desktop and Outlook on the web.
Current status: Our investigation into the source of the increased request traffic is ongoing. In parallel, our deployment of configuration changes to remediate impact is continuing, and we anticipate it will complete, resolving impact for all users, by our next scheduled communication update.
Scope of impact: Some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Root cause: The portion of service infrastructure responsible for facilitating the Outlook search is receiving increased request traffic, which is preventing the service from being able to handle the traffic in an efficient manner and is causing impact.
Next update by: Tuesday, September 29, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Sep 25 21:52:18 2026 |
|---|
| Description: | Title: Some users may be unable to search for email in Outlook desktop and Outlook on the web
User impact: Users may be unable to search for email in Outlook desktop and Outlook on the web.
Current status: Our current understanding of the impact suggests that the portion of service infrastructure responsible for facilitating the Outlook search is receiving increased request traffic, which is preventing the service from being able to handle the traffic in an efficient manner. We're continuing to investigate the reason for the increased traffic while our deployment of the aforementioned configuration changes is ongoing.
Scope of impact: Some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Root cause: The portion of service infrastructure responsible for facilitating the Outlook search is receiving increased request traffic, which is preventing the service from being able to handle the traffic in an efficient manner and is causing impact.
Next update by: Monday, September 28, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Sep 25 17:15:39 2026 |
|---|
| Description: | Title: Some users may be unable to search for email in Outlook desktop and Outlook on the web
User impact: Users may be unable to search for email in Outlook desktop and Outlook on the web.
Current status: We're continuing to deploy a set of configuration changes that we anticipate might remediate impact while gathering more information to validate our root cause hypothesis.
Scope of impact: Some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Next update by: Saturday, September 26, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Thu Sep 24 21:52:22 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: Our analysis into the behavior of mailbox queries has identified a potential source of this issue. We're gathering more information to validate our hypothesis in tandem with deploying a set of configuration changes we anticipate can remediate the impact.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Friday, September 25, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 15:12:13 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: We’ve determined that additional configuration changes are required to further mitigate impact. We’re applying these changes across the affected infrastructure and monitoring the affected service to validate successful remediation. In parallel, we’re continuing our investigation to isolate and validate the underlying cause of this issue.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Friday, September 25, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Sep 24 04:00:13 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: We've applied configuration changes to allow user queries to consume more memory across applicable mailbox or container types. We're conducting a period of monitoring to verify its success in mitigating impact and to validate the underlying root cause of impact.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Sep 23 23:15:47 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: During our extended period of monitoring, we received additional reports from some users indicating that they're also impacted. We're analyzing these additional reports while in parallel, working to identify the underlying root cause of the search issues. Previously affected users whose mailboxes have been rerouted to alternate infrastructure should still no longer be experiencing impact.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Sep 23 12:55:21 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: We've finished routing the remaining affected mailboxes to alternate healthy infrastructure, and we've received feedback from a subset of the affected users that the issue is no longer occurring. We're monitoring service health telemetry to validate if any additional remediation actions are required to restore full service functionality.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Sep 23 10:30:06 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: We've completed processing the remaining mailbox moves and we're performing validation checks to confirm if impact is now resolved or if any further mitigation actions are required.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Wednesday, September 23, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Sep 23 08:43:11 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: We're continuing to process the remaining mailbox moves and estimate that this should be complete by our next scheduled update.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Wednesday, September 23, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Sep 23 05:14:06 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: The aforementioned fix didn’t provide the expected recovery. We’ve since confirmed that relocating affected mailboxes to alternate database infrastructure restores search functionality, and most of these moves have now been completed. The remaining mailbox moves are in progress, and we’re monitoring the results to confirm that this mitigation fully resolves the impact, with completion expected by our next scheduled update.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Wednesday, September 23, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Sep 22 22:08:13 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: While we continue our analysis of the aforementioned exceptions relating to an invalid authentication component so we can refine our understanding of the underlying cause of impact, we’re in the process of deploying an expedited fix to circumvent the resource allocation limits within affected mailboxes. We anticipate that these actions will further our clarification on the needed troubleshooting steps to ensure that impact is fully resolved.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Wednesday, September 23, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Sep 22 15:18:07 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: We're reviewing our service side logs to identify the reason that the resource allocation limit is being hit, so that we can develop a mitigation strategy to relieve the impact. In tandem, we've isolated exceptions relating to an invalid authentication component and are investigating these to determine whether they're contributing to this issue.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Wednesday, September 23, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Mon Sep 21 23:11:15 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: As we finalize our investigation into whether a resource allocation issue may be contributing to the impact, we're proceeding with further analysis of the exceptions associated with impact to better understand their source and develop our next steps.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Tuesday, September 22, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Sep 18 13:18:12 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: Our investigation of the section of mailbox database infrastructure is ongoing, and we're focusing our efforts on determining whether an issue with resource allocation is the underlying root cause before we begin developing a mitigation strategy.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Tuesday, September 22, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Fri Sep 18 09:17:18 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: We’ve isolated the search failures to resource constraints affecting search processing within a section of mailbox database infrastructure. We’re assessing the health and resource allocation of the affected infrastructure to determine why these limits are being reached and identify our next troubleshooting actions.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Friday, September 18, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Sep 18 02:07:26 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: We’re further pursuing or analysis into the system logs to refine our understanding of where the search issues are manifesting as these actions will expedite the development of our next troubleshooting actions.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Friday, September 18, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Thu Sep 17 23:54:33 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook desktop and Outlook on the web
User impact: Users are unable to search for email in Outlook desktop and Outlook on the web.
Current status: We're analyzing system logs to understand the source of the search issues, which will help us determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and the issue impacts some users attempting to search for Exchange Online email in the Outlook desktop client and Outlook on the web. This information may be updated as our investigation continues.
Next update by: Friday, September 18, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Sep 17 23:30:23 2026 |
|---|
| Description: | Title: Some users are unable to search for email in Outlook and Outlook on the web
User impact: Users are unable to search for email in Outlook and Outlook on the web.
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.
|
|---|
|
TM1440450 - Users may be unable to run run-only workflows from Microsoft Teams
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 30 03:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 1 20:37:33 2026 |
|---|
| Root Cause: | A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
|
|---|
| Next Update: | Tuesday, October 6, 2026, at 1:00 AM UTC |
|---|
|
Details
| Time: | Thu Oct 1 20:37:33 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: The deployment of our fix is taking longer than initially projected and is currently 50 percent complete. We’re monitoring its progress to ensure it completes as expected and resolves the issue by our next scheduled update.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Tuesday, October 6, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Sep 28 19:08:32 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've identified that the deployment of the fix is taking longer than anticipated; however, we are taking manual action to correct the problem. We anticipate that the deployment of the fix should complete by the end of October 1, 2026.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Friday, October 2, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Sep 25 20:02:55 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've identified that the deployment of the fix is taking longer than anticipated. It's currently 25 percent saturated, and we anticipate it will be complete and the issue fully resolved by our next scheduled update.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. This information may be updated as our investigation continues.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Tuesday, September 29, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Sep 14 19:21:15 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've completed validating our fix for this issue and anticipate that its deployment will be complete by Friday, September 25, 2026.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. This information may be updated as our investigation continues.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Saturday, September 26, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Sep 9 20:20:15 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We're completing validation of our fix and preparing for deployment. Once validation activities are complete, we'll begin deployment and provide a more specific resolution timeline in the next scheduled update.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. This information may be updated as our investigation continues.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Tuesday, September 15, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Sep 4 15:02:42 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We’re continuing to perform final validations to ensure the fix fully remediates the impact without introducing any unintended effects. We’ll provide a resolution timeline once available.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses. This information may be updated as our investigation continues.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Thursday, September 10, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Aug 28 15:36:30 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We’re continuing to validate and test the fix to confirm that it fully remediates the impact without introducing any unintended effects.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Friday, September 4, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Aug 26 14:49:52 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: Our process to validate and confirm efficacy of the fix is ongoing, as we work to both ensure successful impact remediation and that there are no adverse effects.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Friday, August 28, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Aug 20 15:36:09 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We're completing the final validations to confirm the efficacy of our secondary fix designed to resolve the impact that occurs when hovering and selecting "More actions" > "Create workflows." We aim to provide a timeline to deployment as soon as possible.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Wednesday, August 26, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Aug 17 14:40:23 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We're continuing to validate the efficacy of a secondary fix designed to resolve the impact that occurs when hovering and selecting "More actions" > "Create workflows." Once a timeline for the deployment of the fix is available, we'll share it accordingly.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Thursday, August 20, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Aug 14 15:14:28 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: Our efforts to validate a secondary fix to remediate the issue in full are ongoing, and we’ll provide a resolution timeline once available.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Monday, August 17, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 14:57:15 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We’re continuing to validate a secondary fix to remediate the issue in full, and we’ll provide an update on the resolution timeline once available.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Friday, August 14, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 30 15:14:16 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've confirmed that our initial fix has resolved this issue for running workflows through the "workflows" button in Microsoft Teams. However, less common scenarios such hovering and selecting "More actions" > "Create workflows" are still impacted. We're validating a secondary fix to address all scenarios in which workflows are run in order to fully resolve this event and will provide an update on the timeline of this final deployment by our next scheduled communication.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Thursday, August 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 20:06:22 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We’re performing an extended period of monitoring the telemetry to ensure that our fix has reached all affected users.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Thursday, July 30, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 04:15:06 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've received confirmation from some affected users that the issue has been mitigated. However, our telemetry indicates that some users are still encountering errors. We're continuing to monitor the telemetry over an extended period to determine when the fix has reached all affected users and fully mitigated the impact. We'll also assess whether any additional mitigation actions are required.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Thursday, July 30, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Jul 28 14:13:09 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've confirmed that the reversion has completed and are reaching out to affected users to confirm this has remediated impact.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running workflows from Microsoft Teams.
Next update by: Wednesday, July 29, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Mon Jul 27 13:41:24 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've validated that we're able to revert the responsible change for expedient remediation as we continue to develop our long-term code fix. We anticipate that this reversion will be completed, mitigating impact, by our next scheduled update.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running workflows from Microsoft Teams.
Next update by: Tuesday, July 28, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Jul 27 08:42:37 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We’ve determined that a recent service update inadvertently introduced a code regression that affected how Teams processes shared workflow requests, preventing some users from running workflows from Teams. We’re developing a fix and validating it before deployment to the affected environment.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running workflows from Microsoft Teams.
Next update by: Monday, July 27, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Jul 27 08:02:26 2026 |
|---|
| Description: | Title: All users are unable to run Microsoft Teams workflows used to create incidents internally
User impact: Users are unable to run Microsoft Teams workflows used to create incidents internally.
More info: Users receive the following error message when attempting to create incidents:
"Missing Trigger URI"
Current status: We're reviewing HTTP Archive (HAR) logs and Teams logs to help identify the root cause and next steps required to mitigate impact.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Next update by: Monday, July 27, 2026, at 7:00 PM UTC
|
|---|
|
MO1457843 - Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Aug 19 18:38:36 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 1 18:50:49 2026 |
|---|
| Root Cause: | A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact.
|
|---|
| Next Update: | Friday, October 30, 2026, at 11:00 PM UTC |
|---|
|
Details
| Time: | Thu Oct 1 18:50:49 2026 |
|---|
| Description: | Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs
User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs.
More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams.
Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs.
Current status: We're deploying the first of three changes which we need to make for to ensure a comprehensive long-term solution. Due to the complexity of these changes, we currently anticipate remediation by Friday, January 30, 2027. We're continuing to monitor the progress of our deployment to identify any opportunities to expedite the process.
Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues.
Start time: Friday, July 10, 2026, at 2:05 PM UTC
Estimated time to resolve: We estimate that our three-phase improvement will be complete by January 30, 2026.
Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact.
Next update by: Friday, October 30, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Sep 16 18:07:58 2026 |
|---|
| Description: | Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs
User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs.
More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams.
Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs.
Current status: We're progressing with our additional levels of validations so we can ensure that our solution returns admins ability to determine who deleted Viva Engage communities or its Microsoft 365 Group in Entra ID audit logs. We'll provide an updated timeline for the deployment of our fix and the remediation of the impact once our pre-deployment tests have concluded.
Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues.
Start time: Friday, July 10, 2026, at 2:05 PM UTC
Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact.
Next update by: Thursday, October 1, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Sep 2 18:29:30 2026 |
|---|
| Description: | Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs
User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs.
More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams.
Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs.
Current status: We've determined that resolving this issue requires additional validation to ensure that our fix addresses the impact without introducing unintended effects to the service. We're continuing testing and validation efforts and will provide an updated deployment timeline once those activities are completed.
Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs. This information may be updated as our investigation continues.
Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact.
Next update by: Wednesday, September 16, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Aug 19 18:38:40 2026 |
|---|
| Description: | Title: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Microsoft Entra ID audit logs
User impact: Admins can't identify who deleted a Viva Engage community or its Microsoft 365 Group in Entra ID audit logs.
More info: Impact applies to deletions initiated from both the Viva Engage web experience and the Viva Engage app in Microsoft Teams.
Admins needing to identify who deleted a specific community or group during the affected period should open a Microsoft support case with the deletion date and group/community details so support can trace the initiating user through service-side logs.
Current status: We've identified an update to our Viva Engage communities that’s preventing admins from identifying users who deleted a Viva Engage community or its connected Microsoft 365 Group in Microsoft Entra ID audit logs. We've developed and are internally validating a fix to remediate the impact. We'll provide an updated timeline for the deployment of our solution and the remediation of the impact once it has become available.
Scope of impact: This issue is preventing all admins from identifying who deleted Viva Engage communities or their connected Microsoft 365 Group in Microsoft Entra ID audit logs.
Root cause: A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 11:00 PM UTC
|
|---|
|
DV1484853 - A small subset of events may not been included in activity logs
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 1 07:45:00 2026 |
|---|
| End Time: | Thu Oct 1 14:00:00 2026 |
|---|
| Service: | Microsoft Dataverse |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 1 16:53:29 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 1 16:53:29 2026 |
|---|
| Description: | Title: A small subset of events may not been included in activity logs
User impact: A small subset of events may not been included in activity logs.
Final Status: We determined that a period of high resource utilization in a portion of our infrastructure responsible for activity auditing led to failures for a subset of activity logging requests, preventing events from appearing in your activity logging. The affected services recovered without the need for manual intervention, restoring activity logging reliability.
This is the final update on the incident.
Preliminary Root Cause: A period of high resource utilization in a portion of our infrastructure responsible for activity auditing.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
EX1478033 - Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 18 23:00:00 2026 |
|---|
| End Time: | Wed Sep 30 12:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Oct 1 12:40:28 2026 |
|---|
| Root Cause: | An authentication issue was preventing users from searching mailbox or Address Book content in Exchange Online.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 1 12:39:32 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may have been unable to search mailbox or Address Book content in Exchange Online across connection methods.
Final status: We've completed deployment of our fix to resolve the authentication issue and validated with a subset of affected users that our fix successfully remediated impact.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may have been affected.
Start time: Saturday, September 19, 2026, at 3:00 AM UTC
End time: Wednesday, September 30, 2026, at 4:00 PM UTC
Root cause: An authentication issue was preventing users from searching mailbox or Address Book content in Exchange Online.
Next steps:
- We're isolating how the authentication issue was introduced into our service to validate what additional actions we can take to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 29 16:57:16 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: The fix has begun deployment in the affected environment, and it appears to be remediating impact. This confirms that an authentication issue is preventing users from searching mailbox or Address Book content in Exchange Online. We’ll provide an estimated timeline for the complete saturation of this fix if it becomes available.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Root cause: An authentication issue is preventing users from searching mailbox or Address Book content in Exchange Online.
Next update by: Friday, October 2, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Sep 28 15:27:56 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: We're continuing the development and validation of our potential fix, and an estimated timeline for their deployment will be provided if it becomes available.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Next update by: Tuesday, September 29, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Sun Sep 27 15:34:50 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: As we progress with our root cause analysis and validate the source for this event, we've determined that our potential fix will require some adjustments ahead of deployment. We're developing and validating these additions, and an estimated timeline for their deployment is expected to be available by our next scheduled communication update.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Next update by: Monday, September 28, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Sat Sep 26 15:15:55 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: We're preparing our potential fix for deployment to resolve the 503 errors and anticipate that deployment should be ready by the time of our next update.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Next update by: Sunday, September 27, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Sep 25 14:58:12 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: We're developing and validating a potential fix to resolve an increase in 503 errors seen within our service processors and remediate impact.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Next update by: Saturday, September 26, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 17:21:10 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: We've completed performance optimizations on a subset of affected Exchange Online service infrastructure and validated that some affected users are seeing remediation, though impact is ongoing for others. We're implementing additional performance optimizations while we continue our investigation into the underlying root cause.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Next update by: Friday, September 25, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 16:12:45 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: We're initiating performance optimizations on a subset of affected Exchange Online service infrastructure to alleviate some impact while we continue to troubleshoot and isolate the underlying root cause.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Next update by: Thursday, September 24, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 14:24:55 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: We've validated that a subset of affected users are still experiencing impact at this time. We're analyzing the service infrastructure hosting affected mailboxes to isolate potential discrepancies leading to continued impact and to determine our next troubleshooting steps.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Next update by: Thursday, September 24, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Sep 23 20:42:09 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: Our review of the service telemetry has led us to suspect that a portion of Exchange Online service infrastructure that facilitates the authentication flow necessary for searching for mailbox or Address Book content may be encountering failures. We've restarted the affected portion of infrastructure and are reaching out to some affected users to confirm whether this action has resolved the issue.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Next update by: Thursday, September 24, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Sep 23 19:01:18 2026 |
|---|
| Description: | Title: Some users may be unable to search mailbox or Address Book content in Exchange Online across connection methods
User impact: Users may be unable to search mailbox or Address Book content in Exchange Online across connection methods.
Current status: We've received support cases indicating that some users can't search mailbox or Address Book content in Exchange Online across connection methods. We're reviewing our service telemetry to isolate the root cause of impact and develop a remediation strategy.
Scope of impact: Some users attempting to search mailbox or Address Book content in Exchange Online across connection methods may be affected. This section may be updated as our investigation progresses.
Next update by: Thursday, September 24, 2026, at 1:00 AM UTC
|
|---|
|
EX1477761 - Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 9 17:43:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 1 11:57:48 2026 |
|---|
| Root Cause: | A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.
|
|---|
| Next Update: | Thursday, October 8, 2026, at 5:30 PM UTC |
|---|
|
Details
| Time: | Thu Oct 1 11:57:48 2026 |
|---|
| Description: | Title: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups
User impact: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups.
More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.
As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.
Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups.
Current status: Our validations are taking longer than initially anticipated as we test the effectiveness of our code fix to ensure it fully remediates impact once deployed. We anticipate beginning deployment by Friday, October 15, 2026, and we aim to provide updates on our timeline to release as we complete our validation process.
Scope of impact: This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.
Start time: Tuesday, June 9, 2026, at 9:43 PM UTC
Root cause: A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.
Next update by: Thursday, October 8, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 12:06:27 2026 |
|---|
| Description: | Title: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups
User impact: Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups.
More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.
As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.
Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups.
Current status: We're deploying a code fix to our internal test environment to validate its efficacy in remediating the impact. We anticipate our validations will be completed by our next scheduled communications update, at which time we'll aim to provide a timeline for the broad deployment.
Scope of impact: This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.
Start time: Tuesday, June 9, 2026, at 9:43 PM UTC
Root cause: A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.
Next update by: Thursday, October 1, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Sep 23 13:55:02 2026 |
|---|
| Description: | Title: Some admins may experience intermittent failures adding or removing members from Exchange Online distribution groups
User impact: Admins may experience intermittent failures adding or removing members from Exchange Online distribution groups.
More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.
As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.
Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups.
Current status: After reviewing reports of impact and provided diagnostic data, we've isolated that when admins are attempting to add or remove members from Exchange Online distribution groups, there's a conflict between a configuration and a recent update which is preventing admins from being able to add or remove users from distribution groups for on-premises configurations. We’re removing the problematic behavior from our code flow with a new code fix. We aim to provide a timeline for code fix deployment to be initiated by our next scheduled update.
Scope of impact: This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.
Start time: Tuesday, June 9, 2026, at 9:43 PM UTC
Root cause: A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.
Next update by: Thursday, September 24, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Sep 23 12:54:27 2026 |
|---|
| Description: | Title: Some admins may experience intermittent failures adding or removing members from Exchange Online distribution groups
User impact: Admins may experience intermittent failures adding or removing members from Exchange Online distribution groups.
More info: Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.
As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.
Current status: We've received reports from a subset of affected admins that the impact scenario documented in EX1466035 is still ongoing and additional analysis is required. We're reviewing the latest reports of impact to further our understanding and to determine our next troubleshooting steps.
Scope of impact: This issue impacts some admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.
Next update by: Wednesday, September 23, 2026, at 6:00 PM UTC
|
|---|
|
MP1478531 - Some admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 21 10:30:00 2026 |
|---|
| End Time: | Thu Oct 1 11:09:37 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 1 11:20:04 2026 |
|---|
| Root Cause: | A recent service update introduced a code discrepancy which caused the Multipurpose Internet Mail Extensions (MIME) parser for Communications Compliance messages to receive a null embedded message, resulting in policy hits not being registered.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 1 11:19:59 2026 |
|---|
| Description: | Title: Some admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview
User impact: Admins may have been unable to review Communications Compliance messages for certain apps in Microsoft Purview.
More info: The following apps were impacted:
- Microsoft Teams
- Microsoft 365 Copilot
Final status: We've confirmed that the backlog of events have been processed and validated that this issue has been remediated using service telemetry.
Scope of impact: This issue impacted some admins who may have been unable to review policy hits in Communications Compliance portal for Microsoft Teams and Microsoft 365 Copilot.
Start time: Monday, September 21, 2026, at 2:30 PM UTC
End time: Thursday, October 1, 2026, at 1:52 PM UTC
Root cause: A recent service update introduced a code discrepancy which caused the Multipurpose Internet Mail Extensions (MIME) parser for Communications Compliance messages to receive a null embedded message, resulting in policy hits not being registered.
Next steps:
- We're continuing our analysis of the impacting code to better identify and prevent similar impact during our testing and validation phases in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 30 12:07:44 2026 |
|---|
| Description: | Title: Some admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview
User impact: Admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview.
More info: The following apps are impacted:
- Microsoft Teams
- Microsoft 365 Copilot
Current status: We're continuing to monitor as the backlog of events are processed, and we anticipate the backlog to be fully processed by Friday, October 2, 2026. We expect most users to be remediated at this time and messages to be reviewable while we finalize processing.
Scope of impact: This issue impacts some admins who may be unable to review policy hits in Communications Compliance portal for Microsoft Teams and Microsoft 365 Copilot. This section may be updated as the investigation progresses.
Start time: Monday, September 21, 2026, at 2:30 PM UTC
Root cause: A recent service update introduced a code discrepancy which caused the Multipurpose Internet Mail Extensions (MIME) parser for Communications Compliance messages to receive a null embedded message, resulting in policy hits not being registered.
Next update by: Thursday, October 1, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Sep 29 13:14:25 2026 |
|---|
| Description: | Title: Some admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview
User impact: Admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview.
More info: The following apps are impacted:
- Microsoft Teams
- Microsoft 365 Copilot
Current status: While most users should see relief and messages are reviewable, we're continuing to monitor as the backlog of events are processed. We expect to have a complete remediation timeline by the next scheduled update.
Scope of impact: This issue impacts some admins who may be unable to review policy hits in Communications Compliance portal for Microsoft Teams and Microsoft 365 Copilot. This section may be updated as the investigation progresses.
Start time: Monday, September 21, 2026, at 2:30 PM UTC
Root cause: A recent service update introduced a code discrepancy which caused the Multipurpose Internet Mail Extensions (MIME) parser for Communications Compliance messages to receive a null embedded message, resulting in policy hits not being registered.
Next update by: Wednesday, September 30, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Sep 28 12:14:55 2026 |
|---|
| Description: | Title: Some admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview
User impact: Admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview.
More info: The following apps are impacted:
- Microsoft Teams
- Microsoft 365 Copilot
Current status: Our efforts to process the backlog of affected messages are ongoing. We anticipate this process will complete, fully remediating impact for all admins, by our next scheduled communication update.
Scope of impact: This issue impacts some admins who may be unable to review policy hits in Communications Compliance portal for Microsoft Teams and Microsoft 365 Copilot. This section may be updated as the investigation progresses.
Start time: Monday, September 21, 2026, at 2:30 PM UTC
Root cause: A recent service update introduced a code discrepancy which caused the Multipurpose Internet Mail Extensions (MIME) parser for Communications Compliance messages to receive a null embedded message, resulting in policy hits not being registered.
Next update by: Tuesday, September 29, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 14:44:41 2026 |
|---|
| Description: | Title: Some admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview
User impact: Admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview.
More info: The following apps are impacted:
- Microsoft Teams
- Microsoft 365 Copilot
Current status: We've isolated that a recent service update introduced a code discrepancy which caused the Multipurpose Internet Mail Extensions (MIME) parser for Communications Compliance messages to receive a null embedded message, resulting in policy hits not being registered. We've rolled back the problematic update and validated from our telemetry that new Communications Compliance messages are being processed as expected. We're processing the backlog of affected messages, and we aim to provide a timeline for the backlog to be fully cleared in our next scheduled update.
Scope of impact: This issue impacts some admins who may be unable to review policy hits in Communications Compliance portal for Microsoft Teams and Microsoft 365 Copilot. This section may be updated as the investigation progresses.
Start time: Monday, September 21, 2026, at 2:30 PM UTC
Root cause: A recent service update introduced a code discrepancy which caused the Multipurpose Internet Mail Extensions (MIME) parser for Communications Compliance messages to receive a null embedded message, resulting in policy hits not being registered.
Next update by: Monday, September 28, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 13:59:19 2026 |
|---|
| Description: | Title: Some admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview
User impact: Admins may be unable to review Communications Compliance messages for certain apps in Microsoft Purview.
More info: The following apps are impacted:
- Microsoft Teams
- Microsoft 365 Copilot
Current status: We've received reports from a subset of affected admins who have noted they aren't seeing policy hits for Microsoft Teams or Microsoft 365 Copilot workloads in Communications Compliance portal. We've isolated a recent service update which we believe may be contributing to impact, and rolling back the update to validate if this action remediates impact.
Scope of impact: This issue impacts some admins who may be unable to review policy hits in in Communications Compliance portal for Microsoft Teams and Microsoft 365 Copilot. This section may be updated as the investigation progresses.
Start time: Monday, September 21, 2026, at 2:30 PM UTC
Next update by: Thursday, September 24, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 13:44:40 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Purview
User impact: We're checking for potential impact to your users.
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.
|
|---|
|
MP1482189 - Users may have been unable to fetch Shared Access Signatures (SAS) keys during mailbox file import in Microsoft Purview
| Status: | serviceRestored |
|---|
| Start Time: | Wed Sep 23 06:12:00 2026 |
|---|
| End Time: | Wed Sep 30 08:30:00 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 1 06:40:27 2026 |
|---|
| Root Cause: | Data Lifecyle Management calls to create new accounts in Azure during PST import SAS key generations were failing for tenants requiring new storage accounts in certain regions.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 1 05:34:57 2026 |
|---|
| Description: | Title: Users may have been unable to fetch Shared Access Signatures (SAS) keys during mailbox file import in Microsoft Purview
User impact: Users may have been unable to fetch SAS keys during mailbox file import in Microsoft Purview Data Lifecycle Management.
More info: This issue specifically affected tenants requiring new storage-account provisioning for Personal Storage Table (PST) imports, and tenants that already have storage accounts provisioned were unaffected.
Users impacted by this event encountered the following error during SAS key generation: "(500) Internal Server Error."
Final status: We've confirmed that impact is remediated following an extended period of monitoring service-side telemetry.
Scope of impact: This issue may have affected any user for tenants provisioning new storage accounts in the following regions: Australia East, Brazil South, Canada Central, Central India, East US 2, France Central, Germany West Central, Indonesia Central, Israel Central, Italy North, Japan East, Korea Central, New Zealand North, North Europe, Norway East, Poland Central, South Africa North, Southeast Asia, Spain Central, Sweden Central, Switzerland North, Taiwan North, UAE North, and UK West.
Start time: Wednesday, September 23, 2026, at 10:12 AM UTC
End time: Wednesday, September 30, 2026, at 12:30 PM UTC
Root cause: Data Lifecyle Management calls to create new accounts in Azure during PST import SAS key generations were failing for tenants requiring new storage accounts in certain regions.
Next steps: We're reviewing performance data and trends on the affected systems to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 30 11:18:22 2026 |
|---|
| Description: | Title: Some users may be unable to fetch Shared Access Signatures (SAS) keys during mailbox file import in Microsoft Purview
User impact: Users may be unable to fetch SAS keys during mailbox file import in Microsoft Purview Data Lifecycle Management.
More info: This issue specifically affects tenants requiring new storage-account provisioning for Personal Storage Table (PST) imports, and tenants that already have storage accounts provisioned are unaffected.
Users impacted by this event encounter the following error during SAS key generation: "(500) Internal Server Error."
Current status: We've completed a fix to correct the import of SAS key generation. Users may need to complete a fresh login and retry twice if the first attempt fails. We're continuing to monitor our service-side telemetry to ensure the stability and effectiveness of the fix.
Scope of impact: This issue may affect any user for tenants provisioning new storage accounts in the following regions: Australia East, Brazil South, Canada Central, Central India, East US 2, France Central, Germany West Central, Indonesia Central, Israel Central, Italy North, Japan East, Korea Central, New Zealand North, North Europe, Norway East, Poland Central, South Africa North, Southeast Asia, Spain Central, Sweden Central, Switzerland North, Taiwan North, UAE North, and UK West.
Root cause: Data Lifecyle Management calls to create new accounts in Azure during PST import SAS key generations are failing for tenants requiring new storage accounts in certain regions.
Next update by: Thursday, October 1, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Sep 29 12:11:34 2026 |
|---|
| Description: | Title: Some users may be unable to fetch Shared Access Signatures (SAS) keys during mailbox file import in Microsoft Purview
User impact: Users may be unable to fetch SAS keys during mailbox file import in Microsoft Purview Data Lifecycle Management.
More info: This issue specifically affects tenants requiring new storage-account provisioning for Personal Storage Table (PST) imports, and tenants that already have storage accounts provisioned are unaffected.
Users impacted by this event encounter the following error during SAS key generation: "(500) Internal Server Error."
Current status: We've identified that the Data Lifecyle Management calls to create new accounts in Azure during PST import SAS key generations are failing for tenants requiring new storage accounts in certain regions. We're in the process of developing and testing a solution to unblock the calls.
Scope of impact: This issue may affect any user for tenants provisioning new storage accounts in the following regions: Australia East, Brazil South, Canada Central, Central India, East US 2, France Central, Germany West Central, Indonesia Central, Israel Central, Italy North, Japan East, Korea Central, New Zealand North, North Europe, Norway East, Poland Central, South Africa North, Southeast Asia, Spain Central, Sweden Central, Switzerland North, Taiwan North, UAE North, and UK West.
Root cause: Data Lifecyle Management calls to create new accounts in Azure during PST import SAS key generations are failing for tenants requiring new storage accounts in certain regions.
Next update by: Thursday, October 1, 2026, at 10:30 AM UTC
|
|---|
|
CP1483845 - Some users may not receive responses from their Microsoft 365 Copilot agents within Microsoft PowerPoint
| Status: | serviceRestored |
|---|
| Start Time: | Wed Sep 30 17:00:00 2026 |
|---|
| End Time: | Wed Sep 30 19:23:59 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Sep 30 19:24:57 2026 |
|---|
| Root Cause: | A configuration issue contained within a recent service update was causing the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 30 19:24:54 2026 |
|---|
| Description: | Title: Some users may not receive responses from their Microsoft 365 Copilot agents within Microsoft PowerPoint
User impact: Users may have not received responses from their Copilot agents within PowerPoint.
Final status: Following the completion of our fix deployment process and an extended period of monitoring the service health telemetry, we’ve verified that impact has been fully resolved.
Scope of impact: Some users who utilized Copilot agents within PowerPoint may have been impacted.
Start time: Wednesday, September 30, 2026, at 9:00 PM UTC
End time: Wednesday, September 30, 2026, at 11:11 PM UTC
Root cause: A configuration issue contained within a recent service update was causing the impact.
Next steps: - We’re continuing to analyze how the recent service update was applied to understand why the potential for impact wasn't caught during the update testing and validation phase. These actions will help us to clarify what actions we can take to ensure that similar impact doesn't occur in the future and to continue our ongoing mission to improve the resilience of our service for all Microsoft 365 Copilot users.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 30 18:39:45 2026 |
|---|
| Description: | Title: Some users may not receive responses from their Microsoft 365 Copilot agents within Microsoft PowerPoint
User impact: Users may not receive responses from their Copilot agents within PowerPoint.
Current status: We've identified that a configuration issue contained within a recent service update is causing the impact. We've developed a fix to address the configuration issue, which we're deploying to the affected environment. We anticipate the fix will complete deployment and remediate the impact by our next scheduled communications update.
Scope of impact: Some users who utilize Copilot agents within PowerPoint may be impacted. This section may be updated as our investigation continues.
Start time: Wednesday, September 30, 2026, at 9:00 PM UTC
Root cause: A configuration issue contained within a recent service update is causing the impact.
Next update by: Thursday, October 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Sep 30 18:26:56 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1483357 - Users may encounter an error when accessing the context menu in the classic experience within SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Wed Sep 30 08:37:03 2026 |
|---|
| End Time: | Wed Sep 30 11:58:18 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Access Services |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 30 14:54:44 2026 |
|---|
| Root Cause: | A recent update to the rendering mechanism used when accessing the context menu in the classic experience within SharePoint Online contained a code issue, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 30 12:00:30 2026 |
|---|
| Description: | Title: Users may encounter an error when accessing the context menu in the classic experience within SharePoint Online
User impact: Users may have encountered an error when accessing the context menu in the classic experience within SharePoint Online.
Final status: We’ve reverted the update to the last known good version and confirmed with affected users that this has restored context menu access in the classic SharePoint Online experience. Users with existing browser sessions may have to refresh the page to see the fixed behavior. This also confirms that a recent update to the rendering mechanism used when accessing the context menu in the classic experience within SharePoint Online contained a code issue, resulting in impact.
Scope of impact: Impact was specific to some users attempting to access the context menu in the classic experience within SharePoint Online.
Start time: Wednesday, September 30, 2026, at 3:57 AM UTC
End time: Wednesday, September 30, 2026, at 2:37 PM UTC
Root cause: A recent update to the rendering mechanism used when accessing the context menu in the classic experience within SharePoint Online contained a code issue, resulting in impact.
Next steps:
- We're reviewing and improving our service update validation procedure to prevent similar issues from occurring in the future.
|
|---|
|
| Time: | Wed Sep 30 10:42:01 2026 |
|---|
| Description: | Title: Users may encounter an error when accessing the context menu in the Classic experience within SharePoint Online
User impact: Users may encounter an error when accessing the context menu in the Classic experience within SharePoint Online.
Current status: We’ve identified a recent update as the potential cause of impact, which is preventing users in the SharePoint Classic experience from being redirected when accessing the context menu. We’re reverting the update to the last known good version to restore functionality and validate our root cause theory.
Scope of impact: Impact is specific to some users attempting to access the context menu in the Classic experience within SharePoint Online.
Next update by: Wednesday, September 30, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Sep 30 08:45:01 2026 |
|---|
| Description: | Title: Users may encounter an error when accessing the context menu in the Classic experience within SharePoint Online
User impact: Users may encounter an error when accessing the context menu in the Classic experience within SharePoint Online.
Current status: We’re reviewing recent updates that we suspect may be contributing to the impact and are working to formulate a mitigation plan.
Scope of impact: Impact is specific to some users attempting to access the context menu in the Classic experience within SharePoint Online.
Next update by: Wednesday, September 30, 2026, at 3:00 PM UTC
|
|---|
|
CP1447275 - Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Jul 9 13:33:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 30 14:33:14 2026 |
|---|
| Root Cause: | The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
|
|---|
| Next Update: | Wednesday, October 7, 2026, at 7:30 PM UTC |
|---|
|
Details
| Time: | Wed Sep 30 14:33:03 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We’re continuing our efforts to reproduce the impact internally to gather additional diagnostic data to aid our ongoing investigation into why the impact is persisting in specific environments and formulate an appropriate remediation action.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
Next update by: Wednesday, October 7, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Sep 23 14:01:42 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: The process of collecting an internal reproduction of impact is taking longer than anticipated, but we're actively pursuing this reproduction in order to assist our ongoing investigation into why this impact is persisting in specific environments.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
Next update by: Wednesday, September 30, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Sep 23 14:01:40 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: The process of collecting an internal reproduction of impact is taking longer than anticipated, but we're actively pursuing this reproduction in order to assist our ongoing investigation into why this impact is persisting in specific environments.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
Next update by: Wednesday, September 30, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Sep 21 14:34:10 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We're progressing with our internal reproduction of the impact within our internal testing environment. This data is expected to provide further clarity on the impact scenario and identify our next troubleshooting steps for remediating the impact.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
Next update by: Wednesday, September 23, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Sep 17 13:57:01 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: Based on our internal testing, we've determined that the impact is still occurring. We're continuing to reproduce the impact using our internal testing environment to provide us further clarity on the impact scenario, so that we can develop our next mitigation strategy.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
Next update by: Monday, September 21, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 17:33:25 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We're continuing to reach out to impacted users to confirm if impact is remediated after the deployment of our fix.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
Next update by: Thursday, September 17, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 15:36:18 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We've created and deployed the fix and we're confirming with impacted users if the issue is resolved.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
Next update by: Wednesday, September 16, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Sep 15 14:02:41 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We’re continuing our efforts to develop and evaluate a fix for the Unified store accessed through Outlook. We’ll provide a resolution timeline once available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
Next update by: Wednesday, September 16, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Sep 14 14:44:44 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We're continuing to develop and evaluate a fix for the Unified store accessed through Outlook, and we aim to provide a timeline for when fix development will be completed as soon as possible.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store or Unified store accessed through Outlook contains incorrect URL redirection and is causing impact.
Next update by: Tuesday, September 15, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Sep 9 14:15:51 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We've updated the More Info, Scope of impact, and Root cause sections as the impact may also occur within the Unified store accessed through Outlook. We've deployed a permanent fix for the Microsoft 365 app store, and our internal testing has confirmed the impact is no longer occurring in this scenario. We're developing a fix for the Unified store accessed through Outlook, and we'll aim to provide a timeline for these fixes to deploy by our next scheduled communications update.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store, or the Unified store accessed through Outlook may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store, or Unified store accessed through Outlook contains the incorrect URL redirection and is causing impact.
Next update by: Monday, September 14, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Sep 8 14:40:28 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We're continuing to validate and evaluate the effectiveness of our permanent fix prior to initiating deployment to affected users. We recommend users continue to utilize the Copilot agent store while we troubleshoot our remediation steps, and we’ll provide an updated timeline as soon as one becomes available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
Next update by: Wednesday, September 9, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 15:16:40 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: After further review, we've determined that our permanent fix for this issue needs to undergo additional validations, meaning it will take longer than originally project to fully resolve this event. We recommend users continue to utilize the Copilot agent store while we troubleshoot our remediation steps, and we will provide an updated timeline as soon as one becomes available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
Next update by: Tuesday, September 8, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Aug 19 14:00:01 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: Our projection for deployment completion, based on the rate of progress, indicates that the process will be nearing completion by the end of August, but may require additional time to fully saturate. We're continuously monitoring the deployment and will provide an updated timeline for remediation as one becomes available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 5:33 PM UTC
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
Next update by: Monday, August 31, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Aug 12 14:18:59 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We’ve developed and validated the fix to correct the URL redirection and have initiated deployment to the affected environments. Based on our current estimates, we suspect that the deployment will take several weeks to complete, with completion expected by Monday, August 31, 2026. We’re continuing to monitor the progress of the deployment and will provide progress updates as they become available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
Next update by: Wednesday, August 19, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 14:11:35 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We’re continuing to develop a fix to correct the URL redirection, and we’ll provide a resolution timeline once available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
Next update by: Wednesday, August 12, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 13:46:03 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We've identified that the "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact. We're developing a fix to correct the URL redirection and will provide an update on its timeline as one becomes available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
Next update by: Tuesday, August 11, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 12:25:59 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We're continuing to review the details provided by a subset of affected users, including screenshots of the impact, so that we can investigate the source of the impact.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
|
|---|
|
| Time: | Tue Aug 4 11:04:09 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We're reviewing the screenshots provided by a subset of affected users to gain further understanding of the impact and to determine the next steps to isolate the root cause.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, August 4, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 10:51:04 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1441488 - Some users may see unwanted add-ins appearing automatically across all Outlook clients
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jul 17 06:26:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 30 13:41:42 2026 |
|---|
| Root Cause: | A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
|
|---|
| Next Update: | Monday, October 5, 2026, at 7:00 PM UTC |
|---|
|
Details
| Time: | Wed Sep 30 13:41:42 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing.
Current status: Our deployment is taking longer than initially expected and we now anticipate deployment to be fully completed by Monday, October 5, 2026. We anticipate the majority of users to be remediated at this time while we complete our deployment.
Scope of impact: Impact may occur for some users that are viewing their add-ins across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Estimated time to resolve: We anticipate impact to be resolved by Monday, October 5, 2026.
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Monday, October 5, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Sep 28 13:14:55 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing.
Current status: Our deployment is ongoing, and more users may see remediation as it continues. Based on the current rate of progress, we anticipate that this may fully complete deployment by Friday, October 2, 2026. We'll provide further updates on this timeline for remediation with our next scheduled communication update.
Scope of impact: Impact may occur for some users that are viewing their add-ins across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Estimated time to resolve: We anticipate impact to be resolved by Friday, October 2, 2026.
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Wednesday, September 30, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 13:33:38 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing.
Current status: Our deployment is progressing across affected environments, and we anticipate some users to start seeing remediation at this time. We anticipate impact to be fully resolved by Monday, October 5, 2026.
Scope of impact: Impact may occur for some users that are viewing their add-ins across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Estimated time to resolve: We anticipate impact to be resolved by Monday, October 5, 2026.
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Monday, September 28, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Sep 22 14:19:52 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing.
Current status: We've completed our final validations in our internal testing environment and are proceeding with enabling the fix for all affected users. We anticipate some users to start seeing remediation, and we anticipate impact to be fully resolved by Monday, October 5, 2026.
Scope of impact: Impact may occur for some users that are viewing their add-ins across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Estimated time to resolve: We anticipate impact to be resolved by Monday, October 5, 2026.
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Thursday, September 24, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Sep 21 13:05:50 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing.
Current status: As our deployment of the fix is nearing completion, we're performing final validations in our internal testing environment to confirm its efficacy before enabling for all affected users.
Scope of impact: Impact may occur for some users that are viewing their add-ins across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Tuesday, September 22, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 13:00:19 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing.
Current status: Our fix deployment is approximately 65 percent complete, and we've validated it remains on track to complete by Monday, September 21, 2026.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Monday, September 21, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 13:00:09 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing.
Current status: Our fix deployment is approximately 65 percent complete, and we've validated it remains on track to complete by Monday, September 21, 2026.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Monday, September 21, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Sep 11 13:14:57 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing.
Current status: We're deploying our permanent fix to the affected environments, and we currently estimate the deployment will complete by Monday, September 21, 2026. We'll continue to monitor the deployment to ensure that our remediation timeline is accurate.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Wednesday, September 16, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 13:22:22 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed. To bypass this issue, admins can run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that are unintentionally appearing.
Current status: We’ve verified with a subset of affected users that performing the identified workaround successfully mitigates the impact. We’re preparing a permanent fix for deployment, which we expect will take several weeks to saturate. We’ll provide a resolution timeline once available.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Friday, September 11, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 13:02:27 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're coordinating with a subset of affected users who are performing the actions needed to remediate the impact to ensure that running the command and installing previously installed apps fully resolves the issue.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Friday, September 4, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 13:02:21 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're coordinating with a subset of affected users who are performing the actions needed to remediate the impact to ensure that running the command and installing previously installed apps fully resolves the issue.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Friday, September 4, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Aug 26 14:26:00 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: The fix deployment has completed. We've determined that this fix is viable for all affected users but to see the impact remediated, users will need to run the following command: "Set-App -Identity "" -DefaultStateForUser Disabled -OrganizationApp -PrivateCatalog". After running this command all users who previously installed add-ins may need to install them again. We're providing time for affected users to run this command and remediate impact before we consider this resolved.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 13:23:14 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: Our fix deployment timeline reports that our solution will require a bit longer than previously expected. In parallel, we've determined that the deployment will not be viable for all affected users, and that additional mitigation efforts will be required. We're further analyzing our potential long-term solutions for remediating the impact.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Wednesday, August 26, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Aug 19 12:58:57 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: Based on the rate of the deployment progression, we now anticipate the fix will be available on August 22, 2026. We're continuing to monitor as the process nears completion and will begin reaching out to a subset of affected users once the fix is fully saturated to begin verifying impact remediation.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Monday, August 24, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Aug 12 13:29:56 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We’re continuing to monitor the progress of the fix to ensure it propagates successfully. We still suspect this will complete by Wednesday, August 26, 2026, and we’ll provide further updates as they become available.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Wednesday, August 19, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 13:39:36 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We’ve developed and begun deploying the fix to the affected environments. We’re monitoring its progress to ensure it propagates successfully, and based on our current estimates, we expect deployment to complete by Wednesday, August 26, 2026. We’ll provide further resolution updates as they become available.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Wednesday, August 12, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Aug 10 12:54:57 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're developing a fix aimed at correcting the affected portion of Exchange Online add-in sync pipeline that’s resulting in impact, and we’ll provide a timeline for its validation and deployment as one becomes available.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Tuesday, August 11, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Aug 6 12:42:27 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We've identified that a portion of the Exchange Online add-in synchronization pipeline isn't processing add-in state information as expected, resulting in incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available. We're continuing to validate with a subset of affected users whether removing and re-adding an add-in or deploying a test add-in to force synchronization can serve as a viable workaround while our investigation into the underlying cause continues in effort to isolate the source of the issue and identify an appropriate remediation action.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in synchronization pipeline isn't processing add-in state information as expected, resulting in incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available.
Next update by: Monday, August 10, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Aug 5 15:21:21 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're continuing to validate with a subset of affected users whether removing and re-adding an add-in or deploying a test add-in to force sync can serve as a viable workaround while the root cause investigation remains ongoing.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Thursday, August 6, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 15:57:10 2026 |
|---|
| Description: | Title: Users see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We successfully reproduced the issue internally and found that triggering an add-in sync caused the unwanted add-ins to disappear. We are currently validating, with a subset of affected users, whether removing and re-adding an add-in or deploying a test add-in to force sync can serve as a viable workaround while the root cause investigation remains ongoing.
Scope of impact: Your organization is affected by this event, and all users see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Wednesday, August 5, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Aug 3 13:37:54 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're continuing our efforts to reproduce impact within our internal testing environment while reviewing HAR logs alongside any recent updates that may be causing or contributing to impact, to isolate this issue's underlying cause.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Tuesday, August 4, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Jul 31 13:54:55 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We received feedback from a subset of affected users that the potential temporary remediation was insufficient. We're continuing to review provided HAR logs while we reproduce the impact using our internal testing tenant to gain further understanding of the issue.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Monday, August 3, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jul 30 18:05:58 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We've identified a potential temporary remediation while we work towards long-term resolution. We're reaching out to validate this temporary remediation with a portion of the impacted users to determine if it will be an effective solution.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Friday, July 31, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jul 30 13:22:14 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're reviewing newly collected HAR logs provided by a subset of affected users to aid us in our root cause investigation. In the meantime, we're developing a short term mitigation plan to provide relief while our investigation is ongoing.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Thursday, July 30, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 16:17:19 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: Our investigation of the conflicting add-in configurations is ongoing, and we're reaching out to your representatives for additional contextual data and fresh HTTP Archive (HAR) files collected from both Outlook desktop and Outlook on the web clients for further analysis.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Thursday, July 30, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 13:24:56 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're continuing to analyze conflicting add-in configurations which may be contributing to impact along with our continued analysis of relevant recent changes to the affected configurations to isolate the underlying source of impact.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Wednesday, July 29, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jul 28 17:33:47 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We've identified conflicting add-in configurations which may be contributing to impact. We're expanding our investigation into recent relevant changes to the configurations to confirm the root cause.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Wednesday, July 29, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jul 28 12:00:13 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're analyzing the properties being utilized to display add-ins for an affected user along with our continued analysis of the HAR file to isolate potential sources of impact.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Tuesday, July 28, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jul 28 11:29:32 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're analyzing HTTP Archive format (HAR) traces provided by your representatives and reviewing support cases to further our understanding of the current impact scenario and to assist with determining our next troubleshooting steps.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Tuesday, July 28, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Jul 28 11:15:49 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
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.
|
|---|
|
CP1482420 - Users may encounter failures or may be unable to use PowerPoint agents in Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 29 15:17:10 2026 |
|---|
| End Time: | Tue Sep 29 16:40:17 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Sep 29 16:50:47 2026 |
|---|
| Root Cause: | An increase in request traffic to the portion of infrastructure responsible for facilitating PowerPoint agents prevented the service from being able to handle the traffic effectively and caused impact
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 29 16:50:43 2026 |
|---|
| Description: | Title: Users may encounter failures or may be unable to use PowerPoint agents in Microsoft 365 Copilot
User impact: Users may have encountered failures or may have been unable to use PowerPoint agents in Copilot.
Final status: We've identified that an increase in request traffic to the portion of infrastructure responsible for facilitating PowerPoint agents prevented the service from being able to handle the traffic effectively and caused impact. We've rebalanced the request traffic and confirmed through service health telemetry that the impact is remediated as a result.
Scope of impact: Any user that attempted to use PowerPoint agents in Copilot may have been affected.
Start time: Tuesday, September 29, 2026, at 6:30 PM UTC
End time: Tuesday, September 29, 2026, at 8:15 PM UTC
Root cause: An increase in request traffic to the portion of infrastructure responsible for facilitating PowerPoint agents prevented the service from being able to handle the traffic effectively and caused impact
Next steps:
- We're reviewing the source of the request traffic to identify the reason it increased so that we can determine how to prevent similar impact to PowerPoint agents from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 29 15:31:24 2026 |
|---|
| Description: | Title: Users may encounter failures or may be unable to use PowerPoint agents in Microsoft 365 Copilot
User impact: Users may encounter failures or may be unable to use PowerPoint agents in Copilot.
Current status: Our service health monitoring alerted us to failures occurring when users attempt to use PowerPoint agents in Copilot. We're reviewing the failures to identify their source, so that we can determine how to remediate the impact.
Scope of impact: Any user attempting to use PowerPoint agents in Copilot may be affected.
Next update by: Tuesday, September 29, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Sep 29 15:20:07 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MP1471821 - Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Sep 14 12:41:47 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Sep 29 12:35:01 2026 |
|---|
| Root Cause: | A service update which intended to add operations with larger data sizes introduced a code error, causing size limitation issues.
|
|---|
| Next Update: | Tuesday, October 6, 2026, at 6:00 PM UTC |
|---|
|
Details
| Time: | Tue Sep 29 12:35:01 2026 |
|---|
| Description: | Title: Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview
User impact: Admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview.
More info: Impact is limited to Communications Compliance policies with more than four classifiers.
We advise admins to keep classifiers to a maximum of four during this time and we anticipate the limit to be remediated by Monday, October 5, 2026.
Current status: We've continuing to monitor the deployment of our fix which remains scheduled to complete by Monday, October 5, 2026.
Scope of impact: Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview with more than four classifiers. This section may be updated as the investigation progresses.
Estimated time to resolve: We anticipate impact to be remediated by Monday, October 5, 2026.
Root cause: A service update which intended to add operations with larger data sizes introduced a code error, causing size limitation issues.
Next update by: Tuesday, October 6, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 22 12:44:05 2026 |
|---|
| Description: | Title: Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview
User impact: Admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview.
More info: Impact is limited to Communications Compliance policies with more than four classifiers.
We advise admins to keep classifiers to a maximum of four during this time and we anticipate the limit to be remediated by Monday, October 5, 2026.
Current status: We've completed internal validations for our solution and have begun its deployment. Our fix deployment timeline projects the deployment will remediate the impact by Monday, October 5, 2026. Until this time, we advise users to keep Communications Compliance policies limited to under four classifiers in order to avoid impact.
Scope of impact: Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview with more than four classifiers. This section may be updated as the investigation progresses.
Estimated time to resolve: We anticipate impact to be remediated by Monday, October 5, 2026.
Root cause: A recent update introduced operations with larger data size included a code error, causing size limitation issues.
Next update by: Tuesday, September 29, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Sep 14 12:47:32 2026 |
|---|
| Description: | Title: Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview
User impact: Admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview.
More info: Impact is limited to Communications Compliance policies with more than four classifiers.
We advise admins to keep classifiers to a maximum of four during this time and we anticipate the limit to be remediated by Monday, October 5, 2026.
Current status: We've received reports from a subset of affected admins who have reported receiving size limitation failures when creating or updating Communications Compliance policies in Microsoft Purview. We've isolated that a recent update introduced operations with larger data size included a code issue, causing size limitation issues. We've created a code fix to address the issue, which we anticipate being fully deployed by Monday, October 5, 2026. During this time, we advise users to keep Communications Compliance policies limited to under four classifiers in order to avoid impact.
Scope of impact: Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview with more than four classifiers. This section may be updated as the investigation progresses.
Estimated time to resolve: We anticipate impact to be remediated by Monday, October 5, 2026.
Root cause: A recent update introduced operations with larger data size included a code error, causing size limitation issues.
Next update by: Monday, September 28, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Sep 14 12:42:38 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Purview
User impact: We're checking for potential impact to your users.
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.
|
|---|
|
PC1481685 - Microsoft Copilot Studio - Agent intermittently failed to respond in channels
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 28 14:50:00 2026 |
|---|
| End Time: | Tue Sep 29 02:50:00 2026 |
|---|
| Service: | Microsoft Copilot (Power Platform) |
|---|
| Feature Group: | Microsoft Copilot Studio |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 29 04:51:27 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 29 04:51:27 2026 |
|---|
| Description: | Title: Microsoft Copilot Studio - Agent intermittently failed to respond in channels
User impact: Agent intermittently failed to respond in channels.
More Info: Impacted users received a system error.
Final Status: After our investigation, we determined that a recent service deployment introduced a misconfiguration, leading to increased traffic and throttling on a portion of infrastructure supporting agent conversations. We performed an override to disable the previous deployment and after a period of monitoring, we confirmed that agent functionality in Microsoft Copilot Studio has recovered.
This is the final update on the incident.
Preliminary Root Cause: A recent service deployment introduced a misconfiguration, leading to increased traffic and throttling on a portion of infrastructure supporting agent conversations.
Next Steps: We're reviewing our configuration procedures to find ways to prevent this problem from happening again.
|
|---|
|
CW1470765 - Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 22 18:07:00 2026 |
|---|
| End Time: | Mon Sep 28 20:12:26 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 28 21:08:36 2026 |
|---|
| Root Cause: | A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, which resulted in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 28 20:12:09 2026 |
|---|
| Description: | Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
User impact: Users' Exchange Online email messages may not have been retrieved when prompting Copilot Chat.
More info: Some Exchange Online email messages between July 22, 2026, and the date were not retrieved by Copilot Chat when prompted. While the affected email messages were being indexed to the semantic index model, users could've prompted Copilot Chat using exact wording to retrieve the email messages.
Final status: We determined that the deployment fully saturated the environment and after a period of monitoring, we confirmed that the impact was remediated.
Scope of impact: Some users who attempted to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and the present were impacted.
Start time: Wednesday, July 22, 2026, at 10:07 PM UTC
End time: Monday, September 28, 2026, at 5:08 PM UTC
Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, which resulted in the impact.
Next steps: We're investigating why the misconfiguration wasn't identified during the testing and validation phases of the service change to help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 17 21:30:08 2026 |
|---|
| Description: | Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat.
More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages.
Current status: The aforementioned deployment has saturated over 50% of the affected infrastructure and we've confirmed that some users are beginning to see remediation as the fix continues to propagate. Additionally, we expect that the remainder of the affected users will have received the fix deployment prior to our next scheduled update, at which point we'll monitor service health telemetry to ensure that impact is remediated and no additional mitigative actions will be required.
Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, July 22, 2026, at 10:07 PM UTC
Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact.
Next update by: Tuesday, September 29, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Sat Sep 12 21:19:23 2026 |
|---|
| Description: | Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat.
More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages.
Current status: The initial 10% of the deployment has saturated throughout the affected infrastructure and has proven successful. We’re now in the process of deploying another 40% of the fix while we continue monitoring service health. Additionally, we expect that some users may be incrementally remediated as the deployment continues to saturate throughout the affected environment.
Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, July 22, 2026, at 10:07 PM UTC
Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact.
Next update by: Sunday, September 20, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Sat Sep 12 12:09:56 2026 |
|---|
| Description: | Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat.
More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages.
Current status: We’re continuing to monitor the initial 10 percent deployment of our secondary fix, which is progressing as expected. We’ll continue monitoring service health and deployment progress before proceeding with the next phase and provide a timeline for full remediation once available.
Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, July 22, 2026, at 10:07 PM UTC
Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact.
Next update by: Sunday, September 13, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Sep 11 22:12:04 2026 |
|---|
| Description: | Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat.
More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages.
Current status: We've validated our secondary fix and begun the first 10 percent of deployment. We'll monitor this initial deployment process in order to determine the estimated timeline for full remediation and provide those details as soon as they become available.
Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, July 22, 2026, at 10:07 PM UTC
Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact.
Next update by: Saturday, September 12, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Sep 11 18:27:43 2026 |
|---|
| Description: | Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat.
More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages.
Current status: We're continuing to test the efficacy of our secondary fix to repair the affected email messages and will provide a timeline for the validation as one becomes available.
Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, July 22, 2026, at 10:07 PM UTC
Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact.
Next update by: Saturday, September 12, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Fri Sep 11 16:48:31 2026 |
|---|
| Description: | Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat.
More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages.
Current status: We've confirmed that all new email messages are being indexed correctly as a result of our fix. We're testing our secondary fix with a subset of affected user mailboxes to repair the email messages that weren't indexed, so that we can validate its efficacy before we apply it to all affected users.
Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, July 22, 2026, at 10:07 PM UTC
Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact.
Next update by: Friday, September 11, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Sep 11 14:56:59 2026 |
|---|
| Description: | Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat.
More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages.
Current status: The fix to correct the code and ensure that future email messages will be indexed correctly is being deployed. In tandem we're repairing the affected email messages and indexing them to fully remediate the impact.
Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted.
Start time: Wednesday, July 22, 2026, at 10:07 PM UTC
Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact.
Next update by: Friday, September 11, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Sep 11 14:19:07 2026 |
|---|
| Description: | Title: Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
User impact: Users' Exchange Online email messages may not be retrieved when prompting Copilot Chat.
More info: Some Exchange Online email messages between July 22, 2026, and today may not be retrieved by Copilot Chat when prompted. While we index the affected email messages to our semantic index model, users can prompt Copilot Chat using exact wording to retrieve the email messages.
Current status: We've identified that a service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model. We're developing multiple fixes to ensure new email messages would be indexed and to index the email messages that were missed during the impact window.
Scope of impact: Some users that are attempting to prompt Copilot Chat to retrieve details from Exchange Online email messages between July 22, 2026, and today may be impacted.
Start time: Wednesday, July 22, 2026, at 10:07 PM UTC
Root cause: A service change introduced a misconfiguration that prevented Exchange Online email messages between July 22, 2026, and today from being indexed by our semantic index model, causing impact.
Next update by: Friday, September 11, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Sep 11 13:51:24 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot Chat
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1475580 - Some users may be unable to access or use Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Sep 21 09:00:00 2026 |
|---|
| End Time: | Mon Sep 21 09:49:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Sep 28 20:12:25 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 28 20:12:25 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Sep 23 15:06:28 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Sep 21 11:32:45 2026 |
|---|
| Description: | Title: Some users may be unable to access or use Microsoft Teams
User impact: Users may have been unable to access or use Microsoft Teams.
More Info: Impact included but may have not been limited to, audio and video calls, joining or initiating calls, and other calling-related functionality.
Final status: Our review confirmed our automated recovery systems rerouted traffic to healthy infrastructure and the service has recovered to healthy levels.
Scope of impact: Impact was specific to some users whose connection requests were routed through Germany, the United Kingdom and the United States who were unable to access or use Microsoft Teams.
Preliminary root cause: We identified an issue affecting a subset of connection-processing workflows within Microsoft Teams infrastructure. The affected workflows recovered and impact reports subsequently declined. We're continuing to investigate what initially led to impact and will provide more information in our Post-Incident Report.
Final status: Impact reports have subsided and our review of service health indicates that the service has recovered to expected levels. We are continuing to monitor telemetry closely to verify service stability and sustained recovery.
Scope of impact: Impact was specific to some users whose connection requests are routed through Germany, United Kingdom and the United States who were unable to access or use Microsoft Teams.
Start time: Monday, September 21, 2026, at 1:00 PM UTC
End time: Monday, September 21, 2026, at 1:49 PM UTC
Preliminary root cause: We identified an issue affecting a subset of connection-processing workflows within Microsoft Teams infrastructure. The affected workflows recovered and impact reports subsequently declined. We're continuing to investigate what initially led to impact and will provide more information in our Post-Incident Report.
Next steps:
- We’re evaluating our core service configurations to prevent the recurrence of similar impact in the future. In addition, we're further reviewing our monitoring systems to ensure we identify and are expediently alerted to these types of scenarios.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Sep 21 10:27:59 2026 |
|---|
| Description: | User impact reports are decreasing, however, we continue to investigate and validate whether this trend reflects sustained recovery. We're continuing to narrow our investigation to the infrastructure component responsible for processing affected connection requests and are correlating diagnostic telemetry across impacted regions.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, September 21, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Sep 21 10:01:31 2026 |
|---|
| Description: | Title: Some users may be unable to access or use Microsoft Teams
User impact: Users may be unable to access or use Microsoft Teams.
More Info: Impact includes, but may not be limited to, audio and video calls, joining or initiating calls, and other calling-related functionality.
Current status: We're analyzing a portion of the infrastructure responsible for processing connection requests. In parallel, we're reviewing diagnostic data to determine the source of impact and identify a remediation plan.
Scope of impact: Impact is specific to some users whose connection requests are routed through Germany, United Kingdom and the United States who are unable to access or use Microsoft Teams.
Next update by: Monday, September 21, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Sep 21 09:44:44 2026 |
|---|
| Description: | Title: Some users may be unable to access or use Microsoft Teams
User impact: Users may be unable to access or use Microsoft Teams.
Current status: We're reviewing service monitoring telemetry and system logs to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Impact is specific to some users in Germany, United Kingdom and the United States who are unable to access or use Microsoft Teams.
Next update by: Monday, September 21, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Sep 21 09:22:34 2026 |
|---|
| Description: | Title: Some users may be unable to access or use Microsoft Teams
User impact: Users may be unable to access or use Microsoft Teams.
Current status: We're reviewing service monitoring telemetry and system logs to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Impact is specific to some users in Germany, United Kingdom and the United States who are unable to access or use Microsoft Teams.
Next update by: Monday, September 21, 2026, at 3:30 PM UTC
|
|---|
|
EX1479349 - Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Sep 25 11:52:36 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Sep 28 19:56:12 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Tuesday, October 6, 2026, at 1:00 AM UTC |
|---|
|
Details
| Time: | Mon Sep 28 19:56:12 2026 |
|---|
| Description: | Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online
User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.
More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.
Current status: We've initialized our fix deployment to the affected environment and anticipate the impact should be fully remediated by our next scheduled update.
Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.
Next update by: Tuesday, October 6, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Sep 25 20:24:06 2026 |
|---|
| Description: | Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online
User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.
More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.
Current status: We've completed the validation of our planned fixes and are completing the final stages to prepare them for deployment. We anticipate that users will see progressive relief beginning Monday, September 28, 2026, up to our planned remediation date of Friday, October 2, 2026.
Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.
Next update by: Tuesday, September 29, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Sep 25 18:33:44 2026 |
|---|
| Description: | Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online
User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.
More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.
Current status: We're conducting verification and validation testing on our proposed remediation to ensure that it will safely and effectively remediate this issue.
Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online. This information may be updated as our investigation continues.
Next update by: Saturday, September 26, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Sep 25 16:57:43 2026 |
|---|
| Description: | Title: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online
User impact: Users may be unable to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.
More info: As a temporary alternative, impacted users may reply or reply all to email messages through user inboxes.
Current status: We've identified a recent code change which we believe may be responsible for this issue and are developing a targeted fix to verify.
Scope of impact: This issue impacts any user attempting to reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.
Next update by: Friday, September 25, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Sep 25 12:22:57 2026 |
|---|
| Description: | Title: Users can't reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online
User impact: Users can't reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online.
Current status: We're reviewing support case details to better understand the impact scenario and determine our next steps.
Scope of impact: Your organization is impacted by this event and all users attempting to reply to email messages sent to Microsoft 365 groups are affected.
Next update by: Friday, September 25, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Sep 25 11:56:45 2026 |
|---|
| Description: | Title: Users can't reply or reply-all to email messages sent to Microsoft 365 groups in Exchange Online
User impact: Users can't reply or reply-all to email messages sent to Microsoft 365 groups 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.
|
|---|
|
MV1481028 - Users may not be able to access Microsoft Viva Glint
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 28 17:48:07 2026 |
|---|
| End Time: | Mon Sep 28 19:21:22 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Glint |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Sep 28 19:22:25 2026 |
|---|
| Root Cause: | A combination of two simultaneous deployments led to a misconfiguration which resulted in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 28 19:22:22 2026 |
|---|
| Description: | Title: Users may not be able to access Microsoft Viva Glint
User impact: Users may have not been able to access Viva Glint.
Final status: We determined that a combination of two simultaneous deployments led to a misconfiguration which resulted in this impact. We halted one of the responsible deployments and confirmed that this resolved the issue by monitoring service health data.
Scope of impact: This event impacted any user attempting to access Viva Glint.
Start time: Monday, September 28, 2026, at 9:15 PM UTC
End time: Monday, September 28, 2026, at 10:29 PM UTC
Root cause: A combination of two simultaneous deployments led to a misconfiguration which resulted in this impact.
Next steps: - We're reviewing the responsible deployments to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Mon Sep 28 18:16:12 2026 |
|---|
| Description: | Title: Users may not be able to access Microsoft Viva Glint
User impact: Users may not be able to access Viva Glint.
Current status: We're reviewing service logs to isolate the source of this impact and an expedient mitigation to restore service.
Scope of impact: This event impacts any user attempting to access Viva Glint. This information may be updated as our investigation continues.
Start time: Monday, September 28, 2026, at 9:15 PM UTC
Next update by: Monday, September 28, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Mon Sep 28 17:49:57 2026 |
|---|
| Description: | Title: Users may not be able to access Microsoft Viva Glint
User impact: Users may not be able to access Viva Glint.
Current status: We're investigating a potential issue with Viva Glint and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CW1478470 - Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot Chat or Copilot Notebooks
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 21 22:50:00 2026 |
|---|
| End Time: | Mon Sep 28 14:18:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 28 17:43:16 2026 |
|---|
| Root Cause: | A licensing mismatch in the request flow was causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 28 17:42:45 2026 |
|---|
| Description: | Title: Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot Chat or Copilot Notebooks
User impact: Users may have been unable to access or receive prompt responses with Copilot Chat or Copilot Notebooks.
More info: Users may have experienced failing requests for the following scenarios:
- Image generation requests in Copilot Chat
- Prompt generation requests in Copilot Chat
- Failures when attempting to access or view Copilot Notebooks
Final status: We've completed deployment of our code change to address a licensing mismatch in the request flow. After completing an internal monitoring period, we've validated that impact is remediated.
Scope of impact: This incident impacted some users attempting to generate images or prompts using Copilot Chat or accessing Copilot Notebooks.
Start time: Tuesday, September 22, 2026, at 2:50 AM UTC
End time: Sunday, September 27, 2026, at 6:18 PM UTC
Root cause: A licensing mismatch in the request flow was causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
Next steps:
- We're analyzing the problematic request flow to isolate how the licensing mismatch was introduced into our service and to validate what actions we can take to prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 25 13:40:28 2026 |
|---|
| Description: | Title: Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot Chat or Copilot Notebooks
User impact: Users may be unable to access or receive prompt responses with Copilot Chat or Copilot Notebooks.
More info: Users may experience failing requests for the following scenarios:
- Image generation requests in Copilot Chat
- Prompt generation requests in Copilot Chat
- Failures when attempting to access or view Copilot Notebooks
Current status: We've confirmed that the first change needed to allow us to fully remediate this issue has been validated and is in the process of being deployed. We're expediting the creation and deployment of additional changes needed, and anticipate that users will experience progressive relief by Wednesday, September 30, 2026.
Scope of impact: This incident impacts some users attempting to generate images or prompts using Copilot Chat or accessing Copilot notebooks. This section may be updated as the investigation progresses.
Estimated time to resolve: Users are expected to be able to access and receive prompt responses when accessing Copilot directly by Wednesday, September 30, 2026. We're finalizing our ETA for the remaining change to OneNote Copilot functionalities, which will require an additional change.
Root cause: A licensing mismatch in the request flow is causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
Next update by: Monday, September 28, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 15:29:54 2026 |
|---|
| Description: | Title: Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot Chat or Copilot Notebooks
User impact: Users may be unable to access or receive prompt responses with Copilot Chat or Copilot Notebooks.
More info: Users may experience failing requests for the following scenarios:
- Image generation requests in Copilot Chat
- Prompt generation requests in Copilot Chat
- Failures when attempting to access or view Copilot Notebooks
Current status: We've developed a fix that we expect will resolve the issue and are validating its efficacy before proceeding with deployment. We'll provide a timeline for the deployment as one becomes available.
Scope of impact: This incident impacts some users attempting to generate images or prompts using Copilot Chat or accessing Copilot notebooks. This section may be updated as the investigation progresses.
Root cause: A licensing mismatch in the request flow is causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
Next update by: Friday, September 25, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 12:00:33 2026 |
|---|
| Description: | Title: Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot Chat or Copilot Notebooks
User impact: Users may be unable to access or receive prompt responses with Copilot Chat or Copilot Notebooks.
More info: Users may experience failing requests for the following scenarios:
- Image generation requests in Copilot Chat
- Prompt generation requests in Copilot Chat
- Failures when attempting to access or view Copilot Notebooks
Current status: We've received reports from a subset of affected users who have reported impact to prompt and image generation in Copilot Chat, as well as failures when accessing Copilot Notebooks. We've isolated that impact is caused by a licensing mismatch which is causing Copilot Chat to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks. We're developing a fix to remediate the discrepancy, and we aim to provide more details on our fix and a timeline to release in our next scheduled update.
Scope of impact: This incident impacts some users attempting to generate images or prompts using Copilot Chat or accessing Copilot notebooks. This section may be updated as the investigation progresses.
Root cause: A licensing mismatch is causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
Next update by: Thursday, September 24, 2026, at 9:00 PM UTC
|
|---|
|
CP1478444 - Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot or Copilot Notebooks
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 21 22:50:00 2026 |
|---|
| End Time: | Mon Sep 28 14:18:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 28 17:43:08 2026 |
|---|
| Root Cause: | A licensing mismatch in the request flow was causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 28 17:42:49 2026 |
|---|
| Description: | Title: Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot or Copilot Notebooks
User impact: Users may have been unable to access or receive prompt responses with Microsoft 365 Copilot or Copilot Notebooks.
More info: Users may have experienced failing requests for the following scenarios:
- Image generation requests in Copilot
- Prompt generation requests in Copilot
- Failures when attempting to access or view Copilot Notebooks
Final status: We've completed deployment of our code change to address a licensing mismatch in the request flow. After completing an internal monitoring period, we've validated that impact is remediated.
Scope of impact: This incident impacted some users attempting to generate images or prompts using Copilot or accessing Copilot Notebooks.
Start time: Tuesday, September 22, 2026, at 2:50 AM UTC
End time: Sunday, September 27, 2026, at 6:18 PM UTC
Root cause: A licensing mismatch in the request flow was causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
Next steps:
- We're analyzing the problematic request flow to isolate how the licensing mismatch was introduced into our service and to validate what actions we can take to prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 25 13:39:48 2026 |
|---|
| Description: | Title: Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot or Copilot Notebooks
User impact: Users may be unable to access or receive prompt responses with Microsoft 365 Copilot or Copilot Notebooks.
More info: Users may experience failing requests for the following scenarios:
- Image generation requests in Copilot
- Prompt generation requests in Copilot
- Failures when attempting to access or view Copilot Notebooks
Current status: We've confirmed that the first change needed to allow us to fully remediate this issue has been validated and is in the process of being deployed. We're expediting the creation and deployment of additional changes needed, and anticipate that users will experience progressive relief by Wednesday, September 30, 2026.
Scope of impact: This incident impacts some users attempting to generate images or prompts using Copilot or accessing Copilot notebooks. This section may be updated as the investigation progresses.
Estimated time to resolve: Users are expected to be able to access and receive prompt responses when accessing Copilot directly by Wednesday, September 30, 2026. We're finalizing our ETA for the remaining change to OneNote Copilot functionalities, which will require an additional change.
Root cause: A licensing mismatch in the request flow is causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
Next update by: Monday, September 28, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 15:29:52 2026 |
|---|
| Description: | Title: Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot or Copilot Notebooks
User impact: Users may be unable to access or receive prompt responses with Microsoft 365 Copilot or Copilot Notebooks.
More info: Users may experience failing requests for the following scenarios:
- Image generation requests in Copilot
- Prompt generation requests in Copilot
- Failures when attempting to access or view Copilot Notebooks
Current status: We've developed a fix that we expect will resolve the issue and are validating its efficacy before proceeding with deployment. We'll provide a timeline for the deployment as one becomes available.
Scope of impact: This incident impacts some users attempting to generate images or prompts using Copilot or accessing Copilot notebooks. This section may be updated as the investigation progresses.
Root cause: A licensing mismatch in the request flow is causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
Next update by: Friday, September 25, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 12:00:35 2026 |
|---|
| Description: | Title: Some users may be unable to access or receive prompt responses with Microsoft 365 Copilot or Copilot Notebooks
User impact: Users may be unable to access or receive prompt responses with Microsoft 365 Copilot or Copilot Notebooks.
More info: Users may experience failing requests for the following scenarios:
- Image generation requests in Copilot
- Prompt generation requests in Copilot
- Failures when attempting to access or view Copilot Notebooks
Current status: We've received reports from a subset of affected users who have reported impact to prompt and image generation in Copilot, as well as failures when accessing Copilot Notebooks. We've isolated that impact is caused by a licensing mismatch which is causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks. We're developing a fix to remediate the discrepancy, and we aim to provide more details on our fix and a timeline to release in our next scheduled update.
Scope of impact: This incident impacts some users attempting to generate images or prompts using Copilot or accessing Copilot notebooks. This section may be updated as the investigation progresses.
Root cause: A licensing mismatch is causing Copilot to view affected users as unlicensed, preventing them from completing requests or accessing Notebooks.
Next update by: Thursday, September 24, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 11:14:59 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OP1478558 - Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 24 14:23:33 2026 |
|---|
| End Time: | Mon Sep 28 15:57:04 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 28 15:58:10 2026 |
|---|
| Root Cause: | A recent Microsoft Word change relating to the Save As filename validation path to cloud-backed locations prevented the SharePoint save flow from completing and was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 28 15:58:06 2026 |
|---|
| Description: | Title: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations
User impact: Users may have been unable to convert Word desktop app documents to PDFs using Save As to SharePoint locations.
More info: This issue was reported to affect Microsoft Word version 2609, and some users reported that version 2608 wasn't affected. No error was presented and the file was instead saved to the “C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\Content.MSO” folder with an incorrect file name.
While we focused on remediation, users that had the option to save the file locally to their computer may have used this to work around the problem. Additionally, using the Export to PDF function worked as expected.
Final status: We've finished deploying our change to disable the impacting behavior and have confirmed that this has resolved the issue through service health telemetry.
Scope of impact: This event may have impacted any user on version 2609 attempting to save Microsoft Word desktop app documents as PDFs to SharePoint Online.
Start time: Tuesday, September 8, 2026, at 7:00 AM UTC
End time: Friday, September 25, 2026, at 11:00 PM UTC
Root cause: A recent Microsoft Word change relating to the Save As filename validation path to cloud-backed locations prevented the SharePoint save flow from completing and was causing impact.
Next steps: - We're reviewing the responsible change to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 25 15:28:50 2026 |
|---|
| Description: | Title: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations
User impact: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations.
More info: This issue is reported to affect Microsoft Word version 2609, and some users report that version 2608 isn't affected. No error is presented and the file is instead saved to the “C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\Content.MSO” folder with an incorrect file name.
Additionally, this only reported to only impact converting Microsoft Word desktop app documents to PDFs using Save As and SharePoint Online as the location.
While we're focused on remediation, users that have the option to save the file locally to their computer may use this to work around the problem. Additionally, using the Export to PDF function works as expected.
Current status: We've confirmed that the issue is related to a recent Microsoft Word change affecting Save As filename validation for cloud-backed locations. This validation issue prevents the SharePoint save process from completing successfully during PDF conversion. We're actively deploying a change to disable the impacting behavior and expect this deployment to be completed by our next scheduled update.
Scope of impact: This event may impact any user on version 2609 attempting to save Microsoft Word desktop app documents as PDFs to SharePoint Online. This information may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 7:00 AM UTC
Root cause: A recent Microsoft Word change relating to the Save As filename validation path to cloud-backed locations, which prevents the SharePoint save flow from completing and is causing impact.
Next update by: Monday, September 28, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 19:35:02 2026 |
|---|
| Description: | Title: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations
User impact: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations.
More info: This issue is reported to affect Microsoft Word version 2609, and some users report that version 2608 isn't affected. No error is presented and the file is instead saved to the “C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\Content.MSO” folder with an incorrect file name.
Additionally, this only reported to only impact converting Microsoft Word desktop app documents to PDFs using Save As and SharePoint Online as the location.
While we're focused on remediation, users that have the option to save the file locally to their computer may use this to work around the problem. Additionally, using the Export to PDF function works as expected.
Current status: We're in the process of disabling the impacting code for impacted users. This is a multiple-step process, and we will provide an updated remediation timeline as soon as the initial steps have been completed.
Scope of impact: This event may impact any user on version 2609 attempting to save Microsoft Word desktop app documents as PDFs to SharePoint Online. This information may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 7:00 AM UTC
Root cause: A recent code change meant to optimize the save-as pathways utilized by the service contained an issue that's resulting in impact.
Next update by: Friday, September 25, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Sep 24 17:21:15 2026 |
|---|
| Description: | Title: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations
User impact: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations.
More info: This issue is reported to affect Microsoft Word version 2609, and some users report that version 2608 isn't affected. No error is presented and the file is instead saved to the “C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\Content.MSO” folder with an incorrect file name.
Additionally, this only reported to only impact converting Microsoft Word desktop app documents to PDFs using Save As and SharePoint Online as the location.
While we're focused on remediation, users that have the option to save the file locally to their computer may use this to work around the problem. Additionally, using the Export to PDF function works as expected.
Current status: We've identified the code change leading to this behavior and confirmed that disabling it mitigates the impact in our internal tests. Based on this finding, we've determined that this problem may have begun impacting users on Current Channel (Preview) as early as Tuesday, September 8, 2026, while non-Preview Current Channel users may have seen the issue begin on Tuesday, September 22, 2026. While we collect more information regarding this code change to include in this communication, we've halted its rollout to prevent more users from encountering this problem and are preparing to disable the impacting code for currently affected users.
Scope of impact: This event may impact any user on version 2609 attempting to save Microsoft Word desktop app documents as PDFs to SharePoint Online. This information may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 15:25:50 2026 |
|---|
| Description: | Title: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations
User impact: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations.
More info: This issue is reported to affect Microsoft Word version 2609, and some users report that version 2608 isn't affected. No error is presented and the file is instead saved to the “C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\Content.MSO” folder with an incorrect file name.
Additionally, this only reported to only impact converting Microsoft Word desktop app documents to PDFs using Save As and SharePoint Online as the location.
While we're focused on remediation, users that have the option to save the file locally to their computer may use this to work around the problem. Additionally, using the Export to PDF function works as expected.
Current status: We've internally reproduced the problem, and we're reviewing recent service changes that affect this code path to determine the cause of impact.
Scope of impact: This event may impact any user on version 2609 attempting to save Microsoft Word desktop app documents as PDFs to SharePoint Online. This information may be updated as our investigation continues.
Next update by: Thursday, September 24, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Sep 24 14:31:05 2026 |
|---|
| Description: | Title: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations
User impact: Users may be unable to convert Microsoft Word desktop app documents to PDFs using Save As to SharePoint locations.
More info: This issue is reported to affect Microsoft Word version 2609, and some users report that version 2608 isn't affected. No error is presented and the file is instead saved to the “C:\Users\username\AppData\Local\Microsoft\Windows\INetCache\Content.MSO” folder with an incorrect file name.
Additionally, this only reported to only impact converting Microsoft Word desktop app documents to PDFs using Save As and SharePoint Online as the location.
While we're focused on remediation, users that have the option to save the file locally to their computer may use this to work around the problem. Additionally, using the Export to PDF function works as expected.
Current status: We're investigating a potential issue with Microsoft Word saving files as PDF to SharePoint Online, and we're checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
EX1479476 - Some users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 25 16:27:30 2026 |
|---|
| End Time: | Fri Sep 25 22:20:39 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Sep 25 22:25:48 2026 |
|---|
| Root Cause: | A recent service update introduced a misconfiguration that caused the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 25 22:25:42 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods
User impact: Users may have been intermittently unable to access their Exchange Online mailboxes using multiple connection methods.
More info: The following connection methods may have been impacted:
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Final status: We've completed deployment of our fix and confirmed through service health telemetry that the impact is remediated as a result.
Scope of impact: Some users located in North America that attempted to access their Exchange Online mailbox using Outlook on the web, EAS, or MAPI may have been intermittently impacted.
Start time: Friday, September 25, 2026, at 7:00 PM UTC
End time: Saturday, September 26, 2026, at 2:16 AM UTC
Root cause: A recent service update introduced a misconfiguration that caused the impact.
Next steps:
- We're reviewing our service change testing and validation procedures to identify and prevent similar misconfiguration issues impacting user mailbox access during deployments in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 25 22:07:04 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods.
More info: The following connection methods may be impacted:
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: As we deploy our fix, we're monitoring our service health telemetry to ensure that user mailbox access is restored. We expect our fix to complete deployment by the time of our next update.
Scope of impact: Some users located in North America that are attempting to access their Exchange Online mailbox using Outlook on the web, EAS, or MAPI may be intermittently impacted. This section may be updated as our investigation continues.
Start time: Friday, September 25, 2026, at 7:00 PM UTC
Root cause: A recent service update introduced a misconfiguration that's causing the impact.
Next update by: Saturday, September 26, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Fri Sep 25 20:57:37 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods.
More info: The following connection methods may be impacted:
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: We've begun deployment of our fix, which is designed to correct the misconfiguration introduced by the aforementioned service update. We'll provide a timeline for the completion of the deployment as one becomes available.
Scope of impact: Some users located in North America that are attempting to access their Exchange Online mailbox using Outlook on the web, EAS, or MAPI may be intermittently impacted. This section may be updated as our investigation continues.
Start time: Friday, September 25, 2026, at 7:00 PM UTC
Root cause: A recent service update introduced a misconfiguration that's causing the impact.
Next update by: Saturday, September 26, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Sep 25 19:19:02 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods.
More info: The following connection methods may be impacted:
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: We've identified that a recent service update introduced a misconfiguration that's causing the impact. We're developing a fix to correct the configuration and restore user access to their mailboxes.
Scope of impact: Some users located in North America that are attempting to access their Exchange Online mailbox using Outlook on the web, EAS, or MAPI may be intermittently impacted. This section may be updated as our investigation continues.
Start time: Friday, September 25, 2026, at 7:00 PM UTC
Root cause: A recent service update introduced a misconfiguration that's causing the impact.
Next update by: Saturday, September 26, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Sep 25 17:58:04 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods
User impact: Users may be intermittently unable to access their Exchange Online mailboxes using multiple connection methods.
More info: The following connection methods may be impacted:
- Outlook on the web
- Exchange ActiveSync (EAS)
- Messaging API (MAPI)
Current status: Our service health monitoring alerted us to an increase in failures occurring when users attempt to access their Exchange Online mailboxes using Outlook on the web, EAS, or MAPI. We're reviewing the errors to isolate their source.
Scope of impact: Some users located in North America that are attempting to access their Exchange Online mailbox using Outlook on the web, EAS, or MAPI may be intermittently impacted. This section may be updated as our investigation continues.
Next update by: Friday, September 25, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Sep 25 16:30:44 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
MO1479564 - Admins and users may be unable to access or utilize multiple features within some Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 25 19:06:44 2026 |
|---|
| End Time: | Fri Sep 25 21:58:24 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 25 21:58:39 2026 |
|---|
| Root Cause: | A recent roll out of an authentication configuration was causing failures when processing requests to the listed affected scenarios.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 25 21:53:11 2026 |
|---|
| Description: | Title: Admins and users may be unable to access or utilize multiple features within some Microsoft 365 services
User impact: Admins and users may have been unable to access or utilize multiple features within some Microsoft 365 services.
More info: Specifically, Microsoft 365 for Education services, Microsoft Teams, and Microsoft 365 admin center were impacted, and all the affected scenarios consisted of the following:
- Users couldn't access Search Coach and Search Progress in Teams for Education; reports indicated that it couldn't be added as a Teams tab and existing experiences were failing.
- Parent/guardian ("related contact") information couldn't be retrieved through School Data Sync (SDS). Any scenarios depending on related contacts failed.
-Education admins couldn't trigger batch age-gating operations from SDS through the Microsoft 365 admin center
- Admins and users couldn't access Education configuration pages and saw an error message "cannot load page" in Microsoft 365 admin center
- Admins couldn't create or manage Speaker Progress resources using Speaker Progress Graph APIs
- Admins couldn't access or utilize Assignments scenarios that call Related Contacts indirectly.
Final status: We've validated through monitoring our service telemetry that access requests are succeeding once again, confirming that this issue is resolved.
Scope of impact: Admins and users who attempted to access or utilize any of the features listed in the More info section may have been impacted by this event.
Start time: Monday, September 21, 2026, at 6:00 AM UTC
End time: Saturday, September 26, 2026, at 12:20 AM UTC
Root cause: A recent roll out of an authentication configuration was causing failures when processing requests to the listed affected scenarios.
Next steps:
-We're investigating the impacting authentication configuration to pinpoint why it was failing to process requests as expected and why this impact wasn't caught during the testing and validation phase so that we can prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 25 19:50:30 2026 |
|---|
| Description: | Title: Admins and users may be unable to access or utilize multiple features within some Microsoft 365 services
User impact: Admins and users may be unable to access or utilize multiple features within some Microsoft 365 services.
More info: Specifically, Microsoft 365 for Education services, Microsoft Teams, and Microsoft 365 admin center are impacted and all the affected scenarios consist of the following:
-Users cannot access Search Coach and Search Progress in Teams for Education; reports indicate it cannot be added as a Teams tab and existing experiences are failing.
- Parent/guardian ("related contact") information can’t be retrieved through School Data Sync (SDS). Any scenarios depending on related contacts fail.
-Education admins can’t trigger batch age-gating operations from SDS through the Microsoft admin center.
- Admins and users can’t access Education configuration pages and see an error message "cannot load page" in Microsoft 365 admin center
- Admins can’t create or manage Speaker Progress resources using Speaker Progress Graph APIs
-Admins can’t access or utilize Assignments scenarios that call Related Contacts indirectly.
Current status: We've been alerted through our service monitoring that an issue is affecting all education tenants. We've identified that a recent rollout of an authentication configuration is causing failures when processing requests to the listed affected scenarios. We've applied a change to the affected configuration and are working on validating that it resolves this issue.
Scope of impact: Admins and users attempting to access or utilize any of the features listed out in the More info section may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A recent roll out of an authentication configuration is causing failures when processing requests to the listed affected scenarios.
Next update by: Saturday, September 26, 2026, at 2:00 AM UTC
|
|---|
|
TM1478719 - Users may not be able to create, schedule, or update Microsoft Teams meetings
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 24 15:57:37 2026 |
|---|
| End Time: | Thu Sep 24 16:27:15 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 24 18:28:38 2026 |
|---|
| Root Cause: | A recent feature update contained an issue that resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 24 16:29:07 2026 |
|---|
| Description: | Title: Users may not be able to create, schedule, or update Microsoft Teams meetings
User impact: Users may have not been able to create, schedule, or update Microsoft Teams meetings.
Final status: We identified a recent feature update that contained an issue that resulted in impact. We rolled back this responsible update to expediently remediate this event and have confirmed that this effectively resolved impact through service health telemetry.
Scope of impact: This event may have impacted any user attempting to create, schedule, or update Microsoft Teams meetings.
Start time: Thursday, September 24, 2026, at 7:09 PM UTC
End time: Thursday, September 24, 2026, at 8:07 PM UTC
Root cause: A recent feature update contained an issue that resulted in impact.
Next steps: - We're reviewing the responsible change to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 24 15:58:53 2026 |
|---|
| Description: | Title: Users may not be able to create, schedule, or update Microsoft Teams meetings
User impact: Users may not be able to create, schedule, or update 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.
|
|---|
|
MV1478587 - Users may be unable to publish posts in Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 24 14:49:00 2026 |
|---|
| End Time: | Thu Sep 24 15:23:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 24 16:04:02 2026 |
|---|
| Root Cause: | A maintenance task which was running on a portion of relevant hardware prevented a server migration from taking place until it was completed, which further prevented the publishing of posts. Once the task finished, migration was able to take place, remediating impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 24 15:56:44 2026 |
|---|
| Description: | Title: Users may be unable to publish posts in Microsoft Viva Engage
User impact: Users may have been unable to publish posts in Viva Engage.
Final status: After investigation, it was determined that an unrelated maintenance task was briefly running on a portion of hardware which was undergoing migration to a separate system, which was preventing posts from being published. The maintenance task completed shortly after start of impact, which released the lock on traffic and remediated impact without manual action.
Scope of impact: This issue may have affected any user in North America attempting to publish posts in Viva Engage.
Start time: Thursday, September 24, 2026, at 6:49 PM UTC
End time: Thursday, September 24, 2026, at 7:23 PM UTC
Root cause: A maintenance task which was running on a portion of relevant hardware prevented a server migration from taking place until it was completed, which further prevented the publishing of posts. Once the task finished, migration was able to take place, remediating impact.
Next steps:
- We're reviewing the circumstances behind the maintenance task to better understand the reason for the slow-down during server migration and prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 24 15:33:05 2026 |
|---|
| Description: | Title: Users may be unable to publish posts in Microsoft Viva Engage
User impact: Users may have been unable to publish posts in Viva Engage.
Current status: We've investigated a problem with the Viva Engage service in which users couldn't publish posts, 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.
|
|---|
|
MP1473907 - Some users may experience delays accessing audit logs through the Microsoft Purview Management API
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 14 02:00:00 2026 |
|---|
| End Time: | Sun Sep 20 00:56:34 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 24 11:19:49 2026 |
|---|
| Root Cause: | Frequent GC was causing the portion of service infrastructure responsible for facilitating user access to audit logs through the Microsoft Purview Management API to operate in a suboptimal state, which lead to increased request timeouts and was causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 24 11:19:49 2026 |
|---|
| Description: | Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may have experienced delays accessing audit logs through the Microsoft Purview Management API.
Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may have experienced delays accessing audit logs through the Microsoft Purview Management API.
More info: This issue specifically impacted Microsoft Purview users utilizing the Management Activity API and Search features to retrieve audit logs.
Final status: Following an extended period of monitoring the service health telemetry after the completion of our configuration change, we’ve confirmed that impact has been remediated.
Scope of impact: This issue may have potentially impacted a subset of Microsoft Purview users in the North America region who were utilizing the audit log feature of Microsoft Purview.
Start time: Monday, September 14, 2026, at 6:00 AM UTC
End time: Sunday, September 20, 2026, at 4:56 AM UTC
Root cause: Frequent GC was causing the portion of service infrastructure responsible for facilitating user access to audit logs through the Microsoft Purview Management API to operate in a suboptimal state, which lead to increased request timeouts and was causing impact.
Next steps: - We’re continuing to analyze how the Frequent GC issue manifested, as these actions will help us to clarify what actions we can take to ensure that similar impact doesn't occur in the future and to continue our ongoing mission to improve the resilience of our service for all Microsoft Purview users.
This is the final update for the event.
|
|---|
|
| Time: | Sun Sep 20 00:56:37 2026 |
|---|
| Description: | Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may have experienced delays accessing audit logs through the Microsoft Purview Management API.
More info: This issue specifically impacted Microsoft Purview users utilizing the Management Activity API and Search features to retrieve audit logs.
Final status: Following an extended period of monitoring the service health telemetry after the completion of our configuration change, we’ve confirmed that impact has been remediated.
Scope of impact: This issue may have potentially impacted a subset of Microsoft Purview users in the North America region who were utilizing the audit log feature of Microsoft Purview.
Start time: Monday, September 14, 2026, at 6:00 AM UTC
End time: Sunday, September 20, 2026, at 4:56 AM UTC
Root cause: Frequent GC was causing the portion of service infrastructure responsible for facilitating user access to audit logs through the Microsoft Purview Management API to operate in a suboptimal state, which lead to increased request timeouts and was causing impact.
Next steps: - We’re continuing to analyze how the Frequent GC issue manifested, as these actions will help us to clarify what actions we can take to ensure that similar impact doesn't occur in the future and to continue our ongoing mission to improve the resilience of our service for all Microsoft Purview users.
This is the final update for the event.
|
|---|
|
| Time: | Sat Sep 19 00:30:24 2026 |
|---|
| Description: | Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may experience delays accessing audit logs through the Microsoft Purview Management API.
More info: This issue is specifically impacting Microsoft Purview users utilizing the Management Activity API and Search features to retrieve audit logs.
Current status: Our aforementioned configuration change is continuing to help reduce the impact as expected and we anticipate our change will fully resolve this issue by Sunday, September 20, 2026.
Scope of impact: This issue may potentially impact a subset of Microsoft Purview users in the North America region utilizing the audit log feature of Microsoft Purview. This information may be updated as our investigation continues.
Root cause: Frequent GC is causing the portion of service infrastructure responsible for facilitating user access to audit logs through the Microsoft Purview Management API to operate in a suboptimal state, leading to increased request timeouts and is causing impact.
Next update by: Saturday, September 19, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Fri Sep 18 18:22:29 2026 |
|---|
| Description: | Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may experience delays accessing audit logs through the Microsoft Purview Management API.
More info: This issue is specifically impacting Microsoft Purview users utilizing the Management Activity API and Search features to retrieve audit logs.
Current status: Our service health telemetry indicates that the configuration change we applied to a subset of the affected service infrastructure appears to be reducing the impact. We're continuing to monitor the efficacy of our change to confirm that it fully resolves the issue before we apply the change more broadly.
Scope of impact: This issue may potentially impact a subset of Microsoft Purview users in the North America region utilizing the audit log feature of Microsoft Purview. This information may be updated as our investigation continues.
Root cause: Frequent GC is causing the portion of service infrastructure responsible for facilitating user access to audit logs through the Microsoft Purview Management API to operate in a suboptimal state, leading to increased request timeouts and is causing impact.
Next update by: Saturday, September 19, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Fri Sep 18 16:58:46 2026 |
|---|
| Description: | Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may experience delays accessing audit logs through the Microsoft Purview Management API.
More info: This issue is specifically impacting Microsoft Purview users utilizing the Management Activity API and Search features to retrieve audit logs.
Current status: We've identified that frequent garbage collection (GC) is causing the portion of service infrastructure responsible for facilitating user access to audit logs through the Microsoft Purview Management API to operate in a suboptimal state, leading to increased request timeouts and is causing impact. We've applied a configuration change to reduce the GC frequency and are monitoring to confirm that it remediates the impact as expected.
Scope of impact: This issue may potentially impact a subset of Microsoft Purview users in the North America region utilizing the audit log feature of Microsoft Purview. This information may be updated as our investigation continues.
Root cause: Frequent GC is causing the portion of service infrastructure responsible for facilitating user access to audit logs through the Microsoft Purview Management API to operate in a suboptimal state, leading to increased request timeouts and is causing impact.
Next update by: Friday, September 18, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Sep 18 16:45:11 2026 |
|---|
| Description: | Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may experience delays accessing audit logs through the Microsoft Purview Management API.
More info: This issue is specifically impacting Microsoft Purview users utilizing the Management Activity API and Search features to retrieve audit logs.
Current status: We're continuing to investigate the reason the impacting upstream service is timing out the requests while we implement configuration changes to the affected infrastructure that'll increase the number of requests that can be completed.
Scope of impact: This issue may potentially impact a subset of Microsoft Purview users in the North America region utilizing the audit log feature of Microsoft Purview. This information may be updated as our investigation continues.
Root cause: An upstream service that assists in the processing of audit log data in Microsoft Purview is causing delays.
Next update by: Friday, September 18, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Sep 18 13:30:57 2026 |
|---|
| Description: | Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may experience delays accessing audit logs through the Microsoft Purview Management API.
More info: This issue is specifically impacting Microsoft Purview users utilizing the Management Activity API and Search features to retrieve audit logs.
Current status: We've determined that adjusting the rate at which request calls are processed has improved impact across portions of the affected infrastructure. However, some service components responsible for facilitating access to audit logs are continuing to experience increased timeouts and request failures. We're evaluating additional mitigation options, including rebalancing request traffic, while we continue investigating the upstream service responsible for processing audit log requests to determine why it's causing delays.
Scope of impact: This issue may potentially impact a subset of Microsoft Purview users in the North America region utilizing the audit log feature of Microsoft Purview. This information may be updated as our investigation continues.
Root cause: An upstream service that assists in the processing of audit log data in Microsoft Purview is causing delays.
Next update by: Friday, September 18, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Sep 18 05:30:22 2026 |
|---|
| Description: | Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may experience delays accessing audit logs through the Microsoft Purview Management API.
More info: This issue is specifically impacting Microsoft Purview users utilizing the Management Activity API and Search features to retrieve audit logs.
Current status: We're continuing to assess mitigation options and are testing adjustments to improve the impact. We're monitoring the results to determine the most effective next steps.
Scope of impact: This issue may potentially impact a subset of Microsoft Purview users in the North America region utilizing the audit log feature of Microsoft Purview.
Start time: Monday, September 14, 2026, at 6:00 AM UTC
Root cause: An upstream service that assists in the processing of audit log data in Microsoft Purview is causing delays.
Next update by: Friday, September 18, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Sep 18 03:27:03 2026 |
|---|
| Description: | Title: Some users may experience delays accessing audit logs through the Microsoft Purview Management API
User impact: Users may experience delays accessing audit logs through the Microsoft Purview Management API.
More info: This issue is specifically impacting Microsoft Purview users utilizing the Management Activity API and Search features to retrieve audit logs.
Current status: We identified an issue with an upstream service that assists in the processing of audit log data in Microsoft Purview that is causing delays. We're working to address the upstream service issue and are allocating additional resources to help process the backlog of audit log data.
Scope of impact: This issue may potentially impact a subset of Microsoft Purview users in the North America region utilizing the audit log feature of Microsoft Purview.
Start time: Monday, September 14, 2026, at 6:00 AM UTC
Root cause: An upstream service that assists in the processing of audit log data in Microsoft Purview is causing delays.
Next update by: Friday, September 18, 2026, at 9:30 AM UTC
|
|---|
|
DZ1478328 - Users may have been unable to access Microsoft Defender for Endpoint public APIs
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 24 04:17:00 2026 |
|---|
| End Time: | Thu Sep 24 06:55:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 24 08:06:55 2026 |
|---|
| Root Cause: | A configuration issue during a planned service migration caused some Public API requests to continue being routed to infrastructure that was no longer configured to process those requests, resulting in 503 errors.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 24 08:06:20 2026 |
|---|
| Description: | Title: Users may have been unable to access Microsoft Defender for Endpoint public APIs
User impact: Users may have been unable to access Microsoft Defender for Endpoint public APIs.
More info: Affected API requests may have failed and returned a 503 Service Unavailable error.
Final status: We've determined that a configuration issue during a planned service migration caused some Microsoft Defender for Endpoint Public API requests to continue being routed to infrastructure that was no longer configured to process those requests, resulting in 503 errors. We've restored service capacity on the affected infrastructure, allowing API requests to process successfully and remediating the impact.
Scope of impact: Impact was specific to some users attempting to access Microsoft Defender for Endpoint public APIs.
Start time: Thursday, September 24, 2026, at 8:17 AM UTC
End time: Thursday, September 24, 2026, at 10:55 AM UTC
Root cause: A configuration issue during a planned service migration caused some Public API requests to continue being routed to infrastructure that was no longer configured to process those requests, resulting in 503 errors.
Next steps: We’re reviewing our service migration and traffic routing configuration procedures to prevent similar issues from recurring.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 24 07:31:52 2026 |
|---|
| Description: | Title: Users may have been unable to access Microsoft Defender for Endpoint public APIs
User impact: Users may have been unable to access Microsoft Defender for Endpoint public APIs.
Current status: We’ve investigated a problem with Microsoft Defender for Endpoint in which users may have been unable to access public APIs, 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.
|
|---|
|
SP1472983 - Users may be unable to load SharePoint Online sites or pages and receive an error message
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Sep 16 11:04:21 2026 |
|---|
| End Time: | Wed Sep 16 12:30:13 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Sep 23 20:30:19 2026 |
|---|
| Root Cause: | A change intended to improve how links within SharePoint Online pages are processed inadvertently introduced additional service requests when certain pages were loaded. For affected pages, the additional processing could interrupt page rendering and cause users to be redirected to an error page instead of seeing the requested content. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 23 20:27:08 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Sep 16 12:30:34 2026 |
|---|
| Description: | Title: Users may be unable to load SharePoint Online sites or pages and receive an error message
User impact: Users may have been unable to load SharePoint Online sites or pages and receive an error message.
More info: The error message stated: "Sorry, something went wrong: Thread was being aborted."
Final status: We reverted the change and confirmed through our service telemetry that impact is resolved.
Scope of impact: This issue may have affected any user attempting to load SharePoint Online sites and pages.
Start time: Tuesday, August 25, 2026, at 3:45 PM UTC
End time: Wednesday, September 16, 2026, at 3:17 PM UTC
Root cause: A change intended to improve how links within SharePoint Online pages are processed inadvertently introduced additional service requests when certain pages were loaded. For affected pages, the additional processing could interrupt page rendering and cause users to be redirected to an error page instead of seeing the requested content.
Next steps:
-Please see the post-incident report for more information about this event.
|
|---|
|
| Time: | Wed Sep 16 12:15:40 2026 |
|---|
| Description: | Title: Users may be unable to load SharePoint Online sites or pages and receive an error message
User impact: Users may be unable to load SharePoint Online sites or pages and receive an error message.
More info: The error message states: "Sorry, something went wrong: Thread was being aborted."
Current status: Our rollback of the impacting change is ongoing, and we've received confirmation from a subset of users that this is successfully remediating impact. We're monitoring the rollback as it continues to ensure completion and full remediation for all affected users.
Scope of impact: This issue may affect any user attempting to load SharePoint Online sites and pages.
Start time: Tuesday, August 25, 2026, at 3:45 PM UTC
Root cause: A recent configuration change concerning how the server delivers code to site pages to render as content resulted in impact.
Next update by: Wednesday, September 16, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 11:25:23 2026 |
|---|
| Description: | Title: Users may be unable to load SharePoint Online sites or pages and receive an error message
User impact: Users may be unable to load SharePoint Online sites or pages and receive an error message.
More info: The error message states: "Sorry, something went wrong: Thread was being aborted."
Current status: We've identified a recent configuration change concerning how the server delivers code to site pages to render as content resulted in impact. We're rolling back this change to remediate the issue for all users.
Scope of impact: This issue may affect any user attempting to load SharePoint Online sites and pages.
Start time: Tuesday, August 25, 2026, at 3:45 PM UTC
Root cause: A recent configuration change concerning how the server delivers code to site pages to render as content resulted in impact.
Next update by: Wednesday, September 16, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 11:08:34 2026 |
|---|
| Description: | Title: Users may be unable to load SharePoint Online sites or pages and receive an error message
User impact: Users may be unable to load SharePoint Online sites or pages and receive an error message.
More info: The error message states: "Sorry, something went wrong: Thread was being aborted."
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1476802 - Some users may be unable to open the account view in Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 22 08:13:00 2026 |
|---|
| End Time: | Wed Sep 23 12:17:19 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 23 12:27:38 2026 |
|---|
| Root Cause: | A code misconfiguration was introduced by a recent service change intended to modernize the Outlook on the web header, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 23 12:27:27 2026 |
|---|
| Description: | Title: Some users may be unable to open the account view in Outlook on the web
User impact: Users may have been unable to open the account view in Outlook on the web.
More info: When users attempted to access the account page, the authentication flow failed with the following error: 'AADSTS90002: Tenant 'XXXXXXXXXXXXXXXXXXXXXXXXXXXX' not found.
Final status: Following the deployment of our code fix, we've validated with affected users that the code fix has been addressed, and that the impact has been remediated. If users still encounter this problem, they can refresh their Outlook on the web browser session to immediately receive the fix.
Scope of impact: Some users who attempted to open the account view in Outlook on the web may have been impacted.
Start time: Tuesday, September 22, 2026, at 12:44 PM UTC
End time: Wednesday, September 23, 2026, at 2:00 AM UTC
Root cause: A code misconfiguration was introduced by a recent service change intended to modernize the Outlook on the web header, resulting in impact.
Next steps:
- We're further analyzing the recent impacting change to help us improve our pre-deployment tests and validations.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 22 18:06:14 2026 |
|---|
| Description: | Title: Some users may be unable to open the account view in Outlook on the web
User impact: Users may be unable to open the account view in Outlook on the web.
More info: When attempting to access the account page, the authentication flow fails with the following error: 'AADSTS90002: Tenant 'XXXXXXXXXXXXXXXXXXXXXXXXXXXX' not found. Check to make sure you have the correct tenant ID and are signing into the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant.'
Current status: We've identified that a code misconfiguration was introduced by a service change intended to modernize the Outlook on the web header, resulting in impact. We've developed and validated a fix to address the code misconfiguration, which we're preparing to deploy to the affected environment. We anticipate the deployment of our fix will begin by our next scheduled communications update.
Scope of impact: Some users attempting to open the account view in Outlook on the web may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 22, 2026, at 12:44 PM UTC
Root cause: A code misconfiguration was introduced by a recent service change intended to modernize the Outlook on the web header, resulting in impact.
Next update by: Wednesday, September 23, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 22 14:20:06 2026 |
|---|
| Description: | Title: Some users may be unable to open the account view in Outlook on the web
User impact: Users may be unable to open the account view in Outlook on the web.
More info: When attempting to access the account page, the authentication flow fails with the following error: 'AADSTS90002: Tenant 'XXXXXXXXXXXXXXXXXXXXXXXXXXXX' not found. Check to make sure you have the correct tenant ID and are signing into the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant.'
Current status: We're able to reproduce the issue within our internal testing environment, and we're gathering further diagnostic data to aid in our effort to uncover the source of the impact.
Scope of impact: Some users attempting to open the account view in Outlook on the web may be impacted. This section may be updated as our investigation continues.
Next update by: Tuesday, September 22, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Sep 22 10:08:32 2026 |
|---|
| Description: | Title: Some users may be unable to open the account view in Outlook on the web
User impact: Users may be unable to open the account view in Outlook on the web.
More info: When attempting to access the account page, the authentication flow fails with the following error: 'AADSTS90002: Tenant 'XXXXXXXXXXXXXXXXXXXXXXXXXXXX' not found. Check to make sure you have the correct tenant ID and are signing into the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant.'
Current status: We're reviewing data provided by some affected users to determine our next troubleshooting steps.
Scope of impact: Some users attempting to open the account view in Outlook on the web may be impacted. This section may be updated as our investigation continues.
Next update by: Tuesday, September 22, 2026, at 6:30 PM UTC
|
|---|
|
TM1477123 - Some users of HP DirectConnect mode on Poly Microsoft Teams Rooms on Android (MTRA) devices may experience call drops
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 17 20:00:00 2026 |
|---|
| End Time: | Tue Sep 22 18:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Sep 22 18:16:21 2026 |
|---|
| Root Cause: | A recent Teams version update (1449/1.0.96.2026249711) introduced a Microsoft Teams version mismatch between the device console and MTRA device, resulting in calls being dropped as the paired devices need to be running the same Microsoft Teams version.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 22 18:16:08 2026 |
|---|
| Description: | Title: Some users of HP DirectConnect mode on Poly Microsoft Teams Rooms on Android (MTRA) devices may experience call drops
User impact: Users of HP DirectConnect mode on Poly MTRA devices may have experienced call drops after 30 seconds.
More info: Users received an error message stating, "Different Versions on the Touch Panel detected, ending call shortly," before the call was dropped after approximately 30 seconds.
Final status: We've completed deployment of our remove configuration update to address the Microsoft Teams mismatch, and we've validated from internal testing that our update successfully remediated impact. We advise users to restart affected Poly MTRA devices to ensure they receive our update.
Scope of impact: This issue impacted some users of HP DirectConnect mode on Poly MTRA devices, who may have experienced call drops after 30 seconds.
Start time: Friday, September 18, 2026, at 12:00 AM UTC
End time: Tuesday, September 22, 2026, at 10:00 PM UTC
Root cause: A recent Teams version update (1449/1.0.96.2026249711) introduced a Microsoft Teams version mismatch between the device console and MTRA device, resulting in calls being dropped as the paired devices need to be running the same Microsoft Teams version.
Next steps:
- We're analyzing the problematic Microsoft Teams version update to isolate why the potential for impact wasn't caught during our internal testing and validation phases. This analysis will help us to improve our update implementation process moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 22 17:38:53 2026 |
|---|
| Description: | Title: Some users of HP DirectConnect mode on Poly Microsoft Teams Rooms on Android (MTRA) devices may experience call drops
User impact: Users of HP DirectConnect mode on Poly MTRA devices may experience call drops after 30 seconds.
More info: Users receive an error message stating, "Different Versions on the Touch Panel detected, ending call shortly," before the call is dropped after approximately 30 seconds.
Current status: We've received reports from a subset of affected users who state that when using HP DirectConnect mode on Poly Microsoft Teams Rooms on Android (MTRA) devices, their calls drop after approximately 30 seconds. We've isolated that a recent Teams version update (1449/1.0.96.2026249711) introduced a Microsoft Teams version mismatch between the device console and MTRA device, resulting in calls being dropped as the paired devices need to be running the same Microsoft Teams version. We've developed a remote configuration update to address the Microsoft Teams mismatch, and we anticipate the configuration change to be released by our next scheduled update.
Scope of impact: This incident impacts some users of HP DirectConnect mode on Poly MTRA devices, who may experience call drops after 30 seconds and receive an error message stating, "Different Versions on the Touch Panel detected, ending call shortly." This section may be updated as the investigation progresses.
Start time: Friday, September 18, 2026, at 12:00 AM UTC
Root cause: A recent Teams version update (1449/1.0.96.2026249711) introduced a Microsoft Teams version mismatch between the device console and MTRA device, resulting in calls being dropped as the paired devices need to be running the same Microsoft Teams version.
Next update by: Tuesday, September 22, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Sep 22 16:58:22 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Teams
User impact: We're looking into a potential problem impacting 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.
|
|---|
|
MP1474363 - Some users may be unable to access or apply protection to some documents in Microsoft Purview
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 18 18:03:29 2026 |
|---|
| End Time: | Fri Sep 18 18:20:42 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 22 17:59:35 2026 |
|---|
| Root Cause: | A Domain Name System (DNS) misconfiguration in the North America region Rights Management Service caused errors and timeouts when users accessed protected content. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 18 18:20:42 2026 |
|---|
| Description: | Title: Some users may be unable to access or apply protection to some documents in Microsoft Purview
User impact: Users may have been unable to access or apply protection to some documents using Microsoft Information Protection.
More info: Documents with protection already applied kept the protection level they had been assigned. Users may have encountered errors or timeouts when opening or decrypting protected documents, applying labels, publishing protected content, or retrieving protection templates.
Final status: We’ve determined that a Domain Name System (DNS) misconfiguration in the North America region Rights Management Service caused errors and timeouts when users accessed protected content. We successfully reverted the DNS to the previous configuration, and verified from our telemetry that this issue is resolved.
Scope of impact: Some users located in North America may have been unable to access or apply protection to some documents using Microsoft Information Protection.
Start time: Friday, September 18, 2026, at 8:15 PM UTC
End time: Friday, September 18, 2026, at 8:55 PM UTC
Root cause: A Domain Name System (DNS) misconfiguration in the North America region Rights Management Service caused errors and timeouts when users accessed protected content.
Next steps: - We’re continuing our investigation to determine how the DNS configuration was introduced to better detect and prevent issues like this from occurring in the future.
This is the final update for the event.
|
|---|
|
OP1470668 - Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 8 06:00:00 2026 |
|---|
| End Time: | Mon Sep 21 20:06:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 22 15:47:06 2026 |
|---|
| Root Cause: | A code regression contained within a recent service update was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 22 14:26:46 2026 |
|---|
| Description: | Title: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel
User impact: Users may have been unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel.
More info: This issue may have specifically impacted some users utilizing Microsoft Excel 2024, 2021, 2019, and 2016.
Affected users of Microsoft Excel 2016 can utilize the following link within the Microsoft Download Center to install the recently deployed fix: https://www.microsoft.com/en-us/download/details.aspx?id=108833
The following documentation provided additional updates on fix implementation for paste operations failing in Microsoft Excel: https://support.microsoft.com/en-us/support/known-issues/paste-not-work-excel
The following documentation outlined the update history for Microsoft Excel 2016 and Microsoft Excel 2019: https://learn.microsoft.com/en-us/officeupdates/update-history-office-2019
Final status: We've deployed the updated versions of both Microsoft Excel 2016 and 2019, which we've confirmed through monitoring service health telemetry recovered all affected scenarios. The fix for Microsoft Excel 2019 should download automatically for users, while users of Microsoft Excel 2016 will need to download the latest version from the Microsoft Download Center. We've provided a direct link for affected users to download the fix within the More info section of this communication.
Scope of impact: Some users attempting to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel may have been impacted.
Start time: Tuesday, September 8, 2026, at 10:00 AM UTC
End time: Tuesday, September 22, 2026, at 12:06 AM UTC
Root cause: A code regression contained within a recent service update was causing impact.
Next steps:
- We're reviewing our update procedures to understand why impact to Microsoft Excel functionality 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: | Mon Sep 21 13:45:21 2026 |
|---|
| Description: | Title: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel
User impact: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel.
More info: This issue may specifically impact some users utilizing Microsoft Excel 2024, 2021, 2019, and 2016.
For impact to Microsoft Excel 2016, users can utilize the following link to download the latest version (KB5002665) containing a code fix to remediate impact with the exception of paste issues:
https://support.microsoft.com/en-us/servicing/office/hotfix/excel/5002665
For additional updates on fix implementation for paste operations failing in Microsoft Excel, please refer to the following documentation:
https://support.microsoft.com/en-us/support/known-issues/paste-not-work-excel
Current status: After completing deployment of our fixes for Microsoft Excel 2021 and 2024, we've created an updated build of Excel 2016 to address most impact scenarios with the exception of paste issues that is linked in the "More info" section of this communication. We are initiating deployment of updated versions Excel 2016 and Excel 2019, which will also remediate impact Office Online Server (OOS) versions of Excel, which will address paste issues and other reported impact scenarios. We anticipate these builds to be deployed along with updated documentation by our next scheduled update.
Scope of impact: Some users attempting to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 10:00 AM UTC
Root cause: A code regression contained within a recent service update is causing impact.
Next update by: Tuesday, September 22, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Sep 17 15:11:02 2026 |
|---|
| Description: | Title: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel
User impact: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel.
More info: This issue may specifically impact some users utilizing Microsoft Excel 2024, 2021, 2019, and 2016.
Current status: Our fix has completed for Microsoft Excel 2021 and 2024. We're still in the process of validating both a temporary workaround and permanent fix for the 2016, 2019, and Office Online Server (OOS) versions of Excel. We'll provide the documentation on the workaround and timeline for the long-term fix as soon as they become available.
Scope of impact: Some users attempting to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 10:00 AM UTC
Root cause: A code regression contained within a recent service update is causing impact.
Next update by: Monday, September 21, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Sep 15 13:18:47 2026 |
|---|
| Description: | Title: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel
User impact: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel.
More info: This issue may specifically impact some users utilizing Microsoft Excel 2024, 2021, 2019, and 2016.
Current status: We're continuing to test the efficacy of our fixes to confirm that they fully remediate the impact. In the meantime, we're validating a possible workaround and its viability to ensure it's practical to use and also fully avoids this issue while we work on the long-term solution.
Scope of impact: Some users attempting to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 10:00 AM UTC
Root cause: A code regression contained within a recent service update is causing impact.
Next update by: Thursday, September 17, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Sep 14 13:55:20 2026 |
|---|
| Description: | Title: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel
User impact: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel.
More info: This issue may specifically impact some users utilizing Microsoft Excel 2024, 2021, 2019, and 2016.
Current status: Our development and validation of the individual fixes targeting each of the impacted versions is ongoing, and we'll provide an estimated timeline for resolution as one becomes available.
Scope of impact: Some users attempting to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 10:00 AM UTC
Root cause: A code regression contained within a recent service update is causing impact.
Next update by: Tuesday, September 15, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Sep 11 18:18:02 2026 |
|---|
| Description: | Title: Some users can't copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel
User impact: Users can't copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel.
More info: This issue may specifically impact some users utilizing Microsoft Excel 2024, 2021, 2019, and 2016.
Current status: We've identified a code regression contained within a recent service update that's causing impact. We're developing separate fixes for each of the four impacted Microsoft Excel versions, and we'll aim to provide a remediation timeline by our next scheduled communications update.
Scope of impact: Some users attempting to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 10:00 AM UTC
Root cause: A code regression contained within a recent service update is causing impact.
Next update by: Monday, September 14, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Sep 11 08:44:51 2026 |
|---|
| Description: | Title: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel
User impact: Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel.
More info: This issue may specifically impact some users utilizing Microsoft Excel 2024, 2021, 2019, and 2016.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Some users attempting to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel may be impacted. This section may be updated as our investigation continues.
Next update by: Friday, September 11, 2026, at 11:30 PM UTC
|
|---|
|
CP1474143 - Admins may be unable to view the Pay-As-You-Go (PAYG) breakdown in the Microsoft 365 admin center
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Sep 10 08:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 22 13:12:17 2026 |
|---|
| Root Cause: | A recent change to an API that facilitates PAYG breakdown reporting isn't responding to requests as expected, resulting in impact.
|
|---|
| Next Update: | Monday, October 5, 2026, at 6:30 PM UTC |
|---|
|
Details
| Time: | Tue Sep 22 13:12:17 2026 |
|---|
| Description: | Title: Admins may be unable to view the Pay-As-You-Go (PAYG) breakdown in the Microsoft 365 admin center
User impact: Admins may be unable to view the PAYG breakdown in the Microsoft 365 admin center.
More info: Affected admins are seeing the following message:
"Breakdown unavailable
We couldn't load the Pre-purchased (P3) versus pay-as-you-go breakdown right now. Please try again later."
Current status: We've temporarily disabled the PAYG breakdown page, which will be re-enabled once our fix has completed deployment. The development and validation processes for our fix have completed, and we currently estimate the fix will begin and complete deployment by our next scheduled communications update.
Scope of impact: Any admin attempting to access the PAYG breakdown pane within the Microsoft 365 admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, September 10, 2026, at 12:00 PM UTC
Root cause: A recent change to an API that facilitates PAYG breakdown reporting isn't responding to requests as expected, resulting in impact.
Next update by: Monday, October 5, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Sep 18 14:00:36 2026 |
|---|
| Description: | Title: Admins may be unable to view the Pay-As-You-Go (PAYG) breakdown in the Microsoft 365 admin center
User impact: Admins may be unable to view the PAYG breakdown in the Microsoft 365 admin center.
More info: Affected admins are seeing the following message:
"Breakdown unavailable
We couldn't load the Pre-purchased (P3) versus pay-as-you-go breakdown right now. Please try again later."
Current status: We're continuing the development of a fix and expect to have a release timeline by the next scheduled communications update.
Scope of impact: Any admin attempting to access the PAYG breakdown pane within the Microsoft 365 admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, September 10, 2026, at 12:00 PM UTC
Root cause: A recent change to an API that facilitates PAYG breakdown reporting isn't responding to requests as expected, resulting in impact.
Next update by: Tuesday, September 22, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Sep 18 13:01:09 2026 |
|---|
| Description: | Title: Admins may be unable to view the Pay-As-You-Go (PAYG) breakdown in the Microsoft 365 admin center
User impact: Admins may be unable to view the PAYG breakdown in the Microsoft 365 admin center.
More info: Affected admins are seeing the following message:
"Breakdown unavailable
We couldn't load the Pre-purchased (P3) versus pay-as-you-go breakdown right now. Please try again later."
Current status: Our monitoring has identified an increase in errors when loading the PAYG breakdown pane within the Microsoft 365 admin center. We've analyzed browser captures and determined that a recent change to an API that facilitates PAYG breakdown reporting isn't responding to requests as expected, resulting in impact. We're in the process of developing a fix to remediate this issue and will provide a remediation timeline once available.
Scope of impact: Any admin attempting to access the PAYG breakdown pane within the Microsoft 365 admin center may be affected.
Next update by: Friday, September 18, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Sep 18 12:30:06 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1469649 - Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Sep 9 00:30:00 2026 |
|---|
| End Time: | Mon Sep 14 00:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Sep 21 19:34:05 2026 |
|---|
| Root Cause: | A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 21 19:34:05 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Sep 16 19:33:58 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Sep 14 18:31:48 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may have been unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Final status: Our fix deployment has fully saturated and our telemetry confirms that service health has returned to baseline levels, resolving the customer impact.
Scope of impact: Some users who attempted to connect to the Outlook mobile app or Outlook client on Mac devices may have been impacted.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
End time: Monday, September 14, 2026 at 4:00 AM UTC
Preliminary root cause: A recent update to improve mail flow caused high CPU on the affected mailbox database infrastructure.
Next steps: We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Sep 14 12:58:28 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: We're no longer observing errors in the affected environment, and telemetry indicates that the majority of user impact has been mitigated. Deployment of the fix continues on a small subset of remaining servers. We're monitoring the environment over the next 24 hours to confirm service stability and verify that no additional impact occurs.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Tuesday, September 15, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Sun Sep 13 11:57:22 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: The fix has saturated approximately 98.3 percent of the affected service infrastructure, and we continue to assess that this event will be resolved by Monday, September 14, 2026. We continue to recommend Outlook on the web to users that remain affected at this time and have access to this client to bypass the impact.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Monday, September 14, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Sat Sep 12 12:05:53 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: We've confirmed that the expedition efforts to a subset of highly affected users has completed and our monitoring and reports from some users that the issue no longer persists. For those who remain affected, we continue to advise users to utilize Outlook on the web, if possible, to bypass impact. The fix deployment is approximately 97 percent complete, and our previously established estimated time to resolution remains Monday, September 14, 2026.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Sunday, September 13, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Sep 11 13:23:23 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: We’re continuing to monitor the deployment of our backported fix as it progresses through its final stages. Simultaneously, we’re continuing our efforts to expedite deployment to a subset of highly affected users to assist with remediation. We continue to advise users to utilize Outlook on the web, if possible, to bypass impact.
At this time, we expect the fix deployment to be over 95 percent complete, and that it will complete in full by Monday, September 14, 2026.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Saturday, September 12, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Sep 11 12:29:36 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
More info: While we’re focused on remediation, users with access to Outlook on the web may use this to bypass the impact.
Current status: We’re continuing to monitor the deployment of our backported fix as it progresses through its final stages. Simultaneously, we’re continuing our efforts to expedite deployment to a subset of highly affected users to assist with remediation. We continue to advise users to utilize Outlook on the web, if possible, to bypass impact.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Monday, September 14, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Sep 10 17:58:30 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
More info: While we’re focused on remediation, users with access to Outlook on the web may use this to bypass the impact.
Current status: We've initiated a backport of a fix to address impact that we anticipate to reach 95 percent saturation by our next scheduled update. Simultaneously, we're working to expedite deployment to a subset of highly affected users to assist with remediation while our deployment is ongoing. We also advise users to utilize Outlook on the web, if possible, to bypass impact.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Friday, September 11, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Sep 10 10:31:18 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: We’re deploying a fix to address the issue, as this provides a faster path to mitigation than reverting the offending change. The fix has been validated and deployment is underway. We’re monitoring its progress and expect the deployment to complete by our next scheduled update.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Saturday, September 12, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Sep 9 16:58:56 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: The release is still blocked and our investigation into the cause is ongoing. We will provide a release timeline once one is available.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Thursday, September 10, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Sep 9 14:55:58 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: We've encountered blockers that have delayed our planned reversion of the recent update, and we're actively investigating the cause while evaluating alternative remediation options to restore service.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Wednesday, September 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Sep 9 12:58:59 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: The validation is taking longer than initially expected and are monitoring as it progresses. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Wednesday, September 9, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Sep 9 07:33:28 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: We're continuing efforts to revert the recent update and expect to provide a projected completion timeline in our next scheduled update.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Wednesday, September 9, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Sep 9 05:31:46 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: We've determined that the fix may not be the most effective way to mitigate impact. We're working on reverting the recent update and expect to have a completion timeline as part of our next scheduled update.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 4:30 AM UTC
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Wednesday, September 9, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Sep 9 04:32:57 2026 |
|---|
| Description: | Title: Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
User impact: Users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices.
Current status: We've identified that a recent update to improve mail flow is causing high Central Processing Unit (CPU) on the affected mailbox database infrastructures, resulting in impact. We've developed a fix and are currently validating it within our testing environment before deploying to all affected environments.
Scope of impact: Some users attempting to connect to the Outlook mobile app or Outlook client on Mac devices may be impacted. This information may be updated as our investigation continues.
Root cause: A recent update to improve mail flow is causing high CPU on the affected mailbox database infrastructure.
Next update by: Wednesday, September 9, 2026, at 10:30 AM UTC
|
|---|
|
CP1474402 - Admins may see stale or incomplete data in the Microsoft 365 Copilot usage and Copilot chat reports
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 18 20:00:00 2026 |
|---|
| End Time: | Sat Sep 19 05:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Sep 19 14:12:44 2026 |
|---|
| Root Cause: | An upstream data dependency was currently unavailable, which was necessary for the data pipeline to process Copilot Usage and Copilot Chat report data, and was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Sep 19 14:03:28 2026 |
|---|
| Description: | Title: Admins may see stale or incomplete data in the Microsoft 365 Copilot usage and Copilot chat reports
User impact: Admins may have seen stale data in the Copilot usage and Copilot chat reports in the Microsoft 365 admin center
Final status: We've implemented a fix to retore the upstream data dependency to expected functionality, and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Admins located in North America, Asia Pacific, and Europe attempting to view up-to-date or complete Copilot Usage and Copilot chat report data within Microsoft 365 admin center may have been impacted.
Start time: Saturday, September 19, 2026, at 12:00 AM UTC
End time: Saturday, September 19, 2026, at 9:00 AM UTC
Root cause: An upstream data dependency was currently unavailable, which was necessary for the data pipeline to process Copilot Usage and Copilot Chat report data, and was resulting in impact.
Next steps:
- We're reviewing the upstream data dependency to determine why it was failing to process requests as expected, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 18 21:47:49 2026 |
|---|
| Description: | Title: Admins may see stale or incomplete data in the Microsoft 365 Copilot usage and Copilot chat reports
User impact: Admins may see stale or incomplete data in the Copilot usage and Copilot chat reports in the Microsoft 365 admin center
Current status: We've identified that an upstream data dependency is currently unavailable which is necessary for the data pipeline to process Copilot Usage and Copilot Chat report data, and is resulting in impact. We're investigating the underlying reason behind this upstream data delay issue so that we can determine whether any mitigative actions are necessary to help the affected pipelines recover.
Scope of impact: Admins located in North America, Asia Pacific, and Europe attempting to view up-to-date or complete Copilot Usage and Copilot chat report data within Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Root cause: An upstream data dependency is currently unavailable, which is necessary for the data pipeline to process Copilot Usage and Copilot Chat report data, and is resulting in impact.
Next update by: Saturday, September 19, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Sep 18 21:23:06 2026 |
|---|
| Description: | Title: Admins may see stale or incomplete data in the Microsoft 365 Copilot Usage and Copilot chat reports
User impact: Admins may see stale or incomplete data in the Copilot Usage and Copilot chat reports.
Current status: We're investigating a potential issue with Microsoft Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1473821 - Admins may see Copilot usage report delays in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 17 21:00:00 2026 |
|---|
| End Time: | Sat Sep 19 03:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Sep 19 14:01:49 2026 |
|---|
| Root Cause: | An upstream data dependency caused processing delays with Copilot usage reports. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Sep 19 13:45:50 2026 |
|---|
| Description: | Title: Admins may see Copilot usage report delays in the Microsoft 365 admin center
User impact: Admins may have seen Copilot usage report delays in the Microsoft 365 admin center.
Final status: We’ve completed applying our fix and confirmed that Copilot usage reports have successfully recovered and are up to date, resolving the impact.
Scope of impact: This issue may have impacted any admins in the North America and Asia-Pacific regions viewing Copilot usage report data in the Microsoft 365 admin center.
Start time: Friday, September 18, 2026, at 1:00 AM UTC
End time: Saturday, September 19, 2026, at 7:00 AM UTC
Root cause: An upstream data dependency caused processing delays with Copilot usage reports.
Next steps: We’re reviewing the upstream data dependency that caused processing delays with Copilot usage reports to help prevent similar impact from recurring.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 18 22:31:12 2026 |
|---|
| Description: | Title: Admins may see Copilot usage report delays in the Microsoft 365 admin center
User impact: Admins may see Copilot usage report delays in the Microsoft 365 admin center.
Current status: We're continuing to apply our fix and it's progressing as expected. We'll provide a timeline for resolution once it becomes available.
Scope of impact: This issue may impact any admins in the North America and Asia-Pacific regions viewing Copilot usage report data in the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Friday, September 18, 2026, at 1:00 AM UTC
Root cause: An upstream data dependency is causing processing delays with Copilot usage reports.
Next update by: Saturday, September 19, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Sep 18 15:04:54 2026 |
|---|
| Description: | Title: Admins may see Copilot usage report delays in the Microsoft 365 admin center
User impact: Admins may see Copilot usage report delays in the Microsoft 365 admin center.
Current status: We’re applying the fix to address the upstream data dependency issue causing processing delays with Copilot usage reports. Once complete, we’ll monitor the Copilot usage report data to confirm that it becomes up to date.
Scope of impact: This issue may impact any admins in the North America and Asia-Pacific regions viewing Copilot usage report data in the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Friday, September 18, 2026, at 1:00 AM UTC
Root cause: An upstream data dependency is causing processing delays with Copilot usage reports.
Next update by: Saturday, September 19, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Thu Sep 17 22:48:47 2026 |
|---|
| Description: | Title: Admins may see Copilot usage report delays in the Microsoft 365 admin center
User impact: Admins may see Copilot usage report delays in the Microsoft 365 admin center.
Current status: We identified an upstream data dependency issue that is causing processing delays with Copilot usage reports. We're working on a fix to address the source of the upstream issue and will ensure that the Copilot usage report data becomes up to date.
Scope of impact: This issue may impact any admins in the North America and Asia-Pacific regions viewing Copilot usage report data in the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Friday, September 18, 2026, at 1:00 AM UTC
Root cause: An upstream data dependency is causing processing delays with Copilot usage reports.
Next update by: Friday, September 18, 2026, at 8:00 PM UTC
|
|---|
|
PB1474132 - Users can't access Excel workbooks from Power BI and receive an error message
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 8 16:00:00 2026 |
|---|
| End Time: | Sat Sep 19 08:30:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Sep 19 12:06:45 2026 |
|---|
| Root Cause: | A recent service change designed to address a separate issue relating to relationships in Excel files caused impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Sep 19 12:05:53 2026 |
|---|
| Description: | Title: Users can't access Excel workbooks from Power BI and receive an error message
User impact: Users couldn't access Excel workbooks from Power BI and received an error message.
More info: Impact was specific to the September 2026 release of the Power BI desktop client and Power BI on the web.
When users attempted to access Excel workbooks from Power BI, they received an error that stated, "The input couldn't be recognized as a valid Excel document."
Final status: We've completed the reversion of the offending service change, and after monitoring the service, we've verified that this action successfully remediated the impact.
Scope of impact: Your organization was affected by this event, and any user attempting to access Excel workbooks from the September 2026 release of the Power BI desktop client or Power BI on the web was impacted.
Start time: Tuesday, September 8, 2026, at 8:00 PM UTC
End time: Saturday, September 19, 2026, at 12:30 PM UTC
Root cause: A recent service change designed to address a separate issue relating to relationships in Excel files caused impact.
Next steps: We're investigating how the recent service change designed to address a separate issue relating to relationships in Excel files caused this impact.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 18 17:32:48 2026 |
|---|
| Description: | Title: Users can't access Excel workbooks from Power BI and receive an error message
User impact: Users can't access Excel workbooks from Power BI and receive an error message.
More info: Impact is specific to the September 2026 release of the Power BI desktop client and Power BI on the web.
When users attempt to access Excel workbooks from Power BI, they receive an error that states, "The input couldn't be recognized as a valid Excel document."
Current status: We've confirmed that our actions to reverse the impacting service change remediates the impact in our internal testing environment, so we're proceeding with applying this reversion to the affected users. We'll provide a timeline for the completion of this reversion as one becomes available.
Scope of impact: Your organization is affected by this event, and any user attempting to access Excel workbooks from the September 2026 release of the Power BI desktop client or Power BI on the web is impacted. This information may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 8:00 PM UTC
Root cause: A recent service change designed to address a separate issue relating to relationships in Excel files is causing impact.
Next update by: Saturday, September 19, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Sep 18 16:43:29 2026 |
|---|
| Description: | Title: Users can't access Excel workbooks from Power BI and receive an error message
User impact: Users can't access Excel workbooks from Power BI and receive an error message.
More info: Impact is specific to the September 2026 release of the Power BI desktop client and Power BI on the web.
When users attempt to access Excel workbooks from Power BI, they receive an error that states, "The input couldn't be recognized as a valid Excel document."
Current status: We're testing a method of reversing the impacting change to confirm that it remediates the impact as expected before applying this change more broadly.
Scope of impact: Your organization is affected by this event, and any user attempting to access Excel workbooks from the September 2026 release of the Power BI desktop client or Power BI on the web is impacted. This information may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 8:00 PM UTC
Root cause: A recent service change designed to address a separate issue relating to relationships in Excel files is causing impact.
Next update by: Friday, September 18, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Sep 18 14:45:34 2026 |
|---|
| Description: | Title: Users can't access Excel workbooks from Power BI and receive an error message
User impact: Users can't access Excel workbooks from Power BI and receive an error message.
More info: Impact is specific to the September 2026 release of the Power BI desktop client and Power BI on the web.
When users attempt to access Excel workbooks from Power BI, they receive an error that states, "The input couldn't be recognized as a valid Excel document."
Current status: We're evaluating multiple options to reverse the impacting change, so that we can determine which method will be the most efficient at remediating the impact.
Scope of impact: Your organization is affected by this event, and any user attempting to access Excel workbooks from the September 2026 release of the Power BI desktop client or Power BI on the web is impacted. This information may be updated as our investigation continues.
Start time: Tuesday, September 8, 2026, at 8:00 PM UTC
Root cause: A recent service change designed to address a separate issue relating to relationships in Excel files is causing impact.
Next update by: Friday, September 18, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Sep 18 13:20:12 2026 |
|---|
| Description: | Title: Users can't access Excel workbooks from Power BI and receive an error message
User impact: Users can't access Excel workbooks from Power BI and receive an error message.
More info: Impact is specific to the September 2026 release of the Power BI desktop client and Power BI on the web.
When users attempt to access Excel workbooks from Power BI, they receive an error that states, "The input couldn't be recognized as a valid Excel document."
Current status: We've identified a recent service change, designed to address a separate issue relating to relationships in Excel files, that's causing impact. We're evaluating the most efficient method to reverse this change and remediate the impact.
Scope of impact: Your organization is affected by this event, and any user attempting to access Excel workbooks from the September 2026 release of the Power BI desktop client or Power BI on the web is impacted.
Root cause: A recent service change designed to address a separate issue relating to relationships in Excel files is causing impact.
Next update by: Friday, September 18, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Sep 18 12:31:48 2026 |
|---|
| Description: | Title: Users can't access Excel workbooks from Power BI and receive an error message
User impact: Users can't access Excel workbooks from Power BI and receive an error message.
More info: Impact is specific to the September 2026 release of the Power BI desktop client and Power BI on the web.
When users attempt to access Excel workbooks from Power BI, they receive an error that states, "The input couldn't be recognized as a valid Excel document."
Current status: We're reproducing the impact using our internal testing environment to gain clarity on the issue, so that we can determine our next steps to isolate the root cause.
Scope of impact: Your organization is affected by this event, and any user attempting to access Excel workbooks from the September 2026 release of the Power BI desktop client or Power BI on the web is impacted.
Next update by: Friday, September 18, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Sep 18 12:15:46 2026 |
|---|
| Description: | Title: Users can't access Excel workbooks from Power BI and receive an error message
User impact: Users can't access Excel workbooks from Power BI and receive an error message.
More info: Impact is specific to the September 2026 release of the Power BI desktop client and Power BI on the web.
Current status: We're investigating a potential issue with Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1474508 - Users may have seen their submission result status appear as “Unknown” in the Defender portal
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 17 16:00:00 2026 |
|---|
| End Time: | Fri Sep 18 12:30:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Sep 19 06:40:30 2026 |
|---|
| Root Cause: | An issue within Microsoft Defender for Office 365 infrastructure prevented some submissions from being graded, causing their result status to appear as “Unknown.”
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Sep 19 04:58:57 2026 |
|---|
| Description: | Title: Users may have seen their submission result status appear as “Unknown” in the Defender portal
User impact: Users may have seen their submission result status appear as “Unknown” in the Defender portal.
More info: Affected users may have been able to see their submissions in the Defender portal, but the submission result status may have appeared as unknown.
Final status: We've identified an issue within Microsoft Defender for Office 365 infrastructure that prevented some submissions from being graded, causing their result status to appear as “Unknown.” We've restarted the affected infrastructure and, after a period of monitoring, confirmed that the issue is remediated.
Scope of impact: Your organization was affected by this event, and some users attempting to view the submission result status in the Defender portal may have been impacted.
Start time: Thursday, September 17, 2026, at 8:00 PM UTC
End time: Friday, September 18, 2026, at 4:30 PM UTC
Root cause: An issue within Microsoft Defender for Office 365 infrastructure prevented some submissions from being graded, causing their result status to appear as “Unknown.”
Next steps: -We’re reviewing the underlying infrastructure issue and identifying measures to help prevent similar impact from recurring.
This is the final update for the event.
|
|---|
|
CP1470554 - Users may have been unable to access or may have encountered issues when interacting with Microsoft 365 Copilot
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Sep 10 23:45:00 2026 |
|---|
| End Time: | Fri Sep 11 06:16:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sat Sep 19 02:17:11 2026 |
|---|
| Root Cause: | A configuration update unintentionally reduced request-processing limits for some Microsoft 365 Copilot workloads below the levels needed to handle normal traffic. As a result, some valid requests were throttled or could not complete. The change significantly reduced the effective request-processing quota for affected model and scenario combinations, including GPT-5.5 chat and GPT-5.6 reasoning, from the expected production level to 100 requests per minute. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Sep 19 02:15:12 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Sep 15 14:27:17 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Sep 11 07:00:51 2026 |
|---|
| Description: | Title: Users may have been unable to access or may have encountered issues when interacting with Microsoft 365 Copilot
User impact: Users may have been unable to access or may have encountered issues when interacting with Microsoft 365 Copilot.
More info: Users who were encountering issues were encouraged to try an alternate model to avoid impact while our investigation was ongoing.
Affected Microsoft 365 Copilot features and services included, but were not limited to the following:
- Microsoft 365 Copilot Chat
- Microsoft 365 Copilot Notebooks
- Researcher in Microsoft 365 Copilot
- Copilot agents and custom agents
- Microsoft 365 Copilot in Word
- Microsoft 365 Copilot in Excel
- Microsoft 365 Copilot in PowerPoint
- Microsoft Copilot Studio
Final status: We've completed extended monitoring of the service and confirmed through telemetry that all previously affected Microsoft 365 Copilot features and services have recovered and are operating within expected parameters. We've observed healthy request success rates and service performance across impacted workloads.
Scope of impact: Any users served through affected sections of infrastructure may have been impacted when attempting to access or interact with Microsoft 365 Copilot.
Start time: Friday, September 11, 2026, 3:45 AM UTC
End time: Friday, September 11, 2026, 10:16 AM UTC
Root cause: A configuration update unintentionally reduced request-processing limits for some Microsoft 365 Copilot workloads below the levels needed to handle normal traffic. As a result, some valid requests were throttled or could not complete. The change significantly reduced the effective request-processing quota for affected model and scenario combinations, including GPT-5.5 chat and GPT-5.6 reasoning, from the expected production level to 100 requests per minute.
As normal production traffic entered the request admission layer, a large volume of requests was rejected before reaching downstream AI processing services. The failures surfaced primarily as scenario-level HTTP 429 throttling, which caused elevated request failures and retries across multiple Microsoft 365 Copilot experiences.
We restored the affected quota configuration and continued monitoring recovery across the impacted scenarios. After the quota rollback, traffic volumes returned toward expected levels, but the sudden return of traffic required additional traffic-routing and capacity rebalancing with a dependent AI processing service. Following those optimizations, service telemetry showed request success rates, latency, and overall platform health returning to expected operating thresholds, with no ongoing indication of customer 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: | Fri Sep 11 05:30:56 2026 |
|---|
| Description: | Title: Users may be unable to access or may encounter issues when interacting with Microsoft 365 Copilot
User impact: Users may be unable to access or may encounter issues when interacting with Microsoft 365 Copilot
More info: Users who are encountering issues are encouraged to try an alternate model to avoid impact while our investigation is ongoing.
Scope of impact: Any users served through affected sections of infrastructure may be impacted when attempting to access or interact with Microsoft 365 Copilot. This information may be updated as our investigation continues.
Preliminary root cause: A recent configuration change caused an unexpected issue in request processing, resulting in users experiencing failures when using Microsoft 365 Copilot.
Next update by: Friday, September 11, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Fri Sep 11 04:43:56 2026 |
|---|
| Description: | We've completed a configuration rollback and are monitoring recovery. We're working with dependent AI services to optimise traffic routing and rebalance request processing, while closely monitoring telemetry to restore a consistent user experience.
This quick update is designed to give the latest information on this issue.
Next update by: Friday, September 11, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Fri Sep 11 04:05:38 2026 |
|---|
| Description: | Title: Users may be unable to access or may encounter issues when interacting with Microsoft 365 Copilot
User impact: Users may be unable to access or may encounter issues when interacting with Microsoft 365 Copilot.
More info: Users who are encountering issues are encouraged to try an alternate model to avoid impact while our investigation is ongoing.
Current status: We’ve isolated the issue to a specific component involved in processing Microsoft 365 Copilot requests. We've identified a recent configuration change within the affected request path that may be contributing to the impact and are reverting that change while monitoring service telemetry for signs of recovery. In parallel, we're continuing our analysis to identify any additional contributing factors and expedite restoration of normal service functionality. Our remediation efforts remain a high priority as we work to restore a consistent experience for affected users.
Preliminary root cause: A recent configuration change caused an unexpected issue in request processing, resulting in users experiencing failures when using Microsoft 365 Copilot.
Next update by: Friday, September 11, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Fri Sep 11 03:03:33 2026 |
|---|
| Description: | Title: Users may be unable to access or may encounter issues when interacting with Microsoft 365 Copilot
User impact: Users may be unable to access or may encounter issues when interacting with Microsoft 365 Copilot.
More info: Users who are encountering issues are encouraged to try an alternate model to avoid impact while our investigation is ongoing.
Current status: We're closely analyzing our service telemetry dashboards associated with dependent models to isolate the source of the issues and identify our next troubleshooting steps.
Scope of impact: Any users served through affected sections of infrastructure may be impacted when attempting to access or interact with Microsoft 365 Copilot. This information may be updated as our investigation continues.
Next update by: Friday, September 11, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Fri Sep 11 02:45:02 2026 |
|---|
| Description: | We're reviewing dependent reasoning models and the corresponding service telemetry to help us thoroughly understand the scope of the impact and determine the most timely mitigation strategy.
This quick update is designed to give the latest information on this issue.
Next update by: Friday, September 11, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Sep 11 02:26:14 2026 |
|---|
| Description: | Title: Users may be unable to access or encounter issues when interacting with Microsoft 365 Copilot
User impact: Users may be unable to access or encounter issues when interacting with Microsoft 365 Copilot.
Current status: We're reviewing correlated service telemetry to isolate the source of the issue and determine our next troubleshooting actions.
Scope of impact: Any users served through affected sections of infrastructure may be impacted when attempting to access or interact with Microsoft 365 Copilot. This information may be updated as our investigation continues.
Next update by: Friday, September 11, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Sep 11 02:04:13 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1459181 - Users may be unable to join shared channels using some links to messages in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Fri Aug 21 19:42:31 2026 |
|---|
| End Time: | Fri Sep 18 16:58:43 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 18 17:00:13 2026 |
|---|
| Root Cause: | A recent update intended to improve the data pathways leveraged to facilitate channel link generation caused the affected links to be malformed, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 18 17:00:09 2026 |
|---|
| Description: | Title: Users may be unable to join shared channels using some links to messages in Microsoft Teams
User impact: Users may have been unable to join shared channels using some links to messages in Microsoft Teams.
More info: This issue specifically affected links generated using the “Copy Link” option through the three dots menu located at the top right of the shared channel. Users could've bypassed this impact by generating links to channels using any alternate method, such as by right-clicking on the channel in the left rail menu or any specific message within the shared channel and choosing the “Copy Link” option there.
Final status: We've confirmed that the deployment of our fix has completed to all affected environments and resolved this event.
Scope of impact: Users joining channels or generating channels links using the “Copy Link” options within the three dots menu located at the top right of shared Microsoft Teams channels may have been impacted.
Start time: Wednesday, July 1, 2026, at 12:00 AM UTC
End time: Friday, September 18, 2026, at 5:55 PM UTC
Root cause: A recent update intended to improve the data pathways leveraged to facilitate channel link generation caused the affected links to be malformed, which resulted in impact.
Next steps: - We're reviewing the responsible update to better understand what led to the malformed links that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 17 16:22:04 2026 |
|---|
| Description: | Title: Users may be unable to join shared channels using some links to messages in Microsoft Teams
User impact: Users may be unable to join shared channels using some links to messages in Microsoft Teams.
More info: This issue specifically affects links generated using the “Copy Link” option through the three dots menu located at the top right of the shared channel. Users can bypass this impact by generating links to channels using any alternate method, such as by right-clicking on the channel in the left rail menu or any specific message within the shared channel and choosing the “Copy Link” option there.
Current status: The deployment of our fix is nearing completion but is taking additional time. We now anticipate the deployment will complete by Friday, September 18, 2026.
Scope of impact: Users joining channels or generating channels links using the “Copy Link” options within the three dots menu located at the top right of shared Microsoft Teams channels may be impacted.
Start time: Wednesday, July 1, 2026, at 12:00 AM UTC
Root cause: A recent update intended to improve the data pathways leveraged to facilitate channel link generation is causing the affected links to be malformed, leading to impact.
Next update by: Friday, September 18, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Sep 8 15:44:14 2026 |
|---|
| Description: | Title: Users may be unable to join shared channels using some links to messages in Microsoft Teams
User impact: Users may be unable to join shared channels using some links to messages in Microsoft Teams.
More info: This issue specifically affects links generated using the “Copy Link” option through the three dots menu located at the top right of the shared channel. Users can bypass this impact by generating links to channels using any alternate method, such as by right-clicking on the channel in the left rail menu or any specific message within the shared channel and choosing the “Copy Link” option there.
Current status: Many users should see remediation from this issue as the deployment continues to make it to all affected areas. We have an updated timeline for its completeness and now anticipate that all areas should have the deployment by our next communication time.
Scope of impact: Users joining channels or generating channels links using the “Copy Link” options within the three dots menu located at the top right of shared Microsoft Teams channels may be impacted.
Root cause: A recent update intended to improve the data pathways leveraged to facilitate channel link generation is causing the affected links to be malformed, leading to impact.
Next update by: Thursday, September 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 16:58:15 2026 |
|---|
| Description: | Title: Users may be unable to join shared channels using some links to messages in Microsoft Teams
User impact: Users may be unable to join shared channels using some links to messages in Microsoft Teams.
More info: This issue specifically affects links generated using the “Copy Link” option through the three dots menu located at the top right of the shared channel. Users can bypass this impact by generating links to channels using any alternate method, such as by right-clicking on the channel in the left rail menu or any specific message within the shared channel and choosing the “Copy Link” option there.
Current status: We're continuing to monitor as the fix deploys and we expected most users will see relief from this issue by the end of September 4, 2026, but it may take until the end of September 7, 2026 to see complete remediation.
Scope of impact: Users joining channels or generating channels links using the “Copy Link” options within the three dots menu located at the top right of shared Microsoft Teams channels may be impacted.
Root cause: A recent update intended to improve the data pathways leveraged to facilitate channel link generation is causing the affected links to be malformed, leading to impact.
Next update by: Tuesday, September 8, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Aug 28 15:33:49 2026 |
|---|
| Description: | Title: Users may be unable to join shared channels using some links to messages in Microsoft Teams
User impact: Users may be unable to join shared channels using some links to messages in Microsoft Teams.
More info: This issue specifically affects links generated using the “Copy Link” option through the three dots menu located at the top right of the shared channel. Users can bypass this impact by generating links to channels using any alternate method, such as by right-clicking on the channel in the left rail menu or any specific message within the shared channel and choosing the “Copy Link” option there.
Current status: The fix is continuing to deploy successfully, and affected users may begin experiencing recovery as deployment progresses. We expect the deployment to be fully completed by the end of the week of September 4, 2026.
Scope of impact: Users joining channels or generating channels links using the “Copy Link” options within the three dots menu located at the top right of shared Microsoft Teams channels may be impacted.
Root cause: A recent update intended to improve the data pathways leveraged to facilitate channel link generation is causing the affected links to be malformed, leading to impact.
Next update by: Thursday, September 3, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 21:00:23 2026 |
|---|
| Description: | Title: Users may be unable to join shared channels using some links to messages in Microsoft Teams
User impact: Users may be unable to join shared channels using some links to messages in Microsoft Teams.
More info: This issue specifically affects links generated using the “Copy Link” option through the three dots menu located at the top right of the shared channel. Users can bypass this impact by generating links to channels using any alternate method, such as by right-clicking on the channel in the left rail menu or any specific message within the shared channel and choosing the “Copy Link” option there.
Current status: We've started deploying the fix, which we anticipate may take approximately two weeks to complete. We'll aim to provide a more accurate resolution timeline by our next scheduled update.
Scope of impact: Users joining channels or generating channels links using the “Copy Link” options within the three dots menu located at the top right of shared Microsoft Teams channels may be impacted.
Root cause: A recent update intended to improve the data pathways leveraged to facilitate channel link generation is causing the affected links to be malformed, leading to impact.
Next update by: Friday, August 28, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Aug 21 20:12:52 2026 |
|---|
| Description: | Title: Users may be unable to join shared channels using some links to messages in Microsoft Teams
User impact: Users may be unable to join shared channels using some links to messages in Microsoft Teams.
More info: This issue specifically affects links generated using the “Copy Link” option through the three dots menu located at the top right of the shared channel. Users can bypass this impact by generating links to channels using any alternate method, such as by right-clicking on the channel in the left rail menu or any specific message within the shared channel and choosing the “Copy Link” option there.
Current status: We've determined that a recent update intended to improve the data pathways leveraged to facilitate channel link generation is causing the affected links to be malformed, leading to impact. We've developed a fix to resolve this issue, and we're initiating deployment of this fix to the impacted service environments.
Scope of impact: Users joining channels or generating channels links using the “Copy Link” options within the three dots menu located at the top right of shared Microsoft Teams channels may be impacted.
Root cause: A recent update intended to improve the data pathways leveraged to facilitate channel link generation is causing the affected links to be malformed, leading to impact.
Next update by: Tuesday, August 25, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Aug 21 19:43:37 2026 |
|---|
| Description: | Title: Users may be unable to join shared channels using some links to messages in Microsoft Teams
User impact: Users may be unable to join shared channels using some links to messages in Microsoft Teams.
More info: This issue specifically affects links generated using the “Copy Link” options within the three dots menu located at the top right of the shared channel. Users can bypass this impact by generating links to channels using any alternate method, such as by right-clicking on the channel in the left rail menu or any specific message within the shared channel and choosing the “Copy Link” option there.
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.
|
|---|
|
EX1473059 - Users may be unable to access Outlook on the web from a specific Outlook link
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 15 11:00:00 2026 |
|---|
| End Time: | Fri Sep 18 11:40:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 18 16:49:23 2026 |
|---|
| Root Cause: | A recent code change was producing a code regression that was preventing users from accessing Outlook on the web from a specific link within Outlook.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 18 16:20:08 2026 |
|---|
| Description: | Title: Users may be unable to access Outlook on the web from a specific Outlook link
User impact: Users may have been unable to access Outlook on the web from a specific Outlook link.
More info: Users may have been unable to access Outlook on the web from a specific link within Outlook.
Users may have been access Outlook on the web by navigating to a direct URL with /mail/ appended.
As an example, some users could navigate to "https://outlook.office365.com/mail/" to
successfully access the client.
Final status: We've reverted the problematic code change, and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: This issue may have prevented any user attempting to access Outlook on the web from the specific link in the More Info portion of this communication.
Start time: Tuesday, September 15, 2026, at 3:00 PM UTC
End time: Friday, September 18, 2026, at 3:40 PM UTC
Root cause: A recent code change was producing a code regression that was preventing users from accessing Outlook on the web from a specific link within Outlook.
Next steps: - We're reviewing our update procedures to understand why impact to Outlook on the web 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: | Thu Sep 17 14:47:48 2026 |
|---|
| Description: | Title: Users are unable to access Outlook on the web from a specific Outlook link
User impact: Users are unable to access Outlook on the web from a specific Outlook link.
More info: Users are unable to access Outlook on the web from a specific link within Outlook.
Users can access Outlook on the web by navigating to a direct URL with /mail/ appended.
As an example, some users can navigate to "https://outlook.office365.com/mail/" to
successfully access the client.
Department of Defense customers: https://webmail.apps.mil/mail/
GCCH customers: https://outlook.office365.us/mail/
Current status: Our change reversion is approximately 82 percent complete, and our established timeline expects it will have completed by our next scheduled communication update.
Scope of impact: This issue may prevent any user attempting to access Outlook on the web from the specific link in the More Info portion of this communication. This information may be updated as our investigation continues.
Start time: Tuesday, September 15, 2026, at 3:00 PM UTC
Root cause: A recent code change is producing a code regression that is preventing users from accessing Outlook on the web from a specific link within Outlook.
Next update by: Friday, September 18, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Sep 16 13:51:35 2026 |
|---|
| Description: | Title: Users are unable to access Outlook on the web from a specific Outlook link
User impact: Users are unable to access Outlook on the web from a specific Outlook link.
More info: Users are unable to access Outlook on the web from a specific link within Outlook.
Users can access Outlook on the web by navigating to a direct URL with /mail/ appended.
As an example, some users can navigate to "https://outlook.office365.com/mail/" to
successfully access the client.
Department of Defense customers: https://webmail.apps.mil/mail/
GCCH customers: https://outlook.office365.us/mail/
Current status: We've determined that a recent code change is preventing users from accessing Outlook on the web from a specific link within Outlook. We've conducted our change reversion process to address the code issue and to remediate the impact. We're monitoring the environment to ensure no other impact persists and that the issue is resolved.
Scope of impact: This issue may prevent any user attempting to access Outlook on the web from the specific link in the More Info portion of this communication. This information may be updated as our investigation continues.
Start time: Tuesday, September 15, 2026, at 3:00 PM UTC
Root cause: A recent code change is producing a code regression that is preventing users from accessing Outlook on the web from a specific link within Outlook.
Next update by: Thursday, September 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Sep 16 13:38:52 2026 |
|---|
| Description: | Title: Users may be unable to access Outlook on the web from a specific Outlook link
User impact: Users may be unable to access Outlook on the web from a specific Outlook link.
Current status: We're investigating a potential issue with the Exchange Online service and are checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1474100 - Some users may be unable to access their Exchange Online mailboxes through Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 18 11:03:58 2026 |
|---|
| End Time: | Fri Sep 18 12:04:09 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 18 12:10:31 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 18 12:10:27 2026 |
|---|
| Description: | Title: Some users may be unable to access their Exchange Online mailboxes through Outlook on the web
User impact: Users may have been unable to access their Exchange Online mailboxes through Outlook on the web.
Final status: While we were in the process of analyzing the affected infrastructure, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users in North America who attempted to access their Exchange Online mailboxes through Outlook on the web may have been impacted.
Start time: Friday, September 18, 2026, at 11:20 AM UTC
End time: Friday, September 18, 2026, at 12:45 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 18 11:31:36 2026 |
|---|
| Description: | Title: Some users may be unable to access their Exchange Online mailboxes through Outlook on the web
User impact: Users may be unable to access their Exchange Online mailboxes through Outlook on the web.
Current status: We're reviewing service health telemetry, and we suspect that a portion of infrastructure responsible for facilitating mailbox access requests is performing below acceptable thresholds. We're determining our next steps towards addressing the performance issue and mitigating the impact.
Scope of impact: Some users in North America attempting to access their Exchange Online mailboxes through Outlook on the web may be impacted.
Next update by: Friday, September 18, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Sep 18 11:04:30 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
EX1473520 - Users may have encountered issues with the auto compose feature in Outlook mobile app for iOS
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 14 20:00:00 2026 |
|---|
| End Time: | Fri Sep 18 10:31:21 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 18 10:33:33 2026 |
|---|
| Root Cause: | A recent update to a search component that facilitates directory and suggestion requests contained a code error, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 18 10:33:21 2026 |
|---|
| Description: | Title: Users may have encountered issues with the auto compose feature in Outlook mobile app for iOS
User impact: Users may have encountered issues with the auto compose feature in Outlook mobile app for iOS.
More info: Impact was specific to directory searches, and suggestions when composing email messages from the Outlook app for IOS.
Final status: We've successfully deployed the fix and after an extended period of monitoring service health, we've confirmed that impact has been resolved.
Scope of impact: Impact was limited to approximately 10 percent of users performing directory searches or expecting suggestions within Outlook mobile on iOS.
Start time: Tuesday, September 15, 2026, at 12:00 AM UTC
End time: Friday, September 18, 2026, at 5:00 AM UTC
Root cause: A recent update to a search component that facilitates directory and suggestion requests contained a code error, resulting in 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: | Thu Sep 17 12:39:44 2026 |
|---|
| Description: | Title: Users may encounter issues with the auto compose feature in the Outlook mobile app for iOS client
User impact: Users may encounter issues with the auto compose feature in the Outlook mobile app for iOS client.
More info: Impact is specific to directory searches, and suggestions when composing email messages from the Outlook app for IOS.
Current status: We've identified that a recent update to a search component that facilitates directory and suggestion requests contains a code error, resulting in impact. We've developed a fix and are monitoring as it progresses.
Scope of impact: Impact is limited to approximately 10 percent of users performing directory searches or expecting suggestions within Outlook mobile on iOS.
Start time: Tuesday, September 15, 2026, at 12:00 AM UTC
Root cause: A recent update to a search component that facilitates directory and suggestion requests contains a code error, resulting in impact.
Next update by: Friday, September 18, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu Sep 17 12:16:46 2026 |
|---|
| Description: | Title: Users may encounter issues with the auto compose feature in Outlook mobile app for iOS
User impact: Users may encounter issues with the auto compose feature in Outlook mobile app for iOS.
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.
|
|---|
|
TM1394359 - Some users may have seen incorrect presence status information in Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Jun 17 04:30:00 2026 |
|---|
| End Time: | Wed Jun 17 05:35:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Sep 18 05:31:50 2026 |
|---|
| Root Cause: | The Unified Presence Service (UPS) is served through multiple data centers globally for capacity and resiliency reasons. To avoid capacity pressure with an ever-increasing service load, we have been making the long-term architectural change to add an additional data center in the Europe region to process Presence requests. As part of this, the new data center needed to be added to the Azure Traffic Manager (ATM) set-up in preparation for when it was ready to go live. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 18 05:31:50 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Aug 31 09:35:36 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 28 11:42:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jun 23 10:59:21 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jun 18 20:09:52 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 17 06:55:14 2026 |
|---|
| Description: | Title: Some users may have seen incorrect presence status information in Microsoft Teams
User impact: Some users may have seen incorrect presence status information in Microsoft Teams.
Final status: We have confirmed through our telemetry and from some of the previously affected customers that the issue is now resolved.
Scope of impact: This issue primarily affected users in EMEA, and users in other regions may have experienced impact when interacting with the affected users.
Start time: Wednesday, June 17, 2026, at 8:30 AM UTC
End time: Wednesday, June 17, 2026, at 9:35 AM UTC
Root cause: The Unified Presence Service (UPS) is served through multiple data centers globally for capacity and resiliency reasons. To avoid capacity pressure with an ever-increasing service load, we have been making the long-term architectural change to add an additional data center in the Europe region to process Presence requests. As part of this, the new data center needed to be added to the Azure Traffic Manager (ATM) set-up in preparation for when it was ready to go live.
A code bug in the configuration and subsequent miss in the review process resulted in the bad rollout file that was published to ATM. This resulted in inadvertently overwriting/replacing the existing full EMEA configuration that included all the existing data centers which were handling traffic, rather than being extended on top of the existing configuration. This meant that the service removed all the existing data centers from the ATM set-up for Presence and just left the newly added region, which was not in an operational state yet. As such, there were no reachable endpoints for Presence-related requests.
Since Azure Front Door (AFD) has caching for last known good DNS endpoints, we had some protection for client-side presence scenarios and only when a user’s caches expired would they have seen impact.
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 second update was provided on August 31, 2026. The next update will be provided by September 30. 2026.
|
|---|
|
| Time: | Wed Jun 17 06:32:03 2026 |
|---|
| Description: | Since we deployed the fix, we're observing a steady improvement in service recovery. We'll continue to monitor service telemetry for complete recovery.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 17 06:11:20 2026 |
|---|
| Description: | We’ve identified that a recent Teams traffic routing change introduced a misconfiguration, which unexpectedly resulted in impact. We’ve deployed a fix and are closely monitoring service telemetry to ensure full recovery.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 17 05:56:03 2026 |
|---|
| Description: | Title: Some users may see incorrect presence status information in Microsoft Teams
User impact: Some users may see incorrect presence status information 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: This issue is primarily affecting users in EMEA, and users in other regions may experience impact when interacting with the affected users.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 05:16:10 2026 |
|---|
| Description: | Title: Possible delays or problems when accessing Microsoft Teams
User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
DZ1459263 - Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 16:14:00 2026 |
|---|
| End Time: | Fri Sep 18 01:15:33 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 18 01:27:35 2026 |
|---|
| Root Cause: | A code regression after a recent service update impacted OData $Select query, which caused failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 18 01:27:31 2026 |
|---|
| Description: | Title: Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query
User impact: Users may have seen failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query.
More info: The issue specifically happened when using "$Select" as part of the query.
Affected users could've bypassed the issue by not using "$Select" in the queries.
Final status: We've confirmed that the deployment is complete and impact has been successfully resolved.
Scope of impact: This issue may have impacted any user querying the Microsoft Graph Attack Simulation Training API with $Select OData in Microsoft Defender.
Start time: Thursday, August 13, 2026, at 8:14 PM UTC
End time: Thursday, September 10, 2026, at 6:30 PM UTC
Root cause: A code regression after a recent service update impacted OData $Select query, which caused failures.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to querying 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 Sep 15 00:34:12 2026 |
|---|
| Description: | Title: Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query
User impact: Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query.
More info: The issue is specifically happening when using "$Select" as part of the query.
Affected users can bypass the issue by not using "$Select" in the queries.
Current status: We're continuing to monitor the saturation of the deployment, which we anticipate will complete by our next scheduled update, remediating the issue for all affected users.
Scope of impact: This issue may impact any user querying the Microsoft Graph Attack Simulation Training API with $Select OData in Microsoft Defender. This section may be updated as our investigation continues.
Start time: Thursday, August 13, 2026, at 8:14 PM UTC
Root cause: A code regression after a recent service update is impacting OData $Select query, causing failures.
Next update by: Friday, September 18, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 00:18:01 2026 |
|---|
| Description: | Title: Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query
User impact: Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query.
More info: The issue is specifically happening when using "$Select" as part of the query.
Affected users can bypass the issue by not using "$Select" in the queries.
Current status: We've completed the validation within our internal testing environment and begun initiating the fix deployment. As the deployment begins to propagate throughout the affected service environment, we anticipate that some users may experience relief from impact. Additionally, we expect that we will have acquired a complete remediation timeline by our next scheduled update.
Scope of impact: This issue may impact any user querying the Microsoft Graph Attack Simulation Training API with $Select OData in Microsoft Defender. This section may be updated as our investigation continues.
Start time: Thursday, August 13, 2026, at 8:14 PM UTC
Root cause: A code regression after a recent service update is impacting OData $Select query, causing failures.
Next update by: Tuesday, September 15, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Thu Aug 27 00:21:49 2026 |
|---|
| Description: | Title: Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query
User impact: Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query.
More info: The issue is specifically happening when using "$Select" as part of the query.
Affected users can bypass the issue by not using "$Select" in the queries.
Current status: We've started deploying the fix to our internal testing environment prior to releasing it to the affected environment. We expect the validations will be complete by our next scheduled update, and we'll aim to provide an updated resolution timeline.
Scope of impact: This issue may impact any user querying the Microsoft Graph Attack Simulation Training API with $Select OData in Microsoft Defender. This section may be updated as our investigation continues.
Start time: Thursday, August 13, 2026, at 8:14 PM UTC
Root cause: A code regression after a recent service update is impacting OData $Select query, causing failures.
Next update by: Wednesday, September 2, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Sat Aug 22 00:49:17 2026 |
|---|
| Description: | Title: Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query
User impact: Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query.
More info: The issue is specifically happening when using "$Select" as part of the query.
Affected users can bypass the issue by not using "$Select" in the queries.
Current status: Based on our analysis, we've determined that the code fix will take an extended amount of time to deploy to the affected environment. We're monitoring the progress and currently estimate that the fix will reach all affected environments by the middle of September 2026.
Scope of impact: This issue may impact any user querying the Microsoft Graph Attack Simulation Training API with $Select OData in Microsoft Defender. This section may be updated as our investigation continues.
Start time: Thursday, August 13, 2026, at 8:14 PM UTC
Root cause: A code regression after a recent service update is impacting OData $Select query, causing failures.
Next update by: Thursday, August 27, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Fri Aug 21 23:28:48 2026 |
|---|
| Description: | Title: Users see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query
User impact: Users see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query.
More info: The issue is specifically happening when using "$Select" as part of the query.
Affected users can bypass the issue by not using "$Select" in the queries.
Current status: We identified a code regression after a recent service update to Microsoft Defender for Office 365 that is impacting OData $Select queries. We've developed a code fix for the issue and are deploying to the affected environment to remediate the impact.
Scope of impact: This issue may impact any user querying the Microsoft Graph Attack Simulation Training API with $Select OData query.
Start time: Thursday, August 13, 2026, at 6:41 PM UTC
Root cause: A code regression after a recent service update is impacting OData $Select query, causing failures.
Next update by: Saturday, August 22, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Fri Aug 21 22:43:55 2026 |
|---|
| Description: | Title: Users see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query
User impact: Users see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query.
More info: The issue is specifically happening when using "$Select" as part of the query.
Affected users can bypass the issue by not using "$Select" in the queries.
Current status: We're investigating a potential issue with Microsoft Defender and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1473237 - Some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 15 23:00:00 2026 |
|---|
| End Time: | Fri Sep 18 00:51:39 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Sep 18 00:52:27 2026 |
|---|
| Root Cause: | A recent update introduced an issue affecting a component responsible for launching the app and resulted in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 18 00:52:24 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients
User impact: Users may have intermittently been unable to launch Microsoft Teams from the web or desktop clients.
Final status: Following an extended period of monitoring the service health telemetry, we’ve confirmed that impact has been remediated.
Scope of impact: Some users may have intermittently been unable to launch Microsoft Teams from the web or desktop clients.
Start time: Wednesday, September 16, 2026, at 3:00 AM UTC
End time: Thursday, September 17, 2026, at 11:12 AM UTC
Root cause: A recent update introduced an issue affecting a component responsible for launching the app and resulted in the impact.
Next steps: - We’re continuing to analyze how the recent service update was applied to understand why the potential for impact wasn't caught during the update testing and validation phase. These actions will help us to clarify what actions we can take to ensure that similar impact doesn't occur in the future and to continue our ongoing mission to improve the resilience of our service for all Microsoft Teams users.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 17 03:49:16 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients
User impact: Users may intermittently be unable to launch Microsoft Teams from the web or desktop clients.
Current status: We've confirmed that the issue is associated with a recent build update and have expanded our mitigation efforts by rolling affected deployments back to a last-known-good build. We've also implemented measures to prevent further rollout of the affected update while we continue monitoring service health and validating the effectiveness of the mitigation.
Scope of impact: Some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients. This information may be updated as our investigation continues.
Start time: Wednesday, September 16, 2026, at 3:00 AM UTC
Root cause: A recent update introduced an issue affecting a component responsible for launching the app, resulting in the impact.
Next update by: Friday, September 18, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Sep 17 02:13:12 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients
User impact: Users may intermittently be unable to launch Microsoft Teams from the web or desktop clients.
Current status: We’ve determined that a recent update introduced an issue affecting a component responsible for launching the app, resulting in the impact. We’ve initiated the reversion of the problematic update and will provide an estimated completion time once available.
Scope of impact: Some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients. This information may be updated as our investigation continues.
Start time: Wednesday, September 16, 2026, at 3:00 AM UTC
Root cause: A recent update introduced an issue affecting a component responsible for launching the app, resulting in the impact.
Next update by: Thursday, September 17, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Sep 17 00:59:27 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients
User impact: Users may intermittently be unable to launch Microsoft Teams from the web or desktop clients.
Current status: We suspect that a recent build update introduced this issue and we’re reviewing options to revert the offending changes to potentially remediate the impact.
Scope of impact: Some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients. This information may be updated as our investigation continues.
Next update by: Thursday, September 17, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Thu Sep 17 00:49:22 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients
User impact: Users may intermittently be unable to launch Microsoft Teams from the web or desktop clients.
Current status: We're investigating a potential issue in which some users may intermittently be unable to launch Microsoft Teams from the web or desktop clients and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1469836 - Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 27 20:00:00 2026 |
|---|
| End Time: | Thu Sep 17 17:26:14 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 17 17:45:18 2026 |
|---|
| Root Cause: | An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 17 17:45:15 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may have seen Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may have seen the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users displayed as 0
- Teams Chat Messages displayed as 0
- Teams Channel Messages displayed as 0
Final status: Our internal service telemetry has validated that the impacting error within the flow of service health telemetry data has been addressed, and that the impact has been resolved.
Scope of impact: This event impacted some admins, who may have seen Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
End time: Wednesday, September 16, 2026, at 7:20 PM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next steps:
- We're further analyzing the isolated error within the flow of service health telemetry data to help us prevent similar impacting events in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 16 15:04:31 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: We're continuing to validate with affected users that this issue has been successfully remediated for all impacted regions.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next update by: Thursday, September 17, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Sep 15 21:11:55 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: We've confirmed that the backfill has processed as expected and are reaching out to a portion of impacted users to verify that the issue has been remediated.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next update by: Wednesday, September 16, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Sep 14 20:52:56 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: We're continuing to monitor the progress of the backfill processing as more time is needed to ensure its completion and confirm if impact is resolved.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next update by: Wednesday, September 16, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Sep 11 21:16:58 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: The affected data backfill remains in progress and is taking longer than expected. We’re monitoring its progress and expect processing to complete to resolve the issue by our next scheduled update.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next update by: Tuesday, September 15, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Sep 11 17:37:11 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: We’re continuing to backfill the affected data to fully remediate this event. Based on current progress, we anticipate this process will complete by our next scheduled update.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next update by: Saturday, September 12, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Sep 10 13:34:36 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: We've determined that an error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact. We've addressed the underlying issue and are currently in the process of backfilling the data to fully remediate this event.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next update by: Friday, September 11, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Sep 9 14:11:19 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: We've received reports from a subset of admins noting inaccuracies or discrepancies in Microsoft Teams usage reports in the Microsoft 365 admin center starting from August 25, 2026. We're attempting to reproduce the issue to further our understanding of the current impact scenario and to determine our next troubleshooting steps.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Next update by: Thursday, September 10, 2026, at 11:00 PM UTC
|
|---|
|
OP1454727 - Some users were unable to sign in to OneNote using iOS devices
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 20 00:36:00 2026 |
|---|
| End Time: | Sun Aug 30 20:00:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 17 06:43:11 2026 |
|---|
| Root Cause: | A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests were routed, introduced an issue with OneNote iOS Authenticator broker sign-in and caused impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 17 05:58:46 2026 |
|---|
| Description: | Title: Some users were unable to sign in to OneNote using iOS devices
User impact: Users were unable to sign in to OneNote using iOS devices.
More info: Impact was specific to any user with OneNote build 16.112.717.0 or higher.
Whilst we were working on remediation, some impacted users were able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Some users were also able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Final status: We've completed deployment of the fix and confirmed with your organization that impact has been resolved.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices was impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
End time: Monday, August 31, 2026, at 12:00 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests were routed, introduced an issue with OneNote iOS Authenticator broker sign-in and caused impact.
Next steps:
- We're reviewing our deployment and validation processes to help prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 05:55:10 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've completed the validation of our fix in our internal testing environment and are preparing it for deployment, which should complete by our next scheduled update. Additionally, we've received confirmation from a subset of users who reported the issue that the fix resolves impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. This information may be updated as our investigation continues.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Thursday, September 17, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 02:38:25 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: Current status: We're progressing with the validation of our fix in our internal testing environment. Additionally, we're continuing to await confirmation from a subset of users who reported the issue and have received the fix to help with validating its efficacy so we can proceed with its full release.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. This information may be updated as our investigation continues.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Thursday, September 3, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:58:26 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: Validating the efficiency of the fix is taking longer than expected. We're continuing with the validations in our internal testing environment, and we've released the new version containing the fix to a subset of users who reported the issue to help with validating if it remediates impact as expected.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. This information may be updated as our investigation continues.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Wednesday, September 2, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Aug 25 01:57:38 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've identified that additional testing and validations are required in order to ensure the issue is resolved without adversely impacting other aspects of the service. We've halted the release, and we're deploying it to our internal testing environment for additional validation before releasing it to the app store. Once our validations are complete, we'll aim to provide a new timeline for when we expect the deployment to be available in the App store.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. This information may be updated as our investigation continues.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Tuesday, September 1, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Aug 24 01:21:03 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We confirmed that the fix will be part of the updated version of the OneNote app on iOS and are monitoring its implementation on the App Store. Once available, we'll confirm that the updated version remediates the impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Tuesday, August 25, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Fri Aug 21 18:43:26 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We’re continuing to monitor our fix deployments progress as it continues to saturate throughout the affected environment. Additionally, we expect that a remediation timeline will be provided by our next scheduled update.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Monday, August 24, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Tue Aug 18 00:57:55 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: Our fix deployment is taking longer than anticipated but is ongoing. We're continuing to monitor as it progresses to establish a completion timeline.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Friday, August 21, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 11:55:05 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've identified that a code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact. We're deploying a code fix to correct this issue and expect that it'll complete deployment by the time of our next update.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Tuesday, August 18, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 09:49:58 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've identified an issue with the OneNote iOS Authenticator broker sign-in and are working on developing and validating a fix to remediate impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Root cause: An issue with the OneNote iOS Authenticator broker sign-in is preventing users from signing in to OneNote using iOS devices.
Next update by: Friday, August 14, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 07:53:15 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
Current status: We've identified that a recent change to the sign in flow may be causing impact to occur. We've reverted the change but this did not resolve the issue. We're analyzing OneNote logs from impacted users as well as OneNote logs from our internal reproduction of the issue to assist us in identifying the underlying root cause of impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Next update by: Friday, August 14, 2026, at 2:00 PM UTC
|
|---|
|
MO1472904 - Some users in the United States and United Kingdom may be unable to access Microsoft 365 services
| Status: | investigationSuspended |
|---|
| Start Time: | Wed Sep 16 09:22:00 2026 |
|---|
| End Time: | Wed Sep 16 10:54:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Sep 16 16:11:05 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 16 14:20:40 2026 |
|---|
| Description: | Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services
User impact: Users in the United States and United Kingdom may have been unable to access Microsoft 365 services.
More info: Impacted users may have encountered 502 or 503 errors when attempting to access Microsoft 365 services.
Final status: We’ve thoroughly reviewed our telemetry and can confirm there were no issues within the Microsoft-managed environment, which remained healthy throughout this event. We're aware of third-party outages affecting multiple online services inside and outside of the Microsoft ecosystem which may have contributed to impact.
Scope of impact: Users in the United States and United Kingdom attempting to use Microsoft 365 services may have been impacted.
Start time: Wednesday, September 16, 2026, at 1:22 PM UTC
End time: Wednesday, September 16, 2026, at 2:54 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 16 13:00:07 2026 |
|---|
| Description: | Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services
User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services.
More info: Impacted users may encounter 502 or 503 errors when attempting to access Microsoft 365 services.
Current status: Impact reports have largely subsided, and service telemetry continues to indicate stable service conditions. Our investigation hasn’t identified a corresponding issue within the Microsoft 365 service environment, and we’re assessing whether conditions outside the core service path contributed to the reported impact. We’re continuing to monitor service health and validate sustained recovery.
Start time: Wednesday, September 16, 2026, at 1:22 PM UTC
Next update by: Wednesday, September 16, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 12:16:48 2026 |
|---|
| Description: | Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services
User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services.
More info: Impacted users may encounter 502 or 503 errors when attempting to access Microsoft 365 services.
Current status: Impact reports continue to decrease. Our investigation has not identified any issues with core Microsoft 365 components. As part of our ongoing root cause analysis, we're focusing on the request paths and dependency conditions associated with the reported Single Sign-On (SSO) failures and 5xx errors, while continuing to monitor and confirm sustained recovery.
Start time: Wednesday, September 16, 2026, at 1:22 PM UTC
Next update by: Wednesday, September 16, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 11:42:52 2026 |
|---|
| Description: | The majority of impact reports have subsided, however, we continue to investigate. Specifically, we're reviewing multiple sections of the request flows, including IP filtering, upstream dependencies and service access paths associated with the reported Single Sign-On (SSO) failures.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 16, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 11:06:26 2026 |
|---|
| Description: | Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services
User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services.
More info: Impacted users may encounter 502 or 503 errors when attempting to access Microsoft 365 services.
Current status: Our investigation remains focused on the cause of the Single Sign-On (SSO) failures and associated 5xx errors. In parallel, we're reviewing upstream dependencies to determine whether they are contributing to the impact. While some affected customers have reported improvement in service availability, our investigation continues as we work towards a full resolution.
Start time: Wednesday, September 16, 2026, at 1:22 PM UTC
Next update by: Wednesday, September 16, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 10:30:35 2026 |
|---|
| Description: | Title: Some users in the United States and United Kingdom may be unable to access Microsoft 365 services
User impact: Users in the United States and United Kingdom may be unable to access Microsoft 365 services.
Current status: We're reviewing service telemetry while investigating reports of users encountering 502 and 503 errors when accessing Microsoft 365 services. Recent user reports indicate the impact may be decreasing and we're continuing to analyze service health data to determine whether service conditions are improving and to isolate the source of impact.
Scope of impact: Impact is specific to users attempting to access Microsoft 365 services and users whose service requests are routed through the United States and United Kingdom regions. This information may be updated as our investigation continues.
Next update by: Wednesday, September 16, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 10:06:34 2026 |
|---|
| Description: | We're reviewing service telemetry and investigating user reports of 502 and 503 errors when attempting to access Microsoft 365 services to further isolate the source of impact and determine our next remediation steps.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 16, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Sep 16 09:49:36 2026 |
|---|
| Description: | Title: Some users in the United States may be unable to access Microsoft 365 services
User impact: Users in the United States may be unable to access Microsoft 365 services.
Current status: We're reviewing service monitoring telemetry and associated reports to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Impact is specific to users in the United States attempting to access Microsoft 365 services. This information may be updated as our investigation continues.
Next update by: Wednesday, September 16, 2026, at 3:30 PM UTC
|
|---|
|
MO1471241 - Some admins' usage reports may contain stale data in Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Sun Sep 13 00:56:15 2026 |
|---|
| End Time: | Wed Sep 16 14:50:10 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 16 14:51:23 2026 |
|---|
| Root Cause: | Our upstream data pipeline encountered refresh errors and failures when retrieving up-to-date data for the listed reports, which resulted in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 16 14:51:20 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: Impacted report types included:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
Final status: After monitoring the backlog processing for the final remaining impacted report type, we've confirmed that all usage report types listed in the "More Info" section are now created with up-to-date data.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may have been impacted by this issue.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
End time: Wednesday, September 16, 2026, at 8:40 AM UTC
Root cause: Our upstream data pipeline encountered refresh errors and failures when retrieving up-to-date data for the listed reports, which resulted in this impact.
Next steps:
- We're continuing to optimize our data processing pipeline to meet increasing user demand and ensure robust service uptime.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 15 22:34:48 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: Previously impacted report types included:
- OneDrive usage reports in North America and Asia Pacific
- SharePoint usage reports in North America, Asia Pacific, and Europe
- Group Activity reports in North America, Asia Pacific, and Europe
Current status: We've determined that most affected reports are now populating normally, though the remaining backlog of OneDrive reports for users in Europe is taking longer to clear than anticipated. We’re monitoring progress to confirm that the remaining reports are generated successfully.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Wednesday, September 16, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Sep 15 18:41:30 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: Previously impacted report types included:
- OneDrive usage reports in North America and Asia Pacific
- SharePoint usage reports in North America, Asia Pacific, and Europe
- Group Activity reports in North America, Asia Pacific, and Europe
Current status: While the majority of the usage reports are no longer delayed, processing of the backlog of OneDrive usage reports for users in Europe is taking longer than previously expected. We're continuing to monitor its progress to ensure that the final subset of usage reports are created as expected.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Wednesday, September 16, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Sep 15 15:37:07 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
These reports may not have refreshed since September 8, 2026.
Current status: We've confirmed that all reports have recovered with the exception of OneDriveUsage in Europe. We anticipate that the recovery of these last reports will be complete by our next scheduled update, fully resolving the event for all affected environments.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Wednesday, September 16, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Sep 15 12:12:56 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
These reports may not have refreshed since September 8, 2026.
Current status: We've confirmed that most reports have recovered and we expect complete recovery by our next scheduled update.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Tuesday, September 15, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Sep 14 20:34:32 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
These reports may not have refreshed since September 8, 2026.
Current status: Due the size of the data backlog, we've determined that we'll need to continue monitoring the report refresh rate for a longer period of time to ensure remediation. We expect to be able to provide a firm timeline by the time of our next scheduled communication update.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Tuesday, September 15, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Sep 14 17:48:53 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
These reports may not have refreshed since September 8, 2026.
Current status: We've observed recovery in some processes which manage data processing and report generation. We're continuing to monitor the refresh rate of the impacted reports to ensure usage data report freshness.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Tuesday, September 15, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Sep 14 13:21:10 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
These reports may not have refreshed since September 8, 2026.
Current status: After implementing our solution to resolve the delays that are resulting from a portion of the upstream data processing pipeline, we're monitoring the refresh rate of the impacted reports to validate that our remediation is effective.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Monday, September 14, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Sun Sep 13 01:18:58 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
These reports may not have refreshed since September 8, 2026.
Current status: We've identified that our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact. We're implementing a solution to the affected pipeline to restore the normal processing flow and recover delayed data as swiftly as possible. We anticipate being able to provide a timeline for resolution by our next scheduled communications update.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Monday, September 14, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Sun Sep 13 01:00:53 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive Usage reports
- SharePoint Usage reports
- Group Activity reports
Current status: We're investigating a potential issue with usage reports and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1465910 - Users may have been unable to load themes in Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 24 07:00:00 2026 |
|---|
| End Time: | Mon Sep 7 04:38:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 16 06:10:44 2026 |
|---|
| Root Cause: | A recent update, intended to enhance security hardening, inadvertently introduced a regression which was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 16 05:00:19 2026 |
|---|
| Description: | Title: Users may have been unable to load themes in Outlook on the web
User impact: Users may have been unable to load themes in Outlook on the web.
Final status: We've received confirmation from a sample of impacted users that the mitigation was successful and the issue is no longer occurring.
Scope of impact: Some users attempting to load themes in Outlook on the web may have been impacted.
Start time: Friday, July 24, 2026, at 11:00 AM UTC
End time: Monday, September 7, 2026, at 8:38 AM UTC
Root cause: A recent update, intended to enhance security hardening, inadvertently introduced a regression which was resulting in 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: | Mon Sep 14 04:14:19 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've determined that a recent update, intended to enhance security hardening, inadvertently introduced a regression which is resulting in impact. We've reverted the update and following a period of monitoring validation, confirmed that impact has been resolved for the majority of affected users. We're continuing to work with a small number of users who remain affected to conduct additional troubleshooting to fully restore the service.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 11:00 AM UTC
Root cause: A recent update, intended to enhance security hardening, inadvertently introduced a regression which is resulting in impact.
Next update by: Wednesday, September 16, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Fri Sep 11 01:03:24 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We’re continuing our efforts with a subset of affected users to gather additional details regarding the expected theme configuration as well as if users are able to reproduce the issue so we can determine our next troubleshooting steps.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, September 14, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Sep 10 06:55:12 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've reviewed diagnostic data from affected users and confirmed that theme data is being retrieved during client startup. We're working with affected organizations to gather additional details regarding the expected theme configuration and are comparing data from impacted and recovered users to identify any missing information or visual elements that may be contributing to the issue.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, September 11, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Sep 10 04:33:24 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've obtained the HAR logs provided by affected users and identified activity indicating theme data is being retrieved during client startup. We're correlating these findings with machine logs from the affected devices to determine whether this behavior is contributing to the reported impact and to isolate the underlying root cause.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, September 10, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Sep 8 03:12:40 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We're awaiting a response from your organization with HAR logs from affected users who continue to experience impact, as the issue persists despite the rollback. These logs will help us further investigate the remaining impact.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted.
Next update by: Thursday, September 10, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Sep 7 03:58:50 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We're awaiting new HAR logs from users who continue to experience impact following the rollback to help determine why they're still encountering the issue.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted.
Next update by: Tuesday, September 8, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Sep 3 22:58:34 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've received confirmation from a large portion of affected users that impact is resolved; however, some users are still reporting that impact persists for them. We're working to gather and review new HTTP Archive format (HAR) trace logs from affected users to help understand why impact still persists for them.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Monday, September 7, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Sep 3 04:49:26 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've received confirmation from some affected users that impact is resolved. We're reaching out to additional impacted users to confirm that the issue is fully resolved.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 21:20:13 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've rolled back a recent authentication related change that we suspect is contributing to the impact. We're reaching out to affected users to confirm whether our mitigative action has resolved this issue, which will also aid in confirming our root cause theory.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Thursday, September 3, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 17:43:48 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: Our investigation of the web startup process issue is still ongoing to further isolate the reason for the impact and help us determine the next steps to remediate the impact.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Thursday, September 3, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 16:17:24 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We're continuing to review our service side logs to gather more information regarding the web startup process issue and determine why it's preventing the themes from loading, so that we can developed a mitigation strategy.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 02:20:15 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've identified an issue occurring during the Outlook on the web startup process that's preventing themes from loading as expected. We're reviewing system logs to understand what is causing the behavior, which will help us isolate our next steps toward remediation.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Wednesday, September 2, 2026, at 8:30 PM UTC
|
|---|
|
DZ1472548 - Users see delays in Threat Explorer and Advanced Hunting data in Microsoft Defender for Office 365
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 14 12:30:00 2026 |
|---|
| End Time: | Wed Sep 16 00:40:28 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 16 00:43:06 2026 |
|---|
| Root Cause: | Increased traffic to the portion of service infrastructure that facilitates this data was resulting in delays in the service.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 16 00:43:03 2026 |
|---|
| Description: | Title: Users see delays in Threat Explorer and Advanced Hunting data in Microsoft Defender for Office 365
User impact: Users saw delays in Threat Explorer and Advanced Hunting data in Microsoft Defender for Office 365.
More info: Users may have seen delays with the following data:
- Latest delivery location in Threat Explorer
- Verdict in Threat Explorer
- Zero-hour auto purge (ZAP) events in Advanced Hunting
- Manual Remediation in Advanced Hunting
Final status: Following the backlog's full completion and an extended period of monitoring the affected infrastructure, we’ve confirmed that impact has been remediated.
Scope of impact: Your organization was impacted by this event, and users saw delays in Threat Explorer and Advanced Hunting data in Microsoft Defender for Office 365.
Start time: Monday, September 14, 2026, at 4:30 PM UTC
End time: Wednesday, September 16, 2026, at 12:30 AM UTC
Root cause: Increased traffic to the portion of service infrastructure that facilitates this data was resulting in delays in the service.
Next steps: - We’re continuing to analyze why the increase in traffic to the portion of service infrastructure that facilitates Threat Explorer and Advanced Hunting data in Microsoft Defender for Office 365 manifested, as these actions will help us to clarify what actions we can take to ensure similar impact doesn't occur in the future and to continue our ongoing mission to improve the resilience of our service for all Microsoft Defender for Office 365 users.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 15 16:44:58 2026 |
|---|
| Description: | Title: Users see delays in Threat Explorer and Advanced Hunting data in Microsoft Defender for Office 365
User impact: Users see delays in Threat Explorer and Advanced Hunting data in Microsoft Defender for Office 365.
More info: Users may see delays with the following data:
- Latest delivery location in Threat Explorer
- Verdict in Threat Explorer
- Zero-hour auto purge (ZAP) events in Advanced Hunting
- Manual Remediation in Advanced Hunting
Current status: We've determined that increased traffic to the portion of service infrastructure that facilitates this data was resulting in delays in the service. We applied a fix to regulate the flow of traffic and have confirmed that this successfully restore the pipeline. We anticipate that the backlog of data will complete processing and remediate this event by our next scheduled communication.
Scope of impact: Your organization is impacted by this event, and users see delays in Threat Explorer and Advanced Hunting data in Microsoft Defender for Office 365. This information may be updated as our investigation continues.
Start time: Tuesday, September 15, 2026, at 4:30 PM UTC
Root cause: Increased traffic to the portion of service infrastructure that facilitates this data is resulting in delays in the service.
Next update by: Wednesday, September 16, 2026, at 6:30 AM UTC
|
|---|
|
PB1472181 - Microsoft Fabric users may have experienced issues with creating new support cases through the Contact support page
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 15 03:18:03 2026 |
|---|
| End Time: | Tue Sep 15 04:14:15 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 15 04:16:12 2026 |
|---|
| Root Cause: | A recent change in an upstream API that PowerBI and Microsoft Fabric relies on for creating support tickets caused an internal server error that causing support ticket creation to fail.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 15 04:16:09 2026 |
|---|
| Description: | Title: Microsoft Fabric users may have experienced issues with creating new support cases through the Contact support page
User impact: Microsoft Fabric users may have experienced issues with creating new support cases through the Contact support page.
More info: Affected users may have experienced an empty support plan list when attempting to create a support request through the Microsoft Fabric Get Support experience.
Final status: We've determined that a recent change in an upstream API that PowerBI and Microsoft Fabric relies on for creating support tickets caused an internal server error that caused support ticket creation to fail. We've reverted the change and confirmed that the service has been restored and affected users should no longer experience impact.
Scope of impact: Any user attempting to create a support request through the Microsoft Fabric Get Support experience may have been affected.
Start time: Tuesday, September 15, 2026, at 12:30 AM UTC
End time: Tuesday, September 15, 2026, at 7:30 AM UTC
Root cause: A recent change in an upstream API that PowerBI and Microsoft Fabric relies on for creating support tickets caused an internal server error that causing support ticket creation to fail.
Next steps:
- We're reviewing our upstream API change procedures to help prevent similar problems in the future.
This is the final update for this event.
|
|---|
|
| Time: | Tue Sep 15 03:23:09 2026 |
|---|
| Description: | Title: Microsoft Fabric users may experience issues with creating new support cases through the Contact support page
User impact: Microsoft Fabric users may experience issues with creating new support cases through the Contact support page.
More info: Users may experience an empty support plan list when attempting to create a support request through the Microsoft Fabric Get Support experience.
Current status: We're investigating a potential issue affecting support plan selection in Microsoft Fabric and reviewing available diagnostic data to determine the cause and scope of impact.
Scope of impact: Any user attempting to create a support request through the Microsoft Fabric Get Support experience may be affected.
Start time: Tuesday, September 15, 2026, at 12:30 AM UTC
Next update by: Tuesday, September 15, 2026, at 9:30 AM UTC
|
|---|
|
FL1437452 - Flow management and manual invocation operations are failing
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 11:10:00 2026 |
|---|
| End Time: | Thu Jul 23 15:45:00 2026 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 15:49:46 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 14 15:49:46 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Aug 18 17:37:11 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 28 18:31:03 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 23 16:37:27 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations were failing.
Final Status: Following a period of service health diagnostic analysis, we confirmed that service functionality is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A portion of the network infrastructure supporting flow management and manual invocation operations entered an unhealthy state.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Thu Jul 23 15:50:09 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operation are failing.
Current Status: We are continuing to monitor service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 14:49:57 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations are failing.
Current Status: We completed the failover to healthy redundant infrastructure and are monitoring service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:48:06 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations are failing.
Current Status: After our investigation, we determined that a portion of the network infrastructure supporting flow management and manual invocation operations entered an unhealthy state, leading to impact. To mitigate the issue, we are performing a failover to healthy redundant infrastructure.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:46:56 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations are failing.
Current Status: We are aware of an emerging issue where flow management and manual invocation operations are failing. 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.
|
|---|
|
DV1437448 - Users are experiencing intermittent failures accessing your Dataverse data or apps
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 13:10:00 2026 |
|---|
| End Time: | Thu Jul 23 15:32:00 2026 |
|---|
| Service: | Microsoft Dataverse |
|---|
| Feature Group: | Environment access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 15:05:04 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 14 15:05:04 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Aug 18 17:56:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 28 18:29:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 23 16:36:28 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users were experiencing intermittent failures accessing your Dataverse data or apps.
Final Status: Following a period of service health diagnostic analysis, we confirmed that service functionality is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A portion of the network infrastructure supporting your environment entered an unhealthy state.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Thu Jul 23 15:50:00 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: We are continuing to monitor service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 14:49:42 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: We completed the failover to healthy redundant infrastructure and are monitoring service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:41:49 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: After our investigation, we determined that a portion of the network infrastructure supporting your environment has entered an unhealthy state, leading to impact. To mitigate the issue, we are performing a failover to healthy redundant infrastructure.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:27:33 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: We are aware of an emerging issue where users are experiencing intermittent failures accessing your Dataverse data or apps. 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.
|
|---|
|
EX1471707 - Users may have experienced errors accessing their mailbox through one or more Exchange Online connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 14 05:55:00 2026 |
|---|
| End Time: | Mon Sep 14 10:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 10:46:43 2026 |
|---|
| Root Cause: | A section of Exchange Online infrastructure was performing below acceptable performance thresholds, which affected mailbox availability for some users.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 14 10:35:32 2026 |
|---|
| Description: | Title: Users may have experienced errors accessing their mailbox through one or more Exchange Online connection methods
User impact: Users may have experienced errors accessing their mailbox through one or more Exchange Online connection methods.
More info: Affected users may have been unable to access their mailbox through Outlook on the web, Outlook desktop, Exchange ActiveSync, or other Exchange Online connection methods. Users may have encountered service errors, including 503 responses, intermittent connection failures, or have been unable to access mailbox content while the issue persisted.
Final status: We've determined that a section of Exchange Online infrastructure was performing below acceptable performance thresholds, which affected mailbox availability for some users. We've restarted the affected infrastructure and confirmed through service monitoring that impact has been successfully remediated.
Scope of impact: Impact was specific to users attempting to access their mailbox through Outlook on the web, Outlook desktop, Exchange ActiveSync, or other Exchange Online connection methods.
Start time: Monday, September 14, 2026, at 9:55 AM UTC
End time: Monday, September 14, 2026, at 2:00 PM UTC
Root cause: A section of Exchange Online infrastructure was performing below acceptable performance thresholds, which affected mailbox availability for some users.
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 this event.
|
|---|
|
| Time: | Mon Sep 14 08:51:16 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
More info: Affected users may be unable to access their mailbox through Outlook on the web, Outlook desktop, Exchange ActiveSync, or other Exchange Online connection methods. Users may encounter service errors, including 503 responses, intermittent connection failures, or be unable to access mailbox content while the issue persists.
Current status: We've identified an issue within a portion of the Exchange Online service infrastructure that's affecting mailbox availability for some users. We're investigating the underlying cause and reviewing service telemetry to determine why mailbox access requests are failing. We're monitoring the affected environment and continuing our efforts to restore consistent access to impacted mailboxes.
Scope of impact: Impact is specific to users attempting to access their mailbox through Outlook on the web, Outlook desktop, Exchange ActiveSync, or other Exchange Online connection methods.
Next update by: Monday, September 14, 2026, at 3:00 PM UTC
|
|---|
|
TM1458147 - Some users saw incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 5 17:44:00 2026 |
|---|
| End Time: | Fri Sep 11 07:56:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 11 09:57:12 2026 |
|---|
| Root Cause: | A recent code change caused the event validation process to display incorrect warning banners.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 11 09:56:15 2026 |
|---|
| Description: | Title: Some users saw incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
User impact: Users saw incorrect attendee capacity warnings when configuring Microsoft Teams town hall events.
More info: We've confirmed that there was no impact to actual attendee capacity.
Users may have seen the following message:
"Attendee capacity issue. This event is set for 10,000 attendees, but your current limit is 3,000. Attendees above this limit won't be able to join. Contact your Teams administrator to restore capacity."
Final status: We've identified that impact was due to a recent code change which caused the event validation process to display incorrect warning banners. We've completed deployment of the fix across the affected environments and confirmed through service telemetry that impact has been remediated.
Scope of impact: Your organization was affected by this event, and users who were seeing incorrect attendee capacity warnings when configuring Microsoft Teams Town Hall events were impacted.
Start time: Wednesday, August 5, 2026, at 9:44 PM UTC
End time: Friday, September 11, 2026, at 11:56 AM UTC
Root cause: A recent code change caused the event validation process to display incorrect warning banners.
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: | Mon Sep 7 07:48:06 2026 |
|---|
| Description: | Title: Some users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
User impact: Users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events.
More info: We've confirmed that there is no impact to actual attendee capacity.
Users may see the following message:
"Attendee capacity issue. This event is set for 10,000 attendees, but your current limit is 3,000. Attendees above this limit won't be able to join. Contact your Teams administrator to restore capacity."
Current status: We've determined that the fix is taking longer than anticipated to deploy. We'll continue to monitor deployment progress as it continues.
Scope of impact: Your organization is affected by this event, and users seeing incorrect attendee capacity warnings when configuring Microsoft Teams Town Hall events are impacted.
Estimated time to resolve: Tuesday, September 1, 2026
Next update by: Friday, September 11, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Sep 2 07:04:04 2026 |
|---|
| Description: | Title: Some users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
User impact: Users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events.
More info: We've confirmed that there is no impact to actual attendee capacity.
Users may see the following message:
"Attendee capacity issue. This event is set for 10,000 attendees, but your current limit is 3,000. Attendees above this limit won't be able to join. Contact your Teams administrator to restore capacity."
Current status: We're progressing with the fix deployment and expect completion by Monday, September 7, 2026.
Scope of impact: Your organization is affected by this event, and users seeing incorrect attendee capacity warnings when configuring Microsoft Teams Town Hall events are impacted.
Estimated time to resolve: Tuesday, September 1, 2026
Next update by: Monday, September 7, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Aug 20 09:03:30 2026 |
|---|
| Description: | Title: Some users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
User impact: Users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events.
More info: We've confirmed that there is no impact to actual attendee capacity.
Users may see the following message:
"Attendee capacity issue. This event is set for 10,000 attendees, but your current limit is 3,000. Attendees above this limit won't be able to join. Contact your Teams administrator to restore capacity."
Current status: We've confirmed that some users are incorrectly seeing attendee capacity warnings when configuring Microsoft Teams town hall events. We've also confirmed that there is no impact to actual attendee capacity. We've deployed a fix to the service intended to remove the banner and expect the fix to reach the affected infrastructure in early September, 2026.
Scope of impact: Your organization is affected by this event, and users seeing incorrect attendee capacity warnings when configuring Microsoft Teams Town Hall events are impacted.
Estimated time to resolve: Tuesday, September 1, 2026
Next update by: Wednesday, September 2, 2026, at 11:30 AM UTC
|
|---|
|
EX1470457 - Some users may be unable to send or receive Exchange Online email through the native macOS mail app
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 8 20:00:00 2026 |
|---|
| End Time: | Thu Sep 10 23:35:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Sep 11 00:19:58 2026 |
|---|
| Root Cause: | A service feature deployment affecting rate limitations contained changes resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 11 00:10:53 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive Exchange Online email through the native macOS mail app
User impact: Users may have been unable to send or receive Exchange Online email through the native macOS mail app.
Final status: We've disabled the impacting changes and confirmed through internal telemetry that impact has been fully remediated.
Scope of impact: Some users attempting to access the native macOS mail app were impacted.
Start time: Wednesday, September 9, 2026, at 12:00 AM UTC
End time: Friday, September 11, 2026, at 3:35 AM UTC
Root cause: A service feature deployment affecting rate limitations contained changes resulting in impact.
Next steps:
- We're reviewing our update testing and validation methods to better identify issues such as this prior to deployment so we can ensure we prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 10 22:35:43 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive Exchange Online email through the native macOS mail app
User impact: Users may be unable to send or receive Exchange Online email through the native macOS mail app.
Current status: We've identified that a service feature deployment affecting rate limitations contained changes resulting in impact. We're moving to disable the problematic changes and anticipate this should be fully in effect by our next scheduled update, at which point we'll verify the issue is resolved through internal telemetry.
Scope of impact: Some users attempting to access the native macOS mail app are impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 12:00 AM UTC
Root cause: A service feature deployment affecting rate limitations contained changes resulting in impact.
Next update by: Friday, September 11, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Sep 10 22:12:58 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive Exchange Online email through the native macOS mail app
User impact: Users may be unable to send or receive Exchange Online email through the native macOS mail app.
Current status: We've clarified that reporting users are seeing impact to the native mail app on macOS and updated the Title and User impact fields of this communication accordingly. We're reviewing service logs and telemetry data to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Some users attempting to access the native macOS mail app are impacted. This information may be updated as our investigation continues.
Next update by: Friday, September 11, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Sep 10 21:10:32 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive Exchange Online email through the native macOS mail app
User impact: Users may be unable to send or receive Exchange Online email through the native macOS 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 60 minutes.
|
|---|
|
MO1465074 - Users may experience issues when utilizing multiple Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Aug 31 10:56:00 2026 |
|---|
| End Time: | Thu Sep 3 06:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 10 20:47:34 2026 |
|---|
| Root Cause: | An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 20:47:34 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 13:28:10 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 13:11:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Sep 8 05:35:25 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sat Sep 5 15:48:19 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 3 16:04:09 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may have experienced issues when utilizing multiple Microsoft 365 services.
More info: Impact is fully resolved. Previously identified impact included the services and scenarios listed below.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted access and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
- Users couldn’t download email message attachments through any Exchange Online connection method.
- Users may have been unable to sign in to Outlook on the web.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated, and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may have been stale and not updated automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experienced delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Final status: Based on our telemetry all previously impacted services have remained healthy since impact was remediated on Thursday, September 3, 2026, at 10:00 AM UTC, and this issue is resolved.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may have been affected by this event.
Start time: Monday, August 31, 2026, at 2:56 PM UTC
End time: Thursday, September 3, 2026, at 10:00 AM UTC
Preliminary root cause: An issue within a core access configuration used by multiple Microsoft 365 services was resulting in impact.
Next steps:
- We’re evaluating our core service configurations to prevent the recurrence of similar impact in the future. In addition, we're further reviewing our monitoring systems to ensure we identify and are expediently alerted to these types of scenarios.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Sep 3 14:24:20 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is now fully resolved. Previously identified impact included the services and scenarios listed below.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
- Users couldn’t download email message attachments through any Exchange Online connection method.
- Users may have been unable to sign in to Outlook on the web.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: All user impact scenarios are now resolved as we rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of our infrastructure. We will continue to monitor our telemetry to ensure all services remain healthy and plan to close this communication by our next scheduled update.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Friday, September 4, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 12:24:26 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Outlook on the web, Outlook mobile apps, and Outlook for Mac. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We discovered an issue in less than one percent of our infrastructure, where our additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. We remain committed to restoring all services to all users and will continue to carefully monitor our telemetry to ensure recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 10:26:52 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: While monitoring service telemetry closely, we identified a small volume of errors affecting mail flow functionality. We're conducting targeted restarts to reduce the number of errors and alleviate impact. In parallel, we're continuing to analyze service health telemetry to determine if any additional mitigation actions are required to restore normal functionality.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 08:27:31 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We're continuing to implement further mitigation actions where required to resolve any outstanding impact associated with this incident. Customer feedback and reports from our telemetry remain positive, and service health is stable. While this work is underway, we're actively monitoring the service closely to ensure stability is consistent.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 06:25:08 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We're performing additional remediation efforts where necessary to address any remaining impact from this incident. Reports from telemetry data and customer feedback are aligned, indicating a sustained recovery. We're actively monitoring the situation closely to ensure impact is completely mitigated.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 04:25:02 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From Purview Communications compliance perspective, this issue is mitigated. Customers should be able to use the portal. We are running backfill for any missed policy hits and those should appear in the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We're continuing to closely monitor the service to ensure sustained stability, and signals from telemetry and customer feedback remain positive. In parallel, we're conducting additional remediation actions where required to resolve any lingering residual impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Sep 3 02:20:32 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We've confirmed that our services remain stable, and both telemetry and customer reports indicate that the issue has been largely mitigated. We're continuing to address any lingering issues while we remain engaged in an extended monitoring period to validate sustained recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Sep 3 00:16:34 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: Our recovery metrics remain positive, with monitoring continuing to indicate that the service is stable and there is a constant reduction in the number of affected users. We’re continuing to validate recovery through targeted remediation actions and service health checks. We’ll maintain targeted monitoring and validation actions to confirm recovery outcomes and identify any remaining impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 22:21:18 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: Ongoing monitoring continues to show positive recovery progress, with impact no longer observed for most previously affected users. We’re continuing to monitor service health and implement targeted remediation efforts to validate recovery progress and help ensure ongoing service stability.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 20:28:48 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We continue to confirm through ongoing monitoring that recovery efforts are progressing successfully across the affected services, with most impacted users no longer experiencing disruption. We’re remaining focused on identifying and resolving any remaining isolated scenarios while closely monitoring service health and implementing targeted mitigation measures to maintain stability and deliver a consistent, reliable user experience.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 18:00:45 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We continue to see sustained recovery across the affected services, with most users no longer experiencing impact. We’re continuing to focus on the remaining areas of impact and are progressing our mitigation efforts to address these residual scenarios. We’re closely monitoring service health throughout this work to maintain stability.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 16:03:04 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: The majority of services are restored for most users, and we continue to observe broad service recovery. We recognize that some users may still experience residual impact, and addressing these remaining scenarios continues to be our highest priority. We’re actively progressing our mitigation efforts and closely monitoring service health as we work to ensure full recovery for all users.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 14:30:14 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We've confirmed that impact related to OneDrive for Business, SharePoint Online, and Universal Print are now resolved. We recognize that while the majority of services are restored for most users, the remaining issues are disruptive for those still impacted. We're continuing to address residual impact with the highest priority so we can ensure resolution for all users.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 13:36:24 2026 |
|---|
| Description: | We’ve confirmed after a period of monitoring that impact related to OneDrive for Business and SharePoint Online is now resolved.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 13:23:29 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
Current status: We’re working on additional mitigation measures for the portion of infrastructure which have not yet returned to healthy service levels after deployment of our primary remediation. Service availability remains above 99 percent and our monitoring shows impact is resolved for the majority of users. We remain engaged and committed to fully resolving this issue for all users.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 12:21:00 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
Current status: Service availability remains stable above 99%, and telemetry indicates sustained recovery across the affected environments. The primary remediation has been deployed across the majority of impacted infrastructure, with remaining deployment and validation activities progressing as expected. Most previously affected users should no longer experience issues related to this event, though a small subset may continue to see intermittent impact while final recovery validation is completed. Our remaining efforts are focused on validating sustained recovery and identifying any remaining infrastructure requiring remediation. Enhanced monitoring remains in place as we continue recovery validation activities.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 09:37:26 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
*RECOVERED*
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
Current status: We're continuing to observe positive recovery trends across the affected environments, with service availability remaining stable above 99 percent. Based on our telemetry, we expect the vast majority of previously impacted users should no longer be experiencing issues related to this event. Our deployment activities are progressing as expected, and we're continuing to implement the remaining portions of our remediation across affected infrastructure to help ensure recovery is sustained over time. We remain focused on validating end-to-end service health, monitoring for any residual impact, and confirming that recovery is maintained for scenarios that rely on REST and Graph API connection methods. While a small subset of users may still encounter intermittent impact as the deployment continues to progress, current telemetry indicates continued improvement and no signs of broader service degradation. We're maintaining enhanced monitoring and will provide further updates as recovery work continues.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 02:44:32 2026 |
|---|
| Description: | Our telemetry indicates service availability remains stable above 99 percent, and we expect the majority of users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 00:39:19 2026 |
|---|
| Description: | We're observing service availability recovering to above 99 percent across the affected environments, and we expect the majority of previously affected users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 23:30:21 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may be unable to connect to Exchange Web Services (EWS)
- Users may be unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
Current status: Based on our telemetry, we expect a small subset of users may still see impact across the listed scenarios, though we're continuing our work to balance the implementation of our fixes across the infrastructure to achieve withstanding recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 21:31:44 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may be unable to connect to Exchange Web Services (EWS)
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
Current status: We're continuing to closely monitor service health as we carefully expand our reiterative corrective actions across additional regions. This work involves re-deploying our targeted fixes to the dependent authentication components to ensure service resilience, while balancing ongoing traffic patterns to avoid additional residual impact. Most users should see recovery across the majority of impacted scenarios, though some scenarios, including those reliant on Graph API and Representational State Transfer (REST) connection methods, will remain degraded until our mitigation efforts are complete.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 18:29:18 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may be unable to connect to Exchange Web Services (EWS)
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Current status: Most users should see recovery across the majority of impacted scenarios, though some scenarios will remain degraded until our mitigation efforts are complete. We're continuing to progress our mitigation efforts across multiple workstreams as we work to restore the service to healthy levels. We understand the challenges incidents such as these have on your organization and we’ll continue to closely monitor service health and prevent further impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 1:30 PM UTC An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 14:58:50 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Current status: We’re continuing to advance multiple workstreams to restore service and prevent additional impact. We’re prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, we’re investigating remaining reports of impact and evaluating additional actions to support full service recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 14:01:13 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Current status: We are carefully implementing corrective actions while maintaining enhanced monitoring to ensure services remain stable as recovery progresses.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
|
|---|
|
| Time: | Tue Sep 1 12:58:26 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Current status: We've observed continued recovery across previously impacted Exchange Online scenarios, with core mail flow functionality remaining healthy. Our focus remains on validating recovery across dependent Microsoft 365 experiences and confirming that remaining impact scenarios are fully addressed. We're maintaining enhanced monitoring while engineering teams complete end-to-end validation before determining whether any further corrective actions are required.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 11:57:30 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
- Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
- Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Current status: Service telemetry continues to indicate recovery across previously impacted scenarios as remediation progresses through the remaining affected infrastructure. Core Exchange Online experiences, including mail flow and search functionality, have recovered. Our focus has shifted toward validating recovery across remaining Microsoft 365 services. We're actively monitoring service health, assessing any residual pockets of impact, and confirming end-to-end functionality across affected workloads.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 10:18:21 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
- Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
- Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing to apply the targeted remediation across the remaining affected infrastructure where needed. Service telemetry continues to show positive recovery trends, with availability improving across previously impacted scenarios. We're actively validating that authentication, connectivity, and search experiences are returning to expected service levels, while maintaining enhanced monitoring to ensure improvements are sustained and any residual impact is addressed.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 06:58:15 2026 |
|---|
| Description: | A substantial portion of the remediation deployment has been completed, and organizations whose environments remain affected are expected to recover as the deployment reaches the relevant infrastructure. As remediation progresses, we're focused on validating sustained recovery and monitoring for any remaining pockets of impact before determining whether any additional corrective actions are required.
This quick update is designed to give the latest information on this issue.
We recognise the impact this issue may be causing for your organization and want to assure you that resolving it remains our highest priority. We appreciate your patience and understanding as we continue working toward mitigation.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 06:01:14 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
- Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
- Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing to apply the targeted authentication component fix across the remaining affected infrastructure where necessary. Service telemetry continues to indicate recovery, with availability increasing across previously impacted scenarios as remediation progresses. We're validating that authentication, connectivity and search operations are returning to expected service levels while monitoring for any residual impact and confirming that the remediation is delivering broad mitigation across affected Exchange Online scenarios. As recovery signals continue to trend positively, we're maintaining extended monitoring across affected service workflows to ensure improvements are sustained.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 04:56:42 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing to reapply the targeted authentication component fix to the remaining affected infrastructure where necessary. While our remediation effort is underway, indications from service telemetry remain positive. We're observing an overall increase in service availability, and we're monitoring this closely to ensure we're progressing towards a broad mitigation.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 04:02:06 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: Reapplying the targeted authentication component fix and restarting affected infrastructure segments has led to measurable progress. We're observing gradual improvements within telemetry data related to search functionality across the remaining affected infrastructure, and we're continuing this remediation effort across additional infrastructure segments while closely monitoring service health telemetry to ensure we're progressing towards a broader recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 02:39:32 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: Our efforts to restart affected sections infrastructure and re-apply the targeted authentication component fix has yielded progress, and we're observing incremental improvement reflected in the service health telemetry associated with search functionality across a sample of the affected environment. We're continuing this action for additional sections of infrastructure as we monitor closely to ensure widespread remediation.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:54:56 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing our work to restart affected infrastructure and re-apply the targeted authentication component fix to recover search functionality across the affected environments.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:00:45 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're persistently reviewing what additional actions may be required to re-apply our targeted authentication component fix and facilitate the recovery of remaining sections of infrastructure correlated with search functionality to ensure the full remediation. Meantime, we've validated persistent recovery for mail flow across the environment and are focusing our work on recovering search functionality.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 23:49:40 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're observing widespread recovery to Exchange Online mail connectivity, though the draining of backlogged mail queues may take longer for some organizations due to the volume of previously queued messages. Our recovery efforts are now focused on re-applying our targeted authentication component fix and restarting certain instances of infrastructure correlated with search functionality to ensure the full restoration of the associated scenarios.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 22:53:25 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're observing residual impact to some downstream scenarios, including search. We're incrementally restarting corresponding instances of infrastructure to ensure our previously applied authentication components are fully saturated, and we're working to identify whether any additional actions are required to achieve resolution.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 21:54:03 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're closely monitoring the health of the service environment amidst our ongoing recovery work, and we're observing some sections of affected infrastructure which aren't accepting the re-applied authentication components as readily as expected. Users can expect to see continued recovery to email delivery, while users may see residual impact to downstream and dependent scenarios, including search, across affected services. We're working to identify whether any additional actions are required to expedite full recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 20:57:23 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
-Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We’re seeing improvement across the affected environments as we observe the successful albeit gradual implementation of our mitigation actions. Users should expect to see varying degrees of recovery and residual delays until these actions have completed. We're closely monitoring the health of the service environment and will continue to aggressively pursue any available options to expedite our ongoing recovery work, and we'll provide an estimated recovery timeline as soon as one becomes available.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 19:58:05 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're progressively restarting targeted sections of affected infrastructure to ensure the re-applied authentication components are effectively implemented across affected services. We expect this will aid the recovery of affected scenarios. Users should expect delayed delivery of backlogged messages and residual impact across downstream scenarios as these actions are continuing. We'll provide an expected recovery time as soon as one becomes available to us.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 19:32:35 2026 |
|---|
| Description: | We're expanding the aforementioned mitigation action more widely across the affected environments as we closely track the recovery of affected scenarios. Users should primarily begin to see gradual recovery to mail flow. Secondarily, and in parallel to the primary mitigation action previously described, we're restarting targeted sections of affected infrastructure to ensure the acceptance of the re-applied authentication components across affected services and aid the recovery of the downstream scenarios.
This quick update is designed to give the latest information on this issue.
Next update by: Tuesday, September 1, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 18:53:24 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing to implement a targeted mitigation to re-apply core authentication components, and we're expanding this action more widely across the affected environments as we closely track the recovery of affected downstream scenarios. Users may notice gradual recovery to the scenarios identified in the "More info" section as our mitigation action takes effect in their corresponding sections of infrastructure, and we're continuing to review whether any additional actions may be required to achieve withstanding recovery across all affected scenarios. We'll provide an estimated time to resolution as soon as one is available.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 18:40:12 2026 |
|---|
| Description: | We're implementing a targeted mitigation to re-apply core authentication components across a sample of affected infrastructure and are closely monitoring corresponding service telemetry to validate the efficacy of this action. As a result of this work, some users are beginning to see recovery to some impacted scenarios. We'll continue to incrementally expand this mitigation action more widely across the affected environments as quickly as possible.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, August 31, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 17:53:52 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing our targeted review of affected infrastructure and recent changes made to the service to definitively confirm the cause of impact. We're additionally continuing to test and implement various mitigation strategies to apply the necessary authentication component, which have so far yielded positive results. We're monitoring these tests and mitigative actions closely and will provide an estimated time to resolution as soon as one is available.
We understand the impact that events like these can have for your organization and we appreciate your patience as we work to mitigate this issue with the highest priority.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 16:36:45 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're reexamining recent changes made to the service to determine why the authentication components aren't being deployed as expected. Additionally, we are exploring every avenue to safely restore the components, including reverting an update the affected infrastructure recently received. We're performing additional tests to determine whether this will provide relief.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 15:32:27 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Current status: We're continuing to perform comprehensive tests to ensure our mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, we're exploring alternative remediation avenues to minimize impact in the interim.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 15:00:11 2026 |
|---|
| Description: | We're continuing to fine-tune our remediation strategy as our internal tests progress. We'll aim to provide an estimated time for remediation as soon as it's available.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, August 31, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 14:25:35 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Current status: We've identified issues related to a core authentication configuration used by multiple Microsoft 365 services which is resulting in the impact outlined above. We've identified a potential remediation and we're performing tests to ensure its efficacy before applying it more broadly.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Next update by: Monday, August 31, 2026, at 6:30 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 7:30 PM UTC
|
|---|
|
EX1464935 - Users may be unable to connect to, or experience degraded functionality with Exchange Online
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Aug 31 10:56:00 2026 |
|---|
| End Time: | Thu Sep 3 06:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 10 20:46:30 2026 |
|---|
| Root Cause: | An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 20:46:30 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 13:28:26 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 13:11:34 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Sep 8 05:34:59 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sat Sep 5 15:48:40 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 3 16:05:37 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may have been unable to connect to, or experienced degraded functionality with Exchange Online.
More info: We've confirmed that the component issue impacted other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
Users may have experienced a variety of symptoms related to this event, including but not limited to:
- Users couldn't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Access-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work.
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may have been unable to use room finder in Outlook calendars.
- Users may have been unable to sign in to Outlook on the web.
Final status: Based on our telemetry all previously impacted services have remained healthy since impact was remediated on Thursday, September 3, 2026, at 10:00 AM UTC, and this issue is resolved.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may have been affected by this event.
Start time: Monday, August 31, 2026, at 2:56 PM UTC
End time: Thursday, September 3, 2026, at 10:00 AM UTC
Preliminary root cause: An issue within a core access configuration used by multiple Microsoft 365 services was resulting in impact.
Next steps:
- We’re evaluating our core service configurations to prevent the recurrence of similar impact in the future. In addition, we're further reviewing our monitoring systems to ensure we identify and are expediently alerted to these types of scenarios.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Sep 3 14:23:20 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacted other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online was the most predominantly impacted service.
Users may have experienced a variety of symptoms related to this event, including but not limited to:
- Users couldn't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work.
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may have been unable to use room finder in Outlook calendars.
- Users may have been unable to sign in to Outlook on the web.
Current status: All user impact scenarios are now resolved as we rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of our infrastructure. We will continue to monitor our telemetry to ensure all services remain healthy and plan to close this communication by our next scheduled update.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Friday, September 4, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 12:23:14 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We discovered an issue in less than one percent of our infrastructure, where our additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. We remain committed to restoring all services to all users and will continue to carefully monitor our telemetry to ensure recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 6:30 PM UT
|
|---|
|
| Time: | Thu Sep 3 10:26:54 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: While monitoring service telemetry closely, we identified a small volume of errors affecting mail flow functionality. We're conducting targeted restarts to reduce the number of errors and alleviate impact. In parallel, we're continuing to analyze service health telemetry to determine if any additional mitigation actions are required to restore normal functionality.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 08:27:28 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We're continuing to implement further mitigation actions where required to resolve any outstanding impact associated with this incident. Customer feedback and reports from our telemetry remain positive, and service health is stable. While this work is underway, we're actively monitoring the service closely to ensure stability is consistent.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 06:23:13 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We're performing additional remediation efforts where necessary to address any remaining impact from this incident. Reports from telemetry data and customer feedback are aligned, indicating a sustained recovery. We're actively monitoring the situation closely to ensure impact is completely mitigated.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 04:14:51 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We're continuing to closely monitor the service to ensure sustained stability, and signals from telemetry and customer feedback remain positive. In parallel, we're conducting additional remediation actions where required to resolve any lingering residual impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Sep 3 02:21:37 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We've confirmed that our services remain stable, and both telemetry and customer reports indicate that the issue has been largely mitigated. We're continuing to address any lingering issues while we remain engaged in an extended monitoring period to validate sustained recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Sep 3 00:23:02 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: Our recovery metrics remain positive, with monitoring continuing to indicate that the service is stable and there is a constant reduction in the number of affected users. We’re continuing to validate recovery through targeted remediation actions and service health checks. We’ll maintain targeted monitoring and validation actions to confirm recovery outcomes and identify any remaining impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 22:16:05 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: Ongoing monitoring continues to show positive recovery progress, with impact no longer observed for most previously affected users. We’re continuing to monitor service health and implement targeted remediation efforts to validate recovery progress and help ensure ongoing service stability.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 20:21:16 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We continue to observe positive recovery trends through ongoing monitoring, with most affected users no longer experiencing disruption. We remain focused on identifying and resolving any remaining issues while implementing targeted mitigations to support a stable and consistent user experience.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 18:00:23 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We've confirmed that the majority of users remain mitigated. We're continuing to advance several workstreams as we work toward full resolution for all users and in parallel, we're maintaining enhanced monitoring throughout this work to ensure service stability.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 16:31:15 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We’ve completed a restart of affected Outlook on the web infrastructure, and service telemetry indicates that the majority of users have recovered. We’re continuing to closely monitor service health as we roll out more durable fixes designed to address the underlying conditions contributing to the impact.
In parallel, we’re working directly with affected users and examining reports of continued impact to gather additional diagnostic information and identify any remaining issues.
We remain focused on fully restoring service for all affected users and will continue deploying our fixes, investigating reports of impact, and monitoring service health until we’re confident the issue is fully resolved.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 14:29:53 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We recognize that while service is restored for most customers, the remaining issues are disruptive for those still impacted. We are prioritizing fully resolving the issue for all customers.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 13:23:19 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We’re working on additional mitigation measures for the portion of infrastructure which have not yet returned to healthy service levels after deployment of our primary remediation. Service availability remains above 99 percent and our monitoring shows impact is resolved for the majority of users. We remain engaged and committed to fully resolving this issue for all users.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 12:22:25 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
Current status: Service availability remains stable above 99%, and telemetry indicates sustained recovery across the affected environments. The primary remediation has been deployed across the majority of impacted infrastructure, with remaining deployment and validation activities progressing as expected. Most previously affected users should no longer experience issues related to this event, though a small subset may continue to see intermittent impact while final recovery validation is completed. Our remaining efforts are focused on validating sustained recovery and identifying any remaining infrastructure requiring remediation. Enhanced monitoring remains in place as we continue recovery validation activities.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 02:44:50 2026 |
|---|
| Description: | Our telemetry indicates service availability remains stable above 99 percent, and we expect the majority of users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 00:39:37 2026 |
|---|
| Description: | We're observing service availability recovering to above 99 percent across the affected environments, and we expect the majority of previously affected users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 23:31:34 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
Current status: Based on our telemetry, we expect a small subset of users may still see impact across the listed scenarios, though we're continuing our work to balance the implementation of our fixes across the infrastructure to achieve withstanding recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 21:30:32 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We're continuing to closely monitor service health as we carefully expand our reiterative corrective actions across additional regions. This work involves re-deploying our targeted fixes to the dependent authentication components to ensure service resilience, while balancing ongoing traffic patterns to avoid additional residual impact. Most users should see recovery across the majority of impacted scenarios, though some scenarios, including those reliant on Graph API and Representational State Transfer (REST) connection methods, will remain degraded until our mitigation efforts are complete.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 18:30:08 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: Most users should see recovery across the majority of impacted scenarios, though some scenarios will remain degraded until our mitigation efforts are complete. We're continuing to progress our mitigation efforts across multiple workstreams as we work to restore the service to healthy levels. We understand the challenges incidents such as these have on your organization and we’ll continue to closely monitor service health and prevent further impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 18:30:02 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: Most users should see recovery across the majority of impacted scenarios, though some scenarios will remain degraded until our mitigation efforts are complete. We're continuing to progress our mitigation efforts across multiple workstreams as we work to restore the service to healthy levels. We understand the challenges incidents such as these have on your organization and we’ll continue to closely monitor service health and prevent further impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 14:59:44 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We’re continuing to advance multiple workstreams to restore service and prevent additional impact. We’re prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, we’re investigating remaining reports of impact and evaluating additional actions to support full service recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 14:00:57 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We are carefully implementing corrective actions while maintaining enhanced monitoring to ensure services remain stable as recovery progresses.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 12:59:48 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We've observed continued recovery across previously impacted Exchange Online scenarios, with core mail flow functionality remaining healthy. Our focus remains on validating recovery across dependent Microsoft 365 experiences and confirming that remaining impact scenarios are fully addressed. We're maintaining enhanced monitoring while engineering teams complete end-to-end validation before determining whether any further corrective actions are required.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 12:00:28 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: Service telemetry continues to indicate recovery across previously impacted scenarios as remediation progresses through the remaining affected infrastructure. Core Exchange Online experiences, including mail flow and search functionality, have recovered. Our focus has shifted toward validating recovery across remaining Microsoft 365 services. We're actively monitoring service health, assessing any residual pockets of impact, and confirming end-to-end functionality across affected workloads.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 10:18:31 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We're continuing to apply the targeted remediation across the remaining affected infrastructure where needed. Service telemetry continues to show positive recovery trends, with availability improving across previously impacted scenarios. We're actively validating that authentication, connectivity, and search experiences are returning to expected service levels, while maintaining enhanced monitoring to ensure improvements are sustained and any residual impact is addressed.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 06:58:06 2026 |
|---|
| Description: | A substantial portion of the remediation deployment has been completed, and organizations whose environments remain affected are expected to recover as the deployment reaches the relevant infrastructure. As remediation progresses, we're focused on validating sustained recovery and monitoring for any remaining pockets of impact before determining whether any additional corrective actions are required.
This quick update is designed to give the latest information on this issue.
We recognise the impact this issue may be causing for your organization and want to assure you that resolving it remains our highest priority. We appreciate your patience and understanding as we continue working toward mitigation.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 06:00:33 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We're continuing to apply the targeted authentication component fix across the remaining affected infrastructure where necessary. Service telemetry continues to indicate recovery, with availability increasing across previously impacted scenarios as remediation progresses. We're validating that authentication, connectivity and search operations are returning to expected service levels while monitoring for any residual impact and confirming that the remediation is delivering broad mitigation across affected Exchange Online scenarios. As recovery signals continue to trend positively, we're maintaining extended monitoring across affected service workflows to ensure improvements are sustained.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 04:54:53 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're continuing to reapply the targeted authentication component fix to the remaining affected infrastructure where necessary. While our remediation effort is underway, indications from service telemetry remain positive. We're observing an overall increase in service availability, and we're monitoring this closely to ensure we're progressing towards a broad mitigation.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 04:00:26 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: Reapplying the targeted authentication component fix and restarting affected infrastructure segments has led to measurable progress. We're observing gradual improvements within telemetry data related to search functionality across the remaining affected infrastructure, and we're continuing this remediation effort across additional infrastructure segments while closely monitoring service health telemetry to ensure we're progressing towards a broader recovery.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 02:39:47 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: Our efforts to restart affected sections infrastructure and re-apply the targeted authentication component fix has yielded progress, and we're observing incremental improvement reflected in the service health telemetry associated with search functionality across a sample of the affected environment. We're continuing this action for additional sections of infrastructure as we monitor closely to ensure widespread remediation.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:55:10 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're continuing our work to restart affected infrastructure and re-apply the targeted authentication component fix to recover search functionality across the affected environments.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:01:23 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're persistently reviewing what additional actions may be required to re-apply our targeted authentication component fix and facilitate the recovery of remaining sections of infrastructure correlated with search functionality to ensure the full remediation. Meantime, we've validated persistent recovery for mail flow across the environment and are focusing our work on recovering search functionality.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 23:52:06 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're observing widespread recovery to Exchange Online mail connectivity, though the draining of backlogged mail queues may take longer for some organizations due to the volume of previously queued messages. Our recovery efforts are now focused on re-applying our targeted authentication component fix and restarting certain instances of infrastructure correlated with search functionality to ensure the full restoration of the associated scenarios.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 22:55:12 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're observing residual impact to some downstream scenarios, including search. We're incrementally restarting corresponding instances of infrastructure to ensure our previously applied authentication components are fully saturated, and we're working to identify whether any additional actions are required to achieve resolution.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 21:54:43 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're closely monitoring the health of the service environment amidst our ongoing recovery work, and we're observing some sections of affected infrastructure which aren't accepting the re-applied authentication components as readily as expected. Users can expect to see continued recovery to email delivery, while users may see residual impact to downstream and dependent scenarios, including search, across affected services. We're working to identify whether any additional actions are required to expedite full recovery.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 20:59:44 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We’re seeing improvement across the affected environments as we observe the successful albeit gradual implementation of our mitigation actions. Users should expect to see varying degrees of recovery and residual delays until these actions have completed. We're closely monitoring the health of the service environment and will continue to aggressively pursue any available options to expedite our ongoing recovery work, and we'll provide an estimated recovery timeline as soon as one becomes available.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 20:01:08 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're progressively restarting targeted sections of affected infrastructure to ensure the re-applied authentication components are effectively implemented across affected services. We expect this will aid the recovery of affected scenarios. Users should expect delayed delivery of backlogged messages and residual impact across downstream scenarios as these actions are continuing. We'll provide an expected recovery time as soon as one becomes available to us.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 19:33:55 2026 |
|---|
| Description: | We're expanding the aforementioned mitigation action more widely across the affected environments as we closely track the recovery of affected scenarios. Users should primarily begin to see gradual recovery to mail flow. Secondarily, and in parallel to the primary mitigation action previously described, we're restarting targeted sections of affected infrastructure to ensure the acceptance of the re-applied authentication components across affected services and aid the recovery of the downstream scenarios.
This quick update is designed to give the latest information on this issue.
Next update by: Tuesday, September 1, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 18:57:55 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're continuing to implement a targeted mitigation to re-apply core authentication components, and we're expanding this action more widely across the affected environments as we closely track the recovery of affected downstream scenarios. Users may notice gradual recovery to the scenarios identified in the "More info" section as our mitigation action takes effect in their corresponding sections of infrastructure, and we're continuing to review whether any additional actions may be required to achieve withstanding recovery across all affected scenarios. We'll provide an estimated time to resolution as soon as one is available.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 18:40:38 2026 |
|---|
| Description: | We're implementing a targeted mitigation to re-apply core authentication components across a sample of affected infrastructure and are closely monitoring corresponding service telemetry to validate the efficacy of this action. As a result of this work, some users are beginning to see recovery to some impacted scenarios. We'll continue to incrementally expand this mitigation action more widely across the affected environments as quickly as possible.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, August 31, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 17:55:39 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're continuing our targeted review of affected infrastructure and recent changes made to the service to definitively confirm the cause of impact. We're additionally continuing to test and implement various mitigation strategies to apply the necessary authentication component, which have so far yielded positive results. We're monitoring these tests and mitigative actions closely and will provide an estimated time to resolution as soon as one is available.
We understand the impact that events like these can have for your organization and we appreciate your patience as we work to mitigate this issue with the highest priority.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 16:36:03 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're reexamining recent changes made to the service to determine why the authentication components aren't being deployed as expected. Additionally, we are exploring every avenue to safely restore the components, including potentially reverting an update the affected infrastructure recently received. We're performing additional tests to evaluate the best course of action moving forward.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 15:43:43 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're continuing to perform comprehensive tests to ensure our mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, we're exploring alternative remediation avenues to minimize impact in the interim.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 14:41:23 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're continuing to fine-tune our remediation strategy as our internal tests progress. We'll aim to provide an estimated time for remediation as soon as it's available.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 14:18:57 2026 |
|---|
| Description: | We're continuing to test our remediation strategy and in parallel we're working to confirm whether other services are impacted so we can expand our communications accordingly.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Aug 31 13:23:38 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We've identified a potential corrective action for the affected infrastructure and are evaluating deployment options. We're monitoring service telemetry and affected Exchange Online transactions to determine whether the action is reducing impact and to better understand the scope of affected scenarios.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Next update by: Monday, August 31, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 12:33:59 2026 |
|---|
| Description: | We’ve isolated a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity. We're analyzing service telemetry to identify the underlying source of impact and validate potential remediation options. Additionally, we’re continuing to assess the scope of impact and monitor for additional affected scenarios.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, August 31, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 12:16:11 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: Users may experience a variety of symptoms related to this event, including but not limited to:
Delays or failures when sending or receiving email messages.
Authentication-related errors when accessing Exchange Online services.
Difficulties accessing or performing actions within Exchange administration experiences.
Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're reviewing service telemetry and diagnostic data to isolate the source of the issue after receiving an increase in user-reported issues affecting Exchange Online. We'll keep refining the 'more info' section as additional impacts are identified.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Next update by: Monday, August 31, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 11:55:01 2026 |
|---|
| Description: | Title: Investigating user reports of Exchange Online issues
User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.
|
|---|
|
EX1467029 - Users may experience delays sending and receiving email messages from external domains in Exchange Online
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Sep 4 05:00:00 2026 |
|---|
| End Time: | Fri Sep 4 11:15:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 10 11:39:09 2026 |
|---|
| Root Cause: | Exchange Online leverages some Microsoft Defender for Office 365 data, along with a multitude of other data sources, for some of its anti-spam features. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 11:37:09 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 11:33:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Sep 4 12:05:15 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may have experienced a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may have experienced intermittent “Server busy” errors, affecting multiple mailboxes.
Depending on the client, the service should attempt to periodically retry sending the email previously impacted by the issue. If the initial sender received an NDR after 24-72 hours (different clients or email providers can vary), they will need to send a new email.
Final status: We've confirmed that the issue is resolved after an extended period of monitoring, and receiving additional confirmations from previously impacted organizations.
Scope of impact: This issue impacted users who may have been attempting to send and receive email messages from external domains in Exchange Online.
Start time: Friday, September 4, 2026, at 9:00 AM UTC
End time: Friday, September 4, 2026, at 3:15 PM UTC
Root cause: Exchange Online leverages some Microsoft Defender for Office 365 data, along with a multitude of other data sources, for some of its anti-spam features.
An upstream distributed data platform experienced elevated service load after a recent change increased the size of read requests beyond the intended physical thresholds. This caused high latency and instability within the platform, which resulted in time windows where portions of the source data were unavailable to dependent processing jobs.
One of the sender-based reputation processing jobs continued to run with substantially less input data than expected and still reported successful completions. Because the pipeline did not have a sufficiently strong completeness check before publishing its output, the reduced data set was incorporated into the reputation information used by the mail-protection service.
This resulted in incomplete reputation-based data and caused legitimate sending IP addressed to be assigned overly restrictive limits by a volume-based reputation control. When the limits were reached, affected emails were throttled and temporarily deferred with ‘451 4.7.500 Server Busy’ responses.
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 Sep 4 11:08:34 2026 |
|---|
| Description: | Telemetry is trending in a positive direction and shows a reduction in the number of new emails getting impacted as the rule disablement progresses across the service.
Next update by: Friday, September 4, 2026, at 4:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Sep 4 10:33:11 2026 |
|---|
| Description: | We've determined that a different machine level throttling rule within the anti-spam features is being incorrectly triggered for a small number of emails, resulting in the remaining impact. We're disabling this specific rule to provide relief and fully mitigate the issue. We expect this to complete within the next hour.
Next update by: Friday, September 4, 2026, at 4:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Sep 4 10:24:49 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Depending on the client, the service should attempt to periodically retry sending the email previously impacted by the issue. If the initial sender received an NDR after 24-72 hours (different clients or email providers can vary), they will need to send a new email.
Current status: We've received a large number of confirmations that the issue is resolved, however, we're reviewing some isolated reports that some organizations are still experiencing delays in email delivery. We're reviewing example SMTP traces from those impacted users to isolate the source of the issue.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Start time: Friday, September 4, 2026, at 9:00 AM UTC
Preliminary root cause: The enforcement of a specific anti-spam model is contributing to impact for a subset of email traffic.
Next update by: Friday, September 4, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 09:28:48 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Depending on the client, the service should attempt to periodically retry sending the email previously impacted by the issue. If the initial sender received an NDR after 24-72 hours (different clients or email providers can vary), they will need to send a new email.
Current status: Telemetry shows that the service is performing as expected for new emails and this is in line with organizations confirming that the issue no longer occurring. We're monitoring email queues and performing final validations to confirm the issue is fully resolved.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Start time: Friday, September 4, 2026, at 9:00 AM UTC
Preliminary root cause: The enforcement of a specific anti-spam model is contributing to impact for a subset of email traffic.
Next update by: Friday, September 4, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Sep 4 09:02:32 2026 |
|---|
| Description: | Some organizations are reporting that they are experiencing relief and that their queued messages are now processing. We continue to monitor the service to confirm full resolution.
Next update by: Friday, September 4, 2026, at 1:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Sep 4 08:26:10 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: We're progressing with the disablement of the specific model, and telemetry is showing a decrease in matching and throttling actions as the rule changes propagate throughout the service. We estimate this rollout will complete within the next 30 minutes.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 07:59:23 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: We've identified that the enforcement of a specific anti-spam model is contributing to impact for a subset of email traffic. We're adding affected IPs from the throttling enforcement to an allow list as an initial mitigation measure. In parallel, we're working to disable the specific model that caused impact.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 07:03:51 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: Our initial investigation has identified instances where anti-spam protections may be contributing to impact for a subset of users. We are continuing to analyse the behaviour and review service telemetry to better understand the underlying cause and determine the most effective mitigation path.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 06:36:10 2026 |
|---|
| Description: | Title: Users may experience delays receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: This issue impacts users who may be attempting to receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 06:21:23 2026 |
|---|
| Description: | Title: Users may experience delays receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
MO1470143 - Some users in the United Kingdom may have been unable to access multiple Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 10 03:13:00 2026 |
|---|
| End Time: | Thu Sep 10 09:39:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 10 11:02:57 2026 |
|---|
| Root Cause: | Some users may have been unable to access Microsoft 365 services due to facing authentication errors.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 10:22:56 2026 |
|---|
| Description: | Title: Some users in the United Kingdom may have been unable to access multiple Microsoft 365 services
User impact: Users in the United Kingdom may have been unable to access multiple Microsoft 365 services.
More info: Impacted services may have included, but weren't limited to:
- Microsoft Teams
- Outlook
Final status: While implementing traffic optimization actions within the affected environment, we observed service recovery and subsequently confirmed that users could successfully access impacted services. We're continuing to analyze service telemetry, authentication logs, and recent service changes to isolate the underlying cause and help prevent similar impact in the future.
Scope of impact: Impact was specific to some users in the United Kingdom attempting to access multiple Microsoft 365 services.
Start time: Thursday, September 10, 2026, at 8:10 AM UTC
End time: Thursday, September 10, 2026, at 1:39 PM UTC
Root cause: Some users may have been unable to access Microsoft 365 services due to facing authentication errors.
Next steps:
- We're reviewing service telemetry, authentication logs and recent service changes to isolate the root cause and prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 10 09:07:01 2026 |
|---|
| Description: | Title: Some users in the United Kingdom may be unable to access multiple Microsoft 365 services
User impact: Users in the United Kingdom may be unable to access multiple Microsoft 365 services.
More info: Impacted services may include, but aren't limited to:
- Microsoft Teams
- Outlook
Current status: We've identified that a recent authentication component change may be causing users to be unable to access Microsoft 365 services. We're redirecting affected traffic to alternate infrastructure to validate the root cause and provide mitigation.
Scope of impact: Impact is specific to some users in the United Kingdom attempting to access multiple Microsoft 365 services.
Next update by: Thursday, September 10, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Thu Sep 10 07:42:20 2026 |
|---|
| Description: | Title: Some users in the United Kingdom may be unable to access multiple Microsoft 365 services
User impact: Users in the United Kingdom may be unable to access multiple Microsoft 365 services.
More info: Impacted services may include, but aren't limited to:
- Microsoft Teams
- Outlook
Current status: We're proceeding with reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users in the United Kingdom attempting to access multiple Microsoft 365 services.
Next update by: Thursday, September 10, 2026, at 1:30 PM UTC
|
|---|
|
CP1465967 - Admins were unable to view additional sync statistics for some Microsoft Graph Connectors
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 11:47:00 2026 |
|---|
| End Time: | Wed Sep 9 19:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 10 07:51:09 2026 |
|---|
| Root Cause: | A recent service update introduced an incompatibility that prevented the Crawl Statistics service from successfully processing certain requests, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 07:42:44 2026 |
|---|
| Description: | Title: Admins were unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins were unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins were able to view recent crawl details but were unable to view sync statistics in the Microsoft 365 admin experience. The issue affected multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Final status: We've confirmed that deployment of our fix has completed across the affected environments and have validated recovery through service telemetry. Monitoring indicates that requests to the Crawl Statistics service are now being processed successfully, and impacted functionality has been restored.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section of this communication may have been impacted.
Start time: Thursday, August 13, 2026, at 3:47 PM UTC
End time: Wednesday, September 9, 2026, at 11:00 PM UTC
Root cause: A recent service update introduced an incompatibility that prevented the Crawl Statistics service from successfully processing certain requests, resulting in 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: | Thu Sep 10 05:45:07 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins can view recent crawl details but may be unable to view sync statistics in the Microsoft 365 admin experience. The issue affects multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Current status: We've confirmed that deployment of our fix has completed and we've observed recovery in service telemetry, and are continuing to monitor the environment while we work to complete final validation of the remediation.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section may be impacted.
Root cause: A recent service update introduced an incompatibility that is preventing the Crawl Statistics service from successfully processing certain requests, resulting in impact.
Next update by: Thursday, September 10, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Sep 8 08:00:34 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins can view recent crawl details but may be unable to view sync statistics in the Microsoft 365 admin experience. The issue affects multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Current status: We're continuing the fix deployment across the affected environments; however, the deployment is taking longer than initially anticipated to complete due to unforeseen delays within the rollout process. We're monitoring as the deployment continues to saturate across the environments and expect it to complete by Thursday, September 10, 2026.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section may be impacted.
Root cause: A recent service update introduced an incompatibility that is preventing the Crawl Statistics service from successfully processing certain requests, resulting in impact.
Next update by: Thursday, September 10, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Sep 3 08:15:22 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins can view recent crawl details but may be unable to view sync statistics in the Microsoft 365 admin experience. The issue affects multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Current status: We’ve determined that a recent service update introduced an incompatibility that is preventing the Crawl Statistics service from successfully processing certain requests, resulting in impact. We’ve deployed a fix to address the issue and are monitoring the rollout across impacted environments. We expect deployment to complete and the issue to be resolved by our next scheduled update.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section may be impacted.
Estimated time to resolve: Tuesday, September 8, 2026
Root cause: A recent service update introduced an incompatibility that is preventing the Crawl Statistics service from successfully processing certain requests, resulting in impact.
Next update by: Tuesday, September 8, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 09:16:43 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins can view recent crawl details but may be unable to view sync statistics in the Microsoft 365 admin experience. The issue affects multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Current status: We've enabled enhanced diagnostic logging and are analyzing affected requests to determine the root cause of the HTTP 500 errors affecting the retrieval of certain crawl statistics data. In parallel, we're reviewing recent code changes and related service behavior to assess whether they're contributing to the impact.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section may be impacted.
Next update by: Thursday, September 3, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 04:44:52 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins are able to view crawl details but are unable to view sync statistics in the Microsoft 365 admin experience because a specific API is returning HTTP 500 errors. This affects multiple connector types including Confluence, Jira, ServiceNow, Monday.com and others.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: This issue impacts admins attempting to view additional sync statistics for some Microsoft Graph Connectors.
Next update by: Wednesday, September 2, 2026, at 1:30 PM UTC
|
|---|
|
CW1469885 - Users may be unable to see the suggestions pills after receiving a bot response in Microsoft 365 Copilot Chat
| Status: | serviceRestored |
|---|
| Start Time: | Wed Sep 9 16:49:34 2026 |
|---|
| End Time: | Wed Sep 9 16:53:20 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 9 16:54:35 2026 |
|---|
| Root Cause: | An internal drill that tests the resiliency of our service caused this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 9 16:53:20 2026 |
|---|
| Description: | Title: Users may be unable to see the suggestions pills after receiving a bot response in Microsoft 365 Copilot Chat
User impact: Users may have been unable to see the suggestion pills after receiving a bot response in Copilot Chat.
Final status: Our service telemetry has alerted us to an issue in which users may have been unable to see the suggestion pills after receiving a bot response in Copilot Chat. We've determined that an internal drill that tests the resiliency of our service caused this impact. We've halted this impacting drill and confirmed with our service telemetry that impact is remediated.
Scope of impact: Users who attempted to see the suggestions pills after receiving a bot response in Copilot Chat may have been impacted by this event.
Start time: Wednesday, September 9, 2026, at 6:20 PM UTC
End time: Wednesday, September 9, 2026, at 7:30 PM UTC
Root cause: An internal drill that tests the resiliency of our service caused this impact.
Next steps: - We're reviewing our internal drill procedures to better identify the potential for impact to suggestion pills in Copilot Chat prior to beginning the drill, so that we can prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
DZ1189321 - Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 6 20:00:00 2025 |
|---|
| End Time: | Wed Sep 9 12:04:28 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 9 12:14:05 2026 |
|---|
| Root Cause: | A Windows update was producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who upgraded to Windows 11 in or after June of 2025.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 9 12:14:01 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may have seen incorrect names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue only impacted users who have upgraded to Windows 11 during or after June of 2025.
Final status: We've confirmed our solution to address the incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer has fully saturated and the impact has been fully remediated by our actions.
Scope of impact: This issue impacted a subset of users who upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
End time: Wednesday, September 9, 2026, at 4:00 PM UTC
Root cause: A Windows update was producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who upgraded to Windows 11 in or after June of 2025.
Next steps:
- We're evaluating the localization issues introduced by the impacting Windows update so we can more effectively identify and correct similar regressions in future update testing prior to deployments to prevent this issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 31 13:09:50 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We're continuing to deploy our solution to address the incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer. We anticipate this deployment to be completed by our next scheduled update.
Scope of impact: This issue impacts a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Wednesday, September 9, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Aug 26 13:41:39 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We’re continuing to deploy our solution to address the incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer. We’ll provide a resolution timeline once available.
Scope of impact: This issue impacts a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, August 31, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 3 13:05:07 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: After completing our internal validations, we've determined that our solution will address the incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer to remediate the impact. We're deploying our solution, and our fix deployment timeline expects that it will be available by our next scheduled communication update.
Scope of impact: This issue impacts a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Wednesday, August 26, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 16 12:43:42 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: Our final validation process is ongoing and is expected to take several weeks to complete. Based on our current estimates, we expect the fix to be deployed and the issue to be resolved by Tuesday, August 25, 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, August 3, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jun 30 12:51:20 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: Our validation process is ongoing, and we're continuing to verify the fix before determining a release timeline. We'll provide one once it's available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Thursday, July 16, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jun 23 13:10:34 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: The fix validation is ongoing and we expect to have a release timeline by the next scheduled update.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, June 30, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu May 21 13:12:30 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We’re continuing final testing and validation efforts for the fix before deployment. The fix remains scheduled to begin optional rollout around August 25, 2026, through an upcoming Windows cumulative update, before becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, June 23, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Apr 24 15:20:17 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We're continuing our final validation efforts for the fix. The fix is planned for release as part of an upcoming Windows cumulative update, with an optional rollout beginning around August 25, 2026, and becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Thursday, May 21, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Apr 3 13:02:30 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're in the final stages of validation for the fix. The fix is planned to be released as part of an upcoming Windows cumulative update, with optional rollout expected to begin approximately August 25, 2026, and becoming mandatory on September 8, 2026. We'll continue to provide updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 24, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Mar 20 13:24:46 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're preparing the localization fix for additional validations before we initiate the deployment of the fix. We anticipate being able to provide an updated timeline for when we expect the deployment to be released by our next scheduled update.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 3, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Feb 20 12:58:51 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're continuing to work toward delivering the additional localization fix, and we expect this process to take additional time due to the complexity involved in implementing the solution. Based on our current estimates, remediation is targeted for a release window of May 2026. We'll provide further updates as this process progresses.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, March 20, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 14:58:23 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: While we’ve developed an additional fix for the localization issues, the complexity of delivering this solution is preventing an expedited resolution. We expect this process to take several weeks as we validate the subtasks involved in instituting the fix. We’ll provide updates on this process and a timeline for deployment once the subtask orchestration is complete.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, February 20, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jan 9 13:12:08 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’re continuing to assess and validate alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 12:35:31 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve identified that the previously developed code fix isn’t an effective solution for addressing the incorrect service names and descriptions. We’re assessing and validating alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 9, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Dec 9 12:44:40 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: Validation of the code fix is continuing to progress, and due to the complex nature of the code developed to address the incorrect service names and descriptions, we're still expecting the deployment to complete by March 2026. We'll provide a more accurate timeline as one becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, January 6, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Dec 8 03:18:26 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We are continuing to validate the fix’s effectiveness and anticipate full deployment by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, December 9, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 05:20:30 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve developed a code fix to address the issue. It’s currently undergoing validation to ensure effectiveness, and we expect the fix to be fully implemented and remediate impact by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, 8 December 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Nov 23 16:12:56 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We've identified a recent Windows update that is producing incorrect service names and descriptions in Services and the Event Viewer for some users who have upgraded to Windows 11 in or after June of 2025. As we work to confirm an accurate window of impact, we're developing a code fix to address the offending change and to remediate the impact. We'll provide an updated timeline for the deployment of our fix and the remediation of impact once our internal validations have completed.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, November 24, 2025, at 10:30 AM UTC
|
|---|
|
MO1469271 - Some users may be unable to access https://m365.cloud.microsoft and receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 8 11:23:28 2026 |
|---|
| End Time: | Tue Sep 8 13:22:34 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 8 13:28:08 2026 |
|---|
| Root Cause: | A recent service update, intended to improve how chats are loaded when accessing m365.cloud.microsoft, rejected requests which resulted in https://m365.cloud.microsoft failing to load.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 8 13:28:04 2026 |
|---|
| Description: | Title: Some users may be unable to access https://m365.cloud.microsoft and receive an error
User impact: Users may be unable to access https://m365.cloud.microsoft and receive an error message.
More info: Users received a "GetSections returned no conversation history" error message.
Final status: Further analysis indicated that the previously referenced 400 and 503 error messages were unrelated to the issue described in this communication, and we've updated the communication accordingly. We reverted a recent service update that was intended to improve chat-loading functionality when accessing m365.cloud.microsoft and confirmed through service telemetry that the error rates have subsided and service is restored.
Scope of impact: This issue may have affected some users attempting to access https://m365.cloud.microsoft.
Start time: Tuesday, September 8, 2026, at 4:30 AM UTC
End time: Tuesday, September 8, 2026, at 5:15 PM UTC
Root cause: A recent service update, intended to improve how chats are loaded when accessing m365.cloud.microsoft, rejected requests which resulted in https://m365.cloud.microsoft failing to load.
Next steps:
- We're reviewing our testing processes to determine how we can identify similar issues prior to deployment so we can resolve these issues beforehand.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 8 12:06:42 2026 |
|---|
| Description: | Title: Some users may be unable to access https://m365.cloud.microsoft and receive an error
User impact: Users may be unable to access https://m365.cloud.microsoft and receive an error message.
More info: Users receive either a 400 or 503 error code, or a "GetSections returned no conversation history" error message.
Current status: We've received reports of an issue where users receive either a 400 or 503 error code, or a "GetSections returned no conversation history" error message when attempting to access https://m365.cloud.microsoft. We're reviewing a HTTP Archive (HAR) file from both working and non-working scenarios to assess where the issue lies.
Scope of impact: This issue may affect some users attempting to access https://m365.cloud.microsoft.
Next update by: Tuesday, September 8, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 8 11:32:08 2026 |
|---|
| Description: | Title: Some users can't access https://m365.cloud.microsoft and receive an error
User impact: Users can't access https://m365.cloud.microsoft and receive a 400, 503 error code, or a specific error message.
More info: Users receive either a 400 or 503 error code, or a "GetSections returned no conversation history" error message.
Current status: We're investigating a potential issue with accessing https://m365.cloud.microsoft and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1467962 - Some admins' Microsoft 365 admin center usage report data may be delayed
| Status: | serviceRestored |
|---|
| Start Time: | Sat Sep 5 21:47:00 2026 |
|---|
| End Time: | Mon Sep 7 14:20:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 7 15:30:16 2026 |
|---|
| Root Cause: | An upstream data source pipeline issue was causing delays in some usage report data availability and was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 7 15:11:10 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may have been delayed.
More info:
- Microsoft 365 Copilot Readiness Reports may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data at the time of ongoing impact was from August 31, 2026.
- Copilot Chat Reports may have been delayed for admins in North America, and the latest data at the time of ongoing impact was from September 3, 2026.
- Microsoft 365 Apps usage Reports may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data at the time of ongoing impact was from August 31, 2026.
- Microsoft Teams User Activity Reports may have been delayed for admins in North America and Asia Pacific, and the latest data at the time of ongoing impact was from is from September 1, 2026.
Final status: We've validated that our solution to address the upstream data pipeline delay leading to this impact has fully addressed the impact, and all reports are now available as expected.
Scope of impact: Some admins attempting to view some usage report data in the Microsoft 365 admin center may have been impacted.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
End time: Monday, September 7, 2026, at 6:20 PM UTC
Root cause: An upstream data source pipeline issue was causing delays in some usage report data availability and was resulting in impact.
Next steps:
- We're reviewing what led to the upstream data pipeline delays based on our findings from this event to identify and implement improvements, which will help us prevent similar future impact from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Sep 7 14:00:04 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: - Microsoft 365 Copilot Readiness Reports are updated and no longer affected; previously they may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data was from August 31, 2026.
- Copilot Chat Reports are updated and no longer affected; previously they may have been delayed for admins in North America, and the latest data was from September 3, 2026.
- Microsoft 365 Apps usage Reports are updated and no longer affected; previously they may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America and Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: We've confirmed that our mitigations have addressed the impact for most reports, though impact is ongoing for the Microsoft Teams Apps User Activity report. We're continuing to apply our mitigations and aim to have an update on our progress by our next communication update.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Monday, September 7, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Sep 7 11:24:51 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, Microsoft 365 admin center usage reports include the following:
- Microsoft 365 Copilot Readiness Reports are updated and no longer affected; previously they may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data was from August 31, 2026.
- Copilot Chat Reports are updated and no longer affected; previously they may have been delayed for admins in North America, and the latest data was from September 3, 2026.
- Microsoft 365 Apps usage Reports may be delayed for admins in North America, Asia Pacific, and Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America and Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: We're continuing to apply mitigations and monitor the outcome to verify the efficacy of our actions in restoring current data for Microsoft Teams user activity in the Microsoft 365 admin center, as well as the Microsoft Teams Apps App usage and User activity reports in the Microsoft Teams admin center.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Tuesday, September 8, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Sun Sep 6 22:33:13 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, Microsoft 365 admin center usage reports include the following:
- Microsoft 365 Copilot Readiness Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Copilot Chat Reports may be delayed for admins in North America and the latest data is from September 3, 2026.
- Microsoft 365 Apps usage Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America, Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: We're continuing to monitor and implement our mitigations, and Microsoft Teams User Activity and Microsoft 365 Apps usage reports may still be delayed for admins with the latest data from September 1, 2026.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Monday, September 7, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Sun Sep 6 12:59:17 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, Microsoft 365 admin center usage reports include the following:
- Microsoft 365 Copilot Readiness Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Copilot Chat Reports may be delayed for admins in North America and the latest data is from September 3, 2026.
- Microsoft 365 Apps usage Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America, Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: After applying our solution to our data pipeline, our internal service telemetry has verified that Microsoft 365 Copilot Readiness and Copilot Chat Reports are no longer experiencing delays. While we monitor and complete our mitigations, Microsoft Teams User Activity and Microsoft 365 Apps usage reports may still be delayed for admins with the latest data from September 1, 2026.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Monday, September 7, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Sat Sep 5 22:30:16 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, Microsoft 365 admin center usage reports include the following:
- Microsoft 365 Copilot Readiness Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Copilot Chat Reports may be delayed for admins in North America and the latest data is from September 3, 2026.
- Microsoft 365 Apps usage Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America, Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: We've been made aware of an issue in which some admins' Microsoft 365 admin center usage report data may be delayed. We've identified that an upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact. We've developed a solution and are applying it to the affected pipeline to address the issue. We anticipate that impact to Copilot chat report data will be resolved by Sunday, September 6, 2026, at 3:30 AM UTC, and in the interim, we're working on determining the timeline for resolution for the remaining affected reports, which we aim to provide by our next scheduled communications update.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Saturday, September 5, 2026, at 12:00 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Monday, September 7, 2026, at 1:00 AM UTC
|
|---|
|
TM1462514 - Some users attempting to view their Microsoft Teams contact lists may experience latency
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 28 20:00:00 2026 |
|---|
| End Time: | Mon Sep 7 15:26:43 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 7 15:28:06 2026 |
|---|
| Root Cause: | A recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 7 15:28:03 2026 |
|---|
| Description: | Title: Some users attempting to view their Microsoft Teams contact lists may experience latency
User impact: Users attempting to view their Microsoft Teams contact lists may have experienced latency.
More info: Users attempting to view their Microsoft Teams contact lists may have experienced latency.
Final status: Our fix has completed its deployment to all affected regions, resolving this impact.
Scope of impact: Some users who were attempting to view their Microsoft Teams contact lists may have been affected.
Start time: Wednesday, July 29, 2026, at 12:00 AM UTC
End time: Saturday, September 5, 2026, at 12:00 AM UTC
Root cause: A recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and was resulting in impact.
Next steps: - We're reviewing the responsible service update to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 2 16:06:54 2026 |
|---|
| Description: | Title: Some users attempting to view their Microsoft Teams contact lists may experience latency
User impact: Users attempting to view their Microsoft Teams contact lists may experience latency.
More info: Users attempting to view their Microsoft Teams contact lists may experience latency and their contact list may not appear for up to 15 minutes.
Current status: The deployment of the code fix has begun, and we anticipate it being fully deployed to all affected environments by the time of our next communication.
Scope of impact: Some users who are attempting to view their Microsoft Teams contact lists may be affected. This information may be updated as our investigation continues.
Start time: Wednesday, July 29, 2026, at 12:00 AM UTC
Root cause: A recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and is resulting in impact.
Next update by: Monday, September 7, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 26 20:56:42 2026 |
|---|
| Description: | Title: Some users attempting to view their Microsoft Teams contact lists may experience latency
User impact: Users attempting to view their Microsoft Teams contact lists may experience latency.
More info: Users attempting to view their Microsoft Teams contact lists may experience latency and their contact list may appear for up to 15 minutes.
Current status: We’ve determined that a recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and is resulting in impact. We’ve developed a fix to correct the offending code regression, and we anticipate that the deployment process will begin prior to our next scheduled update, at which point we expect that a remediation timeline will be provided.
Scope of impact: Some users who are attempting to view their Microsoft Teams contact lists may be affected. This information may be updated as our investigation continues.
Start time: Wednesday, July 29, 2026, at 12:00 AM UTC
Root cause: A recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 26 20:29:04 2026 |
|---|
| Description: | Title: Some users attempting to view their Microsoft Teams contact lists may experience latency
User impact: Users attempting to view their Microsoft Teams contact lists may experience latency.
More info: Users attempting to view their Microsoft Teams contact lists may experience latency and their contact list may appear for up to 15 minutes.
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.
|
|---|
|
CW1467407 - Users may be unable to query Microsoft 365 Copilot Chat and receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 4 21:45:26 2026 |
|---|
| End Time: | Fri Sep 4 22:34:49 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sat Sep 5 00:18:53 2026 |
|---|
| Root Cause: | A recent configuration change caused a subset of query requests to be rejected, resulting in elevated error rates and resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 22:41:57 2026 |
|---|
| Description: | Title: Users may be unable to query Microsoft 365 Copilot Chat and receive an error
User impact: Users may be unable to query Copilot Chat and receive an error.
More info: When users attempted to query Copilot Chat, some of their queries may have returned no response and instead, users may have received an error that stated, "Something went wrong."
Final status: Our review of the service health telemetry isolated that a recent configuration change caused a subset of requests to be rejected, resulting in elevated error rates and resulted in impact. We’ve since reverted the offending change and after an extended period of monitoring, we’ve confirmed that impact was remediated.
Scope of impact: Any user who attempted to query Copilot Chat may be impacted.
Start time: Saturday, September 5, 2026, at 12:40 AM UTC
End time: Saturday, September 5, 2026, at 2:09 AM UTC
Root cause: A recent configuration change caused a subset of query requests to be rejected, resulting in elevated error rates and resulted in impact.
Next steps: We'll review our service update validation process to ensure similar instances aren't replicated in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 4 21:47:18 2026 |
|---|
| Description: | Title: Users may be unable to query Microsoft 365 Copilot Chat and receive an error
User impact: Users may be unable to query Copilot Chat and receive an error.
More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong."
Current status: Our service health monitoring alerted us to an increase in failures occurring when users attempt to query Copilot Chat. We're reviewing our service health telemetry to isolate the source of the failures, so that we can develop a mitigation plan.
Scope of impact: Any user attempting to query Copilot Chat may be impacted. This information may be updated as our investigation continues.
Next update by: Saturday, September 5, 2026, at 3:00 AM UTC
|
|---|
|
MO1467282 - Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 4 14:44:09 2026 |
|---|
| End Time: | Fri Sep 4 22:47:15 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 4 22:50:13 2026 |
|---|
| Root Cause: | A recent service update intended to refresh the pages of service central contained a code issue, which was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 22:50:10 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may have not been able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users were able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Final status: We've confirmed that our fix has finished deploying to all affected environments, remediating this impact.
Scope of impact: This event impacted any user attempting to access support central through the Microsoft Intune or Microsoft Defender portals.
Start time: Tuesday, September 1, 2026, at 4:00 PM UTC
End time: Saturday, September 5, 2026, at 2:35 AM UTC
Root cause: A recent service update intended to refresh the pages of service central contained a code issue, which was resulting in impact.
Next steps: - We're reviewing the responsible update to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 4 20:48:58 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users are able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Current status: Our fix deployment is progressing, and some users may already be experiencing reduced impact. However, additional time is required for the deployment to reach all affected environments before the issue is fully resolved.
Scope of impact: This event impacts any user attempting to access support central through the Microsoft Intune or Microsoft Defender portals. This information may be updated as our investigation continues.
Root cause: A recent service update intended to refresh the pages of service central contained a code issue, which is resulting in impact.
Next update by: Saturday, September 5, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Fri Sep 4 18:18:05 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users are able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Current status: We've started deploying our fix to address this issue and anticipate that this process will be complete by our next scheduled update.
Scope of impact: This event impacts any user attempting to access support central through the Microsoft Intune or Microsoft Defender portals. This information may be updated as our investigation continues.
Root cause: A recent service update intended to refresh the pages of service central contained a code issue, which is resulting in impact.
Next update by: Saturday, September 5, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Sep 4 15:16:26 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users are able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Current status: We determined that a recent service update intended to refresh the pages of service central contained a code issue, which is resulting in impact. We've developed a fix to address this issue and will provide a remediation timeline once this fix is ready to deploy to all affected environments.
Scope of impact: This event impacts any user attempting to access support central through the Microsoft Intune or Microsoft Defender portals. This information may be updated as our investigation continues.
Start time: Tuesday, September 1, 2026, at 4:00 PM UTC
Root cause: A recent service update intended to refresh the pages of service central contained a code issue, which is resulting in impact.
Next update by: Friday, September 4, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Sep 4 14:46:09 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users are able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Current status: We're investigating a potential issue with two different Microsoft 365 portals and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1466822 - Some users may see various issues with sharing of Agent Builders in Microsoft 365 Copilot Studio
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 3 20:23:39 2026 |
|---|
| End Time: | Fri Sep 4 16:11:21 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 4 16:31:22 2026 |
|---|
| Root Cause: | A previous deployment to Agent Builder contained a code issue that resulted in various issues with sharing of Agent Builders in Copilot Studio.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 16:31:18 2026 |
|---|
| Description: | Title: Some users may see various issues with sharing of Agent Builders in Microsoft 365 Copilot Studio
User impact: Users may have seen various issues with sharing of Agent Builders in Copilot Studio.
More info: In the "Share dialog", the operation appeared to complete successfully, but the share targets weren't actually saved. Users you added didn't gain access, and users you removed may have kept it. Since sharing looked successful, impacted users may not have noticed it until later, when added or removed people didn't persist in the shared-users list.
Specifically, impact happened only if the agent's knowledge sources included a SharePoint Online site that was added from the grounding menu. Agents without such a source were not affected.
While the initial fix prevented any new agents from entering the impacted state, affected users may have been able to perform the following steps for agents that were already impacted:
1) Open the affected agent and remove the SharePoint site knowledge source (keep all other knowledge/media sources).
2) Re-add the SharePoint site. (if doesn't work remove and re-add)
Retry Share and confirm the intended users now appear in the shared-users list.
Final status: We've confirmed that the secondary fix is deployed to clean up agents that were affected throughout the duration of this event has completed development, and after monitoring service health metrics, we've confirmed that the associated failures have ceased and the impact has been remediated by our actions.
Scope of impact: Some users utilizing Agent Builders in Copilot Studio may have been impacted.
Start time: Wednesday, August 26, 2026, at 5:44 AM UTC
End time: Thursday, September 3, 2026, at 10:09 PM UTC
Root cause: A previous deployment to Agent Builder contained a code issue that resulted in various issues with sharing of Agent Builders in Copilot Studio.
Next steps:
- We're reviewing our deployment standards to ensure that similar code issues are identified and corrected ahead of implementation to prevent this from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 21:18:27 2026 |
|---|
| Description: | Title: Some users may see various issue with sharing of Agent Builders in Microsoft 365 Copilot Studio
User impact: Users may see various issue with sharing of Agent Builders in Copilot Studio.
More info: In the "Share dialog", the operation appears to complete successfully, but the share targets aren't actually saved. Users you add don't gain access, and users you remove may keep it. Since sharing looks successful, impacted users may not notice it until later, when added or removed people don't persist in the shared-users list.
Specifically, impact happens only if the agent's knowledge sources include a SharePoint Online site that was added from the grounding menu. Agents without such a source are not affected.
While the initial fix will prevent any new agents from entering the impacted state, affected users may perform the following steps for agents that are already impacted:
1) Open the affected agent and remove the SharePoint site knowledge source. (keep all other knowledge/media sources).
2) Re-add the SharePoint site. (if doesn't work remove and re-add)
Retry Share and confirm the intended users now appear in the shared-users list.
Current status: We've determined that a previous deployment to Agent Builder contains a code issue that's resulting in various issues with sharing of Agent Builders in Copilot Studio. We've developed two parallel fixes to address this issue, and the first code change to ensure that new SharePoint Online site sources are no longer affected has successfully been deployed. The affected sources are now automatically repaired when agents are published or shared, preventing further agents from entering the impacted state. We’re monitoring as the secondary fix is deployed to clean up agents that were already affected throughout the duration of this event.
Scope of impact: Some users utilizing Agent Builders in Copilot Studio may be impacted.
Start time: Wednesday, August 26, 2026, at 5:44 AM UTC
Root cause: A previous deployment to Agent Builder contains a code issue that's resulting in various issues with sharing of Agent Builders in Copilot Studio.
Next update by: Friday, September 4, 2026, at 9:00 PM UTC
|
|---|
|
TM1467148 - Users may be unable to access some third-party apps within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 3 22:53:00 2026 |
|---|
| End Time: | Fri Sep 4 11:14:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 4 14:23:34 2026 |
|---|
| Root Cause: | A code issue occurring within an upstream service caused the third-party app to be removed from the app catalog, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 12:31:17 2026 |
|---|
| Description: | Title: Users may be unable to access some third-party apps within Microsoft Teams
User impact: Users may have been unable to access some third-party apps within Microsoft Teams.
Final status: We've deployed our fix to address the upstream code issue and confirmed through monitoring service health telemetry that the impact has been remediated. Admins will need to restore the pre-impact app configurations within the Microsoft Teams admin center to have access restored. The pre-impact app configuration settings can be gathered from audit logs.
Scope of impact: Any user attempting to access a some third-party apps may have been impacted.
Start time: Friday, September 4, 2026, at 2:53 AM UTC
End time: Friday, September 4, 2026, at 3:14 PM UTC
Root cause: A code issue occurring within an upstream service caused the third-party app to be removed from the app catalog, resulting in impact.
Next steps:
- We're reviewing the offending code issue to determine how it was introduced into the service, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 4 11:14:31 2026 |
|---|
| Description: | Title: Users may be unable to access some third-party apps within Microsoft Teams
User impact: Users may be unable to access some third-party apps within Microsoft Teams.
Current status: We've identified that a code issue occurring within an upstream service caused the third-party app to be removed from the app catalog, resulting in impact. We've developed a fix to address the code issue and return the app to the catalog, and we'll aim to provide a timeline for the deployment of our fix to begin by our next schedule communications update. Once the fix has been deployed, admins will need to restore the pre-impact app configurations within the Microsoft Teams admin center to have access restored.
Scope of impact: Any user attempting to access some third-party apps may be impacted. This section may be updated as our investigation continues.
Start time: Friday, September 4, 2026, at 2:53 AM UTC
Root cause: A code issue occurring within an upstream service caused the third-party app to be removed from the app catalog, resulting in impact.
Next update by: Friday, September 4, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 11:00:13 2026 |
|---|
| Description: | Title: Users may be unable to access some third-party apps within Microsoft Teams
User impact: Users may be unable to access some third-party apps within 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.
|
|---|
|
SP1464785 - Some users may be unable to access SharePoint Online sites configured with Authentication Context
| Status: | serviceRestored |
|---|
| Start Time: | Sat Aug 22 22:38:00 2026 |
|---|
| End Time: | Fri Sep 4 13:18:41 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Access Services |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Sep 4 13:22:06 2026 |
|---|
| Root Cause: | A recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 13:21:41 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may have been unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users were unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users received the following error message:
"Server Error in '/' Application."
As a workaround, users may have been able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users could have also opened a new browser tab on the same session and access the site or used a direct link.
Final status: After confirming that our reversion of the code update to the SharePoint Online authentication process completed as expected and was available in all environments, we validated with a portion of impacted users that access to SharePoint Online sites configured with Authentication Context has been restored.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may have been impacted.
Start time: Sunday, August 23, 2026, at 2:38 AM UTC
End time: Friday, September 4, 2026, at 5:00 PM UTC
Root cause: A recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites.
Next steps: - We're continuing to optimize our quality assurance processes to minimize user impact while ensuring important service health updates are deployed as efficiently as possible.
|
|---|
|
| Time: | Wed Sep 2 13:55:53 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users receive the following error message:
"Server Error in '/' Application."
As a workaround, users may be able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users can also open a new browser tab on the same session and access the site. The link may work as well.
Current status: The deployment is progressing as expected and users will see relief as it progresses. We expect the release to complete, mitigating impact for all users by the next scheduled update.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted. This information may be updated as our investigation continues.
Start time: Sunday, August 23, 2026, at 2:38 AM UTC
Root cause: A recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites.
Next update by: Friday, September 4, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 14:04:34 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users receive the following error message:
"Server Error in '/' Application."
As a workaround, users may be able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users can also open a new browser tab on the same session and access the site. The link may work as well.
Current status: We've identified that a recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites. We've developed a fix to revert the offending change and have initiated deployment to the affected environments. We're monitoring the deployment to ensure successful completion, and as the fix progresses, some users may experience impact relief. We'll provide a resolution timeline once available.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Start time: Sunday, August 23, 2026, at 2:38 AM UTC
Root cause: A recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites.
Next update by: Wednesday, September 2, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 17:49:50 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users receive the following error message:
"Server Error in '/' Application."
As a workaround, users may be able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users could also open a new browser tab on the same session and access the site. The link may work as well.
Current status: We've determined that reverting the update suspected of causing this issue isn't a viable path to remediation. We're reviewing alternative solutions to confirm the impact and resolve the problem.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Tuesday, September 1, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 16:16:36 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users receive the following error message:
"Server Error in '/' Application."
As a workaround, users may be able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users could also open a new browser tab on the same session and access the site. The link may work as well.
Current status: We've identified a recent change which we suspect may be leading to the impact, and we're determining whether rolling the change back is a viable option to remediate impact.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 14:05:46 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Current status: Our investigation of the Authentication Context configuration is ongoing as we work to confirm the source of the impact before we can begin to develop a mitigation strategy.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 12:11:52 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Current status: In addition to our HAR analysis, we're further reviewing the Authentication Context configuration to understand whether this is where the impact originates.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 09:56:25 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Current status: We're reviewing HAR files that compare successful access requests initiated through the root site collection with failing direct-link requests to determine why the behavior differs and identify next steps to mitigate impact.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 08:36:00 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Current status: We've reproduced the issue in our testing environment and are reviewing HTTP Archive (HAR) logs to determine why direct links fail when Authentication Context is enabled through sensitivity labels.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 2:30 PM UTC
|
|---|
|
TM1466659 - Users may have been unable to join calls or meetings in Microsoft Teams for Mac
| Status: | serviceRestored |
|---|
| Start Time: | Sun Aug 23 12:32:00 2026 |
|---|
| End Time: | Wed Aug 26 16:51:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Sep 4 10:55:00 2026 |
|---|
| Root Cause: | A code change caused the service infrastructure responsible for call and meeting functionality to fail to process some requests, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 10:49:44 2026 |
|---|
| Description: | Title: Users may have been unable to join calls or meetings in Microsoft Teams for Mac
User impact: Users may have been unable to join calls or meetings in Microsoft Teams for Mac.
Final status: We've determined that a code change caused the service infrastructure responsible for call and meeting functionality to fail to process some requests, which resulted in impact. We've deployed a fix and confirmed that impact has been resolved after an extended period of monitoring service availability.
Scope of impact: Some users attempting to join calls or meetings in Microsoft Teams for Mac may have been impacted.
Start time: Sunday, August 23, 2026, at 4:32 PM UTC
End time: Wednesday, August 26, 2026, at 8:51 PM UTC
Root cause: A code change caused the service infrastructure responsible for call and meeting functionality to fail to process some requests, which resulted in 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: | Thu Sep 3 16:13:51 2026 |
|---|
| Description: | Title: Users may be unable to join calls or meetings in Microsoft Teams for Mac
User impact: Users may be unable to join calls or meetings in Microsoft Teams for Mac.
Current status: Further review of the suspected code change indicates it may not be the cause of impact for this event. We're reassessing our root cause understanding and reviewing service logs to isolate the source of impact, so that we can determine our next steps regarding impact remediation.
Scope of impact: Some users attempting to join calls or meetings in Microsoft Teams for Mac may be impacted. This section may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 15:25:54 2026 |
|---|
| Description: | Title: Users may be unable to join calls or meetings in Microsoft Teams for Mac
User impact: Users may be unable to join calls or meetings in Microsoft Teams for Mac.
Current status: We've identified a code change that's causing the service infrastructure responsible for call and meeting functionality to fail to process some requests, resulting in impact. We're assessing potential remediation actions to address the problematic code change and restore service functionality.
Scope of impact: Some users attempting to join calls or meetings in Microsoft Teams for Mac may be impacted. This section may be updated as our investigation continues.
Start time: Thursday, July 2, 2026, at 3:09 PM UTC
Root cause: A code change is causing the service infrastructure responsible for call and meeting functionality to fail to process some requests, resulting in impact.
Next update by: Thursday, September 3, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 14:59:28 2026 |
|---|
| Description: | Title: Users may be unable to join calls or meetings in Microsoft Teams for Mac
User impact: Users may be unable to join calls or meetings in Microsoft Teams for Mac.
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.
|
|---|
|
MO1465286 - Admins may see delays in Copilot usage report data in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 31 20:25:42 2026 |
|---|
| End Time: | Thu Sep 3 15:46:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 23:10:10 2026 |
|---|
| Root Cause: | A component utilized in the flow of this functionality was deprecated, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 23:10:10 2026 |
|---|
| Description: | Title: Admins may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins may have seen delays in Copilot usage report data in the Microsoft 365 admin center.
Final status: Our operation to process the remaining backlog of usage report data is complete, and we've monitored our telemetry to confirm that the impact is remediated.
Scope of impact: This event impacted any admin attempting to access Copilot usage report data in the Microsoft 365 admin center.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
End time: Thursday, September 3, 2026, at 7:46 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next steps:
- We're reviewing our deprecation procedures pertaining to the components of Copilot infrastructure responsible for processing usage report data to prevent similar impact after future maintenance operations.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 21:28:56 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: Processing of the usage report data remains underway, and we’re monitoring recovery to confirm sustained progress and determine an updated completion timeline.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Friday, September 4, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Sep 3 13:34:11 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: The usage report data is continuing to progress; however, recovery is occurring more slowly than previously anticipated. We're continuing to monitor the processing progress and validate recovery trends to establish an updated completion timeline. We'll provide additional information on the expected recovery timeline once it has been confirmed.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Friday, September 4, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 20:32:38 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: Our review of service health telemetry indicates that recovery of all usage report data is progressing as expected, and all usage report data may be fully recovered by our next scheduled update. We're continuing to monitor to confirm this timeline, and if validation continues as expected, we anticipate recovery to be complete by our next scheduled communications update.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Thursday, September 3, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 12:36:52 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: A majority of the accumulated data has been processed, and our review of service health telemetry has confirmed that all Copilot usage report data excluding Graph API Copilot usage data is now up to date. While the accumulated data for the Graph API Copilot usage data continues to be processed, we recommend admins utilize the beta Graph API endpoint to view up-to-date data. We'll aim to provide a timeline for all usage report data to be recovered by our next scheduled communications update.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 12:29:09 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: It's taking longer than initially anticipated for the backlog of accumulated data to be processed and for Copilot usage reporting to catch up to the expected data. We'll aim to provide a timeline for the reporting data to be up to date by our next scheduled communications update.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Wednesday, September 2, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 20:27:59 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: We determined that a component utilized in the flow of this functionality was deprecated, resulting in impact. We're reinstating this component and anticipate that this process should be complete by our next scheduled update.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 PM UTC
|
|---|
|
CW1466621 - Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 3 02:30:00 2026 |
|---|
| End Time: | Thu Sep 3 15:45:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 3 17:06:05 2026 |
|---|
| Root Cause: | An increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses prevented the service from being able to efficiently process requests.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 16:58:18 2026 |
|---|
| Description: | Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error
User impact: Users' queries to Copilot Chat may have returned no response, and users received an error.
More info: When users attempted to query Copilot Chat, some of their queries may have returned no response and instead, users may have received an error that stated, "Something went wrong."
Final status: We've applied configuration changes to rebalance the request traffic and confirmed using our service health telemetry that the impact is remediated.
Scope of impact: Any user that attempted to query Copilot Chat may have been impacted.
Start time: Thursday, September 3, 2026, at 6:30 AM UTC
End time: Thursday, September 3, 2026, at 7:45 PM UTC
Root cause: An increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses prevented the service from being able to efficiently process requests.
Next steps:
- We're continuing to investigate the source of the increased request traffic, so that we can determine how to prevent similar impact to users' Copilot Chat queries in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 14:42:10 2026 |
|---|
| Description: | Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error
User impact: Users' queries to Copilot Chat may return no response, and users receive an error.
More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong."
Current status: We've identified an increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses which is preventing the service from being able to efficiently process requests. We're evaluating our mitigation options to identify the most effective method to remediate the impact.
Scope of impact: Any user attempting to query Copilot Chat may be impacted.
Start time: Thursday, September 3, 2026, at 6:30 AM UTC
Root cause: An increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses which is preventing the service from being able to efficiently process requests.
Next update by: Thursday, September 3, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 13:27:02 2026 |
|---|
| Description: | Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error
User impact: Users' queries to Copilot Chat may return no response, and users receive an error.
More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong."
Current status: Our service health monitoring alerted us to an increase in failures occurring when users attempt to query Copilot Chat. We're reviewing our service health telemetry to isolate the source of the failures, so that we can developed a mitigation plan.
Scope of impact: Any user attempting to query Copilot Chat may be impacted.
Next update by: Thursday, September 3, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 13:16:55 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot Chat
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
WP1466588 - Admins may notice that Cloud PC service components aren't updating
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 17 12:00:00 2026 |
|---|
| End Time: | Thu Sep 3 13:25:00 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | Manageability |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 14:17:24 2026 |
|---|
| Root Cause: | A recent service change added new endpoint URLs that weren't publicly communicated, which prevented admins from adding them to their allow lists and caused impact by blocking the requests to update Cloud PC service components.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 13:44:45 2026 |
|---|
| Description: | Title: Admins may notice that Cloud PC service components aren't updating
User impact: Admins may have noticed that Cloud PC service components weren't updating.
More info: Admins may have noticed that their Cloud PC service components, including the remote desktop (RD) agent or side-by-side stack, weren't updating. There was no impact to general user connectivity to the Cloud PCs.
Final status: We've reversed the service change to revert back to our previous list of endpoint URLs and confirmed through internal testing that the impact is remediated as a result for this action.
Scope of impact: Any admin that expected updates to their Cloud PC service components may have been impacted.
Start time: Monday, August 17, 2026, at 4:00 PM UTC
End time: Thursday, September 3, 2026, at 5:25 PM UTC
Root cause: A recent service change added new endpoint URLs that weren't publicly communicated, which prevented admins from adding them to their allow lists and caused impact by blocking the requests to update Cloud PC service components.
Next steps:
- We're reviewing our service change testing and validation procedures to identify and prevent similar issues with changing endpoint URLs before notifying admins moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 12:33:22 2026 |
|---|
| Description: | Title: Admins may notice that Cloud PC service components aren't updating
User impact: Admins may notice that Cloud PC service components aren't updating.
More info: Admins may notice that their Cloud PC service components, including the remote desktop (RD) agent or side-by-side stack, aren't updating. There's no impact to general user connectivity to the Cloud PCs.
Current status: We've identified a recent service change that added new endpoint URLs that weren't publicly communicated, which prevented admins from adding them to their allow lists and is causing impact by blocking the requests to update Cloud PC service components. We're reversing the service change to revert back to our previous list of endpoint URLs and remediate the impact.
Scope of impact: Any admin expecting updates to their Cloud PC service components may be impacted.
Root cause: A recent service change added new endpoint URLs that weren't publicly communicated, which prevented admins from adding them to their allow lists and is causing impact by blocking the requests to update Cloud PC service components.
Next update by: Thursday, September 3, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 12:08:10 2026 |
|---|
| Description: | Title: Admins' Cloud PC components may not be updating
User impact: Admins' Cloud PC components may not be updating.
More info: Admins notice that their Cloud PC components may not be updating; however, there's no impact to general user connectivity to the Cloud PCs.
Current status: We're investigating a potential issue with Windows 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1463371 - Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 19 20:00:00 2026 |
|---|
| End Time: | Mon Aug 31 10:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 13:29:47 2026 |
|---|
| Root Cause: | A recent update introduced a code defect that was resulting in this impacting event.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 11:35:46 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may have failed to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affected users who updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application would have restored optimized functionality.
Final status: We've confirmed through monitoring service health telemetry for an extended period as well as testing with a subset of affected users that the impact has been remediated. If any users are still facing impact, they'll need to restart their Microsoft Teams application so the fix can be applied.
Scope of impact: Users who updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may have experienced failures of the Microsoft Teams application running as optimized for VDI.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
End time: Monday, August 31, 2026, at 2:30 PM UTC
Root cause: A recent update introduced a code defect that was resulting in this impacting event.
Next steps:
- We're reviewing our update procedures to understand why impact to application functionality 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: | Tue Sep 1 11:19:02 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application will restore optimized functionality.
Current status: After our completed deployed code fix, our internal service telemetry reports that the failures when running optimized Microsoft Teams in Virtual Desktop Infrastructure has been remediated. Users who continue to experience failures will need to twice restart their Microsoft Teams application so our fix can be applied and to remediate the impact.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Root cause: A recent update introduced a code defect that's resulting in this impacting event.
Next update by: Thursday, September 3, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 11:23:59 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: Our monitoring continues to show improvement, and we're continuing to observe the positive trend to ensure no further actions are needed and the impact is fully remediated.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Root cause: A recent update inadvertently introduced a code defect resulting in this impacting event.
Next update by: Tuesday, September 1, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Aug 28 17:06:43 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: We're observing positive trends in telemetry after applying our code fix for this issue and are allowing an additional period of monitoring to ensure that this event has fully resolved for all affected environments.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Root cause: A recent update inadvertently introduced a code defect resulting in this impacting event.
Next update by: Monday, August 31, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Aug 28 14:22:34 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: We've applied a code update change to remediate a code defect that was inadvertently introduced in the most recent service-side update. This code change will automatically be applied after four hours as part of the routine service refresh. Alternatively, users can restart Microsoft Teams to get the fix and then restart again five minutes later to apply the fix. We're continuing to monitor service-side telemetry to ensure the remediation actions fully resolve the impact.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Root cause: A recent update inadvertently introduced a code defect resulting in this impacting event.
Next update by: Friday, August 28, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Aug 28 12:49:41 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: We believe we’ve identified a recent service-side update as the root cause of this issue. We're validating a potential remediation solution, which will also confirm our root cause theory, before deploying it to all affected areas.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Next update by: Friday, August 28, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Aug 28 11:30:49 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: We're reviewing service-side logs and recent platform updates to determine the cause of reports that Microsoft Teams isn't consistently operating in its optimized VDI mode. We're analyzing available telemetry to identify the source of the issue and determine appropriate remediation options.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Next update by: Friday, August 28, 2026, at 5:00 PM UTC
|
|---|
|
TM1466441 - Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
| Status: | serviceRestored |
|---|
| Start Time: | Tue Aug 18 09:30:00 2026 |
|---|
| End Time: | Thu Sep 3 09:46:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 13:29:12 2026 |
|---|
| Root Cause: | A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that was preventing Teams channel tabs from rendering correctly.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 11:49:42 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may have been unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may have only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels were long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may have not been visible.
As a workaround, impacted users could zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Final status: We've confirmed through testing with a subset of affected users that reverting the recent configuration change has remediated the impact.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may have been impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
End time: Thursday, September 3, 2026, at 1:46 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that was preventing Teams channel tabs from rendering correctly.
Next steps:
- We're reviewing the offending configuration change to understand why the regression wasn't identified during our pre-deployment testing processes, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 09:50:56 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We've completed the reversion of the offending configuration change and are reaching out to a number of impacted users to confirm that this action successfully resolved the issue.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly.
Next update by: Thursday, September 3, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 08:26:42 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We’re working to revert the offending configuration change. We expect that this will process will be complete and the issue resolved by our next scheduled update.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly.
Next update by: Thursday, September 3, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 08:26:41 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We’re working to revert the offending configuration change. We expect that this will process will be complete and the issue resolved by our next scheduled update.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly.
Next update by: Thursday, September 3, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 06:41:27 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We’ve determined that a recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly. We’re deploying a fix to mitigate the impact and conducting internal validation to confirm it successfully resolves the issue.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly.
Next update by: Thursday, September 3, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 04:45:36 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We're reviewing HTTP Archive (HAR) files and Teams client logs from a number of impacted users to determine the root cause and identify mitigation options.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Next update by: Thursday, September 3, 2026, at 11:00 AM UTC
|
|---|
|
CW1461372 - Some users may be unable to receive responses when using Microsoft 365 Copilot Chat
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Aug 24 18:50:00 2026 |
|---|
| End Time: | Tue Aug 25 06:20:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 3 09:57:04 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 09:57:04 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Sep 1 20:09:20 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Aug 27 16:52:05 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Aug 25 08:02:17 2026 |
|---|
| Description: | Title: Some users may have been unable to receive responses when using Microsoft 365 Copilot Chat
User impact: Users may have been unable to receive responses when using Copilot Chat.
More info: Affected users may have received error messages stating that a problem had occurred or that Copilot could not respond.
Final status: We've completed reverting the change that inadvertently led to impact. Upon completing a period of monitoring, we've determined service availability has returned to normal, and the issue is resolved.
Scope of impact: This issue may have impacted any user attempting to use Copilot Chat.
Start time: Monday, August 24, 2026, at 10:50 PM UTC
End time: Tuesday, August 25, 2026, at 10:20 AM UTC
Preliminary root cause: A recent change designed to support metered access for certain scenarios did not deliver the expected outcome, inadvertently resulting in impact.
Next steps:
- We are reviewing our internal change management processes and controls to identify opportunities for improvement, and strengthen our safeguards around future changes.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue Aug 25 06:47:58 2026 |
|---|
| Description: | The roll back of the suspected change is continuing as expected. Early indications continue to show an improvement in service availability and we've received some reports from previously affected customers that the issue is resolved. We're continuing to monitor this rollback process closely to ensure a complete resolution is achieved.
Next update by: Tuesday, August 25, 2026, at 12:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 25 06:25:49 2026 |
|---|
| Description: | Title: Some users may be unable to receive responses when using Microsoft 365 Copilot Chat
User impact: Users may be unable to receive responses when using Copilot Chat.
More info: Affected users may receive error messages stating that a problem has occurred or that Copilot could not respond.
Current status: We've reverted the suspected change and are observing signs of recovery in service telemetry. We're engaging a sample of affected users to validate whether this action has successfully mitigated the issue and restored Chat functionality.
Scope of impact: This issue may impact any user attempting to use Copilot Chat. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 06:08:54 2026 |
|---|
| Description: | Title: Some users may be unable to receive responses when using Microsoft 365 Copilot Chat
User impact: Users may be unable to receive responses when using Copilot Chat.
More info: Affected users may receive error messages stating that a problem has occurred or that Copilot could not respond.
Current status: We've identified a recent service update that may be contributing to impact. We're continuing to analyze service telemetry and diagnostic data to validate this correlation while evaluating mitigation actions to reduce impact and restore Chat functionality.
Scope of impact: This issue may impact any user attempting to use Copilot Chat. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Aug 25 04:19:07 2026 |
|---|
| Description: | Title: Some users may be unable to receive responses when using Microsoft 365 Copilot Chat
User impact: Users may be unable to receive responses when using Copilot Chat.
More info: Affected users may receive error messages stating that a problem has occurred or that Copilot could not respond.
Current status: We've received reports indicating an issue with Copilot Chat where some users may be unable to receive responses to prompts. We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to use Copilot Chat may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 10:30 AM UTC
|
|---|
|
DZ1466442 - Admins have received delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 3 03:30:00 2026 |
|---|
| End Time: | Thu Sep 3 08:39:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 09:00:23 2026 |
|---|
| Root Cause: | A network policy hardening change introduced a regression affecting a dependency required by the service to retrieve essential configuration data. As a result, some service instances were unable to start successfully, reducing processing capacity and causing telemetry and alert delivery delays.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 08:59:59 2026 |
|---|
| Description: | Title: Admins have received delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal
User impact: Admins have received delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.
More info: Affected admins may have experienced delays of up to 3 hours in receiving Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Final status: We've identified that a network policy hardening change introduced a regression affecting a dependency required by the service to retrieve essential configuration data. As a result, some service instances were unable to start successfully, reducing processing capacity and causing telemetry and alert delivery delays that led to backlog accumulation. We've re-enabled the affected access path and initiated a revert of the impacting networking policy change. Following our mitigation actions, affected service instances have begun recovering successfully and we've observed backlog recovery as processing capacity returned to expected levels.
Scope of impact: Some admins in Europe expecting to receive recent Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal or Microsoft Sentinel may have been impacted.
Start time: Thursday, September 3, 2026, at 7:30 AM UTC
End time: Thursday, September 3, 2026, at 12:39 PM UTC
Root cause: A network policy hardening change introduced a regression affecting a dependency required by the service to retrieve essential configuration data. As a result, some service instances were unable to start successfully, reducing processing capacity and causing telemetry and alert delivery delays.
Next steps:
- We're reviewing our networking policy deployment and validation processes to better identify and prevent similar issues before changes are introduced into production environments.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 06:56:52 2026 |
|---|
| Description: | Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.
More info: Affected admins may experience delays of up to 3 hours in receiving Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We've initiated several mitigation actions to improve processing throughput, including scaling out the affected queue consumer service to increase processing capacity, redeploying the service in impacted regions, and testing configuration changes designed to reduce processing pressure and improve throughput. We're monitoring the effectiveness of these changes as we continue working to identify the underlying cause of the issue.
Scope of impact: Some admins in Europe expecting to receive recent Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal or Microsoft Sentinel may be impacted.
Start time: Thursday, September 3, 2026, at 7:30 AM UTC
Next update by: Thursday, September 3, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 04:50:48 2026 |
|---|
| Description: | Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.
More info: Affected admins may experience delays of up to 3 hours in receiving Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We're reviewing service monitoring telemetry and analyzing system logs to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some admins in Europe expecting to receive recent Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal or Microsoft Sentinel may be impacted.
Start time: Thursday, September 3, 2026, at 7:30 AM UTC
Next update by: Thursday, September 3, 2026, at 11:00 AM UTC
|
|---|
|
EX1466248 - Some users may see intermittent mailbox access issues from any Exchange Online connection method
| Status: | serviceRestored |
|---|
| Start Time: | Wed Sep 2 16:03:08 2026 |
|---|
| End Time: | Wed Sep 2 17:33:40 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 3 00:02:48 2026 |
|---|
| Root Cause: | A subset of infrastructure that facilitated access to Exchange Online mailboxes was operating in a sub optimal state, causing processing delays and leading to mailbox access issues.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 17:39:58 2026 |
|---|
| Description: | Title: Some users may see intermittent mailbox access issues from any Exchange Online connection method
User impact: Users may have seen intermittent mailbox access issues from any Exchange Online connection method.
Final status: We've determined that a subset of infrastructure that facilitated access to Exchange Online mailboxes was operating in a sub optimal state, causing processing delays and leading to mailbox access issues. We’ve switched out the affected subset of infrastructure to remediate the impact and confirmed from service telemetry that this issue is resolved.
Scope of impact: Some users based in North America may have seen intermittent mailbox access issues from any Exchange Online connection method.
Start time: Wednesday, September 2, 2026, at 7:45 PM UTC
End time: Wednesday, September 2, 2026, at 8:11 PM UTC
Root cause: A subset of infrastructure that facilitated access to Exchange Online mailboxes was operating in a sub optimal state, causing processing delays and leading to mailbox access issues.
Next steps: - We're continuing our investigation to determine the underlying reason the affected subset of infrastructure began operating in a sub optimal state to better detect and prevent issues like this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 2 16:28:40 2026 |
|---|
| Description: | Title: Some users may see intermittent mailbox access issues from any Exchange Online connection method
User impact: Users may see intermittent mailbox access issues from any Exchange Online connection method.
Current status: We're reviewing system logs and service telemetry to isolate the origin of this issue.
Scope of impact: Some users based in North America may see intermittent mailbox access issues from any Exchange Online connection method.
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 16:05:34 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
TM1437780 - Some users may be unable to join or create Microsoft Teams meetings or calls
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 20:25:00 2026 |
|---|
| End Time: | Thu Jul 23 21:27:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Sep 2 22:45:12 2026 |
|---|
| Root Cause: | The incident was triggered during the rollback of a Cosmos DB configuration designed to help limit the impact of failures and prevent wider service disruptions in one of the Teams services. As part of a precautionary investigation into a potential issue with this configuration, the feature was disabled in the APAC region. During the rollback, a subset of data partitions experienced a temporary service inconsistency for approximately 23 minutes, which resulted in intermittent request failures.
As dependent services and client applications attempted to recover from these failures, request volumes increased significantly and created an unexpected surge in traffic across several platform services. The elevated traffic levels placed substantial pressure on service infrastructure, leading to broader service degradation and impacting some calling and meeting scenarios.
The issue gradually self-resolved as platform scaling and traffic-management mechanisms automatically adjusted to absorb the increased demand. While service was restored without additional customer action, there are follow-up repair items to further strengthen resilience and reduce the likelihood of similar incidents in the future. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 22:45:12 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Aug 27 21:16:07 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jul 31 17:46:55 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 30 19:15:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jul 27 18:36:11 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 23 23:08:49 2026 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings or calls
User impact: Users may have been unable to join or create Microsoft Teams meetings or calls.
More info: According to our impact analysis, the following scenarios were among those most impacted:
-Recordings and Transcriptions
-1:1 Calling
-Group calling
-Meeting join
-Meeting scheduling and creation
-Public switched telephone network (PSTN) calls
Final status: After a recursive analysis of additional metrics, we've observed persistent recovery across all previously affected scenarios. Closer analysis identified a recent change associated with our ongoing service resilience efforts which overloaded our traffic management processes and caused impact. The service is now restored; however, users whose calls and meetings were previously affected may need to end and restart those calls and meetings to see full recovery.
Scope of impact: Any Microsoft Teams users in the Asia-Pacific region may have been impacted when attempting to create or join meetings or calls.
Start time: Friday, July 24, 2026, at 12:25 AM UTC
End time: Friday, July 24, 2026, at 1:27 AM UTC
Root cause: The incident was triggered during the rollback of a Cosmos DB configuration designed to help limit the impact of failures and prevent wider service disruptions in one of the Teams services. As part of a precautionary investigation into a potential issue with this configuration, the feature was disabled in the APAC region. During the rollback, a subset of data partitions experienced a temporary service inconsistency for approximately 23 minutes, which resulted in intermittent request failures.
As dependent services and client applications attempted to recover from these failures, request volumes increased significantly and created an unexpected surge in traffic across several platform services. The elevated traffic levels placed substantial pressure on service infrastructure, leading to broader service degradation and impacting some calling and meeting scenarios.
The issue gradually self-resolved as platform scaling and traffic-management mechanisms automatically adjusted to absorb the increased demand. While service was restored without additional customer action, there are follow-up repair items to further strengthen resilience and reduce the likelihood of similar incidents in the future.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Review 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 Jul 23 21:59:17 2026 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings or calls
User impact: Users may be unable to join or create Microsoft Teams meetings or calls.
More info: According to our initial impact analysis, the following scenarios are among those most impacted:
-Transcriptions
-1:1 Calling
-Group calling
-Meeting join
-Meeting scheduling and creation
-Public switched telephone network (PSTN) calls
Current status: Our telemetry affirms that the impacted scenarios are nearly recovered. In parallel, we're recursively reviewing the health of the overall service environment, including dependent networking components, to better understand the cause and determine whether any mitigation actions are required to ensure the service remains healthy and available to users. In the interim, users' calls and meetings which were previously affected may need to be ended and restarted to see recovery.
Scope of impact: Any Microsoft Teams users in the Asia-Pacific region may be impacted when attempting to create or join meetings or calls. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:25 AM UTC
Next update by: Friday, July 24, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Jul 23 21:39:49 2026 |
|---|
| Description: | While we're observing recovery across a majority of affected scenarios, we're closely analyzing the service telemetry to isolate the source of the issue and ensure withstanding recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jul 23 21:26:59 2026 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings or calls
User impact: Users may be unable to join or create Microsoft Teams meetings or calls.
More info: According to our initial impact analysis, the following scenarios are among those most impacted:
-Transcriptions
-1:1 Calling
-Group calling
-Meeting join
-Meeting scheduling and creation
-Public switched telephone network (PSTN) calls
Current status: We're investigating a potential networking issue which we suspect is associated with the impact, and we're working to identify the most expeditious mitigation approach.
Scope of impact: Any Microsoft Teams users may be impacted when attempting to create or join meetings or calls.
Next update by: Friday, July 24, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Jul 23 21:02:55 2026 |
|---|
| Description: | Title: We're investigating a potential issue with Microsoft Teams
User impact: Users are reporting issues joining Microsoft Teams meetings.
Current status: We're investigating a potential issue which is preventing users from joining Microsoft Teams meetings and/or is causing disconnections, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1465677 - Users can't manage scheduled prompts in Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 1 13:17:25 2026 |
|---|
| End Time: | Wed Sep 2 21:03:57 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 2 21:05:18 2026 |
|---|
| Root Cause: | A recent service change designed to improve the management operations for scheduled prompts was preventing the management window from being displayed and was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 21:05:14 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users couldn't manage scheduled prompts in Copilot.
More info: When users attempted to schedule a prompt in Copilot, they received an error message that stated, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt was scheduled as expected. When the user then attempted to manage the scheduled prompt, they received the same error and were unable to manage it.
Final status: The rollback of the offending service change is complete and we’ve determined from service telemetry that this issue is resolved.
Scope of impact: Your organization was impacted by this event, and any user attempting to manage scheduled prompts in Copilot was affected.
Start time: Thursday, August 20, 2026, at 7:30 PM UTC
End time: Wednesday, September 2, 2026, at 10:50 AM UTC
Root cause: A recent service change designed to improve the management operations for scheduled prompts was preventing the management window from being displayed and was causing impact.
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 Sep 2 16:55:31 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: The rollback of the offending service change has completed for a majority of the affected environment. At this time, most affected users should be able to manage scheduled prompts in Copilot as expected. We'll aim to provide a timeline for the rollback to complete for the remaining affected users by our next scheduled communications update.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 7:30 PM UTC
Root cause: A recent service change designed to improve the management operations for scheduled prompts is preventing the management window from being displayed and is causing impact.
Next update by: Thursday, September 3, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 18:02:15 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: We've identified the most efficient way to remediate the impact of the previously identified update. We're working to implement a rollback of the recent change and anticipate having an update to the timeframe for that action at our next communication time.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 7:30 PM UTC
Root cause: A recent service change designed to improve the management operations for scheduled prompts is preventing the management window from being displayed and is causing impact.
Next update by: Wednesday, September 2, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 15:01:59 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: We've identified a recent service change designed to improve the management operations for scheduled prompts, which is preventing the management window from being displayed and is causing impact. We're determining the most efficient method to reverse this change and remediate the impact.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Root cause: A recent service change designed to improve the management operations for scheduled prompts is preventing the management window from being displayed and is causing impact.
Next update by: Tuesday, September 1, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 14:31:35 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: We're reviewing our service side logs to identify any failures or abnormalities that may help us narrow down the reason users are seeing the error page, so that we can determine the most effective strategy to remediate the impact.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Next update by: Tuesday, September 1, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 13:34:03 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: We're reviewing the screenshots provided by a subset of affected users to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Next update by: Tuesday, September 1, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 13:22:59 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1466215 - Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 1 18:00:00 2026 |
|---|
| End Time: | Wed Sep 2 16:30:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 2 17:57:46 2026 |
|---|
| Root Cause: | A portion of the Microsoft Defender for Office 365 infrastructure managing chat submissions was operating below acceptable performance thresholds, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 17:21:42 2026 |
|---|
| Description: | Title: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
User impact: Admins saw delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365.
More info: This event specifically impacted admins with V5 or V3 licenses.
Final status: Further review confirmed that the Microsoft Defender for Office 365 infrastructure managing chat submissions was operating below acceptable performance thresholds, resulting in impact. We've restarted the affected infrastructure, and confirmed through monitoring service health telemetry that grading functionality has been restored for email message and Microsoft Teams chat submissions. While we were able to reprocess a majority of requests that failed during the impact period, affected admins may need to resubmit some submissions if they're still seeing that grading didn't complete.
Scope of impact: Your organization was affected by this event, and any admin with V5 or V3 licenses receiving grades for email message or Microsoft Teams chat submissions in Microsoft Defender for Office 365 was impacted.
Start time: Tuesday, September 1, 2026, at 10:00 PM UTC
End time: Wednesday, September 2, 2026, at 8:30 PM UTC
Root cause: A portion of the Microsoft Defender for Office 365 infrastructure managing chat submissions was operating below acceptable performance thresholds, resulting in impact.
Next steps:
- We've reviewing the impacted Microsoft Defender for Office 365 infrastructure to determine what caused it to operate below acceptable performance thresholds and fail to handle traffic as expected, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 2 16:24:30 2026 |
|---|
| Description: | Title: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
User impact: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365.
More info: This event specifically impacts admins with V5 or V3 licenses.
Current status: We're continuing to restart the remaining affected infrastructure which is taking longer than initially anticipated. We're also preparing to reprocess the affected email messages and Microsoft Teams chats to fully remediate the issue.
Scope of impact: Your organization is affected by this event, and any admin with V5 or V3 licenses receiving grades for email message or Microsoft Teams chat submissions in Microsoft Defender for Office 365 is impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 1, 2026, at 10:00 PM UTC
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 14:17:56 2026 |
|---|
| Description: | Title: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
User impact: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365.
More info: This event specifically impacts admins with V5 or V3 licenses.
Current status: We're reviewing service logs to determine the underlying cause of impact. As part of our investigation, we restarted a portion of the Microsoft Defender for Office 365 infrastructure responsible for processing submission grading and observed a return to expected processing performance within that portion of the service. We're now restarting the remaining affected infrastructure to determine whether this action fully restores processing performance. We're monitoring service behavior and will provide additional information, including an expected completion timeline for this remediation activity, in our next update.
Scope of impact: Your organization is affected by this event, and any admin with V5 or V3 licenses receiving grades for email message or Microsoft Teams chat submissions in Microsoft Defender for Office 365 is impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 1, 2026, at 10:00 PM UTC
Next update by: Wednesday, September 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 14:01:08 2026 |
|---|
| Description: | Title: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
User impact: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365.
Current status: We're investigating a potential issue with Microsoft Defender for Office 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1461217 - Guest users were unable to access SharePoint Online sites connected to Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Aug 20 03:30:00 2026 |
|---|
| End Time: | Tue Aug 25 08:47:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Sep 2 14:30:25 2026 |
|---|
| Root Cause: | A change was made to significantly reduce request latency across almost all SPO requests by optimizing how the Dynamic Claims system retrieves and caches information through asynchronous tasks. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 14:27:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Aug 28 08:15:49 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Aug 26 05:14:27 2026 |
|---|
| Description: | Title: Guest users were unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users were unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users were redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins could have manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Final status: We've completed a period of monitoring service telemetry, and we've observed the restoration of service availability to normal levels. Additionally, during this time, we've received multiple reports from previously affected customers that they're experiencing relief from impact, and as such, we've determined this incident is resolved.
Scope of impact: This issue could have impacted any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Start time: Thursday, August 20, 2026, at 7:30 AM UTC
End time: Tuesday, August 25, 2026, at 12:47 PM UTC
Root cause: A change was made to significantly reduce request latency across almost all SPO requests by optimizing how the Dynamic Claims system retrieves and caches information through asynchronous tasks.
There was a latent bug within the initial Dynamic Claims flow where the service checks if the organization allows guest users for M365 group memberships. The pre-check did not force App-only credential requests to MS Graph and instead relied on the absence of user context in the thread to make the call app-only. This worked previously because the user context was not correctly propagated. However, in the new asynchronous tasks, the user context was correctly propagated, and this resulted in the failure to obtain the relevant token due to the service classifying the request as App+user. In this scenario, the service logic failed silently and put an empty value (i.e. the user is not a member of any M365 group) into the Dynamic Claims cache. This resulted in Dynamic Claims refresh call to fail for guest users and then being rejected from accessing the resources.
The issue was not detected by our monitoring systems in our early deployment rings (Microsoft’s internal organization etc.), as traffic for guest users is a small fraction of the overall dynamic traffic in these environments and therefore monitoring alerting thresholds were not met.
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 Aug 26 01:45:51 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We're continuing to engage in extended monitoring while we work with reporting organizations to confirm that the issue is fully resolved. If your organization has reported this problem, we request that you follow-up with the support case owner so we can confirm that the impact has been remediated.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Start time: Thursday, August 20, 2026, at 7:30 AM UTC
Root cause: A recently deployed change interacted with dynamic claims process, causing impact.
Next update by: Wednesday, August 26, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 21:47:35 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We've received some feedback indicating the impact is now resolved after we reverted the change. We're conducting persistent monitoring of the affected environment to ensure customers who previously reported the issue are seeing withstanding recovery.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Start time: Thursday, August 20, 2026, at 7:30 AM UTC
Root cause: A recently deployed change interacted with dynamic claims process, causing impact.
Next update by: Wednesday, August 26, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 09:29:59 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We're continuing to contact organizations who previously reported the issue, to confirm that the impact has been resolved after reverting the change.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Start time: Thursday, August 20, 2026, at 7:30 AM UTC
Next update by: Wednesday, August 26, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Aug 25 08:53:54 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We've identified a recently deployed change which interacted with dynamic claims process and out of an abundance of caution, we've reverted this change. We're contacting impacted organizations to confirm that this rollback has resolved the issue.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 08:17:07 2026 |
|---|
| Description: | We're reviewing forward synchronization protocols and other internal services to understand why the dynamic permission claims for guest users are not replicating as expected.
Next update by: Tuesday, August 25, 2026, at 1:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 25 07:28:21 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We're continuing our analysis of the network trace logs to help isolate why permissions that should grant access are not being correctly applied or recognized. This analysis will help us identify the underlying cause of the access issues and determine the appropriate remediation steps.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Aug 25 05:27:27 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We're continuing to analyze the collected network traces to determine why permissions that should grant access aren't being correctly applied or recognized. Additionally, we've identified a potential workaround that has been successful for a subset of impacted users, where affected guest users are manually added directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 03:34:15 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Current status: We've analyzed the collected network traces and determined that some guest users are being treated as though they don't have the permissions required to access impacted SharePoint sites, resulting in Access Denied responses. We're continuing to investigate why permissions that should grant access aren't being correctly applied or recognized. We're reaching out to a subset of affected users to collect additional traces that capture the process of adding guest users and assigning permissions to further our investigation.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 02:32:22 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: The issue is specifically happening when permissions to the SharePoint Online sites are granted through Microsoft 365 groups.
Current status: We've collected additional network traces and are investigating why the guest users are seeing access denied errors. We suspect that there's an issue happening with permissions, and we're analyzing logs to confirm any potential issue that could be causing the impact.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 00:21:10 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: The issue is specifically happening when permissions to the SharePoint Online sites are granted through Microsoft 365 groups.
Current status: We're working to collect additional network traces from affected users for analysis. In addition, we're reviewing whether any recent service changes could be contributing to the impact.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Mon Aug 24 22:23:22 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: The issue is specifically happening when permissions to the SharePoint Online sites are granted through Microsoft 365 groups.
Current status: We're analyzing system logs to better understand the behavior with the guest users, which will help us to determine our next troubleshoot steps.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Mon Aug 24 22:02:08 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: The issue is specifically happening when permissions to the SharePoint Online sites are granted through Microsoft 365 groups.
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1461484 - Admins may see outdated/incomplete data in workspace settings of Power BI or Microsoft Fabric services
| Status: | serviceRestored |
|---|
| Start Time: | Sun Aug 2 00:12:00 2026 |
|---|
| End Time: | Wed Sep 2 10:27:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI and Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 2 11:40:41 2026 |
|---|
| Root Cause: | A code regression was causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 11:32:50 2026 |
|---|
| Description: | Title: Admins may see outdated/incomplete data in workspace settings of Power BI or Microsoft Fabric services
User impact: Admins may have seen outdated/incomplete data in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may have seen outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continued to apply successfully; however, updated values may have not been reflected in workspace settings after changes were saved or the page was refreshed.
Final status: We've addressed the issue blocking our deployment pipeline, initiated and completed the deployment of our fix to all affected environments, and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Impact was specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service.
Start time: Sunday, August 2, 2026, at 4:12 AM UTC
End time: Wednesday, September 2, 2026, at 2:27 PM UTC
Root cause: A code regression was causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next steps:
- We're reviewing the offending code regression to understand how it was introduced into the service, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 13:04:17 2026 |
|---|
| Description: | Title: Some workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: We're continuing our efforts to unblock our deployment pipeline and will provide a release timeline once it's resolved.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Start time: Sunday, August 2, 2026, at 4:12 AM UTC
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Wednesday, September 2, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 11:45:37 2026 |
|---|
| Description: | Title: Some workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: Due to an unrelated issue impacting our deployment pipelines, deployment has been temporarily delayed. We're evaluating the current timeline to deployment, and we aim to share this as soon as possible.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Start time: Sunday, August 2, 2026, at 4:12 AM UTC
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Tuesday, September 1, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Aug 27 13:12:47 2026 |
|---|
| Description: | Title: Some workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: Our validation of the fix has completed successfully and we're scheduling a broad release to remediate impact. We expect to have a complete mitigation timeline by the next scheduled update.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Monday, August 31, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Aug 26 12:16:03 2026 |
|---|
| Description: | Title: Some workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: We're continuing to test and validate the effectiveness of our code fix within our internal testing environment prior to initiating a wider deployment. We aim to provide a timeline to remediation as soon as possible.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Thursday, August 27, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 11:14:41 2026 |
|---|
| Description: | Title: Some Workspace Admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace Admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace Admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: After further analysis of service monitoring telemetry, we’ve isolated that impact is caused by a code regression causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin. This causes the authorization check to be rejected, resulting in impact. We’re validating and testing a code fix to correct this regression, and we aim to provide a timeline to remediation as soon as possible.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Start time: Sunday, August 2, 2026, at 4:12 AM UTC
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Wednesday, August 26, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 09:21:03 2026 |
|---|
| Description: | Title: Some Workspace Admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace Admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace Admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
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 admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service.
Next update by: Tuesday, August 25, 2026, at 3:30 PM UTC
|
|---|
|
MO1465962 - Some users may have been unable to open Google search links from email and Microsoft Teams messages
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 1 22:53:00 2026 |
|---|
| End Time: | Wed Sep 2 07:24:26 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 2 07:25:56 2026 |
|---|
| Root Cause: | An inaccurate security classification caused legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 07:25:52 2026 |
|---|
| Description: | Title: Some users may have been unable to open Google search links from email and Microsoft Teams messages
User impact: Users may have been unable to open Google search links from email and Microsoft Teams messages.
More info: Microsoft Defender for Office 365 Safe Links may have blocked the opening of Google search links (URLs), identifying them as malicious. In addition, admins may have received related alerts and incidents in the Microsoft Defender portal and Microsoft Sentinel as a result of these detections. Affected users received the following message when attempting to open the Google search links:
"Opening this website might not be safe"
Copying the hyperlink and pasting it directly into a browser didn’t bypass the warning.
Final status: We've received confirmation that the issue has been successfully resolved. However, some users may continue to experience impact for a limited time while the mitigation propagates through the service infrastructure.
Scope of impact: Some users attempting to open Google search links from email and Microsoft Teams messages may have been impacted.
Start time: Wednesday, September 2, 2026, at 2:53 AM UTC
End time: Wednesday, September 2, 2026, at 10:17 AM UTC
Root cause: An inaccurate security classification caused legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links.
Next steps:
- We're reviewing our URL reputation classification processes to help prevent similar false-positives in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 2 06:37:02 2026 |
|---|
| Description: | Title: Some users may be unable to open Google search links from email and Microsoft Teams messages
User impact: Users may be unable to open Google search links from email and Microsoft Teams messages.
More info: Microsoft Defender for Office 365 Safe Links may block the opening of Google search links (URLs), identifying them as malicious. In addition, admins may receive related alerts and incidents in the Microsoft Defender portal and Microsoft Sentinel as a result of these detections. Affected users receive the following message when attempting to open the Google search links:
"Opening this website might not be safe"
Copying the hyperlink and pasting it directly into a browser doesn't bypass the warning.
Current status: We've corrected the inaccurate security classification, and internal testing indicates that this has successfully resolved the issue. However, some users may continue to experience impact for a limited time while the mitigation propagates through the service infrastructure. We're reaching out to a number of affected users to validate that remediation is complete.
Scope of impact: Some users attempting to open Google search links from email and Microsoft Teams messages may be impacted.
Start time: Wednesday, September 2, 2026, at 2:53 AM UTC
Root cause: An inaccurate security classification is causing legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links.
Next update by: Wednesday, September 2, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 05:58:38 2026 |
|---|
| Description: | Title: Some users may be unable to open Google search links from email and Microsoft Teams messages
User impact: Users may be unable to open Google search links from email and Microsoft Teams messages.
More info: Microsoft Defender for Office 365 Safe Links may block the opening of Google search links (URLs), identifying them as malicious. In addition, admins may receive related alerts and incidents in the Microsoft Defender portal and Microsoft Sentinel as a result of these detections. Affected users receive the following message when attempting to open the Google search links:
"Opening this website might not be safe"
Copying the hyperlink and pasting it directly into a browser doesn't bypass the warning.
Current status: We've determined that an inaccurate security classification is causing legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links. We're working to correct the misclassification to remediate impact.
Scope of impact: Some users attempting to open Google search links from email and Microsoft Teams messages may be impacted.
Start time: Wednesday, September 2, 2026, at 2:53 AM UTC
Root cause: An inaccurate security classification is causing legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links.
Next update by: Wednesday, September 2, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Sep 2 04:25:05 2026 |
|---|
| Description: | Title: Some users may be unable to open Google search links from email and Microsoft Teams messages
User impact: Users may be unable to open Google search links from email and Microsoft Teams messages.
More info: Microsoft Defender for Office 365 Safe Links may block the opening of Google search links (URLs), identifying them as malicious. In addition, admins may receive related alerts and incidents in the Microsoft Defender portal and Microsoft Sentinel as a result of these detections. Affected users receive the following message when attempting to open the Google search links:
"Opening this website might not be safe"
Copying the hyperlink and pasting it directly into a browser doesn't bypass the warning.
Current status: We're reviewing affected alert IDs for a subset of impacted users, while also analyzing blocked links and their source, to determine why legitimate Google search URLs are being classified as malicious.
Scope of impact: Some users attempting to open Google search links from email and Microsoft Teams messages may be impacted.
Next update by: Wednesday, September 2, 2026, at 10:30 AM UTC
|
|---|
|
IT1464731 - Some admins may be unable to view device information in the Microsoft Intune admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 31 05:09:53 2026 |
|---|
| End Time: | Tue Sep 1 22:04:12 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 1 22:16:06 2026 |
|---|
| Root Cause: | A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 22:16:03 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may have been unable to view device information in the Microsoft Intune admin center.
Final status: We've confirmed that the backlogged data has been processed and validated by internal monitoring that the issue is resolved.
Scope of impact: Impact was specific to some admins that attempted to view device inventory and reporting information in the Microsoft Intune admin center.
Start time: Saturday, August 29, 2026, at 1:41 AM UTC
End time: Wednesday, September 2, 2026, at 12:25 AM UTC
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next steps:
- We're reviewing the portion of reporting information to isolate what caused it to reference an outdated data source, and to prevent similar impact scenarios from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 20:39:30 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've identified that an increase of backlogged data is preventing the issue from being fully resolved. We're closely monitoring as it's being processed to ensure the impact is remediated for all impacted admins.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Wednesday, September 2, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 17:24:39 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We estimate that the required post-deployment processes will be completed and impact will be remediated by our next scheduled communication update.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Wednesday, September 2, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 12:26:55 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: After our completed fix deployment, our service telemetry is reporting that a majority of the impact has been resolved. We're completing our post-deployment adjustments and validations and are expecting an updated timeline for the impact being remediating to be available by our next scheduled communication update.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Tuesday, September 1, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 05:11:54 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've confirmed that the fix has reached approximately 90% completion. We're completing the final remediation steps and monitoring progress as the deployment nears completion.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Tuesday, September 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 02:26:29 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We're monitoring the fix deployment as it nears completion. We expect it will fully complete by our next scheduled update, at which time we'll conduct final validation checks within our service health telemetry to ensure impact is fully remediated.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Tuesday, September 1, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Mon Aug 31 14:14:58 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: The fix is progressing as expected, and we expect it to complete and remediate impact by the next scheduled update.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Tuesday, September 1, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 13:29:32 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We're initiating a staged roll out of the fix and will provide a remediation timeline once available.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Monday, August 31, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 11:22:12 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've completed the internal validation of a fix and are working to apply the mitigation more broadly.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Monday, August 31, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 09:18:37 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've identified that the reporting infrastructure was referencing outdated data, causing device information to not display as expected in affected reports. Administrators with limited administrative privileges may not see expected devices, while some data may be missing for global administrators. We're validating a fix through manual mitigation efforts before deploying it to the impacted environment.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Monday, August 31, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 06:47:51 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've identified that device data remains available within the service; however, some device information isn't being displayed as expected in reporting views after devices check in. We're continuing our investigation by analyzing reporting telemetry and data processing behavior to determine why certain device attributes aren't being populated correctly and to develop a remediation plan.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Next update by: Monday, August 31, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 05:52:07 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've identified a reporting issue affecting some admins in the Asia Pacific and Australia regions. Affected admins may not see expected device information in device inventory lists and dashboards. We're reviewing telemetry and service data from the affected environments to determine the source of impact.
Scope of impact: Impact is specific to some admins in the Asia Pacific and Australia regions attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Next update by: Monday, August 31, 2026, at 11:30 AM UTC
|
|---|
|
TM1461801 - Users may be unable to use multiple Microsoft Teams features
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Aug 25 21:00:00 2026 |
|---|
| End Time: | Tue Aug 25 22:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Sep 1 19:55:58 2026 |
|---|
| Root Cause: | We determined that maintenance related work in the region was inadvertently causing impact to service health. We will provide more information regarding the root cause within our Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 19:55:58 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Aug 27 19:38:56 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Aug 25 22:23:15 2026 |
|---|
| Description: | Title: Users may be unable to use multiple Microsoft Teams features
User impact: Users may have been unable to use multiple Microsoft Teams features.
More info: Based on our telemetry, multiple Microsoft Teams features were affected such as:
- Live Events
- 1:1 Calling
- PSTN Calling
- Joining Meetings
- Creating Meetings
- Meeting General Functionality
- Town Hall Functionality
Final status: After a period of extended monitoring, we have confirmed that the issue is resolved.
Scope of impact: This issue could have affected any user located in Asia-Pacific.
Start time: Wednesday, August 26, 2026, at 1:00 AM UTC
End time: Wednesday, August 26, 2026, at 2:00 AM UTC
Root cause: We determined that maintenance related work in the region was inadvertently causing impact to service health. We will provide more information regarding the root cause within our Post-Incident Report.
Next steps: We're actively reviewing the maintenance work that resulted in this issue to identify the underlying cause and how to prevent it from occurring again.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue Aug 25 21:56:42 2026 |
|---|
| Description: | Our monitoring indicates that the issue is largely mitigated. We are continuing to monitor the service for the next 15 to 30 minutes to ensure there is no reoccurrence of this issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 25 21:41:45 2026 |
|---|
| Description: | Title: Users may be unable to use multiple Microsoft Teams features
User impact: Users may be unable to use multiple Microsoft Teams features.
More info: Based on our telemetry, multiple Microsoft Teams features are affected:
- Live Events
- 1:1 Calling
- PSTN Calling
- Joining Meetings
- Creating Meetings
- Meeting General Functionality
- Town Hall Functionality
Current status: We have determined that maintenance related work was being conducted on the infrastructure based in Asia-Pacific. As an unintended result of this maintenance work, service health was impacted. We have paused our maintenance work and our telemetry indicates that the issue is no longer occurring. We're continuing to monitor service health and work with reporting users that the issue is no longer occurring.
Scope of impact: This issue could affect any user located in Asia-Pacific. This section is subject to change as our investigation continues.
Start time: Wednesday, August 26, 2026, at 1:00 AM UTC
Preliminary root cause: Maintenance related work in the region is inadvertently causing impact to service health. We will provide more information regarding the root cause as soon as possible.
Next update by: Wednesday, August 26, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Aug 25 21:26:48 2026 |
|---|
| Description: | Title: Users may be unable to join and create Microsoft Teams meetings
User impact: Users may be unable to join and create 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.
|
|---|
|
TM1451939 - Users' locations may not be accurate during iOS Microsoft Teams emergency calls
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 2 11:09:00 2026 |
|---|
| End Time: | Tue Sep 1 14:07:59 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 1 14:17:34 2026 |
|---|
| Root Cause: | A change within iOS API infrastructure resulted in inaccurate user location data being reported during iOS emergency calls.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 14:17:31 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not have been accurate during iOS Microsoft Teams emergency calls.
More info: Affected users were still able to make iOS emergency calls, but their location might have been inaccurate to the responder. This was specific to users on iOS version 26 and newer.
Final status: After verifying with affected users that locations were accurate during iOS Microsoft Teams emergency calls, we've confirmed that the impact has been remediated.
Scope of impact: Impact was specific to users on iOS 26 or newer who made emergency calls using the Microsoft Teams application.
Start time: Thursday, July 2, 2026, at 3:09 PM UTC
End time: Monday, August 31, 2026, at 6:00 PM UTC
Root cause: A change within iOS API infrastructure resulted in inaccurate user location data being reported during iOS emergency calls.
Next steps:
- We're further analyzing the offending change within iOS API infrastructure to help us improve our pre-deployment testing and validation processes and to help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 08:08:39 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We've confirmed the new version deployment has completed successfully, and users should see their Microsoft Teams app update automatically.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues. However, users may also be able to manually download the latest version through the App Store. We're reaching out to your organization's representatives to ensure that impact is resolved.
Root cause: A change within iOS API infrastructure is resulting in inaccurate user location data being reported during iOS emergency calls.
Next update by: Tuesday, September 1, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 23:44:23 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: The deployment of the fix in the latest version of the Microsoft Teams app is in progress. We estimate that the deployment will complete by August 31, 2026. Users with automatic updates enabled in the App Store should see their Microsoft Teams app automatically updated over the course of the deployment. Users may also be able to manually download the latest version through the App Store. We'll continue monitoring the deployment progress to ensure that the impact is remediated.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: A change within iOS API infrastructure is resulting in inaccurate user location data being reported during iOS emergency calls.
Next update by: Tuesday, September 1, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 15:13:07 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We've completed the additional steps required to validate our remediation and have begun the deployment process. We’re aiming to provide more details on the timeline until resolution by our next scheduled communication update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: A change within iOS API infrastructure is resulting in inaccurate user location data being reported during iOS emergency calls.
Next update by: Tuesday, August 25, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Aug 24 07:26:58 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing validation of the fix before deployment can begin. This process is taking longer than anticipated due to additional validation steps. We anticipate deployment will begin before our next scheduled update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: A change within iOS API infrastructure is resulting in inaccurate user location data being reported during iOS emergency calls.
Next update by: Monday, August 24, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Aug 21 07:24:30 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: Our previous update with regards to the fix was incorrect. We're preparing the fix to start deployment, which should start by our next scheduled update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure have resulted in inaccurate user location data during iOS emergency calls.
Next update by: Monday, August 24, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Thu Aug 20 03:50:50 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: The fix deployment is progressing and we expect this to be complete by our next scheduled update. It may take an additional 24 hours for the fix to propagate once its successfully deployed.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure have resulted in inaccurate user location data during iOS emergency calls.
Next update by: Friday, August 21, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Wed Aug 19 14:31:56 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing to monitor as the fix deployment progresses and will provide a complete remediation timeline once available.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure have resulted in inaccurate user location data during iOS emergency calls.
Next update by: Thursday, August 20, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Aug 19 09:49:53 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We've validated the fix and have begun deploying it to the affected infrastructure. We're monitoring the rollout as it continues to propagate across the environment, and are validating that the deployment is fully mitigating impact.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Wednesday, August 19, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 10:28:13 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're progressing with our efforts to validate a suitable fix in our test environment, although this is taking longer than initially anticipated. We're carrying out tests to ensure that the fix doesn't present any further issues and further clarify confirmation of the root cause.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Wednesday, August 19, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Aug 12 13:42:02 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing the validation process for our fix, and we'll aim to provide a timeline for it to complete by our next scheduled communications update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Thursday, August 13, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue Aug 11 14:55:33 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: The development of the fix is taking longer than initially expected. We'll provide an updated timeline once one is available.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Wednesday, August 12, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 08:49:31 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing to develop a fix in our internal environment to remediate impact and restore location data functionality. We expect this to be ready to be deployed by our next scheduled update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Tuesday, August 11, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 10 08:52:01 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We've identified that changes to iOS API infrastructure has inadvertently resulted in user location data to become inaccurate during iOS emergency calls. We're developing a fix in our internal environment to remediate impact and restore location data functionality.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application.
Root cause: Changes to iOS API infrastructure has inadvertently resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Tuesday, August 11, 2026, at 1:00 PM UTC
|
|---|
|
|
