Microsoft's Incident Report for PennO365
Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within
the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh
this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this
list. Additionally you can check Microsoft's
status page for current service status messages.
The last extract was taken on Wed Mar 18 17:00:08 2026.
PC1254549 - Sales in Microsoft 365 Copilot – Multiple degraded scenarios related to meetings
| Status: | restoringService |
|---|
| Start Time: | Tue Mar 17 05:17:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Power Platform) |
|---|
| Feature Group: | Microsoft Copilot for Sales |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 18 15:32:35 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 18 15:29:42 2026 |
|---|
| Description: | Title: Sales in Microsoft 365 Copilot - Multiple degraded scenarios related to meetings
User impact: Users are experiencing multiple degraded scenarios related to meetings.
More Info: Users experience impact in the following scenarios:
• Failures receiving notifications related to meetings, including meeting prep, daily digest and post meeting summary.
• Failures viewing Meeting Prep insights in Sales Home.
• Failures viewing and performing actions with the Post Meeting summary.
• Insights for meetings are not available in Recent Communications and Entity Insights.
As a mitigating workaround to restore functionality for the listed scenarios, users may open and load the Sales app in the Outlook side panel for a brief period.
Current Status: We are continuing to monitor the recovery as it progresses.
Next Update: Thursday, March 19, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Mar 17 19:38:37 2026 |
|---|
| Description: | Title: Sales in Microsoft 365 Copilot - Multiple degraded scenarios related to meetings
User impact: Users are experiencing multiple degraded scenarios related to meetings.
More Info: Users experience impact in the following scenarios:
• Failures receiving notifications related to meetings, including meeting prep, daily digest and post meeting summary.
• Failures viewing Meeting Prep insights in Sales Home.
• Failures viewing and performing actions with the Post Meeting summary.
• Insights for meetings are not available in Recent Communications and Entity Insights.
As a mitigating workaround to restore functionality for the listed scenarios, users may open and load the Sales app in the Outlook side panel for a brief period.
Current Status: Service diagnostics indicate that the failures are gradually decreasing without our manual intervention. In parallel with our root cause analysis, we are monitoring the failure recovery as it progresses.
Next Update: Wednesday, March 18, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Mar 17 19:07:05 2026 |
|---|
| Description: | Title: Sales in Microsoft 365 Copilot - Multiple degraded scenarios related to meetings
User impact: Users are experiencing multiple degraded scenarios related to meetings.
More Info: Users experience impact in the following scenarios:
• Failures receiving notifications related to meetings, including meeting prep, daily digest and post meeting summary.
• Failures viewing Meeting Prep insights in Sales Home.
• Failures viewing and performing actions with the Post Meeting summary.
• Insights for meetings are not available in Recent Communications and Entity Insights.
As a mitigating workaround to restore functionality for the listed scenarios, users may open and load the Sales app in the Outlook side panel for a brief period.
Current Status: After our investigation, we identified that the Redis cache utilized by the service infrastructure supporting the listed scenarios was inadvertently cleared. We are reviewing diagnostics of the affected infrastructure to determine what caused the cache to be cleared and determine our next troubleshooting steps.
Next Update: Wednesday, March 18, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Mar 17 18:36:37 2026 |
|---|
| Description: | Title: Sales in Microsoft 365 Copilot – Multiple degraded scenarios related to meetings
User impact: Users are experiencing multiple degraded scenarios related to meetings.
More Info: Users experience impact in the following scenarios:
• Failures receiving notifications related to meetings, including meeting prep, daily digest and post meeting summary.
• Failures viewing Meeting Prep insights in Sales Home.
• Failures viewing and performing actions with the Post Meeting summary.
• Insights for meetings are not available in Recent Communications and Entity Insights.
As a mitigating workaround to restore functionality for the listed scenarios, users may open and load the Sales app in the Outlook side panel for a brief period.
Current Status: We are aware of an emerging issue where experience users experience the listed scenarios related to meetings in Sales in Microsoft 365 Copilot. 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.
|
|---|
|
CP1253444 - Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Mar 16 11:11:25 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 18 14:59:27 2026 |
|---|
| Root Cause: | A portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. |
|---|
| Next Update: | Thursday, March 19, 2026, at 8:30 PM UTC |
|---|
|
Details
| Time: | Wed Mar 18 14:59:27 2026 |
|---|
| Description: | Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients
User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients.
More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes":
https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes
Current status: Our solution to improve traffic dispersal is fully saturated and our initial internal validations indicate the issue is no longer occurring. We're beginning to reach out to a subset of affected users for further verification.
Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues.
Root cause: A portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact.
Next update by: Thursday, March 19, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Mar 17 14:01:14 2026 |
|---|
| Description: | Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients
User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients.
More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes":
https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes
Current status: We're observing improvement in our telemetry, and we're continuing to monitor to ensure this trend continues as our fix to improve traffic dispersal completes deployment. In parallel, we're beginning to perform internal validations to confirm the fix effectively remediates the impact before we begin reaching out to a subset of affected users for further verification.
Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues.
Root cause: A portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact.
Next update by: Wednesday, March 18, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Mar 16 20:48:17 2026 |
|---|
| Description: | Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients
User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients.
More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes":
https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes
Current status: We've identified a portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact. We're deploying a fix to better disperse traffic throughout additional infrastructure to improve processing and we're monitoring telemetry to ensure that our remediation plan is successful.
Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues.
Root cause: A portion of infrastructure responsible for the functionality of the Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients isn't processing requests as efficiently as expected and is resulting in impact.
Next update by: Tuesday, March 17, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Mar 16 13:26:23 2026 |
|---|
| Description: | Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients
User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients.
More info: This event is related to a known issue with Microsoft Office add-ins, as explained in the following public documentation under "ISSUE: Intermittent failure to load or deploy Office Add-ins due to Exchange authentication changes":
https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues#issue-intermittent-failure-to-load-or-deploy-office-add-ins-due-to-exchange-authentication-changes
Current status: We're reviewing service health telemetry in tandem with the aforementioned logs from impacted users to further isolate a root cause for this known issue with Microsoft Office add-ins and develop a remediation solution.
Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues.
Next update by: Tuesday, March 17, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Mar 16 11:45:27 2026 |
|---|
| Description: | Title: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients
User impact: Users' Copilot for Sales add-in may not appear on Outlook mobile and Outlook for Mac clients.
Current status: We're reviewing logs from impacted users while attempting to conduct reproductions of impact within our internal testing environment to troubleshoot this issue and determine our next steps.
Scope of impact: Some users attempting to view their Copilot for Sales add-in on Outlook mobile and Outlook for Mac clients may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, March 16, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Mon Mar 16 11:12:49 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 Copilot
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft 365 Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1254548 - Some users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics"
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Mar 17 18:32:23 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 18 14:46:06 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | Wednesday, March 18, 2026, at 10:30 PM UTC |
|---|
|
Details
| Time: | Wed Mar 18 14:46:06 2026 |
|---|
| Description: | Title: Some users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics"
User impact: Users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics" attachment.
Current status: We’re continuing our ongoing analysis of available reproduction examples and associated service-side logs, while attempting to reproduce the issue internally to gather additional diagnostic data to aid our investigation and determine appropriate remediation actions.
Scope of impact: This incident impacts using receiving Microsoft Teams meeting invitations who may see the invitation as a “not supported calendar message.ics" attachment. This information may be updated as our investigation continues.
Next update by: Wednesday, March 18, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Mar 18 14:03:41 2026 |
|---|
| Description: | Title: Some users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics"
User impact: Users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics" attachment.
Current status: We’re continuing our analysis of the reproduction examples and associated service-side logs to isolate the source of the issue and determine appropriate remediation actions.
Scope of impact: This incident impacts using receiving Microsoft Teams meeting invitations who may see the invitation as a “not supported calendar message.ics" attachment. This information may be updated as our investigation continues.
Next update by: Wednesday, March 18, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Mar 17 20:22:30 2026 |
|---|
| Description: | Title: Some users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics"
User impact: Users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics" attachment.
Current status: Our analysis of the reproductions of impact provided by affected users has been inconclusive thus far in identifying the issue, although additional evaluation is needed of the reproduction examples and logs supplied. We're also determining what correlating service side logs may be needed to assist in this process.
Scope of impact: This incident impacts using receiving Microsoft Teams meeting invitations who may see the invitation as a “not supported calendar message.ics" attachment. This information may be updated as our investigation continues.
Next update by: Wednesday, March 18, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Mar 17 19:48:23 2026 |
|---|
| Description: | Title: Some users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics"
User impact: Users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics" attachment.
Current status: We're investigating the reproductions of impact from a subset of users to further our analysis of the potential root cause and to determine our next troubleshooting steps.
Scope of impact: This incident impacts using receiving Microsoft Teams meeting invitations who may see the invitation as a “not supported calendar message.ics" attachment. This information may be updated as our investigation continues.
Next update by: Wednesday, March 18, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Tue Mar 17 18:47:36 2026 |
|---|
| Description: | Title: Some users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics"
User impact: Users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics" attachment.
Current status: We're reviewing raised support cases for this impact scenario and working with a subset of users to collect reproductions of impact to further our analysis of the issue and to determine our next troubleshooting steps.
Scope of impact: This incident impacts using receiving Microsoft Teams meeting invitations who may see the invitation as a “not supported calendar message.ics" attachment. This information may be updated as our investigation continues.
Next update by: Wednesday, March 18, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Mar 17 18:33:30 2026 |
|---|
| Description: | Title: Some users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics"
User impact: Users may see Microsoft Teams meeting invitations are being received as “not supported calendar message.ics".
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.
|
|---|
|
EX1253275 - Some users may experience issues when accessing their Exchange Online mailbox via one or more connection method
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Mar 16 05:30:00 2026 |
|---|
| End Time: | Mon Mar 16 09:30:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Mar 18 14:30:48 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 18 14:30:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Mar 18 14:30:33 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Mar 16 12:34:21 2026 |
|---|
| Description: | Title: Some users may have experienced issues when accessing their Exchange Online mailbox via one or more connection method
User impact: Users may have experienced errors when accessing their mailbox via multiple Exchange Online connection methods.
More info: Users may have experienced errors or failures when attempting to access their mailbox. Impacted connection methods included, but were not limited to:
- Outlook on the web
- Outlook desktop
- Exchange ActiveSync
- Other Exchange Online connection protocols
Final status: We've confirmed that service has remained healthy for an extended period of time. Our monitoring indicates the issue is no longer occurring for the affected users.
Scope of impact: Impact was specific to some users attempting to access their mailbox via any of the connection methods detailed above.
Start time: Monday, March 16, 2026, at 9:30 AM UTC
End time: Monday, March 16, 2026, at 1:30 PM UTC
Preliminary root cause: An underlying issue involving the supporting network infrastructure resulted in a service availability degradation across the Exchange Online connection methods. We're continuing to investigate to determine the full root cause and will provide more information within the Post-Incident Report.
Next steps:
- We're continuing to examine the underlying circumstances that led to this behavior to understand the root cause.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Mar 16 11:28:20 2026 |
|---|
| Description: | Title: Some users may experience issues when accessing their Exchange Online mailbox via one or more connection method
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
More info: Users may experience errors or failures when attempting to access their mailbox. Impacted connection methods include but may not be limited to:
- Outlook on the web
- Outlook desktop
- Exchange ActiveSync
- Other Exchange Online connection protocols
Current status: While telemetry continues to show the issue is no longer occurring for affected users, we're continuing to monitor service health to assess whether any additional actions are required to ensure sustained recovery.
Scope of impact: Impact is specific to some users attempting to access their mailbox via any of the connection methods detailed above.
Next update by: Monday, March 16, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon Mar 16 10:45:19 2026 |
|---|
| Description: | We’re continuing to monitor service health to identify whether any additional actions are required to ensure longstanding recovery. Our telemetry continues to indicate the issue is no longer occurring for affected users.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Mon Mar 16 10:19:26 2026 |
|---|
| Description: | Title: Some users may experience issues when accessing their Exchange Online mailbox via one or more connection method
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
More info: Users may experience errors or failures when attempting to accessing their mailbox. Impacted connection methods include but may not be limited to:
- Outlook on the web
Current status: Internal reports and service monitoring telemetry indicate that the issue is no longer occurring for affected users. We’ll continue to monitor service health to ensure ongoing stability.
Scope of impact: Impact is specific to some users attempting to access their mailbox via any of the connection methods detailed above.
Next update by: Monday, March 16, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Mar 16 09:30:35 2026 |
|---|
| Description: | Title: Some users may experience issues when accessing their Exchange Online mailbox via one or more connection method
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
More info: Users may experience errors or failures when attempting to accessing their mailbox.
Impacted connection methods include but may not be limited to:
- Outlook on the web
Current status: We’ve identified a backend issue that’s preventing some services from responding as expected, resulting in mailbox access delays. We’re investigating this behavior across regions to better understand the impact and determine next steps. We’re seeing signs of service recovery and will share additional updates as our investigation continues.
Scope of impact: Impact is specific to some users attempting to access their mailbox via any of the connection methods detailed above.
Next update by: Monday, March 16, 2026, at 3:30 PM UTC
|
|---|
|
| Time: | Mon Mar 16 07:23:23 2026 |
|---|
| Description: | Title: Some users may experience issues when accessing their Exchange Online mailbox via one or more connection method
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
More info: Users may experience errors or failures when attempting to accessing their mailbox.
Impacted connection methods include but may not be limited to:
- Outlook on the web
Current status: We’re currently reviewing service telemetry data to help identify the root cause and next steps required to mitigate impact.
Scope of impact: Impact is specific to some users located in Europe attempting to access their mailbox via any of the connection methods detailed above.
Next update by: Monday, March 16, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Mar 16 06:56:55 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
PC1249454 - Microsoft Copilot Studio - Updates applied to agents that were published in Microsoft Teams are not rendering
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 17 19:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Power Platform) |
|---|
| Feature Group: | Microsoft Copilot Studio |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 18 13:54:12 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 18 13:54:12 2026 |
|---|
| Description: | Title: Microsoft Copilot Studio - Updates applied to agents that were published in Microsoft Teams are not rendering
User impact: Updates applied to agents that were published in Microsoft Teams are not rendering.
More Info: As a workaround, users can republish an affected agent and then re-add the agent in Microsoft Teams.
Current Status: The deployment of the fix is ongoing, and we are continuing to monitor service telemetry for signs of recovery. As the deployment progresses, impacted users should republish affected agents in Microsoft Teams.
Next Update: Tuesday, March 24, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Mar 12 14:46:40 2026 |
|---|
| Description: | Title: Microsoft Copilot Studio - Updates applied to agents that were published in Microsoft Teams are not rendering
User impact: Updates applied to agents that were published in Microsoft Teams are not rendering.
More Info: As a workaround, users can republish an affected agent and then re-add the agent in Microsoft Teams.
Current Status: The deployment of the fix is ongoing, and we are continuing to monitor service telemetry for signs of recovery. As the deployment progresses, impacted users should republish affected agents in Microsoft Teams.
Next Update: Wednesday, March 18, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Mar 11 21:12:40 2026 |
|---|
| Description: | Title: Microsoft Copilot Studio - Updates applied to agents that were published in Microsoft Teams are not rendering
User impact: Updates applied to agents that were published in Microsoft Teams are not rendering.
Current Status: Our investigation determined that impact occurred following a recent service update containing a code regression was deployed to the supporting infrastructure. We have deployed a fix to the impacted infrastructure and are monitoring telemetry for signs of recovery as it progresses.
Next Update: Thursday, March 12, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Mar 11 20:46:02 2026 |
|---|
| Description: | Title: Microsoft Copilot Studio - Updates applied to agents that were published in Microsoft Teams are not rendering
User impact: Updates applied to agents that were published in Microsoft Teams are not rendering.
Current Status: We are aware of an emerging issue where updated content applied to agents that were published in Microsoft Teams is not rendering. 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.
|
|---|
|
MO1243496 - Some admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and users can't access add-ins
| Status: | serviceDegradation |
|---|
| Start Time: | Wed Jan 21 05:27:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 18 12:29:04 2026 |
|---|
| Root Cause: | A recent service change designed to enforce stricter authentication requirements blocked admins from deploying custom add-ins from the Microsoft 365 admin center and blocked user authentication requests from completing. |
|---|
| Next Update: | Wednesday, March 18, 2026, at 10:00 PM UTC |
|---|
|
Details
| Time: | Wed Mar 18 12:29:04 2026 |
|---|
| Description: | Title: Some admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and users can't access add-ins
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and users can't access add-ins.
More info: Admins see an error stating “Learn more about eligibility requirements”.
Users also report being unable to access deployed add-ins in relevant services such as Exchange Online. Affected add-ins we've validated include, but may not be limited to, the following:
- My Templates add-in
- Salesforce add-ins
- Viva Insights add-ins
Current status: Following our completed internal tests with affected users, we've confirmed that our fix will be viable for remediating the impact. Our fix has completed approximately 25 percent of the necessary deployment, and since beginning, our internal service telemetry is reporting a reduction of internal add-in errors. As we monitor the remaining deployment, we'll provide an updated timeline for impact being remediated once it has become available.
Scope of impact: Some admins may be unable deploy custom add-ins from the Microsoft 365 admin center and all users may be unable to access deployed add-ins. This information may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent service change designed to enforce stricter authentication requirements blocked admins from deploying custom add-ins from the Microsoft 365 admin center and blocked user authentication requests from completing.
Next update by: Wednesday, March 18, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Mar 17 17:29:02 2026 |
|---|
| Description: | Title: Some admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and users can't access add-ins
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and users can't access add-ins.
More info: Admins see an error stating “Learn more about eligibility requirements”.
Users also report being unable to access deployed add-ins in relevant services such as Exchange Online. Affected add-ins we've validated include, but may not be limited to, the following:
- My Templates add-in
- Salesforce add-ins
- Viva Insights add-ins
Current status: We've merged communications discussing impact to deployment or access to custom add-ins into a single communication to provide more streamlined and consistent feedback on our mitigation actions. We've updated the "Title", "User impact", "Scope of impact","Start time", and "Root cause" fields of this communication to reflect this change. We've deployed a code fix designed to correct the offending code mismatch in our authentication infrastructure to a subset of our service infrastructure, and we're testing for remediation with a subset of affected users prior to initiating a wider deployment. We aim to provide a timeline to wider deployment at the time of our next scheduled update.
Scope of impact: Some admins may be unable deploy custom add-ins from the Microsoft 365 admin center and all users may be unable to access deployed add-ins. This information may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent service change designed to enforce stricter authentication requirements blocked admins from deploying custom add-ins from the Microsoft 365 admin center and blocked user authentication requests from completing.
Next update by: Friday, March 20, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Mar 11 02:14:39 2026 |
|---|
| Description: | Title: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and get an error.
More info: Admins may see an error stating “Learn more about eligibility requirements”.
Current status: The full deployment of our fix is expected to take an extended period of time, so we're shifting our efforts to focus on expediting the deployment process. We anticipate that we’ll be able to provide an updated remediation timeline, by our next scheduled update.
Scope of impact: Admins may be unable deploy custom add-ins from the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Wednesday, February 25, 2026, at 12:00 PM UTC
Root cause: A recent service change designed to enforce stricter authentication requirements blocked admins from deploying custom add-ins from the Microsoft 365 admin center.
Next update by: Tuesday, March 17, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Mar 10 18:20:38 2026 |
|---|
| Description: | Title: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and get an error.
More info: Admins may see an error stating “Learn more about eligibility requirements”.
Current status: The deployment of our fix is expected to take an extended period of time, so we're evaluating possible options to expedite the deployment.
Scope of impact: Admins may be unable deploy custom add-ins from the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Wednesday, February 25, 2026, at 12:00 PM UTC
Root cause: A recent service change designed to enforce stricter authentication requirements blocked admins from deploying custom add-ins from the Microsoft 365 admin center.
Next update by: Wednesday, March 11, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Mar 9 17:04:27 2026 |
|---|
| Description: | Title: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and get an error.
More info: Admins may see an error stating “Learn more about eligibility requirements”.
Current status: We've correlated the increase in 401 authentication errors to a recent service change designed to enforce stricter authentication requirements, which blocked admins from deploying custom add-ins from the Microsoft 365 admin center. We're deploying a fix that'll unblock the authentication and remediate the impact.
Scope of impact: Admins may be unable deploy custom add-ins from the Microsoft 365 admin center. This information may be updated as our investigation continues.
Start time: Wednesday, February 25, 2026, at 12:00 PM UTC
Root cause: A recent service change designed to enforce stricter authentication requirements blocked admins from deploying custom add-ins from the Microsoft 365 admin center.
Next update by: Tuesday, March 10, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Thu Mar 5 17:38:34 2026 |
|---|
| Description: | Title: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and get an error.
More info: Admins may see an error stating “Learn more about eligibility requirements”.
Current status: We're continuing our analysis of the increase in 401 errors that may be contributing to impact as a part of our active investigation into the underlying root cause of this event.
Scope of impact: Admins may be unable deploy custom add-ins from the Microsoft 365 admin center. This information may be updated as our investigation continues.
Next update by: Monday, March 9, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Mar 4 16:59:42 2026 |
|---|
| Description: | Title: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and get an error.
More info: Admins may see an error stating “Learn more about eligibility requirements”.
Current status: We've identified an increase in 401 errors that may be contributing to impact, and we're further analyzing the errors to isolate a potential root cause and determine how to best remediate impact.
Scope of impact: Admins may be unable deploy custom add-ins from the Microsoft 365 admin center. This information may be updated as our investigation continues.
Next update by: Thursday, March 5, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Mar 3 20:38:19 2026 |
|---|
| Description: | Title: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and get an error.
More info: Admins may see an error stating “Learn more about eligibility requirements”.
Current status: We're continuing our analysis of the most recently-collected service logs and data to gain insight into the underlying exceptions contributing to impact and determine our options for remediation.
Scope of impact: Admins may be unable deploy custom add-ins from the Microsoft 365 admin center. This information may be updated as our investigation continues.
Next update by: Wednesday, March 4, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Mar 3 16:37:30 2026 |
|---|
| Description: | Title: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and get an error.
More info: Admins may see an error stating “Learn more about eligibility requirements”.
Current status: While our review of any recent changes made to the service is ongoing, we're preparing to test some potential mitigative actions with a subset of users to see if they help recover the scenario.
Scope of impact: Admins may be unable deploy custom add-ins from the Microsoft 365 admin center. This information may be updated as our investigation continues.
Next update by: Wednesday, March 4, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Tue Mar 3 16:23:25 2026 |
|---|
| Description: | Title: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center
User impact: Admins may be unable to deploy custom add-ins from the Microsoft 365 admin center and get an error.
More info: Admins may see an error stating “Learn more about eligibility requirements”.
Current status: This is a continuation of EX1243054. We're reviewing any recent changes made to the service that may have introduced this issue to further our understanding of the underlying cause of the problem and formulate a remediation plan.
Scope of impact: Admins may be unable deploy custom add-ins from the Microsoft 365 admin center. This information may be updated as our investigation continues.
Next update by: Tuesday, March 3, 2026, at 11:00 PM UTC
|
|---|
|
MO1255228 - Some users in the United States may be intermittently unable to access some Microsoft 365 services
| Status: | serviceRestored |
|---|
| Start Time: | Wed Mar 18 10:00:00 2026 |
|---|
| End Time: | Wed Mar 18 11:08:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Mar 18 12:28:59 2026 |
|---|
| Root Cause: | A portion of networking infrastructure, slated for reinstatement to active service, had been only partially reinstated, which led to load balancing issues when handling service traffic. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 18 12:28:59 2026 |
|---|
| Description: | Title: Some users in the United States may be intermittently unable to access some Microsoft 365 services
User impact: Users in the United States may have been intermittently unable to access some Microsoft 365 services.
More info: The following services may have been impacted:
- Exchange Online
- Microsoft Teams
Final status: We've confirmed that the service remains healthy after manually reinstating the entire network infrastructure that was slated for active service load and impact is remediated.
Scope of impact: Some users in the United States may have been intermittently unable to access some Microsoft 365 services.
Start time: Wednesday, March 18, 2026, at 2:00 PM UTC
End time: Wednesday, March 18, 2026, at 3:08 PM UTC
Root cause: A portion of networking infrastructure, slated for reinstatement to active service, had been only partially reinstated, which led to load balancing issues when handling service traffic.
Next steps:
- We're continuing our investigation into the partial reinstatement to better understand why this has occurred so we can determine how we can best avoid similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Mar 18 12:10:04 2026 |
|---|
| Description: | Title: Some users in the United States may be intermittently unable to access some Microsoft 365 services
User impact: Users in the United States may be intermittently unable to access some Microsoft 365 services.
More info: The following services may be impacted:
- Exchange Online
- Microsoft Teams
Current status: Our investigation has confirmed that a portion of our networking infrastructure that was recently removed from active service had only reinstated a subset of that removed infrastructure to active service, which led to a load balancing issue when rerouting service traffic. We've manually reinstated the entirety of the networking infrastructure slated for service load, and we're seeing positive trends on the service health. We're monitoring the service telemetry to ensure service recovers back to expected levels.
Scope of impact: Some users in the United States may be intermittently unable to access some Microsoft 365 services.
Next update by: Wednesday, March 18, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Wed Mar 18 11:32:26 2026 |
|---|
| Description: | Title: Investigating user reports of issues with Microsoft 365 products
User impact: We don't have details on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.
|
|---|
|
MO1254319 - Some users may have been unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
| Status: | serviceRestored |
|---|
| Start Time: | Tue Mar 17 07:42:00 2026 |
|---|
| End Time: | Tue Mar 17 12:05:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Mar 18 10:34:34 2026 |
|---|
| Root Cause: | The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page was receiving a high volume of traffic that inhibited the rate at which some users' requests were being processed, preventing some users from accessing the service pages. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 18 10:13:25 2026 |
|---|
| Description: | Title: Some users may have been unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may have been unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: Users could've accessed Microsoft Copilot through application-based Microsoft Copilot services. This included, but wasn't limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
As a workaround, users may have been able to leverage https://m365.cloud.microsoft/search to sign in using this page. Once signed in, users could've accessed Office.com.
Final status: We've concluded our extended period of monitoring and confirmed impact has not reoccurred.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Tuesday, March 17, 2026, at 11:42 AM UTC
End time: Tuesday, March 17, 2026, at 4:05 PM UTC
Root cause: The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page was receiving a high volume of traffic that inhibited the rate at which some users' requests were being processed, preventing some users from accessing the service pages.
Next steps:
- We're reviewing performance data and trends on the affected infrastructure to help prevent similar impact from happening again.
- We're monitoring service telemetry to ensure impact does not reoccur.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 17 20:31:17 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impact to Office.com is still occurring, but the impact to Microsoft 365 Copilot web clients, office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft, have recovered as of March 17, 2026, at 4:05 PM UTC.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes, but is not limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access Office.com.
Current status: While our telemetry indicates that the impact is largely remediated, we’re continuing to monitor the environment as our traffic optimizations are nearing completion. We're proceeding with the monitoring process to ensure the service is stable and to determine whether any additional mitigative steps may be necessary to fully resolve this issue.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Tuesday, March 17, 2026, at 11:42 AM UTC
Root cause: The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page is receiving a high volume of traffic that inhibits the rate at which some users' requests are being processed, preventing some users from accessing the service pages.
Next update by: Wednesday, March 18, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Tue Mar 17 18:11:24 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impact to Office.com is still occurring, but the impact to Microsoft 365 Copilot web clients, office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft, have recovered as of March 17, 2026, at 4:05 PM UTC.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes, but is not limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access Office.com.
Current status: We're continuing to monitor our service health telemetry to ensure that all users regain access to Office.com as our configuration changes are applied to the remaining affected environment.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Tuesday, March 17, 2026, at 11:42 AM UTC
Root cause: The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page is receiving a high volume of traffic that inhibits the rate at which some users' requests are being processed, preventing some users from accessing the service pages.
Next update by: Wednesday, March 18, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Mar 17 16:26:15 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impact to Office.com is still occurring, but the impact to Microsoft 365 Copilot web clients, office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft, have recovered as of March 17, 2026, at 4:05 PM UTC.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes, but is not limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access office.com.
Current status: Our service health telemetry continues to suggest that our configuration changes are restoring access to Office.com. We're gradually applying our changes to further balance the request traffic and remediate the impact for all users.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Tuesday, March 17, 2026, at 11:42 AM UTC
Root cause: The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page is receiving a high volume of traffic that inhibits the rate at which some users' requests are being processed, preventing some users from accessing the service pages.
Next update by: Tuesday, March 17, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Mar 17 14:20:44 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impact to office.com is still occurring, but the impact to Microsoft 365 Copilot web clients, office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft, have recovered as of March 17, 2026, at 4:05 PM UTC.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes, but is not limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access office.com.
Current status: Currently, the affected web client, office.com is still impacted. After applying configuration changes and rebalancing the request traffic, the previously impacted Microsoft 365 Copilot web-clients, office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft, have recovered as of Tuesday, March 17, 2026, at 4:05 PM UTC. We've identified additional configuration changes and are proceeding to roll these out to the affected infrastructure.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Tuesday, March 17, 2026, at 11:42 AM UTC
Root cause: The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page is receiving a high volume of traffic that inhibits the rate at which some users' requests are being processed, preventing some users from accessing the service pages.
Next update by: Tuesday, March 17, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Mar 17 13:58:32 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes, but is not limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access the impacted web-based office.com and Copilot clients.
Current status: We've applied our configuration changes and service health telemetry indicates some improvement; however, some users may still be unable to access Office.com. We're continuing to review the flow of request traffic to determine whether additional remediation actions are required.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Tuesday, March 17, 2026, at 11:42 AM UTC
Root cause: The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page is receiving a high volume of traffic that inhibits the rate at which some users' requests are being processed, preventing some users from accessing the service pages.
Next update by: Tuesday, March 17, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Mar 17 11:55:09 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes, but is not limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access the impacted web-based office.com and Copilot clients.
Current status: We're continuing to apply configuration changes and rebalance the request traffic while monitoring service health telemetry to ensure the services recover.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Tuesday, March 17, 2026, at 11:42 AM UTC
Root cause: The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page is receiving a high volume of traffic that inhibits the rate at which some users' requests are being processed, preventing some users from accessing the service pages.
Next update by: Tuesday, March 17, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Mar 17 10:12:32 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes, but is not limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access the impacted web-based office.com and Copilot clients.
Current status: We've identified that impact associated with MO1253428 has started to reoccur. We're reviewing traffic pattern telemetry and applying configuration changes to optimize connections and remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Tuesday, March 17, 2026, at 4:00 PM UTC
|
|---|
|
EX1213792 - Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or 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: | Wed Mar 18 07:39:09 2026 |
|---|
| Root Cause: | A timing issue during a recent migration is causing backend systems to act before directory changes are fully synchronized. |
|---|
| Next Update: | Thursday, April 2, 2026, at 10:30 AM UTC |
|---|
|
Details
| Time: | Wed Mar 18 07:39:09 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center
User impact: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center.
Current status: We’re continuing to monitor the fix as it deploys across the impacted environments. We anticipate that the deployment should complete by Thursday, April 2, 2026. Once deployment has completed, the fix will be enabled to restore functionality.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from Distribution Lists to Unified Groups using PowerShell or the Exchange admin center. This section may be updated as our investigation continues.
Start time: Friday, October 24, 2025, at 11:32 AM UTC
Estimated time to resolve: Thursday, April 2, 2026
Root cause: A timing issue during a recent migration is causing backend systems to act before directory changes are fully synchronized.
Next update by: Thursday, April 2, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Mar 17 07:54:38 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center
User impact: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center.
Current status: We've determined that a timing issue during a recent migration is causing backend systems to act before directory changes are fully synchronized. This is leading to failures during group configuration, preventing the Distribution List from successfully upgrading to a Unified Group. We're monitoring the deployment fix as it saturates across all impacted environments, which is taking longer than anticipated due to additional validation steps.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from Distribution Lists to Unified Groups using PowerShell or the Exchange admin center. This section may be updated as our investigation continues.
Start time: Friday, October 24, 2025, at 11:32 AM UTC
Root cause: A timing issue during a recent migration is causing backend systems to act before directory changes are fully synchronized.
Next update by: Wednesday, March 18, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Mon Mar 16 07:56:10 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center
User impact: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center.
Current status: We're proceeding with our deployment of the fix across all impacted environments and expect completion by Tuesday, March 17, 2026.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from Distribution Lists to Unified Groups using PowerShell or the Exchange admin center. This section may be updated as our investigation continues.
Estimated time to resolve: Tuesday, March 17, 2026
Next update by: Tuesday, March 17, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Mar 12 07:06:18 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center
User impact: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center.
Current status: We're continuing to deploy the fix across all impacted environments and expect completion by Monday, March 16, 2026.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from Distribution Lists to Unified Groups using PowerShell or the Exchange admin center. This section may be updated as our investigation continues.
Estimated time to resolve: Monday, March 16, 2026
Next update by: Monday, March 16, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Mar 2 07:39:18 2026 |
|---|
| Description: | Title: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center
User impact: Admins can’t upgrade groups from Distributions Lists to Unified Groups using PowerShell or the Exchange admin center.
Current status: We’ve developed a new fix and validated that it works in our testing environment. We’re currently deploying the fix across all impacted environments. Deployment is expected to complete by Monday, March 16, 2026. We’ll continue to monitor deployment progress and share updates accordingly.
Scope of impact: Impact is specific to some admins attempting to upgrade groups from Distribution Lists to Unified Groups using PowerShell or the Exchange admin center. This section may be updated as our investigation continues.
Estimated time to resolve: Monday, March 16, 2026
Next update by: Thursday, March 12, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Fri Feb 27 06:30:10 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 our previous fix did not successfully mitigate impact in the testing environment. We’ve now implemented an alternative fix in the test environment and will share an update on its effectiveness in our next scheduled communication.
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, March 2, 2026, at 1:00 PM UTC
|
|---|
|
| 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 1:00 PM 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.
|
|---|
|
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: | Wed Mar 18 05:48:25 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, March 20, 2026, at 11:00 AM UTC |
|---|
|
Details
| Time: | Wed Mar 18 05:48:25 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: We’re progressing with our review of alternate approaches to determine whether any active groups remain impacted and to confirm whether additional processing is needed.
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, March 20, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Mar 17 08:41:43 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: We’re continuing to review alternative approaches to determine whether any active groups remain impacted and to confirm whether additional processing is needed.
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: Wednesday, March 18, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Mar 17 06:45:58 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: We’ve run the aforementioned script, but it didn't complete successfully due to the large volume of groups. We’re reviewing alternative approaches to validate whether any active groups remain impacted and to confirm whether additional processing is required.
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: Tuesday, March 17, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Tue Mar 10 04:21: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=ex…
https://learn.microsoft.com/en-us/powershell/microsoftgraph/authentication-commands?view=graph-powe…
Current status: We’re developing a script to verify that no residual groups remain impacted. We're expecting that the script development will be complete by Tuesday, March 17, 2026. Once finalized, we’ll run the script to confirm that no additional groups are affected.
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: Tuesday, March 17, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Thu Mar 5 03:21:29 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: We’re reviewing service telemetry to determine whether any groups are still pending processing. At this stage, we're suspecting that all groups will have been processed. However, we’ll provide confirmation if there are any remaining groups by 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. 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: Tuesday, March 10, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 03:11:58 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: We’ve experienced minor delays processing a small number of remaining groups. However, most groups have been completed, and the majority of users should no longer be impacted. We’ll provide a completion timeline once available.
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: Thursday, March 5, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Tue Feb 24 04:28:07 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: We’re in the final stages of deploying the fix and expect completion by the next scheduled update. We’ve also confirmed with affected users that the majority of groups are now resolved.
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: Tuesday, March 3, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Feb 23 04:30:04 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: While we continue deploying the fix and exploring ways to accelerate rollout, we’ve identified that the fix has not yet resolved impact for some groups. We’re engaging with affected users to confirm which groups remain impacted.
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: Tuesday, February 24, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Fri Feb 20 05:20:02 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: We’re continuing to evaluate options to accelerate analysis of the timeout issues so we can efficiently resume the deployment.
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: Monday, February 23, 2026, at 12:30 PM UTC
|
|---|
|
| 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
|
|---|
|
MO1253767 - Admins' Microsoft 365 admin center usage report data may be delayed
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Mar 12 20:00:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 18 01:52:21 2026 |
|---|
| Root Cause: | An upstream data source pipeline issue is causing delays in usage report data availability, and this is resulting in impact. |
|---|
| Next Update: | Thursday, March 19, 2026, at 1:00 AM UTC |
|---|
|
Details
| Time: | Tue Mar 17 20:25:09 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, admins attempting to view usage report data for any Microsoft 365 service in the Microsoft 365 admin center, including Copilot and Microsoft Teams, may see delays.
Current status: We’re implementing a fix to address the upstream data source pipeline issue, which we anticipate we’ll be able to provide a timeline for resolution by our next scheduled communications update. As our fix propagates throughout the affected regions the backlog for some of the affected usage report data has been processed and admins may see impact alleviate during this process. Additionally, as our fix completely saturates the subsequent remaining regions, the remaining backlog will be fully processed.
Scope of impact: Admins attempting to view usage report data in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Friday, March 13, 2026, at 12:00 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in usage report data availability, and this is resulting in impact.
Next update by: Thursday, March 19, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Mar 16 20:06:45 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 admin center usage report data may be delayed
User impact: Admins' Microsoft 365 admin center usage report data may be delayed.
More info: Specifically, admins attempting to view usage report data for any Microsoft 365 service in the Microsoft 365 admin center, including Copilot and Microsoft Teams, may see delays.
Current status: We've identified this impact through internal monitoring and have determined that an issue with an upstream data source pipeline is causing delays in usage report data availability. We're analyzing the impact further to validate the best next steps in our efforts to alleviate this issue.
Scope of impact: Admins attempting to view usage report data in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Friday, March 13, 2026, at 12:00 AM UTC
Root cause: An upstream data source pipeline issue is causing delays in usage report data availability, and this is resulting in impact.
Next update by: Wednesday, March 18, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Mon Mar 16 18:55:12 2026 |
|---|
| Description: | Title: Admins' Microsoft 365 admin center report data availability may be delayed
User impact: Admins' Microsoft 365 admin center report data availability may be delayed.
Current status: We're investigating a potential issue with Microsoft 365 admin center and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
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 Mar 17 20:48:49 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, April 1, 2026, at 2:00 AM UTC |
|---|
|
Details
| Time: | Tue Mar 17 20:48: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 way to circumvent impact, 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 continuing to monitor the deployment of the fix, which we expect will be fully rolled out and the issue remediated by our next scheduled update.
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, April 1, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 19:50:47 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're continuing to monitor the ongoing rollout of our fix; however, due to unexpected blockers in the affected environment we anticipate the full deployment should complete by the end of March 2026. This estimate may change due to the unpredictability of the aforementioned blockers, and we’ll provide a more accurate estimation for the deployment when possible.
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, March 18, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Feb 17 19:32:15 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 resolved the delays affecting our rollout of our fix for this issue and have begun deploying it throughout the remaining affected environment. We're continuing to anticipate the full deployment should complete by early March 2026, and aim to finalize our timeline for its completion by our next scheduled update.
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, March 4, 2026, at 2:00 AM UTC
|
|---|
|
| 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
|
|---|
|
TM1253477 - Some users may be unable to utilize spell check in Microsoft Teams desktop client
| Status: | serviceRestored |
|---|
| Start Time: | Tue Mar 10 11:48:00 2026 |
|---|
| End Time: | Mon Mar 16 18:28:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 17 18:44:17 2026 |
|---|
| Root Cause: | A recent code deployment intended for general service optimizations contained a code issue that resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 17 18:44:17 2026 |
|---|
| Description: | Title: Some users may be unable to utilize spell check in Microsoft Teams desktop client
User impact: Users may have been unable to utilize spell check in Microsoft Teams desktop client.
Final status: We've reverted the offending code change and confirmed with affected users that impact is remediated after they restarted their Microsoft Teams desktop client. This confirms that the offending change intended for general service optimizations contained a code issue that resulted in impact.
Scope of impact: This issue may have affected some users utilizing the Microsoft Teams desktop client on Windows devices.
Start time: Tuesday, March 10, 2026, at 3:48 PM UTC
End time: Monday, March 16, 2026, at 10:28 PM UTC
Root cause: A recent code deployment intended for general service optimizations contained a code issue that resulted in impact.
Next steps:
- We're reviewing our code update validation process to detect and prevent similar issues before they cause future impact.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 16 19:47:19 2026 |
|---|
| Description: | Title: Some users may be unable to utilize spell check in Microsoft Teams desktop client
User impact: Users may be unable to utilize spell check in Microsoft Teams desktop client.
Current status: We've identified a recent deployment intended for general service optimizations may contain a code issue that's resulting in impact. We've reverted the suspected offending change and recommend impacted users to restart their Microsoft Teams desktop client to immediately experience relief. Alternatively, users can wait approximately 24 hours for the effects of reverting the change to automatically reflect. Additionally, we're reaching out to some users who initially reported the issue to validate that our remediation efforts were successful, which will help us confirm our root cause theory. If impact persists, we're requesting fresh logs from actively reproducing the issue so we can resume the root cause investigation.
Scope of impact: This issue may affect some users utilizing the Microsoft Teams desktop client on Windows devices. This information may be updated as our investigation continues.
Start time: Tuesday, March 10, 2026, at 3:48 PM UTC
Next update by: Wednesday, March 18, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Mar 16 14:56:47 2026 |
|---|
| Description: | Title: Some users may be unable to utilize spell check in Microsoft Teams desktop client
User impact: Users may be unable to utilize spell check in Microsoft Teams desktop client.
Current status: Our analysis of the provided Microsoft Teams desktop client logs in parallel with our review of our service health telemetry indicates that errors are occurring in the code path responsible for facilitating spell check, although the overall error count is low. We're investigating these errors further to assist in determining the source of the impact to formulate our next steps.
Scope of impact: This issue may affect some users utilizing the Microsoft Teams desktop client on Windows devices.
Next update by: Tuesday, March 17, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Mar 16 12:56:15 2026 |
|---|
| Description: | Title: Some users may be unable to utilize spell check in Microsoft Teams desktop client
User impact: Users may be unable to utilize spell check in Microsoft Teams desktop client.
Current status: We're reviewing Microsoft Teams desktop client logs collected from a subset of users experiencing impact to identify and isolate any errors potentially contributing to impact for further investigation.
Scope of impact: This issue may affect some users utilizing the Microsoft Teams desktop client on Windows devices.
Next update by: Monday, March 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Mar 16 12:41:46 2026 |
|---|
| Description: | Title: Some users may be unable to utilize spell check in Microsoft Teams desktop client
User impact: Users may be unable to utilize spell check in Microsoft Teams desktop client.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1248186 - Microsoft Teams audio and video quality issues
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Tue Mar 10 09:30:00 2026 |
|---|
| End Time: | Tue Mar 10 11:10:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Mar 17 18:31:05 2026 |
|---|
| Root Cause: | A portion of networking infrastructure was not handling traffic as expected, resulting in networking congestion on the remining infrastructure when the peak of calling/meetings occur at the start of the hour and half-past the hour. More details are provided within the PIR. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 17 18:31:05 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Mar 12 14:46:57 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Mar 10 11:40:54 2026 |
|---|
| Description: | Title: Microsoft Teams audio and video quality issues
User impact: Users may have experienced poor audio and video quality when using Microsoft Teams.
Final status: We've monitored the service following our corrective action and through the next anticipated uptick in traffic and confirmed that the issue is remediated.
Scope of impact: The issue was specific to the North America region, and the impact occurred primarily during the period of time at the start of the hour and half-past the hour.
Start time: Tuesday, March 10, 2026, at 1:30 PM UTC
End time: Tuesday, March 10, 2026, at 3:10 PM UTC
Root Cause: A portion of networking infrastructure was not handling traffic as expected, resulting in networking congestion on the remining infrastructure when the peak of calling/meetings occur at the start of the hour and half-past the hour. More details are provided within the PIR.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue Mar 10 11:23:46 2026 |
|---|
| Description: | We've identified that a portion of network infrastructure was not handling traffic as expected, resulting in congestion on the remaining infrastructure during the period when the peak of calling/meetings occurs at the start of the hour and half-past the hour. We've taken action to correct the issue and are monitoring the service to confirm recovery.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Mar 10 11:09:02 2026 |
|---|
| Description: | We've identified packet loss from networking diagnostics. The focus of the investigation is on networking routing infrastructure between data centers in the North America region.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Mar 10 10:37:03 2026 |
|---|
| Description: | Title: Microsoft Teams audio and video quality issues
User impact: Users may experience poor audio and video quality when using Microsoft Teams.
Current status: We've received multiple reports of impact and monitoring alerts have triggered. We're reviewing relevant telemetry systems and error logs to determine the cause of the issue.
Scope of impact: Reports of impact have been from the North American region. We'll update this field once the full scope is identified.
Next update by: Tuesday, March 10, 2026, at 4:00 PM UTC
|
|---|
|
| Time: | Tue Mar 10 10:26:45 2026 |
|---|
| Description: | We're receiving reports of Microsoft Teams audio quality issues. We're reviewing related telemetry and monitoring systems to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Tue Mar 10 10:17:06 2026 |
|---|
| Description: | Title: Investigating user reports of Microsoft Teams issues
User impact: Users may be unable to access Microsoft Teams or some of its features.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.
This communication serves as a preliminary notification about a potential issue affecting your service.
|
|---|
|
EX1238375 - Some users may be unable to access the My Templates add-in in Exchange Online
| Status: | falsePositive |
|---|
| Start Time: | Wed Jan 21 05:27:00 2026 |
|---|
| End Time: | Tue Mar 17 17:36:26 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 17 17:38:00 2026 |
|---|
| Root Cause: | A recent authentication change intended to improve the My Templates and Viva Insights add-in functionality is causing access issues. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 17 17:36:46 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Final status: We've determined that this issue is a duplicate of another event. Please look for further updates in MO1243496. This communication will expire in 72 hours.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 16 16:20:27 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We've received additional reports from affected users that the My Templates add-in is accessible, and we're continuing our monitoring for an extended period to ensure no additional actions are needed to fully remediate the impact.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates and Viva Insights add-in functionality is causing access issues.
Next update by: Friday, March 20, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Thu Mar 12 15:30:55 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We've observed some recovery in service health and received reports that a subset of affected users are able to access the My Templates add-in. We're monitoring this recovery as we continue to test and validate additional fixes to help resolve this for all affected users. We'll provide a timeline for full remediation as soon as one becomes available.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates and Viva Insights add-in functionality is causing access issues.
Next update by: Monday, March 16, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Mar 11 15:20:11 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We're continuing to deploy the fix to a subset of service infrastructure to test for impact remediation prior to initiating further deployment. Once available, we'll provide a resolution timeline.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates and Viva Insights add-in functionality is causing access issues.
Next update by: Thursday, March 12, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Mar 10 15:20:17 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We've expanded communications to all potentially affected users and have updated the "Title", "User impact", "More info" and "Scope of impact" to reflect this change. After completing an analysis of HAR logs, we've isolated a potential code mismatch in the recent authentication change which needs to be corrected to remediate impact. We've created a code change and are deploying it to a subset of service infrastructure to test for impact remediation prior to initiating further deployment.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates and Viva Insights add-in functionality is causing access issues.
Next update by: Wednesday, March 11, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Mar 9 14:33:07 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We've been unable to identify an alternate solution to correct this issue but we're reviewing HTTP Archive format (HAR) logs to gain a better understand the failures that occur when the My Template and Viva Insights add-ins aren't provided.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates and Viva Insights add-in functionality is causing access issues.
Next update by: Tuesday, March 10, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Mar 9 12:59:09 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: It's taking longer than expected but our validation of an appropriate alternative solution to resolving this issue is ongoing.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates add-in functionality is causing access issues.
Next update by: Monday, March 9, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Mar 6 16:08:40 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We're continuing tests to validate an appropriate alternative solution and once available we'll provide a resolution timeline.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates add-in functionality is causing access issues.
Next update by: Monday, March 9, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Mar 5 16:36:38 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: Our tests for an initial fix using our internal testing environment didn't prove effective, but we've identified and are confirming the efficacy of another fix that may resolve this issue. We'll provide details and a deployment timeline for this potential fix if it proves to effectively remediate impact.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates add-in functionality is causing access issues.
Next update by: Friday, March 6, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Wed Mar 4 15:48:22 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: Our investigation in the internal testing environments is ongoing. This data will aid us in our efforts to pinpoint the next steps in our plan to remediate this issue.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates add-in functionality is causing access issues.
Next update by: Thursday, March 5, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Mar 3 17:53:46 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We’ve confirmed that the reversion of the change didn't remediate the impact. We’re further assessing the underlying cause to support our evaluation of potential alternative remediation approaches. Once validated, we’ll provide a resolution timeline.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates add-in functionality caused access issues.
Next update by: Wednesday, March 4, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Mar 2 20:45:37 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We confirmed that a recent change to switch to using the Representational State Transfer (REST) authentication for the My Templates add-in in Exchange Online caused access issues. We reverted the change to move back to utilizing the previous authentication method and can see in the telemetry that the access errors have dropped. We're reaching out to your representatives to confirm that the impact is remediated.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Start time: Wednesday, January 21, 2026, at 10:27 AM UTC
Root cause: A recent authentication change intended to improve the My Templates add-in functionality caused access issues.
Next update by: Wednesday, March 4, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Mon Mar 2 16:10:18 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: While attempting to refresh cache for affected users and in our efforts to remediate the impact, we've determined that a cache refresh won't return access to the My Templates add-in in Exchange Online as previously expected. We've isolated two recent changes to the service that we believe may be associated with the My Templates problems, the first to our Representational State Transfer (REST) connection method, and the second to the My Templates add-in. We're expecting our analysis of these changes will help us isolate the source for this event and determine our next steps for remediating the impact.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, March 3, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 18:05:42 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: From our analysis of the involved code, we suspect that a caching issue may be contributing to impact. We're working to refresh the caches of affected users as a potential remediation action, and we'll conduct tests with a subset of those users once the refresh has completed to confirm if the scenario has recovered.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Feb 26 21:22:44 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: Our analysis of the surface-level request flow and service logs for the scenario has been inconclusive. We're moving ahead with further in-depth analysis of the involved code to isolate the source of impact and determine our next steps.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Next update by: Saturday, February 28, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Thu Feb 26 16:48:44 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We're beginning to narrow down the source of the impact, and our initial understanding suggests that the add-in data is not being returned in the request flow. We're continuing to troubleshoot to further isolate the root cause.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Next update by: Friday, February 27, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 17:19:52 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: Our analysis into the underlying code identified a previous mitigation that was utilized for returning the missing My Templates add-in in Exchange Online for a similar impact scenario; however, our internal testing validated that it wouldn't be viable for returning the add-in in this situation. We're progressing with our root cause analysis and are analyzing Exchange Online logging and additional portions of the underlying code to determine our next troubleshooting steps for remediating the impact.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Next update by: Thursday, February 26, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Feb 24 22:26:43 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We’ve reproduced the issue internally and can see in the logs that the subscription My Templates exists on the mailbox, but isn’t showing as expected. We're reviewing the underlying code to better understand the origin of this behavior and to identify a path to remediation.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Tue Feb 24 19:42:46 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We're continuing our efforts to reproduce impact internally, in parallel with our review of the provided HAR logs, to help uncover the underlying root cause of impact and inform our next steps.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Tue Feb 24 18:02:28 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We're reviewing the HAR logs provided by a subset of affected users in conjunction with our own reproduction attempts to identify any initial root cause.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Feb 24 17:22:22 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
More info: Users may be unable to access the My Templates and Viva Insights add-ins as they're missing from the Outlook desktop client, Outlook mobile, and Outlook on the web.
Current status: We're reviewing the impact scenario descriptions provided by a subset of affected users, as well as logs they've provided, to better understand this impacting event.
Scope of impact: This event may affect some users attempting to access the My Templates and Viva Insights add-ins through the Outlook desktop client, Outlook mobile, and Outlook on the web. This section may be updated as our investigation continues.
Next update by: Tuesday, February 24, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Feb 24 16:44:19 2026 |
|---|
| Description: | Title: Some users may be unable to access the My Templates add-in in Exchange Online
User impact: Users may be unable to access the My Templates add-in in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1249121 - Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Mar 10 17:08:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 17 15:21:12 2026 |
|---|
| Root Cause: | An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing is preventing users from receiving email notifications. |
|---|
| Next Update: | Wednesday, March 25, 2026, at 9:00 PM UTC |
|---|
|
Details
| Time: | Tue Mar 17 15:21:12 2026 |
|---|
| Description: | Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts
User impact: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts.
Current status: We're continuing to develop and validate our fix aimed at restoring functionality and expect it will be ready for deployment by Saturday, March 28, 2026. We'll provide a timeline for the fix saturation and impact remediation as one becomes available.
Scope of impact: Any user that should receive an email notification for shared Power BI reports and dashboards or Microsoft Fabric artifacts may be impacted.
Start time: Tuesday, March 10, 2026, at 9:08 PM UTC
Root cause: An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing is preventing users from receiving email notifications.
Next update by: Wednesday, March 25, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Fri Mar 13 14:46:51 2026 |
|---|
| Description: | Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts
User impact: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts.
Current status: We're continuing development of the fix to restore functionality and once available, we'll provide a timeline for deployment.
Scope of impact: Any user that should receive an email notification for shared Power BI reports and dashboards or Microsoft Fabric artifacts may be impacted.
Start time: Tuesday, March 10, 2026, at 9:08 PM UTC
Root cause: An unexpected issue with Power BI reports and dashboards and Microsoft Fabric artifact sharing is preventing users from receiving email notifications.
Next update by: Tuesday, March 17, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Wed Mar 11 14:27:22 2026 |
|---|
| Description: | Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts
User impact: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts.
Current status: We've identified an unexpected issue with Power BI report and dashboard and Microsoft Fabric artifact sharing that’s preventing delivery of email notifications reporting the shared item to users. We're working on a fix to restore the functionality and will provide a timeline for the completion of the fix as one becomes available.
Scope of impact: Any user that should receive an email notification for shared Power BI reports and dashboards or Microsoft Fabric artifacts may be impacted.
Start time: Tuesday, March 10, 2026, at 9:08 PM UTC
Root cause: An unexpected issue with Power BI report and dashboard and Microsoft Fabric artifact sharing that is preventing users from receiving email notifications.
Next update by: Friday, March 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Mar 11 14:17:17 2026 |
|---|
| Description: | Title: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifactss
User impact: Users may not get email notifications for shared Power BI reports and dashboards or Microsoft Fabric artifacts.
Current status: We're investigating a potential issue with Power BI and Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1245624 - Some users in the North American region may have been unable to access multiple Microsoft 365 services
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Fri Mar 6 08:08:00 2026 |
|---|
| End Time: | Fri Mar 6 11:50:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Mar 17 12:10:34 2026 |
|---|
| Root Cause: | Throughout the incident, Microsoft-managed infrastructure remained healthy and was performing as expected.
A third-party DNS Security provider incorrectly blocked a domain that is used within the Content Delivery Network (CDN) by multiple Microsoft 365 services. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 10 13:02:51 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Mar 6 13:14:34 2026 |
|---|
| Description: | Title: Some users in the North American region may have been unable to access multiple Microsoft 365 services
User impact: Users in the North American region may have been unable to access multiple Microsoft 365 services.
More info: Impacted services included, but were not limited to:
- Microsoft 365 admin center
- SharePoint Online
- Microsoft Teams
Final status: We've received additional reports that the issue has recovered, and telemetry that monitors CDN interactions has shown there is no longer impact. We've confirmed that a CDN endpoint became unavailable for a period of time and the cause of this is still under investigation. We’re continuing to examine the underlying circumstances that led to this behavior to enhance the resiliency of our services.
Scope of impact: Impact was specific to some users located in the North American region attempting to access the Microsoft 365 admin center, Microsoft Teams and SharePoint Online.
Start time: Friday, March 6, 2026, at 1:08 PM UTC
End time: Friday, March 6, 2026, at 4:50 PM UTC
Root Cause: Throughout the incident, Microsoft-managed infrastructure remained healthy and was performing as expected.
A third-party DNS Security provider incorrectly blocked a domain that is used within the Content Delivery Network (CDN) by multiple Microsoft 365 services.
Next steps:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
As the Microsoft-managed environment was healthy throughout the issue, we will not produce a preliminary Post-Incident Report; we will only be publishing the final Post-Incident Report.
|
|---|
|
| Time: | Fri Mar 6 12:25:14 2026 |
|---|
| Description: | Title: Some users in the North American region may be unable to access multiple Microsoft 365 services
User impact: Users in the North American region may be unable to access multiple Microsoft 365 services.
More info: Impacted services include, but are not limited to:
- Microsoft 365 admin center
- SharePoint Online
- Microsoft Teams
Current status: We've received reports that the issue is no longer occurring for some users and we're continuing our investigation to confirm full recovery. Our investigation is focused on content delivery network (CDN) configurations and interactions with third‑party network providers.
Scope of impact: Impact is specific to some users located in the North American region attempting to access the Microsoft 365 admin center, Microsoft Teams and SharePoint Online.
Next update by: Friday, March 6, 2025, at 6:30 PM UTC
|
|---|
|
| Time: | Fri Mar 6 11:53:53 2026 |
|---|
| Description: | We’re continuing to focus our investigation on Content Delivery Network (CDN) configurations and how they may interact with downstream services.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Mar 6 11:26:53 2026 |
|---|
| Description: | We’re continuing to review telemetry related to the impacted services to help isolate the source of the issue. Our investigation is currently focused on Content Delivery Network (CDN) configurations.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Mar 6 11:09:44 2026 |
|---|
| Description: | Title: Some users in the North American region may be unable to access multiple Microsoft 365 services
User impact: Users in the North American region may be unable to access multiple Microsoft 365 services.
More info: Impacted services include, but are not limited to:
- Microsoft 365 admin center
- SharePoint Online
- Microsoft Teams
Current status: We're retrieving additional service monitoring telemetry for review as we work to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users located in North American region attempting to access the Microsoft 365 admin center, Microsoft Teams and SharePoint Online.
Next update by: Friday, March 6, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Fri Mar 6 10:46:03 2026 |
|---|
| Description: | We’re continuing to review service monitoring telemetry related to Microsoft 365 admin center access in the North American region to isolate the source of the issue.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Fri Mar 6 10:21:20 2026 |
|---|
| Description: | Title: Some admins in the North American region may be unable to access the Microsoft 365 admin center
User impact: Admins in the North American region may be unable to access the Microsoft 365 admin center.
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 admins located in the North American region attempting to access the admin center.
Next update by: Friday, March 6, 2025, at 5:30 PM UTC
|
|---|
|
SP1240084 - Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Feb 26 21:11:21 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 17 11:49:37 2026 |
|---|
| Root Cause: | A recent change introduced a code issue which is resulting in impact. |
|---|
| Next Update: | Thursday, March 19, 2026, at 5:00 PM UTC |
|---|
|
Details
| Time: | Tue Mar 17 11:48:37 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although search results provide all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We’ve confirmed that the fix has reached 25 percent saturation, and we’re continuing to monitor its progression as it deploys across affected environments. Once available, we’ll provide a resolution timeline.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Start time: Friday, January 2, 2026, at 12:00 AM UTC
Root cause: A recent change introduced a code issue which is resulting in impact.
Next update by: Thursday, March 19, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Mar 12 11:51:21 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although search results provide all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We've expanded communications to encompass all potentially affected users and we've updated the "Title", "User impact", and "Scope of impact" fields of our communications to reflect this change. We've initiated deployment of our code fix to address the offending code issue so a subset of users to for additional assurance of it's success, and we anticipate these users will see remediation by Tuesday, March 12, 2026. After validation from that limited deployment, will continue the process to all environment and provide a timeline for remediation as one becomes available.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Start time: Friday, January 2, 2026, at 12:00 AM UTC
Root cause: A recent change introduced a code issue which is resulting in impact.
Next update by: Tuesday, March 17, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Mar 9 11:47:15 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although search results provide all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We've internally validated our code fix and have confirmed it will be viable for addressing the code problems and for remediating the impact. As we further analyze the offending service update that introduced the code problem and confirm when the problems initially began, we're expecting our solution will start deployment and that an estimated timeline for the remediation of the impact will be available by our next scheduled communication update.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Root cause: A recent change introduced a code issue which is resulting in impact.
Next update by: Thursday, March 12, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Mar 6 12:20:42 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although search results are providing all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We've identified that a recent change introduced a code issue which is resulting in impact. We're preparing a fix to correct the code issue and expect to have a timeline for the fix deployment with our next scheduled communication update.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Root cause: A recent change introduced a code issue which is resulting in impact.
Next update by: Monday, March 9, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Mar 6 06:36:21 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although search results are providing all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We're enabling connector data to assist us in validation of the path to confirm whether the property value is coming through as empty or if there is a property resolution issue caused by a conflict. Additionally, we're exploring making code changes to add more logging to allow us to verify the behavior in greater detail.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Next update by: Friday, March 6, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Mar 5 07:14:50 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although search results are providing all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We're progressing with the investigation into all available diagnostic data and support-provided information to help identify the root cause of impact and a mitigation plan.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Next update by: Friday, March 6, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Thu Mar 5 04:53:47 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although search results are providing all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We've obtained further details from reporting users and are continuing to investigate all our available diagnostic data and support-provided information to help identify the root cause of impact and a mitigation plan.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Next update by: Thursday, March 5, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Wed Mar 4 03:44:43 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although search results are providing all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We're continuing to source search results where relevancy results aren't prioritized to determine what is occurring. This process is moving slower than expected due to needing a larger data scope from affected users to understand the cause.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Next update by: Thursday, March 5, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 02:28:47 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although searches results are providing all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We require some additional information to effectively identify the root cause including full search results and confirmation that the searched items are present in the index. We're expecting that this information will be available to us for further investigation and we'll update at our next communication.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Next update by: Wednesday, March 4, 2026, at 9:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 17:09:22 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
More info: Although searches results are providing all items to users, the results don't appear to be utilizing relevancy tuning. Items that are highly relevant to the searches may not be provided as top results due to this.
Current status: We’ve gathered the requested diagnostic data from some affected users, and we're assessing this data to help isolate the source of impact and determine appropriate remediation actions.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Next update by: Tuesday, March 3, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 06:30:25 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
Current status: Our investigation into the HAR logs has so far proven inconclusive. We're collecting additional affected query results to help us continue the investigation.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Next update by: Friday, February 27, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Fri Feb 27 01:36:47 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
Current status: We're continuing our review of the previously provided HAR logs. We've also requested additional search results and URLs that are expected to be listed with higher relevancy to help uncover the underlying reason for deprioritized search results.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Next update by: Friday, February 27, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Thu Feb 26 21:40:35 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
Current status: We're reviewing HTTP Archive format (HAR) logs provided by some affected users to help with isolating the source of the issue and are formulating a remediation plan.
Scope of impact: This incident impacts all users performing SharePoint Online searches, who may not see search returns prioritizing high-relevancy items in the results. This information may be updated as our investigation continues.
Next update by: Friday, February 27, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Thu Feb 26 21:15:10 2026 |
|---|
| Description: | Title: Some users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results
User impact: Users’ SharePoint Online search returns may not be prioritizing high-relevancy items in the results.
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
DZ1253788 - Users may see delays with some reports including scheduled reports in Microsoft Defender for Office 365
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 16 05:00:00 2026 |
|---|
| End Time: | Tue Mar 17 05:00:00 2026 |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 17 11:45:55 2026 |
|---|
| Root Cause: | An issue with an upstream data source for reporting data was causing delays with reports in Microsoft Defender for Office 365 and the EAC. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 17 11:45:55 2026 |
|---|
| Description: | Title: Users may see delays with some reports including scheduled reports in Microsoft Defender for Office 365
User impact: Users may have seen delays with some reports including scheduled reports in Microsoft Defender for Office 365.
More info: Additionally, admins may have seen delays with mail flow reports in the Exchange admin center (EAC).
Final status: The remaining reporting data has been processed and impact successfully remediated for all users.
Scope of impact: This issue may have potentially impacted any user or admin reviewing reports in Microsoft Defender for Office 365 and the EAC.
Start time: Monday, March 16, 2026, at 9:00 AM UTC
End time: Tuesday, March 17, 2026, at 9:00 AM UTC
Root cause: An issue with an upstream data source for reporting data was causing delays with reports in Microsoft Defender for Office 365 and the EAC.
Next steps:
- We're investigating our upstream data source to confirm how the issue was introduced to better understand and prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 17 05:50:39 2026 |
|---|
| Description: | Title: Users may see delays with some reports including scheduled reports in Microsoft Defender for Office 365
User impact: Users may see delays with some reports including scheduled reports in Microsoft Defender for Office 365.
More info: Additionally, admins may see delays with mail flow reports in the Exchange admin center (EAC).
Current status: We've confirmed that most of the reporting data has now been processed and that the remaining data should complete processing by our next scheduled update.
Scope of impact: This issue may potentially impact any user or admin reviewing reports in Microsoft Defender for Office 365 and the EAC.
Start time: Monday, March 16, 2026, at 9:00 AM UTC
Estimated time to resolve: Tuesday, March 17, 2026
Root cause: An issue with an upstream data source for reporting data is causing delays with reports in Microsoft Defender for Office 365 and the EAC.
Next update by: Tuesday, March 17, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Mar 16 20:08:48 2026 |
|---|
| Description: | Title: Users may see delays with some reports including scheduled reports in Microsoft Defender for Office 365
User impact: Users may see delays with some reports including scheduled reports in Microsoft Defender for Office 365.
More info: Additionally, admins may see delays with mail flow reports in the Exchange admin center (EAC).
Current status: We identified an issue with an upstream data source for reporting data that is causing delays with reports in Microsoft Defender for Office 365 and the EAC. We've repaired the upstream data source and can see the backlog of reporting data propagating. We'll continue to monitor to ensure the report data is up to date.
Scope of impact: This issue may potentially impact any user reviewing reports in Microsoft Defender for Office 365 and the EAC.
Start time: Monday, March 16, 2026, at 9:00 AM UTC
Root cause: An issue with an upstream data source for reporting data is causing delays with reports in Microsoft Defender for Office 365 and the EAC.
Next update by: Tuesday, March 17, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Mon Mar 16 19:31:48 2026 |
|---|
| Description: | Title: Users may see delays with some reports in Microsoft Defender for Office 365
User impact: Users may see delays with some reports in Microsoft Defender for Office 365.
Current status: We're investigating a potential issue with Microsoft Defender for Office 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
EX1254044 - Some users may be unable to use Microsoft Outlook Classic while the Microsoft Teams Meeting Add-in is enabled
| Status: | serviceDegradation |
|---|
| Start Time: | Thu Mar 12 08:36:00 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Mar 17 11:03:48 2026 |
|---|
| Root Cause: | A previous Outlook build version that is enabled is causing impact to occur. |
|---|
| Next Update: | Thursday, March 19, 2026, at 10:30 AM UTC |
|---|
|
Details
| Time: | Tue Mar 17 04:54:12 2026 |
|---|
| Description: | Title: Some users may be unable to use Microsoft Outlook Classic while the Microsoft Teams Meeting Add-in is enabled
User impact: Users may be unable to use Microsoft Outlook Classic while the Microsoft Teams Meeting Add-in is enabled.
More info: If Teams Meeting Add-in is disabled then Outlook Classic functions as normal.
As a workaround, users can also perform an Online Repair of Office or update Outlook to the latest version to resolve the issue.
Current status: We've identified that a previous Outlook build version is causing impact to occur. We're working with your representatives to ensure that the latest Outlook version is enabled, to mitigate impact.
Scope of impact: Users attempting to use Microsoft Outlook Classic while the Microsoft Teams Meeting Add-in and previous Outlook build version is enabled may be impacted.
Start time: Thursday, March 12, 2026, at 12:36 PM UTC
Root cause: A previous Outlook build version that is enabled is causing impact to occur.
Next update by: Thursday, March 19, 2026, at 10:30 AM UTC
|
|---|
|
| Time: | Tue Mar 17 02:55:06 2026 |
|---|
| Description: | Title: Some users are unable to use Microsoft Outlook Classic while the Microsoft Teams Meeting Add-in is enabled
User impact: Users are unable to use Microsoft Outlook Classic while the Microsoft Teams Meeting Add-in is enabled.
More info: If Teams Meeting Add-in is disabled then Outlook Classic functions as normal.
As a workaround, users can also perform an Online Repair of Office or update Outlook to the latest version to resolve the issue.
Current status: We're analyzing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and users attempting to use Microsoft Outlook Classic while the Microsoft Teams Meeting Add-in is enabled are impacted.
Next update by: Tuesday, March 17, 2026, at 9:00 AM UTC
|
|---|
|
TM1254117 - Some users may have been unable to start recordings and transcriptions in Microsoft Teams town hall events
| Status: | serviceRestored |
|---|
| Start Time: | Wed Mar 11 12:57:00 2026 |
|---|
| End Time: | Tue Mar 17 08:01:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 17 09:56:37 2026 |
|---|
| Root Cause: | A recent configuration change caused the service to misinterpret recording eligibility, resulting in recording permissions to be treated as unavailable even when recording policies were enabled. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 17 08:59:28 2026 |
|---|
| Description: | Title: Some users may have been unable to start recordings and transcriptions in Microsoft Teams town hall events
User impact: Users may have been unable to start recordings and transcriptions in Microsoft Teams town hall events.
More info: The recording option was disabled and marked as unavailable, even when the event policy was enabled for town hall.
Final status: We’ve identified a recent configuration change was incorrectly misinterpreting recording eligibility, causing permissions to be treated as unavailable even when recording policies were enabled. We've reverted the configuration update to restore expected recording functionality for affected environments, and can confirm that the issue is resolved after a period of monitoring service health.
Scope of impact: Some users attempting to record meetings and transcriptions in town hall events within Microsoft Teams may have been impacted.
Start time: Wednesday, March 11, 2026, at 4:57 PM UTC
End time: Tuesday, March 17, 2026, at 12:01 PM UTC
Root cause: A recent configuration change caused the service to misinterpret recording eligibility, resulting in recording permissions to be treated as unavailable even when recording policies were enabled.
Next steps:
- We’re reviewing our deployment and change validation procedures to help prevent similar configuration issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 17 06:43:49 2026 |
|---|
| Description: | Title: Some users may be unable to start recordings and transcriptions in Microsoft Teams town hall events
User impact: Users may be unable to start recordings and transcriptions in Microsoft Teams town hall events.
More info: The recording option is disabled and marked as unavailable, even when the event policy is enabled for town hall.
Current status: We're analyzing and reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users attempting to record meetings and transcriptions in town hall events within Microsoft Teams may be impacted.
Next update by: Tuesday, March 17, 2026, at 1:00 PM UTC
|
|---|
|
WP1253861 - Users may be unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 16 14:30:00 2026 |
|---|
| End Time: | Tue Mar 17 01:10:00 2026 |
|---|
| Service: | Windows 365 |
|---|
| Feature Group: | End User |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Mar 17 01:57:46 2026 |
|---|
| Root Cause: | A recent update to the affected service contained a configuration issue that led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 17 01:50:01 2026 |
|---|
| Description: | Title: Users may be unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app
User impact: Users may have been unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app.
More info: This occurred in all Windows app clients.
Final status: We've completed our review of our logs and have correlated impact with a recent update to the service that contained a configuration issue, which led to impact. We've since rolled back this update to restore the previous configuration and we've received confirmation for affected users that impact has been successfully remediated.
Scope of impact: Any user may have been impacted by this event, and may have been unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app.
Start time: Monday, March 16, 2026, at 6:30 PM UTC
End time: Tuesday, March 17, 2026, at 5:10 AM UTC
Root cause: A recent update to the affected service contained a configuration issue that led to impact.
Next steps:
- We're reviewing our update procedures to understand why the configuration issue wasn't identified during our initial testing phase. This will help to drive service improvements by proactively identifying similar issues in the future.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Mon Mar 16 23:59:50 2026 |
|---|
| Description: | Title: Users are unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app
User impact: Users are unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app.
More info: This occurs in all Windows app clients.
Current status: We're continuing our review the Windows app logs as well as any recent changes made to the service, to help identify the underlying root cause of impact. Additionally, we've edited the Title, User impact, More info and Scope of impact sections of this communication to align with our current understanding of the affected scenario.
Scope of impact: Your organization is impacted by this event, and users are unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app. This section may be updated as our investigation continues.
Next update by: Tuesday, March 17, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Mon Mar 16 22:33:27 2026 |
|---|
| Description: | Title: Users are unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app
User impact: Users are unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app.
More info: This occurs in all Windows app clients.
Current status: We're reviewing the provided Windows 365 app logs to inform our next troubleshooting steps for identifying the underlying root cause of impact.
Scope of impact: Your organization is impacted by this event, and users are unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app. This section may be updated as our investigation continues.
Next update by: Tuesday, March 17, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Mon Mar 16 22:09:49 2026 |
|---|
| Description: | Title: Users are unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app
User impact: Users are unable to see their Windows 365 Frontline Dedicated Cloud PCs in the Windows app.
More info: This occurs in all Windows app clients.
Current status: We're investigating a potential issue with Windows 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MV1240680 - Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Feb 27 15:56:36 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 16 22:07:25 2026 |
|---|
| Root Cause: | An updated metadata file that contained invalid metric logic is resulting in impact. |
|---|
| Next Update: | Tuesday, March 31, 2026, at 3:00 AM UTC |
|---|
|
Details
| Time: | Mon Mar 16 22:07:25 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We've identified that due to the amount of metrics data impacted, we anticipate the backfilled data will be restated by early to mid-May, 2026. We'll provide updates while this process continues to ensure our timeline remains accurate.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Tuesday, March 31, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Mar 12 22:46:32 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We're continuing to progress with the restating of affected metrics data. We're also still assessing an accurate timeline for completion, and we aim to provide this by our next scheduled update.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Tuesday, March 17, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Mar 5 21:16:34 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We've confirmed that rolling back the impacted metadata component to an earlier logic version has completed, and we've started the process of restating affected metrics data. We anticipate being able to provide a timeline for when this process should complete by our next scheduled update.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Friday, March 13, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 22:18:51 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We're preparing to roll back the impacted metadata component to an earlier logic version to resolve the issue. We're anticipating the rollback should take effect by our next scheduled update, at which point we'll monitor to confirm its efficacy and begin determining our timeline for restatement of the affected metrics data.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Friday, March 6, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 20:19:21 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Current status: We're continuing to validate the most effective mitigation path to address the responsible updated metadata file and remediate the impact.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact.
Next update by: Wednesday, March 4, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Mon Mar 2 22:04:25 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
More info: This metric should be accounting for users that have selected "Send message with elaborate" in Outlook, but it isn't. The total action count appears to be zero.
Current status: We've identified that this was caused by an updated metadata file that contained invalid metric logic, resulting in impact. We're reviewing options to mitigate this issue as well as our options for recovering the reporting data.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact
Next update by: Wednesday, March 4, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 18:01:00 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
More info: This metric should be accounting for users that have selected "Send message with elaborate" in Outlook, but it isn't. The total action count appears to be zero.
Current status: We've identified that this was caused by an updated metadata file that contained invalid metric logic, resulting in impact. We're reviewing options to mitigate this issue as well as our options for recovering the reporting data.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted.
Start time: Thursday, January 22, 2026, at 7:26 PM UTC
Root cause: An updated metadata file that contained invalid metric logic is resulting in impact
Next update by: Tuesday, March 3, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Fri Feb 27 16:49:05 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
More info: This metric should be accounting for users that have selected "Send message with elaborate" in Outlook, but it isn't. The total action count appears to be zero.
Current status: We're reviewing internal telemetry data to determine why users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
Scope of impact: Users reviewing the Copilot metrics "Total emails sent" field may be impacted.
Next update by: Friday, February 27, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Fri Feb 27 16:10:15 2026 |
|---|
| Description: | Title: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field
User impact: Users may see an action count of zero in Microsoft Viva Insights for the Copilot metrics "Total emails sent" field.
More info: This metric should be accounting for users that have selected "Send message with elaborate" in Outlook, but it isn't. The total action count appears to be zero.
Current status: We're investigating a potential issue with Microsoft Viva Insights and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1253428 - Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 16 09:05:00 2026 |
|---|
| End Time: | Mon Mar 16 17:55:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Mar 16 21:06:26 2026 |
|---|
| Root Cause: | The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page received a high volume of traffic that inhibited the rate in which some users' requests were being processed, preventing some users from accessing the service pages. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 16 21:06:26 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may have been unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client was office.com, and impacted Microsoft 365 Copilot web-clients were office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users could access Microsoft Copilot through application-based Microsoft Copilot services. This included but wasn't limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may have been able to leverage office.com/search, which redirects to https://m365.cloud.microsoft/search, and should've been able to sign in using this page. Once signed in, users could access the impacted web-based office.com and Copilot clients.
Final status: We've confirmed through our service-side telemetry that that the service health has fully recovered and impact has been successfully remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Monday, March 16, 2026, at 1:05 PM UTC
End time: Monday, March 16, 2026, at 9:55 PM UTC
Root cause: The infrastructure that supports access to Office.com and the Microsoft 365 Copilot web sign-in page received a high volume of traffic that inhibited the rate in which some users' requests were being processed, preventing some users from accessing the service pages.
Next steps:
- We're continuing to monitor the affected infrastructure closely to ensure the service remains stable and to help inform any changes we can make to improve the service's resilience against similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 16 20:27:59 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes but isn’t limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage office.com/search, which redirects to https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access the impacted web-based office.com and Copilot clients.
Current status: Our service-side telemetry monitoring continues as we're seeing recovery from our latest configuration changes. We're monitoring further to understand if additional changes are needed.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 16, 2026, at 1:05 PM UTC
Next update by: Tuesday, March 17, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Mon Mar 16 18:24:36 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes but isn’t limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage office.com/search, which redirects to https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access the impacted web-based office.com and Copilot clients.
Current status: We're continuing to monitor our service-side telemetry to ensure our latest configuration changes are working as expected.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, March 16, 2026, at 1:05 PM UTC
Next update by: Tuesday, March 17, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Mar 16 16:38:52 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes but isn’t limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage office.com/search, which redirects to https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access the impacted web-based office.com and Copilot clients.
Current status: Our efforts to apply the aforementioned configuration changes are ongoing and we’re monitoring our service-side telemetry to ensure that the configuration changes are having the desired effect. In tandem, we’re determining the most efficient way to reproduce the event in our testing environment so that we can validate our progress.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, March 16, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Mar 16 14:16:44 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes but isn’t limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage office.com/search, which redirects to https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access the impacted web-based office.com and Copilot clients.
Current status: Through analysis of our service-side telemetry, we’ve made additional configuration changes to optimize traffic to the affected infrastructure. Our monitoring of service telemetry tracking successful and failed access attempts continues to ensure the effectiveness of these changes.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, March 16, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Mar 16 12:13:02 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes but isn’t limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
User may be able to leverage office.com/search, which redirects to https://m365.cloud.microsoft/search, and should be able to sign in using this page. Once signed in, users can access the impacted web-based office.com and Copilot clients.
Current status: Our work to optimize the traffic to the affected section of service infrastructure continues. We've made additional configuration changes and are monitoring our service side telemetry to verify its effectiveness.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, March 16, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Mar 16 10:28:52 2026 |
|---|
| Description: | Title: Some users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page
User impact: Users may be unable to access Office.com or the Microsoft 365 Copilot web sign‑in page.
More info: The impacted web-client is office.com, and impacted Microsoft 365 Copilot web-clients are office.com/chat, m365.cloud.microsoft, m365.cloud.microsoft/chat and copilot.cloud.microsoft.
Users can access Microsoft Copilot through application-based Microsoft Copilot services. This includes, but is not limited to:
- Microsoft Copilot desktop app
- Copilot in Microsoft Teams
- Copilot in Office apps
Current status: We've identified that a section of service infrastructure is not processing traffic efficiently. We're making configuration changes to remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Next update by: Monday, March 16, 2026, at 4:30 PM UTC
|
|---|
|
EX1232513 - Some admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center
| 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: | Mon Mar 16 16:38:50 2026 |
|---|
| Root Cause: | A change introduced a code regression to Mailbox Replication Service (MRS), which causes intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured. |
|---|
| Next Update: | Thursday, March 19, 2026, at 9:30 PM UTC |
|---|
|
Details
| Time: | Mon Mar 16 16:38:50 2026 |
|---|
| Description: | Title: Some admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This will allow the affected move jobs to continue to make progress.
Admins may run the following PowerShell cmdlets sequentially for migration batches:
Set-MigrationBatch batchname -SkipMoving FolderRestrictions
Start-MigrationBatch "BatchName"
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online will be returned the following error
"PropTagToPropertyDefinitionConversionException"
Current status: During the initial deployment of our solution into our internal validation environment, our testing determined that while it would address most of the problems admins are experiencing, it wouldn't resolve the problems for any non-signature moves, and thus not be viable for remediating the impact. We're developing a new solution to ensure that all tenant to tenant and offboarding moves are restored for admins in the Exchange Online admin center and expect more clarity into the timeline for its deployment by our next scheduled communication update.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be affected. This information may be updated as our investigation continues.
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which causes intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Thursday, March 19, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Mar 11 12:02:02 2026 |
|---|
| Description: | Title: Some admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may use PowerShell for the affected migrations and moves with the following cmdlet against the affected mailboxes:
Set-MoveRequest "user@yourdomain.com" -SkipMoving FolderRestrictions
Next, the tenant admin may resume the move request using the cmdlet:
Resume-MoveRequest "user@yourdomain.com"
This will allow the affected move jobs to continue to make progress.
Admins may run the following PowerShell cmdlets sequentially for migration batches:
Set-MigrationBatch batchname -SkipMoving FolderRestrictions
Start-MigrationBatch "BatchName"
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online will be returned the following error
"PropTagToPropertyDefinitionConversionException"
Current status: We received a report of our previously communicated PowerShell cmdlet listed in the More info section not working as expected specifically for migration batches. We've updated that section with revised guidance and recommend admins review this updated information. Regarding the deployment status, we're continuing to monitor its progress, which may gradually provide relief to admins as it saturates the environment.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be affected. This information may be updated as our investigation continues.
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which causes intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Monday, March 16, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Mar 9 16:35:34 2026 |
|---|
| Description: | Title: Some admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center
User impact: Admins may be unable to perform tenant to tenant migrations and offboarding moves in the Exchange admin center.
More info: While we work on developing a long-term solution, admins may 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.
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online will be returned the following error
"PropTagToPropertyDefinitionConversionException"
Current status: We're continuing to monitor as the deployment progresses, and we expect it may take a few weeks to be fully saturated. Users will experience remediation incrementally while the fix is deployed, and we'll aim to provide an update on the resolution timeline once available.
Scope of impact: Some admins attempting to perform tenant to tenant migrations and offboarding moves in the Exchange admin center may be affected. This information may be updated as our investigation continues.
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which causes intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Monday, March 16, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Mon Mar 2 15:44:00 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.
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online will be returned the following error "PropTagToPropertyDefinitionConversionException"
Current status: We've completed our final internal validations of our solution to address the code regression, and we've begun the deployment to the affected environment. We're monitoring its progress as we'll provide an estimated time for remediation as one becomes available.
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.
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which causes intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Monday, March 9, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Feb 26 16:24:27 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.
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online will be returned the following error "PropTagToPropertyDefinitionConversionException"
Current status: Following our completed fix development, we've progressed to the internal validation stage of our mitigations so we can ensure that the fix addresses the problems admins are having with migrations and offboarding without introducing any unexpected problems to the service. We're expecting an estimated timeline for the deployment of our fix and the remediation of the impact will be available once our internal validations have completed.
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.
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which causes intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Monday, March 2, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Fri Feb 20 15:59:13 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.
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online will be returned the following error "PropTagToPropertyDefinitionConversionException"
Current status: We're in the final stages of the development of our solution to address the code regression and we're preparing to begin testing this fix to validate that it'll successfully remediate the impact. We'll provide a timeline for resolution as one becomes available.
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.
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which causes intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Thursday, February 26, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Feb 17 16:12:28 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.
Admins attempting to complete a tenant-to-tenant migration or an offboarding move in Exchange Online will be returned the following error "PropTagToPropertyDefinitionConversionException"
Current status: After analyzing backend settings and recent changes, we've isolated the offending change. This change introduced a code regression to Mailbox Replication Service (MRS), which causes intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured. We're creating and validating a code fix to address the regression and we aim to provide updates as development progresses. Simultaneously, we've expanded communications to all potentially affected tenants to ensure all affected admins are receiving updates about this issue.
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.
Root cause: A change introduced a code regression to Mailbox Replication Service (MRS), which causes intermittent failures for tenant-to-tenant migration actions or offboarding moves as the property tags needed to complete the request are not being properly configured.
Next update by: Friday, February 20, 2026, at 10:00 PM UTC
|
|---|
|
| 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
|
|---|
|
SP1240323 - Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 27 04:43:00 2026 |
|---|
| End Time: | Wed Mar 11 18:32:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 16 13:43:47 2026 |
|---|
| Root Cause: | A recent service configuration change affected a SharePoint web service endpoint and prevented certain web service calls from completing successfully, which caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 16 13:43:47 2026 |
|---|
| Description: | Title: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool
User impact: Users may have been unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool.
Final status: We've completed our deployment to correct the aforementioned configuration issue and confirmed through service health telemetry that the impact is remediated.
Scope of impact: Any user that attempted to edit SharePoint Online sites using the SharePoint Designer 2013 tool may have been impacted.
Start time: Friday, February 27, 2026, at 9:43 AM UTC
End time: Wednesday, March 11, 2026, at 10:32 PM UTC
Root cause: A recent service configuration change affected a SharePoint web service endpoint and prevented certain web service calls from completing successfully, which caused impact.
Next steps:
- We're reviewing our service configuration change testing and validation procedures to identify and prevent similar issues with web service calls in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Fri Mar 6 15:12:00 2026 |
|---|
| Description: | Title: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool
User impact: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool.
Current status: We've determined that a recent service configuration change affecting a SharePoint web service endpoint prevented certain web service calls from completing successfully, which led to the impact. We’ve developed and initiated the deployment of a fix to address this issue, and we’ll provide an estimate for its completion when available.
Scope of impact: Any user attempting to edit SharePoint Online sites using the SharePoint Designer 2013 tool may be impacted.
Start time: Friday, February 27, 2026, at 9:43 AM UTC
Root cause: A recent service configuration change affecting a SharePoint web service endpoint prevents certain web service calls from completing successfully, which is leading to the impact.
Next update by: Monday, March 16, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Mar 4 14:06:06 2026 |
|---|
| Description: | Title: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool
User impact: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool.
Current status: We've identified a potential code fix to address this impact, despite the upcoming retirement of the workflow. We're continuing our investigation into the underlying root cause of this issue in parallel to our development of this fix. We estimate having this potential code fix ready to schedule its deployment by our next communication update, at the earliest.
Scope of impact: Any user attempting to edit SharePoint Online sites using the SharePoint Designer 2013 tool may be impacted.
Next update by: Friday, March 6, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Feb 27 14:03:11 2026 |
|---|
| Description: | Title: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool
User impact: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool.
Current status: We're continuing to review logs, correlation IDs, and site collection IDs to identify the root cause so we can determine if a viable mitigation path is available, given the upcoming retirement of the workflow.
Scope of impact: Any user attempting to edit SharePoint Online sites using the SharePoint Designer 2013 tool may be impacted.
Next update by: Wednesday, March 4, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Feb 27 09:47:59 2026 |
|---|
| Description: | Title: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool
User impact: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool.
Current status: We're reviewing Unified Logging Service logs, correlation IDs and site collection IDs to help identify the root cause.
Scope of impact: Any user attempting to edit SharePoint Online sites using the SharePoint Designer 2013 tool may be impacted.
Next update by: Friday, February 27, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Fri Feb 27 07:38:40 2026 |
|---|
| Description: | Title: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool
User impact: Users may be unable to edit SharePoint Online sites using the SharePoint Designer 2013 tool.
Current status: We're analyzing service logs to determine our next troubleshooting steps.
Scope of impact: Any user attempting to edit SharePoint Online sites using the SharePoint Designer 2013 tool may be impacted.
Next update by: Friday, February 27, 2026, at 3:00 PM UTC
|
|---|
|
EX1243339 - Users were unable to create or edit Ownerless Groups policies in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 12 10:33:00 2026 |
|---|
| End Time: | Mon Mar 16 02:30:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 16 04:36:41 2026 |
|---|
| Root Cause: | A recent update to the authentication flow is caused the call to DSAPI to update Ownerless Groups policies to fail due to outdated authentication flow mapping, resulting in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 16 04:36:41 2026 |
|---|
| Description: | Title: Users were unable to create or edit Ownerless Groups policies in Exchange Online
User impact: Users were unable to create or edit Ownerless Groups policies in Exchange Online.
Final status: We’ve successfully developed and deployed the fix and after our validations have confirmed that impact is resolved.
Scope of impact: Users attempting to create or update Ownerless Groups policies in Exchange Online were impacted.
Start time: Thursday, February 12, 2026, at 3:33 PM UTC
End time: Monday, March 16, 2026, at 6:30 AM UTC
Root cause: A recent update to the authentication flow is caused the call to DSAPI to update Ownerless Groups policies to fail due to outdated authentication flow mapping, resulting in the impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles
This is the final update for this event.
|
|---|
|
| Time: | Mon Mar 16 03:33:50 2026 |
|---|
| Description: | Title: Users may be unable to create or edit Ownerless Groups policies in Exchange Online
User impact: Users may be unable to create or edit Ownerless Groups policies in Exchange Online.
Final status: We’ve successfully developed and deployed the fix and after our validations have confirmed that impact is resolved.
Scope of impact: Users attempting to create or update Ownerless Groups policies in Exchange Online were impacted.
Start time: Thursday, February 12, 2026, at 3:33 PM UTC
End time: Monday, March 16, 2026, at 6:30 AM UTC
Root cause: A recent update to the authentication flow is caused the call to DSAPI to update Ownerless Groups policies to fail due to outdated authentication flow mapping, resulting in the impact.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles
This is the final update for this event.
|
|---|
|
| Time: | Tue Mar 10 00:48:32 2026 |
|---|
| Description: | Title: Users may be unable to create or edit Ownerless Groups policies in Exchange Online
User impact: Users may be unable to create or edit Ownerless Groups policies in Exchange Online.
Current status: The fix deployment is ongoing, and we anticipate it will have completed by our next scheduled update.
Scope of impact: Users attempting to create or update Ownerless Groups policies in Exchange Online may be impacted. This section may be updated as our investigation continues.
Root cause: A recent update to the authentication flow is causing the call to DSAPI to update Ownerless Groups policies to fail due to outdated authentication flow mapping, resulting in the impact.
Next update by: Monday, March 16, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Mar 3 12:40:45 2026 |
|---|
| Description: | Title: Users may be unable to create or edit Ownerless Groups policies in Exchange Online
User impact: Users may be unable to create or edit Ownerless Groups policies in Exchange Online.
Current status: We've determined that a recent update to the authentication flow is causing the call to the Directory Services API (DSAPI) to update Ownerless Groups policies to fail due to outdated authentication flow mapping, resulting in the impact. We're deploying a solution to update the flow mapping for this call and we'll provide a timeline for remediation as one becomes available.
Scope of impact: Users attempting to create or update Ownerless Groups policies in Exchange Online may be impacted. This section may be updated as our investigation continues.
Root cause: A recent update to the authentication flow is causing the call to DSAPI to update Ownerless Groups policies to fail due to outdated authentication flow mapping, resulting in the impact.
Next update by: Tuesday, March 10, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Tue Mar 3 12:12:23 2026 |
|---|
| Description: | Title: Users can't create or edit Ownerless Groups policies in Exchange Online
User impact: Users can't create or edit Ownerless Groups policies in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1243431 - Service health dashboard content within the Microsoft 365 admin center may be truncated
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 16 11:00:00 2026 |
|---|
| End Time: | Fri Mar 13 16:45:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Mar 13 19:36:59 2026 |
|---|
| Root Cause: | A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that caused communications to be truncated. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 13 19:36:59 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may have been unable to view full communications for events in the Service health dashboard of the admin center.
More info: The problem impacted admins accessing the Service health section of the Microsoft 365 admin center. This impacted event communications listed under “Active issues Microsoft is working on”, “Issues for your organization to act on”, and “Issue history”. When admins clicked on events listed in any of these sections, the entirety of the communication wasn't visible. For example, admins could see the Title and User impact of an event after clicking on it, but the Current status statement could be visually cut off. After clicking on an event, admins also saw a message indicating that “This message had formatting issues, which we are working to resolve.”
Final status: Deployment of the fix is complete and we’ve determined from service telemetry that this issue is resolved.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may have been impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
End time: Friday, March 13, 2026, at 8:45 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that caused communications to be truncated.
Next steps:
- We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Mar 13 15:19:24 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may be unable to view full communications for events within the Service health dashboard of the admin center.
More info: The problem impacts admins accessing the Service health section of the Microsoft 365 admin center. This impacts event communications listed under "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history”. When clicking on events listed in any of the aforementioned sections, the entirety of the communication isn’t visible. As an example, admins may be able to see the Title and User impact of an event after clicking on it, but the Current status statement may be visually cut off. Note that after clicking on an event, admins see a message indicating that “This message has formatting issues, which we're currently working to resolve.”
Current status: Deployment of the fix is progressing as expected and we anticipate that the process should complete to fully resolve this issue by our next scheduled update.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may be impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that’s causing communications to be truncated.
Next update by: Saturday, March 14, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Thu Mar 12 17:18:34 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may be unable to view full communications for events within the Service health dashboard of the admin center.
More info: The problem impacts admins accessing the Service health section of the Microsoft 365 admin center. This impacts event communications listed under "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history”. When clicking on events listed in any of the aforementioned sections, the entirety of the communication isn’t visible. As an example, admins may be able to see the Title and User impact of an event after clicking on it, but the Current status statement may be visually cut off. Note that after clicking on an event, admins see a message indicating that “This message has formatting issues, which we're currently working to resolve.”
Current status: We've completed our pre-deployment steps and have begun deploying the code fix to our Government cloud. We're monitoring the deployment and will provide a timeline for its completion as one becomes available.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may be impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that’s causing communications to be truncated.
Next update by: Friday, March 13, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Mon Mar 9 20:49:05 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may be unable to view full communications for events within the Service health dashboard of the admin center.
More info: The problem impacts admins accessing the Service health section of the Microsoft 365 admin center. This impacts event communications listed under "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history”. When clicking on events listed in any of the aforementioned sections, the entirety of the communication isn’t visible. As an example, admins may be able to see the Title and User impact of an event after clicking on it, but the Current status statement may be visually cut off. Note that after clicking on an event, admins see a message indicating that “This message has formatting issues, which we're currently working to resolve.”
Current status: Our pre-deployment steps for the Government cloud deployment are continuing to take longer than anticipated but are ongoing. We'll provide an updated deployment timeline when one becomes available.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may be impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that’s causing communications to be truncated.
Next update by: Thursday, March 12, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Thu Mar 5 19:46:22 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may be unable to view full communications for events within the Service health dashboard of the admin center.
More info: The problem impacts admins accessing the Service health section of the Microsoft 365 admin center. This impacts event communications listed under "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history”. When clicking on events listed in any of the aforementioned sections, the entirety of the communication isn’t visible. As an example, admins may be able to see the Title and User impact of an event after clicking on it, but the Current status statement may be visually cut off. Note that after clicking on an event, admins see a message indicating that “This message has formatting issues, which we're currently working to resolve.”
Current status: Our pre-deployment steps for the Government cloud deployment are taking longer than expected, and we now expect the deployment will begin on Monday, March 9, 2026. We'll provide a deployment timeline once one becomes available.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may be impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that’s causing communications to be truncated.
Next update by: Tuesday, March 10, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Mar 4 20:28:14 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may be unable to view full communications for events within the Service health dashboard of the admin center.
More info: The problem impacts admins accessing the Service health section of the Microsoft 365 admin center. This impacts event communications listed under "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history”. When clicking on events listed in any of the aforementioned sections, the entirety of the communication isn’t visible. As an example, admins may be able to see the Title and User impact of an event after clicking on it, but the Current status statement may be visually cut off. Note that after clicking on an event, admins see a message indicating that “This message has formatting issues, which we're currently working to resolve.”
Current status: We've completed our fix deployment in all affected environments excluding Government cloud. We're still completing our pre-deployment steps before the deployment to the Government cloud environment can begin, which is still anticipated for Thursday, March 5, 2026.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may be impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that’s causing communications to be truncated.
Next update by: Friday, March 6, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Mar 4 17:20:17 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may be unable to view full communications for events within the Service health dashboard of the admin center.
More info: The problem impacts admins accessing the Service health section of the Microsoft 365 admin center. This impacts event communications listed under "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history”. When clicking on events listed in any of the aforementioned sections, the entirety of the communication isn’t visible. As an example, admins may be able to see the Title and User impact of an event after clicking on it, but the Current status statement may be visually cut off. Note that after clicking on an event, admins see a message indicating that “This message has formatting issues, which we're currently working to resolve.”
Current status: Our code fix is continuing to progress as expected, and we anticipate all environments excluding Government cloud will receive the fix by our next scheduled communications update. We're completing our pre-deployment processes for the Government cloud environment, and our estimation for deployment to begin remains Thursday, March 5, 2026.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may be impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that’s causing communications to be truncated.
Next update by: Thursday, March 5, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 23:23:39 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may be unable to view full communications for events within the Service health dashboard of the admin center.
More info: The problem impacts admins accessing the Service health section of the Microsoft 365 admin center. This impacts event communications listed under "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history”. When clicking on events listed in any of the aforementioned sections, the entirety of the communication isn’t visible. As an example, admins may be able to see the Title and User impact of an event after clicking on it, but the Current status statement may be visually cut off. Note that after clicking on an event, admins see a message indicating that “This message has formatting issues, which we're currently working to resolve.”
Current status: Our code fix is continuing to propagate to the affected environments and based on our metrics, we now expect majority of impact to be resolved by our next scheduled update. Additionally, the Government cloud deployment is still expected to start on Thursday, March 5, 2026, which we anticipate being able to provide a timeline for completion of this deployment by our next scheduled communications update.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may be impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that’s causing communications to be truncated.
Next update by: Wednesday, March 4, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Mar 3 18:37:20 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may be unable to view full communications for events within the Service health dashboard of the admin center.
More info: The problem impacts admins accessing the Service health section of the Microsoft 365 admin center. This impacts event communications listed under "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history”. When clicking on events listed in any of the aforementioned sections, the entirety of the communication isn’t visible. As an example, admins may be able to see the Title and User impact of an event after clicking on it, but the Current status statement may be visually cut off. Note that after clicking on an event, admins see a message indicating that “This message has formatting issues, which we're currently working to resolve.”
Current status: After reviewing the scope and deployment rate of the code fix intended to resolve the issue, we’ve established that fully resolving impact is going to take longer than previously outlined. While a majority of impact is expected to be resolved by our next scheduled update, some environments, Government cloud specifically, are going to take longer to remediate. The Government cloud deployment is expected to start on Thursday, March 5, 2026, and we’ll provide an estimated time to resolve the issue should it become available.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may be impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that’s causing communications to be truncated.
Next update by: Wednesday, March 4, 2026, at 6:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 13:02:15 2026 |
|---|
| Description: | Title: Service health dashboard content within the Microsoft 365 admin center may be truncated
User impact: Admins may be unable to view full communications for events within the Service health dashboard of the admin center.
More info: The problem impacts admins accessing the Service health section of the Microsoft 365 admin center. This impacts event communications listed under "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history”. When clicking on events listed in any of the aforementioned sections, the entirety of the communication isn’t visible. As an example, admins may be able to see the Title and User impact of an event after clicking on it, but the Current status statement may be visually cut off. Note that after clicking on an event, admins see a message indicating that “This message has formatting issues, which we're currently working to resolve.”
Current status: We’ve investigated the issue and determined that a recent update to the Microsoft 365 admin center introduced a code regression that’s causing the problem. We’ve developed, tested, and started deploying a code fix to resolve the issue. Impact is expected to be remediated by our next scheduled update.
Scope of impact: Any admin attempting to view event communications in the "Active issues Microsoft is working on", "Issues for your organization to act on", and “Issue history” sections of Service health within the Microsoft 365 admin center may be impacted.
Start time: Monday, February 16, 2026, at 4:00 PM UTC
Root cause: A recent update to the Microsoft 365 admin center intended to improve Service health functionality by adding support for additional character inputs introduced a code regression that’s causing communications to be truncated.
Next update by: Wednesday, March 4, 2026, at 4:00 AM 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: | Fri Mar 13 16:02:52 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, April 14, 2026, at 7:00 PM UTC |
|---|
|
Details
| Time: | Fri Mar 13 16:02:52 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: Based on the rate of progress, we anticipate the backfill job will complete in May 2026. Our monitoring is ongoing as we ensure the data continues to be restored as expected, and we'll provide timeline updates as they're 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.
Start time: Wednesday, July 2, 2025, at 12:00 AM 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: Tuesday, April 14, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Mar 13 14:26: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 macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: The backfill process restoring the usage data is ongoing, and our calculation of a timeline for remediation based on this progress is underway. We'll provide an estimated time for this process to complete once possible.
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.
Start time: Wednesday, July 2, 2025, at 12:00 AM 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: Friday, March 13, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Mar 10 12:58:57 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: As we continue to monitor the backfill job to restore usage data, we're actively calculating a projected timeline for completion based on the rate of progress, and we'll provide this info as it 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.
Start time: Wednesday, July 2, 2025, at 12:00 AM 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: Friday, March 13, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Mar 3 13:23:26 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: Our backfill project to restore usage data is progressing, and we're expecting an updated timeline for its completion and the remediation of the impact to be available 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.
Start time: Wednesday, July 2, 2025, at 12:00 AM 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: Tuesday, March 10, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Tue Feb 17 13:40:38 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're continuing to monitor the backfill project to restore usage data with expectations that it should be completed by the end of March 2026.
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, March 3, 2026, at 7:30 PM UTC
|
|---|
|
| 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.
|
|---|
|
TM1250884 - Some users may not see descriptions of Microsoft Teams webinars on the public registration page
| Status: | serviceRestored |
|---|
| Start Time: | Thu Mar 12 06:00:00 2026 |
|---|
| End Time: | Fri Mar 13 13:50:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Mar 13 14:46:57 2026 |
|---|
| Root Cause: | An update to the process by which the description is displayed has introduced a regression which resulted in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 13 14:46:57 2026 |
|---|
| Description: | Title: Some users may not see descriptions of Microsoft Teams webinars on the public registration page
User impact: Users may not see descriptions of Microsoft Teams webinars on the public registration page.
Final status: The roll back to the previous stable build has completed, and we've confirmed that this has remediated the impact which was caused by the regression introduced in the update to the process by which the description is displayed. Affected users may need to refresh their cache to receive the mitigation.
Scope of impact: Some users attempting to see the descriptions of Microsoft Teams webinars on the public registration page may have been impacted.
Start time: Thursday, March 12, 2026, at 10:00 AM UTC
End time: Friday, March 13, 2026, at 5:50 PM UTC
Root cause: An update to the process by which the description is displayed has introduced a regression which resulted in the impact.
Next steps:
- We're reviewing our update procedures to ensure similar issues are caught and addressed ahead of deployment to prevent this from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Fri Mar 13 13:46:29 2026 |
|---|
| Description: | Title: Some users may not see descriptions of Microsoft Teams webinars on the public registration page
User impact: Users may not see descriptions of Microsoft Teams webinars on the public registration page.
Current status: We're monitoring as the roll back to the previous stable build progresses, and we'll provide a timeline for this to complete as one becomes available. We suspect that an update to the process by which the description is displayed has introduced a regression, and rolling back to the previous build will help in confirming this theory.
Scope of impact: Some users attempting to see the descriptions of Microsoft Teams webinars on the public registration page may be impacted.
Next update by: Friday, March 13, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Fri Mar 13 11:41:34 2026 |
|---|
| Description: | Title: Some users may not see descriptions of Microsoft Teams webinars on the public registration page
User impact: Users may not see descriptions of Microsoft Teams webinars on the public registration page.
Current status: We've identified a recent update which we suspect may be causing the impact. We're rolling back to the previous stable version to confirm whether this remediates the impact.
Scope of impact: Some users attempting to see the descriptions of Microsoft Teams webinars on the public registration page may be impacted.
Next update by: Friday, March 13, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Mar 13 11:22:56 2026 |
|---|
| Description: | Title: Some users may not see descriptions of Microsoft Teams webinars on the public registration page
User impact: Users may not see descriptions of Microsoft Teams webinars on the public registration page.
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.
|
|---|
|
MV1250870 - Users' Microsoft Viva Engage feed may not load and they may encounter timeout errors when editing posts or replies
| Status: | serviceRestored |
|---|
| Start Time: | Fri Mar 13 09:12:00 2026 |
|---|
| End Time: | Fri Mar 13 11:05:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | incident |
|---|
| Last Updated: | Fri Mar 13 11:13:00 2026 |
|---|
| Root Cause: | A recent service-level change to the portion of service infrastructure responsible for facilitating users' feeds caused and unexpected increase in traffic to the infrastructure and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 13 11:13:00 2026 |
|---|
| Description: | Title: Users' Microsoft Viva Engage feed may not load and they may encounter timeout errors when editing posts or replies
User impact: Users' Viva Engage feed may not have loaded and they may have encountered timeout errors when editing posts or replies.
Final status: We've identified that a recent service-level change to the portion of service infrastructure responsible for facilitating users' feeds caused and unexpected increase in traffic to the infrastructure and resulted in impact. We've rebalanced the request traffic and confirmed through service health monitoring that the impact is remediated.
Scope of impact: Any user that attempted to view their Viva Engage feed or edit posts or replies may have been impacted.
Start time: Friday, March 13, 2026, at 1:12 PM UTC
End time: Friday, March 13, 2026, at 3:05 PM UTC
Root cause: A recent service-level change to the portion of service infrastructure responsible for facilitating users' feeds caused and unexpected increase in traffic to the infrastructure and resulted in impact.
Next steps:
- We're continuing to evaluate the request traffic to the affected infrastructure along with our service testing testing and validation procedures to prevent similar load balancing issues in deployments moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Fri Mar 13 11:01:06 2026 |
|---|
| Description: | Title: Users' Microsoft Viva Engage feed may not load and they may encounter timeout errors when editing posts or replies
User impact: Users' Viva Engage feed may not load and they may encounter timeout errors when editing posts or replies.
Current status: Our service health monitoring alerted us to failures occurring when users attempt to view their feeds or edit posts or replies. We're reviewing the portion of service infrastructure responsible for facilitating users' feeds to isolate the source of the failures.
Scope of impact: Any user attempting to view their Viva Engage feed or edit posts or replies may be impacted.
Start time: Friday, March 13, 2026, at 1:12 PM UTC
Next update by: Friday, March 13, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Fri Mar 13 10:52:04 2026 |
|---|
| Description: | Title: Users' Microsoft Viva Engage feed may not load and they may encounter timeout errors when editing posts or replies
User impact: Users' Viva Engage feed may not load and they may encounter timeout errors when editing posts or replies.
Current status: We're investigating a potential issue with Viva Engage 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 365 metrics in Microsoft Viva Insights
| Status: | extendedRecovery |
|---|
| Start Time: | Mon Jun 30 20:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Insights |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 12 21:19:31 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 Microsoft 365 admin center to be inaccurate. |
|---|
| Next Update: | Friday, March 27, 2026, at 2:00 AM UTC |
|---|
|
Details
| Time: | Thu Mar 12 21:19:31 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 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 temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: The reinstatement process is ongoing and we're continuing to monitor as it progresses. We anticipate it will complete by Saturday, May 9, 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 Microsoft 365 admin center to be inaccurate.
Next update by: Friday, March 27, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Mar 9 20:42:30 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 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 temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: We've had to restart a portion of the reinstatement process due to an unexpected issue that arose during the process. We'll continue to monitor the reinstatement process to ensure it completes as expected. We now expect that this process may complete by our next scheduled update.
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 Microsoft 365 admin center to be inaccurate.
Next update by: Friday, March 13, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 20:42:05 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 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 temporarily inaccurate. These issues don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
The timeframe of impacted data is from Tuesday, July 1, 2025, through Monday, February 16, 2026.
Current status: We're continuing to monitor the process of reinstating the previously affected incomplete data between Tuesday, July 1, 2025, through Monday, February 16, 2026. Due to the amount of data that needs to be reinstated, we anticipate this process will take several weeks before this issue is fully remediated.
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 Microsoft 365 admin center to be inaccurate.
Next update by: Tuesday, March 10, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Mon Feb 23 20:53:59 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 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 don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: We've started reinstating the previously affected incomplete data and we're monitoring closely to ensure no complications arise. We anticipate being able to provide a resolution timeline by our next scheduled update.
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 Microsoft 365 admin center to be inaccurate.
Next update by: Thursday, February 26, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Fri Feb 20 17:03:35 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 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 don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: We're completing additional validation before reinstating the previously affected incomplete data. We'll provide a timeline on the reinstatement process as soon as it becomes available.
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 Microsoft 365 admin center to be inaccurate.
Next update by: Tuesday, February 24, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Feb 19 21:10:35 2026 |
|---|
| Description: | Title: Users see inaccurate or incomplete Outlook data for Microsoft Copilot 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 don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: We're continuing to assess our next steps that will be taken before reinstating the previously affected incomplete or inaccurate data.
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 Microsoft 365 admin center to be inaccurate.
Next update by: Friday, February 20, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Tue Feb 17 20:59:14 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 don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting as a “generate email” action.
Current status: We've deployed our solution and the correct data will now be output going forward as of February 18, 2026. We’re assessing the next steps that need to be taken before reinstating the previously affected incomplete or inaccurate data, and we'll provide an update on the timeline for this to complete once one becomes available.
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: Friday, February 20, 2026, at 3:00 AM UTC
|
|---|
|
| 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 don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting 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 don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting 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 don't affect all-up user counts for Copilot or Copilot in Outlook.
For some Outlook on the web users, selecting “summary by Copilot” or “summarize” at the top of an email thread isn't counting as a “summarize email thread” action. For some Outlook on the web and Windows 32 Classic Outlook users, selecting “elaborate” in the compose experience or before sending an email isn't counting 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.
|
|---|
|
CP1227436 - Users may intermittently receive no response from Microsoft Copilot (Microsoft 365) agents in Microsoft Teams
| Status: | postIncidentReviewPublished |
|---|
| 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: | Thu Mar 12 19:24:48 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: | Thu Mar 12 19:24:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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.
|
|---|
|
DZ1247911 - Users may be unable to view Zero-hour auto purge (ZAP) email messages in Microsoft Defender for Office 365 quarantine
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Mar 9 19:23:09 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Office 365 |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 12 17:52:00 2026 |
|---|
| Root Cause: | Specific permissions required to complete the process for admins to view ZAP email messages within quarantine aren’t available due to a recent code change, resulting in impact. |
|---|
| Next Update: | Friday, March 20, 2026, at 10:00 PM UTC |
|---|
|
Details
| Time: | Thu Mar 12 17:52:00 2026 |
|---|
| Description: | Title: Users may be unable to view Zero-hour auto purge (ZAP) email messages in Microsoft Defender for Office 365 quarantine
User impact: Users may be unable to view ZAP email messages in Microsoft Defender for Office 365 quarantine.
More info: Users and admins may see no results when searching for ZAP email messages or affected recipients of the ZAP email messages that were moved to quarantine.
As a workaround, admins can view the ZAP email messages in Threat Explorer, but won’t be able to download or release the messages from quarantine.
Current status: We’re continuing to deploy our solution throughout the impacted service infrastructure and have reached 50 percent saturation. We expect the deployment will be complete by our next scheduled update, after which point we will monitor to confirm the issue is fully resolved.
Scope of impact: Your organization may be affected by this event, and any user trying to view or download ZAP email messages in Microsoft Defender for Office 365 quarantine may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 12:00 AM UTC
Root cause: Specific permissions required to complete the process for admins to view ZAP email messages within quarantine aren’t available due to a recent code change, resulting in impact.
Next update by: Friday, March 20, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Mar 11 17:12:31 2026 |
|---|
| Description: | Title: Users may be unable to view Zero-hour auto purge (ZAP) email messages in Microsoft Defender for Office 365 quarantine
User impact: Users may be unable to view ZAP email messages in Microsoft Defender for Office 365 quarantine.
More info: Users and admins may see no results when searching for ZAP email messages or affected recipients of the ZAP email messages that were moved to quarantine.
As a workaround, admins can view the ZAP email messages in Threat Explorer, but won’t be able to download or release the messages from quarantine.
Current status: We’ve confirmed that our solution resolves the issue within our internal testing environment and have started to roll it out to the impacted service infrastructure. We are closely monitoring the deployment and expect we will be able to share an ETA for completion by our next scheduled update.
Scope of impact: Your organization may be affected by this event, and any user trying to view or download ZAP email messages in Microsoft Defender for Office 365 quarantine may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 12:00 AM UTC
Root cause: Specific permissions required to complete the process for admins to view ZAP email messages within quarantine aren’t available due to a recent code change, resulting in impact.
Next update by: Thursday, March 11, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Mar 10 17:56:56 2026 |
|---|
| Description: | Title: Users may be unable to view Zero-hour auto purge (ZAP) email messages in Microsoft Defender for Office 365 quarantine
User impact: Users may be unable to view ZAP email messages in Microsoft Defender for Office 365 quarantine.
More info: Users and admins may see no results when searching for ZAP email messages or affected recipients of the ZAP email messages that were moved to quarantine.
As a workaround, admins can view the ZAP email messages in Threat Explorer, but won’t be able to download or release the messages from quarantine.
Current status: We’ve determined the root cause is a recent code change that resulted in specific permissions required to complete the process for admins to view ZAP email messages being unavailable. We’ve developed a solution and are starting to deploy the fix to our internal testing environment. Once the deployment is complete, we will test to confirm it mitigates impact as expected before proceeding with a broader rollout.
Scope of impact: Your organization may be affected by this event, and any user trying to view or download ZAP email messages in Microsoft Defender for Office 365 quarantine may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 12:00 AM UTC
Root cause: Specific permissions required to complete the process for admins to view ZAP email messages within quarantine aren’t available due to a recent code change, resulting in impact.
Next update by: Wednesday, March 11, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 9 19:49:03 2026 |
|---|
| Description: | Title: Admins can't view Zero-hour auto purge (ZAP) email messages in Microsoft Defender for Office 365 quarantine
User impact: Admins can't view ZAP email messages in Microsoft Defender for Office 365 quarantine.
More info: Specifically, admins can view the ZAP email messages in Threat Explorer, but they can't download them. Additionally, admins see no results when searching for affected recipients of the ZAP email messages.
Current status: We're reviewing fresh logs from actively reproducing the issue to help with the root cause investigation and to identify a remediation plan.
Scope of impact: Your organization is affected by this event, and any admin trying to view or download ZAP email messages in Microsoft Defender for Office 365 quarantine is impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, March 10, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 9 19:24:24 2026 |
|---|
| Description: | Title: Admins can't view Zero-hour auto purge (ZAP) email messages in Microsoft Defender for Office 365 quarantine
User impact: Admins can't view ZAP email messages in Microsoft Defender for Office 365 quarantine.
More info: Specifically, admins can view the ZAP email messages in Threat Explorer, but they can't download them. Additionally, admins see no results when searching for affected recipients of the ZAP email messages.
Current status: We're investigating a potential issue with Microsoft Defender for Office 365 and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
PB1249959 - Users' data activations in the Microsoft Fabric Activator are delayed or some may potentially not trigger as expected
| Status: | serviceRestored |
|---|
| Start Time: | Thu Mar 12 08:30:00 2026 |
|---|
| End Time: | Thu Mar 12 13:30:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 12 14:02:36 2026 |
|---|
| Root Cause: | An internal logging mechanism wasn't processing some data correctly, resulting in consistently retrying the process and causing degradation in a portion of our downstream data management service infrastructure which Fabric Activator depends on. This in turn resulted in delays in data activations or, in some instances, data activations to not trigger. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 12 13:58:23 2026 |
|---|
| Description: | Title: Users' data activations in the Microsoft Fabric Activator are delayed or some may potentially not trigger as expected
User impact: Users' data activations in Microsoft Fabric Activator were delayed or may have potentially not triggered as expected.
Final status: We’ve completed rerouting activation request traffic away from the impacted infrastructure and confirmed after monitoring service health telemetry that the delays have ceased and the service health is recovered.
Scope of impact: Your organization was affected by this event, and all users with data hosted in the Central US region were impacted.
Start time: Thursday, March 12, 2026, at 12:30 PM UTC
End time: Thursday, March 12, 2026, at 5:30 PM UTC
Root cause: An internal logging mechanism wasn't processing some data correctly, resulting in consistently retrying the process and causing degradation in a portion of our downstream data management service infrastructure which Fabric Activator depends on. This in turn resulted in delays in data activations or, in some instances, data activations to not trigger.
Next steps:
- We're reviewing why an internal logging mechanism wasn't processing some data correctly and the retry logic to prevent repeated attempts to lead to impact so we can better prevent similar future impact.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 12 13:22:51 2026 |
|---|
| Description: | Title: Users' data activations in the Microsoft Fabric Activator are delayed or some may potentially not trigger as expected
User impact: Users' data activations in the Microsoft Fabric Activator are delayed or some may potentially not trigger as expected.
Current status: Our work to reroute activation request traffic away from the impacted infrastructure is ongoing and we're monitoring service health telemetry as it continues. We're beginning to see improvements in latency, confirming delays are reducing and service health is recovering. We anticipate this work should be completed, and impact remediated, by our next scheduled communication update.
Scope of impact: Your organization is affected by this event, and all users with data hosted in the Central US region are impacted.
Start time: Thursday, March 12, 2026, at 12:30 PM UTC
Root cause: An internal logging mechanism isn't processing some data correctly, resulting in consistently retrying the process and causing degradation in a portion of our downstream data management service infrastructure which Fabric Activator depends on. This in turn results in delays in data activations or, in some instances, data activations to not trigger.
Next update by: Thursday, March 12, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Thu Mar 12 11:58:34 2026 |
|---|
| Description: | Title: Users' data activations in the Microsoft Fabric Activator are delayed or some may potentially not trigger as expected
User impact: Users' data activations in the Microsoft Fabric Activator are delayed or some may potentially not trigger as expected.
Current status: We've identified that an internal logging mechanism isn't processing some data correctly, resulting in consistently retrying the process and causing degradation in a portion of our downstream data management service infrastructure which Fabric Activator depends on. This in turn results in delays in data activations or, in some instances, data activations to not trigger. We're working to reroute activation request traffic away from the impacted infrastructure as a means of remediating impact.
Scope of impact: Your organization is affected by this event, and all users with data hosted in the Central US region are impacted.
Start time: Thursday, March 12, 2026, at 12:30 PM UTC
Root cause: An internal logging mechanism isn't processing some data correctly, resulting in consistently retrying the process and causing degradation in a portion of our downstream data management service infrastructure which Fabric Activator depends on. This in turn results delays in data activations or, in some instances, data activations to not trigger.
Next update by: Thursday, March 12, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Thu Mar 12 11:39:08 2026 |
|---|
| Description: | Title: Users' data activations in the Microsoft Fabric Activator are delayed or some may potentially not trigger as expected
User impact: Users' data activations in the Microsoft Fabric Activator are delayed or some may potentially not trigger as expected.
More info: Delayed data activations may take up to 2.5 hours to complete.
Current status: We're investigating a potential issue with Microsoft Fabric and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MO1249949 - Admins can’t view Windows 365 Cloud PC report data in the Microsoft Intune admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Mar 12 08:49:00 2026 |
|---|
| End Time: | Thu Mar 12 12:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 12 13:00:53 2026 |
|---|
| Root Cause: | The subset of service infrastructure that provided access to the Cloud PC report data in the Microsoft Intune admin center wasn't efficiently processing data, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 12 13:00:53 2026 |
|---|
| Description: | Title: Admins can’t view Windows 365 Cloud PC report data in the Microsoft Intune admin center
User impact: Admins couldn't view Cloud PC report data in the Microsoft Intune admin center.
Final status: We've identified that the subset of service infrastructure that provided access to the Cloud PC report data in the Microsoft Intune admin center wasn't efficiently processing data, resulting in impact. We restarted the affected infrastructure and confirmed using our internal telemetry data that impact is remediated.
Scope of impact: Your organization was affected by this event, and impact was specific to some admins in the Central US that attempted to view Cloud PC report data in the Microsoft Intune admin center.
Start time: Thursday, March 12, 2026, at 12:49 PM UTC
End time: Thursday, March 12, 2026, at 4:00 PM UTC
Root cause: The subset of service infrastructure that provided access to the Cloud PC report data in the Microsoft Intune admin center wasn't efficiently processing data, resulting in impact.
Next steps:
- We're reviewing and improving our automated infrastructure recovery services to detect and prevent similar issues before cause future impact.
This is the final update for the event.
|
|---|
|
| Time: | Thu Mar 12 11:11:17 2026 |
|---|
| Description: | Title: Admins can’t view Windows 365 Cloud PC report data in the Microsoft Intune admin center
User impact: Admins can’t view Cloud PC report data in the Microsoft Intune admin center.
Current status: We're reviewing service monitoring telemetry to understand why admins can’t view Cloud PC report data in the Microsoft Intune admin center.
Scope of impact: Your organization is affected by this event, and impact is specific to some admins in the Central US that attempt to view Cloud PC report data in the Microsoft Intune admin center.
Next update by: Thursday, March 12, 2026, at 5:00 PM UTC
|
|---|
|
DZ1237222 - Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app
| Status: | serviceDegradation |
|---|
| Start Time: | Mon Feb 23 00:40:04 2026 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Defender XDR |
|---|
| Feature Group: | Microsoft Defender for Endpoint |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 12 07:05:20 2026 |
|---|
| Root Cause: | The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact. |
|---|
| Next Update: | Thursday, March 26, 2026, at 3:00 PM UTC |
|---|
|
Details
| Time: | Thu Mar 12 07:05:20 2026 |
|---|
| Description: | Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app
User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app.
More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues.
Current status: We’re continuing to identify the optimal approach to restore functionality before re‑enabling the feature. We expect the restoration effort to take approximately three weeks. Once functionality is restored, we’ll be able to confirm and communicate a timeline for re‑enabling the feature.
Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted.
Start time: Friday, January 9, 2026, at 12:00 AM UTC
Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact.
Next update by: Thursday, March 26, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Thu Mar 5 07:33:34 2026 |
|---|
| Description: | Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app
User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app.
More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues.
Current status: We're continuing to move forward with identifying the optimal approach to restore the functionality before re-enabling the feature.
Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted.
Start time: Friday, January 9, 2026, at 12:00 AM UTC
Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact.
Next update by: Thursday, March 12, 2026, at 3:00 PM UTC
|
|---|
|
| Time: | Fri Feb 27 10:50:03 2026 |
|---|
| Description: | Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app
User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app.
More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues.
Current status: We're progressing with our analysis of the most efficient method to correct the functionality before re-enabling the feature.
Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted.
Start time: Friday, January 9, 2026, at 12:00 AM UTC
Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact.
Next update by: Thursday, March 5, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Feb 23 11:49:43 2026 |
|---|
| Description: | Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app
User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app.
More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues.
Current status: We've completed the disablement of the root detection capability in the Android Microsoft Defender for Endpoint app. We're continuing to investigate the most efficient method to correct the functionality before re-enabling the feature.
Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted.
Start time: Friday, January 9, 2026, at 12:00 AM UTC
Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact.
Next update by: Friday, February 27, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Feb 23 00:49:14 2026 |
|---|
| Description: | Title: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app
User impact: Users and admins may not receive new root detection alerts from the Android Microsoft Defender for Endpoint app.
More info: The Android Microsoft Defender for Endpoint app will no longer generate new root detection alerts during the rollback process. All other Android Microsoft Defender for Endpoint protections remain active and unaffected. Existing root detection alerts will not be removed and should be manually resolved if needed to avoid compliance or access issues.
Current status: We've identified that the root detection feature on Android, which is currently in preview, has inconsistent detection behavior and is resulting in impact. We're in the process of rolling back the root detection capability in the Android Microsoft Defender for Endpoint app across all environments to improve overall service stability. We initiated the rollback process on February 23, 2026, at 4:30 AM UTC and is expected to complete within approximately 12 hours, with full propagation by February 23, 2026, at 4:30 PM UTC.
Scope of impact: Users and admins expecting to receive new root detection alerts from the Android Microsoft Defender for Endpoint app may be impacted.
Start time: Friday, January 9, 2026, at 12:00 AM UTC
Root cause: The root detection feature on Android, which is currently in preview, has been identified with inconsistent detection behavior and is resulting in impact.
Next update by: Monday, February 23, 2026, at 6:00 PM UTC
|
|---|
|
PB1248171 - Some users may have been unable to run SQL queries in Data Warehouse within Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Fri Mar 6 00:57:00 2026 |
|---|
| End Time: | Wed Mar 11 06:25:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 11 09:03:14 2026 |
|---|
| Root Cause: | A recent service change for Microsoft Fabric to optimize authentication infrastructure pathways introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 11 08:56:29 2026 |
|---|
| Description: | Title: Some users may have been unable to run SQL queries in Data Warehouse within Microsoft Fabric
User impact: Users may have been unable to run SQL queries in Data Warehouse within Microsoft Fabric.
More info: Despite having the required access and using delegated mode, affected users may have been unable to run queries in warehouses and received SELECT permission errors.
Final status: We've confirmed after an extended period of monitoring service telemetry that the issue has been fully resolved.
Scope of impact: This issue may have impacted some users attempting to run SQL queries in Data Warehouse in Microsoft Fabric.
Start time: Friday, March 6, 2026, at 5:57 AM UTC
End time: Wednesday, March 11, 2026, at 10:25 AM UTC
Root cause: A recent service change for Microsoft Fabric to optimize authentication infrastructure pathways introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Wed Mar 11 04:29:12 2026 |
|---|
| Description: | Title: Some users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric
User impact: Users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric.
More info: Despite having the required access and using delegated mode, affected users may be unable to run queries in warehouses and receive SELECT permission errors.
Current status: Our previous update had incorrectly indicated that the deployment had completed. We're continuing the deployment process to mitigate the offending change, and we're conducting an extended period of monitoring service telemetry, to ensure that the issue is fully resolved.
Scope of impact: This issue may impact some users attempting to run SQL queries in Data Warehouse in Microsoft Fabric. This section may be updated as the investigation progresses.
Start time: Friday, March 6, 2026, at 5:57 AM UTC
Root cause: A recent service change for Microsoft Fabric to optimize authentication infrastructure pathways has introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries.
Next update by: Wednesday, March 11, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Wed Mar 11 02:23:20 2026 |
|---|
| Description: | Title: Some users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric
User impact: Users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric.
More info: Despite having the required access and using delegated mode, affected users may be unable to run queries in warehouses and receive SELECT permission errors.
Current status: As the rollout which is intended to disable the offending change has completed, we’re in the process of validating that impact is fully resolved and additional mitigations will not be required.
Scope of impact: This issue may impact some users attempting to run SQL queries in Data Warehouse in Microsoft Fabric. This section may be updated as the investigation progresses.
Start time: Friday, March 6, 2026, at 5:57 AM UTC
Root cause: A recent service change for Microsoft Fabric to optimize authentication infrastructure pathways has introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries.
Next update by: Wednesday, March 11, 2026, at 8:30 AM UTC
|
|---|
|
| Time: | Tue Mar 10 19:10:24 2026 |
|---|
| Description: | Title: Some users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric
User impact: Users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric.
More info: Despite having the required access and using delegated mode, affected users may be unable to run queries in warehouses and receive SELECT permission errors.
Current status: We're continuing to monitor the rollout disabling the offending change and anticipate this may have fully taken effect, remediating impact, by our next scheduled update.
Scope of impact: This issue may impact some users attempting to run SQL queries in Data Warehouse in Microsoft Fabric. This section may be updated as the investigation progresses.
Start time: Friday, March 6, 2026, at 5:57 AM UTC
Root cause: A recent service change for Microsoft Fabric to optimize authentication infrastructure pathways has introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries.
Next update by: Wednesday, March 11, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Tue Mar 10 16:45:50 2026 |
|---|
| Description: | Title: Some users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric
User impact: Users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric.
More info: Despite having the required access and using delegated mode, affected users may be unable to run queries in warehouses and receive SELECT permission errors.
Current status: Upon further review, we've again updated the "Start time" field to better reflect when affected users first began to see SQL query failures due to the offending service change. We're monitoring as the offending change is disabled across affected regions and we will provide a timeline to remediation at the time of our next scheduled update.
Scope of impact: This issue may impact some users attempting to run SQL queries in Data Warehouse in Microsoft Fabric. This section may be updated as the investigation progresses.
Start time: Friday, March 6, 2026, at 5:57 AM UTC
Root cause: A recent service change for Microsoft Fabric to optimize authentication infrastructure pathways has introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries.
Next update by: Wednesday, March 11, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Mar 10 13:43:14 2026 |
|---|
| Description: | Title: Some users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric
User impact: Users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric.
More info: Despite having the required access and using delegated mode, affected users may be unable to run queries in warehouses and receive SELECT permission errors.
Current status: We've isolated that the offending service change was deployed earlier than initially believed, and we've updated the "Start time" field of our communications to reflect the updated impact start time. We're continuing to monitor as the offending change is disabled across affected regions and we're working to validate a timeline to remediation.
Scope of impact: This issue may impact some users attempting to run SQL queries in Data Warehouse in Microsoft Fabric. This section may be updated as the investigation progresses.
Start time: Thursday, March 5, 2026, at 12:00 AM UTC
Root cause: A recent service change for Microsoft Fabric to optimize authentication infrastructure pathways has introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries.
Next update by: Wednesday, March 11, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Mar 10 11:56:28 2026 |
|---|
| Description: | Title: Some users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric
User impact: Users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric.
More info: Despite having the required access and using delegated mode, affected users may be unable to run queries in warehouses and receive SELECT permission errors.
Current status: We've expanded communications to all potentially affected regions and we've updated the "Title", "User impact", "More info", and "Scope of impact" sections of our communications to reflect this. We're continuing our work to disable the offending service change to remediate impact for users across all affected regions. We aim to provide a timeline to remediation once one becomes available.
Scope of impact: This issue may impact some users attempting to run SQL queries in Data Warehouse in Microsoft Fabric. This section may be updated as the investigation progresses.
Start time: Tuesday, March 10, 2026, at 9:20 AM UTC
Root cause: A recent service change for Microsoft Fabric to optimize authentication infrastructure pathways has introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries.
Next update by: Tuesday, March 10, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Tue Mar 10 11:21:21 2026 |
|---|
| Description: | Title: Some users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric
User impact: Users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric.
More info: Despite having the required access and using delegated mode, affected users may be unable to run queries in warehouses and receive SELECT permission errors.
Current status: We've isolated a recent service change for Microsoft Fabric to optimize authentication infrastructure pathways has introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries. We've disabled the offending change for a subset of reporting users and validated that this action successfully remediates impact. We're working to disable the feature for all affected users to fully resolve this issue.
Scope of impact: This issue may impact some users attempting to run SQL queries in Data Warehouse in Microsoft Fabric. This section may be updated as the investigation progresses.
Start time: Tuesday, March 10, 2026, at 9:20 AM UTC
Root cause: A recent service change for Microsoft Fabric to optimize authentication infrastructure pathways has introduced a code error, resulting in permission failures when attempting to evaluate and process SQL queries.
Next update by: Tuesday, March 10, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Tue Mar 10 09:26:17 2026 |
|---|
| Description: | Title: Some users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric
User impact: Users may be unable to run SQL queries in Data Warehouse within Microsoft Fabric.
More info: Despite having the required access and using delegated mode, affected users may be unable to run queries in warehouses and receive SELECT permission errors.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: This issue may impact some users attempting to run SQL queries in Data Warehouse in Microsoft Fabric. This section may be updated as the investigation progresses.
Start time: Tuesday, March 10, 2026, at 9:20 AM UTC
Next update by: Tuesday, March 10, 2026, at 3:30 PM UTC
|
|---|
|
CP1238578 - Users are seeing under reported, inaccurate, or temporarily missing Copilot for Sales data in Microsoft Viva Insights
| Status: | serviceDegradation |
|---|
| Start Time: | Tue Dec 23 07:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 10 19:57:18 2026 |
|---|
| Root Cause: | An upstream service change created mapping issues, which is causing impact. |
|---|
| Next Update: | Friday, March 20, 2026, at 1:00 AM UTC |
|---|
|
Details
| Time: | Tue Mar 10 19:57:18 2026 |
|---|
| Description: | Title: Users are seeing under reported, inaccurate, or temporarily missing Copilot for Sales data in Microsoft Viva Insights
User impact: Users are seeing under reported, inaccurate, or temporarily missing Copilot for Sales data in Microsoft Viva Insights.
More info: This affects the following three Copilot for Sales adoption metrics:
- Generate email draft actions taken using Copilot for Sales
- Review CRM record summary actions taken using Copilot for Sales
- Create CRM record actions taken using Copilot for Sales
Those without a premium Copilot for Sales license aren't included in analyzed population.
Current status: The fix deployment preparations are ongoing, and we continue to anticipate that once the deployment is initiated it will complete by Monday, March 23, 2026.
Scope of impact: Your organization is affected by this event, and users that access Copilot for Sales data in Microsoft Viva Insights are impacted. This information may be updated as our investigation continues.
Start time: Sunday, November 23, 2025, at 12:00 PM UTC
Root cause: An upstream service change created mapping issues, which is causing impact.
Next update by: Friday, March 20, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 19:52:24 2026 |
|---|
| Description: | Title: Users are seeing under reported, inaccurate, or temporarily missing Copilot for Sales data in Microsoft Viva Insights
User impact: Users are seeing under reported, inaccurate, or temporarily missing Copilot for Sales data in Microsoft Viva Insights.
More info: This affects the following three Copilot for Sales adoption metrics:
- Generate email draft actions taken using Copilot for Sales
- Review CRM record summary actions taken using Copilot for Sales
- Create CRM record actions taken using Copilot for Sales
Those without a premium Copilot for Sales license aren't included in analyzed population.
Current status: We're continuing to prepare the fix for deployment. We anticipate this will complete and deployment will begin on Friday, March 20, 2026 and complete by Monday, March 23, 2026.
Scope of impact: Your organization is affected by this event, and users that access Copilot for Sales data in Microsoft Viva Insights are impacted. This information may be updated as our investigation continues.
Start time: Sunday, November 23, 2025, at 12:00 PM UTC
Root cause: An upstream service change created mapping issues, which is causing impact.
Next update by: Wednesday, March 11, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Tue Feb 24 21:11:48 2026 |
|---|
| Description: | Title: Users are seeing under reported, inaccurate, or temporarily missing Copilot for Sales data in Microsoft Viva Insights
User impact: Users are seeing under reported, inaccurate, or temporarily missing Copilot for Sales data in Microsoft Viva Insights.
More info: This affects the following three Copilot for Sales adoption metrics:
- Generate email draft actions taken using Copilot for Sales
- Review CRM record summary actions taken using Copilot for Sales
- Create CRM record actions taken using Copilot for Sales
Those without a premium Copilot for Sales license aren't included in analyzed population.
Current status: We've been alerted to an issue where users are seeing under reported, inaccurate, or temporarily missing Copilot for Sales data in Microsoft Viva Insights. We've identified an upstream service change that has created mapping issues, which is causing impact. We've developed and validated a fix to restore service and are preparing to deploy it to the affected environments. We anticipate the fix will complete by Monday, March 23, 2026, and will monitor as it progresses.
Scope of impact: Your organization is affected by this event, and users that access Copilot for Sales data in Microsoft Viva Insights are impacted.
Start time: Sunday, November 23, 2025, at 12:00 PM UTC
Root cause: An upstream service change created mapping issues, which is causing impact.
Next update by: Wednesday, March 4, 2026, at 2:00 AM UTC
|
|---|
|
CW1247849 - Some users see additional Microsoft 365 Copilot Chat agents available to use
| Status: | serviceRestored |
|---|
| Start Time: | Sun Mar 8 23:30:00 2026 |
|---|
| End Time: | Mon Mar 9 14:08:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 10 17:25:09 2026 |
|---|
| Root Cause: | A recent Copilot Chat service update contained a misconfiguration for returning available agents, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 10 17:25:09 2026 |
|---|
| Description: | Title: Some users see additional Microsoft 365 Copilot Chat agents available to use
User impact: Users may have seen additional Copilot Chat agents available to use.
Final status: We've determined that a recent Copilot Chat service update contained a misconfiguration for returning available agents, resulting in impact. We've reverted the update and confirmed that the additional agents are no longer appearing as available to use.
Scope of impact: This issue may have affected any Copilot Chat user.
Start time: Monday, March 9, 2026, at 3:30 AM UTC
End time: Monday, March 9, 2026, at 6:08 PM UTC
Root cause: A recent Copilot Chat service update contained a misconfiguration for returning available agents, resulting in impact.
Next steps:
- We're reviewing our update testing and validation process to better detect issues such as this prior to deployment as to prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 9 17:36:09 2026 |
|---|
| Description: | Title: Users may see additional Microsoft 365 Copilot Chat agents available to use
User impact: Users may see additional Copilot Chat agents available to use.
More info: The agents are labeled as "bizchat-as-gpt-scenario" and "cwc-as-gpt-scenario."
Current status: We've identified a change to the service that potentially introduced this problem and have rolled it back. We've asked a subset of users to test and confirm that this resolved the issue.
Scope of impact: This issue may affect any Copilot Chat user.
Next update by: Tuesday, March 10, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Mar 9 16:32:04 2026 |
|---|
| Description: | Title: Users may see additional Microsoft 365 Copilot Chat agents available to use
User impact: Users may see additional Microsoft 365 Copilot Chat agents available to use.
More info: The agents are labeled as "bizchat-as-gpt-scenario" and "cwc-as-gpt-scenario."
Current status: We're investigating a potential issue with Microsoft 365 Copilot Chat and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
TM1248323 - Some users may be intermittently unable to create or join meetings or live events in any Microsoft Teams app
| Status: | serviceRestored |
|---|
| Start Time: | Tue Mar 10 09:00:00 2026 |
|---|
| End Time: | Tue Mar 10 12:01:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Mar 10 16:19:56 2026 |
|---|
| Root Cause: | An unexpected increase in create and join request traffic caused some requests to fail and resulted in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 10 15:42:25 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create or join meetings or live events in any Microsoft Teams app
User impact: Users may have been intermittently unable to create or join meetings or live events in any Microsoft Teams app.
More info: Due to the intermittent nature of the issue, subsequent create or join attempts may have been successful.
Final status: While we were in the process of analyzing the failures, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users in North America and Canada attempting to create or join meetings or live events in any Microsoft Teams app may have been impacted.
Start time: Tuesday, March 10, 2026, at 1:00 PM UTC
End time: Tuesday, March 10, 2026, at 4:01 PM UTC
Root cause: An unexpected increase in create and join request traffic caused some requests to fail and resulted in the impact.
Next steps:
- We're continuing our analysis of the requests during the impact window to determine what caused the increase in traffic so we can ensure our infrastructure is adequately bolstered to manage future traffic patterns and prevent this issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 10 15:10:12 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create or join meetings or live events in any Microsoft Teams app
User impact: Users may be intermittently unable to create or join meetings or live events in any Microsoft Teams app.
More info: Due to the intermittent nature of the issue, subsequent create or join attempts may be successful.
Current status: Our initial review of telemetry indicates the impact is no longer occurring. We're investigating the failures which happened during the impact window to isolate the root cause, and in parallel, we're monitoring our telemetry to ensure the issue doesn't reoccur.
Scope of impact: Some users in North America and Canada attempting to create or join meetings or live events in any Microsoft Teams app may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, March 10, 2026, at 1:00 PM UTC
Next update by: Tuesday, March 10, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Mar 10 14:43:30 2026 |
|---|
| Description: | Title: Some users may be intermittently unable to create or join meetings or live events in any Microsoft Teams app
User impact: Users may be intermittently unable to create or join meetings or live events in any Microsoft Teams app.
More info: Due to the intermittent nature of the issue, subsequent create or join attempts may be successful.
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.
|
|---|
|
PL1235137 - Some users may see delays with Microsoft Planner tasks updating to Microsoft To-Do
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 2 19:00:00 2026 |
|---|
| End Time: | Sat Mar 7 05:00:00 2026 |
|---|
| Service: | Planner |
|---|
| Feature Group: | Planner |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 9 17:49:27 2026 |
|---|
| Root Cause: | A processing issue was causing delays within the data pipeline that facilitates Microsoft Planner task updates in Microsoft To-Do, leading to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 9 17:17:21 2026 |
|---|
| Description: | Title: Some users may see delays with Microsoft Planner tasks updating to Microsoft To-Do
User impact: Users may have seen delays with Microsoft Planner tasks updating to Microsoft To-Do.
Final status: We've confirmed that the backlog of remaining event accumulation has been cleared and through telemetry the service shows as healthy again.
Scope of impact: This issue may have impacted some users in the North America and Europe regions who were attempting to get Microsoft Planner tasks updated to Microsoft To-Do.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
End time: Saturday, March 7, 2026, at 10:00 AM UTC
Root cause: A processing issue was causing delays within the data pipeline that facilitates Microsoft Planner task updates in Microsoft To-Do, leading to impact.
Next steps:
- We'll continue to review the data pipeline processing to better understand this event and prevent future similar events.
This is the final update for the event.
|
|---|
|
| Time: | Wed Mar 4 17:32:05 2026 |
|---|
| Description: | Title: Some users may see delays with Microsoft Planner tasks updating to Microsoft To-Do
User impact: Users may see delays with Microsoft Planner tasks updating to Microsoft To-Do.
Current status: We're continuing to monitor the remaining backlog of accumulated events, which is processing slower than initially anticipated. We've been able to confirm that our remediation efforts have eliminated or significantly reduced latency for the majority of affected users, however a portion of users still experience high latencies of up to six hours. We'll provide an updated timeline for the completion of this process for the remaining impacted users as soon as one becomes available.
Scope of impact: This issue may impact some users in the North America and Europe regions who are attempting to get Microsoft Planner tasks updated to Microsoft To-Do.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
Root cause: A processing issue is causing delays within the data pipeline that facilitates Microsoft Planner task updates in Microsoft To-Do, leading to impact.
Next update by: Monday, March 9, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Mon Mar 2 17:29:16 2026 |
|---|
| Description: | Title: Some users may see delays with Microsoft Planner tasks updating to Microsoft To-Do
User impact: Users may see delays with Microsoft Planner tasks updating to Microsoft To-Do.
Current status: We've identified that it's taking longer than anticipated for the remaining backlog of accumulated events to be processed. With the current progress of our remediation efforts, we've confirmed that the latency and delays users are experiencing has drastically reduced from 20 hours, to between 30 minutes and 1 hour. We're continuing to monitor as the remaining backlog of accumulated events are processed to ensure the latency users are experiencing is fully resolved.
Scope of impact: This issue may impact some users in the North America and Europe regions who are attempting to get Microsoft Planner tasks updated to Microsoft To-Do.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
Root cause: A processing issue is causing delays within the data pipeline that facilitates Microsoft Planner task updates in Microsoft To-Do, leading to impact.
Next update by: Thursday, March 5, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 17:22:50 2026 |
|---|
| Description: | Title: Some users may see delays with Microsoft Planner tasks updating to Microsoft To-Do
User impact: Users may see delays with Microsoft Planner tasks updating to Microsoft To-Do.
Current status: The backlog of accumulated events continues to be processed as expected, and we anticipate the backlog will be fully cleared by our next scheduled communications update.
Scope of impact: This issue may impact some users in the North America and Europe regions who are attempting to get Microsoft Planner tasks updated to Microsoft To-Do.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
Estimated time to resolve: We anticipate that the backlog of accumulated requests will be processed and the impact remediated by Tuesday, March 3, 2026, at 12:00 AM UTC.
Root cause: A processing issue is causing delays within the data pipeline that facilitates Microsoft Planner task updates in Microsoft To-Do, leading to impact.
Next update by: Tuesday, March 3, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Tue Feb 24 17:41:29 2026 |
|---|
| Description: | Title: Some users may see delays with Microsoft Planner tasks updating to Microsoft To-Do
User impact: Users may see delays with Microsoft Planner tasks updating to Microsoft To-Do.
Current status: The backlog of events is being processed, though at a slower pace than initially anticipated. We're continuing to monitor the backlog of events as they're processed and to validate what actions we can take to expedite recovery.
Scope of impact: This issue may impact some users in the North America and Europe regions who are attempting to get Microsoft Planner tasks updated to Microsoft To-Do.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
Root cause: A processing issue is causing delays within the data pipeline that facilitates Microsoft Planner task updates in Microsoft To-Do, leading to impact.
Next update by: Saturday, February 28, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Feb 20 17:16:52 2026 |
|---|
| Description: | Title: Some users may see delays with Microsoft Planner tasks updating to Microsoft To-Do
User impact: Users may see delays with Microsoft Planner tasks updating to Microsoft To-Do.
Current status: We're continuing to monitor the backlog of events as they process and return to normal service levels in order to validate that impact is fully remediated. We expect this backlog process and full remediation to complete by our next scheduled update.
Scope of impact: This issue may impact some users in the North America and Europe regions who are attempting to get Microsoft Planner tasks updated to Microsoft To-Do.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
Root cause: A processing issue is causing delays within the data pipeline that facilitates Microsoft Planner task updates in Microsoft To-Do, leading to impact.
Next update by: Wednesday, February 25, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Feb 19 21:02:12 2026 |
|---|
| Description: | Title: Some users may see delays with Microsoft Planner tasks updating to Microsoft To-Do
User impact: Users may see delays with Microsoft Planner tasks updating to Microsoft To-Do.
Current status: We identified an issue that’s causing delays within the data pipeline that facilitates Microsoft Planner task updates in Microsoft To-Do, leading to impact. We can see that the backlog of events is processing and that the service health is improving. We'll continue monitoring the backlog processing to validate that the impact is remediated.
Scope of impact: This issue may impact some users in the North America and Europe regions who are attempting to get Microsoft Planner tasks updated to Microsoft To-Do.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
Root cause: A processing issue is causing delays within the data pipeline that facilitates Microsoft Planner task updates in Microsoft To-Do, leading to impact.
Next update by: Saturday, February 21, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Thu Feb 19 20:28:38 2026 |
|---|
| Description: | Title: Some users may see delays with Microsoft Planner tasks updating to Microsoft To-Do
User impact: Users may see delays with Microsoft Planner tasks updating to Microsoft To-Do.
Current status: We're investigating a potential issue with Microsoft Planner and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
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 Mar 9 17:48:06 2026 |
|---|
| Root Cause: | An influx of automated email traffic from Power BI subscriptions is resulting in impact to external subscription email delivery. |
|---|
| Next Update: | Monday, March 23, 2026, at 11:30 PM UTC |
|---|
|
Details
| Time: | Mon Mar 9 17:48:06 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: Due to the complexity of the issue, the development of our code fix to restore subscription mail flow is taking an extended period of time to complete. We'll provide a timeline for its completion and deployment as one becomes available.
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: Monday, March 23, 2026, at 11:30 PM UTC
|
|---|
|
| Time: | Mon Feb 23 18:11:45 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: The development of our code fix to restore subscription mail flow to external users is progressing. We're expecting an estimated timeline for the deployment of our fix, and the remediation of the impact will be available once our new solution has been tested and verified as a viable solution for remediating the impact.
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: Monday, March 9, 2026, at 12:30 AM UTC
|
|---|
|
| 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
|
|---|
|
CW1218323 - Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message
| Status: | serviceDegradation |
|---|
| Start Time: | Fri Dec 19 13:00:00 2025 |
|---|
| End Time: | N/A |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 9 16:41:46 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: | Wednesday, March 18, 2026, at 10:00 PM UTC |
|---|
|
Details
| Time: | Mon Mar 9 16:41: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: As an optional work around, affected users can use the Copy button to transfer a generated draft from Copilot chat to Outlook, and continue their work. If your organization has enabled Copilot access within Outlook, the user can continue using Copilot to draft an email once they've moved to Outlook.
Current status: We've implemented performance optimizations to assist with improving the slow request response times, and we're now continuing our re-enablement of the "Edit in Outlook" button across the remaining 50 percent of affected environments. We anticipate this re-enablement to be completed by Sunday, March 22, 2026 and we'll update on the progress of this action in our next communication.
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
Estimated time to resolve: We anticipate impact to be remediated by Sunday, March 22, 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 by: Wednesday, March 18, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Feb 23 15:53:09 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: As an optional work around, affected users can use the Copy button to transfer a generated draft from Copilot chat to Outlook, and continue their work. If your organization has enabled Copilot access within Outlook, the user can continue using Copilot to draft an email once they've moved to Outlook.
Current status: Our work to improve the slow request response times continues. We're ensuring that the improvement process will not cause any additional service issues before we re-enable the feature. We anticipate being able to have a solution ready by Friday, March 20, 2026. We will provide any available updates to the progress at next scheduled communication time.
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, March 9, 2026, at 10:00 PM UTC
|
|---|
|
| 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.
|
|---|
|
EX1237864 - Users' auto-decline meeting settings for automatic replies may not be working in Exchange Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 23 03:00:00 2026 |
|---|
| End Time: | Fri Mar 6 13:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Mar 6 15:29:15 2026 |
|---|
| Root Cause: | A latent code issue triggered by a recent service configuration update was resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Mar 6 15:29:15 2026 |
|---|
| Description: | Title: Users' auto-decline meeting settings for automatic replies may not be working in Exchange Online
User impact: Users' auto-decline meeting settings for automatic replies may have not been working in Exchange Online.
Final status: We've completed the deployment of our code fix and confirmed it has saturated throughout the affected environment, remediating impact for all users.
Scope of impact: Users with automatic replies set up to auto-decline meeting invites in Exchange Online may have been impacted.
Start time: Monday, February 23, 2026, at 8:00 AM UTC
End time: Friday, March 6, 2026, at 6:00 PM UTC
Root cause: A latent code issue triggered by a recent service configuration update was resulting in impact.
Next steps:
- We're reviewing our update testing and validation procedures to identify opportunities to better detect impact and prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 2 17:55:58 2026 |
|---|
| Description: | Title: Users' auto-decline meeting settings for automatic replies may not be working in Exchange Online
User impact: Users' auto-decline meeting settings for automatic replies may not be working in Exchange Online.
Current status: Our code fix continues to roll out and has saturated approximately 93% of the environment, and some users may already see mitigation of this issue. At our next communication, which is when we estimate this deployment will conclude, we'll provide an additional update regarding the status of the code fix saturation to all affected users.
Scope of impact: Users with automatic replies set up to auto-decline meeting invites in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, February 23, 2026, at 8:00 AM UTC
Root cause: A latent code issue triggered by a recent service configuration update is resulting in impact.
Next update by: Friday, March 6, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Mon Feb 23 21:23:30 2026 |
|---|
| Description: | Title: Users' auto-decline meeting settings for automatic replies may not be working in Exchange Online
User impact: Users' auto-decline meeting settings for automatic replies may not be working in Exchange Online.
Current status: We've identified through internal monitoring that users' auto-decline meeting settings may be failing to apply, resulting in users' incoming meeting invites not being auto-declined as expected due to a latent code issue triggered by a recent service configuration update. We're working to roll out a code fix that we anticipate should be in effect by our next scheduled update.
Scope of impact: Users with automatic replies set up to auto-decline meeting invites in Exchange Online may be impacted. This information may be updated as our investigation continues.
Start time: Monday, February 23, 2026, at 8:00 AM UTC
Root cause: A latent code issue triggered by a recent service configuration update is resulting in impact.
Next update by: Tuesday, March 3, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Feb 23 21:10:12 2026 |
|---|
| Description: | Title: Users' auto-decline meeting settings for automatic replies may not be working in Exchange Online
User impact: Users' auto-decline meeting settings for automatic replies may not be working in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
MP1240709 - Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 23 03:00:00 2026 |
|---|
| End Time: | Thu Mar 5 05:50:00 2026 |
|---|
| Service: | Microsoft Purview |
|---|
| Feature Group: | Microsoft Purview |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Mar 5 18:32:41 2026 |
|---|
| Root Cause: | A recent service update to improve our event driven programming produced an impacting calendar configuration issue. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 5 18:32:41 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not have been implemented as expected.
More info: This may have impacted changes to the following policies made from Wednesday, February 25, 2026, through Thursday, March 5, 2026:
- Sensitivity Labels
- Microsoft Purview Data Loss Prevention (DLP) policies
- Holds, including custom holds
- Retention Policies
- Insider Risk Management
- Optical Character Recognition (OCR) policies
Additionally, admins may not have been notified if the policies didn't sync as expected.
Final status: We've determined that a recent service update had introduced an impacting calendar configuration issue that was preventing admin updates from being implemented via the Microsoft Purview compliance portal. After our deployment of a fix to correct the isolated calendar configuration issue, our internal service telemetry validated that impact had been remediated.
Scope of impact: Admins who attempted to update policies in the Microsoft Purview compliance portal may not have been able to do so.
Start time: Monday, February 23, 2026, at 8:00 AM UTC
End time: Thursday, March 5, 2026, at 10:50 AM UTC
Root cause: A recent service update to improve our event driven programming produced an impacting calendar configuration issue.
Next steps:
- We're further analyzing the offending service update and impacting calendar configuration issues to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Wed Mar 4 20:27:54 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: This may impact changes to the following policies made since Wednesday, February 25, 2026:
- Sensitivity Labels
- Microsoft Purview Data Loss Prevention (DLP) policies
- Holds, including custom holds
- Retention Policies
- Insider Risk Management
- Optical Character Recognition (OCR) policies
Additionally, admins may not be notified if the policies don’t sync as expected.
Current status: The fix designed to update the code of a specific component change has reached a threshold in which we're able to begin resyncing the previously unsuccessful policy updates. We're about halfway through the resyncing process, which we expect to complete by our next scheduled update.
Scope of impact: Admins who attempt to update policies in the Microsoft Purview compliance portal may not be able to do so. This information may be updated as our investigation continues.
Next update by: Friday, March 6, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Mar 3 20:53:12 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: This may impact changes to the following policies made since Wednesday, February 25, 2026:
- Sensitivity Labels
- Microsoft Purview Data Loss Prevention (DLP) policies
- Holds, including custom holds
- Retention Policies
- Insider Risk Management
- Optical Character Recognition (OCR) policies
Additionally, admins may not be notified if the policies don’t sync as expected.
Current status: We’ve observed that the fix designed to update the code of a specific component change has reached 92% of the affected environment, and we expect that the remainder of this process will be complete by our next scheduled update. The completion of this process will illuminate the manifestation point of impact and validate our root cause theory.
Scope of impact: Admins who attempt to update policies in the Microsoft Purview compliance portal may not be able to do so. This information may be updated as our investigation continues.
Next update by: Thursday, March 5, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Mon Mar 2 14:46:49 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: This may impact changes to the following policies made since Wednesday, February 25, 2026:
- Sensitivity Labels
- Microsoft Purview Data Loss Prevention (DLP) policies
- Holds, including custom holds
- Retention Policies
- Insider Risk Management
- Optical Character Recognition (OCR) policies
Additionally, admins may not be notified if the policies don’t sync as expected.
Current status: We've confirmed the fix is having the desired effect. We're currently deploying the fix to the rest of the affected environments and continuing to monitor its progress. We'll provide additional updates on its progress in our next communication.
Scope of impact: Admins who attempt to update policies in the Microsoft Purview compliance portal may not be able to do so. This information may be updated as our investigation continues.
Next update by: Wednesday, March 4, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Sun Mar 1 22:35:16 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: This may impact changes to the following policies made since Wednesday, February 25, 2026:
- Sensitivity Labels
- Microsoft Purview Data Loss Prevention (DLP) policies
- Holds, including custom holds
- Retention Policies
- Insider Risk Management
- Optical Character Recognition (OCR) policies
Additionally, admins aren’t notified if the policies don’t sync as expected.
Current status: While in the process of deploying the fix to a test environment, we uncovered a problem in our fix deployment pipeline. We've since resolved this pipeline issue and have deployed the fix to our test environment, which we'll monitor overnight and ensure that the fix has the desired effect.
Scope of impact: Admins who attempt to update to policies in the Microsoft Purview compliance portal may not be able to do so. This information may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Sun Mar 1 20:28:34 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: This may impact changes to the following policies made since Wednesday, February 25, 2026:
- Sensitivity Labels
- Microsoft Purview Data Loss Prevention (DLP) policies
- Holds, including custom holds
- Retention Policies
- Insider Risk Management
- Optical Character Recognition (OCR) policies
Additionally, admins aren’t notified if the policies don’t sync as expected.
Current status: We're continuing to monitor as the fix to address the offending component change is deployed to our internal testing environment. Once the deployment completes, we'll perform validations to ensure it remediates impact as expected, and we'll aim to provide a resolution timeline once available.
Scope of impact: Admins who attempt to update to policies in the Microsoft Purview compliance portal may not be able to do so. This information may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Sat Feb 28 13:03:54 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: This may impact changes to the following policies made since Wednesday, February 25, 2026:
- Sensitivity Labels
- Microsoft Purview Data Loss Prevention (DLP) policies
- Holds, including custom holds
- Retention Policies
- Insider Risk Management
- Optical Character Recognition (OCR) policies
Additionally, admins aren’t notified if the policies don’t sync as expected.
Current status: We've updated the More info section of this communication as further investigation has identified additional Microsoft Purview policy types that may be impacted.
We’ve isolated a specific component change that we suspect is causing the impact. We’ve developed a fix to address this change and we're deploying it to our internal test environment to validate that the fix is a viable remediation plan. We’ll aim to provide a timeline for completing internal validations by our next scheduled communications update.
Scope of impact: Admins who attempt to update to policies in the Microsoft Purview compliance portal may not be able to do so.
Next update by: Monday, March 2, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 21:06:43 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: This may impact changes to the following policies made since Wednesday, February 25, 2026:
-Sensitivity Labels
-Microsoft Purview Data Loss Prevention (DLP) policies
-Holds
-Custom Tags
Additionally, admins aren’t notified if the policies don’t sync as expected.
Current status: We're pursuing multiple workstreams aimed at better understanding the nature of the issue, including generation of policies within an internal testing environment. In parallel, we're continuing our work to validate that previous component changes are the source of impact so as to generate an effective code fix.
Scope of impact: Admins who attempt to update to policies in the Microsoft Purview compliance portal may not be able to do so.
Next update by: Saturday, February 28, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Feb 27 20:12:16 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: This may impact changes to the following policies made since Wednesday, February 25, 2026:
-Sensitivity Labels
-Microsoft Purview Data Loss Prevention (DLP) policies
-Holds
-Custom Tags
Additionally, admins aren’t notified if the policies don’t sync as expected.
Current status: We're continuing to validate whether the previously mentioned component changes are the source of impact as well as developing and testing a code fix.
Scope of impact: Admins who attempt to update to policies in the Microsoft Purview compliance portal may not be able to do so.
Next update by: Saturday, February 28, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 18:19:52 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: This may impact changes to the following policies made since Wednesday, February 25, 2026:
-Sensitivity Labels
-Microsoft Purview Data Loss Prevention (DLP) policies
-Holds
-Custom Tags
Additionally, admins aren’t notified if the policies don’t sync as expected.
Current status: We've identified some components of a recent update may have changed event handling for the affected policies, resulting in this impacting event. We're validating whether this is the source of this problem and testing some code fixes that are directed towards remediating this issue.
Scope of impact: Admins who attempt to update to policies in the Microsoft Purview compliance portal may not be able to do so.
Next update by: Saturday, February 28, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Feb 27 17:18:02 2026 |
|---|
| Description: | Title: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected
User impact: Admin updates to the Microsoft Purview compliance portal may not be implemented as expected.
More info: More info: This may impact new changes to policies such as:
-Sensitivity Labels
-Microsoft Purview Data Loss Prevention (DLP) policies
-Holds
-Custom Tags
Additionally, admins aren’t notified if the policies don’t sync as expected.
Current status: We're investigating the back-end service code updates to determine if any recent changes are responsible for this impacting event.
Scope of impact: Admins who attempt to update to policies in the Microsoft Purview compliance portal may not be able to do so.
Next update by: Friday, February 27, 2026, at 11:30 AM UTC
|
|---|
|
PB1232111 - Users may see incorrect data in reports and downstream apps using result set caching in Microsoft Fabric
| Status: | serviceRestored |
|---|
| Start Time: | Sun Jun 15 20:00:00 2025 |
|---|
| End Time: | Sat Feb 14 20:00:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 5 15:43:16 2026 |
|---|
| Root Cause: | A code issue with the result set caching feature in Microsoft Fabric was causing incorrect results with certain queries in Fabric Data Warehouse and Lakehouse SQL Analytics Endpoint, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 5 15:43:16 2026 |
|---|
| Description: | Title: Users may see incorrect data in reports and downstream apps using result set caching in Microsoft Fabric
User impact: Users may have seen incorrect data in reports and downstream apps using result set caching in Microsoft Fabric.
More info: This issue specifically impacted results with the queries in Fabric Data Warehouse and SQL Analytics Endpoint when the result set caching feature was active. The results may have included incorrect cached items or excluded relevant cached items.
We disabled the result set caching feature as of February 16, 2026, to prevent any confusion or misinterpretation of results. For any reports or downstream apps using cached results on or prior to February 16, 2026, from the Data Warehouse or SQL Analytics Endpoints, users will need to manually refresh to obtain relevant results. This will ensure that these other apps don't continue to work with potentially incorrect results.
You can also find further information here:
support.fabric.microsoft.com/known-issues/?product=Data%2520Warehouse&active=true&fixed=true&sort=published&issueId=1729
Final status: We confirmed that disabling the result set caching feature has prevented the problem from spreading further. While we expect that we'll have a fix deployed at the end of April 2026, users will need to manually refresh the affected reports and downstream apps as outlined in the More info section to remediate the issue until that time. Please reach out to a support representative for additional help with manually refreshing the reports and apps or if the manual refresh isn't successful in providing the appropriate results.
Scope of impact: This issue may have potentially impacted any user utilizing result set caching in Microsoft Fabric.
Start time: Monday, June 16, 2025, at 12:00 AM UTC
End time: Sunday, February 15, 2026, at 1:00 AM UTC
Root cause: A code issue with the result set caching feature in Microsoft Fabric was causing incorrect results with certain queries in Fabric Data Warehouse and Lakehouse SQL Analytics Endpoint, which resulted in impact.
Next steps:
- We're continuing to develop a long-term fix to fully resolve the result set caching feature issue and restore query result accuracy for both Fabric Data Warehouse and SQL Analytics Endpoint. We anticipate that this long-term fix development and safe deployment process will complete by Thursday, April 30, 2026.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 26 14:45:45 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 SQL Analytics Endpoint.
While the feature remains disabled, we encourage users to manually refresh any reports, downstream apps, or both that may be using cached results from February 16, 2026, or earlier from the Data Warehouse or SQL Analytics Endpoints. This will ensure that these other apps don't continue to work with potentially incorrect results.
For more information, please see the known-issues page for this event here:
support.fabric.microsoft.com/known-issues/?product=Data%2520Warehouse&active=true&fixed=true&sort=published&issueId=1729
Current status: We’re continuing to work on a long-term fix to allow us to re-enable the result set caching feature at a later date, and we recommend that users follow the steps listed in the More info, if not done so already.
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: Thursday, March 5, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Thu Feb 19 14:50:07 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 SQL Analytics Endpoint.
Users should manually refresh any reports and/or downstream applications that may be using cached results from the Data Warehouse or SQL Analytics Endpoints, to ensure that these other applications don't continue to work with potentially incorrect results.
Current status: While the feature remains disabled, we encourage users to manually refresh any reports and/or downstream applications that may be using cached results from the Data Warehouse or SQL Analytics Endpoints, to ensure that these other applications don't continue to work with potentially incorrect results.
For more information, please see the known-issues page for this event here:
support.fabric.microsoft.com/known-issues/?product=Data%2520Warehouse&active=true&fixed=true&sort=published&issueId=1729
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: Thursday, February 26, 2026, at 9:00 PM UTC
|
|---|
|
| Time: | Tue Feb 17 15:20:48 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: To prevent inaccurate results being generated, we've disabled this feature while we work on a long-term fix.
For more information, please see the known-issues page for this event here:
support.fabric.microsoft.com/known-issues/?product=Data%2520Warehouse&active=true&fixed=true&sort=published&issueId=1729
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: Thursday, February 19, 2026, at 9:00 PM UTC
|
|---|
|
| 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
|
|---|
|
MO1239876 - Admins may have received delayed mailbox usage reports from the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Sat Feb 21 08:00:00 2026 |
|---|
| End Time: | Thu Mar 5 06:00:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Administration |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Mar 5 09:17:23 2026 |
|---|
| Root Cause: | A malformed data issue within the pipeline responsible for timely report data in the admin center was resulting in mailbox usage report delays. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Mar 5 09:17:23 2026 |
|---|
| Description: | Title: Admins may have received delayed mailbox usage reports from the Microsoft 365 admin center
User impact: Admins may have received delayed mailbox usage reports from the Microsoft 365 admin center.
More info: Admins' mailbox usage reports may have been delayed as far back as Tuesday, February 17, 2026.
Final status: We've confirmed that the reports for Microsoft 365 Groups have been processed. We've verified with affected users that impact has now been resolved.
Scope of impact: Any admin attempting to view mailbox usage reports in the Microsoft 365 admin center may have been impacted.
Start time: Saturday, February 21, 2026, at 1:00 PM UTC
End time: Thursday, March 5, 2026, at 11:00 AM UTC
Root cause: A malformed data issue within the pipeline responsible for timely report data in the admin center was resulting in mailbox usage report delays.
Next steps:
- We're analyzing the affected pipeline that handles report data to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 3 11:02:12 2026 |
|---|
| Description: | Title: Admins may receive delayed mailbox usage reports from the Microsoft 365 admin center
User impact: Admins may receive delayed mailbox usage reports from the Microsoft 365 admin center.
More info: Admins' mailbox usage reports may be delayed as far back as Tuesday, February 17, 2026.
Current status: The mailbox usage reports has completed processing for some users, but the Microsoft 365 Groups reporting is still in progress. We expect that all reports will be available by the time of our next update.
Scope of impact: Any admin attempting to view mailbox usage reports in the Microsoft 365 admin center may be impacted.
Start time: Saturday, February 21, 2026, at 1:00 PM UTC
Root cause: A malformed data issue within the pipeline responsible for timely report data in the admin center is resulting in mailbox usage report delays.
Next update by: Thursday, March 5, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Mon Mar 2 10:16:16 2026 |
|---|
| Description: | Title: Admins may receive delayed mailbox usage reports from the Microsoft 365 admin center
User impact: Admins may receive delayed mailbox usage reports from the Microsoft 365 admin center.
Current status: We've completed deploying the fix and anticipate affected pipeline will have recovered by our next scheduled update.
Scope of impact: This issue may potentially affect any admin attempting to view mailbox usage reports in the Microsoft 365 admin center.
Start time: Saturday, February 21, 2026, at 1:00 PM UTC
Root cause: A malformed data issue within the pipeline responsible for timely report data in the admin center is resulting in mailbox usage report delays.
Next update by: Tuesday, March 3, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Fri Feb 27 14:04:02 2026 |
|---|
| Description: | Title: Admins may receive delayed mailbox usage reports from the Microsoft 365 admin center
User impact: Admins may receive delayed mailbox usage reports from the Microsoft 365 admin center.
Current status: We're completing the final validations on our fix to address this malformed data issue and deployment will begin soon. We anticipate that this fix will have completed its deployment to all affected environments by our next scheduled update.
Scope of impact: This issue may potentially affect any admin attempting to view mailbox usage reports in the Microsoft 365 admin center.
Start time: Saturday, February 21, 2026, at 1:00 PM UTC
Root cause: A malformed data issue within the pipeline responsible for timely report data in the admin center is resulting in mailbox usage report delays.
Next update by: Monday, March 2, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Feb 26 16:39:59 2026 |
|---|
| Description: | Title: Admins may receive delayed mailbox usage reports from the Microsoft 365 admin center
User impact: Admins may receive delayed mailbox usage reports from the Microsoft 365 admin center.
Current status: We identified a malformed data issue within the pipeline responsible for timely report data in the admin center, resulting in mailbox usage report delays. We're currently developing a fix to address this underlying root cause and will provide a status on its progress by our next scheduled update.
Scope of impact: This issue may potentially affect any admin attempting to view mailbox usage reports in the Microsoft 365 admin center.
Start time: Saturday, February 21, 2026, at 1:00 PM UTC
Root cause: A malformed data issue within the pipeline responsible for timely report data in the admin center is resulting in mailbox usage report delays.
Next update by: Friday, February 27, 2026, at 8:30 PM UTC
|
|---|
|
TM1243338 - Admins may be unable to load the Microsoft Teams Call Quality Dashboard from the admin center or by URL with "/Activate"
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 26 21:00:00 2026 |
|---|
| End Time: | Wed Mar 4 17:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Mar 4 21:04:57 2026 |
|---|
| Root Cause: | A recent update to a new authentication code library was missing a necessary dependency that was preventing admins from accessing the Microsoft Teams Call Quality Dashboard when "/Activate" was within the URL, including attempts through the Microsoft Teams admin center. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 4 21:04:57 2026 |
|---|
| Description: | Title: Admins may be unable to load the Microsoft Teams Call Quality Dashboard from the admin center or by URL with "/Activate"
User impact: Admins may have been unable to load the Call Quality Dashboard from the admin center or by URL with "/Activate".
More info: This issue specifically affected access to the Call Quality Dashboard with URLs containing "/Activate", which included admin center UI attempts, and admins were presented with an error stating, "Something went wrong, please refresh the page and try again."
While we focused on remediation, admins could circumvent the impact by navigating to the Call Quality Dashboard using "https://cqd.teams.cloud.microsoft" specifically.
Final status: The rollback of the offending deployment completed and after a period of monitoring, we confirmed impact is remediated.
Scope of impact: This issue may have affected any admin accessing the Microsoft Teams Call Quality Dashboard when "/Activate" was within the URL, which included attempts through the Microsoft Teams admin center.
Start time: Friday, February 27, 2026, at 2:00 AM UTC
End time: Wednesday, March 4, 2026, at 10:30 PM UTC
Root cause: A recent update to a new authentication code library was missing a necessary dependency that was preventing admins from accessing the Microsoft Teams Call Quality Dashboard when "/Activate" was within the URL, including attempts through the Microsoft Teams admin center.
Next steps:
- To help prevent similar impact in the future, we're further reviewing our update release procedures to identify dependency issues before being deployed.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 3 21:05:47 2026 |
|---|
| Description: | Title: Admins may be unable to load the Microsoft Teams Call Quality Dashboard from the admin center or by URL with "/Activate"
User impact: Admins may be unable to load the Call Quality Dashboard from the admin center or by URL with "/Activate".
More info: This issue specifically affects access to the Call Quality Dashboard with URLs containing "/Activate", which includes admin center UI attempts, and admins are presented an error stating, "Something went wrong, please refresh the page and try again."
While we're focused on remediation, admins can circumvent the impact by navigating to the Call Quality Dashboard using "https://cqd.teams.cloud.microsoft" specifically.
Current status: The rollback of the update hasn't saturated as quickly as anticipated and will need additional time. We'll provide an updated completion timeline when one becomes available.
Scope of impact: This issue may affect any admin accessing the Microsoft Teams Call Quality Dashboard when "/Activate" is within the URL, which includes attempts through the Microsoft Teams admin center.
Start time: Friday, February 27, 2026, at 2:00 AM UTC
Root cause: A recent update to a new authentication code library is missing a necessary dependency that's preventing admins from accessing the Microsoft Teams Call Quality Dashboard when "/Activate" is within the URL, including attempts through the Microsoft Teams admin center.
Next update by: Thursday, March 5, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Mar 3 15:51:25 2026 |
|---|
| Description: | Title: Admins may be unable to load the Microsoft Teams Call Quality Dashboard from the admin center or by URL with "/Activate"
User impact: Admins may be unable to load the Call Quality Dashboard from the admin center or by URL with "/Activate".
More info: This issue specifically affects access to the Call Quality Dashboard with URLs containing "/Activate", which includes admin center UI attempts, and admins are presented an error stating, "Something went wrong, please refresh the page and try again."
While we're focused on remediation, admins can circumvent the impact by navigating to the Call Quality Dashboard using "https://cqd.teams.cloud.microsoft" specifically.
Current status: Our rollback of the update is requiring more time than initially anticipated, and our updated reversion timeline reports that it will be complete by our next scheduled communication update.
Scope of impact: This issue may affect any admin accessing the Microsoft Teams Call Quality Dashboard when "/Activate" is within the URL, which includes attempts through the Microsoft Teams admin center.
Start time: Friday, February 27, 2026, at 2:00 AM UTC
Root cause: A recent update to a new authentication code library is missing a necessary dependency that's preventing admins from accessing the Microsoft Teams Call Quality Dashboard when "/Activate" is within the URL, including attempts through the Microsoft Teams admin center.
Next update by: Wednesday, March 4, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Tue Mar 3 12:41:24 2026 |
|---|
| Description: | Title: Admins may be unable to load the Microsoft Teams Call Quality Dashboard from the admin center or by URL with "/Activate"
User impact: Admins may be unable to load the Call Quality Dashboard from the admin center or by URL with "/Activate".
More info: This issue specifically affects access to the Call Quality Dashboard with URLs containing "/Activate", which includes admin center UI attempts, and admins are presented an error stating, "Something went wrong, please refresh the page and try again."
While we're focused on remediation, admins can workaround the problem by navigating to the Call Quality Dashboard using "https://cqd.teams.cloud.microsoft" specifically.
Current status: We've identified the issue is due to a recent update to a new authentication code library, though why this update is resulting in this impact is under investigation. We're rolling back this update, which could complete by Tuesday, March 3, 2026, at 10:00 PM UTC.
Scope of impact: This issue may affect any admin accessing the Microsoft Teams Call Quality Dashboard when "/Activate" is within the URL, which includes attempts through the Microsoft Teams admin center.
Start time: Friday, February 27, 2026, at 2:00 AM UTC
Estimated time to resolve: The update rollback may complete and remediate impact by Tuesday, March 3, 2026, at 10:00 PM UTC.
Root cause: A recent update to a new authentication code library contains an issue that's resulting in this impact.
Next update by: Tuesday, March 3, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Tue Mar 3 12:02:20 2026 |
|---|
| Description: | Title: Admins may be unable to load the Microsoft Teams Call Quality Dashboard from the admin center or by URL with "/Activate"
User impact: Admins may be unable to load the Call Quality Dashboard from the admin center or by URL with "/Activate".
More info: Admins may be presented an error stating, "Something went wrong, please refresh the page and try again."
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 60 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: | Wed Mar 4 19:08:37 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: | Wed Mar 4 19:08:37 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Mar 3 07:01:10 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Mar 2 19:47:19 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jan 30 07:15:30 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:39:48 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:11:05 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:08:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Jan 29 19:07:54 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Jan 27 07:47:39 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Jan 26 19:58:56 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Jan 23 01:27:30 2026 |
|---|
| Description: | Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may have seen degraded service functionality or were unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions included, but were not limited to:
- Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
- Collecting message traces in Exchange Online.
- Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams.
- Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
- Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may have been unable to create breakout rooms or Microsoft Teams live events.
- Receiving presence or location information in Microsoft Teams.
- Existing or new meeting options for Facilitator in Teams may not have been honored.
- Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
- Print registration and printer jobs may have failed in Universal Print.
- Microsoft To Do users may have experienced synchronization issues, preventing tasks from updating across devices. Additionally, tasks created in Shared Lists may not have appeared for collaborators.
- Microsoft Defender for Cloud Apps users may not have been able to view insights or view, create, or update OAuth enabled app policies. Reporting data may have also appeared blank, even though no errors were shown.
- Microsoft Defender for Office (MDO) users may have experienced limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection.
- Microsoft Power Automate users may have been unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Final status: We’ve confirmed that the affected infrastructure has returned to a healthy state and is operating as expected. We’ll continue to closely monitor the remediation actions taken and make any necessary adjustments to maintain stability. If users experience any residual issues, clearing local DNS caches or temporarily lowering DNS TTL values may help ensure a quicker remediation.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may have been intermittently impacted. This could have affected users located in Asia-Pacific, Europe, or Latin America.
Preliminary root cause: As part of a planned maintenance activity to improve network routing infrastructure, one of the Cheyenne datacenters was removed from active service rotation. As part of this activity, GLS at the affected Cheyenne datacenter was taken offline on Thursday, January 22, 2026, at 5:45 PM UTC. It was expected that the remaining regional GLS capacity would be sufficient to handle the redirected traffic.
Subsequent review of the incident identified that the load balancers that support the GLS service were unable to accept the redirected traffic in a timely manner causing the GLS load balancers to go into an unhealthy state. This sudden concentration of traffic led to an increase in retry activity, which further amplified the impact. Over time, these conditions triggered a cascading failure that affected dependent services, including mail flow and Domain Name System (DNS) resolution required for email delivery.
Start Time: Thursday, January 22, 2026, at 6:55 PM UTC
End Time: Friday, January 23, 2026, at 5:00 AM UTC
Next steps:
For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We've provided a Post-Incident Report for this incident. Additionally, we'll be updating the Post-Incident Report on a monthly basis, for the next six months, to show the status of the Next Steps. The first update was provided on March 2, 2026. The next update will be provided by April 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.
|
|---|
|
SP1242132 - Some admins may be unable to access the SharePoint Online admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 24 10:30:00 2026 |
|---|
| End Time: | Tue Mar 3 16:33:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Mar 4 01:04:08 2026 |
|---|
| Root Cause: | A portion of SharePoint Online infrastructure responsible for accessing the admin center encountered an issue with a specific authentication component which caused stale cached data to build and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Mar 4 01:01:55 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may have been unable to access the SharePoint Online admin center.
More info: Additionally, the top navigation suite bar (app launcher, search, and settings) didn't load across SharePoint Online sites for any users.
When attempting to access the SharePoint Online admin center, admins may have seen the following error message:
“Sorry, something went wrong.”
Final status: We've determined that a portion of SharePoint Online infrastructure responsible for accessing the admin center encountered an issue with a specific authentication component which caused stale cached data to build and resulted in impact. We’ve repaired the authentication component issue and cleared the stale cache, we've received confirmation from some admins who initially reported the issue that the impact is remediated.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted.
Start time: Tuesday, February 24, 2026, at 3:30 PM UTC
End time: Tuesday, March 3, 2026, at 9:33 PM UTC
Root Cause: A portion of SharePoint Online infrastructure responsible for accessing the admin center encountered an issue with a specific authentication component which caused stale cached data to build and resulted in impact.
Next steps:
- We're further investigating the portion of infrastructure in which the authentication component issue took place, so that we can help prevent similar problems from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 3 14:26:26 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Additionally, the top navigation suite bar (app launcher, search, and settings) doesn't load across SharePoint Online sites for any users.
When attempting to access the SharePoint Online admin center, admins may see the following error message:
“Sorry, something went wrong.”
Technical details of the error may reference an application initialization error.
Current status: Our analysis of the information gathered from a subset of admins who reported impact is persisting after the deployment of the configuration change indicates that a stale caching issue may be preventing them from receiving the fix. We've applied a solution to resolve the caching issue, and we're reaching out to the subset of affected admins to verify this has fully remediated the issue. This verification will help confirm our understanding of the root cause of the issue.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted.
Start time: Tuesday, February 24, 2026, at 3:30 PM UTC
Next update by: Wednesday, March 4, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Tue Mar 3 08:52:07 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Additionally, the top navigation suite bar (app launcher, search, and settings) doesn't load across SharePoint Online sites for any users.
When attempting to access the SharePoint Online admin center, admins may see the following error message:
“Sorry, something went wrong.”
Technical details of the error may reference an application initialization error.
Current status: We’ve identified that some admins may still be unable to access the SharePoint Online admin center following deployment of the configuration change. We’re analyzing information from affected users to determine whether a service issue is still occurring.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted.
Start time: Tuesday, February 24, 2026, at 3:30 PM UTC
Next update by: Tuesday, March 3, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Tue Mar 3 05:33:15 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Additionally, the top navigation suite bar (app launcher, search, and settings) doesn't load across SharePoint Online sites for any users.
When attempting to access the SharePoint Online admin center, admins may see the following error message:
“Sorry, something went wrong.”
Technical details of the error may reference an application initialization error.
Current status: We’ve determined that the configuration change may not have reached all affected environments, and further validation is required to confirm whether the impact has been fully mitigated.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Start time: Tuesday, February 24, 2026, at 3:30 PM UTC
Next update by: Tuesday, March 3, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Tue Mar 3 00:41:11 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Additionally, the top navigation suite bar (app launcher, search, and settings) doesn't load across SharePoint Online sites for any users.
When attempting to access the SharePoint Online admin center, admins may see the following error message:
“Sorry, something went wrong.”
Technical details of the error may reference an application initialization error.
Current status: We've received reports that some users are experiencing remediation after re-deploying a healthy version of the SharePoint Online service. We're continuing to assess whether our configuration change or other additional actions will be necessary to restore service completely.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Start time: Tuesday, February 24, 2026, at 3:30 PM UTC
Next update by: Tuesday, March 3, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Mon Mar 2 14:12:42 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Additionally, the top navigation suite bar (app launcher, search, and settings) doesn't load across SharePoint Online sites for any users.
When attempting to access the SharePoint Online admin center, admins may see the following error message:
“Sorry, something went wrong.”
Technical details of the error may reference an application initialization error.
Current status: We've identified a recent service update to the SharePoint Online service infrastructure that we suspect may be causing the impact. While we prepare our configuration change for deployment, we've re-deployed a known healthy version of the SharePoint Online service as a potential remediation action to address the suspected issue with the aforementioned service update. We're testing with a subset of affected users to determine if the redeployment action has had any effect in restoring service functionality.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Start time: Tuesday, February 24, 2026, at 3:30 PM UTC
Next update by: Tuesday, March 3, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Mon Mar 2 11:59:32 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Additionally, the top navigation suite bar (app launcher, search, and settings) doesn't load across SharePoint Online sites for any users.
When attempting to access the SharePoint Online admin center, admins may see the following error message:
“Sorry, something went wrong.”
Technical details of the error may reference an application initialization error.
Current status: We've isolated that impact isn’t limited to users or admins in Australia and updated the "Title", "User impact", and "Scope of impact" sections of our communications to reflect this change. We're analyzing recent updates to the SharePoint Online admin center. We’re also implementing a configuration change to have SharePoint Online admin center access requests route to any available endpoint as a potential remediation action to restore users to a healthy operating state while we continue to work to isolate the underlying root cause.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Mar 2 08:15:44 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Additionally, the top navigation suite bar (app launcher, search, and settings) doesn't load across SharePoint Online sites for any users. When attempting to access the SharePoint Online admin center, admins may see the following error message:
“Sorry, something went wrong.”
Technical details may reference an application initialization error.
Current status: We’re progressing with our investigation into the reported behavior and are reviewing the additional information provided by affected users to determine next steps toward mitigation.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Mar 2 05:29:56 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Additionally, the top navigation suite bar (app launcher, search, and settings) doesn't load across SharePoint Online sites for any users. When attempting to access the SharePoint Online admin center, admins may see the following error message:
“Sorry, something went wrong.”
Technical details may reference an application initialization error.
Current status: We’re continuing to investigate the reported behavior and are awaiting additional information from affected users to help validate our findings and confirm next mitigative steps.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 2:00 PM UTC
|
|---|
|
| Time: | Mon Mar 2 04:17:40 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: All admins cannot access the SharePoint Online admin center.
In addition, the top navigation suite bar (app launcher, search, and settings) does not load across SharePoint Online sites for any users.
When attempting to access the SharePoint Online admin center, admins may see the following error message:
“Sorry, something went wrong.”
Technical details may reference an application initialization error.
Current status: We’ve identified that this issue appears to be region-specific, with impact currently observed for users accessing SharePoint Online from Australia. We’re continuing to investigate the behavior and are reviewing request patterns and service responses to understand why components are not loading as expected in this region.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Mon Mar 2 01:36:04 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Admins receive the following error message, "Sorry, something went wrong".
Current status: Our investigation into the HAR logs and Unified Logging Service (ULS) logs continue while we try to identify the underlying root cause.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Sun Mar 1 23:48:04 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Admins receive the following error message, "Sorry, something went wrong".
Current status: We're continuing to investigate the HAR logs to help with isolating the source of the issue.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Sun Mar 1 22:52:37 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Admins receive the following error message, "Sorry, something went wrong".
Current status: We're reviewing HTTP Archive format (HAR) logs from admins reproducing the issue to help with the investigation and to identify our next troubleshooting steps.
Scope of impact: Some admins or users attempting to access the SharePoint Online admin center or sites may be impacted, and are returned an error message stating “Sorry, something went wrong.” This information may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Sun Mar 1 22:30:24 2026 |
|---|
| Description: | Title: Some admins may be unable to access the SharePoint Online admin center
User impact: Admins may be unable to access the SharePoint Online admin center.
More info: Admins receive the following error message, "Sorry, something went wrong".
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.
|
|---|
|
TM1223735 - Some users may not have permissions for Microsoft Teams meeting notes if notes are enabled after the meeting was created
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 19 19:00:00 2025 |
|---|
| End Time: | Mon Mar 2 11:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 3 15:49:11 2026 |
|---|
| Root Cause: | A deployment to introduce a new calendar form contained a code issue, causing the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 3 15:49:11 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 had permissions for Microsoft Teams meeting notes if notes were enabled after the meeting creation.
More info: More info: This issue only occurred in organizations where admins enabled the ability for users to share links with "Specific People" in Microsoft OneDrive and SharePoint Online as the meeting notes were hosted there.
When users added meeting notes from the Microsoft Teams Calendar to a meeting that had already been created, the meeting participants may have not been granted permissions to view the notes, while the user that added the notes may have been able to access them as expected.
Final status: We've confirmed that the fix has finished deploying and is present in all previously affected environments. This issue is now mitigated and service is restored.
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 have been affected.
Start time: Thursday, November 20, 2025, at 12:00 AM UTC
End time: Monday, March 2, 2026, at 4:00 PM UTC
Root cause: A deployment to introduce a new calendar form contained a code issue, causing the impact.
Next steps:
- We'll continue to evaluate our processes and how the code was introduced to prevent future duplications of this issue.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 25 16:23:44 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 to monitor the fix as it propagates throughout the affected environments. The deployment is taking longer than anticipated and is currently at 50 percent completion. As the fix progresses, some users may experience alleviation, and based on our current estimates, the deployment should complete 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: Wednesday, March 4, 2026, at 10:30 PM UTC
|
|---|
|
| Time: | Tue Feb 17 16:52: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: We’ve initiated the fix to the affected environments and, as it progresses, some users may experience alleviation. Once the fix is applied, users may need to restart their Microsoft Teams client to experience full remediation. We’re monitoring the saturation of the fix and suspect that it will complete 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: Wednesday, February 25, 2026, at 10:30 PM UTC
|
|---|
|
| 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.
|
|---|
|
MV1243442 - Users may be unable to access the Suite navigation bar within Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Sun Mar 1 23:30:00 2026 |
|---|
| End Time: | Tue Mar 3 13:30:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Mar 3 14:53:23 2026 |
|---|
| Root Cause: | A recent Content Delivery Network (CDN) configuration change introduced an authentication component name mismatch in the allow list that prevented required navigation assets from loading within Viva Engage. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Mar 3 14:49:43 2026 |
|---|
| Description: | Title: Users may be unable to access the Suite navigation bar within Microsoft Viva Engage
User impact: Users may have been unable to access the Suite navigation bar within Viva Engage.
Final status: We've verified after monitoring the service that the applied configuration update to correct the name mismatch in the allow list has successfully remediated the problem.
Scope of impact: Impact may have occurred for all users attempting to utilize the Suite navigation bar within Viva Engage.
Start time: Monday, March 2, 2026, at 4:30 AM UTC
End time: Tuesday, March 3, 2026, at 6:30 PM UTC
Root cause: A recent Content Delivery Network (CDN) configuration change introduced an authentication component name mismatch in the allow list that prevented required navigation assets from loading within Viva Engage.
Next steps:
- We're investigating how the recent Content Delivery Network (CDN) configuration change introduced an authentication component name mismatch in the allow list to prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Mar 3 14:20:07 2026 |
|---|
| Description: | Title: Users may be unable to access the Suite navigation bar within Microsoft Viva Engage
User impact: Users may be unable to access the Suite navigation bar within Viva Engage.
Current status: We've identified that a recent Content Delivery Network (CDN) configuration change introduced an authentication component name mismatch in the allow list that prevented required navigation assets from loading within Viva Engage. To remediate this issue, we've applied a configuration update to correct the name mismatch in the allow list, and we're monitoring the service to ensure successful remediation.
Scope of impact: Impact may occur for all users attempting to utilize the Suite navigation bar within Viva Engage.
Start time: Monday, March 2, 2026, at 4:30 AM UTC
Root cause: A recent Content Delivery Network (CDN) configuration change introduced an authentication component name mismatch in the allow list that prevented required navigation assets from loading within Viva Engage.
Next update by: Tuesday, March 3, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Mar 3 13:39:28 2026 |
|---|
| Description: | Title: Users may be unable to access the Suite navigation bar within Microsoft Viva Engage
User impact: Users may be unable to access the Suite navigation bar within Viva Engage.
Current status: We've received reports from affected users that users may be unable to access the Suite navigation bar within Viva Engage. We're reviewing service telemetry to isolate the source of this impact and determine appropriate remediation actions.
Scope of impact: Impact may occur for all users attempting to utilize the Suite navigation bar within Viva Engage.
Next update by: Tuesday, March 3, 2026, at 7:30 PM UTC
|
|---|
|
PL1242549 - Some users may be unable to access Planner on the web
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 2 02:15:00 2026 |
|---|
| End Time: | Mon Mar 2 12:25:00 2026 |
|---|
| Service: | Planner |
|---|
| Feature Group: | Planner |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Mar 2 17:42:25 2026 |
|---|
| Root Cause: | An update to the Planner MSAL introduced a mismatch between the unauthenticated Planner on the web landing page and the authenticated experience after users signed in. This mismatch resulted in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 2 15:03:45 2026 |
|---|
| Description: | Title: Some users may be unable to access Planner on the web
User impact: Users may have been unable to access Planner on the web.
More info: To bypass the impact, some users may have been able to access Planner via Microsoft Teams if this option was available to them.
Final status: We've confirmed with a subset of affected users that updating the Microsoft Authentication Library (MSAL) to resolve the mismatch has remediated the impact.
Scope of impact: Some users that were trying to access Planner on the web may have been impacted.
Start time: Monday, March 2, 2026, at 7:15 AM UTC
End time: Monday, March 2, 2026, at 5:25 PM UTC
Root cause: An update to the Planner MSAL introduced a mismatch between the unauthenticated Planner on the web landing page and the authenticated experience after users signed in. This mismatch resulted in the impact.
Next steps:
- We're reviewing our standard update protocol to ensure future updates are applied with the proper cadence to prevent similar mismatches from occurring.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 2 13:09:30 2026 |
|---|
| Description: | Title: Some users may be unable to access Planner on the web
User impact: Users may be unable to access Planner on the web.
More info: To bypass the impact, some users may be able to access Planner via Microsoft Teams if this option is available to them.
Current status: We've confirmed that an update to the Planner Microsoft Authentication Library (MSAL) is introducing a mismatch between the unauthenticated Planner on the web landing page and the authenticated experience after users sign in. This mismatch is resulting in the impact. We've updated the MSAL to be aligned across both experiences, and we're validating this has resolved the issue with a subset of affected users.
Scope of impact: Some users that are trying to access Planner on the web may be impacted.
Start time: Monday, March 2, 2026, at 7:15 AM UTC
Root cause: An update to the Planner Microsoft Authentication Library (MSAL) is introducing a mismatch between the unauthenticated Planner on the web landing page and the authenticated experience after users sign in. This mismatch is resulting in the impact.
Next update by: Monday, March 2, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Mon Mar 2 11:10:58 2026 |
|---|
| Description: | Title: Some users may be unable to access Planner on the web
User impact: Users may be unable to access Planner on the web.
More info: To bypass the impact, some users may be able to access Planner via Microsoft Teams if this option is available to them.
Current status: We're reproducing the issue within our internal testing environment to collect further diagnostic data to aid in our troubleshooting and identification of the source of the impact.
Scope of impact: Some users that are trying to access Planner on the web may be impacted.
Next update by: Monday, March 2, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Mon Mar 2 09:32:39 2026 |
|---|
| Description: | Title: Some users may be unable to access Planner on the web
User impact: Users may be unable to access Planner on the web.
More info: As a workaround, some users may be able to access Planner via Microsoft Teams.
Current status: We're reviewing support provided information and service monitoring telemetry, to isolate the source of the issue and establish a fix.
Scope of impact: Some users that are trying to access Planner on the web may be impacted.
Next update by: Monday, March 2, 2026, at 4:30 PM UTC
|
|---|
|
CP1242733 - Users are shown a Microsoft 365 Copilot agent titled "DA_CICap_ST_SDF" that wasn't added by their admins
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 2 07:00:00 2026 |
|---|
| End Time: | Mon Mar 2 15:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 2 15:57:30 2026 |
|---|
| Root Cause: | A Copilot test agent that was meant to be deployed to our internal testing environment was unintentionally deployed to the affected users and caused impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 2 15:57:30 2026 |
|---|
| Description: | Title: Users are shown a Microsoft 365 Copilot agent titled "DA_CICap_ST_SDF" that wasn't added by their admins
User impact: Users were shown a Copilot agent titled "DA_CICap_ST_SDF" that wasn't added by their admins.
More info: The agent was designed as a test tool to assist users with code only by request. While the test agent "DA_CICap_ST_SDF" was deployed it did not access or collect specific information from your organization.
Final status: We've confirmed with a subset of affected users that, after we removed the app, the impact is remediated.
Scope of impact: Your organization was affected by this event, and all Copilot users were shown the agent titled "DA_CICap_ST_SDF."
Start time: Monday, March 2, 2026, at 12:00 PM UTC
End time: Monday, March 2, 2026, at 8:00 PM UTC
Root cause: A Copilot test agent that was meant to be deployed to our internal testing environment was unintentionally deployed to the affected users and caused impact.
Next steps:
- We're reviewing our agent deployment testing and validation procedures to identify and prevent similar issues with deployment agents too broadly moving forward.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 2 15:38:06 2026 |
|---|
| Description: | Title: Users are shown a Microsoft 365 Copilot agent titled "DA_CICap_ST_SDF" that wasn't added by their admins
User impact: Users are shown a Copilot agent titled "DA_CICap_ST_SDF" that wasn't added by their admins.
More info: The agent is designed as a test tool to assist users with code only by request. While the test agent "DA_CICap_ST_SDF" was deployed it did not access or collect specific information from your organization.
Current status: We've identified that a Copilot test agent that was meant to be deployed to our internal testing environment was unintentionally deployed to the affected users, causing impact. We've deployed a fix to remove the agent and are checking with a subset of users to confirm that the impact is remediated.
Scope of impact: Your organization is affected by this event, and all Copilot users are shown the agent titled "DA_CICap_ST_SDF."
Start time: Monday, March 2, 2026, at 12:00 PM UTC
Root cause: A Copilot test agent that was meant to be deployed to our internal testing environment was unintentionally deployed to the affected users, causing impact.
Next update by: Monday, March 2, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Mar 2 15:09:00 2026 |
|---|
| Description: | Title: Users are shown a Microsoft 365 Copilot agent titled "DA_CICap_ST_SDF" that wasn't added by their admins
User impact: Users are shown a Copilot agent titled "DA_CICap_ST_SDF" that wasn't added by their admins.
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.
|
|---|
|
TM1240086 - Users may experience increased latency when performing certain Microsoft Teams and channel lifecycle operations
| Status: | serviceRestored |
|---|
| Start Time: | Wed Feb 25 22:15:00 2026 |
|---|
| End Time: | Sat Feb 28 19:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 2 13:15:03 2026 |
|---|
| Root Cause: | A portion of infrastructure responsible for performing certain Teams and channel lifecycle operations wasn’t processing requests as efficiently as expected due to an unexpected influx of network traffic and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 2 13:15:03 2026 |
|---|
| Description: | Title: Users may experience increased latency when performing certain Microsoft Teams and channel lifecycle operations
User impact: Users may have experienced increased latency when performing certain Teams and channel lifecycle operations.
More info: Affected actions included long running / async operations, such as:
-Archiving a team or channel.
-Removing users from teams or private channels.
-Adding members to teams or private channels.
-Creating a team from a group or template.
-Cloning a team.
Final status: We've confirmed that the backlog of data has completed processing and the impact is remediated.
Scope of impact: Users who attempted to perform certain Microsoft Teams and channel lifecycle operations were affected.
Start time: Thursday, February 26, 2026, at 3:15 AM UTC
End time: Sunday, March 1, 2026, at 12:00 AM UTC
Root cause: A portion of infrastructure responsible for performing certain Teams and channel lifecycle operations wasn’t processing requests as efficiently as expected due to an unexpected influx of network traffic and resulted in impact.
Next steps:
- We're reviewing the portion of affected infrastructure to identify the reason it wasn't processing requests as efficiently as possible so that we can determine how to prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 27 20:51:27 2026 |
|---|
| Description: | Title: Users may experience increased latency when performing certain Microsoft Teams and channel lifecycle operations
User impact: Users may experience increased latency when performing certain Teams and channel lifecycle operations.
More info: Affected actions include long running / async operations, such as:
-Archiving a team or channel.
-Removing users from teams or private channels.
-Adding members to teams or private channels.
-Creating a team from a group or template.
-Cloning a team.
Current status: We’ve restarted the affected infrastructure and we’re monitoring as the backlogged data begins to be processed. We anticipate that this process will be completed, remediating the impact by our next scheduled update.
Scope of impact: Your organization is impacted by this event, and users who are attempting to perform certain Microsoft Teams and channel lifecycle operations are affected. This section may be updated as our investigation proceeds.
Start time: Thursday, February 26, 2026, at 3:15 AM UTC
Root cause: A portion of infrastructure responsible for performing certain Teams and channel lifecycle operations isn’t processing requests as efficiently as expected due to an unexpected influx of network traffic and is resulting in impact.
Next update by: Monday, March 2, 2026, at 7:30 PM UTC
|
|---|
|
| Time: | Fri Feb 27 17:01:19 2026 |
|---|
| Description: | Title: Users may experience increased latency when performing certain Microsoft Teams and channel lifecycle operations
User impact: Users may experience increased latency when performing certain Teams and channel lifecycle operations.
More info: Affected actions include long running / async operations, such as:
-Archiving a team or channel.
-Removing users from teams or private channels.
-Adding members to teams or private channels.
-Creating a team from a group or template.
-Cloning a team.
Current status: After deploying a fix to reduce retries in this scenario and allocating additional resources across dependent services to ease processing load, we haven’t yet seen the expected decrease in the backlog. We’re reassessing the current approach and evaluating next mitigation steps, and we expect to have a clear plan forward by the next scheduled update.
Scope of impact: Your organization is impacted by this event, and users who are attempting to perform certain Microsoft Teams and channel lifecycle operations are affected. This section may be updated as our investigation proceeds.
Start time: Thursday, February 26, 2026, at 3:15 AM UTC
Root cause: A portion of infrastructure responsible for performing certain Teams and channel lifecycle operations isn’t processing requests as efficiently as expected due to an unexpected influx of network traffic and is resulting in impact.
Next update by: Saturday, February 28, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Thu Feb 26 23:23:51 2026 |
|---|
| Description: | Title: Users may experience increased latency when performing certain Microsoft Teams and channel lifecycle operations
User impact: Users may experience increased latency when performing certain Teams and channel lifecycle operations.
More info: Affected actions include long running / async operations, such as:
-Archiving a team or channel.
-Removing users from teams or private channels.
-Adding members to teams or private channels.
-Creating a team from a group or template.
-Cloning a team.
Current status: We’ve determined that the portion of infrastructure responsible for performing certain Teams and channel lifecycle operations isn’t processing requests as efficiently as expected due to an unexpected influx of network traffic, which is resulting in impact. We’ve deployed a fix to rebalanced traffic across the affected infrastructure to better allocate resources and process requests more efficiently and we’re monitoring as the backlogged requests process to ensure that impact is remediated.
Scope of impact: Your organization is impacted by this event, and users who are attempting to perform certain Microsoft Teams and channel lifecycle operations are affected. This section may be updated as our investigation proceeds.
Start time: Thursday, February 26, 2026, at 3:15 AM UTC
Root cause: A portion of infrastructure responsible for performing certain Teams and channel lifecycle operations isn’t processing requests as efficiently as expected due to an unexpected influx of network traffic and is resulting in impact.
Next update by: Friday, February 27, 2026, at 11:00 PM UTC
|
|---|
|
| Time: | Thu Feb 26 21:50:44 2026 |
|---|
| Description: | Title: Users may experience increased latency when performing certain Microsoft Teams and channel lifecycle operations
User impact: Users may experience increased latency when performing certain Teams and channel lifecycle operations.
More info: Affected actions include long running / async operations, such as:
-Archiving a team or channel.
-Removing users from teams or private channels.
-Adding members to teams or private channels.
-Creating a team from a group or template.
-Cloning a team.
Current status: We’re revieing available service logs and telemetry, specific to when impact first occurred, so that we can determine our troubleshooting steps.
Scope of impact: Your organization is impacted by this event, and users who are attempting to perform certain Microsoft Teams and channel lifecycle operations are affected. This section may be updated as our investigation proceeds.
Start time: Thursday, February 26, 2026, at 3:15 AM UTC
Next update by: Friday, February 27, 2026, at 4:30 AM UTC
|
|---|
|
| Time: | Thu Feb 26 21:28:13 2026 |
|---|
| Description: | Title: Users may experience increased latency when performing certain Microsoft Teams and channel lifecycle operations
User impact: Users may experience increased latency when performing certain Teams and channel lifecycle operations.
More info: Affected actions include long running / async operations, such as:
-Archiving a team or channel.
-Removing users from teams or private channels.
-Adding members to teams or private channels.
-Creating a team from a group or template.
-Cloning a team.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
TM1239087 - Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 19 00:00:00 2026 |
|---|
| End Time: | Sat Feb 28 13:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 2 13:01:46 2026 |
|---|
| Root Cause: | A recent service update caused a portion of the supporting Microsoft Teams service infrastructure to operate in a suboptimal state due to high CPU and memory constraint issues, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 2 13:01:46 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may have been unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may have heard the greeting, followed by approximately 15 seconds of silence, then they may have received the error message: “Sorry, I couldn’t help.”
Final status: Further review determined that the recent service update caused a portion of the supporting Microsoft Teams service infrastructure to operate in a suboptimal state due to high CPU and memory constraint issues, resulting in impact. We've completed rolling back the offending service update, and confirmed through testing with a subset of affected users, as well as through monitoring service health telemetry that the impact has been remediated.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may have been impacted.
Start time: Thursday, February 19, 2026, at 5:00 AM UTC
End time: Saturday, February 28, 2026, at 6:30 PM UTC
Root cause: A recent service update caused a portion of the supporting Microsoft Teams service infrastructure to operate in a suboptimal state due to high CPU and memory constraint issues, resulting in impact.
Next steps:
- We're reviewing our update procedures to understand why impact to auto attendant 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 Feb 27 19:15:34 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: We're monitoring the rollback of the service update that we expect is causing this issue throughout the affected environment, and anticipate this process should complete by our next scheduled update, at which point we'll verify through service telemetry whether impact is remediated.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Monday, March 2, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Feb 27 18:16:42 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: We're continuing to reverse the recent service update and will provide a timeline for the completion of this action as one becomes available.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Saturday, February 28, 2026, at 1:30 AM UTC
|
|---|
|
| Time: | Fri Feb 27 16:43:40 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: We've identified a recent service update to the portion of service infrastructure responsible for facilitating calls to agents using Dial-by-Extension for auto attendants that correlates with the impact. We're reversing this update to determine whether it remediates the impact.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Saturday, February 28, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 12:59:31 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: We're reviewing the portion of infrastructure that supports the transfer from auto attendants to agents as we suspect that the volume of requests isn't properly rebalancing to avoid impact.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Saturday, February 28, 2026, at 2:30 AM UTC
|
|---|
|
| Time: | Fri Feb 27 06:53:43 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: Our investigation is currently focused on a potential issue with processing requests, which may be causing impact to occur.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Friday, February 27, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Feb 27 01:35:19 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: We’re continuing to work with a subset of affected users to gather additional information and logging surrounding the timeouts to further our understanding of the underlying issue and determine our next steps.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Friday, February 27, 2026, at 12:00 PM UTC
|
|---|
|
| Time: | Thu Feb 26 04:32:26 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: We’re working with a subset of affected users to gather additional information to better understand the service‑side timeouts, determine the underlying root cause, and identify the appropriate steps to remediate impact.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Friday, February 27, 2026, at 8:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 18:57:33 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: We increased the timeout window and determined that this was not an effective temporary mitigation. We're continuing to investigate these service-side timeouts to determine their underlying root cause in order to develop effective remediation steps to address the impact.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Thursday, February 26, 2026, at 10:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 16:55:21 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: We've located service-side timeout errors that may be contributing to these failures, and we're working to confirm whether increasing the timeout window may serve as a valid temporary mitigation while we continue our investigation.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Thursday, February 26, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 15:53:45 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
Current status: We're reviewing the Fiddler traces provided by a subset of affected users alongside service side data to determine the underlying root cause and develop our next steps toward remediation.
Scope of impact: Any users attempting to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams may be impacted.
Next update by: Wednesday, February 25, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Feb 25 15:32:21 2026 |
|---|
| Description: | Title: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams
User impact: Users may be unable to reach agents through Dial-by-Extension for some auto attendants in Microsoft Teams.
More info: Users may hear the greeting, followed by approximately 15 seconds of silence, then they may receive the error message: “Sorry, I couldn’t help.”
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.
|
|---|
|
CP1238907 - Some newly licensed users may be unable to leverage any Microsoft 365 Copilot premium features in any Outlook client
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 2 19:00:00 2026 |
|---|
| End Time: | Sun Mar 1 02:03:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Mar 2 12:57:13 2026 |
|---|
| Root Cause: | A failure within our licensing sync pipeline produced stale data that prevented licensing updates from being applied, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 2 12:57:13 2026 |
|---|
| Description: | Title: Some newly licensed users may be unable to leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users may have been unable to leverage any Copilot premium features in any Outlook client.
More info: This issue impacted Copilot premium features for newly licensed users that received licenses between Tuesday, February 3, 2026, and Thursday, February 26, 2026, in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Final status: Following the completion of our licensing syncs, our internal service telemetry has verified that users can leverage Copilot premium features from the Outlook client and that impact has been remediated.
Scope of impact: This issue may have impacted newly licensed users in Europe or North America with licenses assigned between Tuesday, February 3, 2026, and Thursday, February 26, 2026, who were attempting to use Copilot premium features in the Outlook desktop client, Outlook on the web, and the Outlook mobile app.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
End time: Sunday, March 1, 2026, at 7:03 AM UTC
Root cause: A failure within our licensing sync pipeline produced stale data that prevented licensing updates from being applied, resulting in impact.
Next steps:
- We're further analyzing the isolated licensing sync pipeline failure to better understand what caused the underlying issue, which will help us prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Fri Feb 27 14:49:02 2026 |
|---|
| Description: | Title: Some newly licensed users may be unable to leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users may be unable to leverage any Copilot premium features in any Outlook client.
More info: This issue impacts Copilot premium features for newly licensed users that received licenses between Tuesday, February 3, 2026, and Thursday, February 26, 2026, in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Current status: We’ve identified that the license syncs are taking longer than anticipated, and we’re continuing to monitor their ongoing progression to ensure it successfully completes.
Scope of impact: This issue may impact newly licensed users in Europe or North America with licenses assigned between Tuesday, February 3, 2026, and Thursday, February 26, 2026, who are attempting to use Copilot premium features in the Outlook desktop client, Outlook on the web, and the Outlook mobile app. This information may be updated as our investigation continues.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
Root cause: A caching issue is preventing licensing updates from being applied as expected and resulting in the impact.
Next update by: Monday, March 2, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Feb 27 13:05:24 2026 |
|---|
| Description: | Title: Some newly licensed users may be unable to leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users may be unable to leverage any Copilot premium features in any Outlook client.
More info: This issue impacts Copilot premium features for newly licensed users that received licenses between Tuesday, February 3, 2026, and Thursday, February 26, 2026, in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Current status: We’re continuing to monitor the progression of the license syncs and have verified that the process has reached 70 percent completion. Based on our current estimates, we expect it to complete by our next scheduled update.
Scope of impact: This issue may impact newly licensed users in Europe or North America with licenses assigned between Tuesday, February 3, 2026, and Thursday, February 26, 2026, who are attempting to use Copilot premium features in the Outlook desktop client, Outlook on the web, and the Outlook mobile app. This information may be updated as our investigation continues.
Start time: Tuesday, February 3, 2026, at 12:00 AM UTC
Root cause: A caching issue is preventing licensing updates from being applied as expected and resulting in the impact.
Next update by: Saturday, February 28, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Feb 26 17:19:07 2026 |
|---|
| Description: | Title: Some newly licensed users may be unable to leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users may be unable to leverage any Copilot premium features in any Outlook client.
More info: This issue impacts Copilot premium features for newly licensed users that received licenses between Tuesday, February 3, 2026, and Thursday, February 26, 2026, in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Current status: We've received initial feedback from users who have had their licenses synced that they're now able to leverage Copilot premium features from the Outlook client. We're progressing with our license syncs and are working to establish an estimated timeline for the full sync process to complete.
Scope of impact: This issue may impact newly licensed users in Europe or North America with licenses assigned between Tuesday, February 3, 2026, and Thursday, February 26, 2026, who are attempting to use Copilot premium features in the Outlook desktop client, Outlook on the web, and the Outlook mobile app. This information may be updated as our investigation continues.
Root cause: A caching issue is preventing licensing updates from being applied as expected and resulting in the impact.
Next update by: Friday, February 27, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Thu Feb 26 12:25:48 2026 |
|---|
| Description: | Title: Some newly licensed users may be unable to leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users may be unable to leverage any Copilot premium features in any Outlook client.
More info: This issue impacts Copilot premium features for newly licensed users that received licenses between February 3, 2026, and February 26, 2026, in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Current status: Following our deployed fix, the problems are no longer occurring for any user being assigned a new license. For affected users who received licenses during the window of impact, we're processing cached data while manually syncing user licenses to remediate the impact. We'll provide an estimated timeline for our remaining mitigations once it has become available.
Scope of impact: This issue may impact newly licensed users in Europe or North America with licenses assigned between February 3, 2026, and February 26, 2026, who are attempting to use Copilot premium features in the Outlook client. This information may be updated as our investigation continues.
Root cause: A caching issue is preventing licensing updates from being applied as expected and resulting in the impact.
Next update by: Friday, February 27, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 20:42:17 2026 |
|---|
| Description: | Title: Some newly licensed users can't leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users can't leverage any Copilot premium features in any Outlook client.
More info: This issue impacts Copilot premium features for newly licensed users in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Current status: We’ve determined that a recent update introduced a caching issue, which is preventing licensing updates from being applied as expected and resulting in the impact. We’ve developed and initiated the process of deploying a fix to address this issue. We expect that we’ll have an estimate for the fix to reach all affected users by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some newly licensed users attempting to use any Copilot premium features in any Outlook client may be impacted. This information may be updated as our investigation continues.
Root cause: A caching issue is preventing licensing updates from being applied as expected and resulting in the impact.
Next update by: Thursday, February 26, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Wed Feb 25 18:35:22 2026 |
|---|
| Description: | Title: Some newly licensed users can't leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users can't leverage any Copilot premium features in any Outlook client.
More info: This issue impacts Copilot premium features for newly licensed users in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Current status: We've manually synced the Copilot license data for a subset of affected users; however, initial reports indicate this hasn't successfully mitigated the impact. We're further analyzing this subset of users to determine why the license data isn't reflecting accurately.
Scope of impact: Your organization is affected by this event, and some users attempting to use any Copilot premium features in any Outlook client may be impacted.
Next update by: Thursday, February 26, 2026, at 2:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 16:54:19 2026 |
|---|
| Description: | Title: Some newly licensed users can't leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users can't leverage any Copilot premium features in any Outlook client.
More info: This issue impacts Copilot premium features for newly licensed users in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Current status: Our investigation of the pipeline responsible for updating Copilot license data is ongoing. In parallel, we're determining whether manually forcing a sync for the affected users is a viable method of expediting mitigation while we're isolating the source of impact.
Scope of impact: Your organization is affected by this event, and some users attempting to use any Copilot premium features in any Outlook client may be impacted.
Next update by: Thursday, February 26, 2026, at 12:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 14:45:17 2026 |
|---|
| Description: | Title: Some newly licensed users can't leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users can't leverage any Copilot premium features in any Outlook client.
More info: This issue impacts Copilot premium features for newly licensed users in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Current status: We suspect a sync issue is occurring within the pipeline responsible for updating Copilot license data, and we're analyzing the pipeline to confirm the root cause of the impact.
Scope of impact: Your organization is affected by this event, and some users attempting to use any Copilot premium features in any Outlook client may be impacted.
Next update by: Wednesday, February 25, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Wed Feb 25 12:38:08 2026 |
|---|
| Description: | Title: Some newly licensed users can't leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users can't leverage any Copilot premium features in any Outlook client.
More info: This issue impacts Copilot premium features for newly licensed users in the Outlook desktop client, Outlook on the web, and Outlook mobile.
Current status: We're expanding our investigation to include a review of the calls being made to Graph API to determine whether the expected Copilot license information is being returned as we work to isolate the source of the issue.
Scope of impact: Your organization is affected by this event, and some users attempting to use any Copilot premium features in any Outlook client may be impacted.
Next update by: Wednesday, February 25, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Feb 25 10:09:51 2026 |
|---|
| Description: | Title: Some newly licensed users can't leverage any Microsoft 365 Copilot premium features in any Outlook client
User impact: Users can't leverage any Copilot premium features in any Outlook client.
Current status: We're reviewing the provided HTTP Archive format (HAR) logs to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to use any Copilot premium features in any Outlook client may be impacted.
Next update by: Wednesday, February 25, 2026, at 5:30 PM UTC
|
|---|
|
TM1238395 - Users may have seen autogenerated chats during Public Switched Telephone Network (PSTN) calls in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 10 05:37:00 2026 |
|---|
| End Time: | Fri Feb 27 14:52:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 2 10:28:38 2026 |
|---|
| Root Cause: | A code issue in a recent deployment to the Microsoft Teams calling service introduced a compatibility complication between the affected calling scenarios and chats, which was causing chat threads to unexpectedly autogenerate in the Microsoft Teams desktop client and web app. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 2 10:28:38 2026 |
|---|
| Description: | Title: Users may have seen autogenerated chats during Public Switched Telephone Network (PSTN) calls in Microsoft Teams
User impact: Users may have seen autogenerated chats during PSTN calls, Call Queues or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may have seen a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may have also affected Call Queue and Auto Attendant calls.
Final status: We've confirmed with a subset of users that impact has been full resolved.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may have been impacted.
Start time: Tuesday, February 10, 2026, at 10:37 AM UTC
End time: Friday, February 27, 2026, at 7:52 PM UTC
Root cause: A code issue in a recent deployment to the Microsoft Teams calling service introduced a compatibility complication between the affected calling scenarios and chats, which was causing chat threads to unexpectedly autogenerate in the Microsoft Teams desktop client and web app.
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 27 11:18:38 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN calling scenarios, Call Queues or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
Current status: We've completed deployment of our fix and are checking with a subset of affected users to confirm that impact is remediated.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, February 10, 2026, at 10:37 AM UTC
Root cause: A code issue in a recent deployment to the Microsoft Teams calling service introduced a compatibility complication between the affected calling scenarios and chats, which is causing chat threads to unexpectedly autogenerate in the Microsoft Teams desktop client and web app.
Next update by: Monday, March 2, 2026, at 5:00 PM UTC
|
|---|
|
| Time: | Thu Feb 26 20:51:34 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN calling scenarios, Call Queues or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
Current status: The deployment of our fix has reached 80% saturation throughout the affected environment. We anticipate that the remainder of the fix will have fully deployed by our next scheduled update. Additionally, affected users will incrementally experience relief from impact as the deployment propagates throughout the affected environment.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, February 10, 2026, at 10:37 AM UTC
Root cause: A code issue in a recent deployment to the Microsoft Teams calling service introduced a compatibility complication between the affected calling scenarios and chats, which is causing the chats threads to unexpectedly autogenerate in the Microsoft Teams desktop client and web app.
Next update by: Friday, February 27, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Thu Feb 26 14:01:37 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN calling scenarios, Call Queues or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
Current status: The deployment of our fix is taking longer than initially anticipated and has currently reached 70% saturation throughout the affected environment. We'll aim to provide a timeline for the deployment to complete by our next scheduled communication update.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, February 10, 2026, at 10:37 AM UTC
Root cause: A code issue in a recent deployment to the Microsoft Teams calling service introduced a compatibility complication between the affected calling scenarios and chats, which is causing the chats threads to unexpectedly autogenerate in the Microsoft Teams desktop client and web app.
Next update by: Friday, February 27, 2026, at 3:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 20:48:23 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN calling scenarios, Call Queues or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
Current status: We've identified that our fix deployment has reached approximately 40 percent saturation throughout the affected environment, and we're anticipating it may complete by our next scheduled update, at which point we'll monitor to confirm full remediation.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, February 10, 2026, at 10:37 AM UTC
Root cause: A code issue in a recent deployment to the Microsoft Teams calling service introduced a compatibility complication between the affected calling scenarios and chats, which is causing the chats threads to unexpectedly autogenerate in the Microsoft Teams desktop client and web app.
Next update by: Thursday, February 26, 2026, at 8:00 PM UTC
|
|---|
|
| Time: | Wed Feb 25 12:08:05 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN call scenarios and Call Queue or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
Current status: We're monitoring the deployment of the fix which has currently reached 20 percent saturation within the affected environment. We'll aim to provide a timeline for the deployment of the fix to complete by our next scheduled communications update.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Start time: Tuesday, February 10, 2026, at 10:37 AM UTC
Root cause: A code issue in a recent deployment to the Microsoft Teams calling service introduced a compatibility complication between the affected calling scenarios and chats, which is causing the chats threads to unexpectedly autogenerate in the Microsoft Teams desktop client and web app.
Next update by: Thursday, February 26, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Wed Feb 25 01:08:33 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN call scenarios and Call Queue or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
Current status: We've started deploying the fix in stages to ensure adequate monitoring and validations can be performed before it continues with its saturation. We anticipate users will experience remediation incrementally while the deployment progresses, and we'll aim to provide a resolution timeline once available.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Root cause: A code issue in a recent deployment to the Microsoft Teams calling service introduced a compatibility complication between the affected calling scenarios and chats, which is causing the chats threads to unexpectedly autogenerate in the Microsoft Teams desktop client and web app.
Next update by: Wednesday, February 25, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Tue Feb 24 21:51:11 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN call scenarios and Call Queue or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
Current status: Our investigation of the recent changes made to the service identified a recent update that inadvertently included a code issue, leading to impact. A fix deployment to revert the update has already begun deploying to the affected environment and we're monitoring its progress.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Root cause: A recent update to the Microsoft Teams calling service inadvertently included a code issue, leading to impact.
Next update by: Wednesday, February 25, 2026, at 6:30 AM UTC
|
|---|
|
| Time: | Tue Feb 24 19:16:31 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN call scenarios and Call Queue or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
Current status: We've collected logs from our reproduction of impact indicating which component is causing this issue and are investigating if any potential recent changes may be contributing to impact.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 4:00 AM UTC
|
|---|
|
| Time: | Tue Feb 24 18:08:07 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN call scenarios and Call Queue or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
Current status: We're reproducing impact in our internal testing environment and collecting logs for further insight into how the issue manifests.
Scope of impact: Any user interacting with PSTN calling scenarios in Microsoft Teams may be impacted. This section may be updated as our investigation continues.
Next update by: Wednesday, February 25, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Tue Feb 24 18:01:19 2026 |
|---|
| Description: | Title: Users may see autogenerated chats during Public Switched Telephone Network (PSTN) calling scenarios in Microsoft Teams
User impact: Users may see autogenerated chats during PSTN call scenarios and Call Queue or Auto Attendant calls in Microsoft Teams.
More info: When placing outbound PSTN calls or receiving inbound PSTN calls, users may see a chat thread autogenerate in the Microsoft Teams desktop client and web app. This may also affect Call Queue and Auto Attendant calls.
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.
|
|---|
|
EX1242346 - Some users may have been unable to access the Exchange admin center (EAC)
| Status: | serviceRestored |
|---|
| Start Time: | Mon Mar 2 03:20:00 2026 |
|---|
| End Time: | Mon Mar 2 06:53:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Mar 2 09:35:44 2026 |
|---|
| Root Cause: | A section of networking infrastructure was performing below acceptable performance thresholds and resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Mar 2 08:30:18 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 networking infrastructure was performing below acceptable performance thresholds and resulting in impact. We've applied traffic and performance optimizations which has remediated impact.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure attempting to access the EAC.
Start time: Monday, March 2, 2026, at 8:20 AM UTC
End time: Monday, March 2, 2026, at 11:53 AM UTC
Root cause: A section of networking infrastructure was performing below acceptable performance thresholds and resulting in impact.
Next steps:
- We're reviewing performance data and trends on the affected infrastructure to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Mon Mar 2 06:16:24 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 our 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: Monday, March 2, 2026, at 1:30 PM UTC
|
|---|
|
| Time: | Mon Mar 2 04:40:37 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: Monday, March 2, 2026, at 11:30 AM UTC
|
|---|
|
MO1242002 - Users in Australia may be unable to access various Microsoft 365 Apps or services from portal.office.com
| Status: | serviceRestored |
|---|
| Start Time: | Sun Mar 1 16:30:00 2026 |
|---|
| End Time: | Sun Mar 1 21:30:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sun Mar 1 23:54:13 2026 |
|---|
| Root Cause: | A resource contention caused by a spike in demand on infrastructure that facilitates access to Microsoft 365 Apps and services through the portal. This reduced the rate at which user requests were processed, which led to impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Mar 1 23:54:13 2026 |
|---|
| Description: | Title: Users in Australia may be unable to access various Microsoft 365 Apps or services from portal.office.com
User impact: Users may have been unable to access various Microsoft 365 Apps or services from portal.office.com.
More info: This issue affected users accessing apps or services from portal.office.com and m365.cloud.microsoft.com.
Final status: We've confirmed with a subset of reporting users, as well as our internal telemetry that service health is stable and impact has been remediated.
Scope of impact: Users in Australia attempting to access or use Microsoft 365 Apps and services may have been impacted.
Start time: Sunday, March 1, 2026, at 9:30 PM UTC
End time: Monday, March 2, 2026, at 2:30 AM UTC
Root cause: A resource contention caused by a spike in demand on infrastructure that facilitates access to Microsoft 365 Apps and services through the portal. This reduced the rate at which user requests were processed, which led to impact.
Next steps:
- We're further analyzing our service telemetry to help identify the underlying root cause of the spike in demand, as well as assessing whether additional monitoring can be implemented to help better detect similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Sun Mar 1 22:29:01 2026 |
|---|
| Description: | Title: Users in Australia may be unable to access various Microsoft 365 Apps or services from portal.office.com
User impact: Users may be unable to access various Microsoft 365 Apps or services from portal.office.com.
More info: This issue affects users accessing apps or services from portal.office.com and m365.cloud.microsoft.com.
Current status: We investigated service health telemetry and identified resource contention caused by a spike in demand on infrastructure that facilitates access to Microsoft 365 apps and services through the portal. This reduced the rate at which user requests were processed, leading to impact. We’ve implemented configuration changes to improve service accessibility. We’re seeing improvements in service health and are validating with a subset of affected users to confirm resolution.
Scope of impact: Users in Australia attempting to access or use Microsoft 365 Apps and services may be impacted. This section may be updated as our investigation continues.
Root cause: A resource contention caused by a spike in demand on infrastructure that facilitates access to Microsoft 365 apps and services through the portal. This reduced the rate at which user requests were processed, leading to impact.
Next update by: Monday, March 2, 2026, at 5:30 AM UTC
|
|---|
|
| Time: | Sun Mar 1 20:30:26 2026 |
|---|
| Description: | Title: Users in Australia may be unable to access various Microsoft 365 Apps or services from portal.office.com
User impact: Users may be unable to access various Microsoft 365 Apps or services from portal.office.com.
More info: This issue affects users accessing apps or services from portal.office.com and m365.cloud.microsoft.com.
Current status: We're continuing to analyze the service health telemetry to further pinpoint the underlying cause of impact to the Microsoft 365 apps and services.
Scope of impact: Users in Australia attempting to access or use Microsoft 365 Apps and services may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 3:30 AM UTC
|
|---|
|
| Time: | Sun Mar 1 19:47:02 2026 |
|---|
| Description: | Title: Users in Australia may be unable to access various Microsoft 365 Apps or services from portal.office.com
User impact: Users may be unable to access various Microsoft 365 Apps or services from portal.office.com.
More info: This issue affects users accessing apps or services from portal.office.com and m365.cloud.microsoft.com.
Current status: We've received reports indicating that users are unable to access Microsoft 365 Apps and services when attempting to access them from portal.office.com or m365.cloud.microsoft.com. We're reviewing the provided impact details and investigating service health telemetry to help contextualize the impact and inform our next troubleshooting steps.
Scope of impact: Users in Australia attempting to access or use Microsoft 365 Apps and services may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, March 2, 2026, at 1:30 AM UTC
|
|---|
|
EX1241696 - Some users may have experienced issues when accessing their Exchange Online mailbox via one or more connection method
| Status: | serviceRestored |
|---|
| Start Time: | Sun Mar 1 04:50:00 2026 |
|---|
| End Time: | Sun Mar 1 05:52:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sun Mar 1 07:42:51 2026 |
|---|
| Root Cause: | A problem with a shared network connection between South America and North America led to unstable traffic between the regions, causing intermittent connection issues and resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sun Mar 1 07:42:51 2026 |
|---|
| Description: | Title: Some users may have experienced issues when accessing their Exchange Online mailbox via one or more connection method
User impact: Users may have experienced issues when accessing their Exchange Online mailbox via one or more connection method.
More info: Users may have experienced errors or failures when attempting to accessing their mailbox.
Impacted connection methods included but may not have been limited to:
- Outlook on the web
Final status: We’ve determined that a problem with a shared network connection between South America and North America led to unstable traffic between the regions, causing intermittent connection issues. To mitigate impact, we rerouted traffic away from the unstable path and confirmed via telemetry that this rebalancing restored the service.
Scope of impact: Impact was specific to some users located in North America attempting to access their mailbox via any of the connection methods detailed above.
Start time: Sunday, March 1, 2026, at 9:50 AM UTC
End time: Sunday, March 1, 2026, at 10:52 AM UTC
Root cause: A problem with a shared network connection between South America and North America led to unstable traffic between the regions, causing intermittent connection issues and resulting in impact.
Next steps:
- We’re reviewing our traffic routing and resilience processes to help reduce the likelihood and impact of similar issues.
This is the final update for the event.
|
|---|
|
| Time: | Sun Mar 1 05:48:57 2026 |
|---|
| Description: | Title: Some users may experience issues when accessing their Exchange Online mailbox via one or more connection method
User impact: Users may experience issues when accessing their Exchange Online mailbox via one or more connection method.
More info: Users may experience errors or failures when attempting to accessing their mailbox.
Impacted connection methods include but may not be limited to:
- Outlook on the web
Current status: We’re currently reviewing service telemetry data to help identify the root cause and next steps required to mitigate impact.
Scope of impact: Impact is specific to some users located in North America attempting to access their mailbox via any of the connection methods detailed above.
Next update by: Sunday, March 1, 2026, at 1:00 PM UTC
|
|---|
|
| Time: | Sun Mar 1 05:11:57 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
EX1240933 - Users may have been unable to access their Exchange Online mailboxes through multiple connection methods
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 27 21:10:00 2026 |
|---|
| End Time: | Sat Feb 28 02:40:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | E-Mail and calendar access |
|---|
| Classification: | incident |
|---|
| Last Updated: | Sat Feb 28 05:39:54 2026 |
|---|
| Root Cause: | An unexpected spike in network traffic on a section of infrastructure that facilitates Exchange Online mailbox access caused intermittent network reachability issues, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Sat Feb 28 05:39:54 2026 |
|---|
| Description: | Title: Users may have been unable to access their Exchange Online mailboxes through multiple connection methods
User impact: Users may have been unable to access their Exchange Online mailboxes through a couple connection methods.
More info: Impacted connection methods included, but wasn't limited to:
- Outlook on the web
- Exchange ActiveSync (EAS)
Final status: We've identified that an unexpected spike in network traffic on a section of infrastructure that facilitates Exchange Online mailbox access caused intermittent network reachability issues, resulting in impact. We've successfully isolated the problematic path and rebalanced the network traffic to mitigate the issue. After an extended period of monitoring service telemetry, we've confirmed that impact is remediated.
Scope of impact: Users in North America and South America attempting to access their Exchange Online mailboxes through Exchange Online may have been impacted by this event.
Start time: Saturday, February 28, 2026, at 2:10 AM UTC
End time: Saturday, February 28, 2026, at 7:40 AM UTC
Root cause: An unexpected spike in network traffic on a section of infrastructure that facilitates Exchange Online mailbox access caused intermittent network reachability issues, resulting in impact.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Sat Feb 28 01:45:46 2026 |
|---|
| Description: | Title: Users may be unable to access their Exchange Online mailboxes through a couple connection methods
User impact: Users may be unable to access their Exchange Online mailboxes through a couple connection methods.
More info: The impacted connection methods consist of the following:
- Outlook on the web
- Exchange ActiveSync (EAS)
Current status: We're continuing to further investigate the aforementioned error to pinpoint the underlying cause of the issue and develop a remediation plan.
Scope of impact: Users in North America and South America attempting to access their Exchange Online mailboxes through Exchange Online may be impacted by this event. This information may be updated as our investigation continues.
Next update by: Saturday, February 28, 2026, at 11:30 AM UTC
|
|---|
|
| Time: | Fri Feb 27 23:50:34 2026 |
|---|
| Description: | Title: Users may be unable to access their Exchange Online mailboxes through a couple connection methods
User impact: Users may be unable to access their Exchange Online mailboxes through a couple connection methods.
More info: The impacted connection methods consist of the following:
- Outlook on the web
- Exchange ActiveSync (EAS)
Current status: We've identified an internal sever error that's contributing to impact and we're further investigating this error to better understand why it's occurring so that we can develop an appropriate remediation plan.
Scope of impact: Users in North America and South America attempting to access their Exchange Online mailboxes through Outlook on the web and EAS may be impacted by this event. This information may be updated as our investigation continues.
Next update by: Saturday, February 28, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 21:53:08 2026 |
|---|
| Description: | Title: Users may be unable to access their Exchange Online mailboxes through a couple connection methods
User impact: Users may be unable to access their Exchange Online mailboxes through a couple connection methods.
More info: The impacted connection methods consist of the following:
- Outlook on the web
- Exchange ActiveSync (EAS)
Current status: We're reviewing our service telemetry to isolate any errors or failures that can help point to the cause of impact and to identify a remediation plan.
Scope of impact: Users in North America and South America attempting to access their Exchange Online mailboxes through Outlook on the web and EAS may be impacted by this event. This information may be updated as our investigation continues.
Next update by: Saturday, February 28, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Fri Feb 27 21:33:37 2026 |
|---|
| Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|---|
|
TM1217690 - Some users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Thu Dec 11 22:10:00 2025 |
|---|
| End Time: | Wed Feb 25 20:30:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 27 02:06:03 2026 |
|---|
| Root Cause: | A latent code issue was affecting the request flow leveraged for SharePoint Online list link access within Microsoft Teams on iOS and resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 27 02:05: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 have been unable to open some SharePoint Online list links through Microsoft Teams on iOS and received an error.
More info: Specifically, users who attempted to access SharePoint lists through Teams on iOS may have received an access permissions error stating: "Permission required - You do not have permission to open this file."
While we were focused on remediation, users on iOS could’ve accessed 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 could’ve used these to avoid impact.
Final status: Our update containing the fix has completed deploying to the entirety of the affected infrastructure and we’ve confirmed through internal testing that the issue is resolved.
Scope of impact: Any users who attempted to access SharePoint lists through links shared on Microsoft Teams while on iOS may have been impacted.
Start time: Friday, December 12, 2025, at 3:10 AM UTC
End time: Thursday, February 26, 2026, at 1:30 AM UTC
Root cause: A latent code issue was affecting the request flow leveraged for SharePoint Online list link access within Microsoft Teams on iOS and resulted in impact.
Next steps:
- We're investigating further into the latent code issue to better understand how it was introduced and why it wasn't caught prior sooner so that we can prevent impact to SharePoint Online list links through Microsoft Teams on iOS in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 25 03:41:49 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 has been successfully deployed to half of the affected infrastructure. We're expecting full remediation of impact by the end of February 2026.
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
Estimated time to resolve: Friday, February 27, 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 by: Friday, February 27, 2026, at 8:30 AM UTC
|
|---|
|
| 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.
|
|---|
|
OP1237616 - Some admins may experience intermittent page loading issues and errors in the Microsoft 365 Apps admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 16 01:30:00 2026 |
|---|
| End Time: | Tue Feb 24 19:00:00 2026 |
|---|
| Service: | Microsoft 365 apps |
|---|
| Feature Group: | Office Client issues |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Thu Feb 26 17:54:45 2026 |
|---|
| Root Cause: | Service infrastructure adjustments to help improve reliability within the Microsoft 365 Apps admin center were intermittently producing page loading failures in the Microsoft 365 Apps admin center. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 26 17:54:45 2026 |
|---|
| Description: | Title: Some admins may experience intermittent page loading issues and errors in the Microsoft 365 Apps admin center
User impact: Admins may have experienced intermittent page loading issues in the Microsoft 365 Apps admin center.
More info: Impacted admins reported that config.office.com pages intermittently failed to load and resulted in errors.
Final status: After our additional system monitoring to ensure that service availability remained constant after our service infrastructure adjustments, we've validated that impact has been remediated.
Scope of impact: This issue may have intermittently impacted admins who were attempting to access and load certain pages in the Microsoft 365 Apps admin center.
Start time: Monday, February 16, 2026, at 6:30 AM UTC
End time: Wednesday, February 25, 2026, at 12:00 AM UTC
Root cause: Service infrastructure adjustments to help improve reliability within the Microsoft 365 Apps admin center were intermittently producing page loading failures in the Microsoft 365 Apps admin center.
Next steps:
- We're further analyzing the isolated offending service infrastructure adjustments to help us prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 25 19:05:22 2026 |
|---|
| Description: | Title: Some admins may experience intermittent page loading issues and errors in the Microsoft 365 Apps admin center
User impact: Admins may experience intermittent page loading issues in the Microsoft 365 Apps admin center.
More info: Impacted admins report that config.office.com pages intermittently fail to load and result in errors.
Current status: We're continuing to monitor the environment to validate if our optimizations have remediated impact. This period of monitoring will help us validate if any additional actions are needed to resolve this issue.
Scope of impact: This issue may intermittently impact admins who are attempting to access and load certain pages in the Microsoft 365 Apps admin center. This section may be updated as our investigation continues.
Start time: Monday, February 16, 2026, at 6:30 AM UTC
Root cause: Service infrastructure adjustments to help improve reliability within the Microsoft 365 Apps admin center are intermittently producing page loading failures in the Microsoft 365 Apps admin center.
Next update by: Friday, February 27, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Feb 25 15:29:19 2026 |
|---|
| Description: | Title: Some admins may experience intermittent page loading issues and errors in the Microsoft 365 Apps admin center
User impact: Admins may experience intermittent page loading issues in the Microsoft 365 Apps admin center.
More info: Impacted admins report that config.office.com pages intermittently fail to load and result in errors.
Current status: Our initial telemetry analysis indicates that the optimizations performed have had a positive effect on the page loads. We're continuing to monitor the environment to validate this issue is no longer occurring.
Scope of impact: This issue may intermittently impact admins who are attempting to access and load certain pages in the Microsoft 365 Apps admin center. This section may be updated as our investigation continues.
Start time: Monday, February 16, 2026, at 6:30 AM UTC
Root cause: Service infrastructure adjustments to help improve reliability within the Microsoft 365 Apps admin center are intermittently producing page loading failures in the Microsoft 365 Apps admin center.
Next update by: Thursday, February 26, 2026, at 1:00 AM UTC
|
|---|
|
| Time: | Tue Feb 24 12:51:02 2026 |
|---|
| Description: | Title: Some admins may experience intermittent page loading issues and errors in the Microsoft 365 Apps admin center
User impact: Admins may experience intermittent page loading issues in the Microsoft 365 Apps admin center.
More info: Impacted admins report that config.office.com pages intermittently fail to load and result in errors.
Current status: Our service health telemetry and admin data analysis has determined that adjustments to service infrastructure in our effort to improve reliability within the Microsoft 365 Apps admin center are producing intermittent page loading failures that are resulting in the impact. We've deployed a fix to address the page loading failures and expect to have more clarity into the problems that were produced by our change, along with an update on our timeline for remediating the impact, by our next scheduled communication update.
Scope of impact: This issue may intermittently impact admins who are attempting to access and load certain pages in the Microsoft 365 Apps admin center. This section may be updated as our investigation continues.
Root cause: Service infrastructure adjustments to help improve reliability within the Microsoft 365 Apps admin center are intermittently producing page loading failures in the Microsoft 365 Apps admin center.
Next update by: Wednesday, February 25, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Mon Feb 23 17:01:17 2026 |
|---|
| Description: | Title: Some admins may experience intermittent page loading issues and errors in the Microsoft 365 Apps admin center
User impact: Admins may experience intermittent page loading issues in the Microsoft 365 Apps admin center.
More info: Impacted admins report that config.office.com pages intermittently fail to load and result in errors.
Current status: We're continuing to analyze service health telemetry and data provided by impacted admins as we investigate into this issue's root cause and determine our next troubleshooting steps.
Scope of impact: This issue may intermittently impact admins who are attempting to access and load certain pages in the Microsoft 365 Apps admin center. This section may be updated as our investigation continues.
Next update by: Tuesday, February 24, 2026, at 7:00 PM
|
|---|
|
| Time: | Mon Feb 23 14:11:46 2026 |
|---|
| Description: | Title: Some admins may experience intermittent page loading issues and errors in the Microsoft 365 Apps admin center
User impact: Admins may experience intermittent page loading issues in the Microsoft 365 Apps admin center.
More info: Impacted admins report that config.office.com pages intermittently fail to load and result in errors.
Current status: We're reviewing service healthy telemetry and data from impacted admins as we investigate into this issue's root cause.
Scope of impact: This issue may intermittently impact admins who are attempting to access and load certain pages in the Microsoft 365 Apps admin center. This section may be updated as our investigation continues.
Next update by: Tuesday, February 24, 2026, at 12:30 AM UTC
|
|---|
|
MO1181369 - Users may see issues accessing some Microsoft 365 services and portals
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Wed Oct 29 11:41:00 2025 |
|---|
| End Time: | Wed Oct 29 20:05:00 2025 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Thu Feb 26 07:15:25 2026 |
|---|
| Root Cause: | An inadvertent configuration change within Azure Front Door (AFD) triggered a widespread service disruption affecting Microsoft services dependent on AFD for global content delivery. More information is provided within the Post-Incident Report. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Thu Feb 26 07:15:25 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Dec 4 16:38:30 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Nov 12 15:06:54 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Nov 5 19:41:06 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Fri Oct 31 19:29:02 2025 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Wed Oct 29 22:11:03 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may have seen issues accessing some Microsoft 365 services and portals.
More info: Impacted scenarios included, but may not have been limited to the following:
- Access to some Microsoft Entra, Microsoft Power Apps, Microsoft Intune, and Microsoft Defender functions.
- Microsoft Purview Information Protection (MIP), Data Lifecycle Management (DLM), eDiscovery, Microsoft Purview Insider Risk Management (IRM), Communications Compliance, Data Governance, and other related Microsoft Purview features.
- Access to the Exchange admin center (EAC), security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls. Users may also see transcription failures and issues leveraging Copilot within meetings.
- High latency, timeouts, errors, or inaccessibility of Microsoft Copilot Dashboards, Copilot Analytics Power BI reports, and advanced reporting capabilities.
- Intermittent connectivity and device discovery issues for Windows 365 Cloud PC users, and issues for admins performing device actions and provisioning new Cloud PCs.
Final status: After extended monitoring, we confirmed that impact stemming from the Azure configuration change has been resolved.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may have been impacted.
Start time: Wednesday, October 29, 2025, 3:41 PM UTC
End time: Thursday, October 30, 2025, at 12:05 AM UTC
Root cause: An inadvertent configuration change within Azure Front Door (AFD) triggered a widespread service disruption affecting Microsoft services dependent on AFD for global content delivery. More information is provided within the Post-Incident Report.
Next steps:
-For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We've provided a Post-Incident Report for this incident. Additionally, we'll periodically be updating the Post-Incident Report to show the status of the Next Steps. The next update will be provided on Tuesday, March 31, 2026.
|
|---|
|
| Time: | Wed Oct 29 20:58:03 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may see issues accessing some Microsoft 365 services and portals.
More info: Impacted scenarios include, but may not be limited to the following:
- Access to some Microsoft Entra, Microsoft Power Apps, Microsoft Intune, and Microsoft Defender functions.
- Microsoft Purview Information Protection (MIP), Data Lifecycle Management (DLM), eDiscovery, Microsoft Purview Insider Risk Management (IRM), Communications Compliance, Data Governance, and other related Microsoft Purview features.
- Access to the Exchange admin center (EAC), security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls. Users may also see transcription failures and issues leveraging Copilot within meetings.
- High latency, timeouts, errors, or inaccessibility of Microsoft Copilot Dashboards, Copilot Analytics Power BI reports, and advanced reporting capabilities.
- Intermittent connectivity and device discovery issues for Windows 365 Cloud PC users, and issues for admins performing device actions and provisioning new Cloud PCs.
Current status: We've confirmed that service health has largely recovered; however, user reports of impact haven't yet returned to pre-incident thresholds. We're continuing to monitor the service to ensure full recovery.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted.
Start time: Wednesday, October 29, 2025, 3:45 PM UTC
Preliminary root cause: A problematic configuration change was applied to a portion of Azure infrastructure.
Next update by: Thursday October 30, 2025, at 2:30 AM UTC
|
|---|
|
| Time: | Wed Oct 29 19:26:42 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may see issues accessing some Microsoft 365 services and portals.
More info: Impacted scenarios include, but may not be limited to the following:
- Access to some Microsoft Entra, Microsoft Power Apps, Microsoft Intune, and Microsoft Defender functions.
- Microsoft Purview Information Protection (MIP), Data Lifecycle Management (DLM), eDiscovery, Microsoft Purview Insider Risk Management (IRM), Communications Compliance, Data Governance, and other related Microsoft Purview features.
- Access to the Exchange admin center (EAC), security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls. Users may also see transcription failures and issues leveraging Copilot within meetings.
- High latency, timeouts, errors, or inaccessibility of Microsoft Copilot Dashboards, Copilot Analytics Power BI reports, and advanced reporting capabilities.
- Intermittent connectivity and device discovery issues for Windows 365 Cloud PC users, and issues for admins performing device actions and provisioning new Cloud PCs.
Current status: Our configuration deployment and traffic rebalancing is showing steady service health improvement for scenarios listed in the "More info" section of this communication. Some users may experience residual impact until availability fully recovers. We're monitoring for an extended period to ensure service health is restored as expected.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted.
Start time: Wednesday, October 29, 2025, 3:45 PM UTC
Preliminary root cause: A problematic configuration change was applied to a portion of Azure infrastructure.
Next update by: Thursday October 30, 2025, at 1:00 AM UTC
|
|---|
|
| Time: | Wed Oct 29 15:59:57 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may see issues accessing some Microsoft 365 services and portals.
More info: We've edited the Title, User impact, and More info sections of this communication to align with our current understanding of the affected scenarios.
Impacted scenarios include, but may not be limited to the following:
- Access to some Microsoft Entra, Microsoft Power Apps, Microsoft Intune, and Microsoft Defender functions.
- Microsoft Purview Information Protection (MIP), Data Lifecycle Management (DLM), eDiscovery, Microsoft Purview Insider Risk Management (IRM), Communications Compliance, Data Governance, and other related Microsoft Purview features.
- Access to the Exchange admin center (EAC), security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls. Users may also see transcription failures and issues leveraging Copilot within meetings.
- High latency, timeouts, errors, or inaccessibility of Microsoft Copilot Dashboards, Copilot Analytics Power BI reports, and advanced reporting capabilities.
- Intermittent connectivity and device discovery issues for Windows 365 Cloud PC users, and issues for admins performing device actions and provisioning new Cloud PCs.
Current status: We've completed the deployment of a healthy configuration and we're continuing our active traffic balancing efforts as well as monitoring corresponding service telemetry to ensure widespread recovery.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, October 29, 2025, 3:45 PM UTC
Preliminary root cause: A problematic configuration change was applied to a portion of Azure infrastructure.
Next update by: Wednesday, October 29, 2025, at 11:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 15:11:53 2025 |
|---|
| Description: | Current status: We've completed the deployment of the previous healthy configuration and are actively rebalancing traffic across healthy infrastructure to actualize recovery across the affected services.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Oct 29 14:35:04 2025 |
|---|
| Description: | Title: Users may see issues accessing some Microsoft 365 services and portals
User impact: Users may see issues accessing some Microsoft 365 services and portals.
More info: We've edited the Title, User impact, and More info sections of this communication to align with our current understanding of the affected scenarios.
Impacted scenarios include, but may not be limited to the following:
- Access to some Microsoft Entra, Microsoft Purview, Microsoft Defender, Microsoft Power Apps and Microsoft Intune functions. For example, Microsoft Defender for Cloud Apps policies may not be applying as expected.
- Access to security.microsoft.com, learn.microsoft.com, and other portals accessed through microsoft.com.
- Issues with add-ins and network connectivity in Outlook.
- Degraded functionality to some workflows within Microsoft Teams, including impact to location data in support of emergency calls.
Current status: We're deploying a previous healthy configuration to the affected portions of infrastructure to resolve this issue. This is being done in tandem with efforts to rebalance traffic across healthy infrastructure to achieve recovery as quickly as possible.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted. This information may be updated as our investigation continues.
Start time: Wednesday, October 29, 2025, 3:45 PM UTC
Preliminary root cause: A problematic configuration change was applied to a portion of Azure infrastructure.
Next update by: Wednesday, October 29, 2025, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 13:50:57 2025 |
|---|
| Description: | Current status: We've halted the rollout of the impacting configuration change. We're continuing our efforts to route service traffic away from affected infrastructure where the change was already applied, to recover service availability as quickly as possible. In parallel, we're working to revert the impacted infrastructure to a previous healthy state.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Oct 29 13:17:13 2025 |
|---|
| Description: | Title: Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services
User impact: Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services.
More info: Additionally, admins are reporting issues when attempting to access some Microsoft Entra, Microsoft Purview, Microsoft Defender, Microsoft Power Apps and Microsoft Intune functions. Users are also seeing issues with add-ins and network connectivity in Outlook.
Current status: We've identified a recent configuration change to a portion of Azure infrastructure which we believe is causing the impact. We're pursuing multiple remediation strategies, including moving traffic away from the impacted infrastructure and blocking the offending change. We'll provide an estimated recovery time as soon as possible.
Scope of impact: Any users attempting to access Microsoft 365 services, such as those detailed in the more info section above, may be impacted. This information may be updated as our investigation continues.
Next update by: Wednesday, October 29, 2025, at 7:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 12:36:49 2025 |
|---|
| Description: | Current status: We're rerouting affected traffic to alternate healthy infrastructure as a near-term resolution while our investigation into the source of the issue is ongoing.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Oct 29 12:28:13 2025 |
|---|
| Description: | Current status: We're reviewing network and hosting infrastructure health to determine why the service is in an unhealthy state.
This quick update is designed to give the latest information on this issue.
|
|---|
|
| Time: | Wed Oct 29 12:21:29 2025 |
|---|
| Description: | Title: Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services
User impact: Users may be unable to access the Microsoft 365 admin center and see delays when accessing other Microsoft 365 services.
More info: Additionally, admins are reporting issues when attempting to access some Microsoft Purview and Microsoft Intune functions. Users are also seeing issues with add-ins and network connectivity in Outlook.
Current status: We're reviewing reports of an issue impacting Microsoft Azure and Microsoft 365 services, including impact to the Microsoft 365 admin center and other services, including but not limited to those described in the more info section of this communication. We're reviewing corresponding service telemetry to isolate the cause of the issue and determine our next troubleshooting steps.
Scope of impact: Any users attempting to access Microsoft 365 services may be impacted.
Next update by: Wednesday, October 29, 2025, at 5:30 PM UTC
|
|---|
|
| Time: | Wed Oct 29 12:07:49 2025 |
|---|
| Description: | Title: We're receiving reports of a potential problem impacting Microsoft 365 services
User impact: We're looking into a potential problem impacting Microsoft 365 services.
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.
|
|---|
|
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: | Wed Feb 25 20:58:46 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, March 20, 2026, at 6:00 PM UTC |
|---|
|
Details
| Time: | Fri Feb 20 12:58:51 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We're continuing to work toward delivering the additional localization fix, and we expect this process to take additional time due to the complexity involved in implementing the solution. Based on our current estimates, remediation is targeted for a release window of May 2026. We'll provide further updates as this process progresses.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, March 20, 2026, at 6:00 PM UTC
|
|---|
|
| Time: | Fri Jan 16 14:58:23 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: While we’ve developed an additional fix for the localization issues, the complexity of delivering this solution is preventing an expedited resolution. We expect this process to take several weeks as we validate the subtasks involved in instituting the fix. We’ll provide updates on this process and a timeline for deployment once the subtask orchestration is complete.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, February 20, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Fri Jan 9 13:12:08 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’re continuing to assess and validate alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 16, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Jan 6 12:35:31 2026 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve identified that the previously developed code fix isn’t an effective solution for addressing the incorrect service names and descriptions. We’re assessing and validating alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 9, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Tue Dec 9 12:44:40 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: Validation of the code fix is continuing to progress, and due to the complex nature of the code developed to address the incorrect service names and descriptions, we're still expecting the deployment to complete by March 2026. We'll provide a more accurate timeline as one becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, January 6, 2026, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Dec 8 03:18:26 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We are continuing to validate the fix’s effectiveness and anticipate full deployment by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, December 9, 2025, at 7:00 PM UTC
|
|---|
|
| Time: | Mon Nov 24 05:20:30 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve developed a code fix to address the issue. It’s currently undergoing validation to ensure effectiveness, and we expect the fix to be fully implemented and remediate impact by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, 8 December 2025, at 10:30 AM UTC
|
|---|
|
| Time: | Sun Nov 23 16:12:56 2025 |
|---|
| Description: | Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We've identified a recent Windows update that is producing incorrect service names and descriptions in Services and the Event Viewer for some users who have upgraded to Windows 11 in or after June of 2025. As we work to confirm an accurate window of impact, we're developing a code fix to address the offending change and to remediate the impact. We'll provide an updated timeline for the deployment of our fix and the remediation of impact once our internal validations have completed.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, November 24, 2025, at 10:30 AM UTC
|
|---|
|
CP1237705 - Admins may not see proper usernames or display names within Microsoft Copilot reports in the Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Thu Feb 19 19:00:00 2026 |
|---|
| End Time: | Tue Feb 24 20:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 25 18:19:06 2026 |
|---|
| Root Cause: | An issue with our data importer feed configuration was causing intermittent decryption failures within the Copilot data ingestion pipeline for the Copilot Usage and Copilot Chat reports. Under specific conditions, encrypted payloads could not have been successfully decrypted, which resulted in data being displayed improperly. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 25 18:19:06 2026 |
|---|
| Description: | Title: Admins may not see proper usernames or display names within Microsoft Copilot reports in the Microsoft 365 admin center
User impact: Admins may have not seen proper usernames or display names within Copilot reports in the Microsoft 365 admin center.
More info: Values in the username and display name columns of the usage details section in the Copilot Usage and Copilot Chat reports may have appeared as an encrypted value instead of the actual data.
Final status: We've confirmed after testing with a subset of affected users that our code fix remediated the impact.
Scope of impact: This issue may have impacted admins in North America, Europe, and Asia Pacific regions, and admins in those regions may not have seen proper usernames or display names within Copilot reports in the Microsoft 365 admin center.
Start time: Friday, February 20, 2026, at 12:00 AM UTC
End time: Wednesday, February 25, 2026, at 1:00 AM UTC
Root cause: An issue with our data importer feed configuration was causing intermittent decryption failures within the Copilot data ingestion pipeline for the Copilot Usage and Copilot Chat reports. Under specific conditions, encrypted payloads could not have been successfully decrypted, which resulted in data being displayed improperly.
Next steps:
- We're reviewing the configuration of the data importer feed to identify why it caused decryption failures and what introduced this problematic configuration, so that we can determine how to prevent similar impact from occurring in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 24 18:22:05 2026 |
|---|
| Description: | Title: Admins may not see proper usernames or display names within Microsoft Copilot reports in the Microsoft 365 admin center
User impact: Admins may not see proper usernames or display names within Copilot reports in the Microsoft 365 admin center.
More info: Values in the username and display name columns of the usage details section in the Copilot Usage and Copilot Chat reports may appear as an encrypted value instead of the actual data.
Current status: We've confirmed our developed code fix has successfully deployed to the North America region and are continuing to monitor the fix as it saturates throughout the Europe and Asia Pacific regions. We’re reaching out to a subset of affected admins in the North America region to validate that impact has been remediated through this code fix, and expect that the Europe and Asia Pacific regions will likewise be ready for remediation validation by our next scheduled update.
Scope of impact: This issue may impact admins in North America, Europe, and Asia Pacific regions, and admins in those regions may not see proper usernames or display names within Copilot reports in the Microsoft 365 admin center. This section may be updated as our investigation continues.
Start time: Friday, February 20, 2026, at 12:00 AM UTC
Root cause: An issue with our data importer feed configuration is causing intermittent decryption failures within the Copilot data ingestion pipeline for the Copilot Usage and Copilot Chat reports. Under specific conditions, encrypted payloads could not be successfully decrypted, which resulted in data being displayed improperly.
Next update by: Thursday, February 26, 2026, at 12:30 AM UTC
|
|---|
|
| Time: | Mon Feb 23 17:57:45 2026 |
|---|
| Description: | Title: Users may not see proper usernames or display names within Microsoft Copilot reports in the Microsoft 365 admin center
User impact: Users may not see proper usernames or display names within Copilot reports in the Microsoft 365 admin center.
More info: Values in the username and display name columns of the usage details section in the Copilot Usage and Copilot Chat reports may appear as an encrypted value instead of the actual data.
Current status: We identified an issue in our data importer configuration that is causing intermittent decryption failure within the Copilot data ingestion pipeline for the Copilot Usage and Copilot Chat reports, which is resulting in this impact. We’ve developed a code fix and are in the process of deploying it to all affected regions. We will provide an update on this deployment timeline as soon as one becomes available.
Scope of impact: This issue may impact users in North America, Europe, and Asia Pacific (APAC) regions, and users in those regions may not see proper usernames or display names within Copilot reports in the Microsoft 365 admin center. This section may be updated as our investigation continues.
Start time: Friday, February 20, 2026, at 12:00 AM UTC
Root cause: An issue with our data importer feed configuration is causing intermittent decryption failures within the Copilot data ingestion pipeline for the Copilot Usage and Copilot Chat reports. Under specific conditions, encrypted payloads could not be successfully decrypted, which resulted in data being displayed improperly.
Next update by: Wednesday, February 25, 2026, at 12:30 AM UTC
|
|---|
|
PB1238769 - Some users using the January 2026 Report Server version (1.25.9508.3237) may have encountered access issues
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 20 19:00:00 2026 |
|---|
| End Time: | Wed Feb 25 10:00:00 2026 |
|---|
| Service: | Power BI |
|---|
| Feature Group: | PowerBI.com |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 25 10:24:05 2026 |
|---|
| Root Cause: | An issue with the January 2026 Report Server version (1.25.9508.3237) may have caused access issues, as certain reports could have triggered excessive crash dump generation on disk. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 25 10:24:05 2026 |
|---|
| Description: | Title: Some users using the January 2026 Report Server version (1.25.9508.3237) may have encountered access issues
User impact: Users using the January 2026 Report Server version (1.25.9508.3237) may have encountered access issues.
More info: Users using the January 2026 Report Server version (1.25.9508.3237) may have encountered access issues, as certain reports may have triggered excessive crash dump generation on disks. As a workaround, users could have downgraded to the September 2025 version (1.15.8377.1837) or deleted the generated crash dump files due to a known limitation.
Final status: We've determined that an issue with the January 2026 Report Server version (1.25.9508.3237) may have caused access issues, as certain reports could have triggered excessive crash dump generation on disk. We've reverted to the previous working version September 2025 version (1.15.8377.1837), which has remediated impact.
Scope of impact: Impact was specific to users using the January 2026 Report Server version (1.25.9508.3237).
Start time: Wednesday, January 21, 2026, at 12:00 AM UTC
End time: Wednesday, February 25, 2026, at 3:00 PM UTC
Root cause: An issue with the January 2026 Report Server version (1.25.9508.3237) may have caused access issues, as certain reports could have triggered excessive crash dump generation on disk.
Next steps:
- We're continuing to identify the underlying root cause of impact within the January 2026 Report Server version (1.25.9508.3237).
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 25 08:32:34 2026 |
|---|
| Description: | Title: Some users using the January 2026 Report Server version (1.25.9508.3237) may encounter access issues
User impact: Users using the January 2026 Report Server version (1.25.9508.3237) may encounter access issues.
More info: Users using the January 2026 Report Server version (1.25.9508.3237) may encounter access issues, as certain reports can trigger excessive crash dump generation on disk. As a workaround, users can downgrade to the September 2025 version (1.15.8377.1837) or may delete the generated crash dump files due to a known limitation.
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 users using the January 2026 Report Server version (1.25.9508.3237).
Start time: Wednesday, January 21, 2026, at 12:00 AM UTC
Next update by: Wednesday, February 25, 2026, at 3:30 PM UTC
|
|---|
|
IT1237713 - Admins may be unable to update the MacOS Wi-Fi policy in the Microsoft Intune admin center
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 10 11:00:00 2026 |
|---|
| End Time: | Tue Feb 24 14:00:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 24 15:57:38 2026 |
|---|
| Root Cause: | An issue with a property update that was introduced in Microsoft Intune build 6.2602.7.2001 was preventing MacOS Wi-Fi policy updates through Microsoft Intune. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 24 15:57:38 2026 |
|---|
| Description: | Title: Admins may be unable to update the MacOS Wi-Fi policy in the Microsoft Intune admin center
User impact: Admins may have been unable to update the MacOS Wi-Fi policy in the Microsoft Intune admin center.
More info: This affected all MacOS devices on Microsoft Intune build 6.2602.7.2001 forward. As a work around, admins could have used Microsoft Graph API to update the MacOS Wi-Fi policy.
Final status: he fix has completed its deployment, and we've validated that this issue is no longer occurring using internal testing and service telemetry.
Scope of impact: This may have affected any admin updating the MacOS Wi-Fi policy for users on build 6.2602.7.2001 forward through Microsoft Intune.
Start time: Tuesday, February 10, 2026, at 4:00 PM UTC
End time: Tuesday, February 24, 2026, at 7:00 PM UTC
Root cause: An issue with a property update that was introduced in Microsoft Intune build 6.2602.7.2001 was preventing MacOS Wi-Fi policy updates through Microsoft Intune.
Next steps:
- We're continuing our analysis of the impacting change to better understand the underlying cause of impact and prevent similar issues in the future.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 24 00:42:43 2026 |
|---|
| Description: | Title: Admins may be unable to update the MacOS Wi-Fi policy in Microsoft Intune
User impact: Admins may be unable to update the MacOS Wi-Fi policy in Microsoft Intune.
More info: This affects all MacOS users on Microsoft Intune build 6.2602.7.2001 forward. As a work around, admins can use Microsoft Graph API to update the MacOS Wi-Fi policy.
Current status: We validated that the fix for the MacOS Wi-Fi policy and have started the deployment to the remaining affected environment. We'll monitor the deployment to ensure that the impact is remediated.
Scope of impact: This may affect all admins updating the MacOS Wi-Fi policy for users on build 6.2602.7.2001 forward through Microsoft Intune.
Start time: Tuesday, February 10, 2026, at 4:00 PM UTC
Root cause: An issue with a property update that was introduced in Microsoft Intune build 6.2602.7.2001 is preventing MacOS Wi-Fi policy updates through Microsoft Intune.
Next update by: Tuesday, February 24, 2026, at 10:00 PM UTC
|
|---|
|
| Time: | Mon Feb 23 21:07:49 2026 |
|---|
| Description: | Title: Admins may be unable to update the MacOS Wi-Fi policy in Microsoft Intune
User impact: Admins may be unable to update the MacOS Wi-Fi policy in Microsoft Intune.
More info: This affects all MacOS users on Microsoft Intune build 6.2602.7.2001 forward. As a work around, admins can use Microsoft Graph API to update the MacOS Wi-Fi policy.
Current status: The validation of our fix for the MacOS Wi-Fi policy updates is underway. Once validation completes, we'll begin deployment to the affected environment.
Scope of impact: This may affect all admins updating the MacOS Wi-Fi policy for users on build 6.2602.7.2001 forward through Microsoft Intune.
Start time: Tuesday, February 10, 2026, at 4:00 PM UTC
Root cause: An issue with a property update that was introduced in Microsoft Intune build 6.2602.7.2001 is preventing MacOS Wi-Fi policy updates through Microsoft Intune.
Next update by: Tuesday, February 24, 2026, at 7:00 AM UTC
|
|---|
|
| Time: | Mon Feb 23 18:17:07 2026 |
|---|
| Description: | Title: Admins may be unable to update the MacOS Wi-Fi policy in Microsoft Intune
User impact: Admins may be unable to update the MacOS Wi-Fi policy in Microsoft Intune.
More info: This affects all MacOS users on Microsoft Intune build 6.2602.7.2001 forward. As a work around, admins can use Microsoft Graph API to update the MacOS Wi-Fi policy.
Current status: We've identified a property update that was introduced in build 6.2602.7.2001 that’s preventing MacOS Wi-Fi policy updates through Microsoft Intune. We’ve developed a solution and are working on final reviews before deploying. We’ll provide a further update on deployment of this solution with our next communication update.
Scope of impact: This may affect all admins updating the MacOS Wi-Fi policy for users on build 6.2602.7.2001 forward through Microsoft Intune.
Start time: Tuesday, February 10, 2026, at 4:00 PM UTC
Root cause: An issue with a property update that was introduced in Microsoft Intune build 6.2602.7.2001 is preventing MacOS Wi-Fi policy updates through Microsoft Intune.
Next update by: Tuesday, February 24, 2026, at 3:00 AM UTC
|
|---|
|
IT1238217 - Some users may have been unable to register their devices with Microsoft Intune and receive an error
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 24 08:45:00 2026 |
|---|
| End Time: | Tue Feb 24 10:40:00 2026 |
|---|
| Service: | Microsoft Intune |
|---|
| Feature Group: | Microsoft Intune |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Feb 24 13:13:14 2026 |
|---|
| Root Cause: | A portion of service infrastructure that's responsible for handling registration requests was processing requests at an inefficient rate, resulting in failures during the process and subsequent impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 24 12:11:30 2026 |
|---|
| Description: | Title: Some users may have been unable to register their devices with Microsoft Intune and receive an error
User impact: Users may have been unable to register their devices with Microsoft Intune and received an error.
Final status: Further investigation has clarified that this event specifically affected user device enrollment. The Title, User impact, and Scope of impact sections of this update have been updated to reflect this. Our review of the service-side telemetry also revealed the need for additional optimization of our service infrastructure. We've applied those optimizations and confirmed after a period of monitoring that this has successfully remediated the issue.
Scope of impact: This issue may have impacted some users who were attempting to register their devices with Microsoft Intune.
Start time: Tuesday, February 24, 2026, at 1:45 PM UTC
End time: Tuesday, February 24, 2026, at 3:40 PM UTC
Root cause: A portion of service infrastructure that's responsible for handling registration requests was processing requests at an inefficient rate, resulting in failures during the process and subsequent impact.
Next steps:
- We're continuing our review of the inefficiency during these registration requests to better understand how the issue was introduced so we can prevent further instances of this issue from reoccurring.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 24 10:34:02 2026 |
|---|
| Description: | Title: Users may experience issues accessing or using the Microsoft Intune service
User impact: Users may experience issues accessing or using the Microsoft Intune service.
Current status: We're investigating a potential issue and are analyzing service telemetry to help us identify the root cause.
Scope of impact: This issue may have impacted some users who were attempting to register their devices with Microsoft Intune.
Next update by: Tuesday, February 24, 2026, at 5:30 PM UTC
|
|---|
|
CW1226324 - Some users' Copilot prompts return information from Sent and Draft folder messages with Copilot DLP policies configured
| Status: | serviceRestored |
|---|
| Start Time: | Wed Jan 21 02:25:00 2026 |
|---|
| End Time: | Mon Feb 23 19:09:00 2026 |
|---|
| Service: | Microsoft 365 Copilot Chat |
|---|
| Feature Group: | Microsoft 365 Copilot Chat |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 24 01:09:33 2026 |
|---|
| Root Cause: | A code issue was 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: | N/A |
|---|
|
Details
| Time: | Tue Feb 24 01:05:21 2026 |
|---|
| Description: | Title: Some users' Copilot prompts return information from Sent and Draft folder messages with Copilot DLP policies configured
User impact: Users' Copilot prompts return information from Sent and Draft folder messages with Copilot DLP policies configured.
More info: This issue was specific to Exchange Online email messages that were in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may have processed these email messages for the user that owned them even though these email messages had a sensitivity label applied, a Copilot DLP policy is configured.
Final status: We have successfully deployed a targeted fix across all impacted environments. The root cause has been addressed, and customers should not experience this issue with email messages going forward.
Scope of impact: Impact was specific to users leveraging Microsoft 365 Copilot Chat with email messages in their Drafts or Sent Items folder with a sensitivity label applied and a Copilot DLP policy configured.
Start time: Wednesday, January 21, 2026, at 7:25 AM UTC
End time: Tuesday, February 24, 2026, at 12:09 AM UTC
Root cause: A code issue was allowing items in the Sent items and Draft folders to be picked up by Copilot even though confidential labels are set in place.
Next steps:
- We are refining our procedures to make our service even more resilient moving forward.
This is the final update for this event.
|
|---|
|
| Time: | Thu Feb 19 20:03:56 2026 |
|---|
| Description: | Title: Some users' Copilot prompts return information from Sent and Draft folder messages with Copilot DLP policies configured
User impact: Users' Copilot prompts return information from Sent and Draft folder messages with Copilot DLP policies configured.
More info: This issue is specific to Exchange Online email messages that are in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may process these email messages for the user that owns them even though these email messages have a sensitivity label applied and a Copilot DLP policy is configured.
Current status: Our targeted code fix to prevent further impact is moving forward and has saturated across the majority of affected environments. Our deployment remains in progress only for a small section of our more complex service environments. As such, we believe the root cause of this issue has been addressed for most customers, and no new email messages for customers who have received the fix will be affected moving forward.
We’re now completing a longer-term, comprehensive sync to apply this fix retroactively to previously affected messages within the Sent and Draft folders to fully remediate the impact.
Scope of impact: Impact is specific to users leveraging Microsoft 365 Copilot Chat with email messages in their Drafts or Sent Items folder with a sensitivity label applied and a Copilot DLP policy configured. 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: Tuesday, February 24, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Thu Feb 19 03:33:57 2026 |
|---|
| Description: | Title: Some users' Copilot prompts return information from Sent and Draft folder messages with Copilot DLP policies configured
User impact: Users' Copilot prompts return information from Sent and Draft folder messages with Copilot DLP policies configured.
More info: This issue is specific to Exchange Online email messages that are in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may process these email messages for the user that owns them even though these email messages have a sensitivity label applied and a Copilot DLP policy is configured.
Current status: We've received feedback from some affected users that the deployment fix has resolved impact. We're monitoring the fix as it fully saturates in the remaining affected environments, and we expect full remediation by our next scheduled update.
Scope of impact: Users leveraging Microsoft 365 Copilot Chat may notice that email messages in their Drafts or Sent Items folder may be referenced in prompt responses even though these messages may have a sensitivity label applied and a Copilot DLP policy configured. 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: Tuesday, February 24, 2026, at 7:30 AM UTC
|
|---|
|
| Time: | Wed Feb 18 21:27:38 2026 |
|---|
| Description: | Title: Users may notice Copilot prompts returning information from Sent and Draft folder messages with DLP policies configured
User impact: Users may notice Copilot prompts returning information from Sent and Draft folder messages with DLP policies configured.
More info: This issue is specific to Exchange Online email messages that are in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may process these email messages for the user that owns them even though these email messages have a sensitivity label applied and a DLP policy is configured.
Current status: We have completed deployment of the fix and we’re working with affected users to confirm that the issue is mitigated.
Scope of impact: Users leveraging Microsoft 365 Copilot Chat may notice that email messages in their Drafts or Sent Items folder may be referenced in prompt responses even though these messages may have a sensitivity label applied and a DLP policy configured. 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: Thursday, February 19, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Wed Feb 18 12:12:22 2026 |
|---|
| Description: | Title: Users' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat
User impact: Users' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat.
More info: This issue is specific to Exchange Online email messages that are in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may process these email messages for the user that owns them even though these email messages have a sensitivity label applied and a DLP policy is configured.
Current status: We're continuing to monitor the final stages of our fix deployment as it saturates throughout the remaining affected infrastructure. Once this saturation is complete, we'll reach out to additional users to verify impact has been remediated as expected.
Scope of impact: Users leveraging Microsoft 365 Copilot Chat may notice that email messages in their Drafts or Sent Items folder may show up despite them having a sensitivity label applied and a DLP policy configured. 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: Thursday, February 19, 2026, at 9:30 AM UTC
|
|---|
|
| Time: | Wed Feb 18 05:14:27 2026 |
|---|
| Description: | Title: Users' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat
User impact: Users' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat.
More info: This issue is specific to Exchange Online email messages that are in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may process these email messages for the user that owns them even though these email messages have a sensitivity label applied and a DLP policy is configured.
Current status: We're proceeding to monitor the deployment of the fix as it progresses and are reaching out to a subset of users to test for impact remediation. We expect to have an estimated time for completion by our next scheduled update.
Scope of impact: Users leveraging Microsoft 365 Copilot Chat may notice that email messages in their Drafts or Sent Items folder may show up despite them having a sensitivity label applied and a DLP policy configured. 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 7:00 PM UTC
|
|---|
|
| Time: | Tue Feb 10 13:22:38 2026 |
|---|
| Description: | Title: Users' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat
User impact: Users' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat.
More info: This issue is specific to Exchange Online email messages that are in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may process these email messages for the user that owns them 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: Users leveraging Microsoft 365 Copilot Chat may notice that email messages in their Drafts or Sent Items folder may show up despite them having a sensitivity label applied and a DLP policy is configured. 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' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat
User impact: Users' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat.
More info: This issue is specific to Exchange Online email messages that are in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may process these email messages for the user that owns them 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 Drafts 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: Users leveraging Microsoft 365 Copilot Chat may notice that email messages in their Drafts or Sent Items folder may show up despite them having a sensitivity label applied and a DLP policy configured. 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' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat
User impact: Users' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat.
More info: This issue is specific to Exchange Online email messages that are in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may process these email messages for the user that owns them even though these email messages have a sensitivity label applied and a DLP policy is configured.
Current status: We're continuing our review email message examples and other documentation provided by some affected users to identify the root cause of impact and mitigation plan.
Scope of impact: Users leveraging Microsoft 365 Copilot Chat may notice that email messages in their Drafts or Sent Items folder may show up despite them having a sensitivity label applied and a DLP policy configured. 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' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat
User impact: Users' sent and draft folder messages with confidential labels may be incorrectly processed by Microsoft Copilot chat.
More info: This issue is specific to Exchange Online email messages that are in the Sent Items and Drafts folders. The Microsoft 365 Copilot "work tab" Chat may process these email messages for the user that owns them even though these email messages have a sensitivity label applied and a DLP policy is configured.
Current status: We've received reports of an issue with the Microsoft 365 Copilot chat improperly summarizing email messages. We're reviewing some sample email messages to identify the underlying root cause of impact and inform our next steps.
Scope of impact: Users leveraging Microsoft 365 Copilot Chat may notice that email messages in their Drafts or Sent Items folder may show up despite them having a sensitivity label applied and a DLP policy configured. This section may be updated as our investigation continues.
Next update by: Tuesday, February 3, 2026, at 9:00 AM UTC
|
|---|
|
MV1237654 - Users may be unable to send posts in Microsoft Viva Engage
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 23 14:08:00 2026 |
|---|
| End Time: | Mon Feb 23 14:46:00 2026 |
|---|
| Service: | Microsoft Viva |
|---|
| Feature Group: | Viva Engage |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 23 16:11:30 2026 |
|---|
| Root Cause: | Routine infrastructure maintenance prevented the affected infrastructure from processing requests to send posts in Viva Engage, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 23 16:11:30 2026 |
|---|
| Description: | Title: Users may be unable to send posts in Microsoft Viva Engage
User impact: Users may have been unable to send posts in Viva Engage.
Final status: We determined that routine infrastructure maintenance prevented the affected infrastructure from processing requests to send posts in Viva Engage, which resulted in impact. We disabled this maintenance and confirmed using our internal telemetry data that impact has been remediated.
Scope of impact: Any user that attempted to send a post in Viva Engage may have been impacted.
Start time: Monday, February 23, 2026, at 7:08 PM UTC
End time: Monday, February 23, 2026, at 7:46 PM UTC
Root cause: Routine infrastructure maintenance prevented the affected infrastructure from processing requests to send posts in Viva Engage, which resulted in impact.
Next steps:
- We're reviewing and improving our routine infrastructure maintenance procedures to prevent similar impact from occurring again in the future.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 23 15:15:41 2026 |
|---|
| Description: | Title: Users may be unable to send posts in Microsoft Viva Engage
User impact: Users may have been unable to send posts in Viva Engage.
Current status: We've investigated a problem in which users may have been unable to send posts in Viva Engage 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.
|
|---|
|
MO1237461 - Users may have experienced issues when trying to access services that required Multi-Factor Authentication (MFA)
| Status: | investigationSuspended |
|---|
| Start Time: | Mon Feb 23 09:00:00 2026 |
|---|
| End Time: | Mon Feb 23 11:38:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Mon Feb 23 13:24:15 2026 |
|---|
| Root Cause: | N/A |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 23 12:25:52 2026 |
|---|
| Description: | Title: Users may experience issues when trying to access services that require Multi-Factor Authentication (MFA)
User impact: Some users may experience issues accessing Microsoft 365 services, particularly during sign‑in or authentication.
More Info: Customers in North America who leverage Cisco/Duo in their MFA sign-in flow were impacted.
Final status: We've confirmed that the reported impact has been mitigated. Our investigation determined that Microsoft services were operating as expected throughout the incident. We’ve confirmed with a third‑party authentication provider (Cisco/Duo) that a fix deployed within their environment has resolved the issue, and we’re seeing successful authentication attempts.
Scope of impact: This issue may have affected any user within your organization leveraging MFA for sign-in. We've confirmed the following region(s) were impacted by this issue: North America. Additional impacted region(s) may be included as our investigation continues.
Start time: Monday, February 23, 2026, at 2:00 PM UTC
End time: Monday, February 23, 2026, at 4:38 PM UTC
Preliminary root cause: A third‑party authentication provider experienced an issue within their environment, which resulted in authentication failures when users attempted to sign in to Microsoft services that depend on that provider.
Next steps: This incident is considered resolved by a third-party without Microsoft action. We’ll continue to monitor service telemetry to ensure ongoing stability.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 23 11:30:16 2026 |
|---|
| Description: | Title: Users may experience issues when trying to access services that require Multi-Factor Authentication (MFA)
User impact: Some users may experience issues accessing Microsoft 365 services, particularly during sign‑in or authentication.
Current status: We’re reviewing Microsoft Entra sign‑in logs and related network telemetry following reports of 504 gateway timeout errors affecting sign‑in using Multi-Factor Authentication (MFA) for Microsoft 365 services. In parallel, we're also analyzing third-party authentication dependencies and interactions to better understand the potential source of the issue.
Scope of impact: This issue may affect any user within your organization leveraging MFA for sign-in. We've confirmed the following region(s) are impacted by this issue: North America. Additional impacted region(s) may be included as our investigation continues.
Next update by: Monday, February 23, 2026, at 5:30 PM UTC
|
|---|
|
| Time: | Mon Feb 23 10:57:41 2026 |
|---|
| Description: | This quick update is designed to give the latest information on this issue.
We're investigating an issue in the North America region where users may be experiencing 504 gateway timeout errors when trying to access services that require Multi-Factor Authentication (MFA). We're reviewing Microsoft Entra logs and network telemetry signals to isolate the potential source of the issue.
|
|---|
|
| Time: | Mon Feb 23 10:26:30 2026 |
|---|
| Description: | Title: Users may experience issues when trying to access services that require Multi-Factor Authentication (MFA)
User impact: Some users may experience issues accessing Microsoft 365 services, particularly during sign‑in or authentication.
Current status: We're investigating reports of impact to M365 services and we're analyzing service telemetry to identify the specific source of the issue, and any next steps to mitigate impact.
Scope of Impact: This issue may affect any user within your organization. We've confirmed the following region(s) are impacted by this issue: North America. Additional impacted region(s) may be included as our investigation continues.
Next update by: Monday, February 23, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Mon Feb 23 09:53:16 2026 |
|---|
| Description: | Title: We're looking into a potential problem impacting Microsoft 365 services
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with the Microsoft 365 service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1234028 - Some admins' Microsoft Copilot (Microsoft 365) usage report data may be delayed in Microsoft 365 admin center
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 9 03:00:00 2026 |
|---|
| End Time: | Thu Feb 19 19:45:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 20 14:48:55 2026 |
|---|
| Root Cause: | A subset of service infrastructure that provides usage data to the Microsoft 365 admin center dropped below our manageable service performance thresholds, delaying data processing tasks and resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 20 14:48:55 2026 |
|---|
| Description: | Title: Some admins' Microsoft Copilot (Microsoft 365) usage report data may be delayed in Microsoft 365 admin center
User impact: Admins in the Asia Pacific region may have seen Copilot usage report data delayed in the Microsoft 365 admin center.
More info: This delayed Copilot usage report data which was last published on February 9, 2026.
Final status: The processing optimizations we applied toward these failed tasks completed, and service has been restored.
Scope of impact: This issue may have affected any admin hosted in the Asia Pacific region attempting to view usage reports in the Microsoft 365 admin center.
Start time: Monday, February 9, 2026, at 8:00 AM UTC
End time: Friday, February 20, 2026, at 12:45 AM UTC
Root cause: A subset of service infrastructure that provides usage data to the Microsoft 365 admin center dropped below our manageable service performance thresholds, delaying data processing tasks and resulting in impact.
Next steps:
- We're reviewing the responsible subset of service infrastructure to prevent similar future occurrences.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 19 15:04:06 2026 |
|---|
| Description: | Title: Some admins' Microsoft Copilot (Microsoft 365) usage report data may be delayed in Microsoft 365 admin center
User impact: Admins in the Asia Pacific region may see Copilot usage report data delayed in the Microsoft 365 admin center.
More info: This is delaying Copilot usage report data which was last published on February 9, 2026.
Current status: Our mitigation plan continues to be delayed by a subset of service infrastructure constraints resulting in longer than anticipated deployment of the processing optimizations. We’re working on addressing the constraints to resume our plan to mitigate the impact.
Scope of impact: This issue may affect any admin hosted in the Asia Pacific region attempting to view usage reports in the Microsoft 365 admin center.
Start time: Monday, February 9, 2026, at 8:00 AM UTC
Root cause: A subset of service infrastructure that provides usage data to the Microsoft 365 admin center has dropped below our manageable service performance thresholds, delaying data processing tasks, and resulting in impact.
Next update by: Friday, February 20, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Wed Feb 18 15:11:17 2026 |
|---|
| Description: | Title: Some admins' Microsoft Copilot (Microsoft 365) usage report data may be delayed in Microsoft 365 admin center
User impact: Admins in the Asia Pacific region may see Copilot usage report data delayed in the Microsoft 365 admin center.
More info: This is delaying Copilot usage report data which was last published on February 9, 2026.
Current status: The application of our processing optimizations for the affected subset of service infrastructure is requiring more time than originally anticipated which has delayed the remediation of the impact. We're expecting an estimated timeline for the optimization applications and for impact being remediated will be available by our next scheduled communication update.
Scope of impact: This issue may affect any admin hosted in the Asia Pacific region attempting to view usage reports in the Microsoft 365 admin center.
Start time: Monday, February 9, 2026, at 8:00 AM UTC
Root cause: A subset of service infrastructure that provides usage data to the Microsoft 365 admin center has dropped below our manageable service performance thresholds, delaying data processing tasks, and resulting in impact.
Next update by: Thursday, February 19, 2026, at 9:30 PM UTC
|
|---|
|
| Time: | Tue Feb 17 13:43:13 2026 |
|---|
| Description: | Title: Asia Pacific region admins' Microsoft Copilot (Microsoft 365) usage reports may be delayed in Microsoft 365 admin center
User impact: Admins' Copilot usage reports may be delayed in the Microsoft 365 admin center.
Current status: We've identified that some data processing tasks on infrastructure responsible for providing data to the Microsoft 365 admin center concerning Copilot usage are failing, resulting in impact. We're applying processing optimizations directed toward these failed tasks to resolve impact. We expect this will take effect, remediating impact for admins, by our next scheduled communication update.
Scope of impact: This issue may affect any admin hosted in the Asia Pacific region attempting to view usage reports in the Microsoft 365 admin center.
Start time: Monday, February 9, 2026, at 8:00 AM UTC
Root cause: Some data processing tasks on infrastructure responsible for providing data to the Microsoft 365 admin center concerning Copilot usage are failing, resulting in impact.
Next update by: Wednesday, February 18, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Tue Feb 17 13:32:38 2026 |
|---|
| Description: | Title: Asia Pacific region admins' Microsoft Copilot (Microsoft 365) usage reports may be delayed in Microsoft 365 admin center
User impact: Admins' Copilot usage reports may be delayed 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.
|
|---|
|
SP1177145 - Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Oct 13 11:50:00 2025 |
|---|
| End Time: | Fri Feb 20 05:45:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 20 13:54:38 2026 |
|---|
| Root Cause: | A recent deployment contained a code regression that introduced a compatibility issue between code that was preventing items that have been deleted and recently restored from being accessible again. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 20 13:54:38 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 have been unable to access or share some items in SharePoint Online.
More info: Specifically, this issue impacted files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experienced failures in sharing and permission operations in SharePoint Online.
Additionally, processes that attempted to enumerate permissions on these items may have seen failures.
Site administrators still had complete access to the content that was been deleted and restored.
Final status: We've monitored service health telemetry to confirm that our fix has remediated the impact.
Scope of impact: Some users with edit and full control permissions who were attempting to access or share some items in SharePoint Online that were deleted and recently restored from the recycle bin may have been impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
End time: Friday, February 20, 2026, at 10:45 AM UTC
Root cause: A recent deployment contained a code regression that introduced a compatibility issue between code that was preventing items that have been deleted and recently restored from being accessible again.
Next steps:
- We're reviewing our update procedures to understand why impact to file access wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 18 13:23:37 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 deployment of our fix that entails an automated repair process and are monitoring our service health telemetry to ensure that the repair process remediates the impact for all affected 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: Friday, February 20, 2026, at 8:00 PM UTC
|
|---|
|
| 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: | serviceRestored |
|---|
| Start Time: | Mon Oct 13 11:50:00 2025 |
|---|
| End Time: | Fri Feb 20 05:45:00 2026 |
|---|
| Service: | Microsoft OneDrive |
|---|
| Feature Group: | OneDrive for Business |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Fri Feb 20 13:54:11 2026 |
|---|
| Root Cause: | A recent deployment contained a code regression that introduced a compatibility issue between code that was preventing items that had been deleted and recently restored from being accessible again. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 20 13:54: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 have been unable to access or share some files in OneDrive.
More info: Specifically, this issue impacted files, folders, and list items that were deleted and recently restored from the recycle bin. Impacted users attempting to access or share some folders experienced failures in sharing and permission operations in OneDrive.
Additionally, processes that attempted to enumerate permissions on these items may have seen failures.
Site administrators still had complete access to the content that was been deleted and restored.
Final status: We've monitored service health telemetry to confirm that our fix has remediated the impact.
Scope of impact: Some users with edit and full control permissions who were attempting to access or share some folders in OneDrive that were deleted and restored from the recycle bin may have been impacted.
Start time: Monday, October 13, 2025, at 3:50 PM UTC
End time: Friday, February 20, 2026, at 10:45 AM UTC
Root cause: A recent deployment contained a code regression that introduced a compatibility issue between code that was preventing items that had been deleted and recently restored from being accessible again.
Next steps:
- We're reviewing our update procedures to understand why impact to file access wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 18 13:22:53 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 deployment of our fix that entails an automated repair process and are monitoring our service health telemetry to ensure that the repair process remediates the impact for all affected 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: Friday, February 20, 2026, at 8:00 PM UTC
|
|---|
|
| 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.
|
|---|
|
MO1231810 - Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
| Status: | postIncidentReviewPublished |
|---|
| 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 20 10:44:26 2026 |
|---|
| Root Cause: | A driver issue on a subset of Graphics Processing Units (GPUs) affected a portion of the infrastructure supporting Microsoft 365 Copilot in Europe. This caused some processing capacity to become temporarily unavailable, which led to a reduction in available capacity within the environment and limited the service’s ability to handle requests at normal levels. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 20 10:44:26 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Feb 17 16:48:02 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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: A driver issue on a subset of Graphics Processing Units (GPUs) affected a portion of the infrastructure supporting Microsoft 365 Copilot in Europe. This caused some processing capacity to become temporarily unavailable, which led to a reduction in available capacity within the environment and limited the service’s ability to handle requests at normal levels.
To reduce user impact while recovery actions were underway, traffic management measures were applied to control request volumes and protect overall service stability. During this process, the traffic controls were briefly applied more aggressively than intended, which resulted in some users outside the Europe region also experiencing impact for a short period (approximately 25 minutes).
As a result of the reduced capacity and the temporary traffic management actions, some users experienced failures or timeouts when accessing Microsoft 365 Copilot until the affected components were restored.
Next Steps
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
|
|---|
|
| 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
|
|---|
|
CP1231765 - Some users may experience failures or timeouts while accessing Microsoft Copilot (Microsoft 365)
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Thu Feb 12 14:17:00 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 20 10:43:09 2026 |
|---|
| Root Cause: | A driver issue on a subset of Graphics Processing Units (GPUs) affected a portion of the infrastructure supporting Microsoft 365 Copilot in Europe. This caused some processing capacity to become temporarily unavailable, which led to a reduction in available capacity within the environment and limited the service’s ability to handle requests at normal levels. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Fri Feb 20 10:43:09 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Feb 17 16:47:41 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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
Root cause: A driver issue on a subset of Graphics Processing Units (GPUs) affected a portion of the infrastructure supporting Microsoft 365 Copilot in Europe. This caused some processing capacity to become temporarily unavailable, which led to a reduction in available capacity within the environment and limited the service’s ability to handle requests at normal levels.
To reduce user impact while recovery actions were underway, traffic management measures were applied to control request volumes and protect overall service stability. During this process, the traffic controls were briefly applied more aggressively than intended, which resulted in some users outside the Europe region also experiencing impact for a short period (approximately 25 minutes).
As a result of the reduced capacity and the temporary traffic management actions, some users experienced failures or timeouts when accessing Microsoft 365 Copilot until the affected components were restored.
Next Steps
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
|
|---|
|
| 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
|
|---|
|
EX1227432 - Some users' legitimate email messages may be marked as phishing and quarantined in Exchange Online
| Status: | postIncidentReviewPublished |
|---|
| 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 19 19:33:57 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 19 19:33:57 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Feb 19 08:20:12 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Feb 17 16:02:56 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Tue Feb 17 15:59:45 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Feb 16 19:52:15 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Mon Feb 16 19:52:01 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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
|
|---|
|
AH1234649 - Users may be unable to create Autopatch groups in Windows Autopatch
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 16 19:00:00 2026 |
|---|
| End Time: | Wed Feb 18 23:20:00 2026 |
|---|
| Service: | Windows Autopatch |
|---|
| Feature Group: | Update Management |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Wed Feb 18 23:52:00 2026 |
|---|
| Root Cause: | A recent feature component deprecation process impacted the request flow leveraged for Autopatch group creation, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 18 23:52:00 2026 |
|---|
| Description: | Title: Users may be unable to create Autopatch groups in Windows Autopatch
User impact: Users may have been unable to create Autopatch groups in Windows Autopatch and encountered an error.
More info: Impacted users received an error stating "The Autopatch group failed to proceed your previous Create action. Click the resubmit button to try again." However, subsequent attempts didn't succeed.
Final status: The code fix completed, and after a period of testing and monitoring, we confirmed impact was remediated.
Scope of impact: Users attempting to create Autopatch groups in Windows Autopatch may have been impacted.
Start time: Tuesday, February 17, 2026, at 12:00 AM UTC
End time: Thursday, February 19, 2026, at 4:20 AM UTC
Root cause: A recent feature component deprecation process impacted the request flow leveraged for Autopatch group creation, which resulted in impact.
Next steps:
- To help prevent similar impact in the future, we're further reviewing our feature component deprecation process to identify issues before being initiated.
This is the final update for the event.
|
|---|
|
| Time: | Wed Feb 18 19:26:04 2026 |
|---|
| Description: | Title: Users may be unable to create Autopatch groups in Windows Autopatch
User impact: Users may be unable to create Autopatch groups in Windows Autopatch and encounter an error.
More info: Impacted users receive an error stating "The Autopatch group failed to proceed your previous Create action. Click the resubmit button to try again." However, subsequent attempts won't succeed.
Current status: We've identified that a recent feature component deprecation process impacted the request flow leveraged for Autopatch group creation, resulting in impact. We're preparing a code fix to resolve the issue and anticipate the impact should be fully remediated by our next scheduled update.
Scope of impact: Users attempting to create Autopatch groups in Windows Autopatch may be impacted.
Start time: Tuesday, February 17, 2026, at 12:00 AM UTC
Root cause: A recent feature component deprecation process impacted the request flow leveraged for Autopatch group creation, resulting in impact.
Next update by: Thursday, February 19, 2026, at 6:00 AM UTC
|
|---|
|
CP1230749 - Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) weren't responding to prompts
| Status: | postIncidentReviewPublished |
|---|
| Start Time: | Mon Feb 9 02:00:00 2026 |
|---|
| End Time: | Wed Feb 11 23:00:00 2026 |
|---|
| Service: | Microsoft Copilot (Microsoft 365) |
|---|
| Feature Group: | Microsoft Copilot (Microsoft 365) |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Feb 18 19:34:33 2026 |
|---|
| Root Cause: | A standard service configuration update unintentionally activated a background data pre-loading feature for Declarative Agents at a significantly broader scope than intended. This feature, designed to proactively retrieve supplementary information to improve agent response quality, was enabled across a much larger population of tenants than planned. The number of active organizations using the affected service path increased from double digits to over four digits, resulting in approximately five times the normal request volume against the backend language model infrastructure. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 18 19:34:33 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| Time: | Thu Feb 12 11:06:48 2026 |
|---|
| Description: | Title: Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) weren't responding to prompts
User impact: Users’ Declarative Agents in Copilot weren't responding to prompts.
Final status: We've determined that a recent standard service update unintentionally enabled new functionality more broadly than intended, which resulted in higher‑than‑expected service traffic that caused elevated latency and degraded performance for some users. To mitigate impact, we've reverted the aforementioned change and applied service controls to reduce request volume and stabilize performance. We’ve confirmed with your representatives that the issue is no longer occurring, and service performance has returned to expected levels following extended monitoring.
Scope of impact: Your organization was affected by this event, and some users of Declarative Agents were impacted. This information may have been updated as our investigation continues.
Start time: Monday, February 9, 2026, at 7:00 AM UTC
End time: Thursday, February 12, 2026, at 4:00 AM UTC
Root cause: A standard service configuration update unintentionally activated a background data pre-loading feature for Declarative Agents at a significantly broader scope than intended. This feature, designed to proactively retrieve supplementary information to improve agent response quality, was enabled across a much larger population of tenants than planned. The number of active organizations using the affected service path increased from double digits to over four digits, resulting in approximately five times the normal request volume against the backend language model infrastructure.
The rapid increase in traffic exceeded the preconfigured capacity and throttling thresholds for the affected model deployment. As the infrastructure became saturated, it began returning throttling responses to incoming requests. Client retry logic then amplified the traffic further, creating a feedback loop of escalating load, increased latency, and additional retries. The 95th percentile response latency for affected requests rose from a baseline of approximately 15 seconds to over 250 seconds, causing many requests to time out entirely.
Additionally, because the configuration was distributed through a client-side mechanism, disabling the feature required waiting for client-side caches to expire before the change took effect. This extended the time required to achieve full mitigation after the root cause was identified and the configuration was reverted.
Next steps:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|---|
|
| Time: | Thu Feb 12 04:29:32 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 continuing to monitor telemetry during peak network traffic hours to ensure impact 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.
Next update by: Thursday, February 12, 2026, at 4:30 PM UTC
|
|---|
|
| Time: | Wed Feb 11 21:34:07 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: As impact continued following the service optimizations and load rebalancing across the affected infrastructure, we further reviewed the unexpected increase in traffic causing some requests to fail and suspect the underlying issue is related to an offending service change. We’ve reverted the change and are monitoring telemetry during peak network traffic hours to ensure impact 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.
Next update by: Thursday, February 12, 2026, at 11:00 AM UTC
|
|---|
|
| Time: | Wed Feb 11 15:26: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: While our optimization actions have improved throughput, we're still seeing a small number of errors and we're continuing to monitor. If you're still affected by this issue, please refresh your session and try again.
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.
Next update by: Thursday, February 12, 2026, at 5:00 AM UTC
|
|---|
|
| Time: | Wed Feb 11 13:19:45 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: Our analysis of service telemetry indicates an unexpected increase in traffic, causing some requests to fail and resulting in impact. We've performed service optimizations and rebalanced load to remediate this issue. Our telemetry is showing improvement and we're continuing to monitor to verify this resolves the 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.
Next update by: Wednesday, February 11, 2026, at 8:30 PM UTC
|
|---|
|
| Time: | Wed Feb 11 12:06:45 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 analyzing service telemetry to better understand the underlying cause of impact and determine our 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.
Next update by: Wednesday, February 11, 2026, at 6:30 PM UTC
|
|---|
|
| Time: | Wed Feb 11 11:42:22 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.
More info: This is a continuation of the event previously communicated via CP1229864.
Current status: We're investigating a potential issue with Microsoft Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|---|
|
CP1229864 - Some users’ Declarative Agents in Microsoft Copilot (Microsoft 365) aren't responding to prompts
| Status: | postIncidentReviewPublished |
|---|
| 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: | Wed Feb 18 19:33:41 2026 |
|---|
| Root Cause: | A standard service configuration update unintentionally activated a background data pre-loading feature for Declarative Agents at a significantly broader scope than intended. This feature, designed to proactively retrieve supplementary information to improve agent response quality, was enabled across a much larger population of tenants than planned. The number of active organizations using the affected service path increased from double digits to over four digits, resulting in approximately five times the normal request volume against the backend language model infrastructure. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 18 19:33:01 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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 standard service configuration update unintentionally activated a background data pre-loading feature for Declarative Agents at a significantly broader scope than intended. This feature, designed to proactively retrieve supplementary information to improve agent response quality, was enabled across a much larger population of tenants than planned. The number of active organizations using the affected service path increased from double digits to over four digits, resulting in approximately five times the normal request volume against the backend language model infrastructure.
The rapid increase in traffic exceeded the preconfigured capacity and throttling thresholds for the affected model deployment. As the infrastructure became saturated, it began returning throttling responses to incoming requests. Client retry logic then amplified the traffic further, creating a feedback loop of escalating load, increased latency, and additional retries. The 95th percentile response latency for affected requests rose from a baseline of approximately 15 seconds to over 250 seconds, causing many requests to time out entirely.
Additionally, because the configuration was distributed through a client-side mechanism, disabling the feature required waiting for client-side caches to expire before the change took effect. This extended the time required to achieve full mitigation after the root cause was identified and the configuration was reverted.
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.
|
|---|
|
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: | Wed Feb 18 19:33:03 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: | Wed Feb 18 19:33:03 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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.
|
|---|
|
TM1231009 - Users may have been unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat
| Status: | serviceRestored |
|---|
| Start Time: | Fri Feb 6 07:00:00 2026 |
|---|
| End Time: | Tue Feb 17 19:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Wed Feb 18 08:42:57 2026 |
|---|
| Root Cause: | A recent update to the services that handle Teams meeting titles contained an error that was improperly handling the URLs, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Wed Feb 18 06:02:23 2026 |
|---|
| Description: | Title: Users may have been unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat
User impact: Users may have been unable to join some Microsoft Teams meetings through the "Join" button in the meeting chat.
More info: While we were focused on remediation, users could've been able to join meetings through meeting URLs.
Final status: We've validated that the fix has successfully relieved impact for users.
Scope of impact: This issue may have potentially impacted any user attempting to join affected meetings through the "Join" button in the meeting chat.
Start time: Friday, February 6, 2026, at 12:00 PM UTC
End time: Wednesday, February 18, 2026, at 12:00 AM UTC
Root cause: A recent update to the services that handle Teams meeting titles contained an error that was improperly handling the URLs, resulting in impact.
Next steps:
- We're reviewing our deployment and testing procedures to help prevent similar impact from happening again.
This is the final update for the event.
|
|---|
|
| Time: | Tue Feb 17 16:50:05 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've confirmed that our fix has completed deployment to all affected environments. We're in the process of validating that this fix has successfully relieved impact for users.
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: Wednesday, February 18, 2026, at 11:00 AM UTC
|
|---|
|
| 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.
|
|---|
|
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 08:56:00 2026 |
|---|
| End Time: | Tue Feb 10 11:25:00 2026 |
|---|
| Service: | Microsoft 365 suite |
|---|
| Feature Group: | Portal |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Feb 17 17:59:14 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: | Tue Feb 17 17:59:14 2026 |
|---|
| Description: | A post-incident report has been published.
|
|---|
|
| 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 1:56 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:
- For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|---|
|
| Time: | Tue 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
|
|---|
|
TM1218513 - Users may be unable to update or add Copilot Studio agents to Microsoft Teams and Microsoft Copilot (Microsoft 365)
| Status: | serviceRestored |
|---|
| Start Time: | Wed Nov 12 12:37:00 2025 |
|---|
| End Time: | Fri Feb 13 19:00:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 17 17:25:33 2026 |
|---|
| Root Cause: | A recent Copilot Studio update introduced a permissions issue that prevented adding or changing Copilot Studio agents in Microsoft Teams and Copilot, resulting in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 17 16:03:29 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 have been unable to update or add Copilot Studio agents to Microsoft Teams and Copilot.
More info: Impacted users received a "permissions needed" error when trying to update or add Copilot Studio agents from Copilot Studio to Teams and Copilot.
For the adding to Teams impact specifically, this affected organizations where sideloading and the interaction of custom Microsoft Teams apps were disabled. This issue had been corrected in the following Teams build versions and updating to them resolved the issue for users:
North America and Latin America regions - build 20260112.8
Europe, Middle East, Africa, and Asia Pacific regions - build 20260120.9
Final status: Following the deployment of our fix, out internal service telemetry has validated that the offending permissions issue has been addressed, and that impact has been remediated.
Scope of impact: Users may have been unable to add or update Copilot Studio agents through Copilot Studio for Microsoft Teams and Copilot.
Start time: Thursday, November 12, 2025, at 5:37 PM UTC
End time: Saturday, February 14, 2026, at 12:00 AM UTC
Root cause: A recent Copilot Studio update introduced a permissions issue that prevented adding or changing Copilot Studio agents in Microsoft Teams and Copilot, resulting in impact.
Next steps:
- We're further analyzing the introduced permissions issue to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
|
|---|
|
| Time: | Mon Feb 16 14:28:07 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: We're monitoring the deployment of our fix to alleviate the remaining impact with Copilot interactions to ensure that it restores service as expected. We’ll provide a timeline for full remediation of this remaining impact 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: Tuesday, February 17, 2026, at 10:30 PM UTC
|
|---|
|
| 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.
|
|---|
|
EX1228240 - Users' MailTips may not reflect free/busy correctly in Outlook desktop and crashes may occur when adding mailboxes
| Status: | serviceRestored |
|---|
| Start Time: | Tue Jan 27 13:00:00 2026 |
|---|
| End Time: | Thu Feb 12 13:00:00 2026 |
|---|
| Service: | Exchange Online |
|---|
| Feature Group: | Management and Provisioning |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Tue Feb 17 16:08:02 2026 |
|---|
| Root Cause: | A routing change for Autodiscover requests introduced a header duplication issue which caused a backlog of requests that ultimately failed or timed out and resulted in the impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 17 16:06:18 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 have reflected free/busy correctly in Outlook desktop and crashes may have occurred.
More info: This issue was specific to the Outlook desktop client in organizations with a hybrid environment that used Exchange Web Services (EWS) for MailTips. Users may have noticed that the MailTips free/busy feature wasn’t operating as expected and may have seen an error stating “we can’t show MailTips right now.”
The Outlook desktop crashes occurred when users attempted to add a new on-premises mailbox.
Admins may have been unable to create new on-premises mailboxes, and their cross-tenant AutoDiscover requests general may have failed from hybrid environments.
While we worked on deploying the fix, admins may have been able to mitigate the impact by restarting the Autodiscover app pool.
Final status: We've validated with a subset of affected users that the fix to prevent the header duplication issue has fully resolved the impact.
Scope of impact: Any admins’ cross-tenant AutoDiscover requests may have failed from hybrid environments, which caused MailTips free/busy not to show and crash for users’ Outlook desktop clients when they added additional on-premises mailboxes.
Start time: Tuesday, January 27, 2026, at 12:30 AM UTC
End time: Thursday, February 12, 2026, at 6:00 PM UTC
Root cause: A routing change for Autodiscover requests introduced a header duplication issue which caused a backlog of requests that ultimately failed or timed out and resulted in the impact.
Next steps:
- We're reviewing our change implementation standards to ensure similar issues are caught and addressed ahead of deployment to prevent this from happening again.
This is the final update for the event.
|
|---|
|
| 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.
|
|---|
|
TM1233974 - Some users may have experienced delays and failures in Microsoft Teams
| Status: | serviceRestored |
|---|
| Start Time: | Tue Feb 17 08:30:00 2026 |
|---|
| End Time: | Tue Feb 17 09:25:00 2026 |
|---|
| Service: | Microsoft Teams |
|---|
| Feature Group: | Teams Components |
|---|
| Classification: | incident |
|---|
| Last Updated: | Tue Feb 17 10:19:46 2026 |
|---|
| Root Cause: | A subsection of service infrastructure, that facilitates underlying caching in Microsoft Teams, fell below our manageable service performance thresholds. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Tue Feb 17 10:19:46 2026 |
|---|
| Description: | Title: Some users may have experienced delays and failures in Microsoft Teams
User impact: Users may have experienced delays and failures in Microsoft Teams.
More info: Users may have experienced delays and failures when sending and receiving chat messages that included inline media (images, code snippets, videos).
Final status: We identified that a subsection of service infrastructure, that facilitates underlying caching in Microsoft Teams, fell below our manageable service performance thresholds and resulted in impact. We reverted the configuration change to the last healthy version, and can confirm that impact is remediated after a period of monitoring service telemetry.
Scope of impact: Impact was specific to some users located in Europe and United States who are served through the affected infrastructure attempting to send and receive chat messages that included inline media (images, code snippets, videos).
Start time: Tuesday, February 17, 2026, at 1:30 PM UTC
End time: Tuesday, February 17, 2026, at 2:25 PM UTC
Root cause: A subsection of service infrastructure, that facilitates underlying caching in Microsoft Teams, fell below our manageable service performance thresholds.
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: | Tue Feb 17 09:29:35 2026 |
|---|
| Description: | Title: Some users may experience delays and failures in Microsoft Teams
User impact: Users may experience delays and failures in Microsoft Teams.
More info: Users may experience delays and failures when sending and receiving chat messages that include inline media (images, code snippets, videos).
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 located in Europe and United States who are served through the affected infrastructure attempting to send and receive chat messages that include inline media (images, code snippets, videos).
Next update by: Tuesday, February 17, 2026, at 4:30 PM UTC
|
|---|
|
SP1233278 - Some admins and users were unable to register or edit pages in SharePoint Online
| Status: | serviceRestored |
|---|
| Start Time: | Mon Feb 9 23:07:00 2026 |
|---|
| End Time: | Mon Feb 16 06:07:00 2026 |
|---|
| Service: | SharePoint Online |
|---|
| Feature Group: | SharePoint Features |
|---|
| Classification: | advisory |
|---|
| Last Updated: | Mon Feb 16 06:32:55 2026 |
|---|
| Root Cause: | A recent standard service update inadvertently introduced the issue, which resulted in impact. |
|---|
| Next Update: | N/A |
|---|
|
Details
| Time: | Mon Feb 16 06:25:38 2026 |
|---|
| Description: | Title: Some admins and users were unable to register or edit pages in SharePoint Online
User impact: Admins and users were unable to register or edit pages in SharePoint Online.
Final status: We’ve determined that a recent standard service update inadvertently introduced the issue, resulting in impact. We've reverted this change to resolve impact.
Scope of impact: Impact was specific to some admins and users who were served through the affected infrastructure attempting to register or edit pages in SharePoint Online.
Start time: Tuesday, February 10, 2026, at 4:07 AM UTC
End time: Monday, February 16, 2026, at 11:07 AM UTC
Root cause: A recent standard service update inadvertently introduced the issue, which resulted in impact.
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: | Mon Feb 16 04:09:51 2026 |
|---|
| Description: | Title: Some admins and users may be unable to register or edit pages in SharePoint Online
User impact: Admins and users may be unable to register or edit pages in SharePoint Online.
More info: As a temporary workaround, some admins and users may be able to edit pages by navigating to the Site Pages library settings and enabling the option “Require documents to be checked out before they can be edited” under Versioning settings.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some admins and users who are served through the affected infrastructure attempting to register or edit pages in SharePoint Online. This information may be updated as our investigation continues.
Next update by: Monday, February 16, 2026, at 11:30 AM 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
|
|---|
|
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.
|
|---|
|
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
|
|---|
|
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.
|
|---|
|
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.
|
|---|
|
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
|
|---|
|
|
