Microsoft's Incident Report for PennO365
Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within
the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh
this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this
list. Additionally you can check Microsoft's
status page for current service status messages.
The last extract was taken on Sat Jul 25 03:15:08 2026.
MP1438577 - Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jul 24 17:56:40 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jul 25 00:56:37 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Saturday, July 25, 2026, at 5:00 PM UTC |
|---|
|
Details
| Time: | Sat Jul 25 00:55:19 2026 |
|---|
| Description: | Title: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions
User impact: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions.
More info: As a result of this issue, admins should not create or update any Microsoft Purview Communication Compliance policies that contain conditions to avoid becoming impacted. Additionally, Data Loss Prevention (DLP) policy changes in Microsoft Purview may not take effect as expected until the issue is resolved.
Current status: We’re continuing to apply a set of configuration changes to ensure that further impact is prevented and anticipate that these changes will take effect prior to our next scheduled update. Additionally, we’re continuing our efforts to initiate the deployment of the corrective service change to address the issues within the aforementioned recent change which we suspect is responsible for causing this issue.
Scope of impact: This issue may affect any admin. This section may be updated as the investigation continues.
Next update by: Saturday, July 25, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Jul 24 21:18:15 2026 |
|---|
| Description: | Title: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions
User impact: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions.
More info: As a result of this issue, admins should not create or update any Microsoft Purview Communication Compliance policies that contain conditions to avoid becoming impacted. Additionally, Data Loss Prevention (DLP) policy changes in Microsoft Purview may not take effect as expected until the issue is resolved.
Current status: We're in the process of deploying a corrective service change to address the issues within the aforementioned recent change which we suspect is responsible for impact. We anticipate that these actions will validate our theory and determine whether additional troubleshooting actions will be necessary.
Scope of impact: This issue may affect any admin. This section may be updated as the investigation continues.
Next update by: Saturday, July 25, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Fri Jul 24 20:22:57 2026 |
|---|
| Description: | Title: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions
User impact: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions.
More info: As a result of this issue, admins should not create or update any Microsoft Purview Communication Compliance policies that contain conditions to avoid becoming impacted.
Current status: We're continuing our analysis on the recent change which we suspect is responsible for impact to validate our theory and cultivate our next troubleshooting actions.
Scope of impact: This issue may affect any admin. This section may be updated as the investigation continues.
Next update by: Saturday, July 25, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Jul 24 18:29:06 2026 |
|---|
| Description: | Title: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions
User impact: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions.
More info: As a result of this issue, admins should not create or update any Microsoft Purview Communication Compliance policies that contain conditions to avoid becoming impacted.
Current status: We're investigating a recent change which we suspect is responsible for impact to confirm our theory and determine next steps for impact remediation.
Scope of impact: This issue may affect any admin. This section may be updated as the investigation continues.
Next update by: Saturday, July 25, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Jul 24 18:04:25 2026 |
|---|
| Description: | Title: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions
User impact: Admins may not receive alerts for Microsoft Purview Communication Compliance policies that contain conditions.
More info: As a result of this issue, admins should not create or update any Microsoft Purview Communication Compliance policies that contain conditions to avoid becoming impacted.
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.
|
|---|
|
MO1438482 - Some admins may see inaccurate status information in the service health section in the Microsoft 365 admin center
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jul 24 16:13:54 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 24 18:25:00 2026 |
|---|
| Root Cause: | A code defect introduced by a recent deployment to the Microsoft 365 admin center caused the systems to resolve status conflicts by severity rather than status change was made resulted in the status showing as active instead of resolved for some communications.
|
|---|
| Next Update: | Saturday, July 25, 2026, at 8:00 PM UTC |
|---|
|
Details
| Time: | Fri Jul 24 18:24:09 2026 |
|---|
| Description: | Title: Some admins may see inaccurate status information in the service health section in the Microsoft 365 admin center
User impact: Admins may see inaccurate status information in the service health section in the Microsoft 365 admin center.
More info: Specifically, admins may see resolved incidents and advisories incorrectly displayed as active.
Current status: We're continuing to monitor the reversion of the responsible deployment to remediate the impact and expect this process to complete for all remaining impacted admins by our next scheduled update.
Scope of impact: Admins in the West US, UK South, and France Central regions attempting to view the accurate status of incident and advisory communications in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, July 21, 2026, at 7:45 PM UTC
Root cause: A code defect introduced by a recent deployment to the Microsoft 365 admin center caused the systems to resolve status conflicts by severity rather than status change was made resulted in the status showing as active instead of resolved for some communications.
Next update by: Saturday, July 25, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Jul 24 16:48:09 2026 |
|---|
| Description: | Title: Some admins may see inaccurate status information in the service health section in the Microsoft 365 admin center
User impact: Admins may see inaccurate status information in the service health section in the Microsoft 365 admin center.
More info: Specifically, admins may see resolved incidents and advisories incorrectly displayed as active.
Current status: We've identified that a code defect was introduced by a recent deployment to the service health feature of the Microsoft admin center which caused the systems to resolve status conflicts by severity rather than how recent a status change was made, resulting in the impact. We're reverting the offending deployment to remediate the impact, which completed for a majority of admins.
Scope of impact: Admins in the West US, UK South, and France Central regions attempting to view the accurate status of incident and advisory communications in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, July 21, 2026, at 7:45 PM UTC
Root cause: A code defect introduced by a recent deployment to the Microsoft 365 admin center caused the systems to resolve status conflicts by severity rather than status change was made resulted in the status showing as active instead of resolved for some communications.
Next update by: Friday, July 24, 2026, at 10:30 PM UTC
|
|---|
|
EX1435168 - Some users may be unable to view location and subject details for other users' Exchange Online calendar items
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Jul 13 20:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 24 17:42:05 2026 |
|---|
| 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: | Monday, July 27, 2026, at 10:00 PM UTC |
|---|
|
Details
| 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
|
|---|
|
TM1437339 - Some users may not receive notifications in the Microsoft Teams desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 15 19:34:00 2026 |
|---|
| End Time: | Thu Jul 23 16:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 24 17:37:11 2026 |
|---|
| Root Cause: | A recent configuration change intended to address a parallel impact changed the behavior of the notification window, which resulted in notifications not being displayed as expected. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 23 21:26:32 2026 |
|---|
| Description: | Title: Some users may not receive notifications in the Microsoft Teams desktop client
User impact: Users may not receive notifications in the Microsoft Teams desktop client.
More info: This issue appeared to be specific to the Microsoft Teams desktop client for Windows. Some affected users may have heard an incoming call ringtone but not received the associated notification, while other affected users may have not received notifications for chat messages.
Final status: We've confirmed that deployment of both of our remediation efforts completed for all affected users and the offending configuration change was reverted. We monitored this solution as it progressed and verified that impact was resolved by our actions.
Scope of impact: Some users who received incoming calls or messages and who were expecting to receive notifications in the Microsoft Teams desktop client for Windows may have been impacted.
Start time: Wednesday, July 15, 2026, at 11:34 PM UTC
End time: Thursday, July 23, 2026, at 8:30 PM UTC
Root cause: A recent configuration change intended to address a parallel impact changed the behavior of the notification window, which resulted in notifications not being displayed as expected.
Next steps: - We've deployed a pre-emptive remediation which will ensure that users do not see service interruptions when receiving this update.
- We're continuing to optimize our deployment pipeline to ensure that similar issues do not reoccur.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 23 17:44:24 2026 |
|---|
| Description: | Title: Some users may not receive notifications in the Microsoft Teams desktop client
User impact: Users may not receive notifications in the Microsoft Teams desktop client.
More info: This issue appears to be specific to the Microsoft Teams desktop client for Windows. Some affected users may hear an incoming call ringtone but not receive the associated notification, while other affected users may not receive notifications for chat messages.
Current status: While we continue to expedite the deployment of our fix, we've also determined that an additional mitigation will further increase its efficacy. We're monitoring both the deployment of our fix and the additional mitigation so that we can ensure full remediation.
Scope of impact: Some users receiving incoming calls or messages and are expecting to receive notifications in the Microsoft Teams desktop client for Windows may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, July 23, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Jul 23 16:37:14 2026 |
|---|
| Description: | Title: Some users may not receive notifications in the Microsoft Teams desktop client
User impact: Users may not receive notifications in the Microsoft Teams desktop client.
More info: This issue appears to be specific to the Microsoft Teams desktop client for Windows. Some affected users may hear an incoming call ringtone but not receive the associated notification, while other affected users may not receive notifications for chat messages.
Current status: We're expediting the deployment of our fix and are monitoring progress to validate remediation.
Scope of impact: Some users receiving incoming calls or messages and are expecting to receive notifications in the Microsoft Teams desktop client for Windows may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, July 23, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Jul 23 14:23:06 2026 |
|---|
| Description: | Title: Some users may not receive notifications in the Microsoft Teams desktop client
User impact: Users may not receive notifications in the Microsoft Teams desktop client.
More info: This issue appears to be specific to the Microsoft Teams desktop client for Windows. Some affected users may hear an incoming call ringtone but not receive the associated notification, while other affected users may not receive notifications for chat messages.
Current status: We're continuing to deploy the configuration change to the subset of affected users, after which we'll test to confirm it was effective at remedating the impact.
Scope of impact: Some users receiving incoming calls or messages and are expecting to receive notifications in the Microsoft Teams desktop client for Windows may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, July 23, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:21:41 2026 |
|---|
| Description: | Title: Some users may not receive notifications in the Microsoft Teams desktop client
User impact: Users may not receive notifications in the Microsoft Teams desktop client.
More info: This issue appears to be specific to the Microsoft Teams desktop client for Windows. Some affected users may hear an incoming call ringtone but not receive the associated notification, while other affected users may not receive notifications for chat messages.
Current status: To expedite the remediation, we're deploying a configuration change to a subset of affected users that we expect will restore the notifications. Once we've confirmed that this remediates the impact, we'll apply the change more broadly.
Scope of impact: Some users receiving incoming calls or messages and are expecting to receive notifications in the Microsoft Teams desktop client for Windows may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, July 23, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 10:55:39 2026 |
|---|
| Description: | Title: Some users may not receive notifications in the Microsoft Teams desktop client
User impact: Users may not receive notifications in the Microsoft Teams desktop client.
More info: This issue appears to be specific to the Microsoft Teams desktop client for Windows. Some affected users may hear an incoming call ringtone but not receive the associated notification, while other affected users may not receive notifications for chat messages.
Current status: We've identified a recent Microsoft Teams desktop client service update for Windows that correlates with the impact. We're reversing this service update to confirm whether this remediates the impact.
Scope of impact: Some users receiving incoming calls or messages and are expecting to receive notifications in the Microsoft Teams desktop client for Windows may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, July 23, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 09:11:05 2026 |
|---|
| Description: | Title: Some users may not receive notifications in the Microsoft Teams desktop client
User impact: Users may not receive notifications in the Microsoft Teams desktop client.
More info: This issue appears to be specific to the Microsoft Teams desktop client for Windows. Some affected users may hear an incoming call ringtone but not receive the associated notification, while other affected users may not receive notifications for chat messages.
Current status: We're analyzing diagnostic data from a sample of affected users to investigate the root cause of the issue and identify a mitigation strategy. In parallel, we're reviewing recent Teams client updates to determine whether a recent change may be contributing to the impact.
Scope of impact: Some users expecting to receive notifications in the Microsoft Teams desktop client for Windows may be impacted.
Next update by: Thursday, July 23, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 09:11:03 2026 |
|---|
| Description: | Title: Some users may not receive notifications in the Microsoft Teams desktop client
User impact: Users may not receive notifications in the Microsoft Teams desktop client.
More info: This issue appears to be specific to the Microsoft Teams desktop client for Windows. Some affected users may hear an incoming call ringtone but not receive the associated notification, while other affected users may not receive notifications for chat messages.
Current status: We're analyzing diagnostic data from a sample of affected users to investigate the root cause of the issue and identify a mitigation strategy. In parallel, we're reviewing recent Teams client updates to determine whether a recent change may be contributing to the impact.
Scope of impact: Some users expecting to receive notifications in the Microsoft Teams desktop client for Windows may be impacted.
Next update by: Thursday, July 23, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 08:27:27 2026 |
|---|
| Description: | Title: Some users may not see incoming call notifications in Microsoft Teams
User impact: Users may not see incoming call notifications in Microsoft Teams.
More info: Affected users may hear the incoming call ringtone but not see the incoming call notification toast. Reports indicate the issue occurs consistently for affected users and may result in missed calls, despite the incoming call reaching the client.
Current status: We're analyzing diagnostic data from affected users and reviewing the results of ongoing testing. We've observed that one affected user no longer experiences the issue after reverting to an earlier version of the Teams desktop client. We're investigating the root cause of the issue, including whether it may be related to a recent Teams client update.
Scope of impact: Your organization is affected by this event, and some users attempting to receive incoming Microsoft Teams calls are impacted.
Next update by: Thursday, July 23, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Jul 23 07:12:06 2026 |
|---|
| Description: | Title: Some users may not see incoming call notifications in Microsoft Teams
User impact: Users may not see incoming call notifications in Microsoft Teams.
More info: Affected users may hear the incoming call ringtone but not see the incoming call notification toast. Reports indicate the issue occurs consistently for affected users and may result in missed calls, despite the incoming call reaching the client.
Current status: We're reviewing client telemetry and diagnostic logs to identify what prevented the incoming call notification from appearing and to determine the next steps required to mitigate impact.
Scope of impact: Your organization is affected by this event, and some users attempting to receive incoming Microsoft Teams calls are impacted.
Next update by: Thursday, July 23, 2026, at 1:00 PM UTC
|
|---|
|
EX1436407 - Some users' mailboxes may be incorrectly quarantined in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jul 19 18:00:00 2026 |
|---|
| End Time: | Fri Jul 24 13:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jul 24 17:07:25 2026 |
|---|
| Root Cause: | A recent infrastructure change resulted in excessive memory consumption from unexpected indexing data results in an out-of-memory condition, which caused affected mailboxes to be incorrectly quarantined.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 24 16:15:22 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may have been incorrectly quarantined in Exchange Online.
More info: This issue may have blocked some users from receiving email messages due to their mailboxes incorrectly being quarantined, and users sending email messages to these mailboxes may have received a Non-Delivery Report (NDR).
Final status: We completed our data cleanup efforts for all remaining portions of affected infrastructure and released the last remaining affected mailboxes. We were able to confirm that these final mitigation steps successfully resolved impact through our service health telemetry.
Scope of impact: Some users attempting to receive email messages through Exchange Online may have been impacted.
Start time: Sunday, July 19, 2026, at 10:00 PM UTC
End time: Friday, July 24, 2026, at 5:00 PM UTC
Root cause: A recent infrastructure change resulted in excessive memory consumption from unexpected indexing data results in an out-of-memory condition, which caused affected mailboxes to be incorrectly quarantined.
Next steps: - We're reviewing the responsible infrastructure change to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 24 13:23:53 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue may block some users from receiving email messages due to their mailboxes incorrectly being quarantined, and users sending email messages to these mailboxes may receive a Non-Delivery Report (NDR).
Current status: While our service health telemetry indicates the impact has improved vastly, we're taking additional time to complete our data cleanup efforts for all portions of affected infrastructure and are releasing the last remaining affected mailboxes to ensure the impact is fully remediated.
Scope of impact: Some users attempting to receive email messages through Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Sunday, July 19, 2026, at 10:00 PM UTC
Root cause: A recent infrastructure change is resulting in excessive memory consumption from unexpected indexing data results in an out-of-memory condition, causing affected mailboxes to be incorrectly quarantined.
Next update by: Friday, July 24, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 20:30:08 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue may block some users from receiving email messages due to their mailboxes incorrectly being quarantined, and users sending email messages to these mailboxes may receive a Non-Delivery Report (NDR).
Current status: The aforementioned data clean-up process is progressing as expected and we’re continuing to remove the affected mailboxes from quarantine in the regions that have been processed. We anticipate both these processes will be completed and this issue will be resolved by our next scheduled communications update.
Scope of impact: Some users attempting to receive email messages through Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Sunday, July 19, 2026, at 10:00 PM UTC
Root cause: A recent infrastructure change is resulting in excessive memory consumption from unexpected indexing data results in an out-of-memory condition, causing affected mailboxes to be incorrectly quarantined.
Next update by: Friday, July 24, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 12:31:39 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue may block some users from receiving email messages due to their mailboxes incorrectly being quarantined, and users sending email messages to these mailboxes may receive a Non-Delivery Report (NDR).
Current status: While we continue to monitor our data clean-up progress in the remaining portion of affected infrastructure, we're removing affected mailboxes from quarantine in the regions that are done processing to remediate impact. We'll aim to provide a timeline for remediating impact in the remaining portion of affected infrastructure by our next scheduled update.
Scope of impact: Some users receiving email messages through Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Sunday, July 19, 2026, at 10:00 PM UTC
Root cause: A recent infrastructure change is resulting in excessive memory consumption from unexpected indexing data results in an out-of-memory condition, causing affected mailboxes to be incorrectly quarantined.
Next update by: Friday, July 24, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jul 22 21:56:12 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue may block some users from receiving email messages due to their mailboxes incorrectly being quarantined, and users sending email to these mailboxes may receive a Non-delivery Report (NDR).
Current status: We're continuing to monitor the progress of cleaning up the excess data, and we'll aim to provide a completion timeline by our next scheduled update.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Sunday, July 19, 2026, at 10:00 PM UTC
Root cause: A recent infrastructure change is resulting in excessive memory consumption from unexpected indexing data results in an out-of-memory condition, causing affected mailboxes to be incorrectly quarantined.
Next update by: Thursday, July 23, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jul 22 19:57:58 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue may block some users from receiving email messages due to their mailboxes incorrectly being quarantined, and users sending email to these mailboxes may receive a Non-delivery Report (NDR).
Current status: The clean-up process of excess data is ongoing, and currently 72 percent complete. While we continue to monitor our clean-up progress, we're removing mailboxes from quarantine in the regions we've validated sufficient memory levels to expedite remediation.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Sunday, July 19, 2026, at 10:00 PM UTC
Root cause: A recent infrastructure change is resulting in excessive memory consumption from unexpected indexing data results in an out-of-memory condition, causing affected mailboxes to be incorrectly quarantined.
Next update by: Thursday, July 23, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Jul 22 17:42:01 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue may block some users from receiving email messages due to their mailboxes incorrectly being quarantined, and users sending email to these mailboxes may receive a Non-delivery Report (NDR).
Current status: Our clean-up of the excess data is approximately 66 percent complete and continues to reduce memory consumption and additional mailboxes from becoming quarantined. As our clean-ups progress, we're subsequently removing mailboxes from quarantine in the regions we've validated sufficient memory levels.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Sunday, July 19, 2026, at 10:00 PM UTC
Root cause: A recent infrastructure change caused excessive memory consumption from unexpected indexing data results in an out-of-memory condition, causing affected mailboxes to be incorrectly quarantined.
Next update by: Thursday, July 23, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Jul 22 15:30:41 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue may block some users from receiving email messages due to their mailboxes incorrectly being quarantined, and users sending email to these mailboxes may receive a Non-delivery Report (NDR).
Current status: We're progressing with our clean-up of the excess data to reduce the memory consumption and prevent additional mailboxes from becoming quarantined. In parallel, we've started to remove mailboxes from quarantine in the initial regions where our cleanup actions have completed. We'll provide an estimated timeline for our mitigation actions once it has become available.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Sunday, July 19, 2026, at 10:00 PM UTC
Root cause: A recent infrastructure change caused excessive memory consumption from unexpected indexing data results in an out-of-memory condition, causing affected mailboxes to be incorrectly quarantined.
Next update by: Wednesday, July 22, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jul 22 11:31:55 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue may block some users from receiving email messages due to their mailboxes incorrectly being quarantined, and users sending email to these mailboxes may receive a Non-delivery Report (NDR).
Current status: We've determined that this is a reoccurrence of EX1434354 and additional actions are needed to completely remediate impact. We've identified excessive indexing data causing memory consumption issues that cause mailboxes to be incorrectly quarantined. We're cleaning up this excess data to reduce the memory consumption to prevent additional mailboxes from becoming quarantined. Once complete, we'll remove the affected mailboxes from quarantine to completely remediate impact.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: Excessive memory consumption from unexpected indexing data results in an out-of-memory condition, causing affected mailboxes to be incorrectly quarantined.
Next update by: Wednesday, July 22, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jul 22 10:52:34 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1438439 - Intune admins may intermittently be unable to complete actions that require Multi Admin Approval
| Status: | falsePositive |
|---|
| Start Time: | Fri Jul 24 14:17:20 2026 |
|---|
| End Time: | Fri Jul 24 14:51:43 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 24 15:35:23 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 24 14:51:43 2026 |
|---|
| Description: | Title: Intune admins may intermittently be unable to complete actions that require Multi Admin Approval
User impact: Intune admins may intermittently be unable to complete actions that require Multi Admin Approval.
Final status: The investigation is complete and we've determined the service is healthy. A service incident didn't actually occur. This communication will expire in 24 hours.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 24 14:28:33 2026 |
|---|
| Description: | Title: Intune admins may intermittently be unable to complete actions that require Multi Admin Approval
User impact: Intune admins may intermittently be unable to complete actions that require Multi Admin Approval.
Current status: We're investigating a potential issue with completing actions that require Multi Admin Approval and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1425545 - Some users may have been unable to open or use custom Copilot agents in Microsoft 365 Copilot and received an error
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Jul 10 13:48:00 2026 |
|---|
| End Time: | Tue Jul 14 04:15:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jul 24 12:53:37 2026 |
|---|
| Root Cause: | A change was introduced to transition model selection data retrieval from the existing API to a new API. The new API initially provided only the default model setting and did not yet include the full model metadata required by the client application. As a result, the application received an incomplete response that was missing expected metadata. Because the client logic assumed this metadata would always be present, it encountered an unhandled condition when processing the response, causing the application to fail and resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 24 12:53:37 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 14 08:37:28 2026 |
|---|
| Description: | Title: Some users may have been unable to open or use custom Copilot agents in Microsoft 365 Copilot and received an error
User impact: Users may have been unable to open or use custom Copilot agents and received an error.
More info: Impacted users reported receiving an error stating "Something went wrong" or "Client error: Cannot read properties of undefined", and they may have encountered client crashes when attempting to open custom Copilot agents that were created through the Agent Builder in Copilot. User reports indicated that custom agents may have still been accessible through Microsoft Teams.
Final status: We've successfully deployed the fix and confirmed with a sample of affected users that impact is resolved.
Scope of impact: Some users who were attempting to open or use custom Copilot agents that were created through the Agent Builder in Copilot may have been impacted.
Start time: Friday, July 10, 2026, at 5:48 PM UTC
End time: Tuesday, July 14, 2026, at 3:50 AM UTC
Root cause: A change was introduced to transition model selection data retrieval from the existing API to a new API. The new API initially provided only the default model setting and did not yet include the full model metadata required by the client application. As a result, the application received an incomplete response that was missing expected metadata. Because the client logic assumed this metadata would always be present, it encountered an unhandled condition when processing the response, causing the application to fail and resulting in 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: | Mon Jul 13 17:23:01 2026 |
|---|
| Description: | Title: Some users may be unable to open or use custom Copilot agents in Microsoft 365 Copilot and receive an error
User impact: Users may be unable to open or use custom Copilot agents and receive an error.
More info: Impacted users report receiving an error stating "Something went wrong" or "Client error: Cannot read properties of undefined", and they may encounter client crashes when attempting to open custom Copilot agents that were created through the Agent Builder in Microsoft 365 Copilot. User reports indicate that custom agents may still be accessible through Microsoft Teams.
Current status: Due to an unrelated issue affecting our deployment infrastructure, we're unable to begin the deployment of our fix as anticipated. We're working to resolve the issues blocking our deployment and provide an updated timeline for deployment initiation and completion.
Scope of impact: Some users who are attempting to open or use custom Copilot agents that were created through the Agent Builder in Microsoft 365 Copilot may be impacted. This information may be updated as our investigation continues.
Start time: Friday, July 10, 2026, at 5:48 PM UTC
Root cause: A recent service change caused Copilot to receive incomplete data when loading the agent experience. As a result, the app couldn't render the affected experience correctly for some users.
Next update by: Tuesday, July 14, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jul 13 14:43:13 2026 |
|---|
| Description: | Title: Some users may be unable to open or use custom Copilot agents in Microsoft 365 Copilot and receive an error
User impact: Users may be unable to open or use custom Copilot agents and receive an error.
More info: Impacted users report receiving an error stating "Something went wrong" or "Client error: Cannot read properties of undefined", and they may encounter client crashes when attempting to open custom Copilot agents that were created through the Agent Builder in Microsoft 365 Copilot. User reports indicate that custom agents may still be accessible through Microsoft Teams.
Current status: We're completing the final round of validations prior to deploying a new build that contains a fix to address incomplete data being returned when loading the Copilot agent experience. We anticipate deployment to be initiated by our next scheduled update, and we aim to provide a timeline for impact remediation at that time.
Scope of impact: Some users who are attempting to open or use custom Copilot agents that were created through the Agent Builder in Microsoft 365 Copilot may be impacted. This information may be updated as our investigation continues.
Start time: Friday, July 10, 2026, at 5:48 PM UTC
Root cause: A recent service change caused Copilot to receive incomplete data when loading the agent experience. As a result, the app couldn't render the affected experience correctly for some users.
Next update by: Monday, July 13, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jul 13 03:59:24 2026 |
|---|
| Description: | Title: Some users may be unable to open or use custom Copilot agents in Microsoft 365 Copilot and receive an error
User impact: Users may be unable to open or use custom Copilot agents and receive an error.
More info: Impacted users report receiving an error stating "Something went wrong" or "Client error: Cannot read properties of undefined", and may encounter client crashes when attempting to open custom Copilot agents that were created through the Agent Builder in Microsoft 365 Copilot. User reports indicate that custom agents may still be accessible through Microsoft Teams.
Current status: We've identified that Microsoft Copilot (Microsoft 365) receives incomplete data while loading the agent experience, causing the app to fail and render correctly. We're validating deployment of a newer build that contains the fix and, if successful, plan to roll it out to the affected environment to mitigate impact.
Scope of impact: Some users who are attempting to open or use custom Copilot agents that were created through the Agent Builder in Microsoft 365 Copilot may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service change caused Microsoft Copilot (Microsoft 365) to receive incomplete data when loading the agent experience. As a result, the app couldn't render the affected experience correctly for some users.
Next update by: Monday, July 13, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Jul 13 01:28:09 2026 |
|---|
| Description: | Title: Some users may be unable to open or use custom Copilot agents in Microsoft 365 Copilot and receive an error
User impact: Users may be unable to open or use custom Copilot agents and receive an error.
More info: Impacted users report receiving an error stating "Something went wrong" or "Client error: Cannot read properties of undefined", and may encounter client crashes when attempting to open custom Copilot agents that were created through the Agent Builder in Microsoft 365 Copilot. User reports indicate that custom agents may still be accessible through Microsoft Teams.
Current status: We're continuing to review network trace logs and attempting to reproduce the issue in our internal testing environment to gain an understanding of the underlying root cause.
Scope of impact: Some users who are attempting to open or use custom Copilot agents that were created through the Agent Builder in Microsoft 365 Copilot may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, July 13, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Sun Jul 12 23:38:39 2026 |
|---|
| Description: | Title: Some users may be unable to open or use custom Copilot Agents in Microsoft Copilot Studio and receive an error
User impact: Users may be unable to open or use custom Copilot Agents in Microsoft Copilot Studio and receive an error.
More info: Impacted users report receiving an error stating "Something went wrong" or "Client error: Cannot read properties of undefined", and may encounter client crashes when attempting to open custom Copilot agents in Microsoft Copilot Studio. User reports indicate that custom agents are still accessible through Microsoft Teams.
Current status: We're reviewing network trace logs to help with the investigation and to aid in determining our next troubleshooting steps.
Scope of impact: Some users who are attempting to open or use custom Copilot Agents in Microsoft Copilot Studio may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, July 13, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Sun Jul 12 22:47:54 2026 |
|---|
| Description: | Title: Some users aren't able to open or use custom Copilot Agents in Microsoft Copilot Studio and get an error
User impact: Users aren't able to open or use custom Copilot Agents in Microsoft Copilot Studio and get an error.
More info: Impacted users report receiving an error stating "Something went wrong" or "Client error: Cannot read properties of undefined", and may encounter client crashes when attempting to open custom Copilot agents in Microsoft Copilot Studio. User reports indicate that custom agents are still accessible through Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Copilot Studio and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
TM1438173 - Users may receive incorrect notifications that Microsoft Teams meeting recordings failed to upload to Microsoft OneDrive
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jul 24 06:03:27 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 24 06:05:38 2026 |
|---|
| Root Cause: | A recent service change introduced an issue within the recording processing workflow that is causing intermittent connectivity failures when recording completion information is being processed.
|
|---|
| Next Update: | Monday, July 27, 2026, at 12:00 PM UTC |
|---|
|
Details
| Time: | Fri Jul 24 06:05:38 2026 |
|---|
| Description: | Title: Users may receive incorrect notifications that Microsoft Teams meeting recordings failed to upload to Microsoft OneDrive
User impact: Users may receive incorrect notifications that Teams meeting recordings failed to upload to OneDrive.
More info: Meeting recordings are uploaded successfully and remain accessible on OneDrive, however, affected users may see notifications in Teams stating that the recording upload failed even though the upload completed successfully.
Current status: We've identified that a recent service change introduced a connection issue within the recording processing workflow. As a result, some recordings that are successfully uploaded to OneDrive aren't correctly recognized as completed, causing users to receive inaccurate notifications. We're deploying an updated service build with corrective changes and are progressively redirecting user traffic to alternate infrastructure to remediate the issue. We're closely monitoring telemetry as the deployment progresses and will provide a completion timeline once it becomes available.
Scope of impact: Any user attempting to access Teams meeting recordings may receive inaccurate upload failure notifications.
Root cause: A recent service change introduced an issue within the recording processing workflow that is causing intermittent connectivity failures when recording completion information is being processed.
Next update by: Monday, July 27, 2026, at 12:00 PM UTC
|
|---|
|
TM1437780 - Some users may be unable to join or create Microsoft Teams meetings or calls
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 23 20:54:54 2026 |
|---|
| End Time: | Thu Jul 23 23:13:30 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jul 24 02:45:26 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| 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:
-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
Preliminary root cause: A recent change associated with our ongoing service resilience efforts overloaded our traffic management processes and caused impact.
Next steps:
- We're conducting an analysis of the recent service configuration change to gain additional clarity into the root cause and identify any further measures we can enact to enhance infrastructure safeguards and avoid the 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: | 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.
|
|---|
|
MO1434392 - Admins may be unable to track open email counts in the Microsoft 365 admin center organizational messages
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Jul 20 16:27:05 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 24 00:06:45 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Wednesday, July 29, 2026, at 1:30 AM UTC |
|---|
|
Details
| Time: | Thu Jul 23 20:03:25 2026 |
|---|
| Description: | Title: Admins may be unable to track open email counts in the Microsoft 365 admin center organizational messages
User impact: Admins may be unable to track open email counts in the Microsoft 365 admin center organizational messages.
Current status: We’ve updated our public documentation to reflect that admins will be able to view the open counts of any Organizational message emails sent before the disablement; however, the open counts of any Organizational message emails sent after the disablement will be unavailable to admins. We anticipate that the in-app banner within Organizational Messages experiences (under Reports in Microsoft 365 admin center) to notify admins of this change, will be reflected by our next scheduled update.
Scope of impact: Any admin attempting to view open counts for their emails sent with Organizational messages in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, July 29, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Jul 20 17:00:00 2026 |
|---|
| Description: | Title: Admins may be unable to track open email counts in the Microsoft 365 admin center organizational messages
User impact: Admins may be unable to track open email counts in the Microsoft 365 admin center organizational messages.
Current status: We've disabled the capability to track open counts for all emails sent with Organizational messages in the Microsoft 365 admin center. Admins will be able to view the open counts of any Organizational message emails sent before the disablement; however, the open counts of any Organizational message emails sent after the disablement will be unavailable to admins. In the near future, we will update our public documentation to reflect this as well as provide an in-app banner within Organizational Messages experiences (under Reports in Microsoft 365 admin center) to notify admins of this change.
Scope of impact: Any admin attempting to view open counts for their emails sent with Organizational messages in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, July 24, 2026, at 1:30 AM UTC
|
|---|
|
MO1437790 - Admins may be unable to access the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 23 21:18:02 2026 |
|---|
| End Time: | Thu Jul 23 21:41:54 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 23 22:27:32 2026 |
|---|
| Root Cause: | An issue affecting an Azure Key Vault dependency caused the Microsoft 365 admin center to become unavailable. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 23 21:35:51 2026 |
|---|
| Description: | Title: Admins may be unable to access the Microsoft 365 admin center
User impact: Admins may have been unable to access the Microsoft 365 admin center.
Final status: We’ve determined that an issue affecting an Azure Key Vault dependency caused the Microsoft 365 admin center to become unavailable. We’ve restarted the affected dependencies to remediate the impact and completed recovery actions across the affected regions. We’ve confirmed from our telemetry that this issue is no longer occurring.
Scope of impact: Any admins hosted on the affected infrastructure in Department of Defense, Government Community Cloud High, and some admins in the West US regions were impacted.
Start time: Thursday, July 23, 2026, at 6:00 PM UTC
End time: Friday, July 24, 2026, at 12:00 AM UTC
Root cause: An issue affecting an Azure Key Vault dependency caused the Microsoft 365 admin center to become unavailable.
Next steps: We’re continuing our review of the event to determine how we can prevent similar impact from occurring again.
This is the final update for the event.
|
|---|
|
CP1434578 - Some users may be unable to drag and drop files to add references into Microsoft Copilot Notebooks
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 9 13:54:00 2026 |
|---|
| End Time: | Thu Jul 23 16:30:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 23 19:06:42 2026 |
|---|
| Root Cause: | An update intended to optimize the service contained an error, which resulted in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 23 18:17:45 2026 |
|---|
| Description: | Title: Some users may be unable to drag and drop files to add references into Microsoft Copilot Notebooks
User impact: Users may have been unable to drag and drop files to add references into Copilot Notebooks.
More info: Affected users could've avoided the issue by referencing files from their local PC by choosing the ‘Upload from this device’ icon to the right of the search bar. To reference files stored in OneDrive or SharePoint, affected users could've used search or chosen the cloud icon to the far right from the search bar.
Final status: We've confirmed that reverting the responsible update has successfully remediated this impact for all affected environments.
Scope of impact: Users attempting to drag and drop files to add references into Copilot Notebooks may have been unable to do so.
Start time: Thursday, July 9, 2026, at 5:54 PM UTC
End time: Thursday, July 23, 2026, at 8:30 PM UTC
Root cause: An update intended to optimize the service contained an error, which resulted in this 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: | Mon Jul 20 19:16:53 2026 |
|---|
| Description: | Title: Some users may be unable to drag and drop files to add references into Microsoft Copilot Notebooks
User impact: Users may be unable to drag and drop files to add references into Copilot Notebooks.
More info: Affected users can avoid the issue by referencing files from their local PC by choosing the ‘Upload from this device’ icon to the right of the search bar. To reference files stored in OneDrive or SharePoint, affected users can use search or choose the cloud icon to the far right from the search bar.
Current status: We identified that an update intended to optimize the service contains an error that’s resulting in this issue. We’ve reverted this change to relieve impact and anticipate that this process will be complete by our next scheduled update.
Scope of impact: Users attempting to drag and drop files to add references into Copilot Notebooks may be unable to do so.
Start time: Thursday, July 9, 2026, at 5:54 PM UTC
Root cause: An update intended to optimize the service contains an error that’s resulting in this issue.
Next update by: Friday, July 24, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Jul 20 18:17:23 2026 |
|---|
| Description: | Title: Some users may be unable to drag and drop files to add references into Microsoft Copilot Notebooks
User impact: Users may be unable to drag and drop files to add references into Copilot Notebooks.
More info: Affected users can avoid the issue by referencing files from their local PC by choosing the ‘Upload from this device’ icon to the right of the search bar. To reference files stored in OneDrive or SharePoint, affected users can use search or choose the cloud icon to the far right from the search bar.
Current status: We're investigating a potential issue with Copilot Notebooks and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1437424 - Issues accessing or using Microsoft 365 services routed through the North America region.
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 23 10:44:00 2026 |
|---|
| End Time: | Thu Jul 23 14:26:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 23 18:37:00 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 23 16:05:38 2026 |
|---|
| Description: | Title: Issues accessing or using Microsoft 365 services routed through the North America region.
User impact: Users may have experienced issues accessing or using Microsoft 365 services routed through the North America region.
More info: We've confirmed that the issue may have affected multiple Microsoft 365 services, including but not limited to:
-Microsoft OneDrive: Intermittent connection issues.
-SharePoint Online: Intermittent connection issues. Some users were receiving “Something went wrong” errors.
-Microsoft Teams: Degraded chat functionality, including images not loading. Additionally, real-time voice apps reporting and historical reporting were not functioning as expected.
-Copilot Chat: Intermittent delays using Copilot Chat and failures in query actions.
-Microsoft 365 Admin Center: Latency and intermittent inability to access features
-Power Automate: Automate flows not loading.
-Microsoft Loop: Unable to open or load Loop pages.
-Microsoft Purview: Degraded Purview DLP Agent response time. eDiscovery and Data -Security Investigations failures when submitting new jobs and delays in processing existing jobs. Additionally, admins may have been unable to view their policies or navigate in the Purview portal. Retries may have succeed.
-Fabric/Power BI: Users in the West US region may have encountered issues accessing Publish to Web reports. Some users in Europe and Asia Pacific regions may also have been intermittently delayed when accessing Fabric artifacts due to service dependencies in West US.
-Power Apps: Users may have experienced some issues accessing the Power Apps Portal and may also have experienced Canvas Apps not loading and data sources failing to connect.
-Copilot Studio: Users may have been unable to load the Copilot Studio Portal and data sources may also have failed to connect.
-Windows 365: Users may have been unable to select a non-English (United States) language for their Cloud PC post provisioning. They could have tried reprovisioning and language selection again and it may have succeeded on the retry.
- Microsoft Defender: Users may have experienced delays receiving responses from Microsoft Defender Experts. Additionally, investigations and workflows handled by Defender Experts may have been delayed. Furthermore, any remediations that fired via Threat Explorer and Advanced Hunting may have failed. Admins may have to re-trigger remediations manually from Threat Explorer and Advanced Hunting.
Final status: We’ve completed reverting the networking update and confirmed through service telemetry and customer reports that this issue is resolved.
Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may have been impacted. Users from other regions who were served by this infrastructure may also have experienced impact.
Start time: Thursday, July 23, 2026, at 2:44 PM UTC
End time: Thursday, July 23, 2026, at 6:26 PM UTC
Preliminary root cause: A recent update to a portion of network infrastructure in the US West region introduced a misconfiguration which interrupted the process by which IP ranges connect requests with downstream services, leading to impact.
Next steps:
-We’re assessing our traffic routing change processes to ensure similar changes don’t introduce future issues.
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 15:00:21 2026 |
|---|
| Description: | Title: Issues accessing or using Microsoft 365 services routed through the North America region.
User impact: Users may experience issues accessing or using Microsoft 365 services routed through the North America region.
More info: We've confirmed that the issue may affect multiple Microsoft 365 services, including but not limited to:
- Microsoft OneDrive: Intermittent connection issues.
- SharePoint Online: Intermittent connection issues. Some users are receiving “Something went wrong” errors.
- Microsoft Teams: Degraded chat functionality, including images not loading. Additionally, real-time voice apps reporting and historical reporting are not functioning as expected.
- Copilot Chat: Intermittent delays using Copilot Chat and failures in query actions.
- Microsoft 365 Admin Center: Latency and intermittent inability to access features
- Power Automate: Automate flows not loading.
- Microsoft Loop: Unable to open or load Loop pages.
- Microsoft Purview: Degraded Purview DLP Agent response time. eDiscovery and Data Security Investigations failures when submitting new jobs and delays in processing existing jobs. Additionally, admins may be unable to view their policies or navigate in the Purview portal. Retries may succeed.
- Fabric/Power BI: Users in the West US region may encounter issues accessing Publish to Web reports. Some users in Europe and Asia Pacific regions may also be intermittently delayed when accessing Fabric artifacts due to service dependencies in West US.
-Power Apps: Users may experience some issues accessing the Power Apps Portal and may also experience Canvas Apps not loading and data sources failing to connect.
-Copilot Studio: Users may be unable to load the Copilot Studio Portal and data sources may also fail to connect.
-Windows 365: Users may be unable to select a non-English (United States) language for their Cloud PC post provisioning. They can try reprovisioning and language selection again and it may succeed on retry.
Current status: We’ve completed reverting the networking update, and our telemetry indicates impact is resolved for the vast majority of users. We're reviewing all known impact scenarios and monitoring for a period of time to confirm resolution for all affected environments.
Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted. Users from other regions who are served by this infrastructure may also experience impact.
Start time: Thursday, July 23, 2026, at 2:44 PM UTC
Next update by: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 14:36:02 2026 |
|---|
| Description: | We've confirmed that our networking change reversion has completed, and our telemetry indicates that our service has recovered following this action. We're closely monitoring our telemetry and reaching out to sample affected users to validate resolution while we evaluate what other actions may be needed.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jul 23 14:05:19 2026 |
|---|
| Description: | Title: Issues accessing or using Microsoft 365 services routed through the North America region.
User impact: Users experiencing issues accessing or using Microsoft 365 services routed through the North America region.
More info: We've confirmed that the issue may affect multiple Microsoft 365 services, including but not limited to:
- Microsoft OneDrive: Intermittent connection issues.
- SharePoint Online: Intermittent connection issues. Some users are receiving “Something went wrong” errors.
- Microsoft Teams: Degraded chat functionality, including images not loading. Additionally, real-time voice apps reporting and historical reporting are not functioning as expected.
- Copilot Chat: Intermittent delays using Copilot Chat and failures in query actions.
- Microsoft 365 Admin Center: Latency and intermittent inability to access features
- Power Automate: Automate flows not loading.
- Microsoft Loop: Unable to open or load Loop pages.
- Microsoft Purview: Degraded Purview DLP Agent response time. eDiscovery and Data Security Investigations failures when submitting new jobs and delays in processing existing jobs.
- Fabric/Power BI: Users in the West US region may encounter issues accessing Publish to Web reports. Some users in Europe and Asia Pacific regions may also be intermittently delayed when accessing Fabric artifacts due to service dependencies in West US.
-Power Apps: Users may experience some issues accessing the Power Apps Portal and may also experience Canvas Apps not loading and data sources failing to connect.
-Copilot Studio: Users may be unable to load the Copilot Studio Portal and data sources may also fail to connect.
-Windows 365: Users may be unable to select a non-English (United States) language for their Cloud PC post provisioning. They can try reprovisioning and language selection again and it may succeed on retry.
Current status: Our service telemetry indicates that rerouting traffic has provided some relief across affected services. We’re continuing to perform targeted traffic-routing actions while we revert the networking change mentioned in our last update. We're monitoring our telemetry and working directly with some impacted customers to ensure our actions are effectively addressing impact. We expect the configuration change reversion to complete by our next scheduled update, and we’re evaluating other pathways to expedite recovery.
Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted. Users from other regions who are served by this infrastructure may also experience impact.
Start time: Thursday, July 23, 2026, at 2:44 PM UTC
Next update by: Thursday, July 23, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:52:54 2026 |
|---|
| Description: | We've identified a recent network configuration change that may be contributing to impact. We're reverting this change in parallel to our ongoing traffic rerouting actions.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jul 23 13:04:04 2026 |
|---|
| Description: | We're scaling traffic rerouting efforts up across our service infrastructure and are seeing indications of increasing relief in our telemetry. We're implementing additional mitigation measures alongside these actions to improve service availability and expedite resolution for affected users.
This quick update is designed to give the latest information on this issue.
Next update by: Thursday, July 23, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 12:47:24 2026 |
|---|
| Description: | Title: Issues accessing or using Microsoft 365 services in the North America region.
User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region.
More info: We've confirmed that multiple Microsoft 365 services are degraded, including but not limited to:
-Microsoft OneDrive - Access to OneDrive is intermittent.
-SharePoint Online - Error message, “Something went wrong”
-Microsoft Teams - Degraded chat functionality, including images not loading.
-Microsoft 365 Admin Center - Admin Center is loading slowly or not at all.
-Power Automate - Automate flows not loading.
-Copilot Chat - Intermittent delays or failures in any Copilot Chat action and query.
-Microsoft Loop - Unable to open or load Loop pages.
Current status: We performed traffic rerouting for some of the affected infrastructure and our initial telemetry indicates that these actions have contributed to partial recovery for some users. We're scaling up our rerouting efforts while continuing to evaluate additional mitigation actions.
Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted, though users located or served from other regions may also experience impact.
Start time: Thursday, July 23, 2026, at 2:44 PM UTC
Next update by: Thursday, July 23, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 12:18:22 2026 |
|---|
| Description: | We've identified alternate network paths and are validating the best next steps to improve service availability. We're continuing to monitor telemetry to assess whether we can take additional actions to expedite recovery for impacted users.
This quick update is designed to give the latest information on this issue.
Next update by: Thursday, July 23, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 12:04:48 2026 |
|---|
| Description: | Title: Issues accessing or using Microsoft 365 services in the North America region.
User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region.
More info: We've confirmed that the issue may affect multiple Microsoft 365 services, including but not limited to:
- OneDrive for Business
- SharePoint Online
- Microsoft Teams
- Microsoft365 Admin Center
- Power Automate
Current status: We’ve identified specific network paths as a focus area and are using diagnostic data from affected infrastructure to determine the source of impact and plan mitigation actions.
Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted.
Start time: Thursday, July 23, 2026, at 2:44 PM UTC
Next update by: Thursday, July 23, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 11:57:23 2026 |
|---|
| Description: | Title: Issues accessing or using Microsoft 365 services in the North America region.
User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region.
More info: We've confirmed that the issue may affect multiple Microsoft 365 services, including but not limited to:
- SharePoint Online
- Microsoft Teams
- Microsoft365 Admin Center
- Power Automate
Current status: We’ve identified specific network paths as a focus area and are using diagnostic data from affected infrastructure to determine the source of impact and plan mitigation actions.
Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted.
Start time: Thursday, July 23, 2026, at 2:44 PM UTC
Next update by: Thursday, July 23, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 11:44:33 2026 |
|---|
| Description: | Title: Issues accessing or using Microsoft 365 services in the North America region
User impact: Users may be experiencing issues accessing or using Microsoft 365 services in the North America region.
Current status: We are continuing our investigation and are reviewing recent changes for potential correlation while we analyze service telemetry and available diagnostic data.
Scope of impact: Users accessing Microsoft 365 services through affected network paths in the North America region may be impacted.
Start time: Thursday, July 23, 2026, at 2:44 PM UTC
Next update by: Thursday, July 23, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 11:15:50 2026 |
|---|
| Description: | Title: Investigating user reports of Microsoft 365 issues
User impact: We don't have detail 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. We'll provide an update in 30 minutes.
|
|---|
|
EX1437461 - Users may be unable to access their mailbox in Exchange Online through multiple connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 23 14:00:00 2026 |
|---|
| End Time: | Thu Jul 23 14:30:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 23 18:08:05 2026 |
|---|
| Root Cause: | Impact was the result of a scheduled maintenance event to perform a dot build upgrade on a portion of Exchange Online infrastructure.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 23 17:08:22 2026 |
|---|
| Description: | Title: Users may be unable to access their mailbox in Exchange Online through multiple connection methods
User impact: Users may have been unable to access their mailbox in Exchange Online through multiple connection methods.
More info: Impacted connection methods included:
- Outlook on the web
- Representational State Transfer (REST) API
- Messaging API (MAPI)
Final status: We've confirmed that impact was the result of a scheduled maintenance event to perform a dot build upgrade on a portion of Exchange Online infrastructure. After this maintenance completed, the service self-recovered and impact was remediated.
Scope of impact: This issue may have affected users in North America attempting to access their mailbox in Exchange Online.
Start time: Thursday, July 23, 2026, at 6:00 PM UTC
End time: Thursday, July 23, 2026, at 6:30 PM UTC
Root cause: Impact was the result of a scheduled maintenance event to perform a dot build upgrade on a portion of Exchange Online infrastructure.
Next steps:
- We're reviewing why this scheduled maintenance occurred during the impacting time and determine opportunities to reduce impact in future scheduled maintenance events.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 23 16:25:20 2026 |
|---|
| Description: | Title: Users may be unable to access their mailbox in Exchange Online through multiple connection methods
User impact: Users may be unable to access their mailbox in Exchange Online through multiple connection methods.
More info: Impacted connection methods include:
- Outlook on the web
- Representational State Transfer (REST) API
- Messaging API (MAPI)
Current status: We're reviewing service health telemetry information to identify and isolate any errors potentially contributing to impact to assist our investigation into the source of this issue.
Scope of impact: This issue may affect users in North America attempting to access their mailbox in Exchange Online.
Next update by: Thursday, July 23, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 14:29:42 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.
|
|---|
|
SP1425697 - Some users' document libraries and list views using multiple group filters may have not displayed results in SharePoint
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 9 07:12:00 2026 |
|---|
| End Time: | Thu Jul 16 01:50:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 23 16:56:29 2026 |
|---|
| Root Cause: | A recent change, intended to improve defense-in-depth and resiliency, contained a code bug for the service component responsible for rendering double grouped views in SharePoint Online document libraries and lists, causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 23 16:56:29 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jul 20 13:15:06 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 16 12:02:15 2026 |
|---|
| Description: | Title: Some users' document libraries and list views using multiple group filters may have not displayed results in SharePoint
User impact: Users' document libraries and list views using multiple group filters may have not displayed results in SharePoint.
More info: Specifically, impacted users reported that document libraries and list views using both Primary and Secondary grouping may have not displayed the full or expected results.
In Classic view settings, a user would have needed to apply a 'First group by' and then a 'Then group by' to become impacted.
Final status: The deployment has completed and we've confirmed that the issue is resolved.
Scope of impact: Some users attempting to view document libraries and list views using multiple group filters may have been impacted.
Start time: Thursday, July 9, 2026, at 11:12 AM UTC
End time: Thursday, July 16, 2026, at 5:50 AM UTC
Root cause: A recent change, intended to improve defense-in-depth and resiliency, contained a code bug for the service component responsible for rendering double grouped views in SharePoint Online document libraries and lists, causing impact.
Specifically, a new section of code was implemented and was supposed to replace an existing code line. However, a miss in the code implementation process resulted in the initial code line remaining after the change. These code sections interacted together and resulted in an output where the request flows for combined “group by” field scenarios started to look up a specific parameter value that did not exist. As the required parameter could not be found, the requests failed and resulted in impact to multiple “grouped by” views.
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 Jul 15 12:53:56 2026 |
|---|
| Description: | Title: Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online
User impact: Users' document libraries and list views using multiple group filters may not display results in SharePoint Online.
More info: Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping may not display the full or expected results.
Current status: The fix deployment has reached over 99 percent saturation, and the majority of users should no longer be impacted. We're continuing to deploy the fix to the remaining infrastructure, and expect this to complete before our next scheduled communication update.
Scope of impact: Some users attempting to view document libraries and list views using multiple group filters may be impacted.
Start time: Thursday, July 9, 2026, at 3:47 PM UTC
Root cause: A recent change contained a code bug for the service component responsible for rendering double grouped views in SharePoint Online document libraries and lists, causing impact.
Next update by: Thursday, July 16, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Jul 14 13:51:51 2026 |
|---|
| Description: | Title: Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online
User impact: Users' document libraries and list views using multiple group filters may not display results in SharePoint Online.
More info: Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping may not display the full or expected results.
Current status: The deployment saturation has reached 94% and is progressing as expected. Users will start to experience relief as soon as the infrastructure they're hosted on has received the deployment.
Scope of impact: Some users attempting to view document libraries and list views using multiple group filters may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, July 15, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Jul 14 07:11:13 2026 |
|---|
| Description: | Title: Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online
User impact: Users' document libraries and list views using multiple group filters may not display results in SharePoint Online.
More info: Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping may not display the full or expected results.
Current status: The fix has deployed to approximately 89% of the impacted environment. We're monitoring as the fix continues to propagate to the remaining environments.
Scope of impact: Some users attempting to view document libraries and list views using multiple group filters may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, July 15, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jul 13 12:56:55 2026 |
|---|
| Description: | Title: Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online
User impact: Users' document libraries and list views using multiple group filters may not display results in SharePoint Online.
More info: Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping may not display the full or expected results.
Current status: We've validated the fix for the issue works as expected and the deployment is progressing across the affected environments. We'll continue to monitor the deployment progress and validate recovery as the fix continues to propagate through the service.
Scope of impact: Some users attempting to view document libraries and list views using multiple group filters may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, July 14, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jul 13 07:25:08 2026 |
|---|
| Description: | Title: Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online
User impact: Users' document libraries and list views using multiple group filters may not display results in SharePoint Online.
More info: Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping may not display the full or expected results.
Current status: We’ve identified that a recent change to the service component responsible for rendering grouped views in SharePoint Online document libraries and lists is causing impact. We’ve developed a fix and are validating that it resolves the issue while we determine the safest deployment approach.
Scope of impact: Some users attempting to view document libraries and list views using multiple group filters may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, July 13, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jul 13 04:17:13 2026 |
|---|
| Description: | Title: Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online
User impact: Users' document libraries and list views using multiple group filters may not display results in SharePoint Online.
More info: Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping may not display the full or expected results.
Current status: We're continuing to analyze network logs to validate that a potential regression within the document libraries codebase is contributing to impact.
Scope of impact: Some users attempting to view document libraries and list views using multiple group filters may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, July 13, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jul 13 02:57:45 2026 |
|---|
| Description: | Title: Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online
User impact: Users' document libraries and list views using multiple group filters may not display results in SharePoint Online.
More info: Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping may not display the full or expected results.
Current status: We've identified a potential regression within the document libraries codebase and are currently analysing network logs to validate our hypothesis.
Scope of impact: Some users attempting to view document libraries and list views using multiple group filters may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, July 13, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Jul 13 02:44:09 2026 |
|---|
| Description: | Title: Users' SharePoint Online document libraries and list views using multiple group filters aren't displaying full results
User impact: Users' SharePoint Online document libraries and list views using multiple group filters aren't displaying full results.
More info: Specifically, impacted users report that document libraries and list views using both Primary and Secondary grouping don't display the full or expected results.
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.
|
|---|
|
FL1437452 - Flow management and manual invocation operations are failing
| Status: | serviceRestored |
|---|
| 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: | Thu Jul 23 16:42:18 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| 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 operation 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: | serviceRestored |
|---|
| 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: | Thu Jul 23 16:36:28 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| 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.
|
|---|
|
CW1436954 - Some users may see an error when sending messages from BizChat and the BizChat side pane in Microsoft 365 apps.
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 22 23:19:34 2026 |
|---|
| End Time: | Thu Jul 23 02:11:58 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 23 02:13:35 2026 |
|---|
| Root Cause: | A recent update intended to enable an updated AI model used to process chat requests and generate responses, Opus 4.8, caused an unexpected influx of service requests that led to the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 23 02:13:32 2026 |
|---|
| Description: | Title: Some users may see an error when sending messages from BizChat and the BizChat side pane in Microsoft 365 apps.
User impact: Some users may have seen an error when sending messages from BizChat and the BizChat side pane in Microsoft 365 apps.
More info: More info: Affected Microsoft 365 apps included:
Outlook on the web
Outlook desktop
Microsoft Teams
Affected users may have seen an error stating “something went wrong.”
This issue affected users that had selected the Opus 4.8 model.
Final status: We’ve determined that a recent update intended to enable an updated AI model used to process chat requests and generate responses, Opus 4.8, caused an unexpected influx of service requests that led to the impact. We’ve reverted the offending update and confirmed from service telemetry that this issue is resolved.
Scope of impact: Some users located in the Asia Pacific or South America regions sending messages from BizChat and the BizChat side pane from an affected M365 app may have been impacted.
Start time: Thursday, July 23, 2026, at 1:23 AM UTC
End time: Thursday, July 23, 2026, at 4:38 AM UTC
Root cause: A recent update intended to enable an updated AI model used to process chat requests and generate responses, Opus 4.8, caused an unexpected influx of service requests that led to the impact.
Next steps: We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 22 23:43:58 2026 |
|---|
| Description: | Title: Some users may see an error when sending messages through the BizChat side pane in multiple M365 apps
User impact: Some users may see an error when sending messages through the BizChat side pane in multiple M365 apps.
More info: Affected M363 apps include, but may not be limited to:
Outlook on the web
Outlook desktop
Microsoft Teams
Affected users may see an error stating “something went wrong.”
Current status: We're investigating a potential issue in which some users may see an error when sending messages through the BizChat side pane in Outlook on the web and Outlook desktop and checking for impact to your organization. We'll provide an update within 30 minutes.
Scope of impact: Some users located in the Asia Pacific or South America regions sending messages from the BizChat side pane from an affected M365 app may see an error stating “something went wrong.” This information may be updated as our investigation continues.
Next update by: Thursday, July 23, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Wed Jul 22 23:35:21 2026 |
|---|
| Description: | Title: Some users may receive an error when sending messages with the Microsoft Copilot Chat side pane
User impact: Users may receive an error when sending messages with the Microsoft Copilot Chat side pane.
More info: Specifically, when attempting to send messages within the Copilot Chat side pane in Outlook on the web and Outlook desktop users receive an error that states, “Something went wrong.”
Current status: We're investigating a potential issue in which some users may see an error when sending messages through the Copilot Chat side pane in Outlook on the web and Outlook desktop and are checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1436888 - Admins may be unable to enforce Data Loss Prevention (DLP) policies in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 22 03:00:00 2026 |
|---|
| End Time: | Thu Jul 23 00:20:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 23 00:34:48 2026 |
|---|
| Root Cause: | An authentication configuration change made to the service infrastructure affected the enforcement of DLP policies, which led to impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 23 00:32:03 2026 |
|---|
| Description: | Title: Admins may be unable to enforce Data Loss Prevention (DLP) policies in Microsoft Teams
User impact: Admins may have been unable to enforce DLP policies in Microsoft Teams.
More info: DLP policies configured in Microsoft Purview successfully detected policy matches, but the expected enforcement actions weren't being applied within Microsoft Teams. As a result, messages that should have been blocked may have continued to be delivered. This applied to all Microsoft Teams channels.
Final status: We've validated through our testing that an authentication configuration change made to the service infrastructure affected the enforcement of DLP policies, which led to impact. We've successfully deployed our fix to roll back this configuration change in all environments and confirmed that impact has been resolved.
Scope of impact: Any admin may have been impacted and may have been unable to enforce DLP policies in Microsoft Teams.
Start time: Monday, June 22, 2026, at 7:00 AM UTC
End time: Thursday, July 23, 2026, at 4:20 AM UTC
Root cause: An authentication configuration change made to the service infrastructure affected the enforcement of DLP policies, which led to impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to DLP policies 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: | Wed Jul 22 22:26:28 2026 |
|---|
| Description: | Title: Admins may be unable to enforce Data Loss Prevention (DLP) policies in Microsoft Teams
User impact: Admins may be unable to enforce DLP policies in Microsoft Teams.
More info: DLP policies configured in Microsoft Purview successfully detect policy matches, but the expected enforcement actions aren't being applied within Microsoft Teams. As a result, messages that should be blocked may continue to be delivered. This applies to all Microsoft Teams channels.
Current status: We're continuing to validate our potential fix and so far, we're seeing positive results. We're continuing to test this fix to ensure it fully resolves the issue before we begin expanding the fix deployment to all impacted environments.
Scope of impact: Any admin may be impacted and may be unable to enforce DLP policies in Microsoft Teams. This section may be updated as our investigation continues.
Next update by: Thursday, July 23, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Wed Jul 22 20:41:10 2026 |
|---|
| Description: | Title: Admins may be unable to enforce Data Loss Prevention (DLP) policies in Microsoft Teams
User impact: Admins may be unable to enforce DLP policies in Microsoft Teams.
More info: DLP policies configured in Microsoft Purview successfully detect policy matches, but the expected enforcement actions aren't being applied within Microsoft Teams. As a result, messages that should be blocked may continue to be delivered. This applies to all Microsoft Teams channels.
Current status: We've identified an issue with DLP policies in Microsoft Teams not being enforced correctly. We’ve investigated the impacted service environment and identified a token error in the service infrastructure logs, and we believe we've correlated the error with a recent authentication configuration change that may be causing impact. We've developed a potential fix, and we’re validating this fix in a small testing environment to confirm this fix addresses the impact fully.
Scope of impact: Any admin may be impacted and may be unable to enforce DLP policies in Microsoft Teams. This section may be updated as our investigation continues.
Next update by: Thursday, July 23, 2026, at 2:30 AM UTC
|
|---|
|
CP1430225 - We’ve identified an issue with Microsoft 365 Copilot spending alerts
| Status: | investigating |
|---|
| Start Time: | Thu Jul 16 18:27:46 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 22 15:36:27 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 16 18:29:25 2026 |
|---|
| Description: | Title: We’ve identified an issue with Microsoft 365 Copilot spending alerts
User impact: If action isn’t taken, admins may see incorrect spending alerts.
Current status: We’ve detected an issue with the Microsoft 365 Copilot service affecting spending alerts. Impact is specific to the alert notification, and set limits are honored as expected.
When an admin configured a spending alert on a policy, the value didn’t persist and would reset to a different value, so the alert threshold wasn’t saved as expected.
Please review the recommendations below to prevent any service issues.
Expiration message: This communication will expire in 14 days, and is scheduled to remain active for the full duration.
|
|---|
|
EX1428537 - Some users may be unable to view mailbox storage data in Outlook and Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jul 11 20:00:00 2026 |
|---|
| End Time: | Tue Jul 21 20:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 22 11:22:05 2026 |
|---|
| Root Cause: | A recent service build introduced an unsupported property into mailbox statistics data returned by a backend process. When the service attempted to retrieve mailbox storage information, the unsupported property caused the request to fail and prevented mailbox storage data from being displayed, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 22 11:18:10 2026 |
|---|
| Description: | Title: Some users may be unable to view mailbox storage data in Outlook and Outlook on the web
User impact: Users may have been unable to view mailbox storage data in Outlook and Outlook on the web.
More info: Affected users were shown the error message, "Storage data is temporarily unavailable," when trying to view mailbox storage data for multiple mailboxes.
Final status: We've validated that our code fix has fully deployed throughout the affected environments and has successfully remediated all impact.
Scope of impact: Some users attempting to view mailbox storage data in Outlook and Outlook on the web may have been impacted.
Start time: Sunday, July 12, 2026, at 12:00 AM UTC
End time: Wednesday, July 22, 2026, at 12:00 AM UTC
Root cause: A recent service build introduced an unsupported property into mailbox statistics data returned by a backend process. When the service attempted to retrieve mailbox storage information, the unsupported property caused the request to fail and prevented mailbox storage data from being displayed, which resulted in impact.
Next steps:
- We're reviewing our service build validation and implementation processes to improve how we detect potential unsupported properties and prevent similar mailbox storage data issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 20 13:37:34 2026 |
|---|
| Description: | Title: Some users may be unable to view mailbox storage data in Outlook and Outlook on the web
User impact: Users may be unable to view mailbox storage data in Outlook and Outlook on the web.
More info: Affected users are shown the following error message "Storage data is temporarily unavailable" when trying to view mailbox storage data for multiple mailboxes.
Current status: Our fix has completed approximately 94 percent of its deployment within the affected environment, and our timeline projects it will have completed and that the impact will be remediated by our next scheduled communication update.
Scope of impact: Some users attempting to view mailbox storage data in Outlook and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service build introduced an unsupported property into mailbox statistics data returned by a backend process. When the service attempted to retrieve mailbox storage information, the unsupported property caused the request to fail and prevented mailbox storage data from being displayed.
Next update by: Thursday, July 23, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jul 17 14:19:38 2026 |
|---|
| Description: | Title: Some users may be unable to view mailbox storage data in Outlook and Outlook on the web
User impact: Users may be unable to view mailbox storage data in Outlook and Outlook on the web.
More info: Affected users are shown the following error message "Storage data is temporarily unavailable" when trying to view mailbox storage data for multiple mailboxes.
Current status: We've completed validation and initiated the release of the fix. Currently at approximately 30 percent, we're monitoring as it progresses and expect to have a complete remediation timeline by the next scheduled update.
Scope of impact: Some users attempting to view mailbox storage data in Outlook and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service build introduced an unsupported property into mailbox statistics data returned by a backend process. When the service attempted to retrieve mailbox storage information, the unsupported property caused the request to fail and prevented mailbox storage data from being displayed.
Next update by: Monday, July 20, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jul 16 18:02:00 2026 |
|---|
| Description: | Title: Some users may be unable to view mailbox storage data in Outlook and Outlook on the web
User impact: Users may be unable to view mailbox storage data in Outlook and Outlook on the web.
More info: Affected users are shown the following error message "Storage data is temporarily unavailable" when trying to view mailbox storage data for multiple mailboxes.
Current status: We're continuing to validate our code fix as it’s being deployed through our internal test environment and monitor service telemetry before proceeding with deployment to the affected environments to help ensure successful remediation. Once available, we'll provide a resolution timeline.
Scope of impact: Some users attempting to view mailbox storage data in Outlook and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service build introduced an unsupported property into mailbox statistics data returned by a backend process. When the service attempted to retrieve mailbox storage information, the unsupported property caused the request to fail and prevented mailbox storage data from being displayed.
Next update by: Friday, July 17, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jul 15 09:03:13 2026 |
|---|
| Description: | Title: Some users may be unable to view mailbox storage data in Outlook and Outlook on the web
User impact: Users may be unable to view mailbox storage data in Outlook and Outlook on the web.
More info: Affected users are shown the following error message "Storage data is temporarily unavailable" when trying to view mailbox storage data for multiple mailboxes.
Current status: We've identified that a recent service build introduced an unsupported property into mailbox statistics data. When the service attempted to retrieve mailbox storage information, the unsupported property caused the request to fail and prevented mailbox storage data from being displayed. We've deployed a code fix to remove the unsupported property and are monitoring service telemetry to verify its success in fixing the issue.
Scope of impact: Some users attempting to view mailbox storage data in Outlook and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service build introduced an unsupported property into mailbox statistics data returned by a backend process. When the service attempted to retrieve mailbox storage information, the unsupported property caused the request to fail and prevented mailbox storage data from being displayed.
Next update by: Wednesday, July 22, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Wed Jul 15 07:37:17 2026 |
|---|
| Description: | Title: Some users may be unable to view mailbox storage data in Outlook and Outlook on the web
User impact: Users may be unable to view mailbox storage data in Outlook and Outlook on the web.
More info: Users are shown the following error message "Storage data is temporarily unavailable" when trying to view mailbox storage data for multiple mailboxes.
Current status: We're reviewing support case details to determine our next troubleshooting steps.
Scope of impact: Some users attempting to view mailbox storage data in Outlook and Outlook on the web may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, July 15, 2026, at 1:30 PM UTC
|
|---|
|
EX1434354 - Some users' mailboxes may be incorrectly quarantined in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jul 19 18:00:00 2026 |
|---|
| End Time: | Tue Jul 21 18:05:33 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jul 21 18:14:21 2026 |
|---|
| Root Cause: | A recent infrastructure change caused excessive memory consumption which resulted in out-of-memory conditions and caused mailboxes to be incorrectly quarantined.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 21 18:14:17 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may have been incorrectly quarantined in Exchange Online.
More info: This issue blocked some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes received a Non-delivery Report (NDR).
Final status: We've further confirmed that the recent infrastructure change was the source of the excessive memory consumption which resulted in impact. We applied a fix that reversed this change and have confirmed impact was successfully remediated.
Scope of impact: Some users receiving email through Exchange Online may have been impacted.
Start time: Sunday, July 19, 2026, at 10:00 PM UTC
End time: Tuesday, July 21, 2026, at 9:30 PM UTC
Root cause: A recent infrastructure change caused excessive memory consumption which resulted in out-of-memory conditions and caused mailboxes to be incorrectly quarantined.
Next steps:
- We're reviewing options to improve impact detection when testing and validating similar infrastructure changes to better prevent future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 21 14:17:56 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue blocks some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes receive a Non-delivery Report (NDR).
Current status: After our additional analysis into updated diagnostic data, we've isolated a recent infrastructure change that is believed to be producing the impacting memory consumption. We're further analyzing the change to confirm our findings, and to determine our most expedient method for remediating the impact.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: Excessive memory consumption is resulting in out-of-memory conditions, causing affected mailboxes to be incorrectly quarantined.
Next update by: Tuesday, July 21, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jul 21 10:36:29 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue blocks some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes receive a Non-delivery Report (NDR).
Current status: We're continuing to collect and analyze diagnostic data to identify the point of failure and determine the most effective path to mitigation.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: Excessive memory consumption is resulting in out-of-memory conditions, causing affected mailboxes to be incorrectly quarantined.
Next update by: Tuesday, July 21, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jul 21 08:47:52 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue blocks some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes receive a Non-delivery Report (NDR).
Current status: We've determined that the configuration change was not successful in reducing resource consumption and improving service stability. We're collecting and analyzing diagnostic data to identify the point of failure and determine the next steps towards mitigation.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: Excessive memory consumption is resulting in out-of-memory conditions, causing affected mailboxes to be incorrectly quarantined.
Next update by: Tuesday, July 21, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue Jul 21 06:34:14 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue blocks some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes receive a Non-delivery Report (NDR).
Current status: We've deployed configuration changes to a subset of the affected infrastructure and are monitoring telemetry to determine their effectiveness in reducing resource consumption and improving service stability. Initial validation is expected as the changes take effect across the affected environment. In parallel, we're continuing to investigate the underlying cause of the elevated memory usage and assessing additional mitigation options should further action be required.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: Excessive memory consumption is resulting in out-of-memory conditions, causing affected mailboxes to be incorrectly quarantined.
Next update by: Tuesday, July 21, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Jul 21 04:54:48 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue blocks some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes receive a Non-delivery Report (NDR).
Current status: We've determined that affected mailboxes are being quarantined because servers are reaching out-of-memory conditions. We've enabled configuration changes on a subset of affected infrastructure to reduce processing concurrency and lower memory usage, and we're monitoring the affected infrastructure to determine whether these changes are successfully mitigating impact.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: Excessive memory consumption is resulting in out-of-memory conditions, causing affected mailboxes to be incorrectly quarantined.
Next update by: Tuesday, July 21, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Jul 20 23:35:56 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Some users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue blocks some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes receive a Non-delivery Report (NDR).
Current status: We've isolated the impact to a specific set of corresponding processes responsible for item indexing. We're rebalancing the traffic load caused by these parallel processes in an effort to remediate user impact.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, July 21, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Jul 20 21:22:20 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Some users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue blocks some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes receive a Non-delivery Report (NDR).
Current status: In the process of manually adding further affected mailboxes to the allow list in an effort to provide efficient mitigation for impacted users, we've continued to detect reoccurrences of the automatic mailbox quarantine processes. Our investigation into these events has allowed us to identify an ongoing issue with traffic flow optimization within the affected portions of service infrastructure. We're continuing to investigate this behavior in order to identify the cause and to determine our options for mitigation.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, July 21, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Jul 20 19:00:10 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Some users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue blocks some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes receive a Non-delivery Report (NDR).
Current status: We've identified that an issue occurring on some portions of service infrastructure which process and store email messages within the service environment is resulting in affected users' mailboxes being incorrectly quarantined. We're continuing to analyze service resources to isolate the underlying root cause and determine our next steps towards remediation.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, July 21, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Jul 20 17:49:58 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Some users' mailboxes may be incorrectly quarantined in Exchange Online.
More info: This issue blocks some users from receiving email messages due to their mailboxes incorrectly being quarantined, and senders to these mailboxes receive a Non-delivery Report (NDR).
Current status: Our investigation identified that the mailboxes were automatically quarantined due to faulty outbound requests. We've manually added the affected mailboxes to the safe senders list, but we’ve confirmed with your representatives that one of the mailboxes is still impacted. We're investigating the behavior of this mailbox and the outbound requests in order to understand why this mailbox has remained quarantined.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, July 21, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Jul 20 16:42:42 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Some users' mailboxes may be incorrectly quarantined in Exchange Online.
Current status: We've identified an error code generated by this issue that indicates that the affected mailboxes are marked as quarantined. We're examining diagnostic information to understand why these mailboxes are impacted.
Scope of impact: Some users receiving email through Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, July 20, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Jul 20 16:17:16 2026 |
|---|
| Description: | Title: Some users' mailboxes may be incorrectly quarantined in Exchange Online
User impact: Some users' mailboxes may be incorrectly quarantined in Exchange Online.
Current status: We're investigating a potential issue with incorrect mailbox quarantining leading to message delivery failures in Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1434281 - Some users in Brazil may have been unable to access or use Microsoft Teams features
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 20 13:45:00 2026 |
|---|
| End Time: | Mon Jul 20 14:15:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jul 21 16:05:21 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 20 14:46:00 2026 |
|---|
| Description: | Title: Some users in Brazil may have been unable to access or use Microsoft Teams features
User impact: Users in Brazil may have been unable to access or use Microsoft Teams features.
Final status: While we were in the process of analyzing service availability dashboards to identify the cause of the reports of user impact in Brazil, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: This issue may have affected some users in Brazil accessing or using Microsoft Teams.
Start time: Monday, July 20, 2026, at 5:45 PM UTC
End time: Monday, July 20, 2026, at 6:15 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 20 14:19:50 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Teams in the Brazil region
User impact: We're checking for potential impact to your users.
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.
|
|---|
|
TM1435242 - Some users may experience delays receiving notifications for Teams Recap Podcasts in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 21 00:00:00 2026 |
|---|
| End Time: | Tue Jul 21 08:48:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 21 13:53:28 2026 |
|---|
| Root Cause: | A recent service update, which was intended to inform users that they could generate Teams Recap Podcasts, caused an unexpected influx in notifications which Microsoft Graph API was unable to process effectively, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 21 13:37:07 2026 |
|---|
| Description: | Title: Some users may experience delays receiving notifications for Teams Recap Podcasts in Microsoft Teams
User impact: Users may have experienced delays receiving notifications for Teams Recap Podcasts in Microsoft Teams.
More info: Users may have experienced delays receiving reminder notifications that prompted them to generate Teams Recap Podcasts. Notifications sent after a podcast had already been generated weren't impacted.
Final status: After analyzing service telemetry and recent updates, we've isolated that a recent service update, which was intended to inform users that they could generate Teams Recap Podcasts, caused an unexpected influx in notifications which Microsoft Graph API was unable to process effectively, resulting in impact. We've rolled back the offending update and validated after monitoring service telemetry that our actions successfully remediated impact.
Scope of impact: Impact is specific to users in North America and South America who were expecting to receive notifications for Teams Recap Podcasts in Microsoft Teams.
Start time: Tuesday, July 21, 2026, at 4:00 AM UTC
End time: Tuesday, July 21, 2026, at 12:48 PM UTC
Root cause: A recent service update, which was intended to inform users that they could generate Teams Recap Podcasts, caused an unexpected influx in notifications which Microsoft Graph API was unable to process effectively, resulting in impact.
Next steps: - We're analyzing the offending service update to isolate why the potential for impact wasn't caught during our internal update testing and validation phases. Simultaneously, we're validating why Microsoft Graph API was unable to handle the influx of requests to determine what performance optimizations we can implement to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 21 08:38:11 2026 |
|---|
| Description: | Title: Some users may experience delays receiving notifications for Teams Recap Podcasts in Microsoft Teams
User impact: Users may experience delays receiving notifications for Teams Recap Podcasts in Microsoft Teams.
More info: Users may experience delays receiving reminder notifications that prompt them to generate Teams Recap Podcasts. Notifications sent after a podcast has already been generated aren't impacted.
Current status: We're reviewing service telemetry to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact is specific to users in North America and South America who are attempting to receive notifications for Teams Recap Podcasts in Microsoft Teams.
Next update by: Tuesday, July 21, 2026, at 6:30 PM UTC
|
|---|
|
OP1432645 - Microsoft 365 Apps usage reports from the Microsoft 365 admin center may be delayed for admins and users
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jul 18 20:00:00 2026 |
|---|
| End Time: | Mon Jul 20 17:06:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 20 17:23:36 2026 |
|---|
| Root Cause: | An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center was causing Microsoft 365 Apps usage report delays.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 20 17:23:17 2026 |
|---|
| Description: | Title: Microsoft 365 Apps usage reports from the Microsoft 365 admin center may be delayed for admins and users
User impact: Microsoft 365 Apps usage reports from the Microsoft 365 admin center may have been delayed for admins and users.
Final status: We've completed processing the backlog of impacted Microsoft 365 Apps usage reports and validated that admins are now able to view up to date usage reports as expected.
Scope of impact: This issue may have potentially affected any admin attempting to view Microsoft 365 Apps usage reports in the Microsoft 365 admin center.
Start time: Sunday, July 19, 2026, at 12:00 AM UTC
End time: Monday, July 20, 2026, at 9:06 PM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center was causing Microsoft 365 Apps usage report delays.
Next steps:
- We're analyzing the affected data pipeline to isolate what additional performance optimizations we can implement to improve the resiliency of our service to ensure similar imapct scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 20 13:50:11 2026 |
|---|
| Description: | Title: Microsoft 365 Apps usage reports from the Microsoft 365 admin center may be delayed for admins and users
User impact: Microsoft 365 Apps usage reports from the Microsoft 365 admin center may be delayed for admins and users.
Current status: We've applied a fix to correct the issues with the pipeline for our upstream data source and the delayed reports for the majority of affected admins and users have completed processing except for those that're located in Europe. We're continuing to monitor as the remaining data is processed.
Scope of impact: This issue may potentially affect any admin attempting to view Microsoft 365 Apps usage reports in the Microsoft 365 admin center.
Start time: Sunday, July 19, 2026, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Microsoft 365 Apps usage report delays.
Next update by: Monday, July 20, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Sun Jul 19 17:18:21 2026 |
|---|
| Description: | Title: Microsoft 365 Apps usage reports from the Microsoft 365 admin center may be delayed for admins and users
User impact: Microsoft 365 Apps usage reports from the Microsoft 365 admin center may be delayed for admins and users.
Current status: We're continuing to address our upstream data source pipeline problems to remediate the impact. We're expecting an updated timeline for our mitigation efforts will be available by our next scheduled communication update.
Scope of impact: This issue may potentially affect any admin attempting to view Microsoft 365 Apps usage reports in the Microsoft 365 admin center.
Start time: Sunday, July 19, 2026, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Microsoft 365 Apps usage report delays.
Next update by: Monday, July 20, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Sat Jul 18 21:39:13 2026 |
|---|
| Description: | Title: Microsoft 365 Apps usage reports from the Microsoft 365 admin center may be delayed for admins and users
User impact: Microsoft 365 Apps usage reports from the Microsoft 365 admin center may be delayed for admins and users.
Current status: We've identified an issue in our telemetry indicating that report data is delayed for Microsoft 365 Apps usage reports. We're working with our upstream data source to remediate the impact.
Scope of impact: This issue may potentially affect any admin attempting to view Microsoft 365 Apps usage reports in the Microsoft 365 admin center.
Start time: Sunday, July 19, 2026, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Microsoft 365 Apps usage report delays.
Next update by: Sunday, July 19, 2026, at 11:00 PM UTC
|
|---|
|
MO1431590 - Admins may see stale non-Copilot usage reports in the Microsoft 365 admin center in the Europe and Asia Pacific region
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 17 20:00:00 2026 |
|---|
| End Time: | Sun Jul 19 07:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 20 15:19:46 2026 |
|---|
| Root Cause: | A recent service update triggered delays with upstream availability which was resulting in stale data being displayed in non-Copilot usage reports.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 20 13:42:48 2026 |
|---|
| Description: | Title: Admins may see stale non-Copilot usage reports in the Microsoft 365 admin center in the Europe and Asia Pacific region
User impact: Admins may have seen stale non-Copilot usage reports in the Microsoft 365 admin center for Europe and Asia Pacific.
Final status: We've confirmed the backfill has completed and impact is fully remediated.
Scope of impact: This issue may have impacted any admin in the Asia Pacific and Europe regions attempting to view non-Copilot usage reports in the Microsoft 365 admin center.
Start time: Saturday, July 18, 2026, at 12:00 AM UTC
End time: Sunday, July 19, 2026, at 11:00 AM UTC
Root cause: A recent service update triggered delays with upstream availability which was resulting in stale data being displayed in non-Copilot usage reports.
Next steps:
- We're reviewing our service update 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: | Sat Jul 18 17:33:44 2026 |
|---|
| Description: | Title: Admins may see stale non-Copilot usage reports in the Microsoft 365 admin center in the Europe and Asia Pacific region
User impact: Admins may see stale non-Copilot usage reports in the Microsoft 365 admin center in the Europe and Asia Pacific region.
Current status: We're continuing to monitor the service as the backfill continues to process. Some non-Copilot usage reports have already been refreshed with the latest data, while the remaining reports continue to be refreshed as the backfill progresses. We'll provide a resolution timeline once it's available.
Scope of impact: This issue may impact any admin in the Asia Pacific and Europe regions attempting to view non-Copilot usage reports in the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Saturday, July 18, 2026, at 12:00 AM UTC
Root cause: A recent service update triggered delays with upstream availability which is resulting in stale data being displayed in non-Copilot usage reports.
Next update by: Monday, July 20, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Jul 17 22:24:34 2026 |
|---|
| Description: | Title: Admins may see stale non-Copilot usage reports in the Microsoft 365 admin center in the Europe and Asia Pacific region
User impact: Admins may see stale non-Copilot usage reports in the Microsoft 365 admin center in the Europe and Asia Pacific region.
Current status: We've identified a delay in report data processing caused by an upstream delay. As a result, non-Copilot usage reports in the Microsoft 365 admin center are displaying stale data. The impacted upstream services have recovered and are currently backfilling data. Report freshness is expected to improve as backfill processing progresses.
Scope of impact: This issue may impact any admin in the Asia Pacific and Europe regions attempting to view non-Copilot usage reports in the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Saturday, July 18, 2026, at 12:00 AM UTC
Root cause: A recent service update triggered delays with upstream availability which is resulting in stale data being displayed in non-Copilot usage reports.
Next update by: Saturday, July 18, 2026, at 11:00 PM UTC
|
|---|
|
CP1432638 - Microsoft Copilot (Microsoft 365) usage reports from the Microsoft 365 admin center may be delayed for admins and users
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jul 18 20:00:00 2026 |
|---|
| End Time: | Mon Jul 20 01:10:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 20 15:05:24 2026 |
|---|
| Root Cause: | An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center produced Copilot usage report delays and was resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 20 14:57:10 2026 |
|---|
| Description: | Title: Microsoft Copilot (Microsoft 365) usage reports from the Microsoft 365 admin center may be delayed for admins and users
User impact: Microsoft Copilot usage reports from the Microsoft 365 admin center may have been delayed for admins and users.
Final status: After restoring the remaining delayed Microsoft 365 Copilot readiness usage reports, our internal service telemetry has verified that all Microsoft Copilot usage reports from the Microsoft 365 admin center have been restored, and that the impact has been remediated.
Scope of impact: This issue potentially affected any admin who attempted to view Microsoft Copilot usage reports in the Microsoft 365 admin center.
Start time: Sunday, July 19, 2026, at 12:00 AM UTC
End time: Monday, July 20, 2026, at 5:10 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center produced Copilot usage report delays and was resulting in impact.
Next steps:
- We're further analyzing the pipeline in our effort to reduce usage report delays and to prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sun Jul 19 16:44:36 2026 |
|---|
| Description: | Title: Microsoft Copilot (Microsoft 365) usage reports from the Microsoft 365 admin center may be delayed for admins and users
User impact: Microsoft Copilot usage reports from the Microsoft 365 admin center may be delayed for admins and users.
Current status: We’ve addressed the issue with our pipeline utilized to process upstream data sources responsible for timely report data in the Microsoft 365 admin center and recovered both Microsoft 365 Copilot and Microsoft 365 Copilot Chat usage reports. Users will now see accurate and up-to-date data for these report types. We're working to restore delayed Microsoft 365 Copilot readiness usage reports, and we aim to provide a timeline for this report type to be recovered by our next scheduled update.
Scope of impact: This issue may potentially affect any admin attempting to view Microsoft Copilot usage reports in the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Sunday, July 19, 2026, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Copilot usage report delays and is resulting in impact.
Next update by: Monday, July 20, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Sat Jul 18 21:18:31 2026 |
|---|
| Description: | Title: Microsoft Copilot (Microsoft 365) usage reports from the Microsoft 365 admin center may be delayed for admins and users
User impact: Microsoft Copilot usage reports from the Microsoft 365 admin center may be delayed for admins and users.
Current status: We identified an issue in our telemetry indicating that usage report data is delayed for Copilot usage reports. We're working to with our upstream data source to refine our understanding of the underlying cause of impact and validate our troubleshooting actions.
Scope of impact: This issue may potentially affect any admin attempting to view Microsoft Copilot usage reports in the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Sunday, July 19, 2026, at 12:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Copilot usage report delays and is resulting in impact.
Next update by: Sunday, July 19, 2026, at 10:00 PM UTC
|
|---|
|
IT1431577 - Users' newly enrolled Windows devices are marked as non-compliant in Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 13 20:00:00 2026 |
|---|
| End Time: | Sun Jul 19 18:02:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jul 19 18:32:18 2026 |
|---|
| Root Cause: | Recent Windows builds introduced a code regression that affected device health attestation and compliance evaluation by Microsoft Intune. As a result, newly enrolled or newly recovered Windows devices that received the affected builds before enrollment completed may have been incorrectly marked as non-compliant.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jul 19 18:31:54 2026 |
|---|
| Description: | Title: Users' newly enrolled Windows devices are marked as non-compliant in Microsoft Intune
User impact: Users' newly enrolled Windows devices were marked as non-compliant in Microsoft Intune.
More info: The issue impacted newly enrolled or newly recovered Windows devices that received Windows builds 26100.8875 and 26200.8875 and were targeted for a compliance policy configured for device health before completing Microsoft Intune enrollment.
Devices that were already enrolled before installing the affected builds were not impacted.
As we developed a permanent remediation, affected organizations should have ensured that new and newly recovered devices completed Microsoft Intune enrollment before installing Windows updates.
Final status: We've completed deployment of a fix to address a code regression introduced in the recent Windows builds to affected environments. After completing a monitoring period of service availability, we've validated that our actions successfully remediated impact.
Scope of impact: Impact was limited to newly enrolled or newly recovered Windows devices that received Windows builds 26100.8875 and 26200.8875 before Microsoft Intune enrollment completed. These devices may have been incorrectly reported as non-compliant by Microsoft Intune.
Start time: Tuesday, July 14, 2026, at 12:00 AM UTC
End time: Sunday, July 19, 2026, at 10:02 PM UTC
Root cause: Recent Windows builds introduced a code regression that affected device health attestation and compliance evaluation by Microsoft Intune. As a result, newly enrolled or newly recovered Windows devices that received the affected builds before enrollment completed may have been incorrectly marked as non-compliant.
Next steps:
- We're analyzing the offending Windows builds to validate why the potential for impact wasn't caught during our build validation process. This further analysis will help us to improve our Windows build implementation process moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jul 18 19:57:40 2026 |
|---|
| Description: | Title: Users' newly enrolled Windows devices are marked as non-compliant in Microsoft Intune
User impact: Users' newly enrolled Windows devices are marked as non-compliant in Microsoft Intune.
More info: The issue impacts newly enrolled or newly recovered Windows devices that receive Windows builds 26100.8875 and 26200.8875 and are targeted for a compliance policy configured for device health before completing Microsoft Intune enrollment.
Devices that were already enrolled before installing the affected build are not currently known to be impacted.
As we continue to develop a permanent remediation, affected organizations should ensure that new and newly recovered devices complete Microsoft Intune enrollment before installing Windows updates.
Current status: We've confirmed that deployment to our test environment has completed and is effective in resolving the impact. We've initiated deployment to the remaining affected environments and anticipate that the issue will be fully remediated by our next communications update.
Scope of impact: Your organization may be affected by this event. Impact is limited to newly enrolled or newly recovered Windows devices that receive Windows builds 26100.8875 and 26200.8875 before Microsoft Intune enrollment completes. These devices may be incorrectly reported as non-compliant by Microsoft Intune. This information may be updated as our investigation continues.
Root cause: A recent Windows build introduced a code regression that affects device health attestation and compliance evaluation by Microsoft Intune. As a result, newly enrolled or newly recovered Windows devices that receive the affected build before enrollment completes may be incorrectly marked as non-compliant.
Next update by: Monday, July 20, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Sat Jul 18 15:21:42 2026 |
|---|
| Description: | Title: Users' newly enrolled Windows devices are marked as non-compliant in Microsoft Intune
User impact: Users' newly enrolled Windows devices are marked as non-compliant in Microsoft Intune.
More info: The issue impacts newly enrolled or newly recovered Windows devices that receive Windows builds 26100.8875 and 26200.8875 and are targeted for a compliance policy configured for device health before completing Microsoft Intune enrollment.
Devices that were already enrolled before installing the affected build are not currently known to be impacted.
As we continue to develop a permanent remediation, affected organizations should ensure that new and newly recovered devices complete Microsoft Intune enrollment before installing Windows updates.
Current status: We've developed a service side fix and are deploying it to test environments to verify its effectiveness before proceeding with deployment to the affected environments. Once available, we'll provide a resolution timeline.
Scope of impact: Your organization may be affected by this event. Impact is limited to newly enrolled or newly recovered Windows devices that receive Windows builds 26100.8875 and 26200.8875 before Microsoft Intune enrollment completes. These devices may be incorrectly reported as non-compliant by Microsoft Intune. This information may be updated as our investigation continues.
Root cause: A recent Windows build introduced a code regression that affects device health attestation and compliance evaluation by Microsoft Intune. As a result, newly enrolled or newly recovered Windows devices that receive the affected build before enrollment completes may be incorrectly marked as non-compliant.
Next update by: Sunday, July 19, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Jul 17 22:04:32 2026 |
|---|
| Description: | Title: Users' newly enrolled Windows devices are marked as non-compliant in Microsoft Intune
User impact: Users' newly enrolled Windows devices are marked as non-compliant in Microsoft Intune.
More info: The issue impacts newly enrolled or newly recovered Windows devices that receive Windows builds 26100.8875 and 26200.8875 and are targeted for a compliance policy configured for device health before completing Microsoft Intune enrollment.
Devices that were already enrolled before installing the affected build are not currently known to be impacted.
As we continue to develop a permanent remediation, affected organizations should ensure that new and newly recovered devices complete Microsoft Intune enrollment before installing Windows updates.
Current status: We've identified a code regression introduced in Windows builds 26100.8875 and 26200.8875 that affects device health attestation and compliance evaluation by Microsoft Intune. We've identified a service side remediation and are currently evaluating and validating the most effective solution.
Scope of impact: Your organization may be affected by this event. Impact is limited to newly enrolled or newly recovered Windows devices that receive Windows builds 26100.8875 and 26200.8875 before Microsoft Intune enrollment completes. These devices may be incorrectly reported as non-compliant by Microsoft Intune. This information may be updated as our investigation continues.
Start time: Tuesday, July 14, 2026, at 5:00 PM UTC
Root cause: A recent Windows build introduced a code regression that affects device health attestation and compliance evaluation by Microsoft Intune. As a result, newly enrolled or newly recovered Windows devices that receive the affected build before enrollment completes may be incorrectly marked as non-compliant.
Next update by: Saturday, July 18, 2026, at 9:00 PM UTC
|
|---|
|
CP1431319 - Admins in Europe may not see Copilot Cowork reports in the expected timeframe in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 17 15:00:00 2026 |
|---|
| End Time: | Sat Jul 18 05:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jul 18 13:26:50 2026 |
|---|
| Root Cause: | Telemetry reports which were used to populate data for Cowork usage reports were delayed, resulting in stale usage data being displayed.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jul 18 13:25:14 2026 |
|---|
| Description: | Title: Admins in Europe may not see Copilot Cowork reports in the expected timeframe in the Microsoft 365 admin center
User impact: Admins in Europe may have not seen Copilot Cowork reports in the expected timeframe in the Microsoft 365 admin center.
More info: Reports for July 15, 2026 and beyond weren't showing up in the Microsoft 365 admin center as expected.
Final status: We've developed and deployed a fix to refresh the delayed telemetry reports, and confirmed through monitoring service health telemetry that Copilot Cowork reports are viewable as expected in the Microsoft 365 admin center.
Scope of impact: This issue may have affected any admin in Europe attempting to view Cowork usage reports in the Microsoft 365 admin center.
Start time: Friday, July 17, 2026, at 7:00 PM UTC
End time: Saturday, July 18, 2026, at 9:00 AM UTC
Root cause: Telemetry reports which were used to populate data for Cowork usage reports were delayed, resulting in stale usage data being displayed.
Next steps:
- We're reviewing the impacted telemetry reporting data to understand what caused the delays, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 17 16:18:24 2026 |
|---|
| Description: | Title: Admins in Europe may not see Copilot Cowork reports in the expected timeframe in the Microsoft 365 admin center
User impact: Admins in Europe may not see Copilot Cowork reports in the expected timeframe in the Microsoft 365 admin center.
More info: Reports for July 15, 2026 and beyond aren't showing up in the Microsoft 365 admin center as expected.
Current status: We've identified that Cowork Usage Report data logged after July 15, 2026, isn't refreshing as expected. We're analyzing the data reporting flow and are developing a fix to restore timely data processing.
Scope of impact: This issue may affect any admin in Europe attempting to view Cowork usage reports in the Microsoft 365 admin center.
Start time: Friday, July 17, 2026, at 7:00 PM UTC
Root cause: Telemetry reports which are used to populate data for Cowork usage reports are delayed, resulting in stale usage data being displayed.
Next update by: Saturday, July 18, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jul 17 15:49:07 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
More info: This issue affects admins in Europe only.
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.
|
|---|
|
CP1429838 - Admins may not see any consumption or charges being recorded for pay-as-you-go (PAYG) Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 16 12:08:52 2026 |
|---|
| End Time: | Fri Jul 17 19:38:16 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 17 19:39:59 2026 |
|---|
| Root Cause: | A recent service change to the portion of infrastructure responsible for recording and communicating the consumption data for PAYG Copilot subscriptions was preventing the call requests that calculate the consumption from completing as expected, which resulted in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 17 19:39:57 2026 |
|---|
| Description: | Title: Admins may not see any consumption or charges being recorded for pay-as-you-go (PAYG) Microsoft 365 Copilot
User impact: Admins may not have seen any consumption or charges being recorded for their PAYG Copilot subscription.
Final status: While awaiting validation on mitigation from a subset of affected users, we were able to validate that our fix has fully remediated this event through service health telemetry.
Scope of impact: Any admin attempting to view consumption and charges for their PAYG Copilot subscription may have been impacted.
Start time: Friday, June 19, 2026, at 8:06 AM UTC
End time: Thursday, July 16, 2026, at 7:00 PM UTC
Root cause: A recent service change to the portion of infrastructure responsible for recording and communicating the consumption data for PAYG Copilot subscriptions was preventing the call requests that calculate the consumption from completing as expected, which resulted in this impact.
Next steps: - We're reviewing the responsible service change to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 17 15:05:51 2026 |
|---|
| Description: | Title: Admins may not see any consumption or charges being recorded for pay-as-you-go (PAYG) Microsoft 365 Copilot
User impact: Admins may not see any consumption or charges being recorded for their PAYG Copilot subscription.
Current status: Our service health telemetry continues to indicate that the consumption calculation rates are returning to expected levels, meaning affected users should start seeing relief of impact. We're reaching out to a subset of affected users to confirm full remediation.
Scope of impact: Any admin attempting to view consumption and charges for their PAYG Copilot subscription may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service change to the portion of infrastructure responsible for recording and communicating the consumption data for PAYG Copilot subscriptions is preventing the call requests that calculate the consumption from completing as expected.
Next update by: Monday, July 20, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Jul 17 11:16:59 2026 |
|---|
| Description: | Title: Admins may not see any consumption or charges being recorded for pay-as-you-go (PAYG) Microsoft 365 Copilot
User impact: Admins may not see any consumption or charges being recorded for their PAYG Copilot subscription.
Current status: The deployment of our fix has completed, and our service health telemetry indicates that the consumption calculation rates are returning to expected levels. We're continuing to monitor the rates to confirm that the impact is fully remediated.
Scope of impact: Any admin attempting to view consumption and charges for their PAYG Copilot subscription may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service change to the portion of infrastructure responsible for recording and communicating the consumption data for PAYG Copilot subscriptions is preventing the call requests that calculate the consumption from completing as expected.
Next update by: Friday, July 17, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 16 13:23:28 2026 |
|---|
| Description: | Title: Admins may not see any consumption or charges being recorded for pay-as-you-go (PAYG) Microsoft 365 Copilot
User impact: Admins may not see any consumption or charges being recorded for their PAYG Copilot subscription.
Current status: We've identified a recent service change affecting the portion of infrastructure responsible for recording and communicating the consumption data for PAYG Copilot subscriptions. As a result, the call requests that calculate consumption aren't completing as expected. We're deploying a fix to correct this issue and are monitoring our service health telemetry for recovery.
Scope of impact: Any admin attempting to view consumption and charges for their PAYG Copilot subscription may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service change to the portion of infrastructure responsible for recording and communicating the consumption data for PAYG Copilot subscriptions is preventing the call requests that calculate the consumption from completing as expected.
Next update by: Friday, July 17, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Jul 16 12:45:00 2026 |
|---|
| Description: | Title: Admins may not see any consumption or charges being recorded for pay-as-you-go (PAYG) Microsoft 365 Copilot
User impact: Admins may not see any consumption or charges being recorded for their PAYG Copilot subscription.
Current status: We're reviewing the code responsible for facilitating the recording of consumption and charges for PAYG subscriptions to identify any abnormalities that may be contributing to the impact.
Scope of impact: Any admin attempting to view consumption and charges for their PAYG Copilot subscription may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, July 16, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 16 12:20:34 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.
|
|---|
|
IT1428980 - Some admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 22 04:00:00 2026 |
|---|
| End Time: | Fri Jul 17 06:00:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 17 13:41:06 2026 |
|---|
| Root Cause: | A recent deployment intended to update internal labeling for device query infrastructure introduced signing validation mismatches that’s resulting in device queries failing to complete.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 17 13:40:19 2026 |
|---|
| Description: | Title: Some admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center
User impact: Admins may have been unable to complete Microsoft Intune single-device queries in the Intune admin center.
More info: Admins may have received an error message stating, "An error occurred. If this happens again, contact your IT support."
Final status: We've completed the rollback to prevent signing validation mismatches throughout the affected environments. After confirming that the rollback had fully propagated, we monitored the service and verified that this action successfully resolved the issue.
Scope of impact: Some admins may have been unable to complete Intune single-device queries in the Intune admin center and may have received an error message stating, "An error occurred. If this happens again, contact your IT support."
Start time: Friday, May 22, 2026, at 8:00 AM UTC
End time: Friday, July 17, 2026, at 10:00 AM UTC
Root cause: A recent deployment intended to update internal labeling for device query infrastructure introduced signing validation mismatches that’s resulting in device queries failing to complete.
Next steps: We're investigating how the recent deployment intended to update internal labeling for device query infrastructure introduced signing validation mismatches to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 16 13:56:02 2026 |
|---|
| Description: | Title: Some admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center
User impact: Admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center.
More info: Admins are returned an error message stating, "An error occurred. If this happens again, contact your IT support."
Current status: We're continuing to monitor the rollback to prevent signing validation mismatches. As the rollback propagates throughout the affected environment, affected users may experience relief from impact. Based on our current estimates, we expect the rollback to complete and the issue to be remediated by our next scheduled update.
Scope of impact: Some admins may be unable to complete Intune single-device queries in the Intune admin center and are returned an error message stating, "An error occurred. If this happens again, contact your IT support." This section may be updated as the investigation continues.
Start time: Friday, May 22, 2026, at 8:00 AM UTC
Root cause: A recent deployment intended to update internal labeling for device query infrastructure introduced signing validation mismatches that’s resulting in device queries failing to complete.
Next update by: Friday, July 17, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jul 15 19:11:11 2026 |
|---|
| Description: | Title: Some admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center
User impact: Admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center.
More info: Admins are returned an error message stating, "An error occurred. If this happens again, contact your IT support."
Current status: We're now in the process of initiating the rollback to prevent signing validation mismatches and we anticipate that a remediation timeline will be provided by our next scheduled update.
Scope of impact: Some admins may be unable to complete Intune single-device queries in the Intune admin center and are returned an error message stating, "An error occurred. If this happens again, contact your IT support." This section may be updated as the investigation continues.
Start time: Friday, May 22, 2026, at 8:00 AM UTC
Root cause: A recent deployment intended to update internal labeling for device query infrastructure introduced signing validation mismatches that’s resulting in device queries failing to complete.
Next update by: Thursday, July 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jul 15 18:17:15 2026 |
|---|
| Description: | Title: Some admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center
User impact: Admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center.
More info: Admins are returned an error message stating, "An error occurred. If this happens again, contact your IT support."
Current status: We're working to initiate a rollback to have impacted device query infrastructure call to the last known working authentication components to prevent signing validation mismatches. Simultaneously, we're working to ensure all authentication components are available to determine if additional remediation actions may be required.
Scope of impact: Some admins may be unable to complete Intune single-device queries in the Intune admin center and are returned an error message stating, "An error occurred. If this happens again, contact your IT support." This section may be updated as the investigation continues.
Start time: Friday, May 22, 2026, at 8:00 AM UTC
Root cause: A recent deployment intended to update internal labeling for device query infrastructure introduced signing validation mismatches that’s resulting in device queries failing to complete.
Next update by: Thursday, July 16, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jul 15 16:48:48 2026 |
|---|
| Description: | Title: Some admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center
User impact: Admins may be unable to complete Microsoft Intune single-device queries in the Intune admin center.
More info: Admins are returned an error message stating, "An error occurred. If this happens again, contact your IT support."
Current status: We've received reports from a subset of impacted admins who have noted that they are unable to complete Microsoft Intune single-device queries in the Intune admin center. After investigating admin reports, we've isolated that impact was caused by a recent deployment intended to update internal labeling for device query infrastructure, which introduced signing validation mismatches resulting in device queries failing to complete. We're investigating potential mitigation strategies to determine the best course of action to remediate impact as soon as possible.
Scope of impact: Some admins may be unable to complete Intune single-device queries in the Intune admin center and are returned an error message stating, "An error occurred. If this happens again, contact your IT support."
Root cause: A recent deployment intended to update internal labeling for device query infrastructure introduced signing validation mismatches that’s resulting in device queries failing to complete.
Next update by: Wednesday, July 15, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jul 15 16:33:35 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Intune
User impact: We're checking for potential impact to your users.
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.
|
|---|
|
CP1430786 - Some admins can't access Copilot Agent report data in the Microsoft 365 admin center from July 14, 2026
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 16 21:00:00 2026 |
|---|
| End Time: | Fri Jul 17 13:20:45 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 17 13:21:31 2026 |
|---|
| Root Cause: | Further analysis confirms that data from July 14, 2026 wasn't available within the expected timeframe, and we've updated our "Title", "User impact", and "Scope of impact" sections to reflect this. We've confirmed that our aforementioned code change successfully remediated the impact, and Copilot Agent report data for July 14, 2026, is now accessible within the Microsoft 365 admin center.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 17 13:21:27 2026 |
|---|
| Description: | Title: Some admins can't access Copilot Agent report data in the Microsoft 365 admin center from July 14, 2026
User impact: Admins couldn't access Copilot Agent report data in the Microsoft 365 admin center from July 14, 2026.
Final status: Further analysis confirms that data from July 14, 2026 wasn't available within the expected timeframe, and we've updated our "Title", "User impact", and "Scope of impact" sections to reflect this. We've confirmed that our aforementioned code change successfully remediated the impact, and Copilot Agent report data for July 14, 2026, is now accessible within the Microsoft 365 admin center.
Scope of impact: This issue may have impacted some admins attempting to view Copilot Agent reports from July 14, 2026 in the Microsoft 365 admin center.
Start time: Friday, July 17, 2026, at 1:00 AM UTC
End time: Friday, July 17, 2026, at 1:00 PM UTC
Root cause: Further analysis confirms that data from July 14, 2026 wasn't available within the expected timeframe, and we've updated our "Title", "User impact", and "Scope of impact" sections to reflect this. We've confirmed that our aforementioned code change successfully remediated the impact, and Copilot Agent report data for July 14, 2026, is now accessible within the Microsoft 365 admin center.
Next steps:
- We're continuing to review the pipeline for our upstream data source to gain a further understanding on why the issue occurred so we can determine how to prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 17 12:24:32 2026 |
|---|
| Description: | Title: Some admins can't access Copilot Agent report data in the Microsoft 365 admin center from July 14, 2026, onward
User impact: Admins can't access Copilot Agent report data in the Microsoft 365 admin center from July 14, 2026, onward.
Current status: We're continuing to review whether our proposed code change, which will modify the query logic to filter data using a tumbling window, will successfully reduce query volume and further mitigate impact.
Scope of impact: This issue may impact some admins attempting to view Copilot Agent reports from July 14, 2026, onward in the Microsoft 365 admin center.
Start time: Friday, July 17, 2026, at 1:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Copilot Agent report delays and resulting in impact.
Next update by: Friday, July 17, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Jul 17 10:29:51 2026 |
|---|
| Description: | Title: Some admins may experience delays when viewing Copilot Agent reports in the Microsoft 365 admin center
User impact: Admins may experience delays when viewing Copilot Agent reports in the Microsoft 365 admin center.
Current status: We've determined that the initial fix deployment didn't successfully mitigate impact. We're preparing to deploy an updated fix to the affected infrastructure and are validating the revised solution to ensure it effectively addresses the issue before deployment. In parallel, we're continuing to monitor the environment and review the proposed changes to minimize the risk of recurrence.
Scope of impact: This issue may potentially affect any admin attempting to view Copilot Agent reports in the Microsoft 365 admin center.
Start time: Friday, July 17, 2026, at 1:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Copilot Agent report delays.
Next update by: Friday, July 17, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Jul 17 08:39:41 2026 |
|---|
| Description: | Title: Some admins may experience delays when viewing Copilot Agent reports in the Microsoft 365 admin center
User impact: Admins may experience delays when viewing Copilot Agent reports in the Microsoft 365 admin center.
Current status: We've deployed a mitigation to increase data copy throughput and are validating its effectiveness while rerunning the affected data processing jobs. In parallel, we're monitoring downstream reporting pipelines and assessing additional recovery measures to expedite service restoration.
Scope of impact: This issue may potentially affect any admin attempting to view Copilot Agent reports in the Microsoft 365 admin center.
Start time: Friday, July 17, 2026, at 1:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Copilot Agent report delays.
Next update by: Friday, July 17, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Jul 17 06:43:53 2026 |
|---|
| Description: | Title: Some admins may experience delays when viewing Copilot Agent reports in the Microsoft 365 admin center
User impact: Admins may experience delays when viewing Copilot Agent reports in the Microsoft 365 admin center.
Current status: We're developing and validating a fix before deployment to the effected environment, in order to mitigate impact.
Scope of impact: This issue may potentially affect any admin attempting to view Copilot Agent reports in the Microsoft 365 admin center.
Start time: Friday, July 17, 2026, at 1:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Copilot Agent report delays.
Next update by: Friday, July 17, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Fri Jul 17 05:04:16 2026 |
|---|
| Description: | Title: Some admins may experience delays when viewing Copilot Agent reports in the Microsoft 365 admin center
User impact: Admins may experience delays when viewing Copilot Agent reports in the Microsoft 365 admin center.
Current status: We've identified an issue in our upstream telemetry indicating that report data is delayed for Copilot Agent. We're working with our upstream data source to remediate the impact.
Scope of impact: This issue may potentially affect any admin attempting to view Copilot Agent reports in the Microsoft 365 admin center.
Start time: Friday, July 17, 2026, at 1:00 AM UTC
Root cause: An issue with the pipeline for our upstream data source responsible for timely report data in the Microsoft 365 admin center is causing Copilot Agent report delays.
Next update by: Friday, July 17, 2026, at 11:00 AM UTC
|
|---|
|
MO1428775 - Some admins may see incorrect classifications of Cowork Tasks in Microsoft 365 Copilot Cowork usage reports
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 17 18:07:00 2026 |
|---|
| End Time: | Thu Jul 16 21:02:54 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 16 21:04:10 2026 |
|---|
| Root Cause: | The classification logic utilized to apply labels to affected tasks was incorrectly classifying "Scheduled" tasks as "User-Initiated", which resulted in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 16 21:04:06 2026 |
|---|
| Description: | Title: Some admins may see incorrect classifications of Cowork Tasks in Microsoft 365 Copilot Cowork usage reports
User impact: Admins may have seen incorrect classifications of Cowork Tasks in Copilot Cowork usage reports.
More info: Admins may have seen that Cowork Tasks that should been categorized as "Scheduled" were reported as "User-Initiated". These usage reports were found within the Microsoft 365 admin center.
Final status: We've validated that the completed backfilling process has successfully resolved this impact.
Scope of impact: Some admins may have seen that Cowork Tasks that should been categorized as "Scheduled" were reported as "User-Initiated" in Microsoft 365 Copilot Cowork usage reports in the Microsoft 365 admin center.
Start time: Wednesday, June 17, 2026, at 10:07 PM UTC
End time: Wednesday, July 15, 2026, at 10:00 PM UTC
Root cause: The classification logic utilized to apply labels to affected tasks was incorrectly classifying "Scheduled" tasks as "User-Initiated", which resulted in this impact.
Next steps: - We're reviewing the involved classification logic to better understand what led to the incorrect task classification and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 16 19:34:30 2026 |
|---|
| Description: | Title: Some admins may see incorrect classifications of Cowork Tasks in Microsoft 365 Copilot Cowork usage reports
User impact: Admins may see incorrect classifications of Cowork Tasks in Copilot Cowork usage reports.
More info: Admins may see that Cowork Tasks that should be categorized as "Scheduled" are currently being reported as "User-Initiated". These usage reports are found within the Microsoft 365 admin center.
Current status: We've confirmed that the process of backfilling the impacted reports has completed, and have reached out to a subset of affected users to validate full remediation.
Scope of impact: Some admins may see that Cowork Tasks that should be categorized as "Scheduled" are reported as "User-Initiated" in Microsoft 365 Copilot Cowork usage reports in the Microsoft 365 admin center.
Start time: Wednesday, June 17, 2026, at 10:07 PM UTC
Root cause: The classification logic utilized to apply labels to affected tasks is incorrectly classifying "Scheduled" tasks as "User-Initiated".
Next update by: Saturday, July 18, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jul 15 14:16:15 2026 |
|---|
| Description: | Title: Some admins may see incorrect classifications of Cowork Tasks in Microsoft 365 Copilot Cowork usage reports
User impact: Admins may see incorrect classifications of Cowork Tasks in Copilot Cowork usage reports.
More info: Admins may see that Cowork Tasks that should be categorized as "Scheduled" are currently being reported as "User-Initiated". These usage reports are found within the Microsoft 365 admin center.
Current status: We've received reports from a subset of admins that they're receiving incorrect usage classifications of Cowork Tasks for Copilot Cowork usage reports in the Microsoft 365 admin center. Specifically, admins see tasks that should be categorized as "Scheduled" are reported as "User-Initiated". We identified that the classification logic utilized to apply labels to affected tasks is incorrectly classifying "Scheduled" tasks as "User-Initiated". We've corrected the offending classification logic and we're backfilling impacted reports to have them reflect the correct usage classification label. We anticipate this process to be completed by Friday, July 17, 2026, at 4:00 AM UTC and we aim to provide updates on our timeline to remediation as the backfill progresses.
Scope of impact: Some admins may see that Cowork Tasks that should be categorized as "Scheduled" are reported as "User-Initiated" in Microsoft 365 Copilot Cowork usage reports in the Microsoft 365 admin center.
Start time: Wednesday, June 17, 2026, at 10:07 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by Friday, July 17, 2026, at 4:00 AM UTC.
Root cause: The classification logic utilized to apply labels to affected tasks is incorrectly classifying "Scheduled" tasks as "User-Initiated".
Next update by: Friday, July 17, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jul 15 13:43:05 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting the Microsoft 365 suite
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with the Microsoft 365 suite and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1430019 - Users are shown the Microsoft Planner app in Outlook and Office hubs
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 7 17:18:00 2026 |
|---|
| End Time: | Thu Jul 16 15:30:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 16 17:25:05 2026 |
|---|
| Root Cause: | While deploying the Microsoft Planner app to our testing environment, it was unintentionally made available to the affected users despite the feature not being released, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 16 17:24:41 2026 |
|---|
| Description: | Title: Users are shown the Microsoft Planner app in Outlook and Office hubs
User impact: Users were shown the Microsoft Planner app in Outlook and Office hubs.
Final status: We've validated that fully reverting the offending app deployment has successfully remediated impact for this issue.
Scope of impact: Your organization was impacted by this event, and any user viewing the apps in their Outlook and Office hubs was affected.
Start time: Tuesday, July 7, 2026, at 9:18 PM UTC
End time: Thursday, July 16, 2026, at 7:30 PM UTC
Root cause: While deploying the Microsoft Planner app to our testing environment, it was unintentionally made available to the affected users despite the feature not being released, which resulted in impact.
Next steps:
- We're reviewing our app deployment validation and implementation processes to improve how we detect unintentional app release issues and prevent similar service events from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 16 15:11:19 2026 |
|---|
| Description: | Title: Users are shown the Microsoft Planner app in Outlook and Office hubs
User impact: Users are shown the Microsoft Planner app in Outlook and Office hubs.
Current status: We're continuing to monitor the reversion of the Microsoft Planner app deployment and expect it'll be complete by the time of our next update.
Scope of impact: Your organization is impacted by this event, and any user viewing the apps in their Outlook and Office hubs are affected.
Start time: Tuesday, July 7, 2026, at 9:18 PM UTC
Root cause: While deploying the Microsoft Planner app to our testing environment, it was unintentionally made available to the affected users despite the feature not being released.
Next update by: Thursday, July 16, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jul 16 14:19:08 2026 |
|---|
| Description: | Title: Users are shown the Microsoft Planner app in Outlook and Office hubs
User impact: Users are shown the Microsoft Planner app in Outlook and Office hubs.
Current status: We've identified that while deploying the Microsoft Planner app to our testing environment, it was unintentionally made available to the affected users despite the feature not being released. We're reversing our deployment of the app to remove it from users' Outlook and Office hubs.
Scope of impact: Your organization is impacted by this event, and any user viewing the apps in their Outlook and Office hubs are affected.
Root cause: While deploying the Microsoft Planner app to our testing environment, it was unintentionally made available to the affected users despite the feature not being released.
Next update by: Thursday, July 16, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jul 16 14:08:18 2026 |
|---|
| Description: | Title: Users are shown the Microsoft Planner app in Outlook and Office hubs
User impact: Users are shown the Microsoft Planner app in Outlook and Office hubs.
We're investigating a potential issue with Outlook and Office hubs and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1420954 - Users are unable to access Microsoft Copilot web and m365.cloud.microsoft
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Jul 7 13:00:00 2026 |
|---|
| End Time: | Fri Jul 10 14:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 16 13:37:12 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 16 13:37:12 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 14 17:55:36 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jul 10 14:47:44 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft Copilot web and m365.cloud.microsoft
User impact: Users were intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually timed out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL was m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to:
- office.com
- portal.microsoft.com
Users may have been using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirected to m365.cloud.microsoft they may have experienced impact, however, users could access M365 applications in the browser directly through the product’s specific URL (such as: outlook.office.com).
As a potential workaround, users could have used the desktop version of the Microsoft 365 applications. Additionally, users may have experienced temporary relief by refreshing the cache when trying to access through the browser.
Final status: We completed the traffic rerouting and have confirmed with previously impacted users that impact is now remediated.
Scope of impact: This issue could have impacted any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Start time: Tuesday, July 7, 2026, at 5:00 PM UTC
End time: Friday, July 10, 2026, at 6:00 PM UTC
Preliminary root cause: A recent change which modified the route that back-end service calls take when users access the affected apps unexpectedly introduced impact.
Next steps:
- We're continuing to investigate why the offending change introduced impact and why it wasn't detected prior to deployment.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Fri Jul 10 13:52:50 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft Copilot web and m365.cloud.microsoft
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL is m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to:
- office.com
- portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact, however, users can access M365 applications in the browser directly through the product’s specific URL (such as: outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: We're proceeding with the traffic rerouting which we expect to fully remediate impact. We anticipate this process will complete by our next scheduled update.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Preliminary root cause: A recent change which modified the route that back-end service calls take when users access the affected apps unexpectedly introduced impact.
Next update by: Friday, July 10, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Jul 10 13:33:26 2026 |
|---|
| Description: | We've completed the aforementioned rollback and as such, no new users will experience this issue and previously affected users are able to clear their browser cookies to mitigate impact.
We're continuing to pursue the traffic rerouting strategy which will allow for larger cookies and ultimately fully remediate this problem without users needing to take action.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Jul 10 12:41:21 2026 |
|---|
| Description: | We're exploring a different fix which involves rerouting traffic through alternate infrastructure that can support the larger cookie size. We aim to pursue the most expedient fix option while ensuring no adverse impact is introduced.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Jul 10 12:01:54 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft Copilot web and m365.cloud.microsoft
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL is m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to:
- office.com
- portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact, however, users can access M365 applications in the browser directly through the product’s specific URL (such as: outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: We are performing final validations to roll back the recent change we suspect is contributing to impact. This change modified the route that back-end service calls take when users access the affected apps. Once the rollback is initiated, we expect it to take approximately one hour to complete. We'll provide an update as soon as this process has started.
In parallel, our investigation into the oversized cookies and the underlying root cause is ongoing. We continue to pursue additional mitigation paths, including a fix to adjust the cookie size to expected thresholds.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Next update by: Friday, July 10, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jul 10 10:20:32 2026 |
|---|
| Description: | Title: Unable to access Microsoft Copilot web and the m365.cloud.microsoft URL
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL is m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to:
- office.com
- portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact, however, users can access M365 applications in the browser directly through the product’s specific URL (eg outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: We’re continuing to analyze and test the rollback of the previously mentioned change. Additionally, we’re reviewing HTTP Archive format (HAR) files from impacted users to assist in identifying why specific chunks in the cookie size have increased above the allowed thresholds. In parallel, we’re testing some redirect configuration paths to reproduce the issue internally and gather additional diagnostics to assist our investigation.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Next update by: Friday, July 10, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri Jul 10 08:42:29 2026 |
|---|
| Description: | Due to the complexity of the change, we're performing detailed analysis and testing before starting the rollback, to ensure that reverting it would not cause impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Jul 10 08:18:27 2026 |
|---|
| Description: | Title: Unable to access Microsoft Copilot web and the m365.cloud.microsoft URL
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The impacted URL is m365.cloud.microsoft and other URLs which redirect to this page, including but not limited to:
- office.com
- portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact. Users can access M365 applications in the browser direct through the product’s specific URL (eg outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: We’ve identified a recent change that occurred around the time that impact was first reported. The change is related to URL redirects that occur for specific services after the authentication process completes. Out of an abundance of caution, we’re reverting this change as a potential expedited mitigation strategy, whilst in parallel, we continue to investigate the underlying cause.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Next update by: Friday, July 10, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Fri Jul 10 07:49:39 2026 |
|---|
| Description: | Quick: We're reviewing options to expedite the fix development and deployment. Additionally, we're reviewing options to revert a recent change we believe may be contributing to impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Jul 10 07:07:00 2026 |
|---|
| Description: | Title: Unable to access Microsoft Copilot web and the m365.cloud.microsoft URL
User impact: Users may be intermittently unable to access Copilot web and other pages that redirect to the m365.cloud.microsoft URL.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
The main impacted URL is m365.cloud.microsoft, however, this issue will also impact other URLs that redirect to this page, including, but not limited to:
- office.com
- portal.microsoft.com
Users may be using URLs such as office.com and the navigation Waffle to access M365 applications in the browser, such as Outlook. For this scenario, when the URL redirects to m365.cloud.microsoft they may experience impact. Users can access M365 applications in the browser direct through the product’s specific URL (e.g. outlook.office.com).
As a potential workaround, users can use the desktop version of the Microsoft 365 applications. Additionally, users may experience temporary relief by refreshing the cache when trying to access through the browser.
Current status: After further investigations, we’ve confirmed that the Microsoft admin portal (admin.cloud.microsoft) is unaffected. The issue is limited to Copilot web (m365.cloud.microsoft) and other browser pages which redirect to this URL.
We're continuing to work on a fix that will remove the impacting code which requests the groups claim within the token. We’ll provide a further update shortly with more details on the development and deployment timelines.
Scope of impact: This issue could impact any user attempting to access Copilot web, or a URL which redirects to m365.cloud.microsoft.
Next update by: Friday, July 10, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Jul 9 15:04:19 2026 |
|---|
| Description: | Title: Some users are intermittently unable to access the Microsoft 365 suite portal
User impact: Users are intermittently unable to access the Microsoft 365 suite portal.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
Current status: Our investigation into the authorization flow has identified that tokens utilized by OAuthentication contain a "groups" claim which includes group memberships for users attempting to authentication. We suspect that due to the inclusion of group memberships, this may be resulting in the generation of larger than expected headers, resulting in impact. We're working on a fix that would disable or remove the code which requests the groups claim within the token as a potential remediation, and working to confirm a timeline for fix deployment.
Scope of impact: Your organization is affected by this event, and some users are intermittently unable to access the Microsoft 365 suite portal.
Next update by: Friday, July 10, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jul 8 22:00:47 2026 |
|---|
| Description: | Title: Some users are intermittently unable to access the Microsoft 365 suite portal
User impact: Users are intermittently unable to access the Microsoft 365 suite portal.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
Current status: We're analyzing the authorization flow to understand why the generated large headers that are responsible for the associated error message are being created and are determining the next best steps for remediation.
Scope of impact: Your organization is affected by this event, and some users are intermittently unable to access the Microsoft 365 suite portal.
Next update by: Thursday, July 9, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jul 8 21:49:09 2026 |
|---|
| Description: | Title: Some users are intermittently unable to access the Microsoft 365 suite portal
User impact: Users are intermittently unable to access the Microsoft 365 suite portal.
More info: Access eventually times out with an error message stating, "Bad Request - Header Field Too Long. HTTP Error 400. A request field is too long."
Current status: We're investigating a potential issue with intermittent failures when accessing the Microsoft 365 suite portal and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1189321 - Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
| Status: | serviceDegradation |
|---|
| Start Time: | Sun Nov 23 14:58:02 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 16 12:43:49 2026 |
|---|
| 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: | Monday, August 3, 2026, at 6:00 PM UTC |
|---|
|
Details
| 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
|
|---|
|
SP1393483 - Admins may be unable to see the configuration search schema mappings in SharePoint Online
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 16 12:02:13 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Tenant Admin |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 16 03:05:28 2026 |
|---|
| Root Cause: | A recent migration introduced a configuration issue, resulting in a regression that is causing impact.
|
|---|
| Next Update: | Friday, July 31, 2026, at 10:00 AM UTC |
|---|
|
Details
| Time: | Thu Jul 16 03:05:28 2026 |
|---|
| Description: | Title: Admins may be unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may be unable to see the configuration search schema mappings in SharePoint Online.
More info: As a workaround, administrators may be able to refresh the affected SharePoint Online search configuration settings by opening them, making any small update, and saving them again. This can trigger the configuration settings to be rewritten and may provide immediate relief while we develop a long-term fix.
Current status: We've determined that additional time is required to complete deployment of the remediation worldwide. Supporting code has been deployed to most affected environments, and we're preparing to initiate a backfill process to apply the necessary updates to existing data. We're expecting the backfill process to take an additional one to two weeks to complete and will provide further updates as progress continues.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Start time: Monday, June 8, 2026, at 3:50 AM UTC
Root cause: A recent migration introduced a configuration issue, resulting in a regression that is causing impact.
Next update by: Friday, July 31, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Jul 6 04:36:36 2026 |
|---|
| Description: | Title: Admins may be unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may be unable to see the configuration search schema mappings in SharePoint Online.
More info: As a workaround, administrators may be able to refresh the affected SharePoint Online search configuration settings by opening them, making any small update, and saving them again. This can trigger the configuration settings to be rewritten and may provide immediate relief while we develop a long-term fix.
Current status: We've updated the affected index settings and are preparing to deploy a long-term fix worldwide. The deployment is expected to begin later this week, and based on our assessment of the affected settings, we expect the remaining impact to be resolved within approximately one week of rollout completion. We're monitoring deployment progress and will provide an update as more information becomes available.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Start time: Monday, June 8, 2026, at 3:50 AM UTC
Root cause: A recent migration introduced a configuration issue, resulting in a regression that is causing impact.
Next update by: Thursday, July 16, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Jun 22 05:18:10 2026 |
|---|
| Description: | Title: Admins may be unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may be unable to see the configuration search schema mappings in SharePoint Online.
More info: As a workaround, administrators may be able to refresh the affected SharePoint Online search configuration settings by opening them, making any small update, and saving them again. This can trigger the configuration settings to be rewritten and may provide immediate relief while we develop a long-term fix.
Current status: We've determined that a recent migration introduced a configuration issue, resulting in a regression that is causing impact. As part of our mitigation efforts, we've reverted traffic to the previous pathway and are working with your representatives to implement the workaround steps detailed in the More info section, which can provide immediate relief. Meanwhile, we're continuing to develop and validate a long-term fix.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Start time: Monday, June 8, 2026, at 3:50 AM UTC
Root cause: A recent migration introduced a configuration issue, resulting in a regression that is causing impact.
Next update by: Monday, July 6, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Jun 19 05:51:54 2026 |
|---|
| Description: | Title: Admins may be unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may be unable to see the configuration search schema mappings in SharePoint Online.
Current status: We're continuing to debug service code to help identify why the configuration search schema mappings in SharePoint Online are not being returned as expected for admins. These mapping and managed properties are working as expected in data ingestion and query.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Monday, June 22, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Jun 18 06:10:31 2026 |
|---|
| Description: | Title: Admins may be unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may be unable to see the configuration search schema mappings in SharePoint Online.
Current status: We’ve confirmed that admins are able to create new managed property and mapping but are unable to see the configuration search schema mappings in the search schema page. We're debugging service code to help identify why the configuration search schema mappings in SharePoint Online are not being returned as expected for admins. These mapping and managed properties are working as expected in data ingestion and query.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Friday, June 19, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Jun 17 06:17:42 2026 |
|---|
| Description: | Title: Admins may be unable to configure search schema mappings in SharePoint Online
User impact: Admins may be unable to configure search schema mappings in SharePoint Online.
Current status: We’re progressing with our review of the internal reproduction of the issue to verify property metadata and check whether promoted properties and annotations are truly indexed and can be queried with filters to aid in determining the underlying cause of impact and our subsequent troubleshooting actions. Additionally, we’re continuing to reach out to a subset of affected users to validate a potential fix, and we anticipate that the results of this validation will expedite our investigative actions.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Thursday, June 18, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Jun 16 23:41:20 2026 |
|---|
| Description: | Title: Admins may be unable to configure search schema mappings in SharePoint Online
User impact: Admins may be unable to configure search schema mappings in SharePoint Online.
Current status: We’re continuing our review of the internal reproduction of the issue to verify property metadata and check whether promoted properties and annotations are truly indexed and can be queried with filters to aid in determining the underlying cause of impact and our subsequent troubleshooting actions. Additionally, we’re reaching out to a subset of affected users to validate a potential fix, and we anticipate that the results of this validation will expedite our investigative actions.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Wednesday, June 17, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Tue Jun 16 14:33:39 2026 |
|---|
| Description: | Title: Admins may be unable to configure search schema mappings in SharePoint Online
User impact: Admins may be unable to configure search schema mappings in SharePoint Online.
Current status: We've managed to reproduce impact in our internal testing environment, and are reviewing our reproduction to verify property metadata and check whether promoted properties and annotations are truly indexed and can be queried with filters to assist our investigation into the source of the issue.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Wednesday, June 17, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Tue Jun 16 12:03:53 2026 |
|---|
| Description: | Title: Admins may be unable to configure search schema mappings in SharePoint Online
User impact: Admins may be unable to configure search schema mappings in SharePoint Online.
Current status: We've received reports from affected admins that they're unable to configure search schema mappings in SharePoint Online. We're reviewing service telemetry to isolate the source of the issue and determine appropriate remediation actions.
Scope of impact: This issue may affect any admin attempting to configure search schema mappings in SharePoint Online. This section may be updated as our investigation proceeds.
Next update by: Tuesday, June 16, 2026, at 7:30 PM UTC
|
|---|
|
TM1428740 - Some users may get failures when starting live transcription in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 15 10:16:00 2026 |
|---|
| End Time: | Wed Jul 15 12:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 15 13:07:18 2026 |
|---|
| Root Cause: | An unexpected influx in requests caused the service infrastructure responsible for facilitating live transcription to begin operating in an unhealthy state, resulting in users' requests failing.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 15 13:07:01 2026 |
|---|
| Description: | Title: Some users may get failures when starting live transcription in Microsoft Teams
User impact: Users may have received failures when starting live transcription in Microsoft Teams.
Final status: Our service monitors alerted us to a spike in failures for users in North America when attempting to initiate live transcription in Microsoft Teams meetings. We've isolated that an unexpected influx in requests caused the service infrastructure responsible for facilitating live transcription to begin operating in an unhealthy state, resulting in users' requests failing. We've implemented performance optimizations to assist with processing user traffic and after monitoring service telemetry, we've validated that our actions successfully remediated impact.
Scope of impact: Some users in North America may have received failures when starting live transcription in Microsoft Teams.
Start time: Wednesday, July 15, 2026, at 2:16 PM UTC
End time: Wednesday, July 15, 2026, at 4:00 PM UTC
Root cause: An unexpected influx in requests caused the service infrastructure responsible for facilitating live transcription to begin operating in an unhealthy state, resulting in users' requests failing.
Next steps:
- We're analyzing the offending service infrastructure to validate what additional performance optimizations we can implement to ensure similar impact scenarios don't occur in the future by bolstering the resiliency of our service infrastructure.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 15 12:39:01 2026 |
|---|
| Description: | Title: Some users may get failures when starting live transcription in Microsoft Teams
User impact: Users may get failures when starting live transcription in Microsoft Teams.
Current status: We've investigated a problem in which some users in North America may have received failures when starting live transcription in Microsoft Teams, and we confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
CP1428746 - Some users in North America may be unable to access Microsoft 365 Copilot in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 15 10:16:00 2026 |
|---|
| End Time: | Wed Jul 15 12:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 15 13:04:04 2026 |
|---|
| Root Cause: | An unexpected influx in requests caused the service infrastructure responsible for facilitating Copilot access within Teams to begin operating in an unhealthy state, resulting in users' requests failing.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 15 13:03:52 2026 |
|---|
| Description: | Title: Some users in North America may be unable to access Microsoft 365 Copilot in Microsoft Teams
User impact: Users in North America may have been unable to access Microsoft Copilot in Microsoft Teams.
Final status: Our service monitors alerted us to a spike in failures for users in North America when attempting to access Microsoft 365 Copilot in Microsoft Teams meetings. We've isolated that an unexpected influx in requests caused the service infrastructure responsible for facilitating Copilot access within Teams to begin operating in an unhealthy state, resulting in users' requests failing. We've implemented performance optimizations to assist with processing user traffic and after monitoring service telemetry, we've validated that our actions successfully remediated impact.
Scope of impact: Some users in North America may have received failures when attempting to access Microsoft Copilot in Microsoft Teams.
Start time: Wednesday, July 15, 2026, at 2:16 PM UTC
End time: Wednesday, July 15, 2026, at 4:00 PM UTC
Root cause: An unexpected influx in requests caused the service infrastructure responsible for facilitating Copilot access within Teams to begin operating in an unhealthy state, resulting in users' requests failing.
Next steps:
- We're analyzing the offending service infrastructure to validate what additional performance optimizations we can implement to ensure similar impact scenarios don't occur in the future by bolstering the resiliency of our service infrastructure.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 15 12:42:42 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1426934 - Some admins may be unable to make changes to distribution lists in Exchange Online and receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jul 12 19:00:00 2026 |
|---|
| End Time: | Wed Jul 15 01:33:30 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 15 01:58:44 2026 |
|---|
| Root Cause: | A recent update to distribution list management functionality inadvertently created a configuration conflict within a subset of the service infrastructure, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 15 01:34:17 2026 |
|---|
| Description: | Title: Some admins may be unable to make changes to distribution lists in Exchange Online and receive an error
User impact: Admins may have been unable to make changes to distribution lists in Exchange Online and received an error.
More info: Affected admins may have been unable to view, add, remove, or edit users associated with distribution lists in Exchange Online and received the following error message:
"You don't have permission to access this page or perform this action".
This issue affected both the Exchange admin center and the Microsoft 365 admin center.
As a workaround, affected admins could’ve used the Exchange Online PowerShell cmdlet “Set-DistributionGroup” to manage distribution lists.
Final status: We’ve confirmed with affected users that this issue is resolved as a result of our reverting the offending service update.
Scope of impact: Some admins attempting to modify Exchange Online distribution lists through the Microsoft 365 admin center or Exchange admin center that are served by the affected infrastructure in the West UK, West Europe, India, Southeast Asia, West Japan, or East Australia regions may have been impacted.
Start time: Sunday, July 12, 2026, at 11:00 PM UTC
End time: Wednesday, July 15, 2026, at 1:00 AM UTC
Root cause: A recent update to distribution list management functionality inadvertently created a configuration conflict within a subset of the service infrastructure, 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: | Tue Jul 14 23:04:04 2026 |
|---|
| Description: | Title: Some admins may be unable to make changes to distribution lists in Exchange Online and receive an error
User impact: Admins may be unable to make changes to distribution lists in Exchange Online and receive an error.
More info: Affected admins may be unable to view, add, remove, or edit users associated with distribution lists in Exchange Online and receiving the following error message:
"You don't have permission to access this page or perform this action".
This issue affects both the Exchange admin center and the Microsoft 365 admin center.
As a workaround, affected admins can use the Exchange Online PowerShell cmdlet “Set-DistributionGroup” to manage distribution lists.
Current status: The process or reverting the offending service update is complete and we’re validating with affected users to ensure the issue is resolved as expected.
Scope of impact: Some admins attempting to modify Exchange Online distribution lists through the Microsoft 365 admin center or Exchange admin center that are served by the affected infrastructure in the West UK, West Europe, India, Southeast Asia, West Japan, or East Australia regions may be impacted.
Start time: Sunday, July 12, 2026, at 11:00 PM UTC
Root cause: A recent update to distribution list management functionality inadvertently created a configuration conflict within a subset of the service infrastructure, resulting in impact.
Next update by: Wednesday, July 15, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Tue Jul 14 17:29:36 2026 |
|---|
| Description: | Title: Some admins may be unable to make changes to distribution lists in Exchange Online and receive an error
User impact: Admins may be unable to make changes to distribution lists in Exchange Online and receive an error.
More info: Affected admins may be unable to view, add, remove, or edit users associated with distribution lists in Exchange Online and receiving the following error message:
"You don't have permission to access this page or perform this action".
This issue affects both the Exchange admin center and the Microsoft 365 admin center.
As a workaround, affected admins can use the Exchange Online PowerShell cmdlet “Set-DistributionGroup” to manage distribution lists.
Current status: Our rollback of the offending service update is still ongoing across affected regions and is taking longer than initially anticipated. We're discussing what actions we can take to expedite the rollback progress to remediate impact as soon as possible.
Scope of impact: Some admins attempting to modify Exchange Online distribution lists through the Microsoft 365 admin center or Exchange admin center that are served by the affected infrastructure in the West UK, West Europe, India, Southeast Asia, West Japan, or East Australia regions may be impacted.
Start time: Sunday, July 12, 2026, at 11:00 PM UTC
Root cause: A recent update to distribution list management functionality inadvertently created a configuration conflict within a subset of the service infrastructure, resulting in impact.
Next update by: Wednesday, July 15, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Jul 14 06:20:14 2026 |
|---|
| Description: | Title: Some admins may be unable to make changes to distribution lists in Exchange Online and receive an error
User impact: Admins may be unable to make changes to distribution lists in Exchange Online and receive an error.
More info: Affected admins may be unable to view, add, remove, or edit users associated with distribution lists in Exchange Online and receiving the following error message:
"You don't have permission to access this page or perform this action".
This issue affects both the Exchange admin center and the Microsoft 365 admin center.
As a workaround, affected admins can use the Exchange Online PowerShell cmdlet “Set-DistributionGroup” to manage distribution lists.
Current status: We’ve determined that a recent update to distribution list management functionality inadvertently created a configuration conflict in a section of the service infrastructure, resulting in impact. We’re reverting the update to mitigate impact and initial indicators suggest that distribution list management functionality has been restored in West UK and West Japan regions. We’re continuing to deploy the fix across the remaining affected regions and expect deployment to be complete by our next scheduled update.
Scope of impact: Some admins attempting to modify Exchange Online distribution lists through the Microsoft 365 admin center or Exchange admin center that are served by the affected infrastructure in the West UK, West Europe, India, Southeast Asia, West Japan, or East Australia regions may be impacted.
Start time: Sunday, July 12, 2026, at 11:00 PM UTC
Root cause: A recent update to distribution list management functionality inadvertently created a configuration conflict within a subset of the service infrastructure, resulting in impact.
Next update by: Tuesday, July 14, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jul 14 01:44:54 2026 |
|---|
| Description: | Title: Some admins may be unable to make changes to distribution lists in Exchange Online and receive an error
User impact: Admins may be unable to make changes to distribution lists in Exchange Online and receive an error.
More info: Affected admins report being unable to view, add, remove, or edit users associated with distribution lists in Exchange Online and receiving "Unauthorized: You don't have permission to access this page or perform this action" permissions errors, even when using global administrator accounts. This affects both the Exchange admin center and the Microsoft 365 admin center.
Current status: We've identified that an API configuration conflict is affecting the permissions flow leveraged for distribution list administrative operations and resulting in impact. We're proceeding with further review of the impacted flow and details provided by affected users to determine our next steps towards remediation.
Scope of impact: Any admins attempting to make changes to Exchange Online distribution lists through the Microsoft 365 admin center or Exchange admin center may be impacted.
Next update by: Tuesday, July 14, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Jul 14 00:23:27 2026 |
|---|
| Description: | Title: Some admins may be unable to make changes to distribution lists in Exchange Online and receive an error
User impact: Admins may be unable to make changes to distribution lists in Exchange Online and receive an error.
More info: Affected users report being unable to view, add, remove, or edit users associated with distribution lists in Exchange Online and receiving "Unauthorized" permissions errors, even when using global administrator accounts.
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.
|
|---|
|
TM1419268 - Issues with chat functionality in Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Jul 7 10:01:00 2026 |
|---|
| End Time: | Tue Jul 7 10:28:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jul 14 19:33:11 2026 |
|---|
| Root Cause: | A networking issue caused intermittent connectivity disruptions within a service that supports chat operations. This impacted underlying dependencies used by multiple chat-related services, resulting in the observed service degradation. As caching components were unable to process requests efficiently, the volume of requests routed directly to chat services and backend databases significantly increased. This resulted in high Central Processing Unit (CPU) utilization leading to latency, frequent HTTP 500 errors, and request timeouts. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 14 19:33:11 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 14 19:06:36 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 9 11:20:51 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 7 11:36:06 2026 |
|---|
| Description: | Title: Issues with chat functionality in Microsoft Teams
User impact: Users may have experienced delays or errors when sending or receiving chat messages.
More info: Some chat-specific functionalities that were impacted include, but were not limited to:
- Delays or errors when loading existing chats or channels
- Failures when attempting to share pictures or files
This issue could have impacted: 1:1 Chats, Group Chats and Meetings
Final status: The service has remained stable for an extended period of time, and we've received confirmation from previously impacted users that the issue is resolved.
Scope of impact: The issue impacted a specific segment of the North America environment.
Start time: Tuesday, July 7, 2026, at 2:01 PM UTC
End time: Tuesday, July 7, 2026, at 2:28 PM UTC
Root cause: A networking issue caused intermittent connectivity disruptions within a service that supports chat operations. This impacted underlying dependencies used by multiple chat-related services, resulting in the observed service degradation. As caching components were unable to process requests efficiently, the volume of requests routed directly to chat services and backend databases significantly increased. This resulted in high Central Processing Unit (CPU) utilization leading to latency, frequent HTTP 500 errors, and request timeouts.
Next steps:
- For a comprehensive list of next steps, please see the Post-Incident Report.
|
|---|
|
| Time: | Tue Jul 7 11:24:06 2026 |
|---|
| Description: | Title: Issues with chat functionality in Microsoft Teams
User impact: Users may experience delays or errors when sending or receiving chat messages.
More info: This issue can impact: 1:1 Chats, Group Chats and Meetings
Other chat-specific functionalities that are impacted include, but are not limited to:
- Delays or errors when loading existing chats or channels
- Failures when attempting to share pictures or files
Current status: Telemetry continues to show improvement and the majority of core chat functionality has recovered as of 2:28 PM UTC. We’re entering a period of extended monitoring to confirm resolution, whilst in parallel, we continue to investigate the underlying root cause.
Scope of impact: The issue impacts a specific segment of the North America environment.
Start time: Tuesday, July 7, 2026, at 2:01 PM UTC
Next update by: Tuesday, July 7, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Jul 7 10:52:42 2026 |
|---|
| Description: | The volume of customer reports of impact is falling in line with our monitoring systems indicating that the service is recovering. We're continuing to investigate the underlying root cause, with the current focus on the networking layer.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jul 7 10:46:35 2026 |
|---|
| Description: | Title: Issues with chat functionality in Microsoft Teams
User impact: Users may experience delays or errors when sending or receiving chat messages.
More info: This issue can chat functionality within:
- 1:1 chats
- Group Chats
- Meetings
Additionally, loading existing chats or channels may experience delays or errors.
Current status: We're reviewing service telemetry to isolate the source of the issue. Initial assessment indicates that the service is recovering, and we're continuing to investigate.
Scope of impact: Initial analysis indicates that the issue impacts a segment of the North America environment, however, we're still confirming the scope.
Next update by: Tuesday, July 7, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Jul 7 10:32:02 2026 |
|---|
| Description: | Title: Investigating user reports of Microsoft Teams issues
User impact: We don't have detail on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
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.
|
|---|
|
EX1426511 - Users may be unable to drag and drop email messages between folders in new Outlook and Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 9 20:00:00 2026 |
|---|
| End Time: | Tue Jul 14 16:30:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 14 18:57:44 2026 |
|---|
| Root Cause: | A service-side update added additional items to the target locations of the My Day pane, which resulted in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 14 18:57:23 2026 |
|---|
| Description: | Title: Users may be unable to drag and drop email messages between folders in new Outlook and Outlook on the web
User impact: Users may have been unable to drag and drop email messages between folders in new Outlook and Outlook on the web.
More info: Users were still able to move email messages by right clicking and selecting the desired folder or they could close the My Day pane when completing drag and drop.
Final status: We've validated that the fix to correct the impact caused by the update to the My Day pane has completed deployment and the impact has been remediated.
Scope of impact: Users may have been unable to drag and drop email messages between folders in new Outlook and Outlook on the web.
Start time: Tuesday, February 10, 2026, at 1:00 AM UTC
End time: Tuesday, July 14, 2026, at 8:30 PM UTC
Root cause: A service-side update added additional items to the target locations of the My Day pane, which resulted in the impact.
Next steps:
- We're reviewing our update release standards to ensure similar issues are identified and corrected ahead of deployment to prevent this from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 14 16:54:28 2026 |
|---|
| Description: | Title: Users may be unable to drag and drop email messages between folders in new Outlook and Outlook on the web
User impact: Users may be unable to drag and drop email messages between folders in new Outlook and Outlook on the web.
More info: Users are still able to move email messages by right clicking and selecting the desired folder or they can close the My Day pane when completing drag and drop.
Current status: We've initialized the deployment of the fix, and we anticipate it will have fully saturated in the affected environment by the time of our next scheduled update.
Scope of impact: Users may be unable to drag and drop email messages between folders in new Outlook and Outlook on the web. This information may be updated as the investigation continues.
Start time: Tuesday, February 10, 2026, at 1:00 AM UTC
Root cause: A service-side update added additional items to the target locations of the My Day pane, resulting in this impacting event.
Next update by: Tuesday, July 14, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jul 14 12:18:53 2026 |
|---|
| Description: | Title: Users may be unable to drag and drop email messages between folders in new Outlook and Outlook on the web
User impact: Users may be unable to drag and drop email messages between folders in new Outlook and Outlook on the web.
More info: Users are still able to move email messages by right clicking and selecting the desired folder or they can close the My Day pane when completing drag and drop.
Current status: We've identified a service-side update that added additional items to the target location of the My Day pane, resulting in this impacting event. We've created a fix and are validating it before it’s deployed. We anticipate having an update on the deployment timeline at next communication time.
Scope of impact: Users may be unable to drag and drop email messages between folders in new Outlook and Outlook on the web. This information may be updated as the investigation continues.
Start time: Tuesday, February 10, 2026, at 1:00 AM UTC
Root cause: A service-side update added additional items to the target locations of the My Day pane, resulting in this impacting event.
Next update by: Tuesday, July 14, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Jul 13 17:30:03 2026 |
|---|
| Description: | Title: Users are unable to drag and drop email messages between folders in new Outlook and Outlook on the web
User impact: Users are unable to drag and drop email messages between folders in new Outlook and Outlook on the web.
More info: Users are still able to move email messages by right clicking and selecting the desired folder.
Current status: We're continuing to review the screen recordings and HTTP Archive format (HAR) traces provided by a subset of affected users alongside recent service-side changes in order further our understanding of this impact to assist in the development of remediation steps.
Scope of impact: Your organization is impacted by this event, and users are unable to drag and drop email messages between folders in new Outlook and Outlook on the web. This information may be updated as the investigation continues.
Next update by: Tuesday, July 14, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jul 13 16:21:09 2026 |
|---|
| Description: | Title: Users are unable to drag and drop email messages between folders in new Outlook and Outlook on the web
User impact: Users are unable to drag and drop email messages between folders in new Outlook and Outlook on the web.
Current status: We're reviewing documentation of impact, including screen recordings and HTTP Archive format (HAR) traces, provided by a subset of affected users to assist in our investigation into the underlying root cause of this event.
Scope of impact: Your organization is impacted by this event, and users are unable to drag and drop email messages between folders in new Outlook and Outlook on the web. This information may be updated as the investigation continues.
Next update by: Monday, July 13, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Jul 13 15:51:53 2026 |
|---|
| Description: | Title: Users are unable to drag and drop email messages between folders in new Outlook and Outlook on the web
User impact: Users are unable to drag and drop email messages between folders in new Outlook and Outlook on the web.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1427120 - Some users were unable to see conference room availability for Exchange Online through a room-booking application
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 13 05:00:00 2026 |
|---|
| End Time: | Tue Jul 14 06:22:42 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 14 06:24:31 2026 |
|---|
| Root Cause: | A recently enabled service change affected how free/busy request tokens were processed, resulting in HTTP 403 errors when users attempted to retrieve conference room mailbox availability information.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 14 06:23:52 2026 |
|---|
| Description: | Title: Some users were unable to see conference room availability for Exchange Online through a room-booking application
User impact: Users were unable to see conference room availability for Exchange Online through a room-booking application.
More info: Affected users may have received HTTP 403 Forbidden errors when attempting to retrieve room mailbox availability data, which prevented meeting room availability lookups, booking, and scheduling operations.
Final status: We've completed the reversion of the aforementioned change and confirmed after an extended period of monitoring that impact has now been remediated.
Scope of impact: Impact was specific to some users attempting to see conference room availability for Exchange Online through the affected third-party room-booking application.
Start time: Monday, July 13, 2026, at 9:00 PM UTC
End time: Tuesday, July 14, 2026, at 8:29 AM UTC
Root cause: A recently enabled service change affected how free/busy request tokens were processed, resulting in HTTP 403 errors when users attempted to retrieve conference room mailbox availability information.
Next steps:
- We're reviewing our service change validation procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 14 04:53:04 2026 |
|---|
| Description: | Title: Users are unable to see conference room availability for Exchange Online through a room-booking application
User impact: Users are unable to see conference room availability for Exchange Online through a room-booking application.
More info: Affected users may receive HTTP 403 Forbidden errors when attempting to retrieve room mailbox availability data, which can prevent meeting room availability lookups, booking and scheduling operations.
Current status: We've identified that a recently enabled service change is affecting how free/busy request tokens are processed, resulting in HTTP 403 errors when users attempt to retrieve conference room mailbox information. We're reverting the offending change to remediate the issue and are monitoring the deployment of the rollback to confirm it successfully restores service. We expect to provide a completion timeline when one becomes available.
Scope of impact: Your organization is affected by this event, and any user attempting to see conference room availability for Exchange Online through the affected third-party room-booking application are impacted. This information may be updated as our investigation continues.
Start time: Monday, July 13, 2026, at 9:00 PM UTC
Root cause: A recently enabled service change is affecting how free/busy request tokens are processed, resulting in HTTP 403 errors when users attempt to retrieve conference room mailbox information.
Next update by: Tuesday, July 14, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Jul 14 02:47:09 2026 |
|---|
| Description: | Title: Users are unable to see conference room availability for Exchange Online through a room-booking application
User impact: Users are unable to see conference room availability for Exchange Online through a room-booking application.
Current status: We're analyzing the error logs to help identify the source of the issue, which will help us determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and the issue impacts any user attempting to see conference room availability for Exchange Online through the affected third-party room-booking application. This information may be updated as our investigation continues.
Next update by: Tuesday, July 14, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Jul 14 02:33:20 2026 |
|---|
| Description: | Title: Users are unable to see conference room availability for Exchange Online through a room-booking application
User impact: Users are unable to see conference room availability for Exchange Online through a room-booking application.
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.
|
|---|
|
TM1411708 - Users may not receive the join option in Teams iOS for meetings or calls active on another device
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 10 20:00:00 2026 |
|---|
| End Time: | Mon Jul 13 18:14:56 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 13 18:16:12 2026 |
|---|
| Root Cause: | A latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 13 18:16:09 2026 |
|---|
| Description: | Title: Users may not receive the join option in Teams iOS for meetings or calls active on another device
User impact: Users may not have received the join option in Teams iOS for meetings or calls active on another device.
Final status: We've completed the deployment of our fix and confirmed impact was successfully remediated.
Scope of impact: Impact may have occurred for users when attempting to join Teams meetings or calls from the Microsoft Teams iOS app on a secondary device.
Start time: Thursday, June 11, 2026, at 12:00 AM UTC
End time: Monday, July 13, 2026, at 6:00 PM UTC
Root cause: A latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected.
Next steps:
- We're reviewing opportunities to improve our code review to better detect similar latent issues and prevent future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 8 19:30:24 2026 |
|---|
| Description: | Title: Users may not receive the join option in Teams iOS for meetings or calls active on another device
User impact: Users may not receive the join option in Teams iOS for meetings or calls active on another device.
Current status: Our efforts to apply the developed configuration change across the affected environment is ongoing and progressing, though it’s taking longer than initially anticipated. Based on our revised current estimations, we now anticipate this application process will be completed and issue will be resolved by our next scheduled communications update.
Scope of impact: Impact may occur for users when attempting to join Teams meetings or calls from the Microsoft Teams iOS app on a secondary device. This section may be updated as our investigation continues.
Start time: Thursday, June 11, 2026, at 12:00 AM UTC
Root cause: A latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected.
Next update by: Tuesday, July 14, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Jul 1 19:23:59 2026 |
|---|
| Description: | Title: Users may not receive the join option in Teams iOS for meetings or calls active on another device
User impact: Users may not receive the join option in Teams iOS for meetings or calls active on another device.
Current status: We’re continuing to apply the aforementioned configuration and as this deployment process progresses across the affected environments, users should start seeing mitigation. We anticipate this deployment process will be completed by our next scheduled communications update.
Scope of impact: Impact may occur for users joining Teams meetings or calls from the Microsoft Teams iOS app on a secondary device. This section may be updated as our investigation continues.
Start time: Thursday, June 11, 2026, at 12:00 AM UTC
Root cause: A latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected.
Next update by: Thursday, July 9, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Jul 1 18:05:53 2026 |
|---|
| Description: | Title: Users may not receive the join option in Teams iOS for meetings or calls active on another device
User impact: Users may not receive the join option in Teams iOS for meetings or calls active on another device.
Current status: We've received reports from affected users that users may not receive the join option in the Microsoft Teams iOS app for meetings or calls active on another device. Our analysis has identified that a latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected. We've developed a configuration change, which we're applying across all affected environments while monitoring the deployment to ensure successful remediation.
Scope of impact: Impact may occur for users joining Teams meetings or calls from the Microsoft Teams iOS app on a secondary device.
Start time: Thursday, June 11, 2026, at 12:00 AM UTC
Root cause: A latent code issue introduced a dependency on an authentication configuration, preventing the companion join banner from functioning as expected.
Next update by: Wednesday, July 1, 2026, at 11:30 PM UTC
|
|---|
|
TM1423737 - Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 8 20:00:00 2026 |
|---|
| End Time: | Mon Jul 13 16:15:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 13 18:15:47 2026 |
|---|
| Root Cause: | The Microsoft Teams for Mac presentation encoder was producing distortion issues when encoding some non-aligned resolutions, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 13 18:15:27 2026 |
|---|
| Description: | Title: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings
User impact: Mac users may have seen distorted content when sharing their full screen in Microsoft Teams meetings or recordings.
Final status: We've completed deploying a code fix, and we've validated with internal testing and monitoring that it successfully remediates the issue. If users are still experiencing impact, they may need to restart their Microsoft Teams client to receive the fix.
Scope of impact: This issue may have impacted Microsoft Teams for Mac users on client versions 26134.1610.4759.7759, 26149.1804.4788.5681, and 26163.407.4839.8659 when attempting to share their full screen in Microsoft Teams meetings.
Start time: Thursday, July 9, 2026, at 12:00 AM UTC
End time: Monday, July 13, 2026, at 8:15 PM UTC
Root cause: The Microsoft Teams for Mac presentation encoder was producing distortion issues when encoding some non-aligned resolutions, which resulted in impact.
Next steps:
- We're further reviewing the Microsoft Teams for Mac presentation encoder to identify what caused it to produce distortion issues when encoding some non-aligned resolutions, to gain a further understanding of the underlying root cause, and to prevent similar impact from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 13 14:55:34 2026 |
|---|
| Description: | Title: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings
User impact: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings.
More info: As a way to bypass impact, affected users may experience improvement by attempting any of the following methods:
- Share a specific application window instead of the entire screen.
- Adjust the display resolution to be at or below 1710 × 1112 (e.g., 1512 × 982).
- Utilizing the Teams web client, if available.
Impact is specific to Microsoft Teams MacOS client versions 26134.1610.4759.7759, 26149.1804.4788.5681, and 26163.407.4839.8659.
Current status: We're continuing our efforts to assess and develop potential remediation strategies in order to correct the encoder distortion issue and remediate all impact.
Scope of impact: This issue may impact Microsoft Teams for Mac users on client versions 26134.1610.4759.7759, 26149.1804.4788.5681, and 26163.407.4839.8659 when attempting to share their full screen in Microsoft Teams meetings. This section may be updated as our investigation continues.
Root cause: The Microsoft Teams for Mac presentation encoder is producing distortion issues when encoding some non-aligned resolutions, which is resulting in impact.
Next update by: Monday, July 13, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Mon Jul 13 12:51:54 2026 |
|---|
| Description: | Title: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings
User impact: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings.
More info: As a way to bypass impact, affected users may experience improvement by attempting any of the following methods:
- Share a specific application window instead of the entire screen
- Adjust the display resolution to be at or below 1710 × 1112 (e.g., 1512 × 982).
- Utilizing the Teams web client, if available.
Impact is specific to Microsoft Teams MacOS client versions 26134.1610.4759.7759, 26149.1804.4788.5681, and 26163.407.4839.8659.
Current status: We've determined that the Microsoft Teams for Mac presentation encoder is producing distortion issues when encoding some non-aligned resolutions, which is resulting in impact. We’re assessing potential remediation strategies aimed at correcting this encoder distortion issue and resolving impact.
Scope of impact: This issue may impact Microsoft Teams for Mac users on client versions 26134.1610.4759.7759, 26149.1804.4788.5681, and 26163.407.4839.8659 when attempting to share their full screen in Microsoft Teams meetings. This section may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 12:00 AM UTC
Root cause: The Microsoft Teams for Mac presentation encoder is producing distortion issues when encoding some non-aligned resolutions, which is resulting in impact.
Next update by: Monday, July 13, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Sat Jul 11 16:01:49 2026 |
|---|
| Description: | Title: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings
User impact: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings.
More info: As a temporary workaround, affected users may experience improvement by changing their display resolution settings or adjusting the size of the shared application window before initiating screen sharing.
Current status: While our investigation into the potential screen resolution configuration issue is ongoing, we're providing as subset of affected users with a temporary workaround to modify the size of the shared window to the standard resolution, which should restore functionality while we investigate.
Scope of impact: This issue may impact Microsoft Teams for Mac users on client versions 26134.1610.4759.7759, 26149.1804.4788.5681, and 26163.407.4839.8659 when attempting to share their full screen in Microsoft Teams meetings. This section may be updated as our investigation continues.
Next update by: Monday, July 13, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Sat Jul 11 10:26:12 2026 |
|---|
| Description: | Title: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings
User impact: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings.
More info: As a temporary workaround, affected users may experience improvement by changing their display resolution settings or adjusting the size of the shared application window before initiating screen sharing.
Current status: We've observed that the issue may be related to a specific screen resolution configuration used on macOS devices. We're reviewing diagnostic data and telemetry to validate this theory, identify the underlying cause, and determine the appropriate mitigation steps.
Scope of impact: This issue may impact Microsoft Teams for Mac users on client versions 26134.1610.4759.7759, 26149.1804.4788.5681, and 26163.407.4839.8659 when attempting to share their full screen in Microsoft Teams meetings. This section may be updated as our investigation continues.
Next update by: Saturday, July 11, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Sat Jul 11 08:46:50 2026 |
|---|
| Description: | Title: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings
User impact: Mac users may see distorted content when sharing their full screen in Microsoft Teams meetings or recordings.
Current status: We’re reviewing associated support case details to understand more about the issue, and determine our next troubleshooting steps.
Scope of impact: This issue may impact Microsoft Teams for Mac users on client versions 26134.1610.4759.7759, 26149.1804.4788.5681, and 26163.407.4839.8659 when attempting to share their full screen in Microsoft Teams meetings. This section may be updated as our investigation continues.
Next update by: Saturday, July 11, 2026, at 3:00 PM UTC
|
|---|
|
TM1402778 - Some users may have been unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 21 21:16:00 2026 |
|---|
| End Time: | Thu Jul 9 08:45:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 13 14:19:20 2026 |
|---|
| Root Cause: | A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identified the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 10 05:39:12 2026 |
|---|
| Description: | Title: Some users may have been unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may have been unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact was specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appeared to have been installed and enabled in classic Outlook; however, it wasn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Final status: We've confirmed that the deployment has successfully completed and validated through service health telemetry that the issue has been resolved and impact no longer persists.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may have been impacted.
Start time: Monday, June 22, 2026, at 1:16 AM UTC
End time: Thursday, July 9, 2026, at 12:45 PM UTC
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identified the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 6 06:46:33 2026 |
|---|
| Description: | Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Users that have access to the new Outlook client or Microsoft Teams desktop or web apps can use these to schedule Microsoft Teams meetings and bypass the impact while we're focused on addressing the impact caused by this event.
Current status: We've deployed the fix to the majority of the affected environments and, due to unforeseen delays, we're expecting the fix to be deployed by Friday, July 10, 2026.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Estimated time to resolve: Friday, July 3, 2026
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Friday, July 10, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Fri Jul 3 03:59:45 2026 |
|---|
| Description: | Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Users that have access to the new Outlook client or Microsoft Teams desktop or web apps can use these to schedule Microsoft Teams meetings and bypass the impact while we're focused on addressing the impact caused by this event.
Current status: We're continuing to expect that the deployment will be complete by the end of Friday, July 3, 2026. Following deployment, we will closely monitor the affected environments over an extended period to confirm that impact has been fully resolved.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Estimated time to resolve: Friday, July 3, 2026
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Monday, July 6, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Jul 1 05:58:20 2026 |
|---|
| Description: | Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Users that have access to the new Outlook client or Microsoft Teams desktop or web apps can use these to schedule Microsoft Teams meetings and bypass the impact while we're focused on addressing the impact caused by this event.
Current status: We're progressing with deploying the fix, and the deployment is expected to complete by Friday, July 3, 2026.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Estimated time to resolve: Friday, July 3, 2026
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Friday, July 3, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Mon Jun 29 14:42:10 2026 |
|---|
| Description: | Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Users that have access to the new Outlook client or Microsoft Teams desktop or web apps can use these to schedule Microsoft Teams meetings and bypass the impact while we're focused on addressing the impact caused by this event.
Current status: We've identified and outlined a method in the More info section of this communication to bypass the impact by utilizing the new Outlook client or Microsoft Teams desktop and web apps, and we've updated the More info section of this communication with this information. We're continuing to deploy our fix, and we expect to have an update on its progress by our next communication update.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Wednesday, July 1, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Jun 24 06:12:54 2026 |
|---|
| Description: | Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Current status: We've determined that a recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments. As a result, the add-in may fail to load, preventing affected users from scheduling Microsoft Teams meetings through Outlook. We've developed a fix to address this behavior and are working to expedite its deployment. To limit additional exposure, we've stopped further rollout of the affected change while we progress deployment activities for the updated fix. Based on our current estimates, we anticipate that the fix will be available by Friday, July 3, 2026.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Wednesday, July 1, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Jun 24 04:30:24 2026 |
|---|
| Description: | Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Current status: We're reviewing support case details to determine our next troubleshooting steps.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Next update by: Wednesday, June 24, 2026, at 10:30 AM UTC
|
|---|
|
OD1424850 - Some users may have been unable to access Microsoft OneDrive content and may have noticed delays or navigation errors
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jul 12 06:20:00 2026 |
|---|
| End Time: | Sun Jul 12 06:44:00 2026 |
|---|
| Service: | Microsoft OneDrive |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sun Jul 12 07:42:14 2026 |
|---|
| Root Cause: | A section of SQL database infrastructure is performing below acceptable performance thresholds and resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jul 12 07:41:58 2026 |
|---|
| Description: | Title: Some users may have been unable to access Microsoft OneDrive content and may have noticed delays or navigation errors
User impact: Users may have been unable to access OneDrive content and may have noticed delays or navigation errors.
Final status: We’ve confirmed, following a period of monitoring service telemetry, that redirecting user traffic to alternate infrastructure successfully resolved the issue.
Scope of impact: This issue impacted internal Microsoft users only.
Start time: Sunday, July 12, 2026, at 10:20 AM UTC
End time: Sunday, July 12, 2026, at 10:44 AM UTC
Root cause: A section of SQL database infrastructure is performing below acceptable performance thresholds and 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: | Sun Jul 12 06:44:11 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft OneDrive content and may notice delays or navigation errors
User impact: Users may be unable to access OneDrive content and may notice delays or navigation errors.
Current status: We’ve identified that a section of SQL database infrastructure is performing below acceptable performance thresholds and resulting in impact. We’ve redirected user traffic to alternate infrastructure in attempt to restore the service.
Scope of impact: This issue impacts internal Microsoft users only.
Start time: Sunday, July 12, 2026, at 10:20 AM UTC
Root cause: A section of SQL database infrastructure is performing below acceptable performance thresholds and resulting in impact.
Next update by: Sunday, July 12, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Sun Jul 12 06:30:45 2026 |
|---|
| Description: | Title: Potential issues accessing Microsoft OneDrive content
User impact: Users may be unable to access OneDrive content and may notice delays or navigation errors.
Current Status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
MO1421789 - Admins' Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 7 20:00:00 2026 |
|---|
| End Time: | Sat Jul 11 03:37:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jul 11 12:27:27 2026 |
|---|
| Root Cause: | The report source data, which provides Microsoft 365 group information, was delayed and caused overall report publishing to have been delayed for Microsoft 365 Groups, Teams user, and Teams device reports, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jul 11 12:25:11 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Microsoft 365 Groups, Teams user, and device reports may have been delayed in the Microsoft 365 admin center.
More info: The last refresh date for Teams device and Teams user reports was Tuesday, July 7, 2026. The last refresh date for Microsoft 365 Groups reports was Friday, July 3, 2026.
Final status: We've confirmed through monitoring service health telemetry that all affected reports are up to date within the Microsoft 365 admin center.
Scope of impact: Any admin viewing Microsoft 365 Groups, Teams user, or Teams device reports in the Microsoft 365 admin center may have been impacted.
Start time: Wednesday, July 8, 2026, at 12:00 AM UTC
End time: Saturday, July 11, 2026, at 7:37 AM UTC
Root cause: The report source data, which provides Microsoft 365 group information, was delayed and caused overall report publishing to have been delayed for Microsoft 365 Groups, Teams user, and Teams device reports, resulting in impact.
Next steps:
- We're reviewing the offending source data to understand what caused the delay, so that we can prevent similar instances of impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 10 12:58:32 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center.
More info: The last refresh date for Teams device and Teams user reports is Tuesday, July 7, 2026. The last refresh date for Microsoft 365 Groups reports is Friday, July 3, 2026.
Current status: We've determined that the report source data, which provides Microsoft 365 group information, is delayed and causing overall report publishing to be delayed for Microsoft 365 Groups, Teams user, and Teams device reports. We've since confirmed that our data pipelines have received and processed the necessary source data required for these reports. We're monitoring as our service streams for each mentioned report type obtain this data and subsequently remediates impact.
Scope of impact: Any admin viewing Microsoft 365 Groups, Teams user, or Teams device reports in the Microsoft 365 admin center may be impacted.
Start time: Wednesday, July 8, 2026, at 12:00 AM UTC
Root cause: The report source data, which provides Microsoft 365 group information, is delayed and causing overall report publishing to be delayed for Microsoft 365 Groups, Teams user, and Teams device reports, resulting in impact.
Next update by: Saturday, July 11, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 9 14:35:31 2026 |
|---|
| Description: | Title: Admin's Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center
User impact: Admin's Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center.
More info: The last refresh date for these reports is Friday, July 3, 2026.
Current status: Our service health monitoring alerted us to delays occurring when publishing Microsoft 365 Groups, Teams user, and Teams device reporting data to the Microsoft 365 admin center. While we investigate the portion of service infrastructure responsible for relaying this reporting data to the Microsoft 365 admin center to isolate the source of the delays, our service health telemetry indicates the data has begun processing. We're monitoring the data to ensure that it continues to process while we determine a strategy to expedite its processing.
Scope of impact: Any admin viewing Microsoft 365 Groups, Teams user, or Teams device reports in the Microsoft 365 admin center may be impacted.
Start time: Wednesday, July 8, 2026, at 12:00 AM UTC
Next update by: Friday, July 10, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 9 14:02:14 2026 |
|---|
| Description: | Title: Admin's Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center
User impact: Admin's Microsoft 365 Groups, Teams user, and Teams device reports may be delayed in the Microsoft 365 admin center.
More info: The last refresh date for these reports is Friday, July 3, 2026.
Current status: We're investigating a potential issue with reports in the Microsoft 365 admin center and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1423133 - Users receive invoice notification emails that don't contain the associated PDF attachments
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 10 19:59:44 2026 |
|---|
| End Time: | Fri Jul 10 20:52:47 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Purchase and Billing |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 10 20:54:26 2026 |
|---|
| Root Cause: | A recent service update changed the flow of certain data inputs utilized in this function, which resulted in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 10 20:54:23 2026 |
|---|
| Description: | Title: Users receive invoice notification emails that don't contain the associated PDF attachments
User impact: Users received invoice notification emails that didn't contain the associated PDF attachments.
More info: This event didn't impact access to invoice documents, and users with the appropriate access and permissions could continue to access and download their invoice PDFs directly from the Microsoft 365 Admin Center during impact.
Final status: We determined that a recent service update changed the flow of certain data inputs utilized in this function, which resulted in this impact. We developed and deployed a fix to address this error and have confirmed that this has successfully restored functionality.
Scope of impact: Your organization was impacted by this event, and users received invoice notification emails that didn't contain the associated PDF attachments.
Start time: Monday, June 8, 2026, at 7:24 PM UTC
End time: Thursday, July 9, 2026, at 6:38 PM UTC
Root cause: A recent service update changed the flow of certain data inputs utilized in this function, which resulted in this 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 Jul 10 20:00:52 2026 |
|---|
| Description: | Title: Users receive invoice notification emails that don't contain the associated PDF attachments
User impact: Users received invoice notification emails that didn't contain the associated PDF attachments.
More info: This event didn't impact access to invoice documents, and users with the appropriate access and permissions could continue to access and download their invoice PDFs directly from the Microsoft 365 Admin Center during impact.
Current status: We've investigated a problem in which users received invoice notification emails that didn't contain the associated PDF attachments and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
DZ1421829 - Admins may see delays to threat intelligence reports in the Security Operation Center (SOC)
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 9 08:00:00 2026 |
|---|
| End Time: | Thu Jul 9 21:30:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 10 01:09:23 2026 |
|---|
| Root Cause: | A portion of the infrastructure utilized in this function was performing below optimal thresholds and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 10 01:09:23 2026 |
|---|
| Description: | Title: Admins may see delays to threat intelligence reports in the Security Operation Center (SOC)
User impact: Admins may have seen delays to threat intelligence reports in the SOC.
More info: Users’ threat intelligence reports may have had delays of three to five hours.
Final status: We’ve addressed the aforementioned backend issue and confirmed after monitoring that the backlog of affected data has completed processing.
Scope of impact: This event impacted admins in North America and Europe, who may have seen delays to threat intelligence reports in the SOC.
Start time: Thursday, July 9, 2026, at 12:00 PM UTC
End time: Friday, July 10, 2026, at 1:30 AM UTC
Root cause: A portion of the infrastructure utilized in this function was performing below optimal thresholds and resulted in impact.
Next steps:
- We're analyzing the affected portion of infrastructure to better understand why it was performing below the optimal threshold so that we can prevent impact to threat intelligence reports in the SOC in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 9 17:59:56 2026 |
|---|
| Description: | Title: Admins may see delays to threat intelligence reports in the Security Operation Center (SOC)
User impact: Admins may see delays to threat intelligence reports in the SOC.
More info: Users may experience threat intelligence report delays of 3 to 5 hours.
Current status: An issue on the backend has delayed the backlog process. We're addressing this issue and continuing to actively monitor as the backlog continues to process.
Scope of impact: This event impacts admins in North America and Europe, who may see delays to threat intelligence reports in the SOC. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 12:00 PM UTC
Root cause: A portion of the infrastructure utilized in this function was performing below optimal thresholds, resulting in impact.
Next update by: Friday, July 10, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Jul 9 15:05:36 2026 |
|---|
| Description: | Title: Admins may see delays to threat intelligence reports in the Security Operation Center (SOC)
User impact: Admins may see delays to threat intelligence reports in the SOC.
More info: Users may experience threat intelligence report delays of 3 to 5 hours.
Current status: We determined that a portion of the infrastructure utilized in this function was performing below optimal thresholds. We restarted the responsible portion of infrastructure and applied load balancing measures to mitigate this impact. We're monitoring as the backload processes, which we anticipate will be completed by our next scheduled update.
Scope of impact: This event impacts admins in North America and Europe, who may see delays to threat intelligence reports in the SOC. This information may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 12:00 PM UTC
Next update by: Thursday, July 9, 2026, at 11:00 PM UTC
|
|---|
|
EX1422126 - Users in North America may be unable to access their mailboxes through any connection method in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 9 20:05:00 2026 |
|---|
| End Time: | Thu Jul 9 21:22:45 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 9 21:27:57 2026 |
|---|
| Root Cause: | A parallel impact caused by a configuration change included a rollback, which may have prevented users from accessing Exchange Online. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 9 21:27:25 2026 |
|---|
| Description: | Title: Users in North America may be unable to access their mailboxes through any connection method in Exchange Online
User impact: Users in North America may have been unable to access their mailboxes through any connection method in Exchange Online.
Final status: Through our analysis of service health telemetry and alert monitoring reports, we've confirmed that all methods of access have been restored.
Scope of impact: This issue affects users in North America who are attempting to access their mailboxes through any method. This information may be updated as our investigation continues.
Start time: Friday, July 10, 2026, at 12:05 AM UTC
End time: Friday, July 10, 2026, at 12:30 AM UTC
Root cause: A parallel impact caused by a configuration change included a rollback, which may have prevented users from accessing Exchange Online.
|
|---|
|
| Time: | Thu Jul 9 20:50:01 2026 |
|---|
| Description: | Title: Users in North America may be unable to access their mailboxes through any connection method in Exchange Online
User impact: Users in North America may be unable to access their mailboxes through any connection method in Exchange Online.
Current status: We're analyzing service health telemetry and system monitoring results to understand the scope of the impact.
Scope of impact: This issue affects users in North America who are attempting to access their mailboxes through any method. This information may be updated as our investigation continues.
Next update by: Friday, July 10, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Jul 9 20:21:07 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.
|
|---|
|
MF1422187 - Some users experience latency and intermittent failures running flows through Microsoft Power Automate
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 7 00:44:00 2026 |
|---|
| End Time: | Thu Jul 9 20:00:00 2026 |
|---|
| Service: | Microsoft Power Automate in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 9 21:25:57 2026 |
|---|
| Root Cause: | The components of infrastructure responsible for facilitating the affected flows were operating below expected performance thresholds due to a code regression which was contained within a recent service change. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 9 21:18:56 2026 |
|---|
| Description: | Title: Some users experience latency and intermittent failures running flows through Microsoft Power Automate
User impact: Users experienced latency and intermittent failures running flows through Microsoft Power Automate.
Final status: Our internal service monitors identified an issue associated with latency and intermittent failures when running flows in Microsoft Power Automate. Following our initial analysis, we determined that the components of infrastructure responsible for facilitating the affected flows were operating below expected performance thresholds due to a code regression which was contained within a recent service change. We’ve since reverted this change, applied a targeted fix to restore flow operations and after an extended period of monitoring the service health telemetry, we confirmed that impact was remediated.
Scope of impact: Your organization was affected by this event, and some users who attempted to run flows in Microsoft Power Automate were impacted.
Start time: Tuesday, July 7, 2026, at 4:44 AM UTC
End time: Friday, July 10, 2026, at 12:00 AM UTC
Root cause: The components of infrastructure responsible for facilitating the affected flows were operating below expected performance thresholds due to a code regression which was contained within a recent service change.
Next steps:
- We’re continuing to analyze how the code issue contained within the service update manifested to understand why the potential for impact wasn't caught during the update testing and validation phase. This analysis will help us to clarify what actions we can take to ensure similar impact doesn't occur in the future and will allow us to continue our ongoing mission to improve the resilience of our service for all Microsoft Power Automate Online users.
This is the final update for the event.
|
|---|
|
MP1418963 - Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 6 00:00:00 2026 |
|---|
| End Time: | Tue Jul 7 18:00:00 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 8 16:26:07 2026 |
|---|
| Root Cause: | A storage account upon which Graph API is dependent is in an unhealthy state, which resulted in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 8 14:55:32 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may have been unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users received a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may have prevented users from retrieving or managing eDiscovery case information via API integrations.
Final status: We've confirmed with a subset of affected users that resetting the affected storage account has successfully resolved this impact.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may have been impacted by this event.
Start time: Monday, July 6, 2026, at 4:00 AM UTC
End time: Tuesday, July 7, 2026, at 10:00 PM UTC
Root cause: A storage account upon which Graph API is dependent is in an unhealthy state, which resulted in the impact.
Next steps: - We're reviewing the responsible storage account to better understand the impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 7 19:19:45 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: We've determined a storage account upon which Graph API depends is in an unhealthy state, resulting in impact. We've reset the affected storage account to resolve this issue, and we're reaching out to your representatives to confirm if our actions have remediated impact.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so. This is subject to change as our investigation continues.
Start time: Monday, July 6, 2026, at 4:00 AM UTC
Root cause: A storage account upon which Graph API is dependent is in an unhealthy state, resulting in the impact.
Next update by: Wednesday, July 8, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jul 7 15:49:03 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: We've identified that there's a dependent storage account that requires a reset and have completed that action; we're monitoring the service health telemetry to determine if this action will fully resolve impact as expected. In parallel, we're continuing to validate the previously identified routing corrections as well. These actions will aid us in pinpointing the root cause and determine if any additional actions will be needed to resolve the issue.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so.
Next update by: Wednesday, July 8, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Jul 7 12:40:53 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: Our HTTP Archive log analysis has identified a Graph network routing issue that we believe could be preventing users from accessing Microsoft Purview eDiscovery cases through the Microsoft Graph API. As we work to verify our findings and confirm the source for this event, we're updating the Graph network routing in our effort to remediate the impact.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so.
Next update by: Tuesday, July 7, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jul 7 09:02:14 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: We’re reviewing HTTP Archive (HAR) logs to identify the source of the issue and determine the mitigation plan.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so.
Next update by: Tuesday, July 7, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jul 7 07:06:38 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API
User impact: Users may be unable to access Microsoft Purview eDiscovery cases through the Microsoft Graph API.
More info: Affected users receive a HTTP 500 (Internal Server Error) message when attempting to access Microsoft Purview eDiscovery cases through Microsoft Graph API requests. This may prevent users from retrieving or managing eDiscovery case information via API integrations.
Current status: We’re reviewing support case details provided by a subset of impacted users to understand more about the issue and determine our next troubleshooting steps.
Scope of impact: Users attempting to access Microsoft Purview eDiscovery cases through the Microsoft Graph API may be unable to do so.
Next update by: Tuesday, July 7, 2026, at 1:00 PM UTC
|
|---|
|
CP1412506 - Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 2 10:12:49 2026 |
|---|
| End Time: | Wed Jul 8 11:57:06 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 8 12:25:34 2026 |
|---|
| Root Cause: | A recent update to the service introduced an error into the editing custom connector experience that resulted in an incomplete set of data to be sent over when making edits to custom connectors.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 8 12:25:30 2026 |
|---|
| Description: | Title: Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users may have been unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users were unable to open or edit connectors as crawl attempts failed with error 1015 and 3191.
Final status: We've confirmed that a recent update to the service introduced an issue where the connector details weren't fully loaded when users made an edit to the custom connector. We created a code correction to ensure connector details are loaded correctly and confirmed with some previously reporting users that the issue is resolved after monitoring service health for an extended period of time.
Scope of impact: Impact was specific to some users attempting to manage custom Microsoft Graph connectors in Microsoft 365 Copilot.
Start time: Sunday, June 21, 2026, at 6:00 PM UTC
End time: Monday, July 6, 2026, at 6:00 PM UTC
Root cause: A recent update to the service introduced an error into the editing custom connector experience that resulted in an incomplete set of data to be sent over when making edits to custom connectors.
Next steps: - We're reviewing our testing procedures to determine how this wasn't identified prior to deployment and why the connector details were incomplete so we can prevent similar issues from recurring in future updates.
This is the final update for this event.
|
|---|
|
| Time: | Wed Jul 8 10:31:03 2026 |
|---|
| Description: | Title: Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users may be unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: We've deployed the fix and received feedback from your representatives to say that the issue is resolved. We're conducting an extended period of monitoring service telemetry to verify the root cause of impact.
Scope of impact: Impact is specific to some users attempting to manage custom Microsoft Graph connectors in Microsoft 365 Copilot.
Next update by: Wednesday, July 8, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Jul 7 10:38:07 2026 |
|---|
| Description: | Title: Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users may be unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: The deployment of the fix is progressing as expected. Once deployment is complete in the affected environment, we will work with your representative to validate that the fix is working as intended. Based on the results of this testing, we will determine next steps and further validate our root cause hypothesis.
Scope of impact: Impact is specific to some users attempting to manage custom Microsoft Graph connectors in Microsoft 365 Copilot.
Next update by: Wednesday, July 8, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Jul 6 10:50:26 2026 |
|---|
| Description: | Title: Users may be unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users may be unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: Due to unforeseen delays in the rollout process, deployment of the fix has taken longer than originally anticipated. We've now deployed the fix and are monitoring its propagation as it continues to rollout across the affected environment. We anticipate deployment to complete by Friday, July 10, 2026.
Scope of impact: Impact is specific to some users attempting to manage custom Microsoft Graph connectors in Microsoft 365 Copilot.
Next update by: Tuesday, July 7, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Jul 2 18:05:04 2026 |
|---|
| Description: | Title: Users can't manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users can't manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: Based on our initial code analysis, we suspect a recent user interface (UI) migration has introduced a logic conflict which is resulting in impact. While we continue our debugging to confirm this theory, we're developing a solution to correct the logic conflict and remediate impact. We anticipate this fix will be prepared to deploy by our next scheduled update and will remediate the impact by Tuesday, July 7, 2026.
Scope of impact: Your organization is affected by this event, and some users attempting to manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Monday, July 6, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Thu Jul 2 16:05:42 2026 |
|---|
| Description: | Title: Users can't manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users can't manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: We've been able to achieve an internal reproduction of the issue, and we're leveraging this ability to further our code analysis in an effort to identify the underlying root cause.
Scope of impact: Your organization is affected by this event, and some users attempting to manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Thursday, July 2, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Jul 2 14:23:38 2026 |
|---|
| Description: | Title: Users can't manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users can't manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: Our initial review of the HAR file and screen recordings has been inconclusive. We're analyzing the custom Graph connector code, as well as determining whether we can reproduce the issue within our internal testing environment for further analysis.
Scope of impact: Your organization is affected by this event, and some users attempting to manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Thursday, July 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 2 12:28:36 2026 |
|---|
| Description: | Title: Users can't manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users can't manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts fail with error 1015 and 3191.
Current status: We've received a fresh HTTP Archive (HAR) file and recordings from your organization to aid in our efforts to identify the source of the issue.
Scope of impact: Your organization is affected by this event, and some users attempting to manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Thursday, July 2, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jul 2 10:19:09 2026 |
|---|
| Description: | Title: Users are unable to manage custom Microsoft Graph connectors in Microsoft 365 Copilot
User impact: Users are unable to manage custom Microsoft Graph connectors in Copilot.
More info: Affected users are unable to open or edit connectors as crawl attempts to fail with error 1015 and 3191.
Current status: We’re reviewing associated support case details to understand more about the issue, and determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to manage custom Microsoft Graph connectors in Copilot are impacted.
Next update by: Thursday, July 2, 2026, at 4:30 PM UTC
|
|---|
|
CW1420563 - Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat
| Status: | investigationSuspended |
|---|
| Start Time: | Tue Jul 7 21:29:00 2026 |
|---|
| End Time: | Wed Jul 8 11:03:39 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 8 11:16:25 2026 |
|---|
| Root Cause: | An update to the Copilot Chat service that made GPT 5.5 the default model caused the GPT 5.5 menu entries to disappear from the Selector menu.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 8 11:08:28 2026 |
|---|
| Description: | Title: Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat
User impact: Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat.
More info: Affected users may notice that the model selector from Microsoft 365 Copilot chat is missing some GPT options.
The Auto, Quick Response, and Think Deeper options are available and working as expected, while the rest of the Copilot functionality remains unaffected.
Final status: Our investigation has confirmed that the disappearance of the GPT 5.5 menu entries is a consequence of GPT-5.5 becoming the default model. As GPT-5.5 becomes the default experience, those nested GPT options are automatically suppressed because they effectively map to the same underlying model now exposed through Auto, Quick Response, and Think Deeper options. This type of selector menu will reappear when additional models become available for selection.
Additionally, we're exploring options to potentially provide additional guidance through updated documentation and in-product guidance around to which model Auto, Quick Response, and Think Deeper are mapped.
Scope of impact: Impact is specific to some users attempting to view or select specific GPT-based models in Microsoft 365 Copilot chat.
Root cause: An update to the Copilot Chat service that made GPT 5.5 the default model caused the GPT 5.5 menu entries to disappear from the Selector menu.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 8 08:52:47 2026 |
|---|
| Description: | Title: Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat
User impact: Users may be unable to view or select specific GPT-based models in Microsoft 365 Copilot chat.
More info: Affected users may notice that the model selector from Microsoft 365 Copilot chat is missing some GPT options.
The Auto, Quick Response, and Think Deeper options are available and working as expected, while the rest of the Copilot functionality remains unaffected.
Current status: We're investigating reports that certain model selector options aren't being returned, which is preventing affected users from selecting some GPT models in Microsoft 365 Copilot. We're reviewing service monitoring telemetry alongside support provided information to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users attempting to view or select specific GPT-based models in Microsoft 365 Copilot chat.
Next update by: Wednesday, July 8, 2026, at 3:00 PM UTC
|
|---|
|
MO1419441 - Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 7 13:04:11 2026 |
|---|
| End Time: | Tue Jul 7 15:55:21 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 7 16:10:28 2026 |
|---|
| Root Cause: | An unexpected number of alerts overwhelmed the service infrastructure and was preventing admins from recieveing alerts as expected.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 7 16:10:11 2026 |
|---|
| Description: | Title: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal
User impact: Admins didn't receive alerts for up to three hours in the Microsoft Defender XDR portal.
More info: This impacted Microsoft Defender for Cloud Apps and Entra ID Identity Protection alerts.
Final status: Our fix skipped duplicate alerts and significantly increased the speed at which the affected infrastructure processed the alert backlog. The backlog is now completely processed and alert latencies have returned to normal.
Scope of impact: Your organization was affected by this event, and any admin recieveing alerts in the Microsoft Defender XDR portal was impacted.
Start time: Tuesday, July 7, 2026, at 11:10 AM UTC
End time: Tuesday, July 7, 2026, at 7:25 PM UTC
Root cause: An unexpected number of alerts overwhelmed the service infrastructure and was preventing admins from recieveing alerts as expected.
Next steps: We're reviewing the alert process to identify and create a more efficient alerting method that prevents duplicate alerts from causing impact in the future.
|
|---|
|
| Time: | Tue Jul 7 15:22:28 2026 |
|---|
| Description: | Title: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal
User impact: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal.
More info: This impacts Microsoft Defender for Cloud Apps and Entra ID Identity Protection alerts.
Current status: We've identified and deployed a fix that introduces a method of skipping duplicate alerts to significantly increase the speed at which the affected infrastructure processes the alert backlog. We expect this should completely remediate impact by our next schedule update.
Scope of impact: Your organization is affected by this event, and any admin recieveing alerts in the Microsoft Defender XDR portal is impacted.
Start time: Tuesday, July 7, 2026, at 11:10 AM UTC
Root cause: An unexpected number of alerts has overwhelmed the service infrastructure and is preventing admins from recieveing alerts as expected.
Next update by: Tuesday, July 7, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jul 7 13:47:38 2026 |
|---|
| Description: | Title: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal
User impact: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal.
More info: This impacts Microsoft Defender for Cloud Apps and Entra ID Identity Protection alerts.
Current status: We've determined that an unexpected number of alerts has overwhelmed the service infrastructure and is preventing admins from recieveing alerts as expected. We're seeking methods of expediting the processing of these alerts to remediate impact.
Scope of impact: Your organization is affected by this event, and any admin recieveing alerts in the Microsoft Defender XDR portal is impacted.
Start time: Tuesday, July 7, 2026, at 11:10 AM UTC
Root cause: An unexpected number of alerts has overwhelmed the service infrastructure and is preventing admins from recieveing alerts as expected.
Next update by: Tuesday, July 7, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jul 7 13:18:40 2026 |
|---|
| Description: | Title: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal
User impact: Admins don't receive alerts for up to three hours in the Microsoft Defender XDR portal.
More info: this impacts Microsoft Defender for Cloud Apps and Entra ID Identity Protection alerts.
Current status: We're investigating a potential issue with Microsoft Defender XDR portal and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1409288 - Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 23 13:00:00 2026 |
|---|
| End Time: | Tue Jul 7 12:16:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 7 15:40:00 2026 |
|---|
| Root Cause: | A recent change intended to improve the file preview experience for Copilot Chat caused errors when users attempted to open linked files.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 7 15:39:09 2026 |
|---|
| Description: | Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may have been unable to view SharePoint Online files that were linked by Copilot Chat or Copilot agents.
More info: When users selected the link to a SharePoint Online file that was provided by Copilot Chat or Copilot agents, they may have received an error that said, "We couldn't show the file."
The issue may have also impacted links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Despite users being unable to open the links from Copilot agents or Copilot chat, there was no unretrievable data, and the files could have been accessed directly.
Final status: We've completed deployment of our long-term fix, and we confirmed with a subset of affected users that the functionality was restored and that clicking the links opened the SharePoint Online files in the same window as expected.
Scope of impact: This issue may have potentially impacted any user attempting to view SharePoint Online files that were linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
End time: Tuesday, July 7, 2026, at 4:16 PM UTC
Root cause: A recent change intended to improve the file preview experience for Copilot Chat caused errors when users attempted to open linked files.
Next steps:
- We're reviewing our service change testing and validation procedures to identify and prevent similar issues when deploying changes to the file preview experience moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 30 16:09:47 2026 |
|---|
| Description: | Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: We've completed the deployment and confirmed with your organization that the affected users are now able to select the link, which opens the SharePoint Online files in a separate tab as a short-term fix. We're validating the efficacy of a long-term fix that will fully restore the functionality and open the SharePoint Online files in the same window, as expected.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, July 7, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jun 30 11:18:06 2026 |
|---|
| Description: | Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: Our initial projected timeline for the deployment of our solution to complete was inaccurate and based on the rate of progression. Based on our current projection, which may be subject to change, we now anticipate the deployment will require more time to fully saturate and may be completed by our next communication update. We'll provide an updated timeline as one becomes available.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Estimated time to resolve: Tuesday, June 30, 2026
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Jun 30 07:22:03 2026 |
|---|
| Description: | Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: We're unable to revert the change due to an unexpected problem in the rollback process. However, we've confirmed that a fix has been developed and validated for this issue. We're deploying the fix across all the impacted environments. Deployment is expected to be complete by our next scheduled update. Once deployment is complete, impacted users can refresh the app to receive the latest version that includes the fix.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Estimated time to resolve: Tuesday, June 30, 2026
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Jun 30 02:10:17 2026 |
|---|
| Description: | Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: An additional modification was needed to revert the change and go back to the previous file preview experience. We'll provide further insights on the remediation progress by the next scheduled update time.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jun 29 22:32:30 2026 |
|---|
| Description: | Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: The process to revert the change and go back to the previous file preview experience is taking additional time. Once the process completes, we'll provide an estimated timeline for impact remediation.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Start time: Tuesday, June 23, 2026, at 5:00 PM UTC
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jun 29 20:27:43 2026 |
|---|
| Description: | Title: Users may be unable to view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users may be unable to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
The issue may also impact links to Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDF files.
Current status: We identified a recent change intended to improve the file preview experience for Copilot Chat that is causing errors when opening linked files. We're reverting the change to go back to the previous file preview experience, which we anticipate may remediate the impact by our next scheduled update.
Scope of impact: This issue may potentially impact any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
Root cause: A recent change intended to improve the file preview experience for Copilot Chat is causing errors when attempting to open linked files.
Next update by: Tuesday, June 30, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Jun 29 18:39:14 2026 |
|---|
| Description: | Title: Users can't view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users can't view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
Current status: We've reached out to your organization to confirm the Copilot version number and are reviewing the provided HTTP Archive format (HAR) logs to help us narrow down the source of the impact.
Scope of impact: Your organization is impacted by this event, and any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents is impacted.
Next update by: Tuesday, June 30, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jun 29 17:55:26 2026 |
|---|
| Description: | Title: Users can't view SharePoint Online files that are linked by Microsoft 365 Copilot Chat or Copilot agents
User impact: Users can't view SharePoint Online files that are linked by Copilot Chat or Copilot agents.
More info: When users select the link to a SharePoint Online file that has been provided by Copilot Chat or Copilot agents, they receive an error that says, "We couldn't show the file."
Current status: We're reviewing the screenshots 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 any user attempting to view SharePoint Online files that are linked by Copilot Chat or Copilot agents is impacted.
Next update by: Monday, June 29, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jun 29 17:42:16 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.
|
|---|
|
DZ1410811 - Users couldn't access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 26 09:43:00 2026 |
|---|
| End Time: | Mon Jul 6 09:00:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 7 05:45:29 2026 |
|---|
| Root Cause: | Some version upgrades to builds 101.26042.0009 and 101.26052.0007, as well as certain reinstallation scenarios, resulted in the Microsoft Defender for Endpoint service not remaining configured to start automatically after a system reboot.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 7 05:43:25 2026 |
|---|
| Description: | Title: Users couldn't access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users couldn't access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 was causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we worked to resolve this issue, we recommended that users not upgrade to the latest version and instead wait until the next version was released or the impact was remediated.
For users who had already upgraded, they could either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
For more information on the completed release note details, please see: https://review.learn.microsoft.com/en-us/defender-endpoint/microsoft-defender-endpoint-releases?branch=main&branchFallbackFrom=pr-en-us-8536.
Final status: We've successfully completed deployment of the targeted fix across the affected environment and confirmed that normal service functionality has been restored. We've verified that impact has been fully remediated and affected users can now upgrade to the latest version without encountering the previously reported issue.
Scope of impact: Your organization was affected by this event, and users expecting their endpoint agent to start automatically after rebooting, following an upgrade to builds 101.26042.0009 and 101.26052.0007, were impacted.
Start time: Friday, June 26, 2026, at 1:43 PM UTC
End time: Monday, July 6, 2026, at 1:00 PM UTC
Root cause: Some version upgrades to builds 101.26042.0009 and 101.26052.0007, as well as certain reinstallation scenarios, resulted in the Microsoft Defender for Endpoint service not remaining configured to start automatically after a system reboot.
Next steps:
- We're analyzing our deployment procedures on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 3 05:25:52 2026 |
|---|
| Description: | Title: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 is causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we work to resolve this issue, we recommend users don't upgrade to the latest version and wait until the next version is released or this impact is remediated.
If users have already upgraded, users can either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
Current status: We're progressing with validation of the fix and expect this work to be completed today. The deployment is scheduled to begin on Monday, 6 July 2026, and we'll provide a deployment completion timeline as part our next scheduled update.
Scope of impact: Your organization is affected by this event, and users expecting their endpoint agent to start automatically after rebooting following an upgrade to version builds 101.26042.0009 and 101.26052.0007 are impacted. This section may be updated as our investigation continues.
Root cause: Some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot.
Next update by: Tuesday, July 7, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Jul 2 23:13:56 2026 |
|---|
| Description: | Title: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 is causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we work to resolve this issue, we recommend users don't upgrade to the latest version and wait until the next version is released or this impact is remediated.
If users have already upgraded, users can either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
Current status: Upon further inspection, we’ve determined that the fix deployment hasn’t been initiated as mentioned in our previous status update. The process of preparing our fix for its deployment is in its final stages of validation and we expect that the process should begin by our next scheduled update.
Scope of impact: Your organization is affected by this event, and users expecting their endpoint agent to start automatically after rebooting following an upgrade to version builds 101.26042.0009 and 101.26052.0007 are impacted. This section may be updated as our investigation continues
Root cause: Some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot.
Next update by: Friday, July 3, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Jul 1 23:35:18 2026 |
|---|
| Description: | Title: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 is causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we work to resolve this issue, we recommend users don't upgrade to the latest version and wait until the next version is released or this impact is remediated.
If users have already upgraded, users can either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
Current status: We've started deploying the fix, and we anticipate being able to provide a deployment timeline by our next scheduled update.
Scope of impact: Your organization is affected by this event, and users expecting their endpoint agent to start automatically after rebooting following an upgrade to version builds 101.26042.0009 and 101.26052.0007 are impacted. This section may be updated as our investigation continues
Root cause: Some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot.
Next update by: Friday, July 3, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Jul 1 00:17:37 2026 |
|---|
| Description: | Title: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade
User impact: Users can’t access the Microsoft Defender for Endpoint on Linux service upon rebooting after a version upgrade.
More info: Specifically, rebooting after upgrading to version builds 101.26042.0009 and 101.26052.0007 is causing impact to active protection on devices across supported Linux platforms, leading to the Microsoft Defender for Endpoint on Linux service being disabled.
While we work to resolve this issue, we recommend users don't upgrade to the latest version and wait until the next version is released or this impact is remediated.
If users have already upgraded, users can either downgrade to a previous version or manually start the Defender service (mdatp) to restore protection on affected devices.
Current status: We've received customer reports indicating that Microsoft Defender for Endpoint on Linux service becomes disabled on some users' devices after a version upgrade and is rebooted. We've identified that some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot. We've developed a fix to address the startup configuration issue and re-enable the affected Linux service, and we're preparing to initiate deployment of this fix to the affected organizations.
Scope of impact: Your organization is affected by this event, and users expecting their endpoint agent to start automatically after rebooting following an upgrade to version builds 101.26042.0009 and 101.26052.0007 are impacted. This section may be updated as our investigation continues
Root cause: Some version upgrades to 101.26042.0009 and 101.26052.0007 builds and reinstalling scenarios aren't remaining configured to start automatically after a system reboot.
Next update by: Thursday, July 2, 2026, at 5:00 AM UTC
|
|---|
|
EX1233142 - Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
| Status: | serviceRestored |
|---|
| Start Time: | Sun Dec 7 22:04:00 2025 |
|---|
| End Time: | Thu Jul 2 15:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 6 15:28:45 2026 |
|---|
| Root Cause: | A recent expansion of the feature logic used to book rooms for scheduled meetings contained a code complication which automatically set the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 6 15:28:16 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may have seen after selecting a meeting room when scheduling meetings, it changed from available to unavailable.
More info: While we worked to remediate the impact, admins could circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Final status: We've deployed our fix to address the offending code complication and confirmed that this process has completed. We've validated with a subset of affected users and from our service telemetry that our actions successfully remediated impact.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may have been impacted.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
End time: Thursday, July 2, 2026, at 7:00 PM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contained a code complication which automatically set the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next steps:
- We're analyzing the offending feature logic change to isolate why the potential for impact wasn't caught prior to deployment. This further analysis will help us to understand how we can update our processes moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 2 15:25:52 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we're working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We've confirmed that our fix has reached 50 percent of the affected environment. We're continuing to monitor its progress to ensure the deployment completes successfully, and based on our current estimates, we expect deployment to complete by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Monday, July 6, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Jun 26 15:28:51 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we're working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We’ve confirmed that our fix encountered a deployment blocker that slowed progress. We've addressed the blocker and confirmed that the fix is deploying at a normal rate and has reached 25 percent of the affected environment. We’ll continue monitoring its progress to ensure it completes as expected by our next scheduled update. We’re also reaching out to a subset of affected users to validate the fix ahead of schedule to expedite the deployment process.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, July 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 17 16:20:04 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we're working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We've validated the code solution that includes the required fix and have resumed deployment, which is on schedule for our anticipated completion date of Friday, June 26, 2026. We're reaching out to a subset of affected users to validate the fix ahead of schedule to further streamline the deployment process.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, June 26, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 16:51:18 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: While performing internal testing of our solution to correct the problematic code, we determined a change was needed to ensure the fix fully remediates the impact. We've made this change to the fix and we're progressing with our validations ahead of deployment. We now anticipate our deployment will complete by June 26, 2026, and we'll continue to assess our projected timeline as internal testing continues.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 08, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, June 17, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 28 17:17:08 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're progressing with our internal tests and validations so we can ensure our deployment remediates the impact. Our fix deployment timeline projects that the deployment will have completed by Friday, June 19, 2026, and we're assessing options to expedite its release, which we anticipate we'll have further clarity on by our next scheduled communications update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 08, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, June 10, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 14 21:45:44 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: Our reviews and checks on the stability and reliability of the aforementioned fix are progressing, though taking an extended period of time as we continue our efforts to ensure it fully addresses impact. Additionally, we anticipate that we will be able to provide an estimated remediation timeline by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, May 28, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue May 12 21:01:35 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're conducting additional reviews and checks on the stability and reliability of the fix before resuming its deployment, to ensure it fully addresses impact. We anticipate being able to share a more accurate timeline for remediation by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, May 15, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Apr 30 20:45:52 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're continuing to monitor the incremental progress of the deployment; however, more time is needed before we can provide an accurate timeline for resolution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 0, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, May 13, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Apr 23 19:49:47 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The incremental rollout of the fix is ongoing and we’re continuing to monitor its progress to ensure it completes as expected. We’ll provide an estimation for full impact resolution when one becomes available.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, May 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 15 19:09:50 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The deployment of our fix is progressing, and our review of service health telemetry shows continued signs of improvement. While we continue to monitor the deployment as it propagates throughout the affected service environment, we anticipate that users will experience relief from impact whilst the time we work to ascertain a full remediation timeline.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, April 24, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 1 19:31:53 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The deployment of the fix is ongoing and we're continuing to monitor as it progresses.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, April 16, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Mar 26 21:39:25 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We’re continuing to monitor the deployment of our fix as it progresses and we anticipate it’ll reach completion by mid-April.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, April 2, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Mar 17 22:02:04 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: Based on feedback received regarding this communication, we've edited the More info, Scope of impact, and Root cause sections of this communication to align with our current understanding of the affected scenario. Additionally, we've completed validation of the fix and have begun its deployment. We're monitoring as it progresses and will provide a completion timeline when one becomes available.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, March 27, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Mar 9 21:39:18 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're continuing our efforts to validate the fix in our internal testing environment; however, more time is needed to complete this process and confirm that the fix fully addresses the impact. Once ready, we will begin the full deployment to the remaining affected environment.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, March 18, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Sun Mar 8 21:47:36 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're continuing to deploy the fix in our internal test environment and completing final validations prior to deploying it to the remaining affected environments.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Tuesday, March 10, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Mar 6 19:51:36 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're working to ensure that our fix has mitigated the impact as expected and are running tests to confirm whether any additional changes need to be made.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Monday, March 9, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Mar 2 18:48:30 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We’ve developed a fix that will implement two changes to resolve the underlying issue. First, the fix will prevent the Exchange Online time zone from automatically setting users working hours to Pacific Standard Time. Secondly, the fix will allow users to select meeting rooms outside of their working hours if the room is actually available. We're preparing to deploy the fix and anticipate it will be fully deployed and the impact remediated by our next scheduled update. Additionally, to immediately resolve the issue, users can manually update their time zone and working hours to reflect accurately.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Saturday, March 7, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 15:35:39 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
Current status: We’re continuing to review our options to most efficiently and permanently resolve this issue. We anticipate having a solidified remediation plan and estimate for the delivery of our fix by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact.
Next update by: Tuesday, March 3, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Feb 26 15:43:19 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
Current status: We've determined that a recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact. We decided that instead of adding a new state to the UI, which would include "Outside of working hours," we’re focusing on improving the logic to correctly determine and display what times are considered in working hours, so that rooms appear in the correct state consistently across the interface.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact.
Next update by: Friday, February 27, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Feb 25 14:49:21 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: We're preparing a code change to introduce a new state to the User Interface (UI), "Outside of working hours," alongside additional logic to correct this issue. We're working to determine a timeline for the code change development along with testing and validation as we continue.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, February 26, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Feb 25 05:05:41 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: As part of our ongoing investigation, we’ve identified a configuration‑related service scenario affecting room availability and have shared a temporary workaround in the More Info section to help prevent further impact. We’re continuing to work to identify steps toward a longer-term resolution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 24 22:26:21 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: We've identified an underlying code conflict scenario, which we suspect is contributing to the impact. Due to the complexity of the scenario, we're anticipating it may take some additional time before we can identify a timeline and route to remediation.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Feb 17 22:27:48 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
Current status: As we continue our investigation to isolate the origin of this issue, we’re reaching out to some affected users to validate and confirm whether their time zone settings are configured correctly as a potential solution to this problem. Additionally, regarding room suggestions not reflecting the configured working hours, we suggest that admins adjust the work hours to 24 hours to prevent this issue from occurring as we focus on developing a long-term solution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Feb 17 12:36:18 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: While our review of the HAR network trace logs is ongoing to progress our root cause investigation, we're assessing the efficacy of some potential remediation actions in recovering the scenario.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 18, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Mon Feb 16 01:20:26 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're continuing to analyze the HAR logs and screenshots of the issue to isolate the root cause of the issue.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, February 17, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Feb 16 00:30:38 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're reviewing HTTP Archive format (HAR) logs and screenshots of the issue to help with the investigation and to determine our next troubleshooting steps.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 16, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Mon Feb 16 00:07:28 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1410413 - Users may be unable to generate content through the Microsoft 365 Copilot Create web app
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 25 08:00:00 2026 |
|---|
| End Time: | Mon Jul 6 13:17:03 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jul 6 13:38:08 2026 |
|---|
| Root Cause: | A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data wasn't being received by the web app, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 6 13:38:03 2026 |
|---|
| Description: | Title: Users may be unable to generate content through the Microsoft 365 Copilot Create web app
User impact: Users may have been unable to generate content through the Microsoft 365 Copilot Create web app.
More info: Content such as images, charts and graphs, tables, stories, summaries, and poems didn't generate correctly or at all within the Copilot Create web app (https://m365.cloud.microsoft/create). Users also didn't see new Create experiences or may have seen outdated experiences.
While we focused on remediation, users with access to the Copilot desktop app could use its Create feature to bypass the impact.
Final status: Following our completed deployments in the affected environments, our internal service telemetry has validated that Create data is now being received by the web app and that the impact has been remediated.
Scope of impact: Users who attempted to generate content through the Copilot Create web app may have been affected by this event.
Start time: Thursday, June 25, 2026, at 12:00 PM UTC
End time: Friday, July 3, 2026, at 2:10 AM UTC
Root cause: A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data wasn't being received by the web app, resulting in impact.
Next steps:
- We're further analyzing the offending service change to better understand why it prevented Create data from being received by the web app, so we can improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 2 13:31:10 2026 |
|---|
| Description: | Title: Users may be unable to generate content through the Microsoft 365 Copilot Create web app
User impact: Users may be unable to generate content through the Microsoft 365 Copilot Create web app.
More info: Content such as images, charts and graphs, tables, stories, summaries, and poems may not generate correctly or at all within the Copilot Create web app (https://m365.cloud.microsoft/create). Users also may not see new Create experiences or see outdated experiences.
While we’re focused on remediation, users with access to the Copilot desktop app may use the Create feature there to bypass the impact.
Current status: Our fix deployment has reached the majority of affected environments, and some users may now see relief from impact. We're continuing the rollout across the remaining affected environments while monitoring progress to confirm successful completion and remediation.
Scope of impact: Users attempting to generate content through the Copilot Create web app may be affected by this event.
Start time: Thursday, June 25, 2026, at 12:00 PM UTC
Root cause: A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data isn’t being received by the web app, which is resulting in impact.
Next update by: Monday, July 6, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jul 1 15:32:38 2026 |
|---|
| Description: | Title: Users may be unable to generate content through the Microsoft 365 Copilot Create web app
User impact: Users may be unable to generate content through the Microsoft 365 Copilot Create web app.
More info: Content such as images, charts and graphs, tables, stories, summaries, and poems may not generate correctly or at all within the Copilot Create web app (https://m365.cloud.microsoft/create). Users also may not see new Create experiences or see outdated experiences.
While we’re focused on remediation, users with access to the Copilot desktop app may use the Create feature there to bypass the impact.
Current status: Our fixes to ensure that the web app is receiving the Create Data have begun deployment. We expect it will be completed by the time of our next update, after which we'll use our testing environment to confirm the impact is remediated.
Scope of impact: Users attempting to generate content through the Copilot Create web app may be affected by this event.
Start time: Thursday, June 25, 2026, at 12:00 PM UTC
Root cause: A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data isn’t being received by the web app, which is resulting in impact.
Next update by: Thursday, July 2, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jun 30 15:20:34 2026 |
|---|
| Description: | Title: Users may be unable to generate content through the Microsoft 365 Copilot Create web app
User impact: Users may be unable to generate content through the Copilot Create web app.
More info: Content such as such as images, charts and graphs, tables, stories, summaries, and poems may not generate correctly or at all within the Copilot Create web app (https://m365.cloud.microsoft/create). Users also may not see new Create experiences or see outdated experiences.
While we’re focused on remediation, users with access to the Copilot desktop app may use the Create feature there to bypass the impact.
Current status: We've determined that a recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data isn’t being received by the web app, which is resulting in impact. We're developing two fixes aimed at correcting this issue and expect them to deploy by our next scheduled update. Once deployed, we'll monitor these fixes as they saturate throughout the affected infrastructure to confirm this issue is fully resolved.
Scope of impact: Users attempting to generate content through the Copilot Create web app may be affected by this event. This section may be updated as our investigation progresses.
Start time: Thursday, June 25, 2026, at 12:00 PM UTC
Root cause: A recent change intended to improve the Copilot Create UI and overall performance introduced an issue where Create data isn’t being received by the web app, which is resulting in impact.
Next update by: Wednesday, July 1, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jun 30 14:52:25 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.
|
|---|
|
MO1413447 - Users in Japan may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 2 23:55:00 2026 |
|---|
| End Time: | Fri Jul 3 00:40:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jul 3 01:10:34 2026 |
|---|
| Root Cause: | A transient issue affecting a network component leveraged to facilitate Microsoft 365 service access resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 3 01:10:34 2026 |
|---|
| Description: | Title: Users in Japan may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Japan may have experienced issues accessing Microsoft Teams and Microsoft 365 services.
Final status: We've identified that a transient issue affecting a network component leveraged to facilitate Microsoft 365 service access resulted in impact. Our automated recovery system repaired this problem before we had the opportunity to manually intervene, and we confirmed that service was restored after monitoring the environment.
Scope of impact: Users in Japan attempting to access Microsoft Teams and other Microsoft 365 services may have been impacted.
Start time: Friday, July 3, 2026, at 3:55 AM UTC
End time: Friday, July 3, 2026, at 4:40 AM UTC
Root cause: A transient issue affecting a network component leveraged to facilitate Microsoft 365 service access resulted in impact.
Next steps:
- We're continuing to monitor the involved network component closely to gain further insight into the source of the underlying issue and identify ways we can better prevent similar issues prior to impact.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jul 3 00:45:54 2026 |
|---|
| Description: | Title: Users in Japan may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Japan may have experienced issues accessing Microsoft Teams and Microsoft 365 services.
Current status: We've investigated a problem in which users may have experienced issues accessing Microsoft 365 services including Microsoft Teams and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
CP1409187 - Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 29 15:34:28 2026 |
|---|
| End Time: | Thu Jul 2 23:07:39 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 2 23:08:38 2026 |
|---|
| Root Cause: | A recent deployment contained a code issue that caused a compatibility conflict with the Microsoft 365 Copilot desktop clients and prevented the affected features from populatingas expected during notebook creation.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 2 23:08:35 2026 |
|---|
| Description: | Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not have seen the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Final status: We've confirmed that a recent deployment contained a code issue that caused a compatibility conflict with the Microsoft 365 Copilot desktop clients and prevented the affected features from populating during notebook creation, causing impact. We've deployed a code fix to the offending error, after a period of monitoring the service health telemetry we've confirmed impact has ceased and service is restored.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
End time: Friday, July 3, 2026, at 2:00 AM UTC
Root cause: A recent deployment contained a code issue that caused a compatibility conflict with the Microsoft 365 Copilot desktop clients and prevented the affected features from populatingas expected during notebook creation.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 2 16:36:11 2026 |
|---|
| Description: | Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: We're continuing our efforts to resolve the issue affecting our deployment pipeline so that we can resume deploying the fix to the remaining affected environments.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Monday, July 6, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Jul 1 22:11:44 2026 |
|---|
| Description: | Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: We're continuing our efforts to resolve the issue with our deployment pipeline so that our fix deployment can continue.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Thursday, July 2, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jul 1 15:17:10 2026 |
|---|
| Description: | Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: The deployment has saturated across approximately 95% of the affected service environment, and most users should no longer be experiencing the issue. We've identified an unrelated issue within our deployment pipeline that's preventing the fix from saturating to the remaining affected environment. We're working to resolve this issue and will provide an updated deployment completion timeline once it's available.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Thursday, July 2, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Jun 30 20:52:45 2026 |
|---|
| Description: | Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: The deployment has saturated throughout 95% of the affected service environment and most users should no longer be experiencing the issue. We anticipate that by our next scheduled update, impact will be fully resolved.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Wednesday, July 1, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jun 30 17:15:41 2026 |
|---|
| Description: | Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: Incremental deployment of the code fix in the affected environment is progressing, albeit at a slower rate than initially projected. We're monitoring as the deployment continues and will provide a timeline for completion as one becomes available to us.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Wednesday, July 1, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Jun 29 16:28:58 2026 |
|---|
| Description: | Title: Some users may not see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users may not see the search bar or features when creating Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: We've identified that a recent deployment contains a code issue that's causing a compatibility conflict with the Copilot desktop clients and preventing the search bar or features from populating as expected when creating notebooks. We've developed a code change that we've validated in our internal testing environment, and we're preparing to deploy it to the impacted environment incrementally. We anticipate the deployment will be completed and the issue will be resolved by our next scheduled update.
Scope of impact: Some users that are attempting to use the search bar or use features when creating Microsoft 365 Copilot notebooks on the desktop clients may be impacted. This information may be updated as our investigation continues.
Start time: Friday, June 26, 2026, at 12:00 AM UTC
Root cause: A recent deployment contains a code issue that's causing a compatibility conflict with the Microsoft 365 Copilot desktop clients and preventing the search bar or features when creating notebooks from populating as expected.
Next update by: Tuesday, June 30, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Jun 29 15:49:52 2026 |
|---|
| Description: | Title: Some users can't see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client
User impact: Users can't see the search bar or features when creating Microsoft 365 Copilot notebooks on the desktop client.
More info: Impact is specific to the Mac and Windows desktop clients.
Current status: We're investigating a potential issue with Microsoft Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1412052 - Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 2 02:30:00 2026 |
|---|
| End Time: | Thu Jul 2 16:59:59 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 2 17:14:04 2026 |
|---|
| Root Cause: | A recent service configuration change caused a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 2 17:14:00 2026 |
|---|
| Description: | Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may have received response failures or a degraded experience when using Researcher in Copilot.
Final status: After monitoring the environment, we've confirmed that this issue has been resolved by our actions to optimize traffic distribution and performance parameters on the affected infrastructure.
Scope of impact: Any user who attempted to submit or process Researcher requests in Copilot may have received response failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
End time: Thursday, July 2, 2026, at 3:30 PM UTC
Root cause: A recent service configuration change caused a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which resulted in impact.
Next steps:
- We're continuing our analysis of the impacting configuration change to better identify why it resulted in impact and how we can bolster our check in process in an effort to prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jul 2 15:40:49 2026 |
|---|
| Description: | Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
Current status: Telemetry continues to show improvement and we're monitoring the environment as service recovers.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may receive response failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which is resulting in impact.
Next update by: Friday, July 3, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Jul 2 13:27:24 2026 |
|---|
| Description: | Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
Current status: While our mitigative actions thus far are helping to stabilize the service, they've been unsuccessful in completely remediating impact. We've further reverted the offending configuration change within additional portions of the affected infrastructure while continuing our efforts to scale up traffic resources to fully resolve this issue's impact.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may get response failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which is resulting in impact.
Next update by: Thursday, July 2, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jul 2 11:23:52 2026 |
|---|
| Description: | Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
Current status: We're monitoring service health telemetry after reverting the offending configuration change within the affected infrastructure to validate whether this is remediating impact or if additional actions are required to resolve the problem.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may get response failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds, which is resulting in impact.
Next update by: Thursday, July 2, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Jul 2 09:16:06 2026 |
|---|
| Description: | Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
More info: Impacted users may experience error messages, resulting in failed responses or a degraded experience.
Current status: We've determined that optimizing service traffic distribution is insufficient to stabilize the service. We're reverting the problematic configuration change within portions of the affected infrastructure to mitigate impact while we investigate whether additional actions are required to restore the service.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may experience failures or degraded performance.
Start time: Thursday, July 2, 2026, at 6:30 AM UTC
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds.
Next update by: Thursday, July 2, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Thu Jul 2 07:30:37 2026 |
|---|
| Description: | Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
More info: Impacted users may experience error messages, resulting in failed responses or a degraded experience.
Current status: We've determined that a recent service configuration change is causing reduced performance within infrastructure that supports Researcher in Copilot. We're optimizing traffic distribution and adjusting performance parameters on the affected infrastructure while closely monitoring service telemetry to validate recovery.
Scope of impact: Any user attempting to submit or process Researcher requests in Copilot may experience failures or degraded performance.
Root cause: A recent service configuration change is causing a section of service infrastructure that facilitates Researcher in Copilot to perform below acceptable performance thresholds.
|
|---|
|
| Time: | Thu Jul 2 05:52:51 2026 |
|---|
| Description: | Title: Some users may receive response failures or a degraded experience when using Researcher in Microsoft 365 Copilot
User impact: Users may receive response failures or a degraded experience when using Researcher in Copilot.
More info: Impacted users may experience errors messages, resulting in failed responses or a degraded experience.
Current status: We’re reviewing service telemetry, along with conversation IDs and service logs, to determine the underlying cause of the issue and identify a path to mitigation.
Scope of impact: The issue potentially impacts any user attempting to use the Researcher feature in Copilot.
Next update by: Thursday, July 2, 2026, at 11:30 AM UTC
|
|---|
|
PB1396749 - Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 14 22:25:00 2026 |
|---|
| End Time: | Tue Jun 30 16:17:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 1 23:22:20 2026 |
|---|
| Root Cause: | A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature was adding additional properties into the payload which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 1 23:21:17 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may have been unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Final status: We’ve completed deploying our fix and confirmed with our service telemetry that it’s saturated across the affected environment, remediating the impact.
Scope of impact: Some users who attempted to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may have been impacted.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
End time: Tuesday, June 30, 2026, at 8:17 PM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature was adding additional properties into the payload which resulted in impact.
Next steps:
- We're investigating the impacting version update to better understand what it was intended to do and why impact wasn't detected during the testing and validation stage, so that we can better prevent impact to tileset jobs in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jun 27 01:02:12 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We’ve completed the aforementioned validations to ensure that the fix won’t contain adverse effects, and we’ve begun the initial stages of the deployment. Additionally, we anticipate that the deployment will have saturated throughout the affected environment by our next scheduled update.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Thursday, July 2, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Jun 24 02:19:51 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: During our process of initiating the deployment of the fix, we've identified that additional validation is needed in order to ensure the fix will successfully remediate impact without adversely impacting other aspects of the service. We've since completed the additional validations and are preparing to deploy the change to the impacted environments. We'll aim to provide a resolution timeline once available.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Saturday, June 27, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Jun 19 23:07:11 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We’ve determined that the efficacious solution to resolving the issue is to develop a code change to address the affected infrastructure. We’ve developed this change and validated its efficacy within our internal testing environment, and we’ve subsequently begun the initial deployments throughout the affected environment. We anticipate that a remediation timeline will be provided by our next scheduled communications update.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Wednesday, June 24, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Jun 19 02:01:32 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We’re in the process of the analyzing recent version update as we’ve begun to review options to either develop an expedited code fix to correct the issue or deploy a fix within the most recent standard service update, depending on resolution efficacy.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Saturday, June 20, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Jun 18 23:44:32 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We've been made aware of an issue in which internal users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric. We're identified that a recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact. We're exploring potential solutions to address this issue.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Friday, June 19, 2026, at 6:00 AM UTC
|
|---|
|
MO1411776 - Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 1 16:00:00 2026 |
|---|
| End Time: | Wed Jul 1 22:02:11 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jul 1 22:02:18 2026 |
|---|
| Root Cause: | A third-party regional networking issue was occurring, preventing users from accessing Microsoft 365 services as expected.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 1 21:54:45 2026 |
|---|
| Description: | Title: Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services
User impact: Due to a third-party networking issue, users in Australia may have been unable to access Microsoft 365 services.
Final status: We've confirmed through monitoring of service metrics that impact has been successfully resolved following our rerouting of service traffic.
Scope of impact: Users in Australia may have been unable to access Microsoft 365 services.
Start time: Wednesday, July 1, 2026, at 8:00 PM UTC
End time: Thursday, July 2, 2026, at 2:02 AM UTC
Root cause: A third-party regional networking issue was occurring, preventing users from accessing Microsoft 365 services as expected.
Next steps:
- We're continuing to work directly with the involved third-party network provider and reviewing our internal networking processes to identify areas for improvement, so we can further reinforce our service's overall resiliency and prevent similar impact from occurring in the future.
This is the final update for this event.
|
|---|
|
| Time: | Wed Jul 1 20:33:22 2026 |
|---|
| Description: | Title: Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services
User impact: Due to a third-party networking issue, users in Australia may be unable to access Microsoft 365 services.
Current status: We've identified through internal monitoring that users in Australia may be unable to access Microsoft 365 services. While we reach out directly to the involved third-party provider for further insight, we're working to manually reroute impacted traffic as a potential route to remediation, which we anticipate may take effect by our next scheduled update.
Scope of impact: Users in Australia may be unable to access Microsoft 365 services. This information may be updated as our investigation continues.
Root cause: A third-party regional networking issue is occurring, preventing users from accessing Microsoft 365 services as expected.
Next update by: Thursday, July 2, 2026, at 3:00 AM UTC
|
|---|
|
EX1409958 - Some users may encounter crashes in the classic Outlook desktop app when right clicking in an email message
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 29 19:59:00 2026 |
|---|
| End Time: | Wed Jul 1 16:52:44 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 1 17:18:05 2026 |
|---|
| Root Cause: | A recent update to improve accessibility introduced an impacting code error.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 1 17:17:55 2026 |
|---|
| Description: | Title: Some users may encounter crashes in the classic Outlook desktop app when right clicking in an email message
User impact: Users may have encountered crashes in the classic Outlook desktop app when right clicking in an email message.
More info: This issue affected users on Current Channel or Monthly Enterprise Channel version 2605.
While the team focused on remediation, users with access to the new Outlook desktop app or Outlook on the web could use these apps to bypass the impact. As an alternative option to more quickly self-mitigate and allow use of the classic Outlook app, we recommended that users could update to version 2606, which wasn't affected by this problem.
Final status: Following our completed change reversion, our internal service telemetry validated that the impact has been remediated. Any user that continues to experience crashes in classic Outlook should restart their device so our changes can be applied.
Scope of impact: Some users on the Current Channel or Monthly Enterprise Channel version 2605 that right-clicked email messages in classic Outlook desktop may have been impacted.
Start time: Monday, June 29, 2026, at 11:59 PM UTC
End time: Wednesday, July 1, 2026, at 3:54 PM UTC
Root cause: A recent update to improve accessibility introduced an impacting code error.
Next steps:
-We're further analyzing the offending accessibility change and the code error it introduced so we can improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 30 16:38:06 2026 |
|---|
| Description: | Title: Some users may encounter crashes in the classic Outlook desktop app when right clicking in an email message
User impact: Users may encounter crashes in the classic Outlook desktop app when right clicking in an email message.
More info: This issue affects users on Current Channel or Monthly Enterprise Channel version 2605. While we're focused on remediation, users with access to the new Outlook desktop app or Outlook on the web may use these apps to bypass the impact. As an alternative option to more quickly self-mitigate and allow use of the classic Outlook app, users may update to version 2606, which isn't affected by this problem.
Current status: We've initiated a reversion of the impacting change and are monitoring as it progresses. We expect this to complete by the next scheduled update.
Scope of impact: Some users on Current Channel or Monthly Enterprise Channel version 2605 right clicking in classic Outlook desktop email messages may be impacted.
Start time: Wednesday, June 17, 2026, at 12:00 PM UTC
Root cause: A recent accessibility change contains a code error, resulting in impact.
Next update by: Wednesday, July 1, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Jun 30 16:15:49 2026 |
|---|
| Description: | Title: Some users may encounter crashes in the Outlook desktop app when right clicking in an email message
User impact: Users may encounter crashes in the Outlook desktop app when right clicking in an email message.
Current status: Our investigation has identified a recent accessibility change contains a code error, resulting in impact. We're in the process of determining the best path to remediate impact and will provide a remediation timeline when available.
Scope of impact: Some users right clicking in Outlook desktop email messages may be impacted.
Next update by: Wednesday, July 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Jun 30 08:29:03 2026 |
|---|
| Description: | Title: Some users may encounter crashes in the Outlook desktop app when right clicking in an email message
User impact: Users may encounter crashes in the Outlook desktop app when right clicking in an email message.
Current status: We're reviewing reported impact scenarios and attempting to internally reproduce impact, in order to isolate the root cause and develop a remediation plan.
Scope of impact: Some users right clicking in Outlook desktop email messages are impacted.
Next update by: Tuesday, June 30, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jun 30 07:27:38 2026 |
|---|
| Description: | Title: Some users may encounter crashes in the Outlook desktop app when right clicking in an email message
User impact: Users may encounter crashes in the Outlook desktop app when right clicking in an email message.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users right clicking in Outlook desktop email messages are impacted.
Next update by: Tuesday, June 30, 2026, at 1:30 PM UTC
|
|---|
|
MO1410980 - Users may have been unable to access sign-out button or account details across multiple Microsoft 365 web services
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 30 13:22:00 2026 |
|---|
| End Time: | Wed Jul 1 03:37:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 1 09:40:31 2026 |
|---|
| Root Cause: | A recent service migration between infrastructure environments introduced an issue that resulted in service impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 1 05:06:24 2026 |
|---|
| Description: | Title: Users may have been unable to access sign-out button or account details across multiple Microsoft 365 web services
User impact: Users may have been unable to access sign-out button or account details across multiple Microsoft 365 web services.
More info: Affected Microsoft 365 services on the web included but weren't limited to Outlook on the web, OneDrive web, and SharePoint Online web where users may have been unable to access the account drop-down in the top right of the web client, preventing them from accessing the sign-out button and account details in this location.
Final status: We've determined that a recent service migration between infrastructure environments introduced an issue that resulted in service impact. To restore service, we've reverted the change and rolled the affected service back to the previous infrastructure. Following the rollback and continued monitoring of service telemetry, we've confirmed that service functionality has been fully restored and the issue is no longer occurring.
Scope of impact: Impact was specific to some users attempting to access the sign-out button and account details in multiple Microsoft 365 services on the web.
Start time: Tuesday, June 30, 2026, at 5:22 PM UTC
End time: Wednesday, July 1, 2026, at 7:37 AM UTC
Root cause: A recent service migration between infrastructure environments introduced an issue that resulted in service impact.
Next steps: -We're reviewing our deployment processes to implement corrective measures in order to help prevent similar issues from reoccurring during future infrastructure migrations.
This is the final update for the event.
|
|---|
|
WP1410526 - Users may see intermittent performance and connectivity issues affecting their Windows 365 Cloud PCs
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 8 11:00:00 2026 |
|---|
| End Time: | Tue Jun 30 19:42:13 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 30 19:42:54 2026 |
|---|
| Root Cause: | A recent feature update intended to improve Windows 365 functionality contained changes leading to performance issues.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 30 19:36:30 2026 |
|---|
| Description: | Title: Users may see intermittent performance and connectivity issues affecting their Windows 365 Cloud PCs
User impact: Users may have seen intermittent performance and connectivity issues affecting their Cloud PCs.
Final status: We identified that a recent feature update intended to improve Windows 365 functionality contained changes leading to performance issues affecting Cloud PCs. We reverted the feature and monitored the service to validate that the impact was remediated.
Scope of impact: This issue may have potentially impacted any user utilizing their Cloud PCs.
Start time: Monday, June 8, 2026, at 3:00 PM UTC
End time: Tuesday, June 30, 2026, at 11:42 PM UTC
Root cause: A recent feature update intended to improve Windows 365 functionality contained changes leading to performance issues.
Next steps: We're continuing our analysis of the feature update to better understand what triggered the impact, which will help us avoid issues during similar future feature rollouts.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 30 19:03:54 2026 |
|---|
| Description: | Title: Users may see intermittent performance and connectivity issues with their Windows 365 Cloud PC
User impact: Users may have seen intermittent performance and connectivity issues with their Windows 365 Cloud PC.
Current status: We've investigated a problem in which users may have seen intermittent performance and connectivity issues with their Windows 365 Cloud PC and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
CP1387482 - Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 11 11:28:27 2026 |
|---|
| End Time: | Tue Jun 30 14:10:46 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jun 30 16:18:25 2026 |
|---|
| Root Cause: | A dependency introduced in a recent deployment caused the rewrite feature requests to fail.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 30 14:33:26 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may have been unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may have encountered the following error message, "Sorry, something went wrong. Copilot is working on it."
Final status: We've confirmed that the fix has completed deployment and validated this issue has been remediated with affected users.
Scope of impact: Impact was specific to some users of the Copilot rewrite feature in classic Outlook.
Start time: Monday, May 25, 2026, at 3:56 PM UTC
End time: Monday, June 29, 2026, at 11:17 PM UTC
Root cause: A dependency introduced in a recent deployment caused the rewrite feature requests to fail.
Next steps:
- We're continuing our analysis of provided client captures and of the recent deployment to better understand the underlying cause of impact and prevent similar impact in the future.
This is the final update for this event.
|
|---|
|
| Time: | Fri Jun 26 13:51:53 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We've validated and applied a code change to stop new internal request failures for this scenario. We're continuing our investigation to isolate an appropriate long-term solution to fully resolve the underlying issue, and we'll provide a remediation timeline once one is available.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Start time: Monday, May 25, 2026, at 3:56 PM UTC
Root cause: A dependency introduced in a recent deployment is causing the rewrite feature requests to fail.
Next update by: Tuesday, June 30, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jun 25 13:55:56 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our analysis into the provided Outlook client captures has helped us isolate a dependency introduced in a recent deployment that we believe is causing the rewrite features requests to fail. As we progress our root cause analysis and confirm our findings, we're validating a solution to address the internal request failures and remediate the impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Root cause: A dependency introduced in a recent deployment is causing the rewrite feature requests to fail.
Next update by: Friday, June 26, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 14:54:23 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're continuing our analysis of the provided Outlook client captures to further our understanding of the issue and determine our next steps.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 25, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 08:04:43 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We've gathered the client data, including Autodiscover details and client boot logs (with endpoints) required to identify the root cause of impact, and to confirm our next troubleshooting steps.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 24, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 05:07:36 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We’re continuing to gather client data, including Autodiscover details and client boot logs (with endpoints), to help determine the next steps to remediate impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 24, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Jun 23 14:13:53 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're reviewing updated Copilot telemetry as we progress with our analysis into why the Outlook classic client isn't able to reach certain Copilot endpoints. In parallel, we're continuing our efforts to collect client data, including Autodiscover and client boot logging (with endpoints), to help us determine our next steps for remediating the impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 24, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Jun 22 15:00:20 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our investigation indicates that the Outlook classic client isn't able to reach certain Copilot endpoints causing requests to fail. We're working with affected users to gather additional client logs to progress the investigation and determine our next steps.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Tuesday, June 23, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jun 18 13:59:39 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our investigation into the URL provisioning issue identified that incorrect value is being returned from the service helps facilitate the rewrite feature process. We're investigating why the incorrect value is being returned to further root cause the issue and formulate mitigating options.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Monday, June 22, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 14:14:25 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our initial analysis into reproductions of the impact and associated affected user logging has isolated a URL provisioning issue that’s potentially producing these errors. We're further analyzing the specific URLs to confirm our findings, so we can determine the next troubleshooting steps for remediating the impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 18, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jun 16 13:12:26 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We've received the requested reproductions of impact and associated logging from a subset of affected users which we're analyzing for more insight into how impact manifests to assist our root cause and mitigation efforts.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 17, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jun 12 17:15:06 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We’re continuing to work with affected users to collect the additional logging and reproductions of the issue to further our understanding of the impacting scenario and formulate remediation plan.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Tuesday, June 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jun 11 18:16:23 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're working with a subset of affected users to collect additional logging and reproductions of impact to assist with debugging the issues and isolating potential regressions in affected Outlook client versions.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Friday, June 12, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jun 11 13:31:38 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're continuing our analysis of the client telemetry data while comparing service behaviors across client versions to determine if a potential regression in the Outlook client is contributing to the reported impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 11, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Jun 11 11:41:47 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message "Sorry, something went wrong. Copilot is working on it."
Current status: We suspect a potential regression in the Outlook client is contributing to the issue. We're analyzing client telemetry data and comparing service behaviors across client versions to determine if a potential regression in the Outlook client is contributing to the reported impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 11, 2026, at 5: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: | Tue Jun 30 12:41:45 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: | 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 first update will be provided by Friday, July 31.
|
|---|
|
| 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.
|
|---|
|
CW1409007 - Users had access to scheduled prompts in Microsoft 365 Copilot Chat when they shouldn't have
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 29 11:40:37 2026 |
|---|
| End Time: | Mon Jun 29 12:14:29 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 29 12:14:29 2026 |
|---|
| Root Cause: | A related service update incorrectly allowed access to the paid service of scheduled prompts in Copilot Chat causing this event.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 29 12:14:29 2026 |
|---|
| Description: | Title: Users had access to scheduled prompts in Microsoft 365 Copilot Chat when they shouldn't have
User impact: Users had access to scheduled prompts in Copilot Chat when they shouldn't have.
Current status: We identified that an update to a related service incorrectly allowed access to the paid service feature of scheduled prompts for users without an add-on Copilot license in Copilot Chat. A fix was applied to the service to correct this by changing the scope of users allowed to see the feature. This change removed the scheduled prompts feature from Microsoft 365 Copilot chat users.
Scope of impact: Users without an add-on Copilot license had access to scheduled prompts in Copilot Chat when they shouldn't have.
Start time: Tuesday, April 21, 2026, at 12:00 AM UTC
End time: Wednesday, June 10, 2026, at 2:06 PM UTC
Root cause: A related service update incorrectly allowed access to the paid service of scheduled prompts in Copilot Chat causing this event.
Next steps: - We'll continue to review our update process to improve our pre-deployment testing and validation phases with the goal of preventing future reoccurrences.
This is the final update for the event.
|
|---|
|
MO1331639 - Issue with webhook-based task notifications in Microsoft To Do
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 2 09:55:00 2026 |
|---|
| End Time: | Fri Jun 26 05:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 29 07:28:13 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 29 07:26:50 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users may have been unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may have affected any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivered to your organization's registered notificationUrl endpoints that was setup using Microsoft Graph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depended on receiving real-time task change callbacks
If your organization relied on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Final status: We've completed the deployment of the long-term fix to the affected infrastructure, and after a period of monitoring, we've confirmed the functionality of webhook-based task notifications in Microsoft To Do is fully restored.
Scope of impact: Your organization was impacted by this event, and this issue may have affected any user within your organization.
Impact start time: Saturday, May 30, 2026 at 9:00 AM UTC
Impact end time: Friday, June 26, 2026 at 9:00 AM UTC
Next steps:
- We're reviewing how we conduct configuration changes to prevent similar events from occurring in future.
This is the final update for this incident.
|
|---|
|
| Time: | Tue Jun 23 03:23:11 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using Microsoft Graph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've validated the fix produces the desired resolution. We've now begun deploying the fix to the affected infrastructure and we're monitoring this process closely to ensure it progresses as expected.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Monday, June 29, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Jun 18 15:15:14 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using Microsoft Graph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We're continuing to internally validate the fix and we'll aim to provide an estimated deployment timeline as soon as it's available.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Monday, June 22, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 06:08:39 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using MSGraph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've completed the development of the long-term fix to restore webhook-based task notifications in Microsoft To Do, and we're now conducting a period of internal testing to ensure the fix produces the expected resolution. Once complete, we'll begin deploying the fix to the affected infrastructure.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 09:55:50 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using MSGraph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've identified a configuration issue affecting webhook-based task notifications in Microsoft To Do. We're developing a long-term fix to restore functionality, and we'll provide additional updates as this progresses.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Wednesday, June 10, 2026, at 12:00 PM UTC
|
|---|
|
PP1407860 - powerappsforadmins connector flows and apps failing
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 28 09:55:33 2026 |
|---|
| End Time: | Sun Jun 28 15:51:15 2026 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sun Jun 28 15:51:16 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 28 15:51:16 2026 |
|---|
| Description: | Title: powerappsforadmins connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the powerappsforadmins connector.
Final status: After monitoring connector telemetry, it has been observed that functionality to flows and apps using powerappsforadmins connectors has recovered.
Preliminary Root Cause: The external service used by the powerappsforadmins connector was unable to handle requests from Microsoft’s connector services.
Next Steps: We continually review our monitoring to reduce detection time and notify customers of issues with external services.
|
|---|
|
| Time: | Sun Jun 28 14:29:06 2026 |
|---|
| Description: | Title: powerappsforadmins connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the powerappsforadmins connector.
Current Status: We are monitoring an external issue in which some users are receiving errors when using flows and apps with the powerappsforadmins connector.
Users may have received HTTP 5xx errors. Users may have received an email notice that their flows failed. Users may have found that their apps were unresponsive.
|
|---|
|
TM1406826 - Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 26 14:42:00 2026 |
|---|
| End Time: | Sun Jun 28 00:02:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jun 28 00:19:14 2026 |
|---|
| Root Cause: | A recent service side change related to Microsoft Teams Rooms devices caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 28 00:17:52 2026 |
|---|
| Description: | Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
User impact: Users may have been unable to sign into MTR on Windows devices.
Final status: After we reverted the impacting change and monitored the affected infrastructure, we validated with a subset of affected users and service side telemetry that impact was resolved by our actions.
Scope of impact: Users who attempted to sign into MTR on Windows devices may have been impacted by this issue.
Start time: Friday, June 26, 2026, at 6:42 PM UTC
End time: Sunday, June 28, 2026, at 4:02 AM UTC
Root cause: A recent service side change related to Microsoft Teams Rooms devices caused impact.
Next steps:
- We’re continuing to analyze how the recent service change was applied to understand why the potential for impact wasn't caught during the update testing and validation phase. These actions will help us to clarify what actions we can take to ensure similar impact doesn't occur in future and to continue our ongoing mission to improve the resilience of our service for all Microsoft Teams users.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jun 27 22:12:47 2026 |
|---|
| Description: | Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
User impact: Users may be unable to sign into MTR on Windows devices.
Current status: We've completed our investigation into the Microsoft Teams Rooms device client logs along with our service metrics and identified a recent service side change related to Microsoft Teams Rooms devices is causing impact. We've reverted the impacting change and are monitoring our telemetry to confirm that this issue is resolved.
Scope of impact: Users attempting to sign into MTR on Windows devices may be impacted by this issue. This section may be updated as our investigation continues.
Root cause: A recent service side change related to Microsoft Teams Rooms devices is causing impact.
Next update by: Sunday, June 28, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Sat Jun 27 20:52:47 2026 |
|---|
| Description: | Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
User impact: Users may be unable to sign into MTR on Windows devices.
Current status: We've determined that impact is limited to only Microsoft Teams Rooms on Windows devices. We've adjusted our title, user impact, and scope of impact to align with our recent findings. Additionally, we're continuing to investigate the aforementioned client logs and our service metrics to pinpoint the root cause and a remediation plan.
Scope of impact: Users attempting to sign into MTR on Windows devices may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Sunday, June 28, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Sat Jun 27 18:54:52 2026 |
|---|
| Description: | Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) devices
User impact: Users may be unable to sign into MTR devices.
Current status: We've received support cases indicating that users may be unable to sign into multiple Microsoft Teams Rooms devices. We're investigating Microsoft Teams Rooms client logs and our service metrics to gain an understanding of why impact may be occurring.
Scope of impact: Users attempting to sign into MTR devices may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Sunday, June 28, 2026, at 1:00 AM UTC
|
|---|
|
WP1405637 - Users are intermittently disconnected from Windows 365
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 17 03:00:00 2026 |
|---|
| End Time: | Fri Jun 26 22:17:00 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 22:20:28 2026 |
|---|
| Root Cause: | Traffic flow issues placed strain on service infrastructure performance that subsequently impacted gateway access for users, which resulted in connection failures and this impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 22:20:28 2026 |
|---|
| Description: | Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Final status: We confirmed through our period of monitoring that our efforts to rebalance the traffic flow in the impacted infrastructure was successful and that our actions resolved this issue.
Scope of impact: Your organization was affected by this event, and users who attempted to connect to Windows 365 were intermittently disconnected.
Start time: Wednesday, June 17, 2026, at 7:00 AM UTC
End time: Saturday, June 27, 2026, at 2:17 AM UTC
Root cause: Traffic flow issues placed strain on service infrastructure performance that subsequently impacted gateway access for users, which resulted in connection failures and this impact.
Next steps:
- We're analyzing the traffic flow issues to determine how best to bolster the service in an effort to avoid impact such as this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 26 22:00:43 2026 |
|---|
| Description: | Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Current status: We've rebalanced traffic on service infrastructure in an effort to alleviate the flow imbalance and are monitoring service health telemetry to validate if our actions resolve the issue.
Scope of impact: Your organization is affected by this event, and users attempting to connect to Windows 365 are intermittently disconnected.
Start time: Wednesday, June 17, 2026, at 7:00 AM UTC
Root cause: Traffic flow issues placed strain on service infrastructure performance that subsequently impacted gateway access for users, which is resulting in connection failures and this impact.
Next update by: Saturday, June 27, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Fri Jun 26 20:24:14 2026 |
|---|
| Description: | Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Current status: We've determined that the traffic flow issues on service infrastructure are resulting from an ongoing upgrade. We're reviewing service health history to pinpoint the most effective infrastructure to continue the upgrade process in an effort to alleviate the impact for affected users.
Scope of impact: Your organization is affected by this event, and users attempting to connect to Windows 365 are intermittently disconnected.
Root cause: Increased traffic flow is interrupting the processing infrastructure due to an ongoing upgrade to gateway connection processes and is resulting in impact.
Next update by: Saturday, June 27, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Jun 26 19:39:00 2026 |
|---|
| Description: | Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Current status: We've identified that traffic flow discrepancies are impacting users' connections to Windows 365, and are investigating multiple avenues to fully understand the source of this behavior.
Scope of impact: Your organization is affected by this event, and users attempting to connect to Windows 365 are intermittently disconnected.
Next update by: Saturday, June 27, 2026, at 12:30 AM UTC
|
|---|
|
TM1403917 - Some users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 25 09:02:35 2026 |
|---|
| End Time: | Fri Jun 26 12:51:20 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 13:03:56 2026 |
|---|
| Root Cause: | Some missing local settings in the Microsoft Teams desktop client and a feature that allowed users to move chats to a new section was relying on these missing settings caused impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 13:03:51 2026 |
|---|
| Description: | Title: Some users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs
User impact: Users may not have seen chat messages from new contacts in the Microsoft Teams desktop client until a restart occured.
More info: Feedback from affected users and internal testing indicated the impact may have been specific to the combined chat and channel view in the Microsoft Teams desktop client. Impacted users may have been able to avoid impact by utilizing the desktop client's separated chat and channel view experience.
Final status: We've identified some missing local settings in the Microsoft Teams desktop client and a feature that allows users to move chats to a new section was relying on these missing settings, causing impact. While we continue to investigate the reason the local settings were going missing so we can develop a long-term code fix, we disabled the offending feature and confirmed that impact is remediated.
Scope of impact: Some users that were recipients of messages from new contacts in the Microsoft Teams desktop client may have been impacted.
Start time: Friday, May 22, 2026, at 3:28 AM UTC
End time: Friday, June 26, 2026, at 1:25 AM UTC
Root cause: Some missing local settings in the Microsoft Teams desktop client and a feature that allowed users to move chats to a new section was relying on these missing settings caused impact.
Next steps:
- We're continuing to investigate the reason the local settings are going missing, so we can develop a long-term code fix.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 25 19:42:53 2026 |
|---|
| Description: | Title: Some users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs
User impact: Users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs.
More info: Feedback from affected users and internal testing indicates the impact may be specific to the combined chat and channel view in the Microsoft Teams desktop client. While we're focused on remediation, impacted users may be able to avoid impact by utilizing the desktop client's separated chat and channel view experience.
Current status: We've identified that further assessment is needed to verify our understanding of the underlying root cause and confirm the full scope of the impacted scenario. In parallel with our continued investigation, we're finalizing the deployment of the previously mentioned fix to our internal testing environment to determine its effectiveness in remediating impact.
Scope of impact: Some users may not be receiving messages from new contacts in the Microsoft Teams desktop client. This information may be updated as our investigation continues.
Next update by: Saturday, June 27, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Jun 25 09:43:10 2026 |
|---|
| Description: | Title: Some users may not see messages from new contacts in Microsoft Teams chat list unless the client is restarted
User impact: Users may not see messages from new contacts in Microsoft Teams chat list unless the client is restarted.
More info: As a workaround, users may be able to switch to a separate chat and channel view.
Current status: We've identified that users receiving new messages from contacts they haven’t previously interacted with, don’t see those messages in the Teams desktop client. Existing chat threads aren’t impacted, and the issue doesn’t occur on the web client. We've developed a fix which is being planned for release, and is expected to reach the impacted infrastructure mid-July.
Scope of impact: Some users receiving Microsoft Teams messages from contacts they haven't previously interacted with may be impacted.
Next update by: Thursday, July 16, 2026, at 6:00 PM UTC
|
|---|
|
OD1405074 - Some users may be unable to access or experienced degraded performance when using Microsoft OneDrive
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 26 10:05:30 2026 |
|---|
| End Time: | Fri Jun 26 10:58:15 2026 |
|---|
| Service: | Microsoft OneDrive |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 11:03:16 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 11:03:13 2026 |
|---|
| Description: | Title: Some users may be unable to access or experienced degraded performance when using Microsoft OneDrive
User impact: Users may have been unable to access or experienced degraded performance when using OneDrive.
Final status: While we were in the process of analyzing the portion of networking infrastructure responsible for facilitating OneDrive access, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users located in North America, South America, India and UAE that attempted to access or use OneDrive may have been impacted.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
End time: Friday, June 26, 2026, at 1:06 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 26 10:07:20 2026 |
|---|
| Description: | Title: Some users may be unable to access or experience degraded performance when using Microsoft OneDrive
User impact: Users may be unable to access or experience degraded performance when using OneDrive.
Current status: We've received monitoring alerts showing a significant drop in requests to the OneDrive service, which correlated with user reports of impact. Telemetry shows that the volume of requests dropped at 12:53 PM UTC and has returned to normal levels at 1:06 PM. Users are now reporting that impact has recovered. We suspect a potential issue within the networking layer, and we're investigating to isolate the source of the issue.
Scope of impact: This could have impacted any user, however, it appears that users in North America, South America, India and UAE experienced the highest levels of impact.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
Next update by: Friday, June 26, 2026, at 3:30 PM UTC
|
|---|
|
SP1405058 - Users may be unable to access or experience degraded performance when using SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 26 09:30:15 2026 |
|---|
| End Time: | Fri Jun 26 11:00:52 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 11:03:13 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 11:03:10 2026 |
|---|
| Description: | Title: Users may be unable to access or experience degraded performance when using SharePoint Online
User impact: Users may have been unable to access or experience degraded performance when using SharePoint Online.
Final status: While we were in the process of analyzing the portion of networking infrastructure responsible for facilitating SharePoint Online access, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users located in North America, South America, India and UAE that attempted to access or use SharePoint Online may have been impacted.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
End time: Friday, June 26, 2026, at 1:06 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 26 09:58:36 2026 |
|---|
| Description: | Title: Some users may be unable to access or experience degraded performance when using SharePoint Online
User impact: Users may be unable to access or experience degraded performance when using SharePoint Online.
Current status: We've received monitoring alerts showing a significant drop in requests to the SharePoint Online service, which correlated with user reports of impact. Telemetry shows that the volume of requests dropped at 12:53 PM UTC and has returned to normal levels at 1:06 PM. Users are now reporting that impact has recovered. We suspect a potential issue within the networking layer, and we're investigating to isolate the source of the issue.
Scope of impact: This could have impacted any user, however, it appears that users in North America, South America, India and UAE experienced the highest levels of impact.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
Next update by: Friday, June 26, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Jun 26 09:32:03 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting SharePoint Online
User impact: We're checking for potential impact to your users.
Current status: We're received reports indicating an issue with SharePoint Online. We're investigating the issue further, and we'll provide an update within 30 minutes.
|
|---|
|
EX1404918 - Users may have experienced errors or failures when accessing their mailbox via Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 26 04:30:00 2026 |
|---|
| End Time: | Fri Jun 26 05:30:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 06:47:42 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 06:46:41 2026 |
|---|
| Description: | Title: Users may have experienced errors or failures when accessing their mailbox via Exchange Online
User impact: Users may have experienced errors or failures when accessing their mailbox via Exchange Online.
Final status: While we were in the process of analyzing system logs to formulate a remediation plan, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Some users located in North America attempting to access their Exchange Online mailbox may have been impacted.
Start time: Friday, June 26, 2026, at 8:30 AM UTC
End time: Friday, June 26, 2026, at 9:30 AM UTC
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 26 05:08:20 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox via Exchange Online
User impact: Users may experience errors or failures when accessing their mailbox via Exchange Online.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users located in North America attempting to access their Exchange Online mailbox may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, June 26, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Fri Jun 26 04:39:13 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.
|
|---|
|
MV1403883 - Some users may experience read and write operation failures in Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 25 06:55:00 2026 |
|---|
| End Time: | Thu Jun 25 11:55:44 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 25 12:20:50 2026 |
|---|
| Root Cause: | A recent service deployment produced an infrastructure restart that caused a subset of service infrastructure to fall below our manageable service performance thresholds, producing read and write failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 25 12:20:46 2026 |
|---|
| Description: | Title: Some users may experience read and write operation failures in Microsoft Viva Engage
User impact: Users may have experienced read and write operation failures in Microsoft Viva Engage.
More info: Users experienced failures with specific read and write operations such as posting messages or loading Engage feeds.
Final status: Our service monitoring has confirmed that our optimizations on the cache population and redistributed service load has remediated the impact.
Scope of impact: The impact was specific to some users in the United States who attempted to use Microsoft Viva Engage.
Start time: Thursday, June 25, 2026, at 10:55 AM UTC
End time: Thursday, June 25, 2026, at 3:25 PM UTC
Root cause: A recent service deployment produced an infrastructure restart that caused a subset of service infrastructure to fall below our manageable service performance thresholds, producing read and write failures.
Next steps:
- We're further analyzing the subset of affected Viva Engage service infrastructure and the deployment that produced infrastructure restarts to help us prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 25 10:57:01 2026 |
|---|
| Description: | Title: Some users may experience read and write operation failures in Microsoft Viva Engage
User impact: Users may experience read and write operation failures in Microsoft Viva Engage.
More info: Users experience failures with specific read and write operations such as posting messages or loading Engage feeds.
Current status: Our automated recovery mechanisms are actively mitigating impact by optimizing cache population and distributing service load more effectively throughout the infrastructure. We're monitoring service telemetry to verify its success in mitigating impact.
Scope of impact: Impact is specific to some users in the United States who are attempting to use Microsoft Viva Engage.
Start time: Thursday, June 25, 2026, at 10:55 AM UTC
Next update by: Thursday, June 25, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jun 25 08:51:45 2026 |
|---|
| Description: | Title: Some users may experience failures in Microsoft Viva Engage
User impact: Users may experience failures in Microsoft Viva Engage.
More info: Users experience failures with specific read and write operations such as posting messages or loading Engage feeds.
Current status: We're reviewing service telemetry to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact is specific to some users in the United States who are attempting to use Microsoft Viva Engage.
Start time: Thursday, June 25, 2026, at 10:55 AM UTC
Next update by: Thursday, June 25, 2026, at 3:00 PM UTC
|
|---|
|
EX1402802 - Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 24 03:55:00 2026 |
|---|
| End Time: | Wed Jun 24 16:01:46 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 24 16:27:08 2026 |
|---|
| Root Cause: | A recent change intended to optimize the service created unexpected latency, which resulted in this impact
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 24 16:03:34 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method
User impact: Users may have experienced errors or failures when accessing their mailbox using any Exchange Online connection method.
Final status: We confirmed that removing a subset of machines from active service infrastructure didn’t mitigate the issue, and we discovered that a recent change intended to optimize the service had created unexpected latency, which resulted in this impact. We've updated the Root cause and Start time sections of our communications to reflect these final investigation details. After reverting the responsible change, we were able to confirm that this successfully remediated the event by monitoring service health telemetry.
Scope of impact: Users in North America who were attempting to access their mailbox using any Exchange Online connection method may have been impacted by this event.
Start time: Wednesday, June 17, 2026, at 3:37 AM UTC
End time: Wednesday, June 24, 2026, at 7:13 PM UTC
Root cause: A recent change intended to optimize the service created unexpected latency, which resulted in this impact
Next steps: - We're reviewing the responsible change to better understand what led to the resulting latency and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 24 11:55:32 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method
User impact: Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method.
Current status: We've placed the affected subset of infrastructure responsible for hosting mailbox databases into maintenance mode to remediate impact and are monitoring this process in order to validate this issue is fully resolved.
Scope of impact: Users in North America who are attempting to access their mailbox using any Exchange Online connection method may be impacted by this event.
Start time: Wednesday, June 24, 2026, at 7:55 AM UTC
Root cause: A subset of infrastructure responsible for hosting Exchange Online mailbox databases hasn't been placed into maintenance mode for an extended period, which is resulting in impact.
Next update by: Wednesday, June 24, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 24 08:00: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.
Current status: We've determined that a subset of infrastructure responsible for hosting mailbox databases had not been placed into maintenance mode for an extended period, which is resulting in impact. We're working to ensure that the mailbox is restored, as well as putting this subset of infrastructure into maintenance mode to mitigate impact.
Scope of impact: Impact is specific to some users in North America who are attempting to access their mailbox via one or more Exchange Online connection methods.
Start time: Wednesday, June 24, 2026, at 7:55 AM UTC
Root cause: A subset of infrastructure responsible for hosting mailbox databases had not been placed into maintenance mode for an extended period, which is resulting in impact.
Next update by: Wednesday, June 24, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 05:43:52 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.
Current status: We're reviewing service telemetry to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact is specific to some users in North America who are attempting to access their mailbox via one or more Exchange Online connection methods.
Next update by: Wednesday, June 24, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 05:07:39 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.
|
|---|
|
TM1315837 - Some users may see repeated location prompts in Microsoft Teams for Mac
| Status: | serviceRestored |
|---|
| Start Time: | Sun May 10 20:00:00 2026 |
|---|
| End Time: | Wed Jun 24 14:51:30 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 24 15:05:49 2026 |
|---|
| Root Cause: | A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 24 15:05:46 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may have seen repeated location prompts in Microsoft Teams for Mac.
More info: This issue affected macOS versions 14, 15, and 26. Impacted users were unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost wanted to use your current location."
Final status: After the deployment of our solution, our internal service telemetry has validated that the offending regression has been addressed and that the impact has been remediated.
Scope of impact: This issue impacted some Microsoft Teams for Mac users who had location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
End time: Wednesday, June 24, 2026, at 4:20 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next steps:
- We're further analyzing the offending security update to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 23 14:50:01 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to monitor the deployment of our fix as it saturates the affected environment and still estimate that impact will be remediated by Wednesday, June 24, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: We estimate the deployment will complete, remediating impact by Wednesday, June 24, 2026.
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, June 24, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jun 22 14:20:46 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: The deployment of our fix has saturated approximately 80 percent of the affected environment. We estimate the deployment will complete, remediating impact by Wednesday, June 24, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: We estimate the deployment will complete, remediating impact by Wednesday, June 24, 2026.
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, June 23, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jun 17 14:12:42 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: Our fix deployment is ongoing, as more time is needed for it to complete. We've confirmed the fix has reached approximately 50 percent of the impacted environment, and some users may begin to see relief. We're continuing to monitor progress as it continues to provide an updated timeline for completion and impact remediation.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 22, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jun 11 14:59:20 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've resolved the issues in our deployment pipeline and have started to deploy our fix. We anticipate that this fix will completely saturate all affected environments by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, June 17, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 12:01:01 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've completed validation of our solution; however, issues in our deployment pipeline are preventing the initiation of our fix deployment. We're working to address these issues and establish a timeline for the eventual fix deployment.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Thursday, June 11, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jun 9 15:42:10 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: It's taking longer then anticipated to validate a solution that will address the isolated compatibility issue preventing our mitigation deployment from completing. We'll provide a timeline for this additional mitigation step and our resumed deployment if one become available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, June 10, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Jun 9 13:24:17 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to validate a solution that will address the isolated compatibility issue that’s preventing our mitigation deployment from completing. We'll provide a timeline for this additional mitigation step and our resumed deployment if one become available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, June 09, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jun 8 12:09:50 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're internally validating a solution that will address the isolated compatibility issue that’s preventing our mitigation deployment from completing. We're expecting an updated timeline for this additional mitigation step and for our resumed deployment will be available by our next scheduled communication update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, June 09, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Jun 8 10:07:35 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We’ve identified a compatibility issue with the fix and are actively working to resolve it so deployment can resume. We’ll provide an updated timeline once it’s available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Monday, June 8, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 08, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Jun 5 10:36:48 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: Our fix is continuing to deploy across the affected environments. This is taking a little longer to propagate than we anticipated, and we now expect this to be complete by Monday, June 8, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Monday, June 8, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 08, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 10:28:32 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've integrated the fix into the Teams client and initiated deployment, which is actively progressing across the affected environments. We expect deployment to complete by Thursday, June 4, 2026, at which point the issue should be fully resolved.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Thursday, June 4, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Friday, June 05, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed May 27 10:37:51 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're progressing with the validation of our fix and estimate that this should complete by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 01, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 26 12:31:29 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: The validation of our fix is taking longer than initially anticipated. We'll provide a timeline for the completion of our validations and for the deployment as one becomes available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, May 27, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 26 10:49:41 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to validate the fix to repair the regression and remediate impact. We expect to provide an estimated completion timeline by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, May 26, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu May 21 09:55:08 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're validating a fix to repair the regression and remediate impact. We anticipate to provide an estimated completion timeline by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, May 26, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed May 20 10:03:56 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":
"Microsoft Teams Modulehost would like to use your current location"
Current status: We’ve further determined that a recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts. We're reviewing available mitigation options and anticipate to provide a strategy by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Thursday, May 21, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 19 10:28:43 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":
"Microsoft Teams Modulehost would like to use your current location"
Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Microsoft Teams" and "Microsoft Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting.
Current status: We’ve identified that a recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. We’re working with Apple to better understand the change and identify a resolution. In parallel, we’re investigating a potential fix within Teams to mitigate the repeated prompts. Additionally, we've provided a workaround for this issue in the "More info" section of this communication.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, May 20, 2026, at 3:00 PM UTC
|
|---|
|
PB1402061 - Users may be intermittently unable to export reports with sensitivity labels in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 23 09:50:00 2026 |
|---|
| End Time: | Tue Jun 23 13:07:42 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 23 13:07:51 2026 |
|---|
| Root Cause: | Service infrastructure which Power BI relies on for processing export requests experienced an issue resulting in suboptimal performance and impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 23 13:07:47 2026 |
|---|
| Description: | Title: Users may be intermittently unable to export reports with sensitivity labels in Power BI
User impact: Users may have been intermittently unable to export reports with sensitivity labels in Power BI.
More info: As a result of impact, users’ exports may have failed or had incomplete export operations. Export operations may have succeeded on retry.
Final status: After reviewing service health telemetry, we confirmed that service infrastructure which Power BI relies on for processing export requests experienced an issue resulting in suboptimal performance and impact. To remediate impact, we've routed export request traffic to alternate infrastructure while applying optimizations to the impacted infrastructure so requests could process properly. We've rerouted traffic back to the original infrastructure at this time and confirmed impact was successfully remediated.
Scope of impact: This issue may have affected any user attempting to export reports with sensitivity labels in Power BI.
Start time: Tuesday, June 23, 2026, at 1:50 PM UTC
End time: Tuesday, June 23, 2026, at 5:07 PM UTC
Root cause: Service infrastructure which Power BI relies on for processing export requests experienced an issue resulting in suboptimal performance and impact.
Next steps:
- We're investigating why the affected infrastructure was performing at suboptimal thresolds to better understand and prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 23 11:58:12 2026 |
|---|
| Description: | Title: Users may be intermittently unable to export reports with sensitivity labels in Power BI
User impact: Users may be intermittently unable to export reports with sensitivity labels in Power BI.
More info: As a result of impact, users’ exports may fail or have incomplete export operations. Export operations may succeed on retry.
Current status: We're reviewing service health telemetry information to identify and isolate potential sources of impact for further investigation.
Scope of impact: This issue may affect any user attempting to export reports with sensitivity labels in Power BI.
Next update by: Tuesday, June 23, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Jun 23 11:37:51 2026 |
|---|
| Description: | Title: Users may be intermittently unable to export reports with sensitivity labels in Power BI
User impact: Users may be intermittently unable to export reports with sensitivity labels in Power BI.
More info: As a result of impact, users’ exports may fail or have incomplete export operations. Export operations may succeed on retry.
Current status: We're investigating a potential issue with Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1400645 - Some users may have delays or failures in multiple Microsoft Teams features
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 22 10:20:37 2026 |
|---|
| End Time: | Mon Jun 22 14:52:23 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jun 22 15:12:04 2026 |
|---|
| Root Cause: | A third-party service network infrastructure interruption resulted in this event.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 22 15:11:28 2026 |
|---|
| Description: | Title: Some users may have delays or failures in multiple Microsoft Teams features
User impact: Users may have had delays or failures in multiple Microsoft Teams features.
More info: This issue impacted message sending, receiving, or both, as well as being able to send or view inline media, starting new calls, chats, and recordings in Microsoft Teams.
Final status: Service-side telemetry has remained stable and confirmed that the service has been restored to a healthy state with no further mitigation actions needed.
Scope of impact: Some users may have had delays or failures when utilizing multiple Microsoft Teams features.
Start time: Monday, June 22, 2026, at 1:00 PM UTC
End time: Monday, June 22, 2026, at 4:53 PM UTC
Root cause: A third-party service network infrastructure interruption resulted in this event.
Next steps: We're identifying what potions of our review process need to be revitalized regarding the way we’re alerted to specific service issues in an effort to prevent impact like this in the future.
|
|---|
|
| Time: | Mon Jun 22 14:18:35 2026 |
|---|
| Description: | Title: Some users may have delays or failures in multiple Microsoft Teams features
User impact: Users may have delays or failures in multiple Microsoft Teams features
More info: This issue impacts message sending, receiving, or both, as well as being able to send or view inline media, starting new calls, chats, and recordings in Microsoft Teams.
Current status: We're continuing to investigate this issue and monitor service-side telemetry to ensure that the service remains healthy, so that we may ensure thereare no further issues requiring action to mitigate the impact.
Scope of impact: Some users may have delays or failures when utilizing multiple Microsoft Teams services.
Root cause: A third-party service network infrastructure interruption is resulting in this event.
Next update by: Monday, June 22, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jun 22 12:16:28 2026 |
|---|
| Description: | Title: Some users may have delays or failures in multiple Microsoft Teams features
User impact: Users may have delays or failures in multiple Microsoft Teams features
More info: This issue impacts message sending, receiving, or both, as well as being able to send or view inline media, starting new calls, chats, and recordings in Microsoft Teams.
Current status: We're continuing to monitor service-side telemetry and are seeing the service is improving. We identified that a third-party service interruption resulted in this impacting event. To ensure the service remains healthy, we're continuing to monitor the telemetry to ensure that further mitigation actions aren't needed.
Scope of impact: Some users may have delays or failures when utilizing multiple Microsoft Teams services.
Root cause: A third-party service network infrastructure interruption is resulting in this event.
Next update by: Monday, June 22, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Jun 22 11:08:02 2026 |
|---|
| Description: | Title: Some users may have delays or failures when sending messages or making calls in Microsoft Teams
User impact: Users may have delays or failures when sending messages or making calls in Microsoft Teams.
Current status: We're investigating service-side telemetry to better understand this impacting issue and determine our next steps.
Scope of impact: Some users may have delays or failures when sending messages or making calls in Microsoft Teams.
Next update by: Monday, June 22, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon Jun 22 10:20:39 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.
|
|---|
|
CW1391746 - Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Jun 12 00:00:00 2026 |
|---|
| End Time: | Mon Jun 15 18:53:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jun 22 09:28:57 2026 |
|---|
| Root Cause: | A recently deployed service change in Microsoft 365 Copilot Chat introduced an issue in the request processing path. The change caused an extension, that was expected to run prior to the final response generation, to instead run after the response had already been fully generated. As this post-generation execution path was not expected, the extension incorrectly modified the completed response state. This caused otherwise successful chat responses to be treated as failed requests by the processing path, resulting in affected users seeing a "Something went wrong" message instead of the response that had originally been generated. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 22 09:27:35 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 17 14:20:06 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 15 19:54:28 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returned the following error message: "Something went wrong." Some users were unable to submit a prompt in Microsoft 365 Copilot Chat and received an error message. Some users saw Copilot responses being provided successfully at first but then encountered an error message that overridden and removed the response after it had initially been generated successfully.
Final status: We have confirmed with impacted users that the issue has been fully resolved. We appreciate your organization's understanding and patience while we worked on addressing this incident.
Scope of impact: This issue affected some users when they tried to submit a prompt in Microsoft 365 Copilot Chat. This section was updated as our investigation continued.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
End time: Monday, June 15, 2026, at 10:40 PM UTC
Root cause: A recently deployed service change in Microsoft 365 Copilot Chat introduced an issue in the request processing path. The change caused an extension, that was expected to run prior to the final response generation, to instead run after the response had already been fully generated. As this post-generation execution path was not expected, the extension incorrectly modified the completed response state. This caused otherwise successful chat responses to be treated as failed requests by the processing path, resulting in affected users seeing a "Something went wrong" message instead of the response that had originally been generated.
Existing monitoring did not detect this scenario because the responses were created and stored successfully before the later error occurred. We mitigated the issue by disabling the affected code path, which restored normal service behavior.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
|
|---|
|
| Time: | Mon Jun 15 18:51:33 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: We've identified that a recent change within the service was causing impact. We've deployed a configuration change to disable the offending portion of code, and we're observing positive improvements in service availability. We're currently monitoring the service and reaching out to affected users to confirm that the issue is fully resolved.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
Root cause: A recently deployed build was identified to be causing impact, and our investigation into the root cause within this build remains ongoing. The previously outlined token authorization configuration change was not directly related to the root cause for this issue.
Next update by: Tuesday, June 16, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Jun 15 16:55:01 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: We’ve encountered an issue within our deployment pipeline that’s preventing a roll back to the last healthy build. We’re working to unblock the pipeline with urgency and once completed, we’ll proceed with the roll back across all impacted infrastructure to the last known healthy build. We understand how much issues like this can affect your organization, and we appreciate your partnership as we work to remediate impact.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
Root cause: A recently deployed build was identified to be causing impact, and our investigation into the root cause within this build remains ongoing. The previously outlined token authorization configuration change was not directly related to the root cause for this issue.
Next update by: Monday, June 15, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 14:58:20 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: Our investigation has identified a specific internal telemetry log matching the reports of this issue, beginning around Friday, June 12, 2026, at 4:00 AM UTC. From this, we’ve identified an internal service build that is causing the issue. We’re rolling back to the last known good build on a small portion of infrastructure to confirm the issue is resolved. Once validated, we’ll proceed with the rollback across all impacted infrastructure.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
Root cause: A recently deployed build was identified to be causing impact, and our investigation into the root cause within this build remains ongoing. The previously outlined token authorization configuration change was not directly related to the root cause for this issue.
Next update by: Monday, June 15, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 12:55:45 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: We’re continuing to see failures in error logs provided by customers and internal service logs after the change reversion. While our review of the fresh set of error logs and our internal service health signals is ongoing, we’ll open more workstreams to mitigate the remaining impact based on our findings.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 11:57:19 2026 |
|---|
| Description: | After reverting the change across the Production environment, we're still seeing some evidence of user impact through our service health telemetry systems. Some customers have also reported the issue appears to still be occurring. We’re investigating a fresh set of logs to determine our next steps to resolve the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 11:01:05 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’ve successfully reverted the change within the Production environment, and we’re working to confirm if this has resolved the issue, or if additional actions are required to mitigate impact. We will continue to open and pursue additional mitigation workstreams until the issue is fully resolved.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 10:36:21 2026 |
|---|
| Description: | We've successfully reverted the change broadly across the Production environment, and we're seeing positive signs of recovery in our service telemetry. Affected customers are testing to confirm mitigation as well.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 09:59:49 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’ve encountered an issue with reverting the change causing it to take longer than we expected. We’ve successfully reverted the change within our internal test environment and are in the process of validating its effectiveness. When this is complete, we will revert the change more broadly.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 09:01:27 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’re continuing to monitor the progress of reverting the change which we expect to be complete within one hour.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 08:32:27 2026 |
|---|
| Description: | We're closely monitoring the reversion of the change which is progressing as expected. While this continues, we're monitoring service telemetry for signs of improvement.
Next update by: Monday, June 15, 2026, at 1:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 08:00:25 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’ve identified a recent token authorization configuration change was applied that unexpectedly introduced a misconfiguration and caused impact. We're continuing to work on reverting this change.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 06:59:51 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: While we’re continuing to analyze this change, we’ve started to reverse it to mitigate the impact. When this has completed, we will begin to validate service telemetry to ensure it has fully resolved the issue.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 06:40:12 2026 |
|---|
| Description: | We’ve identified a recent change that may have resulted in impact and we’re analyzing this change in more detail to determine if it is the root cause.
Next update by: Monday, June 15, 2026, at 11:00 AM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 06:00:09 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: While we continue to analyze the newly obtained HTTP Archive format (HAR) logs, we’ve identified a specific failure from service side telemetry and are looking into this further to determine the next steps required.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Jun 15 05:34:20 2026 |
|---|
| Description: | Our analysis of HTTP Archive format (HAR) logs has so far been inconclusive. We’re reviewing newly obtained logs to assist in progressing the investigation.
Next update by: Monday, June 15, 2026, at 10:00 AM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 04:57:32 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: Our analysis is continuing into impacted users logs and recent changes that align with the impact start time to help identify the next troubleshooting steps required to resolve the issue. While this continues, we’ve requested additional HTTP Archive format (HAR) files to assist in our investigation.
Scope of impact: Your organization is impacted by this event, and users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Jun 15 04:31:15 2026 |
|---|
| Description: | In addition to our analysis of service telemetry and client-side logs from impacted users, we’re reviewing recent changes which may have resulted in impact.
Next update by: Monday, June 15, 2026, at 9:00 AM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 03:24:42 2026 |
|---|
| Description: | We're continuing our analysis of HTTP Archive format (HAR) files and service telemetry. In addition, we're attempting to reproduce the issue internally to determine the next steps required to resolve the issue.
Next update by: Monday, June 15, 2026, at 9:00 AM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 02:47:12 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We're reviewing the provided case details and HTTP Archive format (HAR) files to help inform our next troubleshooting steps for pinpointing the underlying cause of the error message.
Scope of impact: Your organization is impacted by this event, and users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Jun 15 02:17:02 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
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.
|
|---|
|
EX1394927 - Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 17 02:00:00 2026 |
|---|
| End Time: | Sat Jun 20 12:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jun 20 12:30:46 2026 |
|---|
| Root Cause: | A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that was causing resource contention and impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jun 20 12:26:39 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may have been unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may have impacted admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Final status: We've processed the backlog of accumulated requests and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may have been impacted.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
End time: Saturday, June 20, 2026, at 4:00 PM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that was causing resource contention and impact.
Next steps:
- We're reviewing the offending provisioning feature to determine why it introduced a large number of synchronization divergences once implemented, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jun 20 09:32:42 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: Our efforts to monitor service health telemetry to validate that the backlog of accumulated requests has fully processed is ongoing. We expect to be able to provide confirmation that the issue is resolved by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Saturday, June 20, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat Jun 20 04:55:43 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We’re continuing to monitor service health telemetry to validate that the backlog of accumulated requests has fully processed. Service health remains stable following the disablement of the offending provisioning feature and we’re maintaining an extended monitoring period to confirm sustained service stability and ensure no further impact is observed before concluding our mitigation efforts.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Saturday, June 20, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Fri Jun 19 16:04:30 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We've confirmed that disabling the offending provisioning feature successfully helped to stabilize the affected service infrastructure and alleviate impact. We're continuing to monitor service health telemetry in order to validate that the backlog of accumulated requests fully processes, which we anticipate will complete and remediate all impact by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Saturday, June 20, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Fri Jun 19 13:33:44 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We've continuing to disable the offending provisioning feature and clear the backlog of accumulated requests, and we anticipate both these processes will complete and remediate the impact by our next scheduled communications update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Estimated time to resolve: We anticipate the offending provisioning feature will be disabled and the backlog of accumulated requests processed by Friday, June 19, 2026, at 9:30 PM UTC.
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Jun 19 09:57:51 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We’re continuing with our efforts to disable the provisioning feature responsible for generating additional synchronization divergences and to remove the existing backlog. We expect to be able to provide a remediation timeline by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jun 19 03:38:15 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We’re progressing with our efforts to disable the provisioning feature responsible for generating additional synchronization divergences and are continuing cleanup efforts to remove the existing backlog. In parallel, we’re implementing processing changes to help reduce system load and improve throughput, as we work to restore affected provisioning operations to expected service levels.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Jun 18 18:30:14 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We've updated the Title, User impact, More info, and Scope of impact sections as we've determined that any actions involving DNS records within the Exchange admin center may be impacted. We're continuing to perform cleanup efforts and remove existing divergences to return the service to expected functionality.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Jun 18 15:19:11 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We've identified that a recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that prevented some Exchange Online IPv6 to IPv4 domain changes from completing successfully. To remediate this issue and prevent additional synchronization divergences from being created, we've disabled the affected provisioning feature and are performing cleanup efforts to remove the existing divergences for full remediation.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that prevented some Exchange Online IPv6 to IPv4 domain changes from completing successfully.
Next update by: Friday, June 19, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Wed Jun 17 22:46:11 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: More time is needed to investigate the Domain Name System (DNS) logs to isolate the source of impact. We aim to have an updated status by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 8:13 AM UTC
Next update by: Thursday, June 18, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 20:45:05 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We're furthering our analysis on the Domain Name System (DNS) logs to isolate the source of traffic to help determine a path towards remediation.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Jun 17 18:34:45 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We've identified that unusually high traffic to the affected infrastructure is preventing the cmdlet used to change the domain from IPv6 to IPv4 from working as expected. We're reviewing Domain Name System (DNS) logs to determine the source of this traffic, which may help us determine a strategy that remediates impact.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jun 17 16:59:26 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We're continuing to review data, which includes error details, to determine the root cause and a strategy that remediates impact.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, June 17, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 15:56:49 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We're reviewing data to determine why admins may be unable to change their domain from IPv6 to IPv4.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, June 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 15:21:45 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPV6 to IPV4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
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.
|
|---|
|
EX1274156 - Some users may not have seen the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 14 08:35:00 2025 |
|---|
| End Time: | Thu Jun 4 13:25:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jun 20 09:56:21 2026 |
|---|
| Root Cause: | A code regression was causing impact to occur.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jun 20 09:53:32 2026 |
|---|
| Description: | Title: Some users may not have seen the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not have seen the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may have seen that the My Templates add-in wasn't appearing in available apps.
Final status: We've determined that a code regression was causing impact to occur. We've successfully deployed our code fix and have confirmed with a sample of affected users that impact has been resolved.
Scope of impact: This issue may have affected any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Start time: Tuesday, October 14, 2025, at 12:35 PM UTC
End time: Thursday, June 4, 2026, at 5:25 PM UTC
Root cause: A code regression was causing impact to occur.
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 Jun 15 17:49:02 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: As we progress with our root cause analysis and review a subset of Outlook service infrastructure and our legacy code paths, we've deployed a solution to restore My Templates and Viva Insights. Our internal testing has validated that it will restore My Templates and Viva Insights for Outlook desktop and Outlook on the web users, and our fix deployment timeline projects it will have remediated the impact by our next scheduled communication update.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 22, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jun 8 17:38:13 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've continuing to investigate a portion of Outlook infrastructure responsible for My Templates and Viva Insights add-ins to help with identifying the underlying root cause. Simultaneously, we're validating if legacy code paths being utilized to view or access the affected add-ins may be contributing to impact and what our new remediation plan should be.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 15, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 18:34:11 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've completed deploying the fix and identified after additional testing and validations that the impact persists. We're further investigating a portion of Outlook infrastructure responsible for My Templates and Viva Insights add-ins to help with identifying the underlying root cause while we formulate a new remediation plan.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 08, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri May 29 18:50:14 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: Deployment of the fix is ongoing. We’re monitoring the deployment of the fix, which includes enhanced logging that will assist in our assessment of the impact and help with confirming the underlying cause of this issue and will be analyzed prior to our next update to determine whether any additional remediation steps are necessary.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 01, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue May 19 18:01:31 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're deploying the fix to remediate the impact. We expect that our fix deployment will be complete by our next scheduled communication update, after which we'll evaluate any potential needs for supplemental adjustments.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Friday, May 29, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon May 18 22:00:25 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're monitoring our potential fix and evaluating it's effectiveness in our internal testing environment, ensuring that it successfully addresses impact. We'll look to provide an estimated timeline for completion once one becomes available.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, May 19, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 14 21:11:14 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've completed our preliminary validation phase and begun rolling out our potential fix to our internal testing environment for final validation prior to its broad release. In parallel, we're continuing to assess to determine a potential timeline for the full deployment of the fix.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, May 19, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed May 13 20:19:37 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're continuing our operation to finalize our validations for a code fix to address the suspected configuration issue we believe is causing impact. Upon our fix being validated, we'll initiate the deployment and share an estimated timeline of completion.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Friday, May 15, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed May 6 19:53:28 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We’re validating a code fix to address what we suspect may be a configuration issue that was introduced by a recent change made to the service and help confirm the underlying cause of this issue.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, May 14, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 22 19:50:06 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're continuing our analysis of the underlying code to isolate the source of impact. In parallel, we're in the preliminary stages of developing a fix to remediate impact.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, May 7, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Apr 20 19:27:24 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: Our analysis of the underlying code to understand the source of impact with the My Templates add-ins in Exchange Online is ongoing. We've identified a recent change that we're testing disabling for some affected users to validate whether it remediates the impact with My Templates.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 23, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Apr 15 18:32:21 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're continuing to analyze the service code to help uncover the underlying root cause of impact; however, more time is needed.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, April 21, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Apr 13 16:34:53 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our review of the service code is progressing as we seek to identify any issues or unexpected behavior which may indicate the root cause.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 16, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Apr 9 16:15:32 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our review of the HAR traces and additional impact details was inconclusive. We're reviewing the service code to identify potential code issues that may be contributing to the reported impact.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Monday, April 13, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Apr 9 01:28:30 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We’ve determined that the Viva Insights add-in is also impacted by this issue, and we’ve modified the Title, User impact, and Scope sections of this communication to reflect our new understanding. We're continuing to review the fresh HAR traces provided by a subset of affected users and have reached out to a subset of users for additional impact details to assist in our active root cause investigation.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Apr 8 15:13:29 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're continuing to review the fresh HAR traces provided by a subset of affected users and have reached out to a subset of users for additional impact details to assist in our active root cause investigation.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Apr 8 12:42:05 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our analysis of the HAR traces is ongoing to identify the source of the impact and develop a mitigation strategy.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, April 8, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Apr 8 11:52:48 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're reviewing the HTTP Archive (HAR) files provided by a subset of affected users to help determine our next troubleshooting steps.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, April 8, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Apr 8 11:23:48 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1396891 - Admins may be unable to provision some users’ Exchange Online mailboxes
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 18 03:28:00 2026 |
|---|
| End Time: | Fri Jun 19 17:19:51 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 19 17:21:14 2026 |
|---|
| Root Cause: | A separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID caused this issue and resulted in impact to admins' provisioning attempts.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 19 17:21:10 2026 |
|---|
| Description: | Title: Admins may be unable to provision some users’ Exchange Online mailboxes
User impact: Admins may have been unable to provision some users’ Exchange Online mailboxes.
More info: Affected admins may have also been unable to access the Exchange admin center.
Final status: We've validated that the backlogged provisioning requests fully processed and our service change implementation successfully remediated all impact for this issue.
Scope of impact: Admins who attempted to provision some users' Exchange Online mailboxes or access the Exchange admin center may have been impacted by this event.
Start time: Thursday, June 18, 2026, at 7:28 AM UTC
End time: Friday, June 19, 2026, at 8:51 PM UTC
Root cause: A separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID caused this issue and resulted in impact to admins' provisioning attempts.
Next steps:
- We're continuing to review how this data sync gap between Exchange Online and Microsoft Entra ID was introduced in order to improve our service reliability for admin provisioning requests and access to the Exchange admin center, and to avoid similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 19 12:43:37 2026 |
|---|
| Description: | Title: Admins may be unable to provision some users’ Exchange Online mailboxes
User impact: Admins may be unable to provision some users’ Exchange Online mailboxes.
More info: Affected admins may also be unable to access the Exchange admin center.
Current status: We've determined that a separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID is causing this issue and resulting in impact to admins' provisioning attempts. We're continuing to monitor the effectiveness of our service change implementation aimed at correcting this gap while the backlogged provisioning requests process.
Scope of impact: Admins attempting to provision some users' Exchange Online mailboxes or access the Exchange admin center may be impacted by this event.
Start time: Thursday, June 18, 2026, at 7:28 AM UTC
Root cause: A separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID is causing this issue and resulting in impact to admins' provisioning attempts.
Next update by: Saturday, June 20, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Fri Jun 19 07:52:05 2026 |
|---|
| Description: | Title: Admins can’t provision some users’ Exchange Online mailboxes
User impact: Admins can’t provision some users’ Exchange Online mailboxes.
Current status: We're progressing with our analysis of support and diagnostic data to determine the underlying cause of the issue. In parallel, we've implemented a service change that is expected to help mitigate the impact and are actively monitoring its effectiveness as affected provisioning requests continue to be processed. However, we're seeing positive signs, with some provisioning requests now completing successfully. We'll continue to monitor backlog reduction and work closely with your representatives to evaluate the effectiveness of the service change and confirm sustained improvement.
Scope of impact: Impact is specific to admins attempting to provision mailboxes or access the Exchange admin center.
Next update by: Friday, June 19, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Jun 19 05:06:38 2026 |
|---|
| Description: | Title: Admins can’t provision some users’ Exchange Online mailboxes
User impact: Admins can’t provision some users’ Exchange Online mailboxes.
Current status: We’re continuing our analysis of support case details, as well as working with your representatives to obtain further contextual details of the impact scenario to help isolate the source of impact and formulate a mitigation plan.
Scope of impact: Impact is specific to admins attempting to provision mailboxes or access the Exchange admin center.
Next update by: Friday, June 19, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Fri Jun 19 02:12:46 2026 |
|---|
| Description: | Title: Admins can’t provision some users’ Exchange Online mailboxes
User impact: Admins can’t provision some users’ Exchange Online mailboxes.
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 admins can’t provision some users’ Exchange Online mailboxes. This information may be updated as our investigation continues.
Next update by: Friday, June 19, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Jun 19 02:02:05 2026 |
|---|
| Description: | Title: Admins can’t provision some users’ mailboxes
User impact: Admins can’t provision some users’ mailboxes.
Current status: We're investigating a potential issue in which admins can’t provision some users’ mailboxes and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1392948 - Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 15 20:51:00 2026 |
|---|
| End Time: | Thu Jun 18 13:57:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 19:00:17 2026 |
|---|
| Root Cause: | A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, was causing issues within the IME flow, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 18:59:12 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may have been disabled and may have switched to English in Exchange Online.
Final status: We’ve confirmed with affected users that this issue is resolved following the deployment of our fix.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may have been impacted.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
End time: Thursday, June 18, 2026, at 5:57 PM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, was causing issues within the IME flow, 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: | Wed Jun 17 19:08:06 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: Our updated fix deployment has completed and we're reaching out to affected users to confirm that this fix has fully remediated the event.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Friday, June 19, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Jun 17 14:30:12 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We've confirmed that our fix aimed at reverting the offending service update didn't include all necessary components required to remediate impact for this issue. We've corrected this fix and have placed it back in queue for safe deployment, which we expect will initiate by our next scheduled communications update. Once deployed, we'll monitor saturation progress and provide a timeline for its completion as one becomes available.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Thursday, June 18, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Jun 17 04:25:01 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We've received confirmation from affected users that impact persists following the completed reversion. We're investigating why the reversion has not fully alleviated the issue and are assessing why users have not yet received the updated client version containing the fix.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jun 16 23:43:54 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We're continuing our efforts to reach out to affected users to confirm if impact has ceased after our deployed fix.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Jun 16 21:44:17 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: Our deployment to revert the offending service update to remediate impact has completed. We're reaching out to your representatives to confirm if impact has ceased.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Jun 16 15:27:25 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We've completed our review of the HTTP archive format (HAR) logs and identified that a recent service update, intended to modify which touch keyboard appears when users enter email addresses in the recipient field, caused impact to the IME flow and is resulting in impact. We're reverting the offending service update to remediate the impact, which we anticipate will be complete by our next scheduled communications update. Once the reversion is completed, we'll test with a subset of affected users to validate remediation.
Scope of impact: Your organization is affected by this event, and users encountering the IME for Japanese/Korean input is disabled and switches to English in Exchange Online. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jun 16 01:11:45 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We're analyzing HTTP Archive logs and diagnostic data to pinpoint the source of impact to determine our next steps.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Next update by: Tuesday, June 16, 2026, at 7:30 PM UTC
|
|---|
|
SP1386381 - Users may be unable to access Excel files through web browsers from SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 7 23:43:00 2026 |
|---|
| End Time: | Thu Jun 18 15:40:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Office Web Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 17:20:10 2026 |
|---|
| Root Cause: | A code issue during the request flow for opening Excel files in SharePoint Online was causing errors, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 17:09:22 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through web browsers from SharePoint Online
User impact: Users may have been unable to access Excel files through web browsers from SharePoint Online.
More info: As we worked to remediate the impact, users could open the file in the Excel desktop app to circumvent impact.
Final status: Following our completed fix deployment, our testing with affected users has validated that Excel files are able to be accessed through the browser, and that the impact has been remediated.
Scope of impact: Users who attempted to access subsites with unique permissions not inherited from the parent site on SharePoint Online weren't able to access files in Excel for the web browser.
Start time: Monday, June 8, 2026, at 3:43 AM UTC
End time: Thursday, June 18, 2026, at 7:40 PM UTC
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online was causing errors, which resulted in impact.
Next steps:
- We're further analyzing our Excel request flow and the isolated code issue to help us prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 17 16:08:32 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: Our deployment is taking longer than initially expected, and we're isolating ways to expedite the remainder of our deployment to remediate impact as swiftly as possible.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Thursday, June 18, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Jun 15 16:10:18 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We're continuing to monitor the deployment of our fix, and we anticipate that we'll be ready to test for mitigation with a subset of affected users by our next scheduled update.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Wednesday, June 17, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Jun 12 16:25:42 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've completed the validation of the fix and have initiated the release. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Monday, June 15, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Jun 11 14:11:49 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've confirmed that the code fix is ready for testing and validation. Once completed, we'll provide a more detailed update regarding the deployment schedule.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Friday, June 12, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 21:16:13 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We identified a code issue that is causing errors when opening Excel files. We're developing a fix for the issue and anticipate that it will take time to complete. Once the fix is ready, we'll begin deploying to the affected environment to remediate the impact.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Wednesday, June 17, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Jun 10 17:38:08 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: Our investigation has identified a recent update as the potential cause of this issue. We're validating that it's the source of impact as well as a fix before deploying to all affected areas.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Thursday, June 11, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Jun 10 16:49:54 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've determined that the recent update isn't the cause of impact. We're analyzing other recent updates along with testing additional service-side reproductions of this issue to isolate the root cause.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 14:42:06 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've identified a recent update that could be potentially responsible for this issue. We're in the process of validating this as the source before applying mitigation to all impacted areas.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 12:52:31 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: Our investigation continues into our reproduction of the event and log review. In parallel, we're also reviewing if any recent updates or changes could be contributing to impact.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 11:38:12 2026 |
|---|
| Description: | Title: Users may be unable to access files in Excel for the web opened from SharePoint Online
User impact: Users may be unable to access files in Excel for the web opened from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We're reproducing the impact of this event and gathering logs associated with specific requests to better understand this issue and determine our next steps.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 10:58:36 2026 |
|---|
| Description: | Title: Users can't access Excel files through browser from SharePoint Online
User impact: Users can't access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
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.
|
|---|
|
CW1390285 - Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 2 06:05:00 2026 |
|---|
| End Time: | Thu Jun 18 13:04:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 16:21:25 2026 |
|---|
| Root Cause: | A recent upgrade to unlicensed users' capabilities within Copilot Chat wasn't included in current usage logging logic, causing exclusion of that data from usage reports, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 15:31:40 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not have seen accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may have seen lower than expected data reported for Copilot Chat users who didn't have a Microsoft 365 Copilot standalone license assigned.
Final status: We've confirmed after a period of monitoring that the data restatement process has completed and impact is fully remediated.
Scope of impact: This issue may have affected any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
End time: Thursday, June 18, 2026, at 5:04 PM UTC
Root cause: A recent upgrade to unlicensed users' capabilities within Copilot Chat wasn't included in current usage logging logic, causing exclusion of that data from usage reports, which resulted in impact.
Next steps: We're reviewing and improving our update validation procedures to detect and prevent similar data exclusions in usage reports in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 17 15:54:37 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: We're monitoring the final stages of the data restatement process for the organizational level trend view to validate that this issue is fully resolved.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
Root cause: A recent upgrade to unlicensed users' capabilities within Copilot Chat wasn't included in current usage logging logic, causing exclusion of that data from usage reports, which is resulting in impact.
Next update by: Thursday, June 18, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jun 16 15:55:53 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: The backlogged data has completed restatement for active days metrics, which has restored user level details for this event. We're continuing to monitor the final stages of the restatement process for the organizational level trend view to ensure that all usage data is fully restored.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Wednesday, June 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 19:59:33 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: We're continuing to monitor as the backlogged data such as Organization level trend views and Active days metrics in the user level table of Copilot chat usage reports are being processed to ensure all data is included in the reports.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Tuesday, June 16, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 15:59:21 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: We've confirmed that all necessary fixes for usage metrics have been successfully deployed. Admins may start seeing an increase in active usage for Copilot Chat. Additionally, we're monitoring as backlogged data is being drained to ensure all previous impacted usage data during the duration of this event is fully restored.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Tuesday, June 16, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Sun Jun 14 15:43:40 2026 |
|---|
| Description: | Title: Users may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Users may not see accurate usage data for Copilot Chat in usage reports within the Microsoft 365 admin center.
More info: This issue strictly affects usage data for unlicensed Copilot Chat users. Users may see lower than expected data reported for unlicensed Copilot Chat users.
Current status: We've implemented a code fix to restore organizational-level metrics such as accurate Active User counts, and we've confirmed that our fixes are allowing updated accurate reporting to reach affected users. We're working to isolate the root cause on why user-level metrics aren’t being reported in a timely manner to determine our next remediation steps to restore affected user-level metrics.
Scope of impact: This issue may affect any user attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Monday, June 15, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Sat Jun 13 17:19:31 2026 |
|---|
| Description: | Title: Users may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Users may not see accurate usage data for Copilot Chat in usage reports within the Microsoft 365 admin center.
More info: This issue strictly affects usage data for unlicensed Copilot Chat users. Users may see lower than expected data reported for unlicensed Copilot Chat users.
Current status: This is a continuation of MO1388943. We're continuing to review a recent upgrade to identify a viable method to restate the affected data and remediate the impact.
Scope of impact: This issue may affect any user attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Sunday, June 14, 2026, at 9:00 PM UTC
|
|---|
|
MO1387691 - Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jun 11 16:00:00 2026 |
|---|
| End Time: | Thu Jun 11 17:56:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jun 18 11:10:56 2026 |
|---|
| Root Cause: | The root cause is still being investigated. We will provide more information in our next update. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 11:10:56 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 15 19:43:58 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jun 11 18:05:51 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com.
More info: Admins may have been able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams was not impacted and could have been leveraged in the interim while we mitigated the issue.
Final status: We’ve successfully rolled back the change throughout the affected infrastructure, and we've confirmed with previously affected users that the impact is mitigated.
Scope of impact: Any user or admin may have been affected by this event.
Start time: Thursday, June 11, 2026, at 8:00 PM UTC
End time: Thursday, June 11, 2026, at 9:56 PM UTC
Preliminary root cause: We've identified an issue with a recent deployment which is contributing to impact. We will provide more information in our Post-Incident Report.
Next steps:
- We're analyzing the recent deployment to identify why this issue occurred and how to prevent it from happening again in the future.
- We're reviewing our change management processes to determine areas of improvement.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Jun 11 17:54:45 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com.
More info: Admins may be able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams is not expected to be impacted and can be leveraged in the interim while we mitigate the issue.
Current status: We have successfully reverted the change for 97 percent of the affected infrastructure. We're continuing to monitor the progress of the reversion and we're also observing an uptick in service availability. Additionally, we've started to receive confirmation that service availability is returning for some users. In parallel, we're investigating the underlying cause of the problem and will provide more information when available.
Scope of impact: Our investigation indicates that any user or admin may be affected by this event. This section is subject to change as the investigation continues.
Start time: Thursday, June 11, 2026, at 8:00 PM UTC
Preliminary root cause: We've identified an issue with a recent deployment which is contributing to impact. We will continue to perform a root cause analysis to identify how this occurred and how we can prevent this from happening in the future.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jun 11 17:20:21 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com.
More info: Admins may be able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams is not expected to be impacted and can be leveraged in the interim while we mitigate the issue.
Current status: This is a continuation of a communication posted under CW1387674. We’ve identified an issue with a recent deployment for Microsoft Copilot. We’re reverting to a previous build to remediate impact as soon as possible. We expect this to be completed in the next 30 minutes.
Scope of impact: Our investigation indicates that any user or admin may be affected by this event. This section is subject to change as the investigation continues.
Start time: Thursday, June 11, 2026, at 8:00 PM UTC
Estimated time to resolve: We expect the reversion to be complete in the next 30 minutes.
Root cause: The root cause is still being investigated. We will provide more information in our next update.
Next update by: Thursday, June 11, 2026, at 10:00 PM UTC
|
|---|
|
DZ1395542 - Some users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 13 12:14:00 2026 |
|---|
| End Time: | Wed Jun 17 17:02:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 10:17:33 2026 |
|---|
| Root Cause: | A service configuration update caused an issue in the sensor’s dynamic component, leaving a stale proxy configuration that prevented telemetry uploads and resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 08:55:52 2026 |
|---|
| Description: | Title: Some users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint
User impact: Users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint.
More info: Some devices configured with the Telemetry Proxy Server registry may have intermittently experienced a non-reporting state, resulting in missing or delayed security telemetry in Microsoft Defender for Endpoint. Any detections that would have derived from that sensor data during the gap were not generated. Real-time endpoint protection, antivirus, device manageability, and device configuration/identity all continued to function as expected.
To attempt to identify devices that may still be impacted, they can search for devices in 'No sensor data': https://learn.microsoft.com/defender-endpoint/device-health-sensor-health-os#sensor-health--os-tab
Final status: We've identified that a service configuration update caused an issue in the sensor’s dynamic component, leaving a stale proxy configuration that prevented telemetry uploads and resulted in impact. We've deployed a configuration fix to resolve the issue. However, affected devices require a restart or they should remove and re-add the proxy registry.
Scope of impact: Impact was specific to some users utilizing devices that are configured with the Telemetry Proxy Server registry in Microsoft Defender for Endpoint.
Start time: Wednesday, May 13, 2026, at 4:14 PM UTC
End time: Wednesday, June 17, 2026, at 9:02 PM UTC
Root cause: A service configuration update caused an issue in the sensor’s dynamic component, leaving a stale proxy configuration that prevented telemetry uploads and resulted in impact.
Next steps: We're reviewing our configuration change procedures to help prevent this problem from happening again.
|
|---|
|
| Time: | Thu Jun 18 06:56:25 2026 |
|---|
| Description: | Title: Some users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint
User impact: Users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint.
Current status: We've investigated a problem with the Microsoft Defender for Endpoint service in which users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint, and we’ve confirmed that service is now restored. We'll provide additional information in a closure summary within the “History” section of the “Service health” dashboard shortly.
Next update by: Thursday, June 18, 2026, at 1:00 PM UTC
|
|---|
|
PB1395415 - Users may have noticed discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 14 17:15:00 2026 |
|---|
| End Time: | Thu Jun 18 07:17:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI and Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 10:03:44 2026 |
|---|
| Root Cause: | A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, was causing the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 08:51:22 2026 |
|---|
| Description: | Title: Users may have noticed discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may have noticed discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users included, but may not have been limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not have functioned as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not have triggered as expected due to missing utilization signals, and reporting and other metric-driven features may have been affected.
Final status: We've confirmed that the reversion of the offending change has completed successfully. Following a period of monitoring service telemetry, we've verified that service functionality has been restored and impact has been remediated.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may have been impacted by this issue.
Start time: Sunday, June 14, 2026, at 9:15 PM UTC
End time: Thursday, June 18, 2026, at 11:17 AM UTC
Root cause: A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, was causing the 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 Jun 18 04:09:58 2026 |
|---|
| Description: | Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not function as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not trigger as expected due to missing utilization signals, and reporting and other metric-driven features may be affected.
Current status: We're actively monitoring the reversion of the offending change and expect it to complete by our next scheduled update.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, June 14, 2026, at 9:15 PM UTC
Root cause: A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, is causing the impact.
Next update by: Thursday, June 18, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Jun 18 03:28:34 2026 |
|---|
| Description: | Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not function as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not trigger as expected due to missing utilization signals, and reporting and other metric-driven features may be affected.
Current status: We've determined that a recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, is causing the impact. We've begun reverting the change and are actively monitoring progress. We'll provide an estimated completion time for the reversion as soon as it becomes available.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, June 14, 2026, at 9:15 PM UTC
Root cause: A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, is causing the impact.
Next update by: Thursday, June 18, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Jun 18 02:26:18 2026 |
|---|
| Description: | Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not function as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not trigger as expected due to missing utilization signals, and reporting and other metric-driven features may be affected.
Current status: We believe that a recent change made to Microsoft Fabric libraries is causing this issue, and we're reverting this change as a potential remediation option and confirm our root cause theory.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Jun 18 02:02:06 2026 |
|---|
| Description: | Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CW1395054 - Some users may see multiple impact scenarios for Microsoft Copilot Researcher
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 16 10:00:00 2026 |
|---|
| End Time: | Wed Jun 17 21:05:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 17 22:13:16 2026 |
|---|
| Root Cause: | A recent update to the Microsoft Copilot Researcher service incorrectly balanced a high volume of traffic, causing requests to be routed to a portion of infrastructure that didn't have the processing availability to meet the unusual increase in demand and leading to impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 22:11:37 2026 |
|---|
| Description: | Title: Some users may see multiple impact scenarios for Microsoft Copilot Researcher
User impact: Users may have seen multiple impact scenarios for Microsoft Copilot Researcher.
More info: Specifically, users may have seen reauthentication prompts, failed queries, incomplete grounding, or query latency in Microsoft Copilot Researcher
Final status: We've completed our analysis of the system logs and service health telemetry, and we pinpointed a recent update to the Microsoft Copilot Researcher service incorrectly balanced a high volume of traffic, causing requests to be routed to a portion of infrastructure that didn't have the processing availability to meet the unusual increase in demand and leading to impact. We've disabled this update and confirmed through our monitoring that the service health has returned to normal, and impact has been remediated.
Scope of impact: Impact was limited to a small subset of users hosted on the affected infrastructure.
Start time: Tuesday, June 16, 2026, at 2:00 PM UTC
End time: Thursday, June 18, 2026, at 1:05 AM UTC
Root cause: A recent update to the Microsoft Copilot Researcher service incorrectly balanced a high volume of traffic, causing requests to be routed to a portion of infrastructure that didn't have the processing availability to meet the unusual increase in demand and leading to impact.
Next steps:
- We’re analyzing performance data associated with the impacted Microsoft Copilot Researcher scenarios infrastructure following the recent update to better understand what caused the imbalance and prevent similar impact from occurring again in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 17 20:14:25 2026 |
|---|
| Description: | Title: Some users may see multiple impact scenarios for Microsoft Copilot Researcher
User impact: Users may see multiple impact scenarios for Microsoft Copilot Researcher.
More info: Specifically, users may see reauthentication prompts, failed queries, incomplete grounding, or query latency in Microsoft Copilot Researcher
Current status: We're reviewing system logs to isolate the origin of this issue.
Scope of impact: Impact is limited to a small subset of users hosted on the affected infrastructure. This information may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 2:00 AM UTC
|
|---|
|
EX1386636 - Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 13 20:00:00 2026 |
|---|
| End Time: | Mon Jun 15 15:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 17 14:57:36 2026 |
|---|
| Root Cause: | A NetCore deployment introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 14:56:44 2026 |
|---|
| Description: | Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may have been unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurred only when two or more mailbox statuses were requested.
Final status: We've completed deployment of our fix across the affected environment and validated with a subset of affected users that they are now able to see the free/busy status of cross-tenant mailboxes in Exchange Online as expected.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may have been impacted.
Start time: Thursday, May 14, 2026, at 12:00 AM UTC
End time: Monday, June 15, 2026, at 7:00 PM UTC
Root cause: A NetCore deployment introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing.
Next steps:
- We're analyzing the offending NetCore deployment to validate why the potential for impact wasn't caught during our internal testing and validation phases and how we can improve our deployment implementation process moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 16 15:51:25 2026 |
|---|
| Description: | Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurs only when two or more mailbox statuses are requested.
Current status: We've validated that the source of impact was a NetCore deployment, which introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing. Our fix to address the regression is currently at 90 percent saturation in the affected environment, and we've reached out to affected users to begin testing for remediation.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may be impacted.
Start time: Thursday, May 14, 2026, at 12:00 AM UTC
Root cause: A NetCore deployment introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing.
Next update by: Wednesday, June 17, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jun 11 15:19:09 2026 |
|---|
| Description: | Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurs only when two or more mailbox statuses are requested.
Current status: We've confirmed that it may take until our next scheduled update for this fix to saturate and remediate impact. We'll monitor the fix deployment and update the expected timeline of remediation as it progresses.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may be impacted.
Next update by: Tuesday, June 16, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 16:34:38 2026 |
|---|
| Description: | Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurs only when two or more mailbox statuses are requested.
Current status: We've determined that our previous fix will not effectively remediate impact. We're creating a secondary targeted fix that we expect to address the issue and are confirming the timeline for deployment.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may be impacted.
Next update by: Thursday, June 11, 2026, at 8:30 PM UTC
|
|---|
|
MP1394693 - Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 17 03:51:00 2026 |
|---|
| End Time: | Wed Jun 17 13:33:00 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 17 14:16:58 2026 |
|---|
| Root Cause: | A subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 14:14:33 2026 |
|---|
| Description: | Title: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
User impact: Users may have experienced delays in Data Loss Prevention alerts being generated or delivered in Microsoft Purview.
More info: Some users may have experienced delays of up to two hours between DLP activity detection and alert generation in Microsoft Purview.
Final status: We've completed our monitoring period and confirmed that our performance optimizations have successfully remediated the delays in DLP alerts being generated and delivered.
Scope of impact: Impact was specific to users experiencing delays in DLP alerts being generated or delivered in Microsoft Purview.
Start time: Wednesday, June 17, 2026, at 7:51 AM UTC
End time: Wednesday, June 17, 2026, at 5:33 PM UTC
Root cause: A subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact.
Next steps:
- We're analyzing the offending service infrastructure to isolate why it was unable to process and deliver DLP alerts as expected to further our understanding of the underlying impact scenario to determine 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: | Wed Jun 17 12:17:48 2026 |
|---|
| Description: | Title: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
User impact: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
More info: Some users may experience delays of up to two hours between DLP activity detection and alert generation in Microsoft Purview.
Current status: After reviewing reports of impact, we've isolated that a subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact. We've implemented performance optimizations on the affected infrastrucutre to remediate impact, and we're monitoring service availability to confirm DLP alerts are being generated and delivered as expected.
Scope of impact: Impact is specific to users experiencing delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
Start time: Wednesday, June 17, 2026, at 7:51 AM UTC
Root cause: A subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jun 17 11:00:11 2026 |
|---|
| Description: | Title: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
User impact: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
More info: Some users may experience delays of up to two hours between DLP activity detection and alert generation in Microsoft Purview.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Impact is specific to users experiencing delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
Next update by: Wednesday, June 17, 2026, at 5:00 PM UTC
|
|---|
|
TM1393859 - Users may be unable to search for locations for emergency calling in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 16 19:42:23 2026 |
|---|
| End Time: | Wed Jun 17 13:41:34 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 17 13:43:07 2026 |
|---|
| Root Cause: | A recent change meant to optimize the service contained an error that resulted in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 13:43:03 2026 |
|---|
| Description: | Title: Users may be unable to search for locations for emergency calling in Microsoft Teams
User impact: Users may have been unable to search for locations for emergency calling in Microsoft Teams.
More info: Affected users may have received the following error message: "We couldn't find any matches".
Final status: We confirmed that a recent change meant to optimize the service contained an error that resulted in this impact. We reverted this responsible change and have confirmed that this has successfully resolved impact.
Scope of impact: Users attempting to search for locations for emergency calling in Microsoft Teams may have been impacted by this issue.
Start time: Monday, June 8, 2026, at 5:15 PM UTC
End time: Wednesday, June 17, 2026, at 2:00 AM UTC
Root cause: A recent change meant to optimize the service contained an error that resulted in this impact.
Next steps: - We're reviewing the responsible change to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 16 20:21:13 2026 |
|---|
| Description: | Title: Users may be unable to search for locations for emergency calling in Microsoft Teams
User impact: Users may be unable to search for locations for emergency calling in Microsoft Teams.
More info: Affected users may receive the following error message: "We couldn't find any matches".
Current status: We suspect that a recent change related to emergency calling may be causing the issue and we're investigating this change to confirm our root cause theory, which will also aid in determining the next best steps towards a solution.
Scope of impact: Users attempting to search for locations for emergency calling in Microsoft Teams may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Wednesday, June 17, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Jun 16 19:51:29 2026 |
|---|
| Description: | Title: Users may be unable to search and add addresses for emergency calling in auto suggest dialog in Microsoft Teams
User impact: Users may be unable to search and add addresses for emergency calling in auto suggest dialog in Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1329446 - Unable to open files in Office for the web or Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jun 1 08:43:00 2026 |
|---|
| End Time: | Mon Jun 1 10:27:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 17 11:23:04 2026 |
|---|
| Root Cause: | During a routine service deployment, a software compatibility issue affected how a subset of servers reported operational health information within the service. As a result, traffic was not distributed as intended, causing some servers to receive a higher volume of requests than they could efficiently process. The increased load led to elevated request processing times and intermittent failures for some SharePoint and OneDrive operations, including file access, file uploads, and related service requests. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 10:35:25 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 3 19:48:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 11:26:52 2026 |
|---|
| Description: | Title: Unable to open files in Office for the web or Microsoft Teams
User impact: Users may have been unable to open files in Office for the web or Microsoft Teams.
More info: Impacted Office Apps included, but were not limited to:
- Excel
- PowerPoint
When users opened documents, impacted users were shown the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Final status: We've confirmed through customer reports and service telemetry that the impact has been resolved, and the service has remained stable for an extended period of time. As the issue recovered without any specific engineering actions being implemented, engineer teams continue to investigate the underlying root cause so actions can be taken to prevent the issue from reoccurring.
Scope of impact: This issue could have impacted any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Start time: Monday, June 1, 2026, at 12:43 PM UTC
End time: Monday, June 1, 2026, at 2:27 PM UTC
Root cause: During a routine service deployment, a software compatibility issue affected how a subset of servers reported operational health information within the service. As a result, traffic was not distributed as intended, causing some servers to receive a higher volume of requests than they could efficiently process. The increased load led to elevated request processing times and intermittent failures for some SharePoint and OneDrive operations, including file access, file uploads, and related service requests.
Next steps:
- Please see the Post-Incident Report (PIR) for completed list of next steps.
|
|---|
|
| Time: | Mon Jun 1 11:09:52 2026 |
|---|
| Description: | Our telemetry indicates that service availability has returned to normal levels. We're monitoring the service to confirm sustained service stability and continuing to investigate the underlying root cause of the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 1 10:27:25 2026 |
|---|
| Description: | Title: Unable to open files in Office for the web or Microsoft Teams
User impact: Users may be unable to open files in Office for the web or Microsoft Teams.
More info: Impacted Office Apps include, but are not limited to:
- Excel
- PowerPoint
When users open documents, impacted users are shown the following the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Current status: We’re continuing to analyze service telemetry and have identified elevated error rates across Office for the web experiences. We’re correlating these error patterns across service dependencies to further isolate the source of impact and determine appropriate mitigation steps.
Scope of impact: This issue could impact any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Next update by: Monday, June 1, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Jun 1 10:06:31 2026 |
|---|
| Description: | Initial analysis indicates a potential cross-service issue impacting Office for the web experiences. We’re continuing to investigate service telemetry to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 1, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Mon Jun 1 09:49:06 2026 |
|---|
| Description: | Title: Unable to open files in Office for the web.
User impact: Users may be unable to open files in Office for the web.
More info: Impacted Office Apps include, but are not limited to:
- Excel
When users open documents, impacted users are shown the following the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Current status: We're investigating service telemetry to isolate the source of the issue.
Scope of impact: This issue could impact any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Next update by: Monday, June 1, 2026, at 2:30 PM UTC
|
|---|
|
TM1393268 - Some users in North America may have experienced issues with Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 16 09:20:00 2026 |
|---|
| End Time: | Tue Jun 16 09:50:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 16 10:12:58 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 16 10:00:11 2026 |
|---|
| Description: | Title: Some users in North America may have experienced issues with Microsoft Teams
User impact: Users in North America may have experienced issues with Microsoft Teams.
Final status: While we were in the process of analysing service monitoring telemetry to isolate the source of the problem, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Some users using Microsoft Teams in North America may have been impacted.
Start time: Tuesday, June 16, 2026, at 1:20 PM UTC
End time: Tuesday, June 16, 2026, at 1:50 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 16 09:43:15 2026 |
|---|
| Description: | Title: Some users in North America may be experiencing issues with Microsoft Teams
User impact: Users in North America may experience issues when using Microsoft Teams.
Current status: We’ve received reports of an issue affecting Microsoft Teams services in the North America region. We’re reviewing service telemetry and investigating the issue. We’ll provide an update within 30 minutes.
|
|---|
|
|
