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 Wed Aug 19 06:00:07 2026.
DV1437448 - Users are experiencing intermittent failures accessing your Dataverse data or apps
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 13:10:00 2026 |
|---|
| End Time: | Thu Jul 23 15:32:00 2026 |
|---|
| Service: | Microsoft Dataverse |
|---|
| Feature Group: | Environment access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 18 17:56:43 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 18 17:56:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 28 18:29:43 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 23 16:36:28 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users were experiencing intermittent failures accessing your Dataverse data or apps.
Final Status: Following a period of service health diagnostic analysis, we confirmed that service functionality is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A portion of the network infrastructure supporting your environment entered an unhealthy state.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Thu Jul 23 15:50:00 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: We are continuing to monitor service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 14:49:42 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: We completed the failover to healthy redundant infrastructure and are monitoring service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:41:49 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: After our investigation, we determined that a portion of the network infrastructure supporting your environment has entered an unhealthy state, leading to impact. To mitigate the issue, we are performing a failover to healthy redundant infrastructure.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:27:33 2026 |
|---|
| Description: | Title: Users are experiencing intermittent failures accessing your Dataverse data or apps
User impact: Users are experiencing intermittent failures accessing your Dataverse data or apps.
Current Status: We are aware of an emerging issue where users are experiencing intermittent failures accessing your Dataverse data or apps. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
FL1437452 - Flow management and manual invocation operations are failing
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 11:10:00 2026 |
|---|
| End Time: | Thu Jul 23 15:45:00 2026 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 18 17:37:11 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 18 17:37:11 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jul 28 18:31:03 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 23 16:37:27 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations were failing.
Final Status: Following a period of service health diagnostic analysis, we confirmed that service functionality is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A portion of the network infrastructure supporting flow management and manual invocation operations entered an unhealthy state.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
| Time: | Thu Jul 23 15:50:09 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operation are failing.
Current Status: We are continuing to monitor service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 14:49:57 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations are failing.
Current Status: We completed the failover to healthy redundant infrastructure and are monitoring service health diagnostics to confirm recovery.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:48:06 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations are failing.
Current Status: After our investigation, we determined that a portion of the network infrastructure supporting flow management and manual invocation operations entered an unhealthy state, leading to impact. To mitigate the issue, we are performing a failover to healthy redundant infrastructure.
Next Update: Thursday, July 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jul 23 13:46:56 2026 |
|---|
| Description: | Title: Flow management and manual invocation operations are failing
User impact: Flow management and manual invocation operations are failing.
Current Status: We are aware of an emerging issue where flow management and manual invocation operations are failing. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|---|
|
TM1457081 - Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Aug 18 11:33:13 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 18 13:12:30 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Wednesday, August 19, 2026, at 12:00 PM UTC |
|---|
|
Details
| Time: | Tue Aug 18 12:57:26 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client.
More info: Impact is specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Current status: Our investigation has identified a recent configuration change to the video processing pipeline contains an error, resulting in impact. We've reverted this change and are working to validate this issue is no longer occurring.
Scope of impact: Impact is limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client.
Next update by: Wednesday, August 19, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Aug 18 11:59:48 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client.
More info: Impact is specific to approximately four percent of screen sharing sessions initiated by users from the Microsoft Teams web client.
While we're working to remediate impact, users can initiate unaffected screen sharing sessions using the desktop or mobile apps.
Current status: We're analyzing service telemetry to better understand the impact scenario and determine our next diagnostic steps.
Scope of impact: Impact is limited to approximately four percent of users initiating screen sharing from the Microsoft Teams web client.
Next update by: Tuesday, August 18, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Aug 18 11:36:11 2026 |
|---|
| Description: | Title: Some users may experience degraded video quality when screen sharing using the Microsoft Teams web client
User impact: Users may experience degraded video quality when screen sharing using the Microsoft Teams web client.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1456599 - Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 17 09:00:00 2026 |
|---|
| End Time: | Tue Aug 18 11:58:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 18 12:15:17 2026 |
|---|
| Root Cause: | A recent service update introduced a configuration issue in a service component used by the Microsoft Intune Company Portal. Under high traffic conditions, this misconfiguration reduced the effectiveness of the service's caching behavior, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 18 12:14:21 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may have been unable to load apps in the Microsoft Intune Company Portal and received an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client were returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Final status: We've completed the deployment of our fix to correct the misconfiguration and confirmed through service telemetry and user reports that impact was successfully resolved for users.
Scope of impact: Some users attempting to load apps in the Microsoft Intune Company Portal app or web client may have been impacted.
Start time: Monday, August 17, 2026, at 1:00 PM UTC
End time: Tuesday, August 18, 2026, at 3:58 PM UTC
Root cause: A recent service update introduced a configuration issue in a service component used by the Microsoft Intune Company Portal. Under high traffic conditions, this misconfiguration reduced the effectiveness of the service's caching behavior, resulting in impact.
Next steps:
- We're reviewing our service update testing and validation procedures to identify opportunities to improve impact detection and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 18 10:20:01 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We’ve determined that a recent service update introduced a configuration issue in a service component used by the Microsoft Intune Company Portal. Under high traffic conditions, this misconfiguration reduced the effectiveness of the service's caching behavior, resulting in impact. We’re deploying a fix to correct the misconfiguration and are monitoring service telemetry to confirm recovery as the deployment progresses across the affected environments. We've received confirmation that some previously affected users have recovered, while users in environments where deployment of the fix is still in progress may continue to experience impact until deployment is completed.
Scope of impact: Some users attempting to load apps in the Microsoft Intune Company Portal app or web client may be impacted.
Start time: Monday, August 17, 2026, at 1:00 PM UTC
Root cause: A recent service update introduced a configuration issue in a service component used by the Microsoft Intune Company Portal. Under high traffic conditions, this misconfiguration reduced the effectiveness of the service's caching behavior, resulting in impact.
Next update by: Tuesday, August 18, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon Aug 17 21:08:03 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: Based on our telemetry, we can see that the amount of errors has decreased and we expect that most affected users are seeing remediation. We'll continue monitoring to ensure the impact doesn't reoccur. In the meantime, we're continuing our evaluation of recent traffic patterns and potential caching issues to identify the source of the issue which will help us in developing any additional fixes needed.
Scope of impact: Some users may be unable to load apps in the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Tuesday, August 18, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 17 16:14:11 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We're analyzing traffic patterns over the past 24 hours and evaluating potential performance optimizations to assist with remediating impact while we continue to investigate and isolate the underlying root cause.
Scope of impact: Some users may be unable to load apps in the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Tuesday, August 18, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Aug 17 14:38:56 2026 |
|---|
| Description: | Title: Some users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message
User impact: Users may be unable to load apps in the Microsoft Intune Company Portal and receive an error message.
More info: Users attempting to load apps in the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: After further review, we've validated that users are unable to load apps in the Microsoft Intune Company Portal app and are able to load the Intune Company Portal app. We've updated the "Title", "User impact", "More info", and "Scope of impact" fields to reflect this change. We're continuing to review recent service updates and analyze affected Microsoft Intune service infrastructure to isolate potential sources of impact and to determine our next troubleshooting steps.
Scope of impact: Some users may be unable to load apps in the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Monday, August 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Aug 17 14:05:34 2026 |
|---|
| Description: | Title: Some users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message
User impact: Users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message.
More info: Users attempting to load the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We're reviewing recent deployments to affected Intune service infrastructure to isolate potential sources of impact and to determine our next troubleshooting steps.
Scope of impact: Some users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Monday, August 17, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Aug 17 13:17:01 2026 |
|---|
| Description: | Title: Some users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message
User impact: Users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message.
More info: Users attempting to load the Microsoft Intune Company Portal app or web client are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We've received reports from a subset of affected users who have stated that they are unable to load the Microsoft Intune Company Portal app or web client and receive an error message. We're reviewing reports of impact and analyzing the Intune service infrastructure hosting affected users to determine our next troubleshooting steps.
Scope of impact: Some users may be unable to load the Microsoft Intune Company Portal app or web client and receive an error message stating, "Error loading apps: An error occurred attempting to load the apps." This section may be updated as the investigation progresses.
Next update by: Monday, August 17, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Aug 17 12:57:19 2026 |
|---|
| Description: | Title: Users can't load the Microsoft Intune Company Portal app and receive an error message
User impact: Users can't load the Microsoft Intune Company Portal app and receive an error message.
More info: Users attempting to load the Microsoft Intune Company Portal app are returned an error message stating, "Error loading apps: An error occurred attempting to load the apps."
Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1456911 - Users may have been unable to access Microsoft 365 Copilot in Excel
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 17 15:30:00 2026 |
|---|
| End Time: | Tue Aug 18 02:30:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Aug 18 08:14:39 2026 |
|---|
| Root Cause: | A recent change intended to update a supporting web component caused the Copilot pane to fail to load. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 18 03:02:19 2026 |
|---|
| Description: | Title: Users may have been unable to access Microsoft 365 Copilot in Excel
User impact: Users may have been unable to access Copilot in Excel.
More info: The Copilot pane may not have loaded when users selected the Copilot button. Users may have been able to access Copilot through the Excel desktop application.
Final status: We’ve determined that a recent change intended to update a supporting web component caused the Copilot pane to fail to load. We reverted the change to remediate the impact and confirmed in our testing environment that the issue is resolved.
Scope of impact: Impact was specific to users who may have been attempting to access Copilot in Excel through the web application.
Start time: Monday, August 17, 2026, at 7:30 PM UTC
End time: Tuesday, August 18, 2026, at 6:30 AM UTC
Root cause: A recent change intended to update a supporting web component caused the Copilot pane to fail to load.
Next steps: - We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 18 01:55:29 2026 |
|---|
| Description: | Title: Users can’t access Microsoft Copilot in Excel
User impact: Users can’t access Copilot in Excel.
More info: The Copilot pane may not load when users select the Copilot button. Users may be able to access Copilot through the Excel desktop application.
This issue affects Copilot in both Excel on the desktop and the web versions.
Current status: We’re reviewing system logs to isolate the origin of this issue.
Scope of impact: Your organization is affected by this event, and any user can’t access Copilot in Excel on the desktop and on the web. This information may be updated as our investigation continues.
Next update by: Tuesday, August 18, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Aug 18 01:31:12 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1449728 - Users may have experienced increased latency when accessing applications protected by Conditional Access App Control
| Status: | serviceRestored |
|---|
| Start Time: | Fri Aug 7 07:47:00 2026 |
|---|
| End Time: | Fri Aug 7 10:09:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 18 05:03:32 2026 |
|---|
| Root Cause: | A downstream database update responsible for supporting Inline Access functionality introduced an issue that prevented service components from reliably retrieving the data required to process requests, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 7 10:33:37 2026 |
|---|
| Description: | Title: Users may have experienced increased latency when accessing applications protected by Conditional Access App Control
User impact: Users may have experienced increased latency when accessing applications protected by Conditional Access App Control.
More info: Affected users may have encountered intermittent 5XX errors during sign-in attempts when using apps managed by Microsoft Defender XDR. In some cases, retrying the operation may have been successful.
Final status: We've completed our reversion of the affected service change and confirmed through service monitoring that the impact has been remediated.
Scope of impact: Impact was specific to any user attempting to sign in to applications protected by Conditional Access App Control policies.
Start time: Friday, August 7, 2026, at 11:47 AM UTC
End time: Friday, August 7, 2026, at 2:09 PM UTC
Root cause: A downstream database update responsible for supporting Inline Access functionality introduced an issue that prevented service components from reliably retrieving the data required to process requests, resulting in impact.
Next steps:
- We’re reviewing our database update procedures to help prevent the issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Fri Aug 7 09:47:29 2026 |
|---|
| Description: | Title: Users may experience increased latency when accessing applications protected by Conditional Access App Control policies
User impact: Users may experience increased latency when accessing applications protected by Conditional Access App Control policies.
More info: Affected users may encounter intermittent 5XX errors during sign-in attempts when using apps managed by Microsoft Defender XDR. In some cases, retrying the operation may be successful.
Current status: We've identified that a downstream database update responsible for supporting Inline Access functionality introduced an issue that is preventing service components from reliably retrieving the data required to process requests, which is resulting in increased latency and intermittent service errors. We're reverting the recent service change to mitigate impact and are monitoring service health as the reversion progresses.
Scope of impact: Impact is specific to any user attempting to sign in to applications protected by Conditional Access App Control.
Root cause: A downstream database update responsible for supporting Inline Access functionality introduced an issue that is preventing service components from reliably retrieving the data required to process requests, resulting in impact.
Next update by: Friday, August 7, 2026, at 4:00 PM UTC
|
|---|
|
EX1456866 - Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 17 19:38:00 2026 |
|---|
| End Time: | Tue Aug 18 03:15:32 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Aug 18 03:17:37 2026 |
|---|
| Root Cause: | Recent changes to an authentication component utilized for Exchange ActiveSync were causing connection failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 18 03:16:33 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
User impact: Users may have been unable to send or receive new Exchange Online email through the native iOS mail app.
Final status: We reverted the authentication component changes utilized for Exchange ActiveSync and validated in our telemetry as well as with affected users that the impact was remediated.
Scope of impact: Some users attempting to send or receive new Exchange Online email through the native iOS mail app were impacted.
Start time: Monday, August 17, 2026, at 11:38 PM UTC
End time: Tuesday, August 18, 2026, at 7:15 AM UTC
Root cause: Recent changes to an authentication component utilized for Exchange ActiveSync were causing connection failures.
Next steps: We're continuing our analysis of the recent changes to isolate what triggered the initial impact which will help us in refining our update review processes to avoid impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 18 02:48:06 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
User impact: Users may be unable to send or receive new Exchange Online email through the native iOS mail app.
Current status: After reviewing the logs, we identified that there were recent changes to an authentication component utilized for Exchange ActiveSync that is causing connection failures. We're working to revert the problematic changes, which we anticipate should remediate the impact by the time of our next scheduled update, at which point we'll reach out to confirm with a subset of impacted users.
Scope of impact: Some users attempting to send or receive new Exchange Online email through the native iOS mail app are impacted.
Start time: Monday, August 17, 2026, at 11:38 PM UTC
Root cause: Recent changes to an authentication component utilized for Exchange ActiveSync are causing connection failures.
Next update by: Tuesday, August 18, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Aug 18 01:06:54 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
User impact: Users may be unable to send or receive new Exchange Online email through the native iOS mail app.
Current status: We're continuing our analysis of service-side logs and Exchange ActiveSync logs collected from impacted users to understand the source of the issue and determine our next troubleshooting steps.
Scope of impact: Some users attempting to send or receive new Exchange Online email through the native iOS mail app may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, August 18, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Mon Aug 17 23:27:53 2026 |
|---|
| Description: | Title: Some users may be unable to send or receive new Exchange Online email through the native iOS mail app
User impact: Users may be unable to send or receive new Exchange Online email through the native iOS mail app.
Current status: We're reviewing service logs, telemetry, and contextual details provided by impacted users to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Some users attempting to send or receive new Exchange Online email through the native iOS mail app may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, August 18, 2026, at 5:00 AM UTC
|
|---|
|
OP1454727 - Users may be unable to sign in to OneNote using iOS devices
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Aug 14 07:51:32 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Aug 18 01:00:52 2026 |
|---|
| Root Cause: | A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact. |
|---|
| Next Update: | Friday, August 21, 2026, at 4:00 AM UTC |
|---|
|
Details
| Time: | Tue Aug 18 00:57:55 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: Our fix deployment is taking longer than anticipated but is ongoing. We're continuing to monitor as it progresses to establish a completion timeline.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Friday, August 21, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 11:55:05 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've identified that a code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact. We're deploying a code fix to correct this issue and expect that it'll complete deployment by the time of our next update.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Start time: Monday, July 20, 2026, at 4:36 AM UTC
Root cause: A code change included in OneNote builds 16.112.717.0 and above, designed to change how authentication requests are routed, introduced an issue with OneNote iOS Authenticator broker sign-in and is causing impact.
Next update by: Tuesday, August 18, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 09:49:58 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
More info: Impact is specific to users with OneNote build 16.112.717.0 or higher.
Whilst we work on remediation, impacted users may be able to utilize OneNote on the web or remove Authenticator so that authentication falls back to the in-app webview. Users may also be able to sign in to any other Microsoft 365 apps first (e.g. PowerPoint), then attempt to sign in again in OneNote.
Current status: We've identified an issue with the OneNote iOS Authenticator broker sign-in and are working on developing and validating a fix to remediate impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Root cause: An issue with the OneNote iOS Authenticator broker sign-in is preventing users from signing in to OneNote using iOS devices.
Next update by: Friday, August 14, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 07:53:15 2026 |
|---|
| Description: | Title: Users may be unable to sign in to OneNote using iOS devices
User impact: Users may be unable to sign in to OneNote using iOS devices.
Current status: We've identified that a recent change to the sign in flow may be causing impact to occur. We've reverted the change but this did not resolve the issue. We're analyzing OneNote logs from impacted users as well as OneNote logs from our internal reproduction of the issue to assist us in identifying the underlying root cause of impact.
Scope of impact: Any user attempting to sign in to OneNote build 16.112.717.0 or higher using iOS devices is impacted.
Next update by: Friday, August 14, 2026, at 2:00 PM UTC
|
|---|
|
MO1456424 - Some users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Aug 17 08:46:14 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Aug 17 23:41:11 2026 |
|---|
| Root Cause: | A recent deployment introduced a resource utilization inefficiency issue, leading to impact. |
|---|
| Next Update: | Friday, August 21, 2026, at 4:00 AM UTC |
|---|
|
Details
| Time: | Mon Aug 17 23:41:11 2026 |
|---|
| Description: | Title: Some users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop
User impact: Users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Current status: Our investigation identified that a recent deployment introduced a resource utilization inefficiency issue, leading to impact. We've developed and are deploying a fix to reduce the resource pressure and restore service. We're monitoring as this progresses to identify a completion timeline.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop. This section may be updated as our investigation continues.
Start time: Friday, August 14, 2026, at 5:00 AM UTC
Root cause: A recent deployment introduced a resource utilization inefficiency issue, leading to impact.
Next update by: Friday, August 21, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Aug 17 10:15:32 2026 |
|---|
| Description: | Title: Some users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop
User impact: Users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Current status: We're analyzing service telemetry and reviewing recent service changes to determine the cause of impact. We've identified indicators of increased service restarts within a portion of the affected infrastructure, which may be contributing to the issue. We're validating potential remediation options while continuing our investigation into the root cause.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Next update by: Tuesday, August 18, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Aug 17 08:49:09 2026 |
|---|
| Description: | Title: Some users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop
User impact: Users may be unable to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Current status: We're reviewing service monitoring telemetry and support provided information to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users served through the affected infrastructure who are attempting to search for content in SharePoint Online, OneDrive, Outlook on the web, or Outlook desktop.
Next update by: Monday, August 17, 2026, at 3:00 PM UTC
|
|---|
|
EX1454202 - Users’ mailboxes may be set to default configurations
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 12:41:48 2026 |
|---|
| End Time: | Mon Aug 17 17:37:02 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 17 17:37:55 2026 |
|---|
| Root Cause: | A regression introduced through a worldwide modernization update to Exchange Online mailbox plan management caused customized mailbox plan and CAS mailbox plan settings to be set to default values. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 17 17:37:55 2026 |
|---|
| Description: | Title: Users’ mailboxes may be set to default configurations
User impact: Users’ mailboxes may have been set to default configurations.
More info: This communication was also published on the Message Center under MC1453151.
Please take action to confirm mailboxes created between July 21, 2026, to August 14, 2026, have the intended configurations applied.
Configurations set to default include:
- Mailbox quotas: IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota
- Transport quotas: MaxReceiveSize, MaxSendSize, RecipientLimits
- Protocol related config: ImapEnabled, PopEnabled, ActiveSyncEnabled
To identify potentially affected users, admins can use Exchange Online PowerShell with the below commands. Not all mailboxes returned may be impacted; however, we recommend reviewing mailboxes returned in the output and also those which were recently assigned licenses.
$mbxs = Get-Mailbox -Filter "WhenCreatedUTC -gt '07/21/2026 00:00:00'"
$mbxs | fl Identity, ExternalDirectoryObjectId, ProhibitSendQuota, ProhibitSendReceiveQuota, IssueWarningQuota, RecipientLimits, MaxSendSize, MaxReceiveSize
$casMbxs = Get-CasMailbox -Filter "WhenCreatedUTC -gt '07/21/2026 00:00:00'"
$casMbxs | fl Identity, ExternalDirectoryObjectId, ImapEnabled, PopEnabled, ActiveSyncEnabled
For more details on how to connect to Exchange Online PowerShell, please see: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
Final status: We completed our efforts to restore intended mailbox plan configurations; no newly created mailboxes (or users which were assigned new licenses) after August 16, 2026, are impacted. Mailboxes created during the window of impact still may not have settings applied as intended as, as we respected any changes your organization implemented post-mailbox creation, and did not reapply configurations. Your organization needs to take action to ensure the settings are configured as expected.
If your organization manually updated mailbox plans or CAS mailbox plans between July 21, 2026, to August 16, 2026, these changes were not overwritten. Any affected settings were restored to reflect the values that existed prior to the incident.
Root cause: A regression introduced through a worldwide modernization update to Exchange Online mailbox plan management caused customized mailbox plan and CAS mailbox plan settings to be set to default values.
Scope of impact: This could have impacted any mailbox that was created between July 21, 2026, to August 16, 2026.
Start time: July 21, 2026, at 12:00 PM UTC
End time: August 16, 2026, at 5:00 AM UTC
Next steps:
- We're analyzing our mailbox plan deployment methodology to ensure more rigorous testing scenarios to better detect regressions prior to rollout.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 13 12:54:29 2026 |
|---|
| Description: | Title: Users’ mailboxes may be set to default configurations
User impact: Users’ mailboxes may be set to default configurations.
More info: This communication is also published on the Message Center under MC1453151.
Please confirm mailboxes created between July 21, 2026, to August 14, 2026, have the intended configurations applied.
To find potentially affected users, use Exchange Online PowerShell with the below commands. Please note that some mailboxes returned may not be impacted; however, we recommend reviewing mailboxes returned in the output and also those which were recently assigned licenses.
$mbxs = Get-Mailbox -Filter "WhenCreatedUTC -gt '07/21/2026 00:00:00'"
$mbxs | fl Identity, ExternalDirectoryObjectId, ProhibitSendQuota, ProhibitSendReceiveQuota, IssueWarningQuota, RecipientLimits, MaxSendSize, MaxReceiveSize
$casMbxs = Get-CasMailbox -Filter "WhenCreatedUTC -gt '07/21/2026 00:00:00'"
$casMbxs | fl Identity, ExternalDirectoryObjectId, ImapEnabled, PopEnabled, ActiveSyncEnabled
For more details on how to connect to Exchange Online PowerShell, please see: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
Current status: We recently identified a scenario in which mailbox settings in the template used by admins to create new mailboxes (i.e. mailbox plans, CAS Mailbox Plans, Mailbox plans in Exchange Online (https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans)) were set to default configurations rather than what may have been customized. Configurations set to default include:
· Mailbox quotas: IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota
· Transport quotas: MaxReceiveSize, MaxSendSize, RecipientLimits
· Protocol related config: ImapEnabled, PopEnabled, ActiveSyncEnabled
We confirmed that this resulted from a regression introduced in a recent deployment and we reverted the responsible code on August 4, 2026. We’re now reapplying admins’ intended settings to the mailbox plan template so new mailboxes are created with the intended configurations moving forward. This effort is expected to be completed by Friday, August 14.
Mailboxes created during the window of impact won’t have settings applied as intended; out of respect for any changes your organization has already implemented post-mailbox creation, we are unable to reapply configurations to these mailboxes, and your organization needs to take action to ensure the settings are configured as expected.
If you updated mailbox plans for your tenant after August 7th, they will not be overwritten.
Scope of impact: This could of impact any mailbox that was created between July 21, 2026, to August 14, 2026.
Next update by: Monday, August 17, 2026, at 9:30 PM UTC
|
|---|
|
TM1456370 - Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 22 20:00:00 2026 |
|---|
| End Time: | Mon Aug 17 17:02:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 17 17:13:54 2026 |
|---|
| Root Cause: | A recent update to the reporting infrastructure led to a sync issue, resulting in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 17 17:13:44 2026 |
|---|
| Description: | Title: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
User impact: Users were experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
More info: When viewing Health reports in Microsoft Teams Rooms Pro Management Portal, the License Type column may have displayed "syncing" instead of the expected license type for affected devices. The issue may also have been present in exported reports.
As a workaround, users could have viewed accurate license information through alternate report views or by accessing the applicable room management pages within the portal.
Final status: We've completed deployment of our fix to address the offending sync issue and validated from our internal monitors that our actions successfully remediated impact. We advise users to run a new Microsoft Teams Rooms Pro Management Portal reports query to ensure the issue is remediated for them.
Scope of impact: Impact was specific to some users experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
End time: Monday, August 17, 2026, at 9:02 PM UTC
Root cause: A recent update to the reporting infrastructure led to a sync issue, resulting in this impact.
Next steps:
- We're analyzing the offending update to isolate why the potential for impact wasn't caught during our internal update testing and evaluation phases. This further analysis will help us to improve our update implementation process moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 17 16:12:55 2026 |
|---|
| Description: | Title: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
User impact: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
More info: When viewing Health reports in Microsoft Teams Rooms Pro Management Portal, the License Type column may display "syncing" instead of the expected license type for affected devices. The issue may also be present in exported reports.
As a workaround, users can view accurate license information through alternate report views or by accessing the applicable room management pages within the portal.
Current status: We identified that a recent update to the reporting infrastructure is leading to a sync issue, resulting in this impact. We've validated and deployed a fix for this issue, and we anticipate that it should be completely rolled out to all affected environments by our next scheduled update.
Scope of impact: Impact is specific to some users experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
Start time: Thursday, July 23, 2026, at 12:00 AM UTC
Root cause: A recent update to the reporting infrastructure is leading to a sync issue, resulting in this impact.
Next update by: Monday, August 17, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Aug 17 08:03:08 2026 |
|---|
| Description: | Title: Some users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
User impact: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
More info: When viewing Health reports in Microsoft Teams Rooms Pro Management Portal, the License Type column may display "syncing" instead of the expected license type for affected devices. The issue may also be present in exported reports.
As a workaround, users can view accurate license information through alternate report views or by accessing the applicable room management pages within the portal.
Current status: We're investigating inaccurate license synchronization information displayed within health reports. The issue is limited to specific health reports and doesn't affect other report types. Some room licensing information may be displayed inaccurately; however, licensing data remains available through other areas of the portal.
Scope of impact: Impact is specific to some users experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
Next update by: Monday, August 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Aug 17 06:34:21 2026 |
|---|
| Description: | Title: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports
User impact: Users are experiencing license syncing issues in Microsoft Teams Rooms Pro Management Portal reports.
More info: When viewing reports in Microsoft Teams Rooms Pro Management Portal, the License Type column may display "syncing" instead of the expected license type for affected devices. The issue may also be present in exported reports.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Your organization is affected by this event, and some users viewing device reports in the Microsoft Teams Rooms Pro Management Portal are impacted.
Next update by: Monday, August 17, 2026, at 12:30 AM UTC
|
|---|
|
TM1440450 - Users may have been unable to run run-only workflows from Microsoft Teams
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 30 03:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 17 14:40:23 2026 |
|---|
| Root Cause: | A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
|
|---|
| Next Update: | Thursday, August 20, 2026, at 8:30 PM UTC |
|---|
|
Details
| Time: | Mon Aug 17 14:40:23 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a way to avoid this issue, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We're continuing to validate the efficacy of a secondary fix designed to resolve the impact that occurs when hovering and selecting "More actions" > "Create workflows." Once a timeline for the deployment of the fix is available, we'll share it accordingly.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Thursday, August 20, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Aug 14 15:14:28 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: Our efforts to validate a secondary fix to remediate the issue in full are ongoing, and we’ll provide a resolution timeline once available.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Monday, August 17, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 14:57:15 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We’re continuing to validate a secondary fix to remediate the issue in full, and we’ll provide an update on the resolution timeline once available.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Friday, August 14, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jul 30 15:14:16 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: As a result of our initial fix deployment, users are now able to run run-only workflows through the "workflows" button in Microsoft Teams. However, running run-only workflows by hovering and selecting "More actions" > "Create workflows" is still an impacted scenario.
Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've confirmed that our initial fix has resolved this issue for running workflows through the "workflows" button in Microsoft Teams. However, less common scenarios such hovering and selecting "More actions" > "Create workflows" are still impacted. We're validating a secondary fix to address all scenarios in which workflows are run in order to fully resolve this event and will provide an update on the timeline of this final deployment by our next scheduled communication.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Thursday, August 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 20:06:22 2026 |
|---|
| Description: | Title: Users may have been unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We’re performing an extended period of monitoring the telemetry to ensure that our fix has reached all affected users.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Thursday, July 30, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 04:15:06 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've received confirmation from some affected users that the issue has been mitigated. However, our telemetry indicates that some users are still encountering errors. We're continuing to monitor the telemetry over an extended period to determine when the fix has reached all affected users and fully mitigated the impact. We'll also assess whether any additional mitigation actions are required.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running run-only workflows from Microsoft Teams.
Next update by: Thursday, July 30, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Jul 28 14:13:09 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've confirmed that the reversion has completed and are reaching out to affected users to confirm this has remediated impact.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running workflows from Microsoft Teams.
Next update by: Wednesday, July 29, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Mon Jul 27 13:41:24 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We've validated that we're able to revert the responsible change for expedient remediation as we continue to develop our long-term code fix. We anticipate that this reversion will be completed, mitigating impact, by our next scheduled update.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running workflows from Microsoft Teams.
Next update by: Tuesday, July 28, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Jul 27 08:42:37 2026 |
|---|
| Description: | Title: Users may be unable to run run-only workflows from Microsoft Teams
User impact: Users may be unable to run run-only workflows from Microsoft Teams.
More info: Affected users are unable to run workflows in Teams when those workflows are configured to be executed by designated users without requiring those users to own or edit the workflow. Users receive the following error message:
"Missing Trigger URI"
As a workaround, impacted users can be granted Owner or Co-owner permissions for the affected workflow.
Current status: We’ve determined that a recent service update inadvertently introduced a code regression that affected how Teams processes shared workflow requests, preventing some users from running workflows from Teams. We’re developing a fix and validating it before deployment to the affected environment.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, June 30, 2026, at 7:00 AM UTC
Root cause: A recent service update introduced a code regression that affects how Microsoft Teams processes shared workflow requests, preventing some users from running workflows from Microsoft Teams.
Next update by: Monday, July 27, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Jul 27 08:02:26 2026 |
|---|
| Description: | Title: All users are unable to run Microsoft Teams workflows used to create incidents internally
User impact: Users are unable to run Microsoft Teams workflows used to create incidents internally.
More info: Users receive the following error message when attempting to create incidents:
"Missing Trigger URI"
Current status: We're reviewing HTTP Archive (HAR) logs and Teams logs to help identify the root cause and next steps required to mitigate impact.
Scope of impact: Users attempting to run run-only workflows from Microsoft Teams may be impacted. This section may be updated as the investigation progresses.
Next update by: Monday, July 27, 2026, at 7:00 PM UTC
|
|---|
|
TM1452695 - Some users may have been unable to access the Share tab in Microsoft Teams on Android devices
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 10 13:30:00 2026 |
|---|
| End Time: | Thu Aug 13 14:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Aug 16 09:05:48 2026 |
|---|
| Root Cause: | A recent compliance-related service update inadvertently introduced a code defect that resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Aug 16 09:04:34 2026 |
|---|
| Description: | Title: Some users may have been unable to access the Share tab in Microsoft Teams on Android devices
User impact: Users may have been unable to access the Share tab in Microsoft Teams on Android devices.
More info: Affected users may have been unable to access sharing functionality because the Share tab was missing in Microsoft Teams on Android devices.
Final status: We’ve confirmed that reverting the offending update successfully remediated the impact.
Scope of impact: Impact was specific to some users attempting to access the Share tab in Microsoft Teams on Android devices.
Start time: Monday, August 10, 2026, at 5:30 PM UTC
End time: Thursday, August 13, 2026, at 6:30 PM UTC
Root cause: A recent compliance-related service update inadvertently introduced a code defect that resulted in impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 11 08:38:44 2026 |
|---|
| Description: | Title: Some users may be unable to access the Share tab in Microsoft Teams on Android devices
User impact: Users may be unable to access the Share tab in Microsoft Teams on Android devices.
More info: Affected users may be unable to access sharing functionality because the Share tab is missing in Microsoft Teams on Android devices.
Current status: We've begun reverting the offending change to remediate the impact. We expect this process to complete and the impact to be fully resolved by our next scheduled update.
Scope of impact: Impact is specific to some users attempting to access the Share tab in Microsoft Teams on Android devices.
Start time: Monday, August 10, 2026, at 5:30 PM UTC
Root cause: A recent compliance update introduced a code issue, resulting in a service regression and causing impact.
Next update by: Sunday, August 16, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Aug 11 07:44:41 2026 |
|---|
| Description: | Title: Some users may be unable to access the Share tab in Microsoft Teams on Android devices
User impact: Users may be unable to access the Share tab in Microsoft Teams on Android devices.
More info: Affected users may be unable to access sharing functionality because the Share tab is missing in Microsoft Teams on Android devices.
Current status: We've determined that a recent compliance update introduced a code issue, resulting in a service regression and causing impact. We're working to revert the change and remediate impact.
Scope of impact: Impact is specific to some users attempting to access the Share tab in Microsoft Teams on Android devices.
Start time: Monday, August 10, 2026, at 5:30 PM UTC
Root cause: A recent compliance update introduced a code issue, resulting in a service regression and causing impact.
Next update by: Tuesday, August 11, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Aug 11 05:47:35 2026 |
|---|
| Description: | Title: Some users may be unable to access the Share tab in Microsoft Teams on Android devices
User impact: Users may be unable to access the Share tab in Microsoft Teams on Android devices.
More info: Affected users may be unable to access sharing functionality because the Share tab is missing in Microsoft Teams on Android devices.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure, attempting to access the Share tab in Microsoft Teams on Android devices.
Next update by: Tuesday, August 11, 2026, at 12:00 PM UTC
|
|---|
|
CW1454295 - Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 13:26:00 2026 |
|---|
| End Time: | Fri Aug 14 20:30:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Aug 14 21:32:12 2026 |
|---|
| Root Cause: | A misconfiguration with the Agent Builder feature, which caused users to intermittently be unable to access Copilot Chat in Outlook on the web. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 14 21:32:12 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may have intermittently been unable to access Copilot Chat in Outlook on the web.
More info: When some users attempted to access Copilot Chat in Outlook on the web, they may have intermittently received an error that stated, "Something went wrong. An error occurred. Please try again."
Final status: Our investigation identified a misconfiguration with the Agent Builder feature, which caused users to intermittently be unable to access Copilot Chat in Outlook on the web. We disabled this configuration within the feature and confirmed with previously affected users that impact is remediated.
Scope of impact: Impact was specific to some users who attempted to access Copilot Chat in Outlook on the web.
Start time: Thursday, August 13, 2026, at 5:26 PM UTC
End time: Saturday, August 15, 2026, at 12:30 AM UTC
Root cause: A misconfiguration with the Agent Builder feature, which caused users to intermittently be unable to access Copilot Chat in Outlook on the web.
Next steps:
- To help prevent similar impact in the future, we're further reviewing the underlying cause of the misconfiguration.
This is the final update for the event.
|
|---|
|
| Time: | Fri Aug 14 19:39:11 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: Our review of service logging to identify the source of impact and determine our next steps is ongoing.
Scope of impact: Impact is specific to some users attempting to access Copilot Chat in Outlook on the web. This section may be updated as the investigation progresses.
Next update by: Saturday, August 15, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 18:01:38 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We've deployed our fix to the affected environment; however, we found that impact persists. Further review confirmed our previous root cause understanding was incorrect, and we've resumed our review of service logging to isolate the source of impact, so we can determine which mitigative actions can be implemented to restore service functionality.
Scope of impact: Impact is specific to some users attempting to access Copilot Chat in Outlook on the web. This section may be updated as the investigation progresses.
Root cause: An underlying client rendering issue within Copilot Studio is intermittently preventing Copilot Chat from rendering correctly in Outlook on the web.
Next update by: Saturday, August 15, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Aug 14 11:59:28 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We’ve deployed the fix to a subset of the affected environments and are preparing to begin deployment to the remaining affected environments. Once available, we’ll provide a deployment completion timeline.
Scope of impact: Impact is specific to some users attempting to access Copilot Chat in Outlook on the web. This section may be updated as the investigation progresses.
Root cause: An underlying client rendering issue within Copilot Studio is intermittently preventing Copilot Chat from rendering correctly in Outlook on the web.
Next update by: Friday, August 14, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 05:24:44 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We've completed validation of the fix and have started deploying it to the affected environments. As deployment progresses, we're monitoring service telemetry and error rates to verify that Copilot Chat is loading successfully for affected users. We expect deployment to complete before our next scheduled update.
Scope of impact: Impact is specific to some users attempting to access Copilot Chat in Outlook on the web.
Root cause: An underlying client rendering issue within Copilot Studio is intermittently preventing Copilot Chat from rendering correctly in Outlook on the web.
Next update by: Friday, August 14, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 01:46:29 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users may be intermittently unable to access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they may intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We've identified that additional validations of the fix are required prior to deploying the fix to the affected environments. We expect the validations will be complete and we'll aim to provide a resolution timeline by our next scheduled update.
Scope of impact: some users attempting to access Copilot Chat in Outlook on the web may be affected. This information may be updated as our investigation continues.
Root cause: An underlying client rendering issue within Copilot Studio is causing intermittent impact Copilot Chat in Outlook on the web.
Next update by: Friday, August 14, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Aug 13 21:11:20 2026 |
|---|
| Description: | Title: Some users intermittently can't access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users intermittently can't access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: After further review, we identified an underlying client rendering issue that's causing the intermittent impact. We've developed a fix for the issue and are preparing for its application to the affected environment. We'll provide available updates on the deployment timeline at the next scheduled update time.
Scope of impact: Your organization is impacted by this event, and some users attempting to access Copilot Chat in Outlook on the web are affected. This information may be updated as our investigation continues.
Root cause: An underlying client rendering issue within Copilot Studio is causing intermittent impact Copilot Chat in Outlook on the web.
Next update by: Friday, August 14, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Thu Aug 13 19:38:50 2026 |
|---|
| Description: | Title: Some users intermittently can't access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users intermittently can't access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We identified some recent changes to authentication components and we're evaluating whether those changes are contributing to the impact. If the changes are causing impact, we'll determine if they can be rolled back safely.
Scope of impact: Your organization is impacted by this event, and some users attempting to access Copilot Chat in Outlook on the web are affected. This information may be updated as our investigation continues.
Next update by: Friday, August 14, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Aug 13 17:24:16 2026 |
|---|
| Description: | Title: Some users intermittently can't access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users intermittently can't access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We're reviewing our service side logs to identify any failures or abnormalities that may indicate the source of the impact.
Scope of impact: Your organization is impacted by this event, and some users attempting to access Copilot Chat in Outlook on the web are affected. This information may be updated as our investigation continues.
Next update by: Thursday, August 13, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 16:20:30 2026 |
|---|
| Description: | Title: Some users intermittently can't access Microsoft 365 Copilot Chat in Outlook on the web
User impact: Users intermittently can't access Copilot Chat in Outlook on the web.
More info: When some users attempt to access Copilot Chat in Outlook on the web, they intermittently receive an error that states, "Something went wrong. An error occurred. Please try again."
Current status: We're reviewing the sample screenshots and errors provided by your organization to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Your organization is impacted by this event, and some users attempting to access Copilot Chat in Outlook on the web are affected. This information may be updated as our investigation continues.
Next update by: Thursday, August 13, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 16:10:30 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot Chat
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1454883 - Some users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures
| Status: | serviceRestored |
|---|
| Start Time: | Fri Aug 14 08:37:00 2026 |
|---|
| End Time: | Fri Aug 14 13:10:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Aug 14 14:23:54 2026 |
|---|
| Root Cause: | A recent feature update contains a configuration error causing inefficiencies in processing Graph API requests resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 14 14:22:08 2026 |
|---|
| Description: | Title: Some users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures
User impact: Users who utilize any Microsoft Teams application calling Microsoft Graph APIs may have encountered failures.
More info: Impacted Graph APIs included but may not have been limited to:
ActivityNotification
Get team
Final status: We've confirmed that the additional resources have remediated impact according to our service telemetry.
Scope of impact: Any user in the United States region using Microsoft Teams applications that leverage Graph API may have been affected.
Start time: Friday, August 14, 2026, at 12:37 PM UTC
End time: Friday, August 14, 2026, at 5:10 PM UTC
Root cause: A recent feature update contains a configuration error causing inefficiencies in processing Graph API requests resulted in impact.
Next steps:
- We're continuing our efforts to revert the impacting change and prevent similar impact in the future.
This is the final update for this event.
|
|---|
|
| Time: | Fri Aug 14 13:34:24 2026 |
|---|
| Description: | Title: Some users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures
User impact: Users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures.
More info: Impacted Graph APIs included but may not have been limited to:
ActivityNotification
Get team
Current status: Our investigation has identified that a recent feature update contains a configuration error causing inefficiencies in processing Graph API requests, resulting in impact. We've rebalanced load to improve GraphAPI throughput while we're working to revert the impacting change to prevent future impact.
Scope of impact: Any user in the United States region using Microsoft Teams applications that leverage Graph API may be affected.
Start time: Friday, August 14, 2026, at 12:37 PM UTC
Root cause: A recent feature update contains a configuration error causing inefficiencies in processing Graph API requests, resulting in impact.
Next update by: Friday, August 14, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 13:05:39 2026 |
|---|
| Description: | Title: Some users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures
User impact: Users who utilize any Microsoft Teams application calling Microsoft Graph APIs may encounter failures.
More info: Impacted Graph API's included but may not have been limited to:
ActivityNotification
Get team
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1454755 - Users may be unable to send email externally and may receive DNS-related errors.
| Status: | investigationSuspended |
|---|
| Start Time: | Fri Aug 14 08:00:00 2026 |
|---|
| End Time: | Fri Aug 14 10:35:53 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Aug 14 11:08:16 2026 |
|---|
| Root Cause: | A DNS-related issue within a third-party email service caused failures when processing certain externally routed email traffic.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 14 10:50:15 2026 |
|---|
| Description: | Title: Users may be unable to send email externally and may receive DNS-related errors.
User impact: Users may be unable to send email externally and may receive DNS-related errors.
More info: Users attempting to send email to external recipients may receive DNS-related errors indicating that the destination domain does not exist.
Proofpoint is providing updates through its status page: https://proofpoint.my.site.com/community/s/proofpoint-current-incidents.
The provider's communication includes a temporary workaround that affected organizations may evaluate while remediation activities continue.
Final status: We've completed our investigation and confirmed that the Microsoft-managed Exchange Online infrastructure remained healthy throughout the event. Our findings indicate that the issue was caused by a DNS-related problem within a third-party email service. Since the Microsoft 365 service remains healthy and the issue does not originate within the Microsoft-managed environment, we're closing this Service Health Dashboard communication.
Customers should continue to follow the Proofpoint status page for future updates and guidance, including temporary mitigation options provided by the third-party service.
Scope of impact: Impact is limited to organizations that route email through the affected third-party email service, Proofpoint.
Most reported impact was observed in North America, though reports were also received from additional regions.
Start time: Friday, August 14, 2026, at 12:00 PM UTC
End time: Friday, August 14, 2026, at 2:35 PM UTC
Root cause: A DNS-related issue within a third-party email service caused failures when processing certain externally routed email traffic.
This is the final update for this event.
|
|---|
|
| Time: | Fri Aug 14 10:16:12 2026 |
|---|
| Description: | Title: Users may be unable to send email externally and may receive DNS-related errors.
User impact: Users may be unable to send email externally and may receive DNS-related errors.
More info: Users may receive a DNS error, indicating the domain does not exist, when trying to send emails externally.
Proofpoint are providing updates on their status page: https://proofpoint.my.site.com/community/s/proofpoint-current-incidents
Some organizations have reported that the issue resolves once removing the third-party from their mail flow configuration.
Current status: We've identified that emails routed through a specific third-party email service are experiencing DNS-related issues. The third-party is aware of the issue and are providing updates through their status page: https://proofpoint.my.site.com/community/s/proofpoint-current-incidents
We're performing the final validations to confirm that the Microsoft-managed environment remains healthy.
Scope of impact: Impact is specific to organizations that use a specific third-party email service (Proofpoint).
The majority of reported impact is from users in North America; however, we're aware of additional reports from users in other regions and are continuing to investigate the full scope of impact.
Start time: Friday, August 14, 2026, at 12:00 PM UTC
Next update by: Friday, August 14, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 09:45:19 2026 |
|---|
| Description: | Title: Some users may experience issues with mail flow in Exchange Online
User impact: Users may experience issues with mail flow in Exchange Online.
More info: Users may receive a DNS error, indicating the domain does not exist, when trying to send emails externally.
Current status: We're continuing to analyze diagnostic data and service telemetry from email processing systems. Additionally, we're reviewing logs from affected email transactions to help isolate the source of impact.
We're also aware of reports of similar impact affecting a third-party email delivery service and are investigating whether the events are related.
Scope of impact: The majority of reported impact is from users in North America; however, we're aware of additional reports from users in other regions and are continuing to investigate the full scope of impact.
Next update by: Friday, August 14, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 09:17:57 2026 |
|---|
| Description: | Title: Some users may experience issues with mail flow in Exchange Online
User impact: Users may experience issues with mail flow in Exchange Online.
Current status: We're reviewing diagnostic data and monitoring telemetry to isolate the source of the issue.
Scope of impact: The impact is being reported by users in the North America region. We're continuing to investigate the full scope of the issue and will update this as we confirm more information.
Next update by: Friday, August 14, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Fri Aug 14 09:05:23 2026 |
|---|
| Description: | Title: Some users may experience issues with mail flow in Exchange Online
User impact: Users may experience issues with mail flow in Exchange Online.
Current status: We've received reports indicating a potential issue with mail flow in Exchange Online, and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1442253 - Users may be unable to add their personal Google or Gmail calendars in Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 24 05:16:00 2026 |
|---|
| End Time: | Fri Aug 7 07:20:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 13 16:17:31 2026 |
|---|
| Root Cause: | The URLs being utilized to issue the necessary authentication component to add Google or Gmail calendars in Outlook on the web didn't match, resulting in authentication failing.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 13 16:16:56 2026 |
|---|
| Description: | Title: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web
User impact: Users may have been unable to add their personal Google or Gmail calendars in Outlook on the web.
More info: Affected users reported that they received a blank page when attempting to add their personal Google or Gmail calendars in Outlook on the web when navigating to Settings -> Calendar -> Accounts -> Google -> Add personal calendar.
Final status: We've completed deployment of our fix to address a URL mismatch and validated both internally and with a subset of affected users that our actions successfully remediated impact.
Scope of impact: Users attempting to add their personal Google or Gmail calendars in Outlook on the web may have been impacted.
Start time: Tuesday, February 24, 2026, at 10:16 AM UTC
End time: Friday, August 7, 2026, at 11:20 AM UTC
Root cause: The URLs being utilized to issue the necessary authentication component to add Google or Gmail calendars in Outlook on the web didn't match, resulting in authentication failing.
Next steps:
- We're validating how the URL mismatch was first introduced into our service to further our understanding of the impact scenario and to confirm 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 Aug 5 19:09:33 2026 |
|---|
| Description: | Title: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web
User impact: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web.
More info: Affected users may report that they receive a blank page when attempting to add their personal Google or Gmail calendars in Outlook on the web when navigating to Settings -> Calendar -> Accounts -> Google -> Add personal calendar.
Current status: We can confirm that our fix has been deployed and has saturated 30 percent of the affected environment. We'll continue to monitor as the fix progresses to ensure the impact is fully remediated.
Scope of impact: Users attempting to add their personal Google or Gmail calendars in Outlook on the web may be impacted. This section may be updated as our investigation progresses.
Start time: Tuesday, February 24, 2026, at 10:16 AM UTC
Root cause: The URLs being utilized to issue the necessary authentication component to add Google or Gmail calendars in Outlook on the web don't match, resulting in authentication failing.
Next update by: Thursday, August 13, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 16:19:16 2026 |
|---|
| Description: | Title: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web
User impact: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web.
More info: Affected users may report that they receive a blank page when attempting to add their personal Google or Gmail calendars in Outlook on the web when navigating to Settings -> Calendar -> Accounts -> Google -> Add personal calendar.
Current status: After analyzing provided HAR files and screenshots of impact, we've isolated that the URLs being utilized to issue the necessary authentication component to add Google or Gmail calendars in Outlook on the web don't match, resulting in authentication failing. We're developing a fix to remediate the mismatch and we aim to provide a timeline to remediation in our next scheduled update.
Scope of impact: Users attempting to add their personal Google or Gmail calendars in Outlook on the web may be impacted. This section may be updated as our investigation progresses.
Start time: Tuesday, February 24, 2026, at 10:16 AM UTC
Root cause: The URLs being utilized to issue the necessary authentication component to add Google or Gmail calendars in Outlook on the web don't match, resulting in authentication failing.
Next update by: Thursday, August 13, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 13:20:34 2026 |
|---|
| Description: | Title: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web
User impact: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web.
More info: Affected users may report that they receive a blank page when attempting to add their personal Google or Gmail calendars in Outlook on the web when navigating to Settings -> Calendar -> Accounts -> Google -> Add personal calendar.
Current status: We're continuing our analysis of HAR logs and screenshots of impact from affected users to further investigate this issue and determine our next troubleshooting steps.
Scope of impact: Users attempting to add their personal Google or Gmail calendars in Outlook on the web may be impacted. This section may be updated as our investigation progresses.
Next update by: Wednesday, July 29, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 11:35:28 2026 |
|---|
| Description: | Title: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web
User impact: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web.
More info: Affected users may report that they receive a blank page when attempting to add their personal Google or Gmail calendars in Outlook on the web when navigating to Settings -> Calendar -> Accounts -> Google -> Add personal calendar.
Current status: We're reviewing support provided data from affected users, including HTTP Archive format (HAR) logs and screenshots of impact, to investigate into this issue's root cause.
Scope of impact: Users attempting to add their personal Google or Gmail calendars in Outlook on the web may be impacted. This section may be updated as our investigation progresses.
Next update by: Wednesday, July 29, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 11:09:17 2026 |
|---|
| Description: | Title: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web
User impact: Users may be unable to add their personal Google or Gmail calendars in Outlook on the web.
Current status: We're investigating a potential issue impacting Exchange Online in which users can't add personal Google or Gmail Calendars in Outlook on the web. We're checking for impact to your organization and will provide an update in approximately 30 minutes.
|
|---|
|
EX1442215 - Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Feb 13 19:48:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 13 15:05:59 2026 |
|---|
| Root Cause: | A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
|
|---|
| Next Update: | Monday, August 24, 2026, at 9:00 PM UTC |
|---|
|
Details
| Time: | Thu Aug 13 15:04:43 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Current status: We're coordinating with a subset of affected admins who are in the process of completing a cross-tenant mailbox migration to monitor progress, which will help us validate remediation for all impacted admins.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Monday, August 24, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 12 10:47:06 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Current status: We're awaiting feedback from a subset of affected admins to validate if our fix successfully remediated impact.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Thursday, August 13, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 12 08:57:36 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Current status: We've validated and deployed the fix across the affected infrastructure, enabling the mailbox move to complete successfully. During validation, we've identified that the affected folder was processed as a folder creation bad item and therefore could not be migrated intact. We're validating the overall outcome with the affected users to confirm full mitigation.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Wednesday, August 12, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Aug 12 08:57:27 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Admins may be able to run the following PowerShell cmdlets sequentially for migration batches:
Set-MigrationBatch batchname -SkipMoving FolderRestrictions
Start-MigrationBatch "BatchName"
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online receive the following error
"PropTagToPropertyDefinitionConversionException"
Current status: We've validated and deployed the fix across the affected infrastructure, enabling the mailbox move to complete successfully. During validation, we identified that the affected folder was processed as a folder creation bad item and therefore could not be migrated intact. We're validating the overall outcome with the affected users and continuing to monitor the environment to ensure the mitigation remains effective.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be affected. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Wednesday, August 12, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 10:25:30 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may be able to use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may have resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This would allow the affected move jobs to continue to make progress.
Admins may be able to run the following PowerShell cmdlets sequentially for migration batches:
Set-MigrationBatch batchname -SkipMoving FolderRestrictions
Start-MigrationBatch "BatchName"
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online receive the following error
"PropTagToPropertyDefinitionConversionException"
Current status: We've received reports that impact associated with EX1232513 persists. We've resumed our investigation of the issue and have developed and are validating a fix to remediate impact.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be affected. This information may be updated as our investigation continues.
Start time: Saturday, February 14, 2026, at 12:48 AM UTC
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which is causing intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Wednesday, August 12, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 09:32:01 2026 |
|---|
| Description: | Title: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online
User impact: Admins are unable to complete some cross-tenant mailbox migrations in Exchange Online.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and admins attempting to complete some cross-tenant mailbox migrations in Exchange Online are impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, July 29, 2026, at 3:30 PM UTC
|
|---|
|
CP1454166 - Some users hosted in Europe may be unable to log into Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 11:13:00 2026 |
|---|
| End Time: | Thu Aug 13 12:38:33 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 13 14:12:29 2026 |
|---|
| Root Cause: | A recent configuration change to the login service may have prevented users hosted in Europe from logging into Copilot.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 13 13:00:38 2026 |
|---|
| Description: | Title: Some users hosted in Europe may be unable to log into Microsoft 365 Copilot
User impact: Users may have been unable to log into Copilot.
Final status: We've monitored the affected environment using our internal telemetry and confirmed that reverting the configuration change has remediated the impact.
Scope of impact: Any user hosted in Europe that attempted to log into Copilot may have been impacted.
Start time: Thursday, August 13, 2026, at 5:50 AM UTC
End time: Thursday, August 13, 2026, at 3:20 PM UTC
Root cause: A recent configuration change to the login service may have prevented users hosted in Europe from logging into Copilot.
Next steps: - We're reviewing and improving our configuration change validation procedure to prevent similar login issues in the future.
This is the final update for this event.
|
|---|
|
| Time: | Thu Aug 13 11:57:53 2026 |
|---|
| Description: | Title: Some users hosted in Europe may be unable to log into Microsoft 365 Copilot
User impact: Users may be unable to log into Copilot.
Current status: We identified a recent configuration change to the login service that may be contributing to the impact. We've reverted this change and are monitoring to confirm if impact is remediated.
Scope of impact: Any user hosted in Europe attempting to log into Copilot may be impacted.
Next update by: Thursday, August 13, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 11:26: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 impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1454079 - Some users may be unable to access the Copilot services in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 13 07:10:00 2026 |
|---|
| End Time: | Thu Aug 13 12:19:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 13 13:58:04 2026 |
|---|
| Root Cause: | Excessive resource consumption disrupted request processing within a portion of the API management infrastructure supporting Microsoft Fabric, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 13 13:56:48 2026 |
|---|
| Description: | Title: Some users may be unable to access the Copilot services in Microsoft Fabric
User impact: Users may have been unable to access Copilot services in Microsoft Fabric.
More info: Additionally, users may have experienced issues accessing Machine Learning (ML) experiments and models.
Final status: We've identified that excessive resource consumption disrupted request processing within a portion of the API management infrastructure supporting Microsoft Fabric, resulting in impact. We optimized the scaling configuration for the affected infrastructure and after monitoring the service, we've verified that this action restored service functionality successfully.
Scope of impact: Some users in North America and Asia-Pacific regions attempting to interact with Copilot services or access ML experiments and models in Microsoft Fabric may have been impacted.
Start time: Thursday, August 13, 2026, at 11:10 AM UTC
End time: Thursday, August 13, 2026, at 4:19 PM UTC
Root cause: Excessive resource consumption disrupted request processing within a portion of the API management infrastructure supporting Microsoft Fabric, resulting in impact.
Next steps: We're investigating the sources of excessive resource consumption to prevent this problem from happening again in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 13 10:54:51 2026 |
|---|
| Description: | Title: Some users may be unable to access the Copilot services in Microsoft Fabric
User impact: Users may be unable to access the Copilot services in Microsoft Fabric.
More info: Additionally, users may experience issues accessing Machine Learning (ML) experiments and models.
Current status: We're progressing with our root cause analysis and recent service update review, as we isolate the source for this event and determine our next steps for remediating the impact.
Scope of impact: Some users in North America and Asia-Pacific regions attempting to interact with Copilot services or access ML experiments and models in Microsoft Fabric may be impacted.
Start time: Thursday, August 13, 2026, at 11:10 AM UTC
Next update by: Thursday, August 13, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Aug 13 09:36:28 2026 |
|---|
| Description: | Title: Some users may be unable to access the Copilot services in Microsoft Fabric
User impact: Users may be unable to access the Copilot services in Microsoft Fabric.
More info: Additionally, users may experience issues accessing Machine Learning (ML) experiments and models.
Current status: We're continuing to analyze diagnostic data from the affected Microsoft Fabric workloads to isolate the source of impact. In parallel, we're reviewing recent service changes and deployments to determine whether they may be contributing to the issue.
Scope of impact: Some users in North America and Asia-Pacific regions attempting to interact with Copilot services or access ML experiments and models in Microsoft Fabric may be impacted.
Start time: Thursday, August 13, 2026, at 11:10 AM UTC
Next update by: Thursday, August 13, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Aug 13 08:28:07 2026 |
|---|
| Description: | Title: Some users may be unable to access the Copilot services in Microsoft Fabric
User impact: Users may be unable to access the Copilot services in Microsoft Fabric.
More info: Additionally, users may experience issues accessing Machine Learning (ML) experiments and models.
Current status: We’re reviewing service telemetry and diagnostic data from the affected Microsoft Fabric workloads to identify the source of impact and determine the most appropriate mitigation strategy.
Scope of impact: Some users in North America and Asia-Pacific regions attempting to interact with Copilot services or access ML experiments and models in Microsoft Fabric may be impacted.
Start time: Thursday, August 13, 2026, at 11:10 AM UTC
Next update by: Thursday, August 13, 2026, at 2:30 PM UTC
|
|---|
|
TM1451939 - Users' locations may not be accurate during iOS Microsoft Teams emergency calls
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Aug 10 08:44:26 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 13 10:28:13 2026 |
|---|
| Root Cause: | Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
|
|---|
| Next Update: | Wednesday, August 19, 2026, at 3:00 PM UTC |
|---|
|
Details
| Time: | Thu Aug 13 10:28:13 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're progressing with our efforts to validate a suitable fix in our test environment, although this is taking longer than initially anticipated. We're carrying out tests to ensure that the fix doesn't present any further issues and further clarify confirmation of the root cause.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Wednesday, August 19, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Aug 12 13:42:02 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing the validation process for our fix, and we'll aim to provide a timeline for it to complete by our next scheduled communications update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Thursday, August 13, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue Aug 11 14:55:33 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: The development of the fix is taking longer than initially expected. We'll provide an updated timeline once one is available.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application. This information may be updated as our investigation continues.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Wednesday, August 12, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 08:49:31 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We're continuing to develop a fix in our internal environment to remediate impact and restore location data functionality. We expect this to be ready to be deployed by our next scheduled update.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application.
Root cause: Changes to iOS API infrastructure has resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Tuesday, August 11, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Aug 10 08:52:01 2026 |
|---|
| Description: | Title: Users' locations may not be accurate during iOS Microsoft Teams emergency calls
User impact: Users' locations may not be accurate during iOS Microsoft Teams emergency calls.
More info: Affected users are still able to make iOS emergency calls but their location may be inaccurate to the responder. This is specific to users on iOS version 26 and newer.
Current status: We've identified that changes to iOS API infrastructure has inadvertently resulted in user location data to become inaccurate during iOS emergency calls. We're developing a fix in our internal environment to remediate impact and restore location data functionality.
Scope of impact: Impact is specific to any user on iOS 26 or newer making emergency calls using the Microsoft Teams application.
Root cause: Changes to iOS API infrastructure has inadvertently resulted in user location data to become inaccurate during iOS emergency calls.
Next update by: Tuesday, August 11, 2026, at 1:00 PM UTC
|
|---|
|
TM1453882 - Admins may have seen that information in the Auto attendant tab wasn't populating results in the Teams Admin Center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 10 20:00:00 2026 |
|---|
| End Time: | Thu Aug 13 04:54:42 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 13 05:18:44 2026 |
|---|
| Root Cause: | A recent deployment introduced a configuration issue that was preventing Auto attendant from working as expected in the TAC and Microsoft Teams.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 13 05:18:40 2026 |
|---|
| Description: | Title: Admins may have seen that information in the Auto attendant tab wasn't populating results in the Teams Admin Center
User impact: Admins may have seen that information in the Auto attendant tab wasn't populating results in the TAC.
More info: Impacted admins may have seen the following error message in the TAC when clicking the Auto attendant tab, "We can't load the voice app assignment. Some fields may appear empty".
Additionally, the Auto Attendant call forwarding functionality in Microsoft Teams may have not been working as expected. Also, admins may have been unable to use PowerShell to manage Auto attendants.
Final status: The deployment of the fix has completed successfully, and we've received confirmation from affected users that the issue is resolved.
Scope of impact: Some admins that were attempting to access Auto attendants in the TAC or Microsoft Teams may have been impacted.
Start time: Tuesday, August 11, 2026, at 12:00 AM UTC
End time: Thursday, August 13, 2026, at 5:00 AM UTC
Root cause: A recent deployment introduced a configuration issue that was preventing Auto attendant from working as expected in the TAC and Microsoft Teams.
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 Aug 13 01:22:26 2026 |
|---|
| Description: | Title: Admins may see that information in the Auto attendant tab isn't populating results in the Teams Admin Center (TAC)
User impact: Admins may see that information in the Auto attendant tab isn't populating results in the TAC.
More info: Impacted admins may see the following error message in the TAC when clicking the Auto attendant tab, "We can't load the voice app assignment. Some fields may appear empty".
Additionally, the Auto Attendant call forwarding functionality in Microsoft Teams may not be working as expected. Also, admins may be unable to use PowerShell to manage Auto attendants.
Current status: We're monitoring the progression of the deployment, and we anticipate the deployment will be complete and the issue resolved by our next scheduled update.
Scope of impact: Some admins that are attempting to access Auto attendants in the TAC or Microsoft Teams may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, August 11, 2026, at 12:00 AM UTC
Root cause: A recent deployment introduced a configuration issue that's preventing Auto attendant from working as expected in the TAC and Microsoft Teams.
Next update by: Thursday, August 13, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Aug 13 00:07:03 2026 |
|---|
| Description: | Title: Admins may see that information in the Auto attendant tab isn't populating results in the Teams Admin Center (TAC)
User impact: Admins may see that information in the Auto attendant tab isn't populating results in the TAC.
More info: Impacted admins may see the following error message in the TAC when clicking the Auto attendant tab, "We can't load the voice app assignment. Some fields may appear empty".
Additionally, the Auto Attendant call forwarding functionality in Microsoft Teams may not be working as expected. Also, admins may be unable to use PowerShell to manage Auto attendants.
Current status: We've received reports of an issue in which admins may see that information in the Auto attendants tab isn't populating results in the TAC. We've identified that a recent deployment introduced a configuration issue that's preventing Auto attendant from working as expected in the TAC and Microsoft Teams. We've developed and validated a fix that's currently being deployed to the affected environment, and we'll aim to provide a resolution timeline by our next scheduled update.
Scope of impact: Some admins that are attempting to access Auto attendants in the TAC or Microsoft Teams may be impacted. This information may be updated as our investigation continues.
Start time: Tuesday, August 11, 2026, at 12:00 AM UTC
Root cause: A recent deployment introduced a configuration issue that's preventing Auto attendant from working as expected in the TAC and Microsoft Teams.
Next update by: Thursday, August 13, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Wed Aug 12 23:40:29 2026 |
|---|
| Description: | Title: Admins may see that Auto Attendant is not visible in the Teams Admin Center (TAC)
User impact: Admins may see that Auto Attendant is not visible in the TAC.
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.
|
|---|
|
MO1452280 - Some admins may see Copilot Adoption and Copilot Readiness report delays in multiple Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Sun Aug 9 20:00:00 2026 |
|---|
| End Time: | Wed Aug 12 20:39:44 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 12 20:41:16 2026 |
|---|
| Root Cause: | The data pipelines utilized to process and provide affected reporting data was operating in a degraded state due to an ongoing migration to move upstream service infrastructure. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 12 20:39:49 2026 |
|---|
| Description: | Title: Some admins may see Copilot Adoption and Copilot Readiness report delays in multiple Microsoft 365 services
User impact: Admins may have seen Copilot Adoption and Copilot Readiness report delays in multiple Microsoft 365 services.
More info: Admins saw reporting data in both Microsoft Viva Insights and the Microsoft 365 admin center was delayed starting from Thursday, August 6, 2026.
Final Status: We've completed processing the delayed Copilot Adoption and Copilot Readiness reports, and we've confirmed with monitoring internal telemetry that the issue is resolved.
Scope of impact: Some admins may have seen delays for Copilot Adoption and Copilot Readiness reports in Viva Insights and the Microsoft 365 admin center starting from Thursday, August 6, 2026.
Start time: Monday, August 10, 2026, at 12:00 AM UTC
End time: Wednesday, August 12, 2026, at 10:30 PM UTC
Root cause: The data pipelines utilized to process and provide affected reporting data was operating in a degraded state due to an ongoing migration to move upstream service infrastructure.
Next steps:
- We're further reviewing the data pipelines to identify how we can implement improvements to ensure the issue doesn't reoccur with future migrations.
This is the final update for the event.
|
|---|
|
| Time: | Wed Aug 12 12:39:38 2026 |
|---|
| Description: | Title: Some admins may see Copilot Adoption and Copilot Readiness report delays in multiple Microsoft 365 services
User impact: Admins may see Copilot Adoption and Copilot Readiness report delays in multiple Microsoft 365 services.
More info: Admins see reporting data in both Microsoft Viva Insights and the Microsoft 365 admin center is delayed starting from Thursday, August 6, 2026.
Current status: Processing of delayed Copilot Adoption and Copilot Readiness reports has pushed our timeline to remediation back to Thursday, August 13, 2026, at 12:00 AM UTC. We apologize for the delay and we're validating what additional actions we can take to expedite recovery.
Scope of impact: Some admins may see delays for Copilot Adoption and Copilot Readiness reports in Viva Insights and the Microsoft 365 admin center starting from Thursday, August 6, 2026. This section may be updated as the investigation progresses.
Start time: Monday, August 10, 2026, at 12:00 AM UTC
Estimated time to resolve: We anticipate impact to be resolved by Thursday, August 13, 2026, at 12:00 AM UTC.
Root cause: The data pipelines utilized to process and provide affected reporting data is operating in a degraded state due to an ongoing migration to move upstream service infrastructure.
Next update by: Thursday, August 13, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Aug 11 17:21:53 2026 |
|---|
| Description: | Title: Some admins may see Copilot Adoption and Copilot Readiness report delays in multiple Microsoft 365 services
User impact: Admins may see Copilot Adoption and Copilot Readiness report delays in multiple Microsoft 365 services.
More info: Admins see reporting data in both Microsoft Viva Insights and the Microsoft 365 admin center is delayed starting from Thursday, August 6, 2026.
Current status: We've completed implementation of our configuration changes to address the degraded data pipelines and are processing delayed Copilot Adoption and Copilot Readiness reports. We anticipate impact to be resolved by our next scheduled update.
Scope of impact: Some admins may see delays for Copilot Adoption and Copilot Readiness reports in Viva Insights and the Microsoft 365 admin center starting from Thursday, August 6, 2026. This section may be updated as the investigation progresses.
Start time: Monday, August 10, 2026, at 12:00 AM UTC
Estimated time to resolve: We anticipate impact to be resolved by Wednesday, August 12, 2026, at 6:00 PM UTC.
Root cause: The data pipelines utilized to process and provide affected reporting data is operating in a degraded state due to an ongoing migration to move upstream service infrastructure.
Next update by: Wednesday, August 12, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Aug 10 16:42:39 2026 |
|---|
| Description: | Title: Some admins may see Copilot Adoption and Copilot Readiness report delays in Viva Insights and Microsoft 365 admin center
User impact: Admins may see Copilot Adoption and Copilot Readiness report delays in Viva Insights and Microsoft 365 admin center.
More info: Admins will see reporting data is delayed starting from Thursday, August 6, 2026.
Current status: Our service monitors have alerted us to ongoing delays for Copilot Adoption and Copilot Readiness reports in Viva Insights and the M365 admin center. We've isolated that the data pipelines utilized to process and provide affected reporting data is operating in a degraded state due to an ongoing migration to move upstream service infrastructure. We're working to implement configuration changes to remediate the degradation and we aim to provide a timeline to remediation as soon as possible.
Scope of impact: Some admins may see delays for Copilot Adoption and Copilot Readiness reports in Viva Insights and the Microsoft 365 admin center starting from Thursday, August 6, 2026. This section may be updated as the investigation progresses.
Start time: Monday, August 10, 2026, at 12:00 AM UTC
Root cause: The data pipelines utilized to process and provide affected reporting data is operating in a degraded state due to an ongoing migration to move upstream service infrastructure.
Next update by: Tuesday, August 11, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Aug 10 16:16:47 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.
|
|---|
|
TM1452993 - Some users may be unable to generate Microsoft Teams meeting attendance reports
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 10 12:00:00 2026 |
|---|
| End Time: | Wed Aug 12 16:15:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 12 20:36:30 2026 |
|---|
| Root Cause: | A recent first-party app rollout introduced a misconfiguration that caused app component calls to fail, which had resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 12 20:36:30 2026 |
|---|
| Description: | Title: Some users may be unable to generate Microsoft Teams meeting attendance reports
User impact: Users may have been unable to generate Microsoft Teams meeting attendance reports.
More info: The affected meeting attendance reports were being generated internally, but due to the impact scenario, they weren't being provided to the user who requested it.
Final status: We’ve completed regenerating reports for the remaining users and confirmed with our service telemetry that the issue is fully resolved.
Scope of impact: Some users attempting to generate Microsoft Teams meeting attendance reports may have been affected by this event.
Start time: Monday, August 10, 2026, at 4:00 PM UTC
End time: Wednesday, August 12, 2026, at 8:15 PM UTC
Root cause: A recent first-party app rollout introduced a misconfiguration that caused app component calls to fail, which had resulted in impact.
Next steps:
-We're investigating the impacting first-party app to pinpoint why this impact wasn't caught prior to rolling it out so that we can prevent the inability to generate Microsoft Teams meeting attendance reports in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 11 21:35:46 2026 |
|---|
| Description: | Title: Some users may experience failures when generating Microsoft Teams meeting attendance reports
User impact: Users may experience failures when generating Microsoft Teams meeting attendance reports.
More info: The affected meeting attendance reports are being generated internally, but due to the impact scenario, they're not being provided to the user who requested it.
Current status: We've regenerated reports for users in the Europe region. We anticipate that the reports for all remaining users will be regenerated by the time of our next scheduled communication update.
Scope of impact: Some users may experience failures generating Microsoft Teams meeting attendance reports. This section may be updated as the investigation progresses.
Start time: Monday, August 10, 2026, at 4:00 PM UTC
Root cause: A recent first-party app rollout introduced a misconfiguration that caused app component calls to fail, resulting in impact.
Next update by: Thursday, August 13, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Aug 11 17:03:26 2026 |
|---|
| Description: | Title: Some users may experience failures when generating Microsoft Teams meeting attendance reports
User impact: Users may experience failures when generating Microsoft Teams meeting attendance reports.
More info: The affected meeting attendance reports are being generated internally, but due to the impact scenario, they're not being provided to the user who requested it.
Current status: We anticipate missing meeting attendance reports to be fully processed for users in Europe by our next scheduled communications update. We're validating the timeline to restore reports for remaining affected regions and aim to provide this timeline in our next scheduled update.
Scope of impact: Some users may experience failures generating Microsoft Teams meeting attendance reports. This section may be updated as the investigation progresses.
Start time: Monday, August 10, 2026, at 4:00 PM UTC
Root cause: A recent first-party app rollout introduced a misconfiguration that caused app component calls to fail, resulting in impact.
Next update by: Wednesday, August 12, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Aug 11 16:04:40 2026 |
|---|
| Description: | Title: Some users may experience failures when generating Microsoft Teams meeting attendance reports
User impact: Users may experience failures when generating Microsoft Teams meeting attendance reports.
More info: The affected meeting attendance reports are being generated internally, but due to the impact scenario, they're not being provided to the user who requested it.
Current status: After implementing additional performance optimizations, we've validated that meeting attendance report availability has recovered. We're processing meeting attendance reports that were affected by this incident to fully remediate impact.
Scope of impact: Some users may experience failures generating Microsoft Teams meeting attendance reports. This section may be updated as the investigation progresses.
Start time: Monday, August 10, 2026, at 4:00 PM UTC
Root cause: A recent first-party app rollout introduced a misconfiguration that caused app component calls to fail, resulting in impact.
Next update by: Tuesday, August 11, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 14:31:01 2026 |
|---|
| Description: | Title: Some users may experience failures when generating Microsoft Teams meeting attendance reports
User impact: Users may experience failures when generating Microsoft Teams meeting attendance reports.
More info: The affected meeting attendance reports are being generated internally, but due to the impact scenario, they're not being provided to the user who requested it.
Current status: As we continue to implement additional performance optimizations to recover meeting attendance report availability, we can confirm that availability is trending upwards but not fully recovered at this time. We're continuing to monitor availability as we validate what additional actions we can take to remediate impact.
Scope of impact: Some users may experience failures generating Microsoft Teams meeting attendance reports. This section may be updated as the investigation progresses.
Start time: Monday, August 10, 2026, at 4:00 PM UTC
Root cause: A recent first-party app rollout introduced a misconfiguration that caused app component calls to fail, resulting in impact.
Next update by: Tuesday, August 11, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 14:09:29 2026 |
|---|
| Description: | Title: Some users may experience failures when generating Microsoft Teams meeting attendance reports
User impact: Users may experience failures when generating Microsoft Teams meeting attendance reports.
More info: The affected meeting attendance reports are being generated internally, but due to the impact scenario, they're not being provided to the user who requested it.
Current status: Our service monitors alerted us to ongoing impact to a subset of users who are experiencing failures when generating Microsoft Teams meeting attendance reports. We've isolated that a recent first-party app rollout introduced a misconfiguration that caused app component calls to fail, resulting in impact. We've rolled back the offending update and are monitoring service availability while we implement additional performance optimizations to fully remediate impact.
Scope of impact: Some users may experience failures generating Microsoft Teams meeting attendance reports. This section may be updated as the investigation progresses.
Start time: Monday, August 10, 2026, at 4:00 PM UTC
Root cause: A recent first-party app rollout introduced a misconfiguration that caused app component calls to fail, resulting in impact.
Next update by: Tuesday, August 11, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 13:53:24 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Teams
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.
|
|---|
|
MO1453783 - We've detected a Microsoft 365 groups issue within your tenant
| Status: | investigating |
|---|
| Start Time: | Wed Aug 12 18:15:13 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 12 18:21:53 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 12 18:21:53 2026 |
|---|
| Description: | Title: We've detected a Microsoft 365 groups issue within your tenant
User impact: If action is not taken, users may see a duplicate "All Company" Microsoft 365 group in multiple Microsoft 365 services.
Our systems detected a recent service update, intended to fix an unrelated issue, that may have caused an unexpected duplicate Microsoft 365 group named "All Company" to be created within your organization, which would appear in Microsoft Entra ID, SharePoint Online, Microsoft Planner, and Microsoft OneNote. The impacting service update has been reverted and didn’t affect the original "All Company" group or its content. While no new duplicate "All Company" groups are being created with the offending service update reverted, any duplicate "All Company" groups that were created during the impact period of Friday, July 3, 2026, to Wednesday, July 8, 2026, may still exist within your environment. If action is not taken, users may see a duplicate "All Company" Microsoft 365 group in multiple Microsoft 365 services.
This communication will expire in seven days, and is scheduled to remain active for the full duration.
|
|---|
|
CP1447275 - Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Aug 4 10:47:20 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 12 14:19:06 2026 |
|---|
| Root Cause: | The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
|
|---|
| Next Update: | Wednesday, August 19, 2026, at 7:30 PM UTC |
|---|
|
Details
| Time: | Wed Aug 12 14:18:59 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We’ve developed and validated the fix to correct the URL redirection and have initiated deployment to the affected environments. Based on our current estimates, we suspect that the deployment will take several weeks to complete, with completion expected by Monday, August 31, 2026. We’re continuing to monitor the progress of the deployment and will provide progress updates as they become available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
Next update by: Wednesday, August 19, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 14:11:35 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We’re continuing to develop a fix to correct the URL redirection, and we’ll provide a resolution timeline once available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
Next update by: Wednesday, August 12, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 13:46:03 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We've identified that the "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact. We're developing a fix to correct the URL redirection and will provide an update on its timeline as one becomes available.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Root cause: The "Open" button for the Analyst or Researcher agents in the Microsoft 365 app store contains the incorrect URL redirection and is causing impact.
Next update by: Tuesday, August 11, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 12:25:59 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We're continuing to review the details provided by a subset of affected users, including screenshots of the impact, so that we can investigate the source of the impact.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
|
|---|
|
| Time: | Tue Aug 4 11:04:09 2026 |
|---|
| Description: | Title: Users' Microsoft 365 Copilot Analyst and Researcher agents may open a new chat window instead of the agents
User impact: Users' Copilot Analyst and Researcher agents may open a new chat window when opened from app store.
More info: When users attempt to open Copilot Analyst or Researcher from the Microsoft 365 app store, it may open a new chat window instead of the agents. While we work on correcting this issue, users may be able to open the Analyst or Researcher agents from the Copilot agent store.
Current status: We're reviewing the screenshots provided by a subset of affected users to gain further understanding of the impact and to determine the next steps to isolate the root cause.
Scope of impact: Any user attempting to open Copilot Analyst or Researcher from the Microsoft 365 app store may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, August 4, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 10:51:04 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1441488 - Some users may see unwanted add-ins appearing automatically across all Outlook clients
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jul 17 06:26:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 12 13:29:56 2026 |
|---|
| Root Cause: | A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
|
|---|
| Next Update: | Wednesday, August 19, 2026, at 6:30 PM UTC |
|---|
|
Details
| Time: | Wed Aug 12 13:29:56 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We’re continuing to monitor the progress of the fix to ensure it propagates successfully. We still suspect this will complete by Wednesday, August 26, 2026, and we’ll provide further updates as they become available.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Wednesday, August 19, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Aug 11 13:39:36 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We’ve developed and begun deploying the fix to the affected environments. We’re monitoring its progress to ensure it propagates successfully, and based on our current estimates, we expect deployment to complete by Wednesday, August 26, 2026. We’ll provide further resolution updates as they become available.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Wednesday, August 12, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Aug 10 12:54:57 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're developing a fix aimed at correcting the affected portion of Exchange Online add-in sync pipeline that’s resulting in impact, and we’ll provide a timeline for its validation and deployment as one becomes available.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in sync pipeline isn't processing add-in state information as expected. This is causing incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available, which is resulting in impact.
Next update by: Tuesday, August 11, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Aug 6 12:42:27 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We've identified that a portion of the Exchange Online add-in synchronization pipeline isn't processing add-in state information as expected, resulting in incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available. We're continuing to validate with a subset of affected users whether removing and re-adding an add-in or deploying a test add-in to force synchronization can serve as a viable workaround while our investigation into the underlying cause continues in effort to isolate the source of the issue and identify an appropriate remediation action.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Start time: Friday, July 17, 2026, at 10:26 AM UTC
Root cause: A portion of the Exchange Online add-in synchronization pipeline isn't processing add-in state information as expected, resulting in incorrect EnabledStatus values being returned and Outlook automatically displaying add-ins configured as Available.
Next update by: Monday, August 10, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Aug 5 15:21:21 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're continuing to validate with a subset of affected users whether removing and re-adding an add-in or deploying a test add-in to force sync can serve as a viable workaround while the root cause investigation remains ongoing.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Thursday, August 6, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 15:57:10 2026 |
|---|
| Description: | Title: Users see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We successfully reproduced the issue internally and found that triggering an add-in sync caused the unwanted add-ins to disappear. We are currently validating, with a subset of affected users, whether removing and re-adding an add-in or deploying a test add-in to force sync can serve as a viable workaround while the root cause investigation remains ongoing.
Scope of impact: Your organization is affected by this event, and all users see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Wednesday, August 5, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Aug 3 13:37:54 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're continuing our efforts to reproduce impact within our internal testing environment while reviewing HAR logs alongside any recent updates that may be causing or contributing to impact, to isolate this issue's underlying cause.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Tuesday, August 4, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Jul 31 13:54:55 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We received feedback from a subset of affected users that the potential temporary remediation was insufficient. We're continuing to review provided HAR logs while we reproduce the impact using our internal testing tenant to gain further understanding of the issue.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Monday, August 3, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jul 30 18:05:58 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We've identified a potential temporary remediation while we work towards long-term resolution. We're reaching out to validate this temporary remediation with a portion of the impacted users to determine if it will be an effective solution.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Friday, July 31, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jul 30 13:22:14 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're reviewing newly collected HAR logs provided by a subset of affected users to aid us in our root cause investigation. In the meantime, we're developing a short term mitigation plan to provide relief while our investigation is ongoing.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Thursday, July 30, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 16:17:19 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: Our investigation of the conflicting add-in configurations is ongoing, and we're reaching out to your representatives for additional contextual data and fresh HTTP Archive (HAR) files collected from both Outlook desktop and Outlook on the web clients for further analysis.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Thursday, July 30, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 13:24:56 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're continuing to analyze conflicting add-in configurations which may be contributing to impact along with our continued analysis of relevant recent changes to the affected configurations to isolate the underlying source of impact.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Wednesday, July 29, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jul 28 17:33:47 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We've identified conflicting add-in configurations which may be contributing to impact. We're expanding our investigation into recent relevant changes to the configurations to confirm the root cause.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Wednesday, July 29, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jul 28 12:00:13 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're analyzing the properties being utilized to display add-ins for an affected user along with our continued analysis of the HAR file to isolate potential sources of impact.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Tuesday, July 28, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jul 28 11:29:32 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're analyzing HTTP Archive format (HAR) traces provided by your representatives and reviewing support cases to further our understanding of the current impact scenario and to assist with determining our next troubleshooting steps.
Scope of impact: Impact may occur for some users that may see unwanted add-ins appearing automatically across all Outlook clients. This section may be updated as the investigation progresses.
Next update by: Tuesday, July 28, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Jul 28 11:15:49 2026 |
|---|
| Description: | Title: Some users may see unwanted add-ins appearing automatically across all Outlook clients
User impact: Users may see unwanted add-ins appearing automatically across all Outlook clients.
More info: These add-ins are configured to be available to users by admins but aren’t expected to be automatically installed.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1437780 - Some users may be unable to join or create Microsoft Teams meetings or calls
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 20:25:00 2026 |
|---|
| End Time: | Thu Jul 23 21:27:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Aug 12 11:27:51 2026 |
|---|
| Root Cause: | The incident was triggered during the rollback of a Cosmos DB configuration designed to help limit the impact of failures and prevent wider service disruptions in one of the Teams services. As part of a precautionary investigation into a potential issue with this configuration, the feature was disabled in the APAC region. During the rollback, a subset of data partitions experienced a temporary service inconsistency for approximately 23 minutes, which resulted in intermittent request failures.
As dependent services and client applications attempted to recover from these failures, request volumes increased significantly and created an unexpected surge in traffic across several platform services. The elevated traffic levels placed substantial pressure on service infrastructure, leading to broader service degradation and impacting some calling and meeting scenarios.
The issue gradually self-resolved as platform scaling and traffic-management mechanisms automatically adjusted to absorb the increased demand. While service was restored without additional customer action, there are follow-up repair items to further strengthen resilience and reduce the likelihood of similar incidents in the future. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 31 17:46:55 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 30 19:15:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jul 27 18:36:11 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 23 23:08:49 2026 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings or calls
User impact: Users may have been unable to join or create Microsoft Teams meetings or calls.
More info: According to our impact analysis, the following scenarios were among those most impacted:
-Recordings and Transcriptions
-1:1 Calling
-Group calling
-Meeting join
-Meeting scheduling and creation
-Public switched telephone network (PSTN) calls
Final status: After a recursive analysis of additional metrics, we've observed persistent recovery across all previously affected scenarios. Closer analysis identified a recent change associated with our ongoing service resilience efforts which overloaded our traffic management processes and caused impact. The service is now restored; however, users whose calls and meetings were previously affected may need to end and restart those calls and meetings to see full recovery.
Scope of impact: Any Microsoft Teams users in the Asia-Pacific region may have been impacted when attempting to create or join meetings or calls.
Start time: Friday, July 24, 2026, at 12:25 AM UTC
End time: Friday, July 24, 2026, at 1:27 AM UTC
Root cause: The incident was triggered during the rollback of a Cosmos DB configuration designed to help limit the impact of failures and prevent wider service disruptions in one of the Teams services. As part of a precautionary investigation into a potential issue with this configuration, the feature was disabled in the APAC region. During the rollback, a subset of data partitions experienced a temporary service inconsistency for approximately 23 minutes, which resulted in intermittent request failures.
As dependent services and client applications attempted to recover from these failures, request volumes increased significantly and created an unexpected surge in traffic across several platform services. The elevated traffic levels placed substantial pressure on service infrastructure, leading to broader service degradation and impacting some calling and meeting scenarios.
The issue gradually self-resolved as platform scaling and traffic-management mechanisms automatically adjusted to absorb the increased demand. While service was restored without additional customer action, there are follow-up repair items to further strengthen resilience and reduce the likelihood of similar incidents in the future.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Review document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Jul 23 21:59:17 2026 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings or calls
User impact: Users may be unable to join or create Microsoft Teams meetings or calls.
More info: According to our initial impact analysis, the following scenarios are among those most impacted:
-Transcriptions
-1:1 Calling
-Group calling
-Meeting join
-Meeting scheduling and creation
-Public switched telephone network (PSTN) calls
Current status: Our telemetry affirms that the impacted scenarios are nearly recovered. In parallel, we're recursively reviewing the health of the overall service environment, including dependent networking components, to better understand the cause and determine whether any mitigation actions are required to ensure the service remains healthy and available to users. In the interim, users' calls and meetings which were previously affected may need to be ended and restarted to see recovery.
Scope of impact: Any Microsoft Teams users in the Asia-Pacific region may be impacted when attempting to create or join meetings or calls. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:25 AM UTC
Next update by: Friday, July 24, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Jul 23 21:39:49 2026 |
|---|
| Description: | While we're observing recovery across a majority of affected scenarios, we're closely analyzing the service telemetry to isolate the source of the issue and ensure withstanding recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jul 23 21:26:59 2026 |
|---|
| Description: | Title: Some users may be unable to join or create Microsoft Teams meetings or calls
User impact: Users may be unable to join or create Microsoft Teams meetings or calls.
More info: According to our initial impact analysis, the following scenarios are among those most impacted:
-Transcriptions
-1:1 Calling
-Group calling
-Meeting join
-Meeting scheduling and creation
-Public switched telephone network (PSTN) calls
Current status: We're investigating a potential networking issue which we suspect is associated with the impact, and we're working to identify the most expeditious mitigation approach.
Scope of impact: Any Microsoft Teams users may be impacted when attempting to create or join meetings or calls.
Next update by: Friday, July 24, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Jul 23 21:02:55 2026 |
|---|
| Description: | Title: We're investigating a potential issue with Microsoft Teams
User impact: Users are reporting issues joining Microsoft Teams meetings.
Current status: We're investigating a potential issue which is preventing users from joining Microsoft Teams meetings and/or is causing disconnections, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1453149 - Admins may see incorrect Teams membership information for users in the Teams Admin Center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Aug 11 19:14:25 2026 |
|---|
| End Time: | Tue Aug 11 21:28:17 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 11 21:33:44 2026 |
|---|
| Root Cause: | A code issue contained in a recent service update caused the display of incorrect Teams membership information in the Teams Admin Center.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 11 21:33:41 2026 |
|---|
| Description: | Title: Admins may see incorrect Teams membership information for users in the Teams Admin Center
User impact: Admins may have seen incorrect Teams membership information for users in the Teams Admin Center.
Final status: We reverted the recent service update containing the code issue and confirmed through telemetry that the impact was remediated.
Scope of impact: This issue may have impacted any admins viewing Teams membership information for users in the Teams Admin Center.
Start time: Monday, July 13, 2026, at 9:09 PM UTC
End time: Wednesday, August 12, 2026, at 1:00 AM UTC
Root cause: A code issue contained in a recent service update caused the display of incorrect Teams membership information in the Teams Admin Center.
Next steps: We're working to improve our code review procedures to better prevent similar issues from occurring during future service update deployments.
This is the final update for this event.
|
|---|
|
| Time: | Tue Aug 11 20:01:07 2026 |
|---|
| Description: | Title: Admins may see incorrect Teams membership information for users in the Teams Admin Center
User impact: Admins may see incorrect Teams membership information for users in the Teams Admin Center.
Current status: We identified that a code issue in a recent service update is causing the display of incorrect Teams membership information. We're working to revert the code changes to remediate the impact.
Scope of impact: This issue may impact any admins viewing Teams membership information for users in the Teams Admin Center.
Root cause: A code issue contained in a recent service update is causing the display of incorrect Teams membership information in the Teams Admin Center.
Next update by: Wednesday, August 12, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Aug 11 19:22:42 2026 |
|---|
| Description: | Title: Admins may see incorrect Teams membership information for users in the Teams Admin Center
User impact: Admins may see incorrect Teams membership information for users in the Teams Admin Center.
Current status: We're investigating a potential issue with the Microsoft Teams service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1452166 - Some users may be unable to access apps on newly enrolled devices in Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 23 20:00:00 2026 |
|---|
| End Time: | Tue Aug 11 20:45:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 11 21:28:47 2026 |
|---|
| Root Cause: | A code issue was preventing a background process from applying group assignments to newly enrolled devices, which was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 11 21:28:47 2026 |
|---|
| Description: | Title: Some users may be unable to access apps on newly enrolled devices in Microsoft Intune
User impact: Users may have been unable to access apps on newly enrolled devices in Microsoft Intune.
More info: This issue affected new device enrollments which used Enrollment Time Grouping (ETG) in Microsoft Intune. Affected devices weren't being added to the appropriate group after enrollment, which prevented assigned apps from being installed.
Final status: We’ve addressed the aforementioned deployment problem and confirmed our fix deployment completed. Subsequently we validated that impact has been fully resolved for all affected users.
Scope of impact: Some users who enrolled new devices with ETG in Microsoft Intune may have been impacted.
Start time: Friday, July 24, 2026, at 12:00 AM UTC
End time: Wednesday, August 12, 2026, at 12:45 AM UTC
Root cause: A code issue was preventing a background process from applying group assignments to newly enrolled devices, which was resulting in impact.
Next steps:
- We’re continuing to analyze how the code issue manifested, as 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 Intune users.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 11 16:12:58 2026 |
|---|
| Description: | Title: Some users may be unable to access apps on newly enrolled devices in Microsoft Intune
User impact: Users may be unable to access apps on newly enrolled devices in Microsoft Intune.
More info: This issue affects new device enrollments using Enrollment Time Grouping (ETG) in Microsoft Intune. Affected devices aren't being added to the appropriate group after enrollment, preventing assigned apps from being installed.
Current status: We've isolated a deployment issue that's preventing our solution from being deployed to a small subset of affected users. While a majority of users are no longer experiencing this issue, we're addressing the deployment problem and expect an updated timeline for impact being remediated will be available by our next scheduled communication update.
Scope of impact: Some users enrolling new devices with ETG in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:00 AM UTC
Root cause: A code issue is preventing a background process from applying group assignments to newly enrolled devices, which is resulting in impact.
Next update by: Wednesday, August 12, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Aug 11 12:35:12 2026 |
|---|
| Description: | Title: Some users may be unable to access apps on newly enrolled devices in Microsoft Intune
User impact: Users may be unable to access apps on newly enrolled devices in Microsoft Intune.
More info: This issue affects new device enrollments using Enrollment Time Grouping (ETG) in Microsoft Intune. Affected devices aren't being added to the appropriate group after enrollment, preventing assigned apps from being installed.
Current status: We've confirmed that this issue has been remediated for most users, and we expect the deployment to complete, remediating impact for the remaining users, by the next scheduled update.
Scope of impact: Some users enrolling new devices with ETG in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:00 AM UTC
Root cause: A code issue is preventing a background process from applying group assignments to newly enrolled devices, which is resulting in impact.
Next update by: Tuesday, August 11, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Aug 11 03:54:33 2026 |
|---|
| Description: | Title: Some users may be unable to access apps on newly enrolled devices in Microsoft Intune
User impact: Users may be unable to access apps on newly enrolled devices in Microsoft Intune.
More info: This issue affects new device enrollments using Enrollment Time Grouping (ETG) in Microsoft Intune. Affected devices aren't being added to the appropriate group after enrollment, preventing assigned apps from being installed.
Current status: We're continuing to deploy and validate our fix across affected environments. While deployment has completed successfully in most environments, a small number require an additional deployment and validation cycle, which is taking longer than initially anticipated. We're closely monitoring progress and anticipate that the fix will be fully deployed, and the issue resolved, by our next scheduled update.
Scope of impact: Some users enrolling new devices with ETG in Microsoft Intune may be impacted. This section may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:00 AM UTC
Estimated time to resolve: Tuesday, August 11, 2026
Root cause: A code issue is preventing a background process from applying group assignments to newly enrolled devices, which is resulting in impact.
Next update by: Tuesday, August 11, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Aug 10 21:18:38 2026 |
|---|
| Description: | Title: New devices enrolled with Enrollment Time Grouping (ETG) in Microsoft Intune may encounter issues
User impact: New devices enrolled with ETG in Microsoft Intune may encounter issues.
More info: This issue specifically affects new device enrollments using ETG where the background job has failed already. The newly enrolled devices will then not be added to the appropriate effective group.
Current status: Our code fix deployment is still in progress and taking more time than initially expected. We’re continuing to monitor its progress to ensure it completes to resolve this issue as expected.
Scope of impact: New devices enrolled with ETG in Microsoft Intune aren’t added to the appropriate group. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:00 AM UTC
Root cause: An identified code issue supporting background jobs has been identified as the cause of this event.
Next update by: Tuesday, August 11, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Mon Aug 10 17:17:26 2026 |
|---|
| Description: | Title: New devices enrolled with Enrollment Time Grouping (ETG) in Microsoft Intune may encounter issues
User impact: New devices enrolled with ETG in Microsoft Intune may encounter issues.
More info: This issue specifically affects new device enrollments using ETG where the background job has failed already. The newly enrolled devices will then not be added to the appropriate effective group.
Current status: The code fix to address the failed background jobs is progressing incrementally through the affected environment, and we anticipate the deployment will complete by the time of our next scheduled update.
Scope of impact: New devices enrolled with ETG in Microsoft Intune aren’t added to the appropriate group. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:00 AM UTC
Root cause: An identified code issue supporting background jobs has been identified as the cause of this event.
Next update by: Tuesday, August 11, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Aug 10 14:24:23 2026 |
|---|
| Description: | Title: New devices enrolled with Enrollment Time Grouping (ETG) in Microsoft Intune may encounter issues
User impact: New devices enrolled with Enrollment Time Grouping (ETG) in Intune may encounter issues.
More info: This issue specifically affects new device enrollments using ETG where the background job has failed already. The newly enrolled devices will then not be added to the appropriate effective group.
Current status: We're continuing to roll out the fix to affected areas. Since the fix is being deployed incrementally, mitigation may be noticed as devices start to be assigned to the appropriate effective group.
Scope of impact: New devices enrolled with Enrollment Time Grouping (ETG) in Intune will not be added to the appropriate group. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:00 AM UTC
Root cause: An identified code issue supporting background jobs has been identified as the cause of this event.
Next update by: Monday, August 10, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Aug 10 13:15:08 2026 |
|---|
| Description: | Title: New devices enrolled with Enrollment Time Grouping (ETG) in Microsoft Intune may encounter issues
User impact: New devices enrolled with Enrollment Time Grouping (ETG) in Intune may encounter issues.
More info: This issue specifically affects new device enrollments using ETG where the background job has failed already. The newly enrolled devices will then not be added to the appropriate effective group.
Current status: We're deploying a code fix to address the failed background jobs. Once the fix has fully deployed to all affected areas, no additional action will be required and the devices will automatically be applied to the appropriate effective group.
Scope of impact: New devices enrolled with Enrollment Time Grouping (ETG) in Intune will not be added to the appropriate group. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 12:00 AM UTC
Root cause: An identified code issue supporting background jobs has been identified as the cause of this event.
Next update by: Monday, August 10, 2026, at 7:30 PM UTC
|
|---|
|
MF1453005 - Users intermittently can't utilize the Microsoft Dataverse connector for Microsoft Power Automate flows
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 10 22:00:00 2026 |
|---|
| End Time: | Tue Aug 11 12:15:00 2026 |
|---|
| Service: | Microsoft Power Automate in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 11 14:38:21 2026 |
|---|
| Root Cause: | A subset of Power Automate dependency service’s infrastructure was experiencing high resource utilization, intermittently preventing users from utilizing the Microsoft Dataverse connector for Microsoft Power Automate flows.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 11 14:37:21 2026 |
|---|
| Description: | Title: Users intermittently can't utilize the Microsoft Dataverse connector for Microsoft Power Automate flows
User impact: Users intermittently couldn't utilize the Microsoft Dataverse connector for Microsoft Power Automate flows.
Final status: We've determined that a subset of Power Automate dependency service’s infrastructure had experienced high resource utilization, which dropped performance levels below manageable service performance thresholds, degrading performances for flows. After conducting configuration changes to alleviate isolated capacity constraints, our internal service health diagnostics verified that flows were functioning as expected and that the impact had been remediated.
Scope of impact: Your organization was affected by this event, and all users were intermittently unable to utilize Microsoft Dataverse connector for Microsoft Power Automate flows.
Start time: Tuesday, August 11, 2026, at 2:00 AM UTC
End time: Tuesday, August 11, 2026, at 4:15 PM UTC
Root cause: A subset of Power Automate dependency service’s infrastructure was experiencing high resource utilization, intermittently preventing users from utilizing the Microsoft Dataverse connector for Microsoft Power Automate flows.
Next steps:
- We're further anlyzing the dependency service's subset of affected infrastructure to help us prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 11 14:09:45 2026 |
|---|
| Description: | Title: Users intermittently can't utilize the Microsoft Dataverse connector for Microsoft Power Automate flows
User impact: Users intermittently couldn't utilize the Microsoft Dataverse connector for Microsoft Power Automate flows.
Current status: We've investigated a problem with the Microsoft Power Automate service in which users were unable to utilize the Microsoft Dataverse connector for Microsoft Power Automate flows, 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.
|
|---|
|
FL1452952 - Flows that utilize the Microsoft Dataverse connector were intermittently failing
| Status: | serviceRestored |
|---|
| Start Time: | Mon Aug 10 22:00:00 2026 |
|---|
| End Time: | Tue Aug 11 12:15:00 2026 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Aug 11 13:25:18 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 11 13:25:18 2026 |
|---|
| Description: | Title: Flows that utilize the Microsoft Dataverse connector were intermittently failing
User impact: Flows that utilize the Microsoft Dataverse connector were intermittently failing.
Final Status: We identified that a portion of our dependency service’s infrastructure was experiencing high resource utilization, resulting in degraded performance for flows that utilize the Microsoft Dataverse connector. We performed configuration changes to alleviate our capacity constraints and confirmed via service health diagnostics that flows are functioning as expected.
This is the final update on the incident.
Preliminary Root Cause: A portion of our dependency service’s infrastructure was experiencing high resource utilization.
Next Steps: We’re reviewing our code for improved performance and potential automated recovery options to reduce or avoid similar issues in the future.
|
|---|
|
TM1448287 - Users may be unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 29 00:36:00 2026 |
|---|
| End Time: | Mon Aug 10 16:10:04 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 10 16:11:26 2026 |
|---|
| Root Cause: | A recent deployment of a feature change introduced a code conflict, which resulted in users being unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 10 16:11:23 2026 |
|---|
| Description: | Title: Users may be unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls
User impact: Users may have been unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls.
More info: Impacted users may have done any of the following as a temporary alternative:
- Stop window sharing, click "Back" on the share tray, and then resume sharing
- Leave the Town Hall and rejoin
- Use the "share screen" feature instead of the "share window" feature, which wouldn’t display the share tray
Final status: We've verified that our code fix has fully deployed into the impacted environment and all users are now able to close the share tray through any method in Microsoft Teams town halls.
Scope of impact: Any user who used the "Share window" feature in Microsoft Teams town halls may have been affected and may have been unable to close the share tray feature while window sharing.
Start time: Monday, June 29, 2026, at 4:36 AM UTC
End time: Monday, August 10, 2026, at 8:10 PM UTC
Root cause: A recent deployment of a feature change introduced a code conflict, which resulted in users being unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls.
Next steps: - We're continuing to optimize our code development and testing procedures to ensure pre-emptive remediation of potential code conflicts prior to deployment to users.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 6 05:47:55 2026 |
|---|
| Description: | Title: Users may be unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls
User impact: Users may be unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls.
More info: While we work towards full remediation, impacted users may do any of the following as a temporary alternative:
- Stop window sharing, click "Back" on the share tray, and then resume sharing
- Leave the Town Hall and rejoin
- Use the "Share screen" feature instead of the "Share window" feature, which will not display the share tray
Current status: We're continuing the deployment of the aforementioned code change fix to resolve impact. We'll monitor the deployment of this fix and share a timeline for completion once one becomes available.
Scope of impact: Any user who uses the "Share window" feature in Microsoft Teams Town Halls may be affected and may be unable to close the share tray feature while window sharing. This section may be updated as our investigation continues.
Root cause: A recent deployment of a feature change introduced a code conflict, which resulted in users being unable to close the share tray when using the "Share window" feature in Microsoft Teams Town Halls.
Next update by: Monday, August 10, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Aug 5 19:43:25 2026 |
|---|
| Description: | Title: Users may be unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls
User impact: Users may be unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls.
More info: While we work towards full remediation, impacted users may do any of the following as a temporary alternative:
- Stop window sharing, click "Back" on the share tray, and then resume sharing
- Leave the Town Hall and rejoin
- Use the "Share screen" feature instead of the "Share window" feature, which will not display the share tray
Current status: We've successfully developed and initiated the deployment of a code change fix to resolve impact. We'll monitor the deployment of this fix and share a timeline for completion once one becomes available.
Scope of impact: Any user who uses the "Share window" feature in Microsoft Teams Town Halls may be affected and may be unable to close the share tray feature while window sharing. This section may be updated as our investigation continues.
Root cause: A recent deployment of a feature change introduced a code conflict, which resulted in users being unable to close the share tray when using the "Share window" feature in Microsoft Teams Town Halls.
Next update by: Thursday, August 6, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Aug 5 14:51:23 2026 |
|---|
| Description: | Title: Users may be unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls
User impact: Users may be unable to close the share tray when using the "Share window" feature in Microsoft Teams town halls.
More info: While we work towards full remediation, impacted users may do any of the following as a temporary alternative:
- Stop window sharing, click "Back" on the share tray, and then resume sharing
- Leave the Town Hall and rejoin
- Use the "Share screen" feature instead of the "Share window" feature, which will not display the share tray
Current status: We've identified a recent feature change in an ongoing deployment which is responsible for this issue. We're in the process of developing and deploying a code change which we expect will resolve this issue.
Scope of impact: Any user who uses the "Share window" feature in Microsoft Teams Town Halls may be affected and may be unable to close the share tray feature while window sharing. This section may be updated as our investigation continues.
Root cause: A recent deployment of a feature change introduced a code conflict, which resulted in users being unable to close the share tray when using the "Share window" feature in Microsoft Teams Town Halls.
|
|---|
|
PB1451187 - Users may be unable to refresh some Power BI dataflows
| Status: | serviceRestored |
|---|
| Start Time: | Sun Aug 2 00:00:00 2026 |
|---|
| End Time: | Sun Aug 9 19:21:32 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Aug 9 19:22:05 2026 |
|---|
| Root Cause: | A recent service update designed to improve Power BI service monitoring and observability introduced a regression that was preventing some Gen1 dataflow refresh operations from completing successfully. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Aug 9 19:21:36 2026 |
|---|
| Description: | Title: Users may be unable to refresh some Power BI dataflows
User impact: Users may have been unable to refresh some Power BI dataflows.
More info: Affected users saw that their refresh operations remained stuck in an "In Progress" state. This issue impacted a subset of Power BI dataflows (Gen1).
Final status: We've completed deploying the fix to the remaining impacted environment, and we've validated with internal monitoring that the issue is resolved.
Scope of impact: Users that attempted to refresh some Power BI (Gen1) dataflows may have been impacted.
Start time: Sunday, August 2, 2026, at 4:00 AM UTC
End time: Sunday, August 9, 2026, at 10:56 PM UTC
Root cause: A recent service update designed to improve Power BI service monitoring and observability introduced a regression that was preventing some Gen1 dataflow refresh operations from completing successfully.
Next Steps:
- We're further reviewing the service update to understand how the regression was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Sun Aug 9 17:18:25 2026 |
|---|
| Description: | Title: Users may be unable to refresh some Power BI dataflows
User impact: Users may be unable to refresh some Power BI dataflows.
More info: Affected users see that their refresh operations remain stuck in an "In Progress" state. This issue impacts a subset of Power BI dataflows (Gen1).
Current status: The application of our fix to the remaining impacted environments is taking longer than anticipated. We'll provide a timeline for the completion of our mitigations once it has become available.
Scope of impact: Users attempting to refresh some Power BI (Gen1) dataflows may be impacted.
Start time: Sunday, August 2, 2026, at 4:00 AM UTC
Root cause: A recent service update designed to improve Power BI service monitoring and observability introduced a regression that’s preventing some Gen1 dataflow refresh operations from completing successfully.
Next update by: Monday, August 10, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Sun Aug 9 15:13:50 2026 |
|---|
| Description: | Title: Users may be unable to refresh some Power BI dataflows
User impact: Users may be unable to refresh some Power BI dataflows.
More info: Affected users see that their refresh operations remain stuck in an "In Progress" state. This issue impacts a subset of Power BI dataflows (Gen1).
Current status: We're continuing to make progress in applying the fix on the remaining portion of impacted environments.
Scope of impact: Users attempting to refresh some Power BI (Gen1) dataflows may be impacted.
Start time: Sunday, August 2, 2026, at 4:00 AM UTC
Root cause: A recent service update designed to improve Power BI service monitoring and observability introduced a regression that’s preventing some Gen1 dataflow refresh operations from completing successfully.
Next update by: Sunday, August 9, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Sun Aug 9 11:30:42 2026 |
|---|
| Description: | Title: Users may be unable to refresh some Power BI dataflows
User impact: Users may be unable to refresh some Power BI dataflows.
More info: Affected users see that their refresh operations remain stuck in an "In Progress" state. This issue impacts a subset of Power BI dataflows (Gen1).
Current status: We applied the fix in approximately half of the affected environment, and our service telemetry monitoring has verified that it's addressing the introduced code regression and remediating the impact. We'll provide an updated timeline for the completion of our fix deployment once it’s available.
Scope of impact: Users attempting to refresh some Power BI (Gen1) dataflows may be impacted.
Start time: Sunday, August 2, 2026, at 4:00 AM UTC
Root cause: A recent service update designed to improve Power BI service monitoring and observability introduced a regression that’s preventing some Gen1 dataflow refresh operations from completing successfully.
Next update by: Sunday, August 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Sun Aug 9 06:05:09 2026 |
|---|
| Description: | Title: Users may be unable to refresh some Power BI dataflows
User impact: Users may be unable to refresh some Power BI dataflows.
More info: Affected users see that their refresh operations remain stuck in an "In Progress" state. This issue impacts a subset of Power BI dataflows (Gen1).
Current status: We’ve determined that a recent service update designed to improve Power BI service monitoring and observability inadvertently introduced a regression that is preventing some Gen1 dataflow refresh operations from completing successfully. We’ve implemented a fix to mitigate the impact and have received confirmation from a subset of affected users that it successfully restores dataflow refresh operations. We’re continuing to apply the fix across affected environments while monitoring service telemetry to confirm recovery.
Scope of impact: Users attempting to refresh some Power BI (Gen1) dataflows may be impacted.
Start time: Sunday, August 2, 2026, at 4:00 AM UTC
Root cause: A recent service update designed to improve Power BI service monitoring and observability inadvertently introduced a regression that is preventing some Gen1 dataflow refresh operations from completing successfully.
Next update by: Sunday, August 9, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Sun Aug 9 04:30:01 2026 |
|---|
| Description: | Title: Users are unable to refresh some Power BI dataflows
User impact: Users are unable to refresh some Power BI dataflows.
More info: Affected users see that their refresh operations remain stuck in an "In Progress" state. This issue impacts a subset of Power BI dataflows (Gen1).
Current status: We've identified that a recent service update designed to improve Power BI service monitoring and observability may be contributing to the issue. We're evaluating mitigation options to restore affected dataflow refresh operations while continuing to validate the root cause.
Scope of impact: Your organization is affected by this event, and users attempting to refresh some Power BI (Gen1) dataflows are impacted. This section may be updated as our investigation continues.
Next update by: Sunday, August 9, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Aug 9 02:08:51 2026 |
|---|
| Description: | Title: Users are unable to refresh Gen1 dataflows in Power BI
User impact: Users are unable to refresh Gen1 dataflows in Power BI.
More info: Affected users see that their refresh operations remain stuck in an "In Progress" state.
Current status: We've received support cases indicating that users are unable to refresh Gen1 dataflows in Power BI. We're reviewing the support case details along with any recent service changes to isolate the root cause of the issue and identify our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and users attempting to refresh Gen1 dataflows in Power BI are impacted. This section may be updated as our investigation continues.
Next update by: Sunday, August 9, 2026, at 8:30 AM UTC
|
|---|
|
EX1449203 - Users may be unable to access their mailbox with any Exchange Online connection method
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 6 19:00:00 2026 |
|---|
| End Time: | Fri Aug 7 19:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Aug 7 22:53:57 2026 |
|---|
| Root Cause: | A networking issue on the portion of affected infrastructure that services Exchange Online connectivity was leading to inefficient performance and impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 7 22:53:11 2026 |
|---|
| Description: | Title: Users may be unable to access their mailbox with any Exchange Online connection method
User impact: Users may have been unable to access their mailbox with any Exchange Online connection method.
Final status: Following the completion of the infrastructure restarts and a subsequent period of monitoring the service health telemetry, we’ve confirmed that impact was remediated.
Scope of impact: This event may have affected users who attempted to access their mailboxes with any connection method in the North America region.
Start time: Thursday, August 6, 2026, at 11:00 PM UTC
End time: Friday, August 7, 2026, at 3:00 PM UTC
Root cause: A networking issue on the portion of affected infrastructure that services Exchange Online connectivity was leading to inefficient performance and impact.
Next steps:
- We’re reviewing the affected infrastructure for possible improvements to avoid similar instances in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Aug 7 15:48:01 2026 |
|---|
| Description: | Title: Users may be unable to access their mailbox with any Exchange Online connection method
User impact: Users may be unable to access their mailbox with any Exchange Online connection method.
Current status: We’ve paused the infrastructure restarts and configuration deployment while we evaluate an alternate mitigation to remove the affected network filter without requiring additional restarts.
Scope of impact: This event may affect users who attempt to access their mailboxes with any connection method in the North America region. This section may be updated as our investigation continues.
Root cause: A networking issue on the portion of affected infrastructure that services Exchange Online connectivity is leading to inefficient performance and impact.
Next update by: Saturday, August 8, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Fri Aug 7 09:58:35 2026 |
|---|
| Description: | Title: Users may be unable to access their mailbox with any Exchange Online connection method
User impact: Users may be unable to access their mailbox with any Exchange Online connection method.
Current status: Work continues on the required restarts across all affected environments and we're deploying the configuration change to address the regions still experiencing impact as an additional mitigation step.
Scope of impact: This event may affect users who attempt to access their mailboxes with any connection method in the North America region. This section may be updated as our investigation continues.
Root cause: A networking issue on the portion of affected infrastructure that services Exchange Online connectivity is leading to inefficient performance and impact.
Next update by: Friday, August 7, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Aug 7 05:24:57 2026 |
|---|
| Description: | Title: Users may be unable to access their mailbox with any Exchange Online connection method
User impact: Users may be unable to access their mailbox with any Exchange Online connection method.
Current status: Our efforts to complete the required restarts across all affected environments is progressing. We're also validating and testing a possible configuration change in our test environment to address the regions still experiencing impact as an additional mitigation step.
Scope of impact: This event may affect users who attempt to access their mailboxes with any connection method in the North America region. This section may be updated as our investigation continues.
Root cause: A networking issue on the portion of affected infrastructure that services Exchange Online connectivity is leading to inefficient performance and impact.
Next update by: Friday, August 7, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Fri Aug 7 00:10:48 2026 |
|---|
| Description: | Title: Users may be unable to access their mailbox with any Exchange Online connection method
User impact: Users may be unable to access their mailbox with any Exchange Online connection method.
Current status: We're still working to complete the required restarts across all affected environments. So far, we've seen positive results from our review of the service telemetry logs indicating that our actions are working as intended. In addition, we've identified a networking issue on the portion of affected infrastructure that services Exchange Online connectivity, which we believe is leading to impact. We're assessing whether additional actions need to be taken in addition to our current actions to fully remediate impact.
Scope of impact: This event may affect users who attempt to access their mailboxes with any connection method in the North America region. This section may be updated as our investigation continues.
Root cause: A networking issue on the portion of affected infrastructure that services Exchange Online connectivity is leading to inefficient performance and impact.
Next update by: Friday, August 7, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Aug 6 22:28:27 2026 |
|---|
| Description: | Title: Users may be unable to access their mailbox with any Exchange Online connection method
User impact: Users may be unable to access their mailbox with any Exchange Online connection method.
Current status: We've observed recovery for some affected portions of infrastructure; however, we're still seeing impact for infrastructure in the North America region. We're continuing to analyze our service health telemetry logs to help pinpoint the underlying cause of impact. We're also attempting to restart certain portions of infrastructure still affected to assess whether this resolves impact.
Scope of impact: This event may affect users who attempt to access their mailboxes with any connection method in the North America region. This section may be updated as our investigation continues.
Next update by: Friday, August 7, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Aug 6 20:44:16 2026 |
|---|
| Description: | Title: Users may be unable to access their mailbox with any Exchange Online connection method
User impact: Users may be unable to access their mailbox with any Exchange Online connection method.
Current status: We've determined that affected users are unable to access their Exchange Online mailbox with any connection method. During our analysis of the affected infrastructure, we observed recovery after our automated recovery systems moved traffic to healthier infrastructure to repair the issue. We're continuing to monitor the recovery to ensure that impact has been fully remediated, while in parallel, we're working to better understand the root cause of the drop in service availability.
Scope of impact: This event may affect users who attempt to access their mailboxes with any connection method in the North America region. This section may be updated as our investigation continues.
Next update by: Friday, August 7, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Aug 6 19:54:53 2026 |
|---|
| Description: | Title: Investigating user reports of Exchange Online issues
User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.
|
|---|
|
CP1449264 - Some users may encounter intermittent failures with an error when sending prompts in Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 6 21:40:43 2026 |
|---|
| End Time: | Fri Aug 7 02:06:59 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Aug 7 02:17:54 2026 |
|---|
| Root Cause: | A recent change intended to improve how Copilot requests were routed unexpectedly sent some requests through an incompatible service path, resulting in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Aug 7 02:17:50 2026 |
|---|
| Description: | Title: Some users may encounter intermittent failures with an error when sending prompts in Microsoft 365 Copilot
User impact: Users may have encountered intermittent failures with an error when sending prompts in Copilot Chat in Web mode.
More info: This issue intermittently affected a subset of licensed Copilot users attempting to send prompts through Copilot Chat in a web browser while the “Web” content toggle was enabled. Affected users may have received a “Sorry, something went wrong” error when submitting messages and prompts.
Affected users could’ve used the “Work” tab in Copilot Chat to avoid the impact.
Final status: We completed the rollback of the affected update and confirmed through service telemetry that the issue is resolved. Affected users may need to refresh Copilot Chat to experience impact remediation.
Scope of impact: Some users with Copilot licenses encountered errors when attempting to send prompts through Copilot Chat while the “Web” content toggle was enabled.
Start time: Wednesday, August 5, 2026, at 12:13 PM UTC
End time: Friday, August 7, 2026, at 5:30 AM UTC
Root cause: A recent change intended to improve how Copilot requests were routed unexpectedly sent some requests through an incompatible service path, resulting in the impact.
Next steps: - We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Aug 7 00:28:37 2026 |
|---|
| Description: | Title: Some users may encounter intermittent failures with an error when sending prompts in Microsoft 365 Copilot
User impact: Users may encounter intermittent failures with an error when sending prompts in Copilot Chat in Web mode.
More info: This issue intermittently impacts a subset of licensed Copilot users attempting to send prompts through Copilot Chat in the web browser while the "Web" content toggle is enabled, and affected users may receive a “Sorry, something went wrong” error when submitting Copilot Chat messages and prompts.
While we're focused on remediation, affected users can utilize the "Work" tab when using Copilot Chat to avoid potential impact.
Current status: We’ve determined that a recent change intended to improve how Copilot requests are routed unexpectedly sent some requests through an incompatible service path, resulting in the impact. We’ve initiated the process of reverting the offending change and we’re monitoring to ensure that we’re seeing the expected signs of improvement to service health.
Scope of impact: Some users with Copilot licenses may encounter failures with an error when attempting to send prompts in Copilot Chat while the "Web" content toggle is enabled. This information may be updated as our investigation continues.
Start time: Wednesday, August 5, 2026, at 12:13 PM UTC
Root cause: A recent change intended to improve how Copilot requests are routed unexpectedly sent some requests through an incompatible service path, resulting in the impact.
Next update by: Friday, August 7, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Aug 6 22:34:47 2026 |
|---|
| Description: | Title: Some users may encounter intermittent failures with an error when sending prompts in Microsoft 365 Copilot
User impact: Users may encounter intermittent failures with an error when sending prompts in Copilot Chat in Web mode
More info: This issue intermittently impacts a subset of licensed Copilot users attempting to send prompts through Copilot Chat in the web browser while the "Web" content toggle is enabled, and affected users may receive a “Sorry, something went wrong” error when submitting Copilot Chat messages and prompts.
While we're focused on remediation, affected users can utilize the "Work" tab when using Copilot Chat to avoid potential impact.
Current status: Upon further investigation, we've determined this issue is specific to subset of licensed Copilot users attempting to send prompts through Copilot Chat in the web browser while the "Web" content toggle is enabled, and users should be able to avoid impact by disabling this feature and entering "Work" mode. We've updated the User impact and More info sections of this communication accordingly. We're continuing to review the suspected offending change and reviewing options to remediate the impact as soon as possible.
Scope of impact: Some users with Copilot licenses may encounter failures with an error when attempting to send prompts in Copilot Chat while the "Web" content toggle is enabled. This information may be updated as our investigation continues.
Next update by: Friday, August 7, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Aug 6 21:42:34 2026 |
|---|
| Description: | Title: Some users may encounter intermittent failures with an error when sending prompts in Microsoft 365 Copilot
User impact: Users may encounter intermittent failures with an error when sending prompts in Copilot Chat in Web mode
More info: This issue intermittently impacts a subset of licensed Copilot users attempting to send prompts through Copilot Chat in the web browser while the "Web" content toggle is enabled, and affected users may receive a “Sorry, something went wrong” error when submitting Copilot Chat messages and prompts.
While we're focused on remediation, affected users can utilize the "Work" tab when using Copilot Chat to avoid potential impact.
Current status: We’ve isolated a specific change to the service that we suspect is causing some Microsoft 365 Copilot Chat requests to fail. We’re reviewing the affected configurations to confirm our findings and determine the appropriate remediation.
Scope of impact: Some users with Copilot licenses may encounter failures with an error when attempting to send prompts in Copilot Chat while the "Web" content toggle is enabled. This information may be updated as our investigation continues.
Next update by: Friday, August 7, 2026, at 4:00 AM UTC
|
|---|
|
TM1448902 - Admins may be unable to assign Microsoft Teams numbers to resource accounts using multiple methods
| Status: | serviceRestored |
|---|
| Start Time: | Thu Aug 6 03:00:00 2026 |
|---|
| End Time: | Thu Aug 6 14:07:21 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 6 14:19:17 2026 |
|---|
| Root Cause: | A configuration issue within a recent update contains an error causing the Resource Provider service to return a null value, causing the requests to fail and resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 6 14:19:13 2026 |
|---|
| Description: | Title: Admins may be unable to assign Microsoft Teams numbers to resource accounts using multiple methods
User impact: Admins may have been unable to assign Microsoft Teams numbers to resource accounts using multiple methods.
More info: Affected methods included:
- Direct routing
- Operator connect
- PowerShell
Final status: We've confirmed that the rollback has completed and validated this issue has been remediated with affected admins.
Scope of impact: All admins attempting to apply numbers to resource accounts may have been affected.
Start time: Thursday, August 6, 2026, at 7:00 AM UTC
End time: Thursday, August 6, 2026, at 5:20 PM UTC
Root cause: A configuration issue within a recent update contains an error causing the Resource Provider service to return a null value, causing the requests to fail and resulting in impact.
Next steps:
- We're continuing our analysis of the impacting change to better identify and prevent similar issues during our update testing and validation phases in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 6 12:44:05 2026 |
|---|
| Description: | Title: Admins may be unable to assign Microsoft Teams numbers to resource accounts using multiple methods
User impact: Admins may be unable to assign Microsoft Teams numbers to resource accounts using multiple methods.
More info: Affected methods include:
- Direct routing
- Operator connect
- PowerShell
Current status: Our analysis of provided correlation IDs and service telemetry has identified that a configuration issue within a recent update contains an error causing the Resource Provider service to return a null value, causing the requests to fail, resulting in impact. We're in the process of rolling back this change to remediate impact and will provide a remediation timeline once available.
Scope of impact: All admins attempting to apply numbers to resource accounts are affected.
Start time: Thursday, August 6, 2026, at 7:00 AM UTC
Root cause: A configuration issue within a recent update contains an error causing the Resource Provider service to return a null value, causing the requests to fail, resulting in impact.
Next update by: Thursday, August 6, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Aug 6 11:31:34 2026 |
|---|
| Description: | Title: Admins may be unable to assign Microsoft Teams numbers to resource accounts using multiple methods
User impact: Admins may be unable to assign Microsoft Teams numbers to resource accounts using multiple methods.
More info: Affected methods include:
- Direct routing
- Operator connect
- PowerShell
Current status: We've received reports of admins encountering errors when attempting to apply numbers to resource accounts in Microsoft Teams. We're reviewing provided correlation IDs to better understand the impact scenario and determine our next steps.
Scope of impact: All admins attempting to apply numbers to resource accounts are affected.
|
|---|
|
| Time: | Thu Aug 6 11:14:14 2026 |
|---|
| Description: | Title: Admins may be unable to assign Microsoft Teams numbers to resource accounts using multiple methods
User impact: Admins may be unable to assign Microsoft Teams numbers to resource accounts using multiple methods.
More info: Affected methods include:
- Direct routing
- Operator connect
- PowerShell
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.
|
|---|
|
MO1437424 - Issues accessing or using Microsoft 365 services routed through the North America region.
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jul 23 10:44:00 2026 |
|---|
| End Time: | Thu Jul 23 14:40:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 6 10:35:25 2026 |
|---|
| Root Cause: | A detailed root cause is provided within the Post Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 6 10:34:38 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jul 30 14:58:54 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jul 27 18:53:46 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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:40 PM UTC
Root cause: A detailed root cause is provided within the Post Incident Report.
Some Microsoft 365 services took actions, such as rerouting connections to alternate infrastructures, to resolve their impacts sooner.
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.
We’ll be providing an additional Final Post Incident report in line with Azure Networking’s PIR due to be published by August 7, 2026.
|
|---|
|
| 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.
|
|---|
|
MO1447619 - Users may have been unable to sign into the OneNote Web Clipper
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jul 24 04:06:00 2026 |
|---|
| End Time: | Thu Aug 6 06:20:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Aug 6 07:38:26 2026 |
|---|
| Root Cause: | A recent maintenance update intended to remove unnecessary components from the service inadvertently removed a required authentication component, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Aug 6 07:37:57 2026 |
|---|
| Description: | Title: Users may have been unable to sign into the OneNote Web Clipper
User impact: Users may have been unable to sign into the OneNote Web Clipper.
More info: Users may have received an error when attempting to sign into the OneNote Web Clipper.
Final status: We've completed the deployment of the fix, and service monitoring indicates that the impact has now been resolved.
Scope of impact: Your organization was affected by this event, and any users attempting to sign in to OneNote Web Clipper were impacted.
Start time: Friday, July 24, 2026, at 8:06 AM UTC
End time: Thursday, August 6, 2026, at 10:20 AM UTC
Root cause: A recent maintenance update intended to remove unnecessary components from the service inadvertently removed a required authentication component, resulting in impact.
Next steps: - We're reviewing our service maintenance procedures and validation processes to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Aug 6 06:20:18 2026 |
|---|
| Description: | Title: Users may be unable to sign into the OneNote Web Clipper
User impact: Users may be unable to sign into the OneNote Web Clipper.
More info: Users may receive an error when attempting to sign into the OneNote Web Clipper.
Current status: We've completed the deployment of our fix to the majority of the affected environments and anticipate that most users will no longer be affected by the issue. We expect deployment to complete in the remaining affected infrastructure by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues.
Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper.
Next update by: Thursday, August 6, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Thu Aug 6 01:11:54 2026 |
|---|
| Description: | Title: Users may be unable to sign into the OneNote Web Clipper
User impact: Users may be unable to sign into the OneNote Web Clipper.
More info: Users may receive an error when attempting to sign into the OneNote Web Clipper.
Current status: We've completed validations on the new fix and have initiated its deployment. We're monitoring as it progresses to establish a completion timeline.
Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues.
Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper.
Next update by: Thursday, August 6, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Aug 5 16:38:32 2026 |
|---|
| Description: | Title: Users may be unable to sign into the OneNote Web Clipper
User impact: Users may be unable to sign into the OneNote Web Clipper.
More info: Users may receive an error when attempting to sign into the OneNote Web Clipper.
Current status: We've completed the deployment of our fix to our internal testing environment; however, the fix did not resolve the issue as expected. We've prepared another fix which is being deployed to our testing environment. Once complete, we'll perform validations and confirm if we see impact remediation, after which we'll confirm a timeline for deployment to the affected environment.
Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues.
Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper.
Next update by: Thursday, August 6, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Aug 5 09:55:40 2026 |
|---|
| Description: | Title: Users may be unable to sign into the OneNote Web Clipper
User impact: Users may be unable to sign into the OneNote Web Clipper.
More info: Users may receive an error when attempting to sign into the OneNote Web Clipper.
Current status: We've confirmed that the deployment is progressing as expected and anticipate sharing a completion timeline by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues.
Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper.
Next update by: Wednesday, August 5, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 23:22:19 2026 |
|---|
| Description: | Title: Users may be unable to sign into the OneNote Web Clipper
User impact: Users may be unable to sign into the OneNote Web Clipper.
More info: Users may receive an error when attempting to sign into the OneNote Web Clipper.
Current status: We've identified that the deployment of the fix is taking longer than initially anticipated, but we're monitoring its progress closely to ensure the deployment completes without encountering any complications.
Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues.
Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper.
Next update by: Wednesday, August 5, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Aug 4 20:52:24 2026 |
|---|
| Description: | Title: Users may be unable to sign into the OneNote Web Clipper
User impact: Users may be unable to sign into the OneNote Web Clipper.
More info: Users may receive an error when attempting to sign into the OneNote Web Clipper.
Current status: We've completed creating the code fix, and we've initiated deployment to the imapcted environment. We expect the deployment will be complete and the issue resolved by our next scheduled update.
Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper are impacted. This information may be updated as our investigation continues.
Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper.
Next update by: Wednesday, August 5, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Aug 4 18:32:48 2026 |
|---|
| Description: | Title: Users may be unable to sign into the OneNote Web Clipper
User impact: Users may be unable to sign into the OneNote Web Clipper.
More info: Users may receive an error when attempting to sign into the OneNote Web Clipper.
Current status: We've identified that a recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication HTML, preventing users from signing into the OneNote Web Clipper. We're creating a code fix that will add this authentication HTML back into the service and remediate impact.
Scope of impact: Your organization is affected by this event, and any users attempting to sign into the OneNote Web Clipper is impacted. This information may be updated as our investigation continues.
Root cause: A recent maintenance action meant to remove unneeded code from the service has mistakenly removed the authentication html, preventing users from signing into the OneNote Web Clipper.
Next update by: Wednesday, August 5, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Aug 4 18:09:05 2026 |
|---|
| Description: | Title: Users may be unable to sign into the OneNote Web Clipper
User impact: Users may be unable to sign into the OneNote Web Clipper.
More info: Users may receive an error when attempting to sign into the OneNote Web Clipper.
Current status: We're investigating a potential issue with the OneNote Web Clipper and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1448394 - Users may see intermittent delays and errors when accessing their Exchange Online mailbox through any connection method
| Status: | serviceRestored |
|---|
| Start Time: | Wed Aug 5 19:24:00 2026 |
|---|
| End Time: | Wed Aug 5 19:44:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Aug 6 02:11:27 2026 |
|---|
| Root Cause: | A portion of infrastructure supporting timely connections to Exchange Online was performing below the expected service threshold, leading to intermittent delays and errors when accessing Exchange Online mailboxes.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 5 21:01:04 2026 |
|---|
| Description: | Title: Users may see intermittent delays and errors when accessing their Exchange Online mailbox through any connection method
User impact: Users saw intermittent delays and errors when accessing their Exchange Online mailbox through any connection method.
Final status: A portion of infrastructure supporting timely connections to Exchange Online was performing below the expected service threshold. Our automated recovery tools repaired the issue and we monitored the environment to validate that the impact is remediated.
Scope of impact: This issue may have intermittently impacted users attempting to access their Exchange Online mailbox through any connection method.
Start time: Wednesday, August 5, 2026, at 11:24 PM UTC
End time: Wednesday, August 5, 2026, at 11:44 PM UTC
Root cause: A portion of infrastructure supporting timely connections to Exchange Online was performing below the expected service threshold, leading to intermittent delays and errors when accessing Exchange Online mailboxes.
Next steps: We're working to improve our automated detection and recovery tools to better identify and prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Aug 5 19:53:00 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.
|
|---|
|
MO1440526 - Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 22 20:26:00 2026 |
|---|
| End Time: | Wed Aug 5 16:53:46 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 5 17:35:21 2026 |
|---|
| Root Cause: | Organizations that requested we turn off Unlicensed User Access for their organization encountered this problem after OTP deprecation and unlicensed user check in the external sharing code became enforced.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 5 17:35:17 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may have been unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users were unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels. Upon failure, affected users encountered the following error: "That didn't work: We couldn't find a valid SharePoint Online license..."
While we worked to remediate the impact from this event, impacted organizations were able to bypass the impact in one of the following two ways:
1) Create a support case and contact Microsoft to request that "Unlicensed User Access" be enabled for their tenant.
2) Admins within the affected organizations could have assigned any license that included the SharePoint Online service to the external users they were attempting to share with to bypass the impact for those users.
Admins that made any licensing changes during this event should work with support representatives for any further assistance.
Final status: Our extended service monitoring has validated that our roll back of the recent change has remediated the impact.
Scope of impact: Some users who attempted to share files with external recipients through SharePoint Online and OneDrive were impacted.
Start time: Thursday, July 23, 2026, at 12:26 AM UTC
End time: Wednesday, July 29, 2026, at 7:13 PM UTC
Root cause: Organizations that requested we turn off Unlicensed User Access for their organization encountered this problem after OTP deprecation and unlicensed user check in the external sharing code became enforced.
Next steps:
- We're further analyzing our deprecation processes in our effort to prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 3 16:58:31 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may be unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users may be unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels. Upon failure, affected users encounter the following error: "That didn't work: We couldn't find a valid SharePoint Online license..."
While we're working to resolve this issue, impacted organizations may be able to bypass the impact in one of the following two ways:
1) Create a support case and contact Microsoft to request that "Unlicensed User Access" be enabled for their tenant.
2) Admins within the affected organizations can assign any license that provides the SharePoint Online service to the external users they're attempting to share with to bypass the impact for those users.
Current status: We've rolled back a recent service change that we believe may be contributing to this impact and have confirmed that this step has mitigated impact for a subset of users. We're continuing to monitor this rollback in order to validate full remediation for this event.
Scope of impact: Some users attempting to share files with external recipients through SharePoint Online and OneDrive may be impacted. This information may be updated as our investigation continues.
Root cause: Organizations that requested we turn off Unlicensed User Access for their organization are encountering this problem after OTP deprecation and unlicensed user check in the external sharing code is now being enforced.
Next update by: Wednesday, August 5, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Sat Aug 1 01:41:33 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may be unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users may be unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels. Upon failure, affected users encounter the following error: "That didn't work: We couldn't find a valid SharePoint Online license..."
While we're working to resolve this issue, impacted organizations may be able to bypass the impact in one of the following two ways:
1) Create a support case and contact Microsoft to request that "Unlicensed User Access" be enabled for their tenant.
2) Admins within the affected organizations can assign any license that provides the SharePoint Online service to the external users they're attempting to share with to bypass the impact for those users.
Current status: We're continuing to evaluate the data pathways responsible for providing file sharing to external users to assist us in identifying the most expedient path to complete remediation.
Scope of impact: Some users attempting to share files with external recipients through SharePoint Online and OneDrive may be impacted. This information may be updated as our investigation continues.
Root cause: Organizations that requested we turn off Unlicensed User Access for their organization are encountering this problem after OTP deprecation and unlicensed user check in the external sharing code is now being enforced.
Next update by: Monday, August 3, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Jul 30 17:46:48 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may be unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users may be unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels. Upon failure, affected users encounter the following error: "That didn't work: We couldn't find a valid SharePoint Online license..."
Current status: We've identified that this impact only occurs in a specific scenario: if your organization previously contacted Microsoft at some point in the past to specifically request that Microsoft turn off Unlicensed User Access for your organization. Otherwise, no impact is occurring. Furthermore, the reason why this was previously working, and is now not working, is we've identified that an unlicensed user check exists in the external sharing code that was previously not enforced, as one-time password (OTP) generation essentially rendered it unnecessary. However, with the recent deprecation of OTP, this check is now being enforced. We've identified two mitigations impacted organizations can take to relieve the issue:
2) Admins within the affected organizations can assign any license that provides the SharePoint Online service to the external users they're attempting to share with to bypass the impact for those users.
2) Impacted organizations can create a support case and contact Microsoft to request that "Unlicensed User Access" be enabled for their tenant.
We're continuing to evaluate how unlicensed user access should interact with external sharing.
Scope of impact: Some users attempting to share files with external recipients through SharePoint Online and OneDrive may be impacted. This information may be updated as our investigation continues.
Root cause: Organizations that requested we turn off Unlicensed User Access for their organization are encountering this problem after OTP deprecation and unlicensed user check in the external sharing code is now being enforced.
Next update by: Wednesday, August 5, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 17:55:02 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may be unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users may be unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels. Upon failure, affected users encounter the following error: "That didn't work: We couldn't find a valid SharePoint Online license..."
Current status: We're continuing to obtain data such as Trace logs and specific User Principal Names (UPNs) from various affected users to assist in furthering our understanding of the full scope of this issue. The development of effective remediation steps is taking longer than anticipated as we allow time for this this thorough root cause analysis.
Scope of impact: Some users attempting to share files with external recipients through SharePoint Online and OneDrive may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, July 30, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Jul 28 17:47:03 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may be unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users may be unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels.
Current status: We're in the process of obtaining Trace logs, specific User Principal Names (UPNs), and confirmation of the identified feature status from various affected users to further our investigation into the issue and options for mitigation.
Scope of impact: Some users attempting to share files with external recipients through SharePoint Online and OneDrive may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, July 29, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Jul 27 19:45:57 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may be unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users may be unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels.
Current status: We're reviewing cases from affected users and previous service guidance to identify the most effective options for resolution.
Scope of impact: Some users attempting to share files with external recipients through SharePoint Online and OneDrive may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, July 28, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Jul 27 18:33:41 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may be unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users may be unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels.
Current status: We're continuing our investigation into associated configuration changes in parallel with analyzing recent network trace logs from a portion of affected users in order to determine the next steps for remediation.
Scope of impact: Some users attempting to share files with external recipients through SharePoint Online and OneDrive may be impacted.
Next update by: Tuesday, July 28, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Jul 27 15:18:11 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may be unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users may be unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels.
Current status: We're expanding our investigation to include recent changes or updates which may be contributing to the impact.
Scope of impact: Some users attempting to share files with external recipients through SharePoint Online and OneDrive may be impacted.
Next update by: Monday, July 27, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Jul 27 10:48:25 2026 |
|---|
| Description: | Title: Some users may be unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users may be unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users may be unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels.
Current status: We're reviewing HTTP Archive (HAR) files alongside API call patterns to help identify the root cause and next steps required to mitigate impact.
Scope of impact: Some users attempting to share files with external recipients through SharePoint Online and OneDrive may be impacted.
Next update by: Monday, July 27, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jul 27 10:14:16 2026 |
|---|
| Description: | Title: Some users are unable to share files with external recipients through SharePoint Online and Microsoft OneDrive
User impact: Users are unable to share files with external recipients through SharePoint Online and OneDrive.
More info: Affected users are unable to send external sharing invitations from SharePoint Online sites and OneDrive locations, despite external sharing being enabled at both the tenant and site levels.
Current status: We're reviewing HTTP Archive (HAR) files alongside API call patterns to help identify the root cause and next steps required to mitigate impact.
Scope of impact: Your organization is affected by this event, and some users attempting to share files with external recipients through SharePoint Online and OneDrive are impacted. This information may be updated as our investigation continues.
Next update by: Monday, July 27, 2026, at 7:30 PM UTC
|
|---|
|
TM1447500 - Admins may experience authentication issues or errors preventing access to the Microsoft Teams CQD
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 24 17:06:00 2026 |
|---|
| End Time: | Wed Aug 5 16:30:35 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Aug 5 16:32:42 2026 |
|---|
| Root Cause: | A recent service update intending to improve service authentication produced an impacting token refresh issue that prevented admins' access to the Microsoft Teams Call Quality dashboard.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 5 16:32:38 2026 |
|---|
| Description: | Title: Admins may experience authentication issues or errors preventing access to the Microsoft Teams CQD
User impact: Admins may have experienced authentication issues or errors preventing access to the Microsoft Teams CQD.
More info: This issue produced 400 errors or authentication problems for any admin, preventing their access to the Microsoft Teams Call Quality dashboard (CQD).
Final status: Following the deployment of our fix, we've validated with affected admins who confirmed the authentication issues and errors that had prevented access to the Microsoft Teams Call Quality dashboard have subsided, and that the impact has been remediated.
Scope of impact: This issue produced 400 errors or authentication problems for any admin, preventing their access to the Microsoft Teams Call Quality dashboard.
Start time: Friday, July 24, 2026, at 9:06 PM UTC
End time: Wednesday, August 5, 2026, at 12:18 AM UTC
Root cause: A recent service update intending to improve service authentication produced an impacting token refresh issue that prevented admins' access to the Microsoft Teams Call Quality dashboard.
Next steps:
- We're further analyzing the offending service authentication update to help us improve our pre-deployment testing and validations.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 4 15:28:18 2026 |
|---|
| Description: | Title: Admins may experience authentication issues or errors preventing access to the Microsoft Teams Call Quality dashboard
User impact: Admins may experience authentication issues or errors preventing access to the Microsoft Teams Call Quality dashboard.
Current status: We've identified a recent update to service authentication that is producing an impacting authentication token refresh issue that's preventing admins' access to the Microsoft Teams Call Quality Dashboard. We're developing a fix to address the offending token refresh and to remediate the impact. We'll provide an updated timeline for our fix deployment once our internal testing and validations have completed.
Scope of impact: This issue may produce 400 errors or authentication problems for any admin, preventing them access to the Microsoft Teams Call Quality dashboard. This information may be updated as our investigation continues.
Start time: Friday, July 24, 2026, at 9:06 PM UTC
Root cause: A recent service update intending to improve service authentication has produced an impacting token refresh issue, preventing admins' access to the Microsoft Teams Call Quality dashboard.
Next update by: Thursday, August 6, 2026, at 12:00 AM UTC
|
|---|
|
CW1447067 - Users may be unable to access Microsoft Copilot Chat in the browser and may encounter a 400 Request Header error
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 31 16:00:00 2026 |
|---|
| End Time: | Wed Aug 5 00:45:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Aug 5 13:41:13 2026 |
|---|
| Root Cause: | A recent service change affected the way browser authentication information was stored for Microsoft Copilot Chat. This could cause some browser requests to exceed expected limits, which may have prevented users from accessing the service.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 5 13:40:47 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Copilot Chat in the browser and may encounter a 400 Request Header error
User impact: Users may have been unable to access Copilot Chat in the browser and may have encountered a 400 Request Header error.
More info: As a temporary workaround, affected users may have been able to restore access to Microsoft Copilot Chat by clearing their browser cookies and then trying again.
Final status: We've completed deployment of our fix to address the browser authentication information misconfiguration and validated after completing an internal monitoring period that our actions successfully remediated impact. If users are still experiencing impact, we advise them to clear their browser cookies and reload Copilot Chat.
Scope of impact: Impact was specific to some users attempting to access Microsoft Copilot Chat in the browser.
Start time: Friday, July 31, 2026, at 8:00 PM UTC
End time: Wednesday, August 5, 2026, at 4:45 AM UTC
Root cause: A recent service change affected the way browser authentication information was stored for Microsoft Copilot Chat. This could cause some browser requests to exceed expected limits, which may have prevented users from accessing the service.
Next steps:
-We're analyzing the offending service change to isolate why the potential for impact wasn't caught prior to the update being deployed to affected users. This analysis will help us to improve our update implementation process moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 4 18:09:39 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Copilot Chat in the browser and may encounter a 400 Request Header error
User impact: Users may be unable to access Microsoft Copilot Chat in the browser and may encounter a 400 Request Header error.
More info: As a temporary workaround, affected users may be able to restore access to Microsoft Copilot Chat by clearing their browser cookies and then trying again.
Current status: Our fix deployment to address the browser authentication information misconfiguration is ongoing, and we anticipate deployment to be completed by our next scheduled update.
Scope of impact: Impact is specific to some users attempting to access Microsoft Copilot Chat in the browser.
Start time: Friday, July 31, 2026, at 8:00 PM UTC
Root cause: A recent service change that affects the way browser authentication information is stored for Microsoft Copilot Chat. This can cause some browser requests to exceed expected limits, which may prevent users from accessing the service.
Next update by: Wednesday, August 5, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Aug 4 05:28:37 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Copilot Chat in the browser and may encounter a 400 Request Header error
User impact: Users may be unable to access Microsoft Copilot Chat in the browser and may encounter a 400 Request Header error.
More info: As a temporary workaround, affected users may be able to restore access to Microsoft Copilot Chat by clearing their browser cookies and then trying again.
Current status: We've identified the root cause of the issue as a recent service change that affects the way browser authentication information is stored for Microsoft Copilot Chat. This can cause some browser requests to exceed expected limits, which may prevent users from accessing the service. We're currently rolling out a fix and will share an update on deployment timeline in our next scheduled communication.
Scope of impact: Impact is specific to some users attempting to access Microsoft Copilot Chat in the browser.
Start time: Friday, July 31, 2026, at 8:00 PM UTC
Root cause: A recent service change that affects the way browser authentication information is stored for Microsoft Copilot Chat. This can cause some browser requests to exceed expected limits, which may prevent users from accessing the service.
Next update by: Tuesday, August 4, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 03:28:25 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Copilot Chat in the browser and may encounter a 400 Request Header error
User impact: Users may be unable to access Microsoft Copilot Chat in the browser and may encounter a 400 Request Header error.
More info: As a temporary workaround, affected users may be able to restore access to Microsoft Copilot Chat by clearing their browser cookies and then trying again.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users attempting to access Microsoft Copilot Chat in the browser.
|
|---|
|
CP1447620 - Users may be unable to access Microsoft 365 Copilot in the browser and may encounter a 400 Request Header error
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 31 16:00:00 2026 |
|---|
| End Time: | Wed Aug 5 00:45:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Aug 5 13:41:03 2026 |
|---|
| Root Cause: | A recent service change affected the way browser authentication information was stored for Copilot. This could cause some browser requests to exceed expected limits, which may have prevented users from accessing the service.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 5 13:40:51 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft 365 Copilot in the browser and may encounter a 400 Request Header error
User impact: Users may have been unable to access Copilot in the browser and may have encountered a 400 Request Header error.
More info: As a temporary workaround, affected users may have been able to restore access to Microsoft Copilot by clearing their browser cookies and then trying again.
Final status: We've completed deployment of our fix to address the browser authentication information misconfiguration and validated after completing an internal monitoring period that our actions successfully remediated impact. If users are still experiencing impact, we advise them to clear their browser cookies and reload Copilot.
Scope of impact: Impact was specific to some users attempting to access Copilot in the browser.
Start time: Friday, July 31, 2026, at 8:00 PM UTC
End time: Wednesday, August 5, 2026, at 4:45 AM UTC
Root cause: A recent service change affected the way browser authentication information was stored for Copilot. This could cause some browser requests to exceed expected limits, which may have prevented users from accessing the service.
Next steps:
-We're analyzing the offending service change to isolate why the potential for impact wasn't caught prior to the update being deployed to affected users. This analysis will help us to improve our update implementation process moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 4 18:09:37 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft 365 Copilot in the browser and may encounter a 400 Request Header error
User impact: Users may be unable to access Copilot in the browser and may encounter a 400 Request Header error.
More info: As a temporary workaround, affected users may be able to restore access to Microsoft Copilot by clearing their browser cookies and then trying again.
Current status: We've received reports from a subset of affected users who have reported that they are unable to access Copilot in their browser and are encountering a 400 Request Header error. We've isolated that impact is caused by a recent service change that affects the way browser authentication information is stored for Copilot. This can cause some browser requests to exceed expected limits, which may prevent users from accessing the service. We've initiated deployment of a fix to address the browser authentication information misconfiguration, and we anticipate deployment to be completed by our next scheduled update.
Scope of impact: Impact is specific to some users attempting to access Copilot in the browser.
Start time: Friday, July 31, 2026, at 8:00 PM UTC
Root cause: A recent service change that affects the way browser authentication information is stored for Copilot. This can cause some browser requests to exceed expected limits, which may prevent users from accessing the service.
Next update by: Wednesday, August 5, 2026, at 7:00 PM UTC
|
|---|
|
TM1447248 - Users may experience issues accessing Microsoft Teams or using specific Teams features
| Status: | serviceRestored |
|---|
| Start Time: | Tue Aug 4 09:00:00 2026 |
|---|
| End Time: | Tue Aug 4 22:25:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Aug 5 12:42:56 2026 |
|---|
| Root Cause: | A recent service build intended to introduce a component caching system to prefetch authentication components caused an unexpected increase in component traffic for our service infrastructure, resulting in failures when users attempted to access Microsoft Teams
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Aug 5 12:42:41 2026 |
|---|
| Description: | Title: Users may experience issues accessing Microsoft Teams or using specific Teams features
User impact: Users may have experienced issues accessing Microsoft Teams or using specific Teams features.
Final status: We've validated that a recent service build intended to introduce a component caching system to prefetch authentication components caused an unexpected increase in component traffic for our service infrastructure, resulting in failures when users attempted to access Microsoft Teams. We've rolled back the offending build and implemented additional performance optimizations to assist with processing component traffic. After completing a monitoring period of service availability, we've validated that our actions successfully remediated impact.
Scope of impact: Impact was specific to some users in North America attempting to access Microsoft Teams or using specific Teams features.
Start time: Tuesday, August 4, 2026, at 1:00 PM UTC
End time: Wednesday, August 5, 2026, at 2:25 AM UTC
Root cause: A recent service build intended to introduce a component caching system to prefetch authentication components caused an unexpected increase in component traffic for our service infrastructure, resulting in failures when users attempted to access Microsoft Teams
Next steps:
- We're analyzing the offending service build to isolate why the potential for impact wasn't isolated prior to the build being deployed to affected users. This further analysis will help us to improve our build implementation processes moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Aug 4 20:38:37 2026 |
|---|
| Description: | Title: Users may experience issues accessing Microsoft Teams or using specific Teams features
User impact: Users may experience issues accessing Microsoft Teams or using specific Teams features.
Current status: As we were in the process of determining what additional mitigative actions could be taken, we've identified through further monitoring that service health may be recovering following our recent service build rollback. We're continuing to monitor telemetry to verify whether service health continues to improve through peak periods of traffic, which will help us confirm the underlying source of impact and inform our next steps.
Scope of impact: Impact is specific to some users in North America attempting to access Microsoft Teams or using specific Teams features. This section may be updated as the investigation progresses.
Next update by: Wednesday, August 5, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Aug 4 16:30:24 2026 |
|---|
| Description: | Title: Users may experience issues accessing Microsoft Teams or using specific Teams features
User impact: Users may experience issues accessing Microsoft Teams or using specific Teams features.
Current status: Despite having rolled back the build we believed may have been contributing to the impact, we've observed the impact persisting in our service health metrics. We're continuing to review the associated errors to identify the source of the issue before we begin developing a mitigation strategy.
Scope of impact: Impact is specific to some users in North America attempting to access Microsoft Teams or using specific Teams features. This section may be updated as the investigation progresses.
Next update by: Wednesday, August 5, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Aug 4 14:23:33 2026 |
|---|
| Description: | Title: Users may experience issues accessing Microsoft Teams or using specific Teams features
User impact: Users may experience issues accessing Microsoft Teams or using specific Teams features.
Current status: We've completed rolling back a recent build which may have been contributing to the impact, and we're monitoring service health metrics to determine whether the build was causing the impact.
Scope of impact: Impact is specific to some users in North America attempting to access Microsoft Teams or using specific Teams features. This section may be updated as the investigation progresses.
Next update by: Tuesday, August 4, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 12:12:29 2026 |
|---|
| Description: | Title: Users may experience issues accessing Microsoft Teams or using specific Teams features
User impact: Users may experience issues accessing Microsoft Teams or using specific Teams features.
Current status: Our review of service monitoring telemetry has been inconclusive; however, we've identified a recent change which may be contributing to impact, and we're reversing this change to confirm whether the impact is remediated.
Scope of impact: Impact is specific to some users in North America attempting to access Microsoft Teams or using specific Teams features. This section may be updated as the investigation progresses.
Next update by: Tuesday, August 4, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 10:19:07 2026 |
|---|
| Description: | Title: Users may experience issues accessing Microsoft Teams or using specific Teams features
User impact: Users may experience issues accessing Microsoft Teams or using specific Teams features.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users in North America attempting to access Microsoft Teams or using specific Teams features. This section may be updated as the investigation progresses.
Next update by: Tuesday, August 4, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Tue Aug 4 09:56:21 2026 |
|---|
| Description: | Title: We've received reports that some users may be unable to utilize the Microsoft Teams service
User impact: We're validating impact to your organization.
Current status: We're investigating a potential issue with the Microsoft Teams service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
IT1446841 - Users may be unable to access Wi-Fi or VPN on Android devices
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 9 18:25:00 2026 |
|---|
| End Time: | Mon Aug 3 23:16:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Aug 4 00:55:02 2026 |
|---|
| Root Cause: | A recent change to the Microsoft Intune service intended to improve reliability and make certificate delivery more resilient contained a code regression, which impacted certificate delivery and led to impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Aug 4 00:54:46 2026 |
|---|
| Description: | Title: Users may be unable to access Wi-Fi or VPN on Android devices
User impact: Users may have been unable to access Wi-Fi or VPN on Android devices that required a certificate from Microsoft Intune.
More info: Users may have been affected if they required a new SCEP certificate delivery from Microsoft Intune to access their Wi-Fi or VPN on newly targeted Android devices that didn't already have a valid certificate. Users with existing valid SCEP certificates weren't affected by this behavior and were able to access network connections as expected.
However, regardless of whether certificates already exist on the device, users on Android devices leveraging SCEP certificate profiles may have been blocked from receiving any other targeted configuration policy. Admins may have also been affected and may have seen errors in the SCEP policy console for the associated policy status in Microsoft Intune.
Final status: We've completed the deployment of our fix to roll back the previous change and confirmed through our service health telemetry that impact has been resolved.
Scope of impact: Any user or admin may have been affected by this event, and may have been unable to access their Wi-Fi or VPN on Android devices that required a certificate from Microsoft Intune.
Start time: Thursday, July 9, 2026, at 10:25 PM UTC
End time: Tuesday, August 4, 2026, at 3:16 AM UTC
Root cause: A recent change to the Microsoft Intune service intended to improve reliability and make certificate delivery more resilient contained a code regression, which impacted certificate delivery and led to impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to the certificate delivery process in Microsoft Intune prior to deployment to prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 3 23:56:34 2026 |
|---|
| Description: | Title: Users may be unable to access Wi-Fi or VPN on Android devices
User impact: Users may be unable to access their Wi-Fi or VPN on Android devices that require a certificate from Microsoft Intune.
More info: Users may be affected if they require a new SCEP certificate delivery from Microsoft Intune to access their Wi-Fi or VPN on newly targeted Android devices that don't already have a valid certificate. Users with existing valid SCEP certificates aren't affected by this behavior and are able to access network connections as expected.
However, regardless of whether certificates already exist on the device, users on Android devices leveraging SCEP certificate profiles may be blocked from receiving any other targeted configuration policy. Admins may also be affected and may see errors in the SCEP policy console for the associated policy status in Microsoft Intune.
Current status: We've completed all of the needed validations to ensure the fix deployment to roll back the previous change works as expected. We've now deployed this fix to all affected environments and we're monitoring the progress to ensure its completion and subsequent remediation of impact.
Scope of impact: Any user or admin may be affected by this event, and may be unable to access their Wi-Fi or VPN on Android devices that require a certificate from Microsoft Intune. This section may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 10:25 PM UTC
Root cause: A recent change to the Microsoft Intune service intended to improve reliability and make certificate delivery more resilient contained a code regression, which is impacting certificate delivery and leading to impact.
Next update by: Tuesday, August 4, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Aug 3 21:53:12 2026 |
|---|
| Description: | Title: Users may be unable to access Wi-Fi or VPN on Android devices
User impact: Users may be unable to access their Wi-Fi or VPN on Android devices that require a certificate from Microsoft Intune.
More info: Users may be affected if they require a new SCEP certificate delivery from Microsoft Intune to access their Wi-Fi or VPN on newly targeted Android devices that don't already have a valid certificate. Users with existing valid SCEP certificates aren't affected by this behavior and are able to access network connections as expected.
However, regardless of whether certificates already exist on the device, users on Android devices leveraging SCEP certificate profiles may be blocked from receiving any other targeted configuration policy. Admins may also be affected and may see errors in the SCEP policy console for the associated policy status in Microsoft Intune.
Current status: We first deployed our previously mentioned fix to roll back the latest change, in our internal testing environment and confirmed that there's no adverse effects. We're now progressing the deployment of the fix to a subset of affected users and admins to further validate this fix before expanding the deployment to all affected environments.
Scope of impact: Any user or admin may be affected by this event, and may be unable to access their Wi-Fi or VPN on Android devices that require a certificate from Microsoft Intune. This section may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 10:25 PM UTC
Root cause: A recent change to the Microsoft Intune service intended to improve reliability and make certificate delivery more resilient contained a code regression, which is impacting certificate delivery and leading to impact.
Next update by: Tuesday, August 4, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Aug 3 20:11:54 2026 |
|---|
| Description: | Title: Users may be unable to access Wi-Fi or VPN on Android devices
User impact: Users may be unable to access their Wi-Fi or VPN on Android devices that require a certificate from Microsoft Intune.
More info: Users may be affected if they require a new SCEP certificate delivery from Microsoft Intune to access their Wi-Fi or VPN on newly targeted Android devices that don't already have a valid certificate. Users with existing valid SCEP certificates aren't affected by this behavior and are able to access network connections as expected.
However, regardless of whether certificates already exist on the device, users on Android devices leveraging SCEP certificate profiles may be blocked from receiving any other targeted configuration policy. Admins may also be affected and may see errors in the SCEP policy console for the associated policy status in Microsoft Intune.
Current status: We've identified an issue affecting the Microsoft Intune service after receiving reports of impact from users and admins. Our analysis has determined that a recent change to the Microsoft Intune service intended to improve reliability and make certificate delivery more resilient contained a code regression, which is impacting certificate delivery and leading to impact. We're initiating a fix to roll back this change and resolve impact for all users and admins.
Scope of impact: Any user or admin may be affected by this event, and may be unable to access their Wi-Fi or VPN on Android devices that require a certificate from Microsoft Intune. This section may be updated as our investigation continues.
Start time: Thursday, July 9, 2026, at 10:25 PM UTC
Root cause: A recent change to the Microsoft Intune service intended to improve reliability and make certificate delivery more resilient contained a code regression, which is impacting certificate delivery and leading to impact.
Next update by: Tuesday, August 4, 2026, at 2:00 AM UTC
|
|---|
|
TM1446653 - Some users may receive failures when creating channels or adding members to shared channels in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 31 21:35:00 2026 |
|---|
| End Time: | Mon Aug 3 20:07:10 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Aug 3 20:08:10 2026 |
|---|
| Root Cause: | A recent service update migrated JavaScript Object Notation (JSON) deserialization behavior, resulting in scenarios that rely on deserialization to utilize incorrect values and causing users to receive failures, such as when creating channels or adding users to shared channels in Microsoft Teams.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Aug 3 20:08:07 2026 |
|---|
| Description: | Title: Some users may receive failures when creating channels or adding members to shared channels in Microsoft Teams
User impact: Users may have received failures when creating channels or adding members to shared channels in Microsoft Teams.
Final status: After a period of monitoring, we confirmed that rolling back the offending update remediated impact.
Scope of impact: Your organization was affected by this event, and some users may have received failures when creating channels or adding members to shared channels in Microsoft Teams.
Start time: Saturday, August 1, 2026, at 1:35 AM UTC
End time: Monday, August 3, 2026, at 7:07 PM UTC
Root cause: A recent service update migrated JavaScript Object Notation (JSON) deserialization behavior, resulting in scenarios that rely on deserialization to utilize incorrect values and causing users to receive failures, such as when creating channels or adding users to shared channels in Microsoft Teams.
Next steps:
- To help prevent similar impact in the future, we're further reviewing our update release procedures to ensure we're able to better identify issues before changes are deployed.
This is the final update for the event.
|
|---|
|
| Time: | Mon Aug 3 15:42:35 2026 |
|---|
| Description: | Title: Some users may receive failures when creating channels or adding members to shared channels in Microsoft Teams
User impact: Users may receive failures when creating channels or adding members to shared channels in Microsoft Teams.
Current status: After further analysis, we've validated that users can still create shared channels but may be unable to add new users to these channels. We've updated the "Title", "User impact", "Scope of impact", and “Root cause” fields to reflect this. We've rolled back the offending service update and are monitoring service availability to validate remediation. Simultaneously, we're analyzing additional recent updates to validate if there is still potential for residual impact or if the issue is fully remediated.
Scope of impact: Your organization is affected by this event, and some users may receive failures when creating channels or adding members to shared channels in Microsoft Teams. This section may be updated as the investigation progresses.
Start time: Saturday, August 1, 2026, at 1:35 AM UTC
Root cause: A recent service update migrated JavaScript Object Notation (JSON) deserialization behavior, resulting in scenarios that rely on deserialization to utilize incorrect values and causing users to receive failures, such as when creating channels or adding users to shared channels in Microsoft Teams.
Next update by: Tuesday, August 4, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Aug 3 14:44:40 2026 |
|---|
| Description: | Title: Some users may receive failures when creating channels with Channel Capabilities or shared channels in Microsoft Teams
User impact: Users may receive failures when creating channels with Channel Capabilities or shared channels in Microsoft Teams.
Current status: After an internal review, we've isolated that a recent service update migrated JavaScript Object Notation (JSON) deserialization behavior, resulting in scenarios that rely on deserialization to utilize incorrect values and causing users to receive failures, such as when creating channels with Channel Capabilities or shared channels in Microsoft Teams. We're evaluating potential remediation strategies to resolve user impact as soon as possible.
Scope of impact: Your organization is affected by this event, and some users may receive failures when creating channels with Channel Capabilities or shared channels in Microsoft Teams. This section may be updated as the investigation progresses.
Start time: Saturday, August 1, 2026, at 1:35 AM UTC
Root cause: A recent service update migrated JavaScript Object Notation (JSON) deserialization behavior, resulting in scenarios that rely on deserialization to utilize incorrect values and causing users to receive failures, such as when creating channels with Channel Capabilities or shared channels in Microsoft Teams.
Next update by: Monday, August 3, 2026, at 8:00 PM UTC
|
|---|
|
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: | Mon Aug 3 13:05:07 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: | Wednesday, August 26, 2026, at 6:00 PM UTC |
|---|
|
Details
| Time: | Mon Aug 3 13:05:07 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: After completing our internal validations, we've determined that our solution will address the incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer to remediate the impact. We're deploying our solution, and our fix deployment timeline expects that it will be available by our next scheduled communication update.
Scope of impact: This issue impacts a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Wednesday, August 26, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jul 16 12:43:42 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: Our final validation process is ongoing and is expected to take several weeks to complete. Based on our current estimates, we expect the fix to be deployed and the issue to be resolved by Tuesday, August 25, 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, August 3, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jun 30 12:51:20 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: Our validation process is ongoing, and we're continuing to verify the fix before determining a release timeline. We'll provide one once it's available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Thursday, July 16, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jun 23 13:10:34 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: The fix validation is ongoing and we expect to have a release timeline by the next scheduled update.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A Windows update is producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, June 30, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu May 21 13:12:30 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We’re continuing final testing and validation efforts for the fix before deployment. The fix remains scheduled to begin optional rollout around August 25, 2026, through an upcoming Windows cumulative update, before becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, June 23, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Apr 24 15:20:17 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer
User impact: Users may see incorrect service names and descriptions in Microsoft Defender for Endpoint Services and Event Viewer.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
Current status: We're continuing our final validation efforts for the fix. The fix is planned for release as part of an upcoming Windows cumulative update, with an optional rollout beginning around August 25, 2026, and becoming mandatory on September 8, 2026. We’ll provide additional updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Thursday, May 21, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Apr 3 13:02:30 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're in the final stages of validation for the fix. The fix is planned to be released as part of an upcoming Windows cumulative update, with optional rollout expected to begin approximately August 25, 2026, and becoming mandatory on September 8, 2026. We'll continue to provide updates as more information becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 24, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Mar 20 13:24:46 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're preparing the localization fix for additional validations before we initiate the deployment of the fix. We anticipate being able to provide an updated timeline for when we expect the deployment to be released by our next scheduled update.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, April 3, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Feb 20 12:58:51 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're continuing to work toward delivering the additional localization fix, and we expect this process to take additional time due to the complexity involved in implementing the solution. Based on our current estimates, remediation is targeted for a release window of May 2026. We'll provide further updates as this process progresses.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, March 20, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 14:58:23 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: While we’ve developed an additional fix for the localization issues, the complexity of delivering this solution is preventing an expedited resolution. We expect this process to take several weeks as we validate the subtasks involved in instituting the fix. We’ll provide updates on this process and a timeline for deployment once the subtask orchestration is complete.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, February 20, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jan 9 13:12:08 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’re continuing to assess and validate alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 12:35:31 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve identified that the previously developed code fix isn’t an effective solution for addressing the incorrect service names and descriptions. We’re assessing and validating alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 9, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Dec 9 12:44:40 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: Validation of the code fix is continuing to progress, and due to the complex nature of the code developed to address the incorrect service names and descriptions, we're still expecting the deployment to complete by March 2026. We'll provide a more accurate timeline as one becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, January 6, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Dec 8 03:18:26 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We are continuing to validate the fix’s effectiveness and anticipate full deployment by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, December 9, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 05:20:30 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve developed a code fix to address the issue. It’s currently undergoing validation to ensure effectiveness, and we expect the fix to be fully implemented and remediate impact by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, 8 December 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Nov 23 16:12:56 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We've identified a recent Windows update that is producing incorrect service names and descriptions in Services and the Event Viewer for some users who have upgraded to Windows 11 in or after June of 2025. As we work to confirm an accurate window of impact, we're developing a code fix to address the offending change and to remediate the impact. We'll provide an updated timeline for the deployment of our fix and the remediation of impact once our internal validations have completed.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, November 24, 2025, at 10:30 AM UTC
|
|---|
|
IT1442133 - Some admins may have seen incorrect data when navigating to the Windows Cloud PC performance page in Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 9 05:44:00 2026 |
|---|
| End Time: | Fri Jul 31 11:44:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Aug 1 08:31:47 2026 |
|---|
| Root Cause: | A service update intended to support scoped tags for Cloud PC performance reports introduced a code regression that caused some report requests to fail and return incomplete results. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Aug 1 07:05:36 2026 |
|---|
| Description: | Title: Some admins may have seen incorrect data when navigating to the Windows Cloud PC performance page in Microsoft Intune
User impact: Admins may have seen incorrect data when navigating to the Cloud PC performance page in Microsoft Intune.
Final status: We've confirmed that impact has been resolved after an extended period of monitoring service health.
Scope of impact: Your organization was affected by this event, and some admins attempting to view accurate data within the Cloud PC performance page in Microsoft Intune may have been impacted.
Start time: Thursday, July 9, 2026, at 9:44 AM UTC
End time: Friday, July 1, 2026, at 3:44 PM UTC
Root cause: A service update intended to support scoped tags for Cloud PC performance reports introduced a code regression that caused some report requests to fail and return incomplete results.
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: | Wed Jul 29 07:58:34 2026 |
|---|
| Description: | Title: Some admins see incorrect data when navigating to the Windows Cloud PC performance page in Microsoft Intune
User impact: Admins see incorrect data when navigating to the Cloud PC performance page in Microsoft Intune.
Current status: We've identified that a service update intended to support scoped tags for Cloud PC performance reports introduced a code regression that is causing some report requests to fail and return incomplete results. We've developed and deployed a code fix to mitigate impact and expect the issue to be resolved by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some admins attempting to view the Cloud PC performance page in Microsoft Intune are impacted.
Estimated time to resolve: Saturday, August 1, 2026
Root cause: A service update intended to support scoped tags for Cloud PC performance reports introduced a code regression that is causing some report requests to fail and return incomplete results.
Next update by: Saturday, August 1, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 05:46:31 2026 |
|---|
| Description: | Title: Some admins see incorrect data when navigating to the Windows Cloud PC performance page in Microsoft Intune
User impact: Admins see incorrect data when navigating to the Cloud PC performance page in Microsoft Intune.
Current status: We're reviewing support case details to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some admins attempting to view the Cloud PC performance page in Microsoft Intune are impacted.
Next update by: Wednesday, July 29, 2026, at 12:00 PM UTC
|
|---|
|
MV1444510 - Some users may have experienced access issues or transient errors when accessing the Microsoft Viva Insight web app
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 31 22:43:00 2026 |
|---|
| End Time: | Sat Aug 1 01:26:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Aug 1 04:09:59 2026 |
|---|
| Root Cause: | A planned backend infrastructure upgrade was temporarily affecting service availability, resulting in transient access issues for some users during the deployment window.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Aug 1 04:08:57 2026 |
|---|
| Description: | Title: Some users may have experienced access issues or transient errors when accessing the Microsoft Viva Insight web app
User impact: Users may have experienced access issues or transient errors when accessing the Microsoft Viva Insights web app.
Final status: The deployment of the planned backend infrastructure upgrade is complete and no further actions are required. We've confirmed impact is remediated after a period of monitoring service telemetry.
Scope of impact: Impact was specific to some users trying to access the Microsoft Viva Insights web app.
Start time: Saturday, August 1, 2026, at 2:43 AM UTC
End time: Saturday, August 1, 2026, at 5:26 AM UTC
Root cause: A planned backend infrastructure upgrade was temporarily affecting service availability, resulting in transient access issues for some users during the deployment window.
Next steps: We're reviewing our planned backend infrastructure upgrade procedures to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Sat Aug 1 00:41:57 2026 |
|---|
| Description: | Title: Some users may experience intermittent access issues or transient errors when accessing the Microsoft Viva Insights web app
User impact: Users may experience intermittent access issues or transient errors when accessing the Microsoft Viva Insights web app.
Current status: We’re continuing to monitor as the deployment completes throughout the affected service infrastructure to ensure that additional mitigative actions will not be required.
Scope of impact: The problem impacts some users trying to access the Viva Insights web app. This section may be updated as our investigation progresses.
Root cause: A planned backend infrastructure upgrade temporarily is affecting service availability, resulting in transient access issues for some users during the deployment window.
Next update by: Saturday, August 1, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Fri Jul 31 23:27:35 2026 |
|---|
| Description: | Title: Some users may experience intermittent access issues or transient errors when accessing the Microsoft Viva Insights web app
User impact: Users may experience intermittent access issues or transient errors when accessing the Microsoft Viva Insights web app.
Current status: We’ve determined that a planned backend infrastructure upgrade temporarily is affecting service availability, resulting in transient access issues for some users during the deployment window. We’re monitoring as the deployment completes to ensure that additional mitigative actions will not be required.
Scope of impact: The problem impacts some users trying to access the Viva Insights web app. This section may be updated as our investigation progresses.
Root cause: A planned backend infrastructure upgrade temporarily is affecting service availability, resulting in transient access issues for some users during the deployment window.
|
|---|
|
TM1444037 - Users may see a banner in the Microsoft Teams desktop app mistakenly stating they are on an old version
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 31 10:53:54 2026 |
|---|
| End Time: | Fri Jul 31 14:40:11 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 31 14:45:38 2026 |
|---|
| Root Cause: | The service that detects the version of Microsoft Teams a user was using was mistakenly detecting new versions as old, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 31 14:43:37 2026 |
|---|
| Description: | Title: Users may see a banner in the Microsoft Teams desktop app mistakenly stating they are on an old version
User impact: Users may have seen a banner in the Microsoft Teams desktop app mistakenly stating they are on an old version.
More info: The error stated "You're using an old version of Teams. Update the app to continue using Teams on this device". This banner appeared in the Microsoft Teams desktop app regardless of the version being used.
Final status: We've updated the configuration of the offending service update and confirmed that impact is remediated.
Scope of impact: Users on newer versions of Microsoft Teams may have been impacted.
Start time: Monday, July 27, 2026, at 12:30 PM UTC
End time: Friday, July 31, 2026, at 6:40 PM UTC
Root cause: The service that detects the version of Microsoft Teams a user was using was mistakenly detecting new versions as old, resulting in impact.
Next steps: We're reviewing the service that detects the version of Microsoft Teams to identify why it was misconfigured, allowing us to prevent future instances of impact.
|
|---|
|
| Time: | Fri Jul 31 12:52:36 2026 |
|---|
| Description: | Title: Users may see a banner in the Microsoft Teams desktop app mistakenly stating they are on an old version
User impact: Users may see a banner in the Microsoft Teams desktop app mistakenly stating they are on an old version.
More info: The error states "You're using an old version of Teams. Update the app to continue using Teams on this device". This banner appears in the Microsoft Teams desktop app regardless of the version being used.
Current status: We're continuing to update the configuration of the offending service to prevent theses false detections and remediate impact.
Scope of impact: Users on newer versions of Microsoft Teams may be impacted. This information may be updated as our investigation continues.
Root cause: The service that detects the version of Microsoft Teams a user is using is mistakenly detecting new versions as old, resulting in impact.
Next update by: Friday, July 31, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jul 31 11:34:39 2026 |
|---|
| Description: | Title: Users may see a banner in the Microsoft Teams desktop app mistakenly stating they are on an old version
User impact: Users may see a banner in the Microsoft Teams desktop app mistakenly stating they are on an old version.
More info: The error states "You're using an old version of Teams. Update the app to continue using Teams on this device". This banner appears in the Microsoft Teams desktop app regardless of the version being used.
Current status: We've identified that the service that detects the version of Microsoft Teams a user is using is mistakenly detecting new versions as old, resulting in impact. We're updating the configuration of this service to prevent theses false detections and remediate impact.
Scope of impact: Users on newer versions of Microsoft Teams may be impacted. This information may be updated as our investigation continues.
Root cause: The service that detects the version of Microsoft Teams a user is using is mistakenly detecting new versions as old, resulting in impact.
Next update by: Friday, July 31, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Jul 31 11:03:04 2026 |
|---|
| Description: | Title: Users may see a banner in the Microsoft Teams desktop app mistakenly stating they are on an old version
User impact: Users may see a banner in the Microsoft Teams desktop app mistakenly stating they are on an old version.
More info: The error states "You're using an old version of Teams. Update the app to continue using Teams on this device". This banner appears in the Microsoft Teams desktop app regardless of the version being used.
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.
|
|---|
|
SP1393483 - Admins may have been unable to see the configuration search schema mappings in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 7 23:50:00 2026 |
|---|
| End Time: | Wed Jul 29 19:58:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Tenant Admin |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jul 31 04:21:00 2026 |
|---|
| Root Cause: | A recent migration introduced a configuration issue, resulting in a regression that was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jul 31 04:20:47 2026 |
|---|
| Description: | Title: Admins may have been unable to see the configuration search schema mappings in SharePoint Online
User impact: Admins may have been unable to see the configuration search schema mappings in SharePoint Online.
More info: As a workaround, administrators may have been able to refresh the affected SharePoint Online search configuration settings by opening them, making any small update, and saving them again. This triggered the configuration settings to be rewritten and may have provided immediate relief whilst we developed a long-term fix.
Final status: We've confirmed that the deployment and backfill activities have completed successfully, and service monitoring indicates that the impact has been remediated.
Scope of impact: This issue may have affected any admin attempting to configure search schema mappings in SharePoint Online.
Start time: Monday, June 8, 2026, at 3:50 AM UTC
End time: Wednesday, July 29, 2026, at 11:58 PM UTC
Root cause: A recent migration introduced a configuration issue, resulting in a regression that was causing impact.
Next steps:
- We're reviewing our migration procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| 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
|
|---|
|
CP1430225 - We’ve identified an issue with Microsoft 365 Copilot spending alerts
| Status: | investigationSuspended |
|---|
| Start Time: | Thu Jul 16 18:27:46 2026 |
|---|
| End Time: | Thu Jul 30 18:19:13 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 30 18:19:50 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 30 18:19:46 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.
Final status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
|
|---|
|
| Time: | Thu 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.
|
|---|
|
MO1442357 - Admins may be unable to export reports to comma separated values (CSVs) in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 21 20:00:00 2026 |
|---|
| End Time: | Wed Jul 29 23:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 30 16:10:07 2026 |
|---|
| Root Cause: | A recent update to the CSV export pipeline introduced an error that resulted in large CSV exports potentially failing under certain conditions.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 30 14:01:41 2026 |
|---|
| Description: | Title: Admins may be unable to export reports to comma separated values (CSVs) in the Microsoft 365 admin center
User impact: Admins may have been unable to export reports to CSVs in the Microsoft 365 admin center.
More info: This issue affected export to CSV operations, such as exporting Active Users, Group Memberships, and Role Assignments. Admins encountered an error that stated, "We were sorry, something went wrong. Please try refreshing the page in a few minutes."
Final status: We've confirmed that the fix deployment has completed sooner than anticipated and have confirmed that it has resolved the event through service health telemetry.
Scope of impact: This issue affected admins performing export operations of large CSVs from the Microsoft 365 admin center.
Start time: Wednesday, July 22, 2026, at 12:00 AM UTC
End time: Thursday, July 30, 2026, at 3:00 AM UTC
Root cause: A recent update to the CSV export pipeline introduced an error that resulted in large CSV exports potentially failing under certain conditions.
Next steps: - We're reviewing the responsible CSV export pipeline update to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 29 13:46:11 2026 |
|---|
| Description: | Title: Admins may be unable to export reports to comma separated values (CSVs) in the Microsoft 365 admin center
User impact: Admins may be unable to export reports to CSVs in the Microsoft 365 admin center.
More info: This issue affects export to CSV operations, such as exporting Active Users, Group Memberships, and Role Assignments. Admins encounter an error that states, "We are sorry, something went wrong. Please try refreshing the page in a few minutes."
Current status: We've identified a recent update to the CSV export pipeline has introduced an error that's resulting in large CSV exports potentially failing under certain conditions. We've developed a fix to restore the previous behavior used by the export controller and validated it resolves the failures. We've scheduled the fix for deployment and anticipate it will resolve the issue by Tuesday, August 4, 2026.
Scope of impact: This issue affects admins performing export operations of large CSVs from the Microsoft 365 admin center.
Start time: Wednesday, July 22, 2026, at 12:00 AM UTC
Root cause: A recent update to the CSV export pipeline has introduced an error that's resulting in large CSV exports potentially failing under certain conditions.
Next update by: Tuesday, August 4, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jul 29 12:40:20 2026 |
|---|
| Description: | Title: Admins can't export the Active Users report in the Microsoft 365 admin center
User impact: Admins can't export the Active Users report in the Microsoft 365 admin center.
More info: Admins encounter an error that states, "We are sorry, something went wrong. Please try refreshing the page in a few minutes."
Current status: We're investigating a potential issue with Active User report exports in the Microsoft 365 admin center and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
TM1442034 - Some users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 29 03:29:23 2026 |
|---|
| End Time: | Thu Jul 30 13:06:01 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jul 30 13:20:39 2026 |
|---|
| Root Cause: | A recent service update contained a code regression, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 30 13:20:36 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users
User impact: Users may have been unable to create or publish Microsoft Teams town hall or webinar events that included guest users.
Final status: We've corrected our fix, deployed it to the affected environment, and confirmed internally that impact is remediated
Scope of impact: Impact was specific to some users attempting to create or publish Microsoft Teams town hall or webinar events that included guest users.
Start time: Tuesday, July 28, 2026, at 4:02 PM UTC
End time: Wednesday, July 29, 2026, at 9:30 PM UTC
Root cause: A recent service update contained a code regression, which resulted in impact.
Next steps: We're reviewing and improving our service update validation procedure to detect and prevent similar code issues in future updates.
This is the final update for this event.
|
|---|
|
| Time: | Wed Jul 29 13:14:54 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users
User impact: Users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users.
Current status: We've completed the validation of our fix and started deployment to a subset of the affected environment, although the deployment failed to initiate as expected. We're working to address the issues preventing our deployment from initiating so that we can apply our fix and remediate impact as soon as possible.
Scope of impact: Impact is specific to some users attempting to create or publish Microsoft Teams town hall or webinar events that include guest users.
Start time: Tuesday, July 28, 2026, at 4:02 PM UTC
Root cause: A recent service update contains a code regression, which is resulting in impact.
Next update by: Thursday, July 30, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 09:51:49 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users
User impact: Users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users.
Current status: We're in the final stages of validating the fix and expect to share a validation completion timeline as part of our next update. Once completed, we'll test the fix to confirm it resolves impact and then proceed with deployment across all affected environments.
Scope of impact: Impact is specific to some users attempting to create or publish Microsoft Teams town hall or webinar events that include guest users.
Start time: Tuesday, July 28, 2026, at 4:02 PM UTC
Root cause: A recent standard service update contains a code regression, which is resulting in impact.
Next update by: Wednesday, July 29, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 06:35:40 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users
User impact: Users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users.
Current status: We're continuing to validate the fix prior to deployment to ensure it successfully resolves the impact.
Scope of impact: Impact is specific to some users attempting to create or publish Microsoft Teams town hall or webinar events that include guest users.
Start time: Tuesday, July 28, 2026, at 4:02 PM UTC
Root cause: A recent standard service update contains a code regression, which is resulting in impact.
Next update by: Wednesday, July 29, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 05:04:21 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users
User impact: Users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users.
Current status: We've determined that a recent standard service update inadvertently contains a code regression, which is resulting in impact. We've developed a fix and are validating it prior to deployment.
Scope of impact: Impact is specific to some users attempting to create or publish Microsoft Teams town hall or webinar events that include guest users.
Start time: Tuesday, July 28, 2026, at 4:02 PM UTC
Root cause: A recent standard service update inadvertently contains a code regression, which is resulting in impact.
Next update by: Wednesday, July 29, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Wed Jul 29 03:32:00 2026 |
|---|
| Description: | Title: Some users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users
User impact: Users may be unable to create or publish Microsoft Teams town hall or webinar events that include guest users.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users attempting to create or publish Microsoft Teams town hall or webinar events that include guest users.
Next update by: Wednesday, July 29, 2026, at 9:30 AM UTC
|
|---|
|
EX1443140 - Users may experience issues when accessing their mailbox via one or more Exchange Online connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 30 11:59:05 2026 |
|---|
| End Time: | Thu Jul 30 12:48:31 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 30 12:54:20 2026 |
|---|
| Root Cause: | A portion of supporting infrastructure for Exchange Online had become unhealthy resulting this event.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 30 12:54:17 2026 |
|---|
| Description: | Title: Users may experience issues when accessing their mailbox via one or more Exchange Online connection methods
User impact: Users may have experienced issues when accessing their mailbox via one or more Exchange Online connection methods.
Final status: A portion of supporting infrastructure for Exchange Online had become unhealthy. Our automated recovery system repaired this problem, and we confirmed that service was restored after monitoring the environment.
Scope of impact: Users may have experienced errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Start time: Thursday, July 30, 2026, at 3:22 PM UTC
End time: Thursday, July 30, 2026, at 4:39 PM UTC
Root cause: A portion of supporting infrastructure for Exchange Online had become unhealthy resulting this event.
Next steps: We'll continue to monitor the service to ensure it remains in a healthy state.
This is the final update for this event.
|
|---|
|
| Time: | Thu Jul 30 11:59:40 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.
|
|---|
|
PB1443105 - Some users may be unable to access Plan artifacts and PowerTable sheets within shared reports in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jul 30 10:42:45 2026 |
|---|
| End Time: | Thu Jul 30 11:37:03 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jul 30 11:39:33 2026 |
|---|
| Root Cause: | A recently deployed feature update meant to introduce connection validations may have prevented some users from accessing Plan artifacts and PowerTable sheets within shared reports in Microsoft Fabric.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jul 30 11:39:30 2026 |
|---|
| Description: | Title: Some users may be unable to access Plan artifacts and PowerTable sheets within shared reports in Microsoft Fabric
User impact: Users may have been unable to access Plan artifacts and PowerTable sheets within shared reports in Microsoft Fabric.
Final status: We've determined that a recently deployed feature update meant to introduce connection validations may have prevented some users from accessing Plan artifacts and PowerTable sheets within shared reports in Microsoft Fabric. We've disabled this feature update and confirmed using our internal telemetry data that impact is remediated.
Scope of impact: Some users attempting to access Plan artifacts and PowerTable sheets within shared reports in Microsoft Fabric were impacted.
Start time: Thursday, July 23, 2026, at 12:00 PM UTC
End time: Thursday, July 30, 2026, at 2:43 PM UTC
Root cause: A recently deployed feature update meant to introduce connection validations may have prevented some users from accessing Plan artifacts and PowerTable sheets within shared reports in Microsoft Fabric.
Next steps: - We're reviewing and improving our feature update validation procedure to detect and prevent similar issues before they cause impact in the future.
This is the final update for this event.
|
|---|
|
| Time: | Thu Jul 30 10:55:38 2026 |
|---|
| Description: | Title: Users may be unable to access Plan artifacts in Microsoft Fabric
User impact: Users may have been unable to access Plan artifacts in Microsoft Fabric.
Current status: We've investigated a problem with Microsoft Fabric in which users may have been unable to access Plan artifacts, 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.
|
|---|
|
CW1442650 - Some users may receive an error when they initiate Microsoft 365 Copilot Chat requests
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 29 18:45:00 2026 |
|---|
| End Time: | Wed Jul 29 21:59:40 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 29 22:01:03 2026 |
|---|
| Root Cause: | A recent configuration change led to network traffic being incorrectly routed, which led to impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 29 22:00:59 2026 |
|---|
| Description: | Title: Some users may receive an error when they initiate Microsoft 365 Copilot Chat requests
User impact: Users may have received an error when they initiated Microsoft 365 Copilot Chat requests.
More info: The error that impacted users may have received stated "Something went wrong, please try again."
Final status: Our investigation determined that the previously mentioned configuration change led to network traffic being incorrectly routed, which led to impact. After reverting this change, we monitored service health telemetry and confirmed impact is remediated.
Scope of impact: Some users attempting to initiate Microsoft 365 Copilot Chat requests may have been impacted.
Start time: Wednesday, July 29, 2026, at 10:45 PM UTC
End time: Thursday, July 30, 2026, at 1:15 AM UTC
Root cause: A recent configuration change led to network traffic being incorrectly routed, which led to impact.
Next steps:
- To help prevent similar impact in the future, we're further reviewing the underlying reason this configuration change let to network traffic being incorrectly routed.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 29 20:36:52 2026 |
|---|
| Description: | Title: Some users may receive an error when they initiate Microsoft 365 Copilot Chat requests
User impact: Users may receive an error when they initiate Microsoft 365 Copilot Chat requests.
More info: The error that impacted users may receive states "Something went wrong, please try again."
Current status: We've been alerted to an issue where some users may receive an error stating "Something went wrong, please try again." when they initiate Microsoft 365 Copilot Chat requests. While we investigate the issue to confirm the underlying root cause, we're preparing to revert a recent configuration change, which we're anticipating may be able to restore service for affected users.
Scope of impact: Some users attempting to initiate Microsoft 365 Copilot Chat requests may be impacted. This section may be updated as our investigation continues.
Start time: Wednesday, July 29, 2026, at 10:45 PM UTC
Next update by: Thursday, July 30, 2026, at 2:30 AM UTC
|
|---|
|
TM1442237 - Some admins' Microsoft Teams Rooms (MTR) devices may unexpectedly show as unmonitored in the Pro Management Portal
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 29 10:21:17 2026 |
|---|
| End Time: | Wed Jul 29 22:00:09 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 29 22:00:58 2026 |
|---|
| Root Cause: | High resource utilization within portions of the supporting infrastructure resulted in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 29 22:00:55 2026 |
|---|
| Description: | Title: Some admins' Microsoft Teams Rooms (MTR) devices may unexpectedly show as unmonitored in the Pro Management Portal
User impact: Admins' MTR devices may have unexpectedly showed as unmonitored in the Pro Management Portal.
More info: Admins could’ve used the Microsoft Teams admin center or vendor portal to manage their devices.
Final status: We’ve rebalanced affected service traffic and deployed a code fix to clear the backlog of device calls. We’ve confirmed through service telemetry that the issue is no longer occurring.
Scope of impact: Some admins in North America who viewed MTR devices in the Pro Management Portal were impacted.
Start time: Tuesday, July 28, 2026, at 8:29 PM UTC
End time: Thursday, July 30, 2026, at 12:30 AM UTC
Root cause: High resource utilization within portions of the supporting infrastructure resulted in the impact.
Next steps: We’re continuing our investigation to determine what caused the high resource utilization and improve our ability to detect and prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 29 18:09:44 2026 |
|---|
| Description: | Title: Some admins' Microsoft Teams Rooms (MTR) devices may unexpectedly show as unmonitored in the Pro Management Portal
User impact: Admins' MTR devices may unexpectedly show as unmonitored in the Pro Management Portal.
More info: Admins can use the Microsoft Teams admin center or vendor portal to manage devices.
Current status: We continue to monitor the effectiveness of the load rebalancing using our service-side telemetry. In parallel we're applying additional code fixes to address a backlog of device calls to the service.
Scope of impact: Some admins based in North America that are viewing MTR devices in the Pro Management Portal may be impacted.
Start time: Tuesday, July 28, 2026, at 8:29 PM UTC
Root cause: Portions of the supporting infrastructure are experiencing high resource utilization, which is resulting in the impact.
Next update by: Thursday, July 30, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Jul 29 16:14:15 2026 |
|---|
| Description: | Title: Some admins' Microsoft Teams Rooms (MTR) devices may unexpectedly show as unmonitored in the Pro Management Portal
User impact: Admins' MTR devices may unexpectedly show as unmonitored in the Pro Management Portal.
More info: Admins can use the Microsoft Teams admin center or vendor portal to manage devices.
Current status: Our work to rebalance the supporting infrastructure is ongoing. We're using service-side telemetry to monitor and validate the effectiveness of the rebalancing.
Scope of impact: Some admins based in North America that are viewing MTR devices in the Pro Management Portal may be impacted.
Start time: Tuesday, July 28, 2026, at 8:29 PM UTC
Root cause: Portions of the supporting infrastructure are experiencing high resource utilization resulting in the impact.
Next update by: Wednesday, July 29, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 14:03:57 2026 |
|---|
| Description: | Title: Some admins' Microsoft Teams Rooms (MTR) devices may unexpectedly show as unmonitored in the Pro Management Portal
User impact: Admins' MTR devices may unexpectedly show as unmonitored in the Pro Management Portal.
More info: Admins can use the Microsoft Teams admin center or vendor portal to manage devices.
Current status: We've identified that portions of the supporting infrastructure are experiencing high resource utilization, which is resulting in a traffic flow issue. We're pinpointing the best way to balance the supporting infrastructure as a mitigation pathway.
Scope of impact: Some admins based in North America that are viewing MTR devices in the Pro Management Portal may be impacted.
Next update by: Wednesday, July 29, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 11:49:09 2026 |
|---|
| Description: | Title: Some admins' Microsoft Teams Rooms (MTR) devices may unexpectedly show as unmonitored in the Pro Management Portal
User impact: Admins' MTR devices may unexpectedly show as unmonitored in the Pro Management Portal.
More info: Admins can use the Microsoft Teams admin center or vendor portal to manage devices.
Current status: We're continuing to review the provided device logs to better understand this issue and determine our next troubleshooting steps.
Scope of impact: Some admins based in North America that are viewing MTR devices in the Pro Management Portal may be impacted.
Next update by: Wednesday, July 29, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 10:24:52 2026 |
|---|
| Description: | Title: Some admins' Microsoft Teams Rooms (MTR) devices may unexpectedly show as unmonitored in the Pro Management Portal
User impact: Admins' MTR devices may unexpectedly show as unmonitored in the Pro Management Portal.
More info: Admins can use the Microsoft Teams admin center or vendor portal to manage devices.
Current status: We're reviewing support provided details to isolate the root cause and develop a remediation plan.
Scope of impact: Some admins based in North America that are viewing MTR devices in the Pro Management Portal may be impacted.
Next update by: Wednesday, July 29, 2026, at 4:30 PM UTC
|
|---|
|
CP1442025 - Some users may be unable to access Copilot Cowork from the Cowork toggle in Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jul 29 03:10:16 2026 |
|---|
| End Time: | Wed Jul 29 17:48:35 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 29 18:06:16 2026 |
|---|
| Root Cause: | A latency issue in the upstream dependency of the Cowork access flow was resulting in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 29 18:06:13 2026 |
|---|
| Description: | Title: Some users may be unable to access Copilot Cowork from the Cowork toggle in Microsoft 365 Copilot
User impact: Users may have been unable to access Copilot Cowork from the Cowork toggle in Copilot.
More info: This issue prevented users from seeing the Cowork toggle to access this functionality. As a workaround, affected users could access the Copilot Cowork feature directly through the URL, https://m365.cloud.microsoft/cowork.
Final status: We've confirmed the fix to address the remaining impact to new users has completed and after monitoring our service health telemetry, we've verified that the associated failures have ceased and the impact is remediated.
Scope of impact: Some users who attempted to access Copilot Cowork from the Cowork toggle in Copilot may have been impacted.
Start time: Tuesday, July 28, 2026, at 9:15 AM UTC
End time: Wednesday, July 29, 2026, at 9:37 PM UTC
Root cause: A latency issue in the upstream dependency of the Cowork access flow was resulting in the impact.
Next steps:
- We're continuing to review how we leverage our dependency to ensure the Cowork access flow is adequately bolstered against upstream latency to prevent this issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jul 29 16:07:07 2026 |
|---|
| Description: | Title: Some users may be unable to access Copilot Cowork from the Cowork toggle in Microsoft 365 Copilot
User impact: Users may be unable to access Copilot Cowork from the Cowork toggle in Copilot.
More info: This issue prevents users from seeing the Cowork toggle to access this functionality. As a workaround, affected users can access the Copilot Cowork feature directly through the URL, https://m365.cloud.microsoft/cowork.
Current status: We've confirmed that a latency issue in the upstream dependency of the Cowork access flow is resulting in the impact. We've deployed a fix which has addressed this issue for existing users, and we're in the process of deploying a code fix to address this for new users in order to fully remediate the event. We anticipate that this deployment will be completed by our next scheduled update.
Scope of impact: Some users attempting to access Copilot Cowork from the Cowork toggle in Copilot may be impacted.
Start time: Tuesday, July 28, 2026, at 9:15 AM UTC
Root cause: A latency issue in the upstream dependency of the Cowork access flow is resulting in the impact.
Next update by: Wednesday, July 29, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 13:24:45 2026 |
|---|
| Description: | Title: Some users may be unable to access Copilot Cowork from the Cowork toggle in Microsoft 365 Copilot
User impact: Users may be unable to access Copilot Cowork from the Cowork toggle in Copilot.
More info: This issue prevents users from seeing the Cowork toggle to access this functionality. As a workaround, affected users can access the Copilot Cowork feature directly through the URL, https://m365.cloud.microsoft/cowork.
Current status: Our investigation has led us to suspect that an issue with an upstream dependency in the Cowork access flow is resulting in the impact. We're applying a change to route traffic through an alternate flow to avoid the dependency we believe is experiencing the issue in an effort to mitigate the impact while we confirm the root cause.
Scope of impact: Some users attempting to access Copilot Cowork from the Cowork toggle in Copilot may be impacted.
Next update by: Wednesday, July 29, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 11:28:47 2026 |
|---|
| Description: | Title: Some users may be unable to access Copilot Cowork from the Cowork toggle in Microsoft 365 Copilot
User impact: Users may be unable to access Copilot Cowork from the Cowork toggle in Copilot.
More info: This issue prevents users from seeing the Cowork toggle to access this functionality. As a workaround, affected users can access the Copilot Cowork feature directly through the URL, https://m365.cloud.microsoft/cowork.
Current status: We're reviewing entitlement and discoverability service telemetry to isolate the source of impact and develop a mitigation strategy.
Scope of impact: Some users attempting to access Copilot Cowork from the Cowork toggle in Copilot may be impacted.
Next update by: Wednesday, July 29, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 09:29:28 2026 |
|---|
| Description: | Title: Some users are unable to access Copilot Cowork in Microsoft 365 Copilot chat
User impact: Users are unable to access Copilot Cowork in Microsoft 365 Copilot chat.
More info: As a workaround, affected users can access the Copilot Cowork feature directly via the URL.
Current status: We're continuing our review of collected session IDs, trace IDs, and other diagnostic details to determine our next troubleshooting steps, in order to mitigate impact.
Scope of impact: Your organization is affected by this event, and some users attempting to access Copilot Cowork in Microsoft 365 Copilot chat are impacted.
Next update by: Wednesday, July 29, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 07:08:27 2026 |
|---|
| Description: | Title: Some users are unable to access Copilot Cowork in Microsoft 365 Copilot chat
User impact: Users are unable to access Copilot Cowork in Microsoft 365 Copilot chat.
Current status: We're investigating whether a recent regression is causing the Copilot Cowork feature tab to be missing for multiple users in Microsoft 365 Copilot chat. We're gathering session IDs, trace IDs, and other diagnostic details to determine our next steps.
Scope of impact: Your organization is affected by this event, and some users attempting to access Copilot Cowork in Microsoft 365 Copilot chat are impacted.
Next update by: Wednesday, July 29, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Wed Jul 29 05:22:19 2026 |
|---|
| Description: | Title: Some users are unable to access Copilot Cowork in Microsoft 365 Copilot chat
User impact: Users are unable to access Copilot Cowork in Microsoft 365 Copilot chat.
Current status: We're investigating reports that the Copilot Cowork option is missing for multiple users in Microsoft 365 Copilot chat. We're reviewing Cowork visibility settings, usage-based billing policy assignments, and entitlement configuration to determine why the Cowork experience isn't appearing as expected for affected users.
Scope of impact: Your organization is affected by this event, and some users attempting to access Copilot Cowork in Microsoft 365 Copilot chat are impacted.
Next update by: Wednesday, July 29, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Wed Jul 29 03:13:17 2026 |
|---|
| Description: | Title: Some users are unable to access Copilot Cowork in Microsoft 365 Copilot chat
User impact: Users are unable to access Copilot Cowork in Microsoft 365 Copilot chat.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to access Copilot Cowork in Microsoft 365 Copilot chat are impacted.
Next update by: Wednesday, July 29, 2026, at 9:30 AM UTC
|
|---|
|
TM1441044 - Users' email messages sent to Microsoft Teams channels may have been incorrectly formatted
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 20 10:23:00 2026 |
|---|
| End Time: | Tue Jul 28 03:13:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jul 29 04:53:28 2026 |
|---|
| Root Cause: | A recent build deployment introduced a code regression that created a compatibility issue in how plain-text email content was processed, resulting in line breaks not rendering as expected within Microsoft Teams channel messages.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jul 29 04:52:49 2026 |
|---|
| Description: | Title: Users' email messages sent to Microsoft Teams channels may have been incorrectly formatted
User impact: Users' email messages sent to Microsoft Teams channels may have been incorrectly formatted.
More info: Specifically, line breaks in affected email messages may have been missing when sent to Microsoft Teams channel email addresses, causing the messages to appear as a single block of text within the channel. This issue affected plain text messages; HTML-formatted messages weren't affected.
Final status: We've determined that a recent build deployment introduced a code regression affecting how plain-text email formatting was processed, resulting in line breaks not rendering as expected within Microsoft Teams channel messages. We've reverted the change and confirmed following a period of monitoring service health telemetry, that service functionality has been restored. In addition, we've received confirmation from your representatives that impact has been remediated and newly processed email messages are displaying correctly.
Scope of impact: Some users sending plain text email messages to Microsoft Teams channel email addresses may have been impacted.
Start time: Monday, July 20, 2026, at 2:23 PM UTC
End time: Tuesday, July 28, 2026, at 7:13 AM UTC
Root cause: A recent build deployment introduced a code regression that created a compatibility issue in how plain-text email content was processed, resulting in line breaks not rendering as expected within Microsoft Teams channel messages.
Next steps:
- We're reviewing our change testing and validation procedures to help identify similar code regressions earlier and prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jul 28 04:21:27 2026 |
|---|
| Description: | Title: Users' email messages sent to Microsoft Teams channels may not be formatted correctly
User impact: Users' email messages sent to Microsoft Teams channels may not be formatted correctly.
More info: Specifically, line breaks in the email messages may be missing when sent to Microsoft Teams channel email addresses, displaying as a single block of text in the channel. This issue affects plain text messages; HTML-formatted messages aren't affected.
Current status: We're awaiting confirmation from a sample of affected users that reverting the aforementioned update successfully resolved the issue. New email messages sent to Microsoft Teams channels are expected to display correctly following the revert; however, messages processed before the revert aren't expected to be corrected retrospectively.
Scope of impact: Some users sending plain text email messages to Microsoft Teams channel email addresses may be impacted.
Next update by: Wednesday, July 29, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Jul 28 01:28:11 2026 |
|---|
| Description: | Title: Users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting
User impact: Users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting.
More info: Specifically, the line breaks are formatted correctly when the email is composed, but when it sends to the Microsoft Teams channel email address, the formatting is incorrect and not upheld.
Current status: We've completed the rollback of the update that we suspected was causing impact; however, after initial testing with a subset of affected users, it's been reported that impact still persists. We're working further with the subset of users to validate the latest test results to help inform our next troubleshooting steps.
Scope of impact: Some users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting. This section may be updated as our investigation continues.
Next update by: Tuesday, July 28, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Jul 27 22:41:58 2026 |
|---|
| Description: | Title: Users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting
User impact: Users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting.
More info: Specifically, the line breaks are formatted correctly when the email is composed but when it sends to the Microsoft Teams channel email address the formatting is incorrect and not upheld.
Current status: We're in the process of rolling back the build we believe may be responsible for this issue to determine if this allows line breaks to display correctly in email messages sent to Microsoft Teams channels.
Scope of impact: Some users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting. This section may be updated as our investigation continues.
Next update by: Tuesday, July 28, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Mon Jul 27 22:07:02 2026 |
|---|
| Description: | Title: Users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting
User impact: Users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting.
More info: Specifically, the line breaks are formatted correctly when the email is composed but when it sends to the Microsoft Teams channel email address the formatting is incorrect and not upheld.
Current status: We're analyzing a sample email message in order to identify why line break characters are not displaying correctly when the message is sent to a Microsoft Teams channel. We've identified a recent build deployment that we believe may be responsible for the issue and are rolling it back in an effort to alleviate impact and validate our root cause theory.
Scope of impact: Some users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting. This section may be updated as our investigation continues.
Next update by: Tuesday, July 28, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Jul 27 21:39:15 2026 |
|---|
| Description: | Title: Users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting
User impact: Users' email messages sent to Microsoft Teams channel email addresses may not display the correct formatting.
More info: Specifically, the line breaks are formatted correctly when the email is composed but when it sends to the Microsoft Teams channel email address the formatting is incorrect and not upheld.
Current status: We're investigating a potential issue with incorrect line breaks in Microsoft Teams and are 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: | investigationSuspended |
|---|
| Start Time: | Mon Jul 20 16:27:05 2026 |
|---|
| End Time: | Tue Jul 28 20:05:02 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 28 20:26:35 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 28 20:06:58 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.
Final status: We’ve confirmed that the aforementioned in-app banner is rolling out and will be reflecting in Organizational Messages experiences (under Reports in Microsoft 365 admin center) by end of Wednesday, July 29, 2026. Admins may go to the following link to see this in-app banner: https://learn.microsoft.com/en-us/microsoft-365/admin/misc/organizational-messages-microsoft-365?view=o365-worldwide
This is the final update for the event.
|
|---|
|
| 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
|
|---|
|
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 Jul 28 11:42:48 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 Jul 28 11:42:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jun 23 10:59:21 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jun 18 20:09:52 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 17 06:55:14 2026 |
|---|
| Description: | Title: Some users may have seen incorrect presence status information in Microsoft Teams
User impact: Some users may have seen incorrect presence status information in Microsoft Teams.
Final status: We have confirmed through our telemetry and from some of the previously affected customers that the issue is now resolved.
Scope of impact: This issue primarily affected users in EMEA, and users in other regions may have experienced impact when interacting with the affected users.
Start time: Wednesday, June 17, 2026, at 8:30 AM UTC
End time: Wednesday, June 17, 2026, at 9:35 AM UTC
Root cause: The Unified Presence Service (UPS) is served through multiple data centers globally for capacity and resiliency reasons. To avoid capacity pressure with an ever-increasing service load, we have been making the long-term architectural change to add an additional data center in the Europe region to process Presence requests. As part of this, the new data center needed to be added to the Azure Traffic Manager (ATM) set-up in preparation for when it was ready to go live.
A code bug in the configuration and subsequent miss in the review process resulted in the bad rollout file that was published to ATM. This resulted in inadvertently overwriting/replacing the existing full EMEA configuration that included all the existing data centers which were handling traffic, rather than being extended on top of the existing configuration. This meant that the service removed all the existing data centers from the ATM set-up for Presence and just left the newly added region, which was not in an operational state yet. As such, there were no reachable endpoints for Presence-related requests.
Since Azure Front Door (AFD) has caching for last known good DNS endpoints, we had some protection for client-side presence scenarios and only when a user’s caches expired would they have seen impact.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We've provided a Post-Incident Report for this incident. Additionally, we'll be updating the Post-Incident Report on a monthly basis, for the next six months, to show the status of the Next Steps. The first update was provided on July 28, 2026. The next update will be provided by August 31. 2026.
|
|---|
|
| Time: | Wed Jun 17 06:32:03 2026 |
|---|
| Description: | Since we deployed the fix, we're observing a steady improvement in service recovery. We'll continue to monitor service telemetry for complete recovery.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 17 06:11:20 2026 |
|---|
| Description: | We’ve identified that a recent Teams traffic routing change introduced a misconfiguration, which unexpectedly resulted in impact. We’ve deployed a fix and are closely monitoring service telemetry to ensure full recovery.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 17 05:56:03 2026 |
|---|
| Description: | Title: Some users may see incorrect presence status information in Microsoft Teams
User impact: Some users may see incorrect presence status information in Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: This issue is primarily affecting users in EMEA, and users in other regions may experience impact when interacting with the affected users.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 05:16:10 2026 |
|---|
| Description: | Title: Possible delays or problems when accessing Microsoft Teams
User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
MO1441391 - Admins couldn't locate or disable the MailerLite and Miro connectors in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jul 28 07:09:22 2026 |
|---|
| End Time: | Tue Jul 28 08:44:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jul 28 10:28:16 2026 |
|---|
| Root Cause: | A recent configuration change introduced to optimize connector manifest management and improve performance affected how connector metadata was surfaced after connector configuration data was reorganized into separate groupings, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jul 28 10:27:53 2026 |
|---|
| Description: | Title: Admins couldn't locate or disable the MailerLite and Miro connectors in the Microsoft 365 admin center
User impact: Admins couldn't locate or disable the MailerLite and Miro connectors in the Microsoft 365 admin center.
More info: The MailerLite and Miro connectors remained available to users in Microsoft Copilot; however, affected admins were unable to locate these connectors within the Microsoft 365 admin center when attempting to manage, restrict, or disable them.
Final status: We've determined that a recent configuration change introduced to optimize connector manifest management and improve performance affected how connector metadata was surfaced after connector configuration data was reorganized into separate groupings, resulting in the MailerLite and Miro connectors not appearing as expected for administrative management. We've confirmed that deployment of our corrective changes have completed and normal service functionality has been restored.
Scope of impact: Impact was specific to admins attempting to manage or disable the affected MailerLite and Miro connectors within the Microsoft 365 admin center.
Start time: Thursday, July 23, 2026, at 1:00 PM UTC
End time: Tuesday, July 28, 2026, at 12:44 PM UTC
Root cause: A recent configuration change introduced to optimize connector manifest management and improve performance affected how connector metadata was surfaced after connector configuration data was reorganized into separate groupings, which resulted in impact.
Next steps:
- We're reviewing our configuration change and related validation procedures to help prevent similar problems in the future.
this is the final update for the event.
|
|---|
|
| Time: | Tue Jul 28 09:19:03 2026 |
|---|
| Description: | Title: Admins can't locate or disable the MailerLite and Miro connectors in the Microsoft 365 admin center
User impact: Admins can't locate or disable the MailerLite and Miro connectors in the Microsoft 365 admin center.
More info: The MailerLite and Miro connectors remain available to users in Microsoft Copilot; however, affected admins may be unable to locate these connectors within the Microsoft 365 admin center when attempting to manage, restrict, or disable them.
Current status: We're continuing to deploy configuration changes to restore the expected visibility and manageability of the affected connectors within the Microsoft 365 admin center. We expect deployment of these changes to be completed by our next scheduled update.
Scope of impact: Impact is specific to admins attempting to manage or disable the affected MailerLite and Miro connectors within the Microsoft 365 admin center. This section may be updated as our investigation continues.
Start time: Thursday, July 23, 2026, at 1:00 PM UTC
Next update by: Tuesday, July 28, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Tue Jul 28 07:12:42 2026 |
|---|
| Description: | Title: Admins can't locate or disable the MailerLite and Miro connectors in the Microsoft 365 admin center
User impact: Admins can't locate or disable the MailerLite and Miro connectors in the Microsoft 365 admin center.
More info: The MailerLite and Miro connectors remain available to users in Microsoft Copilot; however, affected admins may be unable to locate these connectors within the Microsoft 365 admin center when attempting to manage, restrict, or disable them.
Current status: We're investigating an issue affecting connector management in the Microsoft 365 admin center. We've reproduced the behavior and have initiated configuration changes to restore the expected management experience for the affected connectors. As part of this effort, we're reverting recent changes and applying updated configuration changes to help ensure both connectors can be managed as expected.
Scope of impact: Impact is specific to admins attempting to manage or disable the affected MailerLite and Miro connectors within the Microsoft 365 admin center. This section may be updated as our investigation continues.
Next update by: Tuesday, July 28, 2026, at 1:30 PM UTC
|
|---|
|
EX1435168 - Some users may be unable to view location and subject details for other users' Exchange Online calendar items
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 13 20:00:00 2026 |
|---|
| End Time: | Mon Jul 27 16:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 27 17:36:55 2026 |
|---|
| Root Cause: | A recent Exchange Online service change introduced a permissions issue that prevented some users from viewing location and subject details for other users' calendars, which resulted in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 27 16:32:32 2026 |
|---|
| Description: | Title: Some users may be unable to view location and subject details for other users' Exchange Online calendar items
User impact: Users may have been unable to view location and subject details for other users' Exchange Online calendar items.
More info: Affected users may have only been able to view the free/busy availability of other users' Exchange Online calendars despite having been configured to also view location and subject details for calendar items.
Final status: We've confirmed that the deployment of the solution developed to correct the impacting permissions issue has completed, and we've validated with a subset of affected users that the impact has been resolved by our actions.
Scope of impact: Some users who attempted to view Exchange Online calendar items for users' calendars for which they were configured to have access may have been impacted.
Start time: Tuesday, July 14, 2026, at 12:00 AM UTC
End time: Monday, July 27, 2026, at 8:00 PM UTC
Root cause: A recent Exchange Online service change introduced a permissions issue that prevented some users from viewing location and subject details for other users' calendars, which resulted in the impact.
Next steps:
- We're reviewing our service change process 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: | 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
|
|---|
|
TM1440505 - Some users may have been unable to access Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 27 09:20:00 2026 |
|---|
| End Time: | Mon Jul 27 09:50:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jul 27 10:31:51 2026 |
|---|
| Root Cause: | A section of the service infrastructure responsible for processing Microsoft Teams access requests fell below our manageable service performance thresholds, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 27 10:30:41 2026 |
|---|
| Description: | Title: Some users may have been unable to access Microsoft Teams
User impact: Users may have been unable to access Microsoft Teams.
Final status: We've determined that a section of the service infrastructure responsible for processing Microsoft Teams access requests fell below our manageable service performance thresholds, which resulted in impact. While we were reviewing the issue and identifying corrective actions, the service returned to normal health and we've confirmed that the impact has been resolved.
Scope of impact: Some users located in North America attempting to access Microsoft Teams may have been impacted.
Start time: Monday, July 27, 2026, at 1:20 PM UTC
End time: Monday, July 27, 2026, at 1:50 PM UTC
Root cause: A section of the service infrastructure responsible for processing Microsoft Teams access requests fell below our manageable service performance thresholds, which resulted 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: | Mon Jul 27 09:45:20 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft Teams
User impact: Users may be unable to access Microsoft Teams.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Some users located in North America attempting to access Microsoft Teams may be impacted.
Next update by: Monday, July 27, 2026, at 4:00 PM UTC
|
|---|
|
TM1438173 - Some users may have received incorrect notifications that Teams meeting recordings failed to upload to OneDrive.
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jul 17 06:53:00 2026 |
|---|
| End Time: | Mon Jul 27 07:00:46 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 27 07:02:57 2026 |
|---|
| Root Cause: | A recent service change introduced an issue within the recording processing workflow that caused intermittent connectivity failures when recording completion information was being processed.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 27 07:02:54 2026 |
|---|
| Description: | Title: Some users may have received incorrect notifications that Teams meeting recordings failed to upload to OneDrive.
User impact: Users may have received incorrect notifications that Teams meeting recordings failed to upload to OneDrive.
More info: Meeting recordings were uploaded successfully and remained accessible on OneDrive, however, affected users may have seen notifications in Teams stating that the recording upload failed even though the upload completed successfully.
Final status: We've confirmed, following a period of monitoring, that impact has been fully mitigated after deploying an updated service build containing the corrective changes.
Scope of impact: Any user attempting to access Teams meeting recordings may have received inaccurate upload failure notifications.
Start time: Friday, July 17, 2026, at 10:53 AM UTC
End time: Monday, July 27, 2026, at 1:34 AM UTC
Root cause: A recent service change introduced an issue within the recording processing workflow that caused intermittent connectivity failures when recording completion information was being processed.
Next steps:
- We're reviewing our deployment and provisioning procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| 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
|
|---|
|
MP1438577 - Admins may not have received alerts for Microsoft Purview Communication Compliance policies that contain conditions
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jul 20 22:00:00 2026 |
|---|
| End Time: | Mon Jul 27 02:30:00 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jul 27 05:53:04 2026 |
|---|
| Root Cause: | An unintended side effect of a policy management engine change caused the "contains words and phrases" condition to fail in newly created or edited policies, resulting in missed policy matches.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jul 27 05:52:45 2026 |
|---|
| Description: | Title: Admins may not have received alerts for Microsoft Purview Communication Compliance policies that contain conditions
User impact: Admins may not have received alerts for Microsoft Purview Communication Compliance policies that contain conditions.
More info: As a result of this issue, admins shouldn't have created or updated any Microsoft Purview Communication Compliance policies that contained conditions to avoid becoming impacted. Additionally, Data Loss Prevention (DLP) policy changes in Microsoft Purview may have not taken effect as expected until the issue was resolved.
Final status: We've monitored the affected service environment and confirmed that impact is no longer occurring.
Scope of impact: This issue may have affected any admin.
Start time: Tuesday, July 21, 2026, at 2:00 AM UTC
End time: Monday, July 27, 2026, at 9:52 AM UTC
Root cause: An unintended side effect of a policy management engine change caused the "contains words and phrases" condition to fail in newly created or edited policies, resulting in missed policy matches.
Next steps: We're reviewing our policy management change procedure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jul 27 02:23:24 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've completed the deployment of the configuration changes and corrective service updates to the affected service environment and we're monitoring to ensure it has the desired effect of resolving impact.
Scope of impact: This issue may affect any admin. This section may be updated as the investigation continues.
Estimated time to resolve: We anticipate impact to be resolved by Monday, July 27, 2026, at 10:00 AM UTC.
Next update by: Monday, July 27, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Sun Jul 26 18:09:44 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've completed validations of our configuration changes and corrective service updates and have initiated deployment to the affected service environment. We anticipate the deployment to be completed by our next scheduled update.
Scope of impact: This issue may affect any admin. This section may be updated as the investigation continues.
Estimated time to resolve: We anticipate impact to be resolved by Monday, July 27, 2026, at 7:00 AM UTC.
Next update by: Monday, July 27, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Sun Jul 26 11:37:23 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 prepare the configuration changes and corrective service updates for deployment, and our latest estimate is that we expect to complete the deployment by the time of our next communication update.
Scope of impact: This issue may affect any admin. This section may be updated as the investigation continues.
Next update by: Monday, July 27, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Sat Jul 25 11:16:16 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: The configuration changes and corrective service updates is taking longer than initially expected to apply, as we work to validate that the alterations won't cause any further problems within the service.
Scope of impact: This issue may affect any admin. This section may be updated as the investigation continues.
Next update by: Sunday, July 26, 2026, at 5:00 PM UTC
|
|---|
|
| 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: | serviceRestored |
|---|
| Start Time: | Tue Jul 21 15:45:00 2026 |
|---|
| End Time: | Sat Jul 25 14:57:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jul 25 15:37:23 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 an incorrect method, which resulted in status messages presenting as active instead of resolved for some communications.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jul 25 15:34:01 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 have seen inaccurate status information in the service health section in the Microsoft 365 admin center.
Final status: We've reverted the offending deployment and confirmed through monitoring service health telemetry that the impact has been remediated.
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 have been impacted.
Start time: Tuesday, July 21, 2026, at 7:45 PM UTC
End time: Saturday, July 25, 2026, at 6:57 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 an incorrect method, which resulted in status messages presenting as active instead of resolved for some communications.
Next steps:
- We're reviewing our update procedures to understand why impact to service health information wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Fri 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 365 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
|
|---|
|
TM1439027 - Some users may experience unreliable translated captions in Microsoft Teams meetings
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jul 25 09:40:00 2026 |
|---|
| End Time: | Sat Jul 25 09:55:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jul 25 11:57:34 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jul 25 11:49:50 2026 |
|---|
| Description: | Title: Some users may experience unreliable translated captions in Microsoft Teams meetings
User impact: Users may have experienced unreliable translated captions in Microsoft Teams meetings.
More info: Teams meeting transcription or translated caption functions may have not worked as expected for the affected users.
Final status: While we were in the process of analyzing service health telemetry to isolate the source of impact, 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: Impact was specific to some users attempting to use translated captions in Microsoft Teams meetings.
Start time: Saturday, July 25, 2026, at 1:40 PM UTC
End time: Saturday, July 25, 2026, at 1:55 PM UTC
Next steps:
- While the impact related to caption functionality self-resolved, we're reviewing telemetry and other data related to this event to better understand what caused the issue.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jul 25 10:13:01 2026 |
|---|
| Description: | Title: Some users may experience unreliable translated captions in Microsoft Teams meetings
User impact: Users may experience unreliable translated captions in Microsoft Teams meetings.
More info: Teams meeting transcription or translated caption functions may not work as expected for the affected users.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users attempting to use translated captions in Microsoft Teams meetings.
Next update by: Saturday, July 25, 2026, at 4:00 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.
|
|---|
|
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.
|
|---|
|
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.
|
|---|
|
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.
|
|---|
|
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
|
|---|
|
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.
|
|---|
|
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.
|
|---|
|
|
