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 Sun Feb 15 11:15:07 2026.
MP1232157 - Some admins see delays in Data Security Posture Management (DSPM) metrics and asset information within Microsoft
| Status: | falsePositive |
|---|
| Start Time: | Thu Jan 15 19:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sun Feb 15 00:29:25 2026 |
|---|
| Root Cause: | The infrastructure supporting DSPM metrics and asset information is performing in a suboptimal state due to elevated load and capacity constraints, resulting in impact. |
|---|
| Next Update: | Sunday, February 15, 2026, at 9:00 PM UTC |
|---|
|
Details
| Time: | Sat Feb 14 19:11:24 2026 |
|---|
| Description: | Title: Some admins see delays in Data Security Posture Management (DSPM) metrics and asset information within Microsoft
User impact: Admins see delays in new or modified assets being reflected in DSPM within Microsoft Purview.
More info: More specifically, admins see delays for the following impacted assets:
- Key posture metric for Classified or labeled assets
- Data snapshot (Stale and Fresh data trends)
- Asset explorer
- Posture metrics, sensitive data discovery trends, and risk patterns in the Discover sensitive data in your organization objective
Current status: We’re continuing our aforementioned remediation efforts in tandem with further attempting to attain a remediation timeline to provide by our next scheduled update. Additionally, affected admins will experience remediation gradually as our mitigation efforts progress.
Scope of impact: Your organization is affected by this event, and any admins attempting to view new or modified assets in DSPM within Microsoft Purview are impacted. This information may be updated as our investigation continues.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: The infrastructure supporting DSPM metrics and asset information is performing in a suboptimal state due to elevated load and capacity constraints, resulting in impact.
Next update by: Sunday, February 15, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Sat Feb 14 15:28:31 2026 |
|---|
| Description: | Title: Some admins see delays in Data Security Posture Management (DSPM) metrics and asset information within Microsoft Purview
User impact: Admins see delays in new or modified assets being reflected in DSPM within Microsoft Purview.
More info: More specifically, admins see delays for the following impacted assets:
- Key posture metric for Classified or labeled assets
- Data snapshot (Stale and Fresh data trends)
- Asset explorer
- Posture metrics, sensitive data discovery trends, and risk patterns in the Discover sensitive data in your organization objective
Current status: We've completed our review of the processing delays and identified that the infrastructure supporting DSPM metrics and asset information is performing in a suboptimal state due to elevated load and capacity constraints, resulting in impact. We're incrementally increasing processing capacity on the affected infrastructure, which we've confirmed through internal testing recovers the infrastructure and restores functionality. We've increased processing capacity for a portion of the supporting infrastructure, and affected admins will experience remediation gradually as our mitigation efforts progress. We'll aim to provide a timeline for all of the affected infrastructure to be recovered by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and any admins attempting to view new or modified assets in DSPM within Microsoft Purview are impacted. This information may be updated as our investigation continues.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: The infrastructure supporting DSPM metrics and asset information is performing in a suboptimal state due to elevated load and capacity constraints, resulting in impact.
Next update by: Sunday, February 15, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Sat Feb 14 01:25:00 2026 |
|---|
| Description: | Title: Some admins see delays in Data Security Posture Management (DSPM) metrics and asset information within Microsoft Purview
User impact: Admins see delays in new or modified assets being reflected in DSPM within Microsoft Purview.
More info: More specifically, admins see delays for the following impacted assets:
- Key posture metric for Classified or labeled assets
- Data snapshot (Stale and Fresh data trends)
- Asset explorer
- Posture metrics, sensitive data discovery trends, and risk patterns in the Discover sensitive data in your organization objective
Current status: Our system monitoring has alerted us to an issue in which some admins are seeing delays in new or modified assets in DSPM within Microsoft Purview. We're investigating the processing delays for the affected assets so that we can identify the root cause of the issue and develop a remediation plan.
Scope of impact: Your organization is affected by this event, and any admins attempting to view new or modified assets in DSPM within Microsoft Purview are impacted. This information may be updated as our investigation continues.
Next update by: Saturday, February 14, 2026, at 9:00 PM UTC
|
|---|
|
EX1232513 - Some admins may be unable to perform tenant to tenant migrations and offboarding moves in Exchange Online
| Status: | serviceDegradation |
|---|
| Start Time: | Sat Feb 14 20:44:21 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Feb 14 20:47:25 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Tuesday, February 17, 2026, at 10:00 PM UTC |
|---|
|
Details
| Time: | Sat Feb 14 20:47:25 2026 |
|---|
| Description: | Title: Some admins may be unable to perform tenant to tenant migrations and offboarding moves in Exchange Online
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in Exchange Online.
More info: While we work on developing a long-term solution, admins may use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
The tenant admin may then resume the move request (Resume-MoveRequest "user@yourdomain.com") or simply resume the migration batch. This will allow the affected move jobs to continue to make progress.
Current status: We've been made aware of an issue in which some admins may be unable to perform tenant to tenant migrations and offboarding moves in Exchange Online. We're reviewing backend settings and recent changes to identify the root cause and develop a long-term solution. In the meantime, admins can follow the steps listed in the More Info section of this communication to bypass the impact scenario.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in Exchange Online may be affected. This information may be updated as our investigation continues.
Next update by: Tuesday, February 17, 2026, at 10:00 PM UTC
|
|---|
|
MO1231021 - Some users may be unable to access or see Excel data in multiple Microsoft 365 services on the web
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 29 11:00:00 2026 |
|---|
| End Time: | Fri Feb 13 19:30:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 13 21:58:32 2026 |
|---|
| Root Cause: | A recent deployment in Excel introduced a compatibility issue with multiple Microsoft 365 services that prevented the data from being populated on the web. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 13 21:44:49 2026 |
|---|
| Description: | Title: Some users may be unable to access or see Excel data in multiple Microsoft 365 services on the web
User impact: Users may have been unable to access or see Excel data in multiple Microsoft 365 services on the web.
More info: Specific Microsoft 365 services affected were Power BI and SharePoint Online, though any Microsoft 365 service that utilized Excel web access may have been impacted.
The impact scenario for Power BI was that some users may have been unable to view data when they opened imported Excel workbooks in Power BI workspaces. To avoid this issue, users could’ve seen the data when they utilized workbooks in Excel or Excel for the web.
The impact scenario for SharePoint Online was that some users may have been unable to access or view Excel content on SharePoint Online sites because the content was blank and greyed out. To avoid this issue, users could’ve opened the Excel file directly without using web parts.
Final status: We’ve successfully deployed our fix to address this issue and confirmed in our testing environment that this issue is resolved.
Scope of impact: Some users who attempted to view or access Excel data in multiple Microsoft 365 services on the web may have been unable to do so.
Start time: Thursday, January 29, 2026, at 4:00 PM UTC
End time: Saturday, February 14, 2026, at 12:30 AM UTC
Root cause: A recent deployment in Excel introduced a compatibility issue with multiple Microsoft 365 services that prevented the data from being populated on the web.
Next steps:
- We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 12 16:49:17 2026 |
|---|
| Description: | Title: Some users may be unable to access or see Excel data in multiple Microsoft 365 services on the web
User impact: Users may be unable to access or see Excel data in multiple Microsoft 365 services on the web.
More info: Specific Microsoft 365 services affected are Power BI and SharePoint Online, though any Microsoft 365 service that uses Excel web access may be impacted.
The impact scenario for Power BI is that some users may be unable to view data when opening imported Excel workbooks in Power BI workspaces. To avoid this issue, users can see the data when opening workbooks in Excel or Excel for the web.
The impact scenario for SharePoint Online is that some users may be unable to access or view Excel content on SharePoint Online sites because the content is blank and greyed out. To avoid this issue, users can open the Excel file directly without using web parts.
Current status: Our additional analysis into the compatibility issues that were introduced by the recent change has determined that a fix deployment will be required to remove it and remediate the impact. We're developing a fix and expect that an estimated timeline for the deployment will be available after our internal validations have confirmed it will remediate the impact.
Scope of impact: Some users attempting to view or access or see Excel data in multiple Microsoft 365 services on the web may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 29, 2026, at 4:00 PM UTC
Root cause: A recent deployment in Excel introduced a compatibility issue with multiple Microsoft 365 services that's preventing the data from populating on the web.
Next update by: Wednesday, February 18, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Feb 12 00:55:49 2026 |
|---|
| Description: | Title: Some users may be unable to access or see Excel data in multiple Microsoft 365 services on the web
User impact: Users may be unable to access or see Excel data in multiple Microsoft 365 services on the web.
More info: Specific Microsoft 365 services affected are Power BI and SharePoint Online, though any Microsoft 365 service that uses Excel web access may be impacted.
The impact scenario for Power BI is that some users may be unable to view data when opening imported Excel workbooks in Power BI workspaces. To avoid this issue, users can see the data when opening workbooks in Excel or Excel Online.
The impact scenario for SharePoint Online is that some users may be unable to access or view Excel content on SharePoint Online sites because the content is blank and greyed out. To avoid this issue, users can open the Excel file directly without using web parts.
Current status: We've received reports of an issue in which some users may be unable to access or see Excel data in multiple Microsoft 365 services on the web. We've identified a recent deployment in Excel introduced a compatibility issue with multiple Microsoft 365 services that's preventing the data from populating on the web. We're further reviewing the recent deployment to identify an efficient remediation plan. We anticipate being able to provide details on the proposed fix by our next scheduled update.
Scope of impact: Some users attempting to view or access or see Excel data in multiple Microsoft 365 services on the web may be impacted. This information may be updated as our investigation continues.
Root cause: A recent deployment in Excel introduced a compatibility issue with multiple Microsoft 365 services that's preventing the data from populating on the web.
Next update by: Thursday, February 12, 2026, at 10:00 PM UTC
|
|---|
|
PB1232111 - Users may see incorrect results with certain queries when using result set caching in Microsoft Fabric
| Status: | serviceDegradation |
|---|
| Start Time: | Sun Jun 15 20:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 13 21:37:53 2026 |
|---|
| Root Cause: | A code issue with the result set caching feature in Microsoft Fabric is causing incorrect results with certain queries in Fabric Data Warehouse and Lakehouse SQL Analytics Endpoint. |
|---|
| Next Update: | Tuesday, February 17, 2026, at 9:00 PM UTC |
|---|
|
Details
| Time: | Fri Feb 13 21:37:53 2026 |
|---|
| Description: | Title: Users may see incorrect results with certain queries when using result set caching in Microsoft Fabric
User impact: Users may see incorrect results with certain queries when using result set caching in Microsoft Fabric.
More info: This issue may specifically impact results with the queries in Fabric Data Warehouse and Lakehouse SQL Analytics Endpoint.
While we're focused on remediation, users can disable result set caching in Fabric Data Warehouse and Lakehouse SQL Analytics Endpoint.
Current status: We identified a code issue with the result set caching feature in Microsoft Fabric that is causing incorrect results with certain queries in Fabric Data Warehouse and Lakehouse SQL Analytics Endpoint. We're implementing a fix to disable the result set caching feature to remediate the impact. We anticipate that the fix will complete by the next scheduled update time.
Scope of impact: This issue may potentially impact any user utilizing result set caching in Microsoft Fabric.
Start time: Monday, June 16, 2025, at 12:00 AM UTC
Root cause: A code issue with the result set caching feature in Microsoft Fabric is causing incorrect results with certain queries in Fabric Data Warehouse and Lakehouse SQL Analytics Endpoint.
Next update by: Tuesday, February 17, 2026, at 9:00 PM UTC
|
|---|
|
TM1230627 - Some users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Feb 11 03:34:00 2026 |
|---|
| End Time: | Wed Feb 11 09:44:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Feb 13 18:35:55 2026 |
|---|
| Root Cause: | A change within a recent service deployment resulted in traffic balancing irregularities and caused impact during a peak in traffic across the affected region. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 13 18:35:55 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Feb 11 11:50:01 2026 |
|---|
| Description: | Title: Some users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams
User impact: Users received error messages when attempting to open, set, or delete assignments in Microsoft Teams.
Final status: Our investigation into the root cause has isolated a change within the rolled back deployment which we suspect resulted in traffic balancing irregularities and caused impact during a peak in traffic across the affected region. Our persistent monitoring has validated that the impact is remediated subsequent to the completion of the rollback.
Scope of impact: Any user in your organization served by affected sections of infrastructure across the West Europe and United Kingdom regions may have been impacted when using the assignments app in Microsoft Teams.
Start time: Wednesday, February 11, 2026, at 8:34 AM UTC
End time: Wednesday, February 11, 2026, at 2:44 PM UTC
Root cause: A change within a recent service deployment resulted in traffic balancing irregularities and caused impact during a peak in traffic across the affected region.
Next steps:
- We're closely reviewing our service deployment testing, validation, and release processes to identify necessary refinements to help us identify and respond to similar issues prior to implementation within the active service environment.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Wed Feb 11 10:37:13 2026 |
|---|
| Description: | Although the rollback to the previous known good version is still in progress, our telemetry signals indicate that the service has been restored in parallel. We're carefully reviewing the service landscape and the recent changes to determine whether any additional actions are required and ensure the impact doesn't recur or expand to additional regions.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 11 10:12:38 2026 |
|---|
| Description: | Title: Some users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams
User impact: Users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams.
Current status: As the rollback nears completion, we’re beginning to validate its effectiveness at resolving the issue. We’re monitoring error rates which have significantly reduced while we continue our investigation into the root cause.
Scope of impact: This issue may affect any user within your organization using the assignments app in Microsoft Teams.
Our investigation indicates that the following region(s) are impacted by this issue: United Kingdom, Europe. Users in other locations may be impacted if hosted within these regions. This information may be updated as our investigation continues.
Start time: Wednesday, February 11, 2026, at 9:00 AM UTC
Next update by: Wednesday, February 11, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Feb 11 09:28:42 2026 |
|---|
| Description: | The rollback is progressing as expected, and we’re beginning to validate its effectiveness.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 11 08:59:07 2026 |
|---|
| Description: | Title: Some users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams
User impact: Users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams.
Current status: We’ve initiated the rollback and are closely monitoring service telemetry to ensure it is completes as expected. We anticipate this rollback will be finished by our next update time.
Scope of impact: This issue may affect any user within your organization using the assignments app in Microsoft Teams.
Our investigation indicates that the following region(s) are impacted by this issue: United Kingdom, Europe. Users in other locations may be impacted if hosted within these regions. This information may be updated as our investigation continues.
Start time: Wednesday, February 11, 2026, at 9:00 AM UTC
Next update by: Wednesday, February 11, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Feb 11 08:28:36 2026 |
|---|
| Description: | As the deployment is taking longer than anticipated, we’ve suspended its progress and are preparing to revert to the most recent healthy version to expedite mitigation efforts. Following the initiation of this process, we will work to establish an estimated time of completion.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 11 07:59:50 2026 |
|---|
| Description: | Title: Some users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams
User impact: Users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams.
Current status: The deployment of the change is currently ongoing, and we're continuing to monitor it's progress. Additionally, we're still investigating alternative methods of resolution, in the event the deployment does not produce the expected relief.
Scope of impact: This issue may affect any user within your organization using the assignments app in Microsoft Teams.
Our investigation indicates that the following region(s) are impacted by this issue: United Kingdom, Europe and North America. This information may be updated as our investigation continues.
Start time: Wednesday, February 11, 2026, at 9:00 AM UTC
Next update by: Wednesday, February 11, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Feb 11 07:01:29 2026 |
|---|
| Description: | The deployment is progressing as expected. While we’re monitoring it’s progress, we’re reviewing if additional actions are required to achieve recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 11 06:29:14 2026 |
|---|
| Description: | Title: Some users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams
User impact: Users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams.
Current status: We've started to redeploy the change and are closely monitoring it's progress and service telemetry to ensure it resolves the issue. We anticipate the deployment will be complete by our next update time.
Scope of impact: This issue may affect any user within your organization using the assignments app in Microsoft Teams.
Our investigation indicates that the following region(s) are impacted by this issue: United Kingdom, Europe and North America. This information may be updated as our investigation continues.
Start time: Wednesday, February 11, 2026, at 9:00 AM UTC
Next update by: Wednesday, February 11, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Feb 11 05:39:58 2026 |
|---|
| Description: | We’ve identified a recent change did not complete as expected and may have resulted in impact. We’re redeploying this change while we continue our investigation.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Feb 11 05:12:59 2026 |
|---|
| Description: | Title: Some users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams
User impact: Users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams.
Current status: While we continue to analyze service telemetry to determine the source of the issue, we’re reviewing if any recent changes may have resulted in impact.
Scope of impact: This issue may affect any user within your organization using the assignments app in Microsoft Teams.
Our investigation indicates that the following region(s) are impacted by this issue: United Kingdom, Europe and North America. This information may be updated as our investigation continues.
Next update by: Wednesday, February 11, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Feb 11 04:48:43 2026 |
|---|
| Description: | Title: Some users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams
User impact: Users receive error messages when attempting to open, set, or delete assignments in Microsoft Teams.
Current status: We're reviewing support provided information and service telemetry to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users attempting to open, set, or delete assignments in Microsoft Teams.
Next update by: Wednesday, February 11, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Feb 11 04:23:35 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.
|
|---|
|
CP1231765 - Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 13 08:26:51 2026 |
|---|
| End Time: | Fri Feb 13 16:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Feb 13 16:19:54 2026 |
|---|
| Root Cause: | As a result of a configuration issue, a portion of infrastructure responsible for Copilot access became stalled, which caused timeouts and failures when accessing Copilot. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 13 16:19:54 2026 |
|---|
| Description: | Title: Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
User impact: Users may have experienced failures or timeouts while accessing Copilot.
Final status: After a period of extended monitoring and targeted restarts, we’ve validated that the service has been restored.
Scope of impact: Impact was largely to users and organizations located in Europe, though users in other regions may have experienced impact as well.
Start time: Thursday, February 12, 2026, at 7:17 PM UTC
End time: Friday, February 13, 2026, at 9:00 PM UTC
Preliminary root cause: As a result of a configuration issue, a portion of infrastructure responsible for Copilot access became stalled, which caused timeouts and failures when accessing Copilot.
Next Steps
- We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Fri Feb 13 15:22:05 2026 |
|---|
| Description: | Title: Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
User impact: Users may experience failures or timeouts while accessing Copilot.
Current status: We’re making incremental improvements to service availability for the small portion of users that continue to experience impact. Our work to complete the remaining targeted restarts is progressing successfully.
Scope of impact: Impact is largely to users and organizations located in Europe, though users in other regions may experience impact as well.
Start time: Thursday, February 12, 2026, at 7:17 PM UTC
Root cause: As a result of a configuration issue, a portion of infrastructure responsible for Copilot access became stalled, which caused timeouts and failures when accessing Copilot.
Next update by: Saturday, February 14, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Feb 13 13:28:56 2026 |
|---|
| Description: | Title: Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
User impact: Users may experience failures or timeouts while accessing Copilot.
Current status: The remaining targeted restarts are proceeding as expected. The vast majority of impact has been mitigated; however, we’re monitoring the service and are prepared to take additional action as needed while the final restarts progress.
Scope of impact: Impact is largely to users and organizations located in Europe, though users in other regions may experience impact as well.
Start time: Thursday, February 12, 2026, at 7:17 PM UTC
Next update by: Friday, February 13, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Feb 13 12:41:30 2026 |
|---|
| Description: | This quick update is designed to give the latest information on this issue.
We’ve observed that the impact has largely recovered. We’re continuing to perform targeted restarts to ensure full service restoration.
|
|---|
|
| Time: | Fri Feb 13 10:31:00 2026 |
|---|
| Description: | Title: Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
User impact: Users may experience failures or timeouts while accessing Copilot.
Current Status: Restarting the affected infrastructure is providing relief, and the majority of customers are now experiencing mitigation. While we continue to resolve the underlying issue, we are actively monitoring the service until the issue is fully resolved.
If there is a significant change in user impact, we will update this communication.
Scope of impact: Impact is specific to users located in Europe attempting to access Copilot.
Next update by: Friday, February 13, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Feb 13 10:02:00 2026 |
|---|
| Description: | This quick update is designed to give the latest information on this issue.
We’re continuing to restart the affected components and observing reduced user impact. We will continue to apply the controlled recovery steps and monitor service availability.
|
|---|
|
| Time: | Fri Feb 13 09:22:07 2026 |
|---|
| Description: | Title: Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
User impact: Users may experience failures or timeouts while accessing Copilot.
Current status: We’ve identified an underlying service issue affecting a subset of infrastructure components. We’ve confirmed a remediation plan and are restarting the affected components to restore full service capacity.
Scope of impact: Impact is specific to users located in Europe attempting to access Copilot.
Next update by: Friday, February 13, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Feb 13 08:28:30 2026 |
|---|
| Description: | Title: Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
User impact: Users may experience failures or timeouts while accessing Copilot.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Impact is specific to users located in Europe attempting to access Copilot.
Next update by: Friday, February 13, 2026, at 3:30 PM UTC
|
|---|
|
TM1231009 - Users may be unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Feb 12 00:09:26 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Feb 13 16:05:45 2026 |
|---|
| Root Cause: | A recent update to the services that handle Teams meeting titles contains an error that is improperly handling the URLs, resulting in impact. |
|---|
| Next Update: | Tuesday, February 17, 2026, at 11:00 PM UTC |
|---|
|
Details
| Time: | Fri Feb 13 16:05:45 2026 |
|---|
| Description: | Title: Users may be unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat
User impact: Users may be unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat.
More info: While we're focused on remediation, users may be able to join meetings through meeting URLs.
Current status: We're continuing to monitor the deployment of our fix to address this impact and anticipate that it will fully saturate the affected environment by our next scheduled update.
Scope of impact: This issue may potentially impact any user attempting to join affected meetings through the "Join" button in the meeting chat. This information may be updated as our investigation continues.
Start time: Friday, February 6, 2026, at 12:00 PM UTC
Root cause: A recent update to the services that handle Teams meeting titles contains an error that is improperly handling the URLs, resulting in impact.
Next update by: Tuesday, February 17, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Feb 12 13:11:53 2026 |
|---|
| Description: | Title: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat
User impact: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat.
More info: While we're focused on remediation, users may be able to join meetings through meeting URLs.
Current status: Our investigation has identified that a recent update to the services that handle Teams meeting titles contains an error that is improperly handling the URLs, resulting in impact. We've developed a fix and are in the process of validating it before release. We expect to have a deployment timeline by the next scheduled update.
Scope of impact: This issue may potentially impact any user attempting to join affected meetings through the "Join" button in the meeting chat. This information may be updated as our investigation continues.
Start time: Friday, February 6, 2026, at 12:00 PM UTC
Root cause: A recent update to the services that handle Teams meeting titles contains an error that is improperly handling the URLs, resulting in impact.
Next update by: Friday, February 13, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Feb 12 07:16:05 2026 |
|---|
| Description: | Title: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat
User impact: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat.
More info: While we're focused on remediation, users may be able to join meetings through meeting URLs.
Current status: We've successfully reproduced the issue in a test environment. We're working to develop a possible fix, and to identify the underlying root cause of impact.
Scope of impact: This issue may potentially impact any user attempting to join affected meetings through the "Join" button in the meeting chat. This information may be updated as our investigation continues.
Next update by: Thursday, February 12, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Feb 12 02:20:03 2026 |
|---|
| Description: | Title: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat
User impact: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat.
More info: While we're focused on remediation, users may be able to join meetings through meeting URLs.
Current status: We collected reproduction logs of the issue and are analyzing them to understand the source of the issue and determine our next troubleshooting steps.
Scope of impact: This issue may potentially impact any user attempting to join affected meetings through the "Join" button in the meeting chat. This information may be updated as our investigation continues.
Next update by: Thursday, February 12, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Feb 12 01:45:32 2026 |
|---|
| Description: | Title: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat
User impact: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat.
More info: While we're focused on remediation, users may be able to join meetings through meeting URLs.
Current status: We're working to reproduce the issue in a test environment, which will help to determine what is causing the errors to occur when joining meetings from the meeting chat.
Scope of impact: This issue may potentially impact any user attempting to join affected meetings through the "Join" button in the meeting chat. This information may be updated as our investigation continues.
Next update by: Thursday, February 12, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Thu Feb 12 00:29:13 2026 |
|---|
| Description: | Title: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat
User impact: Users are unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat.
More info: While we're focused on remediation, users may be able to join meetings through meeting URLs.
Current status: We're analyzing the provided logs to help identify the source of the meeting join issues, which will help us determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and the issue may impact any user attempting to affected meetings.
Next update by: Thursday, February 12, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Feb 12 00:10:09 2026 |
|---|
| Description: | Title: Users are unable to join a specific Microsoft Teams meeting through the "Join" button in the meeting chat
User impact: Users are unable to join a specific Microsoft Teams meeting through the "Join" button in the meeting chat.
More info: While we're focused on remediation, users may be able to join the meeting through the meeting URL.
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.
|
|---|
|
PB1226924 - Admins may be missing Microsoft 365 Usage Analytics reports in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Wed Dec 31 19:00:00 2025 |
|---|
| End Time: | Fri Feb 13 12:25:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 13 16:05:16 2026 |
|---|
| Root Cause: | A subset of Power BI logic didn't have the expected date formatting required for the year 2026, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 13 14:52:55 2026 |
|---|
| Description: | Title: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI
User impact: Admins may have been missing Microsoft 365 Usage Analytics reports in Power BI.
More info: Admins could access the missing data through the Microsoft 365 admin center or by leveraging the Graph API.
We recommend affected admins follow these steps to update to the latest app version of Microsoft 365 Usage Analytics, which contains the fix for this issue:
1. Follow the link to the Microsoft 365 Usage Analytics V15 App: https://app.powerbi.com/Redirect?action=InstallApp&appId=5954cb3f-35a2-494c-a7af-adbb9229069f&packageKey=11c1513a-ba16-45c9-9077-cc5f79a6c9d8eReAKIjns3tbhr-POllSDcCeCtjCengXhfHpQMMFJmY&ownerId=72f988bf-86f1-41af-91ab-2d7cd011db47&buildVersion=15
2. Install the app using the desired method.
(Use "Update the workspace and the app" option to overwrite the broken version, or use "Install another copy" if you would like to keep a copy)
3. Once the app is installed, go to the workspace. It will show sample data at first load. Select "Connect your data" from the yellow banner to connect your tenant's data.
4. Enter your tenant ID, select Next
5. Ensure that Authentication Method is set to "OAuth2", then Sign In and Connect.
6. Sign in with your admin/report reader credentials.
7. Report data will refresh and the report will update automatically.
Final status: The validation process for the fix completed, and we've deployed the fix within the most recent app version of Microsoft 365 Usage Analytics. We've tested with a subset of affected admins to ensure the impact has been remediated with our fix implemented, and admins need to take the actions outlined in the More Info section of this communication to update their app version and receive the fix.
Scope of impact: Any admin accessing Microsoft 365 Usage Analytics reports in Power BI may have been affected.
Start time: Thursday, January 1, 2026, at 12:00 AM UTC
End time: Friday, February 13, 2026, at 5:25 PM UTC
Root cause: A subset of Power BI logic didn't have the expected date formatting required for the year 2026, resulting in impact.
Next steps:
- We're reviewing the impacting Power BI logic to determine how the incorrect date formatting wasn't identified prior to being introduced into the service. The results of this investigation will help us to improve our pre-deployment processes and ensure similar instances of impact don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 12 19:08:21 2026 |
|---|
| Description: | Title: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI
User impact: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI.
More info: Admins can access the missing data through the Microsoft 365 admin center or by leveraging the Graph API.
Current status: We're continuing the validations of the fix to correct the date formatting and to restore admins' Microsoft 365 Usage Analytics reports in Power BI, and we'll aim to provide a deployment timeline by our next scheduled update.
Scope of impact: Any admin accessing Microsoft 365 Usage Analytics reports in Power BI may be affected.
Start time: Thursday, January 1, 2026, at 12:00 AM UTC
Root cause: A subset of Power BI logic doesn't have the expected date formatting required for the year 2026, resulting in impact.
Next update by: Friday, February 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Feb 12 14:56:56 2026 |
|---|
| Description: | Title: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI
User impact: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI.
More info: Admins can access the missing data through the Microsoft 365 admin center or by leveraging the Graph API.
Current status: Our fix development to correct the date formatting and to restore admins' Microsoft 365 Usage Analytics reports in Power BI is requiring additional validation time to ensure that it will correct all facets of this issue. In the meantime, we've identified that admins can access the missing data through the Microsoft 365 admin center or by leveraging the Graph API.
Scope of impact: Any admin accessing Microsoft 365 Usage Analytics reports in Power BI may be affected.
Start time: Thursday, January 1, 2026, at 12:00 AM UTC
Root cause: A subset of Power BI logic doesn't have the expected date formatting required for the year 2026, resulting in impact.
Next update by: Friday, February 13, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Feb 11 16:28:03 2026 |
|---|
| Description: | Title: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI
User impact: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI.
Current status: Our fix to correct the date formatting and to restore admins' Microsoft 365 Usage Analytics reports in Power BI requires more time to develop that originally expected. We'll provide an estimated timeline for remediating the impact once it has become available.
Scope of impact: Any admin accessing Microsoft 365 Usage Analytics reports in Power BI may be affected.
Start time: Thursday, January 1, 2026, at 12:00 AM UTC
Root cause: A subset of Power BI logic doesn't have the expected date formatting required for the year 2026, resulting in impact.
Next update by: Friday, February 13, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Feb 9 15:47:35 2026 |
|---|
| Description: | Title: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI
User impact: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI.
Current status: We're progressing with the development of our fix to correct the date formatting for 2026 and later and to restore admins’ Microsoft 365 Usage Analytics reports in Power BI. We'll provide an estimated timeline for the deployment of our solution after our internal fix development and validations have been completed.
Scope of impact: Any admin accessing Microsoft 365 Usage Analytics reports in Power BI may be affected.
Start time: Thursday, January 1, 2026, at 12:00 AM UTC
Root cause: A subset of Power BI logic doesn't have the expected date formatting required for the year 2026, resulting in impact.
Next update by: Wednesday, February 11, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Feb 5 14:59:41 2026 |
|---|
| Description: | Title: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI
User impact: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI.
Current status: We’re continuing our work to develop a fix that updates and corrects the date formatting for 2026 and later to remediate this issue. We’ll provide a resolution timeline once it’s available.
Scope of impact: Any admin accessing Microsoft 365 Usage Analytics reports in Power BI may be affected.
Start time: Thursday, January 1, 2026, at 12:00 AM UTC
Root cause: A subset of Power BI logic doesn't have the expected date formatting required for the year 2026, resulting in impact.
Next update by: Monday, February 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Feb 4 13:32:09 2026 |
|---|
| Description: | Title: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI
User impact: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI.
Current status: We've received reports from admins missing some Microsoft 365 Usage Analytics reports within Power BI. We've analyzed service telemetry in conjunction with HTTP Archive format (HAR) captures of the issue in progress and identified that a subset of Power BI logic doesn't have the expected date formatting required for the year 2026, resulting in impact. We're in the process of developing a fix to update and correct the formatting for 2026 and later to remediate this issue.
Scope of impact: Any admin accessing Microsoft 365 Usage Analytics reports in Power BI may be affected.
Start time: Thursday, January 1, 2026, at 12:00 AM UTC
Root cause: A subset of Power BI logic doesn't have the expected date formatting required for the year 2026, resulting in impact.
Next update by: Thursday, February 5, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Feb 4 13:02:14 2026 |
|---|
| Description: | Title: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI
User impact: Admins may be missing Microsoft 365 Usage Analytics reports in Power BI.
Current status: We're investigating a potential issue with Power BI reporting and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1227436 - Users may intermittently receive no response from Microsoft Copilot (Microsoft 365) agents in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jan 12 14:45:00 2026 |
|---|
| End Time: | Wed Feb 11 19:30:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Feb 13 15:44:42 2026 |
|---|
| Root Cause: | A recent Copilot Studio update introduced an issue that was adversely affecting the installation of apps in Microsoft Teams with shared deep links and chat agent behavior. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 13 15:44:42 2026 |
|---|
| Description: | Title: Users may intermittently receive no response from Microsoft Copilot (Microsoft 365) agents in Microsoft Teams
User impact: Users may have intermittently received no response from Copilot agents in Microsoft Teams.
Final status: The fix deployment completed, and we've confirmed from our internal monitoring telemetry and user reports that impact has been remediated.
Scope of impact: Any user who attempted to send chat messages to a Copilot agent in Microsoft Teams was intermittently impacted.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
End time: Thursday, February 12, 2026, at 12:30 AM UTC
Root cause: A recent Copilot Studio update introduced an issue that was adversely affecting the installation of apps in Microsoft Teams with shared deep links and chat agent behavior.
Next steps:
- We're reviewing and improving our update validation procedure to detect and prevent similar app installation issues in the future.
|
|---|
|
| Time: | Mon Feb 9 19:41:32 2026 |
|---|
| Description: | Title: Users may intermittently receive no response from Microsoft Copilot (Microsoft 365) agents in Microsoft Teams
User impact: Users may intermittently receive no response from Copilot agents in Microsoft Teams.
Current status: We've completed our validations of the fix and initiated its deployment. We're monitoring as it progresses to establish a completion timeline.
Scope of impact: Any user attempting to send chat messages to a Copilot agent in Microsoft Teams is intermittently impacted. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that is adversely affecting the installation of apps in Microsoft Teams with shared deep links and chat agent behavior.
Next update by: Saturday, February 14, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Feb 6 15:38:58 2026 |
|---|
| Description: | Title: Users may intermittently receive no response from Microsoft Copilot (Microsoft 365) agents in Microsoft Teams
User impact: Users may intermittently receive no response from Copilot agents in Microsoft Teams.
Current status: We're preparing to deploy the fix to our internal testing environment to perform additional validations, and to ensure it remediates impact without adversely impacting other aspects of the service. Once our validations are completed, we'll start deploying the fix to the impacted environment and we'll aim to provide a deployment timeline once available.
Scope of impact: Any user attempting to send chat messages to a Copilot agent in Microsoft Teams is intermittently impacted. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that is adversely affecting the installation of apps in Microsoft Teams with shared deep links and chat agent behavior.
Next update by: Tuesday, February 10, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Feb 5 18:31:29 2026 |
|---|
| Description: | Title: Users may intermittently receive no response from Microsoft Copilot (Microsoft 365) agents in Microsoft Teams
User impact: Users may intermittently receive no response from Copilot agents in Microsoft Teams.
Current status: We've determined that additional validations are required to ensure our fix to back-fill data necessary to facilitate responses from Copilot agents remediates all potential impact scenarios. This extended analysis and validation period will help us to ensure remediation once our fix is deployed.
Scope of impact: Any user attempting to send chat messages to a Copilot agent in Microsoft Teams is intermittently impacted. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that is adversely affecting the installation of apps in Microsoft Teams with shared deep links and chat agent behavior.
Next update by: Friday, February 6, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Feb 5 11:19:30 2026 |
|---|
| Description: | Title: Users may intermittently receive no response from Microsoft Copilot (Microsoft 365) agents in Microsoft Teams
User impact: Users may intermittently receive no response from Copilot agents in Microsoft Teams.
Current status: We've identified that a recent Copilot Studio update introduced an issue that is adversely affecting the installation of apps in Microsoft Teams with shared deep links and chat agent behavior. We've developed a fix that will back-fill data that's necessary to facilitate responses from Copilot agents and are determining the most efficient method to deploy the fix to the affected environment.
Scope of impact: Any user attempting to send chat messages to a Copilot agent in Microsoft Teams is intermittently impacted. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that is adversely affecting the installation of apps in Microsoft Teams with shared deep links and chat agent behavior.
Next update by: Friday, February 6, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Feb 5 10:53:59 2026 |
|---|
| Description: | Title: Users may intermittently receive no response from Microsoft Copilot (Microsoft 365) agents in Microsoft Teams
User impact: Users may intermittently receive no response from Copilot agents in Microsoft Teams.
Current status: We're investigating a potential issue with Copilot agents in Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1231314 - Admins may have delayed Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 5 01:00:00 2026 |
|---|
| End Time: | Thu Feb 12 21:28:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 13 14:37:12 2026 |
|---|
| Root Cause: | A portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center was operating in an unhealthy state, which was resulting in delays of Copilot reporting data and degraded performance. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 13 14:27:49 2026 |
|---|
| Description: | Title: Admins may have delayed Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center
User impact: Admins may have had delayed Copilot usage reports in the Microsoft 365 admin center.
Final status: We've identified that a portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center was operating in an unhealthy state, resulting in delays for Copilot reporting data and degraded performance. To remediate this issue, we implemented configuration changes within the affected infrastructure to support increased service traffic and restore stability. We’ve validated resolution through service monitoring and confirmation from affected users.
Scope of impact: This issue may have affected any admin based in the Asia-Pacific region attempting to view usage reports in the Microsoft 365 admin center.
Start time: Thursday, February 5, 2026, at 6:00 AM UTC
End time: Friday, February 13, 2026, at 2:28 AM UTC
Root cause: A portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center was operating in an unhealthy state, which was resulting in delays of Copilot reporting data and degraded performance.
Next steps:
- We're investigating why the portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center was operating in an unhealthy state to prevent this problem from happening again in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 12 15:27:42 2026 |
|---|
| Description: | Title: Admins may have delayed Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center
User impact: Admins may have delayed Copilot usage reports in the Microsoft 365 admin center.
Current status: We've identified that a portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center is operating in an unhealthy state, resulting in delays when relaying Copilot reporting data and degraded performance. We're reviewing service health telemetry to assist in determining our next steps to address the issue and resolve impact.
Scope of impact: This issue may affect any admin based in the Asia-Pacific region attempting to view usage reports in the Microsoft 365 admin center.
Start time: Thursday, February 5, 2026, at 6:00 AM UTC
Root cause: A portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center is operating in an unhealthy state, which is resulting in delays when relaying Copilot reporting data and degraded performance.
Next update by: Friday, February 13, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Feb 12 15:17:47 2026 |
|---|
| Description: | Title: Admins may have delayed Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center
User impact: Admins may have delayed Copilot usage reports in the Microsoft 365 admin center.
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.
|
|---|
|
MV1231713 - Admins may be unable to edit or update communications configurations in Microsoft Viva Glint
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 12 17:30:00 2026 |
|---|
| End Time: | Fri Feb 13 12:30:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Glint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 13 13:42:06 2026 |
|---|
| Root Cause: | A recent code change intended to update service functionality resulted in the communications editor becoming unresponsive when admins attempted to edit email templates. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 13 13:40:55 2026 |
|---|
| Description: | Title: Admins may be unable to edit or update communications configurations in Microsoft Viva Glint
User impact: Admins may have been unable to edit or update communications configurations in Microsoft Viva Glint.
More info: The Viva Glint Communications page became unresponsive when attempting to edit survey email templates (Invite / Reminder). The page remained in a loading state and eventually showed “Page not responding”.
Final status: We've identified that a recent code change intended to update service functionality resulted in the communications editor becoming unresponsive when admins attempted to edit email templates. To remediate this, we've reverted the offending change and after monitoring the service, we've verified that this action has successfully resolved the problem.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure and attempted to edit or update communications configurations in Microsoft Viva Glint.
Start time: Thursday, February 12, 2026, at 10:30 PM UTC
End time: Friday, February 13, 2026, at 5:30 PM UTC
Root cause: A recent code change intended to update service functionality resulted in the communications editor becoming unresponsive when admins attempted to edit email templates.
Next steps:
- We're investigating why the recent code change intended to update service functionality resulted in the communications editor becoming unresponsive when admins attempted to edit email templates to prevent this problem from happening again in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 13 07:22:00 2026 |
|---|
| Description: | Title: Admins may be unable to edit or update communications configurations in Microsoft Viva Glint
User impact: Admins may be unable to edit or update communications configurations in Microsoft Viva Glint.
More info: The Viva Glint Communications page becomes unresponsive when attempting to edit survey email templates (Invite / Reminder). The page remains in a loading state and eventually shows “Page not responding”.
Current status: We've successfully re-produced the issue in our test environment. We're now working to understand the root cause of impact to aid us in developing a mitigation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure and attempting to edit or update communications configurations in Microsoft Viva Glint.
Next update by: Friday, February 13, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Feb 13 05:37:40 2026 |
|---|
| Description: | Title: Admins may be unable to edit or update communications configurations in Microsoft Viva Glint
User impact: Admins may be unable to edit or update communications configurations in Microsoft Viva Glint.
More info: The Viva Glint Communications page becomes unresponsive when attempting to edit survey email templates (Invite / Reminder). The page remains in a loading state and eventually shows “Page not responding”.
Current status: We're reviewing support provided information and service telemetry to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure and attempting to edit or update communications configurations in Microsoft Viva Glint. This information may be updated as our investigation continues.
Next update by: Friday, February 13, 2026, at 12:30 PM UTC
|
|---|
|
MO1231810 - Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 13 08:26:00 2026 |
|---|
| End Time: | Fri Feb 13 10:52:19 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Feb 13 10:52:48 2026 |
|---|
| Root Cause: | Traffic management measures were applied as part of a mitigation for a configuration issue, which caused user impact. More details will be provided in the Post‑Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 13 10:52:48 2026 |
|---|
| Description: | Title: Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
User impact: Users may experience failures or timeouts while accessing Copilot.
Final status: We’ve applied the mitigation and the affected components have been restored to full-service capacity. We will continue to monitor service availability and investigate the underlying root cause.
Scope of impact: Impact was specific to user attempting to access Copilot.
Start time: Friday, February 13, 2026, at 1:26 PM UTC
End time: Friday, February 13, 2026, at 1:54 PM UTC
Root cause: Traffic management measures were applied as part of a mitigation for a configuration issue, which caused user impact. More details will be provided in the Post‑Incident Report.
Next Steps
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Fri Feb 13 10:04:40 2026 |
|---|
| Description: | This quick update is designed to give the latest information on this issue.
We’re continuing to restart the affected components and observing reduced user impact. We will continue to apply the controlled recovery steps and monitor service availability.
|
|---|
|
| Time: | Fri Feb 13 09:31:47 2026 |
|---|
| Description: | Title: Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
User impact: Users may experience failures or timeouts while accessing Copilot.
Current status: We’ve identified an underlying service issue affecting a subset of infrastructure components. We’ve confirmed a remediation plan and are restarting the affected components to restore full service capacity.
Scope of impact: Impact is specific to users located in Europe attempting to access Copilot.
Next update by: Friday, February 13, 2026, at 3:30 PM UTC
|
|---|
|
DZ1231408 - Admins' manual remediations weren't shown on the action history page in the Microsoft Defender XDR portal
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 11 06:59:00 2026 |
|---|
| End Time: | Fri Feb 13 04:43:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 13 10:44:53 2026 |
|---|
| Root Cause: | A code regression was introduced in a recent configuration change. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 13 07:30:45 2026 |
|---|
| Description: | Title: Admins' manual remediations weren't shown on the action history page in the Microsoft Defender XDR portal
User impact: Admins' manual remediations weren't shown on the action history page in the Microsoft Defender XDR portal.
More info: When admins performed a manual remediation, an Approval ID is generated; however, the investigation ID and Approval ID weren't shown on the action history page.
The two-step approval process was missing from the action center/pending page in the Microsoft Defender XDR portal. This issue only affected manual actions completed via Threat explorer, Advanced Hunting, Take action wizard, Custom detection and Graph API. There was no problem with action processing; the issue was with the entries displaying in the Action center.
As a way to circumvent impact whilst we worked to resolve the issue, affected admins could've viewed the status of manual remediations through Microsoft Defender Threat Explorer by applying the following filter in the Query Builder: Additional action == Manual remediation. Alternatively, the status could be seen using Advanced Hunting by utilizing EmailPostDeliveryEvents and filtering by ActionType.
Final status: We’ve successfully reverted the recent change and confirmed through service monitoring that impact has been fully remediated.
Scope of impact: Your organization was affected by this event, and any admin attempting to view manual remediations on the action history page in the Microsoft Defender XDR portal was impacted.
Start time: Wednesday, February 11, 2026, at 11:59 AM UTC
End time: Friday, February 13, 2026, at 9:43 AM UTC
Root cause: A code regression was introduced in a recent configuration change.
Next steps:
- We're reviewing our standard service update procedures to avoid similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 13 05:13:03 2026 |
|---|
| Description: | Title: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal
User impact: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal.
More info: When admins perform a manual remediation, an Approval ID is generated; however, the investigation ID and Approval ID aren't shown on the action history page.
The two-step approval process is missing from the action center/pending page in the Microsoft Defender XDR portal. This issue only affects manual actions completed via Threat explorer, Advanced Hunting, Take action wizard, Custom detection and Graph API. There is no problem with action processing; the issue is with the entries displaying in the Action center.
As a way to circumvent impact while we work to resolve the issue, affected admins can view the status of manual remediations through Microsoft Defender Threat Explorer by applying the following filter in the Query Builder: Additional action == Manual remediation. Alternatively, the status can be seen using Advanced Hunting by utilizing EmailPostDeliveryEvents and filtering by ActionType.
Current status: We’ve determined that a code regression was introduced in a recent configuration change. We're reverting the problematic change to mitigate impact.
Scope of impact: Your organization is affected by this event, and any admin attempting to view manual remediations on the action history page in the Microsoft Defender XDR portal is impacted. This information may be updated as our investigation continues.
Root cause: A code regression was introduced in a recent configuration change.
Next update by: Friday, February 13, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Fri Feb 13 02:23:34 2026 |
|---|
| Description: | Title: Some admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal
User impact: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal.
More info: When admins perform a manual remediation, an Approval ID is generated; however, the investigation ID and Approval ID aren't shown on the action history page.
As a way to circumvent impact while we work to resolve the issue, affected admins can view the status of manual remediations through Microsoft Defender Threat Explorer by applying the following filter in the Query Builder: Additional action == Manual remediation. Alternatively, the status can be seen using Advanced Hunting by utilizing EmailPostDeliveryEvents and filtering by ActionType.
Current status: We’re continuing our investigation by checking if any recent changes or deployments could be causing the issue to determine our next troubleshooting steps.
Scope of impact: Some admins attempting to view manual remediations on the action history page in the Microsoft Defender XDR portal may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, February 13, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Fri Feb 13 00:20:41 2026 |
|---|
| Description: | Title: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal
User impact: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal.
More info: When admins perform a manual remediation, an Approval ID is generated; however, the investigation ID and Approval ID aren't shown on the action history page.
As a way to circumvent impact while we work to resolve the issue, affected admins can view the status of manual remediations through Microsoft Defender Threat Explorer by applying the following filter in the Query Builder: Additional action == Manual remediation. Alternatively, the status can be seen using Advanced Hunting by utilizing EmailPostDeliveryEvents and filtering by ActionType.
Current status: We’re further reviewing if any recent service changes may be contributing to impact to help with identifying the root cause and formulating a fix.
Scope of impact: Your organization is affected by this event, and any admin attempting to view manual remediations on the action history page in the Microsoft Defender XDR portal is impacted.
Next update by: Friday, February 13, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Feb 12 19:54:42 2026 |
|---|
| Description: | Title: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal
User impact: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal.
More info: When admins perform a manual remediation, an Approval ID is generated; however, the investigation ID and Approval ID aren't shown on the action history page.
As a way to circumvent impact while we work to resolve the issue, affected admins can view the status of manual remediations through Microsoft Defender Threat Explorer by applying the following filter in the Query Builder: Additional action == Manual remediation. Alternatively, the status can be seen using Advanced Hunting by utilizing EmailPostDeliveryEvents and filtering by ActionType.
Current status: We’re continuing our review of recent service changes and available service side logs to refine our understanding of the impacted scenario. Additionally, we’ve provided your support case owner with a way to circumvent impact while we further pursue what the underlying cause of the issue is.
Scope of impact: Your organization is affected by this event, and any admin attempting to view manual remediations on the action history page in the Microsoft Defender XDR portal is impacted.
Next update by: Friday, February 13, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Thu Feb 12 18:23:15 2026 |
|---|
| Description: | Title: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal
User impact: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal.
More info: When admins perform a manual remediation, an Approval ID is generated; however, the investigation ID and Approval ID aren't shown on the action history page.
Current status: We're checking recent service changes to determine whether any may be contributing to the impact.
Scope of impact: Your organization is affected by this event, and any admin attempting to view manual remediations on the action history page in the Microsoft Defender XDR portal is impacted.
Next update by: Friday, February 13, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Feb 12 17:54:29 2026 |
|---|
| Description: | Title: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal
User impact: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal.
More info: When admins perform a manual remediation, an Approval ID is generated; however, the investigation ID and Approval ID aren't shown on the action history page.
Current status: We're reviewing screenshots provided by an affected user to gain clarity on the issue and determine the next steps to isolate the root cause.
Scope of impact: Your organization is affected by this event, and any admin attempting to view manual remediations on the action history page in the Microsoft Defender XDR portal is impacted.
Next update by: Friday, February 13, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Feb 12 17:34:50 2026 |
|---|
| Description: | Title: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal
User impact: Admins' manual remediations aren't being shown on the action history page in the Microsoft Defender XDR portal.
More info: When admins perform a manual remediation, an Approval ID is generated; however, the investigation ID and Approval ID aren't shown on the action history page.
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.
|
|---|
|
EX1213792 - Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Jan 6 01:49:02 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 13 06:36:32 2026 |
|---|
| Root Cause: | A timing-related issue during group creation across backend systems where service requests are processed before directory information has fully refreshed across all servers, leading to impact. |
|---|
| Next Update: | Friday, February 27, 2026, at 11:00 AM UTC |
|---|
|
Details
| Time: | Fri Feb 13 06:36:32 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're continuing to test the fix within our internal testing environment. However, due to the complexity of the changes, this testing is expected to take an extended amount of time. We will share further details once testing has completed.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Friday, February 27, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Feb 12 06:20:07 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're deploying the fix to our test environment and expect this process to complete by our next scheduled update. After the deployment completes, we'll be able to validate its effectiveness before deploying to the affected environments.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Friday, February 13, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Feb 10 07:22:35 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We’ve determined that the previously mentioned fix didn't successfully mitigate impact in our testing environment. As a result, we’ve developed an additional fix and are preparing to deploy it to our test environment to validate its effectiveness before deploying it to affected environments.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Thursday, February 12, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Fri Feb 6 07:54:20 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're progressing with our validation of the fix to ensure its efficacy. We'll provide a completion timeline when one becomes available.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Tuesday, February 10, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Feb 4 08:33:34 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're continuing to validate the fix to ensure its efficacy. We'll provide a completion timeline when one becomes available.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Friday, February 6, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Feb 4 01:29:33 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We've begun validation on the fix to ensure its efficacy. We'll provide a completion timeline when one becomes available.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Wednesday, February 4, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 01:58:44 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: After evaluating all available logging, we've identified a fix to safely resolve the impact. We're in the final stages of its development process and once the fix is ready, we will first deploy it to our test environment for validation.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Wednesday, February 4, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Fri Jan 30 01:41:37 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We expect that the fix will complete deployment to our internal testing environment, allowing us to validate its efficacy by the time of our next scheduled update. Additionally, we’re reaching out to a subset of affected users to provide Fiddler trace logs to assist us in validating that the previously mentioned timing-related issue during group creation is leading to impact and subsequently expedite the ongoing deployment of the aforementioned fix.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Monday, February 2, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Wed Jan 28 02:00:13 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We've encountered an issue preventing us from safely rolling out the code changes we were previously theorizing may be able to resolve the issue. We've identified that due to the complexity of the involved request flow and low volume of data associated with the impacted scenario, our internal reproduction of the issue is insufficient to conclusively validate our root cause theory without making changes to enhance our service logging specific to this scenario. We're evaluating options for implementing advanced logging and data collection methods to assist us in identifying our next steps towards remediation, as well as reassessing our options for safely deploying our potential fix.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Friday, January 30, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Tue Jan 27 09:34:38 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We’re proceeding to work on the fix to ensure directory cache information is refreshed correctly across all servers. We’re also progressing our deployment validation and now expect to provide a completion timeline by our next scheduled update.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Root cause: A timing-related issue during group creation across backend systems where service requests are processed before directory information has fully refreshed across all servers, leading to impact.
Next update by: Wednesday, January 28, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Mon Jan 26 09:15:11 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We’re actively working on the fix to ensure directory cache information is refreshed correctly across all servers. We’re progressing our deployment validation and expect to provide a completion timeline by our next scheduled update.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Root cause: A timing-related issue during group creation across backend systems where service requests are processed before directory information has fully refreshed across all servers, leading to impact.
Next update by: Tuesday, January 27, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Jan 23 09:56:31 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We've identified a timing-related issue during group creation across backend systems where service requests are processed before directory information has fully refreshed across all servers, leading to impact. We're deploying a fix to ensure directory cache information is refreshed correctly across all servers and expect to provide completion timeline by our next scheduled update.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Root cause: A timing-related issue during group creation across backend systems where service requests are processed before directory information has fully refreshed across all servers, leading to impact.
Next update by: Monday, January 26, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Jan 23 01:44:43 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're continuing our review of the latest collected error logs and service data to gain further insight into the underlying source of impact and determine our next steps.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu Jan 22 01:51:34 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: After initial difficulties with acquiring specific logs from the impacted service, we've successfully managed to gather the needed error logs to help our investigation into the root cause of impact. We're analyzing these, along with previous data, to help inform our next troubleshooting steps and strategy to resolve the issue.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Wed Jan 21 01:37:09 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're continuing our efforts to gather and analyze additional service logging as we continue to work towards gathering data from an internal reproduction of the issue. Due to the complexity of the scenario, we're anticipating it may require some additional time before we can determine our options for mitigation.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Thursday, January 22, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Jan 20 20:38:12 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: The previously mentioned log analysis to help understand why impact is occurring and to identify a strategy to resolve impact is ongoing. In parallel, we’re working to reproduce the issue internally to help aid our root cause investigation.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Wednesday, January 21, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Jan 20 19:17:02 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're continuing our analysis of the diagnostic logs, along with request IDs and error logs, to help identify the underlying root cause of impact and to inform our next steps to resolve the impact.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This section may be updated as our investigation continues.
Next update by: Wednesday, January 21, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Tue Jan 20 12:38:31 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: Our analysis of the diagnostic logging is progressing as we work to identify the source of the issue and inform our next steps towards developing a strategy to resolve the impact.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Next update by: Wednesday, January 21, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Jan 19 09:03:46 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're proceeding with our analysis of the diagnostic logs, to isolate the underlying root cause of impact and formulate a mitigation plan.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Next update by: Tuesday, January 20, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jan 14 09:52:21 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're continuing to analyze the diagnostic logs to isolate the root cause of impact and develop a fix.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Next update by: Monday, January 19, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue Jan 13 08:45:05 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We've collected diagnostic logs and we're analyzing them to isolate the root cause of impact and develop a fix.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Next update by: Wednesday, January 14, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Mon Jan 12 08:21:23 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're obtaining diagnostic logs to help us isolate the root cause of impact and formulate a mitigation plan.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Next update by: Tuesday, January 13, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Jan 9 08:16:55 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: Our efforts to review logs, group creation and deletion processes, and environmental differences to reach a mitigation plan and root cause analysis is ongoing.
Scope of impact: Your organization is affected by this event, and admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This information may be updated as our investigation continues.
Next update by: Monday, January 12, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Jan 7 08:58:58 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We’re continuing with our review logs, group creation and deletion processes, and environmental differences to find the cause of the upgrade issue.
Scope of impact: Your organization is affected by this event, and admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This information may be updated as our investigation continues.
Next update by: Friday, January 9, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 07:51:01 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We’re currently reviewing logs, group creation and deletion processes, and environmental differences to find the cause of the upgrade issue.
Scope of impact: Your organization is affected by this event, and admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This information may be updated as our investigation continues.
Next update by: Wednesday, January 7, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 02:00:53 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're reviewing system logs to isolate the origin of this issue.
Scope of impact: Your organization is affected by this event, and any admin can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center. This information may be updated as our investigation continues.
Next update by: Tuesday, January 6, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 01:50:39 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center
User impact: Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center.
Current status: We're investigating a potential issue in which admins can’t upgrade groups from distributions lists to unified groups from both PowerShell and the Exchange admin center and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MV1229892 - Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Feb 9 16:22:43 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 12 21:07:08 2026 |
|---|
| Root Cause: | An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the M365 Admin Center to be inaccurate. |
|---|
| Next Update: | Wednesday, February 18, 2026, at 3:00 AM UTC |
|---|
|
Details
| Time: | Thu Feb 12 21:07:08 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 Admin Center, are inaccurate. These issues do not affect all-up user counts for Microsoft 365 Copilot or Copilot in Outlook.
For some Outlook web users, selecting “summary by Copilot” or “summarize” at the top of an email thread did not count as a “summarize email thread” action. For some Outlook web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email did not count as a “generate email” action.
Current status: We’ve determined that an alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the M365 Admin Center to be inaccurate. We’re applying a solution to output the correct data after February 14, 2026, which should appear in the affected reported counts by February, 19, 2026.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: An alignment issue in the metric definition is causing an undercount of “generate email” and “summarize thread email” actions, resulting in reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the M365 Admin Center to be inaccurate.
Next update by: Wednesday, February 18, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Feb 11 19:58:08 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 Admin Center, are inaccurate. These issues do not affect all-up user counts for Microsoft 365 Copilot or Copilot in Outlook.
For some Outlook web users, selecting “summary by Copilot” or “summarize” at the top of an email thread did not count as a “summarize email thread” action. For some Outlook web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email did not count as a “generate email” action.
Current status: Our investigation into the underlying cause of the aforementioned definition alignment issues is progressing, though taking an extended period of time as we continue to develop the most efficacious solution to resolving the issue.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Next update by: Friday, February 13, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 19:41:17 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
More info: Reported counts for both "generate email" and "summarize thread email" actions and their associated active users in Viva Insights and the AI Adoption Score report in the Microsoft 365 Admin Center, are inaccurate. These issues do not affect all-up user counts for Microsoft 365 Copilot or Copilot in Outlook.
For some Outlook web users, selecting “summary by Copilot” or “summarize” at the top of an email thread did not count as a “summarize email thread” action. For some Outlook web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email did not count as a “generate email” action.
Current status: While our analysis of the provided support case information and the expected versus actual Copilot output metrics is ongoing, we've identified an issue in the metric definition that's causing an undercount of “generate email” and “summarize thread email” actions. As a result, reported counts for both actions and their associated active users in Viva Insights and the AI Adoption Score report in the M365 Admin Center, are inaccurate. These issues do not affect all-up user counts for M365 Copilot or Copilot in Outlook. We've updated the "More Info" section above to highlight these findings. We're further investigating the underlying cause of this definition alignment issue so we can identify a remediation strategy.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights. This section may be updated as our investigation continues.
Next update by: Thursday, February 12, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 18:26:02 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
Current status: We're progressing with our support ticket review and our analysis between expected and actual outputted Copilot metric data as we work to isolate the source for this event.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights.
Next update by: Tuesday, February 10, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 16:58:11 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
Current status: We're reviewing support provided data from affected users, particularly the expected Copilot metric data versus the actual outputted Copilot metric data, as we begin isolating this issue's root cause.
Scope of impact: Your organization is impacted by this event, and all users see inaccurate and incomplete data for Copilot metrics in Microsoft Viva Insights.
Next update by: Tuesday, February 10, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 16:33:18 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot (Microsoft 365) metrics in Microsoft Viva Insights
User impact: Users see inaccurate or incomplete Outlook data for Copilot metrics in Microsoft Viva Insights.
Current status: We're investigating a potential issue with Microsoft Viva Insight where users are seeing inaccurate and incomplete data for Copilot metrics. We're checking for impact to your organization and we'll provide an update within 30 minutes.
|
|---|
|
CP1221896 - Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jan 12 23:00:00 2026 |
|---|
| End Time: | Tue Feb 10 19:50:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 12 20:13:15 2026 |
|---|
| Root Cause: | An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 12 20:13:15 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings were delayed up to 25 seconds.
More info: Delays were specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Final status: After an extended period of monitoring, we've confirmed our solutions resolved the impact in the affected regions and that the service is healthy.
Scope of impact: This issue may have affected any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
End time: Wednesday, February 11, 2026, at 12:50 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next steps:
- We're continuing our efforts to improve the routing and processing of request traffic in our infrastructure, which will help us in avoiding similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 10 19:45:49 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: Our solutions have addressed the impact in all affected regions and we’re monitoring these regions to ensure the service remains healthy.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Friday, February 13, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Feb 4 20:07:33 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: Our solutions are continuing to address the impact in Asia Pacific region and Europe. We anticipate full remediation in all affected regions by our next scheduled communications update.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Wednesday, February 11, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Feb 4 18:21:32 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We're continuing to address the remaining impact in the Asia Pacific region by fixing the flow labels. We’ll provide a precise timeline for remediation if one becomes available.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Thursday, February 5, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Jan 28 18:19:28 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: The process to fix the flow labels to address this remaining impact in the Asia Pacific region is still ongoing. We anticipate this fix will take some time to fully address the remaining impact, and we’ll provide a more precise timeline as soon as one becomes available.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Thursday, February 5, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Jan 26 19:58:26 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We’ve observed that the latency levels have reduced and that service has restored for the majority of users; however, the latency has not fully recovered in all affected regions as anticipated. We're currently validating a fix that will update the flow labels in an effort to address this remaining impact and will provide an updated mitigation timeline as soon as one becomes available.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Thursday, January 29, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Jan 23 18:01:39 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We've confirmed that an unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact. We've applied a fix to increase throughput for authentication traffic and have observed that latency has reduced significantly. We're monitoring latency levels to ensure they continue to reduce and impact is successfully remediated.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Tuesday, January 27, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Jan 23 17:01:20 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We're reviewing service health telemetry information to identify and isolate any errors which may potentially be contributing to latency to assist our investigation into the source of the issue.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Next update by: Saturday, January 24, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 16:36:27 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We're investigating a potential issue with Facilitator agent responses and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1221897 - Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jan 12 23:00:00 2026 |
|---|
| End Time: | Tue Feb 10 19:50:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 12 20:12:27 2026 |
|---|
| Root Cause: | An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 12 20:12:27 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings were delayed up to 25 seconds.
More info: Delays were specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Final status: After an extended period of monitoring, we've confirmed our solutions resolved the impact in the affected regions and that the service is healthy.
Scope of impact: This issue may have affected any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
End time: Wednesday, February 11, 2026, at 12:50 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next steps:
- We're continuing our efforts to improve the routing and processing of request traffic in our infrastructure, which will help us in avoiding similar impact in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 10 19:46:35 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: Our solutions have addressed the impact in all affected regions and we’re monitoring these regions to ensure the service remains healthy.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Friday, February 13, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Feb 4 20:07:44 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: Our solutions are continuing to address the impact in Asia Pacific region and Europe. We anticipate full remediation in all affected regions by our next scheduled communications update.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Wednesday, February 11, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Feb 4 18:21:13 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We're continuing to address the remaining impact in the Asia Pacific region by fixing the flow labels. We’ll provide a precise timeline for remediation if one becomes available.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Thursday, February 5, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Jan 28 18:17:16 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: The process to fix the flow labels to address this remaining impact in the Asia Pacific region is still ongoing. We anticipate this fix will take some time to fully address the remaining impact, and we’ll provide a more precise timeline as soon as one becomes available.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Thursday, February 5, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Jan 26 19:57:39 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We’ve observed that the latency levels have reduced and that service has restored for the majority of users; however, the latency has not fully recovered in all affected regions as anticipated. We're currently validating a fix that will update the flow labels in an effort to address this remaining impact and will provide an updated mitigation timeline as soon as one becomes available.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Thursday, January 29, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Jan 23 18:01:36 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We've confirmed that an unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact. We've applied a fix to increase throughput for authentication traffic and have observed that latency has reduced significantly. We're monitoring latency levels to ensure they continue to reduce and impact is successfully remediated.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Start time: Tuesday, January 13, 2026, at 4:00 AM UTC
Root cause: An unusual influx of request traffic pertaining to user authentication when utilizing Facilitator for open-ended questions in meeting chat resulted in impact.
Next update by: Tuesday, January 27, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Jan 23 17:01:19 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We're reviewing service health telemetry information to identify and isolate any errors which may potentially be contributing to latency to assist our investigation into the source of the issue.
Scope of impact: This issue may affect any user in Microsoft Teams meetings attempting to ask open-ended questions in meeting chats from the meeting participants to the Facilitator agent.
Next update by: Saturday, January 24, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 16:36:30 2026 |
|---|
| Description: | Title: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds
User impact: Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds.
More info: Delays are specific to open-ended questions in the meeting chat from the meeting participants to the Facilitator agent.
Current status: We're investigating a potential issue with Facilitator agent responses and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1230320 - Some users in the North America region may have been unable to access the Microsoft 365 admin center
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Feb 10 09:10:00 2026 |
|---|
| End Time: | Tue Feb 10 11:25:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Feb 12 18:13:00 2026 |
|---|
| Root Cause: | A recent change to the redirection service, related to caching mechanisms, resulted in impact. More information is provided within the Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 12 18:13:00 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Feb 10 12:20:15 2026 |
|---|
| Description: | Title: Some users in the North America region may have been unable to access the Microsoft 365 admin center
User impact: Users in the North America region may have been unable to access the Microsoft 365 admin center.
More info: Users able to access the admin center may have experienced degraded functionality.
As functionality was degraded, users may have been unable to raise support tickets through the Microsoft 365 admin center.
Final status: We've confirmed that the issue is resolved through monitoring telemetry and customer validations.
Scope of impact: This issue impacted the North America region.
Start time: Tuesday, February 10, 2026, at 2:10 PM UTC
End time: Tuesday, February 10, 2026, at 4:25 PM UTC
Root cause: A recent change to the redirection service, related to caching mechanisms, resulted in impact. More information is provided within the Post-Incident Report.
Next steps:
- We're reviewing the change to better understand why impact occurred and implement items to prevent this issue reoccurring.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue Feb 10 11:47:04 2026 |
|---|
| Description: | Title: Some users in the North America region may be unable to access the Microsoft 365 admin center
User impact: Users in the North America region may be unable to access the Microsoft 365 admin center.
More info: Users able to access the admin center may be experiencing degraded functionality.
As functionality is degraded, users may be unable to raise support tickets through the Microsoft 365 admin center.
Additionally, users may be unable to access the M365 app.
Current status: Whilst we were performing the targeted restarts, parallel root cause investigations identified a recent change to the redirection service which may have been contributing to impact. We’ve reverted the change and are monitoring the service for recovery. Telemetry indicates that the service is beginning to recover.
Scope of impact: This issue impacts the North America region.
Next update by: Tuesday, February 10, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Feb 10 11:10:38 2026 |
|---|
| Description: | We’ve identified elevated resource utilization in the service that routes requests to the admin center, and we’re restarting the service to mitigate impact.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Feb 10 10:48:04 2026 |
|---|
| Description: | Title: Some users in the North America region may be unable to access the Microsoft 365 admin center
User impact: Users in the North America region may be unable to access the Microsoft 365 admin center.
More info: Users able to access the admin center may be experiencing degraded functionality.
As functionality is degraded, users may be unable to raise support tickets through the Microsoft 365 admin center.
Additionally, users may be unable to access the M365 app.
Current status: We’re continuing to analyze diagnostic data from the Microsoft 365 admin center infrastructure, with a current focus on usage patterns and Central Processing Unit (CPU) utilization levels. Additionally, we’re reviewing HTTP Archive (HAR) files provided by impacted users to support our investigation.
Scope of impact: Initial reports indicate that the issue is occurring in the North America region. We'll provide more information once identified.
Next update by: Tuesday, February 10, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Feb 10 10:18:54 2026 |
|---|
| Description: | We’re continuing to review telemetry related to Microsoft 365 admin center access to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Feb 10 09:50:24 2026 |
|---|
| Description: | Title: Some users in the North America region may be unable to access the Microsoft 365 admin center
User impact: Users in the North America region may be unable to access the Microsoft 365 admin center.
More info: Users able to access the admin center may be experiencing degraded functionality.
As functionality is degraded, users may be unable to raise support tickets through the Microsoft 365 admin center.
Additionally, users may be unable to access the M365 app.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Initial reports indicate that the issue is occurring in the North America region. We'll provide more information as we investigate.
Next update by: Tuesday, February 10, 2026, at 4:00 PM UTC
|
|---|
|
CW1218323 - Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Jan 15 13:55:08 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 12 16:57:57 2026 |
|---|
| Root Cause: | We've disabled the "Edit in Outlook" feature in Copilot Chat while we implement a fix for a separate service issue relating to the feature, causing impact. |
|---|
| Next Update: | Monday, February 23, 2026, at 11:00 PM UTC |
|---|
|
Details
| Time: | Thu Feb 12 16:57:57 2026 |
|---|
| Description: | Title: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message
User impact: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message.
More info: When users prompt Copilot Chat to draft an email message, the button to "Edit in Outlook" may not appear as expected.
Current status: Our metrics indicate that there are slow request response times, making the current metrics insufficient to proceed with re-enabling the "Edit in Outlook" button for the remaining 50 percent of users. We're reviewing possible options to improve request response times, so that we can bring the metrics up to an acceptable level before re-enabling the feature.
Scope of impact: Any user prompting Copilot Chat to draft an email message may be impacted.
Start time: Friday, December 19, 2025, at 6:00 PM UTC
Root cause: We've disabled the "Edit in Outlook" feature in Copilot Chat while we implement a fix for a separate service issue relating to the feature, causing impact.
Next update by: Monday, February 23, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Feb 5 16:23:06 2026 |
|---|
| Description: | Title: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message
User impact: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message.
More info: When users prompt Copilot Chat to draft an email message, the button to "Edit in Outlook" may not appear as expected.
Current status: After re-enabling the feature for 50 percent of the affected environment and then pausing the rollout, the current metrics we've reviewed are not substantial enough to confirm whether to proceed with re-enabling for the remaining 50 percent. We're continuing to monitor metrics until our next scheduled communication update to gather more insight and determine when to proceed with further enabling.
Scope of impact: Any user prompting Copilot Chat to draft an email message may be impacted.
Start time: Friday, December 19, 2025, at 6:00 PM UTC
Root cause: We've disabled the "Edit in Outlook" feature in Copilot Chat while we implement a fix for a separate service issue relating to the feature, causing impact.
Next update by: Thursday, February 12, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Feb 3 16:14:35 2026 |
|---|
| Description: | Title: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message
User impact: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message.
More info: When users prompt Copilot Chat to draft an email message, the button to "Edit in Outlook" may not appear as expected.
Current status: We've paused re-enabling the feature as we perform additional validations to ensure the efficacy of the fix in the broader environment. Once these validations have completed, we'll resume enabling the feature for the rest of the impacted users to fully remediate impact. We expect to have a timeline for completing re-enablement of the feature with our next scheduled communication update.
Scope of impact: Any user prompting Copilot Chat to draft an email message may be impacted.
Start time: Friday, December 19, 2025, at 6:00 PM UTC
Root cause: We've disabled the "Edit in Outlook" feature in Copilot Chat while we implement a fix for a separate service issue relating to the feature, causing impact.
Next update by: Thursday, February 5, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Jan 26 17:16:01 2026 |
|---|
| Description: | Title: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message
User impact: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message.
More info: When users prompt Copilot Chat to draft an email message, the button to "Edit in Outlook" may not appear as expected.
Current status: We've begun re-enabling the feature and about half of the affected users will now see the "Edit in Outlook" button. As the feature continues to saturate the affected environments, users will gradually have access to the feature.
Scope of impact: Any user prompting Copilot Chat to draft an email message may be impacted.
Start time: Friday, December 19, 2025, at 6:00 PM UTC
Root cause: We've disabled the "Edit in Outlook" feature in Copilot Chat while we implement a fix for a separate service issue relating to the feature, causing impact.
Next update by: Tuesday, February 3, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Jan 23 19:18:46 2026 |
|---|
| Description: | Title: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message
User impact: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message.
More info: When users prompt Copilot Chat to draft an email message, the button to "Edit in Outlook" may not appear as expected.
Current status: We're continuing to determine a timeline for the re-enablement of the "Edit in Outlook" feature in Copilot Chat that we expect will remediate impact.
Scope of impact: Any user prompting Copilot Chat to draft an email message may be impacted.
Root cause: We've disabled the "Edit in Outlook" feature in Copilot Chat while we implement a fix for a separate service issue relating to the feature, causing impact.
Next update by: Tuesday, January 27, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Jan 15 14:23:28 2026 |
|---|
| Description: | Title: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message
User impact: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message.
More info: When users prompt Copilot Chat to draft an email message, the button to "Edit in Outlook" may not appear as expected.
Current status: We've disabled the "Edit in Outlook" feature in Copilot Chat while we implement a fix for a separate service issue relating to the feature, causing impact. We're determining a timeline for the re-enablement of the feature.
Scope of impact: Any user prompting Copilot Chat to draft an email message may be impacted.
Root cause: We've disabled the "Edit in Outlook" feature in Copilot Chat while we implement a fix for a separate service issue relating to the feature, causing impact.
Next update by: Saturday, January 24, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Jan 15 13:58:01 2026 |
|---|
| Description: | Title: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message
User impact: Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message.
More info: When users prompt Copilot Chat to draft an email message, the button to "Edit in Outlook" doesn't appear as expected.
Current status: We're investigating a potential issue with Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1223735 - Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Nov 19 19:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 12 15:56:32 2026 |
|---|
| Root Cause: | A deployment to introduce a new calendar form contained a code issue, causing the impact. |
|---|
| Next Update: | Tuesday, February 17, 2026, at 10:30 PM UTC |
|---|
|
Details
| Time: | Thu Feb 12 15:56:32 2026 |
|---|
| Description: | Title: Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
User impact: Users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created.
More info: This issue only occurs in organizations where admins have enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes are hosted there.
When users add meeting notes from the Microsoft Teams Calendar to a meeting that has already been created, the meeting participants may not be granted permissions to view the notes, while the user that added the notes may be able to access them as expected.
Current status: We’ve completed development and validation of the long-term solution and are readying it for deployment to the affected environments. We expect it to be applied, and the issue resolved by our next scheduled update.
Scope of impact: Users scheduled in Microsoft Teams meetings where meeting notes were enabled after the meeting and in organizations where admins have enabled the ability for users to share links with "Specific People" may be affected.
Start time: Thursday, November 20, 2025, at 12:00 AM UTC
Root cause: A deployment to introduce a new calendar form contained a code issue, causing the impact.
Next update by: Tuesday, February 17, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Feb 5 15:56:50 2026 |
|---|
| Description: | Title: Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
User impact: Users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created.
More info: This issue only occurs in organizations where admins have enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes are hosted there.
When users add meeting notes from the Microsoft Teams Calendar to a meeting that has already been created, the meeting participants may not be granted permissions to view the notes, while the user that added the notes may be able to access them as expected.
Current status: We've isolated a misconfiguration which resulted in a subset of affected users to still experience impact after the problematic code was disabled. We've addressed the misconfiguration and are working with a subset of affected users to validate that our actions successfully remediated impact while we continue development of a long-term fix to remediate impact for all affected users.
Scope of impact: Users scheduled in Microsoft Teams meetings where meeting notes were enabled after the meeting and in organizations where admins have enabled the ability for users to share links with "Specific People" may be affected.
Start time: Thursday, November 20, 2025, at 12:00 AM UTC
Root cause: A deployment to introduce a new calendar form contained a code issue, causing the impact.
Next update by: Thursday, February 12, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Feb 4 16:55:34 2026 |
|---|
| Description: | Title: Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
User impact: Users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created.
More info: This issue only occurs in organizations where admins have enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes are hosted there.
When users add meeting notes from the Microsoft Teams Calendar to a meeting that has already been created, the meeting participants may not be granted permissions to view the notes, while the user that added the notes may be able to access them as expected.
Current status: While we've disabled the portion of problematic code and have received positive feedback, we have reports that this deployment remains enabled for a subset of affected users who are still experiencing impact. We're investigating why the impacting update remains enabled for some users to help complete this expedient mitigation process as we develop our long term fix.
Scope of impact: Users scheduled in Microsoft Teams meetings where meeting notes were enabled after the meeting and in organizations where admins have enabled the ability for users to share links with "Specific People" may be affected.
Root cause: A deployment to introduce a new calendar form contained a code issue, causing the impact.
Next update by: Thursday, February 5, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Feb 3 16:54:17 2026 |
|---|
| Description: | Title: Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
User impact: Users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created.
More info: This issue only occurs in organizations where admins have enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes are hosted there.
When users add meeting notes from the Microsoft Teams Calendar to a meeting that has already been created, the meeting participants may not be granted permissions to view the notes, while the user that added the notes may be able to access them as expected.
Current status: We've determined that a deployment to introduce a new calendar form contained a code issue, causing the impact. We've disabled the portion of problematic code for a subset of users and have received positive feedback indicating some users are no longer seeing impact. We're continuing with disabling the code portion for all users and, in parallel, we're validating a code fix to address this impact in the long-term.
Scope of impact: Users scheduled in Microsoft Teams meetings where meeting notes were enabled after the meeting and in organizations where admins have enabled the ability for users to share links with "Specific People" may be affected.
Root cause: A deployment to introduce a new calendar form contained a code issue, causing the impact.
Next update by: Wednesday, February 4, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 16:15:12 2026 |
|---|
| Description: | Title: Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
User impact: Users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created.
More info: This issue only occurs in organizations where admins have enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes are hosted there.
When users add meeting notes from the Microsoft Teams Calendar to a meeting that has already been created, the meeting participants may not be granted permissions to view the notes, while the user that added the notes may be able to access them as expected.
Current status: Our testing with affected users is requiring more time than originally expected. Our internal service telemetry reports that over half of impacted users now have the deployment disabled, and we're awaiting validations if impact has been resolved.
Scope of impact: Users scheduled in Microsoft Teams meetings where meeting notes were enabled after the meeting and in organizations where admins have enabled the ability for users to share links with "Specific People" may be affected.
Next update by: Tuesday, February 3, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Jan 30 16:17:45 2026 |
|---|
| Description: | Title: Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
User impact: Users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created.
More info: This issue only occurs in organizations where admins have enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes are hosted there.
When users add meeting notes from the Microsoft Teams Calendar to a meeting that has already been created, the meeting participants may not be granted permissions to view the notes, while the user that added the notes may be able to access them as expected.
Current status: We've reproduced the issue within our internal test environment, and identified a recent service deployment that we suspect may be have introduced the latent code misconfiguration. We've disabled the suspected service deployment for a subset of affected users, who we're testing with to validate our theory prior to broadly implementing this action.
Scope of impact: Users scheduled in Microsoft Teams meetings where meeting notes were enabled after the meeting and in organizations where admins have enabled the ability for users to share links with "Specific People" may be affected.
Next update by: Monday, February 2, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Jan 29 16:05:39 2026 |
|---|
| Description: | Title: Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
User impact: Users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created.
More info: This issue only occurs in organizations where admins have enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes are hosted there.
When users add meeting notes from the Microsoft Teams Calendar to a meeting that has already been created, the meeting participants may not be granted permissions to view the notes, while the user that added the notes may be able to access them as expected.
Current status: We're continuing our attempts to reproduce the issue in our test environment to better understand the root cause and next steps. While our remediation efforts are ongoing, users can workaround this issue for single instances by updating anything in the title or body of the event. This only remediates impact for the single meeting, and editing each meeting title for any reoccurring meeting is required, if editing a series event.
Scope of impact: Users scheduled in Microsoft Teams meetings where meeting notes were enabled after the meeting and in organizations where admins have enabled the ability for users to share links with "Specific People" may be affected.
Next update by: Friday, January 30, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jan 28 15:12:55 2026 |
|---|
| Description: | Title: Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
User impact: Users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created.
More info: This issue only occurs in organizations where admins have enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes are hosted there.
When users add meeting notes from the Microsoft Teams Calendar to a meeting that has already been created, the meeting participants may not be granted permissions to view the notes, while the user that added the notes may be able to access them as expected.
Current status: We've reproduced the impact using our testing environment and identified a latent code misconfiguration that's causing the impact. We're developing a code fix to correct the misconfiguration and will provide a timeline for the completion of the fix as one becomes available.
Scope of impact: Users scheduled in Microsoft Teams meetings where meeting notes were enabled after the meeting and in organizations where admins have enabled the ability for users to share links with "Specific People" may be affected.
Next update by: Thursday, January 29, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Jan 28 14:52:53 2026 |
|---|
| Description: | Title: Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
User impact: Users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created.
More info: This issue only occurs in organizations where admins have enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes are hosted there.
When users add meeting notes from the Microsoft Teams Calendar to a meeting that has already been created, the meeting participants may not be granted permissions to view the notes, while the user that added the notes may be able to access them as expected.
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.
|
|---|
|
EX1227432 - Some users' legitimate email messages may be marked as phishing and quarantined in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 4 19:26:00 2026 |
|---|
| End Time: | Thu Feb 12 09:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Networking Issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Feb 12 14:15:41 2026 |
|---|
| Root Cause: | The email messages are getting incorrectly marked as phishing and quarantined in Exchange Online due to ever-evolving criteria aimed at identifying suspicious email messages, as spam and phishing techniques have become more sophisticated in avoiding detection. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 12 14:15:41 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing and quarantined in Exchange Online
User impact: Users' legitimate email messages may have been marked as phishing and quarantined in Exchange Online.
More info: Users can expect messages which were previously quarantined by this incident to have been successfully delivered.
Final status: We’ve validated the successful release of the small portion of remaining messages and confirmed the impact associated with this incident is now resolved.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may have been impacted.
Start time: Thursday, February 5, 2026, at 12:26 AM UTC
End time: Thursday, February 12, 2026, at 2:00 PM UTC
Preliminary root cause: An updated URL rule intending to identify more sophisticated spam and phishing email messages was incorrectly quarantining legitimate email messages in Exchange Online.
Next steps: We're reviewing our ongoing URL rule implementation processes to find ways to reduce similar false positive detections in the future while continuing to adapt and respond to evolving spam and phishing techniques.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Thu Feb 12 11:46:35 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing and quarantined in Exchange Online
User impact: Users' legitimate email messages may be marked as phishing and quarantined in Exchange Online.
More info: Users may see some previously quarantined messages successfully delivered; however, some messages may still be impacted until the issue is fully resolved.
Current status: We’re carefully reviewing a small portion of messages which remain in quarantine to assess the final actions needed as we near the completion of the restoration process.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, February 5, 2026, at 12:26 AM UTC
Preliminary root cause: An updated URL rule intending to identify more sophisticated spam and phishing email messages is incorrectly quarantining legitimate email messages in Exchange Online, resulting in impact.
Next update by: Thursday, February 12, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Feb 12 00:17:27 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing and quarantined in Exchange Online
User impact: Users' legitimate email messages may be marked as phishing and quarantined in Exchange Online.
More info: Users may see some previously quarantined messages successfully delivered; however, some messages may still be impacted until the issue is fully resolved.
Current status: We’ve continued to make progress restoring previously affected email messages. We’re actively monitoring the restoration process and taking targeted actions to address any remaining blockers.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, February 5, 2026, at 12:26 AM UTC
Preliminary root cause: An updated URL rule intending to identify more sophisticated spam and phishing email messages is incorrectly quarantining legitimate email messages in Exchange Online, resulting in impact.
Next update by: Thursday, February 12, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Feb 11 19:31:17 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing and quarantined in Exchange Online
User impact: Users' legitimate email messages may be marked as phishing and quarantined in Exchange Online.
More info: Users may see some previously quarantined messages successfully delivered; however, some messages may still be impacted until the issue is fully resolved.
Current status: We've confirmed that no additional messages are being quarantined due to this incident, and we’re proceeding with our work to incrementally release those messages which were previously affected.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, February 5, 2026, at 12:26 AM UTC
Preliminary root cause: An updated URL rule intending to identify more sophisticated spam and phishing email messages is incorrectly quarantining legitimate email messages in Exchange Online, resulting in impact.
Next update by: Thursday, February 12, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Tue Feb 10 19:00:56 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing and quarantined in Exchange Online
User impact: Users' legitimate email messages may be marked as phishing and quarantined in Exchange Online.
More info: Users may see some previously quarantined messages successfully delivered; however, some messages may still be impacted until the issue is fully resolved.
Current status: We’re actively working on unblocking legitimate URLs and releasing quarantined messages. As we progress through these workstreams, some impacted accounts will see legitimate email messages returning to their inboxes from quarantine.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, February 5, 2026, at 12:26 AM UTC
Preliminary root cause: An updated URL rule intending to identify more sophisticated spam and phishing email messages is incorrectly quarantining legitimate email messages in Exchange Online, resulting in impact.
Next update by: Thursday, February 12, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 18:34:22 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing and quarantined in Exchange Online
User impact: Users' legitimate email messages may be marked as phishing and quarantined in Exchange Online.
More info: Users may see some previously quarantined messages successfully delivered; however, some messages may still be impacted until the issue is fully resolved.
Current status: We discovered an issue when unblocking some legitimate URLs which we must resolve prior to releasing the quarantined messages. We’re working on addressing the blocker so we can proceed with unblocking the legitimate URLs and releasing the quarantined messages to remediate.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Start time: Thursday, February 5, 2026, at 12:26 AM UTC
Preliminary root cause: An updated URL rule intending to identify more sophisticated spam and phishing email messages is incorrectly quarantining legitimate email messages in Exchange Online, resulting in impact.
Next update by: Wednesday, February 11, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Sat Feb 7 15:20:01 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing and quarantined in Exchange Online
User impact: Users' legitimate email messages may be marked as phishing and quarantined in Exchange Online.
Current status: We’re reviewing the release of quarantined messages for affected users and working on confirming legitimate URLs are unblocked. Some users may see their previously quarantined messages successfully delivered and we’re working to confirm full remediation. We’ll provide an estimated time to resolve when one becomes available.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Preliminary root cause: An updated URL rule intending to identify more sophisticated spam and phishing email messages is incorrectly quarantining legitimate email messages in Exchange Online, resulting in impact.
Next update by: Tuesday, February 10, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Feb 6 22:50:26 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing email and quarantined in Exchange Online
User impact: Users' legitimate email messages may be marked as phishing email and quarantined in Exchange Online.
Current status: We're continuing to review our logging and detection components to ensure our current mitigation strategy fully remediates the impact. In the meantime, we're releasing quarantined messages for affected users and unblocking URLs as our investigation progresses.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Root cause: The email messages are getting incorrectly marked as phishing and quarantined in Exchange Online due to ever-evolving criteria aimed at identifying suspicious email messages, as spam and phishing techniques have become more sophisticated in avoiding detection.
Next update by: Saturday, February 7, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Feb 6 21:22:02 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing email and quarantined in Exchange Online
User impact: Users' legitimate email messages may be marked as phishing email and quarantined in Exchange Online.
Current status: While monitoring the process of releasing the quarantined messages for the affected users, we received fresh reports of quarantined messages from a subset of affected users. We're reviewing the logging and impact details provided by this subset of users to help us determine how we can adjust our current mitigation strategy to ensure full remediation for all affected environments.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Root cause: The email messages are getting incorrectly marked as phishing and quarantined in Exchange Online due to ever-evolving criteria aimed at identifying suspicious email messages, as spam and phishing techniques have become more sophisticated in avoiding detection.
Next update by: Saturday, February 7, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Fri Feb 6 05:29:10 2026 |
|---|
| Description: | Title: Some users' legitimate email messages may be marked as phishing email and quarantined in Exchange Online
User impact: Users' legitimate email messages may be marked as phishing email and quarantined in Exchange Online.
Current status: We're continuing to release the quarantined messages for the affected users to fully resolve this problem. In parallel, we're actively working to evaluate additional remediation actions to perform in order to expedite the process of recovery.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Root cause: The email messages are getting incorrectly marked as phishing and quarantined in Exchange Online due to ever-evolving criteria aimed at identifying suspicious email messages, as spam and phishing techniques have become more sophisticated in avoiding detection.
Next update by: Saturday, February 7, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Feb 6 00:04:50 2026 |
|---|
| Description: | Title: Some users' legitimate email messages are being marked as phish and quarantined in Exchange Online
User impact: Users' legitimate email messages are being marked as phish and quarantined in Exchange Online.
Current status: We expect that the issue is resolved for any new messages as a result of adding the affected URLs to the allow list and we’re continuing the process of working with support to collect the necessary data to release the quarantine messages to fully resolve this problem. We’ll provide an estimate for the completion of this process when available.
Scope of impact: Your organization is affected by this event, and some users attempting to send or receive Exchange Online email messages are impacted.
Root cause: The email messages are getting incorrectly marked as phish and quarantined in Exchange Online due to ever-evolving criteria aimed at identifying suspicious email messages, as spam and phishing techniques have become more sophisticated in avoiding detection.
Next update by: Friday, February 6, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Thu Feb 5 20:03:38 2026 |
|---|
| Description: | Title: Some users' legitimate email messages are being marked as phish and quarantined in Exchange Online
User impact: Users' legitimate email messages are being marked as phish and quarantined in Exchange Online.
Current status: We’ve added the associated URLs for the affected email messages to the allow list to resolve further impact from occurring. We’re now in the process of releasing the affected quarantined email messages to fully resolve the issue. Additionally, we anticipate that we’ll be able to provide a remediation timeline by the time of our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and some users attempting to send or receive Exchange Online email messages are impacted.
Root cause: The email messages are getting incorrectly marked as phish and quarantined in Exchange Online due to ever-evolving criteria aimed at identifying suspicious email messages, as spam and phishing techniques have become more sophisticated in avoiding detection.
Next update by: Friday, February 6, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Thu Feb 5 12:36:47 2026 |
|---|
| Description: | Title: Some users' legitimate email messages are being marked as phish and quarantined in Exchange Online
User impact: Users' legitimate email messages are being marked as phish and quarantined in Exchange Online.
Current status: We've determined that the URLs associated with these email messages are incorrectly marked as phish and quarantined in Exchange Online due to ever-evolving criteria aimed at identifying suspicious email messages, as spam and phishing techniques have become more sophisticated in avoiding detection. We've added the associated URLs for these affected email messages to an allow list and are currently monitoring as these actions reflect within our service. After we confirm these URLs have successfully been allowed, we'll conduct final testing with a subset of users in order to validate that this has remediated impact.
Scope of impact: Your organization is affected by this event, and some users attempting to send or receive Exchange Online email messages are impacted.
Root cause: The email messages are getting incorrectly marked as phish and quarantined in Exchange Online due to ever-evolving criteria aimed at identifying suspicious email messages, as spam and phishing techniques have become more sophisticated in avoiding detection.
Next update by: Friday, February 6, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Thu Feb 5 10:32:52 2026 |
|---|
| Description: | Title: Some users' legitimate email messages are being marked as phish and quarantined in Exchange Online
User impact: Users' legitimate email messages are being marked as phish and quarantined in Exchange Online.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to send or receive Exchange Online email messages are impacted.
Next update by: Thursday, February 5, 2026, at 5:30 PM UTC
|
|---|
|
CP1231196 - Users may automatically receive the Frontline Agent (Preview) in Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 11 02:00:00 2026 |
|---|
| End Time: | Thu Feb 12 13:22:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 12 14:02:48 2026 |
|---|
| Root Cause: | A recent update to the Frontline Agent (Preview) resulted in it auto-installing for users with Copilot licenses. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 12 14:02:48 2026 |
|---|
| Description: | Title: Users may automatically receive the Frontline Agent (Preview) in Microsoft Copilot (Microsoft 365)
User impact: Users may have automatically received the Frontline Agent (Preview) in Copilot even though they didn't select it.
Final status: We've completed our deployment to remediate the issue resulting in the Frontline Agent (Preview) being auto-installed for users and confirmed after testing that this successfully resolved the issue.
Scope of impact: This issue may have affected any user with a Copilot license.
Start time: Wednesday, February 11, 2026, at 7:00 AM UTC
End time: Thursday, February 12, 2026, at 6:22 PM UTC
Root cause: A recent update to the Frontline Agent (Preview) resulted in it auto-installing for users with Copilot licenses.
Next steps:
- We're continuing work to now unblock this agent so users who previously installed it manually, or who in the future want to install it manually will be able to do so.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 12 12:40:20 2026 |
|---|
| Description: | Title: Users may automatically receive the Frontline Agent (Preview) in Microsoft Copilot (Microsoft 365)
User impact: Users may automatically receive the Frontline Agent (Preview) in Copilot even though they didn't select it.
Current status: We've identified that a recent update to the Frontline Agent (Preview) resulted in it auto-installing for users with Copilot licenses. We're working to develop a fix to revert this change. While we work on the overall remediation, we're preparing to block this agent to ensure no further users receive the agent. While blocked, users who have already installed the agent will be unable to use the agent.
Scope of impact: This issue may affect any user with a Copilot license.
Start time: Wednesday, February 11, 2026, at 7:00 AM UTC
Root cause: A recent update to the Frontline Agent (Preview) resulted in it auto-installing for users with Copilot licenses.
Next update by: Thursday, February 12, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Feb 12 12:33:55 2026 |
|---|
| Description: | Title: Users may automatically receive the Frontline Agent (Preview) in Microsoft Copilot (Microsoft 365)
User impact: Users may automatically receive the Frontline Agent (Preview) in Copilot even though they didn't select it.
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.
|
|---|
|
TM1230723 - Some users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 10 14:00:00 2026 |
|---|
| End Time: | Wed Feb 11 22:20:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 12 12:32:46 2026 |
|---|
| Root Cause: | A recent service change has introduced a mismatch regression when processing Microsoft Teams async operations. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 12 12:32:46 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams
User impact: Users may have been intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams.
Final status: We've completed our monitoring period of service telemetry and validated that our fix deployment successfully remediated user impact.
Scope of impact: Some users attempting to create teams via the Microsoft Graph Create team API may have been impacted.
Start time: Tuesday, February 10, 2026, at 7:00 PM UTC
End time: Thursday, February 12, 2026, at 3:20 AM UTC
Root cause: A recent service change has introduced a mismatch regression when processing Microsoft Teams async operations.
Next steps:
- We're analyzing the offending service change to validate why the potential for impact wasn't caught during our update testing and validation phases. This analysis will help us to bolster our validation processes to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 12 10:48:51 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams
User impact: Users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams.
Current status: We're continuing to monitor the positive improvement in our service telemetry for creating teams as the fix saturates throughout the affected environment.
Scope of impact: Some users attempting to create Microsoft Teams via the Microsoft Graph Create team API may be impacted.
Start time: Tuesday, February 10, 2026, at 7:00 PM UTC
Root cause: A recent service change has introduced a mismatch regression when processing Microsoft Teams async operations.
Next update by: Thursday, February 12, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Feb 11 22:30:53 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams
User impact: Users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams.
Current status: As the fix deployment continues to propagate throughout the affected environment, our initial review of internal telemetry indicates that the issue is beginning to subside. We anticipate that the aforementioned deployment will have saturated throughout the majority of the impacted service environment prior to our next scheduled update, incrementally resolving the issue for affected users.
Scope of impact: Some users attempting to create Microsoft Teams via the Microsoft Graph Create team API may be impacted.
Start time: Tuesday, February 10, 2026, at 7:00 PM UTC
Root cause: A recent service change has inadvertently introduced a mismatch regression when processing Microsoft Teams async operations.
Next update by: Thursday, February 12, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Wed Feb 11 20:25:33 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams
User impact: Users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams.
Current status: We're continuing to monitor the deployment of our fix, which is taking longer than initially expected and has reached roughly 70 percent saturation.
Scope of impact: Some users attempting to create Microsoft Teams via the Microsoft Graph Create team API may be impacted.
Start time: Tuesday, February 10, 2026, at 7:00 PM UTC
Root cause: A recent service change has inadvertently introduced a mismatch regression when processing Microsoft Teams async operations.
Next update by: Thursday, February 12, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Feb 11 13:16:11 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams
User impact: Users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams.
Current status: We’ve developed a code fix to remediate this issue and are deploying it across the affected environments. The deployment has reached approximately 50 percent saturation, and we’re monitoring its progress as it continues to roll out. We expect deployment to complete by our next scheduled update.
Scope of impact: Some users attempting to create Microsoft Teams via the Microsoft Graph Create team API may be impacted.
Start time: Tuesday, February 10, 2026, at 7:00 PM UTC
Root cause: A recent service change has inadvertently introduced a mismatch regression when processing Microsoft Teams async operations.
Next update by: Thursday, February 12, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Feb 11 10:07:50 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams
User impact: Users may be intermittently unable to use the Microsoft Teams API in Microsoft Graph to create teams.
Current status: We've identified that a recent service change has inadvertently introduced a mismatch regression when processing Microsoft Teams async operations, which has impacted the ability to retrieve operation status' causing the inability to create teams in Microsoft Teams using the API in Microsoft Graph. We're assessing various mitigation strategies to apply in order to swiftly remediate impact.
Scope of impact: Some users attempting to create Microsoft Teams via the Microsoft Graph Create team API may be impacted.
Root cause: A recent service change has inadvertently introduced a mismatch regression when processing Microsoft Teams async operations.
Next update by: Wednesday, February 11, 2026, at 7:00 PM UTC
|
|---|
|
PB1231052 - Some users may have experienced delays opening Capacity Settings and workspace licence information in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 11 23:40:00 2026 |
|---|
| End Time: | Thu Feb 12 02:30:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 12 04:59:25 2026 |
|---|
| Root Cause: | A section of Power BI service infrastructure that facilitates Capacity Settings and workspace licence information in Microsoft Fabric was performing below acceptable performance thresholds due to an unexpected spike in user traffic. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 12 04:59:25 2026 |
|---|
| Description: | Title: Some users may have experienced delays opening Capacity Settings and workspace licence information in Microsoft Fabric
User impact: Users may have experienced delays when opening Capacity Settings and workspace licence information in Microsoft Fabric.
More info: Users may have experienced issues with the following scenarios:
- Loading the admin portal
- Rendering the Capacity Metrics app
- Accessing license information in Workspace settings
Final status: We identified that a section of Power BI service infrastructure that facilitates Capacity Settings and workspace licence information in Microsoft Fabric was performing below acceptable performance thresholds due to an unexpected spike in user traffic. We've reverted the service to the last healthy version and can confirm after a period of monitoring service telemetry that impact is remediated.
Scope of impact: Impact was specific to some users attempting to open Capacity Settings or workspace licence information in Microsoft Fabric.
Start time: Thursday, February 12, 2026, at 4:40 AM UTC
End time: Thursday, February 12, 2026, at 7:30 AM UTC
Root cause: A section of Power BI service infrastructure that facilitates Capacity Settings and workspace licence information in Microsoft Fabric was performing below acceptable performance thresholds due to an unexpected spike in user traffic.
Next steps:
- We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 12 02:58:38 2026 |
|---|
| Description: | Title: Some users may experience delays when opening Capacity Settings and workspace licence information in Microsoft Fabric
User impact: Users may experience delays when opening Capacity Settings and workspace licence information in Microsoft Fabric.
More info: Users may experience issues with the following scenarios:
- Loading the admin portal
- Rendering the Capacity Metrics app
- Accessing license information in Workspace settings
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to open Capacity Settings or workspace licence information in Microsoft Fabric.
Next update by: Thursday, February 12, 2026, at 10:00 AM UTC
|
|---|
|
MV1230913 - Some users may not be able to access the Communities section and receive an error in Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 11 17:15:00 2026 |
|---|
| End Time: | Wed Feb 11 19:05:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 11 19:45:51 2026 |
|---|
| Root Cause: | A recent update to the Microsoft Viva Engage infrastructure inadvertently removed a configuration property responsible for facilitating access to the Communities section, which led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 11 19:45:51 2026 |
|---|
| Description: | Title: Some users may not be able to access the Communities section and receive an error in Microsoft Viva Engage
User impact: Users may not have been able to access the Communities section and received an error in Microsoft Viva Engage.
More info: The error stated that "Communities aren't loading right now. Please try again".
Final status: We've confirmed that the roll back of the update successfully completed, and after monitoring the service health, we've confirmed that impact has been remediated.
Scope of impact: Any user may have been impacted by this event, and may not have been able to access the Communities section and received and error.
Start time: Wednesday, February 11, 2026, at 10:15 PM UTC
End time: Thursday, February 12, 2026, at 12:05 AM UTC
Root cause: A recent update to the Microsoft Viva Engage infrastructure inadvertently removed a configuration property responsible for facilitating access to the Communities section, which led to impact.
Next steps:
- We're reviewing our update testing processes and assessing whether additional monitoring can be added to help identify sooner and prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 11 19:24:56 2026 |
|---|
| Description: | Title: Some users may not be able to access the Communities section and receive an error in Microsoft Viva Engage
User impact: Users may not be able to access the Communities section and receive an error in Microsoft Viva Engage.
More info: The error states that "Communities aren't loading right now. Please try again".
Current status: We were made aware of this issue from internal reports indicating that users may not be able to access the Communities section and receive an error. Upon investigating, we identified a recent update to the service removed a configuration property responsible for facilitating access to the Communities section, leading to impact. We're reverting this change to resolve this issue, after which we’ll monitor our service health telemetry to confirm that impact is remediated.
Scope of impact: Any user may have been impacted by this event, and may not be able to access the Communities section and receive and error. This section may be updated as our investigation continues.
Start time: Wednesday, February 11, 2026, at 10:15 PM UTC
Root cause: A recent update to the Microsoft Viva Engage infrastructure inadvertently removed a configuration property responsible for facilitating access to the Communities section, leading to impact.
Next update by: Thursday, February 12, 2026, at 1:30 AM UTC
|
|---|
|
EX1228240 - Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Feb 6 13:45:07 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 11 14:42:34 2026 |
|---|
| Root Cause: | A routing change for Autodiscover requests introduced a header duplication issue causing a backlog of requests that ultimately fail or timeout, resulting in the impact. |
|---|
| Next Update: | Wednesday, February 18, 2026, at 2:00 AM UTC |
|---|
|
Details
| Time: | Wed Feb 11 14:42:34 2026 |
|---|
| Description: | Title: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes
User impact: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes.
More info: This issue is specific to the Outlook desktop client in organizations with a hybrid environment using Exchange Web Services (EWS) for MailTips. Users may notice that the MailTips free/busy feature isn’t operating as expected and may see an error stating “we can’t show MailTips right now.”
The Outlook desktop crashes occur when attempting to add a new on-premises mailbox.
Admins may be unable to create new on-premises mailboxes, and their cross-tenant AutoDiscover requests general may fail from hybrid environments.
While we work on deploying the fix, admins may be able to mitigate the impact by restarting the Autodiscover app pool.
Current status: Our monitoring of the deployment of the fix to prevent the header duplication issue indicates that the majority of admins should be experiencing remediation, and we're beginning to validate impact resolution with a subset of affected admins as the saturation of the fix fully completes.
Scope of impact: Any admins’ cross-tenant AutoDiscover requests may fail from hybrid environments, causing MailTips free/busy not to show and crashing for users’ Outlook desktop clients when adding additional on-premises mailboxes. This information may be updated as our investigation continues.
Start time: Tuesday, January 27, 2026, at 12:30 AM UTC
Root cause: A routing change for Autodiscover requests introduced a header duplication issue causing a backlog of requests that ultimately fail or timeout, resulting in the impact.
Next update by: Wednesday, February 18, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 13:51:34 2026 |
|---|
| Description: | Title: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes
User impact: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes.
More info: This issue is specific to the Outlook desktop client in organizations with a hybrid environment using Exchange Web Services (EWS) for MailTips. Users may notice that the MailTips free/busy feature isn’t operating as expected and may see an error stating “we can’t show MailTips right now.”
The Outlook desktop crashes occur when attempting to add a new on-premises mailbox.
Admins may be unable to create new on-premises mailboxes, and their cross-tenant AutoDiscover requests general may fail from hybrid environments.
While we work on deploying the fix, admins may be able to mitigate the impact by restarting the Autodiscover app pool.
Current status: We've developed a fix that will prevent the header duplication issue from occurring and have begun deploying the fix to the Exchange Online versions 15.20.9587.019, 15.20.9632.004, 15.20.9611.008, and 15.20.9564.022. As the fix saturates, admins will begin to gradually notice impact remediation, and we expect that the fix will complete deployment by the time of our next update.
Scope of impact: Any admins’ cross-tenant AutoDiscover requests may fail from hybrid environments, causing MailTips free/busy not to show and crashing for users’ Outlook desktop clients when adding additional on-premises mailboxes. This information may be updated as our investigation continues.
Start time: Tuesday, January 27, 2026, at 12:30 AM UTC
Root cause: A routing change for Autodiscover requests introduced a header duplication issue causing a backlog of requests that ultimately fail or timeout, resulting in the impact.
Next update by: Wednesday, February 11, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Feb 6 20:41:31 2026 |
|---|
| Description: | Title: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes
User impact: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes.
More info: This issue is specific to the Outlook desktop client in organizations with a hybrid environment using Exchange Web Services (EWS) for MailTips. Users may notice that the MailTips free/busy feature isn’t operating as expected and may see an error stating “we can’t show MailTips right now.”
The Outlook desktop crashes occur when attempting to add a new on-premise mailbox.
Admins may be unable to create new on-premise mailboxes and their cross-tenant AutoDiscover requests general may fail from hybrid environments.
Current status: We’ve determined that a routing change for Autodiscover requests introduced a header duplication issue causing a backlog of requests that ultimately fail or timeout, resulting in the impact. We’ve confirmed that, in addition to AutoDiscover failures and Outlook crashes, users may experience the MailTips free/busy feature isn’t operating as expected and may see an error stating “we can’t show MailTips right now.” As we develop a fix to address this issue, affected admins may be able to mitigate the impact by recycling the Autodiscover application pool. We anticipate having an estimation for the delivery of the permanent fix to resolve this issue by our next scheduled update.
Scope of impact: Any admins’ cross-tenant AutoDiscover requests may fail from hybrid environments, causing MailTips free/busy not to show and crashing for users’ Outlook desktop clients when adding additional on-premises mailboxes. This information may be updated as our investigation continues.
Start time: Tuesday, January 27, 2026, at 12:30 AM UTC
Root cause: A routing change for Autodiscover requests introduced a header duplication issue causing a backlog of requests that ultimately fail or timeout, resulting in the impact.
Next update by: Monday, February 9, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Feb 6 18:00:16 2026 |
|---|
| Description: | Title: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes
User impact: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes.
More info: This issue is specific to the Outlook desktop client in organizations with a hybrid environment using Exchange Web Services (EWS) for MailTips. Users may notice that the MailTips free/busy feature isn’t operating as expected and may see an error stating “we can’t show MailTips right now.”
The Outlook desktop crashes occur when attempting to add a new on-premise mailbox.
Admins may be unable to create new on-premise mailboxes and their cross-tenant AutoDiscover requests general may fail from hybrid environments.
Current status: We’re reviewing the impacted request flow and any recent changes to the service to determine the source of the errors and formulate a remediation plan.
Scope of impact: Any admins’ cross-tenant AutoDiscover requests may fail from hybrid environments, causing MailTips free/busy not to show and crashing for users’ Outlook desktop clients when adding additional on-premises mailboxes. This information may be updated as our investigation continues.
Next update by: Saturday, February 7, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Fri Feb 6 16:07:27 2026 |
|---|
| Description: | Title: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes
User impact: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes.
More info: This issue is specific to the Outlook desktop client in organizations with a hybrid environment using Exchange Web Services (EWS) for MailTips. Users may notice that the MailTips free/busy feature isn’t operating as expected and may see an error stating “we can’t show MailTips right now.”
The Outlook desktop crashes occur when attempting to add a new on-premise mailbox.
Admins may be unable to create new on-premise mailboxes and their cross-tenant AutoDiscover requests general may fail from hybrid environments.
Current status: We’re continuing to analyze system logs and telemetry to determine the source of what we suspect is preventing specific AutoDiscover requests from being processed as expected, causing on-premises service requests to accumulate, and some requests to intermittently fail, leading to the impact.
Scope of impact: Any admins’ cross-tenant AutoDiscover requests may fail from hybrid environments, causing MailTips free/busy not to show and crashing for users’ Outlook desktop clients when adding additional on-premises mailboxes. This information may be updated as our investigation continues.
Next update by: Friday, February 6, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Feb 6 14:19:43 2026 |
|---|
| Description: | Title: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes
User impact: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes.
More info: This issue is specific to the Outlook desktop client in organizations with a hybrid environment using Exchange Web Services (EWS) for MailTips. Users may notice that the MailTips free/busy feature isn’t operating as expected and may see an error stating “we can’t show MailTips right now.”
The Outlook desktop crashes occur when attempting to add a new on-premise mailbox.
Admins may be unable to create new on-premise mailboxes and their cross-tenant AutoDiscover requests general may fail from hybrid environments.
Current status: We’re reviewing system logs to isolate the origin of this issue.
Scope of impact: Any admins’ cross-tenant AutoDiscover requests may fail from hybrid environments, causing MailTips free/busy not to show and crashing for users’ Outlook desktop clients when adding additional on-premises mailboxes. This information may be updated as our investigation continues.
Next update by: Friday, February 6, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Feb 6 14:01:42 2026 |
|---|
| Description: | Title: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes
User impact: Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes.
More info: This issue is specific to the Outlook desktop client in organizations with a hybrid environment using Exchange Web Services (EWS) for MailTips. Users may notice that the MailTips free/busy feature isn’t operating as expected and may see an error stating “we can’t show MailTips right now.”
The Outlook desktop crashes occur when attempting to add a new on-premise mailbox.
Admins may be unable to create new on-premise mailboxes and their cross-tenant AutoDiscover requests general may fail from hybrid environments.
Current status: We're investigating a potential issue in which admins' cross-tenant AutoDiscover requests may fail from hybrid environments and Outlook desktop crashes when adding additional on-premises mailboxes, and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1217690 - Some users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Dec 11 22:10:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 11 02:03:17 2026 |
|---|
| Root Cause: | A latent code issue is affecting the request flow leveraged for SharePoint Online list link access within Microsoft Teams on iOS, resulting in impact. |
|---|
| Next Update: | Wednesday, February 25, 2026, at 10:00 AM UTC |
|---|
|
Details
| Time: | Wed Feb 11 01:20:33 2026 |
|---|
| Description: | Title: Some users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error
User impact: Users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error
More info: Specifically, users attempting to access SharePoint lists through Teams on iOS may receive an access permissions error stating: "Permission required - You do not have permission to open this file."
While we're focused on remediation, users on iOS can access the affected pages and list links by manually copying the impacted URLs from the Teams chat to open them elsewhere. Additionally, users with access to alternative Microsoft Teams access methods such as the Microsoft Teams desktop client and web app can use these to avoid impact.
Current status: The update containing the fix is still scheduled to be available by the end of February 2026, and we expect to be able to provide a confirmed release timeline by our next scheduled communications update.
Scope of impact: Any users attempting to access SharePoint lists through links shared on Microsoft Teams while on iOS may be impacted. This information may be updated as our investigation continues.
Start time: Friday, December 12, 2025, at 3:10 AM UTC
Root cause: A latent code issue is affecting the request flow leveraged for SharePoint Online list link access within Microsoft Teams on iOS, resulting in impact.
Next update by: Wednesday, February 25, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Jan 28 02:50:14 2026 |
|---|
| Description: | Title: Some users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error
User impact: Users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error
More info: Specifically, users attempting to access SharePoint lists through Teams on iOS may receive an access permissions error stating: "Permission required - You do not have permission to open this file."
While we're focused on remediation, users on iOS can access the affected pages and list links by manually copying the impacted URLs from the Teams chat to open them elsewhere. Additionally, users with access to alternative Microsoft Teams access methods such as the Microsoft Teams desktop client and web app can use these to avoid impact.
Current status: We’ve successfully developed the fix, which is planned for release as part of the iOS client version 8.2x. We expect this update to be available by the end of February 2026 and will share a confirmed release timeline once it’s finalized.
Scope of impact: Any users attempting to access SharePoint lists through links shared on Microsoft Teams while on iOS may be impacted. This information may be updated as our investigation continues.
Root cause: A latent code issue is affecting the request flow leveraged for SharePoint Online list link access within Microsoft Teams on iOS, resulting in impact.
Next update by: Wednesday, February 11, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Wed Jan 14 03:43:28 2026 |
|---|
| Description: | Title: Some users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error
User impact: Users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error.
More info: Specifically, users attempting to access SharePoint lists through Teams on iOS may receive an access permissions error stating: "Permission required - You do not have permission to open this file."
While we're focused on remediation, users on iOS can access the affected pages and list links by manually copying the impacted URLs from the Teams chat to open them elsewhere. Additionally, users with access to alternative Microsoft Teams access methods such as the Microsoft Teams desktop client and web app can use these to avoid impact.
Current status: We're developing a fix to correct the latent code issue but this is expected to take some time. We'll share an development timeline as part of our next update.
Scope of impact: Any users attempting to access SharePoint lists through links shared on Microsoft Teams while on iOS may be impacted. This information may be updated as our investigation continues.
Root cause: A latent code issue is affecting the request flow leveraged for SharePoint Online list link access within Microsoft Teams on iOS, resulting in impact.
Next update by: Wednesday, January 28, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Wed Jan 14 00:47:18 2026 |
|---|
| Description: | Title: Some users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error
User impact: Users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error.
More info: Specifically, users attempting to access SharePoint lists through Teams on iOS may receive an access permissions error stating: "Permission required - You do not have permission to open this file."
While we're focused on remediation, users on iOS can access the affected pages and list links by manually copying the impacted URLs from the Teams chat to open them elsewhere. Additionally, users with access to alternative Microsoft Teams access methods such as the Microsoft Teams desktop client and web app can use these to avoid impact.
Current status: We've determined that a latent code issue is affecting the request flow leveraged for SharePoint Online list link access within Microsoft Teams on iOS, resulting in impact. We're proceeding with further analysis to determine our options for remediation.
Scope of impact: Any users attempting to access SharePoint lists through links shared on Microsoft Teams while on iOS may be impacted. This information may be updated as our investigation continues.
Root cause: A latent code issue is affecting the request flow leveraged for SharePoint Online list link access within Microsoft Teams on iOS, resulting in impact.
Next update by: Wednesday, January 14, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Wed Jan 14 00:34:55 2026 |
|---|
| Description: | Title: Users aren't able to open SharePoint Online lists through Microsoft Teams on iOS and receive an error
User impact: Users aren't able to open SharePoint Online lists through Microsoft Teams on iOS and receive an error.
More info: Specifically, users attempting to access SharePoint lists through Teams on iOS receive an access permissions error stating: "Permission required - You do not have permission to open this file."
While we're focused on remediation, users on iOS can access the affected pages and list links by manually copying the impacted URLs from the Teams chat to open them elsewhere. Additionally, users with access to alternative Microsoft Teams access methods such as the Microsoft Teams desktop client and web app can use these to avoid impact.
Current status: We're reviewing service logs and contextual details provided by impacted users to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Your organization is affected by this event, and users attempting to access SharePoint lists through links shared on Microsoft Teams are impacted.
Next update by: Wednesday, January 14, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Jan 14 00:12:56 2026 |
|---|
| Description: | Title: Users aren't able to open SharePoint Online lists through Microsoft Teams on iOS and receive an error
User impact: Users aren't able to open SharePoint Online lists through Microsoft Teams on iOS and receive an error.
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.
|
|---|
|
CW1226324 - Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Jan 21 02:25:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 11 00:52:24 2026 |
|---|
| Root Cause: | A code issue is allowing items in the sent items and draft folders to be picked up by Copilot even though confidential labels are set in place. |
|---|
| Next Update: | Wednesday, February 18, 2026, at 11:00 AM UTC |
|---|
|
Details
| Time: | Tue Feb 10 13:22:38 2026 |
|---|
| Description: | Title: Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat
User impact: Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat.
More info: The Microsoft 365 Copilot "work tab" Chat is summarizing email messages even though these email messages have a sensitivity label applied and a DLP policy is configured.
Current status: Deployment of our fix to remediate incorrect processing of email messages with a confidential label by Microsoft 365 Copilot chat is ongoing, and we're reaching out to a subset of affected users to test for impact remediation as our rollout saturates across affected environments. We aim to provide a timeline to remediation as one becomes available.
Scope of impact: Your organization is affected by this event, and users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 7:25 AM UTC
Root cause: A code issue is allowing items in the sent items and draft folders to be picked up by Copilot even though confidential labels are set in place.
Next update by: Wednesday, February 18, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Feb 3 05:41:13 2026 |
|---|
| Description: | Title: Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat
User impact: Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat.
More info: The Microsoft 365 Copilot "work tab" Chat is summarizing email messages even though these email messages have a sensitivity label applied and a DLP policy is configured.
Current status: We've identified a code issue that is allowing items in the sent items and draft folders to be picked up by Copilot even though confidential labels are set in place. We've developed and started to deploy a fix to mitigate impact.
Scope of impact: Your organization is affected by this event, and users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat. This section may be updated as our investigation continues.
Root cause: A code issue is allowing items in the sent items and draft folders to be picked up by Copilot even though confidential labels are set in place.
Next update by: Tuesday, February 10, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Feb 3 03:49:51 2026 |
|---|
| Description: | Title: Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat
User impact: Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat.
More info: The Microsoft 365 Copilot "work tab" Chat is summarizing email messages even though these email messages have a sensitivity label applied and a DLP policy is configured.
Current status: We're continuing our review of the provided case details, sample email message screenshots and all available resources to identify the root cause of impact and mitigation plan.
Scope of impact: Your organization is affected by this event, and users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat. This section may be updated as our investigation continues.
Next update by: Tuesday, February 3, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Feb 3 02:29:44 2026 |
|---|
| Description: | Title: Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat
User impact: Users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat.
More info: The Microsoft 365 Copilot "work tab" Chat is summarizing email messages even though these email messages have a sensitivity label applied and a DLP policy is configured.
Current status: We've received a report of an issue with the Microsoft 365 Copilot chat improperly summarizing email messages. We're reviewing the provided case details and sample email message screenshots to identify the underlying root cause of impact and inform our next steps.
Scope of impact: Your organization is affected by this event, and users' email messages with a confidential label applied are being incorrectly processed by Microsoft 365 Copilot chat. This section may be updated as our investigation continues.
Next update by: Tuesday, February 3, 2026, at 9:00 AM UTC
|
|---|
|
CP1229864 - Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 9 02:00:00 2026 |
|---|
| End Time: | Tue Feb 10 13:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Feb 10 20:59:05 2026 |
|---|
| Root Cause: | A portion of infrastructure responsible for Declarative Agents populating prompt responses wasn't processing requests as efficiently as expected, producing an increase in latency, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 10 20:59:05 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Copilot weren't responding to prompts.
Final status: We've completed our period of extended monitoring and confirmed the impact is remediated.
Scope of impact: Your organization was affected by this event, and some users of Declarative Agents were impacted.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
End time: Tuesday, February 10, 2026, at 6:00 PM UTC
Root cause: A portion of infrastructure responsible for Declarative Agents populating prompt responses wasn't processing requests as efficiently as expected, producing an increase in latency, which resulted in impact.
Next steps:
- To help prevent similar impact in the future, we're further reviewing the underlying cause of this portion of infrastructure not processing requests as expected.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 10 14:39:28 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Copilot aren't responding to prompts.
Current status: To ensure latency has returned to standard service levels, we’re continuing our extended monitoring to verify the issue is fully remediated.
Scope of impact: Your organization is affected by this event, and some users of Declarative Agents are impacted. This information may be updated as our investigation continues.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
Root cause: A portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact.
Next update by: Wednesday, February 11, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Feb 10 12:20:37 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Copilot aren't responding to prompts.
Current status: We're seeing notable decreases in latency from our service telemetry, but service recovery is moving slower than initially anticipated. We're extending our monitoring period to ensure full impact remediation and we anticipate this process to be completed by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users of Declarative Agents are impacted. This information may be updated as our investigation continues.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
Root cause: A portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact.
Next update by: Tuesday, February 10, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 10 08:16:02 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts.
Current status: We've reverted the previously mentioned change that was contributing to ongoing impact. We’re conducting a period of monitoring telemetry as latency decreases to ensure that the service returns to a healthy state.
Scope of impact: Your organization is affected by this event, and some users of Declarative Agents are impacted. This information may be updated as our investigation continues.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
Root cause: A portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact.
Next update by: Tuesday, February 10, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Tue Feb 10 03:08:20 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts.
Current status: While the configuration changes to rebalance resource utilization resulted in an improvement in latency, we’ve identified a potential change that may be contributing to the ongoing impact. We’re conducting a deeper analysis of this change to confirm whether it is the root cause.
Scope of impact: Your organization is affected by this event, and some users of Declarative Agents are impacted. This information may be updated as our investigation continues.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
Root cause: A portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact.
Next update by: Tuesday, February 10, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Tue Feb 10 00:26:15 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts.
Current status: We’ve completed an initial set of configuration changes to rebalance resource utilization on the affected portion of infrastructure and have observed reduced latency for the impacted requests. However, additional action may be required to fully remediate the issue, and we’re continuing analysis to determine next steps.
Scope of impact: Your organization is affected by this event, and some users of Declarative Agents are impacted. This information may be updated as our investigation continues.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
Root cause: A portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact.
Next update by: Tuesday, February 10, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 21:55:19 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts.
Current status: We're continuing to make improvements by rebalancing resources on the affected infrastructure to restore service functionality. In tandem, we’re identifying if any additional remediation actions will be needed to fully resolve this issue.
Scope of impact: Your organization is affected by this event, and some users of Declarative Agents are impacted. This information may be updated as our investigation continues.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
Root cause: A portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact.
Next update by: Tuesday, February 10, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 19:49:34 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts.
Current status: We're performing improvements and rebalancing resources on the affected infrastructure to remediate impact.
Scope of impact: Your organization is affected by this event, and some users of Declarative Agents are impacted. This information may be updated as our investigation continues.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
Root cause: A portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact.
Next update by: Tuesday, February 10, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 17:45:17 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Copilot aren't responding to prompts.
Current status: We've identified a portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact. We're further investigating the affected infrastructure to identify a fix to restore the service functionality.
Scope of impact: Your organization is affected by this event, and some users of Declarative Agents are impacted. This information may be updated as our investigation continues.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
Root cause: A portion of infrastructure responsible for Declarative Agents populating prompt responses isn't processing requests as efficiently as expected, producing an increase in latency and resulting in impact.
Next update by: Tuesday, February 10, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Feb 9 15:58:49 2026 |
|---|
| Description: | Title: Users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users’ Declarative Agents in Copilot aren't responding to prompts.
Current status: We're continuing to investigate the HAR logs to help with isolating the source of the issue.
Scope of impact: Your organization is affected by this event, and all users of Declarative Agents are impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 9, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Feb 9 14:54:28 2026 |
|---|
| Description: | Title: Users Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users Declarative Agents in Copilot aren't responding to prompts.
Current status: We're analyzing HTTP Archive format (HAR) files to help with the investigation and to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and all users attempting to use Declarative Agents are impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Feb 9 14:26:24 2026 |
|---|
| Description: | Title: Users Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
User impact: Users Declarative Agents in Copilot aren't responding to prompts.
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.
|
|---|
|
OD1229770 - Some admins may be unable to provision new Microsoft OneDrive personal sites for newly onboarded users
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 2 12:47:00 2026 |
|---|
| End Time: | Tue Feb 10 01:12:00 2026 |
|---|
| Service: | Microsoft OneDrive |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 10 13:40:30 2026 |
|---|
| Root Cause: | A recent service update which intended to modify the permissions for newly onboarded users contained a code issue, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 10 13:40:30 2026 |
|---|
| Description: | Title: Some admins may be unable to provision new Microsoft OneDrive personal sites for newly onboarded users
User impact: Admins may have been unable to provision new OneDrive personal sites for newly onboarded users.
More info: As a result, new users may have been unable to access OneDrive.
Users who were auto-provisioned by the service weren't affected.
Final status: We've identified that a recent service update, intended to modify the permissions for newly onboarded users, contained a code issue which resulted in impact. We've reverted the offending service update and confirmed through testing with affected users that the impact has been remediated.
Scope of impact: Some admins attempting to provision new OneDrive personal sites for newly onboarded users may have been impacted.
Start time: Friday, February 6, 2026, at 5:47 PM UTC
End time: Tuesday, February 10, 2026, at 6:12 AM UTC
Root cause: A recent service update which intended to modify the permissions for newly onboarded users contained a code issue, which resulted in impact.
Next steps:
- We're reviewing our update procedures to understand why impact to onboarding wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 9 20:19:55 2026 |
|---|
| Description: | Title: Some admins may be unable to provision new Microsoft OneDrive personal sites for newly onboarded users
User impact: Admins may be unable to provision new OneDrive personal sites for newly onboarded users.
More info: As a result, new users may be unable to access OneDrive.
Users who are auto-provisioned by the service aren't affected.
Current status: We’re continuing to analyze the recently collected ULS logs and are reviewing any recent changes to authentication that may have contributed to the impact to confirm our findings and determine our next troubleshooting steps.
Scope of impact: Some admins attempting to provision new OneDrive personal sites may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, February 10, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Feb 9 17:12:31 2026 |
|---|
| Description: | Title: Some admins may be unable to provision new Microsoft OneDrive personal sites for newly onboarded users
User impact: Admins may be unable to provision new OneDrive personal sites for newly onboarded users.
More info: As a result, new users may be unable to access OneDrive.
Users who are auto-provisioned by the service aren't affected.
Current status: Our roll back of the recent change we suspected may be causing the impact hasn't resolved the issue. We're continuing our review of the ULS logging collected from a reproduction of the impact conducted in our internal testing environment for any further errors or exceptions which may uncover the source of the impact.
Scope of impact: Some admins attempting to provision new OneDrive personal sites may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, February 10, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Feb 9 15:50:49 2026 |
|---|
| Description: | Title: Some admins may be unable to provision new Microsoft OneDrive personal sites for newly onboarded users
User impact: Admins may be unable to provision new OneDrive personal sites for newly onboarded users.
More info: As a result, new users may be unable to access OneDrive.
Users who are auto-provisioned by the service aren't affected.
Current status: We've identified a recent change which we suspect may be causing the impact, and we're reversing this change to check whether this resolves the issue.
Scope of impact: Some admins attempting to provision new OneDrive personal sites may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 9, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Feb 9 13:52:33 2026 |
|---|
| Description: | Title: Some admins may be unable to provision new Microsoft OneDrive personal sites for newly onboarded users
User impact: Admins may be unable to provision new OneDrive personal sites for newly onboarded users.
More info: As a result, new users may be unable to access OneDrive.
Users who are auto-provisioned by the service aren't affected.
Current status: We've identified an exception which may indicate an authentication issue, and we're further analyzing this exception to confirm whether this is the origin of the impact.
Scope of impact: Some admins attempting to provision new OneDrive personal sites may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 9, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Feb 9 11:37:22 2026 |
|---|
| Description: | Title: Some admins may be unable to provision new Microsoft OneDrive personal sites for newly onboarded users
User impact: Admins may be unable to provision new OneDrive personal sites for newly onboarded users.
More info: As a result, new users may be unable to access OneDrive.
Current status: We're expanding our investigation to include correlation IDs and request IDs provided by a sample affected user to aid our efforts in identifying the source of impact.
Scope of impact: Some admins attempting to provision new OneDrive personal sites may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 9, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Feb 9 10:31:32 2026 |
|---|
| Description: | Title: Some admins may be unable to provision new Microsoft OneDrive personal sites for newly onboarded users
User impact: Admins may be unable to provision new OneDrive personal sites for newly onboarded users.
More info: As a result, new users may be unable to access OneDrive.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some admins attempting to provision new OneDrive personal sites may be impacted. This information may be updated as our investigation continues.
Next update by: Monday, February 9, 2026, at 5:30 PM UTC
|
|---|
|
TM1226057 - Users don't see the dial pad in Microsoft Teams Rooms (MTR) for Windows devices
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 29 10:00:00 2026 |
|---|
| End Time: | Tue Feb 10 01:50:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 10 12:48:19 2026 |
|---|
| Root Cause: | A code regression in the latest build of Microsoft Teams caused the dial pad User Interface (UI) elements to been missing. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 10 12:48:19 2026 |
|---|
| Description: | Title: Users don't see the dial pad in Microsoft Teams Rooms (MTR) for Windows devices
User impact: Users may not have seen the dial pad on MTR for Windows devices.
More info: Impact was specific to users on build 25113001316 of the MTR app.
Final status: We've cleared the issue in our deployment infrastructure causing a delay and have completed the deployment of our fix. The impact has been remediated for all users.
Scope of impact: Any user on build 25113001316 of the Microsoft Teams Rooms app leveraging an MTR for Windows device may have been impacted.
Start time: Thursday, January 29, 2026, at 3:00 PM UTC
End time: Tuesday, February 10, 2026, at 6:50 AM UTC
Root cause: A code regression in the latest build of Microsoft Teams caused the dial pad User Interface (UI) elements to been missing.
Next steps:
- We're investigating how the code regression was introduced to better understand and prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 9 12:45:24 2026 |
|---|
| Description: | Title: Users may not see the dial pad in Microsoft Teams Rooms (MTR) for Windows devices
User impact: Users may not see the dial pad on MTR for Windows devices.
More info: Impact is specific to users on build 25113001316 of the MTR app.
Current status: An issue in our deployment infrastructure caused a delay, as a result the deployment has increased from 75 to 80 percent, but hasn't completed as expected. We've addressed the delay and are continuing to monitor deployment progress to confirm completion and impact resolution.
Scope of impact: Any user on build 25113001316 of the Microsoft Teams Rooms app leveraging an MTR for Windows device may be impacted. This section may be updated as the investigation progresses.
Start time: Thursday, January 29, 2026, at 3:00 PM UTC
Root cause: A code regression in the latest build of Microsoft Teams caused the dial pad User Interface (UI) elements to be missing.
Next update by: Tuesday, February 10, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Feb 6 13:26:30 2026 |
|---|
| Description: | Title: Users may not see the dial pad in Microsoft Teams Rooms (MTR) for Windows devices
User impact: Users may not see the dial pad on MTR for Windows devices.
More info: Impact is specific to users on build 25113001316 of the MTR app.
Current status: We’re continuing to monitor deployment of the fix to restore the missing UI elements on the impacted MTR app version, which has reached 75 percent saturation. As the deployment progresses, users will continue to see impact relief. Based on current estimates, we expect completion by our next scheduled update.
Scope of impact: Any user on build 25113001316 of the Microsoft Teams Rooms app leveraging an MTR for Windows device may be impacted. This section may be updated as the investigation progresses.
Start time: Thursday, January 29, 2026, at 3:00 PM UTC
Root cause: A code regression in the latest build of Microsoft Teams caused the dial pad User Interface (UI) elements to be missing.
Next update by: Monday, February 9, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Feb 5 13:30:07 2026 |
|---|
| Description: | Title: Users may not see the dial pad in Microsoft Teams Rooms (MTR) for Windows devices
User impact: Users may not see the dial pad on MTR for Windows devices.
More info: Impact is specific to users on build 25113001316 of the MTR app.
Current status: We’re continuing to monitor deployment of the fix to restore the missing UI elements on the impacted version of the MTR app, and it’s reached 50 percent saturation. As the fix progresses, users will progressively experience impact relief and based on current estimates, we expect the deployment to be complete by our next scheduled update.
Scope of impact: Any user on build 25113001316 of the Microsoft Teams Rooms app leveraging an MTR for Windows device may be impacted. This section may be updated as the investigation progresses.
Start time: Thursday, January 29, 2026, at 3:00 PM UTC
Root cause: A code regression in the latest build of Microsoft Teams caused the dial pad User Interface (UI) elements to be missing.
Next update by: Friday, February 6, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Feb 2 22:13:26 2026 |
|---|
| Description: | Title: Users may not see the dial pad in Microsoft Teams Rooms (MTR) for Windows devices
User impact: Users may not see the dial pad on MTR for Windows devices.
More info: Impact is specific to users on build 25113001316 of the MTR app.
Current status: We're continuing to monitor our deployment to restore the missing UI elements on the impacted version of the MTR app, and our projections continue to indicate impact may be fully resolved by the end of Thursday, February 5, 2026.
Scope of impact: Any user on build 25113001316 of the Microsoft Teams Rooms app leveraging an MTR for Windows device may be impacted. This section may be updated as the investigation progresses.
Start time: Thursday, January 29, 2026, at 3:00 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by the end of Thursday, February 5, 2026.
Root cause: A code regression in the latest build of Microsoft Teams caused the dial pad User Interface (UI) elements to be missing.
Next update by: Thursday, February 5, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 12:34:58 2026 |
|---|
| Description: | Title: Users may not see the dial pad in Microsoft Teams Rooms (MTR) for Windows devices
User impact: Users may not see the dial pad on MTR for Windows devices.
Current status: We've validated a code regression in a recent build of Microsoft Teams which caused the dial pad User Interface (UI) elements to be missing on MTR devices. We've expanded the scope of our communications to encompass all users potentially affected by this regression and we've updated the "Title", "User impact", and "Scope of impact" sections of our communications to reflect this change. We're deploying a code fix to restore the missing UI elements which we anticipate will reach affected users by the end of Thursday, February 5, 2026, which will allow us to validate impact remediation at that time.
Scope of impact: Any user on build 25113001316 of the Microsoft Teams Rooms app leveraging an MTR for Windows device may be impacted. This section may be updated as the investigation progresses.
Start time: Thursday, January 29, 2026, at 3:00 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by the end of Thursday, February 5, 2026.
Root cause: A code regression in the latest build of Microsoft Teams caused the dial pad User Interface (UI) elements to be missing.
Next update by: Thursday, February 5, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 11:52:39 2026 |
|---|
| Description: | Title: Users may not see the dial pad in Microsoft Teams Rooms (MTR) for Windows devices
User impact: Users may not see the dial pad on MTR for Windows devices.
Current status: We're reviewing raised support cases to understand the current impact scenario that users are facing and to determine our initial troubleshooting actions.
Scope of impact: Any user on build 25113001316 of the Microsoft Teams Rooms app leveraging an MTR for Windows device may be impacted. This section may be updated as the investigation progresses.
Next update by: Monday, February 2, 2026, at 6:00 PM UTC
|
|---|
|
EX1226012 - Users' contacts hidden from the Global Address List (GAL) did not appear in Outlook on the web people search results
| Status: | serviceRestored |
|---|
| Start Time: | Thu Dec 18 14:52:00 2025 |
|---|
| End Time: | Mon Feb 9 08:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 10 08:55:42 2026 |
|---|
| Root Cause: | A code change inadvertently caused a regression, which caused impact to occur. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 10 08:55:42 2026 |
|---|
| Description: | Title: Users' contacts hidden from the Global Address List (GAL) did not appear in Outlook on the web people search results
User impact: Users' contacts hidden from the Global Address List (GAL) did not appear in Outlook on the web people search results.
Final status: We've determined that a code change inadvertently caused a regression, which caused impact to occur. We've confirmed that the fix deployment has successfully completed and that impact has been remediated.
Scope of impact: Some users attempting to retrieve contacts in Outlook on the web people search results may have been impacted.
Start time: Thursday, December 18, 2025, at 7:52 PM UTC
End time: Monday, February 9, 2026, at 1:00 PM UTC
Root cause: A code change inadvertently caused a regression, which caused 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: | Fri Feb 6 08:38:03 2026 |
|---|
| Description: | Title: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results
User impact: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results.
Current status: We're continuing to monitor the progress of the fix deployment, and expect to have an estimated time of completion by our next scheduled update.
Scope of impact: Some users attempting to retrieve contacts in Outlook on the web people search results may be impacted.
Next update by: Tuesday, February 10, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Feb 4 09:46:59 2026 |
|---|
| Description: | Title: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results
User impact: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results.
Current status: We're proceeding to monitor the deployment of this fix so that we can validate its effectiveness upon completion.
Scope of impact: Some users attempting to retrieve contacts in Outlook on the web people search results may be impacted.
Next update by: Friday, February 6, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Feb 3 13:27:39 2026 |
|---|
| Description: | Title: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results
User impact: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results.
Current status: The fix has currently saturated to 35 percent of the affected environment. We’ll continue to monitor the deployment of this fix so that we can validate its effectiveness upon completion.
Scope of impact: Some users attempting to retrieve contacts in Outlook on the web people search results may be impacted.
Next update by: Wednesday, February 4, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 16:29:09 2026 |
|---|
| Description: | Title: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results
User impact: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results.
Current status: We've initiated the deployment of the fix, which is progressing though saturation is slower than anticipated. We'll provide an estimate for when the fix deployment is expected to complete when this is available.
Scope of impact: Some users attempting to retrieve contacts in Outlook on the web people search results may be impacted.
Next update by: Tuesday, February 3, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 10:34:00 2026 |
|---|
| Description: | Title: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results
User impact: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results.
Current status: We've identified a potential cause of impact and are actively developing and validating a fix. The fix will be deployed to the affected infrastructure to validate our hypothesis and restore service health.
Scope of impact: Some users attempting to retrieve contacts in Outlook on the web people search results may be impacted.
Next update by: Monday, February 2, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Feb 2 09:07:18 2026 |
|---|
| Description: | Title: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results
User impact: Users' contacts hidden from the Global Address List (GAL) may not appear in Outlook on the web people search results.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Some users attempting to retrieve contacts in Outlook on the web people search results may be impacted.
Next update by: Monday, February 2, 2026, at 4:00 PM UTC
|
|---|
|
EX1229917 - Users may be unable to access Outlook on the web or the Outlook desktop app
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 9 16:23:00 2026 |
|---|
| End Time: | Mon Feb 9 16:38:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Feb 9 18:25:18 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 9 17:32:48 2026 |
|---|
| Description: | Title: Users may be unable to access Outlook on the web or the Outlook desktop app
User impact: Users may have been unable to access Outlook on the web or the Outlook desktop app.
Final status: While we were in the process of analyzing affected network traffic, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: This issue may have affected users in the United States accessing Outlook on the web or the Outlook desktop app.
Start time: Monday, February 9, 2026, at 9:23 PM UTC
End time: Monday, February 9, 2026, at 9:38 PM UTC
This is the final update for the event.
|
|---|
|
PB1224494 - Users may be unable to send subscription emails to external users in Power BI
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Jan 29 13:41:24 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 9 18:14:34 2026 |
|---|
| Root Cause: | An influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. |
|---|
| Next Update: | Tuesday, February 24, 2026, at 12:30 AM UTC |
|---|
|
Details
| Time: | Mon Feb 9 18:14:34 2026 |
|---|
| Description: | Title: Users may be unable to send subscription emails to external users in Power BI
User impact: Users may be unable to send subscription emails to external users in Power BI.
Current status: We're working to develop a code fix although we anticipate this process may take an extended period as we work to address the issue resulting in impact, and in tandem restore subscription mail flow to external users. We’ll provide a resolution timeline as more details become available to us.
Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI.
Start time: Thursday, January 29, 2026, at 6:45 PM UTC
Root cause: An influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery.
Next update by: Tuesday, February 24, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Feb 2 18:12:02 2026 |
|---|
| Description: | Title: Users may be unable to send subscription emails to external users in Power BI
User impact: Users may be unable to send subscription emails to external users in Power BI.
Current status: We've determined that the previous potential mitigation mentioned in our last update isn't a viable solution to deploy to all impacted users. We're further analyzing the influx of automated email traffic from Power BI subscriptions to help with identifying a new remediation plan to resolve the issue for all impacted users.
Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI.
Start time: Thursday, January 29, 2026, at 6:45 PM UTC
Root cause: An influx of automated email traffic from Power BI subscriptions resulted in impact to external subscription email delivery.
Next update by: Tuesday, February 10, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Fri Jan 30 18:22:50 2026 |
|---|
| Description: | Title: Users may be unable to send subscription emails to external users in Power BI
User impact: Users may be unable to send subscription emails to external users in Power BI.
Current status: In addition to temporarily limiting subscription email to be only sent within the same Power BI environment, we’re testing another potential mitigation with a subset of affected users for validation as we continue to review options to resolve this problem for all affected users.
Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI.
Start time: Thursday, January 29, 2026, at 6:45 PM UTC
Root cause: An influx of automated email traffic from Power BI subscriptions resulted in impact to external subscription email delivery.
Next update by: Tuesday, February 3, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Jan 29 14:53:16 2026 |
|---|
| Description: | Title: Users may be unable to send subscription emails to external users in Power BI
User impact: Users may be unable to send subscription emails to external users in Power BI.
Current status: Our monitoring systems have identified impact where users may be unable to send subscription email to external users in Power BI. Our assessment has identified that an influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. To remediate this, we’re temporarily limiting subscription email to be sent only within the same Power BI environment.
Scope of impact: Impact may occur for all users attempting to send subscription emails to external users in Power BI.
Start time: Thursday, January 29, 2026, at 6:45 PM UTC
Root cause: An influx of automated email traffic from Power BI subscriptions resulted in impact to external subscription email delivery.
Next update by: Saturday, January 31, 2026, at 12:30 AM UTC
|
|---|
|
TM1229898 - Mac users can't download the Microsoft Teams desktop client through the Join Launcher
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 6 01:00:00 2026 |
|---|
| End Time: | Fri Feb 6 23:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 9 17:02:21 2026 |
|---|
| Root Cause: | A Content Delivery Network (CDN) update to Microsoft Teams App download locations produced a Join Launcher error that prevented the downloading of the Microsoft Teams desktop client from the Join Launcher. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 9 17:02:21 2026 |
|---|
| Description: | Title: Mac users can't download the Microsoft Teams desktop client through the Join Launcher
User impact: Mac users couldn't download the Teams desktop client through the Join Launcher.
Final status: We've isolated a recent Content Delivery Network (CDN) update to Microsoft Teams App download locations that has produced a Join Launcher error that prevented the downloading of the Microsoft Teams desktop client from the Join Launcher. After deploying a code fix, our internal service telemetry has verified that impact has been remediated.
Scope of impact: This issue may have prevented any Mac user from downloading the Teams desktop client through the Join Launcher.
Start time: Tuesday, January 6, 2026, at 6:00 AM UTC
End time: Saturday, February 7, 2026, at 4:00 AM UTC
Root cause: A Content Delivery Network (CDN) update to Microsoft Teams App download locations produced a Join Launcher error that prevented the downloading of the Microsoft Teams desktop client from the Join Launcher.
Next steps:
- We're further analyzing the update to our CDN to help improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
CP1228310 - Admins may have delayed Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 5 01:00:00 2026 |
|---|
| End Time: | Sun Feb 8 17:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 9 13:37:32 2026 |
|---|
| Root Cause: | A portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center was operating in an unhealthy state, resulting in delays in relaying Copilot reporting data and degraded performance. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 9 13:37:32 2026 |
|---|
| Description: | Title: Admins may have delayed Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center
User impact: Admins may have seen delayed Copilot usage reports in the Microsoft 365 admin center.
Final status: We've isolated that a portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center was operating in an unhealthy state, resulting in delays in relaying Copilot reporting data and degraded performance. We've implemented additional performance optimizations to restore affected infrastructure to a healthy operating state and validated via our service monitoring telemetry that our actions successfully remediated impact.
Scope of impact: Any admin viewing Copilot usage reports in the Microsoft 365 admin center may have been impacted.
Start time: Thursday, February 5, 2026, at 6:00 AM UTC
End time: Sunday, February 8, 2026, at 10:00 PM UTC
Root cause: A portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center was operating in an unhealthy state, resulting in delays in relaying Copilot reporting data and degraded performance.
Next steps:
- We're analyzing the offending service infrastructure to isolate how it began to operate in an unhealthy state to validate what additional performance enhancements we can implement to ensure similar impact doesn't occur.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 6 18:21:50 2026 |
|---|
| Description: | Title: Admins may have delayed Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center
User impact: Admins may have delayed Copilot usage reports in the Microsoft 365 admin center.
Current status: Our service health monitoring alerted us to failures occurring within the portion of service infrastructure responsible for relaying Copilot reporting data to the Microsoft 365 admin center. We're investigating the affected infrastructure to identify the source of the failures.
Scope of impact: Any admin viewing Copilot usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Monday, February 9, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Feb 6 17:58:01 2026 |
|---|
| Description: | Title: Admins may have delayed Microsoft Copilot (Microsoft 365) usage reports in the Microsoft 365 admin center
User impact: Admins may have delayed Copilot usage reports in the Microsoft 365 admin center.
Current status: We're investigating a potential issue with Copilot usage reports in the Microsoft 365 admin center and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1228788 - Some users may experience various issues with some Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Sat Feb 7 03:07:00 2026 |
|---|
| End Time: | Mon Feb 9 07:24:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 9 11:48:42 2026 |
|---|
| Root Cause: | A recent power surge within a portion of our Azure infrastructure in the West US region caused services to go temporarily offline. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 9 11:48:42 2026 |
|---|
| Description: | Title: Some users may experience various issues with some Microsoft 365 services
User impact: Users may have experienced various issues with some Microsoft 365 services.
More info: This issue impacted the following services and scenarios:
- Some users in the West US region may have been unable to execute data plane operations in Power BI.
- Some users may have been unable to utilize Activity and file policy evaluation, Anomaly detection, or Advanced hunting for Microsoft Defender for Cloud Apps.
- Users may have also seen stale information in the portal and execution of governance actions for Microsoft Defender for Cloud Apps.
- Some users may have been unable to utilize Advanced hunting in Microsoft Defender for Identity.
- Admins may have been unable to complete onboarding activities in the Microsoft Defender XDR portal.
- Admins may have been unable to see Microsoft Purview Communication Compliance policy hits in Microsoft Purview.
- Users may have been unable to view recent data in Threat Explorer and Advanced Hunting within Microsoft Defender for Office 365.
- Users may have seen device enrollment failures in Microsoft Intune.
Final status: We've completed our efforts to restore the remaining infrastructure and further confirmed that the remaining backlogs have been processed. Impact has been remediated for all users.
Scope of impact: This issue may have affect users in the West US region who were attempting to utilize the features outlined in the More info section.
Start time: Saturday, February 7, 2026, at 8:00 AM UTC
End time: Monday, February 9, 2026, at 12:24 PM UTC
Root cause: A recent power surge within a portion of our Azure infrastructure in the West US region caused services to go temporarily offline.
Next steps:
- We're reviewing options to increase power surge protection in the affected portion of infrastructure to better prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Sat Feb 7 16:26:22 2026 |
|---|
| Description: | Title: Some users may experience various issues with some Microsoft 365 services
User impact: Users may experience various issues with some Microsoft 365 services.
More info: This issue impacts the following services and scenarios:
- Some users in the West US region may be unable to execute data plane operations in Power BI.
- Some users may be unable to utilize Activity and file policy evaluation, Anomaly detection, or Advanced hunting for Microsoft Defender for Cloud Apps.
- Users may also see stale information in the portal and execution of governance actions for Microsoft Defender for Cloud Apps.
- Some users may be unable to utilize Advanced hunting in Microsoft Defender for Identity.
- Admins may be unable to complete onboarding activities in the Microsoft Defender XDR portal
- Admins may be unable to see Microsoft Purview Communication Compliance policy hits in Microsoft Purview.
- Users may be unable to view recent data in Threat Explorer and Advanced Hunting within Microsoft Defender for Office 365.
- Users may see device enrollment failures in Microsoft Intune.
Current status: Our backup power systems have connected all but a subset of the impacted services and we're working to process the remaining backlogs to ensure full recovery for those services. Review of service health telemetry indicates the backup power systems have returned those services to expected functionality, and we're continuing our efforts to restore the remaining affected infrastructure.
Scope of impact: This issue may affect users in the West US region who are attempting to utilize the features outlined in the More info section.
Start time: Saturday, February 7, 2026, at 8:07 AM UTC
Root cause: A recent power surge within a portion of our Azure infrastructure in the West US region caused services to go temporarily offline.
Next update by: Monday, February 9, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Sat Feb 7 14:22:08 2026 |
|---|
| Description: | Title: Some users may experience various issues with some Microsoft 365 services
User impact: Users may experience various issues with some Microsoft 365 services.
More info: This issue impacts the following services and scenarios:
- Some users in the West US region may be unable to execute data plane operations in Power BI.
- Some users may be unable to utilize Activity and file policy evaluation, Anomaly detection, or Advanced hunting for Microsoft Defender for Cloud Apps.
- Users may also see stale information in the portal and execution of governance actions for Microsoft Defender for Cloud Apps.
- Some users may be unable to utilize Advanced hunting in Microsoft Defender for Identity.
- Admins may be unable to complete onboarding activities in the Microsoft Defender XDR portal
- Admins may be unable to see Microsoft Purview Communication Compliance policy hits in Microsoft Purview.
- Users may be unable to view recent data in Threat Explorer and Advanced Hunting within Microsoft Defender for Office 365.
- Users may see device enrollment failures in Microsoft Intune.
Current status: We're seeing recovery within a portion of the affected Microsoft 365 services as our backup power systems connect to impacted services and the backlog from services are processed. We're reviewing telemetry related to the remaining portion of affected infrastructure to determine what additional mitigation actions are required to fully recover the service.
Scope of impact: This issue may affect users in the West US region who are attempting to utilize the features outlined in the More info section.
Root cause: A recent power surge within a portion of our Azure infrastructure in the West US region caused services to go temporarily offline.
Next update by: Saturday, February 7, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Sat Feb 7 12:16:58 2026 |
|---|
| Description: | Title: Some users may experience various issues with some Microsoft 365 services
User impact: Users may experience various issues with some Microsoft 365 services.
More info: This issue impacts the following services and scenarios:
- Some users in the West US region may be unable to execute data plane operations in Power BI.
- Some users may be unable to utilize Activity and file policy evaluation, Anomaly detection, or Advanced hunting for Microsoft Defender for Cloud Apps.
- Users may also see stale information in the portal and execution of governance actions for Microsoft Defender for Cloud Apps.
- Some users may be unable to utilize Advanced hunting in Microsoft Defender for Identity.
- Admins may be unable to complete onboarding activities in the Microsoft Defender XDR portal
- Admins may be unable to see Microsoft Purview Communication Compliance policy hits in Microsoft Purview.
- Users may be unable to view recent data in Threat Explorer and Advanced Hunting within Microsoft Defender for Office 365.
- Users may see device enrollment failures in Microsoft Intune.
Current status: Our monitoring has notified us of an issue in the West US region where some users may experience various impacts to some Microsoft 365 services, which we've outlined in the More info section above. We've confirmed that a recent power surge at a portion of our Azure infrastructure in the West US region caused services to go temporarily offline. Our backup power systems were activated and we've confirmed that power remains stable to handle service activity. We're working to restore connectivity to the impacted services to fully resolve this issue.
Scope of impact: This issue may affect users in the West US region who are attempting to utilize the features outlined in the More info section.
Root cause: A recent power surge within a portion of our Azure infrastructure in the West US region caused services to go temporarily offline.
Next update by: Saturday, February 7, 2026, at 7:30 PM UTC
|
|---|
|
TM1215277 - Admins were unable to add users to the owner or member roles for Private Microsoft Teams channels
| Status: | serviceRestored |
|---|
| Start Time: | Fri Dec 26 01:33:00 2025 |
|---|
| End Time: | Fri Feb 6 19:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 9 10:03:14 2026 |
|---|
| Root Cause: | A recent API configuration change contained an error, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 9 08:53:30 2026 |
|---|
| Description: | Title: Admins were unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins were unable to add users to the owner or member roles for Private Microsoft Teams channels.
Final status: We've fully deployed the fix and service telemetry has confirmed that impact has been mitigated.
Scope of impact: Your organization was affected by this event, and admins were unable to add users to the owner or member roles for Private Teams channels.
Start time: Wednesday, December 26, 2025, at 6:33 PM UTC
End time: Saturday, February 7, 2026, at 12:00 AM UTC
Root cause: A recent API configuration change contained an error, which resulted in impact.
Next steps:
- We're reviewing our code introduction and validation processes to better detect similar configuration issues earlier in development and testing.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 9 06:53:51 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
Current status: We've confirmed that the fix has been deployed, and we're now reaching out to your organization representatives to confirm that impact is no longer occurring.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Root cause: A recent API configuration change contains an error, which is resulting in impact.
Next update by: Monday, February 9, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Jan 27 03:41:47 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
Current status: We’ve successfully completed validation checks and are now proceeding with deployment. We expect the deployment to complete by Saturday, February 7, 2026. Once deployed, we’ll monitor for an extended period of time, to ensure the impact has been fully remediated.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Estimated time to resolve: Saturday, February 7, 2026
Root cause: A recent API configuration change contains an error, which is resulting in impact.
Next update by: Monday, February 9, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jan 26 08:37:51 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
Current status: We’re progressing with final validation checks before proceeding with the deployment.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Tuesday, January 27, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Mon Jan 26 07:00:15 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We’re continuing to complete final validation checks before proceeding with the deployment.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Monday, January 26, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Thu Jan 22 23:31:34 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We’ve completed development for one part of the fix and are completing final checks before proceeding with the remaining work. Once those checks are finished, we’ll move forward with the next phase and deployment. We’ll share an updated timeline once those steps are complete.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Monday, January 26, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Wed Jan 21 08:01:37 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: Development of the fix is nearing completion, which we expect to conclude by Thursday, January 22, 2026. Once finalized, we'll begin the deployment and share an estimated timeline as soon as one becomes available.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Friday, January 23, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Tue Jan 13 04:05:16 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We're in the final stages of developing the fix and expect completion by Wednesday, January 21, 2026. Once finalized, we will begin the rollout and share a detailed deployment timeline as soon as it becomes available.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Wednesday, January 21, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Fri Jan 9 07:16:06 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We're continuing to develop a fix to validate the root cause and mitigation internally and will provide a remediation timeline once available.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Tuesday, January 13, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Thu Jan 8 17:11:40 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We've identified that a recent API configuration change contains an error resulting in impact. We're in the process of developing a fix to validate the root cause and mitigation internally and will provide a remediation timeline once available.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Friday, January 9, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Wed Jan 7 22:37:58 2026 |
|---|
| Description: | Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
Current status: We've received reports from admins unable to add users as owners or members for private channels. We've reviewed our logs and we’ve identified a recent service change that we suspect may be causing impact. We're testing and validating a potential fix that we anticipate will confirm our theory and resolve the issue.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels. This section may be updated as our investigation continues.
Next update by: Thursday, January 8, 2026, at 11:00 PM UTC
|
|---|
|
IT1229615 - Admins may have been unable to edit certain policies in the Endpoint Security node in Microsoft Intune
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 4 21:30:00 2026 |
|---|
| End Time: | Mon Feb 9 07:09:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 9 08:44:47 2026 |
|---|
| Root Cause: | A regression introduced in the latest UX workflow deployment (version 2601) was preventing the UI from correctly loading and binding policy settings. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 9 08:44:47 2026 |
|---|
| Description: | Title: Admins may have been unable to edit certain policies in the Endpoint Security node in Microsoft Intune
User impact: Admins may have been unable to edit certain policies in the Endpoint Security node in Microsoft Intune.
More info: Admins may have been unable to edit configuration settings and may have seen errors when editing assignments for Endpoint security policies.
If impact still persists, users may need to clear their browser cache and restart the browser to fully resolve impact.
Final status: We’ve successfully reverted back to the previous stable version to restore normal functionality. However, if impact still persists, please follow the guidelines provided in the "More info" section of this communication to fully restore the service.
Scope of impact: Some admins attempting to edit certain policies in the Endpoint Security node in Microsoft Intune may have been impacted.
Start time: Thursday, February 5, 2026, at 2:30 AM UTC
End time: Monday, February 9, 2026, at 12:09 PM UTC
Root cause: A regression introduced in the latest UX workflow deployment (version 2601) was preventing the UI from correctly loading and binding policy settings.
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 Feb 9 04:13:45 2026 |
|---|
| Description: | Title: Admins may be unable to edit certain policies in the Endpoint Security node in Microsoft Intune
User impact: Admins may be unable to edit certain policies in the Endpoint Security node in Microsoft Intune.
More info: Admins may be unable to edit configuration settings and may see errors when editing assignments for Endpoint security policies.
Current status: We’ve identified that a regression introduced in the latest UX workflow deployment is preventing the UI from correctly loading and binding policy settings, which results in settings panes failing to load and assignment operations sending empty data that trigger errors. We’re reverting to the previous stable version to restore normal functionality, and will share a completion timeline when one becomes available.
Scope of impact: Some admins attempting to edit certain policies in the Endpoint Security node in Microsoft Intune may be impacted.
Start time: Thursday, February 5, 2026, at 2:30 AM UTC
Root cause: A regression introduced in the latest UX workflow deployment (version 2601) is preventing the UI from correctly loading and binding policy settings.
Next update by: Monday, February 9, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Feb 9 02:00:17 2026 |
|---|
| Description: | Title: Admins may be unable to edit certain policies in the Endpoint Security node in Microsoft Intune
User impact: Admins may be unable to edit certain policies in the Endpoint Security node in Microsoft Intune.
More info: Admins may be unable to edit configuration settings and may see errors when editing assignments for Endpoint security policies.
Current status: We've received reports of issues when attempting to edit certain policies in Microsoft Intune. We're investigating our service logs and attempting to reproduce the issue internally to help understand the underlying cause of impact and inform our next troubleshooting steps.
Scope of impact: Scope of impact: Some admins attempting to edit certain policies in the Endpoint Security node in Microsoft Intune may be impacted.
Next update by: Monday, February 9, 2026, at 10:00 AM UTC
|
|---|
|
MP1228686 - Some users may have seen errors in DLP policy across Endpoint, Copilot and autolabeling
| Status: | serviceRestored |
|---|
| Start Time: | Sat Feb 7 02:56:00 2026 |
|---|
| End Time: | Sat Feb 7 06:18:00 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Feb 7 11:25:03 2026 |
|---|
| Root Cause: | An issue within a section of our West US infrastructure caused a subset of dependent resources to become unavailable. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Feb 7 08:26:35 2026 |
|---|
| Description: | Title: Some users may have seen errors in DLP policy across Endpoint, Copilot and autolabeling
User impact: Users may have seen errors in DLP policy across Endpoint, Copilot and autolabeling.
Final status: We’ve identified an issue within a section of our West US infrastructure caused a subset of dependent resources to become unavailable. This was impacting access to some compute, storage, and networking capabilities. We've rerouted traffic to alternate infrastructure as part of the mitigation and confirmed after a period of time that issue is no loner occurring.
Scope of impact: Some users in North United States attempting to view DLP policy may have been impacted.
Start time: Saturday, February 7, 2026, at 7:56 AM UTC
End time: Saturday, February 7, 2026, at 11:18 AM UTC
Root cause: An issue within a section of our West US infrastructure caused a subset of dependent resources to become unavailable.
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: | Sat Feb 7 06:45:39 2026 |
|---|
| Description: | Title: Some users may be seeing errors in DLP policy across Endpoint, Copilot and autolabeling
User impact: Users may be seeing errors in DLP policy across Endpoint, Copilot and autolabeling.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Some users in North United States attempting to view DLP policy may be impacted.
Next update by: Saturday, February 7, 2026, at 2:00 PM UTC
|
|---|
|
MO1176905 - Some admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Oct 7 04:27:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 6 06:19:01 2026 |
|---|
| Root Cause: | A recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups. |
|---|
| Next Update: | Friday, February 20, 2026, at 12:30 PM UTC |
|---|
|
Details
| Time: | Fri Feb 6 06:19:01 2026 |
|---|
| Description: | Title: Some admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services
User impact: Admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services.
More info: This issue specifically affects admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True".
While we finalize the deployment of our fix to restore the appropriate configuration for the impacted Microsoft 365 Groups, affected admins can follow the steps below to manually restore the SecurityEnabled property configuration and resolve the impact:
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”, then run the following command to retrieve audit logs specific to this scenario:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000.
2. Filter logs matching the issue to gather affected group info by running the following two commands:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
3. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All" and then run the following command to restore the SecurityEnabled property for the affected groups to True, which should remediate the impact:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
For further information on how to run Microsoft Graph PowerShell commands and cmdlets or guidance on connecting to Exchange Online through PowerShell, please reference the following documentation:
https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=ex…
https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
Current status: Our analysis of the aforementioned timeout issues is taking longer than we expected. This is required so we can efficiently resume the deployment on the remaining impacted groups. We're working to identify options that can accelerate the progress of analyzing timeout issues.
Scope of impact: Admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True" may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups.
Next update by: Friday, February 20, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Fri Feb 6 01:29:22 2026 |
|---|
| Description: | Title: Some admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services
User impact: Admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services.
More info: This issue specifically affects admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True".
While we finalize the deployment of our fix to restore the appropriate configuration for the impacted Microsoft 365 Groups, affected admins can follow the steps below to manually restore the SecurityEnabled property configuration and resolve the impact:
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”, then run the following command to retrieve audit logs specific to this scenario:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000.
2. Filter logs matching the issue to gather affected group info by running the following two commands:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
3. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All" and then run the following command to restore the SecurityEnabled property for the affected groups to True, which should remediate the impact:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
For further information on how to run Microsoft Graph PowerShell commands and cmdlets or guidance on connecting to Exchange Online through PowerShell, please reference the following documentation:
https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
Current status: We’re continuing our analysis of the aforementioned timeout issues so we can efficiently resume the deployment on the remaining impacted groups.
Scope of impact: Admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True" may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups.
Next update by: Friday, February 6, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Fri Jan 30 01:38:33 2026 |
|---|
| Description: | Title: Some admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services
User impact: Admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services.
More info: This issue specifically affects admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True".
While we finalize the deployment of our fix to restore the appropriate configuration for the impacted Microsoft 365 Groups, affected admins can follow the steps below to manually restore the SecurityEnabled property configuration and resolve the impact:
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”, then run the following command to retrieve audit logs specific to this scenario:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000.
2. Filter logs matching the issue to gather affected group info by running the following two commands:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
3. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All" and then run the following command to restore the SecurityEnabled property for the affected groups to True, which should remediate the impact:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
For further information on how to run Microsoft Graph PowerShell commands and cmdlets or guidance on connecting to Exchange Online through PowerShell, please reference the following documentation:
https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
Current status: We've identified that the deployment of the fix has encountered unexpected timeout issues that's preventing it from fully saturating all impacted Microsoft 365 Groups. While we've confirmed that the majority of groups have successfully received the fix, we're further investigating the timeout issues to identify how we can efficiently resume the deployment on the remaining impacted groups.
Scope of impact: Admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True" may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups.
Next update by: Friday, February 6, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Fri Jan 23 01:11:53 2026 |
|---|
| Description: | Title: Some admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services
User impact: Admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services.
More info: This issue specifically affects admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True".
While we finalize the deployment of our fix to restore the appropriate configuration for the impacted Microsoft 365 Groups, affected admins can follow the steps below to manually restore the SecurityEnabled property configuration and resolve the impact:
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”, then run the following command to retrieve audit logs specific to this scenario:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000.
2. Filter logs matching the issue to gather affected group info by running the following two commands:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
3. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All" and then run the following command to restore the SecurityEnabled property for the affected groups to True, which should remediate the impact:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
For further information on how to run Microsoft Graph PowerShell commands and cmdlets or guidance on connecting to Exchange Online through PowerShell, please reference the following documentation:
https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
Current status: The fix deployment is progressing as expected and we're continuing to monitor as it saturates.
Scope of impact: Admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True" may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups.
Next update by: Friday, January 30, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Fri Jan 16 01:19:12 2026 |
|---|
| Description: | Title: Some admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services
User impact: Admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services.
More info: This issue specifically affects admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True".
While we finalize the deployment of our fix to restore the appropriate configuration for the impacted Microsoft 365 Groups, affected admins can follow the steps below to manually restore the SecurityEnabled property configuration and resolve the impact:
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”, then run the following command to retrieve audit logs specific to this scenario:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000.
2. Filter logs matching the issue to gather affected group info by running the following two commands:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
3. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All" and then run the following command to restore the SecurityEnabled property for the affected groups to True, which should remediate the impact:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
For further information on how to run Microsoft Graph PowerShell commands and cmdlets or guidance on connecting to Exchange Online through PowerShell, please reference the following documentation:
https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
Current status: The deployment of the fix has resumed and we're monitoring as it saturates for timeout errors and latency issues. We continue to anticipate the fix to complete by the end of January 2026.
Scope of impact: Admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True" may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups.
Next update by: Friday, January 23, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Mon Jan 12 02:13:40 2026 |
|---|
| Description: | Title: Some admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services
User impact: Admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services.
More info: This issue specifically affects admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True".
While we finalize the deployment of our fix to restore the appropriate configuration for the impacted Microsoft 365 Groups, affected admins can follow the steps below to manually restore the SecurityEnabled property configuration and resolve the impact:
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”, then run the following command to retrieve audit logs specific to this scenario:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000.
2. Filter logs matching the issue to gather affected group info by running the following two commands:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
3. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All" and then run the following command to restore the SecurityEnabled property for the affected groups to True, which should remediate the impact:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
For further information on how to run Microsoft Graph PowerShell commands and cmdlets or guidance on connecting to Exchange Online through PowerShell, please reference the following documentation:
https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
Current status: While monitoring the deployment of the fix, we've identified an increase in timeout errors and latency that's preventing some groups from successfully receiving the fix. We've halted the deployment and are actively working to resolve the timeout issues occurring on a subset of affected groups. Once the deployment resumes, we'll continue to closely monitor and resolve any timeout or latency issues groups encounter before proceeding with the deployment to ensure the issue is fully resolved. Due to the complexity of the issue, we expect it may take until the end of January 2026 for all affected groups to be fixed, and we anticipate users in affected groups will experience remediation incrementally while the deployment progresses.
Scope of impact: Admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True" may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups.
Next update by: Friday, January 16, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Sat Jan 10 01:05:47 2026 |
|---|
| Description: | Title: Some admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services
User impact: Admins and users managed through Microsoft 365 Groups may be unable to access some Microsoft 365 services.
More info: This issue specifically affects admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True".
While we finalize the deployment of our fix to restore the appropriate configuration for the impacted Microsoft 365 Groups, affected admins can follow the steps below to manually restore the SecurityEnabled property configuration and resolve the impact:
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”, then run the following command to retrieve audit logs specific to this scenario:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000.
2. Filter logs matching the issue to gather affected group info by running the following two commands:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
3. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All" and then run the following command to restore the SecurityEnabled property for the affected groups to True, which should remediate the impact:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
For further information on how to run Microsoft Graph PowerShell commands and cmdlets or guidance on connecting to Exchange Online through PowerShell, please reference the following documentation:
https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
Current status: Through further analysis and investigation, we've clarified that a recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups. We're finalizing the rollout of our fix to restore the impacted groups and anticipate the remaining impact may be remediated by the time of our next scheduled update.
Scope of impact: Admins and users whose service access is managed by Microsoft 365 Groups that were previously configured with the "SecurityEnabled" setting set to "True" may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups.
Next update by: Monday, January 12, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Fri Jan 9 15:13:27 2026 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: While we monitor the fix deployment as it completes, we've updated the "More info" section to correct an incomplete URL which was shared under step 5. Additionally, we'll provide further clarifying information regarding which specific services are impacted by this event as this information becomes available.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Saturday, January 10, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Mon Jan 5 01:25:44 2026 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We've deployed the fix to one of the affected environments and have seen some initial recovery. We're continuing to monitor as the deployment saturates the remaining impacted environments, which we expect to be fully deployed and the impact remediated by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Monday, January 12, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Mon Dec 29 01:51:55 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We can confirm that the deployment has completed for our internal testing environment and that we are now moving forward with deploying the fix to the remaining affected environments upon final validations.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Monday, January 5, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Fri Dec 19 01:02:41 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We've completed the validation of our fix in our internal testing environment and are initiating the roll out of the fix to all affected environments. We'll provide a timeline for full deployment and remediation as it becomes available.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Monday, December 29, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Mon Dec 15 01:31:21 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: The deployment of the initial fix has completed, though we've identified a secondary deployment is needed to ensure the impact is fully remediated. We've started deploying the secondary fix to our internal testing environment, and we'll aim to provide a resolution timeline by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, December 19, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Mon Dec 8 03:27:27 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: The deployment of the fix is ongoing and is expected to complete by Monday, December 15, 2025.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Estimated time to resolve: Monday, December 15, 2025
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Monday, December 15, 2025, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Dec 5 10:14:25 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We're continuing to deploy the fix and will share a completion timeline when one becomes available.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Monday, December 8, 2025, at 1:00 PM UTC
|
|---|
|
| Time: | Fri Nov 28 10:22:24 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We've deployed a part of the fix and have also successfully tested the remaining part of the fix which is being deployed to the affected infrastructure. We anticipate that this should complete by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Estimated time to resolve: Friday, December 5, 2025
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, December 5, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Nov 21 10:22:19 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We've validated a part of the fix which is ready to be deployed, and the remaining part of the fix is under review to be tested prior to deploying it to the affected infrastructure. We anticipate to provide the estimated deployment time line by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, November 28, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Nov 14 09:09:32 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We've developed the aforementioned fix to address the impact. We're now conducting a validation and testing process to ensure the effectiveness of the fix prior to deploying it to the affected infrastructure. We expect to share an estimated deployment time line by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, November 21, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Nov 7 09:03:02 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We’re proceeding to develop a fix to address the impact and will begin testing once development is complete to ensure effectiveness before deployment. We expect to share an estimated completion time by our next scheduled update.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, November 14, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Nov 3 09:42:15 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: Our development of the fix in ongoing and we'll share a completion timeline when one becomes available. Whilst we work on developing our fix to update the SecurityEnabled property from False to True, admins can continue using the cmdlets shared in the "More info" section to remediate the impact.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, November 7, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Oct 27 11:01:02 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can run the following cmdlets to mitigate the impact.
1. Connect to Exchange Online PowerShell with “Connect-ExchangeOnline”.
Reference: https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps
2. Run Search-UnifiedAuditLog and retrieve audit logs:
$AuditLog = Search-UnifiedAuditLog -Operations "Update group" -StartDate (Get-Date).AddDays(-30) -EndDate (Get-Date) -ResultSize 5000
3. Filter logs matching the issue and replace "Group_" in ObjectID:
$GroupID = $AuditLog | % {ConvertFrom-Json $_.AuditData} | ? {($_.Actor -match "Group Configuration Processor") -and ($_.ModifiedProperties -match "SecurityEnabled")} | % {$_.ObjectId -replace "^.*Group_", ""}
* Because ObjectID from UnifiedAuditLog starts with "Group_", it cannot be used directly with Get-UnifiedGroup.
4. You can verify each group info to see which ones were affected with the following command:
$GroupID | Get-UnifiedGroup -ResultSize Unlimited
5. Connect to Microsoft Graph PowerShell with Connect-MgGraph -Scope "Group.ReadWrite.All".
Reference: https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powershell-1.0
6. Update SecurityEnabled to True:
$GroupID | % {Update-MgGroup -GroupId $_ -BodyParameter @{SecurityEnabled = $true}}
Current status: We're continuing to develop and validate our fix, designed to update the SecurityEnabled property from False to True, and we expect the validations and deployment to complete in two to three weeks. We'll provide an updated deployment timeline as one becomes available. While we work on deploying our fix to update the SecurityEnabled property from False to True, admins can use the cmdlets shared in the "More info" section to remediate the impact.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Monday, November 3, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Oct 24 06:12:49 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
Current status: We’ve developed a potential fix to update SecurityEnabled from False to True for the remaining affected groups. The fix is currently undergoing internal validation to ensure it fully mitigates the issue before deployment to the affected environments.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Monday, October 27, 2025, at 3:30 PM UTC
|
|---|
|
| Time: | Thu Oct 23 01:42:58 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
Current status: We're continuing to explore options for updating the SecurityEnabled to True from False for the remaining affected groups. Additionally, our ongoing monitoring indicates that new properties are unaffected.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Start time: Tuesday, October 7, 2025, at 8:27 AM UTC
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Friday, October 24, 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Wed Oct 22 01:58:14 2025 |
|---|
| Description: | Title: Some admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the SecurityEnabled property changed to False by the Group Configuration Processor.
Current status: We've received confirmation that reverting the offending change which caused to the Group SecurityEnabled property to change to False as default completed, and new properties are no longer being set to False by default. Additionally, we're exploring options on how to update the SecurityEnabled to True from False for the remaining affected groups to ensure the underlying issue is fully resolved.
Scope of impact: Any admin or users attempting to access any Microsoft 365 services with the Microsoft 365 Group SecurityEnabled set to false may be impacted.
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Thursday, October 23, 2025, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 09:52:20 2025 |
|---|
| Description: | Title: Admins or users may be unable to access multiple Microsoft 365 services
User impact: Admins or users may be unable to access multiple Microsoft 365 services.
More info: This specifically impacts Microsoft 365 services that have the Microsoft 365 Group SecurityEnabled changed to false.
Current status: We've identified that a recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact. We've reverted the aforementioned change, and we're working with affected users to verify that impact has been fully resolved.
Scope of impact: Your organization is affected by this event, and any admin or users attempting to access any Microsoft 365 services with Microsoft 365 Group SecurityEnabled set to false is impacted.
Root cause: A recent change caused a misconfiguration, which led to the Microsoft 365 Group SecurityEnabled being changed to false as default, resulting in impact.
Next update by: Wednesday, October 22, 2025, at 7:00 AM UTC
|
|---|
|
TM1227179 - Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 21 19:09:00 2026 |
|---|
| End Time: | Fri Feb 6 00:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 6 00:27:16 2026 |
|---|
| Root Cause: | A code regression inadvertently introduced in a recent update was causing a graph API which Microsoft Teams relies on for scheduling channel meetings with a meeting room to fail. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 6 00:27:16 2026 |
|---|
| Description: | Title: Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams
User impact: Users may have been unable to select or find meeting rooms when creating channel meetings in Microsoft Teams.
Final status: We've monitored the deployment progress of the fix and we've now confirmed that it has fully deployed, resolving the impact.
Scope of impact: Any user attempting to select or find meetings rooms when creating channel meetings in Microsoft Teams may have been impacted.
Start time: Thursday, January 22, 2026, at 12:09 AM UTC
End time: Friday, February 6, 2026, at 5:00 AM UTC
Root cause: A code regression inadvertently introduced in a recent update was causing a graph API which Microsoft Teams relies on for scheduling channel meetings with a meeting room to fail.
Next steps:
- We're reviewing our update procedures to understand why the code regression wasn't identified during our testing phase. This will help us to improve our testing processes and proactively identifying similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 5 14:04:00 2026 |
|---|
| Description: | Title: Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams
User impact: Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams.
Current status: The fix has released to around 45 percent of affected infrastructure and we're monitoring as it progresses. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Any user attempting to select or find meetings rooms when creating channel meetings in Microsoft Teams may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 12:09 AM UTC
Root cause: A regression is causing a graph API which Microsoft Teams relies on for scheduling channel meetings with a meeting room to fail.
Next update by: Friday, February 6, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Thu Feb 5 06:01:50 2026 |
|---|
| Description: | Title: Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams
User impact: Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams.
Current status: We’ve initiated the deployment process, which is expected to take approximately 40 hours to complete. In parallel, we’re exploring additional options to determine whether the deployment timeline can be expedited.
Scope of impact: Any user attempting to select or find meetings rooms when creating channel meetings in Microsoft Teams may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 12:09 AM UTC
Root cause: A regression is causing a graph API which Microsoft Teams relies on for scheduling channel meetings with a meeting room to fail.
Next update by: Thursday, February 5, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Feb 5 02:05:02 2026 |
|---|
| Description: | Title: Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams
User impact: Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams.
Current status: We’ve developed a fix and are performing validations to ensure it addresses the issue without any adverse effects. Once we’ve completed the validation phase, we’ll begin the expedited deployment of our fix to the affected users. We anticipate being able to provide a timeline for complete deployment by our next scheduled communications update.
Scope of impact: Any user attempting to select or find meetings rooms when creating channel meetings in Microsoft Teams may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 12:09 AM UTC
Root cause: A regression is causing a graph API which Microsoft Teams relies on for scheduling channel meetings with a meeting room to fail.
Next update by: Thursday, February 5, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Thu Feb 5 00:33:02 2026 |
|---|
| Description: | Title: Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams
User impact: Users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams.
Current status: We've received reports from affected users indicating that users may be unable to select or find meeting rooms when creating channel meetings in Microsoft Teams. We've identified a regression is causing a graph API which Microsoft Teams relies on for scheduling channel meetings with a meeting room to fail. We're assessing solutions available for swift resolution of impact.
Scope of impact: Any user attempting to select or find meetings rooms when creating channel meetings in Microsoft Teams may be impacted. This information may be updated as our investigation continues.
Root cause: A regression is causing a graph API which Microsoft Teams relies on for scheduling channel meetings with a meeting room to fail.
Next update by: Thursday, February 5, 2026, at 8:00 AM UTC
|
|---|
|
MO1227225 - Admins' usage reports in the Microsoft 365 admin center may be delayed
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 2 19:00:00 2026 |
|---|
| End Time: | Wed Feb 4 19:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 5 17:02:30 2026 |
|---|
| Root Cause: | A failure in an upstream data processing component prevented usage report data from being generated and supplied to the Microsoft 365 admin center, resulting in delayed usage reports. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 5 16:48:05 2026 |
|---|
| Description: | Title: Admins' usage reports in the Microsoft 365 admin center may be delayed
User impact: Admins' usage reports in the Microsoft 365 admin center may have been delayed.
More info: The "Teams Team" and "Group Activity" usage reports in the Microsoft 365 admin center may have been delayed.
Final status: We’ve identified a failure in an upstream data processing component that prevented usage report data from generating to the Microsoft 365 admin center, resulting in delayed usage reports. To remediate this issue, we manually restarted the affected data processing component and, after monitoring the service, we’ve verified the issue is successfully resolved.
Scope of impact: Any admin may have been affected and may have seen delays in their usage reports in the Microsoft admin center.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
End time: Thursday, February 5, 2026, at 12:00 AM UTC
Root cause: A failure in an upstream data processing component prevented usage report data from being generated and supplied to the Microsoft 365 admin center, resulting in delayed usage reports.
Next steps:
- We’re investigating the failure in the upstream data processing component to help prevent this issue from recurring.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 5 01:52:16 2026 |
|---|
| Description: | Title: Admins' usage reports in the Microsoft admin center may be delayed
User impact: Admins' usage reports in the Microsoft admin center may be delayed.
More info: The "Teams Team" and "Group Activity" usage reports in the Microsoft admin center may be delayed.
Current status: We were alerted to an issue from our internal monitoring that indicated a delay for the usage reports in the Microsoft admin center. We're reviewing our service infrastructure and telemetry logs to help pinpoint the underlying cause of the delayed usage report data, and to help develop our next troubleshooting steps.
Scope of impact: Any admin may be affected and see delays in their usage reports in the Microsoft admin center. This information may be updated as our investigation continues.
Next update by: Thursday, February 5, 2026, at 10:30 PM UTC
|
|---|
|
TM1226449 - Users may be unable to apply video effects during meetings in Microsoft Teams desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 3 08:00:00 2026 |
|---|
| End Time: | Wed Feb 4 03:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 4 21:33:35 2026 |
|---|
| Root Cause: | A recent routine service update exposed a code regression, which affected some users' ability to apply video effects during meetings in Microsoft Teams desktop client and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 4 21:33:35 2026 |
|---|
| Description: | Title: Users may be unable to apply video effects during meetings in Microsoft Teams desktop client
User impact: Users may have been unable to apply video effects during meetings in Microsoft Teams desktop client.
Final status: Our review of the internal reproduction had determined that a recent routine service update exposed a code regression, which affected some users' ability to apply video effects during meetings in Microsoft Teams desktop client. We've since reverted the service update and after an extended period of monitoring confirmed that impact has been remediated.
Scope of impact: This issue may have impacted any Microsoft Teams desktop user who attempted to apply video effects in a meeting.
Start time: Tuesday, February 3, 2026, at 1:00 PM UTC
End time: Wednesday, February 4, 2026, at 8:00 AM UTC
Root cause: A recent routine service update exposed a code regression, which affected some users' ability to apply video effects during meetings in Microsoft Teams desktop client and resulted in impact.
Next steps:
- We’re continuing to analyze how the 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: | Tue Feb 3 15:24:38 2026 |
|---|
| Description: | Title: Users may be unable to apply video effects during meetings in Microsoft Teams desktop client
User impact: Users may be unable to apply video effects during meetings in Microsoft Teams desktop client.
Current status: We’re continuing to assess the results of our internal reproductions of the impact to isolate the root cause and determine appropriate remediation actions.
Scope of impact: This issue may impact any Microsoft Teams desktop user attempting to apply video effects in a meeting.
Next update by: Thursday, February 5, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Feb 3 13:46:20 2026 |
|---|
| Description: | Title: Users may be unable to apply video effects during meetings in Microsoft Teams desktop client
User impact: Users may be unable to apply video effects during meetings in Microsoft Teams desktop client.
Current status: We’re continuing to debug the results of our internal reproductions of impact to isolate this issue's root cause and develop remediation solutions.
Scope of impact: This issue may impact any Microsoft Teams desktop user attempting to apply video effects in a meeting.
Next update by: Tuesday, February 3, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Feb 3 11:55:21 2026 |
|---|
| Description: | Title: Some users may be unable to apply video effects in Microsoft Teams
User impact: Users may be unable to apply video effects in Microsoft Teams.
Current status: We’ve reproduced this issue internally and are debugging the results to determine the root cause and a strategy that remediates impact.
Scope of impact: Some users attempting to apply video effects in Microsoft Teams may be impacted.
Next update by: Tuesday, February 3, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Feb 3 10:33:35 2026 |
|---|
| Description: | Title: Some users may be unable to apply video effects in Microsoft Teams
User impact: Users may be unable to apply video effects in Microsoft Teams.
Current status: We’re reviewing service telemetry and system logs to identify the underlying cause, in order to develop a remediation plan.
Scope of impact: Some users attempting to apply video effects in Microsoft Teams may be impacted.
Next update by: Tuesday, February 3, 2026, at 5:30 PM UTC
|
|---|
|
SP1177145 - Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Oct 13 14:50:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 4 13:53:40 2026 |
|---|
| Root Cause: | A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again. |
|---|
| Next Update: | Wednesday, February 18, 2026, at 8:00 PM UTC |
|---|
|
Details
| Time: | Wed Feb 4 13:39:02 2026 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We've completed our tests within the infrastructure which received the automated repair process and confirmed this action remediates the impact. We're monitoring the deployment as it progresses to the remaining affected infrastructure, and our estimation for this process to complete remains late February 2026.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, February 18, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 14:01:08 2026 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We've completed the validations for our automated repair process, which we've deployed to a portion of the affected infrastructure. We're running tests within the infrastructure where the automated repair process is running to further ensure it has the desired effect in remediating the impact, prior to progressing the deployment any further. Our current estimation for the repair process to be saturated within all affected infrastructure is late February 2026.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, February 4, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jan 14 13:46:43 2026 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: The validation of our automated repair process to identify and correct currently impacted folders, files, and list items is ongoing and will require a bit longer than previously expected to complete. We're progressing with our internal tests and expect that an updated timeline for impact remediation will be available by our next scheduled communication update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, January 21, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Dec 1 16:23:34 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: As the validation of our automated repair process to identify and correct currently impacted items, such as folders, files, and list items is ongoing, we’ve determined that more time will be needed to complete this step. We anticipate the initial validation of our fix will complete by Wednesday, January 14, 2026, at 8:00 PM UTC, after which we expect to have more insight into the overall timeline for impact remediation for all users.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, January 14, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Dec 1 13:54:20 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: The validation of our automated repair process to identify and correct currently impacted items, such as folders, files, and list items is ongoing. Based on our current estimated timelines, we anticipate the initial validation of our fix will complete by our next scheduled communication update, after which we expect to have more insight into the overall timeline for impact remediation for all users.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, January 7, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 19 15:20:35 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We’ve successfully deployed a fix that addresses the underlying issue and prevents additional folders, files, and list items from being impacted. To address folders, files, and list items that are still impacted by this event, we're validating an automated repair process that identifies and corrects impacted items. While initial indications are that the process to address and corrected impacted items will take an extended period of time, we’ll communicate the status of this long-term mitigation strategy and provide an updated remediation timeline as this event progresses.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Monday, December 1, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 14:25:25 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: The removal of the errors isolated during our internal tests and validations requires additional time, and we'll provide an updated timeline for our fix validations once it’s available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 19, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 5 14:08:43 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: During the validation process of our fix, we isolated additional errors that needed to be addressed prior to beginning a broad deployment to the affected environment. We’re working to eliminate all additional errors, and we aim to provide a timeline to deployment as one becomes available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 12, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 29 14:10:06 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We're continuing to prepare the fix for broad deployment to the affected environment and we'll aim to provide a timeline for the deployment to begin by our next scheduled communications update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 5, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 13:44:02 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've completed our internal validation of the completed portion of our fix and confirmed it successfully remediates impact. For any users experiencing impact at this time, your organization may raise a support case to have this fix manually run to repair affected items. With our internal validation completed, we're continuing to prepare the fix for a future deployment so that the repair job runs proactively to fully remediate impact. We're working to estimate a timeline for this deployment and overall impact resolution.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 29, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Oct 24 16:04:16 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: Development of the remaining necessary portions of the overall solution is progressing as we continue internal testing of the completed portion to verify its efficacy to correct the issue. We'll continue to provide updates as we near the completion of this process and provide a remediation timeline when possible.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Monday, October 27, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 15:19:56 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: While we've finalized a portion of the necessary code fixes to address the issue, and are validating the effectiveness of this portion, we're still developing several other portions of overall solution. All portions of the full fix will need to be completed and validated before we begin our deployment process as they are dependent on each other. Once complete, we'll provide a timeline for deployment and impact remediation as one becomes available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Friday, October 24, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 23:10:34 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've made progress in the development of a portion of code fixes to address the issue. We're working to further finalize our remaining code fixes needed to address the full impact before we can provide a full deployment timeline.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 19:49:39 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We're continuing the development and internal testing of our code fix, and anticipate we may be able to provide an estimated timeline for its deployment by our next scheduled update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 16:44:25 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in SharePoint Online.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've identified a recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again. We're developing a code fix that will undergo internal testing and validations, and we'll aim to provide a resolution timeline once available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 16:18:27 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
User impact: Users with edit and full control permissions may be unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Current status: We're investigating a potential issue with OneDrive and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
OD1177143 - Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Oct 13 11:50:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft OneDrive |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 4 13:37:04 2026 |
|---|
| Root Cause: | A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again. |
|---|
| Next Update: | Wednesday, February 18, 2026, at 8:00 PM UTC |
|---|
|
Details
| Time: | Wed Feb 4 13:37:04 2026 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We've completed our tests within the infrastructure which received the automated repair process and confirmed this action remediates the impact. We're monitoring the deployment as it progresses to the remaining affected infrastructure, and our estimation for this process to complete remains late February 2026.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, February 18, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 14:01:34 2026 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We've completed the validations for our automated repair process, which we've deployed to a portion of the affected infrastructure. We're running tests within the infrastructure where the automated repair process is running to further ensure it has the desired effect in remediating the impact, prior to progressing the deployment any further. Our current estimation for the repair process to be saturated within all affected infrastructure is late February 2026.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, February 4, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jan 14 13:47:11 2026 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: The validation of our automated repair process to identify and correct currently impacted folders, files, and list items is ongoing and will require a bit longer than previously expected to complete. We're progressing with our internal tests and expect that an updated timeline for impact remediation will be available by our next scheduled communication update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, January 21, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Dec 1 16:23:13 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: As the validation of our automated repair process to identify and correct currently impacted items, such as folders, files, and list items is ongoing, we’ve determined that more time will be needed to complete this step. We anticipate the initial validation of our fix will complete by Wednesday, January 14, 2026, at 8:00 PM UTC, after which we expect to have more insight into the overall timeline for impact remediation for all users.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, January 14, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Dec 1 13:54:11 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: The validation of our automated repair process to identify and correct currently impacted items, such as folders, files, and list items is ongoing. Based on our current estimated timelines, we anticipate the initial validation of our fix will complete by our next scheduled communication update, after which we expect to have more insight into the overall timeline for impact remediation for all users.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, January 7, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 19 15:16:59 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We’ve successfully deployed a fix that addresses the underlying issue and prevents additional folders, files, and list items from being impacted. To address folders, files, and list items that are still impacted by this event, we're validating an automated repair process that identifies and corrects impacted items. While initial indications are that the process to address and corrected impacted items will take an extended period of time, we’ll communicate the status of this long-term mitigation strategy and provide an updated remediation timeline as this event progresses.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Monday, December 1, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 12 14:25:52 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: The removal of the errors isolated during our internal tests and validations requires additional time, and we'll provide an updated timeline for our fix validations once it’s available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 19, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Nov 5 14:08:46 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: During the validation process of our fix, we isolated additional errors that needed to be addressed prior to beginning a broad deployment to the affected environment. We’re working to eliminate all additional errors, and we aim to provide a timeline to deployment as one becomes available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 12, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 29 14:09:50 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
While we work to implement our fix to fully resolve the impact, your organization may raise a support case to have the fix manually run to repair affected items.
Current status: We're continuing to prepare the fix for broad deployment to the affected environment, and we'll aim to provide a timeline for the deployment to begin by our next scheduled communications update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, November 5, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Mon Oct 27 13:42:19 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've completed our internal validation of the completed portion of our fix and confirmed it successfully remediates impact. For any users experiencing impact at this time, your organization may raise a support case to have this fix manually run to repair affected items. With our internal validation completed, we're continuing to prepare the fix for a future deployment so that the repair job runs proactively to fully remediate impact. We're working to estimate a timeline for this deployment and overall impact resolution.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 29, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Oct 24 16:02:53 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Additionally, processes that attempt to enumerate permissions on these items may see failures.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: Development of the remaining necessary portions of the overall solution is progressing as we continue internal testing of the completed portion to verify its efficacy to correct the issue. We'll continue to provide updates as we near the completion of this process and provide a remediation timeline when possible.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some folders in OneDrive that were deleted and recently restored from the recycle bin may be impacted. This information may be updated as our investigation continues.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Monday, October 27, 2025, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Oct 22 15:16:24 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some content in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: While we've finalized a portion of the necessary code fixes to address the issue, and are validating the effectiveness of this portion, we're still developing several other portions of overall solution. All portions of the full fix will need to be completed and validated before we begin our deployment process as they are dependent on each other. Once complete, we'll provide a timeline for deployment and impact remediation as one becomes available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some content in OneDrive that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Friday, October 24, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 23:11:51 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some content in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've made progress in the development of a portion of code fixes to address the issue. We're working to further finalize our remaining code fixes needed to address the full impact before we can provide a full deployment timeline.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some content in OneDrive that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Oct 21 19:49:45 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some content in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We're continuing the development and internal testing of our code fix, and anticipate we may be able to provide an estimated timeline for its deployment by our next scheduled update.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some content in OneDrive that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 16:42:05 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some content in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Site administrators will still have complete access to the content that's been deleted and restored.
Current status: We've identified a recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again. We're developing a code fix that will undergo internal testing and validations, and we'll aim to provide a resolution timeline once available.
Scope of impact: Some users with edit and full control permissions who are attempting to access or share some content in OneDrive that were deleted and recently restored from the recycle bin may be impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
Root cause: A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next update by: Wednesday, October 22, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Oct 21 16:16:01 2025 |
|---|
| Description: | Title: Some users with edit and full control permissions may be unable to access or share some content in Microsoft OneDrive
User impact: Users with edit and full control permissions may be unable to access or share some files in OneDrive.
More info: Specifically, this issue impacts files and folders that were deleted and recently restored. Impacted users attempting to access or share some folders experience failures in sharing and permission operations in OneDrive.
Current status: We're investigating a potential issue with OneDrive and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1226887 - Some users may be unable to toggle call queues on or off in the Microsoft Teams web or desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 4 04:30:00 2026 |
|---|
| End Time: | Wed Feb 4 11:22:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 4 12:45:19 2026 |
|---|
| Root Cause: | A code change contained within a recent service update was causing requests to be sent to an incorrect URL, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 4 12:08:35 2026 |
|---|
| Description: | Title: Some users may be unable to toggle call queues on or off in the Microsoft Teams web or desktop client
User impact: Users may have been unable to toggle call queues on or off in the Microsoft Teams web or desktop client.
More info: As a workaround, users may have been able to use the Microsoft Teams mobile app to toggle call queues as expected.
Additionally, admins may have been unable to make changes to call queues, auto attendants, and holidays within the Microsoft Teams admin center.
Final status: We've reverted the offending service update and confirmed through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Some users hosted in the North America region attempting to toggle call queues in the Microsoft Teams web or desktop client may have been impacted.
Additionally, admins making changes to call queues, auto attendants, and holidays in the Microsoft Teams admin center may also have been affected.
Start time: Wednesday, February 4, 2026, at 9:30 AM UTC
End time: Wednesday, February 4, 2026, at 4:22 PM UTC
Root cause: A code change contained within a recent service update was causing requests to be sent to an incorrect URL, resulting in impact.
Next steps:
- We're reviewing our update procedures to understand why impact to call queues 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 Feb 4 11:11:01 2026 |
|---|
| Description: | Title: Some users may be unable to toggle call queues on or off in the Microsoft Teams web or desktop client
User impact: Users may be unable to toggle call queues on or off in the Microsoft Teams web or desktop client.
More info: As a workaround, users may be able to use the Microsoft Teams mobile app to toggle call queues as expected.
Current status: We've identified that a code change contained within a recent service update is causing requests to be sent to an incorrect URL, resulting in impact. We're reverting the offending service update as a potential remediation action, and anticipate this process will complete by our next scheduled communications update.
Scope of impact: Some users hosted in the North America region attempting to toggle call queues in the Microsoft Teams web or desktop client may be impacted.
Start time: Wednesday, February 4, 2026, at 9:30 AM UTC
Root cause: A code change contained within a recent service update is causing request to be sent to an incorrect URL, resulting in impact.
Next update by: Wednesday, February 4, 2026, at 6:00 PM UTC
|
|---|
|
TM1226855 - Some users may experience PowerPoint slide download failures during Microsoft Teams meeting recordings
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 4 05:15:00 2026 |
|---|
| End Time: | Wed Feb 4 10:47:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 4 11:48:38 2026 |
|---|
| Root Cause: | The PowerPoint Live conversion service deployed new authentication components that weren't compatible with previous components, which resulted in failures when attempting to download PowerPoint slides. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 4 11:48:38 2026 |
|---|
| Description: | Title: Some users may experience PowerPoint slide download failures during Microsoft Teams meeting recordings
User impact: Users may have experienced PowerPoint slide download failures during Teams meeting recordings.
More info: Users' PowerPoint slide download failures resulted in unauthorized access errors and service unavailability.
As a workaround, users could have used regular screen sharing, which were captured in recordings.
Final status: We've completed the revert process to remove the impacting authentication components and successfully issued the new component configuration to resolve the incompatibility that triggered the failures, remediating impact for all users.
Scope of impact: Your organization was affected by this event, and some users attempting to utilize PowerPoint slide download failures during Microsoft Teams meeting recordings were impacted.
Start time: Wednesday, February 4, 2026, at 10:15 AM UTC
End time: Wednesday, February 4, 2026, at 3:47 PM UTC
Root cause: The PowerPoint Live conversion service deployed new authentication components that weren't compatible with previous components, which resulted in failures when attempting to download PowerPoint slides.
Next steps:
- We're reviewing our service deployment procedures to identify opportunities to avoid incompatibility issues and prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 4 09:17:58 2026 |
|---|
| Description: | Title: Some users may experience PowerPoint slide download failures during Microsoft Teams meeting recordings
User impact: Users may experience PowerPoint slide download failures during Teams meeting recordings.
More info: Users' PowerPoint slide download failures is resulting in unauthorized access errors and service unavailability.
As a workaround, users should avoid PowerPoint Live and instead use regular screen sharing, which will be captured in recordings.
Current status: We're reverting a recent deployment, which introduced a new network authentication component configuration, which has caused unauthorized errors for partner services such as the recorder. We're also working to issue a new compatible network authentication component configuration to resolve the incompatibility that triggered the failures and aim to provide a remediation timeline by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users attempting to utilize PowerPoint slide download failures during Microsoft Teams meeting recordings may be impacted.
Start time: Wednesday, February 4, 2026, at 10:15 AM UTC
Root cause: The PowerPoint Live conversion service deployed new authentication components that aren't compatible with previous components, which has resulted in failures when attempting to download PowerPoint slides.
Next update by: Wednesday, February 4, 2026, at 6:30 PM UTC
|
|---|
|
MV1097445 - Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 5 21:11:00 2025 |
|---|
| End Time: | Tue Feb 3 02:00:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 3 22:16:20 2026 |
|---|
| Root Cause: | A conflict between two SharePoint web parts which render on the same page was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 3 21:51:30 2026 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may have encountered errors when creating a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may have occurred specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix was in progress, users could have copied the SharePoint page URL and started the post directly within Viva Engage.
Final status: We've completed the additional changes and proceeded with the deployment of the code fix. After allowing time for the deployment to complete and for the fix to fully saturate, we've confirmed that impact has now been resolved.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may have encountered errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
End time: Tuesday, February 3, 2026, at 7:00 AM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page was resulting in impact.
Next steps:
- We're working to make additional changes to our service to provide additional support and harden our infrastructure to help prevent similar issues from occurring again in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jan 20 20:49:14 2026 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: During our process of initiating the deployment of the fix, we've identified an additional change to the code is needed in order to ensure it will successfully remediate impact without adversely impacting other aspects of the service. We've halted the deployment and are implementing the necessary change before proceeding with the deployment of the code fix. We expect the saturation will be complete, and the impact remediated by our next scheduled update.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, February 4, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Jan 12 20:54:45 2026 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We've tested and validated that our code solution has successfully resolved the issue in our testing environment. We're now progressing with a full deployment of the fix which we anticipate will complete by our next scheduled update.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, January 21, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Dec 23 19:06:20 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: Due to the complexity of the fix, additional testing is required before we're ready to start deploying the code solution to address the conflict between the two SharePoint Online web parts. We now anticipate that the deployment will begin by our next scheduled communications update.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Tuesday, January 13, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Dec 9 20:44:31 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: Our development of the code solution that we anticipate will address the conflict between the two SharePoint web parts which render on the same page, is ongoing. We're in the initial evaluation and development stages and we expect that we'll begin deployment of the full fix by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, December 24, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Nov 25 21:32:31 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to complete the fix for this issue and prepare it for deployment. We're still aiming to have the issue fully remediated by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, December 10, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Nov 10 20:57:44 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: Work on the fix is continuing though progress is slow due to the complexity of the issue. We anticipate that deployment of the fix will start in December 2025 and complete by the end of the calendar year. We'll provide updates on the timeline and ETA as they become available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, November 26, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Oct 28 21:01:53 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The development of the fix is ongoing, and due to the complexity of the issue, we're still anticipating deployment will start in December 2025. We'll provided an updated timeline and ETA once one becomes available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, November 12, 2025, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Oct 14 20:20:21 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to develop the fix and still anticipate the fix, and a deployment timeline will be provided by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, October 29, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Sep 30 20:40:02 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The development of the fix is taking longer than previously anticipated. We now anticipate that the fix will be completed, and a deployment timeline will be provided by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, October 15, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Sep 16 21:27:28 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The development of the fix is nearly completed. Once development is complete, which we anticipate will be in October 2025, we'll aim to provide a deployment timeline.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, October 1, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Sep 2 20:38:12 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to progress in our development of the fix. Once development is complete, which we anticipate will be in October 2025, we'll aim to provide a deployment timeline.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, September 17, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Aug 12 21:05:16 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to prepare the fix, which we still anticipate will be ready for deployment by early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, September 3, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 29 20:26:29 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The preparation of the fix deployment is ongoing. We're still projecting that the full release of the fix will complete around early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, August 13, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 15 20:24:52 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to prepare our fix for deployment. We're currently projecting its full release may complete around early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, July 30, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jul 1 20:30:42 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to develop a code fix for the conflicting SharePoint web parts. We anticipate that the fix and subsequent deployment will take an extended time to complete. We'll provide updates on the status as they become available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Root cause: A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact.
Next update by: Wednesday, July 16, 2025, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jun 17 22:53:13 2025 |
|---|
| Description: | Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We've identified an issue where users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page, and we've determined this issue stems from a conflict between two SharePoint web parts which render on the same page. Due to the complexity of their interaction, a code-level resolution is required to ensure that impact is fully alleviated. We're working to develop this solution and will provide updates as its development progresses.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Root cause: A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact.
Next update by: Wednesday, July 2, 2025, at 2:00 AM UTC
|
|---|
|
TM1198582 - Some guest users may be unable to unmute their mics in recurring Microsoft Teams meetings when recording is enabled
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Dec 17 09:09:52 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 3 21:41:35 2026 |
|---|
| Root Cause: | The impact is the result of an issue affecting the authentication components assigned to guest users when joining recurring Microsoft Teams meetings and recording the meeting in which stale components are being leveraged and causing an error to occur that prevents these guest users from unmuting their mics, sharing their screen, or using their camera. |
|---|
| Next Update: | Wednesday, February 18, 2026, at 2:00 AM UTC |
|---|
|
Details
| Time: | Tue Feb 3 21:41:35 2026 |
|---|
| Description: | Title: Some guest users may be unable to unmute their mics in recurring Microsoft Teams meetings when recording is enabled
User impact: Guest users may be unable to unmute their mics during recurring Microsoft Teams meetings when recording is enabled.
More info: This issue is specific to guest users who have joined Microsoft Teams meetings through the Windows or Mac desktop clients. This issue also impacts guest users when attempting to share their screen or turn on their camera during affected Microsoft Teams meetings. As a workaround, affected guest users can clear their cache to remove expired authentication components or utilize the Microsoft Teams web app or mobile app.
Current status: We've identified that an unrelated issue has delayed the rollout of the fix, and we now expect it to complete by March 2026. We've resolved the unrelated issue and are continuing to monitor the deployments progression.
Scope of impact: Some external guest participants attempting to unmute their microphones, share their screen, or use their camera during recurring Microsoft Teams meetings while recording may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
Root cause: The impact is the result of an issue affecting the authentication components assigned to guest users when joining recurring Microsoft Teams meetings and recording the meeting in which stale components are being leveraged and causing an error to occur that prevents these guest users from unmuting their mics, sharing their screen, or using their camera.
Next update by: Wednesday, February 18, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jan 20 21:07:46 2026 |
|---|
| Description: | Title: Some guest users may be unable to unmute their mics in recurring Microsoft Teams meetings when recording is enabled
User impact: Guest users may be unable to unmute their mics during recurring Microsoft Teams meetings when recording is enabled.
More info: This issue is specific to guest users who have joined Microsoft Teams meetings through the Windows or Mac desktop clients. This issue also impacts guest users when attempting to share their screen or turn on their camera during affected Microsoft Teams meetings. As a workaround, affected guest users can clear their cache to remove expired authentication components or utilize the Microsoft Teams web app or mobile app.
Current status: The rollout of the fix to address the issue on the Teams desktop client for Mac is progressing. Our estimate for the fix reaching affected users is early to mid February 2026, and we'll continue monitoring the progress to ensure it completes successfully.
Scope of impact: Some external guest participants attempting to unmute their microphones, share their screen, or use their camera during recurring Microsoft Teams meetings while recording may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
Root cause: The impact is the result of an issue affecting the authentication components assigned to guest users when joining recurring Microsoft Teams meetings and recording the meeting in which stale components are being leveraged and causing an error to occur that prevents these guest users from unmuting their mics, sharing their screen, or using their camera.
Next update by: Wednesday, February 4, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Mon Jan 5 20:58:49 2026 |
|---|
| Description: | Title: Some guest users may be unable to unmute their mics in recurring Microsoft Teams meetings when recording is enabled
User impact: Guest users may be unable to unmute their mics during recurring Microsoft Teams meetings when recording is enabled.
More info: This issue is specific to guest users who have joined Microsoft Teams meetings through the Windows or Mac desktop clients. This issue also impacts guest users when attempting to share their screen or turn on their camera during affected Microsoft Teams meetings. As a workaround, affected guest users can clear their cache to remove expired authentication components or utilize the Microsoft Teams web app or mobile app.
Current status: The process of preparing our fix to address the issue on the Teams desktop client for Mac is progressing as expected. Our estimation for the fix reaching affected users remains early February 2026, and we’ll continue monitoring this process to ensure it completes as expected by this time.
Scope of impact: Some external guest participants attempting to unmute their microphones, share their screen, or use their camera during recurring Microsoft Teams meetings while recording may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
Root cause: The impact is the result of an issue affecting the authentication components assigned to guest users when joining recurring Microsoft Teams meetings and recording the meeting in which stale components are being leveraged and causing an error to occur that prevents these guest users from unmuting their mics, sharing their screen, or using their camera.
Next update by: Wednesday, January 21, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Dec 17 21:22:47 2025 |
|---|
| Description: | Title: Some guest users may be unable to unmute their mics in recurring Microsoft Teams meetings when recording is enabled
User impact: Guest users may be unable to unmute their mics during recurring Microsoft Teams meetings when recording is enabled.
More info: This issue is specific to guest users who have joined Microsoft Teams meetings through the Windows or Mac desktop clients. This issue also impacts guest users when attempting to share their screen or turn on their camera during affected Microsoft Teams meetings. As a workaround, affected guest users can clear their cache to remove expired authentication components or utilize the Microsoft Teams web app or mobile app.
Current status: We've developed the fix to address the issue on the Teams desktop client for Mac and are preparing for its deployment to the affected environment. The deployment of the fix is expected to complete in early February 2026. We'll continue monitoring the progress and will provide updates on the status as they become available.
Scope of impact: Some external guest participants attempting to unmute their microphones, share their screen, or use their camera during recurring Microsoft Teams meetings while recording may be impacted. This information may be updated as our investigation continues.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
Root cause: The impact is the result of an issue affecting the authentication components assigned to guest users when joining recurring Microsoft Teams meetings and recording the meeting in which stale components are being leveraged and causing an error to occur that prevents these guest users from unmuting their mics, sharing their screen, or using their camera.
Next update by: Tuesday, January 6, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Dec 17 16:38:12 2025 |
|---|
| Description: | Title: Some guest users may be unable to unmute their mics in recurring Microsoft Teams meetings when recording is enabled
User impact: Guest users may be unable to unmute their mics during recurring Microsoft Teams meetings when recording is enabled.
More info: This issue is specific to guest users who have joined Microsoft Teams meetings through the Windows or Mac desktop clients. This issue also impacts guest users when attempting to share their screen or turn on their camera during affected Microsoft Teams meetings. As a workaround, affected guest users can clear their cache to remove expired authentication components or utilize the Microsoft Teams web app or mobile app.
Current status: We’ve discovered an issue affecting the authentication components assigned to guest users when joining recurring Microsoft Teams meetings and recording the meeting in which stale components are being leveraged and causing an error to occur that prevents these guest users from unmuting their mics, sharing their screen, or using their camera. We’ve deployed a fix that addressed this issue on the Teams desktop app for Windows; however, a fix to address this issue on the Teams desktop client for Mac is still under development. We’ll provide an estimate for the delivery of our Teams desktop client for Mac fix when available.
Scope of impact: Some external guest participants attempting to unmute their microphones, share their screen, or use their camera during recurring Microsoft Teams meetings while recording may be impacted.
Next update by: Thursday, December 18, 2025, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Dec 17 11:25:04 2025 |
|---|
| Description: | Title: Some guest users may be unable to unmute their mics in recurring Microsoft Teams meetings when recording is enabled
User impact: Guest users may be unable to unmute their mics during recurring Microsoft Teams meetings when recording is enabled.
More info: This issue is specific to guest users who have joined Microsoft Teams meetings through the Windows or Mac desktop clients. This issue also impacts guest users when attempting to share their screen or turn on their camera during affected Microsoft Teams meetings. As a workaround, affected guest users can clear their cache to remove expired authentication components or utilize the Microsoft Teams web app or mobile app.
Current status: We're analyzing support provided data alongside reviewing service health telemetry and any recent changes in order to isolate this issue's root cause. We're also working with your representatives to obtain logs from working and non-working scenarios to further inform this investigation.
Scope of impact: Your organization is affected by this event, and some external guest participant users attempting to unmute their microphones in cross-cloud Microsoft Teams meetings are impacted.
Next update by: Wednesday, December 17, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Dec 17 09:12:06 2025 |
|---|
| Description: | Title: Some guest users may be unable to unmute their mics in recurring Microsoft Teams meetings when recording is enabled
User impact: Guest users may be unable to unmute their mics during recurring Microsoft Teams meetings when recording is enabled.
More info: This issue is specific to guest users who have joined Microsoft Teams meetings through the Windows or Mac desktop clients. This issue also impacts guest users when attempting to share their screen or turn on their camera during affected Microsoft Teams meetings. As a workaround, affected guest users can clear their cache to remove expired authentication components or utilize the Microsoft Teams web app or mobile app.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some external guest participant users attempting to unmute their microphones in cross-cloud Microsoft Teams meetings are impacted.
Next update by: Wednesday, December 17, 2025, at 4:30 PM UTC
|
|---|
|
TM1218513 - Users may be unable to update or add Copilot Studio agents to Microsoft Teams and Microsoft Copilot (Microsoft 365)
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Jan 16 01:37:01 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 3 15:17:15 2026 |
|---|
| Root Cause: | A recent Copilot Studio update introduced a permissions issue preventing adding or changing Copilot Studio agents in Microsoft Teams and Copilot, resulting in impact. |
|---|
| Next Update: | Monday, February 16, 2026, at 9:00 PM UTC |
|---|
|
Details
| Time: | Tue Feb 3 15:17:15 2026 |
|---|
| Description: | Title: Users may be unable to update or add Copilot Studio agents to Microsoft Teams and Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to update or add Copilot Studio agents to Microsoft Teams and Copilot.
More info: Impacted users receive a "permissions needed" error when trying to update or add Copilot Studio agents from Copilot Studio to Teams and Copilot.
For the Teams adding impact specifically, this affects organizations where sideloading and the interaction of custom Microsoft Teams apps are disabled. This issue has been corrected in the following Teams build versions and updating to them will resolve the issue for users:
North America and Latin America regions - build 20260112.8
Europe, Middle East, Africa, and Asia Pacific regions - build 20260120.9
Current status: While we’ve validated that the issue is mitigated for users attempting to add or update Copilot Studio agents, we've determined that this scenario is also occurring when attempting to add or update these agents in Copilot. We've updates the Title, User impact, More info, and Scope of impact fields to reflect the full impact scenario. We're developing a fix aimed at alleviating this remaining impact with Copilot interactions, and estimate that deployment will begin by our next scheduled update.
Scope of impact: Users attempting to add or update Copilot Studio agents through Copilot Studio to Microsoft Teams and Copilot may be affected. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced a permissions issue preventing adding or changing Copilot Studio agents in Microsoft Teams and Copilot, resulting in impact.
Next update by: Monday, February 16, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 14:36:24 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams.
More info: Impacted users receive a "permissions needed" error when trying to update or add Copilot Studio agents in Teams.
Updated Teams build versions that include the fix are:
North America and Latin America regions - build 20260112.8
Europe, Middle East, Africa, and Asia Pacific regions - build 20260120.9
Current status: We’ve validated that the issue is mitigated for the majority of previously affected users. Users still seeing impact will need to update their Microsoft Teams client to the most recent version and then re-start the Teams client to remediate impact. Relevant build versions are provided in the More Info section. If these actions are still unsuccessful in resolving the issue, users will need to provide HTTP Archive format (HAR) logs while reproducing the impact so that we may investigate the persisting impact.
Scope of impact: This issue affects organizations where sideloading and the interaction of custom Microsoft Teams apps are disabled. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that affected the permissions required to make changes to Copilot Studio agents in Microsoft Teams, resulting in impact.
Next update by: Tuesday, February 3, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 04:03:35 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams.
More info: Impacted users receive a "permissions needed" error when trying to update or add Copilot Studio agents in Teams.
Current status: We’ve validated that the issue is mitigated for some users. For those still experiencing impact, we’re reviewing HTTP Archive (HAR) logs and are coordinating with your representatives to collect both working and additional non‑working samples of affected users to help us determine an appropriate fix.
Scope of impact: This issue affects organizations where sideloading and the interaction of custom Microsoft Teams apps are disabled. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that affected the permissions required to make changes to Copilot Studio agents in Microsoft Teams, resulting in impact.
Next update by: Monday, February 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Jan 30 20:06:29 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive a "permissions needed" error.
Current status: We’re awaiting confirmation from some affected users that our deployed solution has addressed impact.
Scope of impact: Users in organizations with the sideloading and interaction of custom apps disabled may be unable to update or add Copilot Studio agents within Microsoft Teams. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that affected the permissions required to make changes to Copilot Studio agents in Microsoft Teams, resulting in impact.
Next update by: Monday, February 2, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Fri Jan 30 18:53:34 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive a "permissions needed" error.
Current status: Our fix has completed deployment and we’re reaching out to some affected users to validate that our solution has addressed impact.
Scope of impact: Users in organizations with the sideloading and interaction of custom apps disabled may be unable to update or add Copilot Studio agents within Microsoft Teams. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that affected the permissions required to make changes to Copilot Studio agents in Microsoft Teams, resulting in impact.
Next update by: Saturday, January 31, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jan 27 18:06:59 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive a "permissions needed" error.
Current status: The deployment of our fix was delayed and is now underway. Our updated timeline projects the deployment will have completed and that impact will be remediated by our next scheduled communication update.
Scope of impact: Users in organizations with the sideloading and interaction of custom apps disabled may be unable to update or add Copilot Studio agents within Microsoft Teams. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that adversely affected the permissions required to make changes to Copilot Studio agents in Microsoft Teams, resulting in impact.
Next update by: Saturday, January 31, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Jan 23 14:51:53 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive a "permissions needed" error.
Current status: We’ve initiated the process of deploying our fix to address this issue to the affected environment and expect that the deployment should complete to resolve this problem by our next scheduled update.
Scope of impact: Users in organizations with the sideloading and interaction of custom apps disabled may be unable to update or add Copilot Studio agents within Microsoft Teams. This information may be updated as our investigation continues.
Start time: Monday, January 12, 2026, at 7:45 PM UTC
Root cause: A recent Copilot Studio update introduced an issue that adversely affected the permissions required to make changes to Copilot Studio agents in Teams, resulting in impact.
Next update by: Wednesday, January 28, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Jan 20 14:45:26 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive a "permissions needed" error.
Current status: We're completing the development of the code fix. We anticipate beginning the deployment to the affected environment by the time of our next scheduled update, at which time we expect to be able to provide an estimated timeline for remediation.
Scope of impact: Users in organizations with the sideloading and interaction of custom apps disabled may be unable to update or add Copilot Studio agents within Microsoft Teams. This information may be updated as our investigation continues.
Root cause: A recent Copilot Studio update introduced an issue that adversely affected the permissions required to make changes to Copilot Studio agents in Teams, resulting in impact.
Next update by: Friday, January 23, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 15:36:36 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive a "permissions needed" error.
Current status: We're continuing our preparation of a code fix to address the impact introduced by the recent update, and our initial projections indicate the fix will begin deploying by our next update. We'll provide an updated timeline for impact resolution as one becomes available.
Scope of impact: Users in organizations with the sideloading and interaction of custom apps disabled may be unable to update or add Copilot Studio agents within Microsoft Teams. This information may be updated as our investigation continues.
Root cause: A recent Copilot Studio update introduced an issue that adversely affected the permissions required to make changes to Copilot Studio agents in Teams, resulting in impact.
Next update by: Tuesday, January 20, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 02:04:13 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive a "permissions needed" error.
Current status: We've identified that a recent Copilot Studio update introduced an issue that adversely affected the permissions required to make changes to Copilot Studio agents in Teams, resulting in impact. We're working to prepare a code fix for deployment and anticipate we may have a timeline for remediation by our next update.
Scope of impact: Users in organizations with the sideloading and interaction of custom apps disabled may be unable to update or add Copilot Studio agents within Microsoft Teams. This information may be updated as our investigation continues.
Root cause: A recent Copilot Studio update introduced an issue that adversely affected the permissions required to make changes to Copilot Studio agents in Teams, resulting in impact.
Next update by: Friday, January 16, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 01:37:47 2026 |
|---|
| Description: | Title: Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error
User impact: Users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive a "permissions needed" error.
Current status: We're investigating a potential issue with Copilot Studio agents within Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1226532 - Some users may experience issues when utilizing specific Microsoft Copilot (Microsoft 365) intelligence features
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 3 08:50:00 2026 |
|---|
| End Time: | Tue Feb 3 11:45:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Feb 3 14:59:25 2026 |
|---|
| Root Cause: | A recent configuration change which was intended to optimize performance resulted in impact to Augmentation Loop, which caused users of Copilot features within Microsoft 365 apps to experience issues or delays as outlined in the "More info" section of this communication. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 3 14:59:25 2026 |
|---|
| Description: | Title: Some users may experience issues when utilizing specific Microsoft Copilot (Microsoft 365) intelligence features
User impact: Users may have experienced issues when utilizing specific Microsoft Copilot intelligence features.
More info: The known Copilot impact scenarios and features within Microsoft 365 services such as Microsoft Teams, Word, Excel, PowerPoint, SharePoint Online, ClipChamp, and Microsoft Stream are listed below:
Impacted Copilot intelligence features:
- Copilot features within Microsoft 365 apps may have returned delayed responses, timeout errors, or no results
- Text prediction or Copilot summaries within Microsoft 365 services were delayed, returned no results, or returned timeout errors.
- Text prediction or ContextIQ queries were delayed, returned no results, or returned timeout errors.
- Sensitivity auto-labelling may not have been applied as expected.
Final status: We've isolated that a recent configuration change which was intended to optimize performance resulted in impact to Augmentation Loop, which caused users of Copilot features within Microsoft 365 apps to experience issues or delays as outlined in the "More info" section of this communication. We've rolled back the offending configuration change and validated this resolved the majority of the reported impact scenarios by Tuesday, February 3, 2026, at 2:40 PM UTC. We completed an internal monitoring period to monitor and validate full remediation, which completed on Tuesday, February 3, 2026, at 4:45 PM UTC, and allowed us to confirm that our rollback successfully remediated user impact.
Scope of impact: Some users may have experienced issues or delays when utilizing specific Microsoft Copilot intelligence features such as text prediction, Copilot summaries, or sensitivity auto-labelling.
Start time: Tuesday, February 3, 2026, at 1:50 PM UTC
End time: Tuesday, February 3, 2026, at 4:45 PM UTC
Root cause: A recent configuration change which was intended to optimize performance resulted in impact to Augmentation Loop, which caused users of Copilot features within Microsoft 365 apps to experience issues or delays as outlined in the "More info" section of this communication.
Next steps:
- We're analyzing the offending configuration change to isolate why the potential for impact wasn't caught during our update testing and validation phases. This analysis will help us to improve the resilience and performance of our future updates, while also helping us to ensure similar impact scenarios don't occur in the future.
This is the final update for the event.
|
|---|
|
EX1226468 - Group owners may be unable to modify group memberships in the Global Address Book in the classic Outlook desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 2 19:15:00 2026 |
|---|
| End Time: | Tue Feb 3 12:29:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 3 13:29:34 2026 |
|---|
| Root Cause: | A recent feature change intended to enable the use of a new API for managing distribution group modifications introduced an issue resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 3 13:29:34 2026 |
|---|
| Description: | Title: Group owners may be unable to modify group memberships in the Global Address Book in the classic Outlook desktop client
User impact: Group owners were unable to modify group memberships in the Global Address Book in the classic Outlook desktop client.
More info: Distribution Groups may have been able to be modified, but Security Groups may have been affected.
While we worked towards mitigation, affected users may have been able to utilize the new Outlook desktop client or Outlook on the web to perform Distribution Group modifications.
Final status: We've identified that a recent feature change intended to enable the use of a new API for managing distribution group modifications introduced an issue resulting in impact. We've reverted the affecting change and confirmed that impact was successfully remediated.
Scope of impact: This issue may have affected all group owners modifying certain group memberships through the Outlook Address Book in the classis Outlook desktop client.
Start time: Tuesday, February 3, 2026, at 12:15 AM UTC
End time: Tuesday, February 3, 2026, at 5:29 PM UTC
Root cause: A recent feature change intended to enable the use of a new API for managing distribution group modifications introduced an issue resulting in impact.
Next steps:
- We're reviewing the affecting change to understand why it resulted in impact to better prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 3 12:00:24 2026 |
|---|
| Description: | Title: Group owners may be unable to modify group memberships in the Global Address Book in the classic Outlook desktop client
User impact: Group owners are unable to modify group memberships in the Global Address Book in the classic Outlook desktop client.
More info: Distribution Groups may be modified, but Security Groups may be affected.
While we work towards mitigation, affected users may be able to utilize the new Outlook desktop client or Outlook on the web to perform Distribution Group modifications.
Current status: We're reviewing Problem Steps Recorder (PSR) logs in parallel with Fiddler trace logs collected from an affected user to identify and isolate any errors which may be contributing to impact for further investigation.
Scope of impact: This issue may affect all group owners modifying certain group memberships through the Outlook Address Book in the classis Outlook desktop client.
Next update by: Tuesday, February 3, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Feb 3 11:38:08 2026 |
|---|
| Description: | Title: Group owners may be unable to modify group memberships in the Global Address Book in the classic Outlook desktop client
User impact: Group owners are unable to modify group memberships in the Global Address Book in the classic Outlook desktop client.
More info: Distribution Groups may be modified, but Security Groups may be affected.
While we work towards mitigation, affected users may be able to utilize the new Outlook desktop client or Outlook on the web to perform Distribution Group modifications.
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.
|
|---|
|
TM1226123 - Users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jan 30 03:34:00 2026 |
|---|
| End Time: | Tue Feb 3 11:50:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 3 12:42:01 2026 |
|---|
| Root Cause: | A subset of tenants within the affected environment have a specific company configuration flag being applied to them despite lacking the license to have this flag applied. This was resulting in users of the "New Calendar" setting to been unable to utilize the Webinar creation option in the Microsoft Teams desktop or web app calendars. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 3 12:42:01 2026 |
|---|
| Description: | Title: Users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars
User impact: Users didn't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars.
More info: User feedback indicated the issue was specific to Teams Calendar scenarios when the "New Calendar" setting was enabled. While we were focused on remediation, users could disable the "New Calendar" setting in the Teams desktop app or web app as a temporary workaround.
Final status: We've completed deployment of our two fixes to disable the "New Calendar" experience for affected tenants, and have validated with a subset of affected users that our actions successfully remediated impact. Users can now utilize the Webinar creation option in the Microsoft Teams desktop app or web app calendars using the legacy calendar experience.
Scope of impact: Users whose organization was hosted within the Microsoft Government Cloud attempting to create Webinars may have been impacted.
Start time: Friday, January 30, 2026, at 8:34 AM UTC
End time: Tuesday, February 3, 2026, at 4:50 PM UTC
Root cause: A subset of tenants within the affected environment have a specific company configuration flag being applied to them despite lacking the license to have this flag applied. This was resulting in users of the "New Calendar" setting to been unable to utilize the Webinar creation option in the Microsoft Teams desktop or web app calendars.
Next steps:
- We're working to isolate why the offending company configuration flag was being applied to affected tenants. This analysis will help us to isolate potential discrepancies resulting in impact and to create remediation actions which will allow us to re-enable the "New Calendar" experience at a later time.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 3 11:25:52 2026 |
|---|
| Description: | Title: Users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars
User impact: Users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars.
More info: User feedback indicates the issue is specific to Teams Calendar scenarios when the "New Calendar" setting is enabled. While we're focused on remediation, users can disable the "New Calendar" setting in the Teams desktop app or web app as a temporary workaround.
Current status: After further analysis, we've determined that impact is limited to a subset of tenants within the affected environment who have a specific company configuration flag being applied to them despite lacking the license to have this flag applied. This is resulting in users of the "New Calendar" setting being unable to utilize the Webinar creation option in the Microsoft Teams desktop or web app calendars. While we continue to investigate why the configuration flag is being applied, we're implementing two code fixes to disable the "New Calendar" experience for affected tenants, which will mitigate the impact scenario. Although the timeline for implementing these fixes is subject to change, we currently estimate that we may finish deploying and enabling the fixes for your organization by the time of our next communication update.
Scope of impact: Users whose organization is hosted within the Microsoft Government Cloud attempting to create Webinars may be impacted. This information may be updated as our investigation continues.
Root cause: A subset of tenants within the affected environment have a specific company configuration flag being applied to them despite lacking the license to have this flag applied. This is resulting in users of the "New Calendar" setting to be unable to utilize the Webinar creation option in the Microsoft Teams desktop or web app calendars.
Next update by: Tuesday, February 3, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Feb 3 10:10:18 2026 |
|---|
| Description: | Title: Some users may not have the Webinar creation option in the Microsoft Teams desktop app or web app calendars
User impact: Users may not have the Webinar creation option in the Microsoft Teams desktop app or web app calendars.
Current status: We’ve successfully deployed the configuration changes, but impact persists. We suspect a recent Calendar feature update may be contributing to the issue and are validating whether reverting the change will remediate the impact.
Scope of impact: Some users whose organization is hosted within the Microsoft Government Cloud attempting to create Webinars may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, February 3, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Feb 3 06:07:09 2026 |
|---|
| Description: | Title: Some users may not have the Webinar creation option in the Microsoft Teams desktop app or web app calendars
User impact: Users may not have the Webinar creation option in the Microsoft Teams desktop app or web app calendars.
More info: User feedback indicates the issue is specific to Teams Calendar scenarios when the "New Calendar" setting is enabled. While we're focused on remediation, users can disable the "New Calendar" setting in the Teams desktop app or web app as a temporary workaround.
Current status: We're continuing to roll out the additional configuration changes, which we suspect may resolve the impact and give us further insight into the underlying issue.
Scope of impact: Some users in GCC attempting to create Webinars may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, February 3, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Tue Feb 3 02:03:24 2026 |
|---|
| Description: | Title: Some users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars
User impact: Users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars.
More info: User feedback indicates the issue is specific to Teams Calendar scenarios when the "New Calendar" setting is enabled. While we're focused on remediation, users can disable the "New Calendar" setting in the Teams desktop app or web app as a temporary workaround.
Current status: We've identified that some configuration issues may have occurred during our rollout of some recent service updates as part of our effort to introduce the New Calendar experience to your environment. We're rolling out some additional configuration changes we're theorizing may be able to resolve the impact and give us further insight into the underlying issue, and anticipate they may take effect by our next scheduled update.
Scope of impact: Your organization is impacted by this event, and some users attempting to create Webinars in the Teams desktop client and web app are affected. This information may be updated as our investigation continues.
Next update by: Tuesday, February 3, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Mon Feb 2 19:10:19 2026 |
|---|
| Description: | Title: Some users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars
User impact: Users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars.
More info: User feedback indicates the issue is specific to Teams Calendar scenarios when the "New Calendar" setting is enabled. While we're focused on remediation, users can disable the "New Calendar" setting in the Teams desktop app or web app as a temporary workaround.
Current status: We've received feedback from your representatives indicating the issue is specific to Teams Calendar scenarios when the "New Calendar" setting is enabled, and that users can disable this setting to avoid impact as a temporary workaround. We're continuing with further analysis of the latest HTTP Archive format (HAR) network trace logs collected from reproductions of the scenario to gain insight into the source of impact and determine our next steps.
Scope of impact: Your organization is impacted by this event, and some users attempting to create Webinars in the Teams desktop client and web app are affected.
Next update by: Tuesday, February 3, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Mon Feb 2 18:24:18 2026 |
|---|
| Description: | Title: Some users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars
User impact: Users don't have the Webinar creation option in the Microsoft Teams desktop app or web app calendars.
More info: This issue only impacts Teams calendars that are based on calendars created through the new Outlook desktop client or Outlooks on the web. Users with the option to switch to the classic Teams desktop client can bypass this issue and create a Webinar through the calendar.
Current status: We're reviewing the calendar data flow between Outlook and Microsoft Teams as we suspect that it may be blocked in the request path.
Scope of impact: Your organization is impacted by this event, and some users attempting to create Webinars in the Teams desktop client and web app are affected.
Next update by: Tuesday, February 3, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Feb 2 15:59:02 2026 |
|---|
| Description: | Title: Users can't see or use the webinar option in Microsoft Teams desktop or web app after an update
User impact: Users can't see or use the webinar option in Microsoft Teams desktop or web app after an update.
Current status: We're reviewing support case data provided by your organization's representatives from impacted users while analyzing recent Microsoft Teams service updates to begin isolating this issue's root cause
Scope of impact: Your organization is impacted by this event, and all users and admins are affected.
Next update by: Monday, February 2, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 15:20:24 2026 |
|---|
| Description: | Title: Users can't see or use the webinar option in Microsoft Teams desktop or web app after an update
User impact: Users can't see or use the webinar option in Microsoft Teams desktop or web app after an update.
Current status: We're investigating a potential issue with Microsoft Teams where users are unable to see or use the webinar option in Microsoft Teams after updating their client versions to those specified within the More Info section. We're checking for impact to your organization and we'll provide an update within 30 minutes.
|
|---|
|
WP1226141 - Admins may be unable to provision Windows 365 Cloud PCs and may get provisioning failures
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 2 13:32:00 2026 |
|---|
| End Time: | Mon Feb 2 19:20:00 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | Manageability |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 2 19:39:51 2026 |
|---|
| Root Cause: | A backend service dependency responsible for storage wasn't operating with the correct settings due to a recent configuration change, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 2 19:39:51 2026 |
|---|
| Description: | Title: Admins may be unable to provision Windows 365 Cloud PCs and may get provisioning failures
User impact: Admins may have been unable to provision their Cloud PCs and may have received provisioning failures.
More info: New provisioning and reprovisioning attempts may have been impacted.
Final status: We've confirmed that the deployment to reintegrate the correct settings to the backend service dependency completed as expected. Our service health telemetry validated that the errors have stopped as a result, and that impact has been resolved by our actions.
Scope of impact: Admins attempting to provision or reprovision their Cloud PCs may have been unable to do so and may have received provisioning failures.
Start time: Monday, February 2, 2026, at 6:32 PM UTC
End time: Tuesday, February 3, 2026, at 12:20 AM UTC
Root cause: A backend service dependency responsible for storage wasn't operating with the correct settings due to a recent configuration change, which resulted in impact.
Next steps:
- We're analyzing why the update for the backend service dependency responsible for storage contained a configuration issue so that we can improve our check process in an effort to avoid impact like this in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 2 17:50:41 2026 |
|---|
| Description: | Title: Admins may be unable to provision Windows 365 Cloud PCs and may get provisioning failures
User impact: Admins may be unable to provision their Cloud PCs and may get provisioning failures.
More info: New provisioning and reprovisioning attempts may be impacted.
Current status: We've identified that a backend service dependency responsible for storage isn't operating with the correct settings due to a recent configuration change. We've developed, tested, and are now deploying a solution that will reintroduce the correct settings.
Scope of impact: Admins attempting to provision or reprovision their Cloud PCs may be unable to do so and may get provisioning failures.
Start time: Monday, February 2, 2026, at 6:32 PM UTC
Root cause: A backend service dependency responsible for storage isn't operating with the correct settings due to a recent configuration change, which is resulting in impact.
Next update by: Tuesday, February 3, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Feb 2 16:27:05 2026 |
|---|
| Description: | Title: Admins may be unable to provision Windows 365 Cloud PCs and may get provisioning failures
User impact: Admins may be unable to provision their Cloud PCs and may get provisioning failures.
Current status: We've identified errors in our service health telemetry and are analyzing them to pinpoint the origin of impact. This investigation will allow us to determine the next actions we'll take in our effort to resolve this issue.
Scope of impact: Admins attempting to provision or reprovision their Cloud PCs may be unable to do so and may get provisioning failures.
Next update by: Monday, February 2, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Feb 2 16:13:25 2026 |
|---|
| Description: | Title: Admins may be unable to provision Windows 365 Cloud PCs and may get provisioning failures
User impact: Admins may be unable to provision their Cloud PCs and may get provisioning failures.
Current status: We're investigating a potential issue in which admins may be unable to provision their Cloud PCs and may get provisioning failures. We'll provide an update within 30 minutes.
|
|---|
|
MP1226160 - Users' Microsoft Purview Data Loss Prevention (DLP) policies in Australia may intermittently fail
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 2 15:46:00 2026 |
|---|
| End Time: | Mon Feb 2 19:28:29 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Feb 2 19:29:08 2026 |
|---|
| Root Cause: | Recent network configuration changes intended to improve service reliability caused impact to DLP policies. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 2 19:29:08 2026 |
|---|
| Description: | Title: Users' Microsoft Purview Data Loss Prevention (DLP) policies in Australia may intermittently fail
User impact: Users' Microsoft Purview Data Loss Prevention (DLP) policies in Australia may have intermittently fail.
More info: Affected services included but may have not been limited to the application of DLP policies in:
- Exchange Online
- SharePoint Online
- Microsoft OneDrive
- Microsoft Teams
- Microsoft Purview Data Loss Prevention for Endpoint
- Microsoft Defender for Cloud Apps
- Power BI
Final status: We identified recent network configuration changes that caused the impact to DLP policies. We reverted the changes and monitored the telemetry to validate that the impact was remediated.
Scope of impact: Any user in the Australia region may have been intermittently affected.
Start time: Monday, February 2, 2026, at 8:46 PM UTC
End time: Monday, February 2, 2026, at 11:55 PM UTC
Root cause: Recent network configuration changes intended to improve service reliability caused impact to DLP policies.
Next steps:
- We're further reviewing the recently implemented network configuration changes to better understand what triggered the initial impact, which will help us in finding ways to avoid similar situations in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 2 18:00:50 2026 |
|---|
| Description: | Title: Users' Microsoft Purview Data Loss Prevention (DLP) policies in Australia may intermittently fail
User impact: Users' Microsoft Purview Data Loss Prevention (DLP) policies in Australia may intermittently fail.
More info: Affected services include but may not be limited to the application of DLP policies in:
- Exchange Online
- SharePoint Online
- Microsoft OneDrive
- Microsoft Teams
- Microsoft Purview Data Loss Prevention for Endpoint
- Microsoft Defender for Cloud Apps
- Power BI
Current status: Our monitoring has identified an increase in DLP request failures affecting the Australia region. We're reviewing service telemetry to better understand the impact scenario and determine our next steps.
Scope of impact: Any user in the Australia region may be intermittently affected.
Next update by: Tuesday, February 3, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Feb 2 17:36:51 2026 |
|---|
| Description: | Title: Some users in Australia may experience reduced effectiveness of Microsoft Purview Data Loss Prevention (DLP) policies
User impact: Users may experience reduced effectiveness of DLP polices across multiple Microsoft 365 services.
More info: Affected services include but may not be limited to the application of DLP policies in:
- Exchange Online
- SharePoint Online
- Microsoft OneDrive
- Microsoft Teams
- Microsoft Purview Data Loss Prevention for Endpoint
- Microsoft Defender for Cloud Apps
- Power BI
Current status: We're investigating a potential issue with Microsoft Purview Data Loss Prevention and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1225246 - Users may see issues with their templated subscription email in Power BI
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 29 04:21:00 2026 |
|---|
| End Time: | Mon Feb 2 13:00:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 2 19:28:30 2026 |
|---|
| Root Cause: | A recent change altering the subscription email template for Power BI affected users' existing subscription email templates. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 2 19:28:30 2026 |
|---|
| Description: | Title: Users may see issues with their templated subscription email in Power BI
User impact: Users may have seen issues with their templated subscription email in Power BI.
More info: Specifically, users may have observed that the subscription email template was altered due to a change rolled out altering the template format.
Customers may have seen additional revisions to this template in the future and it is recommended to update processes to be resilient to these changes. We apologize for the disruption this change has caused. Future updates to this template will be communicated with notice so users can update their processes appropriately.
Final status: We've completed reverting the template to it's previous default state, and after a period of monitoring, we've confirmed impact was remediated.
Scope of impact: Users leveraging templated subscription emails in Power BI may have been impacted.
Start time: Thursday, January 29, 2026, at 9:21 AM UTC
End time: Monday, February 2, 2026, at 6:00 PM UTC
Root cause: A recent change altering the subscription email template for Power BI affected users' existing subscription email templates.
Next steps:
- To help prevent similar impact in the future, we're further reviewing our change release procedures to identify issues before being released.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 30 20:38:40 2026 |
|---|
| Description: | Title: Users may see issues with their templated subscription email in Power BI
User impact: Users may see issues with their templated subscription email in Power BI.
More info: Specifically, users may observe that the subscription email template has been altered due to a change rolled out altering the template format.
Customers may see additional revisions to this template in the future and it is recommended to update processes to be resilient to these changes. We apologize for the disruption this change has caused. Future updates to this template will be communicated with notice so users can update their processes appropriately.
Current status: We've determined that a recent change altering the subscription email template for Power BI affected users' existing subscription email templates. We're moving to roll back the template to the previous default and anticipate we'll have an estimated timeline for full remediation by our next scheduled update.
Scope of impact: Users leveraging templated subscription emails in Power BI may be impacted.
Start time: Thursday, January 29, 2026, at 9:21 AM UTC
Root cause: A recent change altering the subscription email template for Power BI affected users' existing subscription email templates.
Next update by: Tuesday, February 3, 2026, at 2:00 AM UTC
|
|---|
|
TM1224481 - Some users may see stale profile pictures or profile information for other users within Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 27 04:00:00 2026 |
|---|
| End Time: | Sat Jan 31 15:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 2 13:07:59 2026 |
|---|
| Root Cause: | A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 2 13:07:59 2026 |
|---|
| Description: | Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may have seen stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affected some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Final status: Following our reversion of the offending infrastructure update and the isolated code regression, our internal service telemetry has verified that impact has been remediated.
Scope of impact: Some users viewing the profile pictures or profile information for other users within Microsoft Teams may have been impacted.
Start time: Tuesday, January 27, 2026, at 9:00 AM UTC
End time: Saturday, January 31, 2026, at 8:00 PM UTC
Root cause: A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure resulted in impact.
Next steps:
- We're further analyzing the offending infrastructure update and the introduced code regression to help us improve our pre-deployment testing and validation processes in our effort to prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 30 18:21:50 2026 |
|---|
| Description: | Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: Reverting the offending service update is taking longer than expected, but its been reverted in 94 percent of the affected environment. We anticipate this process will complete by our next scheduled communications update.
Scope of impact: Some users viewing the profile pictures or profile information for other users within Microsoft Teams may be impacted.
Start time: Tuesday, January 27, 2026, at 9:00 AM UTC
Root cause: A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing impact.
Next update by: Monday, February 2, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jan 29 17:59:05 2026 |
|---|
| Description: | Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: We've initiated the reversion of the offending service update, and we anticipate this process will complete by our next scheduled communications update.
Scope of impact: Some users viewing the profile pictures or profile information for other users within Microsoft Teams may be impacted.
Start time: Tuesday, January 27, 2026, at 9:00 AM UTC
Root cause: A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing impact.
Next update by: Saturday, January 31, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Jan 29 15:35:46 2026 |
|---|
| Description: | Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: We're continuing to prepare the reversion of the offending update, which we anticipate will begin by our next scheduled communication update.
Scope of impact: Some users viewing the profile pictures or profile information for other users within Microsoft Teams may be impacted.
Start time: Tuesday, January 27, 2026, at 9:00 AM UTC
Root cause: A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing impact.
Next update by: Friday, January 30, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Jan 29 14:42:57 2026 |
|---|
| Description: | Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: We've identified that a code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing the impact. We're preparing to revert the offending update to remediate the issue, and we'll aim to provide a timeline for the reversion to complete by our next scheduled communications update.
Scope of impact: Some users viewing the profile pictures or profile information for other users within Microsoft Teams may be impacted.
Start time: Tuesday, January 27, 2026, at 9:00 AM UTC
Root cause: A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing impact.
Next update by: Thursday, January 29, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Jan 29 14:23:39 2026 |
|---|
| Description: | Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: We're investigating a potential issue with some users seeing stale profile pictures or profile information for other users within Microsoft Teams, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
WP1218937 - Users may experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions
| Status: | investigationSuspended |
|---|
| Start Time: | Sat Jan 17 17:37:26 2026 |
|---|
| End Time: | Sat Jan 31 18:03:14 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jan 31 18:03:27 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jan 31 18:03:27 2026 |
|---|
| Description: | Title: Users may experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions
User impact: If action is not taken, users may continue to experience intermittent issues signing-in to Cloud PC sessions.
Final status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
|
|---|
|
| Time: | Sat Jan 17 17:41:57 2026 |
|---|
| Description: | Title: Users may experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions
User impact: If action is not taken, users may continue to experience intermittent issues signing-in to Cloud PC sessions.
Current status: Due to the code misconfiguration introduced with the Windows security update (KB5074109), users may be experiencing intermittent sign-in or connection failures for Windows 365 Cloud PC sessions. While we recommended users follow the Known Issue Rollback (KIR) instructions to resolve the issue, a recently released out-of-band (OOB) update has deployed which is now the recommended action for resolving the issue. If action isn't taken to install the OOB update, users may continue to experience intermittent issues signing-in to Cloud PC sessions.
This communication will expire in 14 days and is scheduled to remain active for the full duration.
|
|---|
|
MO1224866 - Some users may have been unable to export usage reports from the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 29 08:07:00 2026 |
|---|
| End Time: | Fri Jan 30 19:30:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Sat Jan 31 04:20:56 2026 |
|---|
| Root Cause: | A recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may have prevented users from exporting usage reports. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Jan 31 04:19:13 2026 |
|---|
| Description: | Title: Some users may have been unable to export usage reports from the Microsoft 365 admin center
User impact: Users may have been unable to export usage reports from the Microsoft 365 admin center.
More info: Users may have also encountered errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Final status: We’ve confirmed following the feedback from some affected users that impact has been remediated.
Scope of impact: Some users attempting to export usage reports in the Microsoft 365 admin center may have been impacted.
Start time: Thursday, January 29, 2026, at 1:07 PM UTC
End time: Saturday, January 31, 2026, at 12:30 AM UTC
Root cause: A recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may have prevented users from exporting usage reports.
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: | Fri Jan 30 19:35:25 2026 |
|---|
| Description: | Title: Some users may be unable to export usage reports from the Microsoft 365 admin center
User impact: Users may be unable to export usage reports from the Microsoft 365 admin center.
More info: Users may also encounter errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Current status: We’ve initiated the process of deploying the code fix and we’re validating with affected users that have received the fix to ensure its operating as expected to resolve this issue.
Scope of impact: Some users attempting to export usage reports in the Microsoft 365 admin center may be impacted.
Start time: Thursday, January 29, 2026, at 11:00 PM UTC
Root cause: A recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may prevent users from exporting usage reports.
Next update by: Saturday, January 31, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Fri Jan 30 14:29:03 2026 |
|---|
| Description: | Title: Some users may be unable to export usage reports from the Microsoft 365 admin center
User impact: Users may be unable to export usage reports from the Microsoft 365 admin center.
More info: Users may also encounter errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Current status: We've identified that a recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may prevent users from exporting usage reports. We've created and are validating a code fix that will deploy shortly and remediate impact by our next scheduled update.
Scope of impact: Some users attempting to export usage reports in the Microsoft 365 admin center may be impacted.
Start time: Thursday, January 29, 2026, at 11:00 PM UTC
Root cause: A recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may prevent users from exporting usage reports.
Next update by: Saturday, January 31, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Jan 30 05:56:49 2026 |
|---|
| Description: | Title: Some users are unable to export usage reports from the Microsoft 365 admin center
User impact: Users are unable to export usage reports from the Microsoft 365 admin center.
More info: Users may also encounter errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Current status: We're reviewing a potential code change and available logs to help determine the root cause and mitigation plan.
Scope of impact: Some users in the North US region attempting to export usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Friday, January 30, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Jan 30 03:49:42 2026 |
|---|
| Description: | Title: Some users are unable to export usage reports from the Microsoft 365 admin center
User impact: Users are unable to export usage reports from the Microsoft 365 admin center.
More info: Users may also encounter errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users in the North US region attempting to export usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Friday, January 30, 2026, at 11:00 AM UTC
|
|---|
|
TM1222851 - Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 14 22:40:00 2026 |
|---|
| End Time: | Fri Jan 30 13:38:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jan 30 17:41:06 2026 |
|---|
| Root Cause: | A recent service library update introduced a code regression that was resulting in users intermittently seeing a red border after screensharing was stopped in Microsoft Teams. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jan 30 17:37:49 2026 |
|---|
| Description: | Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may have intermittently seen a red border after screensharing was stopped in Microsoft Teams
More info: This specifically affected users of the Microsoft Teams version 26005.204.4249.1621.
Final status: We've completed the deployment of our code solution and confirmed through monitoring service health telemetry that the impact is remediated for users who update to the latest version of Microsoft Teams.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilized screensharing functionality in Microsoft Teams may have been intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
End time: Friday, January 30, 2026, at 6:38 PM UTC
Root cause: A recent service library update introduced a code regression that was resulting in users intermittently seeing a red border after screensharing was stopped in Microsoft Teams.
Next steps:
- We're reviewing our update procedures to understand why impact to screensharing functionality wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 30 11:25:48 2026 |
|---|
| Description: | Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We're monitoring our code solution deployment as it nears saturation and we estimate that this process will be complete by our next scheduled update. As this saturation finalizes, users may incrementally be remediated from impact.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Saturday, January 31, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Jan 28 20:27:39 2026 |
|---|
| Description: | Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We’ve initiated a safe process to expedite our code solution, and we expect our solution to complete deployment by our next scheduled update.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Friday, January 30, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jan 28 18:54:09 2026 |
|---|
| Description: | Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We’re continuing to deploy our code solution to the affected environment and are working on assessing alternative methods to safely expedite this deployment process to remediate impact as swiftly as possible. We'll provide a timeline for our solution to complete deployment as one becomes available.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Thursday, January 29, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jan 27 18:04:30 2026 |
|---|
| Description: | Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We've finished the validations for our fix which we've begun deploying to the affected environment. We'll aim to provide a timeline for the deployment to complete by our next scheduled communications update.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Thursday, January 29, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Jan 27 14:47:32 2026 |
|---|
| Description: | Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We've developed our fix to repair the regression and are doing final validations before deploying the solution to the affected environments. Once available, we'll provide a resolution timeline.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Wednesday, January 28, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Jan 27 11:38:22 2026 |
|---|
| Description: | Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We're continuing to develop our fix to repair the regression, which we anticipate will be ready for deployment by our next scheduled communication update.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Tuesday, January 27, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Jan 27 10:43:23 2026 |
|---|
| Description: | Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users utilizing the Windows desktop version 26005.204.4249.1621
Current status: We've identified that a recent service library update has introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams. We're developing a fix to repair the regression and anticipate this process to be complete by our next scheduled update time.
Scope of impact: Impact is specific to any user with the Windows desktop version 26005.204.4249.1621 who are served through the affected infrastructure.
Root cause: A recent service library update has introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Tuesday, January 27, 2026, at 6:00 PM UTC
|
|---|
|
EX1224375 - Users routing their Exchange Online email through a third-party protection service may have send and receive delays
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jan 26 01:00:00 2026 |
|---|
| End Time: | Fri Jan 30 13:25:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail timely delivery |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jan 30 14:43:40 2026 |
|---|
| Root Cause: | A cache limit configuration that helps facilitate the impact scenario process with SMTP mail flow was misconfigured, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jan 30 14:26:22 2026 |
|---|
| Description: | Title: Users routing their Exchange Online email through a third-party protection service may have send and receive delays
User impact: Users' Exchange Online email routed through a third-party protection service may have been delayed.
More info: This issue specifically impacted users who use Simple Mail Transfer Protocol (SMTP) as their Exchange Online connection method and routed their email messages through a specific third-party email protection service. The email delays, which impacted both sending and receiving email, occurred in all Exchange Online connection methods.
Final status: We've fully implemented our identified configuration change and confirmed using internal telemetry that it effectively mitigated this issue. We determined that a cache limit configuration that helps facilitate the impact scenario process with SMTP mail flow was misconfigured, resulting in impact.
Scope of impact: This problem may have impacted any user sending or receiving email messages when leveraging a specific third-party email protection service.
Start time: Monday, January 26, 2026, at 6:00 AM UTC
End time: Friday, January 30, 2026, at 6:25 PM UTC
Root cause: A cache limit configuration that helps facilitate the impact scenario process with SMTP mail flow was misconfigured, resulting in impact.
Next steps:
- We're continuing our research into identifying the root cause of this impacting event to better understand how to prevent it from happening again in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 30 12:49:22 2026 |
|---|
| Description: | Title: Users routing their Exchange Online email through a third-party protection service may have send and receive delays
User impact: Users routing their Exchange Online email through a third-party protection service may have send and receive delays.
More info: This issue specifically impacts users who use Simple Mail Transfer Protocol (SMTP) as their connection method and route their email messages through a specific third-party email protection service. The email delays, which impacts both sending and receiving email, occurs in all Exchange Online connection methods.
Current status: Though our investigation into the root cause of this impacting issue is ongoing, we've identified and implemented a configuration change in effort to mitigate the problem. We're reviewing our internal telemetry to assess if the configuration change was effective. Please note that we've updated the Title, User impact, and More info of this communication to better reflect the impact of the event.
Scope of impact: This problem may impact any user sending or receiving email messages when leveraging a specific third-party email protection service.
Next update by: Friday, January 30, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Thu Jan 29 16:19:48 2026 |
|---|
| Description: | Title: Users may experience delays when sending or receiving Exchange Online email messages
User impact: Users may experience delays when sending or receiving Exchange Online email messages.
More info: This issue specifically impacts users who are on Simple Mail Transfer Protocol (SMTP) connection methods, which include Outlook on the web, the Outlook desktop clients, and the mobile apps.
Current status: Our investigation has further identified that exceptions may be occurring as our mail transport service is sending an unexpectedly large amount of requests to downstream components in the mail routing code path. We're investigating recent changes to confirm this theory and determine next steps for remediation.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Next update by: Friday, January 30, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jan 29 14:19:17 2026 |
|---|
| Description: | Title: Users may experience delays when sending or receiving Exchange Online email messages
User impact: Users may experience delays when sending or receiving Exchange Online email messages.
More info: This issue specifically impacts users who are on Simple Mail Transfer Protocol (SMTP) connection methods, which include Outlook on the web, the Outlook desktop clients, and the mobile apps.
Current status: We've identified the "451 4.3.2 Temporary server error" occurring that's leading to impact. This error, generally, is a common error, however our review of transport service health telemetry confirmed an increase in the rate of this error generating. We're investigating why we see an increase of this error resulting in impact to better understand how the issue is manifesting and prepare next steps for potential remediating actions.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Next update by: Thursday, January 29, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Jan 29 13:05:41 2026 |
|---|
| Description: | Title: Users may experience delays when sending or receiving Exchange Online email messages
User impact: Users may experience delays when sending or receiving Exchange Online email messages.
More info: This issue specifically impacts users who are on Simple Mail Transfer Protocol (SMTP) connection methods, which include Outlook on the web, the Outlook desktop clients, and the mobile apps.
Current status: We're reviewing transport service logs in parallel with samples of affected messages to identify and isolate any errors that may be contributing to impact for further investigation.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Next update by: Thursday, January 29, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Jan 29 12:36:32 2026 |
|---|
| Description: | Title: Users may experience delays when sending or receiving Exchange Online email messages
User impact: Users may experience delays when sending or receiving Exchange Online email messages.
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.
|
|---|
|
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: | Fri Jan 30 07:15:30 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: | 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.
We've provided a Post-Incident Report for this incident. Additionally, we'll be updating the Post-Incident Report on a monthly basis, for the next six months, to show the status of the Next Steps. The first update will be provided by March 2, 2026.
|
|---|
|
| 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.
|
|---|
|
MV1224509 - Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 29 04:00:00 2026 |
|---|
| End Time: | Thu Jan 29 17:50:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jan 29 18:26:24 2026 |
|---|
| Root Cause: | A recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and prevented network admins from making network settings changes. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jan 29 18:17:32 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app
User impact: Users may have been unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app.
More info: Additionally, network admins may have been unable to change network settings for users.
Final status: We reverted the offending change and confirmed using our internal telemetry data that impact is remediated.
Scope of impact: Any users attempting to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, or any network admin attempting to change a user's network settings may have been impacted.
Start time: Thursday, January 29, 2026, at 9:00 AM UTC
End time: Thursday, January 29, 2026, at 10:50 PM UTC
Root cause: A recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and prevented network admins from making network settings changes.
Next steps:
- We're reviewing and improving our schema field update validation procedure to detect and prevent similar issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jan 29 17:27:59 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app
User impact: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app.
More info: Additionally, network admins may be unable to change network settings for users.
Current status: At the current stage of our update reversion, we've confirmed that users are able to access Microsoft Viva engage content, but network admins are still unable to change network settings. We're continuing to revert the offending update and expect it should complete and fully remediate impact by our next scheduled update.
Scope of impact: Any users attempting to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, or any network admin attempting to change a user's network settings.
Start time: Thursday, January 29, 2026, at 9:00 AM UTC
Root cause: A recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and preventing network admins from making network settings changes.
Next update by: Friday, January 30, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Jan 29 15:55:31 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app
User impact: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app.
More info: Additionally, network admins may be unable to change network settings for users.
Current status: We've identified that a recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and preventing network admins from making network settings changes. We're reverting this update to remediate impact.
Scope of impact: Any users attempting to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, or any network admin attempting to change a user's network settings.
Root cause: A recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and preventing network admins from making network settings changes.
Next update by: Thursday, January 29, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Jan 29 15:10:59 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app
User impact: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app.
More info: Additionally, network admins may be unable to change network settings for users.
Current status: We're investigating a potential issue with Microsoft Viva Engage and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CW1224109 - Some users using Microsoft 365 Copilot Chat may have not seen any responses being generated
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 29 04:20:00 2026 |
|---|
| End Time: | Thu Jan 29 09:00:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jan 29 09:41:20 2026 |
|---|
| Root Cause: | A section of Microsoft API service infrastructure had dropped below our manageable service performance thresholds, producing failures for users generating responses for Copilot Chat. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jan 29 09:14:32 2026 |
|---|
| Description: | Title: Some users using Microsoft 365 Copilot Chat may have not seen any responses being generated
User impact: Users using Copilot Chat may not have seen any responses being generated.
More info: Users may have seen the following error message "Something went wrong. Please try again."
Final status: We've determined that a section of Microsoft API service infrastructure had dropped below our manageable service performance thresholds, producing failures for users generating responses for Copilot Chat. While we further investigate the source for the lower-than-expected service infrastructure performance levels, we've temporarily increased performance parameters to mitigate impact.
Scope of impact: Some users attempting to generate responses within Copilot Chat in the Europe may have been impacted.
Start time: Thursday, January 29, 2026, at 9:20 AM UTC
End time: Thursday, January 29, 2026, at 2:00 PM UTC
Root cause: A section of Microsoft API service infrastructure had dropped below our manageable service performance thresholds, producing failures for users generating responses for Copilot Chat.
Next steps:
- We're further analyzing the affected subset of Microsoft API service infrastructure in our effort to isolate the source for the lower-than-normal performance levels, and to help prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jan 29 07:25:21 2026 |
|---|
| Description: | Title: Some users using Microsoft 365 Copilot Chat may not see any responses being generated
User impact: Users using Copilot Chat may not see any responses being generated.
More info: Users may see the following error message "Something went wrong. Please try again."
Current status: We've received reports indicating users may be unable to generate responses within Copilot Chat. We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to generate responses within Copilot Chat in the Europe may be impacted.
Next update by: Thursday, January 29, 2026, at 2:30 PM UTC
|
|---|
|
DZ1223715 - Users may be unable to access Threat Analytics in the Microsoft Defender XDR portal
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 28 12:14:00 2026 |
|---|
| End Time: | Wed Jan 28 13:22:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jan 28 14:30:38 2026 |
|---|
| Root Cause: | The cache infrastructure performance fell below suboptimal thresholds, resulting in this impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jan 28 14:30:38 2026 |
|---|
| Description: | Title: Users may be unable to access Threat Analytics in the Microsoft Defender XDR portal
User impact: Users may have been unable to access Threat Analytics in the Microsoft Defender XDR portal.
Final status: We determined that the cache infrastructure performance had fallen below suboptimal thresholds, and we applied manual mitigations to the affected portions of the infrastructure to relieve this impact. After a period of monitoring, we confirmed that the service returned to a healthy state.
Scope of impact: Any user attempting to access Threat Analytics in the Microsoft Defender XDR portal may have been impacted by this event.
Start time: Wednesday, January 28, 2026, at 5:14 PM UTC
End time: Wednesday, January 28, 2026, at 6:22 PM UTC
Root cause: The cache infrastructure performance fell below suboptimal thresholds, resulting in this impact.
Next steps:
- We're reviewing the cache infrastructure to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jan 28 13:47:23 2026 |
|---|
| Description: | Title: Users may be unable to access Threat Analytics in the Microsoft Defender XDR portal
User impact: Users may have been unable to access Threat Analytics in the Microsoft Defender XDR portal.
Current status: We've investigated a problem in which users may have been unable to access Threat Analytics in the Microsoft Defender XDR portal and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
EX1223427 - Some users may have been unable to access the Exchange admin center (EAC)
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 28 04:06:00 2026 |
|---|
| End Time: | Wed Jan 28 06:12:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jan 28 07:43:09 2026 |
|---|
| Root Cause: | A section of infrastructure, responsible for facilitating EAC access, unexpectedly began performing below acceptable performance thresholds and caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jan 28 07:39:32 2026 |
|---|
| Description: | Title: Some users may have been unable to access the Exchange admin center (EAC)
User impact: Users may have been unable to access the EAC.
Final status: We've identified that a section of infrastructure, responsible for facilitating EAC access, unexpectedly began performing below acceptable performance thresholds and caused impact. We've redirected affected traffic to alternate healthy infrastructure and confirmed impact is no longer occurring after a period of monitoring.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure attempting to access the EAC.
Start time: Wednesday, January 28, 2026, at 9:06 AM UTC
End time: Wednesday, January 28, 2026, at 11:12 AM UTC
Root cause: A section of infrastructure, responsible for facilitating EAC access, unexpectedly began performing below acceptable performance thresholds and caused impact.
Next steps:
- We're reviewing performance data and trends on the affected systems to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jan 28 06:29:05 2026 |
|---|
| Description: | Title: Some users may be unable to access the Exchange admin center (EAC)
User impact: Users may be unable to access the EAC.
Current status: We're continuing to review service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to access the EAC.
Next update by: Wednesday, January 28, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Jan 28 04:49:26 2026 |
|---|
| Description: | Title: Some users may be unable to access the Exchange admin center (EAC)
User impact: Users may be unable to access the EAC.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to access the EAC.
Next update by: Wednesday, January 28, 2026, at 12:00 PM UTC
|
|---|
|
TM1221763 - Users may have seen a User Interface (UI) glitch in Microsoft Teams which showed an added bar at the top of each window
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 15 19:00:00 2026 |
|---|
| End Time: | Sun Jan 25 01:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jan 28 06:58:20 2026 |
|---|
| Root Cause: | A code regression in the WebView2 version 144.0.3719.82 was causing impact to occur. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jan 28 06:58:20 2026 |
|---|
| Description: | Title: Users may have seen a User Interface (UI) glitch in Microsoft Teams which showed an added bar at the top of each window
User impact: Users may have seen a User Interface (UI) glitch in Microsoft Teams which showed an added bar at the top of each window.
More info: This specifically impacted users of WebView2 version 144.0.3719.82 on Windows 10 devices.
Some users may be required to manually install the latest WebView2 version if it was not automatically applied. The download is available at the following link:
https://developer.microsoft.com/en-us/microsoft-edge/webview2?form=MA13LH#download
Final status: We’ve confirmed that the updated WebView2 version has been released. While we previously advised that affected users might need to update their Microsoft Teams client, this is no longer required. If impact persists, users should verify that they are running the latest stable version of WebView2. Users on an older version will need to manually update WebView2 by following the instructions provided in the More info section of this communication.
Scope of impact: Impact is specific to some users that are on WebView2 version 144.0.3719.82 on Windows 10 devices.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
End time: Sunday, January 25, 2026, at 6:30 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 was causing impact to occur.
Next steps:
- We're reviewing our WebView2 configuration to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jan 26 11:37:46 2026 |
|---|
| Description: | Title: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window
User impact: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window.
More info: This specifically impacts users of WebView2 version 144.0.3719.82 on Windows 10 devices.
Current status: We made the necessary adjustments to our fix and have deployed it as WebView2 version update 144.0.3719.93, where it is saturating across the affected environment. We expect that this saturation and full remediation will complete by our next scheduled update. Users should update their Microsoft Teams client to version 144.0.3719.93 as it becomes available to them and restart their Microsoft Teams apps in order to remediate impact.
Scope of impact: Impact is specific to some users that are on WebView2 version 144.0.3719.82 on Windows 10 devices.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 is causing impact to occur.
Next update by: Wednesday, January 28, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Jan 23 18:39:41 2026 |
|---|
| Description: | Title: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window
User impact: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window.
More info: This specifically impacts users that are using WebView2 version 144.0.3719.82 on Windows 10 devices.
Current status: We’re making the necessary adjustments to expedite the deployment of our fix to resolve the issue as soon as possible and anticipate the fix should reach affected users by our next scheduled update.
Scope of impact: Impact is specific to some users that are on WebView2 version 144.0.3719.82 on Windows 10 devices.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 is causing impact to occur.
Next update by: Monday, January 26, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Jan 23 12:15:21 2026 |
|---|
| Description: | Title: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window
User impact: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window.
More info: This specifically impacts users that are using WebView2 version 144.0.3719.82 on Windows 10 devices.
Current status: We've developed a code fix to remove the added bar and expect that it'll complete deployment by the time of our next update.
Scope of impact: Impact is specific to some users that are on WebView2 version 144.0.3719.82 on Windows 10 devices.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 is causing impact to occur.
Next update by: Friday, January 30, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jan 23 07:58:01 2026 |
|---|
| Description: | Title: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window
User impact: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window.
More info: This specifically impacts users that are using WebView2 version 144.0.3719.82 on Windows 10 devices.
Current status: We've identified a code regression in the WebView2 version 144.0.3719.82 is causing impact to occur. We’re working to identify the safest and most effective way to mitigate the impact.
Scope of impact: Impact is specific to some users utilizing the UI in Microsoft Teams.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 is causing impact to occur.
Next update by: Friday, January 23, 2026, at 7:00 PM UTC
|
|---|
|
MV1220701 - Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Jan 21 15:53:16 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jan 27 14:01:12 2026 |
|---|
| Root Cause: | A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events. |
|---|
| Next Update: | Tuesday, February 17, 2026, at 7:30 PM UTC |
|---|
|
Details
| Time: | Tue Jan 27 14:01:12 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: We've completed the restoration of the usage data; however, we've determined that the process to backfill the restored data to be made available to admins will require additional time. Initial projections indicate the process will finish by the end of March 2026. We're monitoring this process and will provide an updated timeline as one becomes available.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Tuesday, February 17, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Jan 26 12:59:14 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: We've determined that restoring the usage data will require a bit longer than previously expected, and we're now projecting that the process will have completed and that impact will be remediated by our next scheduled communication update.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Tuesday, January 27, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 13:57:00 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts Mac OS admins using the Microsoft Viva Insights desktop, mobile and web Outlook add-ins.
Current status: We've corrected the metadata file to prevent additional impact and we're in the process of restoring the usage data to correct metrics. We anticipate all past usage data will be restored to expected values by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and any admins attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Estimated time to resolve: We anticipate all usage data will be restored to correct metrics by Monday, January 26, 2026, at 7:30 PM UTC.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Monday, January 26, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jan 21 16:36:20 2026 |
|---|
| Description: | Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts Mac OS admins using the Microsoft Viva Insights desktop, mobile and web Outlook add-ins.
Current status: We've identified that a recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events. We're correcting this metadata file to prevent additional impact, and we'll subsequently restore the usage data to provide the correct metrics to completely resolve the issue.
Scope of impact: Your organization is affected by this event, and any admins attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Friday, January 23, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 15:55:15 2026 |
|---|
| Description: | Title: Users see inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Users see inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
Current status: We're investigating a potential issue with the Microsoft Viva Insights Outlook add-in and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1221839 - Some users were unable to view attached meetings URLs for Microsoft Teams meetings or see the Microsoft Teams toggle
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 22 15:42:00 2026 |
|---|
| End Time: | Sun Jan 25 00:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jan 27 08:59:39 2026 |
|---|
| Root Cause: | Impact associated to Service Incident (SI) MO1221364 caused the default meeting property provider to show as unknown instead of Microsoft Teams for users, which resulted in this impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jan 27 08:59:39 2026 |
|---|
| Description: | Title: Some users were unable to view attached meetings URLs for Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Users were unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users could have circumvented this impact by sending meeting URLs from the classic Outlook desktop experience.
Final status: We’ve determined that impact associated to Service Incident (SI) MO1221364 caused impact to occur. We've received confirmation from a further subset of affected users that impact is no longer occurring and after an extended period of monitoring service health, can confirm that the issue is resolved.
Scope of impact: Some users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 8:42 PM UTC
End time: Sunday, January 25, 2026, at 5:00 AM UTC
Root cause: Impact associated to Service Incident (SI) MO1221364 caused the default meeting property provider to show as unknown instead of Microsoft Teams for users, which resulted in this impact.
Next steps:
- We're further reviewing the event and the circumstances that lead to impact, so that we can identify next steps that'll help us further improve the reliability and resiliency of our service.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jan 26 07:20:05 2026 |
|---|
| Description: | Title: Some users may be unable to view attached meetings URLs for Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: We’re continuing to monitor the service telemetry and expect to share more details in our next scheduled update.
Scope of impact: Some users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Root cause: A transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users is resulting in this impact.
Next update by: Tuesday, January 27, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 19:37:44 2026 |
|---|
| Description: | Title: Some users may be unable to view attached meeting URLs for Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: While we were in the process of applying our temporary mitigation, system monitoring has indicated that the service has returned to normal healthy state independent of our deployment. We've confirmed that the issue is no longer occurring for a subset of affected users and anticipate the service will return to a healthy state for the remaining impacted users by January 24, 2026, based on trends in service health telemetry. We'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Root cause: A transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users is resulting in this impact.
Next update by: Monday, January 26, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 18:41:57 2026 |
|---|
| Description: | Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: After further investigation, we determined that this transient error is a symptom of different underlying issue and we're investigating this root cause to help develop a permanent fix for this issue. While this is ongoing, we've developed a temporary fix to address this issue and are monitoring it with a subset of affected users to ensure it restores services.
Scope of impact: Your organization is impacted by this event, and some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Root cause: A transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users is resulting in this impact.
Next update by: Saturday, January 24, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Jan 23 16:40:27 2026 |
|---|
| Description: | Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: We've determined that this issue is related to a known transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users, resulting in this impact. We've developed a temporary fix to address this issue, which we have deployed to a subset of affected users. We're monitoring this temporary fix as we work to develop a permanent solution for this issue.
Scope of impact: Your organization is impacted by this event, and some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Root cause: A transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users, results in this impact.
Next update by: Friday, January 23, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 15:28:10 2026 |
|---|
| Description: | Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: We're continuing our review of HTTP Archive format (HAR) traces and documentation of impact and working to confirm a potential correlation to an ongoing event as we actively work on developing troubleshooting steps to address this impact for your organization.
Scope of impact: Your organization is impacted by this event, and some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 14:10:06 2026 |
|---|
| Description: | Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: We're reviewing the HTTP Archive format (HAR) traces and documentation of impact provided by your organization to assist in our investigation of the underlying root cause and the development of our next troubleshooting steps.
Scope of impact: Your organization is impacted by this event, and some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 13:46:42 2026 |
|---|
| Description: | Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
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.
|
|---|
|
CR1222626 - Degraded plug-in functionality
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jan 26 12:02:00 2026 |
|---|
| End Time: | Mon Jan 26 18:38:00 2026 |
|---|
| Service: | Dynamics 365 Apps |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jan 26 19:13:40 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jan 26 19:13:40 2026 |
|---|
| Description: | Title: Degraded plug-in functionality
User impact: Plug-in functionality was degraded.
Final Status: We have confirmed that the node restarts restored functionality via service health diagnostics.
This is the final update for this incident.
Preliminary Root Cause: A portion of an upstream dependency service, that supports plug-in functionality, entered an unhealthy state.
Next Steps: We're reviewing our configuration procedures to find ways to prevent this problem from happening again.
|
|---|
|
| Time: | Mon Jan 26 18:41:14 2026 |
|---|
| Description: | Title: Degraded plug-in functionality
User impact: Plug-in functionality is degraded.
Current Status: After our investigation, we identified that a portion of an upstream dependency service, that supports plug-in functionality, entered an unhealthy state. As a preliminary troubleshooting step, we restarted nodes on the affected infrastructure and are monitoring telemetry for recovery.
Next Update: Tuesday, January 27, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Mon Jan 26 18:22:27 2026 |
|---|
| Description: | Title: Degraded plug-in functionality
User impact: Plug-in functionality is degraded.
Current Status: We are aware of an emerging issue where users are experiencing degraded plug-in functionality and 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.
|
|---|
|
MO1218616 - Some admins may be unable to view pooled storage management in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jan 5 17:40:00 2026 |
|---|
| End Time: | Sun Jan 25 17:28:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jan 26 16:54:06 2026 |
|---|
| Root Cause: | A recent code change intended to update how storage reports were loaded to the Microsoft 365 admin center introduced a regression which was causing the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jan 26 16:54:06 2026 |
|---|
| Description: | Title: Some admins may be unable to view pooled storage management in the Microsoft 365 admin center
User impact: Admins may have been unable to view pooled storage management in the Microsoft 365 admin center.
More info: This issue was specific to Microsoft 365 Education admins.
Final status: We've completed the deployment of our fix and confirmed after testing with a subset of affected users that this has successfully remediated impact.
Scope of impact: Admins in Microsoft 365 Education organizations attempting to view pooled storage management in the Microsoft 365 admin center may have been impacted.
Start time: Monday, January 5, 2026, at 10:40 PM UTC
End time: Sunday, January 25, 2026, at 10:28 PM UTC
Root cause: A recent code change intended to update how storage reports were loaded to the Microsoft 365 admin center introduced a regression which was causing the impact.
Next steps:
- We're reviewing our code change testing and validation procedures to identify opportunities to identify impact earlier and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 23 13:39:14 2026 |
|---|
| Description: | Title: Some admins may be unable to view pooled storage management in the Microsoft 365 admin center
User impact: Admins may be unable to view pooled storage management in the Microsoft 365 admin center.
More info: This issue is specific to Microsoft 365 Education admins.
Current status: The code fix has saturated to 92 percent of the affected environment. As the deployment progresses and applies to the content hosting infrastructure to which admins are connecting, admins may begin to see the issue automatically resolve upon refreshing the storage report page. We expect the code fix will saturate the affected environment 100 percent on Wednesday, January 28, 2026.
Scope of impact: Admins in Microsoft 365 Education organizations attempting to view pooled storage management in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Monday, January 5, 2026, at 10:40 PM UTC
Root cause: A recent code change intended to update how storage reports are loaded to the Microsoft 365 admin center introduced a regression which is causing the impact.
Next update by: Wednesday, January 28, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Jan 20 14:00:21 2026 |
|---|
| Description: | Title: Some admins may be unable to view pooled storage management in the Microsoft 365 admin center
User impact: Admins may be unable to view pooled storage management in the Microsoft 365 admin center.
More info: This issue is specific to Microsoft 365 Education admins.
Current status: The code fix has saturated to 66 percent of the affected environment. As the deployment progresses and applies to the content hosting infrastructure to which admins are connecting, admins may begin to see the issue automatically resolve upon refreshing the storage report page.
Scope of impact: Admins in Microsoft 365 Education organizations attempting to view pooled storage management in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Monday, January 5, 2026, at 10:40 PM UTC
Root cause: A recent code change intended to update how storage reports are loaded to the Microsoft 365 admin center introduced a regression which is causing the impact.
Next update by: Friday, January 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 12:34:29 2026 |
|---|
| Description: | Title: Some admins may be unable to view pooled storage management in the Microsoft 365 admin center
User impact: Admins may be unable to view pooled storage management in the Microsoft 365 admin center.
More info: This issue is specific to Microsoft 365 Education admins.
Current status: We've identified a recent code change intended to update how storage reports are loaded to the Microsoft 365 admin center introduced a regression which is causing the impact. We've developed and are deploying a code fix to correct this issue and confirmed the deployment is currently saturated 13 percent of the infrastructure that supports Microsoft 365 Education. We'll provide a timeline for remediation as one becomes available.
Scope of impact: Admins in Microsoft 365 Education organizations attempting to view pooled storage management in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Monday, January 5, 2026, at 10:40 PM UTC
Root cause: A recent code change intended to update how storage reports are loaded to the Microsoft 365 admin center introduced a regression which is causing the impact.
Next update by: Friday, January 23, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Jan 16 10:34:30 2026 |
|---|
| Description: | Title: Some users may be unable to access or view the storage usage page in the M365 admin center
User impact: Users may be unable to access or view the storage usage page in the M365 admin center.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to access or view the storage usage page in the M365 admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, January 16, 2026, at 5:30 PM UTC
|
|---|
|
TM1216503 - Some users may experience degraded video and screensharing quality in Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Dec 30 20:00:00 2025 |
|---|
| End Time: | Fri Jan 16 16:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jan 26 14:51:42 2026 |
|---|
| Root Cause: | In April 2025, we introduced an improved timestamping algorithm that provided more accurate bandwidth estimates for media traffic, to help deliver better video call quality. However, we’ve subsequently identified that this change inadvertently introduced a code defect that only occurred when Microsoft Teams back-end components had run for an extended period without being restarted. When this happened, bandwidth estimates stopped working correctly, resulting in poor video quality for some calls. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jan 26 14:50:09 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jan 19 01:22:22 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may have experienced degraded video and screensharing quality in Microsoft Teams.
More info: The issue wasn't limited to Microsoft Teams Rooms (MTR) devices and also affected desktop clients and other scenarios.
Final status: After extensive monitoring, we've confirmed that the configuration change was successful and the impact is remediated.
Scope of impact: This issue could have affected users joining Microsoft Teams meetings whose requests were routed through portions of Microsoft Teams infrastructure that have received the update.
Root cause: In April 2025, we introduced an improved timestamping algorithm that provided more accurate bandwidth estimates for media traffic, to help deliver better video call quality. However, we’ve subsequently identified that this change inadvertently introduced a code defect that only occurred when Microsoft Teams back-end components had run for an extended period without being restarted. When this happened, bandwidth estimates stopped working correctly, resulting in poor video quality for some calls.
This code defect was not triggered and did not cause impact to customers between April and December 2025 due to our back-end components being regularly restarted. From November 2025, some components were no longer being restarted as frequently due to a planned change in deployment cadence, and by January 2026, we began to see an increase in poor video quality on calls, which was later identified as linked to components encountering this code defect. Upon review, the validations for this change did not cover long-duration runtime scenarios, which resulted in this defect not being identified during testing.
Start time: Wednesday, December 31, 2025, at 1:00 AM UTC
End time: Friday, January 16, 2026, at 9:00 PM UTC
Next Steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
|
|---|
|
| Time: | Fri Jan 16 20:33:17 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We've confirmed that our configuration change has taken effect throughout the affected environment and our service metrics indicate impact is no longer occurring. We're proceeding with an additional period of monitoring for final validation that the issue is resolved.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Monday, January 19, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Fri Jan 16 15:51:19 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We've applied the ECS configuration change to all affected environments and are completing a period of monitoring to ensure it resolves impacted as expected.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Saturday, January 17, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Jan 16 13:11:02 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We're continuing our incremental application of the ECS configuration change to a portion of the affected environments, and we've received reports from users that this change remediates impact. We anticipate that the deployment will complete for all affected environments by Friday, January 16, 2026.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 02:02:42 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We incrementally applied the ECS configuration change to a portion of the affected environments and are seeing positive results. In addition, we've received confirmation from a subset of affected users that the performance has improved. We plan to continue rolling out the ECS configuration change incrementally and if things are continuing to trend positively, we'll start the broader deployment. We anticipate that the deployment will complete by Friday, January 16, 2026.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Jan 15 22:17:39 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We’re continuing to incrementally apply the ECS configuration change and closely monitor the affected environments to ensure we’re seeing positive results. In parallel, we’re validating with a subset of affected users to confirm they’re seeing the expected improvements before proceeding with broader deployment, which we expect to complete by Friday, January 16, 2026.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Thu Jan 15 19:20:55 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We’ve confirmed that our ECS configuration change remediation is operating as expected within our internal environment and we’re progressing incrementally with the change to affected users. We’ll continue to monitor and assess as the change is applied with the expectation that it should reach all affected users by Friday, January 16, 2026.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Thu Jan 15 17:07:08 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We're continuing to validate the ECS configuration change fix to ensure it will remediate the impact without introducing any adverse effects.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Thu Jan 15 13:34:08 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue is not limited to Microsoft Teams Rooms (MTR) devices, but also affects desktop clients and other scenarios.
Current status: We determined that our fix didn't remediate impact as expected. We're validating an Enhanced Configuration Service (ECS) configuration change fix that we believe will more appropriately alleviate impact.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Thursday, January 15, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Jan 15 10:06:20 2026 |
|---|
| Description: | Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue is not limited to Microsoft Teams Rooms (MTR) devices, but also affects desktop clients and other scenarios.
Current status: A permanent fix is now being deployed across all impacted environments. We'll share an estimated timeline for full resolution as soon as it’s available.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Thursday, January 15, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jan 14 20:09:06 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: The issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android but is not limited to these devices.
Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: Our investigation into the root cause of impact has identified that a recent Microsoft Teams server update unintentionally introduced a corruption scenario, leading to degraded video or screensharing quality during calls. We're continuing our deployment to the remaining impacted regions, and we'll provide a timeline for full remediation once one becomes available.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update unintentionally introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Thursday, January 15, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jan 14 18:08:49 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: The issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android but is not limited to these devices.
Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're continuing to monitor the deployment of this fix and actively investigating a method by which we can accelerate the mitigation in all impacted regions. We're working to determine an accurate timeline for remediation and will provide one when it becomes available.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Thursday, January 15, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Jan 14 15:47:24 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: The issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android but is not limited to these devices.
Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: While the deployment of the fix is underway, we're continuing our efforts to identify a method by which we can accelerate the mitigation, and we'll provide a timeline for impact resolution as one becomes available.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Thursday, January 15, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Wed Jan 14 13:07:16 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: The issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android but is not limited to these devices.
Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We've identified an issue which can lead to degraded video quality during calls for some users which was introduced in the latest Microsoft Teams server deployment. We've developed and begun deploying a mitigation strategy which has proven successful at remediating the impact during our testing, and a small number of users should already be experiencing relief. We're exploring options to expedite the deployment of the fix to fully resolve the issue.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Wednesday, January 14, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jan 13 19:37:48 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We encountered an obstacle that has delayed our effort to internally reproduce the impact and confirm the source for the degraded video quality for users being added to ongoing Microsoft Teams meetings. We're addressing this internal issue now as we continue to enable enhanced media and server logging.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Wednesday, January 14, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jan 13 16:47:18 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: As we continue our efforts to internally reproduce the impact and confirm the source for the degraded video quality for users being added to ongoing Microsoft Teams meetings, we're continuing to enable enhanced media and server logging which will be required before we can apply a potential mitigation.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Wednesday, January 14, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jan 13 13:18:29 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We’re continuing to enable enhanced media and server logging to validate and apply a mitigation action. In parallel, we’re reviewing contextual details shared by affected users and attempting to reproduce the issue internally to isolate the source of the problem and confirm the full scope of impact.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Jan 13 06:07:56 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: While we continue enabling enhanced media and server logging as a potential mitigation, we're reviewing additional contextual details shared by some affected users to help pinpoint the root cause.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jan 13 03:27:41 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're continuing to enable robust media and server logging as a initial mitigation step. We're also working with your organizations representatives to obtain further contextual details to help us understand the root cause and full mitigation plan.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 12:30 PM UTC
|
|---|
|
| Time: | Mon Jan 12 22:25:25 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We’ve successfully reproduced the issue in our local testing environment. We’re enabling robust media and server logging to continue our investigation into the underlying cause of this issue and determine our next steps.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Mon Jan 12 19:29:26 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're continuing to work with a subset of affected users to perform further reproductions of impact and collect additional logs to assist our investigation into the source of the issue. In parallel, we're exploring potential mitigation strategies to help relieve this impact for users.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Mon Jan 12 14:58:05 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: After further investigation, we've confirmed the issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android. We're working with a subset of affected users to perform further reproductions of impact and collect additional logs to assist our investigation into the source of the issue.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Mon Jan 12 13:16:45 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: Our review of the provided logging identified that the bandwidth estimation coming from the media player to the client is very low, causing the outbound traffic from the client to the media player component to be a very low video quality. We suspect there may be two possibilities as to why impact is occurring - either bandwidth estimation isn't running at all or it's falling back to an older bandwidth estimation algorithm, resulting in an incorrect estimation and thus the low resolution.
To determine the source of the issue, we're working to reproduce the impact in our internal environment for more insight into how impact manifests. In parallel, we're reviewing overall telemetry for instances where bandwidth estimation is low to further correlate when the issue began with any potential impacting changes that may have occurred at the same time. We’re also investigating additional client and device logs to assist with our investigation.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Monday, January 12, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Jan 12 09:16:22 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're reviewing networking related logging alongside affected user details to isolate the root cause and develop a remediation plan.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Monday, January 12, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Jan 12 06:11:34 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're continuing to await input from an impacted user to confirm whether media flow is being disrupted and to validate potential mitigation options.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Monday, January 12, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Sun Jan 11 03:29:53 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We’ve determined that Microsoft Teams meetings are currently routed through a relay service, which acts as an intermediary when direct peer-to-peer communication isn’t possible, and may be contributing to the issue. We’re awaiting input from an impacted user to confirm whether media flow is being disrupted and to validate potential mitigation options.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Monday, January 12, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Sat Jan 10 20:48:45 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're reviewing a reproduction of impact provided by some affected users in tandem with service side networking logs to refine our understanding of the underlying cause of impact.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Sunday, January 11, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Sat Jan 10 20:21:01 2026 |
|---|
| Description: | Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
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.
|
|---|
|
DZ1222472 - Some users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jan 26 04:30:00 2026 |
|---|
| End Time: | Mon Jan 26 10:00:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jan 26 11:21:34 2026 |
|---|
| Root Cause: | An update for a dependent service caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jan 26 11:21:34 2026 |
|---|
| Description: | Title: Some users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR
User impact: Users may have seen a delay of up to five hours for alerts and incidents in Microsoft Defender XDR.
Final status: After our processing of the backlogged alerts and incidents, our internal service telemetry validates that the impact has been remediated.
Scope of impact: This issue may have impacted some users within your organization that were accessing the service from West and North Europe.
Start time: Monday, January 26, 2026, at 9:30 AM UTC
End time: Monday, January 26, 2026, at 3:00 PM UTC
Root cause: An update for a dependent service caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds.
Next steps:
- We're further analyzing the offending dependent service update along with the affected subset of service infrastructure to help us improve our pre-deployment testing and validations.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jan 26 09:59:45 2026 |
|---|
| Description: | Title: Some users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR
User impact: Users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR.
Current status: While we continue processing the backlogged alerts and incidents, we’ve identified some residual performance issues and are actively working to restore performance across the affected infrastructure.
Scope of impact: This issue may impact some users within your organization that are accessing the service from the affected region(s): West and North Europe.
Start time: Monday, January 26, 2026, at 9:30 AM UTC
Root cause: An update for a dependent service inadvertently caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds.
Next update by: Monday, January 26, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Jan 26 08:06:01 2026 |
|---|
| Description: | Title: Some users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR
User impact: Users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR.
Current status: We've identified that an update for a dependent service inadvertently caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds and resulted in impact. We've confirmed that the update has completed and the section of infrastructure performance has recovered. We're now processing the backlogged alerts and incidents to fully restore the service.
Scope of impact: This issue may impact some users within your organization that are accessing the service from the affected region(s): West and North Europe.
Start time: Monday, January 26, 2026, at 9:30 AM UTC
Root cause: An update for a dependent service inadvertently caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds.
Next update by: Monday, January 26, 2026, at 3:30 PM UTC
|
|---|
|
EX1221076 - Users may have been unable to delete email messages after running the QUIT command through the POP3 connection method
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 20 00:01:00 2026 |
|---|
| End Time: | Mon Jan 26 00:19:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jan 26 03:47:56 2026 |
|---|
| Root Cause: | A package version conflict introduced a regression that caused the POP3 QUIT command to fail after a DELE operation. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jan 26 03:47:56 2026 |
|---|
| Description: | Title: Users may have been unable to delete email messages after running the QUIT command through the POP3 connection method
User impact: Users may have been unable to delete email messages after running the QUIT command through the POP3 connection method.
More info: Specifically, POP3 users could read and download their email messages, but any messages they deleted may not have actually been removed, because the session failed to close properly. If a message was deleted on Exchange Online using the DELE command, the POP3 QUIT command may have failed, preventing the session from closing cleanly and caused messages marked for deletion to remain in the mailbox.
If the user was not using POP3, they were not impacted.
Final status: We’ve confirmed that the fix deployment has completed successfully and that the issue has been fully resolved.
Scope of impact: Impact was specific to some users attempting to delete email messages after running the QUIT command using POP3 connection method.
Start time: Tuesday, January 20, 2026, at 5:01 AM UTC
End time: Saturday, January 24, 2026, at 5:19 AM UTC
Root cause: A package version conflict introduced a regression that caused the POP3 QUIT command to fail after a DELE operation.
Next steps:
- We're reviewing our package provisioning procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 23 04:13:56 2026 |
|---|
| Description: | Title: Users may be unable to delete email messages after running the QUIT command when POP3 connection method is used
User impact: Users may be unable to delete email messages after running the QUIT command when POP3 connection method is used.
More info: Specifically, POP3 users can read and download their email messages, but any messages they delete may not actually be removed, because the session fails to close properly. If a message is deleted on Exchange Online using the DELE command, the POP3 QUIT command may fail, preventing the session from closing cleanly and causing messages marked for deletion to remain in the mailbox.
If the user is not using POP3, they are not impacted.
Current status: We’ve begun rolling out the fix and can confirm it has been successfully deployed to approximately 56% of the affected environments. We’ll continue monitoring progress and will provide an updated completion timeline as soon as it’s available.
Scope of impact: Impact is specific to some users attempting to delete email messages after running the QUIT command using POP3 connection method.
Root cause: A package version conflict introduced a regression that causes the POP3 QUIT command to fail after a DELE operation.
Next update by: Monday, January 26, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Jan 22 06:59:05 2026 |
|---|
| Description: | Title: Users may be unable to delete email messages after running the QUIT command when POP3 connection method is used
User impact: Users may be unable to delete email messages after running the QUIT command when POP3 connection method is used.
More info: Specifically, POP3 users can read and download their email messages, but any messages they delete may not actually be removed, because the session fails to close properly. If a message is deleted on Exchange Online using the DELE command, the POP3 QUIT command may fail, preventing the session from closing cleanly and causing messages marked for deletion to remain in the mailbox.
If the user is not using POP3, they are not impacted.
Current status: We’ve identified an issue where a recent update introduced a conflict that prevents the POP3 QUIT command from completing after a message is deleted. We've validated a fix in our test environment and initiated a deployment to affected users. The deployment is progressing through a gradual rollout and we expect full completion within the next 24 to 48 hours.
Scope of impact: Impact is specific to some users attempting to delete email messages after running the QUIT command using POP3 connection method.
Root cause: A package version conflict introduced a regression that causes the POP3 QUIT command to fail after a DELE operation.
Next update by: Friday, January 23, 2026, at 10:00 AM UTC
|
|---|
|
SP1220310 - Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 8 07:24:00 2026 |
|---|
| End Time: | Fri Jan 23 20:07:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jan 23 20:27:03 2026 |
|---|
| Root Cause: | A recent service change to remove a separate feature introduced a regression within SharePoint Online email notifications, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jan 23 20:27:03 2026 |
|---|
| Description: | Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that were mentioned in list comments in SharePoint Online may have not received email notifications.
Final status: Our reversion of the offending change has completed its saturation process throughout the affected environment, and we’ve confirmed through an extended period of monitoring the service health telemetry that impact has been remediated.
Scope of impact: Impact was specific to some users that were mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
End time: Saturday, January 24, 2026, at 1:07 AM UTC
Root cause: A recent service change to remove a separate feature introduced a regression within SharePoint Online email notifications, which resulted in impact.
Next steps:
- We’re continuing to analyze how the service change was partially 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 SharePoint Online users.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 23 11:52:10 2026 |
|---|
| Description: | Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We’re continuing to monitor progress of our fix to reverse the offending change, where it's saturated across 90 percent of the affected infrastructure. We estimate that this saturation will complete by our next communications update, after which we'll perform final testing with a subset of affected users to validate remediation.
Scope of impact: Impact is specific to some users that are mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
Root cause: A recent service change to remove a separate feature introduced a regression within SharePoint Online email notifications, resulting in impact.
Next update by: Saturday, January 24, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Jan 22 13:00:29 2026 |
|---|
| Description: | Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We’re continuing to monitor progress of the fix to reverse the offending change and will provide a resolution timeline once available.
Scope of impact: Impact is specific to some users that are mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
Root cause: A recent service change to remove a separate feature is causing impact.
Next update by: Friday, January 23, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Jan 21 13:49:25 2026 |
|---|
| Description: | Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We're continuing to reverse the offending change and will provide a timeline for the completion of this reversal as one becomes available.
Scope of impact: Impact is specific to some users that are mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
Root cause: A recent service change to remove a separate feature is causing impact.
Next update by: Thursday, January 22, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 12:22:01 2026 |
|---|
| Description: | Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We've identified a recent service change to remove a separate feature is causing impact. While we investigate the reason the change caused impact, we're reversing the offending change to remediate the impact.
Scope of impact: Impact is specific to some users that are mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
Root cause: A recent service change to remove a separate feature is causing impact.
Next update by: Wednesday, January 21, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Jan 21 10:24:54 2026 |
|---|
| Description: | Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We’ve identified a potential update that may be causing impact to occur. We're analyzing the update code path to confirm the update is the root cause of impact.
Scope of impact: Impact is specific some users that are mentioned in list comments in SharePoint Online.
Next update by: Wednesday, January 21, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Jan 21 08:20:22 2026 |
|---|
| Description: | Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications.
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We’re reviewing any recent changes to the service that may be causing impact to occur.
Scope of impact: Impact is specific some users that are mentioned in list comments in SharePoint Online.
Next update by: Wednesday, January 21, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Wed Jan 21 06:18:23 2026 |
|---|
| Description: | Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Impact is specific some users that are mentioned in list comments in SharePoint Online.
Next update by: Wednesday, January 21, 2026, at 1:30 PM UTC
|
|---|
|
EX1221742 - Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jan 23 02:00:00 2026 |
|---|
| End Time: | Fri Jan 23 19:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Sign-in |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jan 23 20:19:15 2026 |
|---|
| Root Cause: | A recent code regression was causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jan 23 20:18:53 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may have been intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacted the following connection methods:
- Outlook on the web
- Outlook mobile app
- Outlook on Mac devices
Final status: After monitoring the service recovery progress, we've confirmed that the service availability has reached expected levels and impact is remediated.
Scope of impact: This issue may have impacted any user based in Australia, Brazil, Canada, Europe/Middle East/Africa, France, Mexico, The United States, Norway, South America, Sweden, and the United Kingdom regions.
Start time: Friday, January 23, 2026, 7:00 AM UTC
End time: Saturday, January 24, 2026, at 12:00 AM UTC
Root cause: A recent code regression was causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next steps:
- We're investigating further into the recent code regression to better understand why it caused the inability to access Exchange Online and why impact was caught sooner so that we can proactively identify similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 23 18:31:07 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them:
- Outlook on the web
- Outlook mobile app
- Outlook on Mac devices
Current status: The ongoing service recovery progress shows availability is slowly approaching expected levels, and we're continuing to monitor, ensuring this trend continues and the impact is remediated in a timely manner.
Scope of impact: This issue may impact any user based in Australia, Brazil, Canada, Europe/Middle East/Africa, France, Mexico, The United States, Norway, South America, Sweden, and the United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Saturday, January 24, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Jan 23 16:19:27 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them:
- Outlook on the web
- Outlook mobile app
- Outlook on Mac devices
Current status: While we monitor service health broadly as availability recovers, we're also analyzing and comparing recovering sections of infrastructure to ensure improvement continues to progress and no additional measures are necessary for remediation.
Scope of impact: This issue may impact any user based in the United States, France, Canada, and United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Friday, January 23, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 15:49:36 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them:
- Outlook on the web
- Outlook mobile app
- Outlook on Mac devices
Current status: We've completed applying the additional configuration change to the affected infrastructure, and we're continuing to monitor as availability slowly recovers. In parallel, we're assessing whether there are any further actions needed to fully resolve the issue.
Scope of impact: This issue may impact any user based in the United States, France, and United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Friday, January 23, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Jan 23 13:57:31 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them:
- Outlook on the web
- Outlook mobile app
- Outlook on Mac devices
Current status: While our initial mitigating action of rolling back the problematic change has provided some relief and prevented further impact from occurring, we're applying an additional configuration change to affected portions of infrastructures to address an outdated Dynamic-link library (DLL) which is being incorrectly referenced by the service as a result of the regression and is continuing to cause crashes.
Scope of impact: This issue may impact any user based in the United States, France, and United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Friday, January 23, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Jan 23 11:36:42 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them:
- Outlook on the web
- Outlook mobile app
- Outlook on Mac devices
Current status: While we're observing some recovery after rolling back the impacting change, we're exploring options to expedite the resolution.
Scope of impact: This issue may impact any user based in the United States, France, and United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Friday, January 23, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jan 23 09:29:50 2026 |
|---|
| Description: | Title: Users may experience errors when accessing or loading Exchange Online via one or more clients or connection methods
User impact: Users may experience errors when accessing or loading Exchange Online via one or more clients or connection methods.
More info: The following impacted clients and connection methods include but aren't limited to:
- Outlook on the web
- Outlook mobile app
- Outlook on MAC devices
Current status: We’ve identified that a recent code regression in the Exchange Online service is causing unexpected errors and service instability in Outlook on the web, New Outlook, Mac and Mobile clients. The issue is linked to backported updates that affected Information Protection features, leading to increased crashes within the affected infrastructure. We've initiated a rollback of the affected changes and we’re continuing to monitor performance across all environments to ensure full recovery.
Scope of impact: This issue may impact any user within your organization served via the affected region(s): United States, France and United Kingdom. This information may be updated as our investigation continues.
Root cause: A recent code regression introduced changes in Exchange Online service resulting in impact. This regression is causing crashes on some of the affected mailbox infrastructure affecting Outlook on the web, New Outlook, Mac and Mobile clients.
Next update by: Friday, January 23, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 07:20:18 2026 |
|---|
| Description: | Title: Some users may be unable to access or load Outlook on the web
User impact: Users may be unable to access or load Outlook on the web.
Current status: We’ve completed a rollback of recent changes and restored the service to a stable configuration. Our monitoring shows that availability is improving across affected regions, but some environments are still experiencing issues. Additionally, we've identified an update that caused unexpected behavior and are working on a fix to deploy once fully validated.
Scope of impact: This issue may impact any user within your organization served via the affected region(s): United States, France and United Kingdom. This information may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 2:30 PM UTC
|
|---|
|
| Time: | Fri Jan 23 05:32:37 2026 |
|---|
| Description: | Title: Some users may be unable to access or load Outlook on the web
User impact: Users may be unable to access or load Outlook on the web.
Current status: We've received reports that users may be unable to access or load Outlook on the web, and we're reviewing service monitoring telemetry to understand the scope of impact.
Scope of impact: This issue may impact any user within your organization served via the affected region(s): United States, France and United Kingdom. This information may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 12:30 PM UTC
|
|---|
|
CW1221869 - Some users may not receive Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jan 23 13:42:00 2026 |
|---|
| End Time: | Fri Jan 23 14:36:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jan 23 16:21:44 2026 |
|---|
| Root Cause: | A recent deployment introduced a request routing misconfiguration for Copilot Chat response traffic, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jan 23 15:42:30 2026 |
|---|
| Description: | Title: Some users may not receive Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response
User impact: Users may not have received Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response.
Final status: A recent deployment introduced a request routing misconfiguration for Copilot Chat response traffic, resulting in impact. We've corrected the configuration while our automated recovery system directed affected traffic to infrastructure where the request routing configuration wasn't impacted to remediate impact. We confirmed that service was restored by these actions after monitoring the environment.
Scope of impact: Users may have experienced latency or not received responses while using Microsoft Copilot Chat GPT 5.2 Quick response
Start time: Friday, January 23, 2026, at 6:42 PM UTC
End time: Friday, January 23, 2026, at 7:36 PM UTC
Root cause: A recent deployment introduced a request routing misconfiguration for Copilot Chat response traffic, resulting in impact.
Next steps:
- We're reviewing our update testing and validation process to better identify routing and network issues prior to deployment and avoid issue like this moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 23 14:58:20 2026 |
|---|
| Description: | Title: Some users may not receive Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response
User impact: Users may not receive Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response.
Current status: We're investigating a potential issue with Microsoft Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1220516 - Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 20 18:00:00 2026 |
|---|
| End Time: | Fri Jan 23 12:13:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Jan 23 14:39:34 2026 |
|---|
| Root Cause: | The latest Outlook for iOS update contained a code error related to a change meant to refresh rather than restart tabs when feature flags were updated, which was resulting in this impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jan 23 13:22:30 2026 |
|---|
| Description: | Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may have crashed or froze on iPad devices.
More info: Affected users could launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we worked towards mitigation.
Final status: We've confirmed with a subset of previously affected users that the latest version of the Outlook mobile app (5.2602.1) successfully resolves the issue. Users without automatic updates configured may need to manually update to this version through the App Store.
Scope of impact: This issue may have affected all users' iPad devices using Outlook for iOS version 5.2602.0.
Start time: Tuesday, January 20, 2026, at 11:00 PM UTC
End time: Thursday, January 22, 2026, at 5:13 PM UTC
Root cause: The latest Outlook for iOS update contained a code error related to a change meant to refresh rather than restart tabs when feature flags were updated, which was resulting in this impact.
Next steps:
- We're reviewing our update testing and validation procedures to identify how impact was missed and better prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jan 22 12:02:07 2026 |
|---|
| Description: | Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices.
More info: Affected users can launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we work towards mitigation.
Current status: We've completed the development of our fix to address the underlying issue, and we've provided the new version of the app to Apple who are going through their standard review and release processes. It can take up to 24 hours for the new iOS Outlook app version to appear in the App Store. We recommend users periodically check within the App Store for version 5.2602.1 and update to receive the fix.
Scope of impact: This issue may affect all users' iPad devices using Outlook for iOS version 5.2602.0. This information may be updated as our investigation continues.
Start time: Tuesday, January 20, 2026, at 11:00 PM UTC
Root cause: The latest Outlook for iOS update contains a code error related to a change meant to refresh rather than restart tabs when feature flags are updated, which is resulting in this impact.
Next update by: Friday, January 23, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 17:51:06 2026 |
|---|
| Description: | Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices.
More info: Affected users can launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we work towards mitigation.
Current status: We determined that the latest Outlook for iOS update contains a code error related to a change meant to refresh rather than restart tabs when feature flags are updated, which is resulting in this impact. We’ve developed a code solution for the next update to address this issue, which we intend to roll out to iOS tomorrow. We’ll provide further updates on this timeline as soon as they become available.
Scope of impact: This issue may affect all users' iPad devices using Outlook for iOS version 5.2602.0. This information may be updated as our investigation continues.
Start time: Tuesday, January 20, 2026, at 11:00 PM UTC
Root cause: The latest Outlook for iOS update contains a code error related to a change meant to refresh rather than restart tabs when feature flags are updated, which is resulting in this impact.
Next update by: Thursday, January 22, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 12:56:40 2026 |
|---|
| Description: | Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices.
More info: Affected users can launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we work towards mitigation.
Current status: We've successfully reproduced impact in our internal testing environment. We're analyzing this reproduction of impact to determine if a regression was introduced in the latest Outlook for iOS version to better understand how impact manifests and determine next steps for remediation.
Scope of impact: This issue may affect all users' iPad devices using Outlook for iOS version 5.2602.0. This information may be updated as our investigation continues.
Next update by: Thursday, January 22, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Jan 21 12:50:50 2026 |
|---|
| Description: | Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices.
More info: Affected users can launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we work towards mitigation.
Current status: We're investigating a potential issue with Outlook mobile and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1221222 - Users can't access the Threat Analytics page in Microsoft Defender XDR portal
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 22 07:08:00 2026 |
|---|
| End Time: | Thu Jan 22 09:50:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jan 22 12:02:33 2026 |
|---|
| Root Cause: | An improperly configured infrastructure update prevented users from having the necessary permissions to access the Threat Analytics page in the Microsoft Defender XDR portal. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jan 22 12:02:33 2026 |
|---|
| Description: | Title: Users can't access the Threat Analytics page in Microsoft Defender XDR portal
User impact: Users couldn't access the Threat Analytics page in Microsoft Defender XDR portal.
Final status: We've determined that an improperly configured infrastructure update prevented users from having the necessary permissions to access the Threat Analytics page in the Microsoft Defender XDR portal. We reverted this change and confirmed using our internal telemetry that impact is remediated.
Scope of impact: Any user attempting to access the Threat Analytics page in the Microsoft Defender XDR portal may have been impacted.
Start time: Thursday, January 22, 2026, at 12:08 PM UTC
End time: Thursday, January 22, 2026, at 2:50 PM UTC
Root cause: An improperly configured infrastructure update prevented users from having the necessary permissions to access the Threat Analytics page in the Microsoft Defender XDR portal.
Next steps:
- We're reviewing and improving our infrastructure update validation procedure to detect and prevent similar misconfigurations in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jan 22 11:17:15 2026 |
|---|
| Description: | Title: Users may be unable to access the Threat Analytics page in the Microsoft Defender XDR portal
User impact: Users may have been unable to access the Threat Analytics page in the Microsoft Defender XDR portal.
Current status: We've investigated a problem in which users couldn't access the Threat Analytics page in Microsoft Defender XDR portal and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
MO1220544 - Users' Microsoft Power Automate flows may not trigger when users create, update, or delete shifts in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 20 21:30:00 2026 |
|---|
| End Time: | Wed Jan 21 15:08:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jan 21 15:19:45 2026 |
|---|
| Root Cause: | Our recent efforts to redirect request traffic to alternate portions of infrastructure responsible for facilitating Microsoft Power Automate flows triggered by Microsoft Teams shifts caused the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jan 21 15:19:45 2026 |
|---|
| Description: | Title: Users' Microsoft Power Automate flows may not trigger when users create, update, or delete shifts in Microsoft Teams
User impact: Users' Microsoft Power Automate flows may not have triggered when users created, updated, or deleted shifts.
More info: Flows that were configured with "When a Shift was created, updated or deleted" may have failed to trigger when users performed the actions in Microsoft Teams.
Final status: We've identified that our recent efforts to redirect request traffic to alternate portions of infrastructure, responsible for facilitating Microsoft Power Automate flows triggered by Microsoft Teams shifts, caused the impact. We've reversed the change by directing the traffic back to its original infrastructure and confirmed through internal testing that the impact is remediated.
Scope of impact: Any user that attempted to create, update, or delete shifts in Microsoft Teams and had a Microsoft Power Automate flow configured with "When a Shift was created, updated or deleted" may have been impacted.
Start time: Wednesday, January 21, 2026, at 2:30 AM UTC
End time: Wednesday, January 21, 2026, at 8:08 PM UTC
Root cause: Our recent efforts to redirect request traffic to alternate portions of infrastructure responsible for facilitating Microsoft Power Automate flows triggered by Microsoft Teams shifts caused the impact.
Next steps:
- We're continuing to review the affected infrastructure to identify the reason it caused impact, so that we can prevent similar impacts from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jan 21 14:48:10 2026 |
|---|
| Description: | Title: Users' Microsoft Power Automate flows may not trigger when users create, update, or delete shifts in Microsoft Teams
User impact: Users' Microsoft Power Automate flows may not trigger when users create, update, or delete shifts in Microsoft Teams.
More info: Flows that are configured with "When a Shift is created, updated or deleted" may fail to trigger when users perform the actions in Microsoft Teams.
Current status: We're reproducing the impact in our testing environment to gain clarity on the issue and determine our next steps to isolate the root cause.
Scope of impact: Any user attempting to create, update, or delete shifts in Microsoft Teams and has a Microsoft Power Automate flow configured with "When a Shift is created, updated or deleted" may be impacted.
Next update by: Wednesday, January 21, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 14:23:34 2026 |
|---|
| Description: | Title: Users' Microsoft Power Automate flows aren't triggered when users create, update, or delete shifts in Microsoft Teams
User impact: Users' Microsoft Power Automate flows aren't triggered when users create, update, or delete shifts in Microsoft Teams.
More info: Flows that are configured with "When a Shift is created, updated or deleted" fail to trigger when users perform the actions in Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and Microsoft Power Automate and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1220495 - Users may be unable to access Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 21 11:45:09 2026 |
|---|
| End Time: | Wed Jan 21 12:10:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jan 21 13:24:26 2026 |
|---|
| Root Cause: | A third-party ISP ASN routing configuration issue caused impact to downstream services, such as Microsoft 365. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jan 21 13:24:26 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft 365 services
User impact: Users may have been unable to access Microsoft 365 services, including Teams and Outlook.
More info: As this issue was a result of a third-party ISP Autonomous System Number (ASN) routing configuration issue; the impact to Microsoft 365 services may have manifested in a multitude of ways. For example, some users may have been unable to access the services and portals altogether, whereas others may have seen impact more variable, such being intermittently unable to send or receive email.
Final status: We've determined this issue was a result of a third-party ISP Autonomous System Number (ASN) routing configuration issue, and we've identified that the third-party has taken action to remediate the impact to downstream services, such as Microsoft 365, and we've confirmed the issue is no longer occurring.
Scope of impact: Your organization was affected by this event, and any of your users hosted in North America may have been impacted.
Start time: Wednesday, January 21, 2026, at 4:10 PM UTC
End time: Wednesday, January 21, 2026, at 5:10 PM UTC
Root cause: A third-party ISP ASN routing configuration issue caused impact to downstream services, such as Microsoft 365.
Next steps:
- We're carefully monitoring our managed service environment to ensure the issue doesn't reoccur, and we're reviewing our service resilience practices to identify any necessary improvements so we can reduce the downtime associated with these types of ISP-dependent issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jan 21 12:36:47 2026 |
|---|
| Description: | Title: Users may be unable to access Microsoft 365 services
User impact: Users may be unable to access Microsoft 365 services, including Teams and Outlook.
Current status: Our investigation so far indicates impact is associated with a possible third-party networking issue. We're recursively investigating the health of the Microsoft-managed service environment to identify whether any mitigation actions are required and ensure our services are healthy.
Scope of impact: Your organization is affected by this event, and any of your users hosted in North America may be impacted.
Next update by: Wednesday, January 21, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 12:15:37 2026 |
|---|
| Description: | As the primary reports of impact are originating from users hosted in North America, we're reviewing networking health across the region to help us determine whether there are any connectivity issues affecting the Microsoft-managed service environment.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Jan 21 12:07:08 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, including Teams and Outlook.
Current status: We're reviewing telemetry across dependent portions of service infrastructure to help us isolate the nature of the impact, the source of the issue, and determine what recovery actions may be required.
Scope of impact: The scope of this issue is currently being investigated.
Next update by: Wednesday, January 21, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Jan 21 11:51:14 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, including Teams and Outlook.
Current status: We're investigating a potential issue with Microsoft 365 services and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MF1219609 - Some users may have been unable to run Microsoft Power Automate flows
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 20 05:41:00 2026 |
|---|
| End Time: | Tue Jan 20 07:33:00 2026 |
|---|
| Service: | Microsoft Power Automate in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jan 20 09:51:36 2026 |
|---|
| Root Cause: | An update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jan 20 09:29:19 2026 |
|---|
| Description: | Title: Some users may have been unable to run Microsoft Power Automate flows
User impact: Users may have been unable to run Microsoft Power Automate flows.
More info: Users may have been unable to run flows, use connectors, or perform operations that rely on Power Automate services.
Final status: We’ve determined that an update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services. We’ve confirmed that the service recovered after the aforementioned update completed as expected.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure attempting to run Microsoft Power Automate flows.
Start time: Tuesday, January 20, 2026, at 10:41 AM UTC
End time: Tuesday, January 20, 2026, at 12:33 PM UTC
Root cause: An update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services.
Next steps:
- We're reviewing our Power Platform update procedures to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jan 20 07:40:02 2026 |
|---|
| Description: | Title: Some users may be unable to run Microsoft Power Automate flows
User impact: Users may be unable to run Microsoft Power Automate flows.
More info: Users may be unable to run flows, use connectors, or perform operations that rely on Power Automate services.
Current status: We’re analyzing service telemetry to identify the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to run Microsoft Power Automate flows.
Next update by: Tuesday, January 20, 2026, at 2:30 PM UTC
|
|---|
|
MM1219608 - Some users may have been unable to open Microsoft Power Apps
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 20 07:24:29 2026 |
|---|
| End Time: | Tue Jan 20 07:33:00 2026 |
|---|
| Service: | Power Apps in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Jan 20 09:51:22 2026 |
|---|
| Root Cause: | An update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jan 20 09:27:33 2026 |
|---|
| Description: | Title: Some users may have been unable to open Microsoft Power Apps
User impact: Users may have been unable to open Microsoft Power Apps.
More info: Users may have been unable to open Power Apps, load data from SharePoint-backed applications, or use connectors that rely on Power Apps services.
Final status: We’ve determined that an update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services. We’ve confirmed that the service recovered after the aforementioned update completed as expected.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure attempting to open Power App
Start time: Tuesday, January 20, 2026, at 10:41 AM UTC
End time: Tuesday, January 20, 2026, at 12:33 PM UTC
Root cause: An update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services.
Next steps:
- We're reviewing our Power Platform update procedures to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jan 20 07:38:56 2026 |
|---|
| Description: | Title: Some users may be unable to open Microsoft Power Apps
User impact: Users may be unable to open Microsoft Power Apps.
More info: Users may be unable to open Power Apps, load data from SharePoint-backed applications, or use connectors that rely on Power Apps services.
Current status: We’re analyzing service telemetry to identify the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to open Power Apps.
Next update by: Tuesday, January 20, 2026, at 2:30 PM UTC
|
|---|
|
CP1219289 - Some users may have experienced errors and disruptions when starting or continuing chats in Microsoft Copilot
| Status: | serviceRestored |
|---|
| Start Time: | Mon Jan 19 00:00:00 2026 |
|---|
| End Time: | Mon Jan 19 09:25:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Jan 19 10:30:15 2026 |
|---|
| Root Cause: | A recent standard service update inadvertently contained a code regression, which was resulting in impact. |
|---|
| Next Update: | Monday, January 19, 2026, at 4:00 PM UTC |
|---|
|
Details
| Time: | Mon Jan 19 10:19:03 2026 |
|---|
| Description: | Title: Some users may have experienced errors and disruptions when starting or continuing chats in Microsoft Copilot
User impact: Users may have experienced errors and disruptions when starting or continuing chats in Microsoft Copilot.
More info: Affected users received error messages such as: "A problem has occurred", "Something went wrong," or that the service is unavailable.
Some users were also unable to publish agents created in Microsoft Copilot within Microsoft Teams.
Current status: We've reverted the offending change and confirmed that impact has been remediated.
Scope of impact: Impact was specific to some users attempting to utilize chats in Microsoft Copilot, or publish agents created in Microsoft Copilot within Microsoft Teams.
Start time: Monday, January 19, 2026, at 5:00 AM UTC
End time: Monday, January 19, 2026, at 2:25 PM UTC
Root cause: A recent standard service update inadvertently contained a code regression, which was resulting in impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jan 19 08:42:22 2026 |
|---|
| Description: | Title: Some users may experience errors and disruptions when starting or continuing chats in Microsoft Copilot
User impact: Users may experience errors and disruptions when starting or continuing chats in Microsoft Copilot.
More info: Affected users receive error messages such as: "A problem has occurred", "Something went wrong," or that the service is unavailable.
Current status: We've determined that a recent standard service update inadvertently contains a code regression, which is resulting in impact. We're reverting the offending change to remediate impact.
Scope of impact: Impact is specific to some users attempting to utilize chats in Microsoft Copilot.
Start time: Monday, January 19, 2026, at 5:00 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression, which is resulting in impact.
Next update by: Monday, January 19, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Mon Jan 19 06:40:46 2026 |
|---|
| Description: | Title: Some users may experience errors and disruptions when starting or continuing chats in Microsoft Copilot
User impact: Users may experience errors and disruptions when starting or continuing chats in Microsoft Copilot.
More info: Affected users receive error messages such as: "A problem has occurred", "Something went wrong," or that the service is unavailable.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users attempting to utilize chats in Microsoft Copilot.
Next update by: Monday, January 19, 2026, at 2:00 PM UTC
|
|---|
|
SP1218552 - Some users may be unable to select schedule dates within SharePoint Online pages
| Status: | serviceRestored |
|---|
| Start Time: | Fri Jan 16 01:47:00 2026 |
|---|
| End Time: | Fri Jan 16 18:40:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jan 16 19:24:10 2026 |
|---|
| Root Cause: | A regression was introduced during recent service update which was causing the date selector not to open, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jan 16 19:19:05 2026 |
|---|
| Description: | Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Final status: Our fix has fully saturated throughout the affected environment and after an extended period of monitoring the service health telemetry and validating within our internal testing environment, we’ve confirmed that impact has been remediated.
Scope of impact: Some users who were attempting to select scheduled dates within SharePoint Online may have been impacted.
Start time: Thursday, January 15, 2026, at 6:47 AM UTC
End time: Friday, January 16, 2026, at 11:40 PM UTC
Root cause: A regression was introduced during recent service update which was causing the date selector not to open, which resulted in impact.
Next steps:
- We're reviewing our update vetting procedures to help ensure impact of this nature doesn’t reoccur with future updates.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 16 17:40:54 2026 |
|---|
| Description: | Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Current status: Our fix to correct the regression introduced by the recent service update is currently ten percent saturated across the affected environment and is progressing slower than we initially anticipated. We're monitoring as it deploys to ensure it completes in a timely manner.
Scope of impact: Some users attempting to select scheduled dates within SharePoint Online may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 15, 2026, at 6:47 AM UTC
Root cause: A regression was introduced during recent service update which is causing the date selector not to open, resulting in impact.
Next update by: Saturday, January 17, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Jan 16 15:57:58 2026 |
|---|
| Description: | Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Current status: We’ve initiated the process of rolling out a fix to address this issue and anticipate that the deployment should complete to resolve this issue by our next scheduled update.
Scope of impact: Some users attempting to select scheduled dates within SharePoint Online may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 15, 2026, at 6:47 AM UTC
Root cause: A change introduced as part of a recent service update is causing impact.
Next update by: Saturday, January 17, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Jan 16 07:16:05 2026 |
|---|
| Description: | Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Current status: We've determined that a recent service update is causing impact to occur. As a mitigation strategy, we've initiated the deployment of the fix which has reached an estimated 25 percent of the impacted service environments. We’ll provide a timeline for full completion as soon as it becomes available.
Scope of impact: Some users attempting to select scheduled dates within SharePoint Online may be impacted. This information may be updated as our investigation continues.
Root cause: A change introduced as part of a recent service update is causing impact.
Next update by: Friday, January 16, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Fri Jan 16 06:05:07 2026 |
|---|
| Description: | Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to select scheduled dates within SharePoint Online may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, January 16, 2026, at 1:00 PM UTC
|
|---|
|
DZ1189321 - Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
| 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: | Fri Jan 16 14:58:23 2026 |
|---|
| 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: | Friday, February 20, 2026, at 7:00 PM UTC |
|---|
|
Details
| 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
|
|---|
|
MF1218664 - Users intermittently can't perform HTTP actions in Microsoft Power Automate flows
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 13 14:08:00 2026 |
|---|
| End Time: | Fri Jan 16 12:48:00 2026 |
|---|
| Service: | Microsoft Power Automate in Microsoft 365 |
|---|
| Feature Group: | Service and web access issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jan 16 14:35:00 2026 |
|---|
| Root Cause: | A portion of the service infrastructure supporting HTTP actions in Microsoft Power Automate flows entered an unhealthy state, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jan 16 14:35:00 2026 |
|---|
| Description: | Title: Users intermittently can't perform HTTP actions in Microsoft Power Automate flows
User impact: Users intermittently couldn't perform HTTP actions in Microsoft Power Automate flows.
Final status: We determined that a portion of the service infrastructure supporting HTTP actions in Microsoft Power Automate flows entered an unhealthy state, resulting in impact. We restarted the impacted infrastructure and, following a period of monitoring service health, we confirmed that functionality is restored.
Scope of impact: Your organization was affected by this event, and any user attempting to perform HTTP actions in Microsoft Power Automate flows was intermittently impacted.
Start time: Tuesday, January 13, 2026, at 7:08 PM UTC
End time: Friday, January 16, 2026, at 5:48 PM UTC
Root cause: A portion of the service infrastructure supporting HTTP actions in Microsoft Power Automate flows entered an unhealthy state, resulting in impact.
Next steps:
- We're reviewing the affected service infrastructure to identify why it entered and unhealthy state, allowing us to implement early detection and automated mitigation processes that prevent future impact.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 16 13:43:28 2026 |
|---|
| Description: | Title: Users intermittently can't perform HTTP actions in Microsoft Power Automate flows
User impact: Users intermittently can't perform HTTP actions in Microsoft Power Automate flows.
Current status: We've investigated a problem in which users intermittently couldn't perform HTTP actions in Microsoft Power Automate flows and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.
|
|---|
|
FL1218660 - HTTP actions in flows were intermittently failing
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 13 14:08:00 2026 |
|---|
| End Time: | Fri Jan 16 12:48:00 2026 |
|---|
| Service: | Microsoft Power Automate |
|---|
| Feature Group: | Other |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Jan 16 13:29:05 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Jan 16 13:29:05 2026 |
|---|
| Description: | Title: HTTP actions in flows were intermittently failing
User impact: HTTP actions in flows were intermittently failing.
Final Status: We determined that a portion of the node infrastructure supporting HTTP actions in flows entered an unhealthy state, leading to impact. To mitigate the issue, we restarted the impacted infrastructure and, following a period of monitoring service health, we confirmed that functionality is restored.
This is the final update on the incident.
Preliminary Root Cause: A portion of the node infrastructure supporting HTTP actions in flows entered an unhealthy state.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.
|
|---|
|
SP1218404 - Users may be unable to open People Cards in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 14 13:47:00 2026 |
|---|
| End Time: | Thu Jan 15 23:00:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jan 15 23:25:10 2026 |
|---|
| Root Cause: | Recent authorization changes intended to improve security functionality introduced an error that prevented users from opening People Cards. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jan 15 23:25:10 2026 |
|---|
| Description: | Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may have been unable to open People Cards in SharePoint Online.
Final status: We confirmed that recent authorization changes intended to improve security functionality introduced an error that prevented users from opening People Cards. We reverted the authorization changes and confirmed in our telemetry that the impact is remediated.
Scope of impact: This issue may have potentially impacted any user attempting to open People Cards in SharePoint Online.
Start time: Wednesday, January 14, 2026, at 6:47 PM UTC
End time: Friday, January 16, 2026, at 4:00 AM UTC
Root cause: Recent authorization changes intended to improve security functionality introduced an error that prevented users from opening People Cards.
Next steps:
- We're analyzing the authorization changes to better understand what triggered the initial impact, which will help us in avoiding similar issues during future updates.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jan 15 22:56:42 2026 |
|---|
| Description: | Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may be unable to open People Cards in SharePoint Online.
Current status: Our initial testing shows that disabling the change is remediating impact in our test environment. We're evaluating that the change can be safely disabled for the remaining impacted environment before taking any additional mitigation steps.
Scope of impact: This issue may potentially impact any user attempting to open People Cards in SharePoint Online.
Next update by: Friday, January 16, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Thu Jan 15 20:56:25 2026 |
|---|
| Description: | Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may be unable to open People Cards in SharePoint Online.
Current status: We identified a recent authorization change that we suspect is causing the impact to People Cards. We're testing disabling the change in our environment to validate that it remediates impact.
Scope of impact: This issue may potentially impact any user attempting to open People Cards in SharePoint Online.
Next update by: Friday, January 16, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Thu Jan 15 19:16:18 2026 |
|---|
| Description: | Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may be unable to open People Cards in SharePoint Online.
Current status: We're analyzing system logs, including any recent changes, to identify the source of the issue, which will help us determine our next troubleshooting steps.
Scope of impact: This issue may potentially impact any user attempting to open People Cards in SharePoint Online.
Next update by: Friday, January 16, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Thu Jan 15 18:58:11 2026 |
|---|
| Description: | Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may be unable to open People Cards in SharePoint Online.
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1212913 - Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video
| Status: | serviceRestored |
|---|
| Start Time: | Mon Dec 22 01:14:00 2025 |
|---|
| End Time: | Thu Jan 15 00:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Jan 15 01:49:59 2026 |
|---|
| Root Cause: | A recent routine Microsoft Teams update contained a code issue, which led to higher battery and CPU usage in Microsoft Teams calls. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jan 15 01:49:59 2026 |
|---|
| Description: | Title: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video
User impact: Users may have seen higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
More info: Microsoft Teams users on Windows may have seen higher battery and CPU usage when viewing a screenshare or video from other participants, which could have led to increased battery drain as more participants shared video. This issue only impacted the Microsoft Teams desktop client on Windows.
Final status: The deployment of the fix completed to the affected portion of infrastructure and we've confirmed in our telemetry that the impact is remediated.
Scope of impact: Any user may have been impacted by this event and may have seen higher battery and CPU usage in Microsoft Teams calls when participants screenshared or shared video.
Start time: Monday, December 22, 2025, at 6:14 AM UTC
End time: Thursday, January 15, 2026, at 5:30 AM UTC
Root cause: A recent routine Microsoft Teams update contained a code issue, which led to higher battery and CPU usage in Microsoft Teams calls.
Next steps:
- We're reviewing our update procedures to develop better methods of detecting and preventing similar code issues from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jan 12 00:11:38 2026 |
|---|
| Description: | Title: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video
User impact: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
More info: Microsoft Teams users on Windows may see higher battery and CPU usage when viewing a screenshare or video from other participants, which can lead to increased battery drain as more participants share video. This issue only impacts the Microsoft Teams desktop client on Windows.
Current status: The deployment of the fix is still progressing. We're seeing progress as the fix nears completion in a portion of affected infrastructure. We anticipate the deployment will be completed by our next scheduled update and impact should be resolved.
Scope of impact: Any user may be impacted by this event and may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
Start time: Monday, December 22, 2025, at 6:14 AM UTC
Root cause: A recent routine Microsoft Teams update contained a code issue, leading to higher battery and CPU usage in Microsoft Teams calls.
Next update by: Friday, January 16, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Tue Jan 6 23:12:17 2026 |
|---|
| Description: | Title: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video
User impact: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
More info: Microsoft Teams users on Windows may see higher battery and CPU usage when viewing a screenshare or video from other participants, which can lead to increased battery drain as more participants share video. This issue only impacts the Microsoft Teams desktop client on Windows.
Current status: We've completed validation of the fix and have initiated its deployment. We're monitoring as it progresses and will provide a completion timeline when one becomes available.
Scope of impact: Any user may be impacted by this event and may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
Start time: Monday, December 22, 2025, at 6:14 AM UTC
Root cause: A recent routine Microsoft Teams update contained a code issue, leading to higher battery and CPU usage in Microsoft Teams calls.
Next update by: Monday, January 12, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Mon Jan 5 01:18:14 2026 |
|---|
| Description: | Title: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video
User impact: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
More info: Microsoft Teams users on Windows may see higher battery and CPU usage when viewing a screenshare or video from other participants, which can lead to increased battery drain as more participants share video. This issue only impacts the Microsoft Teams desktop client on Windows.
Current status: We received reports of an issue with higher battery and CPU usage within Microsoft Teams calls. We analyzed service telemetry and recent service changes, which identified a routine update containing a code issue that led to increased battery and CPU usage during calls. We're validating a fix in our internal testing environments. Once validation is complete, we'll monitor progress and proceed with full deployment to the impacted environments.
Scope of impact: Any user may be impacted by this event and may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
Start time: Monday, December 22, 2025, at 6:14 AM UTC
Root cause: A recent routine Microsoft Teams update contained a code issue, leading to higher battery and CPU usage in Microsoft Teams calls.
Next update by: Wednesday, January 7, 2026, at 7:30 AM UTC
|
|---|
|
WP1217671 - Users experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 13 19:11:00 2026 |
|---|
| End Time: | Wed Jan 14 06:41:00 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Jan 14 18:32:17 2026 |
|---|
| Root Cause: | A code misconfiguration in the recent January 2026 Windows security update (KB5074109) caused intermittent connection failures for Cloud PC, causing those access requests to fail. The issue affected Windows App on specific Windows builds, causing sign-in failures. For more information, refer to: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-25h2#3760msgdesc. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jan 14 14:41:03 2026 |
|---|
| Description: | Title: Users experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions
User impact: Users may have experienced intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: To resolve this issue fully, users or admins will need to follow the Known Issue Rollback (KIR) instructions for resolving authentication errors and connection failures when connecting to Windows 365 Cloud PCs:
For enterprise-managed devices managed by IT departments that have installed the affected update and encountered this issue, IT admins can resolve it by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates. Organizations that don't utilize an IT department managed enterprise-managed device update process can also follow the provided links for information on resolving the issue.
For information on deploying and configuring this special Group Policy, please see "How to use Group Policy to deploy a Known Issue Rollback" here: https://learn.microsoft.com/en-us/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback
Download for Windows 11 25H2 and Windows 11 24H2: Windows 11 25H2 and Windows 11 24H2 KB5074109 20260114_07451 Known Issue Rollback: https://download.microsoft.com/download/4ce38d6d-6a7c-477a-b18d-613c5879ead3/Windows%2011%2024H2,%20Windows%2011%2025H2%20and%20Windows%20Server%202025%20KB5074109%20260114_07451%20Known%20Issue%20Rollback.msi
Download for Windows 11 23H2: Windows 11 23H2 KB5073455 260114_09101 Known Issue Rollback: https://download.microsoft.com/download/8f939ffe-afab-4124-9629-0e2eb4d9fa45/Windows%2011%2022H2%20KB5073455%20260114_09101%20Known%20Issue%20Rollback.msi
Download for Windows 10 version 22H2: Windows 10 22H2 KB5073724 20260114_11451 Known Issue Rollback: https://download.microsoft.com/download/aa4a6443-93e5-4046-bdb7-4e2248295e82/Windows%2010%2020H2,%2021H1,%2021H2%20and%2022H2%20KB5073724%20260114_11451%20Known%20Issue%20Rollback.msi
Download for Windows 10 version 1607: Windows 10 1607 KB5073722 20260114_11301 Known Issue Rollback: https://download.microsoft.com/download/c47cf5c1-bb79-4814-acc8-d2f8fa892948/Windows%2010%201607%20and%20Windows%20Server%202016%20KB5073722%20260114_11301%20Known%20Issue%20Rollback.msi
Important: Users and admins need to install and configure the Group Policy for your version of Windows to resolve this issue. Users and admins also need to restart affected devices to apply the group policy setting.
Final status: We've determined that a code misconfiguration in the recent January 2026 Windows security update (KB5074109) caused intermittent connection failures for Cloud PC, causing those access requests to fail. We've deployed a code fix for this issue to better connection handling for the request path and confirmed that this resolves the problem; however, users and admins will need to follow the details laid out in the More info section of this communication to fully resolve the impact.
This post was updated to correct some misconfigured URL links and provide a more accurate representation of why the problem occurred.
Scope of impact: Any user connecting to Cloud PC sessions may have been intermittently affected by this issue.
Start time: Wednesday, January 14, 2026, at 12:11 AM UTC
End time: Wednesday, January 14, 2026, at 11:41 AM UTC
Root cause: A code misconfiguration in the recent January 2026 Windows security update (KB5074109) caused intermittent connection failures for Cloud PC, causing those access requests to fail. The issue affected Windows App on specific Windows builds, causing sign-in failures. For more information, refer to: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-25h2#3760msgdesc.
Next steps:
- We're reviewing our update procedures to better identify similar code issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jan 14 06:44:35 2026 |
|---|
| Description: | Title: Users may experience intermittent failures and issues signing-in when connecting to Microsoft 365 Cloud PC sessions
User impact: Users may experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: If you are impacted, please use one of the following connection options as a workaround:
- Use the Remote Desktop client for Windows to connect to Azure Virtual Desktop here (What's new in the Remote Desktop client for Windows - Remote Desktop client | Microsoft Learn)
- Connect using the Windows App Web Client at windows.cloud.microsoft
Current status: We've developed and implemented a fix to correct the failed connections, with deployment expected to complete by the next scheduled update.
Scope of impact: Any user may be affected and experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
Start time: Wednesday, January 14, 2026, at 12:11 AM UTC
Root cause: A recent Windows 365 update intended to further improve security functionality is causing failed connection attempts to Cloud PC sessions.
Next update by: Wednesday, January 14, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Wed Jan 14 04:02:46 2026 |
|---|
| Description: | Title: Users may experience intermittent failures and issues signing-in when connecting to Microsoft 365 Cloud PC sessions
User impact: Users may experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: If you are impacted, please use one of the following connection options as a workaround:
- Use the Remote Desktop client for Windows to connect to Azure Virtual Desktop here (What's new in the Remote Desktop client for Windows - Remote Desktop client | Microsoft Learn)
- Connect using the Windows App Web Client at windows.cloud.microsoft
Current status: We're continuing with our analysis of the recent update to determine how best to mitigate impact.
Scope of impact: Any user may be affected and experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
Start time: Wednesday, January 14, 2026, at 12:11 AM UTC
Root cause: A recent Windows 365 update intended to further improve security functionality is causing failed connection attempts to Cloud PC sessions.
Next update by: Wednesday, January 14, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jan 14 01:18:44 2026 |
|---|
| Description: | Title: Users may experience intermittent failures and issues signing-in when connecting to Microsoft 365 Cloud PC sessions
User impact: Users may experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: Users can utilize the following connection options to avoid impact:
- Connect using the Windows App Web Client at windows.cloud.microsoft
- Use the Remote Desktop client to connect to Windows 365.
Current status: We identified that a recent Windows 365 update intended to further improve security functionality is causing failed connection attempts. We're further analyzing the update to determine the best method of remediating the impact. We'll provide further updates on the potential mitigation plans as they become available.
Scope of impact: Any user may be affected and experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
Start time: Wednesday, January 14, 2026, at 12:11 AM UTC
Root cause: A recent Windows 365 update intended to further improve security functionality is causing failed connection attempts to Cloud PC sessions.
Next update by: Wednesday, January 14, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Tue Jan 13 22:58:32 2026 |
|---|
| Description: | Title: Users may experience intermittent failures and issues signing-in when connecting to Microsoft 365 Cloud PC sessions
User impact: Users may experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: Users can utilize the following connection options to avoid impact:
- Connect using the Windows App Web Client at windows.cloud.microsoft
- Use the Remote Desktop client to connect to Windows 365.
Current status: We detected an issue with Cloud PC connections and sign-in through our automated service monitoring after seeing an increase in failed connection attempts. We're investigating our service telemetry, including recent Windows 365 updates, to identify the underlying cause of impact and to help inform our next troubleshooting steps.
Scope of impact: Any user may be affected and experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
Next update by: Wednesday, January 14, 2026, at 7:30 AM UTC
|
|---|
|
MO1213801 - Users may have been unable to access shared Microsoft To Do lists
| Status: | serviceRestored |
|---|
| Start Time: | Mon Dec 29 15:00:00 2025 |
|---|
| End Time: | Wed Jan 14 07:30:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Jan 14 09:04:10 2026 |
|---|
| Root Cause: | A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Jan 14 08:52:49 2026 |
|---|
| Description: | Title: Users may have been unable to access shared Microsoft To Do lists
User impact: Users may have been unable to access shared Microsoft To Do lists.
More info: Users may also have been unable to open shared To Do list invitation links.
Final status: We’ve confirmed that the issue is resolved following successful deployment of the fix.
Scope of impact: This issue may have potentially impacted any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
End time: Wednesday, January 14, 2026, at 12:30 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which resulted in impact.
Next steps:
- We’ll continue monitoring the sharing functionality to ensure stability and service health.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jan 13 04:26:06 2026 |
|---|
| Description: | Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We’ve identified that a small number of system processes are running more slowly than expected, which is temporarily delaying the reversion of the change. The reversion has now been successfully completed for approximately 93% of the affected environments. We’ll provide an updated completion timeline as soon as it’s available.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Wednesday, January 14, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Jan 12 09:31:30 2026 |
|---|
| Description: | Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're continuing to revert the offending change and anticipate completion by the end of Monday, January 12, 2026. Once completed, we'll need to monitor for an extended period of time to ensure that impact has been fully resolved.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Tuesday, January 13, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Fri Jan 9 10:20:37 2026 |
|---|
| Description: | Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We've started the reversion process and anticipate complete by Monday, January 12, 2026.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Estimated time to resolve: Monday, January 12, 2026
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Monday, January 12, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Jan 8 11:44:19 2026 |
|---|
| Description: | Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're completing the final validations prior to initiating the reversion process which we anticipate will begin by our next scheduled communications update.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Friday, January 9, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Jan 7 14:26:34 2026 |
|---|
| Description: | Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We've identified a recent change, intended to add optimizations when sharing To Do lists, that's introduced a misconfiguration and is resulting in impact. We're reverting this change to resolve the issue, and we'll provide a timeline for remediation as one becomes available.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Thursday, January 8, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Jan 6 19:36:24 2026 |
|---|
| Description: | Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're continuing to analyze a reproduction of the impact within our internal testing environment as well as reviewing recent updates.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Next update by: Wednesday, January 7, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 16:44:01 2026 |
|---|
| Description: | Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're analyzing a reproduction of impact within our internal testing environment along with reviewing recent updates to Microsoft To Do, to isolate potential discrepancies and to determine our next troubleshooting steps.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Next update by: Wednesday, January 7, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Jan 6 13:22:33 2026 |
|---|
| Description: | Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: Our investigation of service logs indicates that requests to access Microsoft To Do lists are returning 'not found'. We're continuing our analysis of these logs to further isolate the root cause of impact and develop a remediation strategy.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Next update by: Tuesday, January 6, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 02:48:43 2026 |
|---|
| Description: | Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're analyzing system logs including any recent changes to assist in identifying the source of the issue, which will help us determine our next troubleshooting steps.
Scope of impact: This issue may potentially impact any user attempting to access a shared Microsoft To Do lists.
Next update by: Tuesday, January 6, 2026, at 7:30 PM UTC
|
|---|
|
OP1217551 - Some users may not be able to get the latest Microsoft 365 Apps updates
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 13 10:30:00 2026 |
|---|
| End Time: | Tue Jan 13 17:00:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jan 13 18:16:55 2026 |
|---|
| Root Cause: | Values needed weren’t present in the release build which then prevented the Cloud Update service from picking up the new update, and this resulted in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jan 13 18:04:21 2026 |
|---|
| Description: | Title: Some users may not be able to get the latest Microsoft 365 Apps updates
User impact: Users may not have been able to get the latest Microsoft 365 Apps updates.
More info: This issue specifically impacted organizations where these updates were facilitated through the Cloud Update process in the Microsoft 365 apps admin center.
Final status: After our analysis of the latest update, we determined that values needed weren’t present in the release build which then prevented the Cloud Update service from picking up the new update, and this resulted in the impact. We've applied a fix to restore the values and confirmed that this has remediated the issue.
Scope of impact: Some users reliant on the Cloud Update process to update their Microsoft 365 apps may have been affected.
Start time: Tuesday, January 13, 2026, at 3:30 PM UTC
End time: Tuesday, January 13, 2026, at 10:00 PM UTC
Root cause: Values needed weren’t present in the release build which then prevented the Cloud Update service from picking up the new update, and this resulted in the impact.
Next steps:
- We're reviewing our update standards to ensure missing values are caught and corrected ahead of publishing to prevent this from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Jan 13 15:39:14 2026 |
|---|
| Description: | Title: Some users may not be able to get the latest Microsoft 365 Apps updates
User impact: Users may not be able to get the latest Microsoft 365 Apps updates.
More info: This issue specifically impacts organizations where these updates are facilitated through the Cloud Update process in the Microsoft 365 apps admin center.
Current status: We're analyzing the latest update to determine our next troubleshooting steps.
Scope of impact: Some users reliant on the Cloud Update process to update their Microsoft 365 apps may be affected. This section may be updated as our investigation continues.
Next update by: Wednesday, January 14, 2026, at 12:30 AM UTC
|
|---|
|
SP1216181 - Users may not receive email notifications generated from the SharePoint Online Rules
| Status: | serviceRestored |
|---|
| Start Time: | Mon Dec 8 07:00:00 2025 |
|---|
| End Time: | Tue Jan 13 13:00:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jan 13 13:39:15 2026 |
|---|
| Root Cause: | A recent feature update contained a code error that prevented email notifications from generating as expected, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jan 13 13:39:15 2026 |
|---|
| Description: | Title: Users may not receive email notifications generated from the SharePoint Online Rules
User impact: Users may not have received email notifications generated from the SharePoint Online Rules feature.
More info: Users could have created a new rule with the same settings as an affected rule to bypass the impact while we worked to resolve this issue.
Final status: We've confirmed the fix has completed deployment and the configuration change has been applied. After validating impact remediation with a subset of affected users, we've verified the issue has been resolved.
Scope of impact: Any user expecting SharePoint Online rules email notifications may have been affected.
Start time: Monday, December 8, 2025, at 12:00 PM UTC
End time: Tuesday, January 13, 2026, at 6:00 PM UTC
Root cause: A recent feature update contained a code error that prevented email notifications from generating as expected, which resulted in impact.
Next steps:
- We're reviewing our feature update protocols to ensure similar code errors are caught and addressed ahead of deployment to prevent this from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jan 12 13:40:59 2026 |
|---|
| Description: | Title: Users may not receive email notifications generated from the SharePoint Online Rules
User impact: Users may not receive email notifications generated from the SharePoint Online Rules feature.
More info: Users can create a new rule with the same settings as an affected rule to bypass the impact while we work to resolve this issue.
Current status: We're monitoring as the fix continues its deployment and confirmed it's reached over 95 percent of affected infrastructure. Once complete, an additional configuration change will be applied to fully remediate impact. We hope to provide a remediation timeline by the next scheduled update.
Scope of impact: Any user expecting SharePoint Online rules email notifications may be affected.
Start time: Monday, December 8, 2025, at 12:00 PM UTC
Root cause: A recent feature update contains a code error that's preventing email notifications from generating as expected, resulting in impact.
Next update by: Tuesday, January 13, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jan 9 16:12:31 2026 |
|---|
| Description: | Title: Users may not receive email notifications generated from the SharePoint Online Rules
User impact: Users may not receive email notifications generated from the SharePoint Online Rules feature.
More info: Users can create a new rule with the same settings as an affected rule to bypass the impact while we work to resolve this issue.
Current status: Our analysis of recent changes has confirmed that a recent feature update contains a code error that's preventing email notifications from generating as expected, resulting in impact. We're in the process of developing a fix to remediate impact and expect to have a mitigation timeline by the next scheduled communications update.
Scope of impact: Any user expecting SharePoint Online rules email notifications may be affected.
Start time: Monday, December 8, 2025, at 12:00 PM UTC
Root cause: A recent feature update contains a code error that's preventing email notifications from generating as expected, resulting in impact.
Next update by: Monday, January 12, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Jan 9 13:43:05 2026 |
|---|
| Description: | Title: Users aren't receiving notification emails generated from the SharePoint Online Rules feature
User impact: Users aren't receiving notification emails generated from the SharePoint Online Rules feature.
More info: Users can create a new rule with the same settings as an affected rule to bypass the impact while we work to resolve this issue.
Current status: We're reviewing recent service updates which may be contributing to impact.
Scope of impact: Any user expecting SharePoint Online rules notifications may be affected.
Next update by: Friday, January 9, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Jan 9 13:19:15 2026 |
|---|
| Description: | Title: Users aren't receiving notification emails generated from the SharePoint Online Rules feature
User impact: Users aren't receiving notification emails generated from the SharePoint Online Rules feature.
More info: This event is a continuation of the incident previously communicated via SP1216014.
Users can create a new rule with the same settings as an affected rule to bypass the impact while we work to resolve this issue.
Current status: We're investigating a potential issue with SharePoint Online rules and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1217058 - Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 8 01:00:00 2026 |
|---|
| End Time: | Mon Jan 12 22:30:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Jan 13 01:56:28 2026 |
|---|
| Root Cause: | A recent service update designed to change how tasks deliver subscription email messages for reports and dashboards in Microsoft Power BI were processed, was preventing the tasks from being completed efficiently and causing impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Jan 13 01:56:28 2026 |
|---|
| Description: | Title: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' subscription email messages for reports and dashboards in Microsoft Power BI were delayed or weren't delivered.
More info: Impact was intermittent for some users.
While we worked on fixing the issue, users could've leveraged the "send now" button to deliver the subscription email messages.
Final status: We've completed reverting the offending update, and after a period of monitoring, we confirmed impact was remediated.
Scope of impact: Your organization was affected by this event, and any user configured to receive email messages reports and dashboards in Microsoft Power BI was impacted.
Start time: Thursday, January 8, 2026, at 6:00 AM UTC
End time: Tuesday, January 13, 2026, at 3:30 AM UTC
Root cause: A recent service update designed to change how tasks deliver subscription email messages for reports and dashboards in Microsoft Power BI were processed, was preventing the tasks from being completed efficiently and causing impact.
Next steps:
- To help prevent similar impact in the future, we're further reviewing our update release procedures to identify delivery and processing issues before being deployed.
This is the final update for the event.
|
|---|
|
| Time: | Mon Jan 12 18:13:16 2026 |
|---|
| Description: | Title: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered.
More info: Impact is intermittent for some users.
While we work on fixing this issues, users can leverage the "send now" button to deliver the subscription email messages.
Current status: We're identified a recent service update designed to change how tasks to deliver subscription email messages for reports and dashboards in Microsoft Power BI are processed, which is preventing the tasks from being completed efficiently and causing impact. We're reversing the offending change to remediate the impact.
Scope of impact: Your organization is affected by this event, and any user configured to receive email messages reports and dashboards in Microsoft Power BI is impacted.
Start time: Thursday, January 8, 2026, at 6:00 AM UTC
Root cause: A recent service update designed to change how tasks to deliver subscription email messages for reports and dashboards in Microsoft Power BI are processed, is preventing the tasks from being completed efficiently and causing impact.
Next update by: Tuesday, January 13, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Mon Jan 12 16:53:44 2026 |
|---|
| Description: | Title: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered.
More info: Impact is intermittent for some users.
While we work on fixing this issue, users can leverage the "send now" button to deliver the subscription email messages.
Current status: We're reviewing the portion of service infrastructure responsible for facilitating the delivery of subscription email messages for reports and dashboards in Microsoft Power BI to check whether the tasks to deliver the email messages are being processed efficiently.
Scope of impact: Your organization is affected by this event, and any user configured to receive email messages reports and dashboards in Microsoft Power BI is impacted.
Next update by: Tuesday, January 13, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Jan 12 15:39:05 2026 |
|---|
| Description: | Title: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered.
More info: Impact is intermittent for some users.
Current status: We're reviewing the queue of unsent email subscription messages to determine the next steps to isolate why they're delayed for failing to send.
Scope of impact: Your organization is affected by this event, and any user configured to receive email messages reports and dashboards in Microsoft Power BI is impacted.
Next update by: Monday, January 12, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Jan 12 15:23:07 2026 |
|---|
| Description: | Title: Users' email subscriptions for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' email subscriptions for reports and dashboards in Microsoft Power BI are delayed or aren't delivered.
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.
|
|---|
|
CP1215237 - Users may be unable to use the AI features in the Create module of Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Mon Dec 15 13:35:00 2025 |
|---|
| End Time: | Fri Jan 9 12:35:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jan 12 16:48:02 2026 |
|---|
| Root Cause: | A recent code change intended to introduce a toggle that disables the AI features in the Create module was causing the previously available AI features to been hidden and inaccessible for all users, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jan 12 16:48:02 2026 |
|---|
| Description: | Title: Users may be unable to use the AI features in the Create module of Microsoft Copilot (Microsoft 365)
User impact: Users may have been unable to use the AI features in the Create module of Microsoft Copilot.
Final status: We've confirmed our fix to address the impact caused by the recent code change has completed deploying to the affected environment and the issue has been remediated.
Scope of impact: Any user attempting to use the AI features in the Create module of Microsoft Copilot may have been impacted by this event.
Start time: Monday, December 15, 2025, at 6:35 PM UTC
End time: Friday, January 9, 2026, at 5:35 PM UTC
Root cause: A recent code change intended to introduce a toggle that disables the AI features in the Create module was causing the previously available AI features to been hidden and inaccessible for all users, which resulted in impact.
Next steps:
- We're reviewing our update procedures to ensure similar issues are caught and addressed ahead of any code changes to prevent this from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Wed Jan 7 21:14:56 2026 |
|---|
| Description: | Title: Users may be unable to use the AI features in the Create module of Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to use the AI features in the Create module of Microsoft Copilot.
Current status: We've been made aware of an issue in which users may be unable to use the AI features in the Create module of Microsoft Copilot. We've determined that a recent code change intended to introduce a toggle that disables the AI features in the Create module is causing the previously available AI features to be hidden and inaccessible for all users, resulting in impact. We've developed a fix to address the issue and we're preparing it for deployment throughout the affected environments. We anticipate our fix will complete the deployment by our next scheduled communications update.
Scope of impact: Any user attempting to use the AI features in the Create module of Microsoft Copilot may be impacted by this event. This information may be updated as our investigation continues.
Root cause: A recent code change intended to introduce a toggle that disables the AI features in the Create module is causing the previously available AI features to be hidden and inaccessible for all users, resulting in impact.
Next update by: Thursday, January 15, 2026, at 8:00 PM UTC
|
|---|
|
TM1212728 - Users may have been unable to search new users in Microsoft Teams by their display name
| Status: | serviceRestored |
|---|
| Start Time: | Tue Dec 9 19:00:00 2025 |
|---|
| End Time: | Sun Jan 11 19:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Jan 12 05:55:22 2026 |
|---|
| Root Cause: | A recent change to our Active Directory service introduced a regression affecting user search functionality. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Jan 12 05:55:22 2026 |
|---|
| Description: | Title: Users may have been unable to search new users in Microsoft Teams by their display name
User impact: Users may have been unable to search new users in Microsoft Teams by their display name.
More info: This may have impacted users in both the desktop and web clients. Users could still search new users using their email address.
Final status: We've successfully completed the reindexing and verified with some affected users, that impact has fully resolved.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may have been impacted.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
End time: Monday, January 12, 2026, at 12:00 AM UTC
Root cause: A recent change to our Active Directory service introduced a regression affecting user search functionality.
Next steps:
- We're reviewing our change procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Jan 9 06:22:27 2026 |
|---|
| Description: | Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We've completed the index reset and enabled it for all customers on Wednesday, January 6, 2026, at 15:00 UTC. Reindexing continues to progress as planned and is expected to complete by Monday, January 12, 2026.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Estimated time to resolve: Monday, January 12, 2026
Root cause: A recent change to our Active Directory service introduced a regression affecting user search functionality, resulting in impact.
Next update by: Monday, January 12, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Wed Jan 7 05:39:22 2026 |
|---|
| Description: | Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We’re continuing to reset the index for affected customers in stages. The process has already been enabled for 50% of customers and will advance to 100% tomorrow. Due to heavy system load and parallel processing, completion is expected by Monday, January 12, 2026. Once complete, normal search functionality will be restored for impacted users.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Estimated time to resolve: Monday, January 12, 2026
Root cause: A recent change to our Active Directory service introduced a regression affecting user search functionality, resulting in impact.
Next update by: Friday, January 9, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jan 5 05:50:21 2026 |
|---|
| Description: | Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We've identified that a recent change to our Active Directory service introduced a regression affecting user search functionality. This change has been rolled back, and reindexing has been initiated for impacted customers. We expect the index rebuild to complete within 48 hours, after which normal search functionality will be restored for impacted users.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Root cause: A recent change to our Active Directory service introduced a regression affecting user search functionality, resulting in impact.
Next update by: Wednesday, January 7, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Jan 5 03:19:48 2026 |
|---|
| Description: | Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We're continuing to review the provided case details and logs to help identify the underlying cause of the display name search issue for new users, and help to develop our next troubleshooting steps.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, January 5, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Sun Jan 4 22:14:01 2026 |
|---|
| Description: | Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We're reviewing the provided case details and logs to help identify the underlying cause of the display name search issue for new users, and help to develop our next troubleshooting steps.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, January 5, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Jan 4 21:46:34 2026 |
|---|
| Description: | Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
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.
|
|---|
|
SP1215831 - Some read-only users may see blank pages for their SharePoint Online sites
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 7 14:44:00 2026 |
|---|
| End Time: | Thu Jan 8 13:18:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jan 8 15:22:17 2026 |
|---|
| Root Cause: | The latest SharePoint Online service build contained a regression which resulted in read-only users seeing blank pages for their SharePoint Online sites. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jan 8 14:53:29 2026 |
|---|
| Description: | Title: Some read-only users may see blank pages for their SharePoint Online sites
User impact: Read-only users may have seen blank pages for their SharePoint Online sites.
More info: Affected users reported seeing relevant page information displaying briefly before becoming a blank page.
Final status: We've validated that the latest SharePoint Online service build contained a regression which resulted in read-only users seeing blank pages for their SharePoint Online sites. We've rolled back the offending build and validated with a subset of affected users that our actions successfully resolved the issue.
Scope of impact: Some read-only users may have seen blank pages for their SharePoint Online sites.
Start time: Wednesday, January 7, 2026, at 7:44 PM UTC
End time: Thursday, January 8, 2026, at 6:18 PM UTC
Root cause: The latest SharePoint Online service build contained a regression which resulted in read-only users seeing blank pages for their SharePoint Online sites.
Next steps:
- We're analyzing the offending service build to isolate the underlying root cause. This analysis will help us to improve the quality and reliability of our future updates, while also helping that similar impact doesn't occur in future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jan 8 14:20:45 2026 |
|---|
| Description: | Title: Some read-only users may see blank pages for their SharePoint Online sites
User impact: Read-only users may see blank pages for their SharePoint Online sites.
More info: Affected users report seeing relevant page information displaying briefly before becoming a blank page.
Current status: We're reviewing reports from affected users to understand the current impact scenario and to determine what mitigation actions we can take to resolve impact.
Scope of impact: Some read-only users may see blank pages for their SharePoint Online sites. This section may be updated as the investigation progresses.
Next update by: Thursday, January 8, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Thu Jan 8 14:07:37 2026 |
|---|
| Description: | Title: Read-only users see blank pages for their SharePoint Online sites
User impact: Read-only users see blank pages for their SharePoint Online sites.
More info: Affected users report seeing relevant page information displaying briefly before becoming a blank page.
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.
|
|---|
|
EX1215307 - Some users may have been unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
| Status: | serviceRestored |
|---|
| Start Time: | Thu Jan 1 19:00:00 2026 |
|---|
| End Time: | Thu Jan 8 06:30:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Jan 8 07:34:33 2026 |
|---|
| Root Cause: | A recent IMAP deployment related to authentication support contained a code conflict that introduced a configuration issue and was causing intermittent mailbox access issues for some impacted users. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Jan 8 07:34:33 2026 |
|---|
| Description: | Title: Some users may have been unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may have intermittently been unable to access their mailboxes using IMAP4.
More info: Impact was specific to IMAP4, other connection methods were not impacted. Additionally, if users were actively facing this issue, retries may have been successful.
Final status: We’ve completed deploying the configuration change on the affected servers, which reduced volume and restored normal service functionality. After a period of monitoring, we’ve confirmed that impact has been fully remediated.
Scope of impact: Some users that were attempting to access their mailboxes using IMAP4 may have been intermittently impacted.
Start time: Friday, January 2, 2026, at 12:00 AM UTC
End time: Thursday, January 8, 2026, at 11:30 AM UTC
Root cause: A recent IMAP deployment related to authentication support contained a code conflict that introduced a configuration issue and was causing intermittent mailbox access issues for some impacted users.
Next steps:
- We're reviewing our deployment and provisioning procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jan 8 07:19:31 2026 |
|---|
| Description: | Title: Some users may have been unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may have intermittently been unable to access their mailboxes using IMAP4.
More info: Impact was specific to IMAP4, other connection methods were not impacted. Additionally, if users were actively facing this issue, retries may have been successful.
Final status: We’ve completed deploying the configuration change on the affected servers, which reduced volume and restored normal service functionality. After a period of monitoring, we’ve confirmed that impact has been fully remediated.
Scope of impact: Some users that were attempting to access their mailboxes using IMAP4 may have been intermittently impacted.
Start time: Friday, January 2, 2026, at 12:00 AM UTC
End time: Thursday, January 8, 2026, at 11:30 AM UTC
Root cause: A recent IMAP deployment related to authentication support contained a code conflict that introduced a configuration issue and was causing intermittent mailbox access issues for some impacted users.
Next steps:
- We're reviewing our deployment and provisioning procedures to help prevent similar problems in the future.
This is the final update for the event.
|
|---|
|
| Time: | Thu Jan 8 02:58:43 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may intermittently be unable to access their mailboxes using IMAP4.
More info: Impact is specific to IMAP4, other connection methods are not impacted. Additionally, if users are actively facing this issue, retries may be successful.
Current status: We're continuing to deploy the configuration change and expect this process to complete by our next scheduled update.
Scope of impact: Some users that are attempting to access their mailboxes using IMAP4 may be intermittently impacted. This information may be updated as our investigation continues.
Root cause: A recent IMAP deployment related to authentication support contains a code conflict that introduced a configuration issue and is causing intermittent mailbox access issues for some impacted users.
Next update by: Thursday, January 8, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Thu Jan 8 00:37:19 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may intermittently be unable to access their mailboxes using IMAP4.
More info: Impact is specific to IMAP4, other connection methods are not impacted. Additionally, if users are actively facing this issue, retries may be successful.
Current status: We've completed developing the configuration change and have validated it in our internal testing environment to ensure its efficacy in remediating impact. We've started deploying it to the impacted environments and we'll aim to provide a resolution timeline by our next scheduled update.
Scope of impact: Some users that are attempting to access their mailboxes using IMAP4 may be intermittently impacted. This information may be updated as our investigation continues.
Root cause: A recent IMAP deployment related to authentication support contains a code conflict that introduced a configuration issue and is causing intermittent mailbox access issues for some impacted users.
Next update by: Thursday, January 8, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Thu Jan 8 00:09:13 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may intermittently be unable to access their mailboxes using IMAP4.
More info: Impact is specific to IMAP4, other connection methods are not impacted. Additionally, if users are actively facing this issue, retries may be successful.
Current status: We've identified a recent IMAP deployment related to authentication support contains a code conflict that introduced a configuration issue and is causing intermittent mailbox access issues for some impacted users. We're halting the deployment to prevent further impact from spreading and are developing a configuration change to restore service functionality. We'll aim to provide a resolution timeline once available.
Scope of impact: Some users that are attempting to access their mailboxes using IMAP4 may be intermittently impacted. This information may be updated as our investigation continues.
Root cause: A recent IMAP deployment related to authentication support contains a code conflict that introduced a configuration issue and is causing intermittent mailbox access issues for some impacted users.
Next update by: Thursday, January 8, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Wed Jan 7 23:52:58 2026 |
|---|
| Description: | Title: Some users may intermittently be unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may intermittently be unable to access their mailboxes using IMAP4.
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.
|
|---|
|
|
