Microsoft's Incident Report for PennO365
Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within
the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh
this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this
list. Additionally you can check Microsoft's
status page for current service status messages.
The last extract was taken on Mon Sep 14 20:00:07 2026.
TM1440450 - Users may have been unable to run run-only workflows from Microsoft Teams
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 30 03:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 19:21:15 2026 |
|---|
| Root Cause: | A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
|
|---|
| Next Update: | Saturday, September 26, 2026, at 1:00 AM UTC |
|---|
|
Details
| 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
|
|---|
|
EX1469649 - Some users may be unable to connect to the Outlook mobile app or Outlook client on Mac devices
| Status: | serviceRestored |
|---|
| 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 14 19:18:29 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 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
|
|---|
|
MO1471241 - Some admins' usage reports may contain stale data in Microsoft 365 admin center
| Status: | investigating |
|---|
| Start Time: | Sun Sep 13 00:56:15 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 17:48:53 2026 |
|---|
| Root Cause: | Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
|
|---|
| Next Update: | Tuesday, September 15, 2026, at 2:00 AM UTC |
|---|
|
Details
| Time: | Mon Sep 14 17:48:53 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
These reports may not have refreshed since September 8, 2026.
Current status: We've observed recovery in some processes which manage data processing and report generation. We're continuing to monitor the refresh rate of the impacted reports to ensure usage data report freshness.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Tuesday, September 15, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Sep 14 13:21:10 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
These reports may not have refreshed since September 8, 2026.
Current status: After implementing our solution to resolve the delays that are resulting from a portion of the upstream data processing pipeline, we're monitoring the refresh rate of the impacted reports to validate that our remediation is effective.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Monday, September 14, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Sun Sep 13 01:18:58 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive usage reports
- SharePoint usage reports
- Group Activity reports
These reports may not have refreshed since September 8, 2026.
Current status: We've identified that our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact. We're implementing a solution to the affected pipeline to restore the normal processing flow and recover delayed data as swiftly as possible. We anticipate being able to provide a timeline for resolution by our next scheduled communications update.
Scope of impact: Some admins and users in North America, Asia Pacific, and Europe attempting to see up-to-date data in the affected reports listed in the More info section may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, September 13, 2026, at 12:00 AM UTC
Root cause: Our upstream data pipeline is encountering refresh errors and failures when retrieving up-to-date data for the listed reports, which is resulting in this impact.
Next update by: Monday, September 14, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Sun Sep 13 01:00:53 2026 |
|---|
| Description: | Title: Some admins' usage reports may contain stale data in Microsoft 365 admin center
User impact: Admins' usage reports may contain stale data in Microsoft 365 admin center.
More info: This usage data refresh issue affects the following reports:
- OneDrive Usage reports
- SharePoint Usage reports
- Group Activity reports
Current status: We're investigating a potential issue with usage reports and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
FL1437452 - Flow management and manual invocation operations are failing
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 11:10:00 2026 |
|---|
| End Time: | Thu Jul 23 15:45:00 2026 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 15:49:46 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 14 15:49:46 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Aug 18 17:37:11 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 28 18:31:03 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 23 16:37:27 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations were failing.
Final Status: Following a period of service health diagnostic analysis, we confirmed that service functionality is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A portion of the network infrastructure supporting flow management and manual invocation operations entered an unhealthy state.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Thu Jul 23 15:50:09 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operation are failing.
Current Status: We are continuing to monitor service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 14:49:57 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations are failing.
Current Status: We completed the failover to healthy redundant infrastructure and are monitoring service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:48:06 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations are failing.
Current Status: After our investigation, we determined that a portion of the network infrastructure supporting flow management and manual invocation operations entered an unhealthy state, leading to impact. To mitigate the issue, we are performing a failover to healthy redundant infrastructure.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:46:56 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations are failing.
Current Status: We are aware of an emerging issue where flow management and manual invocation operations are failing. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
DV1437448 - Users are experiencing intermittent failures accessing your Dataverse data or apps
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 13:10:00 2026 |
|---|
| End Time: | Thu Jul 23 15:32:00 2026 |
|---|
| Service: | Microsoft Dataverse |
|---|
| Feature Group: | Environment access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 15:05:04 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 14 15:05:04 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Aug 18 17:56:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 28 18:29:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 23 16:36:28 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users were experiencing intermittent failures accessing your Dataverse data or apps.
Final Status: Following a period of service health diagnostic analysis, we confirmed that service functionality is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A portion of the network infrastructure supporting your environment entered an unhealthy state.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Thu Jul 23 15:50:00 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: We are continuing to monitor service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 14:49:42 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: We completed the failover to healthy redundant infrastructure and are monitoring service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:41:49 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: After our investigation, we determined that a portion of the network infrastructure supporting your environment has entered an unhealthy state, leading to impact. To mitigate the issue, we are performing a failover to healthy redundant infrastructure.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:27:33 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: We are aware of an emerging issue where users are experiencing intermittent failures accessing your Dataverse data or apps. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
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: | Mon Sep 14 14:44:44 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: | Tuesday, September 15, 2026, at 7:30 PM UTC |
|---|
|
Details
| 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.
|
|---|
|
OP1470668 - Users may be unable to copy, paste, drag, or duplicate cells and worksheets in Microsoft Excel
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Sep 11 08:36:11 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 13:55:20 2026 |
|---|
| Root Cause: | A code regression contained within a recent service update is causing impact.
|
|---|
| Next Update: | Tuesday, September 15, 2026, at 7:00 PM UTC |
|---|
|
Details
| 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.
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
|
|---|
|
MP1471821 - Some admins may receive failures creating or updating Communications Compliance policies in Microsoft Purview
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Sep 14 12:41:47 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Sep 14 13:21:42 2026 |
|---|
| Root Cause: | A recent update introduced operations with larger data size included a code error, causing size limitation issues.
|
|---|
| Next Update: | Monday, September 28, 2026, at 6:00 PM UTC |
|---|
|
Details
| 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.
|
|---|
|
EX1471707 - Users may have experienced errors accessing their mailbox through one or more Exchange Online connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Mon Sep 14 05:55:00 2026 |
|---|
| End Time: | Mon Sep 14 10:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 10:46:43 2026 |
|---|
| Root Cause: | A section of Exchange Online infrastructure was performing below acceptable performance thresholds, which affected mailbox availability for some users.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 14 10:35:32 2026 |
|---|
| Description: | Title: Users may have experienced errors accessing their mailbox through one or more Exchange Online connection methods
User impact: Users may have experienced errors accessing their mailbox through one or more Exchange Online connection methods.
More info: Affected users may have been unable to access their mailbox through Outlook on the web, Outlook desktop, Exchange ActiveSync, or other Exchange Online connection methods. Users may have encountered service errors, including 503 responses, intermittent connection failures, or have been unable to access mailbox content while the issue persisted.
Final status: We've determined that a section of Exchange Online infrastructure was performing below acceptable performance thresholds, which affected mailbox availability for some users. We've restarted the affected infrastructure and confirmed through service monitoring that impact has been successfully remediated.
Scope of impact: Impact was specific to users attempting to access their mailbox through Outlook on the web, Outlook desktop, Exchange ActiveSync, or other Exchange Online connection methods.
Start time: Monday, September 14, 2026, at 9:55 AM UTC
End time: Monday, September 14, 2026, at 2:00 PM UTC
Root cause: A section of Exchange Online infrastructure was performing below acceptable performance thresholds, which affected mailbox availability for some users.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for this event.
|
|---|
|
| Time: | Mon Sep 14 08:51:16 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
More info: Affected users may be unable to access their mailbox through Outlook on the web, Outlook desktop, Exchange ActiveSync, or other Exchange Online connection methods. Users may encounter service errors, including 503 responses, intermittent connection failures, or be unable to access mailbox content while the issue persists.
Current status: We've identified an issue within a portion of the Exchange Online service infrastructure that's affecting mailbox availability for some users. We're investigating the underlying cause and reviewing service telemetry to determine why mailbox access requests are failing. We're monitoring the affected environment and continuing our efforts to restore consistent access to impacted mailboxes.
Scope of impact: Impact is specific to users attempting to access their mailbox through Outlook on the web, Outlook desktop, Exchange ActiveSync, or other Exchange Online connection methods.
Next update by: Monday, September 14, 2026, at 3:00 PM UTC
|
|---|
|
EX1471665 - Potential issues accessing mailboxes via one or more connection methods
| Status: | falsePositive |
|---|
| Start Time: | Mon Sep 14 06:50:55 2026 |
|---|
| End Time: | Mon Sep 14 07:40:57 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 07:41:01 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 14 07:40:57 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.
Final status: We've determined that this issue is a duplicate of another event. Please look for further updates in EX1471582. This communication will expire in 24 hours.
|
|---|
|
| Time: | Mon Sep 14 06:51:26 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.
|
|---|
|
EX1465910 - Users may be unable to load themes in Outlook on the web
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Sep 2 02:01:52 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 14 04:14:19 2026 |
|---|
| Root Cause: | A recent update, intended to enhance security hardening, inadvertently introduced a regression which is resulting in impact.
|
|---|
| Next Update: | Wednesday, September 16, 2026, at 9:00 AM UTC |
|---|
|
Details
| Time: | Mon Sep 14 04:14:19 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've determined that a recent update, intended to enhance security hardening, inadvertently introduced a regression which is resulting in impact. We've reverted the update and following a period of monitoring validation, confirmed that impact has been resolved for the majority of affected users. We're continuing to work with a small number of users who remain affected to conduct additional troubleshooting to fully restore the service.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 11:00 AM UTC
Root cause: A recent update, intended to enhance security hardening, inadvertently introduced a regression which is resulting in impact.
Next update by: Wednesday, September 16, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Fri Sep 11 01:03:24 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We’re continuing our efforts with a subset of affected users to gather additional details regarding the expected theme configuration as well as if users are able to reproduce the issue so we can determine our next troubleshooting steps.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, September 14, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Sep 10 06:55:12 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've reviewed diagnostic data from affected users and confirmed that theme data is being retrieved during client startup. We're working with affected organizations to gather additional details regarding the expected theme configuration and are comparing data from impacted and recovered users to identify any missing information or visual elements that may be contributing to the issue.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, September 11, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Sep 10 04:33:24 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've obtained the HAR logs provided by affected users and identified activity indicating theme data is being retrieved during client startup. We're correlating these findings with machine logs from the affected devices to determine whether this behavior is contributing to the reported impact and to isolate the underlying root cause.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, September 10, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Sep 8 03:12:40 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We're awaiting a response from your organization with HAR logs from affected users who continue to experience impact, as the issue persists despite the rollback. These logs will help us further investigate the remaining impact.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted.
Next update by: Thursday, September 10, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Sep 7 03:58:50 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We're awaiting new HAR logs from users who continue to experience impact following the rollback to help determine why they're still encountering the issue.
Scope of impact: Some users attempting to load themes in Outlook on the web may be impacted.
Next update by: Tuesday, September 8, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Sep 3 22:58:34 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've received confirmation from a large portion of affected users that impact is resolved; however, some users are still reporting that impact persists for them. We're working to gather and review new HTTP Archive format (HAR) trace logs from affected users to help understand why impact still persists for them.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Monday, September 7, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Thu Sep 3 04:49:26 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've received confirmation from some affected users that impact is resolved. We're reaching out to additional impacted users to confirm that the issue is fully resolved.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 21:20:13 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've rolled back a recent authentication related change that we suspect is contributing to the impact. We're reaching out to affected users to confirm whether our mitigative action has resolved this issue, which will also aid in confirming our root cause theory.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Thursday, September 3, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 17:43:48 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: Our investigation of the web startup process issue is still ongoing to further isolate the reason for the impact and help us determine the next steps to remediate the impact.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Thursday, September 3, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 16:17:24 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We're continuing to review our service side logs to gather more information regarding the web startup process issue and determine why it's preventing the themes from loading, so that we can developed a mitigation strategy.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 02:20:15 2026 |
|---|
| Description: | Title: Users may be unable to load themes in Outlook on the web
User impact: Users may be unable to load themes in Outlook on the web.
Current status: We've identified an issue occurring during the Outlook on the web startup process that's preventing themes from loading as expected. We're reviewing system logs to understand what is causing the behavior, which will help us isolate our next steps toward remediation.
Scope of impact: Impact is specific to users attempting to load themes in Outlook on the web. This information may be updated as our investigation continues.
Next update by: Wednesday, September 2, 2026, at 8:30 PM UTC
|
|---|
|
CW1470765 - Some users' Exchange Online email messages may not be retrieved when prompting Microsoft 365 Copilot Chat
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Jul 22 18:07:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sat Sep 12 21:19:23 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, causing impact.
|
|---|
| Next Update: | Sunday, September 20, 2026, at 3:00 AM UTC |
|---|
|
Details
| 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.
|
|---|
|
MO1469836 - Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Sep 9 13:57:58 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 11 21:16:58 2026 |
|---|
| Root Cause: | An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
|
|---|
| Next Update: | Tuesday, September 15, 2026, at 2:30 AM UTC |
|---|
|
Details
| Time: | Fri Sep 11 21:16:58 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: The affected data backfill remains in progress and is taking longer than expected. We’re monitoring its progress and expect processing to complete to resolve the issue by our next scheduled update.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next update by: Tuesday, September 15, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Sep 11 17:37:11 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: We’re continuing to backfill the affected data to fully remediate this event. Based on current progress, we anticipate this process will complete by our next scheduled update.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next update by: Saturday, September 12, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Sep 10 13:34:36 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: We've determined that an error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact. We've addressed the underlying issue and are currently in the process of backfilling the data to fully remediate this event.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Start time: Friday, August 28, 2026, at 12:00 AM UTC
Root cause: An error occurred within the flow of service health telemetry data utilized by the service, resulting in this impact.
Next update by: Friday, September 11, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Sep 9 14:11:19 2026 |
|---|
| Description: | Title: Some admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center
User impact: Admins may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center.
More info: Admins may see the following inaccuracies in Microsoft Teams usage reports starting from August 25, 2026:
- Teams Active Users may display as 0
- Teams Chat Messages may display as 0
- Teams Channel Messages may display as 0
Current status: We've received reports from a subset of admins noting inaccuracies or discrepancies in Microsoft Teams usage reports in the Microsoft 365 admin center starting from August 25, 2026. We're attempting to reproduce the issue to further our understanding of the current impact scenario and to determine our next troubleshooting steps.
Scope of impact: This event impacts some admins, who may see Microsoft Teams usage report data discrepancies in the Microsoft 365 admin center starting from August 25, 2026. This section may be updated as the investigation progresses.
Next update by: Thursday, September 10, 2026, at 11:00 PM UTC
|
|---|
|
EX1441488 - Some users may see unwanted add-ins appearing automatically across all Outlook clients
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jul 17 06:26:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 11 13:14:57 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: | Wednesday, September 16, 2026, at 6:30 PM UTC |
|---|
|
Details
| 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.
|
|---|
|
CP1470554 - Users may have been unable to access or may have encountered issues when interacting with Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| 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: | Fri Sep 11 10:24:20 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| 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
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 steps:
- We’re reviewing our deployment and validation procedures to isolate the root cause and prevent recurrence of this issue.
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.
|
|---|
|
TM1458147 - Some users saw incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 5 17:44:00 2026 |
|---|
| End Time: | Fri Sep 11 07:56:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 11 09:57:12 2026 |
|---|
| Root Cause: | A recent code change caused the event validation process to display incorrect warning banners.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 11 09:56:15 2026 |
|---|
| Description: | Title: Some users saw incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
User impact: Users saw incorrect attendee capacity warnings when configuring Microsoft Teams town hall events.
More info: We've confirmed that there was no impact to actual attendee capacity.
Users may have seen the following message:
"Attendee capacity issue. This event is set for 10,000 attendees, but your current limit is 3,000. Attendees above this limit won't be able to join. Contact your Teams administrator to restore capacity."
Final status: We've identified that impact was due to a recent code change which caused the event validation process to display incorrect warning banners. We've completed deployment of the fix across the affected environments and confirmed through service telemetry that impact has been remediated.
Scope of impact: Your organization was affected by this event, and users who were seeing incorrect attendee capacity warnings when configuring Microsoft Teams Town Hall events were impacted.
Start time: Wednesday, August 5, 2026, at 9:44 PM UTC
End time: Friday, September 11, 2026, at 11:56 AM UTC
Root cause: A recent code change caused the event validation process to display incorrect warning banners.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Mon Sep 7 07:48:06 2026 |
|---|
| Description: | Title: Some users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
User impact: Users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events.
More info: We've confirmed that there is no impact to actual attendee capacity.
Users may see the following message:
"Attendee capacity issue. This event is set for 10,000 attendees, but your current limit is 3,000. Attendees above this limit won't be able to join. Contact your Teams administrator to restore capacity."
Current status: We've determined that the fix is taking longer than anticipated to deploy. We'll continue to monitor deployment progress as it continues.
Scope of impact: Your organization is affected by this event, and users seeing incorrect attendee capacity warnings when configuring Microsoft Teams Town Hall events are impacted.
Estimated time to resolve: Tuesday, September 1, 2026
Next update by: Friday, September 11, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Sep 2 07:04:04 2026 |
|---|
| Description: | Title: Some users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
User impact: Users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events.
More info: We've confirmed that there is no impact to actual attendee capacity.
Users may see the following message:
"Attendee capacity issue. This event is set for 10,000 attendees, but your current limit is 3,000. Attendees above this limit won't be able to join. Contact your Teams administrator to restore capacity."
Current status: We're progressing with the fix deployment and expect completion by Monday, September 7, 2026.
Scope of impact: Your organization is affected by this event, and users seeing incorrect attendee capacity warnings when configuring Microsoft Teams Town Hall events are impacted.
Estimated time to resolve: Tuesday, September 1, 2026
Next update by: Monday, September 7, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Aug 20 09:03:30 2026 |
|---|
| Description: | Title: Some users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events
User impact: Users see incorrect attendee capacity warnings when configuring Microsoft Teams town hall events.
More info: We've confirmed that there is no impact to actual attendee capacity.
Users may see the following message:
"Attendee capacity issue. This event is set for 10,000 attendees, but your current limit is 3,000. Attendees above this limit won't be able to join. Contact your Teams administrator to restore capacity."
Current status: We've confirmed that some users are incorrectly seeing attendee capacity warnings when configuring Microsoft Teams town hall events. We've also confirmed that there is no impact to actual attendee capacity. We've deployed a fix to the service intended to remove the banner and expect the fix to reach the affected infrastructure in early September, 2026.
Scope of impact: Your organization is affected by this event, and users seeing incorrect attendee capacity warnings when configuring Microsoft Teams Town Hall events are impacted.
Estimated time to resolve: Tuesday, September 1, 2026
Next update by: Wednesday, September 2, 2026, at 11:30 AM UTC
|
|---|
|
EX1470457 - Some users may be unable to send or receive Exchange Online email through the native macOS mail app
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 8 20:00:00 2026 |
|---|
| End Time: | Thu Sep 10 23:35:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Sep 11 00:19:58 2026 |
|---|
| Root Cause: | A service feature deployment affecting rate limitations contained changes resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 11 00:10:53 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive Exchange Online email through the native macOS mail app
User impact: Users may have been unable to send or receive Exchange Online email through the native macOS mail app.
Final status: We've disabled the impacting changes and confirmed through internal telemetry that impact has been fully remediated.
Scope of impact: Some users attempting to access the native macOS mail app were impacted.
Start time: Wednesday, September 9, 2026, at 12:00 AM UTC
End time: Friday, September 11, 2026, at 3:35 AM UTC
Root cause: A service feature deployment affecting rate limitations contained changes resulting in impact.
Next steps:
- We're reviewing our update testing and validation methods to better identify issues such as this prior to deployment so we can ensure we prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 10 22:35:43 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive Exchange Online email through the native macOS mail app
User impact: Users may be unable to send or receive Exchange Online email through the native macOS mail app.
Current status: We've identified that a service feature deployment affecting rate limitations contained changes resulting in impact. We're moving to disable the problematic changes and anticipate this should be fully in effect by our next scheduled update, at which point we'll verify the issue is resolved through internal telemetry.
Scope of impact: Some users attempting to access the native macOS mail app are impacted. This information may be updated as our investigation continues.
Start time: Wednesday, September 9, 2026, at 12:00 AM UTC
Root cause: A service feature deployment affecting rate limitations contained changes resulting in impact.
Next update by: Friday, September 11, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Sep 10 22:12:58 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive Exchange Online email through the native macOS mail app
User impact: Users may be unable to send or receive Exchange Online email through the native macOS mail app.
Current status: We've clarified that reporting users are seeing impact to the native mail app on macOS and updated the Title and User impact fields of this communication accordingly. We're reviewing service logs and telemetry data to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Some users attempting to access the native macOS mail app are impacted. This information may be updated as our investigation continues.
Next update by: Friday, September 11, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Sep 10 21:10:32 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive Exchange Online email through the native macOS mail app
User impact: Users may be unable to send or receive Exchange Online email through the native macOS mail app.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
MO1465074 - Users may experience issues when utilizing multiple Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Aug 31 10:56:00 2026 |
|---|
| End Time: | Thu Sep 3 06:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 10 20:47:34 2026 |
|---|
| Root Cause: | An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 20:47:34 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 13:28:10 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 13:11:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Sep 8 05:35:25 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sat Sep 5 15:48:19 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 3 16:04:09 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may have experienced issues when utilizing multiple Microsoft 365 services.
More info: Impact is fully resolved. Previously identified impact included the services and scenarios listed below.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted access and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
- Users couldn’t download email message attachments through any Exchange Online connection method.
- Users may have been unable to sign in to Outlook on the web.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated, and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may have been stale and not updated automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experienced delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Final status: Based on our telemetry all previously impacted services have remained healthy since impact was remediated on Thursday, September 3, 2026, at 10:00 AM UTC, and this issue is resolved.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may have been affected by this event.
Start time: Monday, August 31, 2026, at 2:56 PM UTC
End time: Thursday, September 3, 2026, at 10:00 AM UTC
Preliminary root cause: An issue within a core access configuration used by multiple Microsoft 365 services was resulting in impact.
Next steps:
- We’re evaluating our core service configurations to prevent the recurrence of similar impact in the future. In addition, we're further reviewing our monitoring systems to ensure we identify and are expediently alerted to these types of scenarios.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Sep 3 14:24:20 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is now fully resolved. Previously identified impact included the services and scenarios listed below.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
- Users couldn’t download email message attachments through any Exchange Online connection method.
- Users may have been unable to sign in to Outlook on the web.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: All user impact scenarios are now resolved as we rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of our infrastructure. We will continue to monitor our telemetry to ensure all services remain healthy and plan to close this communication by our next scheduled update.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Friday, September 4, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 12:24:26 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Outlook on the web, Outlook mobile apps, and Outlook for Mac. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods were affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We discovered an issue in less than one percent of our infrastructure, where our additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. We remain committed to restoring all services to all users and will continue to carefully monitor our telemetry to ensure recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 10:26:52 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: While monitoring service telemetry closely, we identified a small volume of errors affecting mail flow functionality. We're conducting targeted restarts to reduce the number of errors and alleviate impact. In parallel, we're continuing to analyze service health telemetry to determine if any additional mitigation actions are required to restore normal functionality.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 08:27:31 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We're continuing to implement further mitigation actions where required to resolve any outstanding impact associated with this incident. Customer feedback and reports from our telemetry remain positive, and service health is stable. While this work is underway, we're actively monitoring the service closely to ensure stability is consistent.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 06:25:08 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From a Microsoft Purview Communication Compliance perspective, the issue has been mitigated and customers should now be able to access and use the portal as expected. We are currently processing any policy activity that may have been delayed during the event, and any missed policy hits, alerts, or related results are expected to appear within the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We're performing additional remediation efforts where necessary to address any remaining impact from this incident. Reports from telemetry data and customer feedback are aligned, indicating a sustained recovery. We're actively monitoring the situation closely to ensure impact is completely mitigated.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 04:25:02 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- From Purview Communications compliance perspective, this issue is mitigated. Customers should be able to use the portal. We are running backfill for any missed policy hits and those should appear in the next 24 to 48 hours.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We're continuing to closely monitor the service to ensure sustained stability, and signals from telemetry and customer feedback remain positive. In parallel, we're conducting additional remediation actions where required to resolve any lingering residual impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Sep 3 02:20:32 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We've confirmed that our services remain stable, and both telemetry and customer reports indicate that the issue has been largely mitigated. We're continuing to address any lingering issues while we remain engaged in an extended monitoring period to validate sustained recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Sep 3 00:16:34 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: Our recovery metrics remain positive, with monitoring continuing to indicate that the service is stable and there is a constant reduction in the number of affected users. We’re continuing to validate recovery through targeted remediation actions and service health checks. We’ll maintain targeted monitoring and validation actions to confirm recovery outcomes and identify any remaining impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 22:21:18 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: Ongoing monitoring continues to show positive recovery progress, with impact no longer observed for most previously affected users. We’re continuing to monitor service health and implement targeted remediation efforts to validate recovery progress and help ensure ongoing service stability.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 20:28:48 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact is currently limited to Microsoft Outlook on the web. Previously identified impact included the services and scenarios listed below. We will continue to update this list as our investigation progresses and our understanding of the issue evolves.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We continue to confirm through ongoing monitoring that recovery efforts are progressing successfully across the affected services, with most impacted users no longer experiencing disruption. We’re remaining focused on identifying and resolving any remaining isolated scenarios while closely monitoring service health and implementing targeted mitigation measures to maintain stability and deliver a consistent, reliable user experience.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 18:00:45 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We continue to see sustained recovery across the affected services, with most users no longer experiencing impact. We’re continuing to focus on the remaining areas of impact and are progressing our mitigation efforts to address these residual scenarios. We’re closely monitoring service health throughout this work to maintain stability.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 16:03:04 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: The majority of services are restored for most users, and we continue to observe broad service recovery. We recognize that some users may still experience residual impact, and addressing these remaining scenarios continues to be our highest priority. We’re actively progressing our mitigation efforts and closely monitoring service health as we work to ensure full recovery for all users.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 14:30:14 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may have been unable to create, upload, or retrieve print jobs.
Current status: We've confirmed that impact related to OneDrive for Business, SharePoint Online, and Universal Print are now resolved. We recognize that while the majority of services are restored for most users, the remaining issues are disruptive for those still impacted. We're continuing to address residual impact with the highest priority so we can ensure resolution for all users.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 13:36:24 2026 |
|---|
| Description: | We’ve confirmed after a period of monitoring that impact related to OneDrive for Business and SharePoint Online is now resolved.
OneDrive for Business and SharePoint Online:
- Users may have been unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may have also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may have seen partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 13:23:29 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
- Users may be unable to sign in to Outlook on the web.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displayed offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
Current status: We’re working on additional mitigation measures for the portion of infrastructure which have not yet returned to healthy service levels after deployment of our primary remediation. Service availability remains above 99 percent and our monitoring shows impact is resolved for the majority of users. We remain engaged and committed to fully resolving this issue for all users.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 12:21:00 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
RECOVERED
Microsoft Graph:
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Service telemetry indicates recovery of the majority of previously impacted authentication and protocol connectivity scenarios.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that required Microsoft 365 grounding, such as email content, may have failed.
- Users may have experienced failures for scenarios that rely on access to Exchange Online data.
- Users prompts may have failed or they may have experienced degradation when utilizing Cowork.
Current status: Service availability remains stable above 99%, and telemetry indicates sustained recovery across the affected environments. The primary remediation has been deployed across the majority of impacted infrastructure, with remaining deployment and validation activities progressing as expected. Most previously affected users should no longer experience issues related to this event, though a small subset may continue to see intermittent impact while final recovery validation is completed. Our remaining efforts are focused on validating sustained recovery and identifying any remaining infrastructure requiring remediation. Enhanced monitoring remains in place as we continue recovery validation activities.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 09:37:26 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Exchange Online:
- Users can't download email message attachments through any Exchange Online connection method.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
*RECOVERED*
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may have been unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may have been unable to connect to Exchange Web Services (EWS)
- Users may have been unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Users may have experienced delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may have experienced issues authenticating into the admin center.
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
Current status: We're continuing to observe positive recovery trends across the affected environments, with service availability remaining stable above 99 percent. Based on our telemetry, we expect the vast majority of previously impacted users should no longer be experiencing issues related to this event. Our deployment activities are progressing as expected, and we're continuing to implement the remaining portions of our remediation across affected infrastructure to help ensure recovery is sustained over time. We remain focused on validating end-to-end service health, monitoring for any residual impact, and confirming that recovery is maintained for scenarios that rely on REST and Graph API connection methods. While a small subset of users may still encounter intermittent impact as the deployment continues to progress, current telemetry indicates continued improvement and no signs of broader service degradation. We're maintaining enhanced monitoring and will provide further updates as recovery work continues.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 02:44:32 2026 |
|---|
| Description: | Our telemetry indicates service availability remains stable above 99 percent, and we expect the majority of users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 00:39:19 2026 |
|---|
| Description: | We're observing service availability recovering to above 99 percent across the affected environments, and we expect the majority of previously affected users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 23:30:21 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may be unable to connect to Exchange Web Services (EWS)
- Users may be unable to use room finder in Outlook calendars.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
Current status: Based on our telemetry, we expect a small subset of users may still see impact across the listed scenarios, though we're continuing our work to balance the implementation of our fixes across the infrastructure to achieve withstanding recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 21:31:44 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may be unable to connect to Exchange Web Services (EWS)
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
Current status: We're continuing to closely monitor service health as we carefully expand our reiterative corrective actions across additional regions. This work involves re-deploying our targeted fixes to the dependent authentication components to ensure service resilience, while balancing ongoing traffic patterns to avoid additional residual impact. Most users should see recovery across the majority of impacted scenarios, though some scenarios, including those reliant on Graph API and Representational State Transfer (REST) connection methods, will remain degraded until our mitigation efforts are complete.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 18:29:18 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
- Users prompts may fail or they may experience degradation when utilizing Cowork.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
- Users may be unable to connect to Exchange Web Services (EWS)
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may have failed.
- Users may have experienced issues with Microsoft Teams Room (MTR) devices and desktop phones displaying as offline in the Teams admin center.
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Current status: Most users should see recovery across the majority of impacted scenarios, though some scenarios will remain degraded until our mitigation efforts are complete. We're continuing to progress our mitigation efforts across multiple workstreams as we work to restore the service to healthy levels. We understand the challenges incidents such as these have on your organization and we’ll continue to closely monitor service health and prevent further impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 1:30 PM UTC An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 14:58:50 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with search and users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Microsoft Teams:
- Users may have experienced issues creating, deleting, and editing Teams channels.
- Users may have experienced issues with calendar functionality.
Current status: We’re continuing to advance multiple workstreams to restore service and prevent additional impact. We’re prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, we’re investigating remaining reports of impact and evaluating additional actions to support full service recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 14:01:13 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Microsoft Graph:
- Users may experience failures for scenarios that rely on access to Exchange Online data.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Current status: We are carefully implementing corrective actions while maintaining enhanced monitoring to ensure services remain stable as recovery progresses.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
|
|---|
|
| Time: | Tue Sep 1 12:58:26 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Resolved
Microsoft Purview:
- Users can now access the Microsoft Purview portal.
- Any policy hits, alerts, or processing activities delayed during the event are expected to appear over the next 24 to 48 hours as recovery validation continues.
- Additionally, in Microsoft Purview Communication Compliance, users may have experienced errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies, and policy creation or evaluation delays.
Microsoft Defender XDR:
- Users may have experienced intermittent authorization failures across solutions in Defender.
Current status: We've observed continued recovery across previously impacted Exchange Online scenarios, with core mail flow functionality remaining healthy. Our focus remains on validating recovery across dependent Microsoft 365 experiences and confirming that remaining impact scenarios are fully addressed. We're maintaining enhanced monitoring while engineering teams complete end-to-end validation before determining whether any further corrective actions are required.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 11:57:30 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
- Users may experience failures for scenarios that rely on access to Exchange Online data.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Service telemetry indicates recovery of core mail flow and search functionality.
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
- Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
- Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Current status: Service telemetry continues to indicate recovery across previously impacted scenarios as remediation progresses through the remaining affected infrastructure. Core Exchange Online experiences, including mail flow and search functionality, have recovered. Our focus has shifted toward validating recovery across remaining Microsoft 365 services. We're actively monitoring service health, assessing any residual pockets of impact, and confirming end-to-end functionality across affected workloads.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 10:18:21 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
- Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
- Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing to apply the targeted remediation across the remaining affected infrastructure where needed. Service telemetry continues to show positive recovery trends, with availability improving across previously impacted scenarios. We're actively validating that authentication, connectivity, and search experiences are returning to expected service levels, while maintaining enhanced monitoring to ensure improvements are sustained and any residual impact is addressed.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 06:58:15 2026 |
|---|
| Description: | A substantial portion of the remediation deployment has been completed, and organizations whose environments remain affected are expected to recover as the deployment reaches the relevant infrastructure. As remediation progresses, we're focused on validating sustained recovery and monitoring for any remaining pockets of impact before determining whether any additional corrective actions are required.
This quick update is designed to give the latest information on this issue.
We recognise the impact this issue may be causing for your organization and want to assure you that resolving it remains our highest priority. We appreciate your patience and understanding as we continue working toward mitigation.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 06:01:14 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
- Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
- Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
- Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
- Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Outlook for iOS and Android:
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Microsoft Teams:
- Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
- Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
- Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
- Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
- Admins may experience issues authenticating into the admin center.
Universal Print:
- Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing to apply the targeted authentication component fix across the remaining affected infrastructure where necessary. Service telemetry continues to indicate recovery, with availability increasing across previously impacted scenarios as remediation progresses. We're validating that authentication, connectivity and search operations are returning to expected service levels while monitoring for any residual impact and confirming that the remediation is delivering broad mitigation across affected Exchange Online scenarios. As recovery signals continue to trend positively, we're maintaining extended monitoring across affected service workflows to ensure improvements are sustained.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 04:56:42 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing to reapply the targeted authentication component fix to the remaining affected infrastructure where necessary. While our remediation effort is underway, indications from service telemetry remain positive. We're observing an overall increase in service availability, and we're monitoring this closely to ensure we're progressing towards a broad mitigation.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 04:02:06 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: Reapplying the targeted authentication component fix and restarting affected infrastructure segments has led to measurable progress. We're observing gradual improvements within telemetry data related to search functionality across the remaining affected infrastructure, and we're continuing this remediation effort across additional infrastructure segments while closely monitoring service health telemetry to ensure we're progressing towards a broader recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 02:39:32 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: Our efforts to restart affected sections infrastructure and re-apply the targeted authentication component fix has yielded progress, and we're observing incremental improvement reflected in the service health telemetry associated with search functionality across a sample of the affected environment. We're continuing this action for additional sections of infrastructure as we monitor closely to ensure widespread remediation.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:54:56 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing our work to restart affected infrastructure and re-apply the targeted authentication component fix to recover search functionality across the affected environments.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:00:45 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're persistently reviewing what additional actions may be required to re-apply our targeted authentication component fix and facilitate the recovery of remaining sections of infrastructure correlated with search functionality to ensure the full remediation. Meantime, we've validated persistent recovery for mail flow across the environment and are focusing our work on recovering search functionality.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 23:49:40 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're observing widespread recovery to Exchange Online mail connectivity, though the draining of backlogged mail queues may take longer for some organizations due to the volume of previously queued messages. Our recovery efforts are now focused on re-applying our targeted authentication component fix and restarting certain instances of infrastructure correlated with search functionality to ensure the full restoration of the associated scenarios.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 22:53:25 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're observing residual impact to some downstream scenarios, including search. We're incrementally restarting corresponding instances of infrastructure to ensure our previously applied authentication components are fully saturated, and we're working to identify whether any additional actions are required to achieve resolution.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 21:54:03 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
- Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, such as failures when attempting to use the search function, within Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're closely monitoring the health of the service environment amidst our ongoing recovery work, and we're observing some sections of affected infrastructure which aren't accepting the re-applied authentication components as readily as expected. Users can expect to see continued recovery to email delivery, while users may see residual impact to downstream and dependent scenarios, including search, across affected services. We're working to identify whether any additional actions are required to expedite full recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 20:57:23 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
Microsoft 365 Copilot:
-Users' Copilot prompts that require Microsoft 365 grounding, such as email content, may fail
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We’re seeing improvement across the affected environments as we observe the successful albeit gradual implementation of our mitigation actions. Users should expect to see varying degrees of recovery and residual delays until these actions have completed. We're closely monitoring the health of the service environment and will continue to aggressively pursue any available options to expedite our ongoing recovery work, and we'll provide an estimated recovery timeline as soon as one becomes available.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 19:58:05 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're progressively restarting targeted sections of affected infrastructure to ensure the re-applied authentication components are effectively implemented across affected services. We expect this will aid the recovery of affected scenarios. Users should expect delayed delivery of backlogged messages and residual impact across downstream scenarios as these actions are continuing. We'll provide an expected recovery time as soon as one becomes available to us.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 19:32:35 2026 |
|---|
| Description: | We're expanding the aforementioned mitigation action more widely across the affected environments as we closely track the recovery of affected scenarios. Users should primarily begin to see gradual recovery to mail flow. Secondarily, and in parallel to the primary mitigation action previously described, we're restarting targeted sections of affected infrastructure to ensure the acceptance of the re-applied authentication components across affected services and aid the recovery of the downstream scenarios.
This quick update is designed to give the latest information on this issue.
Next update by: Tuesday, September 1, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 18:53:24 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
-Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
-Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
-Microsoft Teams Room (MTR) devices and desktop phones display as offline in the Teams admin center.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing to implement a targeted mitigation to re-apply core authentication components, and we're expanding this action more widely across the affected environments as we closely track the recovery of affected downstream scenarios. Users may notice gradual recovery to the scenarios identified in the "More info" section as our mitigation action takes effect in their corresponding sections of infrastructure, and we're continuing to review whether any additional actions may be required to achieve withstanding recovery across all affected scenarios. We'll provide an estimated time to resolution as soon as one is available.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 18:40:12 2026 |
|---|
| Description: | We're implementing a targeted mitigation to re-apply core authentication components across a sample of affected infrastructure and are closely monitoring corresponding service telemetry to validate the efficacy of this action. As a result of this work, some users are beginning to see recovery to some impacted scenarios. We'll continue to incrementally expand this mitigation action more widely across the affected environments as quickly as possible.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, August 31, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 17:53:52 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're continuing our targeted review of affected infrastructure and recent changes made to the service to definitively confirm the cause of impact. We're additionally continuing to test and implement various mitigation strategies to apply the necessary authentication component, which have so far yielded positive results. We're monitoring these tests and mitigative actions closely and will provide an estimated time to resolution as soon as one is available.
We understand the impact that events like these can have for your organization and we appreciate your patience as we work to mitigate this issue with the highest priority.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 16:36:45 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Universal Print:
-Users may be unable to create, upload, or retrieve print jobs.
Current status: We're reexamining recent changes made to the service to determine why the authentication components aren't being deployed as expected. Additionally, we are exploring every avenue to safely restore the components, including reverting an update the affected infrastructure recently received. We're performing additional tests to determine whether this will provide relief.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 15:32:27 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Microsoft 365 Admin Center:
-Admins may experience issues authenticating into the admin center.
Current status: We're continuing to perform comprehensive tests to ensure our mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, we're exploring alternative remediation avenues to minimize impact in the interim.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 15:00:11 2026 |
|---|
| Description: | We're continuing to fine-tune our remediation strategy as our internal tests progress. We'll aim to provide an estimated time for remediation as soon as it's available.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, August 31, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 14:25:35 2026 |
|---|
| Description: | Title: Users may experience issues when utilizing multiple Microsoft 365 services
User impact: Users may experience issues when utilizing multiple Microsoft 365 services.
More info: Impact includes, but may not be limited to, the below services and scenarios. We will update this list as our understanding of the issue progresses.
OneDrive for Business and SharePoint Online:
-Users may be unable to load or refresh portions of OneDrive and SharePoint, including account and storage information, search results, Favorites, Followed and Shared With Me content, recent files, lists, and news.
Some users may also experience delayed or failed file opening, Office policy-label retrieval, OneDrive synchronization, mobile camera upload, and video playback.
Users may see partial page failures, missing or stale content, repeated retries, and operation timeouts rather than a complete platform outage.
Exchange Online:
-Users may be unable to connect to, or experience degraded functionality, with Exchange Online. All connection methods are affected.
Microsoft Teams:
-Users may experience issues with calendar functionality and search. Users’ presence may be stale and not update automatically or through manual adjustment. User location adjustment may fail.
Microsoft Purview:
-Users may face intermittent authorization failures across solutions in Purview. Purview admins can’t access the portal.
Additionally, in Microsoft Purview Communication Compliance, users may see errors when loading Communication Compliance policies and Data Loss Prevention (DLP) policies. Communication Compliance policy creation and evaluation may be delayed.
Microsoft Defender XDR:
-Users may experience intermittent authorization failures across solutions in Defender.
Current status: We've identified issues related to a core authentication configuration used by multiple Microsoft 365 services which is resulting in the impact outlined above. We've identified a potential remediation and we're performing tests to ensure its efficacy before applying it more broadly.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Next update by: Monday, August 31, 2026, at 6:30 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 7:30 PM UTC
|
|---|
|
EX1464935 - Users may be unable to connect to, or experience degraded functionality with Exchange Online
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Aug 31 10:56:00 2026 |
|---|
| End Time: | Thu Sep 3 06:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 10 20:46:30 2026 |
|---|
| Root Cause: | An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 20:46:30 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 13:28:26 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 13:11:34 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Sep 8 05:34:59 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sat Sep 5 15:48:40 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 3 16:05:37 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may have been unable to connect to, or experienced degraded functionality with Exchange Online.
More info: We've confirmed that the component issue impacted other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
Users may have experienced a variety of symptoms related to this event, including but not limited to:
- Users couldn't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Access-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work.
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may have been unable to use room finder in Outlook calendars.
- Users may have been unable to sign in to Outlook on the web.
Final status: Based on our telemetry all previously impacted services have remained healthy since impact was remediated on Thursday, September 3, 2026, at 10:00 AM UTC, and this issue is resolved.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may have been affected by this event.
Start time: Monday, August 31, 2026, at 2:56 PM UTC
End time: Thursday, September 3, 2026, at 10:00 AM UTC
Preliminary root cause: An issue within a core access configuration used by multiple Microsoft 365 services was resulting in impact.
Next steps:
- We’re evaluating our core service configurations to prevent the recurrence of similar impact in the future. In addition, we're further reviewing our monitoring systems to ensure we identify and are expediently alerted to these types of scenarios.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Sep 3 14:23:20 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacted other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online was the most predominantly impacted service.
Users may have experienced a variety of symptoms related to this event, including but not limited to:
- Users couldn't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work.
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may have been unable to use room finder in Outlook calendars.
- Users may have been unable to sign in to Outlook on the web.
Current status: All user impact scenarios are now resolved as we rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of our infrastructure. We will continue to monitor our telemetry to ensure all services remain healthy and plan to close this communication by our next scheduled update.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Friday, September 4, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 12:23:14 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We discovered an issue in less than one percent of our infrastructure, where our additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. We remain committed to restoring all services to all users and will continue to carefully monitor our telemetry to ensure recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 6:30 PM UT
|
|---|
|
| Time: | Thu Sep 3 10:26:54 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: While monitoring service telemetry closely, we identified a small volume of errors affecting mail flow functionality. We're conducting targeted restarts to reduce the number of errors and alleviate impact. In parallel, we're continuing to analyze service health telemetry to determine if any additional mitigation actions are required to restore normal functionality.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 08:27:28 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We're continuing to implement further mitigation actions where required to resolve any outstanding impact associated with this incident. Customer feedback and reports from our telemetry remain positive, and service health is stable. While this work is underway, we're actively monitoring the service closely to ensure stability is consistent.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 06:23:13 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We're performing additional remediation efforts where necessary to address any remaining impact from this incident. Reports from telemetry data and customer feedback are aligned, indicating a sustained recovery. We're actively monitoring the situation closely to ensure impact is completely mitigated.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 04:14:51 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We're continuing to closely monitor the service to ensure sustained stability, and signals from telemetry and customer feedback remain positive. In parallel, we're conducting additional remediation actions where required to resolve any lingering residual impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Sep 3 02:21:37 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We've confirmed that our services remain stable, and both telemetry and customer reports indicate that the issue has been largely mitigated. We're continuing to address any lingering issues while we remain engaged in an extended monitoring period to validate sustained recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Sep 3 00:23:02 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: Our recovery metrics remain positive, with monitoring continuing to indicate that the service is stable and there is a constant reduction in the number of affected users. We’re continuing to validate recovery through targeted remediation actions and service health checks. We’ll maintain targeted monitoring and validation actions to confirm recovery outcomes and identify any remaining impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 22:16:05 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: Ongoing monitoring continues to show positive recovery progress, with impact no longer observed for most previously affected users. We’re continuing to monitor service health and implement targeted remediation efforts to validate recovery progress and help ensure ongoing service stability.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 20:21:16 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We continue to observe positive recovery trends through ongoing monitoring, with most affected users no longer experiencing disruption. We remain focused on identifying and resolving any remaining issues while implementing targeted mitigations to support a stable and consistent user experience.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 18:00:23 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We've confirmed that the majority of users remain mitigated. We're continuing to advance several workstreams as we work toward full resolution for all users and in parallel, we're maintaining enhanced monitoring throughout this work to ensure service stability.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Thursday, September 3, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Sep 2 16:31:15 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We’ve completed a restart of affected Outlook on the web infrastructure, and service telemetry indicates that the majority of users have recovered. We’re continuing to closely monitor service health as we roll out more durable fixes designed to address the underlying conditions contributing to the impact.
In parallel, we’re working directly with affected users and examining reports of continued impact to gather additional diagnostic information and identify any remaining issues.
We remain focused on fully restoring service for all affected users and will continue deploying our fixes, investigating reports of impact, and monitoring service health until we’re confident the issue is fully resolved.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 14:29:53 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We recognize that while service is restored for most customers, the remaining issues are disruptive for those still impacted. We are prioritizing fully resolving the issue for all customers.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 13:23:19 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
- Users may be unable to sign in to Outlook on the web.
Current status: We’re working on additional mitigation measures for the portion of infrastructure which have not yet returned to healthy service levels after deployment of our primary remediation. Service availability remains above 99 percent and our monitoring shows impact is resolved for the majority of users. We remain engaged and committed to fully resolving this issue for all users.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 12:22:25 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
Current status: Service availability remains stable above 99%, and telemetry indicates sustained recovery across the affected environments. The primary remediation has been deployed across the majority of impacted infrastructure, with remaining deployment and validation activities progressing as expected. Most previously affected users should no longer experience issues related to this event, though a small subset may continue to see intermittent impact while final recovery validation is completed. Our remaining efforts are focused on validating sustained recovery and identifying any remaining infrastructure requiring remediation. Enhanced monitoring remains in place as we continue recovery validation activities.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 02:44:50 2026 |
|---|
| Description: | Our telemetry indicates service availability remains stable above 99 percent, and we expect the majority of users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 00:39:37 2026 |
|---|
| Description: | We're observing service availability recovering to above 99 percent across the affected environments, and we expect the majority of previously affected users should no longer be seeing impact from this issue. Our continued focus is on balancing the implementation of our fixes across remaining portions of affected infrastructure to ensure persistent recovery.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 23:31:34 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Users can't download email message attachments through any Exchange Online connection method.
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
- Users may be unable to use room finder in Outlook calendars.
Current status: Based on our telemetry, we expect a small subset of users may still see impact across the listed scenarios, though we're continuing our work to balance the implementation of our fixes across the infrastructure to achieve withstanding recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 21:30:32 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We're continuing to closely monitor service health as we carefully expand our reiterative corrective actions across additional regions. This work involves re-deploying our targeted fixes to the dependent authentication components to ensure service resilience, while balancing ongoing traffic patterns to avoid additional residual impact. Most users should see recovery across the majority of impacted scenarios, though some scenarios, including those reliant on Graph API and Representational State Transfer (REST) connection methods, will remain degraded until our mitigation efforts are complete.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 18:30:08 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: Most users should see recovery across the majority of impacted scenarios, though some scenarios will remain degraded until our mitigation efforts are complete. We're continuing to progress our mitigation efforts across multiple workstreams as we work to restore the service to healthy levels. We understand the challenges incidents such as these have on your organization and we’ll continue to closely monitor service health and prevent further impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 18:30:02 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: Most users should see recovery across the majority of impacted scenarios, though some scenarios will remain degraded until our mitigation efforts are complete. We're continuing to progress our mitigation efforts across multiple workstreams as we work to restore the service to healthy levels. We understand the challenges incidents such as these have on your organization and we’ll continue to closely monitor service health and prevent further impact.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 14:59:44 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We’re continuing to advance multiple workstreams to restore service and prevent additional impact. We’re prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, we’re investigating remaining reports of impact and evaluating additional actions to support full service recovery.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 14:00:57 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We are carefully implementing corrective actions while maintaining enhanced monitoring to ensure services remain stable as recovery progresses.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 12:59:48 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We've observed continued recovery across previously impacted Exchange Online scenarios, with core mail flow functionality remaining healthy. Our focus remains on validating recovery across dependent Microsoft 365 experiences and confirming that remaining impact scenarios are fully addressed. We're maintaining enhanced monitoring while engineering teams complete end-to-end validation before determining whether any further corrective actions are required.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 12:00:28 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: Service telemetry continues to indicate recovery across previously impacted scenarios as remediation progresses through the remaining affected infrastructure. Core Exchange Online experiences, including mail flow and search functionality, have recovered. Our focus has shifted toward validating recovery across remaining Microsoft 365 services. We're actively monitoring service health, assessing any residual pockets of impact, and confirming end-to-end functionality across affected workloads.
Scope of impact: Users attempting to perform any of the outlined impact scenarios may be affected by this event.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 10:18:31 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We're continuing to apply the targeted remediation across the remaining affected infrastructure where needed. Service telemetry continues to show positive recovery trends, with availability improving across previously impacted scenarios. We're actively validating that authentication, connectivity, and search experiences are returning to expected service levels, while maintaining enhanced monitoring to ensure improvements are sustained and any residual impact is addressed.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 06:58:06 2026 |
|---|
| Description: | A substantial portion of the remediation deployment has been completed, and organizations whose environments remain affected are expected to recover as the deployment reaches the relevant infrastructure. As remediation progresses, we're focused on validating sustained recovery and monitoring for any remaining pockets of impact before determining whether any additional corrective actions are required.
This quick update is designed to give the latest information on this issue.
We recognise the impact this issue may be causing for your organization and want to assure you that resolving it remains our highest priority. We appreciate your patience and understanding as we continue working toward mitigation.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 06:00:33 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
- Delays or failures when sending or receiving email messages via Outlook for iOS and Android.
Current status: We're continuing to apply the targeted authentication component fix across the remaining affected infrastructure where necessary. Service telemetry continues to indicate recovery, with availability increasing across previously impacted scenarios as remediation progresses. We're validating that authentication, connectivity and search operations are returning to expected service levels while monitoring for any residual impact and confirming that the remediation is delivering broad mitigation across affected Exchange Online scenarios. As recovery signals continue to trend positively, we're maintaining extended monitoring across affected service workflows to ensure improvements are sustained.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 04:54:53 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're continuing to reapply the targeted authentication component fix to the remaining affected infrastructure where necessary. While our remediation effort is underway, indications from service telemetry remain positive. We're observing an overall increase in service availability, and we're monitoring this closely to ensure we're progressing towards a broad mitigation.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 04:00:26 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: Reapplying the targeted authentication component fix and restarting affected infrastructure segments has led to measurable progress. We're observing gradual improvements within telemetry data related to search functionality across the remaining affected infrastructure, and we're continuing this remediation effort across additional infrastructure segments while closely monitoring service health telemetry to ensure we're progressing towards a broader recovery.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 02:39:47 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: Our efforts to restart affected sections infrastructure and re-apply the targeted authentication component fix has yielded progress, and we're observing incremental improvement reflected in the service health telemetry associated with search functionality across a sample of the affected environment. We're continuing this action for additional sections of infrastructure as we monitor closely to ensure widespread remediation.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:55:10 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're continuing our work to restart affected infrastructure and re-apply the targeted authentication component fix to recover search functionality across the affected environments.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:01:23 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're persistently reviewing what additional actions may be required to re-apply our targeted authentication component fix and facilitate the recovery of remaining sections of infrastructure correlated with search functionality to ensure the full remediation. Meantime, we've validated persistent recovery for mail flow across the environment and are focusing our work on recovering search functionality.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 23:52:06 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're observing widespread recovery to Exchange Online mail connectivity, though the draining of backlogged mail queues may take longer for some organizations due to the volume of previously queued messages. Our recovery efforts are now focused on re-applying our targeted authentication component fix and restarting certain instances of infrastructure correlated with search functionality to ensure the full restoration of the associated scenarios.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 22:55:12 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're observing residual impact to some downstream scenarios, including search. We're incrementally restarting corresponding instances of infrastructure to ensure our previously applied authentication components are fully saturated, and we're working to identify whether any additional actions are required to achieve resolution.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 21:54:43 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're closely monitoring the health of the service environment amidst our ongoing recovery work, and we're observing some sections of affected infrastructure which aren't accepting the re-applied authentication components as readily as expected. Users can expect to see continued recovery to email delivery, while users may see residual impact to downstream and dependent scenarios, including search, across affected services. We're working to identify whether any additional actions are required to expedite full recovery.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 20:59:44 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We’re seeing improvement across the affected environments as we observe the successful albeit gradual implementation of our mitigation actions. Users should expect to see varying degrees of recovery and residual delays until these actions have completed. We're closely monitoring the health of the service environment and will continue to aggressively pursue any available options to expedite our ongoing recovery work, and we'll provide an estimated recovery timeline as soon as one becomes available.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 20:01:08 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're progressively restarting targeted sections of affected infrastructure to ensure the re-applied authentication components are effectively implemented across affected services. We expect this will aid the recovery of affected scenarios. Users should expect delayed delivery of backlogged messages and residual impact across downstream scenarios as these actions are continuing. We'll provide an expected recovery time as soon as one becomes available to us.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 19:33:55 2026 |
|---|
| Description: | We're expanding the aforementioned mitigation action more widely across the affected environments as we closely track the recovery of affected scenarios. Users should primarily begin to see gradual recovery to mail flow. Secondarily, and in parallel to the primary mitigation action previously described, we're restarting targeted sections of affected infrastructure to ensure the acceptance of the re-applied authentication components across affected services and aid the recovery of the downstream scenarios.
This quick update is designed to give the latest information on this issue.
Next update by: Tuesday, September 1, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 18:57:55 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery work
Current status: We're continuing to implement a targeted mitigation to re-apply core authentication components, and we're expanding this action more widely across the affected environments as we closely track the recovery of affected downstream scenarios. Users may notice gradual recovery to the scenarios identified in the "More info" section as our mitigation action takes effect in their corresponding sections of infrastructure, and we're continuing to review whether any additional actions may be required to achieve withstanding recovery across all affected scenarios. We'll provide an estimated time to resolution as soon as one is available.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Tuesday, September 1, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 18:40:38 2026 |
|---|
| Description: | We're implementing a targeted mitigation to re-apply core authentication components across a sample of affected infrastructure and are closely monitoring corresponding service telemetry to validate the efficacy of this action. As a result of this work, some users are beginning to see recovery to some impacted scenarios. We'll continue to incrementally expand this mitigation action more widely across the affected environments as quickly as possible.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, August 31, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 17:55:39 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're continuing our targeted review of affected infrastructure and recent changes made to the service to definitively confirm the cause of impact. We're additionally continuing to test and implement various mitigation strategies to apply the necessary authentication component, which have so far yielded positive results. We're monitoring these tests and mitigative actions closely and will provide an estimated time to resolution as soon as one is available.
We understand the impact that events like these can have for your organization and we appreciate your patience as we work to mitigate this issue with the highest priority.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 16:36:03 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're reexamining recent changes made to the service to determine why the authentication components aren't being deployed as expected. Additionally, we are exploring every avenue to safely restore the components, including potentially reverting an update the affected infrastructure recently received. We're performing additional tests to evaluate the best course of action moving forward.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 15:43:43 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're continuing to perform comprehensive tests to ensure our mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, we're exploring alternative remediation avenues to minimize impact in the interim.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 14:41:23 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: We've confirmed that the authentication component issue impacts other services beyond Exchange Online. For more information regarding other impact scenarios, please see: MO1465074.
We've opted to keep this post (EX1464935) open as Exchange Online remains the most predominantly impacted service.
Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're continuing to fine-tune our remediation strategy as our internal tests progress. We'll aim to provide an estimated time for remediation as soon as it's available.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Preliminary root cause: An issue within a core authentication configuration used by multiple Microsoft 365 services is resulting in impact.
Next update by: Monday, August 31, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 14:18:57 2026 |
|---|
| Description: | We're continuing to test our remediation strategy and in parallel we're working to confirm whether other services are impacted so we can expand our communications accordingly.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Aug 31 13:23:38 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: Users may experience a variety of symptoms related to this event, including but not limited to:
- Delays, failures, or incomplete results when searching for content within Exchange Online mailboxes.
- Delays or failures when sending or receiving email messages.
- Authentication-related errors when accessing Exchange Online services.
- Difficulties accessing or performing actions within Exchange administration experiences.
- Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We've identified a potential corrective action for the affected infrastructure and are evaluating deployment options. We're monitoring service telemetry and affected Exchange Online transactions to determine whether the action is reducing impact and to better understand the scope of affected scenarios.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Start Time: Monday, August 31, 2026, at 3:08 PM UTC
Next update by: Monday, August 31, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 12:33:59 2026 |
|---|
| Description: | We’ve isolated a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity. We're analyzing service telemetry to identify the underlying source of impact and validate potential remediation options. Additionally, we’re continuing to assess the scope of impact and monitor for additional affected scenarios.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, August 31, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 12:16:11 2026 |
|---|
| Description: | Title: Users may be unable to connect to, or experience degraded functionality with Exchange Online
User impact: Users may be unable to connect to, or experience degraded functionality with Exchange Online.
More info: Users may experience a variety of symptoms related to this event, including but not limited to:
Delays or failures when sending or receiving email messages.
Authentication-related errors when accessing Exchange Online services.
Difficulties accessing or performing actions within Exchange administration experiences.
Intermittent failures affecting mailbox operations and message delivery workflows.
Current status: We're reviewing service telemetry and diagnostic data to isolate the source of the issue after receiving an increase in user-reported issues affecting Exchange Online. We'll keep refining the 'more info' section as additional impacts are identified.
Scope of impact: This issue may impact users attempting to send or receive email messages through Exchange Online. We're continuing our investigation to determine the full scope of affected scenarios and will provide additional information as it becomes available.
Next update by: Monday, August 31, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 11:55:01 2026 |
|---|
| Description: | Title: Investigating user reports of Exchange Online issues
User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.
|
|---|
|
EX1467029 - Users may experience delays sending and receiving email messages from external domains in Exchange Online
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Sep 4 05:00:00 2026 |
|---|
| End Time: | Fri Sep 4 11:15:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 10 11:39:09 2026 |
|---|
| Root Cause: | Exchange Online leverages some Microsoft Defender for Office 365 data, along with a multitude of other data sources, for some of its anti-spam features. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 11:37:09 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Sep 10 11:33:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Sep 4 12:05:15 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may have experienced a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may have experienced intermittent “Server busy” errors, affecting multiple mailboxes.
Depending on the client, the service should attempt to periodically retry sending the email previously impacted by the issue. If the initial sender received an NDR after 24-72 hours (different clients or email providers can vary), they will need to send a new email.
Final status: We've confirmed that the issue is resolved after an extended period of monitoring, and receiving additional confirmations from previously impacted organizations.
Scope of impact: This issue impacted users who may have been attempting to send and receive email messages from external domains in Exchange Online.
Start time: Friday, September 4, 2026, at 9:00 AM UTC
End time: Friday, September 4, 2026, at 3:15 PM UTC
Root cause: Exchange Online leverages some Microsoft Defender for Office 365 data, along with a multitude of other data sources, for some of its anti-spam features.
An upstream distributed data platform experienced elevated service load after a recent change increased the size of read requests beyond the intended physical thresholds. This caused high latency and instability within the platform, which resulted in time windows where portions of the source data were unavailable to dependent processing jobs.
One of the sender-based reputation processing jobs continued to run with substantially less input data than expected and still reported successful completions. Because the pipeline did not have a sufficiently strong completeness check before publishing its output, the reduced data set was incorporated into the reputation information used by the mail-protection service.
This resulted in incomplete reputation-based data and caused legitimate sending IP addressed to be assigned overly restrictive limits by a volume-based reputation control. When the limits were reached, affected emails were throttled and temporarily deferred with ‘451 4.7.500 Server Busy’ responses.
Next Steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Fri Sep 4 11:08:34 2026 |
|---|
| Description: | Telemetry is trending in a positive direction and shows a reduction in the number of new emails getting impacted as the rule disablement progresses across the service.
Next update by: Friday, September 4, 2026, at 4:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Sep 4 10:33:11 2026 |
|---|
| Description: | We've determined that a different machine level throttling rule within the anti-spam features is being incorrectly triggered for a small number of emails, resulting in the remaining impact. We're disabling this specific rule to provide relief and fully mitigate the issue. We expect this to complete within the next hour.
Next update by: Friday, September 4, 2026, at 4:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Sep 4 10:24:49 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Depending on the client, the service should attempt to periodically retry sending the email previously impacted by the issue. If the initial sender received an NDR after 24-72 hours (different clients or email providers can vary), they will need to send a new email.
Current status: We've received a large number of confirmations that the issue is resolved, however, we're reviewing some isolated reports that some organizations are still experiencing delays in email delivery. We're reviewing example SMTP traces from those impacted users to isolate the source of the issue.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Start time: Friday, September 4, 2026, at 9:00 AM UTC
Preliminary root cause: The enforcement of a specific anti-spam model is contributing to impact for a subset of email traffic.
Next update by: Friday, September 4, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 09:28:48 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Depending on the client, the service should attempt to periodically retry sending the email previously impacted by the issue. If the initial sender received an NDR after 24-72 hours (different clients or email providers can vary), they will need to send a new email.
Current status: Telemetry shows that the service is performing as expected for new emails and this is in line with organizations confirming that the issue no longer occurring. We're monitoring email queues and performing final validations to confirm the issue is fully resolved.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Start time: Friday, September 4, 2026, at 9:00 AM UTC
Preliminary root cause: The enforcement of a specific anti-spam model is contributing to impact for a subset of email traffic.
Next update by: Friday, September 4, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Sep 4 09:02:32 2026 |
|---|
| Description: | Some organizations are reporting that they are experiencing relief and that their queued messages are now processing. We continue to monitor the service to confirm full resolution.
Next update by: Friday, September 4, 2026, at 1:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Sep 4 08:26:10 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: We're progressing with the disablement of the specific model, and telemetry is showing a decrease in matching and throttling actions as the rule changes propagate throughout the service. We estimate this rollout will complete within the next 30 minutes.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 07:59:23 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: We've identified that the enforcement of a specific anti-spam model is contributing to impact for a subset of email traffic. We're adding affected IPs from the throttling enforcement to an allow list as an initial mitigation measure. In parallel, we're working to disable the specific model that caused impact.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 07:03:51 2026 |
|---|
| Description: | Title: Users may experience delays sending and receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in sending and receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: Our initial investigation has identified instances where anti-spam protections may be contributing to impact for a subset of users. We are continuing to analyse the behaviour and review service telemetry to better understand the underlying cause and determine the most effective mitigation path.
Scope of impact: This issue impacts users who may be attempting to send and receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 06:36:10 2026 |
|---|
| Description: | Title: Users may experience delays receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: This issue impacts users who may be attempting to receive email messages from external domains in Exchange Online. This information may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 06:21:23 2026 |
|---|
| Description: | Title: Users may experience delays receiving email messages from external domains in Exchange Online
User impact: Users may experience a delay in receiving email messages from external domains in Exchange Online.
More info: Users may experience intermittent “Server busy” errors, affecting multiple mailboxes.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
MO1470143 - Some users in the United Kingdom may have been unable to access multiple Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 10 03:13:00 2026 |
|---|
| End Time: | Thu Sep 10 09:39:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 10 11:02:57 2026 |
|---|
| Root Cause: | Some users may have been unable to access Microsoft 365 services due to facing authentication errors.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 10:22:56 2026 |
|---|
| Description: | Title: Some users in the United Kingdom may have been unable to access multiple Microsoft 365 services
User impact: Users in the United Kingdom may have been unable to access multiple Microsoft 365 services.
More info: Impacted services may have included, but weren't limited to:
- Microsoft Teams
- Outlook
Final status: While implementing traffic optimization actions within the affected environment, we observed service recovery and subsequently confirmed that users could successfully access impacted services. We're continuing to analyze service telemetry, authentication logs, and recent service changes to isolate the underlying cause and help prevent similar impact in the future.
Scope of impact: Impact was specific to some users in the United Kingdom attempting to access multiple Microsoft 365 services.
Start time: Thursday, September 10, 2026, at 8:10 AM UTC
End time: Thursday, September 10, 2026, at 1:39 PM UTC
Root cause: Some users may have been unable to access Microsoft 365 services due to facing authentication errors.
Next steps:
- We're reviewing service telemetry, authentication logs and recent service changes to isolate the root cause and prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 10 09:07:01 2026 |
|---|
| Description: | Title: Some users in the United Kingdom may be unable to access multiple Microsoft 365 services
User impact: Users in the United Kingdom may be unable to access multiple Microsoft 365 services.
More info: Impacted services may include, but aren't limited to:
- Microsoft Teams
- Outlook
Current status: We've identified that a recent authentication component change may be causing users to be unable to access Microsoft 365 services. We're redirecting affected traffic to alternate infrastructure to validate the root cause and provide mitigation.
Scope of impact: Impact is specific to some users in the United Kingdom attempting to access multiple Microsoft 365 services.
Next update by: Thursday, September 10, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Thu Sep 10 07:42:20 2026 |
|---|
| Description: | Title: Some users in the United Kingdom may be unable to access multiple Microsoft 365 services
User impact: Users in the United Kingdom may be unable to access multiple Microsoft 365 services.
More info: Impacted services may include, but aren't limited to:
- Microsoft Teams
- Outlook
Current status: We're proceeding with reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users in the United Kingdom attempting to access multiple Microsoft 365 services.
Next update by: Thursday, September 10, 2026, at 1:30 PM UTC
|
|---|
|
CP1465967 - Admins were unable to view additional sync statistics for some Microsoft Graph Connectors
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 11:47:00 2026 |
|---|
| End Time: | Wed Sep 9 19:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 10 07:51:09 2026 |
|---|
| Root Cause: | A recent service update introduced an incompatibility that prevented the Crawl Statistics service from successfully processing certain requests, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 10 07:42:44 2026 |
|---|
| Description: | Title: Admins were unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins were unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins were able to view recent crawl details but were unable to view sync statistics in the Microsoft 365 admin experience. The issue affected multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Final status: We've confirmed that deployment of our fix has completed across the affected environments and have validated recovery through service telemetry. Monitoring indicates that requests to the Crawl Statistics service are now being processed successfully, and impacted functionality has been restored.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section of this communication may have been impacted.
Start time: Thursday, August 13, 2026, at 3:47 PM UTC
End time: Wednesday, September 9, 2026, at 11:00 PM UTC
Root cause: A recent service update introduced an incompatibility that prevented the Crawl Statistics service from successfully processing certain requests, resulting in impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 10 05:45:07 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins can view recent crawl details but may be unable to view sync statistics in the Microsoft 365 admin experience. The issue affects multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Current status: We've confirmed that deployment of our fix has completed and we've observed recovery in service telemetry, and are continuing to monitor the environment while we work to complete final validation of the remediation.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section may be impacted.
Root cause: A recent service update introduced an incompatibility that is preventing the Crawl Statistics service from successfully processing certain requests, resulting in impact.
Next update by: Thursday, September 10, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Sep 8 08:00:34 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins can view recent crawl details but may be unable to view sync statistics in the Microsoft 365 admin experience. The issue affects multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Current status: We're continuing the fix deployment across the affected environments; however, the deployment is taking longer than initially anticipated to complete due to unforeseen delays within the rollout process. We're monitoring as the deployment continues to saturate across the environments and expect it to complete by Thursday, September 10, 2026.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section may be impacted.
Root cause: A recent service update introduced an incompatibility that is preventing the Crawl Statistics service from successfully processing certain requests, resulting in impact.
Next update by: Thursday, September 10, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Sep 3 08:15:22 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins can view recent crawl details but may be unable to view sync statistics in the Microsoft 365 admin experience. The issue affects multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Current status: We’ve determined that a recent service update introduced an incompatibility that is preventing the Crawl Statistics service from successfully processing certain requests, resulting in impact. We’ve deployed a fix to address the issue and are monitoring the rollout across impacted environments. We expect deployment to complete and the issue to be resolved by our next scheduled update.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section may be impacted.
Estimated time to resolve: Tuesday, September 8, 2026
Root cause: A recent service update introduced an incompatibility that is preventing the Crawl Statistics service from successfully processing certain requests, resulting in impact.
Next update by: Tuesday, September 8, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 09:16:43 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins can view recent crawl details but may be unable to view sync statistics in the Microsoft 365 admin experience. The issue affects multiple connector types, including Confluence, Jira, ServiceNow, Monday.com, and others.
Current status: We've enabled enhanced diagnostic logging and are analyzing affected requests to determine the root cause of the HTTP 500 errors affecting the retrieval of certain crawl statistics data. In parallel, we're reviewing recent code changes and related service behavior to assess whether they're contributing to the impact.
Scope of impact: Admins attempting to view additional sync statistics for some Microsoft Graph Connectors of the types referenced in the More info section may be impacted.
Next update by: Thursday, September 3, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 04:44:52 2026 |
|---|
| Description: | Title: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors
User impact: Admins may be unable to view additional sync statistics for some Microsoft Graph Connectors.
More info: Admins are able to view crawl details but are unable to view sync statistics in the Microsoft 365 admin experience because a specific API is returning HTTP 500 errors. This affects multiple connector types including Confluence, Jira, ServiceNow, Monday.com and others.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: This issue impacts admins attempting to view additional sync statistics for some Microsoft Graph Connectors.
Next update by: Wednesday, September 2, 2026, at 1:30 PM UTC
|
|---|
|
CW1469885 - Users may be unable to see the suggestions pills after receiving a bot response in Microsoft 365 Copilot Chat
| Status: | serviceRestored |
|---|
| Start Time: | Wed Sep 9 16:49:34 2026 |
|---|
| End Time: | Wed Sep 9 16:53:20 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 9 16:54:35 2026 |
|---|
| Root Cause: | An internal drill that tests the resiliency of our service caused this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 9 16:53:20 2026 |
|---|
| Description: | Title: Users may be unable to see the suggestions pills after receiving a bot response in Microsoft 365 Copilot Chat
User impact: Users may have been unable to see the suggestion pills after receiving a bot response in Copilot Chat.
Final status: Our service telemetry has alerted us to an issue in which users may have been unable to see the suggestion pills after receiving a bot response in Copilot Chat. We've determined that an internal drill that tests the resiliency of our service caused this impact. We've halted this impacting drill and confirmed with our service telemetry that impact is remediated.
Scope of impact: Users who attempted to see the suggestions pills after receiving a bot response in Copilot Chat may have been impacted by this event.
Start time: Wednesday, September 9, 2026, at 6:20 PM UTC
End time: Wednesday, September 9, 2026, at 7:30 PM UTC
Root cause: An internal drill that tests the resiliency of our service caused this impact.
Next steps: - We're reviewing our internal drill procedures to better identify the potential for impact to suggestion pills in Copilot Chat prior to beginning the drill, so that we can prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
DZ1189321 - Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 6 20:00:00 2025 |
|---|
| End Time: | Wed Sep 9 12:04:28 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 9 12:14:05 2026 |
|---|
| Root Cause: | A Windows update was producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who upgraded to Windows 11 in or after June of 2025.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 9 12:14:01 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may have seen incorrect names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue only impacted users who have upgraded to Windows 11 during or after June of 2025.
Final status: We've confirmed our solution to address the incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer has fully saturated and the impact has been fully remediated by our actions.
Scope of impact: This issue impacted a subset of users who upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
End time: Wednesday, September 9, 2026, at 4:00 PM UTC
Root cause: A Windows update was producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who upgraded to Windows 11 in or after June of 2025.
Next steps:
- We're evaluating the localization issues introduced by the impacting Windows update so we can more effectively identify and correct similar regressions in future update testing prior to deployments to prevent this issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 31 13:09:50 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We're continuing to deploy our solution to address the incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer. We anticipate this deployment to be completed by our next scheduled update.
Scope of impact: This issue impacts a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Wednesday, September 9, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Aug 26 13:41:39 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We’re continuing to deploy our solution to address the incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer. We’ll provide a resolution timeline once available.
Scope of impact: This issue impacts a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, August 31, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 3 13:05:07 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: After completing our internal validations, we've determined that our solution will address the incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer to remediate the impact. We're deploying our solution, and our fix deployment timeline expects that it will be available by our next scheduled communication update.
Scope of impact: This issue impacts a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Wednesday, August 26, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 16 12:43:42 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: Our final validation process is ongoing and is expected to take several weeks to complete. Based on our current estimates, we expect the fix to be deployed and the issue to be resolved by Tuesday, August 25, 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, August 3, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jun 30 12:51:20 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: Our validation process is ongoing, and we're continuing to verify the fix before determining a release timeline. We'll provide one once it's available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Thursday, July 16, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jun 23 13:10:34 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: The fix validation is ongoing and we expect to have a release timeline by the next scheduled update.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, June 30, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu May 21 13:12:30 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We’re continuing final testing and validation efforts for the fix before deployment. The fix remains scheduled to begin optional rollout around August 25, 2026, through an upcoming Windows cumulative update, before becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, June 23, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Apr 24 15:20:17 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We're continuing our final validation efforts for the fix. The fix is planned for release as part of an upcoming Windows cumulative update, with an optional rollout beginning around August 25, 2026, and becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Thursday, May 21, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Apr 3 13:02:30 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're in the final stages of validation for the fix. The fix is planned to be released as part of an upcoming Windows cumulative update, with optional rollout expected to begin approximately August 25, 2026, and becoming mandatory on September 8, 2026. We'll continue to provide updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 24, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Mar 20 13:24:46 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're preparing the localization fix for additional validations before we initiate the deployment of the fix. We anticipate being able to provide an updated timeline for when we expect the deployment to be released by our next scheduled update.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 3, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Feb 20 12:58:51 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're continuing to work toward delivering the additional localization fix, and we expect this process to take additional time due to the complexity involved in implementing the solution. Based on our current estimates, remediation is targeted for a release window of May 2026. We'll provide further updates as this process progresses.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, March 20, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 14:58:23 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: While we’ve developed an additional fix for the localization issues, the complexity of delivering this solution is preventing an expedited resolution. We expect this process to take several weeks as we validate the subtasks involved in instituting the fix. We’ll provide updates on this process and a timeline for deployment once the subtask orchestration is complete.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, February 20, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jan 9 13:12:08 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’re continuing to assess and validate alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 12:35:31 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve identified that the previously developed code fix isn’t an effective solution for addressing the incorrect service names and descriptions. We’re assessing and validating alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 9, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Dec 9 12:44:40 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: Validation of the code fix is continuing to progress, and due to the complex nature of the code developed to address the incorrect service names and descriptions, we're still expecting the deployment to complete by March 2026. We'll provide a more accurate timeline as one becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, January 6, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Dec 8 03:18:26 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We are continuing to validate the fix’s effectiveness and anticipate full deployment by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, December 9, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 05:20:30 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve developed a code fix to address the issue. It’s currently undergoing validation to ensure effectiveness, and we expect the fix to be fully implemented and remediate impact by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, 8 December 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Nov 23 16:12:56 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We've identified a recent Windows update that is producing incorrect service names and descriptions in Services and the Event Viewer for some users who have upgraded to Windows 11 in or after June of 2025. As we work to confirm an accurate window of impact, we're developing a code fix to address the offending change and to remediate the impact. We'll provide an updated timeline for the deployment of our fix and the remediation of impact once our internal validations have completed.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, November 24, 2025, at 10:30 AM UTC
|
|---|
|
TM1459181 - Users may be unable to join shared channels using some links to messages in Microsoft Teams
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Aug 21 19:42:31 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 8 15:44:14 2026 |
|---|
| 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: | Thursday, September 17, 2026, at 9:00 PM UTC |
|---|
|
Details
| 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.
|
|---|
|
MO1469271 - Some users may be unable to access https://m365.cloud.microsoft and receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 8 11:23:28 2026 |
|---|
| End Time: | Tue Sep 8 13:22:34 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 8 13:28:08 2026 |
|---|
| Root Cause: | A recent service update, intended to improve how chats are loaded when accessing m365.cloud.microsoft, rejected requests which resulted in https://m365.cloud.microsoft failing to load.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 8 13:28:04 2026 |
|---|
| Description: | Title: Some users may be unable to access https://m365.cloud.microsoft and receive an error
User impact: Users may be unable to access https://m365.cloud.microsoft and receive an error message.
More info: Users received a "GetSections returned no conversation history" error message.
Final status: Further analysis indicated that the previously referenced 400 and 503 error messages were unrelated to the issue described in this communication, and we've updated the communication accordingly. We reverted a recent service update that was intended to improve chat-loading functionality when accessing m365.cloud.microsoft and confirmed through service telemetry that the error rates have subsided and service is restored.
Scope of impact: This issue may have affected some users attempting to access https://m365.cloud.microsoft.
Start time: Tuesday, September 8, 2026, at 4:30 AM UTC
End time: Tuesday, September 8, 2026, at 5:15 PM UTC
Root cause: A recent service update, intended to improve how chats are loaded when accessing m365.cloud.microsoft, rejected requests which resulted in https://m365.cloud.microsoft failing to load.
Next steps:
- We're reviewing our testing processes to determine how we can identify similar issues prior to deployment so we can resolve these issues beforehand.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 8 12:06:42 2026 |
|---|
| Description: | Title: Some users may be unable to access https://m365.cloud.microsoft and receive an error
User impact: Users may be unable to access https://m365.cloud.microsoft and receive an error message.
More info: Users receive either a 400 or 503 error code, or a "GetSections returned no conversation history" error message.
Current status: We've received reports of an issue where users receive either a 400 or 503 error code, or a "GetSections returned no conversation history" error message when attempting to access https://m365.cloud.microsoft. We're reviewing a HTTP Archive (HAR) file from both working and non-working scenarios to assess where the issue lies.
Scope of impact: This issue may affect some users attempting to access https://m365.cloud.microsoft.
Next update by: Tuesday, September 8, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 8 11:32:08 2026 |
|---|
| Description: | Title: Some users can't access https://m365.cloud.microsoft and receive an error
User impact: Users can't access https://m365.cloud.microsoft and receive a 400, 503 error code, or a specific error message.
More info: Users receive either a 400 or 503 error code, or a "GetSections returned no conversation history" error message.
Current status: We're investigating a potential issue with accessing https://m365.cloud.microsoft and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1467962 - Some admins' Microsoft 365 admin center usage report data may be delayed
| Status: | serviceRestored |
|---|
| Start Time: | Sat Sep 5 21:47:00 2026 |
|---|
| End Time: | Mon Sep 7 14:20:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 7 15:30:16 2026 |
|---|
| Root Cause: | An upstream data source pipeline issue was causing delays in some usage report data availability and was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 7 15:11:10 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may have been delayed.
More info:
- Microsoft 365 Copilot Readiness Reports may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data at the time of ongoing impact was from August 31, 2026.
- Copilot Chat Reports may have been delayed for admins in North America, and the latest data at the time of ongoing impact was from September 3, 2026.
- Microsoft 365 Apps usage Reports may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data at the time of ongoing impact was from August 31, 2026.
- Microsoft Teams User Activity Reports may have been delayed for admins in North America and Asia Pacific, and the latest data at the time of ongoing impact was from is from September 1, 2026.
Final status: We've validated that our solution to address the upstream data pipeline delay leading to this impact has fully addressed the impact, and all reports are now available as expected.
Scope of impact: Some admins attempting to view some usage report data in the Microsoft 365 admin center may have been impacted.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
End time: Monday, September 7, 2026, at 6:20 PM UTC
Root cause: An upstream data source pipeline issue was causing delays in some usage report data availability and was resulting in impact.
Next steps:
- We're reviewing what led to the upstream data pipeline delays based on our findings from this event to identify and implement improvements, which will help us prevent similar future impact from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Sep 7 14:00:04 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: - Microsoft 365 Copilot Readiness Reports are updated and no longer affected; previously they may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data was from August 31, 2026.
- Copilot Chat Reports are updated and no longer affected; previously they may have been delayed for admins in North America, and the latest data was from September 3, 2026.
- Microsoft 365 Apps usage Reports are updated and no longer affected; previously they may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America and Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: We've confirmed that our mitigations have addressed the impact for most reports, though impact is ongoing for the Microsoft Teams Apps User Activity report. We're continuing to apply our mitigations and aim to have an update on our progress by our next communication update.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Monday, September 7, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Sep 7 11:24:51 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, Microsoft 365 admin center usage reports include the following:
- Microsoft 365 Copilot Readiness Reports are updated and no longer affected; previously they may have been delayed for admins in North America, Asia Pacific, and Europe, and the latest data was from August 31, 2026.
- Copilot Chat Reports are updated and no longer affected; previously they may have been delayed for admins in North America, and the latest data was from September 3, 2026.
- Microsoft 365 Apps usage Reports may be delayed for admins in North America, Asia Pacific, and Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America and Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: We're continuing to apply mitigations and monitor the outcome to verify the efficacy of our actions in restoring current data for Microsoft Teams user activity in the Microsoft 365 admin center, as well as the Microsoft Teams Apps App usage and User activity reports in the Microsoft Teams admin center.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Tuesday, September 8, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Sun Sep 6 22:33:13 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, Microsoft 365 admin center usage reports include the following:
- Microsoft 365 Copilot Readiness Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Copilot Chat Reports may be delayed for admins in North America and the latest data is from September 3, 2026.
- Microsoft 365 Apps usage Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America, Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: We're continuing to monitor and implement our mitigations, and Microsoft Teams User Activity and Microsoft 365 Apps usage reports may still be delayed for admins with the latest data from September 1, 2026.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Monday, September 7, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Sun Sep 6 12:59:17 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, Microsoft 365 admin center usage reports include the following:
- Microsoft 365 Copilot Readiness Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Copilot Chat Reports may be delayed for admins in North America and the latest data is from September 3, 2026.
- Microsoft 365 Apps usage Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America, Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: After applying our solution to our data pipeline, our internal service telemetry has verified that Microsoft 365 Copilot Readiness and Copilot Chat Reports are no longer experiencing delays. While we monitor and complete our mitigations, Microsoft Teams User Activity and Microsoft 365 Apps usage reports may still be delayed for admins with the latest data from September 1, 2026.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Sunday, September 6, 2026, at 1:47 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Monday, September 7, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Sat Sep 5 22:30:16 2026 |
|---|
| Description: | Title: Some admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, Microsoft 365 admin center usage reports include the following:
- Microsoft 365 Copilot Readiness Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Copilot Chat Reports may be delayed for admins in North America and the latest data is from September 3, 2026.
- Microsoft 365 Apps usage Reports may be delayed for admins in North America, Asia Pacific, Europe, and the latest data is from August 31, 2026.
- Microsoft Teams User Activity Reports may be delayed for admins in North America, Asia Pacific, and the latest data is from is from September 1, 2026.
Current status: We've been made aware of an issue in which some admins' Microsoft 365 admin center usage report data may be delayed. We've identified that an upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact. We've developed a solution and are applying it to the affected pipeline to address the issue. We anticipate that impact to Copilot chat report data will be resolved by Sunday, September 6, 2026, at 3:30 AM UTC, and in the interim, we're working on determining the timeline for resolution for the remaining affected reports, which we aim to provide by our next scheduled communications update.
Scope of impact: Admins attempting to view some usage report data in the Microsoft 365 admin center may be impacted. This section may be updated as our investigation continues.
Start time: Saturday, September 5, 2026, at 12:00 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in some usage report data availability and is resulting in impact.
Next update by: Monday, September 7, 2026, at 1:00 AM UTC
|
|---|
|
TM1462514 - Some users attempting to view their Microsoft Teams contact lists may experience latency
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 28 20:00:00 2026 |
|---|
| End Time: | Mon Sep 7 15:26:43 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Sep 7 15:28:06 2026 |
|---|
| Root Cause: | A recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Sep 7 15:28:03 2026 |
|---|
| Description: | Title: Some users attempting to view their Microsoft Teams contact lists may experience latency
User impact: Users attempting to view their Microsoft Teams contact lists may have experienced latency.
More info: Users attempting to view their Microsoft Teams contact lists may have experienced latency.
Final status: Our fix has completed its deployment to all affected regions, resolving this impact.
Scope of impact: Some users who were attempting to view their Microsoft Teams contact lists may have been affected.
Start time: Wednesday, July 29, 2026, at 12:00 AM UTC
End time: Saturday, September 5, 2026, at 12:00 AM UTC
Root cause: A recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and was resulting in impact.
Next steps: - We're reviewing the responsible service update to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 2 16:06:54 2026 |
|---|
| Description: | Title: Some users attempting to view their Microsoft Teams contact lists may experience latency
User impact: Users attempting to view their Microsoft Teams contact lists may experience latency.
More info: Users attempting to view their Microsoft Teams contact lists may experience latency and their contact list may not appear for up to 15 minutes.
Current status: The deployment of the code fix has begun, and we anticipate it being fully deployed to all affected environments by the time of our next communication.
Scope of impact: Some users who are attempting to view their Microsoft Teams contact lists may be affected. This information may be updated as our investigation continues.
Start time: Wednesday, July 29, 2026, at 12:00 AM UTC
Root cause: A recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and is resulting in impact.
Next update by: Monday, September 7, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 26 20:56:42 2026 |
|---|
| Description: | Title: Some users attempting to view their Microsoft Teams contact lists may experience latency
User impact: Users attempting to view their Microsoft Teams contact lists may experience latency.
More info: Users attempting to view their Microsoft Teams contact lists may experience latency and their contact list may appear for up to 15 minutes.
Current status: We’ve determined that a recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and is resulting in impact. We’ve developed a fix to correct the offending code regression, and we anticipate that the deployment process will begin prior to our next scheduled update, at which point we expect that a remediation timeline will be provided.
Scope of impact: Some users who are attempting to view their Microsoft Teams contact lists may be affected. This information may be updated as our investigation continues.
Start time: Wednesday, July 29, 2026, at 12:00 AM UTC
Root cause: A recent service update to improve the user interface of Microsoft Teams contact lists contained a code regression and is resulting in impact.
Next update by: Wednesday, September 2, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 26 20:29:04 2026 |
|---|
| Description: | Title: Some users attempting to view their Microsoft Teams contact lists may experience latency
User impact: Users attempting to view their Microsoft Teams contact lists may experience latency.
More info: Users attempting to view their Microsoft Teams contact lists may experience latency and their contact list may appear for up to 15 minutes.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CW1467407 - Users may be unable to query Microsoft 365 Copilot Chat and receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 4 21:45:26 2026 |
|---|
| End Time: | Fri Sep 4 22:34:49 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sat Sep 5 00:18:53 2026 |
|---|
| Root Cause: | A recent configuration change caused a subset of query requests to be rejected, resulting in elevated error rates and resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 22:41:57 2026 |
|---|
| Description: | Title: Users may be unable to query Microsoft 365 Copilot Chat and receive an error
User impact: Users may be unable to query Copilot Chat and receive an error.
More info: When users attempted to query Copilot Chat, some of their queries may have returned no response and instead, users may have received an error that stated, "Something went wrong."
Final status: Our review of the service health telemetry isolated that a recent configuration change caused a subset of requests to be rejected, resulting in elevated error rates and resulted in impact. We’ve since reverted the offending change and after an extended period of monitoring, we’ve confirmed that impact was remediated.
Scope of impact: Any user who attempted to query Copilot Chat may be impacted.
Start time: Saturday, September 5, 2026, at 12:40 AM UTC
End time: Saturday, September 5, 2026, at 2:09 AM UTC
Root cause: A recent configuration change caused a subset of query requests to be rejected, resulting in elevated error rates and resulted in impact.
Next steps: We'll review our service update validation process to ensure similar instances aren't replicated in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 4 21:47:18 2026 |
|---|
| Description: | Title: Users may be unable to query Microsoft 365 Copilot Chat and receive an error
User impact: Users may be unable to query Copilot Chat and receive an error.
More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong."
Current status: Our service health monitoring alerted us to an increase in failures occurring when users attempt to query Copilot Chat. We're reviewing our service health telemetry to isolate the source of the failures, so that we can develop a mitigation plan.
Scope of impact: Any user attempting to query Copilot Chat may be impacted. This information may be updated as our investigation continues.
Next update by: Saturday, September 5, 2026, at 3:00 AM UTC
|
|---|
|
MO1467282 - Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
| Status: | serviceRestored |
|---|
| Start Time: | Fri Sep 4 14:44:09 2026 |
|---|
| End Time: | Fri Sep 4 22:47:15 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 4 22:50:13 2026 |
|---|
| Root Cause: | A recent service update intended to refresh the pages of service central contained a code issue, which was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 22:50:10 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may have not been able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users were able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Final status: We've confirmed that our fix has finished deploying to all affected environments, remediating this impact.
Scope of impact: This event impacted any user attempting to access support central through the Microsoft Intune or Microsoft Defender portals.
Start time: Tuesday, September 1, 2026, at 4:00 PM UTC
End time: Saturday, September 5, 2026, at 2:35 AM UTC
Root cause: A recent service update intended to refresh the pages of service central contained a code issue, which was resulting in impact.
Next steps: - We're reviewing the responsible update to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 4 20:48:58 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users are able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Current status: Our fix deployment is progressing, and some users may already be experiencing reduced impact. However, additional time is required for the deployment to reach all affected environments before the issue is fully resolved.
Scope of impact: This event impacts any user attempting to access support central through the Microsoft Intune or Microsoft Defender portals. This information may be updated as our investigation continues.
Root cause: A recent service update intended to refresh the pages of service central contained a code issue, which is resulting in impact.
Next update by: Saturday, September 5, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Fri Sep 4 18:18:05 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users are able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Current status: We've started deploying our fix to address this issue and anticipate that this process will be complete by our next scheduled update.
Scope of impact: This event impacts any user attempting to access support central through the Microsoft Intune or Microsoft Defender portals. This information may be updated as our investigation continues.
Root cause: A recent service update intended to refresh the pages of service central contained a code issue, which is resulting in impact.
Next update by: Saturday, September 5, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Sep 4 15:16:26 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users are able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Current status: We determined that a recent service update intended to refresh the pages of service central contained a code issue, which is resulting in impact. We've developed a fix to address this issue and will provide a remediation timeline once this fix is ready to deploy to all affected environments.
Scope of impact: This event impacts any user attempting to access support central through the Microsoft Intune or Microsoft Defender portals. This information may be updated as our investigation continues.
Start time: Tuesday, September 1, 2026, at 4:00 PM UTC
Root cause: A recent service update intended to refresh the pages of service central contained a code issue, which is resulting in impact.
Next update by: Friday, September 4, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Sep 4 14:46:09 2026 |
|---|
| Description: | Title: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals
User impact: Users may not be able to open support central in Microsoft Intune and Microsoft Defender portals.
More info: Users are able to open support tickets through the Microsoft 365 admin center to circumvent impact.
Current status: We're investigating a potential issue with two different Microsoft 365 portals and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1466822 - Some users may see various issues with sharing of Agent Builders in Microsoft 365 Copilot Studio
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 3 20:23:39 2026 |
|---|
| End Time: | Fri Sep 4 16:11:21 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 4 16:31:22 2026 |
|---|
| Root Cause: | A previous deployment to Agent Builder contained a code issue that resulted in various issues with sharing of Agent Builders in Copilot Studio.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 16:31:18 2026 |
|---|
| Description: | Title: Some users may see various issues with sharing of Agent Builders in Microsoft 365 Copilot Studio
User impact: Users may have seen various issues with sharing of Agent Builders in Copilot Studio.
More info: In the "Share dialog", the operation appeared to complete successfully, but the share targets weren't actually saved. Users you added didn't gain access, and users you removed may have kept it. Since sharing looked successful, impacted users may not have noticed it until later, when added or removed people didn't persist in the shared-users list.
Specifically, impact happened only if the agent's knowledge sources included a SharePoint Online site that was added from the grounding menu. Agents without such a source were not affected.
While the initial fix prevented any new agents from entering the impacted state, affected users may have been able to perform the following steps for agents that were already impacted:
1) Open the affected agent and remove the SharePoint site knowledge source (keep all other knowledge/media sources).
2) Re-add the SharePoint site. (if doesn't work remove and re-add)
Retry Share and confirm the intended users now appear in the shared-users list.
Final status: We've confirmed that the secondary fix is deployed to clean up agents that were affected throughout the duration of this event has completed development, and after monitoring service health metrics, we've confirmed that the associated failures have ceased and the impact has been remediated by our actions.
Scope of impact: Some users utilizing Agent Builders in Copilot Studio may have been impacted.
Start time: Wednesday, August 26, 2026, at 5:44 AM UTC
End time: Thursday, September 3, 2026, at 10:09 PM UTC
Root cause: A previous deployment to Agent Builder contained a code issue that resulted in various issues with sharing of Agent Builders in Copilot Studio.
Next steps:
- We're reviewing our deployment standards to ensure that similar code issues are identified and corrected ahead of implementation to prevent this from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 21:18:27 2026 |
|---|
| Description: | Title: Some users may see various issue with sharing of Agent Builders in Microsoft 365 Copilot Studio
User impact: Users may see various issue with sharing of Agent Builders in Copilot Studio.
More info: In the "Share dialog", the operation appears to complete successfully, but the share targets aren't actually saved. Users you add don't gain access, and users you remove may keep it. Since sharing looks successful, impacted users may not notice it until later, when added or removed people don't persist in the shared-users list.
Specifically, impact happens only if the agent's knowledge sources include a SharePoint Online site that was added from the grounding menu. Agents without such a source are not affected.
While the initial fix will prevent any new agents from entering the impacted state, affected users may perform the following steps for agents that are already impacted:
1) Open the affected agent and remove the SharePoint site knowledge source. (keep all other knowledge/media sources).
2) Re-add the SharePoint site. (if doesn't work remove and re-add)
Retry Share and confirm the intended users now appear in the shared-users list.
Current status: We've determined that a previous deployment to Agent Builder contains a code issue that's resulting in various issues with sharing of Agent Builders in Copilot Studio. We've developed two parallel fixes to address this issue, and the first code change to ensure that new SharePoint Online site sources are no longer affected has successfully been deployed. The affected sources are now automatically repaired when agents are published or shared, preventing further agents from entering the impacted state. We’re monitoring as the secondary fix is deployed to clean up agents that were already affected throughout the duration of this event.
Scope of impact: Some users utilizing Agent Builders in Copilot Studio may be impacted.
Start time: Wednesday, August 26, 2026, at 5:44 AM UTC
Root cause: A previous deployment to Agent Builder contains a code issue that's resulting in various issues with sharing of Agent Builders in Copilot Studio.
Next update by: Friday, September 4, 2026, at 9:00 PM UTC
|
|---|
|
TM1467148 - Users may be unable to access some third-party apps within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 3 22:53:00 2026 |
|---|
| End Time: | Fri Sep 4 11:14:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Sep 4 14:23:34 2026 |
|---|
| Root Cause: | A code issue occurring within an upstream service caused the third-party app to be removed from the app catalog, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 12:31:17 2026 |
|---|
| Description: | Title: Users may be unable to access some third-party apps within Microsoft Teams
User impact: Users may have been unable to access some third-party apps within Microsoft Teams.
Final status: We've deployed our fix to address the upstream code issue and confirmed through monitoring service health telemetry that the impact has been remediated. Admins will need to restore the pre-impact app configurations within the Microsoft Teams admin center to have access restored. The pre-impact app configuration settings can be gathered from audit logs.
Scope of impact: Any user attempting to access a some third-party apps may have been impacted.
Start time: Friday, September 4, 2026, at 2:53 AM UTC
End time: Friday, September 4, 2026, at 3:14 PM UTC
Root cause: A code issue occurring within an upstream service caused the third-party app to be removed from the app catalog, resulting in impact.
Next steps:
- We're reviewing the offending code issue to determine how it was introduced into the service, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Sep 4 11:14:31 2026 |
|---|
| Description: | Title: Users may be unable to access some third-party apps within Microsoft Teams
User impact: Users may be unable to access some third-party apps within Microsoft Teams.
Current status: We've identified that a code issue occurring within an upstream service caused the third-party app to be removed from the app catalog, resulting in impact. We've developed a fix to address the code issue and return the app to the catalog, and we'll aim to provide a timeline for the deployment of our fix to begin by our next schedule communications update. Once the fix has been deployed, admins will need to restore the pre-impact app configurations within the Microsoft Teams admin center to have access restored.
Scope of impact: Any user attempting to access some third-party apps may be impacted. This section may be updated as our investigation continues.
Start time: Friday, September 4, 2026, at 2:53 AM UTC
Root cause: A code issue occurring within an upstream service caused the third-party app to be removed from the app catalog, resulting in impact.
Next update by: Friday, September 4, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Sep 4 11:00:13 2026 |
|---|
| Description: | Title: Users may be unable to access some third-party apps within Microsoft Teams
User impact: Users may be unable to access some third-party apps within Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1464785 - Some users may be unable to access SharePoint Online sites configured with Authentication Context
| Status: | serviceRestored |
|---|
| Start Time: | Sat Aug 22 22:38:00 2026 |
|---|
| End Time: | Fri Sep 4 13:18:41 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Access Services |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Sep 4 13:22:06 2026 |
|---|
| Root Cause: | A recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 13:21:41 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may have been unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users were unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users received the following error message:
"Server Error in '/' Application."
As a workaround, users may have been able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users could have also opened a new browser tab on the same session and access the site or used a direct link.
Final status: After confirming that our reversion of the code update to the SharePoint Online authentication process completed as expected and was available in all environments, we validated with a portion of impacted users that access to SharePoint Online sites configured with Authentication Context has been restored.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may have been impacted.
Start time: Sunday, August 23, 2026, at 2:38 AM UTC
End time: Friday, September 4, 2026, at 5:00 PM UTC
Root cause: A recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites.
Next steps: - We're continuing to optimize our quality assurance processes to minimize user impact while ensuring important service health updates are deployed as efficiently as possible.
|
|---|
|
| Time: | Wed Sep 2 13:55:53 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users receive the following error message:
"Server Error in '/' Application."
As a workaround, users may be able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users can also open a new browser tab on the same session and access the site. The link may work as well.
Current status: The deployment is progressing as expected and users will see relief as it progresses. We expect the release to complete, mitigating impact for all users by the next scheduled update.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted. This information may be updated as our investigation continues.
Start time: Sunday, August 23, 2026, at 2:38 AM UTC
Root cause: A recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites.
Next update by: Friday, September 4, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 14:04:34 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users receive the following error message:
"Server Error in '/' Application."
As a workaround, users may be able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users can also open a new browser tab on the same session and access the site. The link may work as well.
Current status: We've identified that a recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites. We've developed a fix to revert the offending change and have initiated deployment to the affected environments. We're monitoring the deployment to ensure successful completion, and as the fix progresses, some users may experience impact relief. We'll provide a resolution timeline once available.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Start time: Sunday, August 23, 2026, at 2:38 AM UTC
Root cause: A recent SharePoint Online code change intended to update authentication processing resulted in Authentication Context requests not being processed as expected, preventing some users from accessing affected sites.
Next update by: Wednesday, September 2, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 17:49:50 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users receive the following error message:
"Server Error in '/' Application."
As a workaround, users may be able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users could also open a new browser tab on the same session and access the site. The link may work as well.
Current status: We've determined that reverting the update suspected of causing this issue isn't a viable path to remediation. We're reviewing alternative solutions to confirm the impact and resolve the problem.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Tuesday, September 1, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 16:16:36 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Users receive the following error message:
"Server Error in '/' Application."
As a workaround, users may be able to temporarily access the affected content by first clearing internet browser cookies and navigating to the root site collection before opening the direct link. Users could also open a new browser tab on the same session and access the site. The link may work as well.
Current status: We've identified a recent change which we suspect may be leading to the impact, and we're determining whether rolling the change back is a viable option to remediate impact.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 14:05:46 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Current status: Our investigation of the Authentication Context configuration is ongoing as we work to confirm the source of the impact before we can begin to develop a mitigation strategy.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 12:11:52 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Current status: In addition to our HAR analysis, we're further reviewing the Authentication Context configuration to understand whether this is where the impact originates.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 09:56:25 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Current status: We're reviewing HAR files that compare successful access requests initiated through the root site collection with failing direct-link requests to determine why the behavior differs and identify next steps to mitigate impact.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 08:36:00 2026 |
|---|
| Description: | Title: Some users may be unable to access SharePoint Online sites configured with Authentication Context
User impact: Users may be unable to access SharePoint Online sites configured with Authentication Context.
More info: Specifically, users are unable to access SharePoint Online sites configured with Authentication Context through sensitivity labels.
Current status: We've reproduced the issue in our testing environment and are reviewing HTTP Archive (HAR) logs to determine why direct links fail when Authentication Context is enabled through sensitivity labels.
Scope of impact: Some users attempting to access SharePoint Online sites configured with Authentication Context through sensitivity labels may be impacted.
Next update by: Monday, August 31, 2026, at 2:30 PM UTC
|
|---|
|
TM1466659 - Users may have been unable to join calls or meetings in Microsoft Teams for Mac
| Status: | serviceRestored |
|---|
| Start Time: | Sun Aug 23 12:32:00 2026 |
|---|
| End Time: | Wed Aug 26 16:51:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Sep 4 10:55:00 2026 |
|---|
| Root Cause: | A code change caused the service infrastructure responsible for call and meeting functionality to fail to process some requests, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Sep 4 10:49:44 2026 |
|---|
| Description: | Title: Users may have been unable to join calls or meetings in Microsoft Teams for Mac
User impact: Users may have been unable to join calls or meetings in Microsoft Teams for Mac.
Final status: We've determined that a code change caused the service infrastructure responsible for call and meeting functionality to fail to process some requests, which resulted in impact. We've deployed a fix and confirmed that impact has been resolved after an extended period of monitoring service availability.
Scope of impact: Some users attempting to join calls or meetings in Microsoft Teams for Mac may have been impacted.
Start time: Sunday, August 23, 2026, at 4:32 PM UTC
End time: Wednesday, August 26, 2026, at 8:51 PM UTC
Root cause: A code change caused the service infrastructure responsible for call and meeting functionality to fail to process some requests, which resulted in impact.
Next steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 16:13:51 2026 |
|---|
| Description: | Title: Users may be unable to join calls or meetings in Microsoft Teams for Mac
User impact: Users may be unable to join calls or meetings in Microsoft Teams for Mac.
Current status: Further review of the suspected code change indicates it may not be the cause of impact for this event. We're reassessing our root cause understanding and reviewing service logs to isolate the source of impact, so that we can determine our next steps regarding impact remediation.
Scope of impact: Some users attempting to join calls or meetings in Microsoft Teams for Mac may be impacted. This section may be updated as our investigation continues.
Next update by: Friday, September 4, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 15:25:54 2026 |
|---|
| Description: | Title: Users may be unable to join calls or meetings in Microsoft Teams for Mac
User impact: Users may be unable to join calls or meetings in Microsoft Teams for Mac.
Current status: We've identified a code change that's causing the service infrastructure responsible for call and meeting functionality to fail to process some requests, resulting in impact. We're assessing potential remediation actions to address the problematic code change and restore service functionality.
Scope of impact: Some users attempting to join calls or meetings in Microsoft Teams for Mac may be impacted. This section may be updated as our investigation continues.
Start time: Thursday, July 2, 2026, at 3:09 PM UTC
Root cause: A code change is causing the service infrastructure responsible for call and meeting functionality to fail to process some requests, resulting in impact.
Next update by: Thursday, September 3, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 14:59:28 2026 |
|---|
| Description: | Title: Users may be unable to join calls or meetings in Microsoft Teams for Mac
User impact: Users may be unable to join calls or meetings in Microsoft Teams for Mac.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1465286 - Admins may see delays in Copilot usage report data in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 31 20:25:42 2026 |
|---|
| End Time: | Thu Sep 3 15:46:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 23:10:10 2026 |
|---|
| Root Cause: | A component utilized in the flow of this functionality was deprecated, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 23:10:10 2026 |
|---|
| Description: | Title: Admins may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins may have seen delays in Copilot usage report data in the Microsoft 365 admin center.
Final status: Our operation to process the remaining backlog of usage report data is complete, and we've monitored our telemetry to confirm that the impact is remediated.
Scope of impact: This event impacted any admin attempting to access Copilot usage report data in the Microsoft 365 admin center.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
End time: Thursday, September 3, 2026, at 7:46 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next steps:
- We're reviewing our deprecation procedures pertaining to the components of Copilot infrastructure responsible for processing usage report data to prevent similar impact after future maintenance operations.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 21:28:56 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: Processing of the usage report data remains underway, and we’re monitoring recovery to confirm sustained progress and determine an updated completion timeline.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Friday, September 4, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Sep 3 13:34:11 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: The usage report data is continuing to progress; however, recovery is occurring more slowly than previously anticipated. We're continuing to monitor the processing progress and validate recovery trends to establish an updated completion timeline. We'll provide additional information on the expected recovery timeline once it has been confirmed.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Friday, September 4, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 20:32:38 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: Our review of service health telemetry indicates that recovery of all usage report data is progressing as expected, and all usage report data may be fully recovered by our next scheduled update. We're continuing to monitor to confirm this timeline, and if validation continues as expected, we anticipate recovery to be complete by our next scheduled communications update.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Thursday, September 3, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 12:36:52 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: A majority of the accumulated data has been processed, and our review of service health telemetry has confirmed that all Copilot usage report data excluding Graph API Copilot usage data is now up to date. While the accumulated data for the Graph API Copilot usage data continues to be processed, we recommend admins utilize the beta Graph API endpoint to view up-to-date data. We'll aim to provide a timeline for all usage report data to be recovered by our next scheduled communications update.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Thursday, September 3, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 12:29:09 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: It's taking longer than initially anticipated for the backlog of accumulated data to be processed and for Copilot usage reporting to catch up to the expected data. We'll aim to provide a timeline for the reporting data to be up to date by our next scheduled communications update.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Wednesday, September 2, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 20:27:59 2026 |
|---|
| Description: | Title: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center
User impact: Admins' may see delays in Copilot usage report data in the Microsoft 365 admin center.
Current status: We determined that a component utilized in the flow of this functionality was deprecated, resulting in impact. We're reinstating this component and anticipate that this process should be complete by our next scheduled update.
Scope of impact: This event impacts any admin attempting to access Copilot usage report data in a Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:00 PM UTC
Root cause: A component utilized in the flow of this functionality was deprecated, resulting in impact.
Next update by: Tuesday, September 1, 2026, at 6:00 PM UTC
|
|---|
|
CW1466621 - Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 3 02:30:00 2026 |
|---|
| End Time: | Thu Sep 3 15:45:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 3 17:06:05 2026 |
|---|
| Root Cause: | An increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses prevented the service from being able to efficiently process requests.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 16:58:18 2026 |
|---|
| Description: | Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error
User impact: Users' queries to Copilot Chat may have returned no response, and users received an error.
More info: When users attempted to query Copilot Chat, some of their queries may have returned no response and instead, users may have received an error that stated, "Something went wrong."
Final status: We've applied configuration changes to rebalance the request traffic and confirmed using our service health telemetry that the impact is remediated.
Scope of impact: Any user that attempted to query Copilot Chat may have been impacted.
Start time: Thursday, September 3, 2026, at 6:30 AM UTC
End time: Thursday, September 3, 2026, at 7:45 PM UTC
Root cause: An increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses prevented the service from being able to efficiently process requests.
Next steps:
- We're continuing to investigate the source of the increased request traffic, so that we can determine how to prevent similar impact to users' Copilot Chat queries in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 14:42:10 2026 |
|---|
| Description: | Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error
User impact: Users' queries to Copilot Chat may return no response, and users receive an error.
More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong."
Current status: We've identified an increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses which is preventing the service from being able to efficiently process requests. We're evaluating our mitigation options to identify the most effective method to remediate the impact.
Scope of impact: Any user attempting to query Copilot Chat may be impacted.
Start time: Thursday, September 3, 2026, at 6:30 AM UTC
Root cause: An increase in request traffic to the portion of service infrastructure responsible for facilitating Copilot Chat responses which is preventing the service from being able to efficiently process requests.
Next update by: Thursday, September 3, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 13:27:02 2026 |
|---|
| Description: | Title: Users' queries to Microsoft 365 Copilot Chat may return no response, and users receive an error
User impact: Users' queries to Copilot Chat may return no response, and users receive an error.
More info: When users attempt to query Copilot Chat, some of their queries may return no response and instead, users may receive an error that states, "Something went wrong."
Current status: Our service health monitoring alerted us to an increase in failures occurring when users attempt to query Copilot Chat. We're reviewing our service health telemetry to isolate the source of the failures, so that we can developed a mitigation plan.
Scope of impact: Any user attempting to query Copilot Chat may be impacted.
Next update by: Thursday, September 3, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 13:16:55 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot Chat
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
WP1466588 - Admins may notice that Cloud PC service components aren't updating
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 17 12:00:00 2026 |
|---|
| End Time: | Thu Sep 3 13:25:00 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | Manageability |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 14:17:24 2026 |
|---|
| Root Cause: | A recent service change added new endpoint URLs that weren't publicly communicated, which prevented admins from adding them to their allow lists and caused impact by blocking the requests to update Cloud PC service components.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 13:44:45 2026 |
|---|
| Description: | Title: Admins may notice that Cloud PC service components aren't updating
User impact: Admins may have noticed that Cloud PC service components weren't updating.
More info: Admins may have noticed that their Cloud PC service components, including the remote desktop (RD) agent or side-by-side stack, weren't updating. There was no impact to general user connectivity to the Cloud PCs.
Final status: We've reversed the service change to revert back to our previous list of endpoint URLs and confirmed through internal testing that the impact is remediated as a result for this action.
Scope of impact: Any admin that expected updates to their Cloud PC service components may have been impacted.
Start time: Monday, August 17, 2026, at 4:00 PM UTC
End time: Thursday, September 3, 2026, at 5:25 PM UTC
Root cause: A recent service change added new endpoint URLs that weren't publicly communicated, which prevented admins from adding them to their allow lists and caused impact by blocking the requests to update Cloud PC service components.
Next steps:
- We're reviewing our service change testing and validation procedures to identify and prevent similar issues with changing endpoint URLs before notifying admins moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 12:33:22 2026 |
|---|
| Description: | Title: Admins may notice that Cloud PC service components aren't updating
User impact: Admins may notice that Cloud PC service components aren't updating.
More info: Admins may notice that their Cloud PC service components, including the remote desktop (RD) agent or side-by-side stack, aren't updating. There's no impact to general user connectivity to the Cloud PCs.
Current status: We've identified a recent service change that added new endpoint URLs that weren't publicly communicated, which prevented admins from adding them to their allow lists and is causing impact by blocking the requests to update Cloud PC service components. We're reversing the service change to revert back to our previous list of endpoint URLs and remediate the impact.
Scope of impact: Any admin expecting updates to their Cloud PC service components may be impacted.
Root cause: A recent service change added new endpoint URLs that weren't publicly communicated, which prevented admins from adding them to their allow lists and is causing impact by blocking the requests to update Cloud PC service components.
Next update by: Thursday, September 3, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 12:08:10 2026 |
|---|
| Description: | Title: Admins' Cloud PC components may not be updating
User impact: Admins' Cloud PC components may not be updating.
More info: Admins notice that their Cloud PC components may not be updating; however, there's no impact to general user connectivity to the Cloud PCs.
Current status: We're investigating a potential issue with Windows 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1463371 - Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 19 20:00:00 2026 |
|---|
| End Time: | Mon Aug 31 10:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 13:29:47 2026 |
|---|
| Root Cause: | A recent update introduced a code defect that was resulting in this impacting event.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 11:35:46 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may have failed to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affected users who updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application would have restored optimized functionality.
Final status: We've confirmed through monitoring service health telemetry for an extended period as well as testing with a subset of affected users that the impact has been remediated. If any users are still facing impact, they'll need to restart their Microsoft Teams application so the fix can be applied.
Scope of impact: Users who updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may have experienced failures of the Microsoft Teams application running as optimized for VDI.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
End time: Monday, August 31, 2026, at 2:30 PM UTC
Root cause: A recent update introduced a code defect that was resulting in this impacting event.
Next steps:
- We're reviewing our update procedures to understand why impact to application functionality wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 11:19:02 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application will restore optimized functionality.
Current status: After our completed deployed code fix, our internal service telemetry reports that the failures when running optimized Microsoft Teams in Virtual Desktop Infrastructure has been remediated. Users who continue to experience failures will need to twice restart their Microsoft Teams application so our fix can be applied and to remediate the impact.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Root cause: A recent update introduced a code defect that's resulting in this impacting event.
Next update by: Thursday, September 3, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 11:23:59 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: Our monitoring continues to show improvement, and we're continuing to observe the positive trend to ensure no further actions are needed and the impact is fully remediated.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Root cause: A recent update inadvertently introduced a code defect resulting in this impacting event.
Next update by: Tuesday, September 1, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Aug 28 17:06:43 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: We're observing positive trends in telemetry after applying our code fix for this issue and are allowing an additional period of monitoring to ensure that this event has fully resolved for all affected environments.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Root cause: A recent update inadvertently introduced a code defect resulting in this impacting event.
Next update by: Monday, August 31, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Aug 28 14:22:34 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: We've applied a code update change to remediate a code defect that was inadvertently introduced in the most recent service-side update. This code change will automatically be applied after four hours as part of the routine service refresh. Alternatively, users can restart Microsoft Teams to get the fix and then restart again five minutes later to apply the fix. We're continuing to monitor service-side telemetry to ensure the remediation actions fully resolve the impact.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Root cause: A recent update inadvertently introduced a code defect resulting in this impacting event.
Next update by: Friday, August 28, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Aug 28 12:49:41 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: We believe we’ve identified a recent service-side update as the root cause of this issue. We're validating a potential remediation solution, which will also confirm our root cause theory, before deploying it to all affected areas.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Next update by: Friday, August 28, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Aug 28 11:30:49 2026 |
|---|
| Description: | Title: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure
User impact: Users' Microsoft Teams application may fail to run as optimized in Virtual Desktop Infrastructure.
More info: This issue affects users who have updated to New VDI solution for Teams version 26213.1002.4977.2998 or later. Restarting the Microsoft Teams application may temporarily restore optimized functionality.
Current status: We're reviewing service-side logs and recent platform updates to determine the cause of reports that Microsoft Teams isn't consistently operating in its optimized VDI mode. We're analyzing available telemetry to identify the source of the issue and determine appropriate remediation options.
Scope of impact: Users who have updated their Virtual Desktop Infrastructure (VDI) to New VDI solution for Teams version of 26213.1002.4977.2998 or greater may experience failures of the Microsoft Teams application running as optimized for VDI. This information may be updated as our investigation continues.
Next update by: Friday, August 28, 2026, at 5:00 PM UTC
|
|---|
|
TM1466441 - Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
| Status: | serviceRestored |
|---|
| Start Time: | Tue Aug 18 09:30:00 2026 |
|---|
| End Time: | Thu Sep 3 09:46:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 13:29:12 2026 |
|---|
| Root Cause: | A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that was preventing Teams channel tabs from rendering correctly.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 11:49:42 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may have been unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may have only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels were long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may have not been visible.
As a workaround, impacted users could zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Final status: We've confirmed through testing with a subset of affected users that reverting the recent configuration change has remediated the impact.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may have been impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
End time: Thursday, September 3, 2026, at 1:46 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that was preventing Teams channel tabs from rendering correctly.
Next steps:
- We're reviewing the offending configuration change to understand why the regression wasn't identified during our pre-deployment testing processes, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 09:50:56 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We've completed the reversion of the offending configuration change and are reaching out to a number of impacted users to confirm that this action successfully resolved the issue.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly.
Next update by: Thursday, September 3, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 08:26:42 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We’re working to revert the offending configuration change. We expect that this will process will be complete and the issue resolved by our next scheduled update.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly.
Next update by: Thursday, September 3, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 08:26:41 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We’re working to revert the offending configuration change. We expect that this will process will be complete and the issue resolved by our next scheduled update.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly.
Next update by: Thursday, September 3, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 06:41:27 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We’ve determined that a recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly. We’re deploying a fix to mitigate the impact and conducting internal validation to confirm it successfully resolves the issue.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Start time: Tuesday, August 18, 2026, at 1:30 PM UTC
Root cause: A recent configuration change associated with a user interface modernization effort inadvertently introduced a regression that is preventing Teams channel tabs from rendering correctly.
Next update by: Thursday, September 3, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Sep 3 04:45:36 2026 |
|---|
| Description: | Title: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels
User impact: Users may be unable to access tabs beyond the Conversation tab in certain Microsoft Teams channels.
More info: Users may only see the Conversation tab in Microsoft Teams channels when channel names and associated sensitivity labels are long, particularly on smaller displays. As a result, other tabs such as Shared, Files, Notes, and custom tabs may not be visible.
As a workaround, impacted users can zoom out in Teams, use a larger display where available, or, in some cases, select the overflow arrow to access hidden tabs.
Current status: We're reviewing HTTP Archive (HAR) files and Teams client logs from a number of impacted users to determine the root cause and identify mitigation options.
Scope of impact: Any user attempting to access tabs beyond the Conversation tab in Microsoft Teams channels with long channel names and/or associated sensitivity labels may be impacted.
Next update by: Thursday, September 3, 2026, at 11:00 AM UTC
|
|---|
|
CW1461372 - Some users may be unable to receive responses when using Microsoft 365 Copilot Chat
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Aug 24 18:50:00 2026 |
|---|
| End Time: | Tue Aug 25 06:20:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 3 09:57:04 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 09:57:04 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Sep 1 20:09:20 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Aug 27 16:52:05 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Aug 25 08:02:17 2026 |
|---|
| Description: | Title: Some users may have been unable to receive responses when using Microsoft 365 Copilot Chat
User impact: Users may have been unable to receive responses when using Copilot Chat.
More info: Affected users may have received error messages stating that a problem had occurred or that Copilot could not respond.
Final status: We've completed reverting the change that inadvertently led to impact. Upon completing a period of monitoring, we've determined service availability has returned to normal, and the issue is resolved.
Scope of impact: This issue may have impacted any user attempting to use Copilot Chat.
Start time: Monday, August 24, 2026, at 10:50 PM UTC
End time: Tuesday, August 25, 2026, at 10:20 AM UTC
Preliminary root cause: A recent change designed to support metered access for certain scenarios did not deliver the expected outcome, inadvertently resulting in impact.
Next steps:
- We are reviewing our internal change management processes and controls to identify opportunities for improvement, and strengthen our safeguards around future changes.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue Aug 25 06:47:58 2026 |
|---|
| Description: | The roll back of the suspected change is continuing as expected. Early indications continue to show an improvement in service availability and we've received some reports from previously affected customers that the issue is resolved. We're continuing to monitor this rollback process closely to ensure a complete resolution is achieved.
Next update by: Tuesday, August 25, 2026, at 12:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 25 06:25:49 2026 |
|---|
| Description: | Title: Some users may be unable to receive responses when using Microsoft 365 Copilot Chat
User impact: Users may be unable to receive responses when using Copilot Chat.
More info: Affected users may receive error messages stating that a problem has occurred or that Copilot could not respond.
Current status: We've reverted the suspected change and are observing signs of recovery in service telemetry. We're engaging a sample of affected users to validate whether this action has successfully mitigated the issue and restored Chat functionality.
Scope of impact: This issue may impact any user attempting to use Copilot Chat. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 06:08:54 2026 |
|---|
| Description: | Title: Some users may be unable to receive responses when using Microsoft 365 Copilot Chat
User impact: Users may be unable to receive responses when using Copilot Chat.
More info: Affected users may receive error messages stating that a problem has occurred or that Copilot could not respond.
Current status: We've identified a recent service update that may be contributing to impact. We're continuing to analyze service telemetry and diagnostic data to validate this correlation while evaluating mitigation actions to reduce impact and restore Chat functionality.
Scope of impact: This issue may impact any user attempting to use Copilot Chat. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Aug 25 04:19:07 2026 |
|---|
| Description: | Title: Some users may be unable to receive responses when using Microsoft 365 Copilot Chat
User impact: Users may be unable to receive responses when using Copilot Chat.
More info: Affected users may receive error messages stating that a problem has occurred or that Copilot could not respond.
Current status: We've received reports indicating an issue with Copilot Chat where some users may be unable to receive responses to prompts. We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to use Copilot Chat may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 10:30 AM UTC
|
|---|
|
DZ1466442 - Admins have received delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal
| Status: | serviceRestored |
|---|
| Start Time: | Thu Sep 3 03:30:00 2026 |
|---|
| End Time: | Thu Sep 3 08:39:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 09:00:23 2026 |
|---|
| Root Cause: | A network policy hardening change introduced a regression affecting a dependency required by the service to retrieve essential configuration data. As a result, some service instances were unable to start successfully, reducing processing capacity and causing telemetry and alert delivery delays.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Sep 3 08:59:59 2026 |
|---|
| Description: | Title: Admins have received delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal
User impact: Admins have received delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.
More info: Affected admins may have experienced delays of up to 3 hours in receiving Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Final status: We've identified that a network policy hardening change introduced a regression affecting a dependency required by the service to retrieve essential configuration data. As a result, some service instances were unable to start successfully, reducing processing capacity and causing telemetry and alert delivery delays that led to backlog accumulation. We've re-enabled the affected access path and initiated a revert of the impacting networking policy change. Following our mitigation actions, affected service instances have begun recovering successfully and we've observed backlog recovery as processing capacity returned to expected levels.
Scope of impact: Some admins in Europe expecting to receive recent Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal or Microsoft Sentinel may have been impacted.
Start time: Thursday, September 3, 2026, at 7:30 AM UTC
End time: Thursday, September 3, 2026, at 12:39 PM UTC
Root cause: A network policy hardening change introduced a regression affecting a dependency required by the service to retrieve essential configuration data. As a result, some service instances were unable to start successfully, reducing processing capacity and causing telemetry and alert delivery delays.
Next steps:
- We're reviewing our networking policy deployment and validation processes to better identify and prevent similar issues before changes are introduced into production environments.
This is the final update for the event.
|
|---|
|
| Time: | Thu Sep 3 06:56:52 2026 |
|---|
| Description: | Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.
More info: Affected admins may experience delays of up to 3 hours in receiving Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We've initiated several mitigation actions to improve processing throughput, including scaling out the affected queue consumer service to increase processing capacity, redeploying the service in impacted regions, and testing configuration changes designed to reduce processing pressure and improve throughput. We're monitoring the effectiveness of these changes as we continue working to identify the underlying cause of the issue.
Scope of impact: Some admins in Europe expecting to receive recent Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal or Microsoft Sentinel may be impacted.
Start time: Thursday, September 3, 2026, at 7:30 AM UTC
Next update by: Thursday, September 3, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Sep 3 04:50:48 2026 |
|---|
| Description: | Title: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal
User impact: Admins may receive delayed Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal.
More info: Affected admins may experience delays of up to 3 hours in receiving Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We're reviewing service monitoring telemetry and analyzing system logs to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some admins in Europe expecting to receive recent Microsoft Defender for Endpoint telemetry and alerts in the Microsoft 365 Defender portal or Microsoft Sentinel may be impacted.
Start time: Thursday, September 3, 2026, at 7:30 AM UTC
Next update by: Thursday, September 3, 2026, at 11:00 AM UTC
|
|---|
|
OP1454727 - Users may be unable to sign in to OneNote using iOS devices
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Aug 14 07:51:32 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Sep 3 05:55:10 2026 |
|---|
| Root Cause: | A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
|
|---|
| Next Update: | Thursday, September 17, 2026, at 10:00 AM UTC |
|---|
|
Details
| Time: | Thu Sep 3 05:55:10 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've completed the validation of our fix in our internal testing environment and are preparing it for deployment, which should complete by our next scheduled update. Additionally, we've received confirmation from a subset of users who reported the issue that the fix resolves impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. This information may be updated as our investigation continues.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Thursday, September 17, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Sep 2 02:38:25 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: Current status: We're progressing with the validation of our fix in our internal testing environment. Additionally, we're continuing to await confirmation from a subset of users who reported the issue and have received the fix to help with validating its efficacy so we can proceed with its full release.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. This information may be updated as our investigation continues.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Thursday, September 3, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 01:58:26 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: Validating the efficiency of the fix is taking longer than expected. We're continuing with the validations in our internal testing environment, and we've released the new version containing the fix to a subset of users who reported the issue to help with validating if it remediates impact as expected.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. This information may be updated as our investigation continues.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Wednesday, September 2, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Aug 25 01:57:38 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've identified that additional testing and validations are required in order to ensure the issue is resolved without adversely impacting other aspects of the service. We've halted the release, and we're deploying it to our internal testing environment for additional validation before releasing it to the app store. Once our validations are complete, we'll aim to provide a new timeline for when we expect the deployment to be available in the App store.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted. This information may be updated as our investigation continues.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Tuesday, September 1, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Aug 24 01:21:03 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We confirmed that the fix will be part of the updated version of the OneNote app on iOS and are monitoring its implementation on the App Store. Once available, we'll confirm that the updated version remediates the impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Tuesday, August 25, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Fri Aug 21 18:43:26 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We’re continuing to monitor our fix deployments progress as it continues to saturate throughout the affected environment. Additionally, we expect that a remediation timeline will be provided by our next scheduled update.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Monday, August 24, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Tue Aug 18 00:57:55 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: Our fix deployment is taking longer than anticipated but is ongoing. We're continuing to monitor as it progresses to establish a completion timeline.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Friday, August 21, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 11:55:05 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've identified that a code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact. We're deploying a code fix to correct this issue and expect that it'll complete deployment by the time of our next update.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Tuesday, August 18, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 09:49:58 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've identified an issue with the OneNote iOS Authenticator broker sign-in and are working on developing and validating a fix to remediate impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Root cause: An issue with the OneNote iOS Authenticator broker sign-in is preventing users from signing in to OneNote using iOS devices.
Next update by: Friday, August 14, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 07:53:15 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
Current status: We've identified that a recent change to the sign in flow may be causing impact to occur. We've reverted the change but this did not resolve the issue. We're analyzing OneNote logs from impacted users as well as OneNote logs from our internal reproduction of the issue to assist us in identifying the underlying root cause of impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Next update by: Friday, August 14, 2026, at 2:00 PM UTC
|
|---|
|
EX1466248 - Some users may see intermittent mailbox access issues from any Exchange Online connection method
| Status: | serviceRestored |
|---|
| Start Time: | Wed Sep 2 16:03:08 2026 |
|---|
| End Time: | Wed Sep 2 17:33:40 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Sep 3 00:02:48 2026 |
|---|
| Root Cause: | A subset of infrastructure that facilitated access to Exchange Online mailboxes was operating in a sub optimal state, causing processing delays and leading to mailbox access issues.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 17:39:58 2026 |
|---|
| Description: | Title: Some users may see intermittent mailbox access issues from any Exchange Online connection method
User impact: Users may have seen intermittent mailbox access issues from any Exchange Online connection method.
Final status: We've determined that a subset of infrastructure that facilitated access to Exchange Online mailboxes was operating in a sub optimal state, causing processing delays and leading to mailbox access issues. We’ve switched out the affected subset of infrastructure to remediate the impact and confirmed from service telemetry that this issue is resolved.
Scope of impact: Some users based in North America may have seen intermittent mailbox access issues from any Exchange Online connection method.
Start time: Wednesday, September 2, 2026, at 7:45 PM UTC
End time: Wednesday, September 2, 2026, at 8:11 PM UTC
Root cause: A subset of infrastructure that facilitated access to Exchange Online mailboxes was operating in a sub optimal state, causing processing delays and leading to mailbox access issues.
Next steps: - We're continuing our investigation to determine the underlying reason the affected subset of infrastructure began operating in a sub optimal state to better detect and prevent issues like this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 2 16:28:40 2026 |
|---|
| Description: | Title: Some users may see intermittent mailbox access issues from any Exchange Online connection method
User impact: Users may see intermittent mailbox access issues from any Exchange Online connection method.
Current status: We're reviewing system logs and service telemetry to isolate the origin of this issue.
Scope of impact: Some users based in North America may see intermittent mailbox access issues from any Exchange Online connection method.
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 16:05:34 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
TM1437780 - Some users may be unable to join or create Microsoft Teams meetings or calls
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 20:25:00 2026 |
|---|
| End Time: | Thu Jul 23 21:27:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Sep 2 22:45:12 2026 |
|---|
| Root Cause: | The incident was triggered during the rollback of a Cosmos DB configuration designed to help limit the impact of failures and prevent wider service disruptions in one of the Teams services. As part of a precautionary investigation into a potential issue with this configuration, the feature was disabled in the APAC region. During the rollback, a subset of data partitions experienced a temporary service inconsistency for approximately 23 minutes, which resulted in intermittent request failures.
As dependent services and client applications attempted to recover from these failures, request volumes increased significantly and created an unexpected surge in traffic across several platform services. The elevated traffic levels placed substantial pressure on service infrastructure, leading to broader service degradation and impacting some calling and meeting scenarios.
The issue gradually self-resolved as platform scaling and traffic-management mechanisms automatically adjusted to absorb the increased demand. While service was restored without additional customer action, there are follow-up repair items to further strengthen resilience and reduce the likelihood of similar incidents in the future. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 22:45:12 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Aug 27 21:16:07 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jul 31 17:46:55 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 30 19:15:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jul 27 18:36:11 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 23 23:08:49 2026 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings or calls
User impact: Users may have been unable to join or create Microsoft Teams meetings or calls.
More info: According to our impact analysis, the following scenarios were among those most impacted:
-Recordings and Transcriptions
-1:1 Calling
-Group calling
-Meeting join
-Meeting scheduling and creation
-Public switched telephone network (PSTN) calls
Final status: After a recursive analysis of additional metrics, we've observed persistent recovery across all previously affected scenarios. Closer analysis identified a recent change associated with our ongoing service resilience efforts which overloaded our traffic management processes and caused impact. The service is now restored; however, users whose calls and meetings were previously affected may need to end and restart those calls and meetings to see full recovery.
Scope of impact: Any Microsoft Teams users in the Asia-Pacific region may have been impacted when attempting to create or join meetings or calls.
Start time: Friday, July 24, 2026, at 12:25 AM UTC
End time: Friday, July 24, 2026, at 1:27 AM UTC
Root cause: The incident was triggered during the rollback of a Cosmos DB configuration designed to help limit the impact of failures and prevent wider service disruptions in one of the Teams services. As part of a precautionary investigation into a potential issue with this configuration, the feature was disabled in the APAC region. During the rollback, a subset of data partitions experienced a temporary service inconsistency for approximately 23 minutes, which resulted in intermittent request failures.
As dependent services and client applications attempted to recover from these failures, request volumes increased significantly and created an unexpected surge in traffic across several platform services. The elevated traffic levels placed substantial pressure on service infrastructure, leading to broader service degradation and impacting some calling and meeting scenarios.
The issue gradually self-resolved as platform scaling and traffic-management mechanisms automatically adjusted to absorb the increased demand. While service was restored without additional customer action, there are follow-up repair items to further strengthen resilience and reduce the likelihood of similar incidents in the future.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Review document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Jul 23 21:59:17 2026 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings or calls
User impact: Users may be unable to join or create Microsoft Teams meetings or calls.
More info: According to our initial impact analysis, the following scenarios are among those most impacted:
-Transcriptions
-1:1 Calling
-Group calling
-Meeting join
-Meeting scheduling and creation
-Public switched telephone network (PSTN) calls
Current status: Our telemetry affirms that the impacted scenarios are nearly recovered. In parallel, we're recursively reviewing the health of the overall service environment, including dependent networking components, to better understand the cause and determine whether any mitigation actions are required to ensure the service remains healthy and available to users. In the interim, users' calls and meetings which were previously affected may need to be ended and restarted to see recovery.
Scope of impact: Any Microsoft Teams users in the Asia-Pacific region may be impacted when attempting to create or join meetings or calls. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:25 AM UTC
Next update by: Friday, July 24, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Jul 23 21:39:49 2026 |
|---|
| Description: | While we're observing recovery across a majority of affected scenarios, we're closely analyzing the service telemetry to isolate the source of the issue and ensure withstanding recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jul 23 21:26:59 2026 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings or calls
User impact: Users may be unable to join or create Microsoft Teams meetings or calls.
More info: According to our initial impact analysis, the following scenarios are among those most impacted:
-Transcriptions
-1:1 Calling
-Group calling
-Meeting join
-Meeting scheduling and creation
-Public switched telephone network (PSTN) calls
Current status: We're investigating a potential networking issue which we suspect is associated with the impact, and we're working to identify the most expeditious mitigation approach.
Scope of impact: Any Microsoft Teams users may be impacted when attempting to create or join meetings or calls.
Next update by: Friday, July 24, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Jul 23 21:02:55 2026 |
|---|
| Description: | Title: We're investigating a potential issue with Microsoft Teams
User impact: Users are reporting issues joining Microsoft Teams meetings.
Current status: We're investigating a potential issue which is preventing users from joining Microsoft Teams meetings and/or is causing disconnections, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1465677 - Users can't manage scheduled prompts in Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 1 13:17:25 2026 |
|---|
| End Time: | Wed Sep 2 21:03:57 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 2 21:05:18 2026 |
|---|
| Root Cause: | A recent service change designed to improve the management operations for scheduled prompts was preventing the management window from being displayed and was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 21:05:14 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users couldn't manage scheduled prompts in Copilot.
More info: When users attempted to schedule a prompt in Copilot, they received an error message that stated, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt was scheduled as expected. When the user then attempted to manage the scheduled prompt, they received the same error and were unable to manage it.
Final status: The rollback of the offending service change is complete and we’ve determined from service telemetry that this issue is resolved.
Scope of impact: Your organization was impacted by this event, and any user attempting to manage scheduled prompts in Copilot was affected.
Start time: Thursday, August 20, 2026, at 7:30 PM UTC
End time: Wednesday, September 2, 2026, at 10:50 AM UTC
Root cause: A recent service change designed to improve the management operations for scheduled prompts was preventing the management window from being displayed and was causing impact.
Next steps: - We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 2 16:55:31 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: The rollback of the offending service change has completed for a majority of the affected environment. At this time, most affected users should be able to manage scheduled prompts in Copilot as expected. We'll aim to provide a timeline for the rollback to complete for the remaining affected users by our next scheduled communications update.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 7:30 PM UTC
Root cause: A recent service change designed to improve the management operations for scheduled prompts is preventing the management window from being displayed and is causing impact.
Next update by: Thursday, September 3, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 18:02:15 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: We've identified the most efficient way to remediate the impact of the previously identified update. We're working to implement a rollback of the recent change and anticipate having an update to the timeframe for that action at our next communication time.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 7:30 PM UTC
Root cause: A recent service change designed to improve the management operations for scheduled prompts is preventing the management window from being displayed and is causing impact.
Next update by: Wednesday, September 2, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 15:01:59 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: We've identified a recent service change designed to improve the management operations for scheduled prompts, which is preventing the management window from being displayed and is causing impact. We're determining the most efficient method to reverse this change and remediate the impact.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Root cause: A recent service change designed to improve the management operations for scheduled prompts is preventing the management window from being displayed and is causing impact.
Next update by: Tuesday, September 1, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 14:31:35 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: We're reviewing our service side logs to identify any failures or abnormalities that may help us narrow down the reason users are seeing the error page, so that we can determine the most effective strategy to remediate the impact.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Next update by: Tuesday, September 1, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 13:34:03 2026 |
|---|
| Description: | Title: Users can't manage scheduled prompts in Microsoft 365 Copilot
User impact: Users can't manage scheduled prompts in Copilot.
More info: When users attempt to schedule a prompt in Copilot, they receive an error message that states, "Try refreshing the page. Something went wrong and we couldn't get the page to display." Despite receiving the error, the prompt is scheduled as expected. When the user then attempts to manage the scheduled prompt, they receive the same error and are unable to manage it.
Current status: We're reviewing the screenshots provided by a subset of affected users to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Your organization is impacted by this event, and any user attempting to manage scheduled prompts in Copilot is affected. This information may be updated as our investigation continues.
Next update by: Tuesday, September 1, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Sep 1 13:22:59 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
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 Sep 2 18:29:30 2026 |
|---|
| Root Cause: | A recent update to improve group deletions of Viva Engage communities within Microsoft Teams is resulting in impact.
|
|---|
| Next Update: | Wednesday, September 16, 2026, at 11:00 PM UTC |
|---|
|
Details
| 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
|
|---|
|
DZ1466215 - Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 1 18:00:00 2026 |
|---|
| End Time: | Wed Sep 2 16:30:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 2 17:57:46 2026 |
|---|
| Root Cause: | A portion of the Microsoft Defender for Office 365 infrastructure managing chat submissions was operating below acceptable performance thresholds, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 17:21:42 2026 |
|---|
| Description: | Title: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
User impact: Admins saw delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365.
More info: This event specifically impacted admins with V5 or V3 licenses.
Final status: Further review confirmed that the Microsoft Defender for Office 365 infrastructure managing chat submissions was operating below acceptable performance thresholds, resulting in impact. We've restarted the affected infrastructure, and confirmed through monitoring service health telemetry that grading functionality has been restored for email message and Microsoft Teams chat submissions. While we were able to reprocess a majority of requests that failed during the impact period, affected admins may need to resubmit some submissions if they're still seeing that grading didn't complete.
Scope of impact: Your organization was affected by this event, and any admin with V5 or V3 licenses receiving grades for email message or Microsoft Teams chat submissions in Microsoft Defender for Office 365 was impacted.
Start time: Tuesday, September 1, 2026, at 10:00 PM UTC
End time: Wednesday, September 2, 2026, at 8:30 PM UTC
Root cause: A portion of the Microsoft Defender for Office 365 infrastructure managing chat submissions was operating below acceptable performance thresholds, resulting in impact.
Next steps:
- We've reviewing the impacted Microsoft Defender for Office 365 infrastructure to determine what caused it to operate below acceptable performance thresholds and fail to handle traffic as expected, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 2 16:24:30 2026 |
|---|
| Description: | Title: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
User impact: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365.
More info: This event specifically impacts admins with V5 or V3 licenses.
Current status: We're continuing to restart the remaining affected infrastructure which is taking longer than initially anticipated. We're also preparing to reprocess the affected email messages and Microsoft Teams chats to fully remediate the issue.
Scope of impact: Your organization is affected by this event, and any admin with V5 or V3 licenses receiving grades for email message or Microsoft Teams chat submissions in Microsoft Defender for Office 365 is impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 1, 2026, at 10:00 PM UTC
Next update by: Wednesday, September 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 14:17:56 2026 |
|---|
| Description: | Title: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
User impact: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365.
More info: This event specifically impacts admins with V5 or V3 licenses.
Current status: We're reviewing service logs to determine the underlying cause of impact. As part of our investigation, we restarted a portion of the Microsoft Defender for Office 365 infrastructure responsible for processing submission grading and observed a return to expected processing performance within that portion of the service. We're now restarting the remaining affected infrastructure to determine whether this action fully restores processing performance. We're monitoring service behavior and will provide additional information, including an expected completion timeline for this remediation activity, in our next update.
Scope of impact: Your organization is affected by this event, and any admin with V5 or V3 licenses receiving grades for email message or Microsoft Teams chat submissions in Microsoft Defender for Office 365 is impacted. This section may be updated as our investigation continues.
Start time: Tuesday, September 1, 2026, at 10:00 PM UTC
Next update by: Wednesday, September 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 14:01:08 2026 |
|---|
| Description: | Title: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365
User impact: Admins see delayed grading for email message and Microsoft Teams chat submissions in Microsoft Defender for Office 365.
Current status: We're investigating a potential issue with Microsoft Defender for Office 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1461217 - Guest users were unable to access SharePoint Online sites connected to Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Aug 20 03:30:00 2026 |
|---|
| End Time: | Tue Aug 25 08:47:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Sep 2 14:30:25 2026 |
|---|
| Root Cause: | A change was made to significantly reduce request latency across almost all SPO requests by optimizing how the Dynamic Claims system retrieves and caches information through asynchronous tasks. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 14:27:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Aug 28 08:15:49 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Aug 26 05:14:27 2026 |
|---|
| Description: | Title: Guest users were unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users were unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users were redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins could have manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Final status: We've completed a period of monitoring service telemetry, and we've observed the restoration of service availability to normal levels. Additionally, during this time, we've received multiple reports from previously affected customers that they're experiencing relief from impact, and as such, we've determined this incident is resolved.
Scope of impact: This issue could have impacted any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Start time: Thursday, August 20, 2026, at 7:30 AM UTC
End time: Tuesday, August 25, 2026, at 12:47 PM UTC
Root cause: A change was made to significantly reduce request latency across almost all SPO requests by optimizing how the Dynamic Claims system retrieves and caches information through asynchronous tasks.
There was a latent bug within the initial Dynamic Claims flow where the service checks if the organization allows guest users for M365 group memberships. The pre-check did not force App-only credential requests to MS Graph and instead relied on the absence of user context in the thread to make the call app-only. This worked previously because the user context was not correctly propagated. However, in the new asynchronous tasks, the user context was correctly propagated, and this resulted in the failure to obtain the relevant token due to the service classifying the request as App+user. In this scenario, the service logic failed silently and put an empty value (i.e. the user is not a member of any M365 group) into the Dynamic Claims cache. This resulted in Dynamic Claims refresh call to fail for guest users and then being rejected from accessing the resources.
The issue was not detected by our monitoring systems in our early deployment rings (Microsoft’s internal organization etc.), as traffic for guest users is a small fraction of the overall dynamic traffic in these environments and therefore monitoring alerting thresholds were not met.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Aug 26 01:45:51 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We're continuing to engage in extended monitoring while we work with reporting organizations to confirm that the issue is fully resolved. If your organization has reported this problem, we request that you follow-up with the support case owner so we can confirm that the impact has been remediated.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Start time: Thursday, August 20, 2026, at 7:30 AM UTC
Root cause: A recently deployed change interacted with dynamic claims process, causing impact.
Next update by: Wednesday, August 26, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 21:47:35 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We've received some feedback indicating the impact is now resolved after we reverted the change. We're conducting persistent monitoring of the affected environment to ensure customers who previously reported the issue are seeing withstanding recovery.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Start time: Thursday, August 20, 2026, at 7:30 AM UTC
Root cause: A recently deployed change interacted with dynamic claims process, causing impact.
Next update by: Wednesday, August 26, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 09:29:59 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We're continuing to contact organizations who previously reported the issue, to confirm that the impact has been resolved after reverting the change.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Start time: Thursday, August 20, 2026, at 7:30 AM UTC
Next update by: Wednesday, August 26, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Aug 25 08:53:54 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We've identified a recently deployed change which interacted with dynamic claims process and out of an abundance of caution, we've reverted this change. We're contacting impacted organizations to confirm that this rollback has resolved the issue.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 08:17:07 2026 |
|---|
| Description: | We're reviewing forward synchronization protocols and other internal services to understand why the dynamic permission claims for guest users are not replicating as expected.
Next update by: Tuesday, August 25, 2026, at 1:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 25 07:28:21 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We're continuing our analysis of the network trace logs to help isolate why permissions that should grant access are not being correctly applied or recognized. This analysis will help us identify the underlying cause of the access issues and determine the appropriate remediation steps.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Aug 25 05:27:27 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
As a potential workaround, admins can manually add affected guest users directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Current status: We're continuing to analyze the collected network traces to determine why permissions that should grant access aren't being correctly applied or recognized. Additionally, we've identified a potential workaround that has been successful for a subset of impacted users, where affected guest users are manually added directly to the SharePoint Members group instead of relying on Microsoft 365 Group membership propagation.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 03:34:15 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: Specifically, guest users are redirected to an AccessDenied.aspx page when attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups.
Current status: We've analyzed the collected network traces and determined that some guest users are being treated as though they don't have the permissions required to access impacted SharePoint sites, resulting in Access Denied responses. We're continuing to investigate why permissions that should grant access aren't being correctly applied or recognized. We're reaching out to a subset of affected users to collect additional traces that capture the process of adding guest users and assigning permissions to further our investigation.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 02:32:22 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: The issue is specifically happening when permissions to the SharePoint Online sites are granted through Microsoft 365 groups.
Current status: We've collected additional network traces and are investigating why the guest users are seeing access denied errors. We suspect that there's an issue happening with permissions, and we're analyzing logs to confirm any potential issue that could be causing the impact.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 00:21:10 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: The issue is specifically happening when permissions to the SharePoint Online sites are granted through Microsoft 365 groups.
Current status: We're working to collect additional network traces from affected users for analysis. In addition, we're reviewing whether any recent service changes could be contributing to the impact.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Mon Aug 24 22:23:22 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: The issue is specifically happening when permissions to the SharePoint Online sites are granted through Microsoft 365 groups.
Current status: We're analyzing system logs to better understand the behavior with the guest users, which will help us to determine our next troubleshoot steps.
Scope of impact: This issue could impact any guest users attempting to access SharePoint Online sites where access is granted through Microsoft 365 Groups. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Mon Aug 24 22:02:08 2026 |
|---|
| Description: | Title: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams
User impact: Guest users are unable to access SharePoint Online sites connected to Microsoft Teams.
More info: The issue is specifically happening when permissions to the SharePoint Online sites are granted through Microsoft 365 groups.
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1461484 - Admins may see outdated/incomplete data in workspace settings of Power BI or Microsoft Fabric services
| Status: | serviceRestored |
|---|
| Start Time: | Sun Aug 2 00:12:00 2026 |
|---|
| End Time: | Wed Sep 2 10:27:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI and Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 2 11:40:41 2026 |
|---|
| Root Cause: | A code regression was causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 11:32:50 2026 |
|---|
| Description: | Title: Admins may see outdated/incomplete data in workspace settings of Power BI or Microsoft Fabric services
User impact: Admins may have seen outdated/incomplete data in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may have seen outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continued to apply successfully; however, updated values may have not been reflected in workspace settings after changes were saved or the page was refreshed.
Final status: We've addressed the issue blocking our deployment pipeline, initiated and completed the deployment of our fix to all affected environments, and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Impact was specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service.
Start time: Sunday, August 2, 2026, at 4:12 AM UTC
End time: Wednesday, September 2, 2026, at 2:27 PM UTC
Root cause: A code regression was causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next steps:
- We're reviewing the offending code regression to understand how it was introduced into the service, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 13:04:17 2026 |
|---|
| Description: | Title: Some workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: We're continuing our efforts to unblock our deployment pipeline and will provide a release timeline once it's resolved.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Start time: Sunday, August 2, 2026, at 4:12 AM UTC
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Wednesday, September 2, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Aug 31 11:45:37 2026 |
|---|
| Description: | Title: Some workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: Due to an unrelated issue impacting our deployment pipelines, deployment has been temporarily delayed. We're evaluating the current timeline to deployment, and we aim to share this as soon as possible.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Start time: Sunday, August 2, 2026, at 4:12 AM UTC
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Tuesday, September 1, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Aug 27 13:12:47 2026 |
|---|
| Description: | Title: Some workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: Our validation of the fix has completed successfully and we're scheduling a broad release to remediate impact. We expect to have a complete mitigation timeline by the next scheduled update.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Monday, August 31, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Aug 26 12:16:03 2026 |
|---|
| Description: | Title: Some workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: We're continuing to test and validate the effectiveness of our code fix within our internal testing environment prior to initiating a wider deployment. We aim to provide a timeline to remediation as soon as possible.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Thursday, August 27, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 11:14:41 2026 |
|---|
| Description: | Title: Some Workspace Admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace Admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace Admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: After further analysis of service monitoring telemetry, we’ve isolated that impact is caused by a code regression causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin. This causes the authorization check to be rejected, resulting in impact. We’re validating and testing a code fix to correct this regression, and we aim to provide a timeline to remediation as soon as possible.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service. This section may be updated as the investigation progresses.
Start time: Sunday, August 2, 2026, at 4:12 AM UTC
Root cause: A code regression is causing workspace settings requests to incorrectly identify the caller for the request as a tenant admin instead of a workspace admin, resulting in the authorization check being rejected.
Next update by: Wednesday, August 26, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 09:21:03 2026 |
|---|
| Description: | Title: Some Workspace Admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services
User impact: Workspace Admins see outdated/incomplete information in workspace settings of Power BI or Microsoft Fabric services.
More info: Workspace Admins may see outdated or incomplete information when viewing workspace settings, including Capacity Details, Domain settings, Contacts, OneDrive settings, and Semantic Model Storage Format. Configuration changes continue to be applied successfully; however, updated values may not be reflected in workspace settings after changes are saved or the page is refreshed.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some admins attempting to view the current state of workspace settings in the Power BI or Microsoft Fabric service.
Next update by: Tuesday, August 25, 2026, at 3:30 PM UTC
|
|---|
|
MO1465962 - Some users may have been unable to open Google search links from email and Microsoft Teams messages
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 1 22:53:00 2026 |
|---|
| End Time: | Wed Sep 2 07:24:26 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 2 07:25:56 2026 |
|---|
| Root Cause: | An inaccurate security classification caused legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Sep 2 07:25:52 2026 |
|---|
| Description: | Title: Some users may have been unable to open Google search links from email and Microsoft Teams messages
User impact: Users may have been unable to open Google search links from email and Microsoft Teams messages.
More info: Microsoft Defender for Office 365 Safe Links may have blocked the opening of Google search links (URLs), identifying them as malicious. In addition, admins may have received related alerts and incidents in the Microsoft Defender portal and Microsoft Sentinel as a result of these detections. Affected users received the following message when attempting to open the Google search links:
"Opening this website might not be safe"
Copying the hyperlink and pasting it directly into a browser didn’t bypass the warning.
Final status: We've received confirmation that the issue has been successfully resolved. However, some users may continue to experience impact for a limited time while the mitigation propagates through the service infrastructure.
Scope of impact: Some users attempting to open Google search links from email and Microsoft Teams messages may have been impacted.
Start time: Wednesday, September 2, 2026, at 2:53 AM UTC
End time: Wednesday, September 2, 2026, at 10:17 AM UTC
Root cause: An inaccurate security classification caused legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links.
Next steps:
- We're reviewing our URL reputation classification processes to help prevent similar false-positives in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Sep 2 06:37:02 2026 |
|---|
| Description: | Title: Some users may be unable to open Google search links from email and Microsoft Teams messages
User impact: Users may be unable to open Google search links from email and Microsoft Teams messages.
More info: Microsoft Defender for Office 365 Safe Links may block the opening of Google search links (URLs), identifying them as malicious. In addition, admins may receive related alerts and incidents in the Microsoft Defender portal and Microsoft Sentinel as a result of these detections. Affected users receive the following message when attempting to open the Google search links:
"Opening this website might not be safe"
Copying the hyperlink and pasting it directly into a browser doesn't bypass the warning.
Current status: We've corrected the inaccurate security classification, and internal testing indicates that this has successfully resolved the issue. However, some users may continue to experience impact for a limited time while the mitigation propagates through the service infrastructure. We're reaching out to a number of affected users to validate that remediation is complete.
Scope of impact: Some users attempting to open Google search links from email and Microsoft Teams messages may be impacted.
Start time: Wednesday, September 2, 2026, at 2:53 AM UTC
Root cause: An inaccurate security classification is causing legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links.
Next update by: Wednesday, September 2, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Wed Sep 2 05:58:38 2026 |
|---|
| Description: | Title: Some users may be unable to open Google search links from email and Microsoft Teams messages
User impact: Users may be unable to open Google search links from email and Microsoft Teams messages.
More info: Microsoft Defender for Office 365 Safe Links may block the opening of Google search links (URLs), identifying them as malicious. In addition, admins may receive related alerts and incidents in the Microsoft Defender portal and Microsoft Sentinel as a result of these detections. Affected users receive the following message when attempting to open the Google search links:
"Opening this website might not be safe"
Copying the hyperlink and pasting it directly into a browser doesn't bypass the warning.
Current status: We've determined that an inaccurate security classification is causing legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links. We're working to correct the misclassification to remediate impact.
Scope of impact: Some users attempting to open Google search links from email and Microsoft Teams messages may be impacted.
Start time: Wednesday, September 2, 2026, at 2:53 AM UTC
Root cause: An inaccurate security classification is causing legitimate Google search URLs to be incorrectly identified as malicious, resulting in Microsoft Defender for Office 365 Safe Links blocking access to affected links.
Next update by: Wednesday, September 2, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Sep 2 04:25:05 2026 |
|---|
| Description: | Title: Some users may be unable to open Google search links from email and Microsoft Teams messages
User impact: Users may be unable to open Google search links from email and Microsoft Teams messages.
More info: Microsoft Defender for Office 365 Safe Links may block the opening of Google search links (URLs), identifying them as malicious. In addition, admins may receive related alerts and incidents in the Microsoft Defender portal and Microsoft Sentinel as a result of these detections. Affected users receive the following message when attempting to open the Google search links:
"Opening this website might not be safe"
Copying the hyperlink and pasting it directly into a browser doesn't bypass the warning.
Current status: We're reviewing affected alert IDs for a subset of impacted users, while also analyzing blocked links and their source, to determine why legitimate Google search URLs are being classified as malicious.
Scope of impact: Some users attempting to open Google search links from email and Microsoft Teams messages may be impacted.
Next update by: Wednesday, September 2, 2026, at 10:30 AM UTC
|
|---|
|
DZ1459263 - Users may see failures when querying the Microsoft Graph Attack Simulation Training API with $Select OData query
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Aug 13 16:14:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Sep 2 00:18:01 2026 |
|---|
| Root Cause: | A code regression after a recent service update is impacting OData $Select query, causing failures.
|
|---|
| Next Update: | Tuesday, September 15, 2026, at 4:00 AM UTC |
|---|
|
Details
| 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.
|
|---|
|
IT1464731 - Some admins may be unable to view device information in the Microsoft Intune admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 31 05:09:53 2026 |
|---|
| End Time: | Tue Sep 1 22:04:12 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 1 22:16:06 2026 |
|---|
| Root Cause: | A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 22:16:03 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may have been unable to view device information in the Microsoft Intune admin center.
Final status: We've confirmed that the backlogged data has been processed and validated by internal monitoring that the issue is resolved.
Scope of impact: Impact was specific to some admins that attempted to view device inventory and reporting information in the Microsoft Intune admin center.
Start time: Saturday, August 29, 2026, at 1:41 AM UTC
End time: Wednesday, September 2, 2026, at 12:25 AM UTC
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next steps:
- We're reviewing the portion of reporting information to isolate what caused it to reference an outdated data source, and to prevent similar impact scenarios from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 20:39:30 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've identified that an increase of backlogged data is preventing the issue from being fully resolved. We're closely monitoring as it's being processed to ensure the impact is remediated for all impacted admins.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Wednesday, September 2, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 17:24:39 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We estimate that the required post-deployment processes will be completed and impact will be remediated by our next scheduled communication update.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Wednesday, September 2, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Sep 1 12:26:55 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: After our completed fix deployment, our service telemetry is reporting that a majority of the impact has been resolved. We're completing our post-deployment adjustments and validations and are expecting an updated timeline for the impact being remediating to be available by our next scheduled communication update.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Tuesday, September 1, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 05:11:54 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've confirmed that the fix has reached approximately 90% completion. We're completing the final remediation steps and monitoring progress as the deployment nears completion.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Tuesday, September 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Sep 1 02:26:29 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We're monitoring the fix deployment as it nears completion. We expect it will fully complete by our next scheduled update, at which time we'll conduct final validation checks within our service health telemetry to ensure impact is fully remediated.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Tuesday, September 1, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Mon Aug 31 14:14:58 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: The fix is progressing as expected, and we expect it to complete and remediate impact by the next scheduled update.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Tuesday, September 1, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 13:29:32 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We're initiating a staged roll out of the fix and will provide a remediation timeline once available.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Monday, August 31, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 11:22:12 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've completed the internal validation of a fix and are working to apply the mitigation more broadly.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Monday, August 31, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 09:18:37 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've identified that the reporting infrastructure was referencing outdated data, causing device information to not display as expected in affected reports. Administrators with limited administrative privileges may not see expected devices, while some data may be missing for global administrators. We're validating a fix through manual mitigation efforts before deploying it to the impacted environment.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Root cause: A portion of the reporting infrastructure referenced an outdated data source, resulting in device information not displaying as expected in affected reports.
Next update by: Monday, August 31, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 06:47:51 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've identified that device data remains available within the service; however, some device information isn't being displayed as expected in reporting views after devices check in. We're continuing our investigation by analyzing reporting telemetry and data processing behavior to determine why certain device attributes aren't being populated correctly and to develop a remediation plan.
Scope of impact: Impact is specific to some admins attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Next update by: Monday, August 31, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Aug 31 05:52:07 2026 |
|---|
| Description: | Title: Some admins may be unable to view device information in the Microsoft Intune admin center
User impact: Admins may be unable to view device information in the Microsoft Intune admin center.
Current status: We've identified a reporting issue affecting some admins in the Asia Pacific and Australia regions. Affected admins may not see expected device information in device inventory lists and dashboards. We're reviewing telemetry and service data from the affected environments to determine the source of impact.
Scope of impact: Impact is specific to some admins in the Asia Pacific and Australia regions attempting to view device inventory and reporting information in the Microsoft Intune admin center. This section may be updated as the investigation continues.
Next update by: Monday, August 31, 2026, at 11:30 AM UTC
|
|---|
|
TM1461801 - Users may be unable to use multiple Microsoft Teams features
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Aug 25 21:00:00 2026 |
|---|
| End Time: | Tue Aug 25 22:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Sep 1 19:55:58 2026 |
|---|
| Root Cause: | We determined that maintenance related work in the region was inadvertently causing impact to service health. We will provide more information regarding the root cause within our Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 19:55:58 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Aug 27 19:38:56 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Aug 25 22:23:15 2026 |
|---|
| Description: | Title: Users may be unable to use multiple Microsoft Teams features
User impact: Users may have been unable to use multiple Microsoft Teams features.
More info: Based on our telemetry, multiple Microsoft Teams features were affected such as:
- Live Events
- 1:1 Calling
- PSTN Calling
- Joining Meetings
- Creating Meetings
- Meeting General Functionality
- Town Hall Functionality
Final status: After a period of extended monitoring, we have confirmed that the issue is resolved.
Scope of impact: This issue could have affected any user located in Asia-Pacific.
Start time: Wednesday, August 26, 2026, at 1:00 AM UTC
End time: Wednesday, August 26, 2026, at 2:00 AM UTC
Root cause: We determined that maintenance related work in the region was inadvertently causing impact to service health. We will provide more information regarding the root cause within our Post-Incident Report.
Next steps: We're actively reviewing the maintenance work that resulted in this issue to identify the underlying cause and how to prevent it from occurring again.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue Aug 25 21:56:42 2026 |
|---|
| Description: | Our monitoring indicates that the issue is largely mitigated. We are continuing to monitor the service for the next 15 to 30 minutes to ensure there is no reoccurrence of this issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Aug 25 21:41:45 2026 |
|---|
| Description: | Title: Users may be unable to use multiple Microsoft Teams features
User impact: Users may be unable to use multiple Microsoft Teams features.
More info: Based on our telemetry, multiple Microsoft Teams features are affected:
- Live Events
- 1:1 Calling
- PSTN Calling
- Joining Meetings
- Creating Meetings
- Meeting General Functionality
- Town Hall Functionality
Current status: We have determined that maintenance related work was being conducted on the infrastructure based in Asia-Pacific. As an unintended result of this maintenance work, service health was impacted. We have paused our maintenance work and our telemetry indicates that the issue is no longer occurring. We're continuing to monitor service health and work with reporting users that the issue is no longer occurring.
Scope of impact: This issue could affect any user located in Asia-Pacific. This section is subject to change as our investigation continues.
Start time: Wednesday, August 26, 2026, at 1:00 AM UTC
Preliminary root cause: Maintenance related work in the region is inadvertently causing impact to service health. We will provide more information regarding the root cause as soon as possible.
Next update by: Wednesday, August 26, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Aug 25 21:26:48 2026 |
|---|
| Description: | Title: Users may be unable to join and create Microsoft Teams meetings
User impact: Users may be unable to join and create Microsoft Teams meetings.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1451939 - Users' locations may not be accurate during iOS Microsoft Teams emergency calls
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 2 11:09:00 2026 |
|---|
| End Time: | Tue Sep 1 14:07:59 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 1 14:17:34 2026 |
|---|
| Root Cause: | A change within iOS API infrastructure resulted in inaccurate user location data being reported during iOS emergency calls.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 14:17:31 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not have been accurate during iOS Microsoft Teams emergency calls.
More info: Affected users were still able to make iOS emergency calls, but their location might have been inaccurate to the responder. This was specific to users on iOS version 26 and newer.
Final status: After verifying with affected users that locations were accurate during iOS Microsoft Teams emergency calls, we've confirmed that the impact has been remediated.
Scope of impact: Impact was specific to users on iOS 26 or newer who made emergency calls using the Microsoft Teams application.
Start time: Thursday, July 2, 2026, at 3:09 PM UTC
End time: Monday, August 31, 2026, at 6:00 PM UTC
Root cause: A change within iOS API infrastructure resulted in inaccurate user location data being reported during iOS emergency calls.
Next steps:
- We're further analyzing the offending change within iOS API infrastructure to help us improve our pre-deployment testing and validation processes and to help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 08:08:39 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We've confirmed the new version deployment has completed successfully, and users should see their Microsoft Teams app update automatically.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues. However, users may also be able to manually download the latest version through the App Store. We're reaching out to your organization's representatives to ensure that impact is resolved.
Root cause: A change within iOS API infrastructure is resulting in inaccurate user location data being reported during iOS emergency calls.
Next update by: Tuesday, September 1, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 23:44:23 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: The deployment of the fix in the latest version of the Microsoft Teams app is in progress. We estimate that the deployment will complete by August 31, 2026. Users with automatic updates enabled in the App Store should see their Microsoft Teams app automatically updated over the course of the deployment. Users may also be able to manually download the latest version through the App Store. We'll continue monitoring the deployment progress to ensure that the impact is remediated.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: A change within iOS API infrastructure is resulting in inaccurate user location data being reported during iOS emergency calls.
Next update by: Tuesday, September 1, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 15:13:07 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We've completed the additional steps required to validate our remediation and have begun the deployment process. We’re aiming to provide more details on the timeline until resolution by our next scheduled communication update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: A change within iOS API infrastructure is resulting in inaccurate user location data being reported during iOS emergency calls.
Next update by: Tuesday, August 25, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Mon Aug 24 07:26:58 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing validation of the fix before deployment can begin. This process is taking longer than anticipated due to additional validation steps. We anticipate deployment will begin before our next scheduled update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: A change within iOS API infrastructure is resulting in inaccurate user location data being reported during iOS emergency calls.
Next update by: Monday, August 24, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Aug 21 07:24:30 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: Our previous update with regards to the fix was incorrect. We're preparing the fix to start deployment, which should start by our next scheduled update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure have resulted in inaccurate user location data during iOS emergency calls.
Next update by: Monday, August 24, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Thu Aug 20 03:50:50 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: The fix deployment is progressing and we expect this to be complete by our next scheduled update. It may take an additional 24 hours for the fix to propagate once its successfully deployed.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure have resulted in inaccurate user location data during iOS emergency calls.
Next update by: Friday, August 21, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Wed Aug 19 14:31:56 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing to monitor as the fix deployment progresses and will provide a complete remediation timeline once available.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure have resulted in inaccurate user location data during iOS emergency calls.
Next update by: Thursday, August 20, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Aug 19 09:49:53 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We've validated the fix and have begun deploying it to the affected infrastructure. We're monitoring the rollout as it continues to propagate across the environment, and are validating that the deployment is fully mitigating impact.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Wednesday, August 19, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 10:28:13 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're progressing with our efforts to validate a suitable fix in our test environment, although this is taking longer than initially anticipated. We're carrying out tests to ensure that the fix doesn't present any further issues and further clarify confirmation of the root cause.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Wednesday, August 19, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Aug 12 13:42:02 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing the validation process for our fix, and we'll aim to provide a timeline for it to complete by our next scheduled communications update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Thursday, August 13, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue Aug 11 14:55:33 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: The development of the fix is taking longer than initially expected. We'll provide an updated timeline once one is available.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Wednesday, August 12, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 08:49:31 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing to develop a fix in our internal environment to remediate impact and restore location data functionality. We expect this to be ready to be deployed by our next scheduled update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Tuesday, August 11, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 10 08:52:01 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We've identified that changes to iOS API infrastructure has inadvertently resulted in user location data to become inaccurate during iOS emergency calls. We're developing a fix in our internal environment to remediate impact and restore location data functionality.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application.
Root cause: Changes to iOS API infrastructure has inadvertently resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Tuesday, August 11, 2026, at 1:00 PM UTC
|
|---|
|
CP1465608 - Some users may experience delays or failures when receiving responses from Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 1 09:23:00 2026 |
|---|
| End Time: | Tue Sep 1 13:40:52 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Sep 1 13:42:08 2026 |
|---|
| Root Cause: | Elevated request volume overwhelmed a portion of the infrastructure responsible for processing Copilot requests, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 12:34:05 2026 |
|---|
| Description: | Title: Some users may experience delays or failures when receiving responses from Microsoft 365 Copilot
User impact: Users may have experienced delays or failures when receiving responses from Microsoft 365 Copilot.
More info: Affected users may have encountered error responses, delayed completions, or requests that failed to complete when using Microsoft 365 Copilot, Copilot Chat, Declarative Agents, and Copilot for Education experiences.
Final status: We’ve identified that elevated request volume overwhelmed a portion of the infrastructure responsible for processing Copilot requests, resulting in impact. To remediate the issue, we adjusted traffic flow to reduce the request load on the affected infrastructure. After monitoring the service, we verified that this action successfully resolved the issue.
Scope of impact: Impact was specific to some users attempting to receive responses from Microsoft 365 Copilot, Copilot Chat, Declarative Agents, and Copilot for Education experiences.
Start time: Tuesday, September 1, 2026, at 1:23 PM UTC
End time: Tuesday, September 1, 2026, at 5:40 PM UTC
Root cause: Elevated request volume overwhelmed a portion of the infrastructure responsible for processing Copilot requests, resulting in impact.
Next steps: We’re investigating why the elevated request volume resulted in impact to prevent recurrence.
- We’re optimizing scaling throughout the affected infrastructure to ensure it can better accommodate elevated request volume and prevent this issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 10:39:26 2026 |
|---|
| Description: | Title: Some users may experience delays or failures when receiving responses from Microsoft 365 Copilot
User impact: Users may experience delays or failures when receiving responses from Microsoft 365 Copilot.
More info: Affected users may encounter error responses, delayed completions, or requests that fail to complete when using Microsoft 365 Copilot, Copilot Chat, Declarative Agents, and Copilot for Education experiences.
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 attempting to receive responses from Microsoft 365 Copilot, Copilot Chat, Declarative Agents, and Copilot for Education experiences.
Next update by: Tuesday, September 1, 2026, at 5:00 PM UTC
|
|---|
|
DZ1465444 - Some admins may have seen incomplete or missing data in some Microsoft Defender for Office 365 reporting experiences
| Status: | serviceRestored |
|---|
| Start Time: | Sun Aug 30 19:30:00 2026 |
|---|
| End Time: | Tue Sep 1 06:33:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 1 08:06:54 2026 |
|---|
| Root Cause: | A section of reporting processes failed due to disk capacity exhaustion on affected backend infrastructure, causing report generation and data processing failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 07:28:44 2026 |
|---|
| Description: | Title: Some admins may have seen incomplete or missing data in some Microsoft Defender for Office 365 reporting experiences
User impact: Admins may have seen incomplete or missing data in some Microsoft Defender for Office 365 reporting experiences.
Final status: We've identified that a section of reporting processes failed due to disk capacity exhaustion on affected backend infrastructure, causing report generation and data processing failures. We've restored capacity on affected infrastructure through targeted file cleanup and workload redistribution which has fixed the issue.
Scope of impact: This issue impacted admins attempting to see data in Microsoft Defender for Office 365 reporting experiences.
Start time: Sunday, August 30, 2026, at 11:30 PM UTC
End time: Tuesday, September 1, 2026, at 10:33 AM UTC
Root cause: A section of reporting processes failed due to disk capacity exhaustion on affected backend infrastructure, causing report generation and data processing failures.
Next steps: We're analyzing performance data and trends on the affected database infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 05:09:14 2026 |
|---|
| Description: | Title: Some admins may see incomplete or missing data in some Microsoft Defender for Office 365 reporting experiences
User impact: Admins may see incomplete or missing data in some Microsoft Defender for Office 365 reporting experiences.
Current status: We're actively removing accumulated temporary files from impacted background infrastructure while redirecting workloads to alternate infrastructure as an initial attempt to mitigate impact. Investigations into the underlying file-cleanup failure are continuing to help validate a root cause hypothesis.
Scope of impact: This issue impacts admins attempting to see data in Microsoft Defender for Office 365 reporting experiences.
Next update by: Tuesday, September 1, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Tue Sep 1 03:33:22 2026 |
|---|
| Description: | Title: Some admins may see incomplete or missing data in some Microsoft Defender for Office 365 reporting experiences
User impact: Admins may see incomplete or missing data in some Microsoft Defender for Office 365 reporting experiences.
Current status: We're restarting impacted machines to clear sufficient temporary data and restore processing as an initial mitigation step. In parallel, we're reviewing service monitoring telemetry to validate our root cause theory and develop any further mitigation steps.
Scope of impact: This issue impacts admins attempting to see data in Microsoft Defender for Office 365 reporting experiences.
Next update by: Tuesday, September 1, 2026, at 9:30 AM UTC
|
|---|
|
CP1465477 - Some users may have experienced delays or failures when receiving responses from Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Tue Sep 1 03:50:00 2026 |
|---|
| End Time: | Tue Sep 1 05:10:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Sep 1 07:23:18 2026 |
|---|
| Root Cause: | An unexpected increase in request volume overwhelmed a portion of the infrastructure responsible for processing Copilot requests, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 07:21:53 2026 |
|---|
| Description: | Title: Some users may have experienced delays or failures when receiving responses from Microsoft 365 Copilot
User impact: Users may have experienced delays or failures when receiving responses from Microsoft 365 Copilot.
More info: Affected users may have encountered error responses, delayed completions, or requests that failed to complete when using Microsoft 365 Copilot, Copilot Chat, Declarative Agents, and Copilot for Education experiences.
Final status: We've determined that an unexpected increase in request volume overwhelmed a portion of the infrastructure responsible for processing Copilot requests, resulting in impact. While we were in the process of reviewing available mitigation options to restore services, system monitoring indicated that service had recovered. We've monitored service health for an extended period of time and confirmed that the issue is no longer occurring.
Scope of impact: Impact was specific to some users attempting to receive responses from Microsoft 365 Copilot, Copilot Chat, Declarative Agents, and Copilot for Education experiences.
Start time: Tuesday, September 1, 2026, at 7:50 AM UTC
End time: Tuesday, September 1, 2026, at 9:10 AM UTC
Root cause: An unexpected increase in request volume overwhelmed a portion of the infrastructure responsible for processing Copilot requests, resulting in impact.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Sep 1 05:37:47 2026 |
|---|
| Description: | Title: Some users may experience delays or failures when receiving responses from Microsoft 365 Copilot
User impact: Users may experience delays or failures when receiving responses from Microsoft 365 Copilot.
More info: Affected users may encounter error responses, delayed completions, or requests that fail to complete when using Microsoft 365 Copilot, Copilot Chat, Declarative Agents, and Copilot for Education experiences.
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 attempting to receive responses from Microsoft 365 Copilot, Copilot Chat, Declarative Agents, and Copilot for Education experiences.
Next update by: Tuesday, September 1, 2026, at 11:30 AM UTC
|
|---|
|
DZ1463442 - Users' browsers hang in Microsoft Defender for Office 365 when editing attack simulation training end user notifications
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 10 06:42:00 2026 |
|---|
| End Time: | Tue Sep 1 00:28:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Sep 1 01:33:56 2026 |
|---|
| Root Cause: | A latent code regression caused users’ browsers to hang in Microsoft Defender for Office 365 when editing attack simulation training end user notifications and resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Sep 1 01:33:45 2026 |
|---|
| Description: | Title: Users' browsers hang in Microsoft Defender for Office 365 when editing attack simulation training end user notifications
User impact: Users' browsers hung when editing Microsoft Defender for Office 365 attack simulation training end user notifications.
More info: When the browser hang occurred, the browser would hang indefinitely until the users exit out. This occurred before the user was able to perform the notification edits.
Final status: We've completed the development and deployment of our code fix and confirmed that impact has been successfully remediated.
Scope of impact: Some users who were utilizing Microsoft Defender for Office 365 editing attack simulation training end user notifications were impacted.
Start time: Monday, August 10, 2026, at 10:42 AM UTC
End time: Tuesday, September 1, 2026, at 4:28 AM UTC
Root cause: A latent code regression caused users’ browsers to hang in Microsoft Defender for Office 365 when editing attack simulation training end user notifications and resulted in impact.
Next steps:
- We're working to better understand the underlying cause of the latent code regression so that we can prevent similar issues from happening in the future and make the service more resilient.
This is the final update for the event.
|
|---|
|
| Time: | Sun Aug 30 01:27:16 2026 |
|---|
| Description: | Title: Users' browsers hang in Microsoft Defender for Office 365 when editing attack simulation training end user notifications
User impact: Users' browsers hang when editing Microsoft Defender for Office 365 attack simulation training end user notifications.
More info: When the browser hang occurs, the browser hangs indefinitely until the users exits out. This occurs before the user is able to perform the notification edits.
Current status: Following our review of the internal reproduction of impact and HAR logs provided by a subset of affected users, we’ve determined that there is a latent code regression that is causing users’ browsers to hang in Microsoft Defender for Office 365 when editing attack simulation training end user notifications and resulting in impact. We’ve developed a code fix to address this issue and anticipate that the deployment progress will begin prior to our next scheduled update. At which point, we aim to provide a remediation timeline.
Scope of impact: Some users who are utilizing Microsoft Defender for Office 365 users editing attack simulation training end user notifications are impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, August 11, 2026, at 2:30 PM UTC
Root cause: A latent code regression that is causing users’ browsers to hang in Microsoft Defender for Office 365 when editing attack simulation training end user notifications and resulting in impact.
Next update by: Tuesday, September 1, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Fri Aug 28 15:23:16 2026 |
|---|
| Description: | Title: Users' browsers hang in Microsoft Defender for Office 365 when editing attack simulation training end user notifications
User impact: Users' browsers hang when editing Microsoft Defender for Office 365 attack simulation training end user notifications.
More info: When the browser hang occurs, the browser hangs indefinitely until the users exits out. This occurs before the user is able to perform the notification edits.
Current status: We successfully reproduced the issue internally and are reviewing the resulting diagnostic data alongside HAR logs provided by your organization. We're using this analysis to identify the underlying cause and determine the most effective remediation approach.
Scope of impact: Some users who are utilizing Microsoft Defender for Office 365 users editing attack simulation training end user notifications are impacted. This section may be updated as the investigation progresses.
Next update by: Sunday, August 30, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Fri Aug 28 14:52:44 2026 |
|---|
| Description: | Title: Users' browsers hang in Microsoft Defender for Office 365 when editing attack simulation training end user notifications
User impact: Users' browsers hang when editing Microsoft Defender for Office 365 attack simulation training end user notifications.
More info: When the browser hang occurs, the browser hangs indefinitely until the users exits out. This occurs before the user is able to perform the notification edits.
Current status: We're reviewing HTTP Archive format (HAR) logs captured from an impacted user, in parallel with a screen recording of impact as we work to confirm potential sources of impact.
Scope of impact: Some users who are utilizing Microsoft Defender for Office 365 users editing attack simulation training end user notifications are impacted. This section may be updated as the investigation progresses.
Next update by: Friday, August 28, 2026, at 8:30 PM UTC
|
|---|
|
MV1465260 - Some users may be unable to perform searches in Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 31 17:45:00 2026 |
|---|
| End Time: | Mon Aug 31 22:25:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 31 23:16:07 2026 |
|---|
| Root Cause: | A recent authentication component configuration change in Microsoft Viva Engage impacted search functionality.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 31 23:15:48 2026 |
|---|
| Description: | Title: Some users may be unable to perform searches in Microsoft Viva Engage
User impact: Users may have been unable to perform searches in Microsoft Viva Engage.
Final status: We updated the authentication component configuration and monitored the telemetry to confirm that the impact was remediated.
Scope of impact: This issue may have potentially impacted any user performing searches in Microsoft Viva Engage.
Start time: Monday, August 31, 2026, at 9:45 PM UTC
End time: Tuesday, September 1, 2026, at 2:25 AM UTC
Root cause: A recent authentication component configuration change in Microsoft Viva Engage impacted search functionality.
Next steps: We're reviewing our service update procedures to be identify similar configuration problems prior to their implementation in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 31 20:34:15 2026 |
|---|
| Description: | Title: Some users may be unable to perform searches in Microsoft Viva Engage
User impact: Users may be unable to perform searches in Microsoft Viva Engage.
Current status: We identified a authentication configuration change in Microsoft Viva Engage that is impacting searches. We're working to update the authentication configuration to remediate the impact.
Scope of impact: This issue may be potentially impacting any user performing searches in Microsoft Viva Engage.
Start time: Monday, August 31, 2026, at 9:45 PM UTC
Root cause: A recent authentication configuration change in Microsoft Viva Engage impacts search functionality.
Next update by: Tuesday, September 1, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Aug 31 19:59:59 2026 |
|---|
| Description: | Title: Some users may be unable to perform searches in Microsoft Viva Engage
User impact: Users may be unable to perform searches in Microsoft Viva Engage.
Current status: We're investigating a potential issue with Microsoft Viva Engage and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OP1460815 - Some users may be unable to activate new or refresh existing Office 365 licenses
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Aug 24 09:00:00 2026 |
|---|
| End Time: | Mon Aug 24 15:40:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Aug 31 17:28:43 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 31 17:28:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Aug 26 19:12:45 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Aug 24 16:08:51 2026 |
|---|
| Description: | Title: Some users may be unable to activate new or refresh existing Office 365 licenses
User impact: Users may have been unable to activate new or refresh existing Office 365 licenses.
More info: For the users who were unable to activate or refresh Office 365 licenses, this prevented them from signing in or accessing Office 365 applications.
Users may have received multiple prompts; however, the activation process may have failed when they attempted to sign in.
Final status: After a brief period of monitoring, we confirmed that our service is healthy and users are no longer impacted by this event.
Scope of impact: Some users attempting to activate new or refresh existing Office 365 licenses may have been impacted.
Start time: Monday, August 24, 2026, at 1:00 PM UTC
End time: Monday, August 24, 2026, at 7:40 PM UTC
Preliminary root cause: A processing bottleneck within the service reduced its ability to handle incoming requests efficiently. As request volume accumulated, some requests experienced delays or timed out before they could be completed.
Next steps:
-We’re further investigating the bottleneck so we can determine what originally caused it and prevent similar future issues from leading to service impact.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Aug 24 15:07:27 2026 |
|---|
| Description: | We’re continuing to monitor closely as we incrementally restore traffic in the environment; however, the infrastructure hasn't returned to normal health as expected. We’re continuing to analyze recent changes made to the service so we can isolate and address a root cause while we in parallel explore options to further optimize the infrastructure and mitigate impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Aug 24 14:36:07 2026 |
|---|
| Description: | Title: Some users may be unable to activate new or refresh existing Office 365 licenses
User impact: Users may be unable to activate new or refresh existing Office 365 licenses.
More info: For the users who are unable to activate or refresh Office 365 licenses, this prevents them from signing in or accessing Office 365 applications.
Users may receive multiple prompts; however, the activation process may fail when they attempt to sign in.
Current status: The backlog on a portion of affected Office 365 infrastructure has been processed, and we’re reintroducing traffic to the environment. We’re monitoring this process closely to ensure it completes as expected and in parallel, we’re continuing to investigate the underlying cause of impact.
Scope of impact: Some users attempting to activate new or refresh existing Office 365 licenses may be impacted. This section may be updated as the investigation progresses.
Start time: Monday, August 24, 2026, at 1:00 PM UTC
Next update by: Monday, August 24, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 13:17:38 2026 |
|---|
| Description: | Title: Some users may be unable to activate new or refresh existing Office 365 licenses
User impact: Users may be unable to activate new or refresh existing Office 365 licenses.
More info: For the users who are unable to activate or refresh Office 365 licenses, this prevents them from signing in or accessing Office 365 applications.
Users may receive multiple prompts; however, the activation process may fail when they attempt to sign in.
Current status: We're implementing performance optimizations on affected Office 365 service infrastructure to assist with processing the activation backlog and to assist with recovering service reliability while we continue to isolate the underlying root cause.
Scope of impact: Some users attempting to activate new Office 365 licenses may be impacted. This section may be updated as the investigation progresses.
Start time: Monday, August 24, 2026, at 1:00 PM UTC
Next update by: Monday, August 24, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 11:24:00 2026 |
|---|
| Description: | Title: Some users may be unable to activate new or refresh existing Office 365 licenses
User impact: Users may be unable to activate new or refresh existing Office 365 licenses.
More info: For the users who are unable to activate or refresh Office 365 licenses, this prevents them from signing in or accessing Office 365 applications.
Users may receive multiple prompts; however, the activation process may fail when they attempt to sign in.
Current status: After further review of customer reports and our service monitoring telemetry, we've confirmed that impact is occurring for users attempting to activate new Office 365 licenses, which prevents them from being able to sign-in or access Office 365 applications. We've updated the "Title", "User impact", and "Scope of impact" fields of our communications to reflect this change. We're reviewing recent service updates to isolate potential sources of impact or discrepancies that could be causing this impact to users.
Scope of impact: Some users attempting to activate new Office 365 licenses may be impacted. This section may be updated as the investigation progresses.
Next update by: Monday, August 24, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 10:40:03 2026 |
|---|
| Description: | Title: Some users may be unable to sign-in or access Office 365 applications
User impact: Users may be unable to sign-in or access Office 365 applications.
More info: Users may receive multiple prompts to activate Office 365 applications; however, the activation process may fail when they attempt to sign in.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to sign into Office 365 applications may be impacted.
Next update by: Monday, August 24, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 10:22:59 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Office 365 apps
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Office 365 apps activations and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1458983 - Admins may encounter reporting delays across multiple Microsoft 365 admin centers and Viva Insights
| Status: | serviceDegradation |
|---|
| 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: | Mon Aug 31 15:36:54 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
|
|---|
|
CP1463378 - Users may see delayed data in Microsoft 365 Copilot usage and adoption reports
| Status: | serviceRestored |
|---|
| Start Time: | Fri Aug 28 19:00:00 2026 |
|---|
| End Time: | Sat Aug 29 21:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 31 15:02:38 2026 |
|---|
| Root Cause: | A delay within the upstream data processing pipeline resulted in subsequent delays generating usage and adoption reports
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 31 13:55:45 2026 |
|---|
| Description: | Title: Users may see delayed data in Microsoft 365 Copilot usage and adoption reports
User impact: Users may have seen delayed data in Microsoft 365 Copilot usage and adoption reports.
Final status: We've resolved the impacting delays in the upstream pipeline and restarted several report generation processes. After monitoring to ensure that the stalled reports processed and that new usage and adoption reports were being generated as expected, we've confirmed that the service availability has been fully restored.
Scope of impact: Impact may have occurred for users in North America and Europe, where affected users may have seen delayed data in Microsoft 365 Copilot usage and adoption reports.
Start time: Friday, August 28, 2026, at 11:00 PM UTC
End time: Sunday, August 30, 2026, at 1:00 AM UTC
Root cause: A delay within the upstream data processing pipeline resulted in subsequent delays generating usage and adoption reports
Next steps: - We're continuing to streamline the data processing flow to ensure robust service availability and effectively meet increasing user demand.
|
|---|
|
| Time: | Fri Aug 28 12:01:52 2026 |
|---|
| Description: | Title: Users may see delayed data in Microsoft 365 Copilot usage and adoption reports
User impact: Users may see delayed data in Microsoft 365 Copilot usage and adoption reports.
Current status: Our monitoring systems have identified impact for users in the North America and Europe regions, where affected users may see delayed data in Microsoft 365 Copilot usage and adoption reports. We’ve identified an upstream delay within the Microsoft 365 Copilot service that’s affecting usage and adoption reporting. We’re investigating the delay to determine its underlying cause and isolate an appropriate remediation action. We’ll provide a resolution timeline once available.
Scope of impact: Impact may occur for users in North America and Europe, where affected users may see delayed data in Microsoft 365 Copilot usage and adoption reports.
Next update by: Monday, August 31, 2026, at 7:00 PM UTC
|
|---|
|
DZ1462187 - Some admins may experience 30-minute delays on average in Microsoft Defender for Endpoint detections
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 26 08:50:00 2026 |
|---|
| End Time: | Mon Aug 31 08:54:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 31 11:12:49 2026 |
|---|
| Root Cause: | A section of the detection processing infrastructure was causing delays in the detections pipeline.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 31 11:12:35 2026 |
|---|
| Description: | Title: Some admins may experience 30-minute delays on average in Microsoft Defender for Endpoint detections
User impact: Admins may have experienced 30-minute delays on average in Microsoft Defender for Endpoint detections.
More info: Affected admins may have experienced delays in receiving Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel.
Final status: We've completed processing the accumulated backlog of Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel and validated that the issue is remediated.
Scope of impact: Some admins expecting to receive Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel detections may have been impacted.
Start time: Wednesday, August 26, 2026, at 12:50 PM UTC
End time: Monday, August 31, 2026, at 12:54 PM UTC
Root cause: A section of the detection processing infrastructure was causing delays in the detections pipeline.
Next steps:
- We're analyzing the affected detection processing infrastructure to further our understanding of the underlying source of impact and to validate what actions we can take to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 27 11:34:48 2026 |
|---|
| Description: | Title: Some admins may experience delays in Microsoft Defender for Endpoint detections
User impact: Admins may experience delays in Microsoft Defender for Endpoint detections.
More info: Affected admins may experience delays in receiving Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We're progressing with our processing of the accumulated backlog of Microsoft Defender for Endpoint detections, and we're expecting the process will have completed and for the impact to be remediated by our next scheduled communication update.
Scope of impact: Some admins expecting to receive Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel detections may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, August 26, 2026, at 12:50 PM UTC
Root cause: A section of the detection processing infrastructure that is causing delays in the detections pipeline.
Next update by: Monday, August 31, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Aug 26 11:41:59 2026 |
|---|
| Description: | Title: Some admins may experience delays in Microsoft Defender for Endpoint detections
User impact: Admins may experience delays in Microsoft Defender for Endpoint detections.
More info: Affected admins may experience delays in receiving Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We've implemented performance optimizations to assist with restoring the affected section of the detection processing infrastructure that was causing delays, and we’ve validated from our service monitors that users are now receiving new Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel. We're processing the backlog of affected Microsoft Defender for Endpoint detections, and we aim to provide a timeline to remediation by our next scheduled update.
Scope of impact: Some admins expecting to receive Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel detections may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, August 26, 2026, at 12:50 PM UTC
Root cause: A section of the detection processing infrastructure that is causing delays in the detections pipeline.
Next update by: Thursday, August 27, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Aug 26 10:14:33 2026 |
|---|
| Description: | Title: Some admins may experience delays in Microsoft Defender for Endpoint detections
User impact: Admins may experience delays in Microsoft Defender for Endpoint detections.
More info: Affected admins may experience delays in receiving Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel.
Current status: We've identified an issue within a section of the detection processing infrastructure that is causing delays in the detections pipeline. We've developed a potential mitigation and are currently validating its effectiveness while closely monitoring service health to ensure processing resumes and stabilizes as expected.
Scope of impact: Some admins expecting to receive Microsoft Defender for Endpoint detections in the Microsoft 365 Defender portal and Microsoft Sentinel detections may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, August 26, 2026, at 12:50 PM UTC
Root cause: A section of the detection processing infrastructure that is causing delays in the detections pipeline.
Next update by: Wednesday, August 26, 2026, at 7:30 PM UTC
|
|---|
|
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: | Mon Aug 31 09:35:36 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: | 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.
|
|---|
|
PB1464659 - Some users were unable to access the Power BI Data Agent or Microsoft Fabric Environment extensions
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 31 00:15:00 2026 |
|---|
| End Time: | Mon Aug 31 03:20:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI and Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 31 04:01:38 2026 |
|---|
| Root Cause: | A recent service deployment introduced compatibility issues and delivery inconsistencies with required application assets, resulting in resource loading failures for affected users. This condition caused blank screens, page load failures, and 4XX errors when accessing affected Fabric extension experiences.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 31 04:01:24 2026 |
|---|
| Description: | Title: Some users were unable to access the Power BI Data Agent or Microsoft Fabric Environment extensions
User impact: Users were unable to access the Power BI Data Agent or Microsoft Fabric Environment extensions.
More info: Additionally, affected users experienced blank screens, page load failures, or 4XX errors when attempting to access Fabric extensions, including Data Agent, Environment, Pipeline experiences, and associated artifacts.
Final status: We've validated through internal testing and monitoring that the aforementioned change successfully remediated impact.
Scope of impact: Some users attempting to access the Power BI Data Agent or Microsoft Fabric Environment extensions were affected.
Start time: Monday, August 31, 2026, at 4:15 AM UTC
End time: Monday, August 31, 2026, at 7:20 AM UTC
Root cause: A recent service deployment introduced compatibility issues and delivery inconsistencies with required application assets, resulting in resource loading failures for affected users. This condition caused blank screens, page load failures, and 4XX errors when accessing affected Fabric extension experiences.
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 this event.
|
|---|
|
| Time: | Mon Aug 31 02:35:46 2026 |
|---|
| Description: | Title: Some users may be unable to access the Power BI Data Agent or Microsoft Fabric Environment extensions
User impact: Users may be unable to access the Power BI Data Agent or Microsoft Fabric Environment extensions.
More info: Additionally, users may see blank screens, page load failures, or 4XX errors when attempting to access Fabric extensions, including Data Agent, Environment, Pipeline experiences, and associated artifacts.
Current status: We've identified that a recent service deployment introduced compatibility issues and delivery inconsistency with required applications, which is causing resource loading failures for affected users. We've implemented a configuration change in order to resolve the compatibility issue, and we're validating with internal testing and monitoring to confirm if our remediation efforts were successful.
Scope of impact: Some users attempting to access the Power BI Data Agent or Microsoft Fabric Environment extensions may be impacted. This information may be updated as our investigation continues.
Start time: Monday, August 31, 2026, at 4:15 AM UTC
Root cause: A recent service deployment introduced compatibility issues and delivery inconsistency with required applications, which is causing resource loading failures for affected users.
Next update by: Monday, August 31, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Mon Aug 31 02:22:30 2026 |
|---|
| Description: | Title: Some users may be unable to access the Power BI Data Agent or Microsoft Fabric Environment extensions
User impact: Users may be unable to access the Power BI Data Agent or Microsoft Fabric Environment extensions.
More info: Additionally, impacted users may see blank reports rendering.
Current status: We're investigating a potential issue with Microsoft Fabric and Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1462874 - Users may be unable to access or manage some Microsoft Teams channels features
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 27 15:22:00 2026 |
|---|
| End Time: | Thu Aug 27 23:29:55 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 27 23:32:05 2026 |
|---|
| Root Cause: | A processing delay caused requests to exceed the retry timeout and enter a queue before earlier requests had completed. This created a large backlog of failed events and prevented users from accessing or managing some Microsoft Teams channel features.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 23:32:01 2026 |
|---|
| Description: | Title: Users may be unable to access or manage some Microsoft Teams channels features
User impact: Users may have been unable to access or manage some Microsoft Teams channels features.
More info: Impacted features included viewing shared and private channel membership in the Microsoft Teams admin center and Microsoft Teams apps.
Final status: We disabled the affected request processing components to prevent additional requests from entering the backlog and allow our initial mitigative action to complete. We’ve confirmed through service monitoring that the backlog has cleared and the issue is resolved.
Scope of impact: This issue impacted some users in North America who attempted to access or manage Microsoft Teams channel membership features.
Start time: Thursday, August 27, 2026, at 7:22 PM UTC
End time: Friday, August 28, 2026, at 3:10 AM UTC
Root cause: A processing delay caused requests to exceed the retry timeout and enter a queue before earlier requests had completed. This created a large backlog of failed events and prevented users from accessing or managing some Microsoft Teams channel features.
Next steps: - We’re continuing our investigation to determine the underlying cause of the offending processing delays to better detect and prevent issues like this from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 27 21:34:35 2026 |
|---|
| Description: | Title: Users may be unable to access or manage some Microsoft Teams channels features
User impact: Users may be unable to access or manage some Microsoft Teams channels features.
More info: The currently impacted features include, but are not limited to:
- Viewing shared and private channel membership in the Microsoft Teams Admin Center
- Viewing shared and private channel membership in Microsoft Teams apps
Current status: We've updated the title, user impact, and scope of impact fields to reflect that we've confirmed that the majority of features related to Microsoft Teams channel access and management have recovered. However, our monitoring indicates that features related to user channel membership are still impacted due to the ongoing processing of the requests made to the managing API. We're continuing to analyze the reliability of this feature to determine if expediting remediation will be feasible.
Scope of impact: This issue may impact any user in North America who is attempting to interact with some features of Microsoft Teams channels. This information may be updated as our investigation continues.
Start time: Thursday, August 27, 2026, at 7:22 PM UTC
Root cause: A large number of user channel membership requests made to an API that handles Microsoft Teams channel information created a heavy load on service infrastructure, resulting in users in North America not being able to access or manage channels.
Next update by: Friday, August 28, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Aug 27 20:17:11 2026 |
|---|
| Description: | Title: Users may be unable to access or manage Microsoft Teams channels
User impact: Users may be unable to access or manage Microsoft Teams channels.
Current status: Our monitoring of service health telemetry indicates that a stronger change will be required to address this issue. We're deploying the next set of changes to achieve short-term mitigation. In addition, our analysis has identified a potential misconfiguration that may provide an option for long-term remediation.
Scope of impact: This issue may impact any user in North America who is attempting to interact with Microsoft Teams channels. This information may be updated as our investigation continues.
Start time: Thursday, August 27, 2026, at 7:22 PM UTC
Root cause: A large number of user channel membership requests made to an API that handles Microsoft Teams channel information created a heavy load on service infrastructure, resulting in users in North America not being able to access or manage channels.
Next update by: Friday, August 28, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Aug 27 18:29:17 2026 |
|---|
| Description: | Title: Users may be unable to access or manage Microsoft Teams channels
User impact: Users may be unable to access or manage Microsoft Teams channels.
Current status: While our initial remediation efforts relieved some of the impact from this issue, our ongoing monitoring of service health telemetry indicated that more robust changes will be necessary to achieve full remediation. We're developing an additional change to the way process calls are handled while continuing our investigation into the cause of this issue.
Scope of impact: This issue may impact any user in North America who is attempting to interact with Microsoft Teams channels. This information may be updated as our investigation continues.
Start time: Thursday, August 27, 2026, at 7:22 PM UTC
Root cause: A large number of user channel membership requests made to an API that handles Microsoft Teams channel information created a heavy load on service infrastructure, resulting in users in North America not being able to access or manage channels.
Next update by: Friday, August 28, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Aug 27 17:17:13 2026 |
|---|
| Description: | Title: Users may be unable to access or manage Microsoft Teams channels
User impact: Users may be unable to access or manage Microsoft Teams channels.
Current status: We've identified a large number of requests which are creating heavy load on service infrastructure that's responsible for processing user channel membership information. We're making a change to the way these process calls are handled to rebalance load across service infrastructure, which we expect will remediate impact.
Scope of impact: This issue may impact any user in North America who is attempting to interact with Microsoft Teams channels. This information may be updated as our investigation continues.
Root cause: A large number of user channel membership requests made to an API that handles Microsoft Teams channel information created a heavy load on service infrastructure, resulting in users in North America not being able to access or manage channels.
Next update by: Thursday, August 27, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Aug 27 16:23:30 2026 |
|---|
| Description: | Title: Users may be unable to access or manage Microsoft Teams channels
User impact: Users may be unable to access or manage Microsoft Teams channels.
Current status: We've identified a series of 500 and 503 error codes originating from specific APIs that are required for channel management. We're investigating these error codes to understand the manifestation of the issue.
Scope of impact: This issue may impact any user in North America who is attempting to interact with Microsoft Teams channels. This information may be updated as our investigation continues.
Start time: Thursday, August 27, 2026, at 7:22 PM UTC
Next update by: Thursday, August 27, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Aug 27 16:08:45 2026 |
|---|
| Description: | Title: Users may be unable to access or manage Microsoft Teams channels
User impact: Users may be unable to access or manage Microsoft Teams channels.
Current status: We're investigating a potential issue with accessing and managing Microsoft Teams channels and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MF1462932 - Users may experience delays or failures when Power Automate flows attempt to post messages to Microsoft Teams channels
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 27 18:54:31 2026 |
|---|
| End Time: | Thu Aug 27 21:21:56 2026 |
|---|
| Service: | Microsoft Power Automate in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 27 21:25:41 2026 |
|---|
| Root Cause: | A dependency-related issue was affecting a subset of Power Automate flows infrastructure which facilitates interactions with Microsoft Teams channels was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 21:25:38 2026 |
|---|
| Description: | Title: Users may experience delays or failures when Power Automate flows attempt to post messages to Microsoft Teams channels
User impact: Users may experience delays or failures when Power Automate flows attempt to post messages to Microsoft Teams channels.
More info: Users may receive a 429 or 500 error when the Power Automate flow fails, and the message won’t appear within the channel.
Final status: The deployment of our fix has completed and after an extended period of monitoring the service health telemetry, we’ve confirmed that impact has been remediated.
Scope of impact: Your organization was impacted by this event and users who utilized Power Automate flows to post messages to Microsoft Teams channels were affected.
Start time: Thursday, August 27, 2026, at 7:20 PM UTC
End time: Friday, August 28, 2026, at 12:32 AM UTC
Root cause: A dependency-related issue was affecting a subset of Power Automate flows infrastructure which facilitates interactions with Microsoft Teams channels was resulting in impact.
Next steps: -We’re continuing our investigation to determine how the dependency-related issue for the infrastructure which facilitates interactions with Microsoft Teams channels manifested as these actions will help better detect and prevent issues like this from occurring for all Microsoft 365 Power Automate in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 27 19:19:08 2026 |
|---|
| Description: | Title: Users may experience delays or failures when Power Automate flows attempt to post messages to Microsoft Teams channels
User impact: Users may experience delays or failures when Power Automate flows attempt to post messages to Microsoft Teams channels.
More info: Users may receive a 429 or 500 error when the Power Automate flow fails, and the message won’t appear within the channel.
Current status: We’ve identified a dependency-related issue which is affecting a subset of Power Automate flows that interact with Microsoft Teams channels and subsequently deployed a targeted fix to potentially address this issue. We anticipate that the completion of these actions will further refine our understanding of the underlying cause of impact and determine whether additional mitigative actions will be necessary.
Scope of impact: Your organization is impacted by this event and users who utilize Power Automate flows to post messages to Microsoft Teams channels are affected. This information may be updated as our investigation continues.
Next update by: Friday, August 28, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Aug 27 18:56:20 2026 |
|---|
| Description: | Title: Users may experience delays or failures when Power Automate flows attempt to post messages to Microsoft Teams channels
User impact: Users may experience delays or failures when Power Automate flows attempt to post messages to Microsoft Teams channels.
Current status: We're investigating a potential issue with Microsoft Power Automate and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
FL1462928 - Cloud flows are failing when posting or replying with adaptive cards in Microsoft Teams channels
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 27 15:20:00 2026 |
|---|
| End Time: | Thu Aug 27 20:32:00 2026 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 27 21:22:17 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 21:22:17 2026 |
|---|
| Description: | Title: Cloud flows are failing when posting or replying with adaptive cards in Microsoft Teams channels
User impact: Cloud flows were failing when posting or replying with adaptive cards in Microsoft Teams channels.
Final Status: We have completed applying the configuration changes and, after a period of monitoring service health diagnostics, confirmed that the issue has been resolved.
This is the final update on the incident.
Preliminary Root Cause: An internal service dependency experienced an influx of service calls, which exhausted the available resources within the service infrastructure.
Next Steps: We're analyzing service traffic data on the affected service infrastructure to prevent this problem from happening again.
|
|---|
|
| Time: | Thu Aug 27 20:18:59 2026 |
|---|
| Description: | Title: Cloud flows are failing when posting or replying with adaptive cards in Microsoft Teams channels
User impact: Cloud flows are failing when posting or replying with adaptive cards in Microsoft Teams channels.
More Info: Users may receive a 429 or 500 error when the flow fails, and the message will not appear in the channel.
Current Status: Following our service diagnostic review, we identified that the internal service dependency experienced an influx of service calls, which exhausted the available resources within the service infrastructure. We are applying configuration changes to limit the amount of service calls to reduce resource exhaustion.
Next Update: Friday, August 28, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Aug 27 18:35:08 2026 |
|---|
| Description: | Title: Cloud flows are failing when posting or replying with adaptive cards in Microsoft Teams channels
User impact: Cloud flows are failing when posting or replying with adaptive cards in Microsoft Teams channels.
More Info: Users may receive a 429 or 500 error when the flow fails, and the message will not appear in the channel.
Current Status: Following our investigation, we identified that a service dependency utilized when publishing adaptive cards in Microsoft Teams channels is experiencing a service issue. We are reviewing service diagnostics to isolate the root cause of the issue to determine our next troubleshooting steps.
Next Update: Friday, August 28, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Aug 27 18:27:33 2026 |
|---|
| Description: | Title: Cloud flows are failing when posting or replying with adaptive cards in Microsoft Teams channels
User impact: Cloud flows are failing when posting or replying with adaptive cards in Microsoft Teams channels.
More Info: Users may receive a 429 or 500 error when the flow fails, and the message will not appear in the channel.
Current Status: We are aware of an emerging issue where cloud flows are failing when posting or replying with adaptive cards in Microsoft Teams channels. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
SP1461580 - Some users may not receive results when searching on SharePoint Online sites
| Status: | serviceRestored |
|---|
| Start Time: | Tue Aug 25 12:58:38 2026 |
|---|
| End Time: | Thu Aug 27 21:06:29 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Search and Delve |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 27 21:10:09 2026 |
|---|
| Root Cause: | A recent change to search indexing was not applied as expected, which resulted in some users accessing indexes hosted in the impacted infrastructure not receiving search results.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 21:09:34 2026 |
|---|
| Description: | Title: Some users may not receive results when searching on SharePoint Online sites
User impact: Users may not have received results when searching on SharePoint Online sites.
More info: Users may have seen a blank screen when searching on affected SharePoint Online sites.
Final status: Our targeted reversion has applied to all previously affected users, and we've monitored our service-side metrics to confirm that the impact is remediated.
Scope of impact: Some users may not have received results and may see a blank screen when searching on SharePoint Online sites.
Start time: Tuesday, August 25, 2026, at 7:57 AM UTC
End time: Thursday, August 27, 2026, at 10:52 AM UTC
Root cause: A recent change to search indexing was not applied as expected, which resulted in some users accessing indexes hosted in the impacted infrastructure not receiving search results.
Next steps:
- We're continuing to analyze the manifestation of this issue to understand why our planned update was not applied as expected and instead resulted in impact.
This is the final update for the event.
|
|---|
|
| Time: | Wed Aug 26 17:25:04 2026 |
|---|
| Description: | Title: Some users may not receive results when searching on SharePoint Online sites
User impact: Users may not receive results when searching on SharePoint Online sites.
More info: Users may see a blank screen when searching on affected SharePoint Online sites.
Current status: Our testing with a subset of affected users indicates the issue is no longer occurring. We're continuing our testing while reviewing service health telemetry to determine if this feature scenario has recovered while we continue to progress our root cause investigation.
Scope of impact: Some users may not receive results and may see a blank screen when searching on SharePoint Online sites. This section may be updated as the investigation progresses.
Next update by: Friday, August 28, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 23:26:28 2026 |
|---|
| Description: | Title: Some users may not receive results when searching on SharePoint Online sites
User impact: Users may not receive results when searching on SharePoint Online sites.
More info: Users may see a blank screen when searching on affected SharePoint Online sites.
Current status: Our analysis of the Substrate search failures and 500 "NoSupportException" errors has been inconclusive. Subsequently, we’re working with a subset of affected users to gather additional details surrounding the affected ASC mailboxes so that we can refine our understanding of the underlying cause of impact and guide our next troubleshooting actions.
Scope of impact: Some users may not receive results and may see a blank screen when searching on SharePoint Online sites. This section may be updated as the investigation progresses.
Next update by: Wednesday, August 26, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 19:26:19 2026 |
|---|
| Description: | Title: Some users may not receive results when searching on SharePoint Online sites
User impact: Users may not receive results when searching on SharePoint Online sites.
More info: Users may see a blank screen when searching on affected SharePoint Online sites.
Current status: Our analysis of the Substrate search failures and 500 "NoSupportException" errors is progressing, though taking an extended period of time due to the complexity of this issue.
Scope of impact: Some users may not receive results and may see a blank screen when searching on SharePoint Online sites. This section may be updated as the investigation progresses.
Next update by: Wednesday, August 26, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Aug 25 17:09:34 2026 |
|---|
| Description: | Title: Some users may not receive results when searching on SharePoint Online sites
User impact: Users may not receive results when searching on SharePoint Online sites.
More info: Users may see a blank screen when searching on affected SharePoint Online sites.
Current status: We're continuing to analyze Substrate search failures and 500 "NoSupportException" errors to isolate the underlying source of impact.
Scope of impact: Some users may not receive results and may see a blank screen when searching on SharePoint Online sites. This section may be updated as the investigation progresses.
Next update by: Tuesday, August 25, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 15:06:57 2026 |
|---|
| Description: | Title: Some users may not be returned results when searching on SharePoint Online sites
User impact: Users may not be returned results when searching on SharePoint Online sites.
More info: Users may be returned a blank screen when searching on affected SharePoint Online sites.
Current status: We've updated the "Title", "User impact", "More info", and "Scope of impact" fields to reflect our updated understanding of impact. We're analyzing Substrate search failures occurring during impacted SharePoint Online searches to isolate the underlying source of impact.
Scope of impact: Some users may not be returned results and may see a blank screen when searching on SharePoint Online sites. This section may be updated as the investigation progresses.
Next update by: Tuesday, August 25, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 13:58:53 2026 |
|---|
| Description: | Title: Users aren't returned results when searching on SharePoint Online sites
User impact: Users aren't returned results when searching on SharePoint Online sites.
More info: Users are returned a blank screen when searching on affected SharePoint Online sites.
Current status: We're reviewing network traces provided by a subset of affected users to isolate potential discrepancies or points of impact to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and approximately 400 users aren't returned results and see a blank screen when searching on SharePoint Online sites. This section may be updated as the investigation progresses.
Next update by: Tuesday, August 25, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 13:14:34 2026 |
|---|
| Description: | Title: Users aren't returned results when searching on SharePoint Online sites
User impact: Users aren't returned results when searching on SharePoint Online sites.
More info: Users are returned a blank screen when searching on affected SharePoint Online sites.
Current status: We're reviewing the support case 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 approximately 400 users aren't returned results and see a blank screen when searching on SharePoint Online sites. This section may be updated as the investigation progresses.
Next update by: Tuesday, August 25, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 13:01:28 2026 |
|---|
| Description: | Title: Users aren't returned results when searching on SharePoint Online sites
User impact: Users aren't returned results when searching on SharePoint Online sites.
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.
|
|---|
|
TM1462904 - Some users with an active Microsoft Teams license may be unable to sign in to Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 27 10:41:00 2026 |
|---|
| End Time: | Thu Aug 27 19:54:07 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 27 19:55:17 2026 |
|---|
| Root Cause: | A recent authorization configuration change intended to block users without active licenses inadvertently blocked some users with active Microsoft Teams licenses, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 19:55:14 2026 |
|---|
| Description: | Title: Some users with an active Microsoft Teams license may be unable to sign in to Microsoft Teams
User impact: Users with an active Microsoft Teams license may have been unable to sign in to Microsoft Teams.
More info: Additionally, admins may have been unable to access organization wide settings.
Final status: We’ve completed the reversion of the offending authorization configuration change and confirmed through service telemetry that the issue is resolved.
Scope of impact: Impact was limited to some users with an active Microsoft Teams license who attempted to sign in to Microsoft Teams.
Start time: Thursday, August 27, 2026, at 2:41 PM UTC
End time: Thursday, August 27, 2026, at 9:58 PM UTC
Root cause: A recent authorization configuration change intended to block users without active licenses inadvertently blocked some users with active Microsoft Teams licenses, resulting in 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: | Thu Aug 27 17:59:12 2026 |
|---|
| Description: | Title: Some users with an active Microsoft Teams license may be unable to sign in to Microsoft Teams
User impact: Users with an active Microsoft Teams license may be unable to sign in to Microsoft Teams.
More info: Additionally, admins may be unable to access organization-wide settings.
Current status: We’ve initiated the reversion of the offending authorization configuration change and are monitoring the service to ensure it completes successfully. We’ll provide a resolution timeline once available.
Scope of impact: Impact may occur for some users with an active Microsoft Teams license who are attempting to sign in to Microsoft Teams. This information may be updated as our investigation continues.
Start time: Thursday, August 27, 2026, at 2:41 PM UTC
Root cause: A recent authorization configuration change intended to block users without active licenses inadvertently blocked some users with active Microsoft Teams licenses, resulting in impact.
Next update by: Friday, August 28, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Aug 27 17:16:49 2026 |
|---|
| Description: | Title: Some users with an active Microsoft Teams license may be unable to sign in to Microsoft Teams
User impact: Users with an active Microsoft Teams license may be unable to sign in to Microsoft Teams.
More info: Additionally, admins may be unable to access organization-wide settings.
Current status: We’ve received reports that some users with an active Microsoft Teams license are unable to sign in to Microsoft Teams. Our assessment has determined that a recent authorization configuration change intended to block users without active licenses is resulting in impact. We’re validating a remediation action to revert the offending change and will provide a resolution timeline once available.
Scope of impact: Impact may occur for some users with an active Microsoft Teams license who are attempting to sign in to Microsoft Teams. This information may be updated as our investigation continues.
Root cause: A recent authorization configuration change intended to block users without active licenses inadvertently blocked some users with active Microsoft Teams licenses, resulting in impact.
Next update by: Thursday, August 27, 2026, at 10:30 PM UTC
|
|---|
|
CP1458544 - Some users were unable to use Microsoft 365 Copilot in Excel
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Aug 20 17:00:00 2026 |
|---|
| End Time: | Fri Aug 21 08:20:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 27 19:36:03 2026 |
|---|
| Root Cause: | We've identified a component in a recent update that affected functionality and prevented access to the feature. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 19:36:03 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Aug 25 19:48:30 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Aug 21 10:29:01 2026 |
|---|
| Description: | Title: Some users were unable to use Microsoft 365 Copilot in Excel
User impact: Some users were unable to use Microsoft 365 Copilot in Excel because the Copilot pane was blank.
More info: Some users in the Asia Pacific region experienced an issue in which the Microsoft 365 Copilot pane in Excel appeared blank when opened, preventing access to Copilot functionality.
The affected users could restore functionality by restarting the application or rebooting their device.
Final status: We've completed the rollback of the affected update and validated that the issue is resolved.
Users who continue to experience a blank Copilot pane can restore functionality by restarting Excel or rebooting their device.
Scope of impact: Some users in the APAC region attempting to use Microsoft 365 Copilot in Excel may experience a blank Copilot pane and be unable to access Copilot functionality.
Start time: Thursday, August 20, 2026, at 9:00 PM UTC
End time: Friday, August 21, 2026, at 12:20 PM UTC
Preliminary root cause: A service configuration update associated with the Excel Agent deployment was unintentionally released to production users before intended validation was completed. The update introduced an issue that prevented the Copilot pane from loading correctly within the Excel desktop application.
We determined that the affected density configuration version had been rolled back for the web experience but remained active for the desktop experience. As impacted clients received the unintended configuration, the Copilot pane failed to render and appeared blank, preventing users from accessing Microsoft 365 Copilot functionality.
Next steps: For a more compressive set of next steps, please review the Post-Incident Report.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Fri Aug 21 04:40:42 2026 |
|---|
| Description: | Title: Some users may be unable to use Microsoft 365 Copilot in Excel
User impact: Some users may be unable to use or see Microsoft 365 Copilot in Excel.
More info: Specifically, some users in the APAC region are experiencing an issue where the Copilot in Excel side pane appears blank when opened, preventing them from using Copilot features.
The affected users are able to restore functionality by restarting the application or rebooting their device.
Current status: The rollback of the affected update is continuing, and most of the previously impacted users are now experiencing recovery. Users who continue to encounter a blank Copilot pane can restore functionality by restarting Excel or rebooting their device. We're actively monitoring recovery throughout the affected region to verify that service functionality is fully restored.
Scope of impact: Some users in the APAC region attempting to use Microsoft 365 Copilot in Excel may experience a blank Copilot pane and be unable to access Copilot functionality.
Start time: Thursday, August 20, 2026, at 9:00 PM UTC
Preliminary root cause: We've identified that a component in a recent update is affecting the Copilot experience in the Excel desktop application, preventing users from accessing the Copilot pane.
Next update by: Friday, August 21, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri Aug 21 02:01:16 2026 |
|---|
| Description: | Title: Some users may be unable to use Microsoft 365 Copilot in Excel
User impact: Some users may be unable to use or see Microsoft 365 Copilot in Excel.
More info: Specifically, some users in the APAC region are experiencing an issue where the Copilot in Excel side pane appeared blank when opened, preventing them from using Copilot features.
As a workaround, affected users may be able to restore functionality more quickly by restarting the application or rebooting their device.
Current status: We've identified a component within a recent update that prevented the feature from functioning as expected. The affected update has been rolled back, and we're actively monitoring recovery to ensure service is fully restored. We anticipate the feature will be available again within the next three hours.
Scope of impact: Some users in the APAC region attempting to use Copilot in Excel may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 9:00 PM UTC
Root cause: We've identified a component in a recent update that affected functionality and prevented access to the feature.
Next update by: Friday, August 21, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Fri Aug 21 01:33:52 2026 |
|---|
| Description: | As a workaround, affected users may be able to restore functionality more quickly by restarting the application or rebooting their device.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Aug 21 01:19:12 2026 |
|---|
| Description: | We've identified an update that caused the functionality to become unavailable. A rollback has been initiated, and we're closely monitoring recovery to ensure the experience is fully restored.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Aug 21 00:59:20 2026 |
|---|
| Description: | Title: Some users may be unable to use Microsoft 365 Copilot in Excel
User impact: Some users may be unable to use or see Microsoft 365 Copilot in Excel.
More info: Specifically, some users in the APAC region are experiencing an issue where the Copilot in Excel side pane appeared blank when opened, preventing them from using Copilot features.
Current status: We’re reviewing service telemetry to determine the root cause of the issue and evaluate the effectiveness of initial mitigation efforts. The investigation remains ongoing as we identify additional mitigation options to accelerate recovery.
Scope of impact: Some users in the APAC region attempting to use Copilot in Excel may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, August 21, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Thu Aug 20 23:43:20 2026 |
|---|
| Description: | Title: Some users aren't able to use Microsoft Copilot in Excel
User impact: Users aren't able to use or see Copilot in Excel.
More info: Specifically, impacted users report that when the Copilot in Excel side pane is opened, the panel is blank and the functionality is not usable.
Current status: We're reviewing service logs, recent changes introduced to the service, and contextual details provided by users who've encountered the issue to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Your organization is affected by this event, and some users attempting to use Copilot in Excel are impacted. This information may be updated as our investigation continues.
Next update by: Friday, August 21, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Thu Aug 20 23:34:14 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.
|
|---|
|
SP1461655 - Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 5 18:29:00 2026 |
|---|
| End Time: | Thu Aug 27 14:02:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 27 17:58:25 2026 |
|---|
| Root Cause: | An automated code update intended to upgrade supporting software packages removed a required feature gate, leading to the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 17:57:33 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not have seen the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Final status: We've completed the deployment of our fix and confirmed after additional testing with a subset of affected users that impact was successfully remediated.
Scope of impact: Any user may not have seen the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Start time: Wednesday, August 5, 2026, at 10:29 PM UTC
End time: Thursday, August 27, 2026, at 6:02 PM UTC
Root cause: An automated code update intended to upgrade supporting software packages removed a required feature gate, leading to the impact.
Next steps:
- We're reviewing our automated code update procedures to identify opportunities to prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 27 13:45:41 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Current status: We've completed our validation of the necessary changes and have initiated the deployment of our fix to the affected environment. We anticipate this deployment will complete, remediating impact for all users, by our next scheduled communication update.
Scope of impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online. This information may be updated as our investigation continues.
Start time: Wednesday, August 5, 2026, at 10:29 PM UTC
Root cause: An automated code update intended to upgrade supporting software packages removed a required feature gate, leading to the impact.
Next update by: Thursday, August 27, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Aug 27 07:52:57 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Current status: We've determined that the deployment initially expected to mitigate impact will not resolve the issue. We're identifying an alternative deployment path that is believed to contain the required fix and are working to validate and deploy the necessary changes to the affected production environments. We're continuing to monitor progress and assess mitigation efforts as the deployment process moves forward.
Scope of impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online. This information may be updated as our investigation continues.
Root cause: An automated code update intended to upgrade supporting software packages removed a required feature gate, leading to the impact.
Next update by: Thursday, August 27, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Aug 27 04:35:07 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Current status: We've confirmed that the fix to restore the missing controls is progressing through the affected environments. We're actively validating the fix as it reaches additional infrastructure and monitoring the deployment to verify that impact is remediated as expected.
Scope of impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online. This information may be updated as our investigation continues.
Root cause: An automated code update intended to upgrade supporting software packages removed a required feature gate, leading to the impact.
Next update by: Thursday, August 27, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Aug 27 02:20:11 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Current status: We’ve initiated the deployment of a fix to address this issue and we’re monitoring its progress to assess and determine a timeline for its completion by our next scheduled update.
Scope of impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online. This information may be updated as our investigation continues.
Root cause: An automated code update intended to upgrade supporting software packages inadvertently removed a required feature gate, leading to the impact.
Next update by: Thursday, August 27, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Wed Aug 26 06:47:51 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Current status: We've developed and validated a fix in our internal testing environments to address impact. We're deploying the fix to the affected infrastructure and continue to monitor it's progress to ensure impact is remediated as expected.
Scope of impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online. This information may be updated as our investigation continues.
Root cause: An automated code update intended to upgrade supporting software packages inadvertently removed a required feature gate, leading to the impact.
Next update by: Thursday, August 27, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Aug 26 01:27:15 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Current status: We’ve determined that an automated code update intended to upgrade supporting software packages inadvertently removed a required feature gate, leading to the impact. We’re continuing the process of validating a fix to address this issue and we’ll provide a timeline for its deployment once available.
Scope of impact: Any user may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online. This information may be updated as our investigation continues.
Root cause: An automated code update intended to upgrade supporting software packages inadvertently removed a required feature gate, leading to the impact.
Next update by: Wednesday, August 26, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Aug 25 18:01:26 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Current status: We've developed a fix to address this impact while we conclude validating the underlying root cause of this event. We'll provide updates on our root cause investigation and remediation timeline by our next scheduled communication.
Scope of impact: Any user may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online. This information may be updated as our investigation continues.
Next update by: Wednesday, August 26, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Tue Aug 25 16:25:36 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
Current status: We're reviewing a reproduction of impact provided by a subset of affected users to assist in our investigation into the underlying root cause of this event.
Scope of impact: Any user may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online. This information may be updated as our investigation continues.
Next update by: Tuesday, August 25, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 15:52:55 2026 |
|---|
| Description: | Title: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online
User impact: Users may not see the controls in the file and media webpart for embedded PowerPoint files in SharePoint Online.
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.
|
|---|
|
EX1458145 - Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 10 21:00:00 2026 |
|---|
| End Time: | Wed Aug 26 21:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 27 14:14:36 2026 |
|---|
| Root Cause: | The mailbox migration task was being delayed due to the integrity validation process remaining pending at the completion stage, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 14:10:25 2026 |
|---|
| Description: | Title: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish
User impact: Users may have been unable to complete mailbox offboarding because the migration task is blocked and couldn’t finish.
Final status: We've completed deployment of our fix faster than initially anticipated and validated after a period of monitoring service availability that our actions successfully remediated impact.
Scope of impact: Users attempting to complete mailbox offboarding in Exchange Online may have been impacted by this issue.
Start time: Tuesday, August 11, 2026, at 1:00 AM UTC
End time: Thursday, August 27, 2026, at 1:00 AM UTC
Root cause: The mailbox migration task was being delayed due to the integrity validation process remaining pending at the completion stage, resulting in impact.
Next steps:
- We're analyzing the offending integrity validation process to validate how it was introduced into our service and to confirm what actions we can take to prevent similar impact scenarios from occurring in the future.
|
|---|
|
| Time: | Wed Aug 26 14:53:24 2026 |
|---|
| Description: | Title: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish
User impact: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish.
Current status: We've initiated release of the subsequent fix and users should see relief as it progresses. We'll expect to provide a complete remediation timeline by the next scheduled update.
Scope of impact: Users attempting to complete mailbox offboarding in Exchange Online may be impacted by this issue. This section may be updated as our investigation continues.
Root cause: The mailbox migration task is being delayed due to the integrity validation process remaining pending at the completion stage, resulting in impact.
Next update by: Thursday, August 27, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 16:54:12 2026 |
|---|
| Description: | Title: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish
User impact: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish.
Current status: Additional review indicates the issue isn't resolved for all affected users. We're continuing to prepare our code fix for deployment, and we'll aim to provide a timeline for it to begin by our next scheduled communications update.
Scope of impact: Users attempting to complete mailbox offboarding in Exchange Online may be impacted by this issue. This section may be updated as our investigation continues.
Root cause: The mailbox migration task is being delayed due to the integrity validation process remaining pending at the completion stage, resulting in impact.
Next update by: Wednesday, August 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 25 15:56:38 2026 |
|---|
| Description: | Title: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish
User impact: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish.
Current status: While we're preparing our code fix for deployment, we're monitoring service health telemetry to confirm whether the mitigation we implemented to disable the affected integrity validation process has resolved the issue for all affected users.
Scope of impact: Users attempting to complete mailbox offboarding in Exchange Online may be impacted by this issue. This section may be updated as our investigation continues.
Root cause: The mailbox migration task is being delayed due to the integrity validation process remaining pending at the completion stage, resulting in impact.
Next update by: Tuesday, August 25, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Aug 21 14:54:07 2026 |
|---|
| Description: | Title: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish
User impact: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish.
Current status: We've been able to successfully disable the affected integrity validation process and resolve this issue for the majority of users. We're in the process of developing a code fix for the remaining impacted users and will provide an updated timeline on this final step in the remediation process as soon as it becomes available.
Scope of impact: Users attempting to complete mailbox offboarding in Exchange Online may be impacted by this issue. This section may be updated as our investigation continues.
Root cause: The mailbox migration task is being delayed due to the integrity validation process remained pending at the completion stage, resulting in impact.
Next update by: Tuesday, August 25, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Aug 21 03:45:35 2026 |
|---|
| Description: | Title: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish
User impact: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish.
Current status: We're continuing to run the commandlet to help disable the aforementioned integrity validation process. We'll share a completion timeline when one becomes available.
Scope of impact: Users attempting to complete mailbox offboarding in Exchange Online may be impacted by this issue. This section may be updated as our investigation continues.
Root cause: The mailbox migration task is being delayed due to the integrity validation process remained pending at the completion stage, resulting in impact.
Next update by: Friday, August 21, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Aug 20 23:47:18 2026 |
|---|
| Description: | Title: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish
User impact: Users may be unable to complete mailbox offboarding because the migration task is blocked and can’t finish.
Current status: We’re running a commandlet to help disable the aforementioned integrity validation process and anticipate by our next scheduled communications update that this process has completed.
Scope of impact: Users attempting to complete mailbox offboarding in Exchange Online may be impacted by this issue. This section may be updated as our investigation continues.
Root cause: The mailbox migration task is being delayed due to the integrity validation process remained pending at the completion stage, resulting in impact.
Next update by: Friday, August 21, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Aug 20 16:21:36 2026 |
|---|
| Description: | Title: Users may experience delays completing mailbox offboarding because the migration task is blocked and cannot finish
User impact: Users may experience delays completing mailbox offboarding because the migration task is blocked and cannot finish.
Current status: We're progressing with our analysis into the observed behavior and verifying the source for the unsuccessful completions of integrity validations. In parallel, we're determining the best option for disabling the “IsInteg” process, which is the integrity validation, in our effort to remediate the impact.
Scope of impact: Impact is specific to some users in Asia Pacific region attempting to completing mailbox offboarding.
Root cause: The mailbox migration task is being delayed due to the integrity validation process remained pending at the completion stage, resulting in impact.
Next update by: Friday, August 21, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Thu Aug 20 10:31:04 2026 |
|---|
| Description: | Title: Users may experience delays completing mailbox offboarding because the migration task is blocked and cannot finish
User impact: Users may experience delays completing mailbox offboarding because the migration task is blocked and cannot finish.
Current status: We're continuing our investigation and evaluating mitigation options before proceeding with a broader disablement of the IsInteg process. In parallel, we're assessing whether the observed behaviour is the result of a recent regression to better understand the underlying issue and determine the most appropriate path forward.
Scope of impact: Impact is specific to some users in Asia Pacific region attempting to completing mailbox offboarding.
Root cause: The mailbox migration task is being delayed due to the integrity validation process remained pending at the completion stage, resulting in impact.
Next update by: Thursday, August 20, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Aug 20 08:38:55 2026 |
|---|
| Description: | Title: Users may experience delays completing mailbox offboarding because the migration task is blocked and cannot finish
User impact: Users may experience delays completing mailbox offboarding because the migration task is blocked and cannot finish.
Current status: We've identified that the mailbox migration task is being delayed due to the integrity validation process remained pending at the completion stage. We're disabling the integrity check for the affected mailboxes to remediate impact. We're monitoring the migration to confirm successful completion and validate that offboarding can proceed as expected.
Scope of impact: Impact is specific to some users in Asia Pacific region attempting to completing mailbox offboarding.
Root cause: The mailbox migration task is being delayed due to the integrity validation process remained pending at the completion stage, resulting in impact.
Next update by: Thursday, August 20, 2026, at 2:30 PM UTC
|
|---|
|
PB1462800 - Some users may experience intermittent failures or delays when accessing Microsoft Power BI or Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 27 11:15:00 2026 |
|---|
| End Time: | Thu Aug 27 12:47:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI and Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 27 13:58:10 2026 |
|---|
| Root Cause: | An unexpected influx in user traffic caused our service infrastructure to begin operating in an unhealthy state, delaying the processing of user requests.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 13:57:57 2026 |
|---|
| Description: | Title: Some users may experience intermittent failures or delays when accessing Microsoft Power BI or Microsoft Fabric
User impact: Users may have experienced intermittent failures or delays when accessing Microsoft Power BI or Microsoft Fabric.
Final status: We've completed our monitoring period of service availability and confirmed that our performance optimizations successfully remediated impact.
Scope of impact: This incident impacted some users, who may have experienced intermittent failures or delays when accessing Microsoft Power BI or Microsoft Fabric.
Start time: Thursday, August 27, 2026, at 3:15 PM UTC
End time: Thursday, August 27, 2026, at 4:47 PM UTC
Root cause: An unexpected influx in user traffic caused our service infrastructure to begin operating in an unhealthy state, delaying the processing of user requests.
Next steps:
- We're analyzing the affected service infrastructure to validate what additional performance optimizations we can implement to bolster the resiliency of our service and to prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 27 13:16:48 2026 |
|---|
| Description: | Title: Some users may experience intermittent failures or delays when accessing Microsoft Power BI or Microsoft Fabric
User impact: Users may experience intermittent failures or delays when accessing Microsoft Power BI or Microsoft Fabric.
Current status: Our service monitors have alerted us to an availability drop affecting some users accessing Microsoft Power BI or Microsoft Fabric, who may experience intermittent failures or delays accessing our services. We've validated that impact was caused by an unexpected influx in user traffic, which caused our service infrastructure to begin operating in an unhealthy state and delaying the processing of user requests. We've implemented performance optimizations to recover affected infrastructure and are monitoring service availability to confirm impact is remediated.
Scope of impact: This incident impacts some users, who may experience intermittent failures or delays when accessing Microsoft Power BI or Microsoft Fabric. This section may be updated as the investigation progresses.
Start time: Thursday, August 27, 2026, at 3:15 PM UTC
Root cause: An unexpected influx in user traffic caused our service infrastructure to begin operating in an unhealthy state, delaying the processing of user requests.
Next update by: Thursday, August 27, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Aug 27 13:03:48 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Fabric and Microsoft Power BI
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft Fabric and Microsoft Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MB1462509 - Users may have seen blank pages when opening Microsoft Bookings
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 26 00:00:00 2026 |
|---|
| End Time: | Thu Aug 27 06:30:00 2026 |
|---|
| Service: | Microsoft Bookings |
|---|
| Feature Group: | Microsoft Bookings |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 27 10:30:24 2026 |
|---|
| Root Cause: | Bookings APIs were getting timed out because of repeated deprecated KV cache look-ups after a change was enabled for deprecation of the KV cache.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 27 10:28:23 2026 |
|---|
| Description: | Title: Users may have seen blank pages when opening Microsoft Bookings
User impact: Users may have seen blank pages when opening Microsoft Bookings.
Final status: We've determined that Bookings APIs were getting timed out because of repeated deprecated KV cache look-ups after a change was enabled for deprecation of the KV cache. We've deployed a fix and confirmed with a sample of affected users that impact has been remediated.
Scope of impact: Any user may have seen blank pages when opening Microsoft Bookings.
Start time: Wednesday, August 26, 2026, at 4:00 AM UTC
End time: Thursday, August 27, 2026, at 10:30 AM UTC
Root cause: Bookings APIs were getting timed out because of repeated deprecated KV cache look-ups after a change was enabled for deprecation of the KV cache.
Next steps: We’re reviewing our KV cache change procedures to help prevent the issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 27 00:49:47 2026 |
|---|
| Description: | Title: Users may see blank pages when opening Microsoft Bookings
User impact: Users may see blank pages when opening Microsoft Bookings.
Current status: Our review of the HAR network trace logs and the service health telemetry indicate that this issue is self-resolving. Subsequently, we’re reaching out to a subset of affected users to provide a reproduction of impact to determine this issue is still occurring while we continue working to determine the underlying cause of impact.
Scope of impact: Any user may see blank pages when opening Microsoft Bookings. This information may be updated as our investigation continues.
Next update by: Thursday, August 27, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Wed Aug 26 21:23:10 2026 |
|---|
| Description: | Title: Users may see blank pages when opening Microsoft Bookings
User impact: Users may see blank pages when opening Microsoft Bookings.
Current status: We've received additional user feedback indicating that users may be unable to open the Microsoft Bookings portal page and that other Bookings links may not load. While we continue to assess internal telemetry and user feedback to confirm the scope of the impacted scenarios, we're reaching out to a subset of impacted users to gather additional HTTP Archive format (HAR) network trace logs that we're anticipating can help us gain insight into the underlying source of impact and inform our next steps.
Scope of impact: Any user may see blank pages when opening Microsoft Bookings. This information may be updated as our investigation continues.
Next update by: Thursday, August 27, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Aug 26 20:21:31 2026 |
|---|
| Description: | Title: Users may see blank pages when opening Microsoft Bookings
User impact: Users may see blank pages when opening Microsoft Bookings.
Current status: We suspect that the issue facing your organization is connected to an ongoing service incident with Microsoft Bookings, however we need an additional HTTP Archive format (HAR) trace from your organization in order to confirm that this is the case. We've reached out to your representatives to collect this HAR trace so that we can determine the most effective next steps to resolve this issue.
Scope of impact: Any user may see blank pages when opening Microsoft Bookings. This information may be updated as our investigation continues.
Next update by: Thursday, August 27, 2026, at 4:00 AM UTC
|
|---|
|
PB1433864 - Users' filters in Excel PivotTables connected to Microsoft Fabric Semantic Models may have reset after a refresh
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 9 23:03:00 2026 |
|---|
| End Time: | Mon Jul 20 05:20:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 27 04:28:12 2026 |
|---|
| Root Cause: | A recent service change affected how Excel PivotTables retained filter selections after a Microsoft Fabric Semantic Model refresh.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 20 07:30:27 2026 |
|---|
| Description: | Title: Users' filters in Excel PivotTables connected to Microsoft Fabric Semantic Models may have reset after a refresh
User impact: Users' filters in Excel PivotTables connected to Microsoft Fabric Semantic Models may have reset after a refresh.
More info: After refreshing a Microsoft Fabric Semantic Model and the associated Excel PivotTable, previously selected filter values may have been cleared and reset to default selections. No data loss was identified; the impact was limited to retained filter selections within affected PivotTables.
Final status: Our investigation determined that a recently enabled change was resulting in users' filter selections resetting after Microsoft Fabric Semantic Model refresh operations. We've disabled the aforementioned change and confirmed that impact has been remediated after carefully monitoring the environment.
Scope of impact: Impact was limited to users in the UK South region with Excel PivotTables connected to Microsoft Fabric Semantic Models.
Start time: Friday, July 10, 2026, at 3:03 AM UTC
End time: Monday, July 20, 2026, at 9:20 AM UTC
Root cause: A recent service change affected how Excel PivotTables retained filter selections after a Microsoft Fabric Semantic Model refresh.
Next steps:
-We're reviewing our change testing and validation procedures to identify opportunities to improve impact detection and better prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 20 06:12:00 2026 |
|---|
| Description: | Title: Users' filters in Excel PivotTables connected to Microsoft Fabric Semantic Models may reset after a refresh
User impact: Users' filters in Excel PivotTables connected to Microsoft Fabric Semantic Models may reset after a refresh.
More info: After refreshing a Microsoft Fabric Semantic Model and the associated Excel PivotTable, previously selected filter values may be cleared and reset to default selections. No data loss has been identified; the impact is limited to retained filter selections within affected PivotTables.
Current status: We're continuing to validate the reported impact with affected users while reviewing additional information to refine the scope of impact. We're also validating a potential resolution and determining the appropriate next steps.
Scope of impact: Any user with Excel PivotTables connected to Microsoft Fabric Semantic Models may be affected by this issue.
Next update by: Monday, July 20, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Mon Jul 20 04:27:10 2026 |
|---|
| Description: | Title: Users' filters in Excel PivotTables connected to Microsoft Fabric Semantic Models may reset after a refresh
User impact: Users' filters in Excel PivotTables connected to Microsoft Fabric Semantic Models may reset after a refresh.
More info: After refreshing a Microsoft Fabric Semantic Model and the associated Excel PivotTable, previously selected filter values may be cleared and reset to default selections. No data loss has been identified; the impact is limited to retained filter selections within affected PivotTables.
Current status: We're investigating reports of previously applied filters resetting in Excel PivotTables connected to Microsoft Fabric Semantic Models after refresh operations. We've identified a recent service change associated with this behavior and are deploying a fix while monitoring its progress and effectiveness.
Scope of impact: Any user with Excel PivotTables connected to Microsoft Fabric Semantic Models may be affected by this issue.
Next update by: Monday, July 20, 2026, at 10:30 AM UTC
|
|---|
|
MO1453783 - We've detected a Microsoft 365 groups issue within your tenant
| Status: | investigationSuspended |
|---|
| Start Time: | Wed Aug 12 18:15:13 2026 |
|---|
| End Time: | Wed Aug 26 19:43:09 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 26 19:43:30 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 26 19:43:26 2026 |
|---|
| Description: | Title: We've detected a Microsoft 365 groups issue within your tenant
User impact: If action is not taken, users may see a duplicate "All Company" Microsoft 365 group in multiple Microsoft 365 services.
Final status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 20 01:39:06 2026 |
|---|
| Description: | Title: We've detected a Microsoft 365 groups issue within your tenant
User impact: If action is not taken, users may see a duplicate "All Company" Microsoft 365 group in multiple Microsoft 365 services.
Current status: Our systems detected a recent service update, intended to fix an unrelated issue, that may have caused an unexpected duplicate Microsoft 365 group named "All Company" to be created within your organization, which would appear in Microsoft Entra ID, SharePoint Online, Microsoft Planner, and Microsoft OneNote. The impacting service update has been reverted and didn’t affect the original "All Company" group or its content. While no new duplicate "All Company" groups are being created with the offending service update reverted, any duplicate "All Company" groups that were created during the impact period of Friday, July 3, 2026, to Wednesday, July 8, 2026, may still exist within your environment. If action is not taken, users may see a duplicate "All Company" Microsoft 365 group in multiple Microsoft 365 services.
Expiration message: This communication will expire in 7 days and is scheduled to remain active for the full duration.
|
|---|
|
| Time: | Wed Aug 12 18:21:53 2026 |
|---|
| Description: | Title: We've detected a Microsoft 365 groups issue within your tenant
User impact: If action is not taken, users may see a duplicate "All Company" Microsoft 365 group in multiple Microsoft 365 services.
Current status: Our systems detected a recent service update, intended to fix an unrelated issue, that may have caused an unexpected duplicate Microsoft 365 group named "All Company" to be created within your organization, which would appear in Microsoft Entra ID, SharePoint Online, Microsoft Planner, and Microsoft OneNote. The impacting service update has been reverted and didn’t affect the original "All Company" group or its content. While no new duplicate "All Company" groups are being created with the offending service update reverted, any duplicate "All Company" groups that were created during the impact period of Friday, July 3, 2026, to Wednesday, July 8, 2026, may still exist within your environment. If action is not taken, users may see a duplicate "All Company" Microsoft 365 group in multiple Microsoft 365 services.
Expiration message: This communication will expire in 7 days and is scheduled to remain active for the full duration.
|
|---|
|
EX1435168 - Some users may be unable to view location and subject details for other users' Exchange Online calendar items
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jul 13 20:00:00 2026 |
|---|
| End Time: | Mon Jul 27 16:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 26 18:34:07 2026 |
|---|
| Root Cause: | A recent Exchange Online service change introduced an issue affecting the preservation of calendar-sharing permissions during mailbox moves. The change was implemented to improve folder-copy consistency within the mailbox move process and modified the method used to validate the presence of calendar-sharing permissions. Due to this change, the validation process incorrectly identified these permissions as absent, even when they were configured correctly. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 26 18:34:07 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Aug 26 18:33:51 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jul 27 16:32:32 2026 |
|---|
| Description: | Title: Some users may be unable to view location and subject details for other users' Exchange Online calendar items
User impact: Users may have been unable to view location and subject details for other users' Exchange Online calendar items.
More info: Affected users may have only been able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Final status: We've confirmed that the deployment of the solution developed to correct the impacting permissions issue has completed, and we've validated with a subset of affected users that the impact has been resolved by our actions.
Scope of impact: Some users who attempted to view Exchange Online calendar items for users' calendars for which they were configured to have access may have been impacted.
Start time: Tuesday, July 14, 2026, at 12:00 AM UTC
End time: Monday, July 27, 2026, at 8:00 PM UTC
Root cause: A recent Exchange Online service change introduced an issue affecting the preservation of calendar-sharing permissions during mailbox moves. The change was implemented to improve folder-copy consistency within the mailbox move process and modified the method used to validate the presence of calendar-sharing permissions. Due to this change, the validation process incorrectly identified these permissions as absent, even when they were configured correctly.
As a result, mailboxes moved while the change was active were recreated without their existing calendar-sharing permission settings and instead reverted to the default availability-only configuration. Users who previously had permissions to view additional calendar details, such as meeting subjects and locations, were subsequently limited to viewing free/busy information only, resulting in the impact.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 24 17:42:05 2026 |
|---|
| Description: | Title: Some users may be unable to view location and subject details for other users' Exchange Online calendar items
User impact: Users may be unable to view location and subject details for other users' Exchange Online calendar items.
More info: Affected users may only be able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Current status: Our fix is deployed 35 percent to completion and we’re continuing to monitor its progress to provide as estimation of impact remediation by our next scheduled update.
Scope of impact: Some users attempting to view Exchange Online calendar items for users' calendars that they're configured to have access to may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, July 14, 2026, at 12:00 AM UTC
Root cause: A recent Exchange Online service change introduced a permissions issue that's preventing some users from viewing location and subject details for other users' calendars, which is resulting in impact.
Next update by: Monday, July 27, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jul 22 20:32:04 2026 |
|---|
| Description: | Title: Some users may be unable to view location and subject details for other users' Exchange Online calendar items
User impact: Users may be unable to view location and subject details for other users' Exchange Online calendar items.
More info: Affected users may only be able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Current status: We’ve completed the aforementioned final validation of our developed code fix and have begun deploying it to the affected environments. We’ll provide a timeline to remediation as it becomes available. When the fix has completed deployment, admins will need to reapply access permissions for the previously impacted users to restore access and fully resolve the impact.
Scope of impact: Some users attempting to view Exchange Online calendar items for users' calendars that they're configured to have access to may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, July 14, 2026, at 12:00 AM UTC
Root cause: A recent Exchange Online service change introduced a permissions issue that's preventing some users from viewing location and subject details for other users' calendars, which is resulting in impact.
Next update by: Friday, July 24, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jul 22 15:23:13 2026 |
|---|
| Description: | Title: Some users may be unable to view location and subject details for other users' Exchange Online calendar items
User impact: Users may be unable to view location and subject details for other users' Exchange Online calendar items.
More info: Affected users may only be able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Current status: We’ve confirmed that a recent Exchange Online service change introduced a permissions issue that's preventing some users from viewing location and subject details for other users' calendars. We've reverted the offending service change and are conducting final validations for our developed code fix, which we expect will deploy and remediate impact by our next communications update.
Scope of impact: Some users attempting to view Exchange Online calendar items for users' calendars that they're configured to have access to may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, July 14, 2026, at 12:00 AM UTC
Root cause: A recent Exchange Online service change introduced a permissions issue that's preventing some users from viewing location and subject details for other users' calendars, which is resulting in impact.
Next update by: Thursday, July 23, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 21 21:20:04 2026 |
|---|
| Description: | Title: Some users may be unable to view location and subject details for other users' Exchange Online calendar items
User impact: Users may be unable to view location and subject details for other users' Exchange Online calendar items.
More info: Affected users may only be able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Current status: We’re continuing the process of developing and validating a code fix to address what we suspect is a permissions issue introduced by a recent service change that’s preventing some users from viewing location and subject details for other users’ Exchange Online calendar to confirm our findings and potentially remediate the impact.
Scope of impact: Some users attempting to view Exchange Online calendar items for users' calendars that they're configured to have access to may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, July 22, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jul 21 14:14:58 2026 |
|---|
| Description: | Title: Some users may be unable to view location and subject details for other users' Exchange Online calendar items
User impact: Users may be unable to view location and subject details for other users' Exchange Online calendar items.
More info: Affected users may only be able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Current status: We've edited the Title, User impact, More info, and Scope of impact sections of this communication to align with our current understanding of the affected scenario. After further investigation, we identified that the affected users' mailboxes were recently migrated to alternate portions of storage infrastructure by our service as an automatic load balancing effort. When the migration took place, the permissions that allow users to view location and subject details for other users' calendars weren't properly copied over. We believe this is caused by the aforementioned service change and are developing a code fix designed to correct this issue.
Scope of impact: Some users attempting to view Exchange Online calendar items for users' calendars that they're configured to have access to may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, July 22, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Jul 21 12:23:58 2026 |
|---|
| Description: | Title: Some users may be unable to view location and subject details for other users' Exchange Online calendar items
User impact: Users may be unable to view location and subject details for other users' Exchange Online calendar items.
More info: Affected users may only be able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Current status: We've identified that some access permissions may not have been moved over during recent mailbox migrations and our findings suggest that a recent service change to how the service checks whether a folder has explicit Free/Busy permissions may be causing this issue. We're reversing the recent service change to confirm whether this is the case and to remediate the impact.
Scope of impact: Some users attempting to view Exchange Online calendar items for users' calendars that they're configured to have access to may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, July 21, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jul 21 08:18:07 2026 |
|---|
| Description: | Title: Some users may be unable to view location and subject details for other users' Exchange Online calendar items
User impact: Users may be unable to view location and subject details for other users' Exchange Online calendar items.
More info: Affected users may only be able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Current status: We're continuing our review of details provided by a subset of affected users to help us understand the root cause of impact and a mitigation plan.
Scope of impact: Some users attempting to view Exchange Online calendar items for users' calendars that they're configured to have access to may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, July 21, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Jul 21 06:35:11 2026 |
|---|
| Description: | Title: Some users may experience reduced calendar visibility as access permissions reset in Exchange Online
User impact: Users may experience reduced calendar visibility as access permissions reset in Exchange Online.
More info: Affected users may only be able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Current status: We're reviewing details provided by a subset of affected users to determine our next troubleshooting steps.
Scope of impact: Some users attempting to view Exchange Online calendar items for users' calendars that they're configured to have access to may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, July 21, 2026, at 12:30 PM UTC
|
|---|
|
MO1457636 - Users in South America may have been unable to use multiple Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Aug 19 10:15:00 2026 |
|---|
| End Time: | Wed Aug 19 10:39:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Aug 26 15:18:51 2026 |
|---|
| Root Cause: | A fiber event in the Colombia region shifted traffic onto a alternate network path, which became congested. This resulted in intermittent packet loss, traffic drops, slower connectivity, and/or higher latency. More details are provided within the Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 26 15:17:49 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Aug 21 12:25:25 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Aug 19 11:51:23 2026 |
|---|
| Description: | Title: Users in South America may have been unable to use multiple Microsoft 365 services
User impact: Users in South America may have been unable to access or experience degraded functionality with multiple services.
More info: Impacted services included, but were not limited to:
- Microsoft Teams
- Outlook
- Office Online Apps
Final status: We've confirmed that the issue is resolved after an extended period of monitoring.
Scope of impact: The majority of reports were from users in Colombia.
Start time: Wednesday, August 19, 2026, at 2:15 PM UTC
End time: Wednesday, August 19, 2026, at 2:39 PM UTC
Root cause: A fiber event in the Colombia region shifted traffic onto a alternate network path, which became congested. This resulted in intermittent packet loss, traffic drops, slower connectivity, and/or higher latency. More details are provided within the Post-Incident Report.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Aug 19 11:17:12 2026 |
|---|
| Description: | Title: Users in South America may be unable to use multiple Microsoft 365 services
User impact: Users in South America may be unable to access or experience degraded functionality with multiple Microsoft 365 services
More info: Impacted services include, but are not limited to:
- Microsoft Teams
- Outlook
- Office Online Apps
Current status: We've rerouted traffic through alternate network paths and telemetry shows the service had recovered by 2:50 PM UTC. We're monitoring to validate full recovery.
Scope of impact: The majority of reports are from users in Colombia. We're still assessing the scope of the issue and will update this section as we know more information.
Start time: Wednesday, August 19, 2026, at 2:14 PM UTC
Next update by: Wednesday, August 19, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Aug 19 11:00:52 2026 |
|---|
| Description: | Telemetry is showing improvement as our mitigation actions progress. This is in line with a reduction in user reports of impact.
This quick update is designed to give the latest information on this issue.
Next update by: Wednesday, August 19, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Aug 19 10:53:47 2026 |
|---|
| Description: | Title: Users in South America may be unable to use multiple Microsoft 365 services
User impact: Users in South America may be unable to access or experience degraded functionality with multiple Microsoft 365 services
More info: Impacted services include, but are not limited to:
- Microsoft Teams
- Outlook
- Office Online Apps
Current status: We've identified an issue with network paths in the South America region. We're currently rerouting traffic to alternate network paths to remediate impact.
Scope of impact: The majority of reports are from users in Colombia. We're still assessing the scope of the issue and will update this section as we know more information.
Next update by: Wednesday, August 19, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Aug 19 10:40:14 2026 |
|---|
| Description: | Title: Users in South America may be unable to use multiple Microsoft 365 services
User impact: Users in South America may be unable to access or experience degraded functionality with multiple Microsoft 365 services
More info: Impacted services include, but are not limited to:
- Microsoft Teams
- Outlook
- Office Online Apps
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings. This communication serves as a preliminary notification about a potential issue affecting your service. We'll provide an update in 30 minutes.
Scope of impact: The majority of reports are from users in Colombia. We're still assessing the scope of the issue and will update this section as we know more information.
|
|---|
|
OP1459987 - Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 19 20:00:00 2026 |
|---|
| End Time: | Tue Aug 25 15:19:30 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 25 16:19:30 2026 |
|---|
| Root Cause: | A standard .NET service update to improve service functionality had introduced an impacting code regression.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 25 16:19:27 2026 |
|---|
| Description: | Title: Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
User impact: Admins may have seen outdated device inventory and update status information in the Microsoft 365 Apps admin center.
More info: Device updates continued as expected, but the reported status and insights might not have reflected the latest device state in the Microsoft 365 Apps admin center.
Final status: We've determined that a recent standard update to improve service functionality introduced an impacting code regression, which was producing the outdated device inventory and update status information in the Microsoft 365 Apps admin center. After deploying our code fix and removing the isolated code regression, a queued collection of service requests required processing before the impact was resolved. Our internal service telemetry has verified that, following our completed request processing, the impact has been remediated.
Scope of impact: This issue affected any admin attempting to view device inventory and update status information in the Microsoft 365 Apps admin center.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
End time: Tuesday, August 25, 2026, at 7:00 AM UTC
Root cause: A standard .NET service update to improve service functionality had introduced an impacting code regression.
Next steps:
- We're further analyzing the offending .NET improvements to help us improve our pre-deployment testing and validation processes to prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 24 17:09:04 2026 |
|---|
| Description: | Title: Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
User impact: Admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center.
More info: Device updates are continuing as expected, but the reported status and insights may not reflect the latest device state.
Current status: Our code fix is fully deployed and as the backlog clears admins will start to see mitigation. We're continuing to monitor the progress of the backlog clearing and anticipate having a better understanding of the time needed for it to be finished by the time of our next communication update.
Scope of impact: Admins attempting to view device inventory and update status information in the Microsoft 365 Apps admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Next update by: Tuesday, August 25, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 12:12:57 2026 |
|---|
| Description: | Title: Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
User impact: Admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center.
More info: Device updates are continuing as expected, but the reported status and insights may not reflect the latest device state.
Current status: As we progress with our root cause analysis and confirm the source for this event, our validations have verified that our code fix addresses the outdated device inventory and update status admins are experiencing, remediating the impact. We're releasing our solution, and we'll provide an updated timeline for its deployment once it’s available.
Scope of impact: Admins attempting to view device inventory and update status information in the Microsoft 365 Apps admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Next update by: Monday, August 24, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 12:10:06 2026 |
|---|
| Description: | Title: Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
User impact: Admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center.
More info: Device updates are continuing as expected, but the reported status and insights may not reflect the latest device state.
Current status: As we progress with our root cause analysis and confirm the source for this event, our validations have verified that our code fix addresses the outdated device inventory and update status admins are experiencing, remediating the impact. We're releasing our solution, and we'll provide an updated timeline for its deployment once it’s available.
Scope of impact: Admins attempting to view device inventory and update status information in the Microsoft 365 Apps admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Next update by: Monday, August 24, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 00:49:46 2026 |
|---|
| Description: | Title: Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
User impact: Admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center.
More info: Device updates are continuing as expected, but the reported status and insights may not reflect the latest device state.
Current status: Following our internal validation process, we're moving to validate our potential code fix in a portion of the affected environment to verify that impact is successfully remediated. We're aiming to confirm a timeline for full deployment as it becomes available.
Scope of impact: Admins attempting to view device inventory and update status information in the Microsoft 365 Apps admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Next update by: Monday, August 24, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Sun Aug 23 22:57:22 2026 |
|---|
| Description: | Title: Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
User impact: Admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center.
More info: Device updates are continuing as expected, but the reported status and insights may not reflect the latest device state.
Current status: We're continuing to deploy the code fix to our internal testing environment to validate if it remediates impact as expected before deploying it to the affected environment.
Scope of impact: Admins attempting to view device inventory and update status information in the Microsoft 365 Apps admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Next update by: Monday, August 24, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Sun Aug 23 19:40:45 2026 |
|---|
| Description: | Title: Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
User impact: Admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center.
More info: Device updates are continuing as expected, but the reported status and insights may not reflect the latest device state.
Current status: We suspect that a recent service update may be contributing to impact. We've developed a potential fix which is preparing for internal validations. Once validations are complete we'll aim to provide a resolution timeline and more details of the underlying root cause.
Scope of impact: Admins attempting to view device inventory and update status information in the Microsoft 365 Apps admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Next update by: Monday, August 24, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Sun Aug 23 15:29:31 2026 |
|---|
| Description: | Title: Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
User impact: Admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center.
More info: Device updates are continuing as expected, but the reported status and insights may not reflect the latest device state.
Current status: Our service health telemetry was able to verify when admins began to see outdated device inventory and update status information. We're analyzing a subset of service update deployments that correlate with this start time of impact to help us determine our next steps in remediating the impact.
Scope of impact: Admins attempting to view device inventory and update status information in the Microsoft 365 Apps admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Next update by: Monday, August 24, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sun Aug 23 00:18:44 2026 |
|---|
| Description: | Title: Some admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center
User impact: Admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center.
More info: Device updates are continuing as expected, but the reported status and insights may not reflect the latest device state.
Current status: We’ve been alerted through our internal monitors and a subset of affected users to an issue in which admins may see outdated device inventory and update status information in the Microsoft 365 Apps admin center. We’re reviewing service health telemetry specific to when impact first occurred so that we can refine our understanding of how impact arose, which we anticipate will help ascertain our next troubleshooting actions.
Scope of impact: Admins attempting to view device inventory and update status information in the Microsoft 365 Apps admin center may be affected. This information may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 12:00 AM UTC
Next update by: Sunday, August 23, 2026, at 9:00 PM UTC
|
|---|
|
MV1461005 - Some users may be unable to access Microsoft Viva Glint services
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 24 14:16:48 2026 |
|---|
| End Time: | Mon Aug 24 16:34:47 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Glint |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Aug 24 16:41:43 2026 |
|---|
| Root Cause: | A recent build release contained a regression which caused the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 24 16:41:32 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Viva Glint services
User impact: Users may have been unable to access Viva Glint services.
More info: Affected users were able to sign in as expected but may have seen a blank page and weren't able to access any Viva Glint services.
Final status: We've completed rolling back the offending build and after monitoring service health metrics, confirmed the impact is remediated.
Scope of impact: Some users who attempted to access Microsoft Viva Glint services may have been impacted.
Start time: Monday, August 24, 2026, at 5:20 PM UTC
End time: Monday, August 24, 2026, at 7:47 PM UTC
Root cause: A recent build release contained a regression which caused the impact.
Next steps:
- We're reviewing our build update standards to ensure similar regressions are identified and corrected ahead of deployment to ensure this doesn't reoccur.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 24 15:34:54 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Viva Glint services
User impact: Users may be unable to access Viva Glint services.
More info: Affected users are able to sign in as expected but may see a blank page and won't be able to access any Viva Glint services.
Current status: We're monitoring as the release containing the regression is rolled back to ensure the issue is remediated and no further actions are necessary to fully resolve the impact.
Scope of impact: Some users attempting to access Microsoft Viva Glint services may be impacted. This section may be updated as our investigation continues.
Start time: Monday, August 24, 2026, at 5:20 PM UTC
Root cause: A recent build release contains a regression which is causing the impact.
Next update by: Monday, August 24, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 14:44:35 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Viva Glint services
User impact: Users may be unable to access Viva Glint services.
More info: Affected users are able to sign in as expected but may see a blank page and won't be able to access any Viva Glint services.
Current status: Our investigation determined that a recent build release contains a regression which is causing the impact. We're rolling this release back to remediate the issue.
Scope of impact: Some users attempting to access Microsoft Viva Glint services may be impacted. This section may be updated as our investigation continues.
Start time: Monday, August 24, 2026, at 5:20 PM UTC
Root cause: A recent build release contains a regression which is causing the impact.
Next update by: Monday, August 24, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 14:24:18 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Viva Glint services
User impact: Users may be unable to access Viva Glint services.
More info: Affected users are able to log in as expected but may see a blank page and won't be able to access any Viva Glint services.
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.
|
|---|
|
EX1442215 - Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 13 19:48:00 2026 |
|---|
| End Time: | Mon Aug 24 16:35:37 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 24 16:37:41 2026 |
|---|
| Root Cause: | A change introduced a code regression to Mailbox Replication Service (MRS) caused intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request were not being properly configured.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 24 16:37:40 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may have been unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we worked on developing a long-term solution, admins may have been able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin could have resumed the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Final status: We confirmed that the cross-tenant migration process has successfully completed for a subset of affected admins, validating that our configuration change has resolved the event.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may have been impacted.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
End time: Friday, August 14, 2026, at 5:24 PM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS) caused intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request were not being properly configured.
Next steps: - We're reviewing the responsible change to better understand what led to the configuration error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 24 16:37:30 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may have been unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we worked on developing a long-term solution, admins may have been able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin could have resumed the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Final status: We confirmed that the cross-tenant migration process has successfully completed for a subset of affected admins, validating that our configuration change has resolved the event.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may have been impacted.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
End time: Friday, August 14, 2026, at 5:24 PM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS) caused intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request were not being properly configured.
Next steps: - We're reviewing the responsible change to better understand what led to the configuration error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 13 15:04:43 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Current status: We're coordinating with a subset of affected admins who are in the process of completing a cross-tenant mailbox migration to monitor progress, which will help us validate remediation for all impacted admins.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Monday, August 24, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 12 10:47:06 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Current status: We're awaiting feedback from a subset of affected admins to validate if our fix successfully remediated impact.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Thursday, August 13, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 12 08:57:36 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Current status: We've validated and deployed the fix across the affected infrastructure, enabling the mailbox move to complete successfully. During validation, we've identified that the affected folder was processed as a folder creation bad item and therefore could not be migrated intact. We're validating the overall outcome with the affected users to confirm full mitigation.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Wednesday, August 12, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Aug 12 08:57:27 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Admins may be able to run the following PowerShell cmdlets sequentially for migration batches:
Set-MigrationBatch batchname -SkipMoving FolderRestrictions
Start-MigrationBatch "BatchName"
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online receive the following error
"PropTagToPropertyDefinitionConversionException"
Current status: We've validated and deployed the fix across the affected infrastructure, enabling the mailbox move to complete successfully. During validation, we identified that the affected folder was processed as a folder creation bad item and therefore could not be migrated intact. We're validating the overall outcome with the affected users and continuing to monitor the environment to ensure the mitigation remains effective.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be affected. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Wednesday, August 12, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 10:25:30 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Admins may be able to run the following PowerShell cmdlets sequentially for migration batches:
Set-MigrationBatch batchname -SkipMoving FolderRestrictions
Start-MigrationBatch "BatchName"
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online receive the following error
"PropTagToPropertyDefinitionConversionException"
Current status: We've received reports that impact associated with EX1232513 persists. We've resumed our investigation of the issue and have developed and are validating a fix to remediate impact.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be affected. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Wednesday, August 12, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 09:32:01 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and admins attempting to complete some cross-tenant mailbox migrations in Exchange Online are impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, July 29, 2026, at 3:30 PM UTC
|
|---|
|
MP1460870 - Admins may be unable to access Content Explorer or Data Explorer in Microsoft Purview
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 17:07:00 2026 |
|---|
| End Time: | Mon Aug 24 14:15:00 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 24 15:02:10 2026 |
|---|
| Root Cause: | A recent authentication configuration update resulted in increased restrictions on cross-resource token usage, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 24 15:00:25 2026 |
|---|
| Description: | Title: Admins may be unable to access Content Explorer or Data Explorer in Microsoft Purview
User impact: Admins may have been unable to access Content Explorer or Data Explorer in Microsoft Purview.
Final status: We've confirmed that a recent authentication configuration update resulted in increased restrictions on cross-resource token usage, resulting in impact. We've applied a configuration change to remediate impact and confirmed with a subset of affected users that the issue was successfully resolved.
Scope of impact: This issue may have affected any admin attempting to access Content Explorer or Data Explorer in Microsoft Purview.
Start time: Thursday, August 13, 2026, at 9:07 PM UTC
End time: Monday, August 24, 2026, at 6:15 PM UTC
Root cause: A recent authentication configuration update resulted in increased restrictions on cross-resource token usage, resulting in impact.
Next steps:
- We're reviewing our change testing and validation procedures to identify opportunities to improve impact detection and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 24 13:18:30 2026 |
|---|
| Description: | Title: Admins may be unable to access Content Explorer or Data Explorer in Microsoft Purview
User impact: Admins may be unable to access Content Explorer or Data Explorer in Microsoft Purview.
Current status: We're working to develop a configuration change to address the potential authentication issue to both confirm our theory as the cause of impact and mitigate the issue for affected admins.
Scope of impact: This issue may affect any admin attempting to access Content Explorer or Data Explorer in Microsoft Purview.
Next update by: Monday, August 24, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 12:01:39 2026 |
|---|
| Description: | Title: Admins may be unable to access Content Explorer or Data Explorer in Microsoft Purview
User impact: Admins may be unable to access Content Explorer or Data Explorer in Microsoft Purview.
Current status: We suspect a potential authentication issue may be occurring resulting in impact to admins. We're investigating service health telemetry in parallel with Microsoft Purview logs to confirm this theory and determine our next troubleshooting steps.
Scope of impact: This issue may affect any admin attempting to access Content Explorer or Data Explorer in Microsoft Purview.
Next update by: Monday, August 24, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 24 11:29:56 2026 |
|---|
| Description: | Title: Admins may be unable to access Content Explorer or Data Explorer in Microsoft Purview
User impact: Admins may be unable to access Content Explorer or Data Explorer in Microsoft Purview.
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.
|
|---|
|
TM1460590 - Some users may experience degraded video quality when screensharing in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 01:56:00 2026 |
|---|
| End Time: | Mon Aug 24 10:48:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Aug 24 14:51:43 2026 |
|---|
| Root Cause: | A recent update related to meeting performance optimization was causing impact to some users.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 24 13:27:25 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screensharing in Microsoft Teams
User impact: Users may have experienced degraded video quality when screensharing in Microsoft Teams.
Final status: We've confirmed with a subset of affected users that our deployed fix has successfully resolved impact.
Scope of impact: Impact was specific to some users attempting to screenshare in Microsoft Teams.
Start time: Tuesday, August 18, 2026, at 5:56 AM UTC
End time: Monday, August 24, 2026, at 2:48 PM UTC
Root cause: A recent update related to meeting performance optimization was causing impact to some users.
Next steps:
- We're reviewing our update testing and validation procedures to identify opportunities to improve impact detection and prevent similar future issues.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 24 11:41:58 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screensharing in Microsoft Teams
User impact: Users may experience degraded video quality when screensharing in Microsoft Teams.
Current status: We've completed the deployment of our configuration update and are validating with a subset of affected users that impact was successfully remediated.
Scope of impact: Impact is specific to some users attempting to screenshare in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Tuesday, August 18, 2026, at 5:56 AM UTC
Root cause: A recent update related to meeting performance optimization is causing impact to some users.
Next update by: Monday, August 24, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 10:00:11 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screensharing in Microsoft Teams
User impact: Users may experience degraded video quality when screensharing in Microsoft Teams.
Current status: We're continuing to deploy the configuration update to remediate impact and are monitoring telemetry as the change progresses through the service.
Scope of impact: Impact is specific to some users attempting to screenshare in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Tuesday, August 18, 2026, at 5:56 AM UTC
Root cause: A recent update related to meeting performance optimization is causing impact to some users.
Next update by: Monday, August 24, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 05:02:40 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screensharing in Microsoft Teams
User impact: Users may experience degraded video quality when screensharing in Microsoft Teams.
Current status: We've determined that a recent update related to meeting performance optimization is causing impact to some users. We're deploying a configuration update to remediate impact and are monitoring telemetry as the change progresses through the service.
Scope of impact: Impact is specific to some users attempting to screenshare in Microsoft Teams. This information may be updated as our investigation continues.
Start time: Tuesday, August 18, 2026, at 5:56 AM UTC
Root cause: A recent update related to meeting performance optimization is causing impact to some users.
Next update by: Monday, August 24, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Aug 24 03:59:40 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screensharing in Microsoft Teams
User impact: Users may experience degraded video quality when screensharing in Microsoft Teams.
Current status: We're continuing our review and analysis of service logs provided by some affected users, alongside service monitoring telemetry to isolate the root cause and determine our next steps.
Scope of impact: Impact is specific to some users attempting to screenshare in Microsoft Teams. This information may be updated as our investigation continues.
Next update by: Monday, August 24, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Aug 24 02:03:15 2026 |
|---|
| Description: | Title: Some users experience degraded video quality when screensharing in Microsoft Teams
User impact: Users experience degraded video quality when screensharing in Microsoft Teams.
Current status: We're continuing our review and analysis of the service logs provided by affected users to gain insight into the impacted scenario and determine our next steps.
Scope of impact: Your organization is affected by this event, and users attempting to screenshare in Microsoft Teams are impacted. This information may be updated as our investigation continues.
Next update by: Monday, August 24, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Mon Aug 24 01:30:47 2026 |
|---|
| Description: | Title: Some users experience degraded video quality when screensharing in Microsoft Teams
User impact: Users experience degraded video quality when screensharing in Microsoft Teams.
Current status: We've received user reports indicating some users are experiencing degraded video quality when screensharing in Microsoft Teams. We're reviewing service logs and contextual details provided by your representatives to gain insight into the affected scenario and determine our next investigative steps.
Scope of impact: Your organization is affected by this event, and users attempting to screenshare in Microsoft Teams are impacted. This information may be updated as our investigation continues.
Next update by: Monday, August 24, 2026, at 7:00 AM UTC
|
|---|
|
CP1458413 - Some users may experience inconsistencies with Microsoft 365 Copilot features
| Status: | serviceRestored |
|---|
| Start Time: | Fri Aug 21 02:30:00 2026 |
|---|
| End Time: | Mon Aug 24 12:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 24 12:45:08 2026 |
|---|
| Root Cause: | A planned update deployment process may have caused inconsistent Copilot feature experiences for a subset of users.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 24 12:43:35 2026 |
|---|
| Description: | Title: Some users may experience inconsistencies with Microsoft 365 Copilot features
User impact: Users may experience inconsistencies across Copilot features including chat, agent availability, and Microsoft 365 apps.
More info: Our planned update communicated through MC1405498 may have resulted in Copilot feature issues for a subset of users with disabled “Microsoft Copilot with Graph-grounded chat” service plan as they transitioned from the Premium to Basic grounding experiences. While this may have been intentional for some users based on the plans that admins assigned to users, admins could have enabled the “Microsoft Copilot with Graph-grounded chat” service plan for any user that should have retained a Copilot Premium grounding experience.
Final status: The deployment and propagation window are complete. Users with disabled “Microsoft Copilot with Graph-grounded chat” service plans should now see the Basic license label. They also may need to clear cache or refresh their Copilot client or browser session to help accelerate entitlement convergence for their experience if they encounter any residual errors.
Scope of impact: Users with a disabled “Copilot with Graph-grounded chat” service plan may have experienced inconsistencies with Copilot features, including chat, agent availability, and integrations with Microsoft 365 service and apps.
Start time: Friday, August 21, 2026, at 6:30 AM UTC
End time: Monday, August 24, 2026, at 4:00 PM UTC
Root cause: A planned update deployment process may have caused inconsistent Copilot feature experiences for a subset of users.
Next steps:
- We're reviewing our deployment processes to determine how we can avoid inconsistent Copilot experiences such as this during deployment and propagation periods.
|
|---|
|
| Time: | Sun Aug 23 11:05:43 2026 |
|---|
| Description: | Title: Some users may experience inconsistencies with Microsoft 365 Copilot features
User impact: Users may experience inconsistencies across Copilot features including chat, agent availability, and Microsoft 365 apps.
More info: Our planned update communicated through MC1405498 may result in Copilot feature issues for a subset of users with disabled “Microsoft Copilot with Graph-grounded chat” service plan as they will transition from the Premium to Basic grounding experiences. While this may be intentional for some users based on the plans that admins assigned to users, admins can enable the “Microsoft Copilot with Graph-grounded chat” service plan for any user that should retain a Copilot Premium grounding experience.
Current status: The propagation window is in its final stages, and entitlement convergence is expected to complete soon. During this period, which we anticipate will complete by Monday, August 24, 2026, users with disabled “Microsoft Copilot with Graph-grounded chat” service plan may see the described impact.
Scope of impact: Users with a disabled “Copilot with Graph-grounded chat” service plan may experience inconsistencies with Copilot features, including chat, agent availability, and integrations with Microsoft 365 service and apps.
Start time: Friday, August 21, 2026, at 6:30 AM UTC
Root cause: A planned update deployment process may be causing inconsistent Copilot feature experiences for a subset of users.
Next update by: Monday, August 24, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat Aug 22 11:25:40 2026 |
|---|
| Description: | Title: Some users may experience inconsistencies with Microsoft 365 Copilot features
User impact: Users may experience inconsistencies across Copilot features including chat, agent availability, and Microsoft 365 apps.
More info: Our planned update communicated through MC1405498 may result in Copilot feature issues for a subset of users with disabled “Microsoft Copilot with Graph-grounded chat” service plan as they will transition from the Premium to Basic grounding experiences. While this may be intentional for some users based on the plans that admins assigned to users, admins can enable the “Microsoft Copilot with Graph-grounded chat” service plan for any user that should retain a Copilot Premium grounding experience.
Current status: The changes are continuing to propagate as expected and will continue to impact fewer users as user entitlements converge. During this period, which we anticipate will complete by Monday, August 24, 2026, users with disabled “Microsoft Copilot with Graph-grounded chat” service plan may see the described impact.
Scope of impact: Users with a disabled “Copilot with Graph-grounded chat” service plan may experience inconsistencies with Copilot features, including chat, agent availability, and integrations with Microsoft 365 service and apps.
Start time: Friday, August 21, 2026, at 6:30 AM UTC
Root cause: A planned update deployment process may be causing inconsistent Copilot feature experiences for a subset of users.
Next update by: Sunday, August 23, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Aug 21 16:32:33 2026 |
|---|
| Description: | Title: Some users may experience inconsistencies with Microsoft 365 Copilot features
User impact: Users may experience inconsistencies across Copilot features including chat, agent availability, and Microsoft 365 apps.
More info: Our planned update communicated through MC1405498 may result in Copilot feature issues for a subset of users with disabled “Microsoft Copilot with Graph-grounded chat” service plan as they will transition from the Premium to Basic grounding experiences. While this may be intentional for some users based on the plans that admins assigned to users, admins can enable the “Microsoft Copilot with Graph-grounded chat” service plan for any user that should retain a Copilot Premium grounding experience.
Current status: We’ve completed our deployment and the changes are propagating as expected. During this period, which we anticipate will complete by Monday, August 24, 2026, users with disabled “Microsoft Copilot with Graph-grounded chat” service plan may see the described impact. This will impact fewer users as the propagation process continues.
Scope of impact: Users with a disabled “Copilot with Graph-grounded chat” service plan may experience inconsistencies with Copilot features, including chat, agent availability, and integrations with Microsoft 365 service and apps.
Start time: Friday, August 21, 2026, at 6:30 AM UTC
Root cause: A planned update deployment process may be causing inconsistent Copilot feature experiences for a subset of users.
Next update by: Saturday, August 22, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Aug 20 18:01:10 2026 |
|---|
| Description: | Title: Some users may experience inconsistencies with Microsoft 365 Copilot features
User impact: Users may experience inconsistencies across Copilot features including chat, agent availability, and Microsoft 365 apps.
Current status: We’ve determined that our planned update communicated through MC1405498 may result in Copilot feature issues for a subset of users with disabled “Microsoft Copilot with Graph-grounded chat” service plan as they will transition from the Premium to Basic grounding experiences. While this may be intentional for some users based on the plans that admins assigned to users, admins can enable the “Microsoft Copilot with Graph-grounded chat” service plan for any user that should retain a Copilot Premium grounding experience.
During the update maintenance period, users with a disabled “Copilot with Graph-grounded chat” service plan may see inconsistent experiences such as with chat, agent availability, and integrated Microsoft 365 features. Once the update is completed, which we expect will occur by Monday, August 24, 2026, users should return to a consistent experience appropriate for their configured plan. We’ll continue to provide updates on the progress of the planned action as it deploys.
Scope of impact: Users with a disabled “Copilot with Graph-grounded chat” service plan may experience inconsistencies with Copilot features, including chat, agent availability, and integrations with Microsoft 365 service and apps.
Root cause: A planned update deployment process may be causing inconsistent Copilot feature experiences for a subset of users.
Next update by: Friday, August 21, 2026, at 10:00 PM UTC
|
|---|
|
TM1457081 - Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client and VDI
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 04:21:00 2026 |
|---|
| End Time: | Fri Aug 21 11:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Aug 21 15:35:33 2026 |
|---|
| Root Cause: | A recent configuration change to the video processing pipeline contains an error, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 21 12:51:56 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client and VDI
User impact: Users may have experienced degraded video quality when screen sharing using the Microsoft Teams web client and VDI.
More info: Impact was specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client. This may also have impacted users attempting to screenshare through VDI.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Final status: We've confirmed that the fix has completed its deployment and validated that this issue has been remediated using service telemetry.
Scope of impact: Impact was limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client and VDI.
End time: Friday, August 21, 2026, at 3:00 PM UTC
Root cause: A recent configuration change to the video processing pipeline contains an error, which resulted in impact.
Next steps:
- We're continuing our analysis of the impacting configuration change to better identify and prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 20 13:14:52 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client and VDI
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client and VDI.
More info: Impact is specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client. This may also impact users attempting to screenshare through VDI.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Current status: We've deployed our fix to 10 percent of the affected environment. We're monitoring service health telemetry for a period to ensure no regressions occur, after which we'll proceed with deploying to the remaining affected environment.
Scope of impact: Impact is limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client and VDI. This information may be updated as our investigation continues.
Start time: Thursday, August 13, 2026, at 8:21 AM UTC
Root cause: A recent configuration change to the video processing pipeline contains an error, which is resulting in impact.
Next update by: Friday, August 21, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Aug 20 05:00:39 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client and VDI
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client and VDI.
More info: Impact is specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client. This may also impact users attempting to screenshare through VDI.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Current status: We've confirmed with a subset of affected users that the issue has been mitigated following the deployment of the fix. The fix is now being deployed across the remaining environments and we expect to provide a confirmed completion timeline in our next scheduled update.
Scope of impact: Impact is limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client and VDI. This information may be updated as our investigation continues.
Root cause: A recent configuration change to the video processing pipeline contains an error, which is resulting in impact.
Next update by: Thursday, August 20, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Aug 20 00:37:08 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client.
More info: Impact is specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Current status: We're working with your representatives to ensure that affected users have received the fix and that impact is fully resolved.
Scope of impact: Impact is limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client. This information may be updated as our investigation continues.
Root cause: A recent configuration change to the video processing pipeline contains an error, which is resulting in impact.
Next update by: Thursday, August 20, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Wed Aug 19 10:00:12 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client.
More info: Impact is specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Current status: We're reaching out to affected users to confirm that the fix has been effective and that the issue has been mitigated.
Scope of impact: Impact is limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client. This information may be updated as our investigation continues.
Root cause: A recent configuration change to the video processing pipeline contains an error, which is resulting in impact.
Next update by: Thursday, August 20, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Wed Aug 19 07:59:52 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client.
More info: Impact is specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Current status: We've validated that reverting the previously identified change did not resolve the issue. As a result, we've deployed an additional configuration update for the web client which has completed deployment. Once the fix is fully propagated, we'll confirm with affected users whether the update has successfully mitigated the impact.
Scope of impact: Impact is limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client. This information may be updated as our investigation continues.
Root cause: A recent configuration change to the video processing pipeline contains an error, which is resulting in impact.
Next update by: Wednesday, August 19, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Aug 18 12:57:26 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client.
More info: Impact is specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Current status: Our investigation has identified a recent configuration change to the video processing pipeline contains an error, resulting in impact. We've reverted this change and are working to validate this issue is no longer occurring.
Scope of impact: Impact is limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client. This information may be updated as our investigation continues.
Next update by: Wednesday, August 19, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Aug 18 11:59:48 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client.
More info: Impact is specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Current status: We're analyzing service telemetry to better understand the impact scenario and determine our next diagnostic steps.
Scope of impact: Impact is limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client. This information may be updated as our investigation continues.
Next update by: Tuesday, August 18, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Aug 18 11:36:11 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1452826 - Some users may see outdated activity data in Microsoft Teams usage reports
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 22 20:00:00 2026 |
|---|
| End Time: | Fri Aug 21 11:23:46 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Aug 21 11:38:14 2026 |
|---|
| Root Cause: | An upstream data source unexpectedly encountered delays, which resulted in multiple usage reports being outdated.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 21 11:38:10 2026 |
|---|
| Description: | Title: Some users may see outdated activity data in Microsoft Teams usage reports
User impact: Users have may seen outdated activity data in Microsoft Teams usage reports.
Final status: We've confirmed after monitoring the backfill process that the Teams activity data is now up-to-date and the impact has been remediated.
Scope of impact: This issue may have intermittently impacted some users who attempted to view activity data in Microsoft Teams usage reports.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
End time: Friday, August 21, 2026, at 3:00 PM UTC
Root cause: An upstream data source unexpectedly encountered delays, which resulted in multiple usage reports being outdated.
Next steps:
- We're continuing our analysis of the upstream data source to understand what caused the delays so we can improve our service's resiliency to prevent similar issues from arising in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 20 16:19:28 2026 |
|---|
| Description: | Title: Some users may see outdated activity data in Microsoft Teams usage reports
User impact: Users may see outdated activity data in Microsoft Teams usage reports.
Current status: Based on the progression of the backfill, we estimate additional time will be needed to complete it. We're continuing to monitor as it progresses to validate a finalized timeline to remediation.
Scope of impact: This issue may intermittently impact some users attempting to view activity data in Microsoft Teams usage reports. This information may be updated as our investigation continues.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
Root cause: An upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated.
Next update by: Friday, August 21, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Aug 20 11:31:01 2026 |
|---|
| Description: | Title: Some users may see outdated activity data in Microsoft Teams usage reports
User impact: Users may see outdated activity data in Microsoft Teams usage reports.
Current status: We've validated that the backfill of delayed activity data for Microsoft Teams usage reports has completed through Thursday, August 13, 2026. We’re monitoring as the backfill progresses to validate a finalized timeline to remediation.
Scope of impact: This issue may intermittently impact some users attempting to view activity data in Microsoft Teams usage reports. This information may be updated as our investigation continues.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
Root cause: An upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated.
Next update by: Friday, August 21, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Aug 19 12:07:29 2026 |
|---|
| Description: | Title: Some users may see outdated activity data in Microsoft Teams usage reports
User impact: Users may see outdated activity data in Microsoft Teams usage reports.
Current status: We’re continuing to monitor the backfill of delayed activity data for Microsoft Teams usage reports, which has completed through Wednesday, August 12, 2026. We expect the remaining backfill to be completed by our next scheduled update.
Scope of impact: This issue may intermittently impact some users attempting to view activity data in Microsoft Teams usage reports. This information may be updated as our investigation continues.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
Root cause: An upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated.
Next update by: Thursday, August 20, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Aug 18 12:03:18 2026 |
|---|
| Description: | Title: Some users may see outdated activity data in Microsoft Teams usage reports
User impact: Users may see outdated activity data in Microsoft Teams usage reports.
Current status: We've remediated an additional impacted data source and are proceeding with completing a backfill of delayed activity data for Microsoft Teams usage reports. We aim to provide a timeline for the backfill to complete in our next scheduled update.
Scope of impact: This issue may intermittently impact some users attempting to view activity data in Microsoft Teams usage reports. This information may be updated as our investigation continues.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
Root cause: An upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated.
Next update by: Wednesday, August 19, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 17 11:55:58 2026 |
|---|
| Description: | Title: Some users may see outdated activity data in Microsoft Teams usage reports
User impact: Users may see outdated activity data in Microsoft Teams usage reports.
Current status: Our fix has completed its deployment, and data has been backfilled up to August 9. However, we've identified an additional impacted data source which needs to be remediated in order to complete the backfill. We're applying a fix to this data source to correct the issue and will continue to monitor as backlogged data is processed to ensure impact remediation.
Scope of impact: This issue may intermittently impact some users attempting to view activity data in Microsoft Teams usage reports. This information may be updated as our investigation continues.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
Root cause: An upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated.
Next update by: Tuesday, August 18, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Aug 14 16:46:55 2026 |
|---|
| Description: | Title: Some users may see outdated activity data in Microsoft Teams usage reports
User impact: Users may see outdated activity data in Microsoft Teams usage reports.
Current status: We identified that an additional fix was needed to restore the upstream data source. We initiated the deployment of the fix and expect it to complete by August 17, 2026. Once the upstream data source is restored, we'll monitor the backfill of activity data to ensure it becomes up to date and that the impact is remediated.
Scope of impact: This issue may intermittently impact some users attempting to view activity data in Microsoft Teams usage reports. This information may be updated as our investigation continues.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
Root cause: An upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated.
Next update by: Monday, August 17, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 15:51:15 2026 |
|---|
| Description: | Title: Some users see outdated activity data in Microsoft Teams usage reports
User impact: Users see outdated activity data in Microsoft Teams usage reports.
Current status: While monitoring the progress of the backlog processing, we've identified another source of impact that is contributing to the reporting delay. We're analyzing this source to identify our most effective next steps. We anticipate that we'll be able to provide an updated timeline by our next scheduled reconvene.
Scope of impact: This issue may intermittently impact some users attempting to view activity data in Microsoft Teams usage reports. This information may be updated as our investigation continues.
Root cause: An upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated.
Next update by: Friday, August 14, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Aug 12 18:07:56 2026 |
|---|
| Description: | Title: Some users see outdated activity data in Microsoft Teams usage reports
User impact: Users see outdated activity data in Microsoft Teams usage reports.
Current status: We're continuing to monitor the service as the backlog of accumulated data is processed. We anticipate activity data will be fully up to date in Microsoft Teams usage reports by our next scheduled communications update.
Scope of impact: This issue may intermittently impact some users attempting to view activity data in Microsoft Teams usage reports. This information may be updated as our investigation continues.
Root cause: An upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated.
Next update by: Thursday, August 13, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 10:02:50 2026 |
|---|
| Description: | Title: Some users may see outdated activity data in Microsoft Teams usage reports
User impact: Users may see outdated activity data in Microsoft Teams usage reports.
Current status: We've identified an upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated. We're repairing the upstream data source pipeline to address the upstream latency issue and can see that the report data is repopulating. We expect the processing of the data will take some time to backfill and we'll continue to monitor the progress to ensure all data becomes up to date.
Scope of impact: This issue may intermittently impact some users attempting to view activity data in Microsoft Teams usage reports. This information may be updated as our investigation continues.
Root cause: An upstream data source has unexpectedly encountered delays, which is resulting in multiple usage reports being outdated.
Next update by: Wednesday, August 12, 2026, at 10:00 PM UTC
|
|---|
|
MO1456424 - Some users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 17 08:46:14 2026 |
|---|
| End Time: | Thu Aug 20 23:38:16 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 20 23:46:17 2026 |
|---|
| Root Cause: | A recent deployment introduced a resource utilization inefficiency issue and affected the search functionality in SharePoint Online, OneDrive, Outlook on the web, and the Outlook desktop client.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 20 23:46:13 2026 |
|---|
| Description: | Title: Some users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop
User impact: Users may have been unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Final status: We've completed deploying the fix to reduce the resource pressure, and we've validated by monitoring internal telemetry that the issue is resolved.
Scope of impact: Impact was specific to some users served through the affected infrastructure who were attempting to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Start time: Friday, August 14, 2026, at 5:00 AM UTC
End time: Tuesday, August 18, 2026, at 12:00 AM UTC
Root cause: A recent deployment introduced a resource utilization inefficiency issue and affected the search functionality in SharePoint Online, OneDrive, Outlook on the web, and the Outlook desktop client.
Next steps:
- We're further reviewing the recent deployment to understand how the resource utilization inefficiency issue was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future deployments.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 17 23:41:11 2026 |
|---|
| Description: | Title: Some users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop
User impact: Users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Current status: Our investigation identified that a recent deployment introduced a resource utilization inefficiency issue, leading to impact. We've developed and are deploying a fix to reduce the resource pressure and restore service. We're monitoring as this progresses to identify a completion timeline.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop. This section may be updated as our investigation continues.
Start time: Friday, August 14, 2026, at 5:00 AM UTC
Root cause: A recent deployment introduced a resource utilization inefficiency issue, leading to impact.
Next update by: Friday, August 21, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Aug 17 10:15:32 2026 |
|---|
| Description: | Title: Some users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop
User impact: Users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Current status: We're analyzing service telemetry and reviewing recent service changes to determine the cause of impact. We've identified indicators of increased service restarts within a portion of the affected infrastructure, which may be contributing to the issue. We're validating potential remediation options while continuing our investigation into the root cause.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Next update by: Tuesday, August 18, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Aug 17 08:49:09 2026 |
|---|
| Description: | Title: Some users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop
User impact: Users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Current status: We're reviewing service monitoring telemetry and support provided information to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Next update by: Monday, August 17, 2026, at 3:00 PM UTC
|
|---|
|
TM1458179 - Some users may encounter errors making changes to teams, channels or calendars in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 20 09:00:00 2026 |
|---|
| End Time: | Thu Aug 20 12:10:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 20 14:01:02 2026 |
|---|
| Root Cause: | A recent feature update caused a portion of the Microsoft Teams service infrastructure to operate in a suboptimal state, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 20 13:51:48 2026 |
|---|
| Description: | Title: Some users may encounter errors making changes to teams, channels or calendars in Microsoft Teams
User impact: Users may have encountered errors making changes to teams, channels or calendars in Microsoft Teams.
Final status: We've reverted the offending feature update and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Some users attempting to make changes to teams, channels, or calendars in Microsoft Teams may have been impacted.
Start time: Thursday, August 20, 2026, at 1:00 PM UTC
End time: Saturday, June 20, 2026, at 4:10 PM UTC
Root cause: A recent feature update caused a portion of the Microsoft Teams service infrastructure to operate in a suboptimal state, resulting in impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to teams, channels and calendar functionality 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 Aug 20 12:25:28 2026 |
|---|
| Description: | Title: Some users may encounter errors making changes to teams, channels or calendars in Microsoft Teams
User impact: Users may encounter errors making changes to teams, channels or calendars in Microsoft Teams.
Current status: We suspect that a recent feature update is causing a portion of the Microsoft Teams service infrastructure to operate in a suboptimal state and fail to process requests as expected. We're validating our root cause hypothesis while we assess if reverting the identified feature update is a valid remediation plan.
Scope of impact: Some users attempting to make changes to teams, channels, or calendars in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Start time: Thursday, August 20, 2026, at 1:00 PM UTC
Next update by: Thursday, August 20, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Aug 20 10:17:16 2026 |
|---|
| Description: | Title: Some users may encounter errors making changes to teams or channels in Microsoft Teams
User impact: Users may encounter errors making changes to teams or channels in Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users in the United States attempting to make changes to teams or channels.
Next update by: Thursday, August 20, 2026, at 4:30 PM UTC
|
|---|
|
OP1457784 - Admins may not see data in multiple tabs within the Microsoft 365 apps admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 19 13:00:00 2026 |
|---|
| End Time: | Wed Aug 19 16:13:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 19 17:38:30 2026 |
|---|
| Root Cause: | A recent deployment to optimize Microsoft 365 apps service infrastructure incorrectly removed the Inventory apps and Shared Apps, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 19 17:38:12 2026 |
|---|
| Description: | Title: Admins may not see data in multiple tabs within the Microsoft 365 apps admin center
User impact: Admins may not have seen data in multiple tabs within the Microsoft 365 apps admin center.
More info: Admins may not have seen data in the following locations in the Microsoft 365 apps admin center:
- Home page
- Cloud update
- Inventory
- Security Update Status
Admins may have received an error message stating, “There was a problem retrieving data for this page. Please refresh the page or try again later.”
Final status: After further monitoring of service telemetry, we've validated that our deployment to reinstate the removed Inventory apps and Shared Apps successfully remediated impact.
Scope of impact: Some admins may not have seen data in the Home page, Cloud update, Inventory, or Security update status sections in the Microsoft 365 apps admin center.
Start time: Wednesday, August 19, 2026, at 5:00 PM UTC
End time: Wednesday, August 19, 2026, at 8:13 PM UTC
Root cause: A recent deployment to optimize Microsoft 365 apps service infrastructure incorrectly removed the Inventory apps and Shared Apps, resulting in impact.
Next steps:
- We're analyzing the offending deployment to isolate why the potential for impact wasn't caught prior to implementation. This further analysis will help us to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Aug 19 17:01:49 2026 |
|---|
| Description: | Title: Admins may not see data in multiple tabs within the Microsoft 365 apps admin center
User impact: Admins may not see data in multiple tabs within the Microsoft 365 apps admin center.
More info: Admins may not see data in the following locations in the Microsoft 365 apps admin center:
- Home page
- Cloud update
- Inventory
- Security Update Status
Admins may receive an error message stating, “There was a problem retrieving data for this page. Please refresh the page or try again later.”
Current status: After further analysis, we've isolated that impact was caused by a recent deployment to optimize Microsoft 365 apps service infrastructure that incorrectly removed the Inventory apps and Shared Apps, resulting in impact. We've added the missing applications back to affected service infrastructure and are monitoring telemetry for remediation.
Scope of impact: Some admins may not see data in the Home page, Cloud update, Inventory, or Security update status sections in the Microsoft 365 apps admin center. This section may be updated as the investigation progresses.
Start time: Wednesday, August 19, 2026, at 5:00 PM UTC
Root cause: A recent deployment to optimize Microsoft 365 apps service infrastructure incorrectly removed the Inventory apps and Shared Apps, resulting in impact.
Next update by: Wednesday, August 19, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Aug 19 16:37:27 2026 |
|---|
| Description: | Title: Admins may not see data in multiple tabs within the Microsoft 365 apps admin center
User impact: Admins may not see data in multiple tabs within the Microsoft 365 apps admin center.
More info: Admins may not see data in the following locations in the Microsoft 365 apps admin center:
- Home page
- Cloud update
- Inventory
- Security Update Status
Admins may receive an error message stating, “There was a problem retrieving data for this page. Please refresh the page or try again later.”
Current status: Our service monitors have alerted us to ongoing impact to a subset of admins who may not see data in the tabs outlined in the "More info" section of this communication within the Microsoft 365 apps admin center. We're reviewing reports of impact to further our understanding of the current impact scenario and to determine our next troubleshooting steps.
Scope of impact: Some admins may not see data in the Home page, Cloud update, Inventory, or Security update status sections in the Microsoft 365 apps admin center. This section may be updated as the investigation progresses.
Next update by: Wednesday, August 19, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Aug 19 16:17:41 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 apps
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft 365 apps and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1456599 - Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 17 09:00:00 2026 |
|---|
| End Time: | Tue Aug 18 11:58:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 18 12:15:17 2026 |
|---|
| Root Cause: | A recent service update introduced a configuration issue in a service component used by the Microsoft Intune Company Portal. Under high traffic conditions, this misconfiguration reduced the effectiveness of the service's caching behavior, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 18 12:14:21 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may have been unable to load apps in the Microsoft Intune Company Portal and received an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client were returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Final status: We've completed the deployment of our fix to correct the misconfiguration and confirmed through service telemetry and user reports that impact was successfully resolved for users.
Scope of impact: Some users attempting to load apps in the Microsoft Intune Company Portal app or web client may have been impacted.
Start time: Monday, August 17, 2026, at 1:00 PM UTC
End time: Tuesday, August 18, 2026, at 3:58 PM UTC
Root cause: A recent service update introduced a configuration issue in a service component used by the Microsoft Intune Company Portal. Under high traffic conditions, this misconfiguration reduced the effectiveness of the service's caching behavior, resulting in impact.
Next steps:
- We're reviewing our service update testing and validation procedures to identify opportunities to improve impact detection and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 18 10:20:01 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We’ve determined that a recent service update introduced a configuration issue in a service component used by the Microsoft Intune Company Portal. Under high traffic conditions, this misconfiguration reduced the effectiveness of the service's caching behavior, resulting in impact. We’re deploying a fix to correct the misconfiguration and are monitoring service telemetry to confirm recovery as the deployment progresses across the affected environments. We've received confirmation that some previously affected users have recovered, while users in environments where deployment of the fix is still in progress may continue to experience impact until deployment is completed.
Scope of impact: Some users attempting to load apps in the Microsoft Intune Company Portal app or web client may be impacted.
Start time: Monday, August 17, 2026, at 1:00 PM UTC
Root cause: A recent service update introduced a configuration issue in a service component used by the Microsoft Intune Company Portal. Under high traffic conditions, this misconfiguration reduced the effectiveness of the service's caching behavior, resulting in impact.
Next update by: Tuesday, August 18, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon Aug 17 21:08:03 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: Based on our telemetry, we can see that the amount of errors has decreased and we expect that most affected users are seeing remediation. We'll continue monitoring to ensure the impact doesn't reoccur. In the meantime, we're continuing our evaluation of recent traffic patterns and potential caching issues to identify the source of the issue which will help us in developing any additional fixes needed.
Scope of impact: Some users may be unable to load apps in the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Tuesday, August 18, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 17 16:14:11 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We're analyzing traffic patterns over the past 24 hours and evaluating potential performance optimizations to assist with remediating impact while we continue to investigate and isolate the underlying root cause.
Scope of impact: Some users may be unable to load apps in the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Tuesday, August 18, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Aug 17 14:38:56 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: After further review, we've validated that users are unable to load apps in the Microsoft Intune Company Portal app and are able to load the Intune Company Portal app. We've updated the "Title", "User impact", "More info", and "Scope of impact" fields to reflect this change. We're continuing to review recent service updates and analyze affected Microsoft Intune service infrastructure to isolate potential sources of impact and to determine our next troubleshooting steps.
Scope of impact: Some users may be unable to load apps in the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Monday, August 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Aug 17 14:05:34 2026 |
|---|
| Description: | Title: Some users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message
User impact: Users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message.
More info: Users attempting to load the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We're reviewing recent deployments to affected Intune service infrastructure to isolate potential sources of impact and to determine our next troubleshooting steps.
Scope of impact: Some users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Monday, August 17, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Aug 17 13:17:01 2026 |
|---|
| Description: | Title: Some users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message
User impact: Users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message.
More info: Users attempting to load the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We've received reports from a subset of affected users who have stated that they are unable to load the Microsoft Intune Company Portal app or web client and receive an error message. We're reviewing reports of impact and analyzing the Intune service infrastructure hosting affected users to determine our next troubleshooting steps.
Scope of impact: Some users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Monday, August 17, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Aug 17 12:57:19 2026 |
|---|
| Description: | Title: Users can't load the Microsoft Intune Company Portal app and receive an error message
User impact: Users can't load the Microsoft Intune Company Portal app and receive an error message.
More info: Users attempting to load the Microsoft Intune Company Portal app are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1456911 - Users may have been unable to access Microsoft 365 Copilot in Excel
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 17 15:30:00 2026 |
|---|
| End Time: | Tue Aug 18 02:30:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Aug 18 08:14:39 2026 |
|---|
| Root Cause: | A recent change intended to update a supporting web component caused the Copilot pane to fail to load. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 18 03:02:19 2026 |
|---|
| Description: | Title: Users may have been unable to access Microsoft 365 Copilot in Excel
User impact: Users may have been unable to access Copilot in Excel.
More info: The Copilot pane may not have loaded when users selected the Copilot button. Users may have been able to access Copilot through the Excel desktop application.
Final status: We’ve determined that a recent change intended to update a supporting web component caused the Copilot pane to fail to load. We reverted the change to remediate the impact and confirmed in our testing environment that the issue is resolved.
Scope of impact: Impact was specific to users who may have been attempting to access Copilot in Excel through the web application.
Start time: Monday, August 17, 2026, at 7:30 PM UTC
End time: Tuesday, August 18, 2026, at 6:30 AM UTC
Root cause: A recent change intended to update a supporting web component caused the Copilot pane to fail to load.
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: | Tue Aug 18 01:55:29 2026 |
|---|
| Description: | Title: Users can’t access Microsoft Copilot in Excel
User impact: Users can’t access Copilot in Excel.
More info: The Copilot pane may not load when users select the Copilot button. Users may be able to access Copilot through the Excel desktop application.
This issue affects Copilot in both Excel on the desktop and the web versions.
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 any user can’t access Copilot in Excel on the desktop and on the web. This information may be updated as our investigation continues.
Next update by: Tuesday, August 18, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Aug 18 01:31:12 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.
|
|---|
|
DZ1449728 - Users may have experienced increased latency when accessing applications protected by Conditional Access App Control
| Status: | serviceRestored |
|---|
| Start Time: | Fri Aug 7 07:47:00 2026 |
|---|
| End Time: | Fri Aug 7 10:09:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 18 05:03:32 2026 |
|---|
| Root Cause: | A downstream database update responsible for supporting Inline Access functionality introduced an issue that prevented service components from reliably retrieving the data required to process requests, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 7 10:33:37 2026 |
|---|
| Description: | Title: Users may have experienced increased latency when accessing applications protected by Conditional Access App Control
User impact: Users may have experienced increased latency when accessing applications protected by Conditional Access App Control.
More info: Affected users may have encountered intermittent 5XX errors during sign-in attempts when using apps managed by Microsoft Defender XDR. In some cases, retrying the operation may have been successful.
Final status: We've completed our reversion of the affected service change and confirmed through service monitoring that the impact has been remediated.
Scope of impact: Impact was specific to any user attempting to sign in to applications protected by Conditional Access App Control policies.
Start time: Friday, August 7, 2026, at 11:47 AM UTC
End time: Friday, August 7, 2026, at 2:09 PM UTC
Root cause: A downstream database update responsible for supporting Inline Access functionality introduced an issue that prevented service components from reliably retrieving the data required to process requests, resulting in impact.
Next steps:
- We’re reviewing our database update procedures to help prevent the issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Fri Aug 7 09:47:29 2026 |
|---|
| Description: | Title: Users may experience increased latency when accessing applications protected by Conditional Access App Control policies
User impact: Users may experience increased latency when accessing applications protected by Conditional Access App Control policies.
More info: Affected users may encounter intermittent 5XX errors during sign-in attempts when using apps managed by Microsoft Defender XDR. In some cases, retrying the operation may be successful.
Current status: We've identified that a downstream database update responsible for supporting Inline Access functionality introduced an issue that is preventing service components from reliably retrieving the data required to process requests, which is resulting in increased latency and intermittent service errors. We're reverting the recent service change to mitigate impact and are monitoring service health as the reversion progresses.
Scope of impact: Impact is specific to any user attempting to sign in to applications protected by Conditional Access App Control.
Root cause: A downstream database update responsible for supporting Inline Access functionality introduced an issue that is preventing service components from reliably retrieving the data required to process requests, resulting in impact.
Next update by: Friday, August 7, 2026, at 4:00 PM UTC
|
|---|
|
EX1456866 - Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 17 19:38:00 2026 |
|---|
| End Time: | Tue Aug 18 03:15:32 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Aug 18 03:17:37 2026 |
|---|
| Root Cause: | Recent changes to an authentication component utilized for Exchange ActiveSync were causing connection failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 18 03:16:33 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
User impact: Users may have been unable to send or receive new Exchange Online email through the native iOS mail app.
Final status: We reverted the authentication component changes utilized for Exchange ActiveSync and validated in our telemetry as well as with affected users that the impact was remediated.
Scope of impact: Some users attempting to send or receive new Exchange Online email through the native iOS mail app were impacted.
Start time: Monday, August 17, 2026, at 11:38 PM UTC
End time: Tuesday, August 18, 2026, at 7:15 AM UTC
Root cause: Recent changes to an authentication component utilized for Exchange ActiveSync were causing connection failures.
Next steps: We're continuing our analysis of the recent changes to isolate what triggered the initial impact which will help us in refining our update review processes to avoid impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 18 02:48:06 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
User impact: Users may be unable to send or receive new Exchange Online email through the native iOS mail app.
Current status: After reviewing the logs, we identified that there were recent changes to an authentication component utilized for Exchange ActiveSync that is causing connection failures. We're working to revert the problematic changes, which we anticipate should remediate the impact by the time of our next scheduled update, at which point we'll reach out to confirm with a subset of impacted users.
Scope of impact: Some users attempting to send or receive new Exchange Online email through the native iOS mail app are impacted.
Start time: Monday, August 17, 2026, at 11:38 PM UTC
Root cause: Recent changes to an authentication component utilized for Exchange ActiveSync are causing connection failures.
Next update by: Tuesday, August 18, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Aug 18 01:06:54 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
User impact: Users may be unable to send or receive new Exchange Online email through the native iOS mail app.
Current status: We're continuing our analysis of service-side logs and Exchange ActiveSync logs collected from impacted users to understand the source of the issue and determine our next troubleshooting steps.
Scope of impact: Some users attempting to send or receive new Exchange Online email through the native iOS mail app may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, August 18, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Mon Aug 17 23:27:53 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
User impact: Users may be unable to send or receive new Exchange Online email through the native iOS mail app.
Current status: We're reviewing service logs, telemetry, and contextual details provided by impacted users to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Some users attempting to send or receive new Exchange Online email through the native iOS mail app may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, August 18, 2026, at 5:00 AM UTC
|
|---|
|
EX1454202 - Users’ mailboxes may be set to default configurations
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 12:41:48 2026 |
|---|
| End Time: | Mon Aug 17 17:37:02 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 17 17:37:55 2026 |
|---|
| Root Cause: | A regression introduced through a worldwide modernization update to Exchange Online mailbox plan management caused customized mailbox plan and CAS mailbox plan settings to be set to default values. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 17 17:37:55 2026 |
|---|
| Description: | Title: Users’ mailboxes may be set to default configurations
User impact: Users’ mailboxes may have been set to default configurations.
More info: This communication was also published on the Message Center under MC1453151.
Please take action to confirm mailboxes created between July 21, 2026, to August 14, 2026, have the intended configurations applied.
Configurations set to default include:
- Mailbox quotas: IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota
- Transport quotas: MaxReceiveSize, MaxSendSize, RecipientLimits
- Protocol related config: ImapEnabled, PopEnabled, ActiveSyncEnabled
To identify potentially affected users, admins can use Exchange Online PowerShell with the below commands. Not all mailboxes returned may be impacted; however, we recommend reviewing mailboxes returned in the output and also those which were recently assigned licenses.
$mbxs = Get-Mailbox -Filter "WhenCreatedUTC -gt '07/21/2026 00:00:00'"
$mbxs | fl Identity, ExternalDirectoryObjectId, ProhibitSendQuota, ProhibitSendReceiveQuota, IssueWarningQuota, RecipientLimits, MaxSendSize, MaxReceiveSize
$casMbxs = Get-CasMailbox -Filter "WhenCreatedUTC -gt '07/21/2026 00:00:00'"
$casMbxs | fl Identity, ExternalDirectoryObjectId, ImapEnabled, PopEnabled, ActiveSyncEnabled
For more details on how to connect to Exchange Online PowerShell, please see: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
Final status: We completed our efforts to restore intended mailbox plan configurations; no newly created mailboxes (or users which were assigned new licenses) after August 16, 2026, are impacted. Mailboxes created during the window of impact still may not have settings applied as intended as, as we respected any changes your organization implemented post-mailbox creation, and did not reapply configurations. Your organization needs to take action to ensure the settings are configured as expected.
If your organization manually updated mailbox plans or CAS mailbox plans between July 21, 2026, to August 16, 2026, these changes were not overwritten. Any affected settings were restored to reflect the values that existed prior to the incident.
Root cause: A regression introduced through a worldwide modernization update to Exchange Online mailbox plan management caused customized mailbox plan and CAS mailbox plan settings to be set to default values.
Scope of impact: This could have impacted any mailbox that was created between July 21, 2026, to August 16, 2026.
Start time: July 21, 2026, at 12:00 PM UTC
End time: August 16, 2026, at 5:00 AM UTC
Next steps:
- We're analyzing our mailbox plan deployment methodology to ensure more rigorous testing scenarios to better detect regressions prior to rollout.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 13 12:54:29 2026 |
|---|
| Description: | Title: Users’ mailboxes may be set to default configurations
User impact: Users’ mailboxes may be set to default configurations.
More info: This communication is also published on the Message Center under MC1453151.
Please confirm mailboxes created between July 21, 2026, to August 14, 2026, have the intended configurations applied.
To find potentially affected users, use Exchange Online PowerShell with the below commands. Please note that some mailboxes returned may not be impacted; however, we recommend reviewing mailboxes returned in the output and also those which were recently assigned licenses.
$mbxs = Get-Mailbox -Filter "WhenCreatedUTC -gt '07/21/2026 00:00:00'"
$mbxs | fl Identity, ExternalDirectoryObjectId, ProhibitSendQuota, ProhibitSendReceiveQuota, IssueWarningQuota, RecipientLimits, MaxSendSize, MaxReceiveSize
$casMbxs = Get-CasMailbox -Filter "WhenCreatedUTC -gt '07/21/2026 00:00:00'"
$casMbxs | fl Identity, ExternalDirectoryObjectId, ImapEnabled, PopEnabled, ActiveSyncEnabled
For more details on how to connect to Exchange Online PowerShell, please see: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
Current status: We recently identified a scenario in which mailbox settings in the template used by admins to create new mailboxes (i.e. mailbox plans, CAS Mailbox Plans, Mailbox plans in Exchange Online (https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans)) were set to default configurations rather than what may have been customized. Configurations set to default include:
· Mailbox quotas: IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota
· Transport quotas: MaxReceiveSize, MaxSendSize, RecipientLimits
· Protocol related config: ImapEnabled, PopEnabled, ActiveSyncEnabled
We confirmed that this resulted from a regression introduced in a recent deployment and we reverted the responsible code on August 4, 2026. We’re now reapplying admins’ intended settings to the mailbox plan template so new mailboxes are created with the intended configurations moving forward. This effort is expected to be completed by Friday, August 14.
Mailboxes created during the window of impact won’t have settings applied as intended; out of respect for any changes your organization has already implemented post-mailbox creation, we are unable to reapply configurations to these mailboxes, and your organization needs to take action to ensure the settings are configured as expected.
If you updated mailbox plans for your tenant after August 7th, they will not be overwritten.
Scope of impact: This could of impact any mailbox that was created between July 21, 2026, to August 14, 2026.
Next update by: Monday, August 17, 2026, at 9:30 PM UTC
|
|---|
|
TM1456370 - Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 22 20:00:00 2026 |
|---|
| End Time: | Mon Aug 17 17:02:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 17 17:13:54 2026 |
|---|
| Root Cause: | A recent update to the reporting infrastructure led to a sync issue, resulting in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 17 17:13:44 2026 |
|---|
| Description: | Title: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
User impact: Users were experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
More info: When viewing Health reports in Microsoft Teams Rooms Pro Management Portal, the License Type column may have displayed "syncing" instead of the expected license type for affected devices. The issue may also have been present in exported reports.
As a workaround, users could have viewed accurate license information through alternate report views or by accessing the applicable room management pages within the portal.
Final status: We've completed deployment of our fix to address the offending sync issue and validated from our internal monitors that our actions successfully remediated impact. We advise users to run a new Microsoft Teams Rooms Pro Management Portal reports query to ensure the issue is remediated for them.
Scope of impact: Impact was specific to some users experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
End time: Monday, August 17, 2026, at 9:02 PM UTC
Root cause: A recent update to the reporting infrastructure led to a sync issue, resulting in this impact.
Next steps:
- We're analyzing the offending update to isolate why the potential for impact wasn't caught during our internal update testing and evaluation phases. This further 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: | Mon Aug 17 16:12:55 2026 |
|---|
| Description: | Title: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
User impact: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
More info: When viewing Health reports in Microsoft Teams Rooms Pro Management Portal, the License Type column may display "syncing" instead of the expected license type for affected devices. The issue may also be present in exported reports.
As a workaround, users can view accurate license information through alternate report views or by accessing the applicable room management pages within the portal.
Current status: We identified that a recent update to the reporting infrastructure is leading to a sync issue, resulting in this impact. We've validated and deployed a fix for this issue, and we anticipate that it should be completely rolled out to all affected environments by our next scheduled update.
Scope of impact: Impact is specific to some users experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
Root cause: A recent update to the reporting infrastructure is leading to a sync issue, resulting in this impact.
Next update by: Monday, August 17, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 17 08:03:08 2026 |
|---|
| Description: | Title: Some users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
User impact: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
More info: When viewing Health reports in Microsoft Teams Rooms Pro Management Portal, the License Type column may display "syncing" instead of the expected license type for affected devices. The issue may also be present in exported reports.
As a workaround, users can view accurate license information through alternate report views or by accessing the applicable room management pages within the portal.
Current status: We're investigating inaccurate license synchronization information displayed within health reports. The issue is limited to specific health reports and doesn't affect other report types. Some room licensing information may be displayed inaccurately; however, licensing data remains available through other areas of the portal.
Scope of impact: Impact is specific to some users experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
Next update by: Monday, August 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Aug 17 06:34:21 2026 |
|---|
| Description: | Title: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
User impact: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
More info: When viewing reports in Microsoft Teams Rooms Pro Management Portal, the License Type column may display "syncing" instead of the expected license type for affected devices. The issue may also be present in exported reports.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Your organization is affected by this event, and some users viewing device reports in the Microsoft Teams Rooms Pro Management Portal are impacted.
Next update by: Monday, August 17, 2026, at 12:30 AM UTC
|
|---|
|
TM1452695 - Some users may have been unable to access the Share tab in Microsoft Teams on Android devices
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 10 13:30:00 2026 |
|---|
| End Time: | Thu Aug 13 14:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Aug 16 09:05:48 2026 |
|---|
| Root Cause: | A recent compliance-related service update inadvertently introduced a code defect that resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Aug 16 09:04:34 2026 |
|---|
| Description: | Title: Some users may have been unable to access the Share tab in Microsoft Teams on Android devices
User impact: Users may have been unable to access the Share tab in Microsoft Teams on Android devices.
More info: Affected users may have been unable to access sharing functionality because the Share tab was missing in Microsoft Teams on Android devices.
Final status: We’ve confirmed that reverting the offending update successfully remediated the impact.
Scope of impact: Impact was specific to some users attempting to access the Share tab in Microsoft Teams on Android devices.
Start time: Monday, August 10, 2026, at 5:30 PM UTC
End time: Thursday, August 13, 2026, at 6:30 PM UTC
Root cause: A recent compliance-related service update inadvertently introduced a code defect that resulted in impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 11 08:38:44 2026 |
|---|
| Description: | Title: Some users may be unable to access the Share tab in Microsoft Teams on Android devices
User impact: Users may be unable to access the Share tab in Microsoft Teams on Android devices.
More info: Affected users may be unable to access sharing functionality because the Share tab is missing in Microsoft Teams on Android devices.
Current status: We've begun reverting the offending change to remediate the impact. We expect this process to complete and the impact to be fully resolved by our next scheduled update.
Scope of impact: Impact is specific to some users attempting to access the Share tab in Microsoft Teams on Android devices.
Start time: Monday, August 10, 2026, at 5:30 PM UTC
Root cause: A recent compliance update introduced a code issue, resulting in a service regression and causing impact.
Next update by: Sunday, August 16, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Aug 11 07:44:41 2026 |
|---|
| Description: | Title: Some users may be unable to access the Share tab in Microsoft Teams on Android devices
User impact: Users may be unable to access the Share tab in Microsoft Teams on Android devices.
More info: Affected users may be unable to access sharing functionality because the Share tab is missing in Microsoft Teams on Android devices.
Current status: We've determined that a recent compliance update introduced a code issue, resulting in a service regression and causing impact. We're working to revert the change and remediate impact.
Scope of impact: Impact is specific to some users attempting to access the Share tab in Microsoft Teams on Android devices.
Start time: Monday, August 10, 2026, at 5:30 PM UTC
Root cause: A recent compliance update introduced a code issue, resulting in a service regression and causing impact.
Next update by: Tuesday, August 11, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Aug 11 05:47:35 2026 |
|---|
| Description: | Title: Some users may be unable to access the Share tab in Microsoft Teams on Android devices
User impact: Users may be unable to access the Share tab in Microsoft Teams on Android devices.
More info: Affected users may be unable to access sharing functionality because the Share tab is missing 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: Impact is specific to some users who are served through the affected infrastructure, attempting to access the Share tab in Microsoft Teams on Android devices.
Next update by: Tuesday, August 11, 2026, at 12:00 PM UTC
|
|---|
|
CW1454295 - Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 13:26:00 2026 |
|---|
| End Time: | Fri Aug 14 20:30:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Aug 14 21:32:12 2026 |
|---|
| Root Cause: | A misconfiguration with the Agent Builder feature, which caused users to intermittently be unable to access Copilot Chat in Outlook on the web. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 14 21:32:12 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may have intermittently been unable to access Copilot Chat in Outlook on the web.
More info: When some users attempted to access Copilot Chat in Outlook on the web, they may have intermittently received an error that stated, "Something went wrong. An error occurred. Please try again."
Final status: Our investigation identified a misconfiguration with the Agent Builder feature, which caused users to intermittently be unable to access Copilot Chat in Outlook on the web. We disabled this configuration within the feature and confirmed with previously affected users that impact is remediated.
Scope of impact: Impact was specific to some users who attempted to access Copilot Chat in Outlook on the web.
Start time: Thursday, August 13, 2026, at 5:26 PM UTC
End time: Saturday, August 15, 2026, at 12:30 AM UTC
Root cause: A misconfiguration with the Agent Builder feature, which caused users to intermittently be unable to access Copilot Chat in Outlook on the web.
Next steps:
- To help prevent similar impact in the future, we're further reviewing the underlying cause of the misconfiguration.
This is the final update for the event.
|
|---|
|
| Time: | Fri Aug 14 19:39:11 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: Our review of service logging to identify the source of impact and determine our next steps is ongoing.
Scope of impact: Impact is specific to some users attempting to access Copilot Chat in Outlook on the web. This section may be updated as the investigation progresses.
Next update by: Saturday, August 15, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 18:01:38 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We've deployed our fix to the affected environment; however, we found that impact persists. Further review confirmed our previous root cause understanding was incorrect, and we've resumed our review of service logging to isolate the source of impact, so we can determine which mitigative actions can be implemented to restore service functionality.
Scope of impact: Impact is specific to some users attempting to access Copilot Chat in Outlook on the web. This section may be updated as the investigation progresses.
Root cause: An underlying client rendering issue within Copilot Studio is intermittently preventing Copilot Chat from rendering correctly in Outlook on the web.
Next update by: Saturday, August 15, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 11:59:28 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We’ve deployed the fix to a subset of the affected environments and are preparing to begin deployment to the remaining affected environments. Once available, we’ll provide a deployment completion timeline.
Scope of impact: Impact is specific to some users attempting to access Copilot Chat in Outlook on the web. This section may be updated as the investigation progresses.
Root cause: An underlying client rendering issue within Copilot Studio is intermittently preventing Copilot Chat from rendering correctly in Outlook on the web.
Next update by: Friday, August 14, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 05:24:44 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We've completed validation of the fix and have started deploying it to the affected environments. As deployment progresses, we're monitoring service telemetry and error rates to verify that Copilot Chat is loading successfully for affected users. We expect deployment to complete before our next scheduled update.
Scope of impact: Impact is specific to some users attempting to access Copilot Chat in Outlook on the web.
Root cause: An underlying client rendering issue within Copilot Studio is intermittently preventing Copilot Chat from rendering correctly in Outlook on the web.
Next update by: Friday, August 14, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 01:46:29 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We've identified that additional validations of the fix are required prior to deploying the fix to the affected environments. We expect the validations will be complete and we'll aim to provide a resolution timeline by our next scheduled update.
Scope of impact: some users attempting to access Copilot Chat in Outlook on the web may be affected. This information may be updated as our investigation continues.
Root cause: An underlying client rendering issue within Copilot Studio is causing intermittent impact Copilot Chat in Outlook on the web.
Next update by: Friday, August 14, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Aug 13 21:11:20 2026 |
|---|
| Description: | Title: Some users intermittently can't access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users intermittently can't access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: After further review, we identified an underlying client rendering issue that's causing the intermittent impact. We've developed a fix for the issue and are preparing for its application to the affected environment. We'll provide available updates on the deployment timeline at the next scheduled update time.
Scope of impact: Your organization is impacted by this event, and some users attempting to access Copilot Chat in Outlook on the web are affected. This information may be updated as our investigation continues.
Root cause: An underlying client rendering issue within Copilot Studio is causing intermittent impact Copilot Chat in Outlook on the web.
Next update by: Friday, August 14, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Thu Aug 13 19:38:50 2026 |
|---|
| Description: | Title: Some users intermittently can't access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users intermittently can't access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We identified some recent changes to authentication components and we're evaluating whether those changes are contributing to the impact. If the changes are causing impact, we'll determine if they can be rolled back safely.
Scope of impact: Your organization is impacted by this event, and some users attempting to access Copilot Chat in Outlook on the web are affected. This information may be updated as our investigation continues.
Next update by: Friday, August 14, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Aug 13 17:24:16 2026 |
|---|
| Description: | Title: Some users intermittently can't access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users intermittently can't access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We're reviewing our service side logs to identify any failures or abnormalities that may indicate the source of the impact.
Scope of impact: Your organization is impacted by this event, and some users attempting to access Copilot Chat in Outlook on the web are affected. This information may be updated as our investigation continues.
Next update by: Thursday, August 13, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 16:20:30 2026 |
|---|
| Description: | Title: Some users intermittently can't access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users intermittently can't access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We're reviewing the sample screenshots and errors provided by your organization to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Your organization is impacted by this event, and some users attempting to access Copilot Chat in Outlook on the web are affected. This information may be updated as our investigation continues.
Next update by: Thursday, August 13, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 16:10:30 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 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1454883 - Some users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures
| Status: | serviceRestored |
|---|
| Start Time: | Fri Aug 14 08:37:00 2026 |
|---|
| End Time: | Fri Aug 14 13:10:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Aug 14 14:23:54 2026 |
|---|
| Root Cause: | A recent feature update contains a configuration error causing inefficiencies in processing Graph API requests resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 14 14:22:08 2026 |
|---|
| Description: | Title: Some users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures
User impact: Users who utilize any Microsoft Teams application calling Microsoft Graph APIs may have encountered failures.
More info: Impacted Graph APIs included but may not have been limited to:
ActivityNotification
Get team
Final status: We've confirmed that the additional resources have remediated impact according to our service telemetry.
Scope of impact: Any user in the United States region using Microsoft Teams applications that leverage Graph API may have been affected.
Start time: Friday, August 14, 2026, at 12:37 PM UTC
End time: Friday, August 14, 2026, at 5:10 PM UTC
Root cause: A recent feature update contains a configuration error causing inefficiencies in processing Graph API requests resulted in impact.
Next steps:
- We're continuing our efforts to revert the impacting change and prevent similar impact in the future.
This is the final update for this event.
|
|---|
|
| Time: | Fri Aug 14 13:34:24 2026 |
|---|
| Description: | Title: Some users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures
User impact: Users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures.
More info: Impacted Graph APIs included but may not have been limited to:
ActivityNotification
Get team
Current status: Our investigation has identified that a recent feature update contains a configuration error causing inefficiencies in processing Graph API requests, resulting in impact. We've rebalanced load to improve GraphAPI throughput while we're working to revert the impacting change to prevent future impact.
Scope of impact: Any user in the United States region using Microsoft Teams applications that leverage Graph API may be affected.
Start time: Friday, August 14, 2026, at 12:37 PM UTC
Root cause: A recent feature update contains a configuration error causing inefficiencies in processing Graph API requests, resulting in impact.
Next update by: Friday, August 14, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 13:05:39 2026 |
|---|
| Description: | Title: Some users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures
User impact: Users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures.
More info: Impacted Graph API's included but may not have been limited to:
ActivityNotification
Get team
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.
|
|---|
|
EX1454755 - Users may be unable to send email externally and may receive DNS-related errors.
| Status: | investigationSuspended |
|---|
| Start Time: | Fri Aug 14 08:00:00 2026 |
|---|
| End Time: | Fri Aug 14 10:35:53 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Aug 14 11:08:16 2026 |
|---|
| Root Cause: | A DNS-related issue within a third-party email service caused failures when processing certain externally routed email traffic.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 14 10:50:15 2026 |
|---|
| Description: | Title: Users may be unable to send email externally and may receive DNS-related errors.
User impact: Users may be unable to send email externally and may receive DNS-related errors.
More info: Users attempting to send email to external recipients may receive DNS-related errors indicating that the destination domain does not exist.
Proofpoint is providing updates through its status page: https://proofpoint.my.site.com/community/s/proofpoint-current-incidents.
The provider's communication includes a temporary workaround that affected organizations may evaluate while remediation activities continue.
Final status: We've completed our investigation and confirmed that the Microsoft-managed Exchange Online infrastructure remained healthy throughout the event. Our findings indicate that the issue was caused by a DNS-related problem within a third-party email service. Since the Microsoft 365 service remains healthy and the issue does not originate within the Microsoft-managed environment, we're closing this Service Health Dashboard communication.
Customers should continue to follow the Proofpoint status page for future updates and guidance, including temporary mitigation options provided by the third-party service.
Scope of impact: Impact is limited to organizations that route email through the affected third-party email service, Proofpoint.
Most reported impact was observed in North America, though reports were also received from additional regions.
Start time: Friday, August 14, 2026, at 12:00 PM UTC
End time: Friday, August 14, 2026, at 2:35 PM UTC
Root cause: A DNS-related issue within a third-party email service caused failures when processing certain externally routed email traffic.
This is the final update for this event.
|
|---|
|
| Time: | Fri Aug 14 10:16:12 2026 |
|---|
| Description: | Title: Users may be unable to send email externally and may receive DNS-related errors.
User impact: Users may be unable to send email externally and may receive DNS-related errors.
More info: Users may receive a DNS error, indicating the domain does not exist, when trying to send emails externally.
Proofpoint are providing updates on their status page: https://proofpoint.my.site.com/community/s/proofpoint-current-incidents
Some organizations have reported that the issue resolves once removing the third-party from their mail flow configuration.
Current status: We've identified that emails routed through a specific third-party email service are experiencing DNS-related issues. The third-party is aware of the issue and are providing updates through their status page: https://proofpoint.my.site.com/community/s/proofpoint-current-incidents
We're performing the final validations to confirm that the Microsoft-managed environment remains healthy.
Scope of impact: Impact is specific to organizations that use a specific third-party email service (Proofpoint).
The majority of reported impact is from users in North America; however, we're aware of additional reports from users in other regions and are continuing to investigate the full scope of impact.
Start time: Friday, August 14, 2026, at 12:00 PM UTC
Next update by: Friday, August 14, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 09:45:19 2026 |
|---|
| Description: | Title: Some users may experience issues with mail flow in Exchange Online
User impact: Users may experience issues with mail flow in Exchange Online.
More info: Users may receive a DNS error, indicating the domain does not exist, when trying to send emails externally.
Current status: We're continuing to analyze diagnostic data and service telemetry from email processing systems. Additionally, we're reviewing logs from affected email transactions to help isolate the source of impact.
We're also aware of reports of similar impact affecting a third-party email delivery service and are investigating whether the events are related.
Scope of impact: The majority of reported impact is from users in North America; however, we're aware of additional reports from users in other regions and are continuing to investigate the full scope of impact.
Next update by: Friday, August 14, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 09:17:57 2026 |
|---|
| Description: | Title: Some users may experience issues with mail flow in Exchange Online
User impact: Users may experience issues with mail flow in Exchange Online.
Current status: We're reviewing diagnostic data and monitoring telemetry to isolate the source of the issue.
Scope of impact: The impact is being reported by users in the North America region. We're continuing to investigate the full scope of the issue and will update this as we confirm more information.
Next update by: Friday, August 14, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 09:05:23 2026 |
|---|
| Description: | Title: Some users may experience issues with mail flow in Exchange Online
User impact: Users may experience issues with mail flow in Exchange Online.
Current status: We've received reports indicating a potential issue with mail flow in Exchange Online, and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
|
