Microsoft's Incident Report for PennO365
Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within
the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh
this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this
list. Additionally you can check Microsoft's
status page for current service status messages.
The last extract was taken on Sat Oct 17 09:45:08 2026.
SP1503038 - Users may be unable to view or modify custom forms in SharePoint Online
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sun Oct 11 21:00:00 2026 |
|---|
| End Time: | Wed Oct 14 12:00:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Oct 16 19:40:59 2026 |
|---|
| Root Cause: | A recent API change to the SharePoint Online infrastructure introduced an incompatibility in how requests from custom forms are processed, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 16 19:40:59 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 14 13:52:12 2026 |
|---|
| Description: | Title: Users may be unable to view or modify custom forms in SharePoint Online
User impact: Users may have been unable to view or modify custom forms in SharePoint Online.
More info: Affected users may have encountered multiple potential scenarios with Nintex and SharePoint Framework (SPFx) Customizers forms, including:
- Blank pages
- Null target exceptions
Final status: We've completed deployment of the fix to all affected environments, and we've confirmed with impacted organizations that the issue is no longer occurring.
Scope of impact: This issue may have impacted any user attempting to view or modify Nintex or SPFx Customizers forms in SharePoint Online.
Start time: Monday, October 12, 2026, at 1:00 AM UTC
End time: Wednesday, October 14, 2026, at 5:52 PM UTC
Root cause: A recent API change to the SharePoint Online infrastructure introduced an incompatibility in how requests from custom forms are processed, resulting in impact.
Next steps:
- We're reviewing our testing and validation procedures to help prevent 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: | Tue Oct 13 12:27:40 2026 |
|---|
| Description: | Title: Users may be unable to view or modify custom forms in SharePoint Online
User impact: Users may be unable to view or modify custom forms in SharePoint Online.
More info: Affected users may encounter multiple potential scenarios with Nintex and SharePoint Framework (SPFx) Customizers forms, including:
- Blank pages
- Null target exceptions
Current status: We're continuing to deploy our fix to the affected environments and anticipate that deployment will be completed within 48 hours. We'll provide the latest deployment progress and updated completion timeline in our next update.
Scope of impact: Impact may be specific to any user attempting to view or modify Nintex or SPFx Customizers forms in SharePoint Online.
Start time: Monday, October 12, 2026, at 1:00 AM UTC
Root cause: A recent API change to the SharePoint Online infrastructure introduced an incompatibility in how requests from custom forms are processed, resulting in impact.
Next update by: Wednesday, October 14, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Oct 13 11:26:12 2026 |
|---|
| Description: | Title: Users may be unable to view or modify forms in SharePoint Online
User impact: Users may be unable to view or modify forms in SharePoint Online.
More info: Affected users may encounter multiple potential scenarios with Nintex and SharePoint Framework (SPFx) Customizers forms, including:
- Blank pages
- Null target exceptions
Current status: We've confirmed a recent API change as the source of the impact and have prevented it from reaching any further environments. We're continuing to deploy our fix to the affected environments to remediate the impact.
Scope of impact: Impact may be specific to any user attempting to view or modify Nintex or SPFx Customizers forms in SharePoint Online.
Start time: Monday, October 12, 2026, at 1:00 AM UTC
Root cause: A recent API change to the SharePoint Online infrastructure introduced an incompatibility in how requests from custom forms are processed, resulting in impact.
Next update by: Tuesday, October 13, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Oct 12 20:22:33 2026 |
|---|
| Description: | Title: Users may be unable to view or modify forms in SharePoint Online
User impact: Users may be unable to view or modify forms in SharePoint Online.
More info: Affected users may encounter multiple potential scenarios with Nintex and SharePoint Framework (SPFx) Customizers forms, including:
- Blank pages
- Null target exceptions
Current status: We’ve isolated a recent API change as the suspected source of the impact. We’ve initiated the process of deploying a fix to confirm our findings and potentially remediate the impact.
Scope of impact: Impact may be specific to any user attempting to view or modify Nintex or SPFx Customizers forms in SharePoint Online.
Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Oct 12 16:58:27 2026 |
|---|
| Description: | Title: Users can't view or modify Nintex forms in SharePoint Online and receive an error
User impact: Users can't view or modify Nintex forms in SharePoint Online and receive an error.
More info: Affected users are encountering multiple potential scenarios, including:
- Blank pages
- 200 HTTP errors
- Null target exceptions
Current status: We're continuing our analysis of the HAR captures to determine the cause of impact.
Scope of impact: Your organization is impacted by this event, and impact is limited to users viewing or modifying Nintex forms in SharePoint Online.
Next update by: Tuesday, October 13, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Oct 12 15:11:30 2026 |
|---|
| Description: | Title: Users can't view or modify Nintex forms in SharePoint Online and receive an error
User impact: Users can't view or modify Nintex forms in SharePoint Online and receive an error.
More info: Affected users are encountering multiple potential scenarios, including:
- Blank pages
- 200 HTTP errors
- Null target exceptions
Current status: We're expanding our investigation to include HTTP Archive format (HAR) browser captures of the issue in progress to assist in isolating the underlying cause of impact and develop a remediation strategy.
Scope of impact: Your organization is impacted by this event, and impact is limited to users viewing or modifying Nintex forms in SharePoint Online.
Next update by: Monday, October 12, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Oct 12 14:27:32 2026 |
|---|
| Description: | Title: Users can't view or modify Nintex forms in SharePoint Online and receive an error
User impact: Users can't view or modify Nintex forms in SharePoint Online and receive an error.
More info: Affected users are encountering multiple potential scenarios, including:
- Blank pages
- 200 HTTP errors
- Null target exceptions
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 impact is limited to users viewing or modifying Nintex forms in SharePoint Online.
Next update by: Monday, October 12, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Oct 12 14:07:09 2026 |
|---|
| Description: | Title: Users can't view or modify Nintex forms in SharePoint Online and receive an error
User impact: Users can't view or modify Nintex forms in SharePoint Online and receive an error.
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.
|
|---|
|
CW1507178 - Some users were unable to see model selection options in Microsoft 365 Copilot chat
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Oct 13 23:34:00 2026 |
|---|
| End Time: | Wed Oct 14 05:30:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Oct 16 17:33:10 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 16 17:33:10 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 14 06:19:33 2026 |
|---|
| Description: | Title: Some users were unable to see model selection options in Microsoft 365 Copilot chat
User impact: Users were unable to see model selection options in Microsoft 365 Copilot chat.
More info: Affected users were unable to see GPT, Claude, or other available models within the model selection options in Copilot chat.
Final status: We’ve verified through service telemetry and previously impacted users that the issue is now resolved.
Scope of impact: Some users attempting to access GPT, Claude, or other model selection options in Copilot chat were impacted.
Start time: Wednesday, October 14, 2026, at 3:34 AM UTC
End time: Wednesday, October 14, 2026, at 9:30 AM UTC
Preliminary root cause: A recent change resulted in the component responsible for producing the model selection options in Copilot chat to not function correctly.
Next steps:
- We're analyzing service telemetry on the affected component to help prevent this problem from happening again.
We’ll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Oct 14 05:56:27 2026 |
|---|
| Description: | We've completed deploying the fix to the affected infrastructure, and we've verified in our internal environment that the model selection options have been restored within Copilot chat. We're now contacting affected customers directly to ensure the fix has produced the expected resolution.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Oct 14 05:20:46 2026 |
|---|
| Description: | Title: Some users may be unable to see model selection options in Microsoft 365 Copilot chat
User impact: Users may be unable to see model selection options in Microsoft 365 Copilot chat.
More info: Affected users may not see GPT, Claude, or other available models within the model selection options in Copilot chat.
Current status: We've identified a component responsible for producing the model selection options in Copilot chat was not functioning correctly. To mitigate impact, we've developed a fix which is currently being deployed to the affected infrastructure and we're monitoring this process closely to ensure it delivers the expected resolution.
Scope of impact: Some users attempting to access GPT, Claude, or other model selection options in Copilot chat may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, October 14, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Oct 14 04:13:33 2026 |
|---|
| Description: | Title: Some users may be unable to see model selection options in Microsoft 365 Copilot chat
User impact: Users may be unable to see model selection options in Microsoft 365 Copilot chat.
More info: Affected users may not see GPT, Claude, or other available models within the model selection options in Copilot chat.
Current status: We’re reviewing service monitoring telemetry and support provided information to determine why model selection options aren’t appearing as expected, in order to develop a remediation plan.
Scope of impact: Some users attempting to access GPT, Claude, or other model selection options in Copilot chat may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, October 14, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Oct 14 03:07:25 2026 |
|---|
| Description: | Title: Some users are unable to see model selection options in Microsoft 365 Copilot chat
User impact: Users are unable to see model selection options in Copilot chat.
More info: Affected users may not see GPT, Claude, or other available models within the model selection options in Copilot chat.
Current status: We've received reports indicating an issue with model selection options in Copilot Chat. 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 access GPT, Claude, or other model selection options in Copilot chat are impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, October 14, 2026, at 9:00 AM UTC
|
|---|
|
TM1508612 - Some users may not receive meeting-started notifications on Android devices
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 13 19:03:00 2026 |
|---|
| End Time: | Fri Oct 16 03:35:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 16 16:49:06 2026 |
|---|
| Root Cause: | A recent notification service change intended to address an unrelated issue affected meeting-started notifications for Android users.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 16 16:36:09 2026 |
|---|
| Description: | Title: Some users may not receive meeting-started notifications on Android devices
User impact: Users may have not received meeting-started notifications on Android devices.
Final status: We've reverted the impacting service change, and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Some users expecting to receive meeting start notifications in Microsoft Teams on Android devices may have been impacted.
Start time: Tuesday, October 13, 2026, at 11:03 PM UTC
End time: Friday, October 16, 2026, at 7:35 AM UTC
Root cause: A recent notification service change intended to address an unrelated issue affected meeting-started notifications for Android users.
Next steps:
- We're reviewing the recent notification service change to understand why impact to meeting-started notifications 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 Oct 15 11:58:40 2026 |
|---|
| Description: | Title: Some users may not receive meeting-started notifications on Android devices
User impact: Users may not receive meeting-started notifications on Android devices.
Current status: Our reversion of the affecting change is ongoing, and initial review of our service health telemetry indicates errors associated with impact have decreased and successful notification delivery is increasing. We're continuing to monitor, and users will need to open the application in order to receive the fix.
Scope of impact: Some users expecting to receive meeting start notifications in Microsoft Teams on Android devices may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, October 13, 2026, at 11:03 PM UTC
Root cause: A recent notification service change intended to address an unrelated issue affected meeting-started notifications for Android users.
Next update by: Friday, October 16, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Oct 15 06:30:07 2026 |
|---|
| Description: | Title: Some users may not receive meeting-started notifications on Android devices
User impact: Users may not receive meeting-started notifications on Android devices.
Current status: We’ve identified that a recent change to the notification service, intended to address an unrelated issue, inadvertently caused meeting-started notifications to fail for Android users. We’re reverting the affected change to mitigate the impact and expect to provide completion timeline by our next schedule update.
Scope of impact: Some users expecting to receive meeting start notifications in Microsoft Teams on Android devices may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, October 13, 2026, at 11:03 PM UTC
Root cause: A recent notification service change intended to address an unrelated issue affected meeting-started notifications for Android users.
Next update by: Thursday, October 15, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Oct 15 04:39:48 2026 |
|---|
| Description: | Title: Some users may not receive meeting start notifications in Microsoft Teams on Android devices
User impact: Users may not receive meeting start notifications in Microsoft Teams on Android devices.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Some users expecting to receive meeting start notifications in Microsoft Teams on Android devices may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, October 15, 2026, at 10:30 AM UTC
|
|---|
|
MO1501829 - Admins may see stale data in the Copilot Health page in the Microsoft 365 admin center
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Sep 8 12:05:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 16 15:46:36 2026 |
|---|
| Root Cause: | An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
|
|---|
| Next Update: | Monday, October 19, 2026, at 10:30 AM UTC |
|---|
|
Details
| Time: | Fri Oct 16 15:46:36 2026 |
|---|
| Description: | Title: Admins may see stale data in the 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, monthly data in the Update channels, Microsoft 365 updates (Past 6 months view), Connected experiences status, and OneDrive status cards on the Copilot Health page may not reflect data after July 2026. The Today view in the Microsoft 365 updates card isn't affected.
Current status: We've validated our fix's efficacy in remediating the impact, and we're preparing to begin the deployment and restore the affected pipeline. We'll aim to provide a timeline for the deployment to begin by our next scheduled communications update.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
Next update by: Monday, October 19, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Oct 14 13:20:28 2026 |
|---|
| Description: | Title: Admins may see stale data in the 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, monthly data in the Update channels, Microsoft 365 updates (Past 6 months view), Connected experiences status, and OneDrive status cards on the Copilot Health page may not reflect data after July 2026. The Today view in the Microsoft 365 updates card isn't affected.
Current status: We're continuing our efforts to develop a fix to gather the missing data needed to restore our pipeline and remediate the impact. Once internal validations are complete, we'll provide a timeline for the deployment.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
Next update by: Friday, October 16, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Oct 13 13:57:12 2026 |
|---|
| Description: | Title: Admins may see stale data in the 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, monthly data in the Update channels, Microsoft 365 updates (Past 6 months view), Connected experiences status, and OneDrive status cards on the Copilot Health page may not reflect data after July 2026. The Today view in the Microsoft 365 updates card isn't affected.
Current status: We're developing a fix that will gather the missing data necessary to restore our pipeline and to remediate the impact. We'll provide a timeline for the deployment of our solution once internal validations have been completed.
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, October 14, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Oct 13 06:56:42 2026 |
|---|
| Description: | Title: Admins may see stale data in the 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, monthly data in the Update channels, Microsoft 365 updates (Past 6 months view), Connected experiences status, and OneDrive status cards on the Copilot Health page may not reflect data after July 2026. The Today view in the Microsoft 365 updates card isn't affected.
Current status: We’ve confirmed that the pipeline responsible for processing Copilot Health data is running. We're working to gather the missing data so we can rerun the pipeline and resolve the issue.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted.
Start time: Tuesday, September 8, 2026, at 4:05 PM UTC
Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
Next update by: Tuesday, October 13, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Oct 12 08:56:55 2026 |
|---|
| Description: | Title: Admins may see stale data in the 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, monthly data in the Update channels, Microsoft 365 updates (Past 6 months view), Connected experiences status, and OneDrive status cards on the Copilot Health page may not reflect data after July 2026. The Today view in the Microsoft 365 updates card isn't affected.
Current status: We've confirmed that impact associated with CP1482212 persists as the data was not processed as expected. We're validating that the data is present to be able to run the pipeline successfully and remediate impact completely.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may be impacted.
Start time: Tuesday, September 8, 2026, at 4:05 PM UTC
Root cause: An upstream process responsible for Copilot Health data was disabled, resulting in the impact.
Next update by: Tuesday, October 13, 2026, at 12:00 PM UTC
|
|---|
|
TM1492872 - Users may be unable to download webinar registration details from the Events app in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Fri Oct 9 14:56:09 2026 |
|---|
| End Time: | Fri Oct 16 15:24:22 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 16 15:34:20 2026 |
|---|
| Root Cause: | A recent service update introduced a regression that caused the registration report download option to become unavailable when the engagement reporting policy was disabled, despite the report being independent of this policy.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 16 15:34:17 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may have been unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacted users who had the AllowEngagementReport meeting policy set to Off, and they were unable to download webinar registration details in Microsoft Teams Events because the Download option didn’t appear.
Final status: We've verified with a subset of affected users that our actions have remediated the impact.
Scope of impact: Impact may have occurred for users whose assigned meeting policy had AllowEngagementReport set to Off, which prevented them from downloading webinar registration details from the Events app in Microsoft Teams.
Start time: Friday, October 9, 2026, at 4:10 PM UTC
End time: Friday, October 16, 2026, at 3:28 AM UTC
Root cause: A recent service update introduced a regression that caused the registration report download option to become unavailable when the engagement reporting policy was disabled, despite the report being independent of this policy.
Next steps:
- We're evaluating our service update protocols to ensure similar issues are identified and corrected ahead of implementation to prevent this from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Fri Oct 16 00:28:42 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option doesn’t appear.
Current status: We’ve completed deployment of the fix and are validating with affected users to confirm that the issue is resolved.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Friday, October 9, 2026, at 4:10 PM UTC
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Friday, October 16, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Oct 15 19:29:12 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option doesn’t appear.
Current status: We're still in the process of deploying our fix to the remaining affected environments and our projections now indicate it may complete by our next scheduled communication update.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Friday, October 9, 2026, at 4:10 PM UTC
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Friday, October 16, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Oct 15 14:01:28 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option doesn’t appear.
Current status: The deployment of our fix to the remaining affected environments is ongoing. We anticipate this will complete, remediating impact for all users, by our next scheduled communication update.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Friday, October 9, 2026, at 4:10 PM UTC
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Friday, October 16, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Oct 13 13:38:51 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option doesn’t appear.
Current status: After receiving reports that some affected users are still impacted by this issue, we've found that the fix hadn't completed deployment as expected. The deployment of our fix is still in progress, and we'll continue to monitor its progress to ensure it completes and resolves the issue for all users.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Thursday, October 15, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 11:49:58 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option does not appear.
Current status: We've reached out t a subset of affected users and are awaiting feedback to confirm that the fix we deployed remediates the impact as expected.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Friday, October 9, 2026, at 4:10 PM UTC
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Tuesday, October 13, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Oct 12 09:57:36 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option does not appear.
Current status: We've deployed the aforementioned fix and are reaching out to affected users to validate that impact is no longer occurring.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Tuesday, October 13, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sun Oct 11 06:35:44 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option does not appear.
Current status: We're continuing to monitor the deployment of our code fix, which we anticipate will complete by our next scheduled communications update.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Friday, October 9, 2026, at 4:10 PM UTC
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Monday, October 12, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sun Oct 11 06:35:43 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option does not appear.
Current status: We're continuing to monitor the deployment of our code fix, which we anticipate will complete by our next scheduled communications update.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Friday, October 9, 2026, at 4:10 PM UTC
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Monday, October 12, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Sat Oct 10 11:03:26 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option does not appear.
Current status: We're monitoring the deployment of our code fix, which we anticipate will complete by our next scheduled communications update.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Friday, October 9, 2026, at 4:10 PM UTC
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Sunday, October 11, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Sat Oct 10 05:51:13 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option does not appear.
Current status: We've identified that a recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy. We're applying a code fix to mitigate impact and expect to be able to provide a remediation timeline by our next scheduled update.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Root cause: A recent service update introduced a regression that causes the registration report download option to become unavailable when the engagement reporting policy is disabled, despite the report being independent of this policy.
Next update by: Saturday, October 10, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Oct 9 17:49:52 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option does not appear.
Current status: We've identified a potential code issue which we're validating a fix for to ensure its efficacy before applying it to affected environments. Once validation is complete and we confirm that the code issue is the source of the impact, we'll provide a timeline for deployment of the fix.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Next update by: Saturday, October 10, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Oct 9 15:35:40 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option does not appear.
Current status: In conjunction with our continued review of feature updates that may be contributing to the issue, we're analyzing logs provided by some affected user to determine the source of impact.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Next update by: Friday, October 9, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Oct 9 14:57:19 2026 |
|---|
| Description: | Title: Users may be unable to download webinar registration details from the Events app in Microsoft Teams
User impact: Users may be unable to download webinar registration details from the Events app in Microsoft Teams.
More info: Specifically, this impacts users who have the AllowEngagementReport meeting policy set to Off, as they're unable to download webinar registration details in Microsoft Teams Events because the Download option does not appear.
Current status: We've received reports from affected users that users may be unable to download webinar registration details in Microsoft Teams Events when the AllowEngagementReport meeting policy is set to Off. We're reviewing recent feature updates to the service to isolate the source of this issue and identify appropriate remediation actions.
Scope of impact: Impact may occur for users whose assigned meeting policy has AllowEngagementReport set to Off, preventing them from downloading webinar registration details from the Events app in Microsoft Teams. This information may be updated as our investigation continues.
Next update by: Friday, October 9, 2026, at 8:00 PM UTC
|
|---|
|
MO1481173 - Admins may see multiple usage reports not updating 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 16 14:54:29 2026 |
|---|
| Root Cause: | Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.
|
|---|
| Next Update: | Monday, October 19, 2026, at 8:30 PM UTC |
|---|
|
Details
| Time: | Fri Oct 16 14:54:29 2026 |
|---|
| Description: | Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center
User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.
More info: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage reports may not show data since October 6, 2026:
-Microsoft 365 Apps Active Users reports
-Overview reports
-Forms reports
The following usage reports have recovered as of October 12, 2026:
- Adoption Score reports
- Multi-geo Tenant usage reports
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Microsoft 365 Apps usage reports
The following usage reports have recovered as of October 15, 2026:
- Mailbox usage reports
- Microsoft Teams User activity reports
- Microsoft 365 Group activity reports
Current status: Our enablement of the optimizations to resolve the delayed Microsoft 365 Apps Active Users reports, Overview, and Forms reports is still ongoing, and we'll provide a timeline for the completion of our resolution as one becomes 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.
Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.
Next update by: Monday, October 19, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Oct 15 16:09:35 2026 |
|---|
| Description: | Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center
User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.
More info: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage reports may not show data since October 6, 2026:
-Microsoft 365 Apps Active Users reports
-Overview reports
-Forms reports
The following usage reports have recovered as of October 12, 2026:
- Adoption Score reports
- Multi-geo Tenant usage reports
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Microsoft 365 Apps usage reports
The following usage reports have recovered as of October 15, 2026:
- Mailbox usage reports
- Microsoft Teams User activity reports
- Microsoft 365 Group activity reports
Current status: After our optimizations addressed the delays for Mailbox usage, Microsoft Teams User activity, and Microsoft 365 Group activity reports, we've determined that our pipeline is also producing delays for Microsoft 365 Apps Active Users reports, Overview, and Forms reports. We're enabling the same optimizations to affected users which we're expecting to remediate the impact.
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.
Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.
Next update by: Friday, October 16, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Oct 14 16:50:07 2026 |
|---|
| Description: | Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center
User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.
More info: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage reports may not show data since October 6, 2026:
- Mailbox usage reports
- Microsoft Teams User activity reports
- Microsoft 365 Group activity reports
The following usage reports have recovered as of October 12, 2026:
- Adoption Score reports
- Multi-geo Tenant usage reports
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Microsoft 365 Apps usage reports
Current status: We've identified that additional server-side optimizations are needed to fully remediate the impact. We're applying these optimizations to the remaining affected users and continuing to monitor the affected report types to validate full recovery.
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.
Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.
Next update by: Thursday, October 15, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 16:40:12 2026 |
|---|
| Description: | Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center
User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.
More info: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage reports may not show data since October 6, 2026:
- Mailbox usage reports
- Microsoft Teams User activity reports
- Microsoft 365 Group activity reports
The following usage reports have recovered as of October 12, 2026:
- Adoption Score reports
- Multi-geo Tenant usage reports
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Microsoft 365 Apps usage reports
Current status: We've completed our additional service-side optimizations and received some reports from impacted users that this issue has been remediated. We're continuing to monitor the final impacted report types to validate recovery.
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.
Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.
Next update by: Wednesday, October 14, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Oct 12 16:07:33 2026 |
|---|
| Description: | Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center
User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.
More info: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage reports may not show data since October 6, 2026:
- Mailbox usage reports
- Microsoft Teams User activity reports
- Microsoft 365 Group activity reports
The following usage reports have recovered as of October 12, 2026:
- Adoption Score reports
- Multi-geo Tenant usage reports
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Microsoft 365 Apps usage reports
Current status: We've updated the "More info" section to reflect the current processing delays for the impacted report types. While we've remediated the issues which led to the majority of delays across the listed report types, we're completing additional optimization to ensure that the data reporting delays for the remaining three report types recover as quickly and efficiently as possible.
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.
Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.
Next update by: Tuesday, October 13, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Oct 9 16:51:27 2026 |
|---|
| Description: | Title: Admins may see multiple usage reports not updating in the Microsoft 365 admin center
User impact: Admins may see multiple usage reports not updating in the Microsoft 365 admin center.
More info: The following usage reports may not show data since October 5, 2026:
- Microsoft 365 Group Activity reports
- Adoption score reports
- Microsoft Teams usage reports
- Microsoft Teams per-channel analytics
- Multi-geo Tenant usage reports
The following usage reports may not show data since October 4, 2026:
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Mailbox usage reports
- Microsoft 365 Apps usage reports
Current status: We've updated the More info section of this communication to indicate that a portion of some of the reports with stale data since October 3, 2026 now include data through October 5, 2026. We'll continue to update that portion of our messaging while the remediation actions progress through the backlog of data ingestion. need to monitor in order to provide a better timeline for remediation is taking longer than expected. We continue to monitor as the backlog of data processes. We anticipate that a better timeline will be available with our next communication.
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.
Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.
Next update by: Monday, October 12, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Oct 8 15:58:01 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 may show data from prior to October 3, 2026:
- Microsoft 365 Group Activity reports
- Adoption score reports
- Microsoft Teams usage reports
- Microsoft Teams per-channel analytics
- Multi-geo Tenant usage reports
The following usage reports have recovered as of October 8, 2026, and show data up to October 4, 2026:
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Mailbox usage reports
- Microsoft 365 Apps usage reports
Current status: We've enabled our long-term fix, but we're continuing our monitoring of service health as the backlog processes to ensure that this fully remediates the issue. We anticipate that our monitoring will also help us provide more information on our timeline by our next scheduled communications update,
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.
Root cause: Upstream processes responsible for managing user data were unable to process data as effectively as expected, leading to delays populating user reports.
Next update by: Friday, October 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 15:50:21 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: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage report types may show delays after October 3, 2026:
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Mailbox usage reports
- Microsoft 365 Apps usage reports
- Microsoft Teams usage reports
- Microsoft 365 Group Activity reports
- Adoption Score reports
Current status: While our efforts to enable our long-term fix are ongoing, we're continuing to rebalance service traffic to provide an interim improvement to data freshness for impacted users.
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 8, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Oct 6 16:21:41 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: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage report types may have been delayed since September 29, 2026:
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Mailbox usage reports
- Microsoft 365 Apps usage reports
- Microsoft Teams usage reports
- Microsoft 365 Group Activity reports
- Adoption Score reports
Current status: Following our traffic optimizations to the affected subset of service infrastructure, we're monitoring their recovery and the reduction of data reporting delays. We're expecting clarity into our mitigation timeline by our next scheduled communication update.
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, October 7, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Oct 5 16:45:32 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: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage report types may have been delayed since September 29, 2026:
- Active user reports
- Email Activity reports
- Email Apps usage reports
- Mailbox usage reports
- Microsoft 365 Apps usage reports
- Microsoft Teams usage reports
- Microsoft 365 Group Activity reports
- Adoption Score reports
Current status: We've continued to observe significant recovery in data reporting delays for the impacted report types. However, our monitoring of service health telemetry has allowed us to identify a portion of service infrastructure that is underperforming and which is resulting in continued impact. We're analyzing our next steps so that we can develop a timeline for full remediation.
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, October 6, 2026, at 9:00 PM UTC
|
|---|
|
| 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
- Microsoft 365 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
More info: 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
- Microsoft 365 Apps usage reports
- Microsoft 365 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
- Microsoft 365 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: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage report types are delayed since September 19, 2026:
- Microsoft Teams usage reports
- Microsoft 365 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
- Microsoft 365 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: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage report types are delayed since September 19, 2026:
- Microsoft Teams usage reports
- Microsoft 265 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
- Microsoft 365 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: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage report types are delayed since September 19, 2026:
- Microsoft Teams usage reports
- Microsoft 365 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
- Microsoft 365 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: Due to the delay in data propagation, impacted usage reports may not be viewable.
The following usage report types are delayed since September 19, 2026:
- Microsoft Teams usage reports
- Microsoft 365 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
- Microsoft 365 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
|
|---|
|
OP1505951 - Some users may be unable to create or publish assignments in Microsoft OneNote
| Status: | serviceRestored |
|---|
| Start Time: | Sun Oct 11 08:10:00 2026 |
|---|
| End Time: | Fri Oct 16 10:25:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 16 14:29:53 2026 |
|---|
| Root Cause: | A recent update to the authentication flow utilized in this event contained an issue, which is resulting in this issue.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 16 13:59:49 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish assignments in Microsoft OneNote
User impact: Users may have been unable to create or publish assignments in OneNote.
Final status: We've completed the release of the fix and validated this has remediated impact with internal testing and service telemetry.
Scope of impact: Impact was specific to some users attempting to create or publish assignments in Microsoft OneNote.
Start time: Sunday, October 11, 2026, at 12:10 PM UTC
End time: Friday, October 16, 2026, at 2:25 PM UTC
Root cause: A recent update to the authentication flow utilized in this event contained an issue, which is resulting in this issue.
Next steps:
- We're continuing our analysis of the impacting authentication change to better identify and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 14 13:43:10 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish assignments in Microsoft OneNote
User impact: Users may be unable to create or publish assignments in OneNote.
Current status: While our fix is continuing to deploy at a rate slower than originally anticipated, we're observing some reduction in the associated errors. However, our analysis of the infrastructure to which the fix has been deployed shows some portions aren't updating as expected, which is preventing the full remediation of the impact. We're analyzing these affected portions of infrastructure to determine whether there are any other actions necessary to totally resolve the issue.
Scope of impact: Impact is specific to some users attempting to create or publish assignments in Microsoft OneNote.
Start time: Sunday, October 11, 2026, at 12:10 PM UTC
Root cause: A recent update to the authentication flow utilized in this event contained an issue, which is resulting in this issue.
Next update by: Friday, October 16, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 14:14:47 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish assignments in Microsoft OneNote
User impact: Users may be unable to create or publish assignments in OneNote.
Current status: We’ve begun deploying our fix to the affected environment and anticipate that this process will be complete by our next scheduled update.
Scope of impact: Impact is specific to some users attempting to create or publish assignments in Microsoft OneNote.
Start time: Sunday, October 11, 2026, at 12:10 PM UTC
Root cause: A recent update to the authentication flow utilized in this event contained an issue, which is resulting in this issue.
Next update by: Wednesday, October 14, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 07:08:25 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish assignments in Microsoft OneNote
User impact: Users may be unable to create or publish assignments in OneNote.
Current status: We’ve completed development of the fix and are preparing to deploy it across the affected environment. We’ll monitor service health as the deployment progresses to determine whether it is alleviating impact.
Scope of impact: Impact is specific to some users attempting to create or publish assignments in Microsoft OneNote.
Next update by: Tuesday, October 13, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 05:29:26 2026 |
|---|
| Description: | Title: Some users may be unable to create assignments in Microsoft OneNote
User impact: Users may be unable to create assignments in Microsoft OneNote.
Current status: We’re investigating elevated failures affecting assignment creation in Microsoft OneNote and are monitoring the affected environments to assess the extent of impact. We're developing and testing a fix as part of our mitigation efforts. Once validation is complete, we'll begin deploying the fix across the affected environment to restore service functionality.
Scope of impact: Your organization is affected by this event, and some users attempting to create assignments in Microsoft OneNote may be impacted.
Next update by: Tuesday, October 13, 2026, at 11:30 AM UTC
|
|---|
|
TM1509890 - Some users' calls may fail in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 15 22:15:48 2026 |
|---|
| End Time: | Fri Oct 16 13:26:01 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Oct 16 13:32:24 2026 |
|---|
| Root Cause: | A recent configuration change that managed how phone numbers were processed was responsible for impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 16 13:32:20 2026 |
|---|
| Description: | Title: Some users' calls may fail in Microsoft Teams
User impact: Users' calls may have failed in Microsoft Teams.
More info: Specifically, reports from affected users indicated that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams weren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not have received inbound calls.
Final status: We've confirmed that the recent configuration change that managed how phone numbers were processed was responsible for impact, and affected users confirm that impact is remediated after we reverted this change and replaying any changes to phone number that occurred during the window of impact.
Scope of impact: Impact was specific to users attempting to make calls to phone numbers that had recently undergone assignment changes in Microsoft Teams.
Start time: Friday, October 16, 2026, at 2:12 AM UTC
End time: Friday, October 16, 2026, at 4:00 PM UTC
Root cause: A recent configuration change that managed how phone numbers were processed was responsible for impact.
Next steps: We're reviewing and improving our configuration change procedures to detect and prevent similar issues from occurring again in the future.
This is the final update for this event.
|
|---|
|
| Time: | Fri Oct 16 11:30:40 2026 |
|---|
| Description: | Title: Some users' calls may fail in Microsoft Teams
User impact: Users' calls may fail in Microsoft Teams.
More info: Specifically, reports from affected users indicate that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not receive inbound calls.
Current status: We've reverted the recent configuration change that relates to how phone numbers are processed and are monitoring to confirm if this change caused the reported impact and if the issue is resolved.
Scope of impact: Impact is specific to users attempting to make calls to phone numbers that have recently undergone assignment changes in Microsoft Teams. This information may be updated as our investigation continues.
Next update by: Friday, October 16, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Oct 16 09:26:48 2026 |
|---|
| Description: | Title: Some users' calls may fail in Microsoft Teams
User impact: Users' calls may fail in Microsoft Teams.
More info: Specifically, reports from affected users indicate that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not receive inbound calls.
Current status: We’ve reprovisioned the affected resource account-to-phone number association as an initial mitigation. During our investigation, we identified a recent configuration change that may be contributing to the impact. We’re investigating this change to determine whether it’s responsible for the issue.
Scope of impact: Impact is specific to users attempting to make calls to phone numbers that have recently undergone assignment changes in Microsoft Teams.
Next update by: Friday, October 16, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Oct 16 05:23:29 2026 |
|---|
| Description: | Title: Some users' calls may fail in Microsoft Teams
User impact: Users' calls may fail in Microsoft Teams.
More info: Specifically, reports from affected users indicate that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not receive inbound calls.
Current status: We’ve identified a potential issue with cached information not updating as expected following phone-number assignment changes. We’re reprovisioning the affected resource account-to-phone number association as an initial mitigation and monitoring the results to validate our root cause hypothesis and determine whether additional steps are required.
Scope of impact: Impact is specific to users attempting to make calls to phone numbers that have recently undergone assignment changes in Microsoft Teams.
Next update by: Friday, October 16, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Fri Oct 16 00:39:05 2026 |
|---|
| Description: | Title: Some users' calls are failing in Microsoft Teams
User impact: Users' calls are failing in Microsoft Teams.
More info: Specifically, reports from affected users indicate that Public Switched Telephone Network (PSTN) direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected. Additionally, resource accounts and auto attendants associated with these call queues may not receive inbound calls.
Current status: We're continuing to review user-provided service logs and call logs to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Your organization is impacted by this event, and some users making calls in Microsoft Teams are affected.
Next update by: Friday, October 16, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Oct 15 22:52:50 2026 |
|---|
| Description: | Title: Some users' calls are failing in Microsoft Teams
User impact: Users' calls are failing in Microsoft Teams.
More info: Specifically, reports from affected users indicate that PSTN direct routing calls for certain accounts associated with call queues in Microsoft Teams aren't being connected.
Current status: We're reviewing and analyzing user-provided service logs and contextual details to assist with our investigation and determine our next troubleshooting steps.
Scope of impact: Your organization is impacted by this event, and some users making calls in Microsoft Teams are affected.
Next update by: Friday, October 16, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Oct 15 22:21:38 2026 |
|---|
| Description: | Title: Some users' calls are failing in Microsoft Teams
User impact: Users' calls are failing in Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1489432 - Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Oct 6 07:45:49 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 16 05:50:03 2026 |
|---|
| Root Cause: | A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
|
|---|
| Next Update: | Monday, October 19, 2026, at 10:00 AM UTC |
|---|
|
Details
| Time: | Fri Oct 16 05:48:24 2026 |
|---|
| Description: | Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile
User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.
More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop.
More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
Current status: We’re validating an additional fix in our internal environment to confirm its effectiveness before deploying it to the affected infrastructure. We’ll provide the deployment timeline once it becomes available.
Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues.
Start time: Friday, September 25, 2026, at 7:30 AM UTC
Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
Next update by: Monday, October 19, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Oct 14 05:56:16 2026 |
|---|
| Description: | Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile
User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.
More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop.
More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
Current status: We've confirmed that the fix should now have reached most affected users, and we're working with a subset of users to confirm its effectiveness and validate recovery. We've identified some cases where the issue persists and are working to implement additional fix. We'll provide an update once a deployment timeline for the additional fix is available.
Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues.
Start time: Friday, September 25, 2026, at 7:30 AM UTC
Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
Next update by: Friday, October 16, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Oct 12 05:20:53 2026 |
|---|
| Description: | Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile
User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.
More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop.
More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
Current status: We’re proceeding to monitor the deployment as it progresses and expect completion by Wednesday, October 14, 2026.
Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues.
Start time: Friday, September 25, 2026, at 7:30 AM UTC
Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
Next update by: Wednesday, October 14, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Oct 12 05:20:51 2026 |
|---|
| Description: | Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile
User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.
More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop.
More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
Current status: We’re proceeding to monitor the deployment as it progresses and expect completion by Wednesday, October 14, 2026.
Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues.
Start time: Friday, September 25, 2026, at 7:30 AM UTC
Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
Next update by: Wednesday, October 14, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Oct 7 05:26:42 2026 |
|---|
| Description: | Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile
User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.
More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop.
More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
Current status: We’ve completed validation of our fix in our internal testing environment and have begun deploying it across the affected environments. We’ve received confirmation from a subset of affected users that the fix successfully resolves the issue, and we’re continuing to monitor the broader deployment as it progresses. We expect the deployment to complete by Wednesday, October 14, 2026.
Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues.
Start time: Friday, September 25, 2026, at 7:30 AM UTC
Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
Next update by: Monday, October 12, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Oct 6 14:49:01 2026 |
|---|
| Description: | Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile
User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.
More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop.
More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
Current status: We’ve begun deploying our fix to the internal environment to validate its effectiveness. Once this process has completed, we will provide a remediation timeline.
Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted. This information may be updated as our investigation continues.
Start time: Friday, September 25, 2026, at 7:30 AM UTC
Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
Next update by: Wednesday, October 7, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Oct 6 09:32:32 2026 |
|---|
| Description: | Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile
User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.
More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop.
More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
Current status: We’ve developed a fix and are deploying it to our internal environment to validate its effectiveness before deploying it to the affected environment. We expect to provide a deployment timeline and rollout trajectory in our next communication update.
Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted.
Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
|
|---|
|
| Time: | Tue Oct 6 08:24:26 2026 |
|---|
| Description: | Title: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile
User impact: Users may be unable to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile.
More info: Affected users may observe missing contacts, blank or grey placeholder entries, or Speed Dial entries that can't be re-added. This behavior may occur across Microsoft Teams desktop and web experiences, Outlook Mobile, and Outlook desktop.
More specifically, this issue impacts in-tenant contacts created in Microsoft Teams using the Notify when available presence notification option. Some older contacts may also be impacted under specific circumstances.
Current status: We’ve validated that a problem with a contact-processing component has incorrectly separated some Profile Based Contacts (PBCs) from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank. We’re developing a fix to re-merge the affected contacts with their associated profiles and expect to provide deployment timeline by our next scheduled update.
Scope of impact: Some users attempting to view contacts and Speed Dial entries in Microsoft Teams, Outlook desktop and mobile may be impacted.
Root cause: A problem with a contact-processing component has incorrectly separated some PBCs from their associated profiles when specific contact information isn't explicitly stored, causing affected contacts to appear as blank.
Next update by: Tuesday, October 6, 2026, at 1:30 PM UTC
|
|---|
|
TM1489031 - Users may see Microsoft Teams on the web displayed in English
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Oct 6 00:38:30 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 16 01:57:02 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Monday, October 19, 2026, at 10:00 PM UTC |
|---|
|
Details
| Time: | Fri Oct 16 01:56:33 2026 |
|---|
| Description: | Title: Users may see Microsoft Teams on the web displayed in English
User impact: Users may see Microsoft Teams on the web displayed in English.
More info: Impact may affect any user that doesn't have English set as their preferred language.
Current status: We're continuing to prepare our fix for full deployment and our current projections indicate that the issue may be remediated by early to mid-November, 2026.
Scope of impact: Any user may see Microsoft Teams on the web displayed in English when it isn’t their preferred language. This information may be updated as our investigation continues.
Next update by: Monday, October 19, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Oct 6 22:54:58 2026 |
|---|
| Description: | Title: Users see Microsoft Teams on the web displayed in English
User impact: Users see Microsoft Teams on the web displayed in English.
More info: Affected users don’t have English set as their preferred language.
Current status: We’ve developed and are in the initial stages of deploying a fix to correct the recent configuration change which is causing the issue and expect that a remediation timeline will be provided by the time of our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users see Microsoft Teams on the web displayed in English when it isn’t their preferred language. This information may be updated as our investigation continues.
Next update by: Monday, October 19, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Oct 6 02:09:44 2026 |
|---|
| Description: | Title: Users see Microsoft Teams on the web displayed in English
User impact: Users see Microsoft Teams on the web displayed in English.
More info: Affected users don’t have English set as their preferred language.
Current status: We’ve determined that a redirection issue is incorrectly applying English language settings when users access Microsoft Teams on the web. We’re reviewing options to correct this behavior and working with affected users to collect additional logs to better understand the impact scenario and fully resolve the issue.
Scope of impact: Your organization is affected by this event, and some users see Microsoft Teams on the web displayed in English when it isn’t their preferred language. This information may be updated as our investigation continues.
Next update by: Wednesday, October 7, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Oct 6 00:39:57 2026 |
|---|
| Description: | Title: Users see Microsoft Teams on the web displayed in English
User impact: Users see Microsoft Teams on the web displayed in English.
More info: Affected users don’t have English set as their preferred language.
Current status: We’re reviewing system logs to isolate the origin of this issue.
Scope of impact: Your organization is affected by this event, and some users see Microsoft Teams on the web displayed in English when it isn’t their preferred language. This information may be updated as our investigation continues.
Next update by: Tuesday, October 6, 2026, at 6:30 AM UTC
|
|---|
|
TM1506205 - Users may be unable to join Microsoft Teams meetings and see sign-in errors
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 6 21:00:00 2026 |
|---|
| End Time: | Thu Oct 15 23:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Oct 16 00:35:46 2026 |
|---|
| Root Cause: | A recent change to the authentication flow utilized in the event contained a regression, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 16 00:33:23 2026 |
|---|
| Description: | Title: Users may be unable to join Microsoft Teams meetings and see sign-in errors
User impact: Users may have been unable to join Microsoft Teams meetings and saw sign-in errors.
More info: Affected users saw a sign-in prompt when they attempted to join a meeting but clicking "sign-in" on the prompt had no effect.
Users can sign-out and sign back in as a temporary mitigation.
Final status: We've completed the deployment of our code fix to all affected environments and confirmed through telemetry, along with a subset of impacted users, that the issue is resolved.
Scope of impact: Some users who attempted to join Microsoft Teams meetings may have been affected by this issue.
Start time: Wednesday, October 7, 2026, at 1:00 AM UTC
End time: Friday, October 16, 2026, at 3:30 AM UTC
Root cause: A recent change to the authentication flow utilized in the event contained a regression, which resulted in impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to the Microsoft Teams meetings and sign-in authentication path prior to deployment to prevent similar impact in the future, and to improve our pre-deployment update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 15 20:35:31 2026 |
|---|
| Description: | Title: Users may be unable to join Microsoft Teams meetings and see sign-in errors
User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.
More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.
Users can sign-out and sign back in as a temporary mitigation.
Current status: Our code fix has nearly completed propagation throughout most of the affected environments and we're continuing to monitor it as it progresses. We anticipate it'll have fully propagated by our next scheduled communications update.
Scope of impact: Some users attempting to join Microsoft Teams meetings may be affected by this issue. This information may be updated as our investigation continues.
Start time: Wednesday, October 7, 2026, at 1:00 AM UTC
Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.
Next update by: Friday, October 16, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Wed Oct 14 17:49:18 2026 |
|---|
| Description: | Title: Users may be unable to join Microsoft Teams meetings and see sign-in errors
User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.
More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.
Users can sign-out and sign back in as a temporary mitigation.
Current status: We've halted the code change causing this problem to ensure that no additional users encounter Microsoft Teams meeting join and sign-in errors. We're deploying a code fix to remediate the issue for users who received the code change prior to us halting it. Users will experience progressive relief from the issue as this deployment reaches them and we expect the code fix to propagate fully around the time of our next update.
Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.
Start time: Wednesday, October 7, 2026, at 1:00 AM UTC
Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.
Next update by: Thursday, October 15, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 22:06:41 2026 |
|---|
| Description: | Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors
User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.
More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.
Users can sign-out and sign back in as a temporary mitigation.
Current status: We’re monitoring the rollback of the offending change and expect that a remediation timeline will be provided by our next scheduled communications update.
Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.
Start time: Wednesday, October 7, 2026, at 1:00 AM UTC
Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.
Next update by: Wednesday, October 14, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Oct 13 19:51:44 2026 |
|---|
| Description: | Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors
User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.
More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.
Users can sign-out and sign back in as a temporary mitigation.
Current status: We've initiated our rollback of the responsible change and will monitor this rollback to provide a mitigation timeline as it becomes available.
Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.
Start time: Wednesday, October 7, 2026, at 1:00 AM UTC
Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.
Next update by: Wednesday, October 14, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Oct 13 18:00:29 2026 |
|---|
| Description: | Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors
User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.
More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.
Users can sign-out and sign back in as a temporary mitigation.
Current status: We've confirmed a recent change to the authentication flow utilized in the event contained a regression, resulting in this impact. We're preparing to rollback this change in the affected environments and will provide a remediation timeline as soon as one becomes available.
Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.
Start time: Wednesday, October 7, 2026, at 1:00 AM UTC
Root cause: A recent change to the authentication flow utilized in the event contained a regression, resulting in this impact.
Next update by: Wednesday, October 14, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Oct 13 14:56:51 2026 |
|---|
| Description: | Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors
User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.
More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.
Users can sign-out and sign back in as a temporary mitigation.
Current status: We're continuing to review the logs provided by a subset of affected users alongside service side data in order to develop the most effective remediation steps.
Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.
Next update by: Tuesday, October 13, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Oct 13 13:18:36 2026 |
|---|
| Description: | Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors
User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.
More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.
Users can sign-out and sign back in as a temporary mitigation.
Current status: We're reviewing the logs provided by a subset of affected users and have requested an additional set of fresh logs from those users to assist in pinpointing the underlying root cause of this event, so we may develop the most effective remediation steps.
Scope of impact: Some users may be unable to join Microsoft Teams meetings and see sign-in errors. This information may be updated as our investigation continues.
Next update by: Tuesday, October 13, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Oct 13 12:57:13 2026 |
|---|
| Description: | Title: Some users may be unable to join Microsoft Teams meetings and see sign-in errors
User impact: Users may be unable to join Microsoft Teams meetings and see sign-in errors.
More info: Affected users see a sign-in prompt when attempting to join a meeting but clicking "sign-in" on the prompt has no effect.
Users can sign-out and sign back in as a temporary mitigation.
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.
|
|---|
|
MO1505952 - Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Oct 13 03:40:00 2026 |
|---|
| End Time: | Tue Oct 13 14:31:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Oct 15 19:43:53 2026 |
|---|
| Root Cause: | A section of GSA infrastructure was performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 15 19:43:53 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Oct 13 14:54:18 2026 |
|---|
| Description: | Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
User impact: Users may have been unable to access multiple Microsoft 365 services using GSA.
More info: Impacted services may have included, but not been limited to:
- Outlook
- Outlook on the web
- OneDrive
- SharePoint Online
- Microsoft Teams
- Windows 365 Cloud PCs
Final status: We've completed our restarts throughout the affected infrastructure and confirmed through telemetry and user reports that this issue is resolved.
Scope of impact: Some users in Germany that attempted to access Microsoft 365 services listed in the More info section using GSA may have been impacted.
Start time: Tuesday, October 13, 2026, at 7:40 AM UTC
End time: Tuesday, October 13, 2026, at 6:31 PM UTC
Root cause: A section of GSA infrastructure was performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.
Next steps:
- To help prevent similar impact in the future, we're further reviewing the GSA infrastructure and testing performance on the previously impacted portions of infrastructure.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue Oct 13 14:18:24 2026 |
|---|
| Description: | Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
User impact: Users may be unable to access multiple Microsoft 365 services using GSA.
More info: Impacted services may include, but aren't limited to:
- Outlook
- Outlook on the web
- OneDrive
- SharePoint Online
- Microsoft Teams
- Windows 365 Cloud PCs
As a workaround, users may disable GSA to access the affected Microsoft 365 services until the resolution of this incident.
Current status: We're finishing our restarts throughout the affected infrastructure and expect this will be complete and resolve all impact by Tuesday, October 13, 2026, at 7:00 PM UTC. Our telemetry is showing service recovery, and we'll continue to monitor to ensure full remediation.
Scope of impact: Some users in Germany attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.
Start time: Tuesday, October 13, 2026, at 7:40 AM UTC
Preliminary root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.
Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Oct 13 13:56:53 2026 |
|---|
| Description: | As a workaround, users may disable GSA to access the affected Microsoft 365 services until the resolution of this incident.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Oct 13 13:23:43 2026 |
|---|
| Description: | Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
User impact: Users may be unable to access multiple Microsoft 365 services using GSA.
More info: Impacted services may include, but aren't limited to:
- Outlook
- Outlook on the web
- OneDrive
- SharePoint Online
- Microsoft Teams
- Windows 365 Cloud PCs
Current status: We're continuing our targeted restarts throughout the impacted infrastructure, and our telemetry shows services hosted on the restarted infrastructure are now operating at healthy service levels. We're also receiving confirmation that impact is resolved for some users.
Scope of impact: Some users in Germany attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.
Start time: Tuesday, October 13, 2026, at 7:40 AM UTC
Preliminary root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.
Next update by: Tuesday, October 13, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 12:22:38 2026 |
|---|
| Description: | Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
User impact: Users may be unable to access multiple Microsoft 365 services using GSA.
More info: Impacted services may include, but aren't limited to:
- Outlook
- Outlook on the web
- OneDrive
- SharePoint Online
- Microsoft Teams
- Windows 365 Cloud PCs
Current status: We're restarting a portion of impacted infrastructure where we've removed traffic and are seeing positive trends towards recovery. We've confirmed through internal testing that this resolves impact for some users and we're monitoring to validate the full recovery of the service.
Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.
Start time: Tuesday, October 13, 2026, at 8:00 AM UTC
Preliminary root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.
Next update by: Tuesday, October 13, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 11:21:00 2026 |
|---|
| Description: | Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
User impact: Users may be unable to access multiple Microsoft 365 services using GSA.
More info: Impacted services may include, but aren't limited to:
- Outlook
- Outlook on the web
- OneDrive
- SharePoint Online
- Microsoft Teams
- Windows 365 Cloud PCs
Current status: We've completed redirecting traffic to healthy infrastructure and are assessing for positive trends towards recovery. We're continuing to investigate additional mitigating actions to expedite remediation.
Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.
Start time: Tuesday, October 13, 2026, at 8:00 AM UTC
Preliminary root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.
Next update by: Tuesday, October 13, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 10:57:20 2026 |
|---|
| Description: | We're redirecting traffic from the underperforming infrastructure to improve service health. We're monitoring to confirm this will fully resolve impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Oct 13 10:35:16 2026 |
|---|
| Description: | Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
User impact: Users may be unable to access multiple Microsoft 365 services using GSA.
More info: Impacted services may include, but aren't limited to:
- Outlook
- Outlook on the web
- OneDrive
- SharePoint Online
- Microsoft Teams
- Windows 365 Cloud PCs
Current status: We've deployed the traffic optimizations and although we saw a reduction of errors initially, this did not fully resolve the issue. We're continuing to troubleshoot the issue to develop additional mitigation strategies.
Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.
Start time: Tuesday, October 13, 2026, at 8:00 AM UTC
Root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.
Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 09:29:09 2026 |
|---|
| Description: | Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
User impact: Users may be unable to access multiple Microsoft 365 services using GSA.
More info: Impacted services may include, but aren't limited to:
- Outlook
- Outlook on the web
- OneDrive
- SharePoint Online
- Microsoft Teams
- Windows 365 Cloud PCs
Current status: We're continuing to apply the aforementioned traffic and performance optimizations with early signals showing signs of recovery.
Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.
Preliminary root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.
Next update by: Tuesday, October 13, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 07:30:08 2026 |
|---|
| Description: | Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
User impact: Users may be unable to access multiple Microsoft 365 services using GSA.
More info: Impacted services may include, but aren't limited to:
- Outlook
- Outlook on the web
- OneDrive
- SharePoint Online
- Microsoft Teams
- Windows 365 Cloud PCs
Current status: We’ve identified that a section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact. We’re applying performance and traffic optimizations to remediate impact and restore connectivity.
Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.
Preliminary root cause: A section of GSA infrastructure is performing below acceptable performance thresholds, affecting connectivity to Microsoft 365 services and resulting in impact.
Next update by: Tuesday, October 13, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 05:41:18 2026 |
|---|
| Description: | Title: Users may be unable to access multiple Microsoft 365 services using Global Secure Access (GSA)
User impact: Users may be unable to access multiple Microsoft 365 services using GSA.
More info: Impacted services may include, but aren't limited to:
- Outlook
- Outlook on the web
- OneDrive
- SharePoint Online
- Microsoft Teams
- Windows 365 Cloud PCs
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Some users in Germany and the United Kingdom attempting to access Microsoft 365 services listed in the More info section using GSA may be impacted.
Next update by: Tuesday, October 13, 2026, at 11:30 AM UTC
|
|---|
|
DZ1509195 - Users see delays in Microsoft Defender for Identity event-based experiences
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 15 14:04:26 2026 |
|---|
| End Time: | Thu Oct 15 15:23:22 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Identity |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 15 15:24:36 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 15 15:24:32 2026 |
|---|
| Description: | Title: Users see delays in Microsoft Defender for Identity event-based experiences
User impact: Users saw delays in Microsoft Defender for Identity event-based experiences.
More info: Impacted experiences included:
- Viewing activities in the Microsoft Defender portal
- Activity alerts
- Advanced hunting
- Microsoft Defender for Cloud Apps events in Sentinel
Final status: While we were reviewing the service health telemetry related to this event, our automated recovery system repaired this problem. We confirmed that service was restored after monitoring the environment.
Scope of impact: Your organization was impacted by this event, and users saw delays in Microsoft Defender for Identity event-based experiences.
Start time: Thursday, October 15, 2026, at 1:50 PM UTC
End time: Thursday, October 15, 2026, at 4:52 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 15 14:05:42 2026 |
|---|
| Description: | Title: Users see delays in Microsoft Defender for Identity event-based experiences
User impact: Users saw delays in Microsoft Defender for Identity event-based experiences.
More info: Impacted experiences included:
- Viewing activities in the Microsoft Defender portal
- Activity alerts
- Advanced hunting
- Microsoft Defender for Cloud Apps events in Sentinel
Current status: We've investigated a problem in which users saw delays in Microsoft Defender for Identity event-based experiences. and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
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: | Tue Sep 8 19:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 15 14:50:22 2026 |
|---|
| Root Cause: | A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.
|
|---|
| Next Update: | Monday, October 19, 2026, at 8:30 PM UTC |
|---|
|
Details
| Time: | Thu Oct 15 14:50:22 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: Our fix remains at 93 percent, as the remaining saturation is expected to take extra time, per process. We're continuing to monitor progress toward completion and confirm that impact is remediated for all users.
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.
Start time: Tuesday, September 8, 2026, at 11:00 PM UTC
Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.
Next update by: Monday, October 19, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Oct 14 15:33:21 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: Our fix deployment has completed in the initial deployment rings and has started saturating in affected customers' environments. Our monitoring has validated that our fix has completed approximately 93 percent of the deployment, and we'll provide an updated timeline for it completing once it has become available.
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.
Start time: Tuesday, September 8, 2026, at 11:00 PM UTC
Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.
Next update by: Thursday, October 15, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 15:17:13 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: Our monitoring of the deployment is ongoing as it propagates through earlier deployment rings prior to beginning saturation to affected customers’ environments. We'll provide a projected timeline for remediation based on the rate of progress as one becomes available.
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.
Start time: Tuesday, September 8, 2026, at 11:00 PM UTC
Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.
Next update by: Wednesday, October 14, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Oct 12 20:30:13 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 continuing to monitor and track the saturation percentage of the fix deployment to ensure it reaches 100 percent in all affected environments.
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.
Start time: Tuesday, September 8, 2026, at 11:00 PM UTC
Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.
Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 20:02:21 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 validated that the previously identified recent change that removed an attribute component from the service process that requires that attribute, has led to impact. We're continuing to monitor our fix deployment; however, this process is taking longer than anticipated. The current fix saturation is at roughly 90 percent, and we'll provide a timeline of completion once it becomes available.
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.
Start time: Tuesday, September 8, 2026, at 11:00 PM UTC
Root cause: A recent change made to the service removed an attribute component from the service process that requires that attribute, leading to impact.
Next update by: Tuesday, October 13, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Oct 6 19:51:04 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 continuing to monitor the deployment of our fix as it progresses, and we'll aim to provide a timeline of completion by our next scheduled communications.
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: Thursday, October 8, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Oct 5 19:32:54 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: Our fix deployment is nearing completion, and most affected users should now be experiencing recovery. We’ll continue monitoring the deployment to ensure it completes and restores service for all affected users.
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: Wednesday, October 7, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Oct 5 19:32:48 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: Our fix deployment is nearing completion, and most affected users should now be experiencing recovery. We’ll continue monitoring the deployment to ensure it completes and restores service for all affected users.
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: Wednesday, October 7, 2026, at 1:00 AM UTC
|
|---|
|
| 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.
|
|---|
|
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 15 11:55:19 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 22, 2026, at 5:30 PM UTC |
|---|
|
Details
| Time: | Thu Oct 15 11:55:19 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've initiated the deployment of our fix, which is ongoing and has saturated through over 50 percent of the affected environment. We're continuing to monitor its progress as it continues and anticipate it will complete, remediating impact for all users, by our next scheduled communication 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, October 22, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Oct 8 11:57:50 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've completed the validations for our fix, which we're preparing to deploy to the affected environment. We still anticipate deployment will begin by Thursday, October 15, 2026.
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 15, 2026, at 5:30 PM UTC
|
|---|
|
| 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
|
|---|
|
PB1508905 - Some users may encounter refresh failures when using the Dynamics 365 Business Central connector in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 14 11:00:00 2026 |
|---|
| End Time: | Thu Oct 15 10:55:10 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 15 11:41:43 2026 |
|---|
| Root Cause: | A regression in the Dynamics 365 Business Central control-plane service was causing refresh failures when using the connector in Power BI
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 15 11:41:39 2026 |
|---|
| Description: | Title: Some users may encounter refresh failures when using the Dynamics 365 Business Central connector in Power BI
User impact: Users may have encountered refresh failures when using the Dynamics 365 Business Central connector in Power BI.
Final status: After our completed rollback of the affected service, our internal telemetry verified that the impact had been remediated.
Scope of impact: The impact was specific to some users who had expected refreshes using the Dynamics 365 Business Central connector in Power BI.
Start time: Wednesday, October 14, 2026, at 3:00 PM UTC
End time: Thursday, October 15, 2026, at 2:32 PM UTC
Root cause: A regression in the Dynamics 365 Business Central control-plane service was causing refresh failures when using the connector in Power BI
Next steps:
- We're further analyzing the regression to help us isolate its source, and to help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 15 10:17:52 2026 |
|---|
| Description: | Title: Some users may encounter refresh failures when using the Dynamics 365 Business Central connector in Power BI
User impact: Users may encounter refresh failures when using the Dynamics 365 Business Central connector in Power BI.
Current status: We've identified that a regression in the Dynamics 365 Business Central control plane is causing API connection failures. We're rolling back the affected service to remediate the issue and are monitoring progress.
Scope of impact: Impact may be specific to some users expecting refreshes using the Dynamics 365 Business Central connector in Power BI.
Root cause: A regression in the Dynamics 365 Business Central control-plane service is causing refresh failures when using the connector in Power BI
Next update by: Thursday, October 15, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Oct 15 09:31:04 2026 |
|---|
| Description: | Title: Some users may encounter refresh failures when using the Dynamics 365 Business Central connector in Power BI
User impact: Users may encounter refresh failures when using the Dynamics 365 Business Central connector in Power BI.
Current status: We're continuing our analysis of service telemetry to help us identify the root cause and the next steps required to mitigate impact.
Scope of impact: Impact may be specific to some users expecting refreshes using the Dynamics 365 Business Central connector in Power BI.
Next update by: Thursday, October 15, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Oct 15 08:21:50 2026 |
|---|
| Description: | Title: Some users may encounter refresh failures when using the Dynamics 365 Business Central connector in Power BI
User impact: Users may encounter refresh failures when using the Dynamics 365 Business Central connector in Power BI.
Current status: We're analyzing service telemetry to help us identify the root cause and the next steps required to mitigate impact.
Scope of impact: Impact may be specific to some users expecting refreshes using the Dynamics 365 Business Central connector in Power BI.
Next update by: Thursday, October 15, 2026, at 2:00 PM UTC
|
|---|
|
OO1508394 - Users are unable to open presentations in PowerPoint Online for the web
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 14 18:38:00 2026 |
|---|
| End Time: | Wed Oct 14 23:00:00 2026 |
|---|
| Service: | Microsoft 365 for the web |
|---|
| Feature Group: | PowerPoint Online |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 15 02:03:11 2026 |
|---|
| Root Cause: | A recent deployment to the service infrastructure contained a code issue which led to a spike in request failures to the service.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 15 02:02:11 2026 |
|---|
| Description: | Title: Users are unable to open presentations in PowerPoint Online for the web
User impact: Users were unable to open presentations in PowerPoint Online for the web.
Final status: We've completed the roll back of the recent deployment and confirmed through service telemetry that service health has returned to normal and impact is resolved.
Scope of impact: Your organization was impacted by this event, and users were unable to open presentations in PowerPoint for the web.
Start time: Wednesday, October 14, 2026, at 10:38 PM UTC
End time: Thursday, October 15, 2026, at 3:00 AM UTC
Root cause: A recent deployment to the service infrastructure contained a code issue which led to a spike in request failures to the service.
Next steps:
- We're reviewing our update procedures to understand why impact to the PowerPoint Online for the web service infrastructure wasn't caught during the testing phase. This will help us 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: | Wed Oct 14 22:09:09 2026 |
|---|
| Description: | Title: Users are unable to open presentations in PowerPoint Online for the web
User impact: Users are unable to open presentations in PowerPoint Online for the web.
Current status: We're still in the processing of rolling back the recent deployment to the last known healthy version to fully remediate impact. We'll share an estimated timeline of completion once one becomes available.
Scope of impact: Your organization is impacted by this event, and users are unable to open presentations in PowerPoint for the web. This section may be updated as our investigation continues.
Start time: Wednesday, October 14, 2026, at 10:38 PM UTC
Root cause: A recent deployment to the service infrastructure that contained a code issue and led to a spike in request failures to the service.
Next update by: Thursday, October 15, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Oct 14 21:00:07 2026 |
|---|
| Description: | Title: Users are unable to open presentations in PowerPoint Online for the web
User impact: Users are unable to open presentations in PowerPoint Online for the web.
Current status: We've received alerts from our internal monitoring systems which indicates impact to PowerPoint Online for the web. We investigated the service and error logs and correlated impact with a recent deployment to the service infrastructure that contained a code issue and led to a spike in request failures to the service. We've rolled back the deployment and returned to the last known healthy version and we're monitoring the service health telemetry to confirm if impact has been fully resolved.
Scope of impact: Your organization is impacted by this event, and users are unable to open presentations in PowerPoint for the web. This section may be updated as our investigation continues.
Start time: Wednesday, October 14, 2026, at 10:38 PM UTC
Root cause: A recent deployment to the service infrastructure that contained a code issue and led to a spike in request failures to the service.
Next update by: Thursday, October 15, 2026, at 3:00 AM UTC
|
|---|
|
EX1507783 - Some users' mailbox syncs may fail with an error in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 29 18:06:00 2026 |
|---|
| End Time: | Wed Oct 14 17:43:25 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Oct 14 17:44:44 2026 |
|---|
| Root Cause: | recent code change intended to improve the resiliency of features associated with IPM mailboxes was enabled across multiple functions, which caused specific apps which rely on these functions being unable to access them. This resulted in the mailboxes of users with these management apps installed failing to sync.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 14 17:44:32 2026 |
|---|
| Description: | Title: Some users' mailbox syncs may fail with an error in Exchange Online
User impact: Users' mailbox syncs may have failed with an error in Exchange Online.
More info: Users saw the following error message in Microsoft Graph: "HTTP 400 -- Operation not allowed -- Operation on Non IPM Subtree forbidden."
Final status: After reverting the recent code change, we've confirmed through service health telemetry that the error code associated with this issue has been resolved. The portion of impacted users who have apps which access non-Interpersonal Messaging (IPM) mailboxes will now see that mailboxes complete syncing as expected.
Scope of impact: This issue may have affected some users' mailbox syncs, specifically for customers who use apps that access non-Interpersonal Messaging (IPM) mailboxes through Microsoft Graph, which returned an error code in Exchange Online.
Start time: Tuesday, September 29, 2026, at 10:06 PM UTC
End time: Wednesday, October 14, 2026, at 8:59 PM UTC
Root cause: recent code change intended to improve the resiliency of features associated with IPM mailboxes was enabled across multiple functions, which caused specific apps which rely on these functions being unable to access them. This resulted in the mailboxes of users with these management apps installed failing to sync.
Next steps:
- We're analyzing the records from this event so that we can ensure that future code updates account for all potential user scenarios.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 14 16:15:31 2026 |
|---|
| Description: | Title: Some users' mailbox syncs may fail with an error in Exchange Online
User impact: Users' mailbox syncs may fail with an error in Exchange Online.
More info: Users see the following error message in Microsoft Graph: "HTTP 400 -- Operation not allowed -- Operation on Non IPM Subtree forbidden."
Current status: We've identified a recent code change made to specific mailbox APIs which is resulting in the error messages seen in Microsoft Graph when these apps access non-Interpersonal Messaging (IPM) mailboxes. We're reverting this change to verify that it's the source of this issue and to fully remediate impact.
Scope of impact: This issue may affect some users' mailbox syncs, specifically for customers using apps that access non-Interpersonal Messaging (IPM) mailboxes through Microsoft Graph, which returns an error code in Exchange Online. This information may be updated as our investigation continues.
Next update by: Wednesday, October 14, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Oct 14 15:13:17 2026 |
|---|
| Description: | Title: Some users' mailbox syncing fails with an error in Exchange Online
User impact: Users' mailbox syncing fails with an error in Exchange Online.
More info: Users see the following error message in Microsoft Graph: "HTTP 400 -- Operation not allowed -- Operation on Non IPM Subtree forbidden."
Current status: We're investigating the error code associated with this impact alongside our service records to identify the source of the issue.
Scope of impact: This issue may affect some users' mailbox syncs, specifically for customers using apps that access non-Interpersonal Messaging (IPM) mailboxes through Microsoft Graph, which returns an error code in Exchange Online. This information may be updated as our investigation continues.
Next update by: Wednesday, October 14, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Oct 14 15:00:17 2026 |
|---|
| Description: | Title: Users' mailbox syncing fails with an error in Exchange Online
User impact: Users' mailbox syncing fails with an error in Exchange Online.
Current status: We're investigating a potential issue with mailbox sync status in Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1507859 - Some users may be missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Oct 12 16:48:00 2026 |
|---|
| End Time: | Wed Oct 14 14:16:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 14 16:22:48 2026 |
|---|
| Root Cause: | A tenant filter to disable the "Meeting options" button for a specific organization was unintentionally applied broadly to multiple organizations.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 14 16:22:32 2026 |
|---|
| Description: | Title: Some users may be missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps
User impact: Users may have been missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps.
More info: This issue was occurring in the following Microsoft 365 apps:
- Microsoft Teams desktop client
- Microsoft Teams web client
- Outlook on the web
- Outlook desktop client
The issue only occurred in standard Teams meetings, and live events, webinars, and town halls weren’t affected.
Final status: We've validated with a subset of affected users that our rollback of the problematic tenant filter has remediated impact.
Scope of impact: This issue impacted some users who may have been missing the "Meeting options” button when creating standard meetings using multiple Microsoft 365 apps.
Start time: Monday, October 12, 2026, at 8:48 PM UTC
End time: Wednesday, October 14, 2026, at 6:16 PM UTC
Root cause: A tenant filter to disable the "Meeting options" button for a specific organization was unintentionally applied broadly to multiple organizations.
Next steps:
- We're analyzing the problematic tenant filter to validate why it was applied broadly to further our understanding of how the issue was introduced and to evaluate what actions we can take to prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 14 15:04:05 2026 |
|---|
| Description: | Title: Some users may be missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps
User impact: Users may be missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps.
More info: This issue is occurring in the following Microsoft 365 apps:
- Microsoft Teams desktop client
- Microsoft Teams web client
- Outlook on the web
- Outlook desktop client
The issue only occurs in standard Teams meetings, and live events, webinars, and town halls aren’t affected.
Current status: We've received reports from multiple organizations noting that some users are missing the "Meeting options" button for Microsoft Teams meetings in multiple Microsoft 365 apps as listed in the "More info" section of this communication. We've isolated that a tenant filter to disable the "Meetings option" button for a specific group of users was unintentionally applied broadly. We're rolling back the offending change, and we anticipate impact to be remediated by our next scheduled update.
Scope of impact: This issue impacts some users who may be missing the "Meeting options” button when creating standard meetings using multiple Microsoft 365 apps. This section may be updated as the investigation progresses.
Start time: Monday, October 12, 2026, at 8:48 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by our next scheduled update on Wednesday, October 14, 2026, at 9:00 PM UTC.
Root cause: A tenant filter to disable the "Meeting options" button for a specific organization was unintentionally applied broadly to multiple organizations.
Next update by: Wednesday, October 14, 2026, at 9:00 PM UTC
|
|---|
|
MO1458983 - Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 20 20:00:00 2026 |
|---|
| End Time: | Sun Aug 30 20:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 14 15:55:33 2026 |
|---|
| Root Cause: | A recent change to an upstream part of the data processing pipeline resulted in delays impacting report generation.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 31 15:35:32 2026 |
|---|
| Description: | Title: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights
User impact: Admins may have encountered reporting delays across multiple Microsoft 365 admin centers and Viva Insights.
More info: Affected reports included but weren't limited to:
- Copilot Usage report in Microsoft 365 admin center
- Copilot Chat Usage report in Microsoft 365 admin center
- Copilot Readiness reports in Microsoft 365 admin center and Viva Insights
- Copilot Adoption report in Viva Insights
- Microsoft 365 Apps and Active users reports in Microsoft 365 admin center
- Teams App reports in Microsoft 365 admin center and Microsoft Teams admin center
Final status: After confirming that the upstream data pipeline adjustments had remediated the source of the issue and continuing to monitor report generation, we've validated that fresh usage reports are being created as expected and that all previous usage data is now available to admins.
Scope of impact: Any admin expecting reports from the affected scenarios as outlined in the More info section may have been affected.
Start time: Friday, August 21, 2026, at 12:00 AM UTC
End time: Monday, August 31, 2026, at 12:00 AM UTC
Root cause: A recent change to an upstream part of the data processing pipeline resulted in delays impacting report generation.
Next steps:
- We're analyzing the data we've gathered from this issue in order to develop improvements to our proactive remediation procedures to prevent similar impact from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 27 14:16:33 2026 |
|---|
| Description: | Title: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights
User impact: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights.
More info: Affected reports include but aren't limited to:
- Copilot Usage report in Microsoft 365 admin center
- Copilot Chat Usage report in Microsoft 365 admin center
- Copilot Readiness reports in Microsoft 365 admin center and Viva Insights
- Copilot Adoption report in Viva Insights
- Microsoft 365 Apps and Active users reports in Microsoft 365 admin center
- Teams App reports in Microsoft 365 admin center and Microsoft Teams admin center
Current status: Our efforts to make upstream data pipeline adjustments and report migrations to address the remaining reporting delays are ongoing, and at this time most affected data pipelines and reports have already been restored. Additionally, we've further confirmed no usage report data was lost as a result of this issue. We are continuing to monitor recovery until data freshness is fully restored across all remaining reports and are implementing preventive measures to help avoid similar issues in the future.
Scope of impact: Any admin expecting reports from the affected scenarios as outlined in the More info section may be affected.
Start time: Friday, August 21, 2026, at 12:00 AM UTC
Next update by: Monday, August 31, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Aug 26 11:33:13 2026 |
|---|
| Description: | Title: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights
User impact: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights.
More info: Affected reports include but aren't limited to:
- Copilot Usage report in Microsoft 365 admin center
- Copilot Chat Usage report in Microsoft 365 admin center
- Copilot Readiness reports in Microsoft 365 admin center and Viva Insights
- Copilot Adoption report in Viva Insights
- Microsoft 365 Apps and Active users reports in Microsoft 365 admin center
- Teams App reports in Microsoft 365 admin center and Microsoft Teams admin center
Current status: We're continuing to make upstream data pipeline adjustments and report migrations to address the remaining reporting delays. We'll provide a timeline for remediation as soon as one becomes available.
Scope of impact: Any admin expecting reports from the affected scenarios as outlined in the More info section may be affected.
Start time: Friday, August 21, 2026, at 12:00 AM UTC
Next update by: Thursday, August 27, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Aug 25 11:56:45 2026 |
|---|
| Description: | Title: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights
User impact: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights.
More info: Affected reports include, but aren't limited to:
- Copilot Usage report in Microsoft 365 admin center
- Copilot Chat Usage report in Microsoft 365 admin center
- Copilot Readiness reports in Microsoft 365 admin center and Viva Insights
- Copilot Adoption report in Viva Insights
- Microsoft 365 Apps and Active users reports in Microsoft 365 admin center
- Teams App reports in Microsoft 365 admin center and Microsoft Teams admin center
Current status: We're progressing with our upstream data pipeline adjustments to address the remaining reporting delays admins are encountering. Copilot Usage and Copilot Chat Usage reports delays have subsided and we're completing our mitigations for Copilot Readiness reports, Copilot Adoption reports, Microsoft 365 App & Active user reports, and Teams App reports. We're expecting an estimated timeline for the remediation of the impact for all reports will be available by our next scheduled communication update.
Scope of impact: Any admin expecting reports from the affected scenarios as outlined in the More info section may be affected.
Start time: Friday, August 21, 2026, at 12:00 AM UTC
Next update by: Wednesday, August 26, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 13:53:52 2026 |
|---|
| Description: | Title: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights
User impact: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights.
More info: Affected reports include, but aren't limited to:
- Copilot Usage report in Microsoft 365 admin center
- Copilot Chat Usage report in Microsoft 365 admin center
- Copilot Readiness reports in Microsoft 365 admin center and Viva Insights
- Copilot Adoption report in Viva Insights
- Microsoft 365 Apps and Active users reports in Microsoft 365 admin center
- Teams App reports in Microsoft 365 admin center and Microsoft Teams admin center
Current status: We've begun the process of applying mitigations for the report latency, and have confirmed that Copilot Usage and Copilot Chat Usage reports have recovered thanks to these mitigations. We're recovering the remaining impacted reports, and will provide an updated timeline for full remediation as soon as one becomes available.
Scope of impact: Any admin expecting reports from the affected scenarios as outlined in the More info section may be affected.
Start time: Friday, August 21, 2026, at 12:00 AM UTC
Next update by: Tuesday, August 25, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Aug 21 13:31:50 2026 |
|---|
| Description: | Title: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights
User impact: Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights.
More info: Affected reports include, but aren't limited to:
- Copilot Usage report in Microsoft 365 admin center
- Copilot Chat Usage report in Microsoft 365 admin center
- Copilot Readiness reports in Microsoft 365 admin center and Viva Insights
- Copilot Adoption report in Viva Insights
- Microsoft 365 Apps and Active users reports in Microsoft 365 admin center
- Teams App reports in Microsoft 365 admin center and Microsoft Teams admin center
Current status: Our monitoring has identified an increase report generation delays and our investigation has identified that an upstream component that facilitates report data access and generation isn't responding as expected, resulting in impact. We're in the process of identifying the underlying cause of impact and develop a remediation strategy.
Scope of impact: Any admin expecting reports from the affected scenarios as outlined in the More info section may be affected.
Start time: Friday, August 21, 2026, at 12:00 AM UTC
Next update by: Monday, August 24, 2026, at 7: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 Oct 14 14:43:45 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 21, 2026, at 7:30 PM UTC |
|---|
|
Details
| Time: | Wed Oct 14 14:43: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.
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 gathered additional diagnostic data through our internal reproduction of the issue and are reviewing our findings to further isolate the underlying cause and determine appropriate remediation actions. 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, October 21, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Oct 7 14:37: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: We’re continuing our internal reproduction efforts to collect additional diagnostic data and further isolate why the impact persists in specific environments to formulate the 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 14, 2026, at 7:30 PM UTC
|
|---|
|
| 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.
|
|---|
|
MP1507695 - Admins may encounter delays in accessing audit log data results in Microsoft Purview
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Oct 14 12:14:28 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 14 12:46:57 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Wednesday, October 21, 2026, at 6:00 PM UTC |
|---|
|
Details
| Time: | Wed Oct 14 12:46:57 2026 |
|---|
| Description: | Title: Admins may encounter delays in accessing audit log data results in Microsoft Purview
User impact: Admins may encounter delays in accessing audit log data results in Microsoft Purview.
More info: Affected users are encountering delays when accessing audit log data from the Microsoft Purview portal, Microsoft Graph API, or PowerShell.
Current status: Our monitoring identified an increase in processing latency with Microsoft Purview audit log data. We've analyzed service telemetry and determined that a dependent service isn't processing requests as efficiently as expected, resulting in impact. We've taken action to rebalance load and improve throughput. While most users should see relief, we're continuing to monitor as the remaining backlog of events are processed, and we'll provide a complete remediation timeline once available.
Scope of impact: Any admin accessing audit log data from Microsoft Purview may be affected.
Next update by: Wednesday, October 21, 2026, at 6:00 PM UTC
|
|---|
|
PB1507645 - Some users encounter intermittent failures when refreshing datasets in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 14 11:10:45 2026 |
|---|
| End Time: | Wed Oct 14 11:42:22 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 14 11:50:14 2026 |
|---|
| Root Cause: | A portion of infrastructure that facilitates dataset access encountered a cache refresh service that wasn't operating as expected, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 14 11:47:44 2026 |
|---|
| Description: | Title: Some users encountered intermittent failures when refreshing datasets in Power BI
User impact: Users encountered intermittent failures when refreshing datasets in Power BI.
Final status: Our monitoring identified an increase in dataset refresh errors. We reviewed service telemetry and found that a portion of infrastructure that facilitates dataset access encountered an increase in CPU utilization due to a cache refresh service that wasn't operating as expected. Our automated services restarted the impacted nodes, and we confirmed mitigation using service telemetry.
Scope of impact: Your organization was impacted by this event, and some users attempting to refresh datasets in Power BI were intermittently affected.
Start time: Wednesday, October 14, 2026, at 2:00 PM UTC
End time: Wednesday, October 14, 2026, at 2:25 PM UTC
Root cause: A portion of infrastructure that facilitates dataset access encountered a cache refresh service that wasn't operating as expected, resulting in impact.
Next steps:
- We're continuing our analysis of the service telemetry while monitoring the environment to better identify and prevent similar issues in the future.
This is the final update for this event.
|
|---|
|
| Time: | Wed Oct 14 11:15:40 2026 |
|---|
| Description: | Title: Some users encounter intermittent failures when refreshing datasets in Power BI
User impact: Users encountered intermittent failures when refreshing datasets in Power BI.
Current status: We've investigated a problem with the Power BI service in which users experienced dataset refresh failures, 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.
|
|---|
|
EX1500900 - Admins are unable to access the Exchange admin center (EAC)
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Oct 12 04:15:00 2026 |
|---|
| End Time: | Mon Oct 12 08:50:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Oct 14 09:11:27 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 14 09:11:27 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 14 09:11:13 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Oct 12 09:28:40 2026 |
|---|
| Description: | Title: Admins are unable to access the Exchange admin center (EAC)
User impact: Admins are unable to access the EAC.
More info: When attempting to access the Exchange admin center, affected admins encountered an “Internal Server Error” message.
Final status: We've completed the rollback of the identified Exchange admin center (EAC) change. Service telemetry shows that errors have returned to expected levels, and user reports have confirmed that EAC access has been restored. Admins who continue to experience impact should close their existing EAC browser session, open a new session, and retry accessing the EAC. We’ll continue to monitor service health to ensure sustained service stability.
Scope of impact: Impact was specific to admins attempting to access the EAC.
Start time: Monday, October 12, 2026, at 8:15 AM UTC
End time: Monday, October 12, 2026, at 12:50 PM UTC
Preliminary root cause: A recent EAC configuration change resulted in unexpected HTTP responses within the affected request path, preventing admins from successfully accessing the EAC. Reverting the identified change restored expected service functionality.
Next steps:
- We’re reviewing the identified EAC change and associated service configuration to help prevent similar impact from recurring.
- We’re reviewing our monitoring and telemetry to improve detection and alerting for similar service behavior.
We’ll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Oct 12 09:04:24 2026 |
|---|
| Description: | We’ve completed the rollback and are continuing to monitor service health, with telemetry showing errors trending downward from their earlier peak. Admins who continue to experience impact should close their existing Exchange admin center (EAC) browser session, open a new session, and retry accessing the EAC. We’ll continue monitoring to validate recovery.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, October 12, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Oct 12 08:50:57 2026 |
|---|
| Description: | We’re continuing to roll back the identified Exchange admin center (EAC) change. Initial telemetry shows errors trending downward from their earlier peak, and we’re monitoring service health to determine whether the rollback restores access for affected admins.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, October 12, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Oct 12 08:23:27 2026 |
|---|
| Description: | Title: Admins are unable to access the Exchange admin center (EAC)
User impact: Admins are unable to access the EAC.
More info: When attempting to access the Exchange admin center, admins encounter an “Internal Server Error” message.
Current status: Our testing has identified a recent Exchange admin center (EAC) configuration change as a potential contributor to the access failures and associated HTTP 302 redirects. We’re rolling back the change, which we expect to complete within approximately two hours. Once complete, we’ll monitor the environment to determine whether this resolves the impact.
Scope of impact: Impact may be specific to any admin attempting to access the EAC. This information may be updated as our investigation continues.
Next update by: Monday, October 12, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Oct 12 08:01:41 2026 |
|---|
| Description: | We’re continuing to test the rollback of the recent Exchange admin center (EAC) change while monitoring the results to determine if this resolves the impact. In parallel, we’re continuing our analysis of the unexpected HTTP 302 redirects to help determine the source of the issue.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, October 12, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Oct 12 07:21:48 2026 |
|---|
| Description: | Title: Admins are unable to access the Exchange admin center (EAC)
User impact: Admins are unable to access the EAC.
More info: When attempting to access the Exchange admin center, admins encounter an “Internal Server Error” message.
Current status: We’re continuing to investigate the unexpected HTTP 302 redirects and are testing a rollback of a recent Exchange admin center (EAC) change to determine if this resolves the impact. We’re also comparing results across affected environments to determine our next steps.
Scope of impact: Impact may be specific to any admin attempting to access the EAC. This information may be updated as our investigation continues.
Next update by: Monday, October 12, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Mon Oct 12 06:53:19 2026 |
|---|
| Description: | We’ve identified unexpected 302 redirect errors during affected Exchange admin center (EAC) access attempts and are analyzing diagnostic logs to isolate the source of the access failures. While we continue our investigation, admins remain unable to access the EAC, with no workaround currently available.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, October 12, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Mon Oct 12 06:19:37 2026 |
|---|
| Description: | Title: Admins are unable to access the Exchange admin center (EAC)
User impact: Admins are unable to access the EAC.
More info: When attempting to access the Exchange admin center, affected admins may encounter an “Internal Server Error” message.
Current status: We’re reviewing service logs and analyzing available diagnostic data to identify the source of the issue and determine next steps.
Scope of impact: Impact may be specific to any admin attempting to access the EAC. This information may be updated as our investigation continues.
Next update by: Monday, October 12, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Mon Oct 12 05:37:21 2026 |
|---|
| Description: | Title: Some admins may be unable to access the Exchange admin center (EAC)
User impact: Admins may be unable to access the EAC.
More info: When attempting to access the Exchange admin center, affected admins may encounter an “Internal Server Error” message.
Current status: When attempting to access the Exchange admin center, affected admins may encounter an “Internal Server Error” message.
Scope of impact: Impact may be specific to any admin attempting to access the EAC. This information may be updated as our investigation continues.
Next update by: Monday, October 12, 2026, at 11:30 AM UTC
|
|---|
|
PB1505699 - Users may have been unable to view chart data on Power BI dashboards when using standard light or dark themes
| Status: | serviceRestored |
|---|
| Start Time: | Sun Sep 27 09:10:00 2026 |
|---|
| End Time: | Tue Oct 13 20:00:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI and Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 14 05:28:37 2026 |
|---|
| Root Cause: | A recent Power BI service update introduced a code regression that caused dashboard theme settings to incorrectly override the visual formatting of some pinned Cartesian charts, resulting in incorrect chart rendering.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 14 05:28:24 2026 |
|---|
| Description: | Title: Users may have been unable to view chart data on Power BI dashboards when using standard light or dark themes
User impact: Users may have been unable to view chart data on Power BI dashboards when using standard light or dark themes.
Final status: We've determined that a recent Power BI update introduced a code regression that caused dashboard theme settings to incorrectly override the visual formatting of some pinned Cartesian charts, resulting in incorrect chart rendering. We’ve completed deployment of the fix and confirmed that the affected functionality has been restored and impact is no longer occurring.
Scope of impact: Impact was specific to any user attempting to view data on a Cartesian chart pinned to the Power BI dashboard with standard light theme or dark theme enabled.
Start time: Sunday, September 27, 2026, at 1:10 PM UTC
End time: Wednesday, October 14, 2026, at 12:00 AM UTC
Root cause: A recent Power BI service update introduced a code regression that caused dashboard theme settings to incorrectly override the visual formatting of some pinned Cartesian charts, resulting in incorrect chart rendering.
Next steps:
- We’re reviewing our update procedures to help identify similar visual-rendering issues before deployment and prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 13 12:07:27 2026 |
|---|
| Description: | Title: Users may not see chart data when using standard light or dark themes on Power BI dashboards
User impact: Users may not have seen chart data when using standard light or dark themes on Power BI dashboards.
Current status: We've completed development of the fix, and we're initializing the deployment. We'll provide a timeline for remediation as one becomes available, and our investigation to confirm what's causing the persistent impact is ongoing.
Scope of impact: This issue may have impacted any user who was attempting to view data on a cartesian chart pinned to the Power BI dashboard with standard light theme or dark theme enabled. This section may be updated as our investigation continues.
Next update by: Wednesday, October 14, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Oct 13 00:02:38 2026 |
|---|
| Description: | Title: Users may not see chart data when using standard light or dark themes on Power BI dashboards
User impact: Users may not have seen chart data when using standard light or dark themes on Power BI dashboards.
Current status: We've identified that impact communicated in PB1489649 persists. We're working on developing a new fix that we suspect will complete by Tuesday, October 13, 2026. At that time we'll also aim to provide details on the root cause into what caused the impact to persist.
Scope of impact: This issue may have impacted any user who was attempting to view data on a cartesian chart pinned to the Power BI dashboard with standard light theme or dark theme enabled. This section may be updated as our investigation continues.
Next update by: Tuesday, October 13, 2026, at 5:00 PM UTC
|
|---|
|
IT1506313 - Admin may see status cards displaying "Unknown" instead of the expected summary counts in Intune admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 6 19:17:00 2026 |
|---|
| End Time: | Tue Oct 13 17:51:07 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Oct 13 17:58:07 2026 |
|---|
| Root Cause: | An incorrectly scoped Microsoft Graph flight changed the response format for batch requests across production. Some Intune UX experiences (Home, Apps, Devices, Troubleshooting) rely on the previous Base64-encoded behavior and couldn't parse the JSON response, resulting in status cards displaying "Unknown."
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 13 17:58:03 2026 |
|---|
| Description: | Title: Admin may see status cards displaying "Unknown" instead of the expected summary counts in Intune admin center
User impact: Admin may have seen status cards displaying "Unknown" instead of the expected summary counts in Intune admin center.
More info: Admins were impacted when accessing the Home, Apps, Devices, and Troubleshooting Blades.
As a workaround, admins could have clicked the "Unknown" status, which allowed access to the data.
Final status: Following our change reversion process, our internal service telemetry has verified that the impact has been remediated.
Scope of impact: This issue might have affected any admin who accessed the Intune admin center from Home, Apps, Devices, and Troubleshooting Blades.
Start time: Tuesday, October 6, 2026, at 11:17 PM UTC
End time: Tuesday, October 13, 2026, at 9:29 PM UTC
Root cause: An incorrectly scoped Microsoft Graph flight changed the response format for batch requests across production. Some Intune UX experiences (Home, Apps, Devices, Troubleshooting) rely on the previous Base64-encoded behavior and couldn't parse the JSON response, resulting in status cards displaying "Unknown."
Next steps:
- We're further analyzing the offending misconfigured service update to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 13 17:00:08 2026 |
|---|
| Description: | Title: Admin may see status cards displaying "Unknown" instead of the expected summary counts in Intune admin center
User impact: Admin may see status cards displaying "Unknown" instead of the expected summary counts in Intune admin center.
More info: Admins are impacted when accessing the Home, Apps, Devices, and Troubleshooting Blades.
As a workaround, admins can click the "Unknown" status, which will allow access to the data.
Current status: We've identified a recent misconfigured service update that is producing unexpected status card displays for admins in the Intune admin center. We're conducting our change reversion process to remove the offending change and to remediate the impact.
Scope of impact: This issue may affect any admin accessing the Intune admin center from Home and Troubleshooting Blades.
Root cause: An incorrectly scoped Microsoft Graph flight changed the response format for batch requests across production. Some Intune UX experiences (Home, Apps, Devices, Troubleshooting) rely on the previous Base64-encoded behavior and can't parse the JSON response, resulting in status cards displaying "Unknown."
Next update by: Tuesday, October 13, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Oct 13 15:27:04 2026 |
|---|
| Description: | Title: Admin may see status cards displaying "Unknown" instead of the expected summary counts in Intune admin center
User impact: Admin may see status cards displaying "Unknown" instead of the expected summary counts in Intune admin center.
More info: Admins are impacted when accessing the Home and Troubleshooting Blades.
As a workaround, admins can click the "Unknown" status, which will allow access to the data.
Current status: We've identified an issue that is preventing expected status cards for admins accessing the Home and Troubleshooting Blades in the Intune admin center. We're analyzing system logging and recent updates to the service, as we isolate the source for this event and determine our next troubleshooting steps for remediating the impact.
Scope of impact: This issue may affect any admin accessing the Intune admin center from Home and Troubleshooting Blades.
Next update by: Tuesday, October 13, 2026, at 9:30 PM UTC
|
|---|
|
MO1506255 - Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 12 17:54:00 2026 |
|---|
| End Time: | Tue Oct 13 15:35:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Oct 13 16:58:23 2026 |
|---|
| Root Cause: | A recent service update introduced a misconfiguration which caused the Service Health and Communications API to return authentication errors, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 13 16:58:04 2026 |
|---|
| Description: | Title: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center
User impact: Admins may have been unable to review Service health or Message center postings in the Microsoft 365 admin center.
More info: Admins' "What's new" tab in the Microsoft Teams admin center may have been blank and displayed an error stating, "We can't load data. Try again."
Final status: We've completed our monitoring period and validated that the rollback of the service update containing the misconfiguration successfully remediated impact.
Scope of impact: This issue affected some admins attempting to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center.
Start time: Monday, October 12, 2026, at 9:54 PM UTC
End time: Tuesday, October 13, 2026, at 7:35 PM UTC
Root cause: A recent service update introduced a misconfiguration which caused the Service Health and Communications API to return authentication errors, resulting in impact.
Next steps:
- We're analyzing the offending service update to determine why the potential for impact wasn't caught during our internal update testing and validation phases. This further analysis will help us to improve our update implementation processes moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 13 15:45:26 2026 |
|---|
| Description: | Title: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center
User impact: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center.
More info: Users may also see nothing in the "What's new" tab in the Microsoft Teams admin center and are returned an error stating "We can't load data. Try again."
Current status: We're continuing to monitor recovery, and we anticipate some users will start to see remediation at this time. To ensure impact is fully remediated, we've extended our monitoring period, and we anticipate impact to be resolved by our next scheduled update.
Scope of impact: This issue affects some admins who may be unable to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. This section may be updated as the investigation progresses.
Start time: Monday, October 12, 2026, at 9:54 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by Tuesday, October 13, 2026, at 10:00 PM UTC.
Root cause: A recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact.
Next update by: Tuesday, October 13, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Oct 13 14:53:13 2026 |
|---|
| Description: | Title: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center
User impact: Admins may be unable to review Service health or Message center postings in the Microsoft 365 admin center.
More info: Users may also see nothing in the "What's new" tab in the Microsoft Teams admin center and are returned an error stating "We can't load data. Try again."
Current status: We've received reports from a subset of affected users who have reported that they are unable to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. We've isolated that a recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact. We're rolling back the offending update and monitoring for remediation. We anticipate impact to be resolved by our next scheduled update.
Scope of impact: This issue affects some admins who may be unable to review Service health or Message center postings in the Microsoft 365 admin center or see new activities in the “What’s new” tab in the Microsoft Teams admin center. This section may be updated as the investigation progresses.
Start time: Monday, October 12, 2026, at 9:54 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by Tuesday, October 13, 2026, at 8:00 PM UTC.
Root cause: A recent service update introduced a misconfiguration which causes the Service Health and Communications API to return authentication errors, resulting in impact.
Next update by: Tuesday, October 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Oct 13 14:27:32 2026 |
|---|
| Description: | Title: Admins may be unable to review Service health postings in the Microsoft 365 admin center
User impact: Admins may be unable to review Service health postings in the Microsoft 365 admin center.
Current status: We're investigating a potential issue with the Microsoft 365 suite and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1489450 - Some users may experience intermittent audio and video degradation when using Microsoft Teams through VDI 2.0
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 1 08:00:00 2026 |
|---|
| End Time: | Tue Oct 6 19:10:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Oct 13 13:07:05 2026 |
|---|
| Root Cause: | A recent configuration update to the VDI Bridge component responsible for VDI optimization introduced a regression, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 13 11:58:55 2026 |
|---|
| Description: | Title: Some users may experience intermittent audio and video degradation when using Microsoft Teams through VDI 2.0
User impact: Users may have experienced intermittent audio and video degradation when using Microsoft Teams through VDI 2.0
More info: Users also intermittently may have been unable to leverage certain feature optimizations provided by VDI 2.0
As a workaround, users could have restarted Microsoft Teams to resolve the issue.
Final status: We've monitored service health telemetry for an extended period and confirmed that the impact has been remediated on build version 26246.1604.5133.838. We recommend any user still facing impact to download this specific build version to apply the remediation.
Scope of impact: Users who were using Microsoft Teams VDI 2.0 in a Citrix VDI environment may have been impacted.
Start time: Thursday, October 1, 2026, at 12:00 PM UTC
End time: Tuesday, October 6, 2026, at 11:10 PM UTC
Root cause: A recent configuration update to the VDI Bridge component responsible for VDI optimization introduced a regression, resulting in impact.
Next steps:
- We're reviewing the impacting configuration update to understand why impact to audio and video quality wasn't identified during our pre-deployment testing processes. This investigation will help us to prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 12 13:07:48 2026 |
|---|
| Description: | Title: Some users may experience intermittent audio and video degradation when using Microsoft Teams through VDI 2.0
User impact: Users may experience intermittent audio and video degradation when using Microsoft Teams through VDI 2.0
More info: Users also intermittently may be unable leverage certain feature optimization provided by VDI 2.0
As a workaround, users can restart Teams to resolve the issue.
Current status: We're seeing continued success from our mitigation of moving users to a specific build version that doesn't contain the regression, and more monitoring time is needed to ensure this provides a stable resolution for users.
Scope of impact: Users who are using Microsoft Teams VDI 2.0 in a Citrix VDI environment may be impacted.
Root cause: A recent configuration update to the VDI Bridge component responsible for VDI optimization introduced a regression, resulting in impact.
Next update by: Tuesday, October 13, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Oct 9 10:55:32 2026 |
|---|
| Description: | Title: Some users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment
User impact: Users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment.
More info: Users may experience audio and video quality degradation, and unavailability of certain features.
As a workaround, users can restart Teams to resolve the issue.
Current status: We’ve implemented an interim mitigation to provide immediate relief and have observed initial signs of improvement. However, we’re continuing to monitor its effectiveness while progressing with validation of a longer-term fix before proceeding with deployment.
Scope of impact: Some users who are attempting to utilize VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment may be impacted.
Root cause: A recent configuration update to the VDI Bridge component responsible for VDI optimisation introduced a regression, resulting in impact.
Next update by: Monday, October 12, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Oct 8 10:22:58 2026 |
|---|
| Description: | Title: Some users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment
User impact: Users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment.
More info: Users may experience audio and video quality degradation, and unavailability of certain features.
As a workaround, users can restart Teams to resolve the issue.
Current status: We’re proceeding to validate the fix before deploying it to the affected infrastructure. Once available, we’ll provide a deployment timeline.
Scope of impact: Some users who are attempting to utilize VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment may be impacted.
Root cause: A recent configuration update to the VDI Bridge component responsible for VDI optimisation introduced a regression, resulting in impact.
Next update by: Friday, October 9, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 12:45:37 2026 |
|---|
| Description: | Title: Some users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment
User impact: Users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment.
More info: Users may experience audio and video quality degradation, and unavailability of certain features.
As a workaround, users can restart Teams to resolve the issue.
Current status: We’re continuing to validate the fix before deploying it to the affected infrastructure. Once available, we’ll provide a deployment timeline.
Scope of impact: Some users who are attempting to utilize VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment may be impacted.
Root cause: A recent configuration update to the VDI Bridge component responsible for VDI optimisation introduced a regression, resulting in impact.
Next update by: Thursday, October 8, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 04:59:15 2026 |
|---|
| Description: | Title: Some users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment
User impact: Users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment.
More info: Users may experience audio and video quality degradation, and unavailability of certain features.
As a workaround, users can restart Teams to resolve the issue.
Current status: We’ve identified that a recent configuration update to the VDI Bridge component responsible for VDI optimisation introduced a regression, resulting in impact. We’ve developed a fix and are currently validating it before deploying it to the affected infrastructure. We expect to provide a deployment timeline by our next scheduled update.
Scope of impact: Some users who are attempting to utilize VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment may be impacted.
Root cause: A recent configuration update to the VDI Bridge component responsible for VDI optimisation introduced a regression, resulting in impact.
Next update by: Wednesday, October 7, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Oct 6 12:59:31 2026 |
|---|
| Description: | Title: Some users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment
User impact: Users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment.
More info: Users may experience audio and video quality degradation, and unavailability of certain features.
As a workaround, users can restart Teams to resolve the issue.
Current status: As we progress with our root cause analysis and isolate the source for this event, we've isolated an offending code regression that is believed to be producing the problems. We've internally validated a solution that is expected to remediate the impact. We're deploying our solution, and we'll provide an updated timeline for its deployment once it has become available.
Scope of impact: Some users who are attempting to utilize VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment may be impacted.
Next update by: Wednesday, October 7, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Oct 6 09:20:51 2026 |
|---|
| Description: | Title: Some users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment
User impact: Users may encounter intermittent VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment.
More info: Users may experience audio and video quality degradation, and unavailability of certain features.
As a workaround, users can restart Teams to resolve the issue.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Some users who are attempting to utilize VDI2 optimization loss when using Microsoft Teams in a Citrix VDI environment may be impacted.
Next update by: Tuesday, October 6, 2026, at 5:30 PM UTC
|
|---|
|
MO1505181 - Email notifications from Microsoft 365 services are being throttled in your tenant
| Status: | investigationSuspended |
|---|
| Start Time: | Mon Oct 12 18:19:26 2026 |
|---|
| End Time: | Tue Oct 13 09:43:40 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Oct 13 09:43:41 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 13 09:43:41 2026 |
|---|
| Description: | Title: Email notifications from Microsoft 365 services are being throttled in your tenant
User Impact: Emails that are generated by interacting with products within Microsoft 365 will not be sent to users.
Final Status: System monitoring indicated that access to the service in your environment had returned to normal health.
Start time: Monday, October 12, 2026, at 10:19 PM UTC
End time: Tuesday, October 13, 2026, at 1:43 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 12 18:24:30 2026 |
|---|
| Description: | Title: Email notifications from Microsoft 365 services are being throttled in your tenant
User impact: Emails that are generated by interacting with products within Microsoft 365 will not be sent to users.
More info: The affected email notifications may include but are not limited to the following examples:
- File sharing email notifications for OneDrive for Business, or Microsoft 365 apps
- Site sharing email notifications for SharePoint Online
- News post notifications within SharePoint Online
- Comments, mentions in Office documents
Current status: Our monitoring has detected unusual spikes in notification activity in your tenant. In order to protect users, our automated systems have disabled email notifications that are generated through interaction with products in Microsoft 365.
|
|---|
|
TM1504581 - Users' Microsoft Teams contact cards may not fully display Out of office text
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Oct 12 17:18:48 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 12 19:56:40 2026 |
|---|
| Root Cause: | A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact.
|
|---|
| Next Update: | Monday, October 19, 2026, at 9:00 PM UTC |
|---|
|
Details
| Time: | Mon Oct 12 18:42:07 2026 |
|---|
| Description: | Title: Users' Microsoft Teams contact cards may not fully display Out of office text
User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.
More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.
Current status: We've identified that a recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact. We're deploying a fix to correct the value and remediate the impact. We'll provide a timeline for the completion of the deployment as one becomes available.
Scope of impact: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted.
Root cause: A recent service change to the Microsoft Teams contact cards introduced a code regression in which the user interface (UI) of the Out of office text contains an invalid value and is causing impact.
Next update by: Monday, October 19, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Oct 12 17:48:35 2026 |
|---|
| Description: | Title: Users' Microsoft Teams contact cards may not fully display Out of office text
User impact: Users' Microsoft Teams contact cards may not fully display Out of office text.
More info: Selecting “See more” may not display the full Out of office message. Users may hover over the message to see the full text in a tool tip.
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: Any user attempting to view Out of office text on Microsoft Teams contact cards may be impacted.
Next update by: Monday, October 12, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Oct 12 17:28:46 2026 |
|---|
| Description: | Title: Users' Microsoft Teams contact cards don't fully display Out of office text
User impact: Users' Microsoft Teams contact cards don't fully display Out of office text.
More info: Selecting “See more” doesn’t display the full Out of office message. Users may hover over the message to see the full text in a tool tip.
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.
|
|---|
|
MP1471821 - Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 14 12:41:47 2026 |
|---|
| End Time: | Mon Oct 12 12:28:30 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Oct 12 12:42:12 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: | N/A |
|---|
|
Details
| Time: | Mon Oct 12 12:42:08 2026 |
|---|
| Description: | Title: Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview
User impact: Admins may have received failures creating or updating Communications Compliance policies in Microsoft Purview.
More info: Impact was limited to Communications Compliance policies with more than four classifiers.
Final status: The fix deployed to the whole of the affected infrastructure, and we've confirmed with our internal monitoring telemetry that impact is remediated.
Scope of impact: Some admins may have received failures when they created or updated Communications Compliance policies in Microsoft Purview with more than four classifiers.
Start time: Monday, July 6, 2026, at 12:00 AM UTC
End time: Friday, October 9, 2026, at 6:00 PM UTC
Root cause: A service update which intended to add operations with larger data sizes introduced a code error, causing size limitation issues.
Next steps: We're reviewing and improving our service update validation procedure to prevent similar issues from occurring again in the future.
This is the final update for this event.
|
|---|
|
| Time: | Tue Oct 6 13:47:50 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.
Current status: We've completed the deployment to over 90 percent of the affected infrastructure. While most admins should see relief, we expect the release to complete by the next scheduled update.
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.
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: Monday, October 12, 2026, at 6:00 PM UTC
|
|---|
|
| 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.
|
|---|
|
OP1500833 - Users may have been unable to access or protect content using Azure Rights Management (ARM) in Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 12 03:00:00 2026 |
|---|
| End Time: | Mon Oct 12 06:21:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Oct 12 08:14:40 2026 |
|---|
| Root Cause: | A section of the ARM service infrastructure that facilitates the processing of cached service data was underperforming, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 12 08:13:43 2026 |
|---|
| Description: | Title: Users may have been unable to access or protect content using Azure Rights Management (ARM) in Microsoft 365 services
User impact: Users may have been unable to access or protect content using ARM in Microsoft 365 services.
More info: Impact may have prevented users from encrypting, decrypting, or opening protected files and email messages across Microsoft 365 services that rely on ARM. This included protection capabilities in Microsoft Purview, encrypted documents, protected file uploads and downloads in SharePoint Online, related Power BI and dependent service functionality, and publishing agents or adding skills to existing agents in Microsoft 365 Copilot Chat.
Final status: We’ve determined that a section of the ARM service infrastructure that facilitates the processing of cached service data was underperforming, resulting in impact. We’ve confirmed, following a period of monitoring service telemetry, that the mitigating actions successfully resolved the issue.
Scope of impact: Some users attempting to encrypt, decrypt, open, upload, or download protected content across Microsoft 365 services that rely on ARM, including Microsoft Purview and Power BI, or publish agents or add skills to existing agents in Microsoft 365 Copilot Chat, may have been impacted.
Start time: Monday, October 12, 2026, at 7:00 AM UTC
End time: Monday, October 12, 2026, at 10:21 AM UTC
Root cause: A section of the ARM service infrastructure that facilitates the processing of cached service data was underperforming, resulting in impact.
Next steps:
- We’re reviewing performance data and trends on the affected infrastructure to help prevent similar impact from happening again.
|
|---|
|
| Time: | Mon Oct 12 06:42:41 2026 |
|---|
| Description: | Title: Some users may be unable to access or protect content using Azure Rights Management (ARM) across Microsoft 365 services
User impact: Users may be unable to access or protect content using ARM across Microsoft 365 services.
More info: Impact may prevent users from encrypting, decrypting, or opening protected files and email messages across Microsoft 365 services that rely on ARM. This includes protection capabilities in Microsoft Purview, encrypted documents, protected file uploads and downloads in SharePoint Online, related Power BI and dependent service functionality, and publishing agents or adding skills to existing agents in Microsoft 365 Copilot Chat.
Current status: We’ve redirected traffic away from affected infrastructure to allow the unhealthy service components to recover. Following this action, we’ve observed service recovery across all affected regions. We’re monitoring service health to confirm that recovery remains stable while we continue investigating the root cause.
Scope of impact: Some users attempting to encrypt, decrypt, open, upload, or download protected content across Microsoft 365 services that rely on ARM, including Microsoft Purview and Power BI, or publish agents or add skills to existing agents in Microsoft 365 Copilot Chat, may be impacted.
Start time: Monday, October 12, 2026, at 7:00 AM UTC
Next update by: Monday, October 12, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Mon Oct 12 05:16:44 2026 |
|---|
| Description: | Title: Some users may be unable to access or protect content using Azure Rights Management (ARM) across Microsoft 365 services
User impact: Users may be unable to access or protect content using ARM across Microsoft 365 services.
More info: Impact may prevent users from encrypting or decrypting protected content, including files and email messages, across Microsoft 365 services that rely on ARM.
Current status: We’ve identified that some service components responsible for processing ARM requests are in an unhealthy state. We’re attempting to restart the affected components to mitigate impact. We’re seeing early signs of service recovery and are investigating the root cause while evaluating whether additional mitigation actions are required.
Scope of impact: Some users attempting to encrypt or decrypt content using Microsoft 365 services that rely on ARM may be impacted.
Next update by: Monday, October 12, 2026, at 11:30 AM UTC
|
|---|
|
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: | Tue Jul 7 13:33:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 12 04:34:59 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: | Monday, October 19, 2026, at 10:00 AM UTC |
|---|
|
Details
| Time: | Mon Oct 12 04:33:53 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: 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.
Current status: We’ve completed deployment of the fix to the initially affected service environment and expect this has remediated impact for users in that environment. The fix is continuing to propagate across the remaining affected environment, with this process expected to take approximately one additional week to complete. We’ll continue monitoring the deployment as it progresses to confirm that impact is fully remediated.
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.
Start time: Tuesday, July 7, 2026, at 5:33 PM UTC
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: Monday, October 19, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Oct 12 01:30:32 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: 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: Our fix deployment is completing for the initially identified service environment; however, we’ve confirmed that additional environments remain impacted. While some users should experience impact resolution as the fix reaches them, we’re extending the fix deployment to the remaining affected environments, and we’ll provide an estimation for its completion once available.
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: Monday, October 12, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Fri Oct 9 13:02:04 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: 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: Our fix deployment is completing and we're reaching out to some users to confirm the issue is no longer occurring.
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: Monday, October 12, 2026, at 7:00 AM UTC
|
|---|
|
| 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.
|
|---|
|
TM1488543 - Some users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 25 16:09:00 2026 |
|---|
| End Time: | Thu Oct 8 08:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 9 17:36:03 2026 |
|---|
| Root Cause: | A code mismatch in the components utilized when marking a Microsoft Teams emergency call as a multi-party call caused the code to mute participants to not be enabled as expected.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 9 17:34:54 2026 |
|---|
| Description: | Title: Some users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves
User impact: Users conferenced into a Microsoft Teams emergency call may not have been automatically muted or able to mute themselves.
Final status: We've confirmed that our fix has deployed as expected and that users are now automatically muted when or can mute themselves when they're conferenced in to a Microsoft Teams call.
Scope of impact: Users conferenced into a Microsoft Teams emergency call and attempting to mute their audio were affected by this issue.
Start time: Friday, September 25, 2026, at 8:09 PM UTC
End time: Thursday, October 8, 2026, at 12:00 PM UTC
Root cause: A code mismatch in the components utilized when marking a Microsoft Teams emergency call as a multi-party call caused the code to mute participants to not be enabled as expected.
Next steps:
- We're continuing to optimize Teams emergency calls for all user scenarios.
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 5 18:15:44 2026 |
|---|
| Description: | Title: Some users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves
User impact: Users conferenced into a Microsoft Teams emergency call may not be automatically muted or able to mute themselves.
More info: Users conferenced into a Microsoft Teams emergency call are also unable to mute themselves and would need to leave the call.
Current status: We've initiated deployment of our code change to address the code mismatch causing users to not be automatically muted as expected or being able to mute themselves in emergency calls. We anticipate deployment to be completed by Monday, October 12, 2026, and we aim to provide updates on our timeline to remediation as deployment progresses.
Scope of impact: Users conferenced into a Microsoft Teams emergency call and attempting to mute their audio are affected by this issue. This section may be updated as the investigation progresses.
Start time: Friday, September 25, 2026, at 8:09 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by Monday, October 12, 2026.
Root cause: A code mismatch in the components utilized when marking a Microsoft Teams emergency call as a multi-party call is causing the code to mute participants to not be enabled as expected.
Next update by: Friday, October 9, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Oct 5 17:18:00 2026 |
|---|
| Description: | Title: Some users conferenced into a Microsoft Teams E911 call may not be automatically muted or able to mute themselves
User impact: Users conferenced into a Microsoft Teams E911 call may not be automatically muted or able to mute themselves.
More info: Users conferenced into a Microsoft Teams E911 are also unable to mute themselves and would need to leave the call.
Current status: After analyzing correlation and meeting IDs provided by a subset of affected users, we've isolated a code mismatch in the components utilized when marking a Microsoft Teams call as a multi-party call is causing the code to mute participants to not be enabled as expected. We've expanded our communications to all potentially affected tenants and updated the "Title", "User impact" and "Scope of impact" fields of our communications to reflect this change as we begin rolling out a code change to remediate the mismatch.
Scope of impact: Users conferenced into a Microsoft Teams E911 call and attempting to mute their audio are affected by this issue. This section may be updated as the investigation progresses.
Start time: Friday, September 25, 2026, at 8:09 PM UTC
Root cause: A code mismatch in the components utilized when marking a Microsoft Teams call as a multi-party call is causing the code to mute participants to not be enabled as expected.
Next update by: Monday, October 5, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Mon Oct 5 16:23:18 2026 |
|---|
| Description: | Title: Some users conferenced into a Microsoft Teams E911 call may not be automatically muted or able to mute themselves
User impact: Users conferenced into a Microsoft Teams E911 call may not be automatically muted or able to mute themselves.
Current status: We're analyzing affected meeting and correlation IDs provided by a subset of affected users to further our understanding of the underlying impact scenario and to determine what our next troubleshooting steps should be.
Scope of impact: Users conferenced into a Microsoft Teams E911 call and attempting to mute their audio are affected by this issue. This section may be updated as the investigation progresses.
|
|---|
|
| Time: | Mon Oct 5 16:01:45 2026 |
|---|
| Description: | Title: Some users conferenced into a Microsoft Teams E911 call may not be automatically muted or able to mute themselves
User impact: Users conferenced into a Microsoft Teams E911 call may not be automatically muted or able to mute themselves.
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.
|
|---|
|
PB1489649 - Users may not see chart data when using standard light or dark themes on Power BI dashboards
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 6 15:32:12 2026 |
|---|
| End Time: | Fri Oct 9 15:01:10 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI and Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 9 15:08:34 2026 |
|---|
| Root Cause: | A recent code change intended to unify font colors was incorrectly applied to the background color property for cartesian charts pinned to the Power BI dashboard, resulting in the data on these charts being illegible.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 9 15:02:26 2026 |
|---|
| Description: | Title: Users may not see chart data when using standard light or dark themes on Power BI dashboards
User impact: Users may not have seen chart data when using standard light or dark themes on Power BI dashboards.
More info: This display issue impacted the appearance of cartesian charts only, such as bar charts and line charts. Custom themes weren't impacted.
Users could have chosen to keep the report theme when pinning charts or use any dashboard theme other than light mode or dark mode.
Final status: We've updated the Title, User impact, and scope of impact statements of this communication to reflect that this also affected standard dark mode themes. Afer mitigating the previously identified blockers in our deployment pipeline, we've confirmed that our fix has fully deployed as expected and all users can now see chart data on Power BI dashboards that use any theme.
Scope of impact: This issue may have impacted any user who was attempting to view data on a cartesian chart pinned to the Power BI dashboard with standard light theme or dark theme enabled.
Start time: Sunday, September 27, 2026, at 12:00 PM UTC
End time: Friday, October 9, 2026, at 6:00 AM UTC
Root cause: A recent code change intended to unify font colors was incorrectly applied to the background color property for cartesian charts pinned to the Power BI dashboard, resulting in the data on these charts being illegible.
Next steps:
- We're continuing to develop important visual upgrades while optimizing our quality assurance checks to ensure a smooth user experience.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 8 15:48:35 2026 |
|---|
| Description: | Title: Users may not see chart data when using standard light or dark themes on Power BI dashboards
User impact: Users may not see chart data when using standard light or dark themes on Power BI dashboards.
More info: This display issue impacts the appearance of cartesian charts only, such as bar charts and line charts.
As we develop our long-term remediation, users can choose to keep the report theme when pinning charts or use any dashboard theme other than light mode.
Current status: We've encountered some blockers within our deployment pipelines, which we’re currently addressing, and it's taking longer than initially expected. We'll provide a mitigation timeline once available.
Scope of impact: This issue may impact any user who was attempting to view data on a cartesian chart pinned to the Power BI dashboard with standard light theme or dark theme enabled. This information may be updated as our investigation continues.
Next update by: Friday, October 9, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Oct 7 15:33:17 2026 |
|---|
| Description: | Title: Users may not see chart data when using standard light or dark themes on Power BI dashboards
User impact: Users may not see chart data when using standard light or dark themes on Power BI dashboards.
More info: This display issue impacts the appearance of cartesian charts only, such as bar charts and line charts.
As we develop our long-term remediation, users can choose to keep the report theme when pinning charts or use any dashboard theme other than light mode.
Current status: We've completed development of the long-term fix for this issue, and we're expediting the process to deploy it to the affected environment. We anticipate the solution will be fully deployed by the time of our next scheduled update, and the results will aid in confirming the root cause.
Scope of impact: This issue may impact any user who was attempting to view data on a cartesian chart pinned to the Power BI dashboard with standard light theme or dark theme enabled. This information may be updated as our investigation continues.
Next update by: Thursday, October 8, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 6 16:03:25 2026 |
|---|
| Description: | Title: Users may not see chart data when using standard light or dark themes on Power BI dashboards
User impact: Users may not see chart data when using standard light or dark themes on Power BI dashboards.
More info: This display issue impacts the appearance of cartesian charts only, such as bar charts and line charts.
As we develop our long-term remediation, users can choose to keep the report theme when pinning charts or use any dashboard theme other than light mode.
Current status: We've identified that a recent code change has resulted in all data in charts pinned to the Power BI dashboard when choosing the light theme for chart display to show as black. We're developing a long-term fix for this issue, which we expect to be available by the time of our next scheduled communications update.
Scope of impact: This issue may impact any user who was attempting to view data on a cartesian chart pinned to the Power BI dashboard with standard light theme or dark theme enabled. This information may be updated as our investigation continues.
Next update by: Friday, October 16, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Oct 6 15:38:03 2026 |
|---|
| Description: | Title: Users may not see chart data when using standard light or dark themes on Power BI dashboards
User impact: Users may not see chart data when using standard light or dark themes on Power BI dashboards.
Current status: We're investigating an issue with chart data visibility when using the light Power BI dashboard theme and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1492711 - Some users may be unable to access Microsoft Teams transcripts and recordings
| Status: | serviceRestored |
|---|
| Start Time: | Fri Oct 9 09:42:43 2026 |
|---|
| End Time: | Fri Oct 9 13:32:56 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 9 13:33:07 2026 |
|---|
| Root Cause: | A recent standard service update introduced a regression which resulted in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 9 13:33:02 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Teams transcripts and recordings
User impact: Users may have been unable to access Microsoft Teams transcripts and recordings.
More info: Users may have been unable to access Microsoft Teams transcripts and recordings through Microsoft Graph API. Meeting-minutes and sales-visit-summary services may have been unavailable. Meetings since 9 October 2026 at 8:10 AM UTC may not have been processed, and change notifications may have stopped. Users may also have experienced issues with /aiInsights (meeting AI summary) APIs.
Final status: After a period of monitoring service telemetry, we've validated that reverting the service update which introduced a regression has remediated the impact.
Scope of impact: Impact was specific to some users who attempted to access Microsoft Teams transcripts and recordings.
Start time: Friday, October 9, 2026, at 8:10 AM UTC
End time: Friday, October 9, 2026, at 2:40 PM UTC
Root cause: A recent standard service update introduced a regression which resulted in the impact.
Next steps:
- We're evaluating our service update protocols to ensure similar regressions are identified and corrected ahead of deployments to prevent this from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Fri Oct 9 11:53:57 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Teams transcripts and recordings
User impact: Users may be unable to access Microsoft Teams transcripts and recordings.
More info: Users may be unable to access Microsoft Teams transcripts and recordings through Microsoft Graph API. Meeting-minutes and sales-visit-summary services may be unavailable. Meetings since 9 October 2026 at 8:10 AM UTC may not be processed, and change notifications may have stopped. Users may also experience issues with /aiInsights (meeting AI summary) APIs.
Current status: We've identified that our latest standard service update may have contained a regression that is causing impact. We're reverting this service update to the last previous known working as an initial mitigation step and are monitoring service telemetry to validate its success in fixing the issue.
Scope of impact: Impact is specific to some users who may be attempting to access Microsoft Teams transcripts and recordings. This section may be updated as our investigation continues.
Next update by: Friday, October 9, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Oct 9 10:20:52 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Teams transcripts and recordings
User impact: Users may be unable to access Microsoft Teams transcripts and recordings.
More info: Users may be unable to access Microsoft Teams transcripts and recordings through Microsoft Graph API. Meeting-minutes and sales-visit-summary services may be unavailable. Meetings since 9 October 2026 at 8:10 AM UTC may not be processed, and change notifications may have stopped. Users may also experience issues with /aiInsights (meeting AI summary) APIs.
Current status: We're reviewing diagnostic logs to formulate our next steps of our investigation to validate a root cause hypothesis.
Scope of impact: Impact is specific to some users who may be attempting to access Microsoft Teams transcripts and recordings.
Next update by: Friday, October 9, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri Oct 9 09:46:18 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft Teams transcripts and recordings
User impact: Users are unable to access Microsoft Teams transcripts and recordings.
More info: Users are unable to access Microsoft Teams transcripts and recordings through Microsoft Graph API. Meeting-minutes and sales-visit-summary services are unavailable. Meetings since 9 October 2026 at 8:10 AM UTC aren't being processed, and change notifications have stopped.
Current status: We're reviewing support case details to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and users attempting to access Microsoft Teams transcripts and recordings are impacted.
Next update by: Friday, October 9, 2026, at 4:00 PM UTC
|
|---|
|
MO1480956 - Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 22 09:21:00 2026 |
|---|
| End Time: | Fri Oct 9 13:25:47 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Oct 9 13:27:43 2026 |
|---|
| Root Cause: | We determined that a transient connectivity disruption in between the service and its caching layer resulted in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Oct 9 13:27:39 2026 |
|---|
| Description: | Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
User impact: Users may have been unable to make changes to page distribution or review work in OneNote and OneNote for the web.
More info: Users may have received an error message that read "waiting to start" that didn't resolve when attempting the affected actions.
Final status: Our fix has completed its deployment, and we've confirmed that this has resolved the issue though monitoring service health telemetry.
Scope of impact: This issue may have impacted some users attempting to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web.
Start time: Wednesday, July 22, 2026, at 1:21 PM UTC
End time: Thursday, October 8, 2026, at 12:00 AM UTC
Root cause: We determined that a transient connectivity disruption in between the service and its caching layer resulted in this impact.
Next steps: - We're reviewing the connectivity issue 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 Oct 7 13:20:25 2026 |
|---|
| Description: | Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
User impact: Users may be unable to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web.
More info: Users may receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions.
Current status: After further analysis of service availability, we've isolated that additional users are impacted and we've expanded our communications to encompass all potentially affected users. We've updated the "Title". "User impact", "More info", and "Scope of impact" fields of our communication to reflect this change.
We've initiated deployment of our fix, and we anticipate deployment to be completed by our next scheduled update.
Scope of impact: This issue may impact some users attempting to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web. This information may be updated as our investigation continues.
Start time: Wednesday, July 22, 2026, at 1:21 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by our next scheduled update on Friday, October 9, 2026, at 6:30 PM UTC.
Next update by: Friday, October 9, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Oct 6 17:52:21 2026 |
|---|
| Description: | Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
User impact: Users may be unable to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web.
More info: Users may receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions.
Current status: We're addressing an unrelated issue that's causing the deployment of our fix to take additional time. We'll aim to provide a timeline for the deployment to complete by our next scheduled communications update.
Scope of impact: This issue may impact some users attempting to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web. This information may be updated as our investigation continues.
Start time: Wednesday, July 22, 2026, at 1:21 PM UTC
Next update by: Wednesday, October 7, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Oct 5 17:01:06 2026 |
|---|
| Description: | Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
User impact: Users may be unable to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web.
More info: Users may receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions.
Current status: The deployment of a fix that we suspect will remediate the impact is nearly complete. We'll reach out to some affected users to determine is impact is still occurring after the deployment, and we'll also monitor service telemetry to ensure failure rates are decreasing.
Scope of impact: This issue may impact some users attempting to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web. This information may be updated as our investigation continues.
Next update by: Tuesday, October 6, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Oct 2 11:44:02 2026 |
|---|
| Description: | Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
User impact: Users may be unable to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web.
More info: Users may receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions.
Current status: The issue delaying the release of our solution has been resolved, and we've started deploying our fixes for this issue. We anticipate that all necessary deployments will be completed by our next scheduled update.
Scope of impact: This issue may impact some users attempting to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web. This information may be updated as our investigation continues.
Next update by: Monday, October 5, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Sep 29 17:04:17 2026 |
|---|
| Description: | Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
User impact: Users may be unable to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web.
More info: Users may receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions.
Current status: A deployment issue has delayed the release of our solution, and our fix deployment timeline now projects that it will be completed by our next scheduled communication update. Once complete, and if our findings prove to be correct by this solution mitigating the impact, we’ll be able to identify the source for this event to help in our post-incident efforts to prevent future occurrences of the problem.
Scope of impact: This issue may impact some users attempting to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web. This information may be updated as our investigation continues.
Next update by: Thursday, October 1, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Sep 28 17:03:38 2026 |
|---|
| Description: | Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
User impact: Users may receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions.
More info: Users receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions.
Current status: We are working on deploying a potential solution. We anticipate having an update on the effectiveness of this action at our next communication time.
Scope of impact: This issue may impact some users attempting to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web. This information may be updated as our investigation continues.
Next update by: Tuesday, September 29, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Sep 28 15:58:19 2026 |
|---|
| Description: | Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
User impact: Users may be unable to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web.
More info: Users may receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions.
Current status: We're reviewing information provided in specific support cases to better understand the issue and determine our next steps.
Scope of impact: This issue may impact some users attempting to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web. This information may be updated as our investigation continues.
Next update by: Monday, September 28, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Sep 28 15:38:09 2026 |
|---|
| Description: | Title: Some users may be unable to change page distribution or review work in Microsoft OneNote and OneNote for the web
User impact: Users may be unable to make changes to page distribution or review work in Microsoft OneNote and OneNote for the web.
More info: Users may receive an error message that reads "waiting to start" that doesn't resolve when attempting the affected actions.
Current status: We're investigating a potential issue with Microsoft OneNote and OneNote for the web and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1489449 - Some users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 5 08:30:00 2026 |
|---|
| End Time: | Thu Oct 8 10:30:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Search and Delve |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 8 16:28:36 2026 |
|---|
| Root Cause: | A portion of the SharePoint Online service infrastructure was operating in a suboptimal state and causing requests related to the Microsoft 365 app launcher to time out, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 8 16:22:42 2026 |
|---|
| Description: | Title: Some users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online
User impact: Users' Microsoft 365 apps may have not appeared in the App launcher in SharePoint Online.
More info: Users may not have seen the Settings icon, also known as the gear icon, appearing in SharePoint Online.
As a workaround, affected users could access the affected apps directly through office.com or microsoft365.com.
Previously, some users who were based in the Europe, Middle East and Africa region were affected by this event and have since been remediated.
Final status: We've confirmed that the final deployment has completed saturation throughout the remaining affected regions, and after monitoring the service, we've verified that this action has successfully remediated the problem.
Scope of impact: Impact was specific to some users in the United States region who attempted to access apps through the Microsoft 365 app or the Settings page in SharePoint Online.
Start time: Monday, October 5, 2026, at 12:30 PM UTC
End time: Thursday, October 8, 2026, at 2:30 PM UTC
Root cause: A portion of the SharePoint Online service infrastructure was operating in a suboptimal state and causing requests related to the Microsoft 365 app launcher to time out, resulting in impact.
Next steps: We're analyzing performance data and trends on the affected SharePoint Online service infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 8 11:08:56 2026 |
|---|
| Description: | Title: Some users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online
User impact: Users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online.
More info: Users may not have the Settings icon, also known as the gear icon, appearing in SharePoint Online.
As a workaround, affected users can access the affected apps directly through office.com or microsoft365.com.
Previously, some users who are based in the Europe, Middle East and Africa region were affected by this event, and have since been remediated.
Current status: We've validated that a majority of the affected users, specifically those in the Europe, Middle East and Africa regions, that have received our optimizations are no longer impacted by the event. We're monitoring a final deployment as it saturates in the remaining affected region, before verifying that the impact has been remediated.
Scope of impact: Impact is specific to some users in the United States region attempting to access apps through the Microsoft 365 app, or the Setting page, in SharePoint Online. This information may be updated as our investigation continues.
Start time: Monday, October 5, 2026, at 12:30 PM UTC
Root cause: A portion of the SharePoint Online service infrastructure is operating in a suboptimal state and causing requests related to the Microsoft 365 app launcher to time out, resulting in impact.
Next update by: Thursday, October 8, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Oct 8 05:49:59 2026 |
|---|
| Description: | Title: Some users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online
User impact: Users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online.
More info: Users may not have the Settings icon, also known as the gear icon, appearing in SharePoint Online.
As a workaround, affected users can access the affected apps directly through office.com or microsoft365.com.
Current status: We're continuing to monitor as our optimizations are implemented across the affected regions, and we're seeing further signs of recovery. We aim to provide a remediation timeline by our next scheduled update.
Scope of impact: Impact is specific to some users in Europe, Middle East, Africa, and the United States regions attempting to access apps through the Microsoft 365 app, or the Setting page, in SharePoint Online. This information may be updated as our investigation continues.
Start time: Monday, October 5, 2026, at 12:30 PM UTC
Root cause: A portion of the SharePoint Online service infrastructure is operating in a suboptimal state and causing requests related to the Microsoft 365 app launcher to time out, resulting in impact.
Next update by: Thursday, October 8, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Oct 7 18:05:05 2026 |
|---|
| Description: | Title: Some users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online
User impact: Users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online.
More info: Users may not have the Settings icon, also known as the gear icon, appearing in SharePoint Online.
As a workaround, affected users can access the affected apps directly through office.com or microsoft365.com.
Current status: We're monitoring as our optimizations are implemented across the affected regions, and we're noting signs of recovery. We're continuing to monitor and our ongoing observation of the rate of progress will aid in determining a timeline for remediation.
Scope of impact: Impact is specific to some users in Europe, Middle East, Africa, and the United States regions attempting to access apps through the Microsoft 365 app, or the Setting page, in SharePoint Online. This information may be updated as our investigation continues.
Start time: Monday, October 5, 2026, at 12:30 PM UTC
Root cause: A portion of the SharePoint Online service infrastructure is operating in a suboptimal state and causing requests related to the Microsoft 365 app launcher to time out, resulting in impact.
Next update by: Thursday, October 8, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Oct 7 12:22:53 2026 |
|---|
| Description: | Title: Some users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online
User impact: Users' Microsoft 365 apps may not appear in the App launcher in SharePoint Online.
More info: Users may not have the Settings icon, also known as the gear icon, appearing in SharePoint Online.
As a workaround, affected users can access the affected apps directly through office.com or microsoft365.com.
Current status: We've further identified that a portion of the SharePoint Online service infrastructure is operating in a suboptimal state and causing requests from SharePoint Online to the Microsoft 365 app launcher to time out, resulting in impact. We're implementing optimizations to increase the processing functionality of the affected infrastructure and return it to expected functionality. We'll aim to provide a timeline for our optimizations to be implemented by our next scheduled communications update.
Scope of impact: Impact is specific to some users in Europe, Middle East, Africa, and the United States regions attempting to access apps through the Microsoft 365 app, or the Setting page, in SharePoint Online. This information may be updated as our investigation continues.
Start time: Monday, October 5, 2026, at 12:30 PM UTC
Root cause: A portion of the SharePoint Online service infrastructure is operating in a suboptimal state and causing requests related to the Microsoft 365 app launcher to time out, resulting in impact.
Next update by: Wednesday, October 7, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 10:28:18 2026 |
|---|
| Description: | Title: Some users may not see apps in the Microsoft 365 app launcher when accessed through SharePoint Online
User impact: Users may not see apps in the Microsoft 365 app launcher when accessed through SharePoint Online.
More info: Users may also not see the Gear icon for settings in SharePoint Online.
As a workaround, affected users can access the affected apps directly through office.com or microsoft365.com.
Current status: We’ve identified that requests used to display Microsoft 365 app launcher information are failing with an HTTP 500 Internal Server error response. We suspect this is related to a resource constraint affecting the supporting service infrastructure, where increased resource utilization is causing requests to be rejected. We’re working to increase the available infrastructure capacity to mitigate the underlying issue and restore app launcher functionality.
Scope of impact: Impact is specific to some users in Europe, Middle East, Africa, and the United States regions attempting to access apps through the Microsoft 365 app launcher in SharePoint Online. This information may be updated as our investigation continues.
Next update by: Wednesday, October 7, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Oct 6 11:20:18 2026 |
|---|
| Description: | Title: Some users may not see apps in the Microsoft 365 app launcher when accessed through SharePoint Online
User impact: Users may not see apps in the Microsoft 365 app launcher when accessed through SharePoint Online.
More info: Users may also not see the Gear icon for settings in SharePoint Online.
As a workaround, affected users can access the affected apps directly through office.com or microsoft365.com.
Current status: We're progressing with our root cause analysis and analyzing internal tokens, as we isolate both the source for this event and our next steps for remediating the impact.
Scope of impact: Impact is specific to some users in Europe, Middle East, Africa, and the United States regions attempting to access apps through the Microsoft 365 app launcher in SharePoint Online. This information may be updated as our investigation continues.
|
|---|
|
| Time: | Tue Oct 6 09:18:26 2026 |
|---|
| Description: | Title: Some users may not see apps in the Microsoft 365 app launcher when accessed through SharePoint Online
User impact: Users may not see apps in the Microsoft 365 app launcher when accessed through SharePoint Online.
More info: Users may also not see the Gear icon for settings in SharePoint Online.
As a workaround, affected users can access the affected apps directly through office.com or microsoft365.com.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users in Europe, Middle East, Africa, and the United States regions attempting to access apps through the Microsoft 365 app launcher in SharePoint Online. This information may be updated as our investigation continues.
Next update by: Tuesday, October 6, 2026, at 3:30 PM UTC
|
|---|
|
EX1491694 - Some users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 8 10:39:42 2026 |
|---|
| End Time: | Thu Oct 8 14:29:29 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Oct 8 14:40:27 2026 |
|---|
| Root Cause: | A routing service-side testing process created a Domain Name System (DNS) issue resulting in this impacting event.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 8 14:40:15 2026 |
|---|
| Description: | Title: Some users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail
User impact: Users' email messages from on-premises Exchange servers to Exchange Online may have intermittently failed.
More info: Impacted users received the following error "Mail sent to the wrong Office 365 region. ATTR35."
Final status: We have stopped the service-side testing and reversed the changes it had made. We've confirmed with both service-side telemetry and multiple users' feedback that this issue is now resolved. We've stopped the service-side testing, reversed the changes it had made, and confirmed with service-side telemetry and user feedback that this issue is now resolved.
Scope of impact: Some users' email messages from on-premises Exchange servers to Exchange Online may have intermittently failed.
Start time: Thursday, October 8, 2026, at 10:06 AM UTC
End time: Thursday, October 8, 2026, at 4:05 PM UTC
Root cause: A routing service-side testing process created a Domain Name System (DNS) issue resulting in this impacting event.
Next steps:
-We're reviewing our service side testing processes and checks to ensure that impact is avoided or to notify admins ahead of time to potential downtime periods so that preventative actions can be taken.
This is the final update for this event.
|
|---|
|
| Time: | Thu Oct 8 12:20:07 2026 |
|---|
| Description: | Title: Some users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail
User impact: Users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail.
More info: Impacted users receive the following error "Mail sent to the wrong Office 365 region. ATTR35."
Current status: We've identified a potential root cause related to a service-side testing process. We're working on a remediation plan to correct this issue and restore service. This information may be updated as our investigation continues.
Scope of impact: Some users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail.
Next update by: Thursday, October 8, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Oct 8 11:14:23 2026 |
|---|
| Description: | Title: Some users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail
User impact: Users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail.
Current status: We're reviewing the information provided by some reporting users to better understand this issue and determine our next troubleshooting steps.
Scope of impact: Some users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail.
Next update by: Thursday, October 8, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Oct 8 10:53:13 2026 |
|---|
| Description: | Title: Some users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail
User impact: Users' email messages from on-premises Exchange servers to Exchange Online may intermittently fail.
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.
|
|---|
|
CP1491697 - Some users may receive failures when prompting Microsoft 365 Copilot in Outlook on the web or the Outlook desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Thu Oct 8 09:20:00 2026 |
|---|
| End Time: | Thu Oct 8 12:10:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Oct 8 13:41:17 2026 |
|---|
| Root Cause: | A recent model migration for Copilot in Outlook on the web and the Outlook desktop client resulted in an unexpected influx in user traffic and caused degradation in Copilot prompt responses.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 8 13:40:55 2026 |
|---|
| Description: | Title: Some users may receive failures when prompting Microsoft 365 Copilot in Outlook on the web or the Outlook desktop client
User impact: Users may have received failures when prompting Copilot in Outlook on the web or the Outlook desktop client.
More info: Users may have received a "Something went wrong" error message when prompting Copilot in Outlook.
Final status: We've rolled back the model migration that had resulted in degradation in Copilot prompt responses and validated after completing an internal monitoring period that impact is remediated.
Scope of impact: This issue affected some users attempting to prompt Copilot in Outlook on the web or the Outlook desktop client, who may have received a "Something went wrong" error to their prompts.
Start time: Thursday, October 8, 2026, at 1:20 PM UTC
End time: Thursday, October 8, 2026, at 4:10 PM UTC
Root cause: A recent model migration for Copilot in Outlook on the web and the Outlook desktop client resulted in an unexpected influx in user traffic and caused degradation in Copilot prompt responses.
Next steps:
- We're analyzing the problematic model migration to isolate why the potential for impact wasn't caught during our internal testing and validation phases. This further analysis will help us to prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 8 12:33:34 2026 |
|---|
| Description: | Title: Some users may receive failures when prompting Microsoft 365 Copilot in Outlook on the web or the Outlook desktop client
User impact: Users may receive failures when prompting Copilot in Outlook on the web or the Outlook desktop client.
More info: Users may receive a "Something went wrong" error message when prompting Copilot in Outlook.
Current status: After analyzing available service telemetry, we've isolated that a recent model migration for Copilot in Outlook on the web or the Outlook desktop client is resulting in an unexpected influx in user traffic and causing degradation in Copilot prompt responses. We're rolling back the update and monitoring available telemetry for remediation.
Scope of impact: This issue affects some users attempting to prompt Copilot in Outlook on the web or the Outlook desktop client, who may receive a "Something went wrong" error to their prompts. This section may be updated as the investigation progresses.
Start time: Thursday, October 8, 2026, at 1:20 PM UTC
Root cause: A recent model migration for Copilot in Outlook on the web or the Outlook desktop client is resulting in an unexpected influx in user traffic and causing degradation in Copilot prompt responses.
Next update by: Thursday, October 8, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Oct 8 11:24:03 2026 |
|---|
| Description: | Title: Some users may receive failures when prompting Microsoft 365 Copilot in Outlook on the web or the Outlook desktop client
User impact: Users may receive failures when prompting Copilot in Outlook on the web or the Outlook desktop client.
More info: Users may receive a "Something went wrong" error message when prompting Copilot in Outlook.
Current status: Our service monitors have alerted us to a drop in availability for a subset of users attempting to prompt Copilot in Outlook on the web or the Outlook desktop client. We're reviewing available service telemetry to isolate potential sources of impact contributing to the drop in availability and to determine our next troubleshooting steps.
Scope of impact: This issue affects some users attempting to prompt Copilot in Outlook on the web or the Outlook desktop client, who may be returned a "Something went wrong" error to their prompts. This section may be updated as the investigation progresses.
Start time: Thursday, October 8, 2026, at 1:20 PM UTC
Next update by: Thursday, October 8, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Oct 8 11:05:29 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.
|
|---|
|
TM1489909 - Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 28 09:00:00 2026 |
|---|
| End Time: | Thu Oct 8 12:09:48 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 8 12:16:25 2026 |
|---|
| Root Cause: | A subset of networking service infrastructure that helps facilitate access to PowerPoint Live content fell below our manageable service performance thresholds, which resulted in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 8 12:16:22 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 have been missing some slides.
Final status: After a period of monitoring our service telemetry, we've confirmed that our configuration changes and optimizations have remediated the impact.
Scope of impact: Any user located in the United States that was recording PowerPoint Live in Microsoft Teams presentations may have been impacted.
Start time: Monday, September 28, 2026, at 1:00 PM UTC
End time: Thursday, October 8, 2026, at 2:30 PM UTC
Root cause: A subset of networking service infrastructure that helps facilitate access to PowerPoint Live content fell below our manageable service performance thresholds, which resulted in the impact.
Next steps:
- We're continuing our analysis of the subset of networking service infrastructure to better understand why it was performing sub optimally so we can take any additional corrective measures necessary to prevent this from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 7 21:42:05 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 applied the aforementioned configuration changes and optimizations throughout the affected service environment, and our initial review of the service health telemetry yields positive results. Additionally, we anticipate that the issue will be resolved prior to our next scheduled update, at which point we plan to monitor the telemetry to ensure that the issue is fully resolved.
Scope of impact: Any user located in the United States that is 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 8, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 17:59:05 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 apply and test configuration changes and optimizations on the affected infrastructure to assist with remediating user impact. We aim to provide a timeline to remediation as soon as possible.
Scope of impact: Any user located in the United States that is 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 8, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Oct 7 13:01:56 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 working to expedite the process for applying our configuration changes and optimizations to the affected infrastructure. We aim to provide a timeline for our mitigation to be implemented by our next scheduled communications update.
Scope of impact: Any user located in the United States that is 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: Wednesday, October 7, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Oct 7 10:22:21 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 apply configuration change fixes to rebalance the request traffic being routed to the portion of affected infrastructure so that we can bring the service back within optimal performance thresholds.
Scope of impact: Any user located in the United States that is 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: Wednesday, October 7, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Oct 7 09:00:58 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 proceeding to deploy our fix and will provide a timeline for the remediation as one becomes available.
Scope of impact: Any user located in the United States that is 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: Wednesday, October 7, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue Oct 6 18:42:31 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 deploy our fix and will provide a timeline for the remediation as one becomes available.
Scope of impact: Any user located in the United States that is 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: Wednesday, October 7, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Oct 6 18:07:12 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 service health monitoring indicates that the impact previously communicated through TM1483625 is re-occurring. We're deploying a fix to rebalance the request traffic being routed to the portion of affected infrastructure so that we can bring the service back within our optimal performance threshold.
Scope of impact: Any user located in the United States that is 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 11:30 PM UTC
|
|---|
|
| Time: | Tue Oct 6 17:56:40 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.
|
|---|
|
DZ1489394 - Users may have experienced alert and activity delays and unexpected CAAC policy behavior in Microsoft Defender XDR
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 6 04:33:00 2026 |
|---|
| End Time: | Thu Oct 8 03:37:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Oct 8 05:02:45 2026 |
|---|
| Root Cause: | An authentication component issue was resulting in a section of infrastructure, responsible for alerts and activity processing in Microsoft Defender XDR, to become unavailable while connecting to a dependency service.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Oct 8 05:02:21 2026 |
|---|
| Description: | Title: Users may have experienced alert and activity delays and unexpected CAAC policy behavior in Microsoft Defender XDR
User impact: Users may have experienced alert and activity delays and unexpected CAAC policy behavior in Microsoft Defender XDR.
More info: Specifically, alert and activity processing in Microsoft Defender for Cloud Apps was affected. Users may have experience delays in alerts triggered by anomaly detection and activity policies, alert visibility and email notifications. Activity data appearing in the user interface, Advanced Hunting or CloudAppEvents table may have also been delayed, potentially affecting the accuracy of custom detections in Microsoft Sentinel.
For Endpoint Inline users with Conditional Access App Control (CAAC), access and session policies may have not been evaluated as expected, resulting in policies being either bypassed or hardened, depending on the configured behavior.
Final status: We've confirmed that impact has been mitigated following the completion of backlog processing, and we're continuing to monitor service telemetry to confirm that impact is no longer occurring.
Scope of impact: Impact may have been specific to any user with CAAC session and access policies or expecting alerts and activities in Microsoft Defender XDR.
Start time: Tuesday, October 6, 2026, at 8:33 AM UTC
End time: Thursday, October 8, 2026, at 7:37 AM UTC
Root cause: An authentication component issue was resulting in a section of infrastructure, responsible for alerts and activity processing in Microsoft Defender XDR, to become unavailable while connecting to a dependency service.
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: | Thu Oct 8 01:51:24 2026 |
|---|
| Description: | Title: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR
User impact: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR.
More info: Specifically, alert and activity processing in Microsoft Defender for Cloud Apps is affected. Users may experience delays in alerts triggered by anomaly detection and activity policies, alert visibility and email notifications. Activity data appearing in the user interface, Advanced Hunting or CloudAppEvents table may also be delayed, potentially affecting the accuracy of custom detections in Microsoft Sentinel.
For Endpoint Inline users with Conditional Access App Control (CAAC), access and session policies may not be evaluated as expected, resulting in policies being either bypassed or hardened, depending on the configured behavior.
Current status: Although taking longer than previously anticipated, the backlog has nearly completed processing, and we now expect that it will have fully drained prior to our next scheduled communications update. Once it completes, we'll monitor the affected service environment to ensure that the issue is resolved.
Scope of impact: Impact may be specific to any user with CAAC session and access policies or expecting alerts and activities in Microsoft Defender XDR. This information may be updated as our investigation continues.
Root cause: An authentication component issue is resulting in a section of infrastructure, responsible for alerts and activity processing in Microsoft Defender XDR, to become unavailable while connecting to a dependency service.
Next update by: Thursday, October 8, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 12:04:27 2026 |
|---|
| Description: | Title: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR
User impact: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR.
More info: Specifically, alert and activity processing in Microsoft Defender for Cloud Apps is affected. Users may experience delays in alerts triggered by anomaly detection and activity policies, alert visibility and email notifications. Activity data appearing in the user interface, Advanced Hunting or CloudAppEvents table may also be delayed, potentially affecting the accuracy of custom detections in Microsoft Sentinel.
For Endpoint Inline users with Conditional Access App Control (CAAC), access and session policies may not be evaluated as expected, resulting in policies being either bypassed or hardened, depending on the configured behavior.
Current status: An unrelated deployment issue has delayed our processing of the backlogged requests. After addressing the deployment problems, we've resumed our processing of the backlog which we're expecting will have completed by our next scheduled communication update.
Scope of impact: Impact may be specific to any user with CAAC session and access policies or expecting alerts and activities in Microsoft Defender XDR. This information may be updated as our investigation continues.
Root cause: An authentication component issue is resulting in a section of infrastructure, responsible for alerts and activity processing in Microsoft Defender XDR, to become unavailable while connecting to a dependency service.
Next update by: Thursday, October 8, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Oct 7 06:36:54 2026 |
|---|
| Description: | Title: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR
User impact: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR.
More info: Specifically, alert and activity processing in Microsoft Defender for Cloud Apps is affected. Users may experience delays in alerts triggered by anomaly detection and activity policies, alert visibility and email notifications. Activity data appearing in the user interface, Advanced Hunting or CloudAppEvents table may also be delayed, potentially affecting the accuracy of custom detections in Microsoft Sentinel.
For Endpoint Inline users with Conditional Access App Control (CAAC), access and session policies may not be evaluated as expected, resulting in policies being either bypassed or hardened, depending on the configured behavior.
Current status: We're continuing to make progress in clearing the remaining activity backlog. We'll provide a completion timeline as soon as it becomes available.
Scope of impact: Impact may be specific to any user with CAAC session and access policies or expecting alerts and activities in Microsoft Defender XDR. This information may be updated as our investigation continues.
Start time: Tuesday, October 6, 2026, at 9:03 AM UTC
Root cause: An authentication component issue is resulting in a section of infrastructure, responsible for alerts and activity processing in Microsoft Defender XDR, to become unavailable of connecting to a dependency service.
Next update by: Wednesday, October 7, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Oct 7 04:08:34 2026 |
|---|
| Description: | Title: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR
User impact: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR.
More info: Specifically, alert and activity processing in Microsoft Defender for Cloud Apps is affected. Users may experience delays in alerts triggered by anomaly detection and activity policies, alert visibility and email notifications. Activity data appearing in the user interface, Advanced Hunting or CloudAppEvents table may also be delayed, potentially affecting the accuracy of custom detections in Microsoft Sentinel.
For Endpoint Inline users with Conditional Access App Control (CAAC), access and session policies may not be evaluated as expected, resulting in policies being either bypassed or hardened, depending on the configured behavior.
Current status: We're continuing to process the remaining activity backlog and are assessing how quickly delayed data is returning to expected processing levels. This is helping us determine when processing delays have fully cleared across all affected environments and whether any residual impact remains.
Scope of impact: Impact may be specific to any user with CAAC session and access policies or expecting alerts and activities in Microsoft Defender XDR. This information may be updated as our investigation continues.
Start time: Tuesday, October 6, 2026, at 9:03 AM UTC
Root cause: An authentication component issue is resulting in a section of infrastructure, responsible for alerts and activity processing in Microsoft Defender XDR, to become unavailable of connecting to a dependency service.
Next update by: Wednesday, October 7, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Tue Oct 6 11:10:45 2026 |
|---|
| Description: | Title: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR
User impact: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR.
More info: Specifically, alert and activity processing in Microsoft Defender for Cloud Apps is affected. Users may experience delays in alerts triggered by anomaly detection and activity policies, alert visibility and email notifications. Activity data appearing in the user interface, Advanced Hunting or CloudAppEvents table may also be delayed, potentially affecting the accuracy of custom detections in Microsoft Sentinel.
For Endpoint Inline users with Conditional Access App Control (CAAC), access and session policies may not be evaluated as expected, resulting in policies being either bypassed or hardened, depending on the configured behavior.
Current status: We're continuing to monitor the backlog of accumulated requests to fully remediate the impact.
Scope of impact: Impact may be specific to any user with CAAC session and access policies or expecting alerts and activities in Microsoft Defender XDR. This information may be updated as our investigation continues.
Start time: Tuesday, October 6, 2026, at 9:03 AM UTC
Root cause: An authentication component issue is resulting in a section of infrastructure, responsible for alerts and activity processing in Microsoft Defender XDR, to become unavailable of connecting to a dependency service.
Next update by: Wednesday, October 7, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Oct 6 09:58:11 2026 |
|---|
| Description: | Title: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR
User impact: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR.
More info: Specifically, alert and activity processing in Microsoft Defender for Cloud Apps is affected. Users may experience delays in alerts triggered by anomaly detection and activity policies, alert visibility and email notifications. Activity data appearing in the user interface, Advanced Hunting or CloudAppEvents table may also be delayed, potentially affecting the accuracy of custom detections in Microsoft Sentinel.
For Endpoint Inline users with Conditional Access App Control (CAAC), access and session policies may not be evaluated as expected, resulting in policies being either bypassed or hardened, depending on the configured behavior.
Current status: We've confirmed that an authentication component issue is resulting in a section of infrastructure, responsible for alerts and activity processing in Microsoft Defender XDR, to become unavailable of connecting to a dependency service. We've applied performance and traffic optimizations on the infrastructure which has recovered Inline impact as of Tuesday, October 6, 2026, at 1:20 PM UTC. In parallel, we've also validated that alert processing has been restored as of Tuesday, October 6, 2026, at 1:30 PM UTC and we're monitoring a backlog of activities as it decreases to verify full impact remediation.
Scope of impact: Impact may be specific to any user with CAAC session and access policies or expecting alerts and activities in Microsoft Defender XDR. This information may be updated as our investigation continues.
Start time: Tuesday, October 6, 2026, at 9:03 AM UTC
Root cause: An authentication component issue is resulting in a section of infrastructure, responsible for alerts and activity processing in Microsoft Defender XDR, to become unavailable of connecting to a dependency service.
Next update by: Tuesday, October 6, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Oct 6 07:00:54 2026 |
|---|
| Description: | Title: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR.
User impact: Users may encounter delays for alert, activity processing and unexpected CAAC policy behavior in Microsoft Defender XDR.
More info: For Inline users, access and session policies may not be evaluated as expected, resulting in policies being either bypassed or hardened, depending on the configured behavior.
Additionally, alert processing in Microsoft Defender for Cloud Apps is affected and users may notice generation and visibility be delayed. Email notifications for alerts and downstream systems like Advanced Hunting that consume alert data may experience delayed updates.
Current status: We're reviewing service monitoring telemetry, recent service updates and system logs to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Impact may be specific to any Microsoft Defender XDR user with CAAC session and access policies expecting evaluation. This information may be updated as our investigation continues.
Start time: Tuesday, October 6, 2026, at 9:03 AM UTC
Next update by: Tuesday, October 6, 2026, at 3: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: | Wed Oct 7 20:01:04 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, 2027.
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
|
|---|
|
CP1489980 - Users may be unable to interact with the Microsoft 365 Copilot voice experience
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 6 19:07:44 2026 |
|---|
| End Time: | Wed Oct 7 19:34:55 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 7 19:38:18 2026 |
|---|
| Root Cause: | A recent service cleanup removed required feature configurations, resulting in connectivity issues with the Microsoft 365 Copilot voice experience.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 7 19:38:15 2026 |
|---|
| Description: | Title: Users may be unable to interact with the Microsoft 365 Copilot voice experience
User impact: Users may have been unable to interact with the Microsoft 365 Copilot voice experience.
More info: Users may have been unable to use Copilot voice dictation or other voice features.
Final status: We’ve determined that a recent service cleanup removed required feature configurations, resulting in connectivity issues with the Microsoft 365 Copilot voice experience. We restored the previous working build and confirmed that the issue is resolved.
Scope of impact: Users interacting with the Microsoft 365 Copilot voice experience may have been impacted.
Start time: Tuesday, October 6, 2026, at 3:00 PM UTC
End time: Wednesday, October 7, 2026, at 4:00 AM UTC
Root cause: A recent service cleanup removed required feature configurations, resulting in connectivity issues with the Microsoft 365 Copilot voice experience.
Next steps: - We’re reviewing our service cleanup and validation procedures to better detect and prevent issues like this from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 6 19:45:58 2026 |
|---|
| Description: | Title: Users may be unable to interact with the Microsoft 365 Copilot voice experience
User impact: Users may be unable to interact with the Microsoft 365 Copilot voice experience.
More info: Users can't use Copilot voice dictation or any of the voice experience.
Current status: We have investigated the issue and determined that a new build is causing the affected experience. We are rolling back to a previous build to mitigate the issue.
Scope of impact: Users interacting with the Microsoft Copilot voice experience are impacted.
Next update by: Thursday, October 8, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Oct 6 19:23:34 2026 |
|---|
| Description: | Title: Users may be unable to interact with the Microsoft 365 Copilot voice experience
User impact: Users may be unable to interact with the Microsoft 365 Copilot voice experience.
More info: Users can't use Copilot voice dictation or any of the voice experience.
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.
|
|---|
|
EX1490639 - Exchange Web Services (EWS) applications may be unable to access Exchange Online mailboxes
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Oct 6 06:31:00 2026 |
|---|
| End Time: | Wed Oct 7 17:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 7 18:25:50 2026 |
|---|
| Root Cause: | A recent service-side code change introduced an error in how the EWS application authorizations are read by the service and caused impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 7 18:22:52 2026 |
|---|
| Description: | Title: Exchange Web Services (EWS) applications may be unable to access Exchange Online mailboxes
User impact: EWS applications may have been unable to access Exchange Online mailboxes.
Final status: We've completed deployment of our fix to reverse the effects of the impacting change and confirmed through our service health telemetry that the impact is remediated as a result.
Scope of impact: Any user or admin that relies on an EWS application that needs access to Exchange Online mailboxes to complete its functions may have been impacted.
Start time: Tuesday, October 6, 2026, at 10:31 AM UTC
End time: Wednesday, October 7, 2026, at 9:00 PM UTC
Root cause: A recent service-side code change introduced an error in how the EWS application authorizations are read by the service and caused impact.
Next steps:
- We're reviewing our code change testing and validation procedures to identify and prevent similar issues with EWS application functionality in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 7 16:59:43 2026 |
|---|
| Description: | Title: Exchange Web Services (EWS) applications may be unable to access Exchange Online mailboxes
User impact: EWS applications may be unable to access Exchange Online mailboxes.
Current status: We're deploying our fix to reverse the impacting change and will provide a timeline for the completion of the deployment as one becomes available.
Scope of impact: Any user or admin that relies on an EWS application that needs access to Exchange Online mailboxes to complete its functions may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, October 6, 2026, at 10:31 AM UTC
Root cause: A recent service-side code change introduced an error in how the EWS application authorizations are read by the service and is causing impact.
Next update by: Wednesday, October 7, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 15:52:37 2026 |
|---|
| Description: | Title: Exchange Web Services (EWS) applications may be unable to access Exchange Online mailboxes
User impact: EWS applications may be unable to access Exchange Online mailboxes.
Current status: We've identified that a recent service-side code change introduced an error in how the EWS application authorizations are read by the service and is causing impact. We're developing a fix to reverse this change.
Scope of impact: Any user or admin that relies on an EWS application that needs access to Exchange Online mailboxes to complete its functions may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service-side code change introduced an error in how the EWS application authorizations are read by the service and is causing impact.
Next update by: Wednesday, October 7, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 15:39:54 2026 |
|---|
| Description: | Title: Exchange Web Services (EWS) applications may be unable to access Exchange Online mailboxes
User impact: EWS applications may be unable to access Exchange Online mailboxes.
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.
|
|---|
|
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: | Wed Oct 7 17:49:49 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 7 17:49:49 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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
|
|---|
|
DZ1490573 - Some admins may be unable to access the Action center in the Microsoft Defender portal
| Status: | serviceRestored |
|---|
| Start Time: | Wed Oct 7 13:01:44 2026 |
|---|
| End Time: | Wed Oct 7 15:00:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 7 16:47:50 2026 |
|---|
| Root Cause: | A recent update to migrate to a new code base for the Microsoft Defender portal contained a failing component that resulted in stalling and failures when admins attempted to access the Action center.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 7 16:46:52 2026 |
|---|
| Description: | Title: Some admins may be unable to access the Action center in the Microsoft Defender portal
User impact: Admins may have been unable to access the Action center in the Microsoft Defender portal.
More info: Admins reported that clicking on the Action center caused the page to stall and never load.
Final status: We've completed our rollback of the update that introduced a failing component causing stalling and failures when accessing the Action center. We've validated with a subset of reporting users that impact is remediated. If users are still experiencing impact, we advise them to reload the page using Ctrl + F5 on PC or Cmd + Shift + R on Mac. Alternatively, users can close all browser windows and reopen their browser to ensure remediation.
Scope of impact: Some admins may have been unable to access the Action center in the Microsoft Defender portal as the page stalled and never loaded.
Start time: Wednesday, October 7, 2026, at 1:00 PM UTC
End time: Wednesday, October 7, 2026, at 7:00 PM UTC
Root cause: A recent update to migrate to a new code base for the Microsoft Defender portal contained a failing component that resulted in stalling and failures when admins attempted to access the Action center.
Next steps:
- We're analyzing the offending service update to determine why the potential for impact wasn't caught during our internal update testing and validation phases. This analysis will help us to improve our update implementation process moving forward to help ensure similar impact scenarios don't occur in the future.
|
|---|
|
| Time: | Wed Oct 7 15:01:01 2026 |
|---|
| Description: | Title: Some admins may be unable to access the Action center in the Microsoft Defender portal
User impact: Admins may be unable to access the Action center in the Microsoft Defender portal.
More info: Admins report that clicking on the Action center causes the page to stall and never load.
Current status: After further analysis of the internal reproduction of impact, we've isolated that impact is broader than initially diagnosed and we've expanded our communications to encompass all potentially affected admins. We've updated the "Title", "User impact", and "Scope of impact" fields of our communications to reflect this change.
We've isolated that a recent update to migrate to a new code base for the Microsoft Defender portal contained a failing component that’s resulting in stalling and failures when admins attempt to access the Action center. We're rolling back the problematic update to remediate impact, and we anticipate this process to be completed by our next scheduled update.
Scope of impact: Some admins may be unable to access the Action center in the Microsoft Defender portal as the page stalls and never loads. This section may be updated as the investigation progresses.
Root cause: A recent update to migrate to a new code base for the Microsoft Defender portal contained a failing component that’s resulting in stalling and failures when admins attempt to access the Action center.
Next update by: Wednesday, October 7, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Oct 7 14:03:22 2026 |
|---|
| Description: | Title: Admins can't access the Action center in the Microsoft Defender portal
User impact: Admins can't access the Action center in the Microsoft Defender portal.
More info: Admins report that clicking on the Action center causes the page to stall and never load.
Current status: We're analyzing an internal reproduction of impact to isolate points of impact causing the page to freeze when loading the Action center in the Microsoft Defender portal.
Scope of impact: Your organization is affected by this event, and any admin can't access the Action center in the Microsoft Defender portal as the page stalls and never loads. This section may be updated as the investigation progresses.
Next update by: Wednesday, October 7, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Oct 7 13:24:46 2026 |
|---|
| Description: | Title: Some admins may be unable to access the Action center in the Microsoft Defender portal
User impact: Admins may be unable to access the Action center in the Microsoft Defender portal.
More info: Admins report that clicking on the Action center causes the page to stall and never load.
Current status: We're reviewing raised support cases to further our understanding of the ongoing impact scenario and attempting to reproduce the issue internally to assist with our troubleshooting efforts.
Scope of impact: Some admins may be unable to access the Action center in the Microsoft Defender portal as the page stalls and never loads. This section may be updated as the investigation progresses.
Next update by: Wednesday, October 7, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Oct 7 13:08:04 2026 |
|---|
| Description: | Title: Some admins may be unable to access the Action center in the Microsoft Defender portal
User impact: Admins may be unable to access the Action center in the Microsoft Defender portal.
More info: Admins report that clicking on the Action center causes the page to stall and never load.
Current status: We're investigating a potential issue with Microsoft Defender XDR services and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1483619 - Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation
| Status: | serviceRestored |
|---|
| Start Time: | Sun Sep 27 22:36:00 2026 |
|---|
| End Time: | Thu Oct 1 19:59:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Oct 7 16:36:50 2026 |
|---|
| Root Cause: | The Microsoft URL evaluation process was incorrectly identifying the affected messages as potentially malicious due to the URL inclusion, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 5 19:33:55 2026 |
|---|
| Description: | Title: Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation
User impact: Users' email with DocuSign URLs may not have been delivered and may have been quarantined due to URL reputation.
Final status: We've completed manual mitigation of the remaining affected messages and completed implementation of adjustments to our ML model to ensure its correctly sorting email messages containing DocuSign URLs while maintaining the ability to identify and prevent harmful content from reaching users. We've validated from our service telemetry and from a subset of reporting affected users that impact is remediated.
Scope of impact: This issue may have affected some users attempting to send emails with DocuSign URLs, who may have seen messages not being delivered and quarantined due to URL reputation.
Start time: Monday, September 28, 2026, at 2:36 AM UTC
End time: Thursday, October 1, 2026, at 11:59 PM UTC
Root cause: The Microsoft URL evaluation process was incorrectly identifying the affected messages as potentially malicious due to the URL inclusion, resulting in impact.
Next steps:
- We're analyzing our URL evaluation process to validate what additional changes we can implement to ensure similar impact scenarios don't occur in the future while also protecting Exchange Online users from potentially malicious senders.
This is the final update for the event.
|
|---|
|
| Time: | Thu Oct 1 18:23:37 2026 |
|---|
| Description: | Title: Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation
User impact: Users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation.
Current status: We're making further manual adjustments to our ML model to ensure its correctly sorting email messages containing DocuSign URLs while maintaining the ability to identify and prevent harmful content from reaching users. We've confirmed that the majority of formerly impacted email messages have been restored, and we're continuing to manually mitigate the remaining affected messages we receive from impacted users as our ML model is being improved.
Scope of impact: This issue may affect some users attempting to send email with DocuSign URLs, who may see messages not being delivered and quarantined due to URL reputation. This section may be updated as the investigation progresses.
Root cause: The Microsoft URL evaluation process is incorrectly identifying the affected messages as potentially malicious due to the URL inclusion, resulting in impact.
Next update by: Monday, October 5, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Oct 1 14:15:45 2026 |
|---|
| Description: | Title: Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation
User impact: Users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation.
Current status: We're continuing to analyze messages containing affected DocuSign URLs to determine what mitigation actions we can implement to prevent our ML model from detecting messages as malicious while still protecting users from harmful content or messages.
Scope of impact: This issue may affect some users attempting to send email with DocuSign URLs, who may see messages not being delivered and quarantined due to URL reputation. This section may be updated as the investigation progresses.
Root cause: The Microsoft URL evaluation process is incorrectly identifying the affected messages as potentially malicious due to the URL inclusion, resulting in impact.
Next update by: Thursday, October 1, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Oct 1 13:11:04 2026 |
|---|
| Description: | Title: Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation
User impact: Users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation.
Current status: After further analysis of impact, we've determined that the scope of impact is wider than initially documented, and we've expanded our communications to all potentially affected users. We've updated the "Title", "User impact", and "Scope of impact" fields to reflect this change. Propagation has completed for our change to add affected DocuSign URLs to our allow lists, but some messages containing affected URLs have not been able to be recovered at this time as they're still being detected by our Machine Learning (ML) model as potentially malicious. We're analyzing affected messages to determine how we can recover the messages in order to fully remediate impact.
Scope of impact: This issue affects some users attempting to send email with DocuSign URLs, who may see message not being delivered and quarantined due to URL reputation. This section may be updated as the investigation progresses.
Root cause: The Microsoft URL evaluation process is incorrectly identifying the affected messages as potentially malicious due to the URL inclusion, resulting in impact.
Next update by: Thursday, October 1, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Sep 30 20:07:23 2026 |
|---|
| Description: | Title: Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation
User impact: Users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation.
Current status: We've determined that the Microsoft URL evaluation process is incorrectly identifying the affected messages as potentially malicious due to the URL inclusion, resulting in impact. We've added the URLs to our allow list to expedite relief to affected users for new email and we're reprocessing the affected messages. This process may take up to 48 hours but the propagation time is typically less than this. We're reaching out to a subset of users to ensure they are seeing resolution.
Scope of impact: This issue affects some users attempting to send email with DocuSign URLs, who may see message not being delivered and quarantined due to URL reputation. This section may be updated as the investigation progresses.
Root cause: The Microsoft URL evaluation process is incorrectly identifying the affected messages as potentially malicious due to the URL inclusion, resulting in impact.
Next update by: Thursday, October 1, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Sep 30 16:27:15 2026 |
|---|
| Description: | Title: Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation
User impact: Users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation.
Current status: We're currently investigating affected network message IDs to find why URL detonation is occurring and determine next steps.
Scope of impact: This issue affects some users attempting to send email with DocuSign URLs, who may see message not being delivered and quarantined due to URL reputation. This section may be updated as the investigation progresses.
Next update by: Thursday, October 1, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Sep 30 16:06:57 2026 |
|---|
| Description: | Title: Some users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation
User impact: Users' email with DocuSign URLs may not be delivered and may be quarantined due to URL reputation.
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.
|
|---|
|
PL1490629 - Some users may see initial page loading failures and 500 errors within Microsoft Planner
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 28 07:00:00 2026 |
|---|
| End Time: | Wed Oct 7 14:04:00 2026 |
|---|
| Service: | Planner |
|---|
| Feature Group: | Planner |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 7 15:46:09 2026 |
|---|
| Root Cause: | A subset of Microsoft Planner service infrastructure experienced a networking issue that produced initial page failures and 500 errors within Planner. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 7 15:40:59 2026 |
|---|
| Description: | Title: Some users may see initial page loading failures and 500 errors within Microsoft Planner
User impact: Users may have seen initial page loading failures and 500 errors within Microsoft Planner.
Final status: We've isolated a subset of Microsoft Planner service infrastructure that dropped below our manageable service performance thresholds due to a networking issue, resulting in impact. After rerouting service traffic to alternate available infrastructure, our telemetry has verified that the impact has been remediated.
Scope of impact: This issue could have caused any user to see initial page loading failures or 500 errors within Planner.
Start time: Monday, September 28, 2026, at 11:00 AM UTC
End time: Wednesday, October 7, 2026, at 6:04 PM UTC
Root cause: A subset of Microsoft Planner service infrastructure experienced a networking issue that produced initial page failures and 500 errors within Planner.
Next steps:
- We're further analyzing the source of the networking issue that led to the affected service infrastructure’s lower-than expected performance levels to help us prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Oct 7 15:04:17 2026 |
|---|
| Description: | Title: Some users may see initial page loading failures and 500 errors within Microsoft Planner
User impact: Users may have seen initial page loading failures and 500 errors within Planner.
Current status: We've investigated a problem with the Microsoft Planner service in which some users experienced initial page loading failures or 500 errors within Microsoft Planner, 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.
|
|---|
|
MV1489881 - Users are unable to create or edit new meeting or broadcast events in Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 6 17:09:18 2026 |
|---|
| End Time: | Wed Oct 7 01:08:50 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Oct 7 01:50:10 2026 |
|---|
| Root Cause: | A recent deployment introduced a configuration issue that prevented users from creating or editing meeting and broadcast events.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Oct 7 01:21:12 2026 |
|---|
| Description: | Title: Users are unable to create or edit new meeting or broadcast events in Microsoft Viva Engage
User impact: Users were unable to create or edit new meeting or broadcast events in Viva Engage.
More info: Users in Europe and the United States were unable to create or edit new meeting or broadcast events in Viva Engage. Existing events and meetings remained accessible and weren't impacted. To bypass this issue, affected users could've created the meeting or town hall directly in Microsoft Teams and shared the link in Viva Engage.
Final status: We've completed deploying our fix and confirmed with our service telemetry metrics that this issue is resolved.
Scope of impact: Impact may have occurred for all users in Europe and the United States when users attempted to create or edit new meeting or broadcast events in Viva Engage.
Start time: Tuesday, October 6, 2026, at 1:44 AM UTC
End time: Wednesday, October 7, 2026, at 4:50 AM UTC
Root cause: A recent deployment introduced a configuration issue that prevented users from creating or editing meeting and broadcast events.
Next steps:
- We're investigating the impacting recent deployment to pinpoint what the change was intended to do and why impact wasn't caught during the testing and validation phase so that we can prevent impact to the ability of creating and editing of new meetings or broadcast events in Microsoft Viva Engage.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 6 21:51:22 2026 |
|---|
| Description: | Title: Users are unable to create or edit new meeting or broadcast events in Microsoft Viva Engage
User impact: Users are unable to create or edit new meeting or broadcast events in Viva Engage.
More info: Users in Europe and the United States are unable to create or edit new meeting or broadcast events in Viva Engage. Existing events and meetings remain accessible and aren't impacted. To bypass this issue, affected users can create the meeting or town hall directly in Microsoft Teams and share the link in Viva Engage.
Current status: We’ve determined that a recent deployment introduced a configuration issue that prevented users from creating or editing meeting and broadcast events. Deployment of our fix is in its final stages, and we anticipate that it will complete to resolve the issue by our next scheduled update.
Scope of impact: Impact may occur for all users in Europe and the United States when users attempt to create or edit new meeting or broadcast events in Viva Engage. This information may be updated as our investigation continues.
Root cause: A recent deployment introduced a configuration issue that prevented users from creating or editing meeting and broadcast events.
Next update by: Wednesday, October 7, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Oct 6 17:11:21 2026 |
|---|
| Description: | Title: Users are unable to create or edit new meeting or broadcast events in Microsoft Viva Engage
User impact: Users are unable to create or edit new meeting or broadcast events in Viva Engage.
More info: Users in Europe and the United States are unable to create or edit new meeting or broadcast events in Viva Engage. Existing events and meetings remain accessible and aren't impacted. To bypass this issue, affected users can create the meeting or town hall directly in Microsoft Teams and share the link in Viva Engage.
Current status: We’ve received reports from affected users that users are unable to create or edit new meeting or broadcast events in Viva Engage. We’ve developed a configuration fix and are deploying it to the affected environments to mitigate the impact while we continue investigating the underlying cause. Based on our current estimates, we suspect that the configuration fix will complete deployment by our next scheduled update.
Scope of impact: Impact may occur for all users in Europe and the United States when users attempt to create or edit new meeting or broadcast events in Viva Engage. This information may be updated as our investigation continues.
Next update by: Wednesday, October 7, 2026, at 2:00 AM UTC
|
|---|
|
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: | Tue Oct 6 12:23:46 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: | Tue Oct 6 12:23:46 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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.
|
|---|
|
TM1483625 - Users' recordings of presentations using PowerPoint Live in Microsoft Teams may be missing some slides
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 28 09:00:00 2026 |
|---|
| End Time: | Tue Oct 6 10:43:58 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Oct 6 10:49:23 2026 |
|---|
| Root Cause: | A subset of networking service infrastructure that helps facilitate access to PowerPoint Live content fell below our manageable service performance thresholds, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 6 10:49:19 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 have been missing some slides.
Final status: We've confirmed after an extended period of monitoring that our optimizations and traffic management have fully remediated the impact.
Scope of impact: Users who recorded PowerPoint Live in Microsoft Teams presentations may have been impacted.
Start time: Monday, September 28, 2026, at 1:00 PM UTC
End time: Tuesday, October 6, 2026, at 12:00 AM UTC
Root cause: A subset of networking service infrastructure that helps facilitate access to PowerPoint Live content fell below our manageable service performance thresholds, which resulted in impact.
Next steps:
- We're continuing our analysis of the impacted infrastructure so we can understand why it fell below expected performance thresholds and take any corrective actions necessary to prevent this issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Oct 6 05:40:15 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 implement additional optimizations and traffic management controls to mitigate impact. We expect this to be complete by our next scheduled 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 4:30 PM UTC
|
|---|
|
| 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.
|
|---|
|
MO1489051 - Admins intermittently may be unable to access the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 5 18:28:00 2026 |
|---|
| End Time: | Tue Oct 6 01:10:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Oct 6 02:36:20 2026 |
|---|
| Root Cause: | An unexpected influx in requests caused performance degradation and failures for admins who attempted to access the Microsoft 365 admin center.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Oct 6 02:32:03 2026 |
|---|
| Description: | Title: Admins intermittently may be unable to access the Microsoft 365 admin center
User impact: Admins intermittently may have been unable to access the Microsoft 365 admin center.
Final status: We've rolled back our infrastructure to a previous build and changed the response behavior of the API to mitigate the surge of requests and resolve the issue. We've also turned off a recently introduced service change and reduced dropped calls to help stabilize the traffic to the admin center.
Scope of impact: Admins attempting to access the Microsoft 365 admin center may have been intermittently affected.
Start time: Monday, October 5, 2026, at 10:28 PM UTC
End time: Tuesday, October 6, 2026, at 6:16 AM UTC
Root cause: An unexpected influx in requests caused performance degradation and failures for admins who attempted to access the Microsoft 365 admin center.
Next steps:
- We're continuing to monitor the affected infrastructure closely to gain further insight into the source of the performance degradation caused by the unexpected influx of requests and better prevent similar impact in the future.
|
|---|
|
| Time: | Tue Oct 6 01:50:05 2026 |
|---|
| Description: | Title: Admins intermittently may be unable to access the Microsoft 365 admin center
User impact: Admins intermittently may be unable to access the Microsoft 365 admin center.
Current status: We've received additional reports that impact persists despite a previous communication indicating impact remediation. We're reviewing our service health telemetry and logs to help assist our investigation into why impact still persists.
Scope of impact: Admins attempting to access the Microsoft 365 admin center may be intermittently affected. This section may be updated as our investigation continues.
Root cause: An unexpected influx in requests caused performance degradation and failures for admins attempting to access the Microsoft 365 admin center.
|
|---|
|
PB1488968 - Some users may be unable to create or update Ontology artifacts in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 5 18:30:00 2026 |
|---|
| End Time: | Mon Oct 5 20:26:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 5 21:55:44 2026 |
|---|
| Root Cause: | A recent feature update introduced a misconfiguration which prevented Ontology artifact creation or updates.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 5 21:55:23 2026 |
|---|
| Description: | Title: Some users may be unable to create or update Ontology artifacts in Microsoft Fabric
User impact: Users may have been unable to create or update Ontology artifacts in Microsoft Fabric.
Final status: We've isolated a regression impacting a subset of users who were unable create or update Ontology artifacts in Microsoft Fabric. We've determined that a recent feature update introduced a misconfiguration which prevented Ontology artifact creation or updates. We've addressed the misconfiguration and we've validated after an internal monitoring period that impact is remediated.
Scope of impact: This issue impacted some users who may have been unable to create or update Ontology artifacts in Microsoft Fabric.
Start time: Monday, October 5, 2026, at 10:30 PM UTC
End time: Tuesday, October 6, 2026, at 12:26 AM UTC
Root cause: A recent feature update introduced a misconfiguration which prevented Ontology artifact creation or updates.
Next steps:
- We're analyzing the problematic feature update to determine why the potential for impact wasn't caught during our internal update testing and validation phases. This analysis will help us to improve our update implementation process moving forward to help ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 5 21:49:11 2026 |
|---|
| Description: | Title: Some users may be unable to create or update Ontology artifacts in Microsoft Fabric
User impact: Users may have been unable to create or update Ontology artifacts in Microsoft Fabric.
Current status: We've investigated a problem in which some users may have been unable to create or update Ontology artifacts in Microsoft Fabric and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
MO1488931 - Admins intermittently may be unable to access the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 5 18:28:00 2026 |
|---|
| End Time: | Mon Oct 5 19:37:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Oct 5 21:17:11 2026 |
|---|
| Root Cause: | An unexpected influx in requests and caused performance degradation and failures for admins attempting to access the Microsoft 365 admin center.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 5 21:16:49 2026 |
|---|
| Description: | Title: Admins intermittently may be unable to access the Microsoft 365 admin center
User impact: Admins intermittently may have been unable to access the Microsoft 365 admin center.
Final status: We've validated that an unexpected influx in requests caused performance degradation and failures for admins attempting to access the Microsoft 365 admin center. We've implemented additional performance optimizations to assist with processing affected traffic. After completing an internal monitoring period, we've validated that impact is remediated.
Scope of impact: Admins attempting to access the Microsoft 365 admin center may have been intermittently affected.
Start time: Monday, October 5, 2026, at 10:28 PM UTC
End time: Monday, October 5, 2026, at 11:37 PM UTC
Root cause: An unexpected influx in requests and caused performance degradation and failures for admins attempting to access the Microsoft 365 admin center.
Next steps:
- We're evaluating what additional performance optimizations or safeguards we can implement to further the resiliency of our service.
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 5 20:08:20 2026 |
|---|
| Description: | Title: Admins intermittently may be unable to access the Microsoft 365 admin center
User impact: Admins intermittently may be unable to access the Microsoft 365 admin center.
Current status: We're continuing to analyze the unusually large increase in requests to the Microsoft 365 admin center along with recent service updates to isolate potential sources of impact that contributed to the traffic increase. We’ve implemented performance optimizations to assist with processing affected traffic and we've validated that service availability has recovered to pre-impact levels. We're continuing our investigation in order to isolate and remediate the underlying root cause to ensure the similar scenario does not occur again in the future.
Scope of impact: Admins attempting to access the Microsoft 365 admin center may be intermittently affected. This section may be updated as the investigation progresses.
Start time: Monday, October 5, 2026, at 10:28 PM UTC
Next update by: Tuesday, October 6, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Oct 5 19:38:38 2026 |
|---|
| Description: | Title: Admins intermittently may be unable to access the Microsoft 365 admin center
User impact: Admins intermittently may be unable to access the Microsoft 365 admin center.
Current status: We’re investigating an unusually large increase in requests to the Microsoft 365 admin center and expect that this increase is resulting in requests queuing and timing-out. We’re reviewing options for mitigating this issue and determining if other factors are contributing to the problem.
Scope of impact: Admins attempting to access the Microsoft 365 admin center may be intermittently affected. This section may be updated as the investigation progresses.
Next update by: Tuesday, October 6, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Oct 5 19:19:19 2026 |
|---|
| Description: | Title: Some admins can't access the Microsoft 365 admin portal
User impact: Admins may be unable to access the Microsoft 365 admin portal.
Current status: We're investigating a potential issue impacting admin access to the Microsoft 365 admin portal in certain regions and we're 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: | serviceRestored |
|---|
| Start Time: | Tue Jun 30 03:00:00 2026 |
|---|
| End Time: | Fri Oct 2 19:26:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 5 20:03:05 2026 |
|---|
| Root Cause: | A recent service update introduced a code regression that affected how Microsoft Teams processed shared workflow requests, which prevented some users from running "run-only workflows" from Microsoft Teams.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 5 20:02:52 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may have been unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users were 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" was still an impacted scenario.
Affected users were unable to run workflows in Teams when those workflows were configured to be executed by designated users without requiring those users to own or edit the workflow. Users received the following error message:
"Missing Trigger URI"
As a way to have avoided the issue, impacted users could've been granted Owner or Co-owner permissions for the affected workflow.
Final status: We've completed the deployment of our fix and confirmed after monitoring our service health telemetry that impact is remediated.
Scope of impact: Users attempting to run "run-only workflows" from Microsoft Teams may have been impacted.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
End time: Friday, October 2, 2026, at 11:26 PM UTC
Root cause: A recent service update introduced a code regression that affected how Microsoft Teams processed shared workflow requests, which prevented some users from running "run-only workflows" from Microsoft Teams.
Next steps:
- We're reviewing our update procedures to understand why impact to how Microsoft Teams processes shared workflow requests wasn't caught during the testing phase. This will help 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 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
|
|---|
|
EX1478163 - Users may be unable to update calendar delegates in the classic Outlook desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Wed Sep 23 03:13:00 2026 |
|---|
| End Time: | Mon Oct 5 19:58:04 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 5 19:59:52 2026 |
|---|
| Root Cause: | A recent update to the service contained a regression, resulting in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 5 19:59:09 2026 |
|---|
| Description: | Title: Users may be unable to update calendar delegates in the classic Outlook desktop client
User impact: Users may have been unable to update calendar delegates in the classic Outlook desktop client.
More info: As a workaround, affected users could’ve managed delegate changes through Outlook on the web.
Final status: Our fix deployment is complete and we’ve determined from service telemetry that this issue is resolved.
Scope of impact: Impact was specific to users that were unable to update calendar delegates in the classic Outlook desktop client.
Start time: Wednesday, September 23, 2026, at 7:13 AM UTC
End time: Saturday, October 3, 2026, at 12:00 AM UTC
Root cause: A recent update to the service contained a regression, resulting in the 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: | 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.
|
|---|
|
EX1441488 - Some users may see unwanted add-ins appearing automatically across all Outlook clients
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 17 06:26:00 2026 |
|---|
| End Time: | Mon Oct 5 14:31:13 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 5 14:33:06 2026 |
|---|
| Root Cause: | A portion of the Exchange Online add-in sync pipeline wasn't processing add-in state information as expected. This caused incorrect EnabledStatus values to be returned, which resulted in Outlook automatically displaying configured add-ins as Available.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 5 14:32:54 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may have seen unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins were configured to be available to users by admins but weren’t expected to be automatically installed. To bypass this issue, admins could've run the “Set-App -Identity -OrganizationApp -PrivateCatalog -DefaultStateForUser Disabled” command to remove add-ins that were unintentionally appearing.
Final status: We've confirmed that our fix has completed its deployment to all affected environments, fully resolving the issue for all users.
Scope of impact: Impact may have occurred for some users that were viewing their add-ins across all Outlook clients.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
End time: Monday, October 5, 2026, at 3:24 PM 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 wasn't processing add-in state information as expected. This caused incorrect EnabledStatus values to be returned, which resulted in Outlook automatically displaying configured add-ins as Available.
Next steps: - We're reviewing the affected pipeline 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 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.
|
|---|
|
SP1488394 - Some users may be unable to search using the search box in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 5 09:39:01 2026 |
|---|
| End Time: | Mon Oct 5 13:59:35 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Search and Delve |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Oct 5 14:09:26 2026 |
|---|
| Root Cause: | A recent feature update caused a compatibility issue that prevented users from searching in SharePoint Online.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 5 14:09:22 2026 |
|---|
| Description: | Title: Some users may be unable to search using the search box in SharePoint Online
User impact: Users may have been unable to search using the search box in SharePoint Online.
Final status: We've identified that a recent feature update caused a compatibility issue that prevented users from searching in SharePoint Online. We reverted the recent feature update and confirm that impact is remediated.
Scope of impact: Some users attempting to search in SharePoint Online may have been impacted.
Start time: Monday, October 5, 2026, at 7:23 AM UTC
End time: Monday, October 5, 2026, at 4:20 PM UTC
Root cause: A recent feature update caused a compatibility issue that prevented users from searching in SharePoint Online.
Next steps: - We're reviewing and improving our feature update validation procedure to prevent similar search issues from occurring in the future.
This is the final update for this event.
|
|---|
|
| Time: | Mon Oct 5 11:51:26 2026 |
|---|
| Description: | Title: Some users may be unable to search using the search box in SharePoint Online
User impact: Users may be unable to search using the search box in SharePoint Online.
Current status: We've identified a potential compatibility issue with a newly updated search service component and we're reviewing the component details to identify the root cause and a strategy that remediates impact.
Scope of impact: Some users attempting to search in SharePoint Online are impacted. This information may be updated as our investigation continues.
Next update by: Monday, October 5, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Oct 5 09:40:41 2026 |
|---|
| Description: | Title: Some users may be unable to search using the search box in SharePoint Online
User impact: Users may be unable to search using the search box in SharePoint Online.
Current status: We're analyzing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users attempting to search in SharePoint Online are impacted. This information may be updated as our investigation continues.
Next update by: Monday, October 5, 2026, at 4:00 PM UTC
|
|---|
|
CP1474143 - Admins may be unable to view the Pay-As-You-Go (PAYG) breakdown in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 10 08:00:00 2026 |
|---|
| End Time: | Mon Oct 5 12:54:16 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 5 13:10:20 2026 |
|---|
| Root Cause: | A recent change to an API that facilitates PAYG breakdown reporting isn't responding to requests as expected, which caused admins to be able to open the usage breakdown panel, despite not meeting the criteria to use the feature.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 5 13:10:16 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 have been unable to view the PAYG breakdown in the Microsoft 365 admin center.
More info: Affected admins may have seen 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."
Final status: We've identified that as a result of the API that facilitates PAYG breakdown reporting not responding to requests as expected, admins that should not have had access to open the usage breakdown panel were able to access it. We completed deployment of our fix that corrects the criteria for which admins can open that panel, re-released the feature, and confirmed that the actions remediated the impact.
Scope of impact: Any admin attempting to access the PAYG breakdown pane within the Microsoft 365 admin center may have been affected.
Start time: Thursday, September 10, 2026, at 12:00 PM UTC
End time: Thursday, October 1, 2026, at 6:00 PM UTC
Root cause: A recent change to an API that facilitates PAYG breakdown reporting isn't responding to requests as expected, which caused admins to be able to open the usage breakdown panel, despite not meeting the criteria to use the feature.
Next steps:
-We're reviewing our API change testing and validation procedures to identify and prevent similar issues with admins having access to features for which they don't meet the criteria for from occurring in the future.
This is the final update for the event.
|
|---|
|
| 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.
|
|---|
|
CP1482212 - Some admins may see stale data in the Microsoft 365 Copilot Health page in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 8 12:05:00 2026 |
|---|
| End Time: | Mon Oct 5 12:38:49 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Oct 5 12:40:55 2026 |
|---|
| Root Cause: | A service process that facilitates data population to the Copilot Health was disabled during a recent change, resulting in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Oct 5 12:16:40 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 have seen stale data in the Copilot Health page in the Microsoft 365 admin center.
More info: Specifically, the tenant readiness score data may not have updated since September 8, 2026.
Final status: The tenant readiness score data stream has been successfully re-enabled and we've confirmed that Copilot Health page is reflecting the updated data as expected to resolve the issue.
Scope of impact: Some admins attempting to see the latest Copilot Health data in the Microsoft 365 admin center may have been impacted.
Start time: Tuesday, September 8, 2026, at 4:05 PM UTC
End time: Friday, October 2, 2026, at 4:21 PM UTC
Root cause: A service process that facilitates data population to the Copilot Health was disabled during a recent change, resulting in the impact.
Next steps:
- We're reviewing our service change procedures to better understand why the service process disablement wasn't identified prior to deployment to prevent similar issues from happening in the future.
This is the final update for this event.
This is the final update for the event.
|
|---|
|
| Time: | Mon Oct 5 06:02:25 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 to monitor service health telemetry after re-enabling the upstream process to validate the freshness of the readiness-score data. We expect to provide an update on the results of the mitigation in our next scheduled communication.
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 5:00 PM UTC
|
|---|
|
| 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.
|
|---|
|
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
|
|---|
|
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
|
|---|
|
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.
|
|---|
|
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
|
|---|
|
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
|
|---|
|
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.
|
|---|
|
|
