Microsoft's Incident Report for PennO365
Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within
the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh
this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this
list. Additionally you can check Microsoft's
status page for current service status messages.
The last extract was taken on Mon Jun 29 01:15:07 2026.
PP1407860 - powerappsforadmins connector flows and apps failing
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 28 09:55:33 2026 |
|---|
| End Time: | Sun Jun 28 15:51:15 2026 |
|---|
| Service: | Power Platform |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sun Jun 28 15:51:16 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 28 15:51:16 2026 |
|---|
| Description: | Title: powerappsforadmins connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the powerappsforadmins connector.
Final status: After monitoring connector telemetry, it has been observed that functionality to flows and apps using powerappsforadmins connectors has recovered.
Preliminary Root Cause: The external service used by the powerappsforadmins connector was unable to handle requests from Microsoft’s connector services.
Next Steps: We continually review our monitoring to reduce detection time and notify customers of issues with external services.
|
|---|
|
| Time: | Sun Jun 28 14:29:06 2026 |
|---|
| Description: | Title: powerappsforadmins connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the powerappsforadmins connector.
Current Status: We are monitoring an external issue in which some users are receiving errors when using flows and apps with the powerappsforadmins connector.
Users may have received HTTP 5xx errors. Users may have received an email notice that their flows failed. Users may have found that their apps were unresponsive.
|
|---|
|
TM1406826 - Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 26 14:42:00 2026 |
|---|
| End Time: | Sun Jun 28 00:02:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jun 28 00:19:14 2026 |
|---|
| Root Cause: | A recent service side change related to Microsoft Teams Rooms devices caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 28 00:17:52 2026 |
|---|
| Description: | Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
User impact: Users may have been unable to sign into MTR on Windows devices.
Final status: After we reverted the impacting change and monitored the affected infrastructure, we validated with a subset of affected users and service side telemetry that impact was resolved by our actions.
Scope of impact: Users who attempted to sign into MTR on Windows devices may have been impacted by this issue.
Start time: Friday, June 26, 2026, at 6:42 PM UTC
End time: Sunday, June 28, 2026, at 4:02 AM UTC
Root cause: A recent service side change related to Microsoft Teams Rooms devices caused impact.
Next steps:
- We’re continuing to analyze how the recent service change was applied to understand why the potential for impact wasn't caught during the update testing and validation phase. These actions will help us to clarify what actions we can take to ensure similar impact doesn't occur in future and to continue our ongoing mission to improve the resilience of our service for all Microsoft Teams users.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jun 27 22:12:47 2026 |
|---|
| Description: | Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
User impact: Users may be unable to sign into MTR on Windows devices.
Current status: We've completed our investigation into the Microsoft Teams Rooms device client logs along with our service metrics and identified a recent service side change related to Microsoft Teams Rooms devices is causing impact. We've reverted the impacting change and are monitoring our telemetry to confirm that this issue is resolved.
Scope of impact: Users attempting to sign into MTR on Windows devices may be impacted by this issue. This section may be updated as our investigation continues.
Root cause: A recent service side change related to Microsoft Teams Rooms devices is causing impact.
Next update by: Sunday, June 28, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Sat Jun 27 20:52:47 2026 |
|---|
| Description: | Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) on Windows devices
User impact: Users may be unable to sign into MTR on Windows devices.
Current status: We've determined that impact is limited to only Microsoft Teams Rooms on Windows devices. We've adjusted our title, user impact, and scope of impact to align with our recent findings. Additionally, we're continuing to investigate the aforementioned client logs and our service metrics to pinpoint the root cause and a remediation plan.
Scope of impact: Users attempting to sign into MTR on Windows devices may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Sunday, June 28, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Sat Jun 27 18:54:52 2026 |
|---|
| Description: | Title: Users may be unable to sign into Microsoft Teams Rooms (MTR) devices
User impact: Users may be unable to sign into MTR devices.
Current status: We've received support cases indicating that users may be unable to sign into multiple Microsoft Teams Rooms devices. We're investigating Microsoft Teams Rooms client logs and our service metrics to gain an understanding of why impact may be occurring.
Scope of impact: Users attempting to sign into MTR devices may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Sunday, June 28, 2026, at 1:00 AM UTC
|
|---|
|
TM1402778 - Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Jun 24 04:27:08 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jun 27 10:59:51 2026 |
|---|
| Root Cause: | A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
|
|---|
| Next Update: | Wednesday, July 1, 2026, at 10:30 AM UTC |
|---|
|
Details
| Time: | Wed Jun 24 06:12:54 2026 |
|---|
| Description: | Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Current status: We've determined that a recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments. As a result, the add-in may fail to load, preventing affected users from scheduling Microsoft Teams meetings through Outlook. We've developed a fix to address this behavior and are working to expedite its deployment. To limit additional exposure, we've stopped further rollout of the affected change while we progress deployment activities for the updated fix. Based on our current estimates, we anticipate that the fix will be available by Friday, July 3, 2026.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Root cause: A recent service update introduced an incompatibility affecting how the Teams Meeting add-in identifies the appropriate Teams client during initialization in newly configured Outlook environments impact, resulting in impact.
Next update by: Wednesday, July 1, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Jun 24 04:30:24 2026 |
|---|
| Description: | Title: Some users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client
User impact: Users may be unable to schedule Microsoft Teams meetings through the classic Outlook desktop client.
More info: Impact is specific to Microsoft Teams version 26149.1205.4798.6437. The Teams Meeting add-in appears to be installed and enabled in classic Outlook; however, it isn't being displayed, preventing affected users from scheduling Teams meetings directly from the Outlook ribbon.
Current status: We're reviewing support case details to determine our next troubleshooting steps.
Scope of impact: Users on Microsoft Teams version 26149.1205.4798.6437 and attempting to create and schedule Microsoft Teams meetings through the classic Outlook desktop client may be impacted.
Next update by: Wednesday, June 24, 2026, at 10:30 AM UTC
|
|---|
|
PB1396749 - Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Jun 18 23:31:07 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jun 27 01:02:12 2026 |
|---|
| Root Cause: | A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact. |
|---|
| Next Update: | Thursday, July 2, 2026, at 7:30 AM UTC |
|---|
|
Details
| Time: | Sat Jun 27 01:02:12 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We’ve completed the aforementioned validations to ensure that the fix won’t contain adverse effects, and we’ve begun the initial stages of the deployment. Additionally, we anticipate that the deployment will have saturated throughout the affected environment by our next scheduled update.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Thursday, July 2, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Jun 24 02:19:51 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: During our process of initiating the deployment of the fix, we've identified that additional validation is needed in order to ensure the fix will successfully remediate impact without adversely impacting other aspects of the service. We've since completed the additional validations and are preparing to deploy the change to the impacted environments. We'll aim to provide a resolution timeline once available.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Saturday, June 27, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Jun 19 23:07:11 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We’ve determined that the efficacious solution to resolving the issue is to develop a code change to address the affected infrastructure. We’ve developed this change and validated its efficacy within our internal testing environment, and we’ve subsequently begun the initial deployments throughout the affected environment. We anticipate that a remediation timeline will be provided by our next scheduled communications update.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Wednesday, June 24, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Jun 19 02:01:32 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We’re in the process of the analyzing recent version update as we’ve begun to review options to either develop an expedited code fix to correct the issue or deploy a fix within the most recent standard service update, depending on resolution efficacy.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 15, 2026, at 2:25 AM UTC
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Saturday, June 20, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Jun 18 23:44:32 2026 |
|---|
| Description: | Title: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric
User impact: Users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric.
Current status: We've been made aware of an issue in which internal users may be unable to disable scheduled tileset jobs in Map Artifact within Microsoft Fabric. We're identified that a recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact. We're exploring potential solutions to address this issue.
Scope of impact: Some users attempting to disable scheduling of tileset jobs in Map Artifact within Microsoft Fabric may be impacted. This section may be updated as our investigation continues.
Root cause: A recent version update to the Microsoft Fabric service infrastructure which supports the tileset feature is adding additional properties into the payload, resulting in impact.
Next update by: Friday, June 19, 2026, at 6:00 AM UTC
|
|---|
|
WP1405637 - Users are intermittently disconnected from Windows 365
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 17 03:00:00 2026 |
|---|
| End Time: | Fri Jun 26 22:17:00 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 22:20:28 2026 |
|---|
| Root Cause: | Traffic flow issues placed strain on service infrastructure performance that subsequently impacted gateway access for users, which resulted in connection failures and this impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 22:20:28 2026 |
|---|
| Description: | Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Final status: We confirmed through our period of monitoring that our efforts to rebalance the traffic flow in the impacted infrastructure was successful and that our actions resolved this issue.
Scope of impact: Your organization was affected by this event, and users who attempted to connect to Windows 365 were intermittently disconnected.
Start time: Wednesday, June 17, 2026, at 7:00 AM UTC
End time: Saturday, June 27, 2026, at 2:17 AM UTC
Root cause: Traffic flow issues placed strain on service infrastructure performance that subsequently impacted gateway access for users, which resulted in connection failures and this impact.
Next steps:
- We're analyzing the traffic flow issues to determine how best to bolster the service in an effort to avoid impact such as this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 26 22:00:43 2026 |
|---|
| Description: | Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Current status: We've rebalanced traffic on service infrastructure in an effort to alleviate the flow imbalance and are monitoring service health telemetry to validate if our actions resolve the issue.
Scope of impact: Your organization is affected by this event, and users attempting to connect to Windows 365 are intermittently disconnected.
Start time: Wednesday, June 17, 2026, at 7:00 AM UTC
Root cause: Traffic flow issues placed strain on service infrastructure performance that subsequently impacted gateway access for users, which is resulting in connection failures and this impact.
Next update by: Saturday, June 27, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Fri Jun 26 20:24:14 2026 |
|---|
| Description: | Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Current status: We've determined that the traffic flow issues on service infrastructure are resulting from an ongoing upgrade. We're reviewing service health history to pinpoint the most effective infrastructure to continue the upgrade process in an effort to alleviate the impact for affected users.
Scope of impact: Your organization is affected by this event, and users attempting to connect to Windows 365 are intermittently disconnected.
Root cause: Increased traffic flow is interrupting the processing infrastructure due to an ongoing upgrade to gateway connection processes and is resulting in impact.
Next update by: Saturday, June 27, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Jun 26 19:39:00 2026 |
|---|
| Description: | Title: Users are intermittently disconnected from Windows 365
User impact: Users are intermittently disconnected from Windows 365.
Current status: We've identified that traffic flow discrepancies are impacting users' connections to Windows 365, and are investigating multiple avenues to fully understand the source of this behavior.
Scope of impact: Your organization is affected by this event, and users attempting to connect to Windows 365 are intermittently disconnected.
Next update by: Saturday, June 27, 2026, at 12:30 AM UTC
|
|---|
|
EX1233142 - Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
| Status: | serviceDegradation |
|---|
| Start Time: | Sun Dec 7 22:04:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 26 15:28:51 2026 |
|---|
| Root Cause: | A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
|
|---|
| Next Update: | Thursday, July 2, 2026, at 8:30 PM UTC |
|---|
|
Details
| Time: | Fri Jun 26 15:28:51 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we're working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We’ve confirmed that our fix encountered a deployment blocker that slowed progress. We've addressed the blocker and confirmed that the fix is deploying at a normal rate and has reached 25 percent of the affected environment. We’ll continue monitoring its progress to ensure it completes as expected by our next scheduled update. We’re also reaching out to a subset of affected users to validate the fix ahead of schedule to expedite the deployment process.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, July 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 17 16:20:04 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we're working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We've validated the code solution that includes the required fix and have resumed deployment, which is on schedule for our anticipated completion date of Friday, June 26, 2026. We're reaching out to a subset of affected users to validate the fix ahead of schedule to further streamline the deployment process.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, June 26, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 16:51:18 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: While performing internal testing of our solution to correct the problematic code, we determined a change was needed to ensure the fix fully remediates the impact. We've made this change to the fix and we're progressing with our validations ahead of deployment. We now anticipate our deployment will complete by June 26, 2026, and we'll continue to assess our projected timeline as internal testing continues.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 08, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, June 17, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 28 17:17:08 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can circumvent the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're progressing with our internal tests and validations so we can ensure our deployment remediates the impact. Our fix deployment timeline projects that the deployment will have completed by Friday, June 19, 2026, and we're assessing options to expedite its release, which we anticipate we'll have further clarity on by our next scheduled communications update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 08, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, June 10, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 14 21:45:44 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: Our reviews and checks on the stability and reliability of the aforementioned fix are progressing, though taking an extended period of time as we continue our efforts to ensure it fully addresses impact. Additionally, we anticipate that we will be able to provide an estimated remediation timeline by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, May 28, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue May 12 21:01:35 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're conducting additional reviews and checks on the stability and reliability of the fix before resuming its deployment, to ensure it fully addresses impact. We anticipate being able to share a more accurate timeline for remediation by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, May 15, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Apr 30 20:45:52 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We're continuing to monitor the incremental progress of the deployment; however, more time is needed before we can provide an accurate timeline for resolution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 0, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, May 13, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Apr 23 19:49:47 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The incremental rollout of the fix is ongoing and we’re continuing to monitor its progress to ensure it completes as expected. We’ll provide an estimation for full impact resolution when one becomes available.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, May 1, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 15 19:09:50 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The deployment of our fix is progressing, and our review of service health telemetry shows continued signs of improvement. While we continue to monitor the deployment as it propagates throughout the affected service environment, we anticipate that users will experience relief from impact whilst the time we work to ascertain a full remediation timeline.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, April 24, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 1 19:31:53 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: The deployment of the fix is ongoing and we're continuing to monitor as it progresses.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, April 16, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Mar 26 21:39:25 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: We’re continuing to monitor the deployment of our fix as it progresses and we anticipate it’ll reach completion by mid-April.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Thursday, April 2, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Mar 17 22:02:04 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: While we are working to remediate the impact, admins can mitigate the issue by assigning the desired working hours and the time zone for the meeting rooms.
Current status: Based on feedback received regarding this communication, we've edited the More info, Scope of impact, and Root cause sections of this communication to align with our current understanding of the affected scenario. Additionally, we've completed validation of the fix and have begun its deployment. We're monitoring as it progresses and will provide a completion timeline when one becomes available.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings outside the room's working hours in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, December 8, 2025, at 3:04 AM UTC
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets the meeting rooms' default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Friday, March 27, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Mar 9 21:39:18 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're continuing our efforts to validate the fix in our internal testing environment; however, more time is needed to complete this process and confirm that the fix fully addresses the impact. Once ready, we will begin the full deployment to the remaining affected environment.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Wednesday, March 18, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Sun Mar 8 21:47:36 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're continuing to deploy the fix in our internal test environment and completing final validations prior to deploying it to the remaining affected environments.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Tuesday, March 10, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Mar 6 19:51:36 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We're working to ensure that our fix has mitigated the impact as expected and are running tests to confirm whether any additional changes need to be made.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Monday, March 9, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Mar 2 18:48:30 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Impact is specific to users who have not updated their working hours and time zone to reflect accurately. To avoid this issue, users can manually edit their working hours and ensure their time zone is accurate.
Current status: We’ve developed a fix that will implement two changes to resolve the underlying issue. First, the fix will prevent the Exchange Online time zone from automatically setting users working hours to Pacific Standard Time. Secondly, the fix will allow users to select meeting rooms outside of their working hours if the room is actually available. We're preparing to deploy the fix and anticipate it will be fully deployed and the impact remediated by our next scheduled update. Additionally, to immediately resolve the issue, users can manually update their time zone and working hours to reflect accurately.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online who have not updated their working hours or time zone may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings contains a code complication which automatically sets users default working hours to appear in Pacific Standard Time instead of their accurate time zone.
Next update by: Saturday, March 7, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 15:35:39 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
Current status: We’re continuing to review our options to most efficiently and permanently resolve this issue. We anticipate having a solidified remediation plan and estimate for the delivery of our fix by our next scheduled update.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact.
Next update by: Tuesday, March 3, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Feb 26 15:43:19 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
Current status: We've determined that a recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact. We decided that instead of adding a new state to the UI, which would include "Outside of working hours," we’re focusing on improving the logic to correctly determine and display what times are considered in working hours, so that rooms appear in the correct state consistently across the interface.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Root cause: A recent expansion of the feature logic used to book rooms for scheduled meetings didn't account for certain working hour configurations, resulting in impact.
Next update by: Friday, February 27, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Feb 25 14:49:21 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: We're preparing a code change to introduce a new state to the User Interface (UI), "Outside of working hours," alongside additional logic to correct this issue. We're working to determine a timeline for the code change development along with testing and validation as we continue.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, February 26, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Feb 25 05:05:41 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: As part of our ongoing investigation, we’ve identified a configuration‑related service scenario affecting room availability and have shared a temporary workaround in the More Info section to help prevent further impact. We’re continuing to work to identify steps toward a longer-term resolution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 24 22:26:21 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected may be seen incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
While we're focused on remediation, impacted admins may be able to adjust meeting rooms to 24-hour availability within Exchange Online to prevent users from encountering impact.
Current status: We've identified an underlying code conflict scenario, which we suspect is contributing to the impact. Due to the complexity of the scenario, we're anticipating it may take some additional time before we can identify a timeline and route to remediation.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Feb 17 22:27:48 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Additionally, some users are seeing that room suggestions don’t consistently reflect configured working hours, especially before and after selecting a room.
Current status: As we continue our investigation to isolate the origin of this issue, we’re reaching out to some affected users to validate and confirm whether their time zone settings are configured correctly as a potential solution to this problem. Additionally, regarding room suggestions not reflecting the configured working hours, we suggest that admins adjust the work hours to 24 hours to prevent this issue from occurring as we focus on developing a long-term solution.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Feb 17 12:36:18 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: While our review of the HAR network trace logs is ongoing to progress our root cause investigation, we're assessing the efficacy of some potential remediation actions in recovering the scenario.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, February 18, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Mon Feb 16 01:20:26 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're continuing to analyze the HAR logs and screenshots of the issue to isolate the root cause of the issue.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, February 17, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Feb 16 00:30:38 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're reviewing HTTP Archive format (HAR) logs and screenshots of the issue to help with the investigation and to determine our next troubleshooting steps.
Scope of impact: Any users that are trying to select a meeting room when scheduling meetings in Exchange Online may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 16, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Mon Feb 16 00:07:28 2026 |
|---|
| Description: | Title: Some users may see that when selecting a meeting room when scheduling meetings, it changes from available to unavailable
User impact: Users may see that after selecting a meeting room when scheduling meetings, it changes from available to unavailable.
More info: Specifically, the meeting room selected is incorrectly changing from available to unavailable in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1387482 - Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Jun 11 11:28:27 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 26 13:52:00 2026 |
|---|
| Root Cause: | A dependency introduced in a recent deployment is causing the rewrite feature requests to fail.
|
|---|
| Next Update: | Tuesday, June 30, 2026, at 7:00 PM UTC |
|---|
|
Details
| Time: | Fri Jun 26 13:51:53 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We've validated and applied a code change to stop new internal request failures for this scenario. We're continuing our investigation to isolate an appropriate long-term solution to fully resolve the underlying issue, and we'll provide a remediation timeline once one is available.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Start time: Monday, May 25, 2026, at 3:56 PM UTC
Root cause: A dependency introduced in a recent deployment is causing the rewrite feature requests to fail.
Next update by: Tuesday, June 30, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jun 25 13:55:56 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our analysis into the provided Outlook client captures has helped us isolate a dependency introduced in a recent deployment that we believe is causing the rewrite features requests to fail. As we progress our root cause analysis and confirm our findings, we're validating a solution to address the internal request failures and remediate the impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Root cause: A dependency introduced in a recent deployment is causing the rewrite feature requests to fail.
Next update by: Friday, June 26, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 14:54:23 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're continuing our analysis of the provided Outlook client captures to further our understanding of the issue and determine our next steps.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 25, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 08:04:43 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We've gathered the client data, including Autodiscover details and client boot logs (with endpoints) required to identify the root cause of impact, and to confirm our next troubleshooting steps.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 24, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 05:07:36 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We’re continuing to gather client data, including Autodiscover details and client boot logs (with endpoints), to help determine the next steps to remediate impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 24, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Jun 23 14:13:53 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're reviewing updated Copilot telemetry as we progress with our analysis into why the Outlook classic client isn't able to reach certain Copilot endpoints. In parallel, we're continuing our efforts to collect client data, including Autodiscover and client boot logging (with endpoints), to help us determine our next steps for remediating the impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 24, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Jun 22 15:00:20 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our investigation indicates that the Outlook classic client isn't able to reach certain Copilot endpoints causing requests to fail. We're working with affected users to gather additional client logs to progress the investigation and determine our next steps.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Tuesday, June 23, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jun 18 13:59:39 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our investigation into the URL provisioning issue identified that incorrect value is being returned from the service helps facilitate the rewrite feature process. We're investigating why the incorrect value is being returned to further root cause the issue and formulate mitigating options.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Monday, June 22, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 14:14:25 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: Our initial analysis into reproductions of the impact and associated affected user logging has isolated a URL provisioning issue that’s potentially producing these errors. We're further analyzing the specific URLs to confirm our findings, so we can determine the next troubleshooting steps for remediating the impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 18, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jun 16 13:12:26 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We've received the requested reproductions of impact and associated logging from a subset of affected users which we're analyzing for more insight into how impact manifests to assist our root cause and mitigation efforts.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Wednesday, June 17, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jun 12 17:15:06 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We’re continuing to work with affected users to collect the additional logging and reproductions of the issue to further our understanding of the impacting scenario and formulate remediation plan.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Tuesday, June 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jun 11 18:16:23 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're working with a subset of affected users to collect additional logging and reproductions of impact to assist with debugging the issues and isolating potential regressions in affected Outlook client versions.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Friday, June 12, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jun 11 13:31:38 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message, "Sorry, something went wrong. Copilot is working on it."
Current status: We're continuing our analysis of the client telemetry data while comparing service behaviors across client versions to determine if a potential regression in the Outlook client is contributing to the reported impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 11, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Jun 11 11:41:47 2026 |
|---|
| Description: | Title: Some users may be unable to leverage the Microsoft 365 Copilot rewrite feature in classic Outlook
User impact: Users may be unable to leverage the Copilot rewrite feature in classic Outlook.
More info: Copilot rewrite feature functionality works as expected in Outlook on the web and new Outlook.
When affected users select text and use the Copilot rewrite option in classic Outlook, they may encounter the following error message "Sorry, something went wrong. Copilot is working on it."
Current status: We suspect a potential regression in the Outlook client is contributing to the issue. We're analyzing client telemetry data and comparing service behaviors across client versions to determine if a potential regression in the Outlook client is contributing to the reported impact.
Scope of impact: Impact is specific to some users of the Copilot rewrite feature in classic Outlook.
Next update by: Thursday, June 11, 2026, at 5:30 PM UTC
|
|---|
|
TM1403917 - Some users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 25 09:02:35 2026 |
|---|
| End Time: | Fri Jun 26 12:51:20 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 13:03:56 2026 |
|---|
| Root Cause: | Some missing local settings in the Microsoft Teams desktop client and a feature that allowed users to move chats to a new section was relying on these missing settings caused impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 13:03:51 2026 |
|---|
| Description: | Title: Some users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs
User impact: Users may not have seen chat messages from new contacts in the Microsoft Teams desktop client until a restart occured.
More info: Feedback from affected users and internal testing indicated the impact may have been specific to the combined chat and channel view in the Microsoft Teams desktop client. Impacted users may have been able to avoid impact by utilizing the desktop client's separated chat and channel view experience.
Final status: We've identified some missing local settings in the Microsoft Teams desktop client and a feature that allows users to move chats to a new section was relying on these missing settings, causing impact. While we continue to investigate the reason the local settings were going missing so we can develop a long-term code fix, we disabled the offending feature and confirmed that impact is remediated.
Scope of impact: Some users that were recipients of messages from new contacts in the Microsoft Teams desktop client may have been impacted.
Start time: Friday, May 22, 2026, at 3:28 AM UTC
End time: Friday, June 26, 2026, at 1:25 AM UTC
Root cause: Some missing local settings in the Microsoft Teams desktop client and a feature that allowed users to move chats to a new section was relying on these missing settings caused impact.
Next steps:
- We're continuing to investigate the reason the local settings are going missing, so we can develop a long-term code fix.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 25 19:42:53 2026 |
|---|
| Description: | Title: Some users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs
User impact: Users may not see chat messages from new contacts in the Microsoft Teams desktop client until a restart occurs.
More info: Feedback from affected users and internal testing indicates the impact may be specific to the combined chat and channel view in the Microsoft Teams desktop client. While we're focused on remediation, impacted users may be able to avoid impact by utilizing the desktop client's separated chat and channel view experience.
Current status: We've identified that further assessment is needed to verify our understanding of the underlying root cause and confirm the full scope of the impacted scenario. In parallel with our continued investigation, we're finalizing the deployment of the previously mentioned fix to our internal testing environment to determine its effectiveness in remediating impact.
Scope of impact: Some users may not be receiving messages from new contacts in the Microsoft Teams desktop client. This information may be updated as our investigation continues.
Next update by: Saturday, June 27, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Jun 25 09:43:10 2026 |
|---|
| Description: | Title: Some users may not see messages from new contacts in Microsoft Teams chat list unless the client is restarted
User impact: Users may not see messages from new contacts in Microsoft Teams chat list unless the client is restarted.
More info: As a workaround, users may be able to switch to a separate chat and channel view.
Current status: We've identified that users receiving new messages from contacts they haven’t previously interacted with, don’t see those messages in the Teams desktop client. Existing chat threads aren’t impacted, and the issue doesn’t occur on the web client. We've developed a fix which is being planned for release, and is expected to reach the impacted infrastructure mid-July.
Scope of impact: Some users receiving Microsoft Teams messages from contacts they haven't previously interacted with may be impacted.
Next update by: Thursday, July 16, 2026, at 6:00 PM UTC
|
|---|
|
OD1405074 - Some users may be unable to access or experienced degraded performance when using Microsoft OneDrive
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 26 10:05:30 2026 |
|---|
| End Time: | Fri Jun 26 10:58:15 2026 |
|---|
| Service: | Microsoft OneDrive |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 11:03:16 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 11:03:13 2026 |
|---|
| Description: | Title: Some users may be unable to access or experienced degraded performance when using Microsoft OneDrive
User impact: Users may have been unable to access or experienced degraded performance when using OneDrive.
Final status: While we were in the process of analyzing the portion of networking infrastructure responsible for facilitating OneDrive access, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users located in North America, South America, India and UAE that attempted to access or use OneDrive may have been impacted.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
End time: Friday, June 26, 2026, at 1:06 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 26 10:07:20 2026 |
|---|
| Description: | Title: Some users may be unable to access or experience degraded performance when using Microsoft OneDrive
User impact: Users may be unable to access or experience degraded performance when using OneDrive.
Current status: We've received monitoring alerts showing a significant drop in requests to the OneDrive service, which correlated with user reports of impact. Telemetry shows that the volume of requests dropped at 12:53 PM UTC and has returned to normal levels at 1:06 PM. Users are now reporting that impact has recovered. We suspect a potential issue within the networking layer, and we're investigating to isolate the source of the issue.
Scope of impact: This could have impacted any user, however, it appears that users in North America, South America, India and UAE experienced the highest levels of impact.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
Next update by: Friday, June 26, 2026, at 3:30 PM UTC
|
|---|
|
SP1405058 - Users may be unable to access or experience degraded performance when using SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 26 09:30:15 2026 |
|---|
| End Time: | Fri Jun 26 11:00:52 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 11:03:13 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 11:03:10 2026 |
|---|
| Description: | Title: Users may be unable to access or experience degraded performance when using SharePoint Online
User impact: Users may have been unable to access or experience degraded performance when using SharePoint Online.
Final status: While we were in the process of analyzing the portion of networking infrastructure responsible for facilitating SharePoint Online access, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users located in North America, South America, India and UAE that attempted to access or use SharePoint Online may have been impacted.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
End time: Friday, June 26, 2026, at 1:06 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 26 09:58:36 2026 |
|---|
| Description: | Title: Some users may be unable to access or experience degraded performance when using SharePoint Online
User impact: Users may be unable to access or experience degraded performance when using SharePoint Online.
Current status: We've received monitoring alerts showing a significant drop in requests to the SharePoint Online service, which correlated with user reports of impact. Telemetry shows that the volume of requests dropped at 12:53 PM UTC and has returned to normal levels at 1:06 PM. Users are now reporting that impact has recovered. We suspect a potential issue within the networking layer, and we're investigating to isolate the source of the issue.
Scope of impact: This could have impacted any user, however, it appears that users in North America, South America, India and UAE experienced the highest levels of impact.
Start time: Friday, June 26, 2026, at 12:53 PM UTC
Next update by: Friday, June 26, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Jun 26 09:32:03 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting SharePoint Online
User impact: We're checking for potential impact to your users.
Current status: We're received reports indicating an issue with SharePoint Online. We're investigating the issue further, and we'll provide an update within 30 minutes.
|
|---|
|
EX1404918 - Users may have experienced errors or failures when accessing their mailbox via Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 26 04:30:00 2026 |
|---|
| End Time: | Fri Jun 26 05:30:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 26 06:47:42 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 26 06:46:41 2026 |
|---|
| Description: | Title: Users may have experienced errors or failures when accessing their mailbox via Exchange Online
User impact: Users may have experienced errors or failures when accessing their mailbox via Exchange Online.
Final status: While we were in the process of analyzing system logs to formulate a remediation plan, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Some users located in North America attempting to access their Exchange Online mailbox may have been impacted.
Start time: Friday, June 26, 2026, at 8:30 AM UTC
End time: Friday, June 26, 2026, at 9:30 AM UTC
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 26 05:08:20 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox via Exchange Online
User impact: Users may experience errors or failures when accessing their mailbox via Exchange Online.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users located in North America attempting to access their Exchange Online mailbox may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, June 26, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Fri Jun 26 04:39:13 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
MV1403883 - Some users may experience read and write operation failures in Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 25 06:55:00 2026 |
|---|
| End Time: | Thu Jun 25 11:55:44 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 25 12:20:50 2026 |
|---|
| Root Cause: | A recent service deployment produced an infrastructure restart that caused a subset of service infrastructure to fall below our manageable service performance thresholds, producing read and write failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 25 12:20:46 2026 |
|---|
| Description: | Title: Some users may experience read and write operation failures in Microsoft Viva Engage
User impact: Users may have experienced read and write operation failures in Microsoft Viva Engage.
More info: Users experienced failures with specific read and write operations such as posting messages or loading Engage feeds.
Final status: Our service monitoring has confirmed that our optimizations on the cache population and redistributed service load has remediated the impact.
Scope of impact: The impact was specific to some users in the United States who attempted to use Microsoft Viva Engage.
Start time: Thursday, June 25, 2026, at 10:55 AM UTC
End time: Thursday, June 25, 2026, at 3:25 PM UTC
Root cause: A recent service deployment produced an infrastructure restart that caused a subset of service infrastructure to fall below our manageable service performance thresholds, producing read and write failures.
Next steps:
- We're further analyzing the subset of affected Viva Engage service infrastructure and the deployment that produced infrastructure restarts to help us prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 25 10:57:01 2026 |
|---|
| Description: | Title: Some users may experience read and write operation failures in Microsoft Viva Engage
User impact: Users may experience read and write operation failures in Microsoft Viva Engage.
More info: Users experience failures with specific read and write operations such as posting messages or loading Engage feeds.
Current status: Our automated recovery mechanisms are actively mitigating impact by optimizing cache population and distributing service load more effectively throughout the infrastructure. We're monitoring service telemetry to verify its success in mitigating impact.
Scope of impact: Impact is specific to some users in the United States who are attempting to use Microsoft Viva Engage.
Start time: Thursday, June 25, 2026, at 10:55 AM UTC
Next update by: Thursday, June 25, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jun 25 08:51:45 2026 |
|---|
| Description: | Title: Some users may experience failures in Microsoft Viva Engage
User impact: Users may experience failures in Microsoft Viva Engage.
More info: Users experience failures with specific read and write operations such as posting messages or loading Engage feeds.
Current status: We're reviewing service telemetry to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact is specific to some users in the United States who are attempting to use Microsoft Viva Engage.
Start time: Thursday, June 25, 2026, at 10:55 AM UTC
Next update by: Thursday, June 25, 2026, at 3:00 PM UTC
|
|---|
|
EX1402802 - Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 24 03:55:00 2026 |
|---|
| End Time: | Wed Jun 24 16:01:46 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 24 16:27:08 2026 |
|---|
| Root Cause: | A recent change intended to optimize the service created unexpected latency, which resulted in this impact
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 24 16:03:34 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method
User impact: Users may have experienced errors or failures when accessing their mailbox using any Exchange Online connection method.
Final status: We confirmed that removing a subset of machines from active service infrastructure didn’t mitigate the issue, and we discovered that a recent change intended to optimize the service had created unexpected latency, which resulted in this impact. We've updated the Root cause and Start time sections of our communications to reflect these final investigation details. After reverting the responsible change, we were able to confirm that this successfully remediated the event by monitoring service health telemetry.
Scope of impact: Users in North America who were attempting to access their mailbox using any Exchange Online connection method may have been impacted by this event.
Start time: Wednesday, June 17, 2026, at 3:37 AM UTC
End time: Wednesday, June 24, 2026, at 7:13 PM UTC
Root cause: A recent change intended to optimize the service created unexpected latency, which resulted in this impact
Next steps: - We're reviewing the responsible change to better understand what led to the resulting latency and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 24 11:55:32 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method
User impact: Users may experience errors or failures when accessing their mailbox using any Exchange Online connection method.
Current status: We've placed the affected subset of infrastructure responsible for hosting mailbox databases into maintenance mode to remediate impact and are monitoring this process in order to validate this issue is fully resolved.
Scope of impact: Users in North America who are attempting to access their mailbox using any Exchange Online connection method may be impacted by this event.
Start time: Wednesday, June 24, 2026, at 7:55 AM UTC
Root cause: A subset of infrastructure responsible for hosting Exchange Online mailbox databases hasn't been placed into maintenance mode for an extended period, which is resulting in impact.
Next update by: Wednesday, June 24, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 24 08:00:16 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We've determined that a subset of infrastructure responsible for hosting mailbox databases had not been placed into maintenance mode for an extended period, which is resulting in impact. We're working to ensure that the mailbox is restored, as well as putting this subset of infrastructure into maintenance mode to mitigate impact.
Scope of impact: Impact is specific to some users in North America who are attempting to access their mailbox via one or more Exchange Online connection methods.
Start time: Wednesday, June 24, 2026, at 7:55 AM UTC
Root cause: A subset of infrastructure responsible for hosting mailbox databases had not been placed into maintenance mode for an extended period, which is resulting in impact.
Next update by: Wednesday, June 24, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 05:43:52 2026 |
|---|
| Description: | Title: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're reviewing service telemetry to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact is specific to some users in North America who are attempting to access their mailbox via one or more Exchange Online connection methods.
Next update by: Wednesday, June 24, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jun 24 05:07:39 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
TM1315837 - Some users may see repeated location prompts in Microsoft Teams for Mac
| Status: | serviceRestored |
|---|
| Start Time: | Sun May 10 20:00:00 2026 |
|---|
| End Time: | Wed Jun 24 14:51:30 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 24 15:05:49 2026 |
|---|
| Root Cause: | A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 24 15:05:46 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may have seen repeated location prompts in Microsoft Teams for Mac.
More info: This issue affected macOS versions 14, 15, and 26. Impacted users were unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost wanted to use your current location."
Final status: After the deployment of our solution, our internal service telemetry has validated that the offending regression has been addressed and that the impact has been remediated.
Scope of impact: This issue impacted some Microsoft Teams for Mac users who had location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
End time: Wednesday, June 24, 2026, at 4:20 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next steps:
- We're further analyzing the offending security update to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 23 14:50:01 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to monitor the deployment of our fix as it saturates the affected environment and still estimate that impact will be remediated by Wednesday, June 24, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: We estimate the deployment will complete, remediating impact by Wednesday, June 24, 2026.
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, June 24, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jun 22 14:20:46 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: The deployment of our fix has saturated approximately 80 percent of the affected environment. We estimate the deployment will complete, remediating impact by Wednesday, June 24, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: We estimate the deployment will complete, remediating impact by Wednesday, June 24, 2026.
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, June 23, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jun 17 14:12:42 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: Our fix deployment is ongoing, as more time is needed for it to complete. We've confirmed the fix has reached approximately 50 percent of the impacted environment, and some users may begin to see relief. We're continuing to monitor progress as it continues to provide an updated timeline for completion and impact remediation.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 22, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jun 11 14:59:20 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've resolved the issues in our deployment pipeline and have started to deploy our fix. We anticipate that this fix will completely saturate all affected environments by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, June 17, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 12:01:01 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've completed validation of our solution; however, issues in our deployment pipeline are preventing the initiation of our fix deployment. We're working to address these issues and establish a timeline for the eventual fix deployment.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Thursday, June 11, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jun 9 15:42:10 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: It's taking longer then anticipated to validate a solution that will address the isolated compatibility issue preventing our mitigation deployment from completing. We'll provide a timeline for this additional mitigation step and our resumed deployment if one become available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, June 10, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Jun 9 13:24:17 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to validate a solution that will address the isolated compatibility issue that’s preventing our mitigation deployment from completing. We'll provide a timeline for this additional mitigation step and our resumed deployment if one become available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, June 09, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jun 8 12:09:50 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're internally validating a solution that will address the isolated compatibility issue that’s preventing our mitigation deployment from completing. We're expecting an updated timeline for this additional mitigation step and for our resumed deployment will be available by our next scheduled communication update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, June 09, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Jun 8 10:07:35 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We’ve identified a compatibility issue with the fix and are actively working to resolve it so deployment can resume. We’ll provide an updated timeline once it’s available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Monday, June 8, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 08, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Jun 5 10:36:48 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: Our fix is continuing to deploy across the affected environments. This is taking a little longer to propagate than we anticipated, and we now expect this to be complete by Monday, June 8, 2026.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Monday, June 8, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 08, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 10:28:32 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We've integrated the fix into the Teams client and initiated deployment, which is actively progressing across the affected environments. We expect deployment to complete by Thursday, June 4, 2026, at which point the issue should be fully resolved.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Estimated time to resolve: Thursday, June 4, 2026
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Friday, June 05, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed May 27 10:37:51 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're progressing with the validation of our fix and estimate that this should complete by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Monday, June 01, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 26 12:31:29 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: The validation of our fix is taking longer than initially anticipated. We'll provide a timeline for the completion of our validations and for the deployment as one becomes available.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, May 27, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 26 10:49:41 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're continuing to validate the fix to repair the regression and remediate impact. We expect to provide an estimated completion timeline by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, May 26, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu May 21 09:55:08 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow."
"Microsoft Teams Modulehost would like to use your current location"
Current status: We're validating a fix to repair the regression and remediate impact. We anticipate to provide an estimated completion timeline by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Tuesday, May 26, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed May 20 10:03:56 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":
"Microsoft Teams Modulehost would like to use your current location"
Current status: We’ve further determined that a recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts. We're reviewing available mitigation options and anticipate to provide a strategy by our next scheduled update.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update exposed a location regression where the service doesn’t store users’ permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Thursday, May 21, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 19 10:28:43 2026 |
|---|
| Description: | Title: Some users may see repeated location prompts in Microsoft Teams for Mac
User impact: Users may see repeated location prompts in Microsoft Teams for Mac.
More info: This issue affects macOS versions 14, 15, and 26. Impacted users are unable to dismiss the following location prompt by clicking "Allow" or "Don't allow.":
"Microsoft Teams Modulehost would like to use your current location"
Workaround: Impacted users may be able to resolve the issue by manually enabling location access for Teams within macOS settings. To do so, go to "System Settings" > "Privacy & Security" > "Location Services". Locate "Microsoft Teams" and "Microsoft Teams ModuleHost" and cycle the toggles on/off, then set it back to desired setting.
Current status: We’ve identified that a recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts. We’re working with Apple to better understand the change and identify a resolution. In parallel, we’re investigating a potential fix within Teams to mitigate the repeated prompts. Additionally, we've provided a workaround for this issue in the "More info" section of this communication.
Scope of impact: This issue impacts some Microsoft Teams for Mac users who have location access enabled in Teams settings.
Start time: Monday, May 11, 2026, at 12:00 AM UTC
Root cause: A recent macOS security update doesn’t store users’ location permission selections for Teams as expected, resulting in repeated location prompts.
Next update by: Wednesday, May 20, 2026, at 3:00 PM UTC
|
|---|
|
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: | Tue Jun 23 13:10:34 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: | Tuesday, June 30, 2026, at 6:00 PM UTC |
|---|
|
Details
| 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
|
|---|
|
PB1402061 - Users may be intermittently unable to export reports with sensitivity labels in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 23 09:50:00 2026 |
|---|
| End Time: | Tue Jun 23 13:07:42 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 23 13:07:51 2026 |
|---|
| Root Cause: | Service infrastructure which Power BI relies on for processing export requests experienced an issue resulting in suboptimal performance and impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 23 13:07:47 2026 |
|---|
| Description: | Title: Users may be intermittently unable to export reports with sensitivity labels in Power BI
User impact: Users may have been intermittently unable to export reports with sensitivity labels in Power BI.
More info: As a result of impact, users’ exports may have failed or had incomplete export operations. Export operations may have succeeded on retry.
Final status: After reviewing service health telemetry, we confirmed that service infrastructure which Power BI relies on for processing export requests experienced an issue resulting in suboptimal performance and impact. To remediate impact, we've routed export request traffic to alternate infrastructure while applying optimizations to the impacted infrastructure so requests could process properly. We've rerouted traffic back to the original infrastructure at this time and confirmed impact was successfully remediated.
Scope of impact: This issue may have affected any user attempting to export reports with sensitivity labels in Power BI.
Start time: Tuesday, June 23, 2026, at 1:50 PM UTC
End time: Tuesday, June 23, 2026, at 5:07 PM UTC
Root cause: Service infrastructure which Power BI relies on for processing export requests experienced an issue resulting in suboptimal performance and impact.
Next steps:
- We're investigating why the affected infrastructure was performing at suboptimal thresolds to better understand and prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 23 11:58:12 2026 |
|---|
| Description: | Title: Users may be intermittently unable to export reports with sensitivity labels in Power BI
User impact: Users may be intermittently unable to export reports with sensitivity labels in Power BI.
More info: As a result of impact, users’ exports may fail or have incomplete export operations. Export operations may succeed on retry.
Current status: We're reviewing service health telemetry information to identify and isolate potential sources of impact for further investigation.
Scope of impact: This issue may affect any user attempting to export reports with sensitivity labels in Power BI.
Next update by: Tuesday, June 23, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Jun 23 11:37:51 2026 |
|---|
| Description: | Title: Users may be intermittently unable to export reports with sensitivity labels in Power BI
User impact: Users may be intermittently unable to export reports with sensitivity labels in Power BI.
More info: As a result of impact, users’ exports may fail or have incomplete export operations. Export operations may succeed on retry.
Current status: We're investigating a potential issue with Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1394359 - Some users may have seen incorrect presence status information in Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Jun 17 04:30:00 2026 |
|---|
| End Time: | Wed Jun 17 05:35:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jun 23 10:59:21 2026 |
|---|
| Root Cause: | The Unified Presence Service (UPS) is served through multiple data centers globally for capacity and resiliency reasons. To avoid capacity pressure with an ever-increasing service load, we have been making the long-term architectural change to add an additional data center in the Europe region to process Presence requests. As part of this, the new data center needed to be added to the Azure Traffic Manager (ATM) set-up in preparation for when it was ready to go live. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 23 10:59:21 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jun 18 20:09:52 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 17 06:55:14 2026 |
|---|
| Description: | Title: Some users may have seen incorrect presence status information in Microsoft Teams
User impact: Some users may have seen incorrect presence status information in Microsoft Teams.
Final status: We have confirmed through our telemetry and from some of the previously affected customers that the issue is now resolved.
Scope of impact: This issue primarily affected users in EMEA, and users in other regions may have experienced impact when interacting with the affected users.
Start time: Wednesday, June 17, 2026, at 8:30 AM UTC
End time: Wednesday, June 17, 2026, at 9:35 AM UTC
Root cause: The Unified Presence Service (UPS) is served through multiple data centers globally for capacity and resiliency reasons. To avoid capacity pressure with an ever-increasing service load, we have been making the long-term architectural change to add an additional data center in the Europe region to process Presence requests. As part of this, the new data center needed to be added to the Azure Traffic Manager (ATM) set-up in preparation for when it was ready to go live.
A code bug in the configuration and subsequent miss in the review process resulted in the bad rollout file that was published to ATM. This resulted in inadvertently overwriting/replacing the existing full EMEA configuration that included all the existing data centers which were handling traffic, rather than being extended on top of the existing configuration. This meant that the service removed all the existing data centers from the ATM set-up for Presence and just left the newly added region, which was not in an operational state yet. As such, there were no reachable endpoints for Presence-related requests.
Since Azure Front Door (AFD) has caching for last known good DNS endpoints, we had some protection for client-side presence scenarios and only when a user’s caches expired would they have seen impact.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We’ll provide a preliminary post-incident report in two business days, and a full post-incident report in five business days.
|
|---|
|
| 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.
|
|---|
|
MO1331639 - Issue with webhook-based task notifications in Microsoft To Do
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 2 09:55:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 23 03:23:11 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Monday, June 29, 2026, at 12:00 PM UTC |
|---|
|
Details
| Time: | Tue Jun 23 03:23:11 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using Microsoft Graph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've validated the fix produces the desired resolution. We've now begun deploying the fix to the affected infrastructure and we're monitoring this process closely to ensure it progresses as expected.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Monday, June 29, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Jun 18 15:15:14 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using Microsoft Graph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We're continuing to internally validate the fix and we'll aim to provide an estimated deployment timeline as soon as it's available.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Monday, June 22, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 06:08:39 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using MSGraph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've completed the development of the long-term fix to restore webhook-based task notifications in Microsoft To Do, and we're now conducting a period of internal testing to ensure the fix produces the expected resolution. Once complete, we'll begin deploying the fix to the affected infrastructure.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Wednesday, June 17, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 09:55:50 2026 |
|---|
| Description: | Title: Issue with webhook-based task notifications in Microsoft To Do
User impact: Users are unable to receive webhook-based task notifications in Microsoft To Do.
More info: This issue may affect any webhook-based task notification in Microsoft To Do:
- Any webhook notification delivery to your organization's registered notificationUrl endpoints that was setup using MSGraph: https://learn.microsoft.com/en-us/graph/change-notifications-with-resource-data?tabs=csharp
- Any automation or workflow that depends on receiving real-time task change callbacks
If your organization relies on webhook notifications for task automation:
- Consider temporary polling via GET requests to /me/todo/lists/{listId}/tasks as a workaround: https://learn.microsoft.com/en-us/graph/api/resources/todo-overview?view=graph-rest-1.0
Current status: We've identified a configuration issue affecting webhook-based task notifications in Microsoft To Do. We're developing a long-term fix to restore functionality, and we'll provide additional updates as this progresses.
Scope of impact: Your organization is impacted by this event, and this issue may affect any user within your organization.
Next update by: Wednesday, June 10, 2026, at 12:00 PM UTC
|
|---|
|
TM1400645 - Some users may have delays or failures in multiple Microsoft Teams features
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 22 10:20:37 2026 |
|---|
| End Time: | Mon Jun 22 14:52:23 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jun 22 15:12:04 2026 |
|---|
| Root Cause: | A third-party service network infrastructure interruption resulted in this event.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 22 15:11:28 2026 |
|---|
| Description: | Title: Some users may have delays or failures in multiple Microsoft Teams features
User impact: Users may have had delays or failures in multiple Microsoft Teams features.
More info: This issue impacted message sending, receiving, or both, as well as being able to send or view inline media, starting new calls, chats, and recordings in Microsoft Teams.
Final status: Service-side telemetry has remained stable and confirmed that the service has been restored to a healthy state with no further mitigation actions needed.
Scope of impact: Some users may have had delays or failures when utilizing multiple Microsoft Teams features.
Start time: Monday, June 22, 2026, at 1:00 PM UTC
End time: Monday, June 22, 2026, at 4:53 PM UTC
Root cause: A third-party service network infrastructure interruption resulted in this event.
Next steps: We're identifying what potions of our review process need to be revitalized regarding the way we’re alerted to specific service issues in an effort to prevent impact like this in the future.
|
|---|
|
| Time: | Mon Jun 22 14:18:35 2026 |
|---|
| Description: | Title: Some users may have delays or failures in multiple Microsoft Teams features
User impact: Users may have delays or failures in multiple Microsoft Teams features
More info: This issue impacts message sending, receiving, or both, as well as being able to send or view inline media, starting new calls, chats, and recordings in Microsoft Teams.
Current status: We're continuing to investigate this issue and monitor service-side telemetry to ensure that the service remains healthy, so that we may ensure thereare no further issues requiring action to mitigate the impact.
Scope of impact: Some users may have delays or failures when utilizing multiple Microsoft Teams services.
Root cause: A third-party service network infrastructure interruption is resulting in this event.
Next update by: Monday, June 22, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jun 22 12:16:28 2026 |
|---|
| Description: | Title: Some users may have delays or failures in multiple Microsoft Teams features
User impact: Users may have delays or failures in multiple Microsoft Teams features
More info: This issue impacts message sending, receiving, or both, as well as being able to send or view inline media, starting new calls, chats, and recordings in Microsoft Teams.
Current status: We're continuing to monitor service-side telemetry and are seeing the service is improving. We identified that a third-party service interruption resulted in this impacting event. To ensure the service remains healthy, we're continuing to monitor the telemetry to ensure that further mitigation actions aren't needed.
Scope of impact: Some users may have delays or failures when utilizing multiple Microsoft Teams services.
Root cause: A third-party service network infrastructure interruption is resulting in this event.
Next update by: Monday, June 22, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Jun 22 11:08:02 2026 |
|---|
| Description: | Title: Some users may have delays or failures when sending messages or making calls in Microsoft Teams
User impact: Users may have delays or failures when sending messages or making calls in Microsoft Teams.
Current status: We're investigating service-side telemetry to better understand this impacting issue and determine our next steps.
Scope of impact: Some users may have delays or failures when sending messages or making calls in Microsoft Teams.
Next update by: Monday, June 22, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon Jun 22 10:20:39 2026 |
|---|
| Description: | Title: Possible delays or problems when accessing Microsoft Teams
User impact: Some customers have reported issues with accessing the service, or using features in Microsoft Teams.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|---|
|
CW1391746 - Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Jun 12 00:00:00 2026 |
|---|
| End Time: | Mon Jun 15 18:53:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jun 22 09:28:57 2026 |
|---|
| Root Cause: | A recently deployed service change in Microsoft 365 Copilot Chat introduced an issue in the request processing path. The change caused an extension, that was expected to run prior to the final response generation, to instead run after the response had already been fully generated. As this post-generation execution path was not expected, the extension incorrectly modified the completed response state. This caused otherwise successful chat responses to be treated as failed requests by the processing path, resulting in affected users seeing a "Something went wrong" message instead of the response that had originally been generated. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 22 09:27:35 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 17 14:20:06 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 15 19:54:28 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returned the following error message: "Something went wrong." Some users were unable to submit a prompt in Microsoft 365 Copilot Chat and received an error message. Some users saw Copilot responses being provided successfully at first but then encountered an error message that overridden and removed the response after it had initially been generated successfully.
Final status: We have confirmed with impacted users that the issue has been fully resolved. We appreciate your organization's understanding and patience while we worked on addressing this incident.
Scope of impact: This issue affected some users when they tried to submit a prompt in Microsoft 365 Copilot Chat. This section was updated as our investigation continued.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
End time: Monday, June 15, 2026, at 10:40 PM UTC
Root cause: A recently deployed service change in Microsoft 365 Copilot Chat introduced an issue in the request processing path. The change caused an extension, that was expected to run prior to the final response generation, to instead run after the response had already been fully generated. As this post-generation execution path was not expected, the extension incorrectly modified the completed response state. This caused otherwise successful chat responses to be treated as failed requests by the processing path, resulting in affected users seeing a "Something went wrong" message instead of the response that had originally been generated.
Existing monitoring did not detect this scenario because the responses were created and stored successfully before the later error occurred. We mitigated the issue by disabling the affected code path, which restored normal service behavior.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
|
|---|
|
| Time: | Mon Jun 15 18:51:33 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: We've identified that a recent change within the service was causing impact. We've deployed a configuration change to disable the offending portion of code, and we're observing positive improvements in service availability. We're currently monitoring the service and reaching out to affected users to confirm that the issue is fully resolved.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
Root cause: A recently deployed build was identified to be causing impact, and our investigation into the root cause within this build remains ongoing. The previously outlined token authorization configuration change was not directly related to the root cause for this issue.
Next update by: Tuesday, June 16, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Jun 15 16:55:01 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: We’ve encountered an issue within our deployment pipeline that’s preventing a roll back to the last healthy build. We’re working to unblock the pipeline with urgency and once completed, we’ll proceed with the roll back across all impacted infrastructure to the last known healthy build. We understand how much issues like this can affect your organization, and we appreciate your partnership as we work to remediate impact.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
Root cause: A recently deployed build was identified to be causing impact, and our investigation into the root cause within this build remains ongoing. The previously outlined token authorization configuration change was not directly related to the root cause for this issue.
Next update by: Monday, June 15, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 14:58:20 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: Our investigation has identified a specific internal telemetry log matching the reports of this issue, beginning around Friday, June 12, 2026, at 4:00 AM UTC. From this, we’ve identified an internal service build that is causing the issue. We’re rolling back to the last known good build on a small portion of infrastructure to confirm the issue is resolved. Once validated, we’ll proceed with the rollback across all impacted infrastructure.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Start time: Friday, June 12, 2026, at 4:00 AM UTC
Root cause: A recently deployed build was identified to be causing impact, and our investigation into the root cause within this build remains ongoing. The previously outlined token authorization configuration change was not directly related to the root cause for this issue.
Next update by: Monday, June 15, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 12:55:45 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." Some users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. Some users may see Copilot responses being provided successfully at first but then see an error message that overrides and removes the response after it is initially generated successfully.
Current status: We’re continuing to see failures in error logs provided by customers and internal service logs after the change reversion. While our review of the fresh set of error logs and our internal service health signals is ongoing, we’ll open more workstreams to mitigate the remaining impact based on our findings.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 11:57:19 2026 |
|---|
| Description: | After reverting the change across the Production environment, we're still seeing some evidence of user impact through our service health telemetry systems. Some customers have also reported the issue appears to still be occurring. We’re investigating a fresh set of logs to determine our next steps to resolve the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 11:01:05 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’ve successfully reverted the change within the Production environment, and we’re working to confirm if this has resolved the issue, or if additional actions are required to mitigate impact. We will continue to open and pursue additional mitigation workstreams until the issue is fully resolved.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 10:36:21 2026 |
|---|
| Description: | We've successfully reverted the change broadly across the Production environment, and we're seeing positive signs of recovery in our service telemetry. Affected customers are testing to confirm mitigation as well.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 09:59:49 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’ve encountered an issue with reverting the change causing it to take longer than we expected. We’ve successfully reverted the change within our internal test environment and are in the process of validating its effectiveness. When this is complete, we will revert the change more broadly.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 09:01:27 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’re continuing to monitor the progress of reverting the change which we expect to be complete within one hour.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 08:32:27 2026 |
|---|
| Description: | We're closely monitoring the reversion of the change which is progressing as expected. While this continues, we're monitoring service telemetry for signs of improvement.
Next update by: Monday, June 15, 2026, at 1:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 08:00:25 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We’ve identified a recent token authorization configuration change was applied that unexpectedly introduced a misconfiguration and caused impact. We're continuing to work on reverting this change.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Root cause: A recent token authorization configuration change was applied that introduced a misconfiguration to the app id, resulting in impact.
Next update by: Monday, June 15, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 06:59:51 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: While we’re continuing to analyze this change, we’ve started to reverse it to mitigate the impact. When this has completed, we will begin to validate service telemetry to ensure it has fully resolved the issue.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 06:40:12 2026 |
|---|
| Description: | We’ve identified a recent change that may have resulted in impact and we’re analyzing this change in more detail to determine if it is the root cause.
Next update by: Monday, June 15, 2026, at 11:00 AM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 06:00:09 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: While we continue to analyze the newly obtained HTTP Archive format (HAR) logs, we’ve identified a specific failure from service side telemetry and are looking into this further to determine the next steps required.
Scope of impact: This issue may affect some users when trying to submit a prompt in Microsoft 365 Copilot Chat. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Jun 15 05:34:20 2026 |
|---|
| Description: | Our analysis of HTTP Archive format (HAR) logs has so far been inconclusive. We’re reviewing newly obtained logs to assist in progressing the investigation.
Next update by: Monday, June 15, 2026, at 10:00 AM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 04:57:32 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: Our analysis is continuing into impacted users logs and recent changes that align with the impact start time to help identify the next troubleshooting steps required to resolve the issue. While this continues, we’ve requested additional HTTP Archive format (HAR) files to assist in our investigation.
Scope of impact: Your organization is impacted by this event, and users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Mon Jun 15 04:31:15 2026 |
|---|
| Description: | In addition to our analysis of service telemetry and client-side logs from impacted users, we’re reviewing recent changes which may have resulted in impact.
Next update by: Monday, June 15, 2026, at 9:00 AM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 03:24:42 2026 |
|---|
| Description: | We're continuing our analysis of HTTP Archive format (HAR) files and service telemetry. In addition, we're attempting to reproduce the issue internally to determine the next steps required to resolve the issue.
Next update by: Monday, June 15, 2026, at 9:00 AM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 15 02:47:12 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
More info: Microsoft 365 Copilot Chat returns the following error message "Something went wrong." for users when they submit a prompt.
Current status: We're reviewing the provided case details and HTTP Archive format (HAR) files to help inform our next troubleshooting steps for pinpointing the underlying cause of the error message.
Scope of impact: Your organization is impacted by this event, and users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message. This section may be updated as our investigation continues.
Next update by: Monday, June 15, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Mon Jun 15 02:17:02 2026 |
|---|
| Description: | Title: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message
User impact: Users are unable to submit a prompt in Microsoft 365 Copilot Chat and receive an error message.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
SP1393483 - Admins may be unable to see the configuration search schema mappings in SharePoint Online
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jun 16 12:02:13 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Tenant Admin |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 22 05:18:10 2026 |
|---|
| Root Cause: | A recent migration introduced a configuration issue, resulting in a regression that is causing impact.
|
|---|
| Next Update: | Monday, July 6, 2026, at 10:00 AM UTC |
|---|
|
Details
| 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
|
|---|
|
EX1394927 - Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 17 02:00:00 2026 |
|---|
| End Time: | Sat Jun 20 12:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jun 20 12:30:46 2026 |
|---|
| Root Cause: | A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that was causing resource contention and impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jun 20 12:26:39 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may have been unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may have impacted admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Final status: We've processed the backlog of accumulated requests and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may have been impacted.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
End time: Saturday, June 20, 2026, at 4:00 PM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that was causing resource contention and impact.
Next steps:
- We're reviewing the offending provisioning feature to determine why it introduced a large number of synchronization divergences once implemented, so that we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jun 20 09:32:42 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: Our efforts to monitor service health telemetry to validate that the backlog of accumulated requests has fully processed is ongoing. We expect to be able to provide confirmation that the issue is resolved by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Saturday, June 20, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat Jun 20 04:55:43 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We’re continuing to monitor service health telemetry to validate that the backlog of accumulated requests has fully processed. Service health remains stable following the disablement of the offending provisioning feature and we’re maintaining an extended monitoring period to confirm sustained service stability and ensure no further impact is observed before concluding our mitigation efforts.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Saturday, June 20, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Fri Jun 19 16:04:30 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We've confirmed that disabling the offending provisioning feature successfully helped to stabilize the affected service infrastructure and alleviate impact. We're continuing to monitor service health telemetry in order to validate that the backlog of accumulated requests fully processes, which we anticipate will complete and remediate all impact by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Saturday, June 20, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Fri Jun 19 13:33:44 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We've continuing to disable the offending provisioning feature and clear the backlog of accumulated requests, and we anticipate both these processes will complete and remediate the impact by our next scheduled communications update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Estimated time to resolve: We anticipate the offending provisioning feature will be disabled and the backlog of accumulated requests processed by Friday, June 19, 2026, at 9:30 PM UTC.
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Jun 19 09:57:51 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We’re continuing with our efforts to disable the provisioning feature responsible for generating additional synchronization divergences and to remove the existing backlog. We expect to be able to provide a remediation timeline by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jun 19 03:38:15 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We’re progressing with our efforts to disable the provisioning feature responsible for generating additional synchronization divergences and are continuing cleanup efforts to remove the existing backlog. In parallel, we’re implementing processing changes to help reduce system load and improve throughput, as we work to restore affected provisioning operations to expected service levels.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Jun 18 18:30:14 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: This issue may impact admins attempting to perform any actions involving DNS records within the Exchange admin center, such as provisioning new domains or mailboxes, accessing the Exchange admin center, or changing domains from IPv6 to IPv4.
Current status: We've updated the Title, User impact, More info, and Scope of impact sections as we've determined that any actions involving DNS records within the Exchange admin center may be impacted. We're continuing to perform cleanup efforts and remove existing divergences to return the service to expected functionality.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that's causing resource contention and impact.
Next update by: Friday, June 19, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Thu Jun 18 15:19:11 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We've identified that a recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that prevented some Exchange Online IPv6 to IPv4 domain changes from completing successfully. To remediate this issue and prevent additional synchronization divergences from being created, we've disabled the affected provisioning feature and are performing cleanup efforts to remove the existing divergences for full remediation.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 6:00 AM UTC
Root cause: A recently enabled provisioning feature introduced a large number of synchronization divergences, resulting in repeated cmdlet executions that prevented some Exchange Online IPv6 to IPv4 domain changes from completing successfully.
Next update by: Friday, June 19, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Wed Jun 17 22:46:11 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: More time is needed to investigate the Domain Name System (DNS) logs to isolate the source of impact. We aim to have an updated status by our next scheduled update.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 17, 2026, at 8:13 AM UTC
Next update by: Thursday, June 18, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 20:45:05 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We're furthering our analysis on the Domain Name System (DNS) logs to isolate the source of traffic to help determine a path towards remediation.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Jun 17 18:34:45 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We've identified that unusually high traffic to the affected infrastructure is preventing the cmdlet used to change the domain from IPv6 to IPv4 from working as expected. We're reviewing Domain Name System (DNS) logs to determine the source of this traffic, which may help us determine a strategy that remediates impact.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jun 17 16:59:26 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We're continuing to review data, which includes error details, to determine the root cause and a strategy that remediates impact.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, June 17, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 15:56:49 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPv6 to IPv4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We're reviewing data to determine why admins may be unable to change their domain from IPv6 to IPv4.
Scope of impact: Admins attempting to perform actions involving DNS records within the Exchange admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, June 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Jun 17 15:21:45 2026 |
|---|
| Description: | Title: Admins may be unable to perform actions involving Domain Name System (DNS) records within the Exchange admin center
User impact: Admins may be unable to perform actions involving DNS records within the Exchange admin center.
More info: Admins may receive the following error when attempting to change their domain from IPV6 to IPV4: “WARNING: Failed to update DNS record for domain. Error: Too many operations are
requested. Current operation is throttled.”
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1274156 - Some users may not have seen the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
| Status: | serviceRestored |
|---|
| Start Time: | Tue Oct 14 08:35:00 2025 |
|---|
| End Time: | Thu Jun 4 13:25:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jun 20 09:56:21 2026 |
|---|
| Root Cause: | A code regression was causing impact to occur.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jun 20 09:53:32 2026 |
|---|
| Description: | Title: Some users may not have seen the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not have seen the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may have seen that the My Templates add-in wasn't appearing in available apps.
Final status: We've determined that a code regression was causing impact to occur. We've successfully deployed our code fix and have confirmed with a sample of affected users that impact has been resolved.
Scope of impact: This issue may have affected any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Start time: Tuesday, October 14, 2025, at 12:35 PM UTC
End time: Thursday, June 4, 2026, at 5:25 PM UTC
Root cause: A code regression was causing impact to occur.
Next steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 15 17:49:02 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: As we progress with our root cause analysis and review a subset of Outlook service infrastructure and our legacy code paths, we've deployed a solution to restore My Templates and Viva Insights. Our internal testing has validated that it will restore My Templates and Viva Insights for Outlook desktop and Outlook on the web users, and our fix deployment timeline projects it will have remediated the impact by our next scheduled communication update.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 22, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jun 8 17:38:13 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've continuing to investigate a portion of Outlook infrastructure responsible for My Templates and Viva Insights add-ins to help with identifying the underlying root cause. Simultaneously, we're validating if legacy code paths being utilized to view or access the affected add-ins may be contributing to impact and what our new remediation plan should be.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 15, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 18:34:11 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've completed deploying the fix and identified after additional testing and validations that the impact persists. We're further investigating a portion of Outlook infrastructure responsible for My Templates and Viva Insights add-ins to help with identifying the underlying root cause while we formulate a new remediation plan.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 08, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri May 29 18:50:14 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: Deployment of the fix is ongoing. We’re monitoring the deployment of the fix, which includes enhanced logging that will assist in our assessment of the impact and help with confirming the underlying cause of this issue and will be analyzed prior to our next update to determine whether any additional remediation steps are necessary.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Monday, June 01, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue May 19 18:01:31 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're deploying the fix to remediate the impact. We expect that our fix deployment will be complete by our next scheduled communication update, after which we'll evaluate any potential needs for supplemental adjustments.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Next update by: Friday, May 29, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon May 18 22:00:25 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're monitoring our potential fix and evaluating it's effectiveness in our internal testing environment, ensuring that it successfully addresses impact. We'll look to provide an estimated timeline for completion once one becomes available.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, May 19, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 14 21:11:14 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We've completed our preliminary validation phase and begun rolling out our potential fix to our internal testing environment for final validation prior to its broad release. In parallel, we're continuing to assess to determine a potential timeline for the full deployment of the fix.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, May 19, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed May 13 20:19:37 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're continuing our operation to finalize our validations for a code fix to address the suspected configuration issue we believe is causing impact. Upon our fix being validated, we'll initiate the deployment and share an estimated timeline of completion.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Friday, May 15, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed May 6 19:53:28 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We’re validating a code fix to address what we suspect may be a configuration issue that was introduced by a recent change made to the service and help confirm the underlying cause of this issue.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, May 14, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Apr 22 19:50:06 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: We're continuing our analysis of the underlying code to isolate the source of impact. In parallel, we're in the preliminary stages of developing a fix to remediate impact.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, May 7, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Apr 20 19:27:24 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
More info: In addition, users may see that the My Templates add-in isn't appearing in available apps.
Current status: Our analysis of the underlying code to understand the source of impact with the My Templates add-ins in Exchange Online is ongoing. We've identified a recent change that we're testing disabling for some affected users to validate whether it remediates the impact with My Templates.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 23, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Wed Apr 15 18:32:21 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're continuing to analyze the service code to help uncover the underlying root cause of impact; however, more time is needed.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, April 21, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Apr 13 16:34:53 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our review of the service code is progressing as we seek to identify any issues or unexpected behavior which may indicate the root cause.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 16, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Apr 9 16:15:32 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our review of the HAR traces and additional impact details was inconclusive. We're reviewing the service code to identify potential code issues that may be contributing to the reported impact.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Monday, April 13, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Apr 9 01:28:30 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We’ve determined that the Viva Insights add-in is also impacted by this issue, and we’ve modified the Title, User impact, and Scope sections of this communication to reflect our new understanding. We're continuing to review the fresh HAR traces provided by a subset of affected users and have reached out to a subset of users for additional impact details to assist in our active root cause investigation.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Apr 8 15:13:29 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're continuing to review the fresh HAR traces provided by a subset of affected users and have reached out to a subset of users for additional impact details to assist in our active root cause investigation.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, April 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Apr 8 12:42:05 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: Our analysis of the HAR traces is ongoing to identify the source of the impact and develop a mitigation strategy.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, April 8, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Apr 8 11:52:48 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're reviewing the HTTP Archive (HAR) files provided by a subset of affected users to help determine our next troubleshooting steps.
Scope of impact: This issue may affect any user attempting to access the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, April 8, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Apr 8 11:23:48 2026 |
|---|
| Description: | Title: Some users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web
User impact: Users may not see the My Templates or Viva Insights add-ins for Outlook desktop or Outlook on the web.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1396891 - Admins may be unable to provision some users’ Exchange Online mailboxes
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 18 03:28:00 2026 |
|---|
| End Time: | Fri Jun 19 17:19:51 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 19 17:21:14 2026 |
|---|
| Root Cause: | A separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID caused this issue and resulted in impact to admins' provisioning attempts.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 19 17:21:10 2026 |
|---|
| Description: | Title: Admins may be unable to provision some users’ Exchange Online mailboxes
User impact: Admins may have been unable to provision some users’ Exchange Online mailboxes.
More info: Affected admins may have also been unable to access the Exchange admin center.
Final status: We've validated that the backlogged provisioning requests fully processed and our service change implementation successfully remediated all impact for this issue.
Scope of impact: Admins who attempted to provision some users' Exchange Online mailboxes or access the Exchange admin center may have been impacted by this event.
Start time: Thursday, June 18, 2026, at 7:28 AM UTC
End time: Friday, June 19, 2026, at 8:51 PM UTC
Root cause: A separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID caused this issue and resulted in impact to admins' provisioning attempts.
Next steps:
- We're continuing to review how this data sync gap between Exchange Online and Microsoft Entra ID was introduced in order to improve our service reliability for admin provisioning requests and access to the Exchange admin center, and to avoid similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 19 12:43:37 2026 |
|---|
| Description: | Title: Admins may be unable to provision some users’ Exchange Online mailboxes
User impact: Admins may be unable to provision some users’ Exchange Online mailboxes.
More info: Affected admins may also be unable to access the Exchange admin center.
Current status: We've determined that a separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID is causing this issue and resulting in impact to admins' provisioning attempts. We're continuing to monitor the effectiveness of our service change implementation aimed at correcting this gap while the backlogged provisioning requests process.
Scope of impact: Admins attempting to provision some users' Exchange Online mailboxes or access the Exchange admin center may be impacted by this event.
Start time: Thursday, June 18, 2026, at 7:28 AM UTC
Root cause: A separate service issue involving a data sync gap between Exchange Online and Microsoft Entra ID is causing this issue and resulting in impact to admins' provisioning attempts.
Next update by: Saturday, June 20, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Fri Jun 19 07:52:05 2026 |
|---|
| Description: | Title: Admins can’t provision some users’ Exchange Online mailboxes
User impact: Admins can’t provision some users’ Exchange Online mailboxes.
Current status: We're progressing with our analysis of support and diagnostic data to determine the underlying cause of the issue. In parallel, we've implemented a service change that is expected to help mitigate the impact and are actively monitoring its effectiveness as affected provisioning requests continue to be processed. However, we're seeing positive signs, with some provisioning requests now completing successfully. We'll continue to monitor backlog reduction and work closely with your representatives to evaluate the effectiveness of the service change and confirm sustained improvement.
Scope of impact: Impact is specific to admins attempting to provision mailboxes or access the Exchange admin center.
Next update by: Friday, June 19, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Jun 19 05:06:38 2026 |
|---|
| Description: | Title: Admins can’t provision some users’ Exchange Online mailboxes
User impact: Admins can’t provision some users’ Exchange Online mailboxes.
Current status: We’re continuing our analysis of support case details, as well as working with your representatives to obtain further contextual details of the impact scenario to help isolate the source of impact and formulate a mitigation plan.
Scope of impact: Impact is specific to admins attempting to provision mailboxes or access the Exchange admin center.
Next update by: Friday, June 19, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Fri Jun 19 02:12:46 2026 |
|---|
| Description: | Title: Admins can’t provision some users’ Exchange Online mailboxes
User impact: Admins can’t provision some users’ Exchange Online mailboxes.
Current status: We’re reviewing system logs to isolate the origin of this issue.
Scope of impact: Your organization is affected by this event, and admins can’t provision some users’ Exchange Online mailboxes. This information may be updated as our investigation continues.
Next update by: Friday, June 19, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Jun 19 02:02:05 2026 |
|---|
| Description: | Title: Admins can’t provision some users’ mailboxes
User impact: Admins can’t provision some users’ mailboxes.
Current status: We're investigating a potential issue in which admins can’t provision some users’ mailboxes and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1392948 - Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 15 20:51:00 2026 |
|---|
| End Time: | Thu Jun 18 13:57:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 19:00:17 2026 |
|---|
| Root Cause: | A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, was causing issues within the IME flow, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 18:59:12 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may have been disabled and may have switched to English in Exchange Online.
Final status: We’ve confirmed with affected users that this issue is resolved following the deployment of our fix.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may have been impacted.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
End time: Thursday, June 18, 2026, at 5:57 PM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, was causing issues within the IME flow, resulting in impact.
Next steps: We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 17 19:08:06 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: Our updated fix deployment has completed and we're reaching out to affected users to confirm that this fix has fully remediated the event.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Friday, June 19, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Jun 17 14:30:12 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We've confirmed that our fix aimed at reverting the offending service update didn't include all necessary components required to remediate impact for this issue. We've corrected this fix and have placed it back in queue for safe deployment, which we expect will initiate by our next scheduled communications update. Once deployed, we'll monitor saturation progress and provide a timeline for its completion as one becomes available.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Thursday, June 18, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Jun 17 04:25:01 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We've received confirmation from affected users that impact persists following the completed reversion. We're investigating why the reversion has not fully alleviated the issue and are assessing why users have not yet received the updated client version containing the fix.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jun 16 23:43:54 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We're continuing our efforts to reach out to affected users to confirm if impact has ceased after our deployed fix.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Tue Jun 16 21:44:17 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: Our deployment to revert the offending service update to remediate impact has completed. We're reaching out to your representatives to confirm if impact has ceased.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Jun 16 15:27:25 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We've completed our review of the HTTP archive format (HAR) logs and identified that a recent service update, intended to modify which touch keyboard appears when users enter email addresses in the recipient field, caused impact to the IME flow and is resulting in impact. We're reverting the offending service update to remediate the impact, which we anticipate will be complete by our next scheduled communications update. Once the reversion is completed, we'll test with a subset of affected users to validate remediation.
Scope of impact: Your organization is affected by this event, and users encountering the IME for Japanese/Korean input is disabled and switches to English in Exchange Online. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Root cause: A recent service update, intended to modify which touch keyboard appears when users enter email address in the recipient field, is causing issues within the IME flow, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jun 16 01:11:45 2026 |
|---|
| Description: | Title: Users' Input Method Editor (IME) for Japanese/Korean input may be disabled and may switch to English in Exchange Online
User impact: Users' IME for Japanese/Korean input may be disabled and may switch to English in Exchange Online.
Current status: We're analyzing HTTP Archive logs and diagnostic data to pinpoint the source of impact to determine our next steps.
Scope of impact: Users attempting to use their IME for Japanese/Korean input may be impacted. This is subject to change while our investigation continues.
Start time: Friday, June 12, 2026, at 12:51 AM UTC
Next update by: Tuesday, June 16, 2026, at 7:30 PM UTC
|
|---|
|
SP1386381 - Users may be unable to access Excel files through web browsers from SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 7 23:43:00 2026 |
|---|
| End Time: | Thu Jun 18 15:40:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | Office Web Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 17:20:10 2026 |
|---|
| Root Cause: | A code issue during the request flow for opening Excel files in SharePoint Online was causing errors, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 17:09:22 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through web browsers from SharePoint Online
User impact: Users may have been unable to access Excel files through web browsers from SharePoint Online.
More info: As we worked to remediate the impact, users could open the file in the Excel desktop app to circumvent impact.
Final status: Following our completed fix deployment, our testing with affected users has validated that Excel files are able to be accessed through the browser, and that the impact has been remediated.
Scope of impact: Users who attempted to access subsites with unique permissions not inherited from the parent site on SharePoint Online weren't able to access files in Excel for the web browser.
Start time: Monday, June 8, 2026, at 3:43 AM UTC
End time: Thursday, June 18, 2026, at 7:40 PM UTC
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online was causing errors, which resulted in impact.
Next steps:
- We're further analyzing our Excel request flow and the isolated code issue to help us prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 17 16:08:32 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: Our deployment is taking longer than initially expected, and we're isolating ways to expedite the remainder of our deployment to remediate impact as swiftly as possible.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Thursday, June 18, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Jun 15 16:10:18 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We're continuing to monitor the deployment of our fix, and we anticipate that we'll be ready to test for mitigation with a subset of affected users by our next scheduled update.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Wednesday, June 17, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Jun 12 16:25:42 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've completed the validation of the fix and have initiated the release. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Monday, June 15, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Jun 11 14:11:49 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've confirmed that the code fix is ready for testing and validation. Once completed, we'll provide a more detailed update regarding the deployment schedule.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Friday, June 12, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 21:16:13 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We identified a code issue that is causing errors when opening Excel files. We're developing a fix for the issue and anticipate that it will take time to complete. Once the fix is ready, we'll begin deploying to the affected environment to remediate the impact.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Root cause: A code issue during the request flow for opening Excel files in SharePoint Online is causing errors, which is resulting in impact.
Next update by: Wednesday, June 17, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Jun 10 17:38:08 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: Our investigation has identified a recent update as the potential cause of this issue. We're validating that it's the source of impact as well as a fix before deploying to all affected areas.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Thursday, June 11, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Jun 10 16:49:54 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've determined that the recent update isn't the cause of impact. We're analyzing other recent updates along with testing additional service-side reproductions of this issue to isolate the root cause.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 14:42:06 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We've identified a recent update that could be potentially responsible for this issue. We're in the process of validating this as the source before applying mitigation to all impacted areas.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 12:52:31 2026 |
|---|
| Description: | Title: Users may be unable to access Excel files through browser from SharePoint Online
User impact: Users may be unable to access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: Our investigation continues into our reproduction of the event and log review. In parallel, we're also reviewing if any recent updates or changes could be contributing to impact.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 11:38:12 2026 |
|---|
| Description: | Title: Users may be unable to access files in Excel for the web opened from SharePoint Online
User impact: Users may be unable to access files in Excel for the web opened from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We're reproducing the impact of this event and gathering logs associated with specific requests to better understand this issue and determine our next steps.
Scope of impact: Users accessing subsites with unique permissions not inherited from the parent site on SharePoint Online aren't able to access files in Excel for the web browser.
Next update by: Wednesday, June 10, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 10:58:36 2026 |
|---|
| Description: | Title: Users can't access Excel files through browser from SharePoint Online
User impact: Users can't access Excel files through browser from SharePoint Online.
More info: Users can open the file in the Excel desktop app to circumvent impact.
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CW1390285 - Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 2 06:05:00 2026 |
|---|
| End Time: | Thu Jun 18 13:04:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 16:21:25 2026 |
|---|
| Root Cause: | A recent upgrade to unlicensed users' capabilities within Copilot Chat wasn't included in current usage logging logic, causing exclusion of that data from usage reports, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 15:31:40 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not have seen accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may have seen lower than expected data reported for Copilot Chat users who didn't have a Microsoft 365 Copilot standalone license assigned.
Final status: We've confirmed after a period of monitoring that the data restatement process has completed and impact is fully remediated.
Scope of impact: This issue may have affected any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
End time: Thursday, June 18, 2026, at 5:04 PM UTC
Root cause: A recent upgrade to unlicensed users' capabilities within Copilot Chat wasn't included in current usage logging logic, causing exclusion of that data from usage reports, which resulted in impact.
Next steps: We're reviewing and improving our update validation procedures to detect and prevent similar data exclusions in usage reports in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 17 15:54:37 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: We're monitoring the final stages of the data restatement process for the organizational level trend view to validate that this issue is fully resolved.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
Root cause: A recent upgrade to unlicensed users' capabilities within Copilot Chat wasn't included in current usage logging logic, causing exclusion of that data from usage reports, which is resulting in impact.
Next update by: Thursday, June 18, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jun 16 15:55:53 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: The backlogged data has completed restatement for active days metrics, which has restored user level details for this event. We're continuing to monitor the final stages of the restatement process for the organizational level trend view to ensure that all usage data is fully restored.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Wednesday, June 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 19:59:33 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: We're continuing to monitor as the backlogged data such as Organization level trend views and Active days metrics in the user level table of Copilot chat usage reports are being processed to ensure all data is included in the reports.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Tuesday, June 16, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 15:59:21 2026 |
|---|
| Description: | Title: Admins may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Admins may not see accurate usage data for Copilot Chat in the Microsoft 365 admin center.
More info: Admins may see lower than expected data reported for Copilot Chat users who don't have a Microsoft 365 Copilot standalone license assigned.
Current status: We've confirmed that all necessary fixes for usage metrics have been successfully deployed. Admins may start seeing an increase in active usage for Copilot Chat. Additionally, we're monitoring as backlogged data is being drained to ensure all previous impacted usage data during the duration of this event is fully restored.
Scope of impact: This issue may affect any admin attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Tuesday, June 16, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Sun Jun 14 15:43:40 2026 |
|---|
| Description: | Title: Users may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Users may not see accurate usage data for Copilot Chat in usage reports within the Microsoft 365 admin center.
More info: This issue strictly affects usage data for unlicensed Copilot Chat users. Users may see lower than expected data reported for unlicensed Copilot Chat users.
Current status: We've implemented a code fix to restore organizational-level metrics such as accurate Active User counts, and we've confirmed that our fixes are allowing updated accurate reporting to reach affected users. We're working to isolate the root cause on why user-level metrics aren’t being reported in a timely manner to determine our next remediation steps to restore affected user-level metrics.
Scope of impact: This issue may affect any user attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Start time: Tuesday, June 2, 2026, at 10:05 AM UTC
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Monday, June 15, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Sat Jun 13 17:19:31 2026 |
|---|
| Description: | Title: Users may not see accurate usage data for Microsoft 365 Copilot Chat in the Microsoft 365 admin center
User impact: Users may not see accurate usage data for Copilot Chat in usage reports within the Microsoft 365 admin center.
More info: This issue strictly affects usage data for unlicensed Copilot Chat users. Users may see lower than expected data reported for unlicensed Copilot Chat users.
Current status: This is a continuation of MO1388943. We're continuing to review a recent upgrade to identify a viable method to restate the affected data and remediate the impact.
Scope of impact: This issue may affect any user attempting to view reports for Copilot Chat through the Microsoft 365 admin center.
Root cause: A recent upgrade to unlicensed users' capabilities in the Copilot Chat wasn't included in current usage logging logic, resulting in exclusion of that data from usage reports.
Next update by: Sunday, June 14, 2026, at 9:00 PM UTC
|
|---|
|
MO1387691 - Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jun 11 16:00:00 2026 |
|---|
| End Time: | Thu Jun 11 17:56:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jun 18 11:10:56 2026 |
|---|
| Root Cause: | The root cause is still being investigated. We will provide more information in our next update. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 11:10:56 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 15 19:43:58 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jun 11 18:05:51 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com.
More info: Admins may have been able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams was not impacted and could have been leveraged in the interim while we mitigated the issue.
Final status: We’ve successfully rolled back the change throughout the affected infrastructure, and we've confirmed with previously affected users that the impact is mitigated.
Scope of impact: Any user or admin may have been affected by this event.
Start time: Thursday, June 11, 2026, at 8:00 PM UTC
End time: Thursday, June 11, 2026, at 9:56 PM UTC
Preliminary root cause: We've identified an issue with a recent deployment which is contributing to impact. We will provide more information in our Post-Incident Report.
Next steps:
- We're analyzing the recent deployment to identify why this issue occurred and how to prevent it from happening again in the future.
- We're reviewing our change management processes to determine areas of improvement.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Jun 11 17:54:45 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com.
More info: Admins may be able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams is not expected to be impacted and can be leveraged in the interim while we mitigate the issue.
Current status: We have successfully reverted the change for 97 percent of the affected infrastructure. We're continuing to monitor the progress of the reversion and we're also observing an uptick in service availability. Additionally, we've started to receive confirmation that service availability is returning for some users. In parallel, we're investigating the underlying cause of the problem and will provide more information when available.
Scope of impact: Our investigation indicates that any user or admin may be affected by this event. This section is subject to change as the investigation continues.
Start time: Thursday, June 11, 2026, at 8:00 PM UTC
Preliminary root cause: We've identified an issue with a recent deployment which is contributing to impact. We will continue to perform a root cause analysis to identify how this occurred and how we can prevent this from happening in the future.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jun 11 17:20:21 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com
User impact: Users are unable to access Microsoft 365 Copilot Chat or portal.office.com.
More info: Admins may be able to access the Microsoft 365 admin center via admin.cloud.microsoft as a temporary solution. Additionally, Copilot in Microsoft Teams is not expected to be impacted and can be leveraged in the interim while we mitigate the issue.
Current status: This is a continuation of a communication posted under CW1387674. We’ve identified an issue with a recent deployment for Microsoft Copilot. We’re reverting to a previous build to remediate impact as soon as possible. We expect this to be completed in the next 30 minutes.
Scope of impact: Our investigation indicates that any user or admin may be affected by this event. This section is subject to change as the investigation continues.
Start time: Thursday, June 11, 2026, at 8:00 PM UTC
Estimated time to resolve: We expect the reversion to be complete in the next 30 minutes.
Root cause: The root cause is still being investigated. We will provide more information in our next update.
Next update by: Thursday, June 11, 2026, at 10:00 PM UTC
|
|---|
|
DZ1395542 - Some users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 13 12:14:00 2026 |
|---|
| End Time: | Wed Jun 17 17:02:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 10:17:33 2026 |
|---|
| Root Cause: | A service configuration update caused an issue in the sensor’s dynamic component, leaving a stale proxy configuration that prevented telemetry uploads and resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 08:55:52 2026 |
|---|
| Description: | Title: Some users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint
User impact: Users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint.
More info: Some devices configured with the Telemetry Proxy Server registry may have intermittently experienced a non-reporting state, resulting in missing or delayed security telemetry in Microsoft Defender for Endpoint. Any detections that would have derived from that sensor data during the gap were not generated. Real-time endpoint protection, antivirus, device manageability, and device configuration/identity all continued to function as expected.
To attempt to identify devices that may still be impacted, they can search for devices in 'No sensor data': https://learn.microsoft.com/defender-endpoint/device-health-sensor-health-os#sensor-health--os-tab
Final status: We've identified that a service configuration update caused an issue in the sensor’s dynamic component, leaving a stale proxy configuration that prevented telemetry uploads and resulted in impact. We've deployed a configuration fix to resolve the issue. However, affected devices require a restart or they should remove and re-add the proxy registry.
Scope of impact: Impact was specific to some users utilizing devices that are configured with the Telemetry Proxy Server registry in Microsoft Defender for Endpoint.
Start time: Wednesday, May 13, 2026, at 4:14 PM UTC
End time: Wednesday, June 17, 2026, at 9:02 PM UTC
Root cause: A service configuration update caused an issue in the sensor’s dynamic component, leaving a stale proxy configuration that prevented telemetry uploads and resulted in impact.
Next steps: We're reviewing our configuration change procedures to help prevent this problem from happening again.
|
|---|
|
| Time: | Thu Jun 18 06:56:25 2026 |
|---|
| Description: | Title: Some users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint
User impact: Users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint.
Current status: We've investigated a problem with the Microsoft Defender for Endpoint service in which users may have experienced devices intermittently entering a non-reporting state in Microsoft Defender for Endpoint, and we’ve confirmed that service is now restored. We'll provide additional information in a closure summary within the “History” section of the “Service health” dashboard shortly.
Next update by: Thursday, June 18, 2026, at 1:00 PM UTC
|
|---|
|
PB1395415 - Users may have noticed discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 14 17:15:00 2026 |
|---|
| End Time: | Thu Jun 18 07:17:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Power BI and Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 18 10:03:44 2026 |
|---|
| Root Cause: | A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, was causing the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 18 08:51:22 2026 |
|---|
| Description: | Title: Users may have noticed discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may have noticed discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users included, but may not have been limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not have functioned as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not have triggered as expected due to missing utilization signals, and reporting and other metric-driven features may have been affected.
Final status: We've confirmed that the reversion of the offending change has completed successfully. Following a period of monitoring service telemetry, we've verified that service functionality has been restored and impact has been remediated.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may have been impacted by this issue.
Start time: Sunday, June 14, 2026, at 9:15 PM UTC
End time: Thursday, June 18, 2026, at 11:17 AM UTC
Root cause: A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, was causing the impact.
Next steps:
-We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 18 04:09:58 2026 |
|---|
| Description: | Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not function as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not trigger as expected due to missing utilization signals, and reporting and other metric-driven features may be affected.
Current status: We're actively monitoring the reversion of the offending change and expect it to complete by our next scheduled update.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, June 14, 2026, at 9:15 PM UTC
Root cause: A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, is causing the impact.
Next update by: Thursday, June 18, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Jun 18 03:28:34 2026 |
|---|
| Description: | Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not function as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not trigger as expected due to missing utilization signals, and reporting and other metric-driven features may be affected.
Current status: We've determined that a recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, is causing the impact. We've begun reverting the change and are actively monitoring progress. We'll provide an estimated completion time for the reversion as soon as it becomes available.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may be impacted by this issue. This section may be updated as our investigation continues.
Start time: Sunday, June 14, 2026, at 9:15 PM UTC
Root cause: A recently introduced service update, intended to improve the consistency and reliability of capacity usage reporting and related service functionality, is causing the impact.
Next update by: Thursday, June 18, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Jun 18 02:26:18 2026 |
|---|
| Description: | Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Additionally, Surge protection rules may not function as expected, for Power BI and Microsoft Fabric Premium capacities auto scale may not trigger as expected due to missing utilization signals, and reporting and other metric-driven features may be affected.
Current status: We believe that a recent change made to Microsoft Fabric libraries is causing this issue, and we're reverting this change as a potential remediation option and confirm our root cause theory.
Scope of impact: Users in UK South and East US regions attempting to view their data in the Capacity Metrics app in Microsoft Fabric may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Jun 18 02:02:06 2026 |
|---|
| Description: | Title: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric
User impact: Users may notice discrepancies in their data in the Capacity Metrics app within Microsoft Fabric.
More info: Discrepancies observed by affected users include, but may not be limited to, zero usage data for summary views in the Capacity Metrics app through Microsoft Fabric.
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CW1395054 - Some users may see multiple impact scenarios for Microsoft Copilot Researcher
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 16 10:00:00 2026 |
|---|
| End Time: | Wed Jun 17 21:05:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 17 22:13:16 2026 |
|---|
| Root Cause: | A recent update to the Microsoft Copilot Researcher service incorrectly balanced a high volume of traffic, causing requests to be routed to a portion of infrastructure that didn't have the processing availability to meet the unusual increase in demand and leading to impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 22:11:37 2026 |
|---|
| Description: | Title: Some users may see multiple impact scenarios for Microsoft Copilot Researcher
User impact: Users may have seen multiple impact scenarios for Microsoft Copilot Researcher.
More info: Specifically, users may have seen reauthentication prompts, failed queries, incomplete grounding, or query latency in Microsoft Copilot Researcher
Final status: We've completed our analysis of the system logs and service health telemetry, and we pinpointed a recent update to the Microsoft Copilot Researcher service incorrectly balanced a high volume of traffic, causing requests to be routed to a portion of infrastructure that didn't have the processing availability to meet the unusual increase in demand and leading to impact. We've disabled this update and confirmed through our monitoring that the service health has returned to normal, and impact has been remediated.
Scope of impact: Impact was limited to a small subset of users hosted on the affected infrastructure.
Start time: Tuesday, June 16, 2026, at 2:00 PM UTC
End time: Thursday, June 18, 2026, at 1:05 AM UTC
Root cause: A recent update to the Microsoft Copilot Researcher service incorrectly balanced a high volume of traffic, causing requests to be routed to a portion of infrastructure that didn't have the processing availability to meet the unusual increase in demand and leading to impact.
Next steps:
- We’re analyzing performance data associated with the impacted Microsoft Copilot Researcher scenarios infrastructure following the recent update to better understand what caused the imbalance and prevent similar impact from occurring again in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 17 20:14:25 2026 |
|---|
| Description: | Title: Some users may see multiple impact scenarios for Microsoft Copilot Researcher
User impact: Users may see multiple impact scenarios for Microsoft Copilot Researcher.
More info: Specifically, users may see reauthentication prompts, failed queries, incomplete grounding, or query latency in Microsoft Copilot Researcher
Current status: We're reviewing system logs to isolate the origin of this issue.
Scope of impact: Impact is limited to a small subset of users hosted on the affected infrastructure. This information may be updated as our investigation continues.
Next update by: Thursday, June 18, 2026, at 2:00 AM UTC
|
|---|
|
EX1386636 - Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 13 20:00:00 2026 |
|---|
| End Time: | Mon Jun 15 15:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 17 14:57:36 2026 |
|---|
| Root Cause: | A NetCore deployment introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 14:56:44 2026 |
|---|
| Description: | Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may have been unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurred only when two or more mailbox statuses were requested.
Final status: We've completed deployment of our fix across the affected environment and validated with a subset of affected users that they are now able to see the free/busy status of cross-tenant mailboxes in Exchange Online as expected.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may have been impacted.
Start time: Thursday, May 14, 2026, at 12:00 AM UTC
End time: Monday, June 15, 2026, at 7:00 PM UTC
Root cause: A NetCore deployment introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing.
Next steps:
- We're analyzing the offending NetCore deployment to validate why the potential for impact wasn't caught during our internal testing and validation phases and how we can improve our deployment implementation process moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 16 15:51:25 2026 |
|---|
| Description: | Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurs only when two or more mailbox statuses are requested.
Current status: We've validated that the source of impact was a NetCore deployment, which introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing. Our fix to address the regression is currently at 90 percent saturation in the affected environment, and we've reached out to affected users to begin testing for remediation.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may be impacted.
Start time: Thursday, May 14, 2026, at 12:00 AM UTC
Root cause: A NetCore deployment introduced a regression where headers were being dropped during free/busy status requests for cross-tenant scenarios, resulting in back-end authentication requests failing.
Next update by: Wednesday, June 17, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jun 11 15:19:09 2026 |
|---|
| Description: | Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurs only when two or more mailbox statuses are requested.
Current status: We've confirmed that it may take until our next scheduled update for this fix to saturate and remediate impact. We'll monitor the fix deployment and update the expected timeline of remediation as it progresses.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may be impacted.
Next update by: Tuesday, June 16, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 16:34:38 2026 |
|---|
| Description: | Title: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online
User impact: Users may be unable to see the free/busy status of multiple cross-tenant mailboxes in Exchange Online.
More info: This impact occurs only when two or more mailbox statuses are requested.
Current status: We've determined that our previous fix will not effectively remediate impact. We're creating a secondary targeted fix that we expect to address the issue and are confirming the timeline for deployment.
Scope of impact: Users attempting to access the free/busy status of multiple mailboxes at once may be impacted.
Next update by: Thursday, June 11, 2026, at 8:30 PM UTC
|
|---|
|
MP1394693 - Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 17 03:51:00 2026 |
|---|
| End Time: | Wed Jun 17 13:33:00 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 17 14:16:58 2026 |
|---|
| Root Cause: | A subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 14:14:33 2026 |
|---|
| Description: | Title: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
User impact: Users may have experienced delays in Data Loss Prevention alerts being generated or delivered in Microsoft Purview.
More info: Some users may have experienced delays of up to two hours between DLP activity detection and alert generation in Microsoft Purview.
Final status: We've completed our monitoring period and confirmed that our performance optimizations have successfully remediated the delays in DLP alerts being generated and delivered.
Scope of impact: Impact was specific to users experiencing delays in DLP alerts being generated or delivered in Microsoft Purview.
Start time: Wednesday, June 17, 2026, at 7:51 AM UTC
End time: Wednesday, June 17, 2026, at 5:33 PM UTC
Root cause: A subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact.
Next steps:
- We're analyzing the offending service infrastructure to isolate why it was unable to process and deliver DLP alerts as expected to further our understanding of the underlying impact scenario to determine what actions we can take to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 17 12:17:48 2026 |
|---|
| Description: | Title: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
User impact: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
More info: Some users may experience delays of up to two hours between DLP activity detection and alert generation in Microsoft Purview.
Current status: After reviewing reports of impact, we've isolated that a subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact. We've implemented performance optimizations on the affected infrastrucutre to remediate impact, and we're monitoring service availability to confirm DLP alerts are being generated and delivered as expected.
Scope of impact: Impact is specific to users experiencing delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
Start time: Wednesday, June 17, 2026, at 7:51 AM UTC
Root cause: A subset of Microsoft Purview service infrastructure utilized to process and deliver DLP alerts was operating in an unhealthy state, resulting in impact.
Next update by: Wednesday, June 17, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jun 17 11:00:11 2026 |
|---|
| Description: | Title: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview
User impact: Users may experience delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
More info: Some users may experience delays of up to two hours between DLP activity detection and alert generation in Microsoft Purview.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Impact is specific to users experiencing delays in Data Loss Prevention (DLP) alerts being generated or delivered in Microsoft Purview.
Next update by: Wednesday, June 17, 2026, at 5:00 PM UTC
|
|---|
|
TM1393859 - Users may be unable to search for locations for emergency calling in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 16 19:42:23 2026 |
|---|
| End Time: | Wed Jun 17 13:41:34 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 17 13:43:07 2026 |
|---|
| Root Cause: | A recent change meant to optimize the service contained an error that resulted in this impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 13:43:03 2026 |
|---|
| Description: | Title: Users may be unable to search for locations for emergency calling in Microsoft Teams
User impact: Users may have been unable to search for locations for emergency calling in Microsoft Teams.
More info: Affected users may have received the following error message: "We couldn't find any matches".
Final status: We confirmed that a recent change meant to optimize the service contained an error that resulted in this impact. We reverted this responsible change and have confirmed that this has successfully resolved impact.
Scope of impact: Users attempting to search for locations for emergency calling in Microsoft Teams may have been impacted by this issue.
Start time: Monday, June 8, 2026, at 5:15 PM UTC
End time: Wednesday, June 17, 2026, at 2:00 AM UTC
Root cause: A recent change meant to optimize the service contained an error that resulted in this impact.
Next steps: - We're reviewing the responsible change to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 16 20:21:13 2026 |
|---|
| Description: | Title: Users may be unable to search for locations for emergency calling in Microsoft Teams
User impact: Users may be unable to search for locations for emergency calling in Microsoft Teams.
More info: Affected users may receive the following error message: "We couldn't find any matches".
Current status: We suspect that a recent change related to emergency calling may be causing the issue and we're investigating this change to confirm our root cause theory, which will also aid in determining the next best steps towards a solution.
Scope of impact: Users attempting to search for locations for emergency calling in Microsoft Teams may be impacted by this issue. This section may be updated as our investigation continues.
Next update by: Wednesday, June 17, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Jun 16 19:51:29 2026 |
|---|
| Description: | Title: Users may be unable to search and add addresses for emergency calling in auto suggest dialog in Microsoft Teams
User impact: Users may be unable to search and add addresses for emergency calling in auto suggest dialog in Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1329446 - Unable to open files in Office for the web or Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jun 1 08:43:00 2026 |
|---|
| End Time: | Mon Jun 1 10:27:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 17 11:23:04 2026 |
|---|
| Root Cause: | During a routine service deployment, a software compatibility issue affected how a subset of servers reported operational health information within the service. As a result, traffic was not distributed as intended, causing some servers to receive a higher volume of requests than they could efficiently process. The increased load led to elevated request processing times and intermittent failures for some SharePoint and OneDrive operations, including file access, file uploads, and related service requests. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 17 10:35:25 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 3 19:48:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 11:26:52 2026 |
|---|
| Description: | Title: Unable to open files in Office for the web or Microsoft Teams
User impact: Users may have been unable to open files in Office for the web or Microsoft Teams.
More info: Impacted Office Apps included, but were not limited to:
- Excel
- PowerPoint
When users opened documents, impacted users were shown the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Final status: We've confirmed through customer reports and service telemetry that the impact has been resolved, and the service has remained stable for an extended period of time. As the issue recovered without any specific engineering actions being implemented, engineer teams continue to investigate the underlying root cause so actions can be taken to prevent the issue from reoccurring.
Scope of impact: This issue could have impacted any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Start time: Monday, June 1, 2026, at 12:43 PM UTC
End time: Monday, June 1, 2026, at 2:27 PM UTC
Root cause: During a routine service deployment, a software compatibility issue affected how a subset of servers reported operational health information within the service. As a result, traffic was not distributed as intended, causing some servers to receive a higher volume of requests than they could efficiently process. The increased load led to elevated request processing times and intermittent failures for some SharePoint and OneDrive operations, including file access, file uploads, and related service requests.
Next steps:
- Please see the Post-Incident Report (PIR) for completed list of next steps.
|
|---|
|
| Time: | Mon Jun 1 11:09:52 2026 |
|---|
| Description: | Our telemetry indicates that service availability has returned to normal levels. We're monitoring the service to confirm sustained service stability and continuing to investigate the underlying root cause of the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 1 10:27:25 2026 |
|---|
| Description: | Title: Unable to open files in Office for the web or Microsoft Teams
User impact: Users may be unable to open files in Office for the web or Microsoft Teams.
More info: Impacted Office Apps include, but are not limited to:
- Excel
- PowerPoint
When users open documents, impacted users are shown the following the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Current status: We’re continuing to analyze service telemetry and have identified elevated error rates across Office for the web experiences. We’re correlating these error patterns across service dependencies to further isolate the source of impact and determine appropriate mitigation steps.
Scope of impact: This issue could impact any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Next update by: Monday, June 1, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Jun 1 10:06:31 2026 |
|---|
| Description: | Initial analysis indicates a potential cross-service issue impacting Office for the web experiences. We’re continuing to investigate service telemetry to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 1, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Mon Jun 1 09:49:06 2026 |
|---|
| Description: | Title: Unable to open files in Office for the web.
User impact: Users may be unable to open files in Office for the web.
More info: Impacted Office Apps include, but are not limited to:
- Excel
When users open documents, impacted users are shown the following the following error message "Office Online services aren't available right now. We're working to restore all services as soon as possible. Please check back soon."
Current status: We're investigating service telemetry to isolate the source of the issue.
Scope of impact: This issue could impact any user attempting to access Office Apps using Office for the web or Microsoft Teams.
Next update by: Monday, June 1, 2026, at 2:30 PM UTC
|
|---|
|
TM1393268 - Some users in North America may have experienced issues with Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 16 09:20:00 2026 |
|---|
| End Time: | Tue Jun 16 09:50:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 16 10:12:58 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 16 10:00:11 2026 |
|---|
| Description: | Title: Some users in North America may have experienced issues with Microsoft Teams
User impact: Users in North America may have experienced issues with Microsoft Teams.
Final status: While we were in the process of analysing service monitoring telemetry to isolate the source of the problem, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Some users using Microsoft Teams in North America may have been impacted.
Start time: Tuesday, June 16, 2026, at 1:20 PM UTC
End time: Tuesday, June 16, 2026, at 1:50 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 16 09:43:15 2026 |
|---|
| Description: | Title: Some users in North America may be experiencing issues with Microsoft Teams
User impact: Users in North America may experience issues when using Microsoft Teams.
Current status: We’ve received reports of an issue affecting Microsoft Teams services in the North America region. We’re reviewing service telemetry and investigating the issue. We’ll provide an update within 30 minutes.
|
|---|
|
DZ1392272 - Some users may have been unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 10 04:50:00 2026 |
|---|
| End Time: | Mon Jun 15 16:00:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 16 09:06:38 2026 |
|---|
| Root Cause: | A recent service update to introduce an additional authorization check inadvertently resulted in onboarding issues for Microsoft Defender for Endpoint or Defender for Office 365.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 16 08:52:43 2026 |
|---|
| Description: | Title: Some users may have been unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365
User impact: Users may have been unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365.
Final status: We've confirmed with a subset of affected users that impact has been remediated.
Scope of impact: Some users attempting to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365 may have been impacted.
Start time: Wednesday, June 10, 2026, at 8:50 AM UTC
End time: Monday, June 15, 2026, at 8:00 PM UTC
Root cause: A recent service update to introduce an additional authorization check inadvertently resulted in onboarding issues for Microsoft Defender for Endpoint or Defender for Office 365.
Next steps: We’re reviewing our authorization change procedures to help prevent the issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 15 16:19:04 2026 |
|---|
| Description: | Title: Some users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365
User impact: Users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365.
Current status: We've deployed the solution and we're reaching out to a subset of affected users to validate the impact has been remediated.
Scope of impact: Some users attempting to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365 may be impacted.
Start time: Wednesday, June 10, 2026, at 8:50 AM UTC
Root cause: A recent service update to introduce an additional authorization check is resulting in the impact.
Next update by: Tuesday, June 16, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Jun 15 14:23:40 2026 |
|---|
| Description: | Title: Some users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365
User impact: Users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365.
Current status: We're validating our fix to address impact caused by the additional authorization check before we initialize deployment. We'll provide a timeline for remediation as one becomes available.
Scope of impact: Some users attempting to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365 may be impacted.
Start time: Wednesday, June 10, 2026, at 8:50 AM UTC
Root cause: A recent service update to introduce an additional authorization check is resulting in the impact.
Next update by: Monday, June 15, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jun 15 13:16:04 2026 |
|---|
| Description: | Title: Some users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365
User impact: Users may be unable to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365.
Current status: We've identified a recent service update to introduce an additional authorization check is resulting in the impact and we're developing a fix to address this issue.
Scope of impact: Some users attempting to begin onboarding for Microsoft Defender for Endpoint or Defender for Office 365 may be impacted.
Start time: Wednesday, June 10, 2026, at 8:50 AM UTC
Root cause: A recent service update to introduce an additional authorization check is resulting in the impact.
Next update by: Monday, June 15, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Jun 15 12:38:05 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Defender XDR
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft Defender XDR and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1392025 - Some users in North America may have experienced issues with Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 15 09:00:00 2026 |
|---|
| End Time: | Mon Jun 15 09:45:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 16 07:42:35 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 15 10:56:26 2026 |
|---|
| Description: | Title: Some users in North America may have experienced issues with Microsoft Teams
User impact: Users in North America may have experienced issues with Microsoft Teams.
Final status: While we were in the process of analysing service monitoring telemetry to isolate the source of the problem, system monitoring indicated that the service had returned to normal health. We've confirmed that the problem is no longer occurring, and we'll continue to monitor the service to ensure that the problem does not happen again.
Scope of impact: Some users using Microsoft Teams in North America may have been impacted.
Start time: Monday, June 15, 2026, at 1:00 PM UTC
End time: Monday, June 15, 2026, at 1:45 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 15 10:14:59 2026 |
|---|
| Description: | Title: Some users in North America may be experiencing issues with Microsoft Teams
User impact: Users in the North America may experience issues when using Microsoft Teams.
Current status: We’ve received reports indicating a potential issue affecting Microsoft Teams services in the North America region. We’re reviewing service monitoring telemetry and actively investigating. We’ll provide an update within 30 minutes.
|
|---|
|
MV1392264 - Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 14 16:12:00 2026 |
|---|
| End Time: | Mon Jun 15 23:54:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 16 00:15:51 2026 |
|---|
| Root Cause: | A recent code change resulted in a version mismatch between underlying components responsible for processing data to the affected reports.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 16 00:15:27 2026 |
|---|
| Description: | Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may have seen stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Final status: We deployed a code solution to the affected environment and confirmed through our telemetry that the impact is remediated.
Scope of impact: This issue may have affected users viewing data from Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Start time: Sunday, June 14, 2026, at 8:12 PM UTC
End time: Tuesday, June 16, 2026, at 3:54 AM UTC
Root cause: A recent code change resulted in a version mismatch between underlying components responsible for processing data to the affected reports.
Next steps: We're reviewing our service update procedures to improve our methods of detecting and preventing code issues prior to their deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 15 22:18:49 2026 |
|---|
| Description: | Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Current status: We've begun the deployment of the code solution to the remaining affected users. We're monitoring as this progresses to establish a completion timeline.
Scope of impact: This issue may affect users viewing data from Copilot dashboards and analyst workbench reports in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Sunday, June 14, 2026, at 8:12 PM UTC
Root cause: A recent code change is resulting in a version mismatch between underlying components responsible for processing data to the affected reports.
Next update by: Tuesday, June 16, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Jun 15 20:23:53 2026 |
|---|
| Description: | Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Current status: We've deployed the code solution to a majority of the affected users and are finalizing the deployment for the remaining users.
Scope of impact: This issue may affect users viewing data from Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Start time: Sunday, June 14, 2026, at 8:12 PM UTC
Root cause: A recent code change is resulting in a version mismatch between underlying components responsible for processing data to the affected reports.
Next update by: Tuesday, June 16, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Jun 15 12:41:01 2026 |
|---|
| Description: | Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Current status: We've identified that a recent code change that was deployed resulted in a version mismatch between underlying components responsible for processing data to the affected reports. We've initiated the deployment of a code fix to correct this issue and populate the affected data from the impacted time period to remediate impact for all users.
Scope of impact: This issue may affect users viewing data from Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Start time: Sunday, June 14, 2026, at 8:12 PM UTC
Root cause: A recent code change is resulting in a version mismatch between underlying components responsible for processing data to the affected reports.
Next update by: Tuesday, June 16, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Jun 15 12:27:55 2026 |
|---|
| Description: | Title: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights
User impact: Users may see stale data in Copilot dashboards and analyst workbench reports in Microsoft Viva Insights.
Current status: We're investigating a potential issue with Microsoft Viva Insights and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1310533 - Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 11 03:01:00 2026 |
|---|
| End Time: | Mon Jun 15 13:59:37 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 15 14:01:01 2026 |
|---|
| Root Cause: | Basic Authentication credentials weren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 15 14:00:51 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may have been unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may have seen an "Unknown" status for the external Gmail contacts.
Final status: We've received confirmation from additional users that were previously reporting this issue that our mitigation steps have successfully resolved this event.
Scope of impact: Impact was specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
End time: Friday, June 12, 2026, at 10:00 AM UTC
Root cause: Basic Authentication credentials weren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, which resulted in impact.
Next steps: - We're reviewing the flow of Basic Authentication credentials to better understand this impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 12 13:40:49 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: The deployment of our fix has completed as expected and we've received confirmation from a subset of users that this has successfully resolved impact. We're reaching out to additional users that were previously reporting this issue to ensure that this event has been fully remediated.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Monday, June 15, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jun 9 14:19:24 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Following our successful internal testing and validations we've deployed our solution. The deployment is approximately 81 percent complete, and user impact is expected to be addressed as it progresses. Our fix deployment timeline estimates it will have completed and that the impact will be remediated by our next scheduled communication update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Friday, June 12, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Jun 5 14:59:17 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We’ve initiated the deployment of our fix to our internal testing environment after addressing a previous blocker, which caused some delay. We're anticipating the validation process should complete by our next scheduled update, at which point we'll look to confirm a timeline for the full deployment.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Tuesday, June 09, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Jun 4 15:28:58 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: After identifying a new path for our deployment, we've determined that our fix will require an additional level of validations so we can ensure its deployment doesn't introduce any unexpected problems to the service. We're expecting more clarity into the timeline for our fix deployment and the remediation of the impact will be available once these tests have confirmed its viability.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in failures when obtaining free/busy status responses, and resulting in impact.
Next update by: Friday, June 05, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 3 15:18:23 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've completed the validation of our fix; however, we've identified that a separate issue is preventing deployments from initiating within the affected infrastructure. We're working to resolve this separate issue in order to deploy our fix and remediate impact, and we'll aim to provide a timeline for this process as one becomes available.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Thursday, June 04, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 14:48:11 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Our internal validation of the fix is ongoing as we work to ensure efficacy and confirm no adverse effects. We expect to have a timeline for the fix deployment with our next scheduled communication update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Wednesday, June 03, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Jun 1 15:26:05 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Our internal validation process for the fix has been delayed due to a deployment pipeline issue but should be underway shortly. We're expediting this process and we're hopeful it will complete on Tuesday, June 2, 2026. Once complete, we'll provide an estimate on the fix deployment timeline to all affected environments.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Tuesday, June 02, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri May 29 16:14:50 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've identified that Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact. We’ve updated the Root cause section of this communication to more accurately reflect this source of impact. We're validating a fix in our internal testing environment aimed at correcting the credential forwarding problem and will provide a timeline for its safe deployment and subsequent impact remediation as one becomes available.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: Basic Authentication credentials aren’t being correctly forwarded to the third-party service, resulting in the failures to obtain free/busy status responses and causing impact.
Next update by: Monday, June 01, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Thu May 28 19:03:57 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've confirmed the full deployment of our solution; however, we've identified through internal metrics and user feedback that impact is persisting. We're examining fresh logs from a subset of affected users to gain further insight and inform our next steps.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Next update by: Friday, May 29, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 28 13:54:37 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: Our solution is approximately 95 percent saturated throughout the affected environment and should already be alleviating impact for the bulk of affected users. We're working with a subset of affected users to validate the efficacy of our solution and obtain additional trace logs capturing the impact should this issue continue to be reproducible, in order to determine any further mitigative actions that may be required to resolve this event.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Friday, May 29, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue May 26 15:05:08 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've begun the deployment of our solution to the affected environment, and the rate of progress indicates it's on track to complete by the time of our next scheduled update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Thursday, May 28, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri May 22 13:54:48 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've initiated the deployment of our fix to our internal environment for final validations. Once complete, we'll proceed with deploying the fix to the broader affected environment. We anticipate this may take until Wednesday, May 27, 2026 to complete, and will provide an update on the deployment timeline with our next scheduled communication update.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed May 20 14:17:54 2026 |
|---|
| Description: | Title: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar
User impact: Users may be unable to view free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users may see an "Unknown" status for the external Gmail contacts.
Current status: We've completed the development of our code fix, and validation of the fix within our internal testing environment is underway. We'll provide a timeline for deployment as one becomes available.
Scope of impact: Impact is specific to any user attempting to view free/busy status for Gmail contacts in their Exchange Online calendars.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Friday, May 22, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon May 18 14:17:15 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We've received the report from your representatives that the script we provided to run as a possible workaround hasn't successfully mitigated the issue. We're now in the process of developing a code fix to fully remediate the impact.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Wednesday, May 20, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri May 15 15:02:40 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We determined a feature was recently disabled to mitigate an unrelated event, which resulted in a regression for this scenario. We've reached out to your organization and provided a script to run to address this issue, and we're awaiting confirmation that this action successfully alleviates impact.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Start time: Monday, May 11, 2026, at 7:01 AM UTC
Root cause: A feature was recently disabled to mitigate an unrelated event, resulting in this impact.
Next update by: Monday, May 18, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu May 14 18:29:37 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We've discovered a similar ongoing service incident and are working to confirm correlation with that event as a part of our root cause investigation. We're continuing to leverage the documentation provided by your organization, such as the HTTP Archive format (HAR) logs, as a part of this active investigation.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Next update by: Friday, May 15, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu May 14 14:25:32 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We're continuing our review of support case data while analyzing recent service updates and service-side logging to progress the investigation.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Next update by: Thursday, May 14, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu May 14 12:59:25 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
More info: Affected users are seeing an "Unknown" status for the external Gmail contacts.
Current status: We're reviewing support case details to better understand the impact scenario and determine our next diagnostic steps.
Scope of impact: Your organization is impacted by this event, and all users attempting to view free/busy status for Gmail contacts in their Exchange Online calendars are affected.
Next update by: Thursday, May 14, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu May 14 12:41:41 2026 |
|---|
| Description: | Title: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar
User impact: Users aren't seeing free/busy status for Gmail users within the Exchange Online calendar.
Current status: We're investigating a potential issue with free/busy in Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1390337 - Users may be unable to access a recently introduced feature in the Microsoft Copilot Studio Agent Builder
| Status: | serviceRestored |
|---|
| Start Time: | Sat Jun 13 18:44:03 2026 |
|---|
| End Time: | Sat Jun 13 20:38:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jun 13 20:53:18 2026 |
|---|
| Root Cause: | A recent change related to how version strings were read prevented the service infrastructure from identifying which features were available to users. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jun 13 20:53:00 2026 |
|---|
| Description: | Title: Users may be unable to access a recently introduced feature in the Microsoft Copilot Studio Agent Builder
User impact: Users may have been intermittently unable to copy an agent created through the Agent Builder into the full Copilot Studio.
Final status: We've completed deploying our aforementioned targeted fix and confirmed with our service telemetry that this issue is resolved.
Scope of impact: One percent of users who attempted to copy an agent created through the Agent Builder into the full copilot studio were intermittently impacted by this issue.
Start time: Monday, June 8, 2026, at 4:47 PM UTC
End time: Saturday, June 14, 2026, at 12:38 AM UTC
Root cause: A recent change related to how version strings were read prevented the service infrastructure from identifying which features were available to users.
Next steps:
- We're investigating the impacting recent change to pinpoint why this issue wasn't caught prior to deployment so that we better prevent the inability to access some features in the Microsoft Copilot Studio Agent Builder in the future.
This is the final update.
|
|---|
|
| Time: | Sat Jun 13 19:35:24 2026 |
|---|
| Description: | Title: Users may be unable to access a recently introduced feature in the Microsoft Copilot Studio Agent Builder
User impact: Users may be intermittently unable to copy an agent created through the Agent Builder into the full Copilot Studio.
Current status: We've been made aware of an issue in which users may intermittently be unable to copy an agent created through the Agent Builder into the full Copilot studio. We've determined that a recent change related to how version strings are read prevented the service infrastructure from identifying which features are available to users. We're deploying a targeted fix to address this version string issue, and we anticipate this will complete by our next scheduled communications update.
Scope of impact: One percent of users attempting to copy an agent created through the Agent Builder into the full copilot studio are intermittently impacted by this issue. This section may be updated as our investigation progressed.
Start time: Monday, June 8, 2026, at 4:47 PM UTC
Root cause: A recent change related to how version strings are read prevented the service infrastructure from identifying which features are available to users
Next update by: Sunday, June 14, 2026, at 1:30 AM UTC
|
|---|
|
MO1385610 - Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 9 20:00:00 2026 |
|---|
| End Time: | Fri Jun 12 23:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jun 13 10:59:33 2026 |
|---|
| Root Cause: | A delay in our upstream process for Copilot source data was preventing Copilot usage reports from publishing up-to-date data and was resulting in delayed reporting.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jun 13 10:47:43 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Copilot usage reports within the Microsoft 365 admin center may have been delayed.
More info: The affected Copilot usage reports consisted of the following:
-Microsoft 365 Copilot usage reports
-Microsoft 365 Copilot Chat usage reports
-Microsoft Graph API Copilot usage reports
These reports may have been delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Final status: We've completed the restatement process to backfill delayed data and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may have been impacted by this event.
Start time: Wednesday, June 10, 2026, at 12:00 AM UTC
End time: Saturday, June 13, 2026, at 3:00 AM UTC
Root cause: A delay in our upstream process for Copilot source data was preventing Copilot usage reports from publishing up-to-date data and was resulting in delayed reporting.
Next steps:
- We're reviewing our upstream Copilot source data processes to determine what caused the delay, so that we can prevent similar instance of impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jun 12 17:16:56 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed.
More info: The affected Copilot usage reports consist of the following:
-Microsoft 365 Copilot usage reports
-Microsoft 365 Copilot Chat usage reports
-Microsoft Graph API Copilot usage reports
These reports may be delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Current status: The block that was preventing our restatement process from proceeding has been cleared, and our restatement process has been resumed. We expect this will complete, backfilling the delayed data and remediating impact, by our next scheduled communication update.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, June 10, 2026, at 12:00 AM UTC
Root cause: A delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting.
Next update by: Saturday, June 13, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu Jun 11 17:57:51 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed.
More info: The affected Copilot usage reports consist of the following:
-Microsoft 365 Copilot usage reports
-Microsoft 365 Copilot Chat usage reports
-Microsoft Graph API Copilot usage reports
These reports may be delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Current status: Our restatement process has encountered a block which we're working to resolve. We'll establish a remediation timeline once this process resumes.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, June 10, 2026, at 12:00 AM UTC
Root cause: A delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting.
Next update by: Friday, June 12, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 16:46:31 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Copilot usage reports within the Microsoft 365 admin center may be delayed.
More info: The affected Copilot usage reports consist of the following:
-Microsoft 365 Copilot usage reports
-Microsoft 365 Copilot Chat usage reports
-Microsoft Graph API Copilot usage reports
These reports may be delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Current status: As our investigation into the source of the delay in our upstream process is ongoing, we've begun a restatement process on affected data as a means to remediate impact. Once this restatement process is complete, we'll work to establish a timeline for data backfill to complete and issue resolution.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, June 10, 2026, at 12:00 AM UTC
Root cause: A delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting.
Next update by: Thursday, June 11, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Jun 9 19:46:12 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 Copilot usage reports within the Microsoft 365 admin center may be delayed
User impact: Admins' Copilot usage reports within the Microsoft 365 admin center may be delayed.
More info: The affected Copilot usage reports consist of the following:
-Microsoft 365 Copilot usage reports
-Microsoft 365 Copilot Chat usage reports
-Microsoft Graph API Copilot usage reports
These reports may be delayed as of Wednesday, June 10, 2026, at 12:00 AM UTC.
Current status: Our service telemetry alerted us to an issue in which admins in North America and Asia Pacific regions may receive Copilot usage reports delayed through the Microsoft admin center. We've identified that a delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting. We're examining this affected upstream process to pinpoint the underlying cause for the delay and to develop a remediation strategy.
Scope of impact: Any admin located in North America and Asia Pacific regions attempting to view up to date affected Copilot usage reports through the Microsoft 365 admin center listed in the more info section may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A delay in our upstream process for Copilot source data is preventing Copilot usage reports from publishing up-to-date data and is resulting in delayed reporting.
Next update by: Wednesday, June 10, 2026, at 10:30 PM UTC
|
|---|
|
EX1327187 - Some users may be unable to create new online meetings from shared calendar events in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 30 05:11:59 2026 |
|---|
| End Time: | Fri Jun 12 15:49:50 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 12 15:49:55 2026 |
|---|
| Root Cause: | A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service which resulted in the impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 12 11:38:15 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may have been unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users could create online meetings from their personal calendars as an alternative method, and existing shared calendar events remained unaffected.
Final status: We've confirmed that the fix to address the impact to the authorization component of the calendar service has completed and, after monitoring service health metrics to ensure the associated failures have ceased, we've verified the impact is remediated.
Scope of impact: Impact was specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
End time: Friday, June 12, 2026, at 7:49 PM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service which resulted in the impact.
Next steps:
- We're reviewing our updates standards to ensure similar issues are identified and corrected ahead of deployment to prevent this from reoccurring.
|
|---|
|
| Time: | Tue Jun 9 13:40:51 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: The deployment of the fix has saturated 89 percent of the affected environment, and our projection based on the current rate of the deployment indicates the impact will be remediated for all remaining users by the time of our next scheduled update.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Saturday, June 13, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jun 8 12:32:39 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: We've completed our validation of the fix, and it is currently deployed with a saturation progress of 87 percent. Some users may already see the issue mitigated as this continues to saturate all affected areas. We're continuing to monitor the deployment and anticipate having an update on its completion timeline at our next communication.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 9, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jun 4 12:19:19 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Validation of our solution to address the affected authorization component is underway, and we'll provide a timeline for deployment as one becomes available.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Monday, June 8, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 12:35:57 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: The development and validation of the code fix is taking longer than expected due to an issue that's unrelated to this event. We're working to resolve these issues and once complete, we'll proceed with the validation of the code fix.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Thursday, June 4, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 13:09:25 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Our work on developing and validating the code fix continues. The additional time ensures that all impacted areas are captured in the fix and helps us verify its effectiveness before beginning deployment.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 2, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 13:09:23 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Our work on developing and validating the code fix continues. The additional time ensures that all impacted areas are captured in the fix and helps us verify its effectiveness before beginning deployment.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 2, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 13:09:22 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: Our work on developing and validating the code fix continues. The additional time ensures that all impacted areas are captured in the fix and helps us verify its effectiveness before beginning deployment.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Tuesday, June 2, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat May 30 14:40:06 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
More info: Affected users can create online meetings from their personal calendars as an alternative method, and existing shared calendar events remain unaffected.
Current status: We've identified that a recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact. We're developing and validating a code fix to address the issue and will provide a deployment timeline once it becomes available.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Root cause: A recent service update in Exchange Online introduced an issue within an authorization component of the calendar service, resulting in impact.
Next update by: Monday, June 1, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat May 30 09:28:14 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
Current status: We’re continuing to investigate the issue that is causing failures when obtaining authentication tokens within the calendar service. We’re also continually working to validate if the aforementioned service update is contributing to impact, and what remediation actions are required.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Start time: Saturday, May 9, 2026, at 1:16 AM UTC
Next update by: Saturday, May 30, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Sat May 30 07:20:43 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
Current status: We’re investigating an issue that is causing failures when obtaining authentication tokens within the calendar service. We’ve identified a potential correlation with a recent service update and are testing mitigation actions to validate impact and confirm a resolution path.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Next update by: Saturday, May 30, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Sat May 30 05:13:46 2026 |
|---|
| Description: | Title: Some users may be unable to create new online meetings from shared calendar events in Exchange Online
User impact: Users may be unable to create new online meetings from shared calendar events in Exchange Online.
Current status: We’re reviewing service telemetry to isolate the root cause of the issue and determine a fix.
Scope of impact: Impact is specific to some users attempting to create new online meetings from shared calendar events in Exchange Online.
Next update by: Saturday, May 30, 2026, at 11:30 AM UTC
|
|---|
|
PB1387136 - Some users may have experienced failures when attempting to connect to Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 8 19:40:00 2026 |
|---|
| End Time: | Wed Jun 10 03:50:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 12 06:50:36 2026 |
|---|
| Root Cause: | A recent service change in Microsoft Fabric connectivity layer altered the default database selection behaviour, causing queries to fail for some users and resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 12 06:28:44 2026 |
|---|
| Description: | Title: Some users may have experienced failures when attempting to connect to Microsoft Fabric
User impact: Users may have experienced failures when attempting to connect to Microsoft Fabric.
More info: Users connecting to Microsoft Fabric (Data Warehouse) without specifying a database may have landed on the master database by default. When users ran three-part queries (e.g., dbname.dbo.table) from the master database, the query failed with an error message. As a result, users were unable to successfully execute those queries unless they specified or switched to the correct database first.
As a workaround, users could specify the database name in connection properties or added a new line "USE " while querying from database.
Final status: We’ve confirmed that after reverting the recent change and monitoring service telemetry, the issue is no longer occurring.
Scope of impact: Impact was specific to some users in the United States and the United Kingdom who were attempting to connect to Microsoft Fabric.
Start time: Monday, June 8, 2026, at 11:40 PM UTC
End time: Wednesday, June 10, 2026, at 7:50 AM UTC
Root cause: A recent service change in Microsoft Fabric connectivity layer altered the default database selection behaviour, causing queries to fail for some users and resulting in impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 11 05:25:36 2026 |
|---|
| Description: | Title: Some users may experience failures when attempting to connect to Microsoft Fabric
User impact: Users may experience failures when attempting to connect to Microsoft Fabric.
More info: Users connecting to Microsoft Fabric (Data Warehouse) without specifying a database may land on the master database by default. When users run three-part queries (e.g., dbname.dbo.table) from the master database, the query fails with an error message. As a result, users are unable to successfully execute those queries unless they specify or switch to the correct database first.
As a workaround, users can specify the database name in connection properties or add a new line "USE " while querying from database.
Current status: We've identified that a recent service change in Microsoft Fabric connectivity layer altered the default database selection behaviour, causing queries to fail for some users. We're working to revert this change to mitigate impact, and we're conducting a period of monitoring service telemetry to verify its success in mitigating impact.
Scope of impact: Impact is specific to some users in the United States and the United Kingdom who are attempting to connect to Microsoft Fabric.
Root cause: A recent service change in Microsoft Fabric connectivity layer altered the default database selection behaviour, causing queries to fail for some users and resulting in impact.
Next update by: Friday, June 12, 2026, at 11:30 AM UTC
|
|---|
|
CP1386444 - Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 9 02:00:00 2026 |
|---|
| End Time: | Thu Jun 11 14:10:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 11 18:19:13 2026 |
|---|
| Root Cause: | Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 11 18:18:59 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may have experienced degradation with Copilot responses after uploading a file.
More info: Affected users have been returned an error message stating, "Oops! Something happened. Can you try again?"
Affected users have been returned an error message stating, "Oops! Something happened. Can you try again?"
Users reported low-quality responses or hallucinations when Copilot was prompted to respond on content within uploaded files.
Additionally, users who attempted to send a message with file grounding may have received the following response, "I tried to open your file {file name}, but I’m currently unable to retrieve its contents due to an access/activity limit on the file."
Final status: We've completed the scale-out of our configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads. After a period of monitoring for file upload traffic across affected regions, we've confirmed that our actions successfully remediated impact.
Scope of impact: Some users may have experienced degradation with Copilot responses after uploading a file.
Start time: Tuesday, June 9, 2026, at 6:00 AM UTC
End time: Thursday, June 11, 2026, at 6:10 PM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next steps:
- We're continuing to monitor previously affected traffic to confirm what additional performance optimizations we can implement to further improve the resiliency of our service to prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 11 14:11:17 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Additionally, users attempting to send a message with file grounding may receive the following response, "I tried to open your file {file name}, but I’m currently unable to retrieve its contents due to an access/activity limit on the file."
Current status: We've identified another facet of the impacted user experience in that users sending messages with file grounding may receive a response noting Copilot can't retrieve contents due to an access or activity limit, and we've updated the More info section of this communication with this information. Our previously communicated status remains accurate, as we monitor file upload traffic across affected regions to confirm our changes are remediating the impact and scale out our configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 21:01:47 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Current status: We've added additional resources to regions that were experiencing high demand, and we're monitoring file upload traffic over the next 12-14 hours across affected regions to confirm if our changes are assisting with remediation. Simultaneously, we’re also scaling out a configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads to additional affected regions to assist with our remediation efforts.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 16:24:16 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Current status: We're implementing a configuration change to prevent indefinite retries from occurring during OneDrive or SharePoint Online file uploads along with implementing performance optimizations on affected service infrastructure to assist with processing the requests.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Next update by: Thursday, June 11, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jun 10 14:20:01 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Current status: After analyzing service telemetry for file upload scenarios for Copilot, we've isolated that unexpected increased request volume is causing our retry logic for Microsoft OneDrive and SharePoint Online file uploads to retry indefinitely, causing degradation in Copilot responses. We're working to isolate the source of the increased traffic to validate the root cause of impact and to determine our next remediation actions.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Next update by: Wednesday, June 10, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 13:15:46 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot responses after uploading a file
User impact: Users may experience degradation with Copilot responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot is prompted to respond on content within uploaded files.
Current status: We're analyzing service telemetry for file upload scenarios for Copilot to isolate when the degradation started and to determine our next troubleshooting steps.
Scope of impact: Some users may experience degradation with Copilot responses after uploading a file. This section may be updated as the investigation progresses.
Next update by: Wednesday, June 10, 2026, at 6:30 PM UTC
|
|---|
|
CW1386443 - Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 9 02:00:00 2026 |
|---|
| End Time: | Thu Jun 11 14:10:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 11 18:18:20 2026 |
|---|
| Root Cause: | Normal growth in Microsoft 365 Copilot Chat usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 11 18:17:43 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may have experienced degradation with Copilot Chat responses after uploading a file.
More info: Affected users may have been returned an error message stating, "Oops! Something happened. Can you try again?"
Users reported low-quality or inaccurate responses when Copilot Chat was prompted to respond on content within uploaded files.
Additionally, users who attempted to send a message with file grounding may have received the following response, "I tried to open your file {file name}, but I’m currently unable to retrieve its contents due to an access/activity limit on the file."
Final status: We've completed the scale-out of our configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads. After a period of monitoring for file upload traffic across affected regions, we've confirmed that our actions successfully remediated impact.
Scope of impact: Some users may have experienced degradation with Copilot Chat responses after uploading a file.
Start time: Tuesday, June 9, 2026, at 6:00 AM UTC
End time: Thursday, June 11, 2026, at 6:10 PM UTC
Root cause: Normal growth in Microsoft 365 Copilot Chat usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next steps:
- We're continuing to monitor previously affected traffic to confirm what additional performance optimizations we can implement to further improve the resiliency of our service to prevent similar impact scenarios from occurring in the future.
|
|---|
|
| Time: | Thu Jun 11 14:11:10 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality or inaccurate responses when Copilot Chat is prompted to respond on content within uploaded files.
Additionally, users attempting to send a message with file grounding may receive the following response, "I tried to open your file {file name}, but I’m currently unable to retrieve its contents due to an access/activity limit on the file."
Current status: We've identified another facet of the impacted user experience in that users sending messages with file grounding may receive a response noting Copilot Chat can't retrieve contents due to an access or activity limit, and we've updated the More info section of this communication with this information. Our previously communicated status remains accurate, as we monitor file upload traffic across affected regions to confirm our changes are remediating the impact and scale out our configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jun 11 11:55:30 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality or inaccurate responses when Copilot Chat is prompted to respond on content within uploaded files.
Current status: We've added additional resources to regions that were experiencing high demand, and we're monitoring file upload traffic over the next 12-14 hours across affected regions to confirm if our changes are assisting with remediation. Simultaneously, we’re also scaling out a configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads to additional affected regions to assist with our remediation efforts.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: Normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 21:00:53 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality or inaccurate responses when Copilot Chat is prompted to respond on content within uploaded files.
Current status: We’re adding resources in regions that were experiencing high demand and gradually allowing more file upload traffic to resume. We’re also implementing a configuration change to prevent retries from adding more load during OneDrive or SharePoint Online file uploads. We’ll monitor the affected environment during peak usage periods to confirm whether the added resources are sufficient to fully mitigate impact.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Root cause: We’ve determined that normal growth in Microsoft 365 Copilot usage exceeded the available resources needed to process OneDrive and SharePoint Online file upload requests, causing some requests to process slower or fail.
Next update by: Thursday, June 11, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jun 10 16:23:51 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot Chat is prompted to respond on content within uploaded files.
Current status: We're implementing a configuration change to prevent indefinite retries from occurring during OneDrive or SharePoint Online file uploads along with implementing performance optimizations on affected service infrastructure to assist with processing the requests.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Start time: Tuesday, June 09, 2026, at 6:00 AM UTC
Next update by: Thursday, June 11, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jun 10 14:18:49 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot Chat is prompted to respond on content within uploaded files.
Current status: After analyzing service telemetry for file upload scenarios for Copilot Chat, we've isolated that unexpected increased request volume is causing our retry logic for Microsoft OneDrive and SharePoint Online file uploads to retry indefinitely, causing degradation in Copilot Chat responses. We're working to isolate the source of the increased traffic to validate the root cause of impact and to determine our next remediation actions.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Next update by: Wednesday, June 10, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Jun 10 13:14:51 2026 |
|---|
| Description: | Title: Some users may experience degradation with Microsoft 365 Copilot Chat responses after uploading a file
User impact: Users may experience degradation with Copilot Chat responses after uploading a file.
More info: Affected users may be returned an error message stating, "Oops! Something happened. Can you try again?"
Users report low-quality responses or hallucinations when Copilot Chat is prompted to respond on content within uploaded files.
Current status: We're analyzing service telemetry for file upload scenarios for Copilot Chat to isolate when the degradation started and to determine our next troubleshooting steps.
Scope of impact: Some users may experience degradation with Copilot Chat responses after uploading a file. This section may be updated as the investigation progresses.
Next update by: Wednesday, June 10, 2026, at 6:30 PM UTC
|
|---|
|
FL1327422 - Users are experiencing intermittent flow runtime and flow management operations failures
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Sat May 30 08:00:00 2026 |
|---|
| End Time: | Sat May 30 16:51:00 2026 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 11 14:54:03 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 11 14:54:03 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jun 4 10:08:46 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Sat May 30 17:22:26 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users experienced intermittent flow runtime and flow management operations failures.
More info: Impact may have been experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Final Status: We completed applying configuration changes and restarting the impacted infrastructure and confirmed that impact persisted. To mitigate the issue, we then performed a failover to healthy, redundant storage infrastructure and, following a period of service health diagnostic analysis, we confirmed that functionality is restored.
A Post Incident Report will be published within five days.
Preliminary Root Cause: High resource utilization within a portion of the storage infrastructure supporting flow runtime and flow management operations.
Next Steps: We’re reviewing our code for improved performance and potential automated recovery options to reduce or avoid similar issues in the future.
|
|---|
|
| Time: | Sat May 30 13:24:58 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
More info: Impact may be experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Current Status: Following additional investigation, we have identified high resource utilization within the impacted storage infrastructure. As initial mitigating actions, we are applying configurations changes to address the resource utilization and are performing restarts of the impacted infrastructure.
Next Update: Sunday, May 31, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sat May 30 11:34:33 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
More info: Impact may be experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Current Status: After an initial investigation, we determined that a portion of the storage infrastructure supporting flow runtime and flow management operations has entered an unhealthy state, leading to impact. We are continuing to investigate to further isolate the root cause of the impact and to develop a strategy for mitigation.
Next Update: Saturday, May 30, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Sat May 30 11:13:34 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
More info: Impact may be experienced for Power Automate flows and agent flows in Microsoft Copilot Studio.
Current Status: We are continuing to investigate an issue in which users are experiencing intermittent flow runtime and flow management operation failures.
Next Update: Saturday, May 30, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat May 30 10:44:18 2026 |
|---|
| Description: | Title: Users are experiencing intermittent flow runtime and flow management operations failures
User impact: Users are experiencing intermittent flow runtime and flow management operations failures.
Current Status: We are aware of an emerging issue where users are experiencing intermittent flow runtime and flow management operations failures. 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.
|
|---|
|
EX1331830 - Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Jun 2 09:03:00 2026 |
|---|
| End Time: | Wed Jun 3 14:03:39 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 10 19:52:41 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 10 19:52:41 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jun 5 19:08:07 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jun 5 19:07:52 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 3 14:07:00 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may have experienced significant delays or failures in sending and receiving email messages in Exchange Online
More info: Affected users may have received a 421 4.3.2 error code that states "Cannot establish session with remote server."
Final status: After a period of extended monitoring, we've confirmed that customer impact was fully resolved.
Scope of impact: Users located in North America, Europe, and the Asia-Pacific regions who attempted to send or receive email messages in Exchange Online may have experienced delays or failures completing these actions.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
End time: Tuesday, June 02, 2026, at 11:00 PM UTC
Preliminary root cause: A configuration issue prevented some Exchange email delivery systems from properly distributing traffic load, reducing available capacity in several regions and causing increased traffic on remaining systems, which resulted in email delivery delays and disruptions.
Next steps:
-To help identify similar issues earlier and prevent impact in the future, we're further reviewing our traffic routing processes and monitoring systems.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Jun 3 12:59:37 2026 |
|---|
| Description: | We're continuing to observe strong system stability across the previously impacted environment and we expect we'lll be able to confirm the issue is fully resolved by our next scheduled update.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 3 11:50:28 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. We'll continue to monitor service health and take any necessary actions to remediate residual impact.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server."
Current status: Our transition to the functional legacy mechanism across the affected infrastructure has completed successfully. This change will help distribute email traffic more evenly across the service and adds additional resiliency to the impacted environment. In our review of system logging we've identified a configuration issue that prevented some Exchange email delivery systems from properly distributing traffic load, which is a likely source of underlying impact. We are continuing to validate this potential root cause.
Current telemetry indicates that email sending and delivery services continue to remain stable with no observable impact. We’ll continue monitoring to ensure service stability through peak North America business hours.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Preliminary root cause: A configuration issue prevented some Exchange email delivery systems from properly distributing traffic load, reducing available capacity in several regions and causing increased traffic on remaining systems, which resulted in email delivery delays and disruptions.
Next update by: Wednesday, June 03, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 09:56:07 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're continuing to apply a change to transition to a functional legacy mechanism across the remaining affected infrastructure. This task is progressing as expected, and we're monitoring the change as it progresses to ensure it delivers the expected resolution. We're analyzing telemetry closely, and we've observed an increase in service availability within the infrastructure that the change has been successfully applied to. In parallel, we're leading a separate investigation to identify a suspected issue which may have caused the email delivery and sending delays. We're conducting additional targeted restarts of service components and infrastructure to identify if any additional troubleshooting, or mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 09:07:57 2026 |
|---|
| Description: | We're closely monitoring the transition to a proven legacy mechanism across the remaining affected infrastructure, and this is progressing as expected. We're analyzing service telemetry, and we're continuing to observe an increase in service availability as this task is underway.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 3 07:56:03 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're applying a change to transition to a proven legacy mechanism to mitigate impact. We've observed an increase in service availability within the infrastructure in which this change has already been completed, and we're closely tracking the progress of this change within the remaining affected infrastructure to ensure the expected resolution is achieved. Additionally, we're conducting an investigation into a potential issue which may have created the initial impact, causing email delivery and sending delays. To verify this theory, we're conducting additional troubleshooting steps, including targeted restarts, to determine if any other mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 07:11:21 2026 |
|---|
| Description: | As previously mentioned, we’re not seeing delays in sending and receiving email messages at this time. We're continuing to observe an overall improvement in service availability since conducting the transition to the legacy mechanism, and we're monitoring this closely as it is applied to the remaining infrastructure to ensure this progresses as expected.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jun 3 05:55:00 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're continuing to make targeted adjustments, including a transition to a proven legacy mechanism to mitigate impact. Early reports from service telemetry indicate an improvement in service availability, and we're monitoring this closely to ensure this trend continues. In parallel, we're conducting further investigation into a potential issue which may have contributed to the email delivery and sending delays, and we're completing additional troubleshooting steps to determine if any other mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 03:58:34 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Affected users may receive a 421 4.3.2 error code that states "Cannot establish session with remote server.".
Current status: We're monitoring service health telemetry closely to ensure the targeted adjustments we've made are continuing to mitigate impact. In parallel, we're continuing to investigate a potential issue which may have contributed to the email delivery and sending delays to verify if any additional mitigation actions are required.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Jun 3 01:53:03 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Current status: We’ve made progress in the investigation and identified a potential issue that may have contributed to the email delivery and sending delays. We’ve implemented targeted adjustments to improve related processing behavior and are actively monitoring the service to validate recovery and confirm continued stability.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 23:50:20 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: At this time, we’re not seeing delays in sending and receiving email messages. This status may change as investigation and mitigation activities progress.
Current status: We’ve continued monitoring traffic patterns and are currently not observing delays affecting sending or receiving email messages. We’re remaining actively engaged around the clock to monitor service health, analyze telemetry, and implement targeted actions as needed to help maintain service stability and improve overall performance.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 21:57:45 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’ve continued making progress in our investigation to isolate the root cause and identify additional mitigation opportunities. We’re actively analyzing telemetry and traffic patterns across the affected infrastructure to help drive targeted modifications and improve overall service stability and performance.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 21:40:28 2026 |
|---|
| Description: | Investigation efforts remain ongoing as we continue narrowing the potential root causes and evaluating mitigation opportunities to support full service recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 20:58:30 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: Our investigation efforts remain ongoing to isolate the root cause of delays affecting email sending and receiving. We’ll continue reviewing traffic distribution across the infrastructure to identify and implement targeted actions that will help restore the service to normal operations.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 20:28:23 2026 |
|---|
| Description: | Our investigation efforts remain ongoing as we work to determine the root cause and implement additional mitigations as needed to expedite recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 19:58:30 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’re continuing to analyze network traffic volumes to isolate the underlying cause of impact and support our recovery efforts. Email queues have stabilized at pre-incident levels, and we’ll continue monitoring traffic patterns as recovery efforts progress.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 19:26:57 2026 |
|---|
| Description: | We've confirmed that the backlog of message queues has returned to pre-incidents levels. We're still working to isolate the root cause and identify additional mitigations to safeguard the service environment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 19:00:06 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’re continuing to investigate a potential network distribution issue that resulted in certain servers receiving a higher volume of traffic than expected. While we work to confirm this as an underlying cause of impact, we are still observing steady recovery with mail queues approaching pre-incident levels.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Wednesday, June 03, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 18:39:52 2026 |
|---|
| Description: | We identified a potential traffic distribution issue that may have caused imbalances in mail distribution across the affected infrastructure and we're working to confirm whether this is the source of impact for this incident.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 18:04:36 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We're continuing to observe steady improvements in the reduction of message queue volume, in the portion of affected infrastructure where we completed our configuration change deployment and machine restarts. We're continuing to examine system logging and trends in mail delivery in order to isolate a root cause and identify further mitigations.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Tuesday, June 02, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 17:35:23 2026 |
|---|
| Description: | Our targeted restarts have reached approximately 50 percent of impacted machines and we're continuing to observe steady improvements in reducing message queue volume.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 17:00:46 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We've observed improved message throughput in the sample machines where the configuration change was deployed. We're continuing with a batched deployment of the configuration change and staggered restarts across the impacted infrastructure. We're continuing to work with highest priority to identify additional service optimizations to expedite full resolution of this issue.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Tuesday, June 02, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 16:45:40 2026 |
|---|
| Description: | We've deployed the flight and are restarting the service on the subset of targeted machines to activate the configuration changes. We'll closely monitor the health of the targeted machines to confirm the efficacy of the flight deployment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 16:23:51 2026 |
|---|
| Description: | We're preparing a flight to test configuration changes on a subset of impacted infrastructure intended to further drive down memory usage and drain message queues. If successful, we'll deploy the configuration changes broadly.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 16:00:16 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: In the subset of the affected environment where we disabled the high-memory component, we found that the improvements to the mail queues were temporary. We’re now evaluating targeted service infrastructure resets as a mitigation step, and collecting fresh system trace logs to help determine the next remediation actions.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Start time: Tuesday, June 02, 2026, at 1:03 PM UTC
Next update by: Tuesday, June 02, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 15:29:30 2026 |
|---|
| Description: | We've deployed the flight to disable the high memory usage component to a subset of infrastructure and are observing some improvements in the service environment. We're running additional tests to determine whether expanding this fix will result in full remediation.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Jun 2 15:00:52 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We've identified a service component that is consuming a high amount of system memory, which could be contributing to impact. We're preparing a flight to disable this component as a potential mitigation and expect to deploy it within the next hour.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Next update by: Tuesday, June 02, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 13:14:24 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We've received reports of impact for users in the Asia-Pacific (APAC) and Europe regions, and we've expanded our communications to encompass all potentially affected users and have updated the "Scope of impact" field of our communications to reflect this change. We're analyzing the mail queue backlog for affected regions to further our understanding of the current impact scenario and to isolate potential points of failure contributing to impact.
Scope of impact: Impact is specific to users located in North America, Europe, or the Asia-Pacific regions attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Next update by: Tuesday, June 02, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 11:55:29 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays or failures in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We're reviewing additional reports from customers in the North America and Germany regions to further our understanding of the current impact scenario, to isolate error messages affected users are receiving, and to determine our next troubleshooting steps.
Scope of impact: Impact is specific to users located in North America and Germany attempting to send and receive email messages in Exchange Online who may experience delays or failures completing these actions. This section may be updated as the investigation progresses.
Next update by: Tuesday, June 02, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 10:40:02 2026 |
|---|
| Description: | Title: Users may be experiencing significant delays in sending and receiving email messages in Exchange Online
User impact: Users may be experiencing significant delays in sending and receiving email messages in Exchange Online
More info: Users are experiencing significant delays in sending and receiving email messages, with some email messages remaining undelivered for over an hour.
Current status: We’re analyzing support case details to determine the next steps needed to resolve this issue.
Scope of impact: Impact is specific to users located in North America and Germany attempting to send and receive email messages in Exchange Online.
Next update by: Tuesday, June 02, 2026, at 4:30 PM UTC
|
|---|
|
WP1384473 - Users will see intermittent connection drops for Windows 365 Cloud PCs
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 8 18:30:00 2026 |
|---|
| End Time: | Wed Jun 10 00:15:00 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 10 16:01:37 2026 |
|---|
| Root Cause: | Unplanned maintenance for the Windows 365 service is causing intermittent connectivity drops.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 10 15:14:42 2026 |
|---|
| Description: | Title: Users will see intermittent connection drops for Windows 365 Cloud PCs
User impact: Users saw intermittent connection drops for Cloud PCs.
Final status: We've completed our unplanned maintenance for the Windows 365 service, and we confirmed connection interruptions have ceased and impact is remediated.
Scope of impact: Your organization was affected by this event, and the issue impacted any user of a Cloud PC.
Start time: Monday, June 08, 2026, at 10:30 PM UTC
End time: Wednesday, June 10, 2026, at 4:15 AM UTC
Root cause: Unplanned maintenance for the Windows 365 service is causing intermittent connectivity drops.
Next steps:
- We're reviewing opportunities to improve our maintenance scheduling and avoid similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 8 19:49:17 2026 |
|---|
| Description: | Title: Users will see intermittent connection drops for Windows 365 Cloud PCs
User impact: Users will see intermittent connection drops for Cloud PCs.
Current status: We're performing unplanned maintenance for the Windows 365 service. During the time of deployment, users may see brief connection interruptions on their Cloud PCs. We anticipate that most of these sessions will recover automatically, however if a session does not reconnect, a manual reconnect will restore access. We'll monitor the deployment to ensure that the impact is remediated.
Scope of impact: Your organization is affected by this event, and the issue impacts any user utilizing a Cloud PC. This information may be updated as our investigation continues.
Start time: Monday, June 08, 2026, at 10:30 PM UTC
Root cause: Unplanned maintenance for the Windows 365 service is causing intermittent connectivity drops.
Next update by: Wednesday, June 10, 2026, at 7:30 PM UTC
|
|---|
|
MO1385847 - Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jun 5 13:42:00 2026 |
|---|
| End Time: | Wed Jun 10 01:17:51 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 10 01:18:58 2026 |
|---|
| Root Cause: | A recent deployment didn't enable a feature in all environments as expected.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 10 01:18:55 2026 |
|---|
| Description: | Title: Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI
User impact: Users’ workflows intermittently failed in Microsoft Fabric and Microsoft Power BI.
More info: The impacted workflows included the following:
- Prep Data for AI
- Copilot data questions
- Q&A Visual
Final status: We completed disabling the feature and after a period of monitoring, we confirmed impact is remediated.
Scope of impact: Your organization was affected by this event, and some users attempting the affected workflows were intermittently impacted.
Start time: Friday, June 05, 2026, at 5:42 PM UTC
End time: Wednesday, June 10, 2026, at 4:50 AM UTC
Root cause: A recent deployment didn't enable a feature in all environments as expected.
Next steps:
- To help prevent similar impact in the future, we're further reviewing the underlying reason why the feature wasn't enabled in all environments as expected.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 10 00:38:30 2026 |
|---|
| Description: | Title: Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI
User impact: Users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI.
More info: The impacted workflows include the following:
- Prep Data for AI
- Copilot data questions
- Q&A Visual
Current status: We're continuing to disable the feature and will monitor the environment once completed to confirm remediation. We'll provide a completion timeline when one becomes available.
Scope of impact: Your organization is affected by this event, and some users attempting the affected workflows are intermittently impacted. This section may be updated as our investigation continues.
Start time: Friday, June 05, 2026, at 5:42 PM UTC
Root cause: A recent deployment didn't enable a feature in all environments as expected.
Next update by: Wednesday, June 10, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Jun 9 23:40:25 2026 |
|---|
| Description: | Title: Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI
User impact: Users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI.
More info: The impacted workflows include the following:
- Prep Data for AI
- Copilot data questions
- Q&A Visual
Current status: We've been alerted to an issue where users' workflows intermittently fail in Microsoft Fabric and Microsoft Power BI. We've identified a recent deployment that didn't enable a feature in all environments as expected, which is leading to impact. We're disabling this feature and monitoring to confirm the impact is resolved.
Scope of impact: Your organization is affected by this event, and some users attempting the affected workflows are intermittently impacted. This section may be updated as our investigation continues.
Start time: Friday, June 05, 2026, at 5:42 PM UTC
Root cause: A recent deployment didn't enable a feature in all environments as expected.
Next update by: Wednesday, June 10, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Tue Jun 9 23:22:18 2026 |
|---|
| Description: | Title: Some users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI
User impact: Users’ workflows intermittently fail in Microsoft Fabric and Microsoft Power BI.
More info: The impacted workflows include the following:
- Prep Data for AI
- Copilot data questions
- Q&A Visual
Current status: We're investigating a potential issue with Microsoft Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1255789 - Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Mar 16 19:00:00 2026 |
|---|
| End Time: | Tue Mar 24 14:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 9 15:45:33 2026 |
|---|
| Root Cause: | The issue was caused by a configuration error in the Real-Time Activity Feed (RTAF) bot, which unintentionally initiated video connections for every session despite only requiring audio and data. This led to a high volume of idle video connections that congested the shared video infrastructure used by Microsoft Teams Rooms. As a result, available video bandwidth was reduced, causing degraded video quality (including lower resolution and blurriness) for customers. The condition was exacerbated by increased RTAF traffic, which amplified the impact on the shared service. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 8 19:57:12 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Mar 24 20:42:13 2026 |
|---|
| Description: | Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may have experienced video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact was specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients weren't affected.
Users may have been able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Final status: We applied a fix to affected infrastructure to reduce the traffic load and have confirmed through telemetry that the impact was remediated.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may have been impacted.
Start time: Monday, March 16, 2026, at 11:00 PM UTC
End time: Tuesday, March 24, 2026, at 6:00 PM UTC
Root cause: The issue was caused by a configuration error in the Real-Time Activity Feed (RTAF) bot, which unintentionally initiated video connections for every session despite only requiring audio and data. This led to a high volume of idle video connections that congested the shared video infrastructure used by Microsoft Teams Rooms. As a result, available video bandwidth was reduced, causing degraded video quality (including lower resolution and blurriness) for customers. The condition was exacerbated by increased RTAF traffic, which amplified the impact on the shared service.
Next steps:
- Please see PIR for a comprehensive list of next steps.
|
|---|
|
| Time: | Tue Mar 24 16:41:11 2026 |
|---|
| Description: | Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients aren't affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: We've completed implementation of our solution and we believe impact is remediated at this time. To ensure there are no unexpected problems, we're extending our monitoring period and aim to confirm complete remediation by our next scheduled update.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Start time: Wednesday, March 18, 2026, at 1:32 AM UTC
Root cause: A recent feature deployment that intended to improve call handling has caused a large influx of service traffic to accumulate on a subset of infrastructure that facilitates Teams Rooms device video, causing traffic to not process as expected, resulting in impact.
Next update by: Wednesday, March 25, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Mar 24 12:40:46 2026 |
|---|
| Description: | Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients aren't affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: We've validated that our solution that removes the offending feature doesn't produce any unexpected problems for the service and has remediated impact for most users. We're continuing to implement our solution to the remaining affected users and expect this should complete by our next scheduled update.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Start time: Wednesday, March 18, 2026, at 1:32 AM UTC
Root cause: A recent feature deployment that intended to improve call handling has caused a large influx of service traffic to accumulate on a subset of infrastructure that facilitates Teams Rooms device video, causing traffic to not process as expected, resulting in impact.
Next update by: Tuesday, March 24, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 23 17:46:16 2026 |
|---|
| Description: | Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients aren't affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: We're finalizing our internal validations so we can ensure that our solution removes the recently deployed feature without producing any unexpected problems for the service. We're expecting an estimated timeline for our reversion process remediating the impact by our next scheduled communication update.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Start time: Wednesday, March 18, 2026, at 1:32 AM UTC
Root cause: A recent feature deployment that intended to improve call handling has caused a large influx of service traffic to accumulate on a subset of infrastructure that facilitates Teams Rooms device video, causing traffic to not process as expected, resulting in impact.
Next update by: Tuesday, March 24, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Mar 23 13:21:24 2026 |
|---|
| Description: | Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients aren't affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: Our additional analysis into the subset of affected infrastructure has determined that our load balancing efforts haven't addressed the video quality problems in Microsoft Teams Rooms. Our additional analysis has isolated a recent feature deployment that is believed to producing the impacting load for the infrastructure, resulting in the impact. As we conduct our change reversion process and remove the recently deployed feature, we've deployed a new code fix to expand processing on the machines and to remediate the impact.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Start time: Wednesday, March 18, 2026, at 1:32 AM UTC
Root cause: A recent feature deployment that intended to improve call handling has caused a large influx of service traffic to accumulate on a subset of infrastructure that facilitates Teams Rooms device video, causing traffic to not process as expected, resulting in impact.
Next update by: Monday, March 23, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Mar 20 15:51:34 2026 |
|---|
| Description: | Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Impact is specific to users in meetings with at least one participant sharing video from Microsoft Teams Rooms devices. Other Microsoft Teams clients are not affected.
Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: Our investigation has identified that a portion of infrastructure that facilitates Teams Rooms device video isn't processing as efficiently as expected, resulting in impact. We're rebalancing load to improve throughput and remediate impact.
Scope of impact: Some users joining meetings with a participant using Microsoft Teams Rooms on Windows and Android devices may be impacted.
Root cause: A portion of infrastructure that facilitates Teams Rooms device video isn't processing as efficiently as expected, which is resulting in impact.
Next update by: Monday, March 23, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Mar 19 20:43:06 2026 |
|---|
| Description: | Title: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: Our investigation into the service health telemetry is ongoing so that we can pinpoint the origin of impact. In tandem, we suspect that an update to the setting configuration may alleviate this issue and are developing that solution to validate our theory.
Scope of impact: Some users attempting to use Microsoft Teams Rooms on Windows and Android devices may be impacted.
Next update by: Friday, March 20, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Mar 19 04:59:34 2026 |
|---|
| Description: | Title: Some users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices
User impact: Users may experience video quality issues in Microsoft Teams Rooms on Windows and Android devices.
More info: Users may be able to circumvent this issue by disabling Cloud IntelliFrame within the device settings.
Current status: We're investigating a potential issue with users experiencing video call degradation within Microsoft Teams Rooms (MTR) on both Windows and Android platforms and are analyzing service telemetry to help us identify the root cause.
Scope of impact: Some users attempting to use Microsoft Teams Rooms on Windows and Android devices may be impacted.
Next update by: Friday, March 20, 2026, at 1:00 AM UTC
|
|---|
|
AH1330083 - User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jun 1 17:09:00 2026 |
|---|
| End Time: | Mon Jun 1 19:32:01 2026 |
|---|
| Service: | Windows Autopatch |
|---|
| Feature Group: | Update Management |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 9 15:27:07 2026 |
|---|
| Root Cause: | A recent feature update contained a code issue that prevented users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 9 15:27:07 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 19:32:44 2026 |
|---|
| Description: | Title: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
User impact: User couldn't manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch.
Final status: We've confirmed through service health telemetry that our fixes have successfully addressed all impacted functions, resolving this event.
Scope of impact: Your organization was affected by this event, and any user attempting to manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch was impacted.
Start time: Tuesday, April 28, 2026, at 7:00 PM UTC
End time: Monday, June 01, 2026, at 11:00 PM UTC
Root cause: A recent feature update contained a code issue that prevented users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next steps: - We're reviewing the responsible code issue to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 1 17:41:44 2026 |
|---|
| Description: | Title: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
User impact: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch.
Current status: We've identified that a recent feature update contains a code issue that prevents users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license. We've corrected the affected users' license states, which has returned Autopatch group management functionality, and are deploying a code fix that will return users' ability to add new devices to Autopatch groups. We expect this will complete by our next scheduled update. We're reviewing the Autopatch reporting issue to identify a fix that will completely remediate impact.
Scope of impact: Your organization is affected by this event, and any user attempting to manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch is impacted.
Start time: Tuesday, April 28, 2026, at 7:00 PM UTC
Root cause: A recent feature update contains a code issue that prevents users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next update by: Tuesday, June 02, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Jun 1 17:10:51 2026 |
|---|
| Description: | Title: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch
User impact: User can’t manage, add new devices to, or open reports for Autopatch groups in Windows Autopatch.
We're investigating a potential issue with Window Autopatch and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
AH1331264 - Users were unable to access reports or modify groups in Windows Autopatch
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu May 28 15:00:00 2026 |
|---|
| End Time: | Tue Jun 2 02:20:00 2026 |
|---|
| Service: | Windows Autopatch |
|---|
| Feature Group: | Support |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 9 15:26:23 2026 |
|---|
| Root Cause: | A recent feature update inadvertently introduced a code issue that affected Windows Autopatch license detection, preventing users from managing groups and accessing reports in Windows Autopatch. More details are provided within the Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 9 15:26:23 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jun 4 15:25:04 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jun 2 04:34:09 2026 |
|---|
| Description: | Title: Users were unable to access reports or modify groups in Windows Autopatch
User impact: Users were unable to access reports or modify groups in Windows Autopatch.
More info: Users may have seen the following error message when attempting to access Autopatch reports:
"Windows Autopatch is collecting data, which could take up to 48 hours. Check here periodically."
Final status: We’ve confirmed that the fix is fully deployed and has successfully remediated the impact. Users are now able to access reports and perform group-related actions in Windows Autopatch.
Scope of impact: Your organization was affected by this event, and any user attempting to open Autopatch reports or manage Autopatch groups may have been impacted.
Start time: Thursday, May 28, 2026, at 7:00 PM UTC
End time: Tuesday, June 02, 2026, at 6:20 AM UTC
Root cause: A recent feature update inadvertently introduced a code issue that affected Windows Autopatch license detection, preventing users from managing groups and accessing reports in Windows Autopatch. More details are provided within the Post-Incident Report.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue Jun 2 00:55:31 2026 |
|---|
| Description: | Title: Users are unable to open any Autopatch reports in Windows Autopatch
User impact: Users are unable to open any Autopatch reports in Windows Autopatch.
More info: Users may see the error message "Windows Autopatch is collecting data, which could take up to 48 hours. Check here periodically."
Current status: We confirmed that the impact to Autopatch reports from AH1330083 is not fully mitigated. We're deploying an additional fix to more quickly get the report data synced. We anticipate that the deployment will take time to complete and will monitor the progress closely.
Scope of impact: Your organization is affected by this event, and the issue impacts any user opening Autopatch reports.
Start time: Thursday, May 28, 2026, at 7:00 PM UTC
Root cause: A recent feature update contained a code issue that prevented users from managing, adding new devices to, or opening reports for Autopatch groups in Windows Autopatch by falsely detecting that users don't have a Windows Autopatch license.
Next update by: Tuesday, June 2, 2026, at 10:00 AM UTC
|
|---|
|
CP1329665 - Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jun 1 09:10:00 2026 |
|---|
| End Time: | Mon Jun 1 13:35:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jun 8 18:14:08 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 8 18:14:08 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 3 19:49:27 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 13:54:55 2026 |
|---|
| Description: | Title: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
User impact: Users may have been unable to access the Copilot desktop or web app.
Final status: We've rerouted requests to healthy infrastructure and have confirmed through our telemetry that service health has recovered.
Scope of impact: Some users attempting to utilize Microsoft Copilot may have been impacted.
Start time: Monday, June 01, 2026, at 1:10 PM UTC
End time: Monday, June 01, 2026, at 5:35 PM UTC
Preliminary root cause: An influx of traffic was routed to a portion of infrastructure not equipped to handle the volume of requests, resulting in the access and timeout errors.
Next steps:
- To help identify similar issues earlier and prevent impact in the future, we're further reviewing our automated traffic routing processes and monitoring systems.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Jun 1 13:27:41 2026 |
|---|
| Description: | We identified a routing issue which is sending Copilot traffic to a portion of infrastructure that is unhealthy, resulting in the access and timeout errors. We're rerouting requests to healthy infrastructure and our telemetry is starting to show service health recovery.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 01, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 12:44:43 2026 |
|---|
| Description: | Title: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
User impact: Users may be unable to access the Copilot desktop or web app.
Current status: We've received HTTP Archive format (HAR) logs from impacted users and are reviewing them to identify the root cause. We're also continuing to monitor our telemetry to determine mitigating actions we can implement in the interim as our investigation progresses.
Scope of impact: Some users attempting to utilize Microsoft Copilot may be impacted. This section may be updated as our investigation continues.
Start time: Monday, June 01, 2026, at 1:55 PM UTC
Next update by: Monday, June 01, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 12:27:25 2026 |
|---|
| Description: | We're working on getting HTTP Archive format (HAR) logs from impacted users to focus our investigative efforts to isolate the source of impact.
This quick update is designed to give the latest information on this issue.
Next update by: Monday, June 01, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 11:51:22 2026 |
|---|
| Description: | Title: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app
User impact: Users may be unable to access the Microsoft Copilot (Microsoft 365) desktop or web app.
Current status: We’re reviewing our telemetry to determine the specific impact and isolate the root cause.
Scope of impact: Some users attempting to utilize Microsoft Copilot may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, June 01, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 11:10:34 2026 |
|---|
| Description: | Title: Investigating user reports of Microsoft 365 Copilot 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.
|
|---|
|
DZ1333265 - Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 27 20:00:00 2026 |
|---|
| End Time: | Mon Jun 8 18:05:59 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jun 8 18:06:09 2026 |
|---|
| Root Cause: | A recent service update to partner–customer relationship functionality introduced a regression that was causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 8 18:06:06 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may have been unable to access and manage configured GDAP tenants in Microsoft Defender.
Final status: We've validated with internal telemetry that our fix was successful and the underlying issue is resolved.
Scope of impact: Some admins that attempted to access configured GDAP-connected tenants in Microsoft Defender tenant views may have been impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
End time: Monday, June 08, 2026, at 10:05 PM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that was causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact.
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: | Mon Jun 8 00:35:42 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We're seeing improvements in internal telemetry after the deployment of the fix completed, and we're continuing to monitor to ensure that the underlying issue is resolved for all impacted admins.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact.
Next update by: Tuesday, June 09, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Fri Jun 5 19:24:59 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We’ve completed deploying our code fix and are monitoring the service telemetry for an extended period of time to confirm that the issue is resolved.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return an empty tenant list, resulting in impact.
Next update by: Monday, June 08, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Fri Jun 5 11:41:31 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: The deployment of our fix is ongoing and we anticipate it will remediate impact by our next scheduled communication update.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Saturday, June 06, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jun 3 11:22:36 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We've completed our mitigation action for the previously identified impacted users and access has been restored for managing GDAP-connected tenants within Microsoft Defender XDR. We're deploying our code fix and anticipate it will be fully saturated by Friday, June 5, 2026. During this time, we'll also continue to identify newly impacted users and manually mitigate them to reduce downtime.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Friday, June 05, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Jun 3 11:22:36 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We've completed our mitigation action for the previously identified impacted users and access has been restored for managing GDAP-connected tenants within Microsoft Defender XDR. We're deploying our code fix and anticipate it will be fully saturated by Friday, June 5, 2026. During this time, we'll also continue to identify newly impacted users and manually mitigate them to reduce downtime.
Scope of impact: Some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted.
Start time: Thursday, May 28, 2026, at 12:00 AM UTC
Root cause: A recent service update to partner–customer relationship functionality introduced a regression that's causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Friday, June 05, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 08:57:01 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We’ve implemented an initial mitigation targeting MSSPs (Managed Security Service Providers) that have already been identified as impacted. We’ve confirmed that this mitigation restores their ability to access and manage GDAP-connected tenants within Microsoft Defender. However, this mitigation is limited to the currently known impacted tenants. New MSSPs configuring GDAP relationships may still encounter the issue. In parallel, we're continuing to develop and deploy a code fix to fully resolve the underlying issue and prevent further impact.
Scope of impact: Your organization is affected by this event, and some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service update to partner–customer relationship functionality inadvertently introduced a regression that is causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Wednesday, June 03, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Jun 3 06:48:22 2026 |
|---|
| Description: | Title: Some admins may be unable to access and manage configured GDAP tenants in Microsoft Defender
User impact: Admins may be unable to access and manage configured GDAP tenants in Microsoft Defender.
More info: Impacted admins may find that previously configured GDAP (Granular Delegated Admin Privilege) tenants are no longer visible or accessible within the tenant switcher in the Microsoft Defender portal. In some cases, admins may also encounter messaging indicating access to “0 out of 1 tenants,” despite having valid GDAP relationships and appropriate administrative permissions.
Current status: We’ve identified that a recent service update to partner–customer relationship functionality inadvertently introduced a regression that is causing some GDAP-connected tenants to incorrectly return empty tenant lists. We’re developing a fix to address this, which will need to be validated before deployment.
Scope of impact: Your organization is affected by this event, and some admins attempting to access configured GDAP-connected tenants in Microsoft Defender tenant views may be impacted. This information may be updated as our investigation continues.
Root cause: A recent service update to partner–customer relationship functionality inadvertently introduced a regression that is causing some GDAP-connected tenants to incorrectly return empty tenant list, resulting in impact.
Next update by: Wednesday, June 03, 2026, at 1:00 PM UTC
|
|---|
|
MO1329260 - Some users may have been unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Jun 1 03:10:00 2026 |
|---|
| End Time: | Mon Jun 1 05:50:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jun 8 09:26:25 2026 |
|---|
| Root Cause: | A recent configuration change within the Redis cache layer required a failover before it could be fully applied to the production environment. When that failover occurred, it coincided with peak traffic levels in Europe, which increased demand on the remaining MySignIn service infrastructure. Under this elevated load, the service experienced high Central Processing Unit (CPU) and memory utilization and was unable to process requests at the expected rate. As a result, some users encountered 504 Gateway Timeout errors when attempting to set up Multi-Factor Authentication (MFA) or access mysignins.microsoft.com. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jun 8 09:23:44 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Jun 3 10:15:06 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 07:43:26 2026 |
|---|
| Description: | Title: Some users may have been unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may have been unable to setup MFA or access the mysignins.microsoft.com website.
More info: Users may have encountered 504 Gateway Timeout errors when trying to access mysignins.microsoft.com
Final status: We've identified a recent cache configuration change required a failover. During the failover, the service experienced high CPU and memory utilization as EU traffic peaked, which prevented the MySignIn service from processing the volume of requests. Mitigation actions have since been rolled back, and traffic has been restored to the original infrastructure.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may have been impacted.
Start time: Monday, June 1, 2026, at 7:10 AM UTC
End time: Monday, June 1, 2026, at 9:50 AM UTC
Root cause: A recent configuration change within the Redis cache layer required a failover before it could be fully applied to the production environment. When that failover occurred, it coincided with peak traffic levels in Europe, which increased demand on the remaining MySignIn service infrastructure. Under this elevated load, the service experienced high Central Processing Unit (CPU) and memory utilization and was unable to process requests at the expected rate. As a result, some users encountered 504 Gateway Timeout errors when attempting to set up Multi-Factor Authentication (MFA) or access mysignins.microsoft.com.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
|
|---|
|
| Time: | Mon Jun 1 06:51:57 2026 |
|---|
| Description: | Title: Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website.
More info: Users may encounter 504 Gateway Timeout errors when trying to access mysignins.microsoft.com
Current status: We've completed mitigation actions, including failing over to alternate infrastructure, and are continuing to monitor service health. As elevated error rates persist, we're actively evaluating additional mitigation options, including optimizing how service requests are processed to further stabilize the service.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may be impacted.
Next update by: Monday, June 1, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jun 1 06:27:12 2026 |
|---|
| Description: | We’ve completed the failover and while we initially observed improvement, we’re continuing to see elevated error rates. We’re actively implementing additional mitigation actions to stabilize the service as we continue our investigation into a potential underlying cache-related issue.
This quick update is designed to provide the latest information on this issue.
Next update by: Monday, June 1, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Jun 1 05:59:02 2026 |
|---|
| Description: | We’ve completed a failover to healthy infrastructure and are closely monitoring service telemetry to confirm recovery. In parallel, we’re continuing to investigate the underlying cache-related issues that may be contributing to impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 1 05:32:42 2026 |
|---|
| Description: | Upon an initial review of service telemetry, we've identified cache failures as a potential root cause for impact, and we're continuing to investigate this further to verify this theory. In parallel, we're conducting a failover to healthy infrastructure in an attempt to provide relief.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Jun 1 05:16:43 2026 |
|---|
| Description: | Title: Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website.
More info: Users may encounter 504 Gateway Timeout errors when trying to access mysignins.microsoft.com
Current status: We're continuing to analyze service health telemetry to isolate the root cause and determine any additional troubleshooting steps, and potential mitigation actions.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may be impacted.
Next update by: Monday, June 01, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Jun 1 04:52:55 2026 |
|---|
| Description: | Title: Some users may be unable to setup Multi-Factor Authentication (MFA) or access the mysignins.microsoft.com website
User impact: Users may be unable to setup MFA or access the mysignins.microsoft.com website.
Current status: We've received reports indicating an issue with setting up MFA or accessing the mysignins.microsoft.com page. We're reviewing service health telemetry to help isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to setup MFA or accessing the mysignins.microsoft.com website may be impacted.
Next update by: Monday, June 01, 2026, at 11:00 AM UTC
|
|---|
|
DZ1304997 - Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
| Status: | serviceRestored |
|---|
| Start Time: | Sun Apr 26 08:00:00 2026 |
|---|
| End Time: | Sun Jun 7 12:03:24 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Jun 7 12:04:22 2026 |
|---|
| Root Cause: | A previously deployed precautionary code fix for another issue was restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Jun 7 12:04:19 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may have been unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact was specific to users who aren't security or global admins and attempted to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Final status: We've finished the deployment of our code fix and validated this issue has been resolved in full.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may have been impacted.
Start time: Sunday, April 26, 2026, at 12:00 PM UTC
End time: Friday, May 08, 2026, at 7:00 PM UTC
Root cause: A previously deployed precautionary code fix for another issue was restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next steps:
- We're reviewing our code testing and validation procedures based on our findings of the cause of this event to better detect and prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jun 1 11:40:02 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: The deployment of our solution requires more time than previously expected, which is delaying remediation of the impact. We're monitoring the deployment and will provide an updated timeline for the completion of our mitigations once they've become available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, June 07, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed May 27 10:56:46 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: The deployment of the fix is taking longer than expected to complete and we estimate completion by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Monday, June 01, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon May 25 10:37:13 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: We're progressing with deploying the code fix to all affected environment and expect this process to complete by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Wednesday, May 27, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed May 20 10:31:13 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: We're continuing to deploy our aforementioned code fix to a number of users to validate the effectiveness of our fix prior to a wider deployment that is due to be deployed by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Monday, May 25, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sun May 17 11:12:04 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins and attempt to view manual actions within the Microsoft Defender for Endpoint Action center History tab.
Current status: We've completed validations of a code fix to assist with replaying affected actions and restoring impacted data. We're initiating deployment of our code fix to a subset of users in Canada to validate the effectiveness of our fix prior to wider deployment. We aim to provide a timeline to wider deployment by our next scheduled update.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Wednesday, May 20, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed May 13 10:34:29 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: Our efforts to replay affected actions to restore impacted data are ongoing, while validating a code fix to ensure proper processing. We're currently testing the replay script in our internal environment, and once validation is complete, we will share an estimated timeline for deployment to the affected infrastructure.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, May 17, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue May 12 10:57:33 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We’re continuing to replay the affected actions to restore impacted data. In parallel, we're validating a code fix to ensure impacted actions are processed as expected, and are assessing its effectiveness within our internal testing environment, before progressing with a gradual rollout to the affected environment. We'll share an estimated completion timeline when one becomes available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Wednesday, May 13, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon May 11 10:12:31 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We’re proceeding with replaying the affected actions and are working to expedite this process. We'll provide a completion timeline once it becomes available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Tuesday, May 12, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sun May 10 10:12:00 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We're continuing to replay affected associated actions and will provide a completion timeline once one becomes available.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Monday, May 11, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sun May 10 07:47:29 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We're replaying associated actions within the aforementioned offending fix and anticipate this process will be complete by the next scheduled update time.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, May 10, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Sat May 9 05:30:22 2026 |
|---|
| Description: | Title: Some users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center
User impact: Users may be unable to view Microsoft Defender for Endpoint manual actions through the Action center.
More info: Impact is specific to users who aren't security or global admins who are attempting to view manual actions within the Microsoft Defender for Endpoint Action Center History Tab.
Current status: We've determined that a previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators. We're currently analyzing all our available resources to determine the next steps to fully resolve the issue.
Scope of impact: Users who aren't security or global admins attempting to view Microsoft Defender for Endpoint manual actions through the Action center may be impacted.
Root cause: A previously deployed precautionary code fix for another issue is restricting visibility of Microsoft Defender for Endpoint manual actions in the Action Center to only Global or Security Administrators.
Next update by: Sunday, May 10, 2026, at 11:00 AM UTC
|
|---|
|
EX1318421 - Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
| Status: | serviceRestored |
|---|
| Start Time: | Wed Apr 15 06:36:00 2026 |
|---|
| End Time: | Fri Jun 5 15:18:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 5 17:29:12 2026 |
|---|
| Root Cause: | A code issue occurred when an email message was saved to drafts and it created a local copy. When a user edited the email message in drafts, sent it, and then viewed the email message from their sent folder, it attempted to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body failed and caused impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 5 17:20:31 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may have been unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opened and edited an email message in the draft folder, sent it, and then viewed it from their sent folder, the edited portion may have appeared blank in the message preview.
Impact only occurred for users utilizing the "Show email as individual messages" Message organization setting. While we worked on mitigating this issue, users could utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Final status: We've completed the deployment of our fix and confirmed through testing with a subset of affected users that the impact has been remediated.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may have been impacted.
Start time: Wednesday, April 15, 2026, at 10:36 AM UTC
End time: Friday, June 05, 2026, at 7:18 PM UTC
Root cause: A code issue occurred when an email message was saved to drafts and it created a local copy. When a user edited the email message in drafts, sent it, and then viewed the email message from their sent folder, it attempted to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body failed and caused impact.
Next steps: - We're reviewing the offending code issue to determine how it was introduced into the service, so that we can prevent similar instances of impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 26 17:10:55 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion may appear blank in the message preview.
Impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Current status: We've developed a code fix to address this issue and anticipate it will complete its deployment by our next scheduled update, at which point we'll look to confirm remediation with a subset of affected users.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Start time: Wednesday, May 20, 2026, at 11:12 PM UTC
Root cause: A code issue occurs when an email message is saved to drafts and it creates a local copy. When a user edits the email message in drafts, sends it, and then views the email message from their sent folder, it attempts to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body fails and causes impact.
Next update by: Friday, June 05, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri May 22 15:59:36 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion may appear blank in the message preview.
Impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Current status: We've identified that a local copy when an email message is being saved in the Drafts folder. When a user edits the email message through Drafts, sends it, and then views the email message from their Sent folder, it attempts to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body fails and causes impact. We're exploring our options to develop the most effective fix.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Root cause: A code issue occurs when an email message is saved to drafts and it creates a local copy. When a user edits the email message in drafts, sends it, and then views the email message from their sent folder, it attempts to reference the stale local copy instead of the edited version. As a result, the attempt to fetch the body fails and causes impact.
Next update by: Tuesday, May 26, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri May 22 15:35:29 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion may appear blank in the message preview.
Impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" message organization setting to avoid this issue.
Current status: We've narrowed down that impact only occurs for users utilizing the "Show email as individual messages" Message organization setting. While we work on mitigating this issue, users can utilize the "Show email grouped by conversation" Message organization setting to avoid this issue. From the collected client logs, we've found that a request call responsible for fetching the message body is missing, which indicates a potential issue with stale data. We're checking whether recent service changes may be contributing to this impact.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri May 22 13:28:03 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
More info: When a user opens and edits an email message in the draft folder, sends it, and then views it from their sent folder, the edited portion appears blank in the message preview.
Current status: Our review of the HAR logs that were provided by a subset of users remained inconclusive, so we reproduced the impact using our internal testing environment. After collecting client logs from our reproduction, we're analyzing the call requests to identify any abnormalities that may help us identify why the item's message body is truncated.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri May 22 05:23:00 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're continuing our investigation of HTTP Archive logs and reproductions of this incident to help understand the root cause of impact and a mitigation plan.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri May 22 01:38:59 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're investigating HTTP Archive logs and reproductions of this incident from a subset of impacted users to isolate the underlying cause to determine our troubleshooting steps.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu May 21 23:44:35 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're gathering needed diagnostic data to begin our investigation to isolate the source of impact and determine our next steps.
Scope of impact: Users attempting to view the body of edited Exchange Online email messages from the Sent folder may be unable to do so. This is subject to change as our investigation continues.
Next update by: Friday, May 22, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Thu May 21 23:25:41 2026 |
|---|
| Description: | Title: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder
User impact: Users may be unable to view the body of edited Exchange Online email messages from the Sent folder.
Current status: We're investigating a potential issue with Exchange Online and checking for impact. We'll provide an update within 30 minutes.
Next update by: Friday, May 22, 2026, at 3:55 AM UTC
|
|---|
|
CP1326225 - Users may be unable to use Microsoft 365 Copilot
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri May 29 11:26:33 2026 |
|---|
| End Time: | Fri May 29 14:37:18 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 5 13:26:00 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 5 13:26:00 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jun 2 20:21:36 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jun 2 20:21:16 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 29 14:51:20 2026 |
|---|
| Description: | Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may have been unable to use Microsoft 365 Copilot.
More info: Users received errors when attempting to interact with Microsoft 365 Copilot.
This issue affected Copilot experiences across all Microsoft 365 productivity apps and services.
Final status: After a period of extended monitoring, we've validated that service has been restored.
Scope of impact: This issue could have impacted any user who attempted to use Microsoft 365 Copilot.
Start time: Friday, May 29, 2026, at 2:30 PM UTC
End time: Friday, May 29, 2026, at 5:35 PM UTC
Preliminary root cause: An increase in retry traffic within the infrastructure responsible for Copilot LLM API use prevented users from accessing Microsoft 365 Copilot.
Next steps:
-We're investigating the source of the increase in retries within the affected infrastructure to better understand the circumstances that caused this problem.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Fri May 29 14:26:33 2026 |
|---|
| Description: | Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may be unable to use Microsoft 365 Copilot.
More info: Users will receive errors when attempting to interact with Microsoft 365 Copilot.
This issue affects Copilot experiences across all Microsoft 365 productivity apps and services.
Current status: Our mitigation actions have proven successful, and we’ve observed that a majority of impact has been resolved. We’re monitoring the environment to ensure the service remains stable and will take additional action if necessary.
Scope of impact: This issue could impact any user attempting to use Microsoft 365 Copilot.
Start time: Friday, May 29, 2026, at 2:30 PM UTC
Preliminary root cause: An increase in retry traffic within the infrastructure responsible for Copilot LLM API use prevented users from accessing Microsoft 365 Copilot.
Next update by: Friday, May 29, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri May 29 13:45:49 2026 |
|---|
| Description: | The underlying infrastructure that the Copilot LLM APIs use has recovered after the mitigation actions were applied. We're reducing the throttle that was previously applied on some specific traffic types and are monitoring to ensure recovery.
Next update by: Friday, May 29, 2026, at 6:30 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri May 29 12:54:21 2026 |
|---|
| Description: | Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may be unable to use Microsoft 365 Copilot.
More info: Users will receive errors when attempting to interact with Microsoft Copilot.
This issue affects Copilot experiences across all Microsoft 365 productivity apps and services.
Current status: We've identified high utilization on the underlying infrastructure that the Copilot LLM APIs use and are applying mitigations. Additionally, at the Copilot service level, we're reviewing options to change routing paths, throttling rules and retry logic to allow the underlying infrastructure to recover.
Scope of impact: This issue could impact any user attempting to use Microsoft 365 Copilot.
Next update by: Friday, May 29, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri May 29 12:17:01 2026 |
|---|
| Description: | We've isolated the impact to requests to underlying Large Language Model (LLM) APIs. We're performing root cause analysis on the underlying LLM infrastructure, and in parallel, we're reviewing potential options to provide short-term relief.
Next update by: Friday, May 29, 2026, at 5:00 PM UTC
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri May 29 11:47:19 2026 |
|---|
| Description: | Title: Users may be unable to use Microsoft 365 Copilot
User impact: Users may be unable to use Microsoft 365 Copilot.
More info: Users will receive errors when attempting to interact with Microsoft Copilot.
This issue affects Copilot experiences across all Microsoft 365 productivity apps and services.
Current status: We're reviewing service telemetry to isolate the source of the issue.
Scope of impact: This issue could impact any user attempting to use Microsoft 365 Copilot.
Next update by: Friday, May 29, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri May 29 11:37:35 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.
|
|---|
|
CW1352001 - Users may have received no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 1 09:00:00 2026 |
|---|
| End Time: | Fri Jun 5 12:41:21 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jun 5 12:55:05 2026 |
|---|
| Root Cause: | An increase in request traffic was causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 5 12:55:02 2026 |
|---|
| Description: | Title: Users may have received no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may have received no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempted to prompt Copilot Chat using the Claude Opus model, they may have received an error that stated, "We're experiencing high demand. Please try again later."
Final status: After applying our configuration changes to rebalance request traffic, we've confirmed after a period of monitoring that the issue was successfully resolved.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may have been impacted.
Start time: Monday, June 01, 2026, at 1:00 PM UTC
End time: Thursday, June 04, 2026, at 9:00 PM UTC
Root cause: An increase in request traffic was causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next steps:
- We're reviewing opportunities to improve our monitoring and alerting for high request traffic scenarios to improve response time and better prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jun 4 18:16:42 2026 |
|---|
| Description: | Title: Users may receive no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may receive no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempt to prompt Copilot Chat using the Claude Opus model, they may receive an error that states, "We're experiencing high demand. Please try again later."
Current status: We've applied configuration changes to rebalance the request traffic and are monitoring our service health telemetry to confirm whether the impact is remediated.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may be impacted.
Start time: Monday, June 01, 2026, at 1:00 PM UTC
Root cause: An increase in request traffic is causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next update by: Friday, June 05, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Thu Jun 4 17:55:30 2026 |
|---|
| Description: | Title: Users may receive no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may receive no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempt to prompt Copilot Chat using the Claude Opus model, they may receive an error that states, "We're experiencing high demand. Please try again later."
Current status: We've identified that an increase in request traffic is causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state. We're evaluating our options to rebalance the request traffic and remediate the impact.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may be impacted.
Root cause: An increase in request traffic is causing the portion of infrastructure responsible for facilitating the responses to prompts using Claude Opus in Copilot Chat to operate in a suboptimal state.
Next update by: Friday, June 05, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Jun 4 16:59:21 2026 |
|---|
| Description: | Title: Users may receive no response when prompting Microsoft 365 Copilot Chat using the Claude Opus model
User impact: Users may receive no response when prompting Copilot Chat using the Claude Opus model.
More info: When users attempt to prompt Copilot Chat using the Claude Opus model, they may receive an error that states, "We're experiencing high demand. Please try again later."
Current status: We're reviewing provided HTTP Archive format (HAR) logs to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Any user prompting Copilot Chat using the Claude Opus model may be impacted.
Next update by: Thursday, June 04, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jun 4 16:41:47 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot Chat
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1351989 - Admins experienced up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jun 4 09:00:00 2026 |
|---|
| End Time: | Thu Jun 4 23:39:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jun 5 08:04:25 2026 |
|---|
| Root Cause: | An unexpected spike in service load resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jun 5 05:33:57 2026 |
|---|
| Description: | Title: Admins experienced up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
User impact: Admins experienced up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal.
More info: Affected scenarios included but weren't limited to:
- Delayed Advanced Hunting data in Microsoft Defender XDR
- Delayed data in the Identity Inventory for Microsoft Defender for Identity
- Delayed data in Microsoft Security Exposure Management (MSEM)
Final status: We’ve confirmed following a period of monitoring, that previously delayed data has been fully processed and the issue is no longer occurring.
Scope of impact: Your organization was affected by this event, and admins in West Europe may have experienced delays of up to five hours for data and alerts for multiple scenarios in the Microsoft Defender portal.
Start time: Thursday, June 04, 2026, at 1:00 PM UTC
End time: Friday, June 05, 2026, at 3:39 AM UTC
Root cause: An unexpected spike in service load resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
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: | Thu Jun 4 19:36:42 2026 |
|---|
| Description: | Title: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
User impact: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal.
More info: Affected scenarios include the following:
- Delayed Advanced Hunting data in Microsoft Defender XDR
- Delayed data in the Identity Inventory for Microsoft Defender for Identity
- Delayed data in Microsoft Security Exposure Management (MSEM)
Current status: We've completed implementing optimizations to address the service load, and we’ve observed significant improvements in the delays that admins are seeing. We're continuing to monitor telemetry as the backlogged data is being processed to ensure the underlying issue is resolved.
Scope of impact: Your organization is affected by this event, and admins in West Europe experience delays of up to five hours for data and alerts for multiple scenarios in the Microsoft Defender portal.
Start time: Thursday, June 04, 2026, at 1:00 PM UTC
Root cause: An unexpected spike in service load has resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
Next update by: Friday, June 05, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Jun 4 16:40:19 2026 |
|---|
| Description: | Title: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal
User impact: Admins experience up to five-hour delays for data and alerts for multiple scenarios in the Microsoft Defender portal.
More info: Affected scenarios include the following:
- Delayed Advanced Hunting data in Microsoft Defender XDR
- Delayed data in the Identity Inventory for Microsoft Defender for Identity
- Delayed data in Microsoft Security Exposure Management (MSEM)
Current status: Our service monitoring has alerted us to impact on data population for multiple scenarios in the Microsoft Defender portal for a subset of admins in Western Europe. We've isolated an unexpected spike in service load has resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication. We're implementing optimizations to address the service load and restore affected infrastructure. We anticipate this process to be completed by our next scheduled update.
Scope of impact: Your organization is affected by this event, and admins in West Europe experience delays of up to five hours for data and alerts for multiple scenarios in the Microsoft Defender portal.
Start time: Thursday, June 04, 2026, at 1:00 PM UTC
Root cause: An unexpected spike in service load has resulted in degradation to the service infrastructure utilized to process and supply data for impacted Microsoft Defender scenarios as outlined in the "More info" section of this communication.
Next update by: Friday, June 05, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Jun 4 16:05:42 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft Defender XDR services
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft Defender XDR and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1322762 - Some users may see older draft email messages appear as recently modified in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 26 04:15:52 2026 |
|---|
| End Time: | Tue May 26 20:31:53 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jun 4 18:22:42 2026 |
|---|
| Root Cause: | Annotation-only workload updates were incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to have been incorrectly updated and resulted in older drafts appearing as recently modified in users’ mailboxes.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 26 20:34:17 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may have seen older draft email messages appear as recently modified in Exchange Online.
More info: Users may have noticed that previously created draft email messages appeared with a recent modification date, even when no visible changes have been made. This behavior affected multiple draft items, where older drafts appeared as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Final status: We’ve confirmed that our deployment has completely saturated to all affected environments and verified through service health telemetry that this has successfully remediated the impact.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may have been impacted.
Start time: Friday, May 15, 2026, at 5:07 AM UTC
End time: Tuesday, May 26, 2026, at 10:00 PM UTC
Root cause: Annotation-only workload updates were incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to have been incorrectly updated and resulted in older drafts appearing as recently modified in users’ mailboxes.
Next steps: - We're reviewing the impacting workload flow to better understand the source of the issue in an effort to prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 26 14:39:28 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behavior can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve confirmed that 90 percent of the deployment has saturated across the affected environments, and some users may experience alleviation as saturation progresses. We’re continuing to monitor service behavior while the mitigation rollout continues and investigating inconsistencies affecting a subset of traffic to determine an alternate approach that fully addresses the issue, which will help us ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Wednesday, May 27, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue May 26 14:39:18 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behavior can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve confirmed that 90 percent of the deployment has saturated across the affected environments, and some users may experience alleviation as saturation progresses. We’re continuing to monitor service behavior while the mitigation rollout continues and investigating inconsistencies affecting a subset of traffic to determine an alternate approach that fully addresses the issue, which will help us ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Wednesday, May 27, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue May 26 10:27:11 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’re continuing to monitor service behaviour while mitigation rollout progresses and are investigating inconsistencies impacting a subset of traffic to identify an alternate approach to fully address the issue and ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue May 26 10:27:02 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’re continuing to monitor service behaviour while mitigation rollout progresses and are investigating inconsistencies impacting a subset of traffic to identify an alternate approach to fully address the issue and ensure all affected users receive the fix.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue May 26 08:22:32 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We're continuing to monitor service telemetry while we disable the aforementioned offending feature. We expect this to be complete by our next scheduled update.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Tue May 26 06:22:51 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve identified an issue where a feature intended to handle annotation-only updates is affecting draft email messages, causing some drafts to appear as recently modified when no meaningful changes were made. We’re mitigating the impact by disabling this feature and deploying the fix across the service. We’re actively monitoring service health and telemetry to confirm the effectiveness of this mitigation and ensure impact is decreasing.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Tue May 26 06:22:42 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’ve identified an issue where a feature intended to handle annotation-only updates is affecting draft email messages, causing some drafts to appear as recently modified when no meaningful changes were made. We’re mitigating the impact by disabling this feature and deploying the fix across the service. We’re actively monitoring service health and telemetry to confirm the effectiveness of this mitigation and ensure impact is decreasing.
Scope of impact: Some users attempting to view draft email messages in Exchange Online may be impacted.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Tue May 26 04:18:36 2026 |
|---|
| Description: | Title: Some users may see older draft email messages appear as recently modified in Exchange Online
User impact: Users may see older draft email messages appear as recently modified in Exchange Online.
More info: Users may notice that previously created draft email messages appear with a recent modification date, even when no visible changes have been made. This behaviour can affect multiple draft items, where older drafts appear as if they were modified recently, leading to confusion when trying to determine when a draft was originally created or last edited.
Current status: We’re analyzing reported behaviour to better understand the issue and to determine the cause of impact.
Scope of impact: Impact is specific to some users attempting to view draft email messages in Exchange Online.
Root cause: Annotation-only updates performed by the specific workload is incorrectly updating the LastModificationTime property on draft email messages, causing draft email messages to be incorrectly updated and resulting in older drafts appearing as recently modified in users’ mailboxes.
Next update by: Tuesday, May 26, 2026, at 10:30 AM UTC
|
|---|
|
MO1321911 - Some admins may be unable to view usage reports in the Microsoft 365 admin center
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon May 18 19:00:00 2026 |
|---|
| End Time: | Thu May 28 18:15:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jun 4 17:03:24 2026 |
|---|
| Root Cause: | A recent service change related to a backend infrastructure migration contained a code issue which was causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jun 4 17:03:24 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jun 1 12:45:36 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 28 18:41:24 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins were unable to view usage reports in the Microsoft 365 admin center.
Final status: The deployment of the fix has completed and we've confirmed it successfully resolved the issue.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may have been impacted.
Start time: Monday, May 18, 2026, at 11:00 PM UTC
End time: Thursday, May 28, 2026, at 10:15 PM UTC
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which was causing impact.
Next steps: - We're reviewing our service change procedures to better understand why the code issue wasn't detected prior to the migration.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu May 28 12:59:51 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: Our fix is progressing as expected, and telemetry indicates that the issue is resolved for a majority of admins. We're continuing to closely monitor the rollout and expect it be fully saturated within the next 12 hours or sooner.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Start time: Monday, May 18, 2026, at 11:00 PM UTC
Estimated time to resolve: We estimate that this issue will be resolved in the next 12 hours.
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which is causing impact.
Next update by: Friday, May 29, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed May 27 19:59:01 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We're continuing to deploy our fix via staged roll out. Based on our current progress, we expect the issue to be fully resolved within the next 24 hours. We expect admins to be able to view usage reports as the fix propagates throughout the affected environments.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Estimated time to resolve: We estimate that this issue will be resolved in the next 24 hours.
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which is causing impact.
Next update by: Thursday, May 28, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed May 27 14:14:42 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We identified a recent service change related to a backend infrastructure migration that contained a code issue, which is causing impact. We've validated a fix in our internal testing environment and have begun rolling it out to the affected environments. We'll continue to closely monitor this deployment and provide an estimated time to resolution as soon as it is available.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Root cause: A recent service change related to a backend infrastructure migration contained a code issue which is causing impact.
Next update by: Thursday, May 28, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue May 26 21:56:02 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We’ve developed and are validating a fix to potentially address the suspected cause of this issue to confirm our findings and potentially remediate the impact.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Wednesday, May 27, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue May 26 15:09:58 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We're continuing to await error messages seen when encountering this impact and HAR traces from some admins to assist with further debugging. Simultaneously, we're attempting to create a reproduction of impact within our internal testing environment for better analysis and to isolate the underlying source of impact.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Wednesday, May 27, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon May 25 13:54:18 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: Our review of the reports API endpoint failures was inconclusive and didn't pinpoint a service issue that would lead to this impact. We'll continue to investigate available service-side data to potentially progress the investigation, though we're requesting that impacted admins provide additional supporting data, such as error messages seen when encountering this impact and a HTTP Archive format (HAR) trace, as this information will likely be needed to successfully investigate the problem further.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Tuesday, May 26, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon May 25 12:25:17 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We've identified failures occurring with a report API endpoint and are investigating these further to determine what's leading to this behavior, as well as our approach to mitigating the impact.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Monday, May 25, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon May 25 10:15:24 2026 |
|---|
| Description: | Title: Some admins may be unable to view usage reports in the Microsoft 365 admin center
User impact: Admins may be unable to view usage reports in the Microsoft 365 admin center.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Some admins attempting to view usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Monday, May 25, 2026, at 4:30 PM UTC
|
|---|
|
MO1338742 - Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 3 14:30:00 2026 |
|---|
| End Time: | Wed Jun 3 19:49:48 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 3 19:51:33 2026 |
|---|
| Root Cause: | A recent build deployment introduced an issue which is causing failures when utilizing impacted APIs to retrieve Microsoft OneNote content.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 19:51:12 2026 |
|---|
| Description: | Title: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
User impact: Users may have failed to retrieve Microsoft OneNote content using Microsoft Graph APIs.
More info: Impacted APIs include:
GET-recentnotebooks
GET-notebooks
GET-sections
GET-pages
POST-pages
POST-sections
GET-sectiongroups
Final status: We've confirmed that our deployment of the previous unimpacted service build version has completed, and that the impact has been fully remediated for all affected users.
Scope of impact: This issue may have affected some users attempting to utilize Microsoft Graph APIs to retrieve Microsoft OneNote content.
Start time: Wednesday, June 03, 2026, at 6:30 PM UTC
End time: Wednesday, June 03, 2026, at 10:30 PM UTC
Root cause: A recent build deployment introduced an issue which is causing failures when utilizing impacted APIs to retrieve Microsoft OneNote content.
Next steps:
- We're continuing to monitor service health to ensure that this impact does not reoccur.
- We're analyzing our internal validation processes to identify any avenues for enhancing quality assurance to ensure that potential issues are preemptively remediated.
|
|---|
|
| Time: | Wed Jun 3 16:04:49 2026 |
|---|
| Description: | Title: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
User impact: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs.
More info: Impacted APIs include:
GET-recentnotebooks
GET-notebooks
GET-sections
GET-pages
POST-pages
POST-sections
GET-sectiongroups
Current status: We've identified that a recent build deployment introduced an issue which is causing failures when attempting to utilize impacted APIs to retrieve Microsoft OneNote content. We've begun deployment of the previous known good build as a means of remediating impact. We anticipate this deployment will be complete, resolving the issue, by our next scheduled communication update.
Scope of impact: This issue may affect some users of Microsoft Graph APIs retrieving Microsoft OneNote content.
Start time: Wednesday, June 03, 2026, at 6:30 PM UTC
Root cause: A recent build deployment introduced an issue which is causing failures when utilizing impacted APIs to retrieve Microsoft OneNote content.
Next update by: Thursday, June 04, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Jun 3 15:54:22 2026 |
|---|
| Description: | Title: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs
User impact: Users may fail to retrieve Microsoft OneNote content using Microsoft Graph APIs.
Current status: We're investigating a potential issue with Microsoft Graph and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1332784 - Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 2 09:00:00 2026 |
|---|
| End Time: | Wed Jun 3 14:08:07 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 3 14:09:17 2026 |
|---|
| Root Cause: | A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 14:09:14 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates might have been installing drivers.
More info: As we worked to remediate the impact, we determined that the drivers installed were Microsoft approved/signed and that they didn't pose a security threat.
Final status: We've validated that this issue is resolved following impact remediation confirmation from a subset of previously affected users.
Scope of impact: This issue may have caused drivers to be installed for users with a Windows device configured to prevent auto updates.
Start time: Tuesday, June 02, 2026, at 1:00 PM UTC
End time: Wednesday, June 03, 2026, at 5:30 AM UTC
Root cause: A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next steps:
- We're continuing to review how this caching service temporarily dropped Windows device enrollment information to better inform how to detect, prevent, and respond to similar service issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 3 13:05:36 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates might be installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've validated that updating the affected service cache and enrollment status for affected devices has mitigated impact for this issue. We're reaching out to a subset of affected users to likewise validate this impact remediation and confirm this issue is fully resolved.
Scope of impact: This issue may cause drivers to be installed for users with a Windows device configured to prevent auto updates.
Start time: Tuesday, June 02, 2026, at 1:00 PM UTC
Root cause: A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next update by: Thursday, June 04, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 19:34:56 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates might be installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've confirmed that a caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied. We're updating the affected service cache and the enrollment status for affected devices to remediate the impact and anticipate this process may complete by our next scheduled update, at which point we'll monitor to confirm full remediation.
Scope of impact: This issue may cause drivers to be installed for users with a Windows device configured to prevent auto updates.
Start time: Tuesday, June 02, 2026, at 1:00 PM UTC
Root cause: A caching service used by the Windows Update service temporarily dropped device enrollment information. As a result, affected Windows devices were briefly treated as non-enrolled, preventing the expected driver-approval controls being applied.
Next update by: Wednesday, June 03, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jun 2 18:39:10 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates may be installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates may be installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've identified a potential service cache misconfiguration that we believe could be causing drivers to become unexpectedly installed when policies are configured to prevent it. We're further analyzing our service cache configurations to confirm our findings, and so we can determine the next steps for remediating the impact.
Scope of impact: This issue may cause drivers to be installed for users with a Windows device configured to prevent auto updates.
Next update by: Wednesday, June 03, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Jun 2 18:20:41 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates are installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates are installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've focused our investigation on a potential service cache misconfiguration that we believe could be causing drivers to become unexpectedly installed when policies are configured to prevent it. We're further analyzing our service cache configurations to confirm our findings, and so we can determine the next steps for remediating the impact.
Scope of impact: Your organization is impacted by this event, and some users with a Windows device have their drivers unexpectedly installed.
Next update by: Wednesday, June 03, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Jun 2 16:48:00 2026 |
|---|
| Description: | Title: Some users' Windows devices with policies configured to prevent auto updates are installing drivers
User impact: Users' Windows devices with configured policies to prevent auto updates are installing drivers.
More info: As we work to remediate the impact, we've determined that the drivers being installed are Microsoft approved/signed and that they don't pose a security threat.
Current status: We've received a report of an issue where users' Windows devices that have configured policies to prevent auto updates are installing drivers. We're analyzing internal service telemetry and an affected device ID as we isolate the source for this event, and to determine our next troubleshooting steps for remediating the impact.
Scope of impact: Your organization is impacted by this event, and some users with a Windows device have their drivers unexpectedly installed.
Next update by: Tuesday, June 02, 2026, at 10:30 PM UTC
|
|---|
|
PB1333350 - Some users in East US may experience issues opening or refreshing reports in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jun 3 09:05:00 2026 |
|---|
| End Time: | Wed Jun 3 09:34:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jun 3 11:42:39 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 11:41:27 2026 |
|---|
| Description: | Title: Some users in East US may experience issues opening or refreshing reports in Microsoft Fabric
User impact: Users in East US may have experienced issues opening or refreshing reports in Microsoft Fabric.
More info: Users also experienced issues while running queries directly into the semantic model.
Final status: While we were in the process of analyzing service health telemetry and network logs, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users in East US attempting to open or refresh reports, and or run queries directly into the semantic model in Microsoft Fabric may have been impacted.
Start time: Wednesday, June 03, 2026, at 1:05 PM UTC
End time: Wednesday, June 03, 2026, at 1:34 PM UTC
This is the final update for the event.
|
|---|
|
| Time: | Wed Jun 3 10:11:17 2026 |
|---|
| Description: | Title: Some users in East US may experience issues opening or refreshing reports in Microsoft Fabric
User impact: Users in East US may experience issues opening or refreshing reports in Microsoft Fabric.
More info: Users may also experience issues while running queries directly into the semantic model.
Current status: We're reviewing service health telemetry and network logs to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users in East US attempting to open or refresh reports, and or run queries directly into the semantic model in Microsoft Fabric may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, June 03, 2026, at 1:05 PM UTC
Next update by: Wednesday, June 03, 2026, at 4:30 PM UTC
|
|---|
|
CP1324075 - Users' draft generation prompts to Microsoft 365 Copilot may not complete in the classic Outlook desktop app Build 2605
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon May 18 02:27:00 2026 |
|---|
| End Time: | Wed May 27 13:11:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jun 3 08:35:36 2026 |
|---|
| Root Cause: | A recent feature code change, intended to enhance text processing capabilities in Copilot draft generation introduced a code error. Specifically, the client stopped requesting plaintext-only responses so that it could present users with richer responses, however, one of the APIs being leveraged had a dependency on plaintext formatting. This resulted in failures when processing draft generation prompts within the classic Outlook desktop client. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jun 3 08:35:36 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 29 15:54:15 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed May 27 15:13:59 2026 |
|---|
| Description: | Title: Users' draft generation prompts to Microsoft 365 Copilot may not complete in the classic Outlook desktop app Build 2605
User impact: Users' draft generation prompts to Copilot may not have completed in the classic Outlook desktop app Build 2605.
More info: While we were focused on remediation, users may have prompted Copilot through the new Outlook app or Outlook on the web to bypass the impact.
Some users may need to restart the Outlook desktop app multiple times to get the correct configurations which fix the issue.
Additionally, users who reverted their Outlook version as a workaround, need to ensure they re-enable updates by selecting: File > Office Account > Update Options > Enable Updates
Final status: We've confirmed that the impact resulted from a recent feature code upgrade intended to enhance text processing capabilities by enabling Markdown in Copilot when building Drafts, which introduced a code error. We've reverting this feature upgrade for all affected users, which has mitigated the impact. However, users will need to restart the classic Outlook app to have the mitigation applied.
Scope of impact: This issue may have affected all users who were attempting to generate a draft with a Copilot prompt in the classic Outlook desktop app on Build 2605.
Start time: Monday, May 18, 2026, at 6:27 PM UTC
End time: Wednesday, May 27, 2026, at 5:11 PM UTC
Root cause: A recent feature code change, intended to enhance text processing capabilities in Copilot draft generation introduced a code error. Specifically, the client stopped requesting plaintext-only responses so that it could present users with richer responses, however, one of the APIs being leveraged had a dependency on plaintext formatting. This resulted in failures when processing draft generation prompts within the classic Outlook desktop client.
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 May 27 14:18:57 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.
|
|---|
|
CP1332829 - Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jun 2 18:30:00 2026 |
|---|
| End Time: | Tue Jun 2 21:30:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jun 2 22:21:21 2026 |
|---|
| Root Cause: | A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app wasn't processing requests as efficiently as expected and resulted in an increase in latency within the service.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 2 22:15:31 2026 |
|---|
| Description: | Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may have seen latency when using tools and chats in the Microsoft 365 Copilot app.
Final status: While we were further investigating the affected infrastructure, we've identified that a sync issue was preventing availability from recovering for a subset of users. We've redirected traffic to bypass the sync issue and confirmed with monitoring internal telemetry that the impact is remediated.
Scope of impact: Some users that were using tools and chants in the Microsoft 365 Copilot app may have been impacted.
Start time: Tuesday, June 02, 2026, at 10:30 PM UTC
End time: Wednesday, June 03, 2026, at 2:15 AM UTC
Root cause: A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app wasn't processing requests as efficiently as expected and resulted in an increase in latency within the service.
Next steps:
- We're further reviewing the portion of infrastructure to understand what prevented it from processing requests as efficiently as expected, so we can help prevent similar issues from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 2 20:52:06 2026 |
|---|
| Description: | Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may see latency when using tools and chats in the Microsoft 365 Copilot app.
Current status: We’ve completed rebalancing resources and implementing improvements on the affected infrastructure, and our monitoring indicates that the issue is remediated for the majority of impacted users. We're further investigating the affected infrastructure to identify what additional remediation efforts may be needed to resolve the issue for the remaining impacted users.
Scope of impact: Some users that are using tools and chats in the Microsoft 365 Copilot app may be impacted. This information may be updated as our investigation continues.
Root cause: A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app isn't processing requests as efficiently as expected, resulting in an increase in latency within the service.
Next update by: Wednesday, June 03, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 19:32:32 2026 |
|---|
| Description: | Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may see latency when using tools and chats in the Microsoft 365 Copilot app.
Current status: We've identified a portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app isn't processing requests as efficiently as expected, resulting in an increase in latency within the service. We're rebalancing resources and implementing improvements on the affected infrastructure to remediate impact.
Scope of impact: Some users that are using tools and chats in the Microsoft 365 Copilot app may be impacted.
Root cause: A portion of infrastructure responsible for tools and chat functionality in the Microsoft 365 Copilot app isn't processing requests as efficiently as expected, resulting in an increase in latency within the service.
Next update by: Wednesday, June 03, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Jun 2 19:04:54 2026 |
|---|
| Description: | Title: Some users may see latency when using tools and chats in the Microsoft 365 Copilot app
User impact: Users may see latency when using tools and chats in the Microsoft 365 Copilot app.
Current status: We're investigating a potential issue with the Microsoft 365 Copilot app and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1332783 - Some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jun 1 23:00:00 2026 |
|---|
| End Time: | Tue Jun 2 16:40:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jun 2 18:11:01 2026 |
|---|
| Root Cause: | A recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure, resulting in intermittent failures when processing Microsoft 365 Copilot requests and generating responses.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 2 17:52:35 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses
User impact: Users may have intermittently been unable to complete Copilot requests or receive responses.
Final status: We've identified that a recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure, resulting in intermittent failures when processing Microsoft 365 Copilot requests and generating responses. To remediate this issue, we've developed and applied a configuration fix to the affected infrastructure, and after monitoring the service, we've verified that this action has successfully resolved the problem.
Scope of impact: Impact may have occurred for a subset of users who were intermittently unable to complete Microsoft 365 Copilot requests or receive responses.
Start time: Tuesday, June 02, 2026, at 3:00 AM UTC
End time: Tuesday, June 02, 2026, at 8:40 PM UTC
Root cause: A recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure, resulting in intermittent failures when processing Microsoft 365 Copilot requests and generating responses.
Next steps: We're investigating how the recent service change introduced a configuration issue within a portion of the GPT-5.3 chat infrastructure to prevent this problem from happening again through improvements in our service change testing and validation phases.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jun 2 16:49:15 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses
User impact: Users may intermittently be unable to complete Copilot requests or receive responses.
Current status: Our monitoring systems have identified impact where some users may intermittently be unable to complete Microsoft 365 Copilot requests or receive responses. We're reviewing service telemetry in an effort to isolate the source of this issue and determine appropriate remediation actions.
Scope of impact: Impact may occur for a subset of users who are intermittently unable to complete Microsoft 365 Copilot requests or receive responses.
Start time: Tuesday, June 02, 2026, at 3:00 AM UTC
Next update by: Tuesday, June 02, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jun 2 16:44:10 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.
|
|---|
|
DV1302935 - Users experience intermittent environment access failures and general degraded performance
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Apr 30 20:57:00 2026 |
|---|
| End Time: | Thu May 7 17:45:00 2026 |
|---|
| Service: | Microsoft Dataverse |
|---|
| Feature Group: | Other |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jun 2 12:29:26 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jun 2 12:29:26 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 12 11:47:32 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 7 18:22:26 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experienced intermittent environment access failures and general degraded performance.
More Info: This issue affected Dynamics 365 and Microsoft Dataverse.
Final Status: We have completed the service restarts and, following this, confirmed via service diagnostic analysis that the issue has been resolved.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A recently enabled feature resulted in impact as a required service restart was not performed following its enablement.
Next Steps: We're reviewing our feature enablement procedures to avoid similar impact in the future.
|
|---|
|
| Time: | Thu May 7 17:45:27 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: The service restarts are ongoing, and we are monitoring for recovery as they are completed.
Next Update: Thursday, May 8, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu May 7 13:46:47 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: We are continuing to restart services.
Next Update: Thursday, May 7, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 7 10:42:23 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: We are continuing to restart services.
Next Update: Thursday, May 7, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu May 7 08:36:17 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: During our service restarts, we identified a necessary manual configuration change required to complete the process. We have applied the configuration change and resumed the service restarts to mitigate the issue.
Next Update: Thursday, May 7, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu May 7 05:53:24 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: Our service restarts are ongoing.
Next Update: Thursday, May 7, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu May 7 02:29:48 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: Our service restarts are ongoing.
Next Update: Thursday, May 7, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu May 7 00:15:23 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: Our service restarts are ongoing.
Next Update: Thursday, May 7, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Wed May 6 20:35:53 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
More Info: This issue is affecting Dynamics 365 and Microsoft Dataverse.
Current Status: After our investigation, we identified that impact occurred following the application of a recently enabled feature. The feature caused impact due to a required service restart that was not performed when the feature was enabled. We are performing service restarts to restore functionality.
Next Update: Thursday, May 7, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Wed May 6 20:06:07 2026 |
|---|
| Description: | Title: Users experience intermittent environment access failures and general degraded performance
User impact: Users experience intermittent environment access failures and general degraded performance.
Current Status: We are aware of an emerging issue where users experience intermittent environment access failures, intermittent general degraded performance, or intermittent failures for all operations performed in Microsoft Dataverse and Dynamics 365. 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.
|
|---|
|
CP1328187 - Some users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 29 17:45:00 2026 |
|---|
| End Time: | Sun May 31 06:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sun May 31 10:10:20 2026 |
|---|
| Root Cause: | A recent update to the custom engine agent client service inadvertently introduced a code regression that caused connections to reset during use, preventing agents from returning responses and resulting in blank outputs. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun May 31 10:00:04 2026 |
|---|
| Description: | Title: Some users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may not have seen responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may have seen empty message bubbles when interacting with custom engine agents, including admin agents.
Final status: We’ve confirmed that impact is fully remediated following the reversion, with custom engine agents returning responses as expected. Users who continue to see impact may need to start a new Copilot session for the fix to take effect.
Scope of impact: This issue may have affected some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences.
Start time: Friday, May 29, 2026, at 9:45 PM UTC
End time: Sunday, May 31, 2026, at 10:00 AM UTC
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that caused connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
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: | Sun May 31 07:56:28 2026 |
|---|
| Description: | Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may see empty message bubbles when interacting with custom engine agents, including admin agents.
Current status: We’ve completed the rollback of the offending update. We’ve validated that custom engine agents are now returning responses as expected. We’re continuing to monitor service telemetry to confirm that impact is fully remediated.
Scope of impact: This issue may affect some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences. This information may be updated as our investigation continues.
Start time: Friday, May 29, 2026, at 9:45 PM UTC
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next update by: Sunday, May 31, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Sun May 31 05:55:00 2026 |
|---|
| Description: | Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may see empty message bubbles when interacting with custom engine agents, including admin agents.
Current status: We’re reverting the offending update to mitigate impact. We anticipate this rollback to have completed and the issue to be resolved by our next scheduled update.
Scope of impact: This issue may affect some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences. This information may be updated as our investigation continues.
Start time: Friday, May 29, 2026, at 9:45 PM UTC
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next update by: Sunday, May 31, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Sun May 31 05:00:15 2026 |
|---|
| Description: | Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) custom engine agents.
More info: Impacted users may see empty message bubbles when interacting with custom engine agents, including admin agents.
Current status: We’ve determined that a recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs. We’re considering reverting the update to mitigate impact.
Scope of impact: This issue may affect some users interacting with Microsoft Copilot (Microsoft 365) custom engine agents, including admin agents, through the Copilot web experience (m365.cloud.microsoft) and potentially other experiences. This information may be updated as our investigation continues.
Root cause: A recent update to the custom engine agent client service inadvertently introduced a code regression that is causing connections to reset during use, preventing agents from returning responses and resulting in blank outputs.
Next update by: Sunday, May 31, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Sun May 31 03:08:44 2026 |
|---|
| Description: | Title: Some users may see no responses from Microsoft Copilot (Microsoft 365) Custom agents
User impact: Users may see no responses from Microsoft Copilot (Microsoft 365) Custom agents.
More info: Impacted users may see empty message bubbles when interacting with Custom agents, including admin agents.
Current status: We’ve successfully reproduced the issue and are analyzing recent service changes to determine what has introduced the issue and evaluate available mitigation options.
Scope of impact: This issue may impact some users interacting with Custom agents, including admin agents, in Microsoft Copilot (Microsoft 365). This information may be updated as our investigation continues.
Next update by: Sunday, May 31, 2026, at 9:00 AM UTC
|
|---|
|
MO1327455 - Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 30 08:00:00 2026 |
|---|
| End Time: | Sat May 30 16:51:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 30 17:55:44 2026 |
|---|
| Root Cause: | An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 30 17:38:21 2026 |
|---|
| Description: | Title: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
User impact: Users were intermittently unable to create, save, manage, or run Microsoft 365 workflows.
More info: Affected users experienced intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encountered failures when creating, saving, updating, or running workflows and automations.
Final status: We've rerouted traffic to alternate infrastructure to remediate the issue and have verified through monitoring that this action successfully mitigated the problem.
Scope of impact: Your organization was impacted by this event, and all users experienced intermittent failures when creating, saving, managing, or running Microsoft 365 workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
End time: Saturday, May 30, 2026, at 9:37 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
Next steps: We're analyzing the storage connectivity issue and associated telemetry to help prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat May 30 13:23:25 2026 |
|---|
| Description: | Title: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
User impact: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows.
More info: Affected users experience intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encounter failures when creating, saving, updating, or running workflows and automations.
Current status: We're continuing to review potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and all users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Sunday, May 31, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sat May 30 12:08:24 2026 |
|---|
| Description: | Title: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows
User impact: Users are intermittently unable to create, save, manage, or run Microsoft 365 workflows.
More info: Affected users experience intermittent failures with Microsoft Power Automate flows, Microsoft Teams workflows, Microsoft 365 Copilot flows, and Microsoft 365 Copilot agent flows. Users encounter failures when creating, saving, updating, or running workflows and automations.
Current status: Our monitoring systems have identified impact where users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows. Our investigation has identified an issue affecting storage connectivity required for Microsoft 365 workflow operations, resulting in intermittent failures. We're reviewing potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and all users experience intermittent failures when creating, saving, managing, or running Microsoft 365 workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Saturday, May 30, 2026, at 5:30 PM UTC
|
|---|
|
CP1327456 - Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
| Status: | serviceRestored |
|---|
| Start Time: | Sat May 30 08:00:00 2026 |
|---|
| End Time: | Sat May 30 16:51:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 30 17:41:43 2026 |
|---|
| Root Cause: | An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 30 17:40:55 2026 |
|---|
| Description: | Title: Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
User impact: Users experienced intermittent failures when creating, saving, managing, or running Copilot agent workflows.
More info: Affected users experienced intermittent failures with Copilot agent flows. Users encountered failures when creating, saving, updating, or running agent workflows and automations.
Final status: We've rerouted traffic to alternate infrastructure to remediate the issue and have verified through monitoring that this action successfully mitigated the problem.
Scope of impact: Your organization was impacted by this event, and users experienced intermittent failures when creating, saving, managing, or running Copilot agent workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
End time: Saturday, May 30, 2026, at 8:51 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations resulted in intermittent failures.
Next steps: We're analyzing the storage connectivity issue and associated telemetry to help prevent similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sat May 30 13:25:07 2026 |
|---|
| Description: | Title: Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
User impact: Users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
More info: Affected users experience intermittent failures with Copilot agent flows. Users encounter failures when creating, saving, updating, or running agent workflows and automations.
Current status: We're continuing to review potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Sunday, May 31, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sat May 30 12:09:45 2026 |
|---|
| Description: | Title: Users experience intermittent failures when creating, saving, managing, or running Microsoft 365 Copilot agent workflows
User impact: Users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
More info: Affected users experience intermittent failures with Copilot agent flows. Users encounter failures when creating, saving, updating, or running agent workflows and automations.
Current status: Our monitoring systems have identified impact where users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows. Our investigation has identified an issue affecting storage connectivity required for Microsoft 365 workflow operations, resulting in intermittent failures. We're reviewing potential mitigation actions to identify and implement an appropriate solution for this impact.
Scope of impact: Your organization is impacted by this event, and users experience intermittent failures when creating, saving, managing, or running Copilot agent workflows.
Start time: Saturday, May 30, 2026, at 12:00 PM UTC
Root cause: An issue affecting storage connectivity required for Microsoft 365 workflow operations is resulting in intermittent failures.
Next update by: Saturday, May 30, 2026, at 5:30 PM UTC
|
|---|
|
PB1326627 - Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 29 13:25:00 2026 |
|---|
| End Time: | Fri May 29 23:20:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 29 23:39:29 2026 |
|---|
| Root Cause: | A first party app that facilitates the impacted operations was disabled and caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 29 23:37:30 2026 |
|---|
| Description: | Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may have been unable to perform control plane operations on their capacities in Microsoft Fabric.
More info: The affected control plane operations may have consisted of the following:
- Deprovisioning
- Pausing
- Deleting
Final status: We've completed the re-enabling process for the affected first party app and confirmed with our service telemetry that the issue is resolved.
Scope of impact: Any user who attempted to perform the control plane operations listed in the more info section on their capacities in Microsoft Fabric may have been affected.
Start time: Friday, May 29, 2026, at 5:25 PM UTC
End time: Saturday, May 30, 2026, at 3:20 AM UTC
Root cause: A first party app that facilitates the impacted operations was disabled and caused impact.
Next steps:
- We've investigating the impacted first party app which facilitates control plane operations to better understand why it was disabled so that we can prevent similar impact to Microsoft Fabric capacities in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 29 21:56:24 2026 |
|---|
| Description: | Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric.
More info: The affected control plane operations may consist of the following:
- Deprovisioning
- Pausing
- Deleting
Current status: We've identified that a first party app that facilitates the impacted operations was disabled, causing impact. We're re-enabling the affected first party app to resolve the issue and we anticipate this process will be completed by our next scheduled communications update.
Scope of impact: Any user attempting to perform the control plane operations listed in the more info section on their capacities in Microsoft Fabric may be affected. This section may be updated as our investigation continues.
Root cause: A first party app that facilitates the impacted operations was disabled, causing impact.
Next update by: Saturday, May 30, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Fri May 29 20:48:55 2026 |
|---|
| Description: | Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric.
Current status: We're reviewing the service telemetry to isolate any failures or errors that can help point to its underlying root cause and identify a remediation plan.
Scope of impact: Any user attempting to perform the control plane operations listed in the more info section on their capacities in Microsoft Fabric may be affected. This section may be updated as our investigation continues.
Next update by: Saturday, May 30, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri May 29 20:27:29 2026 |
|---|
| Description: | Title: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric
User impact: Users may be unable to perform control plane operations on their capacities in Microsoft Fabric.
More info: The affected control plane operations may consist of the following:
- Deprovisioning
- Pausing
- Deleting
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1326495 - Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 29 14:55:00 2026 |
|---|
| End Time: | Fri May 29 20:30:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 29 21:39:31 2026 |
|---|
| Root Cause: | An issue with a routine maintenance procedure on an upstream supporting service was causing it to perform at suboptimal levels, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 29 21:30:53 2026 |
|---|
| Description: | Title: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks
User impact: Users may have been unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks.
Final status: We've completed the manual restoration of the upstream service and after a period of monitoring, we confirmed impact is remediated.
Scope of impact: Users attempting to initiate Spark sessions or open and perform actions within Microsoft Fabric Notebooks may have been impacted.
Start time: Friday, May 29, 2026, at 6:55 PM UTC
End time: Saturday, May 30, 2026, at 12:30 AM UTC
Root cause: An issue with a routine maintenance procedure on an upstream supporting service was causing it to perform at suboptimal levels, which resulted in impact.
Next steps:
- To help prevent similar impact in the future, we're further working with the upstream service to understand how the maintenance procedure led to impact.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 29 18:20:37 2026 |
|---|
| Description: | Title: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks
User impact: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks.
Current status: We've identified that additional time is needed to complete the manual restoration of the upstream service. Once that action is complete, we'll begin validating if that process has resolved the issue, or if additional actions will be needed to fully mitigate this issue.
Scope of impact: Users attempting to initiate Spark sessions or open and perform actions within Microsoft Fabric Notebooks may be impacted.
Start time: Friday, May 29, 2026, at 6:55 PM UTC
Root cause: An issue with a routine maintenance procedure on an upstream supporting service is causing it to perform at suboptimal levels, resulting in impact.
Next update by: Saturday, May 30, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri May 29 17:14:58 2026 |
|---|
| Description: | Title: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks
User impact: Users may be unable to initiate Spark sessions or open and perform actions in Microsoft Fabric Notebooks.
Current status: We've confirmed that an issue with a routine maintenance procedure on an upstream supporting service is causing it to perform at suboptimal levels, resulting in impact to Spark sessions and Notebook operations, and we've updated the Title, User impact, and Scope of impact fields of this communication accordingly. We're manually restoring the upstream service to a healthy state and anticipate impact may be fully remediated by our next scheduled communications update, at which point we'll verify the issue is resolved through internal telemetry.
Scope of impact: Users attempting to initiate Spark sessions or open and perform actions within Microsoft Fabric Notebooks may be impacted.
Start time: Friday, May 29, 2026, at 6:55 PM UTC
Root cause: An issue with a routine maintenance procedure on an upstream supporting service is causing it to perform at suboptimal levels, resulting in impact.
Next update by: Friday, May 29, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Fri May 29 16:11:05 2026 |
|---|
| Description: | Title: Some users may experience errors when performing actions in Microsoft Fabric Notebooks
User impact: Users may experience errors when performing actions in Microsoft Fabric Notebooks
Current status: We've identified a supporting upstream service is performing at suboptimal levels, resulting in poor performance when completing actions in Microsoft Fabric Notebooks. We're working to identify any possible mitigation options while in parallel investigating the root cause of the upstream impact.
Scope of impact: Some users may experience errors when performing actions in Microsoft Fabric Notebooks during this impacting event.
Start time: Friday, May 29, 2026, at 6:55 PM UTC
Next update by: Friday, May 29, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri May 29 15:48:39 2026 |
|---|
| Description: | Title: Some users may experience errors when performing actions in Microsoft Fabric Notebooks
User impact: Users may experience errors when performing actions in Microsoft Fabric Notebooks
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1309330 - Users are unable to access Microsoft 365 services in South America
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed May 13 09:30:00 2026 |
|---|
| End Time: | Wed May 13 12:30:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri May 29 19:31:49 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 29 19:31:49 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 21 18:52:34 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri May 15 14:48:28 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed May 13 16:04:01 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users were unable to access Microsoft 365 services.
More info: Users may have experienced email delivery delays. intermittent connection disruptions, and encountered service unavailability (503) errors when connecting to Outlook and Microsoft Teams. Additionally, users may have been unable to access SharePoint sites and OneDrive content.
Final status: Service availability has returned to pre-incident thresholds and users are no longer impacted by this issue.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may have been impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
End time: Wednesday, May 13, 2026, at 4:30 PM UTC
Preliminary root cause: Network connectivity issues resulting from a damaged fiber cable caused certain network paths to become unstable. This was further exacerbated by an influx in traffic being routed through alternate paths.
Next steps:
We're examining our failover mechanisms so we can identify areas for more effective traffic rerouting duration during future connectivity issues.
We're still performing a detailed internal post-mortem of the issue. We're providing up to date details in the current Post Incident Report but will be providing further details in an updated Post Incident Report provided by Friday, May 29, 2026.
|
|---|
|
| Time: | Wed May 13 15:29:26 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays. intermittent connection disruptions, and encounter service unavailability (503) errors when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: The vast majority of users are no longer affected by this event. We're continuing to employ infrastructure optimizations to address full resolution for any users still residually affected.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed May 13 14:10:54 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays. intermittent connection disruptions, and encounter service unavailability (503) errors when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: While the service remains stable for the majority of users, we’re taking steps to further manage traffic and reduce demand on portions of the service that are experiencing high load. By optimizing how data is processed, we’re working to stabilize performance across the environment.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed May 13 13:26:42 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays. intermittent connection disruptions, and encounter service unavailability (503) errors when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: We’re actively redirecting traffic to healthy infrastructure to further reduce impact and improve service performance. We’re continuing to monitor the environment as these changes take effect.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed May 13 12:55:25 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays. intermittent connection disruptions, and encounter service unavailability (503) errors when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: Our telemetry indicates that service has recovered for the majority of users, and we’re continuing our work to ensure long-term stability across the affected infrastructure. To that end, we’re bringing an additional network route online and making adjustments to traffic flow to help improve connectivity to the remaining impacted service segment.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed May 13 12:16:40 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays and intermittent connection disruptions when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: We’ve confirmed that many users are now experiencing relief as a result of our mitigation actions; however, high demand on a portion of infrastructure we routed traffic through may be resulting in residual impact to some users. We’re adding additional resources to this infrastructure and are continuing to monitor for recovery.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed May 13 11:49:38 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays and intermittent connection disruptions when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: We’ve identified a fiber connectivity disruption between regions in South America impacting service availability. Traffic has been rerouted to alternate network paths, and we're continuing to monitor the environment to ensure service is restored.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Start time: Wednesday, May 13, 2026, at 1:30 PM UTC
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed May 13 11:19:59 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays and intermittent connection disruptions when connecting to Outlook and Teams. Additionally, users may be unable to access SharePoint sites and OneDrive content.
Current status: We’re taking mitigative actions which include bringing affected network paths back online and redirecting traffic to healthy network infrastructure. We’re continuing to monitor the impact and working to restore service while further isolating the underlying cause.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Preliminary root cause: Intermittent network connectivity issues are causing certain network paths to become unstable, resulting in increased traffic being routed through alternate paths and leading to impact.
Next update by: Wednesday, May 13, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Wed May 13 11:01:05 2026 |
|---|
| Description: | We've identified a network connection issue in South America affecting connections for users hosted primarily in that region. We're working to bring additional network resources online to mitigate impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed May 13 10:59:24 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: Users may experience email delivery delays and intermittent connection disruptions when connecting to Outlook, Teams, and other Microsoft 365 services.
Current status: We’re examining network health and investigating errors observed in internal telemetry to isolate the root cause and determine our next steps.
Scope of impact: Some users in South America attempting to access Microsoft 365 services may be impacted.
Next update by: Wednesday, May 13, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed May 13 10:40:25 2026 |
|---|
| Description: | Title: Users are unable to access Microsoft 365 services in South America
User impact: Some users are unable to access Microsoft 365 services.
More info: User reports indicate that impact is primarily to Outlook, though other Microsoft 365 services and features may be affected.
Current Status: We are aware of an emerging issue where some users are unable to access Microsoft 365 services. We are investigating the issue and will provide another update within the next 30 minutes.
|
|---|
|
TM1283300 - Users may be unable to launch the Microsoft Teams for Windows and Mac desktop clients
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Apr 15 17:27:00 2026 |
|---|
| End Time: | Wed Apr 22 18:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 28 16:22:05 2026 |
|---|
| Root Cause: | A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 28 16:18:00 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Apr 22 18:32:42 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams for Windows and Mac desktop clients
User impact: Users may have been unable to launch the Teams for Windows and Mac desktop clients.
More info: When attempting to launch the Microsoft Teams desktop clients for Windows or Mac, users became stuck on the loading screen and received the following error message: "We're having trouble loading your message. Try refreshing." Impacted users may have been able to restart their client to bypass impact.
Users that continued to see impact may have needed to quit and restart their desktop clients to receive the fix.
Final status: We've monitored service health telemetry for an extended period and confirmed that reverting the offending service update has remediated the impact for all affected users.
Scope of impact: Users attempting to launch the Microsoft Teams desktop clients for Mac may have been impacted by this event.
Start time: Wednesday, April 15, 2026, at 9:27 PM UTC
End time: Wednesday, April 22, 2026, at 10:00 PM UTC
Root cause: A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next steps:
- We're reviewing our update procedures to understand why impact to Microsoft Teams desktop client access wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Wed Apr 22 15:23:11 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams for Windows and Mac desktop clients
User impact: Users may be unable to launch the Teams for Windows and Mac desktop clients.
More info: When attempting to launch the Microsoft Teams desktop clients for Windows or Mac, users become stuck on the loading screen and receive the following error message: "We're having trouble loading your message. Try refreshing." Impacted users may be able to restart their client to bypass impact.
Impact for Windows users is resolved, and users that continue to see impact may need to quit and restart their desktop clients to receive the fix.
Current status: Our monitoring has verified that Window users continue to be no longer impacted by this event; however, Mac users may still intermittently be prevented from launching the Teams desktop client. We're expecting our mitigations will have completed and for impact to be remediated by our next scheduled communication update.
Scope of impact: Users attempting to launch the Microsoft Teams desktop clients for Mac may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, April 15, 2026, at 9:27 PM UTC
Root cause: A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Thursday, April 23, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Apr 21 15:24:59 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop clients for Windows or Mac, users become stuck on the loading screen and receive the following error message: "We're having trouble loading your message. Try refreshing." Impacted users may be able to restart their client to bypass impact.
Windows users that continue to see impact may need to quit and restart their desktop clients to receive the fix.
Current status: We're monitoring service health telemetry which continues to show a positive trend towards recovery for Mac users. We anticipate the service will have fully recovered for all affected users by our next scheduled communications update.
Scope of impact: Users attempting to launch the Microsoft Teams desktop clients for Windows and Mac may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, April 15, 2026, at 9:27 PM UTC
Estimated time to resolve: We anticipate the service will have recovered for all affected users by Wednesday, April 22, 2026, at 8:00 PM UTC.
Root cause: A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Wednesday, April 22, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Apr 20 18:31:19 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop clients for Windows or Mac, users become stuck on the loading screen and receive the following error message: "We're having trouble loading your message. Try refreshing." Impacted users may be able to restart their client to bypass impact.
Windows users that continue to see impact may need to quit and restart their desktop clients to receive the fix.
Current status: While the issue is fully remediated for Windows users, the impact to users with Mac devices appears to be recovering more slowly. We're continuing to review our service health telemetry to ensure that the issue remediates for all Mac users as expected.
Scope of impact: Users attempting to launch the Microsoft Teams desktop clients for Windows and Mac may be impacted by this event. This section may be updated as our investigation continues.
Start time: Wednesday, April 15, 2026, at 9:27 PM UTC
Root cause: A recent client configuration change introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Tuesday, April 21, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Apr 20 14:34:05 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client on Mac or Windows devices, users are stuck on the loading screen and receive the following error message: "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Now that the offending update that introduced the regression has been fully reverted, a restart will be needed in which users fully quit and then restart Teams so that our solution propagates. While we work towards full remediation, your organization may experience increased network traffic loads as impacted users conduct these restarts.
Current status: We’ve confirmed through service health telemetry that this issue is fully resolved for users attempting to launch the Microsoft Teams desktop client on Windows devices. We're continuing to monitor recovery metrics for Mac devices in order to validate impact is remediated for all affected devices as users quit and restart the Microsoft Teams client.
Scope of impact: Users attempting to launch the Microsoft Teams desktop client may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Monday, April 20, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Apr 17 20:24:29 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on the loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Now that the update that introduced the regression has been fully reverted, a restart will be needed in which users fully quit and then restart Teams so that our solution propagates.
Current status: We’re continuing to await feedback from the subset of impacted users and monitoring our service telemetry to confirm the issue is resolved after we've completed the aforementioned reversion.
Scope of impact: Users attempting to launch the Microsoft Teams desktop client may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Monday, April 20, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Apr 17 17:48:27 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on the loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Current status: We've fully reverted the update that introduced the regression. A restart will be needed in which users fully quit and then restart Teams so that our solution will propagate. We're reaching out to a subset of impacted users to validate if the reversion of the offending update has alleviated impact as expected.
Scope of impact: Users attempting to launch the Microsoft Teams desktop client may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Saturday, April 18, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Apr 17 14:42:46 2026 |
|---|
| Description: | Title: Users may be unable to launch the Microsoft Teams desktop client
User impact: Users may be unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on the loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Current status: We've determined that a recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in this transient issue's impact. We're reverting the offending update to remediate impact and will provide a timeline on this process as one becomes available.
Scope of impact: Users attempting to launch the Microsoft Teams desktop client may be impacted by this event. This section may be updated as our investigation continues.
Root cause: A recent service update introduced a regression within the Microsoft Teams client build caching system and is resulting in impact.
Next update by: Monday, April 20, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Apr 17 13:15:38 2026 |
|---|
| Description: | Title: Some users are unable to launch the Microsoft Teams desktop client
User impact: Users are unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Current status: We've confirmed with your representatives that our automated recovery system has successfully remediated impact for the majority of users. We're requesting HTTP Archive format (HAR) capture logs from a subset of users who are still experiencing impact so that we may continue investigating into this issue and develop an appropriate strategy for remediating lingering impact.
Scope of impact: Your organization is affected by this event, and some users attempting to launch the Microsoft Teams desktop client are impacted.
Start time: Friday, April 17, 2026, at 10:00 AM UTC
Root cause: A transient issue within the service infrastructure is causing certain older Microsoft Teams desktop client builds to enter an unhealthy state, and is resulting in impact.
Next update by: Friday, April 17, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Apr 17 11:28:48 2026 |
|---|
| Description: | Title: Some users are unable to launch the Microsoft Teams desktop client
User impact: Users are unable to launch the Teams desktop client.
More info: When attempting to launch the Microsoft Teams desktop client, users are stuck on loading screen and receive an error message "We're having trouble loading your message. Try refreshing."
Impacted users should restart their client to bypass impact.
Current status: We've identified that a transient issue within the service infrastructure is causing certain older Microsoft Teams desktop client builds to enter an unhealthy state, and is resulting in impact. We've confirmed that our automated recovery system has successfully remediated impact and we're reaching out to your representatives to validate this issue is fully resolved for all users.
Scope of impact: Your organization is affected by this event, and some users attempting to launch the Microsoft Teams desktop client are impacted.
Root cause: A transient issue within the service infrastructure is causing certain older Microsoft Teams desktop client builds to enter an unhealthy state, and is resulting in impact.
Next update by: Friday, April 17, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Apr 17 09:16:44 2026 |
|---|
| Description: | Title: Some users are unable to launch the Microsoft Teams desktop client
User impact: Users are unable to launch the Teams desktop client.
More info: When attempting to launch the Teams application, users receive the error:
'Stuck on loading screen and then it gives a message "We're having trouble loading your message. Try refreshing"
Current status: We’re reviewing support provided information and service telemetry to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to launch the Teams desktop client are impacted.
Next update by: Friday, April 17, 2026, at 3:30 PM UTC
|
|---|
|
EX1325157 - Some users may be intermittently unable to send outbound Exchange Online email messages
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 22 11:30:00 2026 |
|---|
| End Time: | Thu May 28 01:32:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 28 13:38:22 2026 |
|---|
| Root Cause: | A recent code change caused the license status for affected users to intermittently be returned incorrectly during the outbound email sending authentication flow, which prevented users from sending email messages.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 28 12:42:11 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to send outbound Exchange Online email messages
User impact: Users may have been intermittently unable to send outbound Exchange Online email messages.
More info: When affected users attempted to send outbound Exchange Online email messages, they may have received a Non-Delivery Report (NDR) with a 550 5.7.233 error that indicated they exceeded their Tenant External Recipient Rate Limit (TERRL) despite being under the limit.
Final status: We've identified that a recent code change caused the license status for affected users to intermittently be returned incorrectly during the outbound email sending authentication flow, which prevented users from sending email messages. We've reversed the offending change and confirmed through service health telemetry that the impact is remediated
Scope of impact: Some users located in North America that attempted to send outbound Exchange Online email messages may have been intermittently impacted.
Start time: Friday, May 22, 2026, at 3:30 PM UTC
End time: Thursday, May 28, 2026, at 5:32 AM UTC
Root cause: A recent code change caused the license status for affected users to intermittently be returned incorrectly during the outbound email sending authentication flow, which prevented users from sending email messages.
Next steps:
- We're reviewing our service change testing and validation procedures to identify and prevent issues with inaccurate license statuses that impact users' mailflow in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 28 12:29:19 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to send outbound Exchange Online email messages
User impact: Users may have been intermittently unable to send outbound Exchange Online email messages.
More info: When affected users attempted to send outbound Exchange Online email messages, they may have received a Non-Delivery Report (NDR) with a 550 5.7.233 error that indicated they exceeded their Tenant External Recipient Rate Limit (TERRL) despite being under the limit.
Current status: We've investigated a problem with Exchange Online in which some users may have been intermittently unable to send outbound Exchange Online email messages and received an NDR with a 550 5.7.233 error, 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.
|
|---|
|
TM1325101 - Some users may experience delays or failures for multiple Microsoft Teams scenarios
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 28 10:00:00 2026 |
|---|
| End Time: | Thu May 28 11:07:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 28 12:19:49 2026 |
|---|
| Root Cause: | Portions of our Teams service infrastructure had been removed for scheduled maintenance while an error in this process prevented alternate infrastructure from being added to prevent impact from occurring, which resulted in overall infrastructure availability struggling to process user demand as traffic spiked.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 28 12:19:10 2026 |
|---|
| Description: | Title: Some users may experience delays or failures for multiple Microsoft Teams scenarios
User impact: Users may have experienced delays or failures for multiple Microsoft Teams scenarios.
More info: Users may have experienced delays or failures for the following Teams scenarios:
- Meeting dial-in failures
- Call queue disconnections or failures
- Auto attendants failing to route as expected
- Teams call recordings failing to generate
- Any automated scenario within Microsoft Teams
Users may have been returned a timeout error when actions failed.
Final status: We've completed our monitoring of service availability and validated that after adding the removed infrastructure back into active service rotation, impact is remediated.
Scope of impact: Some users in North America may have experienced delays or failures for multiple Microsoft Teams automated scenarios.
Start time: Thursday, May 28, 2026, at 2:00 PM UTC
End time: Thursday, May 28, 2026, at 3:07 PM UTC
Root cause: Portions of our Teams service infrastructure had been removed for scheduled maintenance while an error in this process prevented alternate infrastructure from being added to prevent impact from occurring, which resulted in overall infrastructure availability struggling to process user demand as traffic spiked.
Next steps:
- We're isolating why additional service infrastructure was unable to be implemented once portions of the Team service infrastructure had been removed for scheduled maintenance. This analysis will help us to prevent similar impact scenarios from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 28 11:25:14 2026 |
|---|
| Description: | Title: Some users may experience delays or failures for multiple Microsoft Teams scenarios
User impact: Users may experience delays or failures for multiple Microsoft Teams scenarios.
More info: Users may experience delays or failures for the following Teams scenarios:
- Meeting dial-in failures
- Call queue disconnections or failures
- Auto attendants failing to route as expected
- Teams call recordings failing to generate
- Any automated scenario within Microsoft Teams
Users may be returned a timeout error when actions fail.
Current status: We've isolated that users with North America are experiencing a degradation in multiple Microsoft Teams automated scenarios as outlined in the "More Info" section of this communication. We've isolated that portions of our Teams service infrastructure had been removed for scheduled maintenance and an error in this process prevented alternate infrastructure from being added to prevent impact from occurring, which resulted in overall infrastructure availability struggling to process user demand as traffic spiked. We've temporarily added the removed infrastructure back into active service rotation to allow affected traffic to be processed as expected, and we're monitoring service availability to validate that our actions successfully mitigated the impact.
Scope of impact: Some users in North America may experience delays or failures for multiple Microsoft Teams automated scenarios. This section may be updated as the investigation progresses.
Start time: Thursday, May 28, 2026, at 2:00 PM UTC
Root cause: Portions of our Teams service infrastructure had been removed for scheduled maintenance while an error in this process prevented alternate infrastructure from being added to prevent impact from occurring, which resulted in overall infrastructure availability struggling to process user demand as traffic spiked.
Next update by: Thursday, May 28, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu May 28 11:03:33 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.
|
|---|
|
PB1314779 - Users may be unable to access or may experience delays when accessing Microsoft Fabric
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon May 18 09:53:00 2026 |
|---|
| End Time: | Tue May 19 16:59:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | Fabric |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 28 07:46:02 2026 |
|---|
| Root Cause: | On May 18, 2026, Microsoft identified elevated fraudulent traffic volumes for the Microsoft Fabric service. This resulted in increased load on portions of the front-end infrastructure, leading to intermittent service degradation. The traffic exhibited characteristics outside of typical usage patterns, which contributed to resource saturation before mitigation controls were fully optimized, leading to increased request failures. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 26 19:49:00 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 21 19:03:51 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue May 19 14:30:25 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may have been unable to access or may have experienced delays when accessing Microsoft Fabric.
Final status: After a period of extended monitoring, we confirmed that the issue is resolved.
Scope of impact: Any user attempting to access Microsoft Fabric may have been impacted.
Start time: Monday, May 18, 2026, at 1:53 PM UTC
End time: Monday, May 18, 2026, at 8:59 PM UTC
Root cause: On May 18, 2026, Microsoft identified elevated fraudulent traffic volumes for the Microsoft Fabric service. This resulted in increased load on portions of the front-end infrastructure, leading to intermittent service degradation. The traffic exhibited characteristics outside of typical usage patterns, which contributed to resource saturation before mitigation controls were fully optimized, leading to increased request failures.
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: | Mon May 18 17:58:12 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: The service remains healthy at this time and we're continuing to monitor telemetry and assess overall service stability to determine whether any additional actions to fully resolve the issue may be required.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Root cause: An unexpected increase in request traffic is causing the portion of infrastructure that handles Microsoft Fabric access to operate in a suboptimal state, resulting in impact.
Next update by: Wednesday, May 20, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon May 18 17:22:02 2026 |
|---|
| Description: | Our telemetry indicates service health remains healthy following our mitigating actions and we're continuing to monitor to ensure the issue is fully resolved.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon May 18 16:54:15 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We’ve applied the targeted mitigations to resolve the issues with residual traffic in all regions, and our telemetry shows service health is recovering. Some users have reported impact is remediated and we'll continue to monitor service health to ensure the issue is resolved for all users.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Preliminary root cause: An unexpected increase in request traffic is causing the portion of infrastructure that handles Microsoft Fabric access to operate in a suboptimal state, resulting in impact.
Next update by: Monday, May 18, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon May 18 16:22:13 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We’re continuing to see improvements in the regions where our fix is deployed, and we're applying additional targeted mitigations to resolve the issues with residual traffic, which is contributing to a slower recovery for some users.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Preliminary root cause: An unexpected increase in request traffic is causing the portion of infrastructure that handles Microsoft Fabric access to operate in a suboptimal state, resulting in impact.
Next update by: Monday, May 18, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon May 18 15:49:11 2026 |
|---|
| Description: | We’re continuing to see improvements in the regions where our fix is deployed. We’ve identified some residual traffic which is slowing recovery in some regions and are investigating additional targeted mitigations.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon May 18 15:16:56 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We've completed our deployment of the fix to the West US region, and we're seeing service health recovering as a result of our actions. We've started expanding the fix deployment to additional regions and we'll provide an ETA for resolution once one becomes available.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Preliminary root cause: An unexpected increase in request traffic is causing the portion of infrastructure that handles Microsoft Fabric access to operate in a suboptimal state, resulting in impact.
Next update by: Monday, May 18, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon May 18 14:31:10 2026 |
|---|
| Description: | We're applying the fix to balance the impacting request traffic to a subset of the affected infrastructure. Once deployed, we will validate it fully resolves impact before deploying more broadly.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon May 18 14:11:06 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We're working on balancing the impacting request traffic to recover service health while we continue to investigate the source of impact and identify any additional mitigating actions.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Next update by: Monday, May 18, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon May 18 12:23:19 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We've identified an unexpected increase in request traffic that's causing the portion of infrastructure to operate in a suboptimal state. We're continuing to investigate the source of this traffic while we determine the most efficient method to remediate the impact.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Next update by: Monday, May 18, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon May 18 11:17:25 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: Our service health monitoring has alerted us to increased failures occurring when users attempt to access Microsoft Fabric. We're investigating the call requests to the portion of service infrastructure responsible for facilitating access to Microsoft Fabric to identify the source of the failures.
Scope of impact: Any user attempting to access Microsoft Fabric may be impacted.
Start time: Monday, May 18, 2026, at 12:24 PM UTC
Next update by: Monday, May 18, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon May 18 11:08:06 2026 |
|---|
| Description: | Title: Users may be unable to access or may experience delays when accessing Microsoft Fabric
User impact: Users may be unable to access or may experience delays when accessing Microsoft Fabric.
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1318025 - Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 6 03:44:00 2026 |
|---|
| End Time: | Wed May 27 19:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 27 21:38:50 2026 |
|---|
| Root Cause: | A recent change contained a code regression which was creating multiple Copilot Analyst agent request IDs that carried the same value and resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 27 20:46:04 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may have intermittently received blank responses from Analyst agent in Microsoft Copilot.
Final status: We've completed safely disabling the offending OneDrive file and link feature within the affected infrastructure, and we've validated with internal testing that the issue is resolved.
Scope of impact: This event may have impacted any user that utilized the Analyst agent in Copilot.
Start time: Wednesday, May 06, 2026, at 7:44 AM UTC
End time: Wednesday, May 27, 2026, at 11:00 PM UTC
Root cause: A recent change contained a code regression which was creating multiple Copilot Analyst agent request IDs that carried the same value and resulted in impact.
Next steps:
- We're further reviewing the recent change to understand how the code 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 changes.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 27 12:27:29 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Copilot. Affected users can also attempt to bypass persisting impact by avoiding using OneDrive files or links in their Analyst agent requests.
Current status: We've determined that persisting impact is specific to users attempting to receive responses from Analyst agent using OneDrive files and links. We've internally validated that disabling this feature successfully remediates impact and we're assessing our options for safely disabling this OneDrive file and link feature within the affected infrastructure to fully resolve this issue.
Scope of impact: This event may impact any user utilizing the Analyst agent in Copilot.
Start time: Wednesday, May 06, 2026, at 7:44 AM UTC
Root cause: A recent change contains a regression which is creating multiple Copilot Analyst agent request IDs that carry the same value and is subsequently resulting in this impact.
Next update by: Thursday, May 28, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue May 26 22:14:44 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Microsoft Copilot.
Current status: We're continuing our analysis of the telemetry, as well as our internal reproductions of the issue to better understand the source of the impact, which will help us determine our next troubleshooting steps.
Scope of impact: This event may impact any user utilizing the Analyst agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Start time: Wednesday, May 06, 2026, at 7:44 AM UTC
Root cause: A recent change contains a regression which is creating multiple Microsoft Copilot Analyst agent request IDs that carry the same value and is subsequently resulting in this impact.
Next update by: Wednesday, May 27, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue May 26 16:22:19 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Microsoft Copilot.
Current status: We're continuing to analyze service health telemetry and conduct internal reproductions of impact to identify any additional issues contributing to this event's persisting impact to inform how we develop our next mitigative actions.
Scope of impact: This event may impact any user utilizing the Analyst agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Start time: Wednesday, May 06, 2026, at 7:44 AM UTC
Root cause: A recent change contains a regression which is creating multiple Microsoft Copilot Analyst agent request IDs that carry the same value and is subsequently resulting in this impact.
Next update by: Wednesday, May 27, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue May 26 15:26:03 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Microsoft Copilot.
Current status: We've reverted the offending change that introduced this regression but have received feedback from affected users indicating that impact still persists. We're reviewing service health telemetry and conducting internal reproductions of impact to assess what additional mitigative actions may be required to fully resolve this issue.
Scope of impact: This event may impact any user utilizing the Analyst agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Root cause: A recent change contained a regression which is creating multiple Microsoft Copilot Analyst agent request IDs that carry the same value, resulting in this impact.
Next update by: Tuesday, May 26, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue May 26 13:24:16 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst agent in Microsoft Copilot.
Current status: We're continuing to develop potential strategies for remediating impact and will provide a timeline for finishing this process as one becomes available.
Scope of impact: This event may impact any user utilizing the Analyst agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Root cause: A recent change contained a regression which is creating multiple Microsoft Copilot Analyst agent request IDs that carry the same value, resulting in this impact.
Next update by: Tuesday, May 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon May 25 17:43:52 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst Agent in Microsoft Copilot.
Current status: We've confirmed that a recent change contained a regression which created multiple request IDs that carry the same value, resulting in this impact. We're developing a fix to address this error and will provide updates on its implementation as soon as it becomes available.
Scope of impact: This event may impact any user utilizing the Analyst Agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Root cause: A recent change contained a regression which created multiple request IDs that carry the same value, resulting in this impact.
Next update by: Tuesday, May 26, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu May 21 20:09:32 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot.
More info: Affected users can bypass impact by creating a new chat window within the Analyst Agent in Microsoft Copilot.
Current status: Though taking longer than previously anticipated due to the complexity of this issue, we’re continuing our review of the service-side telemetry, along with analyzing recent service updates which may be contributing to impact so that we can refine our understanding of the underlying cause of impact.
Scope of impact: This event may impact any user utilizing the Analyst Agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Next update by: Monday, May 25, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 21 13:38:29 2026 |
|---|
| Description: | Title: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot
User impact: Users may intermittently receive blank responses from Analyst Agent in Microsoft Copilot.
Current status: We're reviewing service-side telemetry in order to isolate the source of this impact and determine our next steps toward remediation.
Scope of impact: This event may impact any user utilizing the Analyst Agent in Microsoft Copilot, and any user might intermittently receive blank responses. This information may be updated as our investigation continues.
Next update by: Friday, May 22, 2026, at 1:30 AM UTC
|
|---|
|
TM1286033 - Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 7 08:00:00 2026 |
|---|
| End Time: | Tue May 26 01:26:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 27 18:40:33 2026 |
|---|
| Root Cause: | A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 27 17:36:17 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to start screen sharing in 1:1 calls using Microsoft Teams web client.
More info: This issue only affected users leveraging Chromium-based browsers, such as the Edge or Chrome browser, attempting to screenshare in a 1:1 call on the Teams web app. Additionally, the first screen sharing session in each call wasn't affected; only subsequent screen-sharing attempts may have been impacted.
While we were working to remediate this issue, affected users could still perform screen sharing by:
- Using the desktop or mobile apps
- Leveraging a non-Chromium-based browser
- Adding another user to the call
- Ending and restarting the call
Final status: Our fix is now fully deployed to both Mac and Windows devices, and any users still encountering the issue can update their Teams web client to the latest version to receive the fix and remediate impact.
Scope of impact: Some users who initiated a second screen sharing session within a 1:1 call using the Microsoft Teams web client may have been affected.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
End time: Tuesday, May 26, 2026, at 5:26 AM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, which resulted in impact.
Next steps: - We're reviewing the responsible service update to better understand the error that resulted in impact in an effort to prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 19 16:56:44 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: This issue only affects users leveraging Chromium-based browsers, such as the Edge or Chrome browser, attempting to screenshare in a 1:1 call on the Microsoft Teams web app. Additionally, the first screen sharing session in each call isn't affected; only subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Leveraging a non-Chromium-based browser
- Adding another user to the call
- Ending and restarting the call
Current status: Our fix for Mac devices is fully deployed and available in Microsoft Teams web client version 26106.2113.4690.1073. Affected Mac users should update their Teams web client to this version to receive the fix and remediate impact. Our fix deployment for Windows devices, which will be available in Microsoft Teams web client version 26106.1911.4707.3286, is continuing to saturate throughout the affected environment. We expect this saturation to complete and remediate the remaining impact by our next scheduled update.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Wednesday, May 27, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue May 19 13:18:25 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: The rollout of our solution to remediate impact is ongoing but progressing slower than anticipated. Current fix saturation is at 75 percent and we're determining what actions we can take to expedite the remainder of our fix deployment.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, May 19, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon May 18 12:05:59 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: The rollout of our solution to remediate impact is ongoing, and we anticipate it will complete by our next scheduled communication update on Tuesday, May 19, 2026, at 6:00 PM UTC.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, May 19, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed May 13 13:10:27 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're monitoring the rollout of our solution, and we'll provide an update on our fix deployment timeline and for when impact will be remediated once they’re available.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, May 18, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed May 13 10:13:07 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We’ve deployed the fix to a portion of the service and are actively progressing the rollout across additional environments. We'll share a deployment completion timeline when one becomes available.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 7, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Wednesday, May 13, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue May 12 13:19:24 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We've validated the fix successfully remediates impact and the deployment has been initiated.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Estimated time to resolve: We expect the deployment to complete by Wednesday, May 13, 2026.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Wednesday, May 13, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Mon May 11 13:15:32 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: Our fix validation has successfully completed, and we expect to have a deployment timeline by the next scheduled update.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, May 12, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Thu May 7 12:44:05 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: Our various fixes are in the final stages of validations, and we anticipate the deployments will be initialized by the time of our next scheduled update.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, May 11, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue May 5 13:16:27 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: Our reworking of the fix has come in the form of several smaller fixes which are currently undergoing internal validation. We'll aim to provide a timeline for the internal validation process to complete, and the deployment of the fixes initiated by our next scheduled communications update.
Scope of impact: Some users initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Thursday, May 07, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon May 4 12:23:32 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: Due to an unrelated issue, the fix wasn't applied correctly and we're reworking the fix to prevent this issue from occurring further.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, May 05, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Apr 30 12:28:30 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may have been unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We've confirmed that the fix has completed deployment, and we're monitoring the environment to validate its effectiveness.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 07, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, May 04, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Apr 29 12:17:35 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're monitoring our deployed fix to validate that it addresses the screen sharing during 1:1 calls and remediates the impact.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Thursday, April 30, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Apr 28 12:03:18 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: After our extended monitoring period of service health telemetry during business hours, we've confirmed that our partially deployed fix is successfully remediating impact for this issue, with many users already experiencing impact relief. We're fully deploying this fix and will provide a timeline for its completion and full impact remediation as one becomes available.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Tuesday, April 7, 2026, at 12:00 PM UTC
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Wednesday, April 29, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Apr 27 12:02:08 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: After reviewing service telemetry based on business hours data, we've confirmed that while telemetry is trending in a positive direction additional monitoring is required to validate impact is fully remediated. We anticipate this process to be completed in the next 24-48 hours, and we anticipate users to begin to see remediation during this time.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Start time: Wednesday, April 08, 2026, at 12:00 PM UTC
Estimated time to resolve: We anticipate our monitoring period to be completed by Wednesday, April 29, 2026.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Tuesday, April 28, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Apr 27 05:59:15 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're investigating service telemetry based on business hours data to determine whether the fix has resolved the issue and that impact has been fully mitigated.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, April 27, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Apr 24 04:25:25 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're continuing to monitor as the fix progresses throughout all affected environments and anticipate its completion by Wednesday, April 29, 2026.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Estimated time to resolve: Wednesday, April 29, 2026
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Monday, April 27, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Fri Apr 24 01:52:26 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We've validated the efficacy of the fix in our internal testing environment and we're monitoring as the fix progresses throughout all affected environments.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected. This section may be updated as our investigation continues.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Friday, April 24, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Apr 23 12:56:03 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We've analyzed recent error trends and identified that a recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact. We've developed a fix to address the incompatibility issue, which we're preparing to deploy to our internal test environment to validate its efficacy in remediating the impact.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Root cause: A recent service update introduced an incompatibility issue for Chromium-based browsers and the Microsoft Teams web client, resulting in impact.
Next update by: Friday, April 24, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Wed Apr 22 11:41:57 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're continuing to analyze the recent error trends to identify the underlying cause of impact, so that we can determine our next steps regarding impact remediation.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Next update by: Thursday, April 23, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Apr 21 12:46:06 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're analyzing error trends over the past seven days for 1:1 and peer-to-peer calls to isolate the specific errors being returned and to determine our next troubleshooting steps.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Next update by: Wednesday, April 22, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Apr 20 12:27:53 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
While we're working to remediate this issue, affected users can still perform screen sharing by:
- Using the desktop or mobile apps
- Adding another user to the call
- Ending and restarting the call
Current status: We're in the process of analyzing gathered logs and service telemetry to better understand the impact scenario and develop a remediation strategy.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Next update by: Tuesday, April 21, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Apr 20 11:20:07 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client.
More info: Specifically, only the first screen sharing session works; subsequent screen-sharing attempts may not be visible.
Current status: We're working to reproduce the issue internally and gather client-side captures to better understand the issue and determine our next steps.
Scope of impact: Any user initiating a second screen sharing session within a 1:1 call using the Microsoft Teams web client may be affected.
Next update by: Monday, April 20, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon Apr 20 10:57:03 2026 |
|---|
| Description: | Title: Some users may be unable to initiate screen sharing in 1:1 calls using the Microsoft Teams web client
User impact: Users may be unable to initiate screen sharing in 1:1 calls 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.
|
|---|
|
CP1323874 - Some users' prompts to Copilot Studio agents that leverage the Microsoft Teams channel connector may fail
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 4 20:00:00 2026 |
|---|
| End Time: | Wed May 27 12:55:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed May 27 13:49:19 2026 |
|---|
| Root Cause: | A recent update intended to allow the acquisition of authentication components using Copilot Studio agents on behalf of the user introduced a regression that caused authentication checks to fail as they weren't provisioned to the user completing the request.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 27 13:16:41 2026 |
|---|
| Description: | Title: Some users' prompts to Copilot Studio agents that leverage the Microsoft Teams channel connector may fail
User impact: Users' prompts to Copilot Studio agents that leveraged the Microsoft Teams channel connector may have failed.
Final status: After analyzing conversation IDs provided by a subset of affected users, we've isolated that a recent update intended to allow the acquisition of authentication components using Copilot Studio agents on behalf of the user introduced a regression that caused authentication checks to fail as they weren't provisioned to the user completing the request. We've rolled back the offending change and validated with a subset of affected tenants that our actions successfully remediated impact.
Scope of impact: Users prompting Copilot Studio agents that leverage the Microsoft Teams channel connector may have had prompts fail to generate.
Start time: Tuesday, May 05, 2026, at 12:00 AM UTC
End time: Wednesday, May 27, 2026, at 4:55 PM UTC
Root cause: A recent update intended to allow the acquisition of authentication components using Copilot Studio agents on behalf of the user introduced a regression that caused authentication checks to fail as they weren't provisioned to the user completing the request.
Next steps:
- We're analyzing the offending update to isolate why the potential for impact wasn't caught during our internal update testing and validation phases. This further analysis will help us to improve our update implementation processes moving forward to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 27 12:14:56 2026 |
|---|
| Description: | Title: Some users' prompts to Copilot Studio agents that leverage the Microsoft Teams channel connector may fail
User impact: Users' prompts to Copilot Studio agents that leverage the Microsoft Teams channel connector may fail.
Current status: We're analyzing conversation IDs provided by a subset of affected users to analyze the APIs invoked by affected Copilot Studio agents to isolate sources contributing to impact and to determine our next troubleshooting steps.
Scope of impact: Some users prompting Copilot Studio agents that leverage the Microsoft Teams channel connector may have prompts fail to generate.
Next update by: Wednesday, May 27, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed May 27 10:20:17 2026 |
|---|
| Description: | Title: Some users’ Copilot Studio agents that leverage the Microsoft Teams channel connector may fail during execution
User impact: Users’ Copilot Studio agent that leverage the Microsoft Teams channel connector may fail during execution.
Current status: We're analyzing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users’ Copilot Studio agents that leverage the Microsoft Teams channel connector may be impacted.
Next update by: Wednesday, May 27, 2026, at 4:30 PM UTC
|
|---|
|
TM1318328 - Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 14 20:00:00 2026 |
|---|
| End Time: | Fri May 22 18:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 26 23:08:50 2026 |
|---|
| Root Cause: | A recent service update contained a code issue with List parameters, causing impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 26 20:11:08 2026 |
|---|
| Description: | Title: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
User impact: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams.
More info: When attempting to open the link, it was unresponsive and didn't open in the Microsoft Teams desktop or web client.
To avoid impact, users could have opened links in Microsoft OneDrive directly in a browser, or opened the Lists link from Microsoft Teams channel or chat.
Final status: We rolled out a code fix to the affected environment and confirmed through our telemetry and with some affected users that the impact is remediated.
Scope of impact: Any user attempting to open Lists links in the Microsoft OneDrive app within Microsoft Teams may have been affected.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
End time: Friday, May 22, 2026, at 10:00 PM UTC
Root cause: A recent service update contained a code issue with List parameters, causing impact.
Next steps: We're working to improve our service update review procedures to better identify similar code issues to prevent impact during future updates.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 22 20:00:34 2026 |
|---|
| Description: | Title: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
User impact: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams.
More info: When attempting to open the link, it's unresponsive and doesn't open in the Microsoft Teams desktop or web client.
To avoid impact, users can open links in Microsoft OneDrive directly in a browser, or open the Lists link from Microsoft Teams channel or chat.
Current status: After determining that a coding fix was the safest strategy for remediation, we've rolled this solution out to the affected environments. We're continuing to monitor this fix and are checking with affected users to validate that the impact is resolved.
Scope of impact: Any user attempting to open Lists links in the Microsoft OneDrive app within Microsoft Teams may be affected. This section may be updated as our investigation continues.
Next update by: Tuesday, May 26, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri May 22 01:39:34 2026 |
|---|
| Description: | Title: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
User impact: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams.
More info: When attempting to open the link, it's unresponsive and doesn't open in the Microsoft Teams desktop or web client.
To avoid impact, users can open links in Microsoft OneDrive directly in a browser, or open the Lists link from Microsoft Teams channel or chat.
Current status: Our analysis of the HAR trace and error logs, along with reviewing any recent changes made to the Lists link service in the Microsoft OneDrive app within Microsoft Teams, has identified and correlated impact with a recent update to the service. We're reviewing this update further to assess and develop the safest strategy going forward to remediate impact.
Scope of impact: Any user attempting to open Lists links in the Microsoft OneDrive app within Microsoft Teams may be affected. This section may be updated as our investigation continues.
Next update by: Saturday, May 23, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu May 21 20:27:07 2026 |
|---|
| Description: | Title: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams
User impact: Users may be unable to open Lists links in the Microsoft OneDrive app within Microsoft Teams.
More info: When attempting to open the link, it's unresponsive and doesn't open in the Microsoft Teams desktop or web client.
To avoid impact, users can open links in Microsoft OneDrive directly in a browser, or open the Lists link from Microsoft Teams channel or chat.
Current status: We've received reports of an issue where Lists links are unresponsive and don't open in the Microsoft OneDrive app within Microsoft Teams. We're reviewing the provided HTTP Archive format (HAR) trace logs and Microsoft Teams error log telemetry, to help pinpoint the underlying cause of impact which will inform our next steps.
Scope of impact: Any user attempting to open Lists links in the Microsoft OneDrive app within Microsoft Teams may be affected. This section may be updated as our investigation continues.
Next update by: Friday, May 22, 2026, at 6:00 AM UTC
|
|---|
|
MO1322422 - Some admins' Viva Learning activity reports may be delayed in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon May 25 20:00:00 2026 |
|---|
| End Time: | Tue May 26 02:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue May 26 13:41:04 2026 |
|---|
| Root Cause: | An issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery is resulting in delays.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue May 26 13:39:26 2026 |
|---|
| Description: | Title: Some admins' Viva Learning activity reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Viva Learning activity reports may have been delayed in the Microsoft 365 admin center.
More info: Impact was specific to admins in the North America, Europe, and Asia-Pacific regions. The latest refresh date shown may have been as outdated as May 20th, 2026.
While the impact has been remediated, reports for May 21st, 2026, are not available.
Final status: We've confirmed that the issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery has been successfully remediated, and the delayed reports are available for all affected users.
Scope of impact: Some admins in the North America, Europe, and Asia-Pacific regions attempting to view Viva Learning reports in the Microsoft 365 admin center may be impacted.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
End time: Tuesday, May 26, 2026, at 6:00 AM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery is resulting in delays.
Next steps: - We're reviewing internal processes to streamline remediation.
- We're continuing to monitor the involved pipeline to ensure that this issue does not reoccur.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 25 18:46:39 2026 |
|---|
| Description: | Title: Some admins' Viva Learning activity reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Viva Learning activity reports may be delayed in the Microsoft 365 admin center.
More info: Impact is specific to admins in the North America, Europe, and Asia-Pacific regions. The latest refresh date shown may be as outdated as May 20th, 2026.
Current status: We've identified that an issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery is resulting in delays. We're working to resolve the upstream pipeline issue to resolve the delays and aim to confirm a timeline for full remediation as one becomes available.
Scope of impact: Some admins in the North America, Europe, and Asia-Pacific regions attempting to view Viva Learning reports in the Microsoft 365 admin center may be impacted.
Start time: Tuesday, May 26, 2026, at 12:00 AM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate Viva Learning activity report delivery is resulting in delays.
Next update by: Tuesday, May 26, 2026, at 10:00 PM UTC
|
|---|
|
TM1303836 - Users experienced incorrect characters in Microsoft Teams call notifications when display names included diacritics.
| Status: | serviceRestored |
|---|
| Start Time: | Fri Apr 10 01:30:00 2026 |
|---|
| End Time: | Fri May 22 18:41:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon May 25 10:47:00 2026 |
|---|
| Root Cause: | A prior fix addressing corrupted text when character encoding failed in call titles inadvertently corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 25 09:43:20 2026 |
|---|
| Description: | Title: Users experienced incorrect characters in Microsoft Teams call notifications when display names included diacritics.
User impact: Users experienced incorrect characters in Microsoft Teams call notifications when display names included diacritics.
More info: Users saw incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contained European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Final status: We've confirmed after a period of monitoring service telemetry that impact has been remediated.
Scope of impact: Impact was specific to some users receiving inbound Microsoft Teams calls notifications when display names contained diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
End time: Friday, May 22, 2026, at 10:41 PM UTC
Root cause: A prior fix addressing corrupted text when character encoding failed in call titles inadvertently corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next steps:
- We're reviewing our deployment and provisioning procedures to help prevent similar problems in the future.
|
|---|
|
| Time: | Thu May 21 11:36:29 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We're monitoring the deployment of our solution which is taking a bit longer than previously estimated to complete. Our internal service telemetry reports it has completed approximately 70 percent of its deployment and has verified that it's addressing the problems users are facing regarding the incorrect characters in Microsoft Teams call notifications. We're expecting that users will no longer be impacted once our deployment has completed, which is expected to finish by our next scheduled communication update.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Estimated time to resolve: Monday, May 25, 2026.
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Monday, May 25, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue May 12 11:16:05 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We've confirmed that the fix deployment is proceeding as expected, with an estimated completion date of Thursday, 21 May 2026.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Estimated time to resolve: Thursday, 21 May 2026.
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Thursday, May 21, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri May 8 11:32:07 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We've completed the validations of the code fix, and we're initializing deployment. We'll monitor the progress and share our projected timeline for remediation as it becomes available.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Tuesday, May 12, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri May 8 09:42:38 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We’re continuing to validate the code fix to confirm its effectiveness before deploying it to the affected infrastructure. We'll share a deployment timeline once the validation is complete.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Friday, May 08, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Fri May 8 03:36:09 2026 |
|---|
| Description: | Title: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics
User impact: Users may see incorrect characters in incoming Microsoft Teams call notifications when display names contain diacritics.
More info: Users may see incorrect or corrupted characters in incoming Microsoft Teams call notification banners when display names contain European diacritical characters (e.g. ä, é, ü), resulting in names appearing with placeholder symbols.
Current status: We've identified a prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact. We're validating a code fix to mitigate impact.
Scope of impact: Impact is specific to some users receiving inbound Microsoft Teams calls notifications when display names contain diacritics.
Start time: Friday, April 10, 2026, at 5:30 AM UTC
Root cause: A prior fix addressing corrupted text appearing when character encoding fails in call titles has unintentionally corrupted valid UTF-8 special characters in display names, causing improper character rendering in inbound call notifications and resulting in impact.
Next update by: Friday, May 08, 2026, at 2:00 PM UTC
|
|---|
|
EX1321282 - Users were intermittently unable to access Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Sun May 24 19:00:00 2026 |
|---|
| End Time: | Mon May 25 03:15:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon May 25 04:43:12 2026 |
|---|
| Root Cause: | A service issue following an authentication activity led to a condition that disrupted normal authentication behavior and access to Exchange Online.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 25 04:31:22 2026 |
|---|
| Description: | Title: Users were intermittently unable to access Exchange Online
User impact: Users were intermittently unable to access Exchange Online.
More info: Users experienced intermittent failures when attempting to access their mailbox, including sign-in failures and connection errors. This impact occurred across various connection methods and client experiences, where access attempts did not complete successfully or timed out.
Final status: We’ve confirmed after a period of monitoring, that the impacted infrastructure self-restored, and service has returned to expected performance levels. We'll closely monitor the service to ensure that it remains healthy.
Scope of impact: Impact was specific to some users served through the affected infrastructure in the Exchange Online service, attempting to access their mailboxes.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
End time: Monday, May 25, 2026, at 7:15 AM UTC
Root cause: A service issue following an authentication activity led to a condition that disrupted normal authentication behavior and access to Exchange Online.
Next steps: We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for this event.
|
|---|
|
| Time: | Mon May 25 02:15:06 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access Exchange Online
User impact: Users may intermittently be unable to access Exchange Online.
Current status: We've confirmed that impact began shortly after certain authentication components stopped functioning as expected. We're furthering our investigation on the diagnostic data to help determine our path towards remediation to restore the affected authentication components.
Scope of impact: This issue may impact users worldwide that are routed through the impacted infrastructure. This information may be updated as our investigation continues.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
Root cause: A portion of the structured query language infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected, resulting in impact.
Next update by: Monday, May 25, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Mon May 25 00:17:30 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access Exchange Online
User impact: Users may intermittently be unable to access Exchange Online.
Current status: In an attempt to alleviate impact, we've restarted some of the affected infrastructure with mixed results. We're continuing our root cause investigation using all available diagnostic data to help determine our next steps towards remediation.
Scope of impact: This issue may impact users worldwide that are routed through the impacted infrastructure. This information may be updated as our investigation continues.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
Root cause: A portion of the structured query language infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected, resulting in impact.
Next update by: Monday, May 25, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Sun May 24 22:09:02 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access Exchange Online
User impact: Users may intermittently be unable to access Exchange Online.
Current status: We've confirmed that faulty authentication components within the infrastructure caused impact. We're developing and deploying a fix we anticipate will alleviate impact.
Scope of impact: This issue may impact users worldwide that are routed through the impacted infrastructure. This information may be updated as our investigation continues.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
Root cause: A portion of the structured query language infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected, resulting in impact.
Next update by: Monday, May 25, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Sun May 24 20:22:56 2026 |
|---|
| Description: | Title: Users may intermittently be unable to access Exchange Online
User impact: Users may intermittently be unable to access Exchange Online.
Current status: We were alerted that a portion of the SQL infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected which resulted in impact. We're investigating different troubleshooting methods to alleviate impact.
Scope of impact: This issue may impact users worldwide that are routed through the impacted infrastructure. This information may be updated as our investigation continues.
Start time: Sunday, May 24, 2026, at 11:00 PM UTC
Root cause: A portion of the structured query language infrastructure responsible for accessing Exchange Online isn't performing as efficiently as expected, resulting in impact.
Next update by: Monday, May 25, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Sun May 24 19:22:54 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.
|
|---|
|
CP1320293 - Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 22 20:00:00 2026 |
|---|
| End Time: | Sun May 24 12:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun May 24 15:52:56 2026 |
|---|
| Root Cause: | An issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data was resulting in delays.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun May 24 15:52:07 2026 |
|---|
| Description: | Title: Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may have been delayed from appearing in the Microsoft 365 admin center.
More info: Specifically, admins in North America and the Asia-Pacific region attempting to view Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted by delays. The latest refresh date shown may have been as outdated as May 20th, 2026.
Final status: We've recovered the affected upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data and have monitored as updated reporting data was delivered to affected users. We've completed our monitoring period at this time and validated that our actions have successfully remediated impact.
Scope of impact: Admins in North America and the Asia-Pacific region attempting to view Microsoft 365 Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may have been impacted.
Start time: Saturday, May 23, 2026, at 12:00 AM UTC
End time: Sunday, May 24, 2026, at 4:00 PM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data was resulting in delays.
Next steps:
- We're analyzing the affected upstream data pipeline to further our understanding of the underlying issue causing delayed reporting data, as this analysis will help us to prevent similar impact scenarios from occurring in the future.
|
|---|
|
| Time: | Sat May 23 20:13:39 2026 |
|---|
| Description: | Title: Some admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center
User impact: Admins' Copilot usage and chat report data may be delayed from appearing in the Microsoft 365 admin center.
More info: Specifically, admins in North America and the Asia-Pacific region attempting to view Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may be impacted by delays. The latest refresh date shown may be as outdated as May 20th, 2026.
Current status: We've identified through internal monitoring that an issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data is resulting in delays. We're working to resolve the upstream delays and aim to confirm a timeline for remediation as it becomes available.
Scope of impact: Admins in North America and the Asia-Pacific region attempting to view Microsoft 365 Copilot usage and chat report data in the Microsoft 365 admin center or directly through Graph API queries may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, May 23, 2026, at 12:00 AM UTC
Root cause: An issue affecting an upstream data pipeline leveraged to facilitate the delivery of Copilot usage and chat report data is resulting in delays.
Next update by: Sunday, May 24, 2026, at 10:00 PM UTC
|
|---|
|
IT1319078 - Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Tue Apr 14 14:00:00 2026 |
|---|
| End Time: | Sat May 23 14:00:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat May 23 19:22:32 2026 |
|---|
| Root Cause: | A latent code issue within our assignment filter logic was causing an issue within a device model validation process and resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat May 23 19:22:32 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may have been unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacted admins who used model name assignment filters for Apple devices.
Final status: Following the completion of our deployment process, we’ve confirmed that impact has been remediated after monitoring an extended period of monitoring the affected service infrastructure.
Scope of impact: This event may have impacted any admin who attempted to use model name assignment filters to apply policies with DDM in Microsoft Intune.
Start time: Tuesday, April 14, 2026, at 12:17 PM UTC
End time: Sunday, May 24, 2026, at 6:00 PM UTC
Root cause: A latent code issue within our assignment filter logic was causing an issue within a device model validation process and resulting in impact.
Next steps:
- We’re continuing to analyze how the latent code issue within our assignment filter logic manifested, as these actions will help us to clarify what actions we can take to ensure similar impact doesn't occur in future and to continue our ongoing mission to improve the resilience of our service for all Microsoft Intune users.
This is the final update for the event.
|
|---|
|
| Time: | Fri May 22 21:18:55 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may be unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacts admins using model name assignment filters for Apple devices.
Current status: We’ve completed our validations to ensure that the aforementioned code fix will resolve the issue and we’ve initiated the deployment process. Additionally, we anticipate that a remediation timeline will be provided by our next scheduled update.
Scope of impact: This event may impact any admin attempting to use model name assignment filters to apply policies with DDM in Microsoft Intune. This information may be updated as our investigation continues.
Start time: Tuesday, April 14, 2026, at 12:17 PM UTC
Root cause: A latent code issue within our assignment filter logic is causing an issue within a device model validation process and resulting in impact.
Next update by: Sunday, May 24, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Fri May 22 17:54:41 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may be unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacts admins using model name assignment filters for Apple devices.
Current status: We're still in the process of validating and testing our code fix to correct this logic path error to ensure that it successfully remediates the issue for all users. We'll provide an estimate on our fix deployment timeline when the validation process has completed.
Scope of impact: This event may impact any admin attempting to use model name assignment filters to apply policies with DDM in Microsoft Intune. This information may be updated as our investigation continues.
Start time: Tuesday, April 14, 2026, at 12:17 PM UTC
Root cause: A latent code issue within our assignment filter logic is causing an issue within a device model validation process and resulting in impact.
Next update by: Saturday, May 23, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri May 22 16:21:33 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may be unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacts admins using model name assignment filters for Apple devices.
Current status: We've determined that a latent code issue within our assignment filter logic is causing an issue within a device model validation process and resulting in impact. We're validating a code fix to correct this logic path and will provide an update on its deployment timeline as soon as one becomes available.
Scope of impact: This event may impact any admin attempting to use model name assignment filters to apply policies with DDM in Microsoft Intune. This information may be updated as our investigation continues.
Root cause: A latent code issue within our assignment filter logic is causing an issue within a device model validation process and resulting in impact.
Next update by: Friday, May 22, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Fri May 22 15:43:54 2026 |
|---|
| Description: | Title: Some admins may be unable to apply policies using filters with Declarative Device Management (DDM) in Microsoft Intune
User impact: Admins on Apple devices may be unable to apply policies using filters with DDM in Microsoft Intune.
More info: This only impacts admins using model name assignment filters for Apple devices.
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.
|
|---|
|
TM1317239 - Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 19 00:17:00 2026 |
|---|
| End Time: | Fri May 22 20:21:56 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri May 22 20:23:02 2026 |
|---|
| Root Cause: | A recent third-party service update to iOS 26.5 caused compatibility issues.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 22 20:22:58 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may have been unable to join town halls in Microsoft Teams using iOS 26.5 version and received an error message.
Final status: The fix deployment completed and after a period of monitoring, we confirmed impact is remediated.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Start time: Tuesday, May 19, 2026, at 4:17 AM UTC
End time: Friday, May 22, 2026, at 8:15 PM UTC
Root cause: A recent third-party service update to iOS 26.5 caused compatibility issues.
Next steps:
- To help prevent similar impact in the future, we're further working with the third-party service to understand how this update caused impact.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 21 19:15:08 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message.
Current status: We've completed the final steps required for deployment of the fix. We expect the deployment to be complete by the time of our next scheduled communication, and will continue to monitor progress to ensure timely remediation.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Next update by: Saturday, May 23, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed May 20 23:24:41 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message.
Current status: We’ve completed the validation process for our potential solution and are preparing it for deployment. We anticipate being able to provide a deployment timeline by our next scheduled communications update.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Next update by: Friday, May 22, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed May 20 22:52:50 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message.
Current status: We’ve completed developing the aforementioned potential solution and are validating it prior to its deployment to ensure it doesn't cause any adverse effects.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Next update by: Thursday, May 21, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Wed May 20 21:34:20 2026 |
|---|
| Description: | Title: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message
User impact: Users may be unable to join town halls in Microsoft Teams using iOS 26.5 version and get an error message.
Current status: We’ve identified a recent change made to iOS 26.5 version that may be contributing to the impact. We're developing a potential solution to test whether it remediates the issue and confirms our root cause theory.
Scope of impact: Any user attempting to join town halls in Microsoft Teams using iOS 26.5 version may be affected by this issue. This section may be updated as our investigation continues.
Next update by: Thursday, May 21, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed May 20 21:15:13 2026 |
|---|
| Description: | Title: Users may be unable to join Townhall streams in Microsoft Teams using iOS 26.5 version
User impact: Users may be unable to join Townhall streams in Microsoft Teams using iOS 26.5 version.
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.
|
|---|
|
CP1314992 - Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
| Status: | serviceRestored |
|---|
| Start Time: | Sun Apr 26 15:00:00 2026 |
|---|
| End Time: | Wed May 20 02:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri May 22 15:01:13 2026 |
|---|
| Root Cause: | A recent feature enablement was responsible for impact. Previously, this feature could have resulted in impact if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature was turned on by default for all users.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri May 22 14:55:28 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may have been unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license couldn't install shared agents that were created by licensed users.
Impacted, licensed users could disable this feature in the Copilot Knowledge card by toggling off the "Reference org chart and profile info" setting.
Final status: We’ve completed the deployment of our fix to the affected environments and verified with affected users that this action has successfully resolved the impact.
Scope of impact: This issue may have impacted users without a Copilot license who were trying to install agents.
Start time: Sunday, April 26, 2026, at 7:00 PM UTC
End time: Wednesday, May 20, 2026, at 6:00 AM UTC
Root cause: A recent feature enablement was responsible for impact. Previously, this feature could have resulted in impact if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature was turned on by default for all users.
Next steps: We’re investigating why the recent feature enablement changed the default behavior for all users and reviewing our deployment and validation processes to prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Mon May 18 19:25:08 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may be unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license can't install shared agents that were created by licensed users.
Currently impacted, licensed users can disable this feature in the Copilot Knowledge card by toggling off the "Reference org chart and profile info" setting.
Current status: We're continuing to prepare our fix for an expedited deployment process that, once deployed, we expect will fix the issue for existing Copilot agents. In addition, we also rolled back the recent feature enablement change to resolve impact for newly created agents and allow for those to then be shared with users who don't have a Copilot license.
Scope of impact: This issue may impact users without a Copilot license who are trying to install agents.
Start time: Sunday, April 26, 2026, at 7:00 PM UTC
Root cause: A recent feature enablement is responsible for impact. Previously, this feature could have impacted if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature has been turned on by default for all users.
Next update by: Friday, May 22, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon May 18 18:17:39 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may be unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license can't install shared agents that were created by licensed users.
Currently impacted, licensed users can disable this feature in the Copilot Knowledge card by toggling off the "Reference org chart and profile info" setting.
Current status: We've completed development of our fix and are preparing it for deployment. We're assessing a timeline for the complete deployment of the fix and impact resolution to provide with our next scheduled communication update.
Scope of impact: This issue may impact users without a Copilot license who are trying to install agents.
Start time: Sunday, April 26, 2026, at 7:00 PM UTC
Root cause: A recent feature enablement is responsible for impact. Previously, this feature could have impacted if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature has been turned on by default for all users.
Next update by: Tuesday, May 19, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 18 17:12:05 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may be unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license can't install shared agents that were created by licensed users.
Current status: We've confirmed that a recent feature enablement is responsible for impact. Previously, this feature could have impacted if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature has been turned on by default for all users.
Currently impacted, licensed users can disable this feature in the Copilot Knowledge card by toggling off the "Reference org chart and profile info" setting. For affected, non-licensed users, who don't have access to toggle the setting off, we're working to develop a fix to fully remediate impact.
Scope of impact: This issue may impact users without a Copilot license who are trying to install agents.
Start time: Sunday, April 26, 2026, at 7:00 PM UTC
Root cause: A recent feature enablement is responsible for impact. Previously, this feature could have impacted if a user had explicitly enabled this capability before sharing with an unlicensed user, but the feature has been turned on by default for all users.
Next update by: Monday, May 18, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon May 18 14:41:35 2026 |
|---|
| Description: | Title: Users may be unable to share agents in Microsoft 365 Copilot with users without a Copilot license
User impact: Users may be unable to share agents in Copilot with users without a Copilot license.
More info: Specifically, users without a Copilot license can't install shared agents that were created by licensed users.
Current status: We're working to conduct an internal reproduction of the impact to troubleshoot whether a recent feature change may be responsible for users' inability to share agents.
Scope of impact: This issue may impact users without a Copilot license who are trying to install agents.
Next update by: Monday, May 18, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon May 18 13:46:16 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1315061 - Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Fri May 15 15:00:00 2026 |
|---|
| End Time: | Thu May 21 20:24:29 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 21 20:24:41 2026 |
|---|
| Root Cause: | A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 20:24:37 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may have been unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may have seen a blank screen when attempting to create a Copilot Notebook.
Subsequent retries to create Copilot Notebooks may succeed.
Final status: Deployment of our fix is complete, and we’ve determined from service telemetry that this issue is resolved.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may have been intermittently impacted.
Start time: Friday, May 15, 2026, at 7:00 PM UTC
End time: Friday, May 22, 2026, at 12:24 AM UTC
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
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: | Mon May 18 20:35:46 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may see a blank screen when attempting to create a Copilot Notebook.
Subsequent retries to create Copilot Notebooks may succeed.
Current status: We're further reviewing and assessing our options to determine whether we can safely expedite the release of our fix. At this time, the fix has entered the normal deployment process, and we expect it will complete by Thursday, May 21st, 2026.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 7:00 PM UTC
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Friday, May 22, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 18 18:31:42 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may see a blank screen when attempting to create a Copilot Notebook.
Subsequent retries to create Copilot Notebooks may succeed.
Current status: We estimate that the roll back of the offending service update may complete by Thursday, May 21, 2026. We're reviewing methods of expediting this rollback to safely remediate impact sooner.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted.
Start time: Friday, May 15, 2026, at 7:00 PM UTC
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Tuesday, May 19, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 18 18:31:39 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may see a blank screen when attempting to create a Copilot Notebook.
Subsequent retries to create Copilot Notebooks may succeed.
Current status: We estimate that the roll back of the offending service update may complete by Thursday, May 21, 2026. We're reviewing methods of expediting this rollback to safely remediate impact sooner.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted.
Start time: Friday, May 15, 2026, at 7:00 PM UTC
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Tuesday, May 19, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon May 18 16:48:43 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
More info: Users affected by the issue may see a blank screen when attempting to create a Copilot Notebook.
Current status: We're continuing our efforts to roll back the offending service update to remediate impact, and we aim to confirm a timeline for remediation as it becomes available.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted.
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Monday, May 18, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon May 18 15:58:10 2026 |
|---|
| Description: | Title: Users intermittently may be unable to create Copilot Notebooks through Microsoft 365 Copilot
User impact: Users intermittently may be unable to create Copilot Notebooks through Copilot.
Current status: We've determined that a recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot. We're rolling back this recent service update to remediate impact.
Scope of impact: Any user attempting to create Copilot Notebooks through Copilot may be intermittently impacted.
Root cause: A recent Copilot service update introduced a code issue resulting in users being intermittently unable to create Copilot Notebooks through Copilot.
Next update by: Monday, May 18, 2026, at 8:30 PM UTC
|
|---|
|
CW1310341 - Some users may be unable to access Microsoft 365 Copilot Chat via any connection method
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed May 13 21:40:00 2026 |
|---|
| End Time: | Thu May 14 11:30:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 21 19:14:50 2026 |
|---|
| Root Cause: | A recent configuration change to the authentication component altered how user sign in requests were processed. This introduced a mismatch in expected authentication behavior, causing authentication requests to fail. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 19:14:19 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon May 18 19:58:35 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu May 14 12:20:17 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft 365 Copilot Chat via any connection method
User impact: Users may have been unable to access Microsoft 365 Copilot Chat via any connection method.
More info: Impacted users may have experienced failed session loads, persistent errors, or unresponsive Copilot chats due to backend services being unable to initialize successfully.
Final status: We've identified and reverted a recent configuration change that altered how user sign in requests were processed. We've now confirmed that impact has been resolved.
Scope of impact: Impact was specific to users attempting to access Microsoft 365 Copilot Chat via any connection method.
Start time: Thursday, May 14, 2026, at 1:40 AM UTC
End time: Thursday, May 14, 2026, at 3:35 PM UTC
Root cause: A recent configuration change to the authentication component altered how user sign in requests were processed. This introduced a mismatch in expected authentication behavior, causing authentication requests to fail.
Next steps: We're examining our configuration change process so we can identify areas for process improvement in future deployments.
A preliminary post incident report (PIR) Will be published within 2 business days from closure, and a final PIR will be published within 5 business days from closure.
|
|---|
|
| Time: | Thu May 14 11:43:02 2026 |
|---|
| Description: | We've identified and reverted a previous configuration change that appears to have affected an authentication workflow within the service. We're now observing recovery in service telemetry.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu May 14 10:40:37 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft 365 Copilot Chat via any connection method
User impact: Users may be unable to access Microsoft 365 Copilot Chat via any connection method.
Current status: We've identified a potentially impacting IP classification dataset version, which we're preparing to revert to a version prior to the suspected impacting change window to unblock ECS access as an initial mitigation. We're monitoring service telemetry and error logs to validate this and to help identify the root cause of impact.
Scope of impact: Impact is specific to users attempting to access Microsoft 365 Copilot Chat via any connection method.
Start time: Thursday, May 14, 2026, at 12:40 AM UTC
Next update by: Thursday, May 14, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu May 14 08:48:28 2026 |
|---|
| Description: | Title: Some users may be unable to access Microsoft 365 Copilot Chat via any connection method
User impact: Users may be unable to access Microsoft 365 Copilot Chat via any connection method.
Current status: We’re reviewing service telemetry and recent service deployments to isolate the root cause of the issue and determine a fix.
Scope of impact: Impact is specific to users attempting to access Microsoft 365 Copilot Chat via any connection method.
Next update by: Thursday, May 14, 2026, at 3:00 PM UTC
|
|---|
|
MO1221364 - Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Jan 22 14:33:29 2026 |
|---|
| End Time: | Fri Jan 23 00:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu May 21 15:23:19 2026 |
|---|
| Root Cause: | We identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon May 4 19:01:32 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Apr 2 18:13:38 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Mar 4 19:08:37 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Mar 3 07:01:10 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Mar 2 19:47:19 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jan 30 07:15:30 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:39:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:11:05 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:08:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:07:54 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jan 27 07:47:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jan 26 19:58:56 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jan 23 01:27:30 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may have seen degraded service functionality or were unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions included, but were not limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may have been unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not have been honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may have failed in Universal Print.
- Microsoft To Do users may have experienced synchronization issues, preventing tasks from updating across devices. Additionally, tasks created in Shared Lists may not have appeared for collaborators.
- Microsoft Defender for Cloud Apps users may not have been able to view insights or view, create, or update OAuth enabled app policies. Reporting data may have also appeared blank, even though no errors were shown.
- Microsoft Defender for Office (MDO) users may have experienced limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection.
- Microsoft Power Automate users may have been unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Final status: We’ve confirmed that the affected infrastructure has returned to a healthy state and is operating as expected. We’ll continue to closely monitor the remediation actions taken and make any necessary adjustments to maintain stability. If users experience any residual issues, clearing local DNS caches or temporarily lowering DNS TTL values may help ensure a quicker remediation.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may have been intermittently impacted. This could have affected users located in Asia-Pacific, Europe, or Latin America.
Preliminary root cause: As part of a planned maintenance activity to improve network routing infrastructure, one of the Cheyenne datacenters was removed from active service rotation. As part of this activity, GLS at the affected Cheyenne datacenter was taken offline on Thursday, January 22, 2026, at 5:45 PM UTC. It was expected that the remaining regional GLS capacity would be sufficient to handle the redirected traffic.
Subsequent review of the incident identified that the load balancers that support the GLS service were unable to accept the redirected traffic in a timely manner causing the GLS load balancers to go into an unhealthy state. This sudden concentration of traffic led to an increase in retry activity, which further amplified the impact. Over time, these conditions triggered a cascading failure that affected dependent services, including mail flow and Domain Name System (DNS) resolution required for email delivery.
Start Time: Thursday, January 22, 2026, at 6:55 PM UTC
End Time: Friday, January 23, 2026, at 5:00 AM UTC
Next steps:
For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
This PIR was updated on a monthly cadence to show the progress of the Next Step actions, with the final update provided on May 4, 2026. As all the Next Step actions listed for this incident have been completed, this is the final version of the PIR. This is the final update for this event.
|
|---|
|
| Time: | Fri Jan 23 01:00:40 2026 |
|---|
| Description: | We’ve confirmed that service restoration is complete. If users continue to see residual issues, clearing local DNS caches or temporarily lowering DNS TTL values can help ensure updates are reflected more quickly.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Jan 23 00:31:54 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
- Microsoft To Do users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
- Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
- Microsoft Defender for Office (MDO) users may experience limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection. As basic mail flow continues to be restored, these associated experiences are expected to resume normal operation.
- Microsoft Power Automate users may be unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Current status: We’ve a high level of confidence that the incident is largely resolved. Access to Microsoft Defender for Office, Microsoft Purview, and DNS functionality has been restored, and Exchange Online mail flow remains stable.
We're continuing to fine tune load balancing adjustments and closely monitor the impact of recent changes to support sustained recovery. While recovery efforts remain ongoing, we are methodically addressing the small number of remaining affected services to ensure full service stability.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: We identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure.
Next update by: Friday, January 23, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 23:58:13 2026 |
|---|
| Description: | We’re continuing to optimize service load distribution and are seeing improved accessibility in Microsoft Purview, along with a noticeable reduction in related errors.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 23:29:38 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
- Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
- Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
- Microsoft Defender for Office (MDO) users may experience limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection. As basic mail flow continues to be restored, these associated experiences are expected to resume normal operation.
- Microsoft Power Automate users may be unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Current status: We’ve identified elevated service load combined with temporary capacity constraints during maintenance resulted in impact. We’re seeing positive signs of recovery in mail delivery, and mitigation actions are in place to better manage service load. While some connectivity impact remains between Microsoft Defender for Office, Microsoft Purview, and Exchange Online, and DNS lookup failures, engineers are actively working to restore full functionality.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: We've identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure.
Next update by: Friday, January 23, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 22:28:10 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
- Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
- Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
Current status: We’re continuing to see steady improvements in service availability for Exchange Online and Microsoft Teams and our broader recovery efforts remain actively underway. Engineers are further refining load balancing measures to accelerate recovery and are methodically addressing the remaining impacted services.
We do not yet consider this issue resolved and we remain committed to treating this issue with the highest urgency and priority. We understand how difficult it can be to operate without a confirmed estimated time to resolution. Please be assured that our teams are actively investigating and addressing the underlying causes of the impact, and we will share an estimated time for resolution as soon as one becomes available.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 21:24:44 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
- Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
- Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
Current status: We’re seeing continued improvements in service availability and functionality as a result of our load-balancing efforts. We’re actively monitoring performance and making targeted adjustments to further improve stability and availability, while continuing recovery actions to ensure a reliable service experience.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 20:57:29 2026 |
|---|
| Description: | We’re seeing notable improvements in availability and service functionality. We’ll continue to closely monitor performance and make any targeted adjustments to further enhance stability.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 20:25:39 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
-Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
Current status: We’re refining our load balancing efforts to optimize performance and reduce potential impact. In parallel, we’re assessing alternative solutions to reinforce recovery and enhance long term stability.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 19:39:45 2026 |
|---|
| Description: | We’re actively optimizing load balancing configurations to address residual imbalances and reinforce recovery efforts, while taking additional precautions to minimize the risk of further recovery related issues.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 19:00:11 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
Current status: We're continuing to refine our load balancing configurations to remedy residual imbalances across the environment and further our ongoing recovery efforts.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 18:23:12 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
Current status: During our ongoing efforts to rebalance traffic across the region, we introduced a targeted load balancing configuration change intended to expedite the recovery process, which incidentally introduced additional traffic imbalances associated with persistent impact for a portion of the affected infrastructure. We're remedying our load balancing configurations while, in parallel, reviewing the viability of expediting our ongoing incremental rebalancing and recovery efforts.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Jan 22 17:29:59 2026 |
|---|
| Description: | While we’re proceeding as quickly as possible to effectively rebalance traffic to achieve recovery, we're also recursively monitoring the extent of the affected environment to identify whether additional actions may be required. We'll provide an estimated recovery timeline as soon as we have this information.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 17:15:39 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces.
- Searching within SharePoint Online and/or Microsoft OneDrive.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not be honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may fail in Universal Print.
Current status: We're carefully rebalancing traffic across all affected infrastructure in the region, while monitoring the corresponding health telemetry, to ensure the environment enters into a balanced state as our remediation efforts continue. We’re proceeding as quickly as possible and this incremental approach will also help us identify whether any additional actions may be required to ensure longstanding recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Thursday, January 22, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Thu Jan 22 16:32:38 2026 |
|---|
| Description: | We've implemented a traffic balancing solution within a limited portion of infrastructure and telemetry shows success. We're applying this solution incrementally across all affected infrastructure to ensure the environment remains balanced as recovery continues.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 16:09:48 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users.
- Collecting message traces.
- Searching within SharePoint Online and/or Microsoft OneDrive.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams.
- Receiving presence or location information in Microsoft Teams.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
Current status: While we've restored the affected infrastructure to a healthy state, further load balancing is required to mitigate persistent impact. We've identified and are implementing additional actions to direct requests and traffic to additional healthy sections of infrastructure to achieve withstanding recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Thursday, January 22, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jan 22 15:45:18 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage.
- Collecting message traces may be delayed or fail.
- Searches within SharePoint Online and/or Microsoft OneDrive mail be delayed or fail to complete.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
Current status: We're continuing to review what actions are required to restore the affected infrastructure to a healthy state and rebalance the service traffic to achieve recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Thursday, January 22, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jan 22 15:16:08 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
Current status: We've identified a portion of dependent service infrastructure in the North America region that is not processing traffic as expected. This is impacting our load balancing processes and general service availability. We're working to restore this infrastructure to a healthy state and rebalance the service traffic to achieve recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Next update by: Thursday, January 22, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jan 22 14:57:58 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality across multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality across multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send mail through Outlook.
Some of the impacted service functions include, but may not be limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage.
- Accessing the service portals, including Microsoft Purview and Microsoft Defender XDR.
Current status: We're reviewing the reported impact scenarios and identifying what portion of the dependent service infrastructure is degraded so we can determine our next troubleshooting steps.
Scope of impact: The scope of this issue is currently being investigated.
Next update by: Thursday, January 22, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Jan 22 14:44:56 2026 |
|---|
| Description: | As we rapidly pursue an investigation into the nature of the impact and the source of the issue, we've received reports that users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to access the service portals or use Outlook.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Thu Jan 22 14:36:00 2026 |
|---|
| Description: | Title: We're investigating a potential issue affecting Microsoft 365 services
User impact: We've received reports of an issue affecting Microsoft 365 services.
Current status: We're investigating a potential issue with Microsoft 365 services and checking for impact to your organization. Initial reports indicate possible issues accessing the Microsoft Defender and Microsoft Purview portals, as well as issues using Outlook. We'll provide an update within 30 minutes.
|
|---|
|
MO1310977 - Admins may see stale or delayed report data in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 14 20:00:00 2026 |
|---|
| End Time: | Wed May 20 22:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 21 13:43:41 2026 |
|---|
| Root Cause: | A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center was performing below expected thresholds, which led to report data being stale and delayed.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 13:28:16 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may have seen stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, included the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Final status: We've confirmed that the data backlog has finished processing in all affected regions and has fully remediated impact for this issue.
Scope of impact: Any admin located in the North America, Asia-Pacific, and Europe regions who attempted to view-up-to-date report data for the listed reports in the More info section for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may have been impacted.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
End time: Thursday, May 21, 2026, at 2:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center was performing below expected thresholds, which led to report data being stale and delayed.
Next steps: - We're reviewing our automated recovery and redirection processes for the affected portions of infrastructure responsible for supporting and providing report data to the Microsoft 365 admin center in order to understand how to better detect, prevent, and respond to similar service issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 20 18:04:28 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: The backlog from Europe is taking longer than we anticipated to process, but we are making progress. We're continuing to monitor its progress and will provide an update to its progress at next communication time.
Scope of impact: Any admin located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, which is leading to report data being stale and delayed.
Next update by: Thursday, May 21, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed May 20 18:04:25 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: The backlog from Europe is taking longer than we anticipated to process, but we are making progress. We're continuing to monitor its progress and will provide an update to its progress at next communication time.
Scope of impact: Any admin located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, which is leading to report data being stale and delayed.
Next update by: Thursday, May 21, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed May 20 14:30:25 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We've completed backlog processing through May 14, 2026, for all regions. We're continuing to monitor as backlog processing continues in the final region, Europe, for the final impacted day, May 15, to confirm full resolution for all impacted admins.
Scope of impact: Any admin located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, which is leading to report data being stale and delayed.
Next update by: Wednesday, May 20, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue May 19 14:27:30 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We're continuing to monitor as the backlog of report data is processed, and we'll provide an estimated timeline for this to complete as one becomes available.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds is leading to report data being stale and delayed.
Next update by: Wednesday, May 20, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon May 18 15:20:51 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: After completing our processing of the backlog of report data for Tuesday, May 12, 2026, reports are now showing accurate data. However, we’ve since isolated a backlog of report data for Friday, May 15, 2026, which we’re now processing to address the problem in full.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, Tuesday, May 12, 2026, or Friday, May 15, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds is leading to report data being stale and delayed.
Next update by: Tuesday, May 19, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Sat May 16 12:41:43 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, or Tuesday, May 12, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We're continuing to monitor the progress of processing the backlog of report data for Tuesday, May 12, 2026, which is taking longer than anticipated to complete. Once available, we'll provide a resolution timeline.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, or Tuesday, May 12, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds is leading to report data being stale and delayed.
Next update by: Monday, May 18, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Fri May 15 21:23:34 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The affected reports for Monday, May 11, 2026, or Tuesday, May 12, 2026, include the following:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We’ve been made aware that while initially this issue affected the four listed affected data reports for Monday 11, 2026, increased traffic to the portion of infrastructure that supports and provides report data to the Microsoft 365 admin center has additionally impacted these reports for Tuesday, May 12, 2026. We’ve updated the More info and Scope of impact to align with our findings. We’ve confirmed that the backlog of report data for Monday, May 11, 2026, has completed processing in all the affected regions. We’re now processing the backlog of report data for Tuesday, May 12, 2026, and we anticipate it’ll complete by our next scheduled communications update.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions who are attempting to view-up-to-date report data for the listed reports in the More info for Monday, May 11, 2026, or Tuesday, May 12, 2026, in the Microsoft 365 admin center may be affected by this issue. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds is leading to report data being stale and delayed.
Next update by: Saturday, May 16, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri May 15 17:47:17 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The reports that may be affected include:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We've confirmed that the backlog of data has completed processing in the Asia-Pacific and North America regions. The progress through the remaining impacted region is taking longer than anticipated, and we'll provide an update timeline for full remediation as soon as one becomes available.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions may be affected by this issue and see stale or delayed report data in the Microsoft 365 admin center.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, leading to report data being stale and delayed.
Next update by: Saturday, May 16, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri May 15 16:08:31 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The reports that may be affected include:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We've confirmed that the backlog of data has completed processing in the Asia-Pacific region. We're monitoring this process as it continues through the remaining impacted environments and anticipate its completion by our next scheduled update.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions may be affected by this issue and see stale or delayed report data in the Microsoft 365 admin center.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, leading to report data being stale and delayed.
Next update by: Friday, May 15, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu May 14 23:17:43 2026 |
|---|
| Description: | Title: Admins may see stale or delayed report data in the Microsoft 365 admin center
User impact: Admins may see stale or delayed report data in the Microsoft 365 admin center.
More info: The reports that may be affected include:
- Copilot Readiness Activity
- Microsoft 365 App Usage
- Project Activity
- Visio Activity
Current status: We were alerted to an issue from our internal monitoring systems that indicated stale or delayed report data in the Microsoft 365 admin center. After investigating the service telemetry and the infrastructure that provides report data, we identified a portion of infrastructure that's performing below expected thresholds, leading to report data being stale and delayed. We deployed a fix to re-initiate and restart the portion of infrastructure and we're now monitoring its performance as it processes through the backlog of report data requests. Once the backlog has been fully processed through, impact will be fully remediated.
Scope of impact: Any admins located in the North America, Asia-Pacific, and Europe regions may be affected by this issue and see stale or delayed report data in the Microsoft 365 admin center. This section may be updated as our investigation continues.
Start time: Friday, May 15, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure that supports and provides report data to the Microsoft 365 admin center is performing below expected thresholds, leading to report data being stale and delayed.
Next update by: Friday, May 15, 2026, at 8:00 PM UTC
|
|---|
|
PL1317706 - Some users may encounter issues accessing features in the Microsoft Planner application
| Status: | serviceRestored |
|---|
| Start Time: | Thu May 21 09:19:09 2026 |
|---|
| End Time: | Thu May 21 13:17:03 2026 |
|---|
| Service: | Planner |
|---|
| Feature Group: | Planner |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 21 13:17:21 2026 |
|---|
| Root Cause: | An authorization path issue caused an increase in cache usage resulting in the service becoming unhealthy and issues accessing the Microsoft Planner application.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 13:17:16 2026 |
|---|
| Description: | Title: Some users may encounter issues accessing features in the Microsoft Planner application
User impact: Users may have encountered issues accessing features in the Microsoft Planner application.
Final status: Service-side telemetry confirms the mitigation steps taken have been successful and restored access to the Microsoft Planner application.
Scope of impact: Some users attempting to access features in the Microsoft Planner app may have been impacted.
Start time: Thursday, May 21, 2026, at 7:25 AM UTC
End time: Thursday, May 21, 2026, at 5:17 PM UTC
Root cause: An authorization path issue caused an increase in cache usage resulting in the service becoming unhealthy and issues accessing the Microsoft Planner application.
Next steps: We're continuing to investigate the root cause of the authorization path issue to help prevent future recurrences.
This is the final update for this communication.
|
|---|
|
| Time: | Thu May 21 11:01:58 2026 |
|---|
| Description: | Title: Some users may encounter issues accessing features in the Microsoft Planner application
User impact: Users may encounter issues accessing features in the Microsoft Planner application.
Current status: We’ve deployed targeted mitigation actions to reduce the impact, increasing the time between background data refreshes and extending caching durations for Microsoft Planner. Service-side telemetry shows improvements from these changes, and we continue working on additional steps to further stabilize the experience while the root cause investigation progresses.
Scope of impact: Some users attempting to access features in the Microsoft Planner app may be impacted.
Next update by: Thursday, May 21, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu May 21 09:34:15 2026 |
|---|
| Description: | Title: Some users may encounter issues accessing features in the Microsoft Planner application
User impact: Users may encounter issues accessing features in the Microsoft Planner application.
Current status: We're investigating an issue with some users that may be encountering intermittent degradation when accessing Microsoft Planner features, and analyzing service telemetry to help us identify the root cause and the next steps required to mitigate impact.
Scope of impact: Impact is specific to some users attempting to access features in the Microsoft Planner application.
Next update by: Thursday, May 21, 2026, at 3:30 PM UTC
|
|---|
|
DZ1316705 - Some admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
| Status: | serviceRestored |
|---|
| Start Time: | Wed May 20 03:30:00 2026 |
|---|
| End Time: | Thu May 21 07:30:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu May 21 09:53:06 2026 |
|---|
| Root Cause: | An authentication component misconfiguration was causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data for a 30-minute window not being ingested.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu May 21 09:41:37 2026 |
|---|
| Description: | Title: Some admins may have experienced a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
User impact: Admins may have experienced a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity.
More info: Impacted admins may have experienced a point-in-time gap of approximately 30 minutes in security telemetry data for Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the affected data wasn’t ingested.
Final status: We've successfully backfilled the gap in telemetry data from the impact window and can confirm that impact is remediated.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) may have been impacted.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
End time: Thursday, May 21, 2026, at 11:30 AM UTC
Root cause: An authentication component misconfiguration was causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data for a 30-minute window not being ingested.
Next steps: We're reviewing our configuration change procedures to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu May 21 06:41:31 2026 |
|---|
| Description: | Title: Some admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
User impact: Admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity.
More info: Impacted admins may experience a point-in-time gap of approximately 30 minutes in security telemetry data for Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the affected data wasn’t ingested.
Current status: Our efforts to backfill the telemetry data gap from the impact window is progressing. We expect impact to be fully remediated and the backfill of telemetry data to be complete by our next scheduled update.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
Root cause: An authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data for a 30-minute window not being ingested.
Next update by: Thursday, May 21, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed May 20 11:25:26 2026 |
|---|
| Description: | Title: Some admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
User impact: Admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity.
More info: Impacted admins may experience a point-in-time gap of approximately 30 minutes in security telemetry data for Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the affected data wasn’t ingested.
Current status: Our fix has restored the authentication component and data ingestion. We’re continuing to backfill the telemetry data gap from the impact window to completely remediate impact. We'll provide a timeline for complete remediation if it becomes available.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
Root cause: An authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data for a 30-minute window not being ingested.
Next update by: Thursday, May 21, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Wed May 20 09:29:06 2026 |
|---|
| Description: | Title: Some admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity
User impact: Admins may experience a gap in security telemetry data and alerts in Microsoft Defender for Endpoint and Identity.
More info: Impacted admins may experience a point-in-time gap of approximately 30 minutes in security telemetry data for Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the affected data was not ingested.
Current status: We’ve deployed the fix to restore the authentication component and data ingestion. We’re monitoring the service to confirm stability. In parallel, we’re working to backfill the telemetry data gap from the impact window. Users may continue to experience gaps in telemetry and alerting until this recovery process completes.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint and Microsoft Defender for Identity (V3 clients) may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
Root cause: An authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint and Microsoft Defender for Identity services, resulting in telemetry data not being ingested.
Next update by: Wednesday, May 20, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed May 20 07:25:31 2026 |
|---|
| Description: | Title: Some admins may experience a 30-minute gap in security telemetry and alerts in Microsoft Defender for Endpoint
User impact: Admins may experience a 30-minute gap in security telemetry and alerts in Microsoft Defender for Endpoint.
More info: Impacted admins may experience a point-in-time gap of approximately 30 minutes in Microsoft Defender for Endpoint telemetry data when viewing information in the Microsoft Defender portal and Microsoft Sentinel, as the impacted data wasn't ingested.
Current status: We’ve determined that an authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint service, resulting in telemetry data not being ingested. We’re deploying a fix to restore the authentication component and stabilize ingestion, which will allow the missing data to be re-ingested.
Scope of impact: Some admins relying on security telemetry reporting in Microsoft Defender for Endpoint may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, May 20, 2026, at 7:30 AM UTC
Root cause: An authentication component misconfiguration is causing authentication issues within a core part of the Microsoft Defender for Endpoint service, resulting in telemetry data not being ingested.
Next update by: Wednesday, May 20, 2026, at 1:30 PM UTC
|
|---|
|
IT1316808 - Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 19 16:00:00 2026 |
|---|
| End Time: | Wed May 20 21:50:50 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 20 21:50:58 2026 |
|---|
| Root Cause: | A code issue was introduced with the Android 17 QRP1 beta 3 version which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 20 21:50:55 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may have crashed if launched on an Android device with the Android 17 QRP1 beta 3 update.
Final status: We've completed releasing the fix in the Microsoft Intune Company Portal beta build version 5.0.6983.0 (8193764). Users will need to enroll in the Google Play beta program to opt into the fix, which can be done by navigating to the following link: https://aka.ms/cpdroidbeta.
Scope of impact: Any user that attempted to access MAM apps launched on an Android device with the Android 17 QRP1 beta 3 update was impacted.
Start time: Tuesday, May 19, 2026, at 8:00 PM UTC
End time: Thursday, May 21, 2026, at 1:50 AM UTC
Root cause: A code issue was introduced with the Android 17 QRP1 beta 3 version which resulted in impact.
Next steps:
- We're further reviewing the impacted Android 17 QRP1 beta 3 version to understand how the code issue was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|---|
|
| Time: | Wed May 20 20:27:20 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update.
More info: We recommend that users don't update their Android devices with the Android 17 QRP1 beta 3 update.
Current status: We've completed the development of our code fix and are preparing it for deployment to all affected environments as part of a new build version of the Microsoft Intune Company Portal beta. We anticipate this deployment may complete by our next scheduled update.
Scope of impact: Any user attempting to access MAM apps launched on an Android device with the Android 17 QRP1 beta 3 update is impacted. This section may be updated as our investigation continues.
Start time: Tuesday, May 19, 2026, at 8:00 PM UTC
Root cause: A code issue was introduced with the Android 17 QRP1 beta 3 version, resulting in impact.
Next update by: Thursday, May 21, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Wed May 20 15:52:39 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update.
More info: We recommend that users don't update their Android devices with the Android 17 QRP1 beta 3 update.
Current status: We've created and reviewed the internal reproduction of impact and identified that a code issue was introduced with the recent Android 17 QRP1 beta 3 version, resulting in impact. We're developing a fix to address the code issue, which we’ll deploy in a new build version of the Microsoft Intune Company Portal beta. We anticipate the development process for our fix will complete by our next scheduled communications update, at which point we'll look to confirm a timeline for its full deployment.
Scope of impact: Any user attempting to access MAM apps launched on an Android device with the Android 17 QRP1 beta 3 update is impacted.
Root cause: A code issue was introduced with the Android 17 QRP1 beta 3 version, resulting in impact.
Next update by: Thursday, May 21, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed May 20 12:40:37 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update.
More info: We recommend that users don't update their Android devices with the Android 17 QRP1 beta 3 update.
Current status: We're creating an internal reproduction of this event to facilitate our understanding of the root cause and development of a strategy that remediates impact. In parallel, we're working with a third-party partner to aid this process.
Scope of impact: Any user attempting to access MAM apps launched on an Android device with the Android 17 QRP1 beta 3 update is impacted.
Next update by: Wednesday, May 20, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed May 20 12:14:26 2026 |
|---|
| Description: | Title: Users’ mobile application management (MAM) apps may crash if launched on devices running Android 17 QRP1 beta 3
User impact: Users’ MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update.
More info: We recommend that users don't update their Android devices with the Android 17 QRP1 beta 3 update.
Current status: We're investigating a potential issue with users MAM apps may crash if launched on an Android device with the Android 17 QRP1 beta 3 update, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1315951 - Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
| Status: | serviceRestored |
|---|
| Start Time: | Tue Dec 23 12:50:00 2025 |
|---|
| End Time: | Tue May 19 18:13:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 20 15:40:58 2026 |
|---|
| Root Cause: | A recent service update removed the logic that records the IP address information in the audit logs for Copilot interactions, which resulted in impact.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 20 15:40:23 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may have been unable to see IP address information in the audit logs for Copilot interactions.
Final status: We've validated with a subset of affected users that impact has been successfully remediated following our roll back of the offending service update which introduced impact.
Scope of impact: Any admin looking for the IP address information in the audit logs for Copilot interactions may have been impacted.
Start time: Tuesday, December 23, 2025, at 5:50 PM UTC
End time: Tuesday, May 19, 2026, at 10:13 PM UTC
Root cause: A recent service update removed the logic that records the IP address information in the audit logs for Copilot interactions, which resulted in impact.
Next steps:
- We're reviewing our service update validation and implementation processes to improve how we detect potential IP address information logic removal issues and prevent similar service events from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue May 19 23:45:01 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may be unable to see IP address information in the audit logs for Copilot interactions.
Current status: We've reverted the recent service update which removed the logic that records the IP information in the audit logs for Copilot interactions and we’re reaching out to a subset of affected users to validate that impact has been remediated.
Scope of impact: Any admin looking for the IP address information in the audit logs for Copilot interactions is impacted. This section may be updated as our investigation progresses.
Root cause: A recent service update removed the logic that records the IP information in the audit logs for Copilot interactions.
Next update by: Wednesday, May 20, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue May 19 16:35:26 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may be unable to see IP address information in the audit logs for Copilot interactions.
Current status: We've determined that a recent service update mistakenly removed the logic that records the IP information in the audit logs for Copilot interactions. We're reverting this change to remediate impact and we'll provide an estimated time for completion if one becomes available.
Scope of impact: Any admin looking for the IP address information in the audit logs for Copilot interactions is impacted. This section may be updated as our investigation progresses.
Root cause: A recent service update removed the logic that records the IP information in the audit logs for Copilot interactions.
Next update by: Wednesday, May 20, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Tue May 19 15:33:12 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may be unable to see IP address information in the audit logs for Copilot interactions.
Current status: We're reviewing the impacted Copilot audit logs to determine why they don't contain the IP address information for Copilot interactions.
Scope of impact: Any admin looking for the IP address information in the audit logs for Copilot interactions is impacted. This section may be updated as our investigation progresses.
Next update by: Tuesday, May 19, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue May 19 14:50:02 2026 |
|---|
| Description: | Title: Admins may be unable to see IP address information in the audit logs for Microsoft Copilot (Microsoft 365) interactions
User impact: Admins may be unable to see IP address information in the audit logs for Copilot interactions.
Current status: We're investigating a potential issue with Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1316208 - Users may have experienced delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
| Status: | serviceRestored |
|---|
| Start Time: | Tue May 19 13:40:00 2026 |
|---|
| End Time: | Tue May 19 21:20:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Cloud Apps |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed May 20 03:48:44 2026 |
|---|
| Root Cause: | A recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing.
|
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed May 20 03:21:17 2026 |
|---|
| Description: | Title: Users may have experienced delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
User impact: Users may have experienced delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts.
More info: Affected users may have experienced delays of up to two hours for any of the following activities and alerts:
- Anomaly detection triggering alerts
- Activity policy triggering alerts
- Advanced hunting activities
- Activities accessed within the user interface (UI)
- CloudAppEvents in Microsoft Sentinel
Additionally, users may have seen inaccurate results for custom detections within Microsoft Sentinel.
Final status: We’ve successfully processed the backlogged data of delayed activities and alerts in Microsoft Defender for Cloud Apps and confirmed that impact has been remediated.
Scope of impact: Impact was specific to any user attempting to utilize the activities and alerts in Microsoft Defender for Cloud Apps mentioned in the More info section of this communication.
Start time: Tuesday, May 19, 2026, at 5:40 PM UTC
End time: Wednesday, May 20, 2026, at 1:20 AM UTC
Root cause: A recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing.
Next steps:
- We're reviewing our configuration change procedures to help prevent this problem from happening again.
This is the final update for this event.
|
|---|
|
| Time: | Tue May 19 19:50:37 2026 |
|---|
| Description: | Title: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
User impact: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts.
More info: Affected users may experience delays of up to two hours for any of the following activities and alerts:
- Anomaly detection triggering alerts
- Activity policy triggering alerts
- Advanced hunting activities
- Activities accessed within the user interface (UI)
- CloudAppEvents in Microsoft Sentinel
Additionally, users may see inaccurate results for custom detections within Microsoft Sentinel.
Current status: We've completed reverting the offending configuration change, and we're monitoring as the backlogged data of delayed activities and alerts in Microsoft Defender for Cloud Apps are being processed. We expect this will be complete and the issue fully mitigated by our next scheduled update.
Scope of impact: This impacts any user attempting to utilize the aforementioned activities and alerts in Microsoft Defender for Cloud Apps.
Root cause: A recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing.
Next update by: Wednesday, May 20, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Tue May 19 18:04:11 2026 |
|---|
| Description: | Title: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
User impact: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts.
More info: Affected users may experience delays of up to two hours for any of the following activities and alerts:
- Anomaly detection triggering alerts
- Activity policy triggering alerts
- Advanced hunting activities
- Activities accessed within the user interface (UI)
- CloudAppEvents in Microsoft Sentinel
Additionally, users may see inaccurate results for custom detections within Microsoft Sentinel.
Current status: We've identified that a recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing. We're reverting this configuration change to remediate impact.
Scope of impact: This impacts any user attempting to utilize the aforementioned activities and alerts in Microsoft Defender for Cloud Apps.
Root cause: A recent configuration change enabled an authentication feature that revealed a regression, resulting in authentication failures preventing Microsoft Defender for Cloud Apps activities and alerts from completing.
Next update by: Wednesday, May 20, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue May 19 17:35:18 2026 |
|---|
| Description: | Title: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts
User impact: Users may experience delays of up to two hours for some Microsoft Defender for Cloud Apps activities and alerts.
More info: Affected users may experience delays of up to two hours for any of the following activities and alerts:
- Anomaly detection triggering alerts
- Activity policy triggering alerts
- Advanced hunting activities
- Activities accessed within the user interface (UI)
- CloudAppEvents in Microsoft Sentinel
Additionally, users may see inaccurate results for custom detections within Microsoft Sentinel.
Current status: We're investigating a potential issue with Microsoft Defender for Cloud Apps and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
|
