Penn Computing
Computing Menu Computing A-Z
Computing Home Information Systems & Computing Penn

Microsoft's Incident Report for PennO365

Following is a data extract from the PennO365 administrative console of incident reports sent by Microsoft within the last 30 days. We pull out incidents that are relevant to the current PennO365 service offerings and we refresh this data every 15 minutes. Note that incidents related to PennO365 administrative functions are not shown in this list. Additionally you can check Microsoft's status page for current service status messages. The last extract was taken on Sun Feb 1 06:45:05 2026.

WP1218937 - Users may experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions

Status:investigationSuspended
Start Time:Sat Jan 17 17:37:26 2026
End Time:Sat Jan 31 18:03:14 2026
Service:Windows 365
Feature Group:End User
Classification:advisory
Last Updated:Sat Jan 31 18:03:27 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Sat Jan 31 18:03:27 2026
Description:Title: Users may experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions
User impact: If action is not taken, users may continue to experience intermittent issues signing-in to Cloud PC sessions.
Final status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
Time:Sat Jan 17 17:41:57 2026
Description:Title: Users may experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions
User impact: If action is not taken, users may continue to experience intermittent issues signing-in to Cloud PC sessions.
Current status: Due to the code misconfiguration introduced with the Windows security update (KB5074109), users may be experiencing intermittent sign-in or connection failures for Windows 365 Cloud PC sessions. While we recommended users follow the Known Issue Rollback (KIR) instructions to resolve the issue, a recently released out-of-band (OOB) update has deployed which is now the recommended action for resolving the issue. If action isn't taken to install the OOB update, users may continue to experience intermittent issues signing-in to Cloud PC sessions.
This communication will expire in 14 days and is scheduled to remain active for the full duration.

MO1224866 - Some users may have been unable to export usage reports from the Microsoft 365 admin center

Status:serviceRestored
Start Time:Thu Jan 29 08:07:00 2026
End Time:Fri Jan 30 19:30:00 2026
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Sat Jan 31 04:20:56 2026
Root Cause:A recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may have prevented users from exporting usage reports.
Next Update:N/A

Details

Time:Sat Jan 31 04:19:13 2026
Description:Title: Some users may have been unable to export usage reports from the Microsoft 365 admin center
User impact: Users may have been unable to export usage reports from the Microsoft 365 admin center.
More info: Users may have also encountered errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Final status: We’ve confirmed following the feedback from some affected users that impact has been remediated.
Scope of impact: Some users attempting to export usage reports in the Microsoft 365 admin center may have been impacted.
Start time: Thursday, January 29, 2026, at 1:07 PM UTC
End time: Saturday, January 31, 2026, at 12:30 AM UTC
Root cause: A recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may have prevented users from exporting usage reports.
Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Fri Jan 30 19:35:25 2026
Description:Title: Some users may be unable to export usage reports from the Microsoft 365 admin center
User impact: Users may be unable to export usage reports from the Microsoft 365 admin center.
More info: Users may also encounter errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Current status: We’ve initiated the process of deploying the code fix and we’re validating with affected users that have received the fix to ensure its operating as expected to resolve this issue.
Scope of impact: Some users attempting to export usage reports in the Microsoft 365 admin center may be impacted.
Start time: Thursday, January 29, 2026, at 11:00 PM UTC
Root cause: A recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may prevent users from exporting usage reports.
Next update by: Saturday, January 31, 2026, at 10:00 AM UTC
Time:Fri Jan 30 14:29:03 2026
Description:Title: Some users may be unable to export usage reports from the Microsoft 365 admin center
User impact: Users may be unable to export usage reports from the Microsoft 365 admin center.
More info: Users may also encounter errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Current status: We've identified that a recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may prevent users from exporting usage reports. We've created and are validating a code fix that will deploy shortly and remediate impact by our next scheduled update.
Scope of impact: Some users attempting to export usage reports in the Microsoft 365 admin center may be impacted.
Start time: Thursday, January 29, 2026, at 11:00 PM UTC
Root cause: A recent code change meant to add new reporting features to the Microsoft 365 admin center mistakenly introduced a code defect that may prevent users from exporting usage reports.
Next update by: Saturday, January 31, 2026, at 2:30 AM UTC
Time:Fri Jan 30 05:56:49 2026
Description:Title: Some users are unable to export usage reports from the Microsoft 365 admin center
User impact: Users are unable to export usage reports from the Microsoft 365 admin center.
More info: Users may also encounter errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Current status: We're reviewing a potential code change and available logs to help determine the root cause and mitigation plan.
Scope of impact: Some users in the North US region attempting to export usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Friday, January 30, 2026, at 9:00 PM UTC
Time:Fri Jan 30 03:49:42 2026
Description:Title: Some users are unable to export usage reports from the Microsoft 365 admin center
User impact: Users are unable to export usage reports from the Microsoft 365 admin center.
More info: Users may also encounter errors or empty data when attempting to generate reports from the Microsoft 365 admin center.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users in the North US region attempting to export usage reports in the Microsoft 365 admin center may be impacted.
Next update by: Friday, January 30, 2026, at 11:00 AM UTC

PB1225246 - Users may see issues with their templated subscription email in Power BI

Status:serviceDegradation
Start Time:Thu Jan 29 04:21:00 2026
End Time:N/A
Service:Power BI
Feature Group:PowerBI.com
Classification:advisory
Last Updated:Fri Jan 30 21:05:38 2026
Root Cause:A recent change altering the subscription email template for Power BI affected users' existing subscription email templates.
Next Update:Tuesday, February 3, 2026, at 2:00 AM UTC

Details

Time:Fri Jan 30 20:38:40 2026
Description:Title: Users may see issues with their templated subscription email in Power BI
User impact: Users may see issues with their templated subscription email in Power BI.
More info: Specifically, users may observe that the subscription email template has been altered due to a change rolled out altering the template format.
Customers may see additional revisions to this template in the future and it is recommended to update processes to be resilient to these changes. We apologize for the disruption this change has caused. Future updates to this template will be communicated with notice so users can update their processes appropriately.
Current status: We've determined that a recent change altering the subscription email template for Power BI affected users' existing subscription email templates. We're moving to roll back the template to the previous default and anticipate we'll have an estimated timeline for full remediation by our next scheduled update.
Scope of impact: Users leveraging templated subscription emails in Power BI may be impacted.
Start time: Thursday, January 29, 2026, at 9:21 AM UTC
Root cause: A recent change altering the subscription email template for Power BI affected users' existing subscription email templates.
Next update by: Tuesday, February 3, 2026, at 2:00 AM UTC

TM1218513 - Some users may be unable to update or add Copilot Studio agents in Microsoft Teams and receive an error

Status:serviceDegradation
Start Time:Fri Jan 16 01:37:01 2026
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Jan 30 20:06:29 2026
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:Monday, February 2, 2026, at 9:30 AM UTC

Details

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.

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:Fri Jan 30 18:22:50 2026
Root Cause:An influx of automated email traffic from Power BI subscriptions resulted in impact to external subscription email delivery.
Next Update:Tuesday, February 3, 2026, at 12:30 AM UTC

Details

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

TM1224481 - Some users may see stale profile pictures or profile information for other users within Microsoft Teams

Status:serviceDegradation
Start Time:Tue Jan 27 04:00:00 2026
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Jan 30 18:21:50 2026
Root Cause:A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing impact.
Next Update:Monday, February 2, 2026, at 8:00 PM UTC

Details

Time:Fri Jan 30 18:21:50 2026
Description:Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: Reverting the offending service update is taking longer than expected, but its been reverted in 94 percent of the affected environment. We anticipate this process will complete by our next scheduled communications update.
Scope of impact: Some users viewing the profile pictures or profile information for other users within Microsoft Teams may be impacted.
Start time: Tuesday, January 27, 2026, at 9:00 AM UTC
Root cause: A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing impact.
Next update by: Monday, February 2, 2026, at 8:00 PM UTC
Time:Thu Jan 29 17:59:05 2026
Description:Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: We've initiated the reversion of the offending service update, and we anticipate this process will complete by our next scheduled communications update.
Scope of impact: Some users viewing the profile pictures or profile information for other users within Microsoft Teams may be impacted.
Start time: Tuesday, January 27, 2026, at 9:00 AM UTC
Root cause: A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing impact.
Next update by: Saturday, January 31, 2026, at 1:00 AM UTC
Time:Thu Jan 29 15:35:46 2026
Description:Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: We're continuing to prepare the reversion of the offending update, which we anticipate will begin by our next scheduled communication update.
Scope of impact: Some users viewing the profile pictures or profile information for other users within Microsoft Teams may be impacted.
Start time: Tuesday, January 27, 2026, at 9:00 AM UTC
Root cause: A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing impact.
Next update by: Friday, January 30, 2026, at 12:30 AM UTC
Time:Thu Jan 29 14:42:57 2026
Description:Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: We've identified that a code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing the impact. We're preparing to revert the offending update to remediate the issue, and we'll aim to provide a timeline for the reversion to complete by our next scheduled communications update.
Scope of impact: Some users viewing the profile pictures or profile information for other users within Microsoft Teams may be impacted.
Start time: Tuesday, January 27, 2026, at 9:00 AM UTC
Root cause: A code regression contained in a recent update to a portion of the Microsoft Teams service infrastructure is causing impact.
Next update by: Thursday, January 29, 2026, at 9:00 PM UTC
Time:Thu Jan 29 14:23:39 2026
Description:Title: Some users may see stale profile pictures or profile information for other users within Microsoft Teams
User impact: Users may see stale profile pictures or profile information for other users within Microsoft Teams.
More info: This issue strictly affects some users attempting to view the profile picture or information of other users who modified either field after Tuesday, January 27, 2026, at 9:00 AM UTC.
Current status: We're investigating a potential issue with some users seeing stale profile pictures or profile information for other users within Microsoft Teams, and we're checking for impact to your organization. We'll provide an update within 30 minutes.

TM1222851 - Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams

Status:serviceRestored
Start Time:Wed Jan 14 22:40:00 2026
End Time:Fri Jan 30 13:38:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Jan 30 17:41:06 2026
Root Cause:A recent service library update introduced a code regression that was resulting in users intermittently seeing a red border after screensharing was stopped in Microsoft Teams.
Next Update:N/A

Details

Time:Fri Jan 30 17:37:49 2026
Description:Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may have intermittently seen a red border after screensharing was stopped in Microsoft Teams
More info: This specifically affected users of the Microsoft Teams version 26005.204.4249.1621.
Final status: We've completed the deployment of our code solution and confirmed through monitoring service health telemetry that the impact is remediated for users who update to the latest version of Microsoft Teams.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilized screensharing functionality in Microsoft Teams may have been intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
End time: Friday, January 30, 2026, at 6:38 PM UTC
Root cause: A recent service library update introduced a code regression that was resulting in users intermittently seeing a red border after screensharing was stopped in Microsoft Teams.
Next steps: - We're reviewing our update procedures to understand why impact to screensharing functionality wasn't caught during the testing phase. This will allow us to drive service improvements by proactively identifying similar issues in the future and improve our update testing processes.
This is the final update for the event.
Time:Fri Jan 30 11:25:48 2026
Description:Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We're monitoring our code solution deployment as it nears saturation and we estimate that this process will be complete by our next scheduled update. As this saturation finalizes, users may incrementally be remediated from impact.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Saturday, January 31, 2026, at 12:00 AM UTC
Time:Wed Jan 28 20:27:39 2026
Description:Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We’ve initiated a safe process to expedite our code solution, and we expect our solution to complete deployment by our next scheduled update.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Friday, January 30, 2026, at 6:00 PM UTC
Time:Wed Jan 28 18:54:09 2026
Description:Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We’re continuing to deploy our code solution to the affected environment and are working on assessing alternative methods to safely expedite this deployment process to remediate impact as swiftly as possible. We'll provide a timeline for our solution to complete deployment as one becomes available.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Thursday, January 29, 2026, at 2:00 AM UTC
Time:Tue Jan 27 18:04:30 2026
Description:Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We've finished the validations for our fix which we've begun deploying to the affected environment. We'll aim to provide a timeline for the deployment to complete by our next scheduled communications update.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Thursday, January 29, 2026, at 12:00 AM UTC
Time:Tue Jan 27 14:47:32 2026
Description:Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We've developed our fix to repair the regression and are doing final validations before deploying the solution to the affected environments. Once available, we'll provide a resolution timeline.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Wednesday, January 28, 2026, at 12:30 AM UTC
Time:Tue Jan 27 11:38:22 2026
Description:Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users of the Microsoft Teams version 26005.204.4249.1621.
Current status: We're continuing to develop our fix to repair the regression, which we anticipate will be ready for deployment by our next scheduled communication update.
Scope of impact: Any user with the Microsoft Teams version 26005.204.4249.1621 who utilizes screensharing functionality in Microsoft Teams may be intermittently impacted.
Start time: Thursday, January 15, 2026, at 3:40 AM UTC
Root cause: A recent service library update introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Tuesday, January 27, 2026, at 8:30 PM UTC
Time:Tue Jan 27 10:43:23 2026
Description:Title: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams
User impact: Users may intermittently see a red border after screensharing has been stopped in Microsoft Teams.
More info: This specifically affects users utilizing the Windows desktop version 26005.204.4249.1621
Current status: We've identified that a recent service library update has introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams. We're developing a fix to repair the regression and anticipate this process to be complete by our next scheduled update time.
Scope of impact: Impact is specific to any user with the Windows desktop version 26005.204.4249.1621 who are served through the affected infrastructure.
Root cause: A recent service library update has introduced a code regression that's resulting in users intermittently seeing a red border after screensharing has been stopped in Microsoft Teams.
Next update by: Tuesday, January 27, 2026, at 6:00 PM UTC

TM1223735 - Microsoft Teams meeting participants may not be granted permissions to meeting notes added after meeting creation

Status:serviceDegradation
Start Time:Wed Jan 28 14:51:58 2026
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Jan 30 16:17:45 2026
Root Cause:A latent code misconfiguration is causing the impact.
Next Update:Monday, February 2, 2026, at 10:00 PM UTC

Details

Time:Fri Jan 30 16:17:45 2026
Description:Title: Microsoft Teams meeting participants may not be granted permissions to meeting notes added after meeting creation
User impact: Microsoft Teams meeting participants may not be granted permissions to meeting notes added after meeting creation.
More info: 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.
Impact may occur when the admins have enabled the Specific People Link (SPL) policy.
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: Microsoft Teams meeting participants attempting to view meeting notes that were added after meeting creation may be impacted.
Root cause: A latent code misconfiguration is causing the impact.
Next update by: Monday, February 2, 2026, at 10:00 PM UTC
Time:Thu Jan 29 16:05:39 2026
Description:Title: Microsoft Teams meeting participants may not be granted permissions to meeting notes added after meeting creation
User impact: Microsoft Teams meeting participants may not be granted permissions to meeting notes added after meeting creation.
More info: 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.
Impact may occur when the admins have enabled the Specific People Link (SPL) policy.
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: Microsoft Teams meeting participants attempting to view meeting notes that were added after meeting creation may be impacted.
Root cause: A latent code misconfiguration is causing the impact.
Next update by: Friday, January 30, 2026, at 10:00 PM UTC
Time:Wed Jan 28 15:12:55 2026
Description:Title: Microsoft Teams meeting participants may not be granted permissions to meeting notes added after meeting creation
User impact: Microsoft Teams meeting participants may not be granted permissions to meeting notes added after meeting creation.
More info: 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.
Impact may occur when the admins have enabled the Specific People Link (PSL) policy.
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: Microsoft Teams meeting participants attempting to view meeting notes that were added after meeting creation may be impacted.
Root cause: A latent code misconfiguration is causing the impact.
Next update by: Thursday, January 29, 2026, at 10:00 PM UTC
Time:Wed Jan 28 14:52:53 2026
Description:Title: Microsoft Teams meeting participants may not be granted permissions to meeting notes added after meeting creation
User impact: Microsoft Teams meeting participants may not be granted permissions to meeting notes added after meeting creation.
More info: 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.
Impact may occur when the admins have enabled the Specific People Link (PSL) policy.
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.

EX1224375 - Users routing their Exchange Online email through a third-party protection service may have send and receive delays

Status:serviceRestored
Start Time:Mon Jan 26 01:00:00 2026
End Time:Fri Jan 30 13:25:00 2026
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:incident
Last Updated:Fri Jan 30 14:43:40 2026
Root Cause:A cache limit configuration that helps facilitate the impact scenario process with SMTP mail flow was misconfigured, resulting in impact.
Next Update:N/A

Details

Time:Fri Jan 30 14:26:22 2026
Description:Title: Users routing their Exchange Online email through a third-party protection service may have send and receive delays
User impact: Users' Exchange Online email routed through a third-party protection service may have been delayed.
More info: This issue specifically impacted users who use Simple Mail Transfer Protocol (SMTP) as their Exchange Online connection method and routed their email messages through a specific third-party email protection service. The email delays, which impacted both sending and receiving email, occurred in all Exchange Online connection methods.
Final status: We've fully implemented our identified configuration change and confirmed using internal telemetry that it effectively mitigated this issue. We determined that a cache limit configuration that helps facilitate the impact scenario process with SMTP mail flow was misconfigured, resulting in impact.
Scope of impact: This problem may have impacted any user sending or receiving email messages when leveraging a specific third-party email protection service.
Start time: Monday, January 26, 2026, at 6:00 AM UTC
End time: Friday, January 30, 2026, at 6:25 PM UTC
Root cause: A cache limit configuration that helps facilitate the impact scenario process with SMTP mail flow was misconfigured, resulting in impact.
Next steps: - We're continuing our research into identifying the root cause of this impacting event to better understand how to prevent it from happening again in the future.
This is the final update for the event.
Time:Fri Jan 30 12:49:22 2026
Description:Title: Users routing their Exchange Online email through a third-party protection service may have send and receive delays
User impact: Users routing their Exchange Online email through a third-party protection service may have send and receive delays.
More info: This issue specifically impacts users who use Simple Mail Transfer Protocol (SMTP) as their connection method and route their email messages through a specific third-party email protection service. The email delays, which impacts both sending and receiving email, occurs in all Exchange Online connection methods.
Current status: Though our investigation into the root cause of this impacting issue is ongoing, we've identified and implemented a configuration change in effort to mitigate the problem. We're reviewing our internal telemetry to assess if the configuration change was effective. Please note that we've updated the Title, User impact, and More info of this communication to better reflect the impact of the event.
Scope of impact: This problem may impact any user sending or receiving email messages when leveraging a specific third-party email protection service.
Next update by: Friday, January 30, 2026, at 8:00 PM UTC
Time:Thu Jan 29 16:19:48 2026
Description:Title: Users may experience delays when sending or receiving Exchange Online email messages
User impact: Users may experience delays when sending or receiving Exchange Online email messages.
More info: This issue specifically impacts users who are on Simple Mail Transfer Protocol (SMTP) connection methods, which include Outlook on the web, the Outlook desktop clients, and the mobile apps.
Current status: Our investigation has further identified that exceptions may be occurring as our mail transport service is sending an unexpectedly large amount of requests to downstream components in the mail routing code path. We're investigating recent changes to confirm this theory and determine next steps for remediation.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Next update by: Friday, January 30, 2026, at 7:30 PM UTC
Time:Thu Jan 29 14:19:17 2026
Description:Title: Users may experience delays when sending or receiving Exchange Online email messages
User impact: Users may experience delays when sending or receiving Exchange Online email messages.
More info: This issue specifically impacts users who are on Simple Mail Transfer Protocol (SMTP) connection methods, which include Outlook on the web, the Outlook desktop clients, and the mobile apps.
Current status: We've identified the "451 4.3.2 Temporary server error" occurring that's leading to impact. This error, generally, is a common error, however our review of transport service health telemetry confirmed an increase in the rate of this error generating. We're investigating why we see an increase of this error resulting in impact to better understand how the issue is manifesting and prepare next steps for potential remediating actions.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Next update by: Thursday, January 29, 2026, at 9:30 PM UTC
Time:Thu Jan 29 13:05:41 2026
Description:Title: Users may experience delays when sending or receiving Exchange Online email messages
User impact: Users may experience delays when sending or receiving Exchange Online email messages.
More info: This issue specifically impacts users who are on Simple Mail Transfer Protocol (SMTP) connection methods, which include Outlook on the web, the Outlook desktop clients, and the mobile apps.
Current status: We're reviewing transport service logs in parallel with samples of affected messages to identify and isolate any errors that may be contributing to impact for further investigation.
Scope of impact: Some users attempting to send or receive Exchange Online email messages may be impacted.
Next update by: Thursday, January 29, 2026, at 7:30 PM UTC
Time:Thu Jan 29 12:36:32 2026
Description:Title: Users may experience delays when sending or receiving Exchange Online email messages
User impact: Users may experience delays when sending or receiving Exchange Online email messages.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1221364 - Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services

Status:postIncidentReviewPublished
Start Time:Thu Jan 22 14:33:29 2026
End Time:Fri Jan 23 00:00:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Fri Jan 30 07:15:30 2026
Root Cause:We identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure.
Next Update:N/A

Details

Time:Fri Jan 30 07:15:30 2026
Description:A post-incident report has been published.
Time:Thu Jan 29 19:39:48 2026
Description:A post-incident report has been published.
Time:Thu Jan 29 19:11:05 2026
Description:A post-incident report has been published.
Time:Thu Jan 29 19:08:39 2026
Description:A post-incident report has been published.
Time:Thu Jan 29 19:07:54 2026
Description:A post-incident report has been published.
Time:Tue Jan 27 07:47:39 2026
Description:A post-incident report has been published.
Time:Mon Jan 26 19:58:56 2026
Description:A post-incident report has been published.
Time:Fri Jan 23 01:27:30 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may have seen degraded service functionality or were unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions included, but were not limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may have been unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not have been honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may have failed in Universal Print. - Microsoft To Do users may have experienced synchronization issues, preventing tasks from updating across devices. Additionally, tasks created in Shared Lists may not have appeared for collaborators. - Microsoft Defender for Cloud Apps users may not have been able to view insights or view, create, or update OAuth enabled app policies. Reporting data may have also appeared blank, even though no errors were shown. - Microsoft Defender for Office (MDO) users may have experienced limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection. - Microsoft Power Automate users may have been unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Final status: We’ve confirmed that the affected infrastructure has returned to a healthy state and is operating as expected. We’ll continue to closely monitor the remediation actions taken and make any necessary adjustments to maintain stability. If users experience any residual issues, clearing local DNS caches or temporarily lowering DNS TTL values may help ensure a quicker remediation.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may have been intermittently impacted. This could have affected users located in Asia-Pacific, Europe, or Latin America.
Preliminary root cause: As part of a planned maintenance activity to improve network routing infrastructure, one of the Cheyenne datacenters was removed from active service rotation. As part of this activity, GLS at the affected Cheyenne datacenter was taken offline on Thursday, January 22, 2026, at 5:45 PM UTC. It was expected that the remaining regional GLS capacity would be sufficient to handle the redirected traffic. Subsequent review of the incident identified that the load balancers that support the GLS service were unable to accept the redirected traffic in a timely manner causing the GLS load balancers to go into an unhealthy state. This sudden concentration of traffic led to an increase in retry activity, which further amplified the impact. Over time, these conditions triggered a cascading failure that affected dependent services, including mail flow and Domain Name System (DNS) resolution required for email delivery.
Start Time: Thursday, January 22, 2026, at 6:55 PM UTC
End Time: Friday, January 23, 2026, at 5:00 AM UTC
Next steps: For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
We've provided a Post-Incident Report for this incident. Additionally, we'll be updating the Post-Incident Report on a monthly basis, for the next six months, to show the status of the Next Steps. The first update will be provided by March 2, 2026.
Time:Fri Jan 23 01:00:40 2026
Description:We’ve confirmed that service restoration is complete. If users continue to see residual issues, clearing local DNS caches or temporarily lowering DNS TTL values can help ensure updates are reflected more quickly.
This quick update is designed to give the latest information on this issue.
Time:Fri Jan 23 00:31:54 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. - Microsoft To Do users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators. - Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown. - Microsoft Defender for Office (MDO) users may experience limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection. As basic mail flow continues to be restored, these associated experiences are expected to resume normal operation. - Microsoft Power Automate users may be unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Current status: We’ve a high level of confidence that the incident is largely resolved. Access to Microsoft Defender for Office, Microsoft Purview, and DNS functionality has been restored, and Exchange Online mail flow remains stable.
We're continuing to fine tune load balancing adjustments and closely monitor the impact of recent changes to support sustained recovery. While recovery efforts remain ongoing, we are methodically addressing the small number of remaining affected services to ensure full service stability.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: We identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure.
Next update by: Friday, January 23, 2026, at 6:30 AM UTC
Time:Thu Jan 22 23:58:13 2026
Description:We’re continuing to optimize service load distribution and are seeing improved accessibility in Microsoft Purview, along with a noticeable reduction in related errors.
This quick update is designed to give the latest information on this issue.
Time:Thu Jan 22 23:29:38 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. - Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators. - Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown. - Microsoft Defender for Office (MDO) users may experience limited access to administrative and SOC experiences, including the quarantine portal and Safe Links protection. As basic mail flow continues to be restored, these associated experiences are expected to resume normal operation. - Microsoft Power Automate users may be unable to utilize Power Automate connectors including Office 365, Office 365 Users, Office 365 Groups, and Office 365 Groups Mail.
Current status: We’ve identified elevated service load combined with temporary capacity constraints during maintenance resulted in impact. We’re seeing positive signs of recovery in mail delivery, and mitigation actions are in place to better manage service load. While some connectivity impact remains between Microsoft Defender for Office, Microsoft Purview, and Exchange Online, and DNS lookup failures, engineers are actively working to restore full functionality.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: We've identified that the issue was caused by elevated service load resulting from reduced capacity during maintenance for a subset of North America hosted infrastructure.
Next update by: Friday, January 23, 2026, at 5:30 AM UTC
Time:Thu Jan 22 22:28:10 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. - Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators. - Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
Current status: We’re continuing to see steady improvements in service availability for Exchange Online and Microsoft Teams and our broader recovery efforts remain actively underway. Engineers are further refining load balancing measures to accelerate recovery and are methodically addressing the remaining impacted services.
We do not yet consider this issue resolved and we remain committed to treating this issue with the highest urgency and priority. We understand how difficult it can be to operate without a confirmed estimated time to resolution. Please be assured that our teams are actively investigating and addressing the underlying causes of the impact, and we will share an estimated time for resolution as soon as one becomes available.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 4:30 AM UTC
Time:Thu Jan 22 21:24:44 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. - Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators. - Microsoft Defender for Cloud Apps users may be unable to view insights or view, create, or update OAuth enabled app policies. Reporting data may also appear blank, even though no error is shown.
Current status: We’re seeing continued improvements in service availability and functionality as a result of our load-balancing efforts. We’re actively monitoring performance and making targeted adjustments to further improve stability and availability, while continuing recovery actions to ensure a reliable service experience.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 3:30 AM UTC
Time:Thu Jan 22 20:57:29 2026
Description:We’re seeing notable improvements in availability and service functionality. We’ll continue to closely monitor performance and make any targeted adjustments to further enhance stability.
This quick update is designed to give the latest information on this issue.
Time:Thu Jan 22 20:25:39 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print. -Microsoft ToDo users may experience synchronization issues, which can prevent tasks from updating across devices. Additionally, tasks created in Shared Lists may not appear for collaborators.
Current status: We’re refining our load balancing efforts to optimize performance and reduce potential impact. In parallel, we’re assessing alternative solutions to reinforce recovery and enhance long term stability.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted. This could affect users located in Asia-Pacific, Europe, or Latin America.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 2:30 AM UTC
Time:Thu Jan 22 19:39:45 2026
Description:We’re actively optimizing load balancing configurations to address residual imbalances and reinforce recovery efforts, while taking additional precautions to minimize the risk of further recovery related issues.
This quick update is designed to give the latest information on this issue.
Time:Thu Jan 22 19:00:11 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print.
Current status: We're continuing to refine our load balancing configurations to remedy residual imbalances across the environment and further our ongoing recovery efforts.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 1:30 AM UTC
Time:Thu Jan 22 18:23:12 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces in Exchange Online. - Searching within SharePoint Online, Microsoft OneDrive, and/or Microsoft Teams. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print.
Current status: During our ongoing efforts to rebalance traffic across the region, we introduced a targeted load balancing configuration change intended to expedite the recovery process, which incidentally introduced additional traffic imbalances associated with persistent impact for a portion of the affected infrastructure. We're remedying our load balancing configurations while, in parallel, reviewing the viability of expediting our ongoing incremental rebalancing and recovery efforts.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Friday, January 23, 2026, at 12:30 AM UTC
Time:Thu Jan 22 17:29:59 2026
Description:While we’re proceeding as quickly as possible to effectively rebalance traffic to achieve recovery, we're also recursively monitoring the extent of the affected environment to identify whether additional actions may be required. We'll provide an estimated recovery timeline as soon as we have this information.
This quick update is designed to give the latest information on this issue.
Time:Thu Jan 22 17:15:39 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook. - Collecting message traces. - Searching within SharePoint Online and/or Microsoft OneDrive. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. Additionally, some users may be intermittently unable to create breakout rooms or Microsoft Teams live events. - Receiving presence or location information in Microsoft Teams. - Existing or new meeting options for Facilitator in Teams may not be honored. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric. - Print registration and printer jobs may fail in Universal Print.
Current status: We're carefully rebalancing traffic across all affected infrastructure in the region, while monitoring the corresponding health telemetry, to ensure the environment enters into a balanced state as our remediation efforts continue. We’re proceeding as quickly as possible and this incremental approach will also help us identify whether any additional actions may be required to ensure longstanding recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Thursday, January 22, 2026, at 11:30 PM UTC
Time:Thu Jan 22 16:32:38 2026
Description:We've implemented a traffic balancing solution within a limited portion of infrastructure and telemetry shows success. We're applying this solution incrementally across all affected infrastructure to ensure the environment remains balanced as recovery continues.
This quick update is designed to give the latest information on this issue.
Time:Thu Jan 22 16:09:48 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage as well as subscription email for Microsoft Fabric users. - Collecting message traces. - Searching within SharePoint Online and/or Microsoft OneDrive. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center. - Creating chats, meetings, teams, channels or adding members in Microsoft Teams. - Receiving presence or location information in Microsoft Teams. - Applying and managing sensitivity labels, interactive operations on reports, and artifacts with sensitivity labels in Microsoft Fabric.
Current status: While we've restored the affected infrastructure to a healthy state, further load balancing is required to mitigate persistent impact. We've identified and are implementing additional actions to direct requests and traffic to additional healthy sections of infrastructure to achieve withstanding recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Thursday, January 22, 2026, at 11:00 PM UTC
Time:Thu Jan 22 15:45:18 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage. - Collecting message traces may be delayed or fail. - Searches within SharePoint Online and/or Microsoft OneDrive mail be delayed or fail to complete. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
Current status: We're continuing to review what actions are required to restore the affected infrastructure to a healthy state and rebalance the service traffic to achieve recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Root cause: A portion of dependent service infrastructure in the North America region isn't processing traffic as expected.
Next update by: Thursday, January 22, 2026, at 11:00 PM UTC
Time:Thu Jan 22 15:16:08 2026
Description:Title: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send or receive email through Outlook.
Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification emails from Microsoft Viva Engage. - Accessing the service portals, including Microsoft Purview, Microsoft Defender XDR, and the Microsoft 365 admin center.
Current status: We've identified a portion of dependent service infrastructure in the North America region that is not processing traffic as expected. This is impacting our load balancing processes and general service availability. We're working to restore this infrastructure to a healthy state and rebalance the service traffic to achieve recovery.
Scope of impact: Any users served through an affected section of service infrastructure in the North America region may be intermittently impacted.
Next update by: Thursday, January 22, 2026, at 10:00 PM UTC
Time:Thu Jan 22 14:57:58 2026
Description:Title: Users may be seeing degraded service functionality across multiple Microsoft 365 services
User impact: Users may be seeing degraded service functionality across multiple Microsoft 365 services.
More info: Users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to send mail through Outlook.
Some of the impacted service functions include, but may not be limited to: - Sending and receiving email through Exchange Online, including notification email from Microsoft Viva Engage. - Accessing the service portals, including Microsoft Purview and Microsoft Defender XDR.
Current status: We're reviewing the reported impact scenarios and identifying what portion of the dependent service infrastructure is degraded so we can determine our next troubleshooting steps.
Scope of impact: The scope of this issue is currently being investigated.
Next update by: Thursday, January 22, 2026, at 9:00 PM UTC
Time:Thu Jan 22 14:44:56 2026
Description:As we rapidly pursue an investigation into the nature of the impact and the source of the issue, we've received reports that users may be receiving a "451 4.3.2 temporary server issue" error message when attempting to access the service portals or use Outlook.
This quick update is designed to give the latest information on this issue.
Time:Thu Jan 22 14:36:00 2026
Description:Title: We're investigating a potential issue affecting Microsoft 365 services
User impact: We've received reports of an issue affecting Microsoft 365 services.
Current status: We're investigating a potential issue with Microsoft 365 services and checking for impact to your organization. Initial reports indicate possible issues accessing the Microsoft Defender and Microsoft Purview portals, as well as issues using Outlook. We'll provide an update within 30 minutes.

EX1213792 - Admins can’t upgrade groups from distributions lists to unified groups from PowerShell and the Exchange admin center

Status:serviceDegradation
Start Time:Tue Jan 6 01:49:02 2026
End Time:N/A
Service:Exchange Online
Feature Group:Sign-in
Classification:advisory
Last Updated:Fri Jan 30 01:41:37 2026
Root Cause:A timing-related issue during group creation across backend systems where service requests are processed before directory information has fully refreshed across all servers, leading to impact.
Next Update:Monday, February 2, 2026, at 8:00 AM UTC

Details

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:Fri Jan 30 01:38:33 2026
Root Cause:A recent service operation intended to upgrade our API flow impacted Microsoft 365 Groups that were previously configured to have the "SecurityEnabled" setting enabled, switching this value back to "False" by default and resulting in impact to admins and users whose service access was being managed by the affected groups.
Next Update:Friday, February 6, 2026, at 8:00 AM UTC

Details

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

MV1224509 - Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app

Status:serviceRestored
Start Time:Thu Jan 29 04:00:00 2026
End Time:Thu Jan 29 17:50:00 2026
Service:Microsoft Viva
Feature Group:Viva Engage
Classification:advisory
Last Updated:Thu Jan 29 18:26:24 2026
Root Cause:A recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and prevented network admins from making network settings changes.
Next Update:N/A

Details

Time:Thu Jan 29 18:17:32 2026
Description:Title: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app
User impact: Users may have been unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app.
More info: Additionally, network admins may have been unable to change network settings for users.
Final status: We reverted the offending change and confirmed using our internal telemetry data that impact is remediated.
Scope of impact: Any users attempting to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, or any network admin attempting to change a user's network settings may have been impacted.
Start time: Thursday, January 29, 2026, at 9:00 AM UTC
End time: Thursday, January 29, 2026, at 10:50 PM UTC
Root cause: A recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and prevented network admins from making network settings changes.
Next steps: - We're reviewing and improving our schema field update validation procedure to detect and prevent similar issues from occurring in the future.
This is the final update for the event.
Time:Thu Jan 29 17:27:59 2026
Description:Title: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app
User impact: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app.
More info: Additionally, network admins may be unable to change network settings for users.
Current status: At the current stage of our update reversion, we've confirmed that users are able to access Microsoft Viva engage content, but network admins are still unable to change network settings. We're continuing to revert the offending update and expect it should complete and fully remediate impact by our next scheduled update.
Scope of impact: Any users attempting to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, or any network admin attempting to change a user's network settings.
Start time: Thursday, January 29, 2026, at 9:00 AM UTC
Root cause: A recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and preventing network admins from making network settings changes.
Next update by: Friday, January 30, 2026, at 12:30 AM UTC
Time:Thu Jan 29 15:55:31 2026
Description:Title: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app
User impact: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app.
More info: Additionally, network admins may be unable to change network settings for users.
Current status: We've identified that a recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and preventing network admins from making network settings changes. We're reverting this update to remediate impact.
Scope of impact: Any users attempting to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, or any network admin attempting to change a user's network settings.
Root cause: A recent schema field update was added to the network settings, preventing users from accessing Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app, and preventing network admins from making network settings changes.
Next update by: Thursday, January 29, 2026, at 10:30 PM UTC
Time:Thu Jan 29 15:10:59 2026
Description:Title: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app
User impact: Users may be unable to access Microsoft Viva Engage content for the first time in the Microsoft Teams mobile app.
More info: Additionally, network admins may be unable to change network settings for users.
Current status: We're investigating a potential issue with Microsoft Viva Engage and checking for impact to your organization. We'll provide an update within 30 minutes.

CW1224109 - Some users using Microsoft 365 Copilot Chat may have not seen any responses being generated

Status:serviceRestored
Start Time:Thu Jan 29 04:20:00 2026
End Time:Thu Jan 29 09:00:00 2026
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:incident
Last Updated:Thu Jan 29 09:41:20 2026
Root Cause:A section of Microsoft API service infrastructure had dropped below our manageable service performance thresholds, producing failures for users generating responses for Copilot Chat.
Next Update:N/A

Details

Time:Thu Jan 29 09:14:32 2026
Description:Title: Some users using Microsoft 365 Copilot Chat may have not seen any responses being generated
User impact: Users using Copilot Chat may not have seen any responses being generated.
More info: Users may have seen the following error message "Something went wrong. Please try again."
Final status: We've determined that a section of Microsoft API service infrastructure had dropped below our manageable service performance thresholds, producing failures for users generating responses for Copilot Chat. While we further investigate the source for the lower-than-expected service infrastructure performance levels, we've temporarily increased performance parameters to mitigate impact.
Scope of impact: Some users attempting to generate responses within Copilot Chat in the Europe may have been impacted.
Start time: Thursday, January 29, 2026, at 9:20 AM UTC
End time: Thursday, January 29, 2026, at 2:00 PM UTC
Root cause: A section of Microsoft API service infrastructure had dropped below our manageable service performance thresholds, producing failures for users generating responses for Copilot Chat.
Next steps: - We're further analyzing the affected subset of Microsoft API service infrastructure in our effort to isolate the source for the lower-than-normal performance levels, and to help prevent similar issues in the future.
This is the final update for the event.
Time:Thu Jan 29 07:25:21 2026
Description:Title: Some users using Microsoft 365 Copilot Chat may not see any responses being generated
User impact: Users using Copilot Chat may not see any responses being generated.
More info: Users may see the following error message "Something went wrong. Please try again."
Current status: We've received reports indicating users may be unable to generate responses within Copilot Chat. We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to generate responses within Copilot Chat in the Europe may be impacted.
Next update by: Thursday, January 29, 2026, at 2:30 PM UTC

CP1221896 - Users' query responses from the Facilitator agent in Microsoft Teams meetings are delayed up to 25 seconds

Status:serviceDegradation
Start Time:Mon Jan 12 23:00:00 2026
End Time:N/A
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Wed Jan 28 18:19:28 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:Thursday, February 5, 2026, at 12:30 AM UTC

Details

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:serviceDegradation
Start Time:Mon Jan 12 23:00:00 2026
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed Jan 28 18:17:16 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:Thursday, February 5, 2026, at 12:30 AM UTC

Details

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.

DZ1223715 - Users may be unable to access Threat Analytics in the Microsoft Defender XDR portal

Status:serviceRestored
Start Time:Wed Jan 28 12:14:00 2026
End Time:Wed Jan 28 13:22:00 2026
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Wed Jan 28 14:30:38 2026
Root Cause:The cache infrastructure performance fell below suboptimal thresholds, resulting in this impact.
Next Update:N/A

Details

Time:Wed Jan 28 14:30:38 2026
Description:Title: Users may be unable to access Threat Analytics in the Microsoft Defender XDR portal
User impact: Users may have been unable to access Threat Analytics in the Microsoft Defender XDR portal.
Final status: We determined that the cache infrastructure performance had fallen below suboptimal thresholds, and we applied manual mitigations to the affected portions of the infrastructure to relieve this impact. After a period of monitoring, we confirmed that the service returned to a healthy state.
Scope of impact: Any user attempting to access Threat Analytics in the Microsoft Defender XDR portal may have been impacted by this event.
Start time: Wednesday, January 28, 2026, at 5:14 PM UTC
End time: Wednesday, January 28, 2026, at 6:22 PM UTC
Root cause: The cache infrastructure performance fell below suboptimal thresholds, resulting in this impact.
Next steps: - We're reviewing the cache infrastructure to better understand what led to the error that resulted in impact and prevent similar future occurrences.
This is the final update for the event.
Time:Wed Jan 28 13:47:23 2026
Description:Title: Users may be unable to access Threat Analytics in the Microsoft Defender XDR portal
User impact: Users may have been unable to access Threat Analytics in the Microsoft Defender XDR portal.
Current status: We've investigated a problem in which users may have been unable to access Threat Analytics in the Microsoft Defender XDR portal and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.

EX1223427 - Some users may have been unable to access the Exchange admin center (EAC)

Status:serviceRestored
Start Time:Wed Jan 28 04:06:00 2026
End Time:Wed Jan 28 06:12:00 2026
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Wed Jan 28 07:43:09 2026
Root Cause:A section of infrastructure, responsible for facilitating EAC access, unexpectedly began performing below acceptable performance thresholds and caused impact.
Next Update:N/A

Details

Time:Wed Jan 28 07:39:32 2026
Description:Title: Some users may have been unable to access the Exchange admin center (EAC)
User impact: Users may have been unable to access the EAC.
Final status: We've identified that a section of infrastructure, responsible for facilitating EAC access, unexpectedly began performing below acceptable performance thresholds and caused impact. We've redirected affected traffic to alternate healthy infrastructure and confirmed impact is no longer occurring after a period of monitoring.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure attempting to access the EAC.
Start time: Wednesday, January 28, 2026, at 9:06 AM UTC
End time: Wednesday, January 28, 2026, at 11:12 AM UTC
Root cause: A section of infrastructure, responsible for facilitating EAC access, unexpectedly began performing below acceptable performance thresholds and caused impact.
Next steps: - We're reviewing performance data and trends on the affected systems to help prevent similar impact from happening again.
This is the final update for the event.
Time:Wed Jan 28 06:29:05 2026
Description:Title: Some users may be unable to access the Exchange admin center (EAC)
User impact: Users may be unable to access the EAC.
Current status: We're continuing to review service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to access the EAC.
Next update by: Wednesday, January 28, 2026, at 2:00 PM UTC
Time:Wed Jan 28 04:49:26 2026
Description:Title: Some users may be unable to access the Exchange admin center (EAC)
User impact: Users may be unable to access the EAC.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to access the EAC.
Next update by: Wednesday, January 28, 2026, at 12:00 PM UTC

TM1221763 - Users may have seen a User Interface (UI) glitch in Microsoft Teams which showed an added bar at the top of each window

Status:serviceRestored
Start Time:Thu Jan 15 19:00:00 2026
End Time:Sun Jan 25 01:30:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed Jan 28 06:58:20 2026
Root Cause:A code regression in the WebView2 version 144.0.3719.82 was causing impact to occur.
Next Update:N/A

Details

Time:Wed Jan 28 06:58:20 2026
Description:Title: Users may have seen a User Interface (UI) glitch in Microsoft Teams which showed an added bar at the top of each window
User impact: Users may have seen a User Interface (UI) glitch in Microsoft Teams which showed an added bar at the top of each window.
More info: This specifically impacted users of WebView2 version 144.0.3719.82 on Windows 10 devices.
Some users may be required to manually install the latest WebView2 version if it was not automatically applied. The download is available at the following link: https://developer.microsoft.com/en-us/microsoft-edge/webview2?form=MA13LH#download
Final status: We’ve confirmed that the updated WebView2 version has been released. While we previously advised that affected users might need to update their Microsoft Teams client, this is no longer required. If impact persists, users should verify that they are running the latest stable version of WebView2. Users on an older version will need to manually update WebView2 by following the instructions provided in the More info section of this communication.
Scope of impact: Impact is specific to some users that are on WebView2 version 144.0.3719.82 on Windows 10 devices.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
End time: Sunday, January 25, 2026, at 6:30 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 was causing impact to occur.
Next steps: - We're reviewing our WebView2 configuration to help prevent similar problems in the future.
This is the final update for the event.
Time:Mon Jan 26 11:37:46 2026
Description:Title: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window
User impact: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window.
More info: This specifically impacts users of WebView2 version 144.0.3719.82 on Windows 10 devices.
Current status: We made the necessary adjustments to our fix and have deployed it as WebView2 version update 144.0.3719.93, where it is saturating across the affected environment. We expect that this saturation and full remediation will complete by our next scheduled update. Users should update their Microsoft Teams client to version 144.0.3719.93 as it becomes available to them and restart their Microsoft Teams apps in order to remediate impact.
Scope of impact: Impact is specific to some users that are on WebView2 version 144.0.3719.82 on Windows 10 devices.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 is causing impact to occur.
Next update by: Wednesday, January 28, 2026, at 8:00 PM UTC
Time:Fri Jan 23 18:39:41 2026
Description:Title: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window
User impact: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window.
More info: This specifically impacts users that are using WebView2 version 144.0.3719.82 on Windows 10 devices.
Current status: We’re making the necessary adjustments to expedite the deployment of our fix to resolve the issue as soon as possible and anticipate the fix should reach affected users by our next scheduled update.
Scope of impact: Impact is specific to some users that are on WebView2 version 144.0.3719.82 on Windows 10 devices.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 is causing impact to occur.
Next update by: Monday, January 26, 2026, at 8:00 PM UTC
Time:Fri Jan 23 12:15:21 2026
Description:Title: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window
User impact: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window.
More info: This specifically impacts users that are using WebView2 version 144.0.3719.82 on Windows 10 devices.
Current status: We've developed a code fix to remove the added bar and expect that it'll complete deployment by the time of our next update.
Scope of impact: Impact is specific to some users that are on WebView2 version 144.0.3719.82 on Windows 10 devices.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 is causing impact to occur.
Next update by: Friday, January 30, 2026, at 6:00 PM UTC
Time:Fri Jan 23 07:58:01 2026
Description:Title: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window
User impact: Users may see a User Interface (UI) glitch in Microsoft Teams which shows an added bar at the top of each window.
More info: This specifically impacts users that are using WebView2 version 144.0.3719.82 on Windows 10 devices.
Current status: We've identified a code regression in the WebView2 version 144.0.3719.82 is causing impact to occur. We’re working to identify the safest and most effective way to mitigate the impact.
Scope of impact: Impact is specific to some users utilizing the UI in Microsoft Teams.
Start time: Friday, January 16, 2026, at 12:00 AM UTC
Root cause: A code regression in the WebView2 version 144.0.3719.82 is causing impact to occur.
Next update by: Friday, January 23, 2026, at 7:00 PM UTC

TM1217690 - Some users may be unable to open some SharePoint Online list links through Microsoft Teams on iOS and receive an error

Status:serviceDegradation
Start Time:Wed Jan 14 00:04:38 2026
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Wed Jan 28 02:50:14 2026
Root Cause:A latent code issue is affecting the request flow leveraged for SharePoint Online list link access within Microsoft Teams on iOS, resulting in impact.
Next Update:Wednesday, February 11, 2026, at 8:00 AM UTC

Details

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.

MV1220701 - Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in

Status:serviceDegradation
Start Time:Wed Jan 21 15:53:16 2026
End Time:N/A
Service:Microsoft Viva
Feature Group:Viva Insights
Classification:advisory
Last Updated:Tue Jan 27 14:01:12 2026
Root Cause:A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next Update:Tuesday, February 17, 2026, at 7:30 PM UTC

Details

Time:Tue Jan 27 14:01:12 2026
Description:Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: We've completed the restoration of the usage data; however, we've determined that the process to backfill the restored data to be made available to admins will require additional time. Initial projections indicate the process will finish by the end of March 2026. We're monitoring this process and will provide an updated timeline as one becomes available.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Tuesday, February 17, 2026, at 7:30 PM UTC
Time:Mon Jan 26 12:59:14 2026
Description:Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts macOS admins using the Microsoft Viva Insights desktop, mobile, and web Outlook add-ins.
Current status: We've determined that restoring the usage data will require a bit longer than previously expected, and we're now projecting that the process will have completed and that impact will be remediated by our next scheduled communication update.
Scope of impact: Your organization is affected by this event, and any admin on macOS attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Tuesday, January 27, 2026, at 7:30 PM UTC
Time:Fri Jan 23 13:57:00 2026
Description:Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts Mac OS admins using the Microsoft Viva Insights desktop, mobile and web Outlook add-ins.
Current status: We've corrected the metadata file to prevent additional impact and we're in the process of restoring the usage data to correct metrics. We anticipate all past usage data will be restored to expected values by our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and any admins attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Estimated time to resolve: We anticipate all usage data will be restored to correct metrics by Monday, January 26, 2026, at 7:30 PM UTC.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Monday, January 26, 2026, at 7:30 PM UTC
Time:Wed Jan 21 16:36:20 2026
Description:Title: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Admins receive inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
More info: This impacts Mac OS admins using the Microsoft Viva Insights desktop, mobile and web Outlook add-ins.
Current status: We've identified that a recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events. We're correcting this metadata file to prevent additional impact, and we'll subsequently restore the usage data to provide the correct metrics to completely resolve the issue.
Scope of impact: Your organization is affected by this event, and any admins attempting to see the Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in are impacted.
Root cause: A recent update to the Microsoft Viva Insights Outlook add-in contains a metadata file that counts five actions per event, causing a spike in email action count events.
Next update by: Friday, January 23, 2026, at 7:00 PM UTC
Time:Wed Jan 21 15:55:15 2026
Description:Title: Users see inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in
User impact: Users see inaccurate Microsoft Copilot usage metrics exported from the Microsoft Viva Insights Outlook add-in.
Current status: We're investigating a potential issue with the Microsoft Viva Insights Outlook add-in and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1221839 - Some users were unable to view attached meetings URLs for Microsoft Teams meetings or see the Microsoft Teams toggle

Status:serviceRestored
Start Time:Thu Jan 22 15:42:00 2026
End Time:Sun Jan 25 00:00:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Jan 27 08:59:39 2026
Root Cause:Impact associated to Service Incident (SI) MO1221364 caused the default meeting property provider to show as unknown instead of Microsoft Teams for users, which resulted in this impact.
Next Update:N/A

Details

Time:Tue Jan 27 08:59:39 2026
Description:Title: Some users were unable to view attached meetings URLs for Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Users were unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users could have circumvented this impact by sending meeting URLs from the classic Outlook desktop experience.
Final status: We’ve determined that impact associated to Service Incident (SI) MO1221364 caused impact to occur. We've received confirmation from a further subset of affected users that impact is no longer occurring and after an extended period of monitoring service health, can confirm that the issue is resolved.
Scope of impact: Some users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Start time: Thursday, January 22, 2026, at 8:42 PM UTC
End time: Sunday, January 25, 2026, at 5:00 AM UTC
Root cause: Impact associated to Service Incident (SI) MO1221364 caused the default meeting property provider to show as unknown instead of Microsoft Teams for users, which resulted in this impact.
Next steps: - We're further reviewing the event and the circumstances that lead to impact, so that we can identify next steps that'll help us further improve the reliability and resiliency of our service.
This is the final update for the event.
Time:Mon Jan 26 07:20:05 2026
Description:Title: Some users may be unable to view attached meetings URLs for Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: We’re continuing to monitor the service telemetry and expect to share more details in our next scheduled update.
Scope of impact: Some users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Root cause: A transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users is resulting in this impact.
Next update by: Tuesday, January 27, 2026, at 2:30 PM UTC
Time:Fri Jan 23 19:37:44 2026
Description:Title: Some users may be unable to view attached meeting URLs for Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: While we were in the process of applying our temporary mitigation, system monitoring has indicated that the service has returned to normal healthy state independent of our deployment. We've confirmed that the issue is no longer occurring for a subset of affected users and anticipate the service will return to a healthy state for the remaining impacted users by January 24, 2026, based on trends in service health telemetry. We'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Some users may be unable to view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Root cause: A transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users is resulting in this impact.
Next update by: Monday, January 26, 2026, at 12:30 PM UTC
Time:Fri Jan 23 18:41:57 2026
Description:Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: After further investigation, we determined that this transient error is a symptom of different underlying issue and we're investigating this root cause to help develop a permanent fix for this issue. While this is ongoing, we've developed a temporary fix to address this issue and are monitoring it with a subset of affected users to ensure it restores services.
Scope of impact: Your organization is impacted by this event, and some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Root cause: A transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users is resulting in this impact.
Next update by: Saturday, January 24, 2026, at 1:30 AM UTC
Time:Fri Jan 23 16:40:27 2026
Description:Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: We've determined that this issue is related to a known transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users, resulting in this impact. We've developed a temporary fix to address this issue, which we have deployed to a subset of affected users. We're monitoring this temporary fix as we work to develop a permanent solution for this issue.
Scope of impact: Your organization is impacted by this event, and some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Root cause: A transient error in which the default meeting property provider shows as unknown instead of Microsoft Teams for users, results in this impact.
Next update by: Friday, January 23, 2026, at 11:30 PM UTC
Time:Fri Jan 23 15:28:10 2026
Description:Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: We're continuing our review of HTTP Archive format (HAR) traces and documentation of impact and working to confirm a potential correlation to an ongoing event as we actively work on developing troubleshooting steps to address this impact for your organization.
Scope of impact: Your organization is impacted by this event, and some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 10:30 PM UTC
Time:Fri Jan 23 14:10:06 2026
Description:Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: We're reviewing the HTTP Archive format (HAR) traces and documentation of impact provided by your organization to assist in our investigation of the underlying root cause and the development of our next troubleshooting steps.
Scope of impact: Your organization is impacted by this event, and some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle. This information may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 8:30 PM UTC
Time:Fri Jan 23 13:46:42 2026
Description:Title: Some users can't view attached meetings URLs Microsoft Teams meetings or see the Microsoft Teams toggle
User impact: Some users can't view attached meeting URLs for new Microsoft Teams meetings or see the Microsoft Teams toggle.
More info: Users can circumvent this impact by sending meeting URLs from the classic Outlook desktop experience.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1215277 - Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels

Status:serviceDegradation
Start Time:Wed Jan 7 20:41:26 2026
End Time:N/A
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Jan 27 03:41:47 2026
Root Cause:A recent API configuration change contains an error, which is resulting in impact.
Next Update:Monday, February 9, 2026, at 12:00 PM UTC

Details

Time:Tue Jan 27 03:41:47 2026
Description:Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
Current status: We’ve successfully completed validation checks and are now proceeding with deployment. We expect the deployment to complete by Saturday, February 7, 2026. Once deployed, we’ll monitor for an extended period of time, to ensure the impact has been fully remediated.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Estimated time to resolve: Saturday, February 7, 2026
Root cause: A recent API configuration change contains an error, which is resulting in impact.
Next update by: Monday, February 9, 2026, at 12:00 PM UTC
Time:Mon Jan 26 08:37:51 2026
Description:Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
Current status: We’re progressing with final validation checks before proceeding with the deployment.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Tuesday, January 27, 2026, at 11:30 AM UTC
Time:Mon Jan 26 07:00:15 2026
Description:Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We’re continuing to complete final validation checks before proceeding with the deployment.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Monday, January 26, 2026, at 1:30 PM UTC
Time:Thu Jan 22 23:31:34 2026
Description:Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We’ve completed development for one part of the fix and are completing final checks before proceeding with the remaining work. Once those checks are finished, we’ll move forward with the next phase and deployment. We’ll share an updated timeline once those steps are complete.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Monday, January 26, 2026, at 11:30 AM UTC
Time:Wed Jan 21 08:01:37 2026
Description:Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: Development of the fix is nearing completion, which we expect to conclude by Thursday, January 22, 2026. Once finalized, we'll begin the deployment and share an estimated timeline as soon as one becomes available.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Friday, January 23, 2026, at 6:30 AM UTC
Time:Tue Jan 13 04:05:16 2026
Description:Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We're in the final stages of developing the fix and expect completion by Wednesday, January 21, 2026. Once finalized, we will begin the rollout and share a detailed deployment timeline as soon as it becomes available.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Wednesday, January 21, 2026, at 2:30 PM UTC
Time:Fri Jan 9 07:16:06 2026
Description:Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We're continuing to develop a fix to validate the root cause and mitigation internally and will provide a remediation timeline once available.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Tuesday, January 13, 2026, at 2:30 PM UTC
Time:Thu Jan 8 17:11:40 2026
Description:Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
More info: While we're working to remediate impact, affected admins can create other users, including other admins, who can subsequently add users to owner or member roles and bypass the problem.
Current status: We've identified that a recent API configuration change contains an error resulting in impact. We're in the process of developing a fix to validate the root cause and mitigation internally and will provide a remediation timeline once available.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels.
Next update by: Friday, January 9, 2026, at 12:30 PM UTC
Time:Wed Jan 7 22:37:58 2026
Description:Title: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels
User impact: Admins are unable to add users to the owner or member roles for Private Microsoft Teams channels.
Current status: We've received reports from admins unable to add users as owners or members for private channels. We've reviewed our logs and we’ve identified a recent service change that we suspect may be causing impact. We're testing and validating a potential fix that we anticipate will confirm our theory and resolve the issue.
Scope of impact: Your organization is affected by this event, and admins are unable to add users to the owner or member roles for Private Teams channels. This section may be updated as our investigation continues.
Next update by: Thursday, January 8, 2026, at 11:00 PM UTC

CR1222626 - Degraded plug-in functionality

Status:serviceRestored
Start Time:Mon Jan 26 12:02:00 2026
End Time:Mon Jan 26 18:38:00 2026
Service:Dynamics 365 Apps
Feature Group:Other
Classification:advisory
Last Updated:Mon Jan 26 19:13:40 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Mon Jan 26 19:13:40 2026
Description:Title: Degraded plug-in functionality
User impact: Plug-in functionality was degraded.
Final Status: We have confirmed that the node restarts restored functionality via service health diagnostics.
This is the final update for this incident.
Preliminary Root Cause: A portion of an upstream dependency service, that supports plug-in functionality, entered an unhealthy state.
Next Steps: We're reviewing our configuration procedures to find ways to prevent this problem from happening again.
Time:Mon Jan 26 18:41:14 2026
Description:Title: Degraded plug-in functionality
User impact: Plug-in functionality is degraded.
Current Status: After our investigation, we identified that a portion of an upstream dependency service, that supports plug-in functionality, entered an unhealthy state. As a preliminary troubleshooting step, we restarted nodes on the affected infrastructure and are monitoring telemetry for recovery.
Next Update: Tuesday, January 27, 2026, at 3:30 AM UTC
Time:Mon Jan 26 18:22:27 2026
Description:Title: Degraded plug-in functionality
User impact: Plug-in functionality is degraded.
Current Status: We are aware of an emerging issue where users are experiencing degraded plug-in functionality and failures. We are investigating the issue and will provide another update within the next 30 minutes.
This information is preliminary and may be subject to changes, corrections, and updates.

CW1218323 - Users aren't shown the "Edit in Outlook" button after prompting Copilot Chat to draft an email message

Status:serviceDegradation
Start Time:Thu Jan 15 13:55:08 2026
End Time:N/A
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:advisory
Last Updated:Mon Jan 26 17:30:57 2026
Root Cause:We've disabled the "Edit in Outlook" feature in Copilot Chat while we implement a fix for a separate service issue relating to the feature, causing impact.
Next Update:Tuesday, February 3, 2026, at 11:00 PM UTC

Details

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.

MO1218616 - Some admins may be unable to view pooled storage management in the Microsoft 365 admin center

Status:serviceRestored
Start Time:Mon Jan 5 17:40:00 2026
End Time:Sun Jan 25 17:28:00 2026
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Mon Jan 26 16:54:06 2026
Root Cause:A recent code change intended to update how storage reports were loaded to the Microsoft 365 admin center introduced a regression which was causing the impact.
Next Update:N/A

Details

Time:Mon Jan 26 16:54:06 2026
Description:Title: Some admins may be unable to view pooled storage management in the Microsoft 365 admin center
User impact: Admins may have been unable to view pooled storage management in the Microsoft 365 admin center.
More info: This issue was specific to Microsoft 365 Education admins.
Final status: We've completed the deployment of our fix and confirmed after testing with a subset of affected users that this has successfully remediated impact.
Scope of impact: Admins in Microsoft 365 Education organizations attempting to view pooled storage management in the Microsoft 365 admin center may have been impacted.
Start time: Monday, January 5, 2026, at 10:40 PM UTC
End time: Sunday, January 25, 2026, at 10:28 PM UTC
Root cause: A recent code change intended to update how storage reports were loaded to the Microsoft 365 admin center introduced a regression which was causing the impact.
Next steps: - We're reviewing our code change testing and validation procedures to identify opportunities to identify impact earlier and prevent similar future occurrences.
This is the final update for the event.
Time:Fri Jan 23 13:39:14 2026
Description:Title: Some admins may be unable to view pooled storage management in the Microsoft 365 admin center
User impact: Admins may be unable to view pooled storage management in the Microsoft 365 admin center.
More info: This issue is specific to Microsoft 365 Education admins.
Current status: The code fix has saturated to 92 percent of the affected environment. As the deployment progresses and applies to the content hosting infrastructure to which admins are connecting, admins may begin to see the issue automatically resolve upon refreshing the storage report page. We expect the code fix will saturate the affected environment 100 percent on Wednesday, January 28, 2026.
Scope of impact: Admins in Microsoft 365 Education organizations attempting to view pooled storage management in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Monday, January 5, 2026, at 10:40 PM UTC
Root cause: A recent code change intended to update how storage reports are loaded to the Microsoft 365 admin center introduced a regression which is causing the impact.
Next update by: Wednesday, January 28, 2026, at 8:00 PM UTC
Time:Tue Jan 20 14:00:21 2026
Description:Title: Some admins may be unable to view pooled storage management in the Microsoft 365 admin center
User impact: Admins may be unable to view pooled storage management in the Microsoft 365 admin center.
More info: This issue is specific to Microsoft 365 Education admins.
Current status: The code fix has saturated to 66 percent of the affected environment. As the deployment progresses and applies to the content hosting infrastructure to which admins are connecting, admins may begin to see the issue automatically resolve upon refreshing the storage report page.
Scope of impact: Admins in Microsoft 365 Education organizations attempting to view pooled storage management in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Monday, January 5, 2026, at 10:40 PM UTC
Root cause: A recent code change intended to update how storage reports are loaded to the Microsoft 365 admin center introduced a regression which is causing the impact.
Next update by: Friday, January 23, 2026, at 8:00 PM UTC
Time:Fri Jan 16 12:34:29 2026
Description:Title: Some admins may be unable to view pooled storage management in the Microsoft 365 admin center
User impact: Admins may be unable to view pooled storage management in the Microsoft 365 admin center.
More info: This issue is specific to Microsoft 365 Education admins.
Current status: We've identified a recent code change intended to update how storage reports are loaded to the Microsoft 365 admin center introduced a regression which is causing the impact. We've developed and are deploying a code fix to correct this issue and confirmed the deployment is currently saturated 13 percent of the infrastructure that supports Microsoft 365 Education. We'll provide a timeline for remediation as one becomes available.
Scope of impact: Admins in Microsoft 365 Education organizations attempting to view pooled storage management in the Microsoft 365 admin center may be impacted. This information may be updated as our investigation continues.
Start time: Monday, January 5, 2026, at 10:40 PM UTC
Root cause: A recent code change intended to update how storage reports are loaded to the Microsoft 365 admin center introduced a regression which is causing the impact.
Next update by: Friday, January 23, 2026, at 7:30 PM UTC
Time:Fri Jan 16 10:34:30 2026
Description:Title: Some users may be unable to access or view the storage usage page in the M365 admin center
User impact: Users may be unable to access or view the storage usage page in the M365 admin center.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to access or view the storage usage page in the M365 admin center may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, January 16, 2026, at 5:30 PM UTC

TM1216503 - Some users may experience degraded video and screensharing quality in Microsoft Teams

Status:postIncidentReviewPublished
Start Time:Tue Dec 30 20:00:00 2025
End Time:Fri Jan 16 16:00:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon Jan 26 14:51:42 2026
Root Cause:In April 2025, we introduced an improved timestamping algorithm that provided more accurate bandwidth estimates for media traffic, to help deliver better video call quality. However, we’ve subsequently identified that this change inadvertently introduced a code defect that only occurred when Microsoft Teams back-end components had run for an extended period without being restarted. When this happened, bandwidth estimates stopped working correctly, resulting in poor video quality for some calls.
Next Update:N/A

Details

Time:Mon Jan 26 14:50:09 2026
Description:A post-incident report has been published.
Time:Mon Jan 19 01:22:22 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may have experienced degraded video and screensharing quality in Microsoft Teams.
More info: The issue wasn't limited to Microsoft Teams Rooms (MTR) devices and also affected desktop clients and other scenarios.
Final status: After extensive monitoring, we've confirmed that the configuration change was successful and the impact is remediated.
Scope of impact: This issue could have affected users joining Microsoft Teams meetings whose requests were routed through portions of Microsoft Teams infrastructure that have received the update.
Root cause: In April 2025, we introduced an improved timestamping algorithm that provided more accurate bandwidth estimates for media traffic, to help deliver better video call quality. However, we’ve subsequently identified that this change inadvertently introduced a code defect that only occurred when Microsoft Teams back-end components had run for an extended period without being restarted. When this happened, bandwidth estimates stopped working correctly, resulting in poor video quality for some calls.
This code defect was not triggered and did not cause impact to customers between April and December 2025 due to our back-end components being regularly restarted. From November 2025, some components were no longer being restarted as frequently due to a planned change in deployment cadence, and by January 2026, we began to see an increase in poor video quality on calls, which was later identified as linked to components encountering this code defect. Upon review, the validations for this change did not cover long-duration runtime scenarios, which resulted in this defect not being identified during testing.
Start time: Wednesday, December 31, 2025, at 1:00 AM UTC
End time: Friday, January 16, 2026, at 9:00 PM UTC
Next Steps: - For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
Time:Fri Jan 16 20:33:17 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We've confirmed that our configuration change has taken effect throughout the affected environment and our service metrics indicate impact is no longer occurring. We're proceeding with an additional period of monitoring for final validation that the issue is resolved.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Monday, January 19, 2026, at 7:30 AM UTC
Time:Fri Jan 16 15:51:19 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We've applied the ECS configuration change to all affected environments and are completing a period of monitoring to ensure it resolves impacted as expected.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Saturday, January 17, 2026, at 3:00 AM UTC
Time:Fri Jan 16 13:11:02 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We're continuing our incremental application of the ECS configuration change to a portion of the affected environments, and we've received reports from users that this change remediates impact. We anticipate that the deployment will complete for all affected environments by Friday, January 16, 2026.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 10:00 PM UTC
Time:Fri Jan 16 02:02:42 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We incrementally applied the ECS configuration change to a portion of the affected environments and are seeing positive results. In addition, we've received confirmation from a subset of affected users that the performance has improved. We plan to continue rolling out the ECS configuration change incrementally and if things are continuing to trend positively, we'll start the broader deployment. We anticipate that the deployment will complete by Friday, January 16, 2026.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 7:00 PM UTC
Time:Thu Jan 15 22:17:39 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We’re continuing to incrementally apply the ECS configuration change and closely monitor the affected environments to ensure we’re seeing positive results. In parallel, we’re validating with a subset of affected users to confirm they’re seeing the expected improvements before proceeding with broader deployment, which we expect to complete by Friday, January 16, 2026.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 8:00 AM UTC
Time:Thu Jan 15 19:20:55 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We’ve confirmed that our ECS configuration change remediation is operating as expected within our internal environment and we’re progressing incrementally with the change to affected users. We’ll continue to monitor and assess as the change is applied with the expectation that it should reach all affected users by Friday, January 16, 2026.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 4:00 AM UTC
Time:Thu Jan 15 17:07:08 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue isn’t limited to Microsoft Teams Rooms (MTR) devices but also affects desktop clients and other scenarios.
Current status: We're continuing to validate the ECS configuration change fix to ensure it will remediate the impact without introducing any adverse effects.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Friday, January 16, 2026, at 1:30 AM UTC
Time:Thu Jan 15 13:34:08 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue is not limited to Microsoft Teams Rooms (MTR) devices, but also affects desktop clients and other scenarios.
Current status: We determined that our fix didn't remediate impact as expected. We're validating an Enhanced Configuration Service (ECS) configuration change fix that we believe will more appropriately alleviate impact.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Thursday, January 15, 2026, at 11:00 PM UTC
Time:Thu Jan 15 10:06:20 2026
Description:Title: Some users may experience degraded video and screensharing quality in Microsoft Teams
User impact: Users may experience degraded video and screensharing quality in Microsoft Teams.
More info: The issue is not limited to Microsoft Teams Rooms (MTR) devices, but also affects desktop clients and other scenarios.
Current status: A permanent fix is now being deployed across all impacted environments. We'll share an estimated timeline for full resolution as soon as it’s available.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update inadvertently introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Thursday, January 15, 2026, at 7:00 PM UTC
Time:Wed Jan 14 20:09:06 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: The issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android but is not limited to these devices. Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: Our investigation into the root cause of impact has identified that a recent Microsoft Teams server update unintentionally introduced a corruption scenario, leading to degraded video or screensharing quality during calls. We're continuing our deployment to the remaining impacted regions, and we'll provide a timeline for full remediation once one becomes available.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Root cause: A recent Microsoft Teams server update unintentionally introduced a corruption scenario, leading to degraded video or screensharing quality during calls.
Next update by: Thursday, January 15, 2026, at 7:00 PM UTC
Time:Wed Jan 14 18:08:49 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: The issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android but is not limited to these devices.
Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're continuing to monitor the deployment of this fix and actively investigating a method by which we can accelerate the mitigation in all impacted regions. We're working to determine an accurate timeline for remediation and will provide one when it becomes available.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Thursday, January 15, 2026, at 2:00 AM UTC
Time:Wed Jan 14 15:47:24 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: The issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android but is not limited to these devices.
Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: While the deployment of the fix is underway, we're continuing our efforts to identify a method by which we can accelerate the mitigation, and we'll provide a timeline for impact resolution as one becomes available.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Thursday, January 15, 2026, at 12:30 AM UTC
Time:Wed Jan 14 13:07:16 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: The issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android but is not limited to these devices.
Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We've identified an issue which can lead to degraded video quality during calls for some users which was introduced in the latest Microsoft Teams server deployment. We've developed and begun deploying a mitigation strategy which has proven successful at remediating the impact during our testing, and a small number of users should already be experiencing relief. We're exploring options to expedite the deployment of the fix to fully resolve the issue.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Wednesday, January 14, 2026, at 10:00 PM UTC
Time:Tue Jan 13 19:37:48 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We encountered an obstacle that has delayed our effort to internally reproduce the impact and confirm the source for the degraded video quality for users being added to ongoing Microsoft Teams meetings. We're addressing this internal issue now as we continue to enable enhanced media and server logging.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Wednesday, January 14, 2026, at 7:00 PM UTC
Time:Tue Jan 13 16:47:18 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: As we continue our efforts to internally reproduce the impact and confirm the source for the degraded video quality for users being added to ongoing Microsoft Teams meetings, we're continuing to enable enhanced media and server logging which will be required before we can apply a potential mitigation.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Wednesday, January 14, 2026, at 2:00 AM UTC
Time:Tue Jan 13 13:18:29 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We’re continuing to enable enhanced media and server logging to validate and apply a mitigation action. In parallel, we’re reviewing contextual details shared by affected users and attempting to reproduce the issue internally to isolate the source of the problem and confirm the full scope of impact.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 10:30 PM UTC
Time:Tue Jan 13 06:07:56 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: While we continue enabling enhanced media and server logging as a potential mitigation, we're reviewing additional contextual details shared by some affected users to help pinpoint the root cause.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 7:00 PM UTC
Time:Tue Jan 13 03:27:41 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're continuing to enable robust media and server logging as a initial mitigation step. We're also working with your organizations representatives to obtain further contextual details to help us understand the root cause and full mitigation plan.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 12:30 PM UTC
Time:Mon Jan 12 22:25:25 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We’ve successfully reproduced the issue in our local testing environment. We’re enabling robust media and server logging to continue our investigation into the underlying cause of this issue and determine our next steps.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 8:30 AM UTC
Time:Mon Jan 12 19:29:26 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're continuing to work with a subset of affected users to perform further reproductions of impact and collect additional logs to assist our investigation into the source of the issue. In parallel, we're exploring potential mitigation strategies to help relieve this impact for users.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 4:30 AM UTC
Time:Mon Jan 12 14:58:05 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: After further investigation, we've confirmed the issue primarily occurs on Microsoft Teams Meeting Room devices using both Windows and Android. We're working with a subset of affected users to perform further reproductions of impact and collect additional logs to assist our investigation into the source of the issue.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Tuesday, January 13, 2026, at 1:30 AM UTC
Time:Mon Jan 12 13:16:45 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: Our review of the provided logging identified that the bandwidth estimation coming from the media player to the client is very low, causing the outbound traffic from the client to the media player component to be a very low video quality. We suspect there may be two possibilities as to why impact is occurring - either bandwidth estimation isn't running at all or it's falling back to an older bandwidth estimation algorithm, resulting in an incorrect estimation and thus the low resolution.
To determine the source of the issue, we're working to reproduce the impact in our internal environment for more insight into how impact manifests. In parallel, we're reviewing overall telemetry for instances where bandwidth estimation is low to further correlate when the issue began with any potential impacting changes that may have occurred at the same time. We’re also investigating additional client and device logs to assist with our investigation.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Monday, January 12, 2026, at 9:00 PM UTC
Time:Mon Jan 12 09:16:22 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're reviewing networking related logging alongside affected user details to isolate the root cause and develop a remediation plan.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Monday, January 12, 2026, at 6:30 PM UTC
Time:Mon Jan 12 06:11:34 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're continuing to await input from an impacted user to confirm whether media flow is being disrupted and to validate potential mitigation options.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Monday, January 12, 2026, at 2:30 PM UTC
Time:Sun Jan 11 03:29:53 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We’ve determined that Microsoft Teams meetings are currently routed through a relay service, which acts as an intermediary when direct peer-to-peer communication isn’t possible, and may be contributing to the issue. We’re awaiting input from an impacted user to confirm whether media flow is being disrupted and to validate potential mitigation options.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Monday, January 12, 2026, at 10:30 AM UTC
Time:Sat Jan 10 20:48:45 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're reviewing a reproduction of impact provided by some affected users in tandem with service side networking logs to refine our understanding of the underlying cause of impact.
Scope of impact: This issue could affect users joining Microsoft Teams meetings whose requests are routed through portions of Microsoft Teams infrastructure that have received the update. This information may be updated as our investigation continues.
Next update by: Sunday, January 11, 2026, at 10:00 AM UTC
Time:Sat Jan 10 20:21:01 2026
Description:Title: Some users may have degraded video and screensharing quality in Microsoft Teams
User impact: Users may have degraded video and screensharing quality in Microsoft Teams.
More info: Affected users may be able to resolve the quality issues by leaving and rejoining the meeting.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

DZ1222472 - Some users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR

Status:serviceRestored
Start Time:Mon Jan 26 04:30:00 2026
End Time:Mon Jan 26 10:00:00 2026
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Mon Jan 26 11:21:34 2026
Root Cause:An update for a dependent service caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds.
Next Update:N/A

Details

Time:Mon Jan 26 11:21:34 2026
Description:Title: Some users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR
User impact: Users may have seen a delay of up to five hours for alerts and incidents in Microsoft Defender XDR.
Final status: After our processing of the backlogged alerts and incidents, our internal service telemetry validates that the impact has been remediated.
Scope of impact: This issue may have impacted some users within your organization that were accessing the service from West and North Europe.
Start time: Monday, January 26, 2026, at 9:30 AM UTC
End time: Monday, January 26, 2026, at 3:00 PM UTC
Root cause: An update for a dependent service caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds.
Next steps: - We're further analyzing the offending dependent service update along with the affected subset of service infrastructure to help us improve our pre-deployment testing and validations.
This is the final update for the event.
Time:Mon Jan 26 09:59:45 2026
Description:Title: Some users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR
User impact: Users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR.
Current status: While we continue processing the backlogged alerts and incidents, we’ve identified some residual performance issues and are actively working to restore performance across the affected infrastructure.
Scope of impact: This issue may impact some users within your organization that are accessing the service from the affected region(s): West and North Europe.
Start time: Monday, January 26, 2026, at 9:30 AM UTC
Root cause: An update for a dependent service inadvertently caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds.
Next update by: Monday, January 26, 2026, at 6:30 PM UTC
Time:Mon Jan 26 08:06:01 2026
Description:Title: Some users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR
User impact: Users may see a delay of up to five hours for alerts and incidents in Microsoft Defender XDR.
Current status: We've identified that an update for a dependent service inadvertently caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds and resulted in impact. We've confirmed that the update has completed and the section of infrastructure performance has recovered. We're now processing the backlogged alerts and incidents to fully restore the service.
Scope of impact: This issue may impact some users within your organization that are accessing the service from the affected region(s): West and North Europe.
Start time: Monday, January 26, 2026, at 9:30 AM UTC
Root cause: An update for a dependent service inadvertently caused a section of infrastructure that processes alerts and incidents to perform below acceptable performance thresholds.
Next update by: Monday, January 26, 2026, at 3:30 PM UTC

EX1221076 - Users may have been unable to delete email messages after running the QUIT command through the POP3 connection method

Status:serviceRestored
Start Time:Tue Jan 20 00:01:00 2026
End Time:Mon Jan 26 00:19:00 2026
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Mon Jan 26 03:47:56 2026
Root Cause:A package version conflict introduced a regression that caused the POP3 QUIT command to fail after a DELE operation.
Next Update:N/A

Details

Time:Mon Jan 26 03:47:56 2026
Description:Title: Users may have been unable to delete email messages after running the QUIT command through the POP3 connection method
User impact: Users may have been unable to delete email messages after running the QUIT command through the POP3 connection method.
More info: Specifically, POP3 users could read and download their email messages, but any messages they deleted may not have actually been removed, because the session failed to close properly. If a message was deleted on Exchange Online using the DELE command, the POP3 QUIT command may have failed, preventing the session from closing cleanly and caused messages marked for deletion to remain in the mailbox.
If the user was not using POP3, they were not impacted.
Final status: We’ve confirmed that the fix deployment has completed successfully and that the issue has been fully resolved.
Scope of impact: Impact was specific to some users attempting to delete email messages after running the QUIT command using POP3 connection method.
Start time: Tuesday, January 20, 2026, at 5:01 AM UTC
End time: Saturday, January 24, 2026, at 5:19 AM UTC
Root cause: A package version conflict introduced a regression that caused the POP3 QUIT command to fail after a DELE operation.
Next steps: - We're reviewing our package provisioning procedures to help prevent similar problems in the future.
This is the final update for the event.
Time:Fri Jan 23 04:13:56 2026
Description:Title: Users may be unable to delete email messages after running the QUIT command when POP3 connection method is used
User impact: Users may be unable to delete email messages after running the QUIT command when POP3 connection method is used.
More info: Specifically, POP3 users can read and download their email messages, but any messages they delete may not actually be removed, because the session fails to close properly. If a message is deleted on Exchange Online using the DELE command, the POP3 QUIT command may fail, preventing the session from closing cleanly and causing messages marked for deletion to remain in the mailbox.
If the user is not using POP3, they are not impacted.
Current status: We’ve begun rolling out the fix and can confirm it has been successfully deployed to approximately 56% of the affected environments. We’ll continue monitoring progress and will provide an updated completion timeline as soon as it’s available.
Scope of impact: Impact is specific to some users attempting to delete email messages after running the QUIT command using POP3 connection method.
Root cause: A package version conflict introduced a regression that causes the POP3 QUIT command to fail after a DELE operation.
Next update by: Monday, January 26, 2026, at 11:00 AM UTC
Time:Thu Jan 22 06:59:05 2026
Description:Title: Users may be unable to delete email messages after running the QUIT command when POP3 connection method is used
User impact: Users may be unable to delete email messages after running the QUIT command when POP3 connection method is used.
More info: Specifically, POP3 users can read and download their email messages, but any messages they delete may not actually be removed, because the session fails to close properly. If a message is deleted on Exchange Online using the DELE command, the POP3 QUIT command may fail, preventing the session from closing cleanly and causing messages marked for deletion to remain in the mailbox.
If the user is not using POP3, they are not impacted.
Current status: We’ve identified an issue where a recent update introduced a conflict that prevents the POP3 QUIT command from completing after a message is deleted. We've validated a fix in our test environment and initiated a deployment to affected users. The deployment is progressing through a gradual rollout and we expect full completion within the next 24 to 48 hours.
Scope of impact: Impact is specific to some users attempting to delete email messages after running the QUIT command using POP3 connection method.
Root cause: A package version conflict introduced a regression that causes the POP3 QUIT command to fail after a DELE operation.
Next update by: Friday, January 23, 2026, at 10:00 AM UTC

SP1220310 - Some users that are mentioned in list comments in SharePoint Online may not receive email notifications

Status:serviceRestored
Start Time:Thu Jan 8 07:24:00 2026
End Time:Fri Jan 23 20:07:00 2026
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Fri Jan 23 20:27:03 2026
Root Cause:A recent service change to remove a separate feature introduced a regression within SharePoint Online email notifications, which resulted in impact.
Next Update:N/A

Details

Time:Fri Jan 23 20:27:03 2026
Description:Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that were mentioned in list comments in SharePoint Online may have not received email notifications.
Final status: Our reversion of the offending change has completed its saturation process throughout the affected environment, and we’ve confirmed through an extended period of monitoring the service health telemetry that impact has been remediated.
Scope of impact: Impact was specific to some users that were mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
End time: Saturday, January 24, 2026, at 1:07 AM UTC
Root cause: A recent service change to remove a separate feature introduced a regression within SharePoint Online email notifications, which resulted in impact.
Next steps: - We’re continuing to analyze how the service change was partially applied to understand why the potential for impact wasn't caught during the update testing and validation phase. These actions will help us to clarify what actions we can take to ensure similar impact doesn't occur in future and to continue our ongoing mission to improve the resilience of our service for all SharePoint Online users.
This is the final update for the event.
Time:Fri Jan 23 11:52:10 2026
Description:Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We’re continuing to monitor progress of our fix to reverse the offending change, where it's saturated across 90 percent of the affected infrastructure. We estimate that this saturation will complete by our next communications update, after which we'll perform final testing with a subset of affected users to validate remediation.
Scope of impact: Impact is specific to some users that are mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
Root cause: A recent service change to remove a separate feature introduced a regression within SharePoint Online email notifications, resulting in impact.
Next update by: Saturday, January 24, 2026, at 3:00 AM UTC
Time:Thu Jan 22 13:00:29 2026
Description:Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We’re continuing to monitor progress of the fix to reverse the offending change and will provide a resolution timeline once available.
Scope of impact: Impact is specific to some users that are mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
Root cause: A recent service change to remove a separate feature is causing impact.
Next update by: Friday, January 23, 2026, at 6:30 PM UTC
Time:Wed Jan 21 13:49:25 2026
Description:Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We're continuing to reverse the offending change and will provide a timeline for the completion of this reversal as one becomes available.
Scope of impact: Impact is specific to some users that are mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
Root cause: A recent service change to remove a separate feature is causing impact.
Next update by: Thursday, January 22, 2026, at 7:00 PM UTC
Time:Wed Jan 21 12:22:01 2026
Description:Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We've identified a recent service change to remove a separate feature is causing impact. While we investigate the reason the change caused impact, we're reversing the offending change to remediate the impact.
Scope of impact: Impact is specific to some users that are mentioned in list comments in SharePoint Online.
Start time: Thursday, January 8, 2026, at 12:24 PM UTC
Root cause: A recent service change to remove a separate feature is causing impact.
Next update by: Wednesday, January 21, 2026, at 7:30 PM UTC
Time:Wed Jan 21 10:24:54 2026
Description:Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We’ve identified a potential update that may be causing impact to occur. We're analyzing the update code path to confirm the update is the root cause of impact.
Scope of impact: Impact is specific some users that are mentioned in list comments in SharePoint Online.
Next update by: Wednesday, January 21, 2026, at 5:30 PM UTC
Time:Wed Jan 21 08:20:22 2026
Description:Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications.
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We’re reviewing any recent changes to the service that may be causing impact to occur.
Scope of impact: Impact is specific some users that are mentioned in list comments in SharePoint Online.
Next update by: Wednesday, January 21, 2026, at 3:30 PM UTC
Time:Wed Jan 21 06:18:23 2026
Description:Title: Some users that are mentioned in list comments in SharePoint Online may not receive email notifications
User impact: Users that are mentioned in list comments in SharePoint Online may not receive email notifications.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Impact is specific some users that are mentioned in list comments in SharePoint Online.
Next update by: Wednesday, January 21, 2026, at 1:30 PM UTC

EX1221742 - Some users may be intermittently unable to access the Exchange Online service through multiple connection methods

Status:serviceRestored
Start Time:Fri Jan 23 02:00:00 2026
End Time:Fri Jan 23 19:00:00 2026
Service:Exchange Online
Feature Group:Sign-in
Classification:incident
Last Updated:Fri Jan 23 20:19:15 2026
Root Cause:A recent code regression was causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next Update:N/A

Details

Time:Fri Jan 23 20:18:53 2026
Description:Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may have been intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacted the following connection methods:
- Outlook on the web - Outlook mobile app - Outlook on Mac devices
Final status: After monitoring the service recovery progress, we've confirmed that the service availability has reached expected levels and impact is remediated.
Scope of impact: This issue may have impacted any user based in Australia, Brazil, Canada, Europe/Middle East/Africa, France, Mexico, The United States, Norway, South America, Sweden, and the United Kingdom regions.
Start time: Friday, January 23, 2026, 7:00 AM UTC
End time: Saturday, January 24, 2026, at 12:00 AM UTC
Root cause: A recent code regression was causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next steps: - We're investigating further into the recent code regression to better understand why it caused the inability to access Exchange Online and why impact was caught sooner so that we can proactively identify similar issues in the future.
This is the final update for the event.
Time:Fri Jan 23 18:31:07 2026
Description:Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them: - Outlook on the web - Outlook mobile app - Outlook on Mac devices
Current status: The ongoing service recovery progress shows availability is slowly approaching expected levels, and we're continuing to monitor, ensuring this trend continues and the impact is remediated in a timely manner.
Scope of impact: This issue may impact any user based in Australia, Brazil, Canada, Europe/Middle East/Africa, France, Mexico, The United States, Norway, South America, Sweden, and the United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Saturday, January 24, 2026, at 1:30 AM UTC
Time:Fri Jan 23 16:19:27 2026
Description:Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them:
- Outlook on the web - Outlook mobile app - Outlook on Mac devices
Current status: While we monitor service health broadly as availability recovers, we're also analyzing and comparing recovering sections of infrastructure to ensure improvement continues to progress and no additional measures are necessary for remediation.
Scope of impact: This issue may impact any user based in the United States, France, Canada, and United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Friday, January 23, 2026, at 11:30 PM UTC
Time:Fri Jan 23 15:49:36 2026
Description:Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them:
- Outlook on the web - Outlook mobile app - Outlook on Mac devices
Current status: We've completed applying the additional configuration change to the affected infrastructure, and we're continuing to monitor as availability slowly recovers. In parallel, we're assessing whether there are any further actions needed to fully resolve the issue.
Scope of impact: This issue may impact any user based in the United States, France, and United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Friday, January 23, 2026, at 11:00 PM UTC
Time:Fri Jan 23 13:57:31 2026
Description:Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them:
- Outlook on the web - Outlook mobile app - Outlook on Mac devices
Current status: While our initial mitigating action of rolling back the problematic change has provided some relief and prevented further impact from occurring, we're applying an additional configuration change to affected portions of infrastructures to address an outdated Dynamic-link library (DLL) which is being incorrectly referenced by the service as a result of the regression and is continuing to cause crashes.
Scope of impact: This issue may impact any user based in the United States, France, and United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Friday, January 23, 2026, at 9:00 PM UTC
Time:Fri Jan 23 11:36:42 2026
Description:Title: Some users may be intermittently unable to access the Exchange Online service through multiple connection methods
User impact: Users may be intermittently unable to access the Exchange Online service through multiple connection methods.
More info: This issue impacts the following connection methods, although impact may not be limited to them:
- Outlook on the web - Outlook mobile app - Outlook on Mac devices
Current status: While we're observing some recovery after rolling back the impacting change, we're exploring options to expedite the resolution.
Scope of impact: This issue may impact any user based in the United States, France, and United Kingdom regions. This information may be updated as our investigation continues.
Root cause: A recent code regression is causing crashes on a portion of mailbox infrastructure that handles access requests from Outlook on the web, New Outlook, Outlook for Mac, and mobile apps.
Next update by: Friday, January 23, 2026, at 7:00 PM UTC
Time:Fri Jan 23 09:29:50 2026
Description:Title: Users may experience errors when accessing or loading Exchange Online via one or more clients or connection methods
User impact: Users may experience errors when accessing or loading Exchange Online via one or more clients or connection methods.
More info: The following impacted clients and connection methods include but aren't limited to:
- Outlook on the web - Outlook mobile app - Outlook on MAC devices
Current status: We’ve identified that a recent code regression in the Exchange Online service is causing unexpected errors and service instability in Outlook on the web, New Outlook, Mac and Mobile clients. The issue is linked to backported updates that affected Information Protection features, leading to increased crashes within the affected infrastructure. We've initiated a rollback of the affected changes and we’re continuing to monitor performance across all environments to ensure full recovery.
Scope of impact: This issue may impact any user within your organization served via the affected region(s): United States, France and United Kingdom. This information may be updated as our investigation continues.
Root cause: A recent code regression introduced changes in Exchange Online service resulting in impact. This regression is causing crashes on some of the affected mailbox infrastructure affecting Outlook on the web, New Outlook, Mac and Mobile clients.
Next update by: Friday, January 23, 2026, at 4:30 PM UTC
Time:Fri Jan 23 07:20:18 2026
Description:Title: Some users may be unable to access or load Outlook on the web
User impact: Users may be unable to access or load Outlook on the web.
Current status: We’ve completed a rollback of recent changes and restored the service to a stable configuration. Our monitoring shows that availability is improving across affected regions, but some environments are still experiencing issues. Additionally, we've identified an update that caused unexpected behavior and are working on a fix to deploy once fully validated.
Scope of impact: This issue may impact any user within your organization served via the affected region(s): United States, France and United Kingdom. This information may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 2:30 PM UTC
Time:Fri Jan 23 05:32:37 2026
Description:Title: Some users may be unable to access or load Outlook on the web
User impact: Users may be unable to access or load Outlook on the web.
Current status: We've received reports that users may be unable to access or load Outlook on the web, and we're reviewing service monitoring telemetry to understand the scope of impact.
Scope of impact: This issue may impact any user within your organization served via the affected region(s): United States, France and United Kingdom. This information may be updated as our investigation continues.
Next update by: Friday, January 23, 2026, at 12:30 PM UTC

CW1221869 - Some users may not receive Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response

Status:serviceRestored
Start Time:Fri Jan 23 13:42:00 2026
End Time:Fri Jan 23 14:36:00 2026
Service:Microsoft 365 Copilot Chat
Feature Group:Microsoft 365 Copilot Chat
Classification:incident
Last Updated:Fri Jan 23 16:21:44 2026
Root Cause:A recent deployment introduced a request routing misconfiguration for Copilot Chat response traffic, resulting in impact.
Next Update:N/A

Details

Time:Fri Jan 23 15:42:30 2026
Description:Title: Some users may not receive Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response
User impact: Users may not have received Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response.
Final status: A recent deployment introduced a request routing misconfiguration for Copilot Chat response traffic, resulting in impact. We've corrected the configuration while our automated recovery system directed affected traffic to infrastructure where the request routing configuration wasn't impacted to remediate impact. We confirmed that service was restored by these actions after monitoring the environment.
Scope of impact: Users may have experienced latency or not received responses while using Microsoft Copilot Chat GPT 5.2 Quick response
Start time: Friday, January 23, 2026, at 6:42 PM UTC
End time: Friday, January 23, 2026, at 7:36 PM UTC
Root cause: A recent deployment introduced a request routing misconfiguration for Copilot Chat response traffic, resulting in impact.
Next steps: - We're reviewing our update testing and validation process to better identify routing and network issues prior to deployment and avoid issue like this moving forward.
This is the final update for the event.
Time:Fri Jan 23 14:58:20 2026
Description:Title: Some users may not receive Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response
User impact: Users may not receive Microsoft Copilot Chat responses or experience latency using GPT 5.2 Quick response.
Current status: We're investigating a potential issue with Microsoft Copilot Chat and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1220516 - Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices

Status:serviceRestored
Start Time:Tue Jan 20 18:00:00 2026
End Time:Fri Jan 23 12:13:00 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Fri Jan 23 14:39:34 2026
Root Cause:The latest Outlook for iOS update contained a code error related to a change meant to refresh rather than restart tabs when feature flags were updated, which was resulting in this impact.
Next Update:N/A

Details

Time:Fri Jan 23 13:22:30 2026
Description:Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may have crashed or froze on iPad devices.
More info: Affected users could launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we worked towards mitigation.
Final status: We've confirmed with a subset of previously affected users that the latest version of the Outlook mobile app (5.2602.1) successfully resolves the issue. Users without automatic updates configured may need to manually update to this version through the App Store.
Scope of impact: This issue may have affected all users' iPad devices using Outlook for iOS version 5.2602.0.
Start time: Tuesday, January 20, 2026, at 11:00 PM UTC
End time: Thursday, January 22, 2026, at 5:13 PM UTC
Root cause: The latest Outlook for iOS update contained a code error related to a change meant to refresh rather than restart tabs when feature flags were updated, which was resulting in this impact.
Next steps: - We're reviewing our update testing and validation procedures to identify how impact was missed and better prevent similar future occurrences.
This is the final update for the event.
Time:Thu Jan 22 12:02:07 2026
Description:Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices.
More info: Affected users can launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we work towards mitigation.
Current status: We've completed the development of our fix to address the underlying issue, and we've provided the new version of the app to Apple who are going through their standard review and release processes. It can take up to 24 hours for the new iOS Outlook app version to appear in the App Store. We recommend users periodically check within the App Store for version 5.2602.1 and update to receive the fix.
Scope of impact: This issue may affect all users' iPad devices using Outlook for iOS version 5.2602.0. This information may be updated as our investigation continues.
Start time: Tuesday, January 20, 2026, at 11:00 PM UTC
Root cause: The latest Outlook for iOS update contains a code error related to a change meant to refresh rather than restart tabs when feature flags are updated, which is resulting in this impact.
Next update by: Friday, January 23, 2026, at 8:00 PM UTC
Time:Wed Jan 21 17:51:06 2026
Description:Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices.
More info: Affected users can launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we work towards mitigation.
Current status: We determined that the latest Outlook for iOS update contains a code error related to a change meant to refresh rather than restart tabs when feature flags are updated, which is resulting in this impact. We’ve developed a code solution for the next update to address this issue, which we intend to roll out to iOS tomorrow. We’ll provide further updates on this timeline as soon as they become available.
Scope of impact: This issue may affect all users' iPad devices using Outlook for iOS version 5.2602.0. This information may be updated as our investigation continues.
Start time: Tuesday, January 20, 2026, at 11:00 PM UTC
Root cause: The latest Outlook for iOS update contains a code error related to a change meant to refresh rather than restart tabs when feature flags are updated, which is resulting in this impact.
Next update by: Thursday, January 22, 2026, at 8:00 PM UTC
Time:Wed Jan 21 12:56:40 2026
Description:Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices.
More info: Affected users can launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we work towards mitigation.
Current status: We've successfully reproduced impact in our internal testing environment. We're analyzing this reproduction of impact to determine if a regression was introduced in the latest Outlook for iOS version to better understand how impact manifests and determine next steps for remediation.
Scope of impact: This issue may affect all users' iPad devices using Outlook for iOS version 5.2602.0. This information may be updated as our investigation continues.
Next update by: Thursday, January 22, 2026, at 12:00 AM UTC
Time:Wed Jan 21 12:50:50 2026
Description:Title: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices
User impact: Users' Outlook for iOS app version 5.2602.0 may crash or freeze on iPad devices.
More info: Affected users can launch Outlook mobile while in Airplane Mode and then re-enable Wi-Fi and/or cellular data as a way to circumvent impact while we work towards mitigation.
Current status: We're investigating a potential issue with Outlook mobile and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1221222 - Users can't access the Threat Analytics page in Microsoft Defender XDR portal

Status:serviceRestored
Start Time:Thu Jan 22 07:08:00 2026
End Time:Thu Jan 22 09:50:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Thu Jan 22 12:02:33 2026
Root Cause:An improperly configured infrastructure update prevented users from having the necessary permissions to access the Threat Analytics page in the Microsoft Defender XDR portal.
Next Update:N/A

Details

Time:Thu Jan 22 12:02:33 2026
Description:Title: Users can't access the Threat Analytics page in Microsoft Defender XDR portal
User impact: Users couldn't access the Threat Analytics page in Microsoft Defender XDR portal.
Final status: We've determined that an improperly configured infrastructure update prevented users from having the necessary permissions to access the Threat Analytics page in the Microsoft Defender XDR portal. We reverted this change and confirmed using our internal telemetry that impact is remediated.
Scope of impact: Any user attempting to access the Threat Analytics page in the Microsoft Defender XDR portal may have been impacted.
Start time: Thursday, January 22, 2026, at 12:08 PM UTC
End time: Thursday, January 22, 2026, at 2:50 PM UTC
Root cause: An improperly configured infrastructure update prevented users from having the necessary permissions to access the Threat Analytics page in the Microsoft Defender XDR portal.
Next steps: - We're reviewing and improving our infrastructure update validation procedure to detect and prevent similar misconfigurations in the future.
This is the final update for the event.
Time:Thu Jan 22 11:17:15 2026
Description:Title: Users may be unable to access the Threat Analytics page in the Microsoft Defender XDR portal
User impact: Users may have been unable to access the Threat Analytics page in the Microsoft Defender XDR portal.
Current status: We've investigated a problem in which users couldn't access the Threat Analytics page in Microsoft Defender XDR portal and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.

MO1220544 - Users' Microsoft Power Automate flows may not trigger when users create, update, or delete shifts in Microsoft Teams

Status:serviceRestored
Start Time:Tue Jan 20 21:30:00 2026
End Time:Wed Jan 21 15:08:00 2026
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Wed Jan 21 15:19:45 2026
Root Cause:Our recent efforts to redirect request traffic to alternate portions of infrastructure responsible for facilitating Microsoft Power Automate flows triggered by Microsoft Teams shifts caused the impact.
Next Update:N/A

Details

Time:Wed Jan 21 15:19:45 2026
Description:Title: Users' Microsoft Power Automate flows may not trigger when users create, update, or delete shifts in Microsoft Teams
User impact: Users' Microsoft Power Automate flows may not have triggered when users created, updated, or deleted shifts.
More info: Flows that were configured with "When a Shift was created, updated or deleted" may have failed to trigger when users performed the actions in Microsoft Teams.
Final status: We've identified that our recent efforts to redirect request traffic to alternate portions of infrastructure, responsible for facilitating Microsoft Power Automate flows triggered by Microsoft Teams shifts, caused the impact. We've reversed the change by directing the traffic back to its original infrastructure and confirmed through internal testing that the impact is remediated.
Scope of impact: Any user that attempted to create, update, or delete shifts in Microsoft Teams and had a Microsoft Power Automate flow configured with "When a Shift was created, updated or deleted" may have been impacted.
Start time: Wednesday, January 21, 2026, at 2:30 AM UTC
End time: Wednesday, January 21, 2026, at 8:08 PM UTC
Root cause: Our recent efforts to redirect request traffic to alternate portions of infrastructure responsible for facilitating Microsoft Power Automate flows triggered by Microsoft Teams shifts caused the impact.
Next steps: - We're continuing to review the affected infrastructure to identify the reason it caused impact, so that we can prevent similar impacts from occurring in the future.
This is the final update for the event.
Time:Wed Jan 21 14:48:10 2026
Description:Title: Users' Microsoft Power Automate flows may not trigger when users create, update, or delete shifts in Microsoft Teams
User impact: Users' Microsoft Power Automate flows may not trigger when users create, update, or delete shifts in Microsoft Teams.
More info: Flows that are configured with "When a Shift is created, updated or deleted" may fail to trigger when users perform the actions in Microsoft Teams.
Current status: We're reproducing the impact in our testing environment to gain clarity on the issue and determine our next steps to isolate the root cause.
Scope of impact: Any user attempting to create, update, or delete shifts in Microsoft Teams and has a Microsoft Power Automate flow configured with "When a Shift is created, updated or deleted" may be impacted.
Next update by: Wednesday, January 21, 2026, at 9:00 PM UTC
Time:Wed Jan 21 14:23:34 2026
Description:Title: Users' Microsoft Power Automate flows aren't triggered when users create, update, or delete shifts in Microsoft Teams
User impact: Users' Microsoft Power Automate flows aren't triggered when users create, update, or delete shifts in Microsoft Teams.
More info: Flows that are configured with "When a Shift is created, updated or deleted" fail to trigger when users perform the actions in Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and Microsoft Power Automate and checking for impact to your organization. We'll provide an update within 30 minutes.

OD1177143 - Some users with edit and full control permissions may be unable to access or share some files in Microsoft OneDrive

Status:serviceDegradation
Start Time:Mon Oct 13 11:50:00 2025
End Time:N/A
Service:Microsoft OneDrive
Feature Group:OneDrive for Business
Classification:advisory
Last Updated:Wed Jan 21 14:01:34 2026
Root Cause:A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next Update:Wednesday, February 4, 2026, at 8:00 PM UTC

Details

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.

SP1177145 - Some users with edit and full control permissions may be unable to access or share some items in SharePoint Online

Status:serviceDegradation
Start Time:Mon Oct 13 14:50:00 2025
End Time:N/A
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Wed Jan 21 14:01:08 2026
Root Cause:A recent deployment contains a code regression that introduced a compatibility issue between code that's preventing items that have been deleted and recently restored from being accessible again.
Next Update:Wednesday, February 4, 2026, at 8:00 PM UTC

Details

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.

MO1220495 - Users may be unable to access Microsoft 365 services

Status:serviceRestored
Start Time:Wed Jan 21 11:45:09 2026
End Time:Wed Jan 21 12:10:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Wed Jan 21 13:24:26 2026
Root Cause:A third-party ISP ASN routing configuration issue caused impact to downstream services, such as Microsoft 365.
Next Update:N/A

Details

Time:Wed Jan 21 13:24:26 2026
Description:Title: Users may be unable to access Microsoft 365 services
User impact: Users may have been unable to access Microsoft 365 services, including Teams and Outlook.
More info: As this issue was a result of a third-party ISP Autonomous System Number (ASN) routing configuration issue; the impact to Microsoft 365 services may have manifested in a multitude of ways. For example, some users may have been unable to access the services and portals altogether, whereas others may have seen impact more variable, such being intermittently unable to send or receive email.
Final status: We've determined this issue was a result of a third-party ISP Autonomous System Number (ASN) routing configuration issue, and we've identified that the third-party has taken action to remediate the impact to downstream services, such as Microsoft 365, and we've confirmed the issue is no longer occurring.
Scope of impact: Your organization was affected by this event, and any of your users hosted in North America may have been impacted.
Start time: Wednesday, January 21, 2026, at 4:10 PM UTC
End time: Wednesday, January 21, 2026, at 5:10 PM UTC
Root cause: A third-party ISP ASN routing configuration issue caused impact to downstream services, such as Microsoft 365.
Next steps: - We're carefully monitoring our managed service environment to ensure the issue doesn't reoccur, and we're reviewing our service resilience practices to identify any necessary improvements so we can reduce the downtime associated with these types of ISP-dependent issues in the future.
This is the final update for the event.
Time:Wed Jan 21 12:36:47 2026
Description:Title: Users may be unable to access Microsoft 365 services
User impact: Users may be unable to access Microsoft 365 services, including Teams and Outlook.
Current status: Our investigation so far indicates impact is associated with a possible third-party networking issue. We're recursively investigating the health of the Microsoft-managed service environment to identify whether any mitigation actions are required and ensure our services are healthy.
Scope of impact: Your organization is affected by this event, and any of your users hosted in North America may be impacted.
Next update by: Wednesday, January 21, 2026, at 7:00 PM UTC
Time:Wed Jan 21 12:15:37 2026
Description:As the primary reports of impact are originating from users hosted in North America, we're reviewing networking health across the region to help us determine whether there are any connectivity issues affecting the Microsoft-managed service environment.
This quick update is designed to give the latest information on this issue.
Time:Wed Jan 21 12:07:08 2026
Description:Title: We're investigating a potential issue affecting Microsoft 365 services
User impact: We've received reports of an issue affecting Microsoft 365 services, including Teams and Outlook.
Current status: We're reviewing telemetry across dependent portions of service infrastructure to help us isolate the nature of the impact, the source of the issue, and determine what recovery actions may be required.
Scope of impact: The scope of this issue is currently being investigated.
Next update by: Wednesday, January 21, 2026, at 6:00 PM UTC
Time:Wed Jan 21 11:51:14 2026
Description:Title: We're investigating a potential issue affecting Microsoft 365 services
User impact: We've received reports of an issue affecting Microsoft 365 services, including Teams and Outlook.
Current status: We're investigating a potential issue with Microsoft 365 services and checking for impact to your organization. We'll provide an update within 30 minutes.

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 Jan 20 21:07:46 2026
Root Cause:The impact is the result of an issue affecting the authentication components assigned to guest users when joining recurring Microsoft Teams meetings and recording the meeting in which stale components are being leveraged and causing an error to occur that prevents these guest users from unmuting their mics, sharing their screen, or using their camera.
Next Update:Wednesday, February 4, 2026, at 3:30 AM UTC

Details

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

MV1097445 - Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page

Status:serviceDegradation
Start Time:Mon Feb 5 21:11:00 2024
End Time:N/A
Service:Microsoft Viva
Feature Group:Viva Engage
Classification:advisory
Last Updated:Tue Jan 20 20:58:17 2026
Root Cause:A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next Update:Wednesday, February 4, 2026, at 3:00 AM UTC

Details

Time:Tue Jan 20 20:49:14 2026
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: During our process of initiating the deployment of the fix, we've identified an additional change to the code is needed in order to ensure it will successfully remediate impact without adversely impacting other aspects of the service. We've halted the deployment and are implementing the necessary change before proceeding with the deployment of the code fix. We expect the saturation will be complete, and the impact remediated by our next scheduled update.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, February 4, 2026, at 3:00 AM UTC
Time:Mon Jan 12 20:54:45 2026
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature. To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We've tested and validated that our code solution has successfully resolved the issue in our testing environment. We're now progressing with a full deployment of the fix which we anticipate will complete by our next scheduled update.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, January 21, 2026, at 3:00 AM UTC
Time:Tue Dec 23 19:06:20 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature. To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: Due to the complexity of the fix, additional testing is required before we're ready to start deploying the code solution to address the conflict between the two SharePoint Online web parts. We now anticipate that the deployment will begin by our next scheduled communications update.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Tuesday, January 13, 2026, at 3:00 AM UTC
Time:Tue Dec 9 20:44:31 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: Our development of the code solution that we anticipate will address the conflict between the two SharePoint web parts which render on the same page, is ongoing. We're in the initial evaluation and development stages and we expect that we'll begin deployment of the full fix by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, December 24, 2025, at 3:00 AM UTC
Time:Tue Nov 25 21:32:31 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to complete the fix for this issue and prepare it for deployment. We're still aiming to have the issue fully remediated by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, December 10, 2025, at 3:00 AM UTC
Time:Mon Nov 10 20:57:44 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature. To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: Work on the fix is continuing though progress is slow due to the complexity of the issue. We anticipate that deployment of the fix will start in December 2025 and complete by the end of the calendar year. We'll provide updates on the timeline and ETA as they become available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, November 26, 2025, at 3:00 AM UTC
Time:Tue Oct 28 21:01:53 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature. To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The development of the fix is ongoing, and due to the complexity of the issue, we're still anticipating deployment will start in December 2025. We'll provided an updated timeline and ETA once one becomes available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, November 12, 2025, at 3:00 AM UTC
Time:Tue Oct 14 20:20:21 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to develop the fix and still anticipate the fix, and a deployment timeline will be provided by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, October 29, 2025, at 2:00 AM UTC
Time:Tue Sep 30 20:40:02 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The development of the fix is taking longer than previously anticipated. We now anticipate that the fix will be completed, and a deployment timeline will be provided by the end of December 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, October 15, 2025, at 2:00 AM UTC
Time:Tue Sep 16 21:27:28 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The development of the fix is nearly completed. Once development is complete, which we anticipate will be in October 2025, we'll aim to provide a deployment timeline.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, October 1, 2025, at 2:00 AM UTC
Time:Tue Sep 2 20:38:12 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to progress in our development of the fix. Once development is complete, which we anticipate will be in October 2025, we'll aim to provide a deployment timeline.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, September 17, 2025, at 2:00 AM UTC
Time:Tue Aug 12 21:05:16 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to prepare the fix, which we still anticipate will be ready for deployment by early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, September 3, 2025, at 2:00 AM UTC
Time:Tue Jul 29 20:26:29 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: The preparation of the fix deployment is ongoing. We're still projecting that the full release of the fix will complete around early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, August 13, 2025, at 2:00 AM UTC
Time:Tue Jul 15 20:24:52 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing to prepare our fix for deployment. We're currently projecting its full release may complete around early October 2025.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Start time: Thursday, February 6, 2025, at 2:11 PM UTC
Root cause: A conflict between two SharePoint web parts which render on the same page is resulting in impact.
Next update by: Wednesday, July 30, 2025, at 2:00 AM UTC
Time:Tue Jul 1 20:30:42 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We're continuing our efforts to develop a code fix for the conflicting SharePoint web parts. We anticipate that the fix and subsequent deployment will take an extended time to complete. We'll provide updates on the status as they become available.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Root cause: A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact.
Next update by: Wednesday, July 16, 2025, at 2:00 AM UTC
Time:Tue Jun 17 22:53:13 2025
Description:Title: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page
User impact: Users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page.
More info: The error may occur specifically when using the “Promote to Viva Engage” feature.
To circumvent impact while the fix is in progress, users can copy the SharePoint page URL and start the post directly within Viva Engage.
Current status: We've identified an issue where users may encounter errors when attempting to create a post in Microsoft Viva Engage directly from a SharePoint page, and we've determined this issue stems from a conflict between two SharePoint web parts which render on the same page. Due to the complexity of their interaction, a code-level resolution is required to ensure that impact is fully alleviated. We're working to develop this solution and will provide updates as its development progresses.
Scope of impact: Users attempting to use the “Promote to Viva Engage” feature through a SharePoint Page may encounter errors in their endeavor to do so.
Root cause: A conflict resulting from two SharePoint web parts which render on the same page, is resulting in impact.
Next update by: Wednesday, July 2, 2025, at 2:00 AM UTC

MF1219609 - Some users may have been unable to run Microsoft Power Automate flows

Status:serviceRestored
Start Time:Tue Jan 20 05:41:00 2026
End Time:Tue Jan 20 07:33:00 2026
Service:Microsoft Power Automate in Microsoft 365
Feature Group:Service and web access issues
Classification:advisory
Last Updated:Tue Jan 20 09:51:36 2026
Root Cause:An update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services.
Next Update:N/A

Details

Time:Tue Jan 20 09:29:19 2026
Description:Title: Some users may have been unable to run Microsoft Power Automate flows
User impact: Users may have been unable to run Microsoft Power Automate flows.
More info: Users may have been unable to run flows, use connectors, or perform operations that rely on Power Automate services.
Final status: We’ve determined that an update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services. We’ve confirmed that the service recovered after the aforementioned update completed as expected.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure attempting to run Microsoft Power Automate flows.
Start time: Tuesday, January 20, 2026, at 10:41 AM UTC
End time: Tuesday, January 20, 2026, at 12:33 PM UTC
Root cause: An update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services.
Next steps: - We're reviewing our Power Platform update procedures to help prevent similar impact from happening again.
This is the final update for the event.
Time:Tue Jan 20 07:40:02 2026
Description:Title: Some users may be unable to run Microsoft Power Automate flows
User impact: Users may be unable to run Microsoft Power Automate flows.
More info: Users may be unable to run flows, use connectors, or perform operations that rely on Power Automate services.
Current status: We’re analyzing service telemetry to identify the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to run Microsoft Power Automate flows.
Next update by: Tuesday, January 20, 2026, at 2:30 PM UTC

MM1219608 - Some users may have been unable to open Microsoft Power Apps

Status:serviceRestored
Start Time:Tue Jan 20 07:24:29 2026
End Time:Tue Jan 20 07:33:00 2026
Service:Power Apps in Microsoft 365
Feature Group:Service and web access issues
Classification:incident
Last Updated:Tue Jan 20 09:51:22 2026
Root Cause:An update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services.
Next Update:N/A

Details

Time:Tue Jan 20 09:27:33 2026
Description:Title: Some users may have been unable to open Microsoft Power Apps
User impact: Users may have been unable to open Microsoft Power Apps.
More info: Users may have been unable to open Power Apps, load data from SharePoint-backed applications, or use connectors that rely on Power Apps services.
Final status: We’ve determined that an update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services. We’ve confirmed that the service recovered after the aforementioned update completed as expected.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure attempting to open Power App
Start time: Tuesday, January 20, 2026, at 10:41 AM UTC
End time: Tuesday, January 20, 2026, at 12:33 PM UTC
Root cause: An update to the Power Platform service didn't run as expected, resulting in slow performance, connection failures, and request failures across dependent services.
Next steps: - We're reviewing our Power Platform update procedures to help prevent similar impact from happening again.
This is the final update for the event.
Time:Tue Jan 20 07:38:56 2026
Description:Title: Some users may be unable to open Microsoft Power Apps
User impact: Users may be unable to open Microsoft Power Apps.
More info: Users may be unable to open Power Apps, load data from SharePoint-backed applications, or use connectors that rely on Power Apps services.
Current status: We’re analyzing service telemetry to identify the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure attempting to open Power Apps.
Next update by: Tuesday, January 20, 2026, at 2:30 PM UTC

CP1219289 - Some users may have experienced errors and disruptions when starting or continuing chats in Microsoft Copilot

Status:serviceRestored
Start Time:Mon Jan 19 00:00:00 2026
End Time:Mon Jan 19 09:25:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Mon Jan 19 10:30:15 2026
Root Cause:A recent standard service update inadvertently contained a code regression, which was resulting in impact.
Next Update:Monday, January 19, 2026, at 4:00 PM UTC

Details

Time:Mon Jan 19 10:19:03 2026
Description:Title: Some users may have experienced errors and disruptions when starting or continuing chats in Microsoft Copilot
User impact: Users may have experienced errors and disruptions when starting or continuing chats in Microsoft Copilot.
More info: Affected users received error messages such as: "A problem has occurred", "Something went wrong," or that the service is unavailable.
Some users were also unable to publish agents created in Microsoft Copilot within Microsoft Teams.
Current status: We've reverted the offending change and confirmed that impact has been remediated.
Scope of impact: Impact was specific to some users attempting to utilize chats in Microsoft Copilot, or publish agents created in Microsoft Copilot within Microsoft Teams.
Start time: Monday, January 19, 2026, at 5:00 AM UTC
End time: Monday, January 19, 2026, at 2:25 PM UTC
Root cause: A recent standard service update inadvertently contained a code regression, which was resulting in impact.
Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Mon Jan 19 08:42:22 2026
Description:Title: Some users may experience errors and disruptions when starting or continuing chats in Microsoft Copilot
User impact: Users may experience errors and disruptions when starting or continuing chats in Microsoft Copilot.
More info: Affected users receive error messages such as: "A problem has occurred", "Something went wrong," or that the service is unavailable.
Current status: We've determined that a recent standard service update inadvertently contains a code regression, which is resulting in impact. We're reverting the offending change to remediate impact.
Scope of impact: Impact is specific to some users attempting to utilize chats in Microsoft Copilot.
Start time: Monday, January 19, 2026, at 5:00 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression, which is resulting in impact.
Next update by: Monday, January 19, 2026, at 4:00 PM UTC
Time:Mon Jan 19 06:40:46 2026
Description:Title: Some users may experience errors and disruptions when starting or continuing chats in Microsoft Copilot
User impact: Users may experience errors and disruptions when starting or continuing chats in Microsoft Copilot.
More info: Affected users receive error messages such as: "A problem has occurred", "Something went wrong," or that the service is unavailable.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users attempting to utilize chats in Microsoft Copilot.
Next update by: Monday, January 19, 2026, at 2:00 PM UTC

SP1218552 - Some users may be unable to select schedule dates within SharePoint Online pages

Status:serviceRestored
Start Time:Fri Jan 16 01:47:00 2026
End Time:Fri Jan 16 18:40:00 2026
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Fri Jan 16 19:24:10 2026
Root Cause:A regression was introduced during recent service update which was causing the date selector not to open, which resulted in impact.
Next Update:N/A

Details

Time:Fri Jan 16 19:19:05 2026
Description:Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Final status: Our fix has fully saturated throughout the affected environment and after an extended period of monitoring the service health telemetry and validating within our internal testing environment, we’ve confirmed that impact has been remediated.
Scope of impact: Some users who were attempting to select scheduled dates within SharePoint Online may have been impacted.
Start time: Thursday, January 15, 2026, at 6:47 AM UTC
End time: Friday, January 16, 2026, at 11:40 PM UTC
Root cause: A regression was introduced during recent service update which was causing the date selector not to open, which resulted in impact.
Next steps: - We're reviewing our update vetting procedures to help ensure impact of this nature doesn’t reoccur with future updates.
This is the final update for the event.
Time:Fri Jan 16 17:40:54 2026
Description:Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Current status: Our fix to correct the regression introduced by the recent service update is currently ten percent saturated across the affected environment and is progressing slower than we initially anticipated. We're monitoring as it deploys to ensure it completes in a timely manner.
Scope of impact: Some users attempting to select scheduled dates within SharePoint Online may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 15, 2026, at 6:47 AM UTC
Root cause: A regression was introduced during recent service update which is causing the date selector not to open, resulting in impact.
Next update by: Saturday, January 17, 2026, at 2:00 AM UTC
Time:Fri Jan 16 15:57:58 2026
Description:Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Current status: We’ve initiated the process of rolling out a fix to address this issue and anticipate that the deployment should complete to resolve this issue by our next scheduled update.
Scope of impact: Some users attempting to select scheduled dates within SharePoint Online may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, January 15, 2026, at 6:47 AM UTC
Root cause: A change introduced as part of a recent service update is causing impact.
Next update by: Saturday, January 17, 2026, at 12:00 AM UTC
Time:Fri Jan 16 07:16:05 2026
Description:Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Current status: We've determined that a recent service update is causing impact to occur. As a mitigation strategy, we've initiated the deployment of the fix which has reached an estimated 25 percent of the impacted service environments. We’ll provide a timeline for full completion as soon as it becomes available.
Scope of impact: Some users attempting to select scheduled dates within SharePoint Online may be impacted. This information may be updated as our investigation continues.
Root cause: A change introduced as part of a recent service update is causing impact.
Next update by: Friday, January 16, 2026, at 9:30 PM UTC
Time:Fri Jan 16 06:05:07 2026
Description:Title: Some users may be unable to select schedule dates within SharePoint Online pages
User impact: Users may be unable to select schedule dates within SharePoint Online pages.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and determine our next troubleshooting steps.
Scope of impact: Some users attempting to select scheduled dates within SharePoint Online may be impacted. This information may be updated as our investigation continues.
Next update by: Friday, January 16, 2026, at 1:00 PM UTC

DZ1189321 - Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11

Status:serviceDegradation
Start Time:Sun Nov 23 14:58:02 2025
End Time:N/A
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:advisory
Last Updated:Fri Jan 16 14:58:23 2026
Root Cause:A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next Update:Friday, February 20, 2026, at 7:00 PM UTC

Details

Time:Fri Jan 16 14:58:23 2026
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: While we’ve developed an additional fix for the localization issues, the complexity of delivering this solution is preventing an expedited resolution. We expect this process to take several weeks as we validate the subtasks involved in instituting the fix. We’ll provide updates on this process and a timeline for deployment once the subtask orchestration is complete.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, February 20, 2026, at 7:00 PM UTC
Time:Fri Jan 9 13:12:08 2026
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’re continuing to assess and validate alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 16, 2026, at 7:00 PM UTC
Time:Tue Jan 6 12:35:31 2026
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve identified that the previously developed code fix isn’t an effective solution for addressing the incorrect service names and descriptions. We’re assessing and validating alternative mitigation approaches and will provide an updated resolution timeline once available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Friday, January 9, 2026, at 7:00 PM UTC
Time:Tue Dec 9 12:44:40 2025
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: Validation of the code fix is continuing to progress, and due to the complex nature of the code developed to address the incorrect service names and descriptions, we're still expecting the deployment to complete by March 2026. We'll provide a more accurate timeline as one becomes available.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, January 6, 2026, at 7:00 PM UTC
Time:Mon Dec 8 03:18:26 2025
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We are continuing to validate the fix’s effectiveness and anticipate full deployment by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Tuesday, December 9, 2025, at 7:00 PM UTC
Time:Mon Nov 24 05:20:30 2025
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We’ve developed a code fix to address the issue. It’s currently undergoing validation to ensure effectiveness, and we expect the fix to be fully implemented and remediate impact by March 2026.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Start time: Tuesday, May 27, 2025, at 12:00 AM UTC
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, 8 December 2025, at 10:30 AM UTC
Time:Sun Nov 23 16:12:56 2025
Description:Title: Some users may see incorrect service names and descriptions in Services and the Event Viewer upon upgrade to Windows 11
User impact: Users may see incorrect service names and descriptions in Services and the Event Viewer after upgrading to Windows 11.
More info: This issue is only impacting users who have upgraded to Windows 11 during or after June of 2025.
User interface impact only:
- Service name for Windows Advanced Threat Protection (Sense) shows as “Sense” in English instead of the localized text.
- Users attempting to view service descriptions under Service may see the following error or descriptions appear in English: "Failed to Read Description. Error Code: 15100"
- Event Viewer logs for Sense may show error text instead of properly formatted localized descriptions.
No functional impact:
- Device telemetry and reporting to Microsoft Defender for Endpoint portal aren’t impacted.
- No portal unavailability, alert delays, or API failures.
Current status: We've identified a recent Windows update that is producing incorrect service names and descriptions in Services and the Event Viewer for some users who have upgraded to Windows 11 in or after June of 2025. As we work to confirm an accurate window of impact, we're developing a code fix to address the offending change and to remediate the impact. We'll provide an updated timeline for the deployment of our fix and the remediation of impact once our internal validations have completed.
Scope of impact: This issue is impacting a subset of users who have upgraded to Windows 11 in or after June of 2025.
Root cause: A standard Windows update may be producing localization issues including incorrect service names and descriptions in Services and the Event Viewer for users who have upgraded to Windows 11 in or after June of 2025.
Next update by: Monday, November 24, 2025, at 10:30 AM UTC

MF1218664 - Users intermittently can't perform HTTP actions in Microsoft Power Automate flows

Status:serviceRestored
Start Time:Tue Jan 13 14:08:00 2026
End Time:Fri Jan 16 12:48:00 2026
Service:Microsoft Power Automate in Microsoft 365
Feature Group:Service and web access issues
Classification:advisory
Last Updated:Fri Jan 16 14:35:00 2026
Root Cause:A portion of the service infrastructure supporting HTTP actions in Microsoft Power Automate flows entered an unhealthy state, resulting in impact.
Next Update:N/A

Details

Time:Fri Jan 16 14:35:00 2026
Description:Title: Users intermittently can't perform HTTP actions in Microsoft Power Automate flows
User impact: Users intermittently couldn't perform HTTP actions in Microsoft Power Automate flows.
Final status: We determined that a portion of the service infrastructure supporting HTTP actions in Microsoft Power Automate flows entered an unhealthy state, resulting in impact. We restarted the impacted infrastructure and, following a period of monitoring service health, we confirmed that functionality is restored.
Scope of impact: Your organization was affected by this event, and any user attempting to perform HTTP actions in Microsoft Power Automate flows was intermittently impacted.
Start time: Tuesday, January 13, 2026, at 7:08 PM UTC
End time: Friday, January 16, 2026, at 5:48 PM UTC
Root cause: A portion of the service infrastructure supporting HTTP actions in Microsoft Power Automate flows entered an unhealthy state, resulting in impact.
Next steps: - We're reviewing the affected service infrastructure to identify why it entered and unhealthy state, allowing us to implement early detection and automated mitigation processes that prevent future impact.
This is the final update for the event.
Time:Fri Jan 16 13:43:28 2026
Description:Title: Users intermittently can't perform HTTP actions in Microsoft Power Automate flows
User impact: Users intermittently can't perform HTTP actions in Microsoft Power Automate flows.
Current status: We've investigated a problem in which users intermittently couldn't perform HTTP actions in Microsoft Power Automate flows and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.

FL1218660 - HTTP actions in flows were intermittently failing

Status:serviceRestored
Start Time:Tue Jan 13 14:08:00 2026
End Time:Fri Jan 16 12:48:00 2026
Service:Microsoft Power Automate
Feature Group:Other
Classification:advisory
Last Updated:Fri Jan 16 13:29:05 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Fri Jan 16 13:29:05 2026
Description:Title: HTTP actions in flows were intermittently failing
User impact: HTTP actions in flows were intermittently failing.
Final Status: We determined that a portion of the node infrastructure supporting HTTP actions in flows entered an unhealthy state, leading to impact. To mitigate the issue, we restarted the impacted infrastructure and, following a period of monitoring service health, we confirmed that functionality is restored.
This is the final update on the incident.
Preliminary Root Cause: A portion of the node infrastructure supporting HTTP actions in flows entered an unhealthy state.
Next Steps: We're analyzing performance data and trends on the affected systems to prevent this problem from happening again.

SP1218404 - Users may be unable to open People Cards in SharePoint Online

Status:serviceRestored
Start Time:Wed Jan 14 13:47:00 2026
End Time:Thu Jan 15 23:00:00 2026
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Thu Jan 15 23:25:10 2026
Root Cause:Recent authorization changes intended to improve security functionality introduced an error that prevented users from opening People Cards.
Next Update:N/A

Details

Time:Thu Jan 15 23:25:10 2026
Description:Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may have been unable to open People Cards in SharePoint Online.
Final status: We confirmed that recent authorization changes intended to improve security functionality introduced an error that prevented users from opening People Cards. We reverted the authorization changes and confirmed in our telemetry that the impact is remediated.
Scope of impact: This issue may have potentially impacted any user attempting to open People Cards in SharePoint Online.
Start time: Wednesday, January 14, 2026, at 6:47 PM UTC
End time: Friday, January 16, 2026, at 4:00 AM UTC
Root cause: Recent authorization changes intended to improve security functionality introduced an error that prevented users from opening People Cards.
Next steps: - We're analyzing the authorization changes to better understand what triggered the initial impact, which will help us in avoiding similar issues during future updates.
This is the final update for the event.
Time:Thu Jan 15 22:56:42 2026
Description:Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may be unable to open People Cards in SharePoint Online.
Current status: Our initial testing shows that disabling the change is remediating impact in our test environment. We're evaluating that the change can be safely disabled for the remaining impacted environment before taking any additional mitigation steps.
Scope of impact: This issue may potentially impact any user attempting to open People Cards in SharePoint Online.
Next update by: Friday, January 16, 2026, at 6:00 AM UTC
Time:Thu Jan 15 20:56:25 2026
Description:Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may be unable to open People Cards in SharePoint Online.
Current status: We identified a recent authorization change that we suspect is causing the impact to People Cards. We're testing disabling the change in our environment to validate that it remediates impact.
Scope of impact: This issue may potentially impact any user attempting to open People Cards in SharePoint Online.
Next update by: Friday, January 16, 2026, at 4:00 AM UTC
Time:Thu Jan 15 19:16:18 2026
Description:Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may be unable to open People Cards in SharePoint Online.
Current status: We're analyzing system logs, including any recent changes, to identify the source of the issue, which will help us determine our next troubleshooting steps.
Scope of impact: This issue may potentially impact any user attempting to open People Cards in SharePoint Online.
Next update by: Friday, January 16, 2026, at 2:30 AM UTC
Time:Thu Jan 15 18:58:11 2026
Description:Title: Users may be unable to open People Cards in SharePoint Online
User impact: Users may be unable to open People Cards in SharePoint Online.
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1212913 - Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video

Status:serviceRestored
Start Time:Mon Dec 22 01:14:00 2025
End Time:Thu Jan 15 00:30:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu Jan 15 01:49:59 2026
Root Cause:A recent routine Microsoft Teams update contained a code issue, which led to higher battery and CPU usage in Microsoft Teams calls.
Next Update:N/A

Details

Time:Thu Jan 15 01:49:59 2026
Description:Title: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video
User impact: Users may have seen higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
More info: Microsoft Teams users on Windows may have seen higher battery and CPU usage when viewing a screenshare or video from other participants, which could have led to increased battery drain as more participants shared video. This issue only impacted the Microsoft Teams desktop client on Windows.
Final status: The deployment of the fix completed to the affected portion of infrastructure and we've confirmed in our telemetry that the impact is remediated.
Scope of impact: Any user may have been impacted by this event and may have seen higher battery and CPU usage in Microsoft Teams calls when participants screenshared or shared video.
Start time: Monday, December 22, 2025, at 6:14 AM UTC
End time: Thursday, January 15, 2026, at 5:30 AM UTC
Root cause: A recent routine Microsoft Teams update contained a code issue, which led to higher battery and CPU usage in Microsoft Teams calls.
Next steps: - We're reviewing our update procedures to develop better methods of detecting and preventing similar code issues from occurring in the future.
This is the final update for the event.
Time:Mon Jan 12 00:11:38 2026
Description:Title: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video
User impact: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
More info: Microsoft Teams users on Windows may see higher battery and CPU usage when viewing a screenshare or video from other participants, which can lead to increased battery drain as more participants share video. This issue only impacts the Microsoft Teams desktop client on Windows.
Current status: The deployment of the fix is still progressing. We're seeing progress as the fix nears completion in a portion of affected infrastructure. We anticipate the deployment will be completed by our next scheduled update and impact should be resolved.
Scope of impact: Any user may be impacted by this event and may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
Start time: Monday, December 22, 2025, at 6:14 AM UTC
Root cause: A recent routine Microsoft Teams update contained a code issue, leading to higher battery and CPU usage in Microsoft Teams calls.
Next update by: Friday, January 16, 2026, at 7:30 AM UTC
Time:Tue Jan 6 23:12:17 2026
Description:Title: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video
User impact: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
More info: Microsoft Teams users on Windows may see higher battery and CPU usage when viewing a screenshare or video from other participants, which can lead to increased battery drain as more participants share video. This issue only impacts the Microsoft Teams desktop client on Windows.
Current status: We've completed validation of the fix and have initiated its deployment. We're monitoring as it progresses and will provide a completion timeline when one becomes available.
Scope of impact: Any user may be impacted by this event and may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
Start time: Monday, December 22, 2025, at 6:14 AM UTC
Root cause: A recent routine Microsoft Teams update contained a code issue, leading to higher battery and CPU usage in Microsoft Teams calls.
Next update by: Monday, January 12, 2026, at 7:30 AM UTC
Time:Mon Jan 5 01:18:14 2026
Description:Title: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video
User impact: Users may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
More info: Microsoft Teams users on Windows may see higher battery and CPU usage when viewing a screenshare or video from other participants, which can lead to increased battery drain as more participants share video. This issue only impacts the Microsoft Teams desktop client on Windows.
Current status: We received reports of an issue with higher battery and CPU usage within Microsoft Teams calls. We analyzed service telemetry and recent service changes, which identified a routine update containing a code issue that led to increased battery and CPU usage during calls. We're validating a fix in our internal testing environments. Once validation is complete, we'll monitor progress and proceed with full deployment to the impacted environments.
Scope of impact: Any user may be impacted by this event and may see higher battery and CPU usage in Microsoft Teams calls when participants screenshare or share video.
Start time: Monday, December 22, 2025, at 6:14 AM UTC
Root cause: A recent routine Microsoft Teams update contained a code issue, leading to higher battery and CPU usage in Microsoft Teams calls.
Next update by: Wednesday, January 7, 2026, at 7:30 AM UTC

WP1217671 - Users experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions

Status:serviceRestored
Start Time:Tue Jan 13 19:11:00 2026
End Time:Wed Jan 14 06:41:00 2026
Service:Windows 365
Feature Group:End User
Classification:incident
Last Updated:Wed Jan 14 18:32:17 2026
Root Cause:A code misconfiguration in the recent January 2026 Windows security update (KB5074109) caused intermittent connection failures for Cloud PC, causing those access requests to fail. The issue affected Windows App on specific Windows builds, causing sign-in failures. For more information, refer to: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-25h2#3760msgdesc.
Next Update:N/A

Details

Time:Wed Jan 14 14:41:03 2026
Description:Title: Users experience intermittent failures and issues signing-in when connecting to Windows 365 Cloud PC sessions
User impact: Users may have experienced intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: To resolve this issue fully, users or admins will need to follow the Known Issue Rollback (KIR) instructions for resolving authentication errors and connection failures when connecting to Windows 365 Cloud PCs:
For enterprise-managed devices managed by IT departments that have installed the affected update and encountered this issue, IT admins can resolve it by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration > Administrative Templates. Organizations that don't utilize an IT department managed enterprise-managed device update process can also follow the provided links for information on resolving the issue.
For information on deploying and configuring this special Group Policy, please see "How to use Group Policy to deploy a Known Issue Rollback" here: https://learn.microsoft.com/en-us/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback
Download for Windows 11 25H2 and Windows 11 24H2: Windows 11 25H2 and Windows 11 24H2 KB5074109 20260114_07451 Known Issue Rollback: https://download.microsoft.com/download/4ce38d6d-6a7c-477a-b18d-613c5879ead3/Windows%2011%2024H2,%20Windows%2011%2025H2%20and%20Windows%20Server%202025%20KB5074109%20260114_07451%20Known%20Issue%20Rollback.msi
Download for Windows 11 23H2: Windows 11 23H2 KB5073455 260114_09101 Known Issue Rollback: https://download.microsoft.com/download/8f939ffe-afab-4124-9629-0e2eb4d9fa45/Windows%2011%2022H2%20KB5073455%20260114_09101%20Known%20Issue%20Rollback.msi
Download for Windows 10 version 22H2: Windows 10 22H2 KB5073724 20260114_11451 Known Issue Rollback: https://download.microsoft.com/download/aa4a6443-93e5-4046-bdb7-4e2248295e82/Windows%2010%2020H2,%2021H1,%2021H2%20and%2022H2%20KB5073724%20260114_11451%20Known%20Issue%20Rollback.msi
Download for Windows 10 version 1607: Windows 10 1607 KB5073722 20260114_11301 Known Issue Rollback: https://download.microsoft.com/download/c47cf5c1-bb79-4814-acc8-d2f8fa892948/Windows%2010%201607%20and%20Windows%20Server%202016%20KB5073722%20260114_11301%20Known%20Issue%20Rollback.msi
Important: Users and admins need to install and configure the Group Policy for your version of Windows to resolve this issue. Users and admins also need to restart affected devices to apply the group policy setting.
Final status: We've determined that a code misconfiguration in the recent January 2026 Windows security update (KB5074109) caused intermittent connection failures for Cloud PC, causing those access requests to fail. We've deployed a code fix for this issue to better connection handling for the request path and confirmed that this resolves the problem; however, users and admins will need to follow the details laid out in the More info section of this communication to fully resolve the impact.
This post was updated to correct some misconfigured URL links and provide a more accurate representation of why the problem occurred.
Scope of impact: Any user connecting to Cloud PC sessions may have been intermittently affected by this issue.
Start time: Wednesday, January 14, 2026, at 12:11 AM UTC
End time: Wednesday, January 14, 2026, at 11:41 AM UTC
Root cause: A code misconfiguration in the recent January 2026 Windows security update (KB5074109) caused intermittent connection failures for Cloud PC, causing those access requests to fail. The issue affected Windows App on specific Windows builds, causing sign-in failures. For more information, refer to: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-25h2#3760msgdesc.
Next steps: - We're reviewing our update procedures to better identify similar code issues during our development and testing cycles.
This is the final update for the event.
Time:Wed Jan 14 06:44:35 2026
Description:Title: Users may experience intermittent failures and issues signing-in when connecting to Microsoft 365 Cloud PC sessions
User impact: Users may experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: If you are impacted, please use one of the following connection options as a workaround:
- Use the Remote Desktop client for Windows to connect to Azure Virtual Desktop here (What's new in the Remote Desktop client for Windows - Remote Desktop client | Microsoft Learn)
- Connect using the Windows App Web Client at windows.cloud.microsoft
Current status: We've developed and implemented a fix to correct the failed connections, with deployment expected to complete by the next scheduled update.
Scope of impact: Any user may be affected and experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
Start time: Wednesday, January 14, 2026, at 12:11 AM UTC
Root cause: A recent Windows 365 update intended to further improve security functionality is causing failed connection attempts to Cloud PC sessions.
Next update by: Wednesday, January 14, 2026, at 2:00 PM UTC
Time:Wed Jan 14 04:02:46 2026
Description:Title: Users may experience intermittent failures and issues signing-in when connecting to Microsoft 365 Cloud PC sessions
User impact: Users may experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: If you are impacted, please use one of the following connection options as a workaround:
- Use the Remote Desktop client for Windows to connect to Azure Virtual Desktop here (What's new in the Remote Desktop client for Windows - Remote Desktop client | Microsoft Learn)
- Connect using the Windows App Web Client at windows.cloud.microsoft
Current status: We're continuing with our analysis of the recent update to determine how best to mitigate impact.
Scope of impact: Any user may be affected and experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
Start time: Wednesday, January 14, 2026, at 12:11 AM UTC
Root cause: A recent Windows 365 update intended to further improve security functionality is causing failed connection attempts to Cloud PC sessions.
Next update by: Wednesday, January 14, 2026, at 12:00 PM UTC
Time:Wed Jan 14 01:18:44 2026
Description:Title: Users may experience intermittent failures and issues signing-in when connecting to Microsoft 365 Cloud PC sessions
User impact: Users may experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: Users can utilize the following connection options to avoid impact: - Connect using the Windows App Web Client at windows.cloud.microsoft - Use the Remote Desktop client to connect to Windows 365.
Current status: We identified that a recent Windows 365 update intended to further improve security functionality is causing failed connection attempts. We're further analyzing the update to determine the best method of remediating the impact. We'll provide further updates on the potential mitigation plans as they become available.
Scope of impact: Any user may be affected and experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
Start time: Wednesday, January 14, 2026, at 12:11 AM UTC
Root cause: A recent Windows 365 update intended to further improve security functionality is causing failed connection attempts to Cloud PC sessions.
Next update by: Wednesday, January 14, 2026, at 12:00 PM UTC
Time:Tue Jan 13 22:58:32 2026
Description:Title: Users may experience intermittent failures and issues signing-in when connecting to Microsoft 365 Cloud PC sessions
User impact: Users may experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
More info: Users can utilize the following connection options to avoid impact: - Connect using the Windows App Web Client at windows.cloud.microsoft - Use the Remote Desktop client to connect to Windows 365.
Current status: We detected an issue with Cloud PC connections and sign-in through our automated service monitoring after seeing an increase in failed connection attempts. We're investigating our service telemetry, including recent Windows 365 updates, to identify the underlying cause of impact and to help inform our next troubleshooting steps.
Scope of impact: Any user may be affected and experience intermittent failures and issues signing-in when connecting to Cloud PC sessions.
Next update by: Wednesday, January 14, 2026, at 7:30 AM UTC

MO1213801 - Users may have been unable to access shared Microsoft To Do lists

Status:serviceRestored
Start Time:Mon Dec 29 15:00:00 2025
End Time:Wed Jan 14 07:30:00 2026
Service:Microsoft 365 suite
Feature Group:Portal
Classification:advisory
Last Updated:Wed Jan 14 09:04:10 2026
Root Cause:A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which resulted in impact.
Next Update:N/A

Details

Time:Wed Jan 14 08:52:49 2026
Description:Title: Users may have been unable to access shared Microsoft To Do lists
User impact: Users may have been unable to access shared Microsoft To Do lists.
More info: Users may also have been unable to open shared To Do list invitation links.
Final status: We’ve confirmed that the issue is resolved following successful deployment of the fix.
Scope of impact: This issue may have potentially impacted any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
End time: Wednesday, January 14, 2026, at 12:30 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which resulted in impact.
Next steps: - We’ll continue monitoring the sharing functionality to ensure stability and service health.
This is the final update for the event.
Time:Tue Jan 13 04:26:06 2026
Description:Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We’ve identified that a small number of system processes are running more slowly than expected, which is temporarily delaying the reversion of the change. The reversion has now been successfully completed for approximately 93% of the affected environments. We’ll provide an updated completion timeline as soon as it’s available.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Wednesday, January 14, 2026, at 3:30 PM UTC
Time:Mon Jan 12 09:31:30 2026
Description:Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're continuing to revert the offending change and anticipate completion by the end of Monday, January 12, 2026. Once completed, we'll need to monitor for an extended period of time to ensure that impact has been fully resolved.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Tuesday, January 13, 2026, at 3:30 PM UTC
Time:Fri Jan 9 10:20:37 2026
Description:Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We've started the reversion process and anticipate complete by Monday, January 12, 2026.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Estimated time to resolve: Monday, January 12, 2026
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Monday, January 12, 2026, at 5:00 PM UTC
Time:Thu Jan 8 11:44:19 2026
Description:Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're completing the final validations prior to initiating the reversion process which we anticipate will begin by our next scheduled communications update.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Friday, January 9, 2026, at 5:00 PM UTC
Time:Wed Jan 7 14:26:34 2026
Description:Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We've identified a recent change, intended to add optimizations when sharing To Do lists, that's introduced a misconfiguration and is resulting in impact. We're reverting this change to resolve the issue, and we'll provide a timeline for remediation as one becomes available.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Root cause: A recent change to add optimizations when sharing To Do lists introduced a misconfiguration which is resulting in impact.
Next update by: Thursday, January 8, 2026, at 6:30 PM UTC
Time:Tue Jan 6 19:36:24 2026
Description:Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're continuing to analyze a reproduction of the impact within our internal testing environment as well as reviewing recent updates.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Start time: Monday, December 29, 2025, at 8:00 PM UTC
Next update by: Wednesday, January 7, 2026, at 8:00 PM UTC
Time:Tue Jan 6 16:44:01 2026
Description:Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're analyzing a reproduction of impact within our internal testing environment along with reviewing recent updates to Microsoft To Do, to isolate potential discrepancies and to determine our next troubleshooting steps.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Next update by: Wednesday, January 7, 2026, at 2:00 AM UTC
Time:Tue Jan 6 13:22:33 2026
Description:Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: Our investigation of service logs indicates that requests to access Microsoft To Do lists are returning 'not found'. We're continuing our analysis of these logs to further isolate the root cause of impact and develop a remediation strategy.
Scope of impact: This issue may potentially impact any user attempting to access shared Microsoft To Do lists.
Next update by: Tuesday, January 6, 2026, at 10:00 PM UTC
Time:Tue Jan 6 02:48:43 2026
Description:Title: Users may be unable to access shared Microsoft To Do lists
User impact: Users may be unable to access shared Microsoft To Do lists.
More info: Users may also be unable to open shared To Do list invitation links.
Current status: We're analyzing system logs including any recent changes to assist in identifying the source of the issue, which will help us determine our next troubleshooting steps.
Scope of impact: This issue may potentially impact any user attempting to access a shared Microsoft To Do lists.
Next update by: Tuesday, January 6, 2026, at 7:30 PM UTC

OP1217551 - Some users may not be able to get the latest Microsoft 365 Apps updates

Status:serviceRestored
Start Time:Tue Jan 13 10:30:00 2026
End Time:Tue Jan 13 17:00:00 2026
Service:Microsoft 365 apps
Feature Group:Office Client issues
Classification:advisory
Last Updated:Tue Jan 13 18:16:55 2026
Root Cause:Values needed weren’t present in the release build which then prevented the Cloud Update service from picking up the new update, and this resulted in the impact.
Next Update:N/A

Details

Time:Tue Jan 13 18:04:21 2026
Description:Title: Some users may not be able to get the latest Microsoft 365 Apps updates
User impact: Users may not have been able to get the latest Microsoft 365 Apps updates.
More info: This issue specifically impacted organizations where these updates were facilitated through the Cloud Update process in the Microsoft 365 apps admin center.
Final status: After our analysis of the latest update, we determined that values needed weren’t present in the release build which then prevented the Cloud Update service from picking up the new update, and this resulted in the impact. We've applied a fix to restore the values and confirmed that this has remediated the issue.
Scope of impact: Some users reliant on the Cloud Update process to update their Microsoft 365 apps may have been affected.
Start time: Tuesday, January 13, 2026, at 3:30 PM UTC
End time: Tuesday, January 13, 2026, at 10:00 PM UTC
Root cause: Values needed weren’t present in the release build which then prevented the Cloud Update service from picking up the new update, and this resulted in the impact.
Next steps: - We're reviewing our update standards to ensure missing values are caught and corrected ahead of publishing to prevent this from happening again.
This is the final update for the event.
Time:Tue Jan 13 15:39:14 2026
Description:Title: Some users may not be able to get the latest Microsoft 365 Apps updates
User impact: Users may not be able to get the latest Microsoft 365 Apps updates.
More info: This issue specifically impacts organizations where these updates are facilitated through the Cloud Update process in the Microsoft 365 apps admin center.
Current status: We're analyzing the latest update to determine our next troubleshooting steps.
Scope of impact: Some users reliant on the Cloud Update process to update their Microsoft 365 apps may be affected. This section may be updated as our investigation continues.
Next update by: Wednesday, January 14, 2026, at 12:30 AM UTC

SP1216181 - Users may not receive email notifications generated from the SharePoint Online Rules

Status:serviceRestored
Start Time:Mon Dec 8 07:00:00 2025
End Time:Tue Jan 13 13:00:00 2026
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Tue Jan 13 13:39:15 2026
Root Cause:A recent feature update contained a code error that prevented email notifications from generating as expected, which resulted in impact.
Next Update:N/A

Details

Time:Tue Jan 13 13:39:15 2026
Description:Title: Users may not receive email notifications generated from the SharePoint Online Rules
User impact: Users may not have received email notifications generated from the SharePoint Online Rules feature.
More info: Users could have created a new rule with the same settings as an affected rule to bypass the impact while we worked to resolve this issue.
Final status: We've confirmed the fix has completed deployment and the configuration change has been applied. After validating impact remediation with a subset of affected users, we've verified the issue has been resolved.
Scope of impact: Any user expecting SharePoint Online rules email notifications may have been affected.
Start time: Monday, December 8, 2025, at 12:00 PM UTC
End time: Tuesday, January 13, 2026, at 6:00 PM UTC
Root cause: A recent feature update contained a code error that prevented email notifications from generating as expected, which resulted in impact.
Next steps: - We're reviewing our feature update protocols to ensure similar code errors are caught and addressed ahead of deployment to prevent this from reoccurring.
This is the final update for the event.
Time:Mon Jan 12 13:40:59 2026
Description:Title: Users may not receive email notifications generated from the SharePoint Online Rules
User impact: Users may not receive email notifications generated from the SharePoint Online Rules feature.
More info: Users can create a new rule with the same settings as an affected rule to bypass the impact while we work to resolve this issue.
Current status: We're monitoring as the fix continues its deployment and confirmed it's reached over 95 percent of affected infrastructure. Once complete, an additional configuration change will be applied to fully remediate impact. We hope to provide a remediation timeline by the next scheduled update.
Scope of impact: Any user expecting SharePoint Online rules email notifications may be affected.
Start time: Monday, December 8, 2025, at 12:00 PM UTC
Root cause: A recent feature update contains a code error that's preventing email notifications from generating as expected, resulting in impact.
Next update by: Tuesday, January 13, 2026, at 7:00 PM UTC
Time:Fri Jan 9 16:12:31 2026
Description:Title: Users may not receive email notifications generated from the SharePoint Online Rules
User impact: Users may not receive email notifications generated from the SharePoint Online Rules feature.
More info: Users can create a new rule with the same settings as an affected rule to bypass the impact while we work to resolve this issue.
Current status: Our analysis of recent changes has confirmed that a recent feature update contains a code error that's preventing email notifications from generating as expected, resulting in impact. We're in the process of developing a fix to remediate impact and expect to have a mitigation timeline by the next scheduled communications update.
Scope of impact: Any user expecting SharePoint Online rules email notifications may be affected.
Start time: Monday, December 8, 2025, at 12:00 PM UTC
Root cause: A recent feature update contains a code error that's preventing email notifications from generating as expected, resulting in impact.
Next update by: Monday, January 12, 2026, at 10:00 PM UTC
Time:Fri Jan 9 13:43:05 2026
Description:Title: Users aren't receiving notification emails generated from the SharePoint Online Rules feature
User impact: Users aren't receiving notification emails generated from the SharePoint Online Rules feature.
More info: Users can create a new rule with the same settings as an affected rule to bypass the impact while we work to resolve this issue.
Current status: We're reviewing recent service updates which may be contributing to impact.
Scope of impact: Any user expecting SharePoint Online rules notifications may be affected.
Next update by: Friday, January 9, 2026, at 10:00 PM UTC
Time:Fri Jan 9 13:19:15 2026
Description:Title: Users aren't receiving notification emails generated from the SharePoint Online Rules feature
User impact: Users aren't receiving notification emails generated from the SharePoint Online Rules feature.
More info: This event is a continuation of the incident previously communicated via SP1216014.
Users can create a new rule with the same settings as an affected rule to bypass the impact while we work to resolve this issue.
Current status: We're investigating a potential issue with SharePoint Online rules and checking for impact to your organization. We'll provide an update within 30 minutes.

PB1217058 - Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered

Status:serviceRestored
Start Time:Thu Jan 8 01:00:00 2026
End Time:Mon Jan 12 22:30:00 2026
Service:Power BI
Feature Group:PowerBI.com
Classification:advisory
Last Updated:Tue Jan 13 01:56:28 2026
Root Cause:A recent service update designed to change how tasks deliver subscription email messages for reports and dashboards in Microsoft Power BI were processed, was preventing the tasks from being completed efficiently and causing impact.
Next Update:N/A

Details

Time:Tue Jan 13 01:56:28 2026
Description:Title: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' subscription email messages for reports and dashboards in Microsoft Power BI were delayed or weren't delivered.
More info: Impact was intermittent for some users.
While we worked on fixing the issue, users could've leveraged the "send now" button to deliver the subscription email messages.
Final status: We've completed reverting the offending update, and after a period of monitoring, we confirmed impact was remediated.
Scope of impact: Your organization was affected by this event, and any user configured to receive email messages reports and dashboards in Microsoft Power BI was impacted.
Start time: Thursday, January 8, 2026, at 6:00 AM UTC
End time: Tuesday, January 13, 2026, at 3:30 AM UTC
Root cause: A recent service update designed to change how tasks deliver subscription email messages for reports and dashboards in Microsoft Power BI were processed, was preventing the tasks from being completed efficiently and causing impact.
Next steps: - To help prevent similar impact in the future, we're further reviewing our update release procedures to identify delivery and processing issues before being deployed.
This is the final update for the event.
Time:Mon Jan 12 18:13:16 2026
Description:Title: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered.
More info: Impact is intermittent for some users.
While we work on fixing this issues, users can leverage the "send now" button to deliver the subscription email messages.
Current status: We're identified a recent service update designed to change how tasks to deliver subscription email messages for reports and dashboards in Microsoft Power BI are processed, which is preventing the tasks from being completed efficiently and causing impact. We're reversing the offending change to remediate the impact.
Scope of impact: Your organization is affected by this event, and any user configured to receive email messages reports and dashboards in Microsoft Power BI is impacted.
Start time: Thursday, January 8, 2026, at 6:00 AM UTC
Root cause: A recent service update designed to change how tasks to deliver subscription email messages for reports and dashboards in Microsoft Power BI are processed, is preventing the tasks from being completed efficiently and causing impact.
Next update by: Tuesday, January 13, 2026, at 7:30 AM UTC
Time:Mon Jan 12 16:53:44 2026
Description:Title: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered.
More info: Impact is intermittent for some users.
While we work on fixing this issue, users can leverage the "send now" button to deliver the subscription email messages.
Current status: We're reviewing the portion of service infrastructure responsible for facilitating the delivery of subscription email messages for reports and dashboards in Microsoft Power BI to check whether the tasks to deliver the email messages are being processed efficiently.
Scope of impact: Your organization is affected by this event, and any user configured to receive email messages reports and dashboards in Microsoft Power BI is impacted.
Next update by: Tuesday, January 13, 2026, at 12:00 AM UTC
Time:Mon Jan 12 15:39:05 2026
Description:Title: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' subscription email messages for reports and dashboards in Microsoft Power BI are delayed or aren't delivered.
More info: Impact is intermittent for some users.
Current status: We're reviewing the queue of unsent email subscription messages to determine the next steps to isolate why they're delayed for failing to send.
Scope of impact: Your organization is affected by this event, and any user configured to receive email messages reports and dashboards in Microsoft Power BI is impacted.
Next update by: Monday, January 12, 2026, at 10:00 PM UTC
Time:Mon Jan 12 15:23:07 2026
Description:Title: Users' email subscriptions for reports and dashboards in Microsoft Power BI are delayed or aren't delivered
User impact: Users' email subscriptions for reports and dashboards in Microsoft Power BI are delayed or aren't delivered.
Current status: We're investigating a potential issue with Microsoft Power BI and checking for impact to your organization. We'll provide an update within 30 minutes.

CP1215237 - Users may be unable to use the AI features in the Create module of Microsoft Copilot (Microsoft 365)

Status:serviceRestored
Start Time:Mon Dec 15 13:35:00 2025
End Time:Fri Jan 9 12:35:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Mon Jan 12 16:48:02 2026
Root Cause:A recent code change intended to introduce a toggle that disables the AI features in the Create module was causing the previously available AI features to been hidden and inaccessible for all users, which resulted in impact.
Next Update:N/A

Details

Time:Mon Jan 12 16:48:02 2026
Description:Title: Users may be unable to use the AI features in the Create module of Microsoft Copilot (Microsoft 365)
User impact: Users may have been unable to use the AI features in the Create module of Microsoft Copilot.
Final status: We've confirmed our fix to address the impact caused by the recent code change has completed deploying to the affected environment and the issue has been remediated.
Scope of impact: Any user attempting to use the AI features in the Create module of Microsoft Copilot may have been impacted by this event.
Start time: Monday, December 15, 2025, at 6:35 PM UTC
End time: Friday, January 9, 2026, at 5:35 PM UTC
Root cause: A recent code change intended to introduce a toggle that disables the AI features in the Create module was causing the previously available AI features to been hidden and inaccessible for all users, which resulted in impact.
Next steps: - We're reviewing our update procedures to ensure similar issues are caught and addressed ahead of any code changes to prevent this from happening again.
This is the final update for the event.
Time:Wed Jan 7 21:14:56 2026
Description:Title: Users may be unable to use the AI features in the Create module of Microsoft Copilot (Microsoft 365)
User impact: Users may be unable to use the AI features in the Create module of Microsoft Copilot.
Current status: We've been made aware of an issue in which users may be unable to use the AI features in the Create module of Microsoft Copilot. We've determined that a recent code change intended to introduce a toggle that disables the AI features in the Create module is causing the previously available AI features to be hidden and inaccessible for all users, resulting in impact. We've developed a fix to address the issue and we're preparing it for deployment throughout the affected environments. We anticipate our fix will complete the deployment by our next scheduled communications update.
Scope of impact: Any user attempting to use the AI features in the Create module of Microsoft Copilot may be impacted by this event. This information may be updated as our investigation continues.
Root cause: A recent code change intended to introduce a toggle that disables the AI features in the Create module is causing the previously available AI features to be hidden and inaccessible for all users, resulting in impact.
Next update by: Thursday, January 15, 2026, at 8:00 PM UTC

TM1212728 - Users may have been unable to search new users in Microsoft Teams by their display name

Status:serviceRestored
Start Time:Tue Dec 9 19:00:00 2025
End Time:Sun Jan 11 19:00:00 2026
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon Jan 12 05:55:22 2026
Root Cause:A recent change to our Active Directory service introduced a regression affecting user search functionality.
Next Update:N/A

Details

Time:Mon Jan 12 05:55:22 2026
Description:Title: Users may have been unable to search new users in Microsoft Teams by their display name
User impact: Users may have been unable to search new users in Microsoft Teams by their display name.
More info: This may have impacted users in both the desktop and web clients. Users could still search new users using their email address.
Final status: We've successfully completed the reindexing and verified with some affected users, that impact has fully resolved.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may have been impacted.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
End time: Monday, January 12, 2026, at 12:00 AM UTC
Root cause: A recent change to our Active Directory service introduced a regression affecting user search functionality.
Next steps: - We're reviewing our change procedures to help prevent similar problems in the future.
This is the final update for the event.
Time:Fri Jan 9 06:22:27 2026
Description:Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We've completed the index reset and enabled it for all customers on Wednesday, January 6, 2026, at 15:00 UTC. Reindexing continues to progress as planned and is expected to complete by Monday, January 12, 2026.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Estimated time to resolve: Monday, January 12, 2026
Root cause: A recent change to our Active Directory service introduced a regression affecting user search functionality, resulting in impact.
Next update by: Monday, January 12, 2026, at 12:00 PM UTC
Time:Wed Jan 7 05:39:22 2026
Description:Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We’re continuing to reset the index for affected customers in stages. The process has already been enabled for 50% of customers and will advance to 100% tomorrow. Due to heavy system load and parallel processing, completion is expected by Monday, January 12, 2026. Once complete, normal search functionality will be restored for impacted users.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Estimated time to resolve: Monday, January 12, 2026
Root cause: A recent change to our Active Directory service introduced a regression affecting user search functionality, resulting in impact.
Next update by: Friday, January 9, 2026, at 12:00 PM UTC
Time:Mon Jan 5 05:50:21 2026
Description:Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We've identified that a recent change to our Active Directory service introduced a regression affecting user search functionality. This change has been rolled back, and reindexing has been initiated for impacted customers. We expect the index rebuild to complete within 48 hours, after which normal search functionality will be restored for impacted users.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Root cause: A recent change to our Active Directory service introduced a regression affecting user search functionality, resulting in impact.
Next update by: Wednesday, January 7, 2026, at 12:00 PM UTC
Time:Mon Jan 5 03:19:48 2026
Description:Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We're continuing to review the provided case details and logs to help identify the underlying cause of the display name search issue for new users, and help to develop our next troubleshooting steps.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, January 5, 2026, at 12:00 PM UTC
Time:Sun Jan 4 22:14:01 2026
Description:Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We're reviewing the provided case details and logs to help identify the underlying cause of the display name search issue for new users, and help to develop our next troubleshooting steps.
Scope of impact: Users attempting to search new users in Microsoft Teams by their display name may be impacted. This section may be updated as our investigation continues.
Next update by: Monday, January 5, 2026, at 10:30 AM UTC
Time:Sun Jan 4 21:46:34 2026
Description:Title: Users may be unable to search new users in Microsoft Teams by their display name
User impact: Users may be unable to search new users in Microsoft Teams by their display name.
More info: This may impact users in both the desktop and web clients. Users can still search new users using their email address.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

SP1215831 - Some read-only users may see blank pages for their SharePoint Online sites

Status:serviceRestored
Start Time:Wed Jan 7 14:44:00 2026
End Time:Thu Jan 8 13:18:00 2026
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:incident
Last Updated:Thu Jan 8 15:22:17 2026
Root Cause:The latest SharePoint Online service build contained a regression which resulted in read-only users seeing blank pages for their SharePoint Online sites.
Next Update:N/A

Details

Time:Thu Jan 8 14:53:29 2026
Description:Title: Some read-only users may see blank pages for their SharePoint Online sites
User impact: Read-only users may have seen blank pages for their SharePoint Online sites.
More info: Affected users reported seeing relevant page information displaying briefly before becoming a blank page.
Final status: We've validated that the latest SharePoint Online service build contained a regression which resulted in read-only users seeing blank pages for their SharePoint Online sites. We've rolled back the offending build and validated with a subset of affected users that our actions successfully resolved the issue.
Scope of impact: Some read-only users may have seen blank pages for their SharePoint Online sites.
Start time: Wednesday, January 7, 2026, at 7:44 PM UTC
End time: Thursday, January 8, 2026, at 6:18 PM UTC
Root cause: The latest SharePoint Online service build contained a regression which resulted in read-only users seeing blank pages for their SharePoint Online sites.
Next steps: - We're analyzing the offending service build to isolate the underlying root cause. This analysis will help us to improve the quality and reliability of our future updates, while also helping that similar impact doesn't occur in future.
This is the final update for the event.
Time:Thu Jan 8 14:20:45 2026
Description:Title: Some read-only users may see blank pages for their SharePoint Online sites
User impact: Read-only users may see blank pages for their SharePoint Online sites.
More info: Affected users report seeing relevant page information displaying briefly before becoming a blank page.
Current status: We're reviewing reports from affected users to understand the current impact scenario and to determine what mitigation actions we can take to resolve impact.
Scope of impact: Some read-only users may see blank pages for their SharePoint Online sites. This section may be updated as the investigation progresses.
Next update by: Thursday, January 8, 2026, at 9:30 PM UTC
Time:Thu Jan 8 14:07:37 2026
Description:Title: Read-only users see blank pages for their SharePoint Online sites
User impact: Read-only users see blank pages for their SharePoint Online sites.
More info: Affected users report seeing relevant page information displaying briefly before becoming a blank page.
Current status: We're investigating a potential issue with SharePoint Online and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1215307 - Some users may have been unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)

Status:serviceRestored
Start Time:Thu Jan 1 19:00:00 2026
End Time:Thu Jan 8 06:30:00 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:incident
Last Updated:Thu Jan 8 07:34:33 2026
Root Cause:A recent IMAP deployment related to authentication support contained a code conflict that introduced a configuration issue and was causing intermittent mailbox access issues for some impacted users.
Next Update:N/A

Details

Time:Thu Jan 8 07:34:33 2026
Description:Title: Some users may have been unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may have intermittently been unable to access their mailboxes using IMAP4.
More info: Impact was specific to IMAP4, other connection methods were not impacted. Additionally, if users were actively facing this issue, retries may have been successful.
Final status: We’ve completed deploying the configuration change on the affected servers, which reduced volume and restored normal service functionality. After a period of monitoring, we’ve confirmed that impact has been fully remediated.
Scope of impact: Some users that were attempting to access their mailboxes using IMAP4 may have been intermittently impacted.
Start time: Friday, January 2, 2026, at 12:00 AM UTC
End time: Thursday, January 8, 2026, at 11:30 AM UTC
Root cause: A recent IMAP deployment related to authentication support contained a code conflict that introduced a configuration issue and was causing intermittent mailbox access issues for some impacted users.
Next steps: - We're reviewing our deployment and provisioning procedures to help prevent similar problems in the future.
This is the final update for the event.
Time:Thu Jan 8 07:19:31 2026
Description:Title: Some users may have been unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may have intermittently been unable to access their mailboxes using IMAP4.
More info: Impact was specific to IMAP4, other connection methods were not impacted. Additionally, if users were actively facing this issue, retries may have been successful.
Final status: We’ve completed deploying the configuration change on the affected servers, which reduced volume and restored normal service functionality. After a period of monitoring, we’ve confirmed that impact has been fully remediated.
Scope of impact: Some users that were attempting to access their mailboxes using IMAP4 may have been intermittently impacted.
Start time: Friday, January 2, 2026, at 12:00 AM UTC
End time: Thursday, January 8, 2026, at 11:30 AM UTC
Root cause: A recent IMAP deployment related to authentication support contained a code conflict that introduced a configuration issue and was causing intermittent mailbox access issues for some impacted users.
Next steps: - We're reviewing our deployment and provisioning procedures to help prevent similar problems in the future.
This is the final update for the event.
Time:Thu Jan 8 02:58:43 2026
Description:Title: Some users may intermittently be unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may intermittently be unable to access their mailboxes using IMAP4.
More info: Impact is specific to IMAP4, other connection methods are not impacted. Additionally, if users are actively facing this issue, retries may be successful.
Current status: We're continuing to deploy the configuration change and expect this process to complete by our next scheduled update.
Scope of impact: Some users that are attempting to access their mailboxes using IMAP4 may be intermittently impacted. This information may be updated as our investigation continues.
Root cause: A recent IMAP deployment related to authentication support contains a code conflict that introduced a configuration issue and is causing intermittent mailbox access issues for some impacted users.
Next update by: Thursday, January 8, 2026, at 1:30 PM UTC
Time:Thu Jan 8 00:37:19 2026
Description:Title: Some users may intermittently be unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may intermittently be unable to access their mailboxes using IMAP4.
More info: Impact is specific to IMAP4, other connection methods are not impacted. Additionally, if users are actively facing this issue, retries may be successful.
Current status: We've completed developing the configuration change and have validated it in our internal testing environment to ensure its efficacy in remediating impact. We've started deploying it to the impacted environments and we'll aim to provide a resolution timeline by our next scheduled update.
Scope of impact: Some users that are attempting to access their mailboxes using IMAP4 may be intermittently impacted. This information may be updated as our investigation continues.
Root cause: A recent IMAP deployment related to authentication support contains a code conflict that introduced a configuration issue and is causing intermittent mailbox access issues for some impacted users.
Next update by: Thursday, January 8, 2026, at 10:00 AM UTC
Time:Thu Jan 8 00:09:13 2026
Description:Title: Some users may intermittently be unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may intermittently be unable to access their mailboxes using IMAP4.
More info: Impact is specific to IMAP4, other connection methods are not impacted. Additionally, if users are actively facing this issue, retries may be successful.
Current status: We've identified a recent IMAP deployment related to authentication support contains a code conflict that introduced a configuration issue and is causing intermittent mailbox access issues for some impacted users. We're halting the deployment to prevent further impact from spreading and are developing a configuration change to restore service functionality. We'll aim to provide a resolution timeline once available.
Scope of impact: Some users that are attempting to access their mailboxes using IMAP4 may be intermittently impacted. This information may be updated as our investigation continues.
Root cause: A recent IMAP deployment related to authentication support contains a code conflict that introduced a configuration issue and is causing intermittent mailbox access issues for some impacted users.
Next update by: Thursday, January 8, 2026, at 6:30 AM UTC
Time:Wed Jan 7 23:52:58 2026
Description:Title: Some users may intermittently be unable to access their mailboxes using Internet Mailbox Access Protocol 4 (IMAP4)
User impact: Users may intermittently be unable to access their mailboxes using IMAP4.
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

SP1030180 - Users may see a new "Content Freshness" template option when creating pages in SharePoint Online

Status:serviceRestored
Start Time:Wed Jan 15 19:00:00 2025
End Time:Wed Jan 7 19:00:00 2026
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Wed Jan 7 22:05:44 2026
Root Cause:A recent deployment incorrectly enabled this feature in the affected environment.
Next Update:N/A

Details

Time:Wed Jan 7 22:05:44 2026
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may have seen a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option had no functional impact. If users encountered the option for the template, they could ignore it and continue using other templates without issues. Affected users may have also seen the option appear in List Settings or the Content Type editing panel.
Final status: Our fix deployment completed, and after a period of monitoring, we've confirmed impact was remediated.
Scope of impact: Users creating pages in SharePoint Online may have been impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
End time: Thursday, January 8, 2026, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next steps: - To help prevent similar impact in the future, we're further reviewing our deployment release procedures to ensure features aren't enabled incorrectly.
This is the final update for the event.
Time:Wed Dec 17 22:05:38 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix is progressing and we're continuing to monitor as it completes.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, January 8, 2026, at 6:00 AM UTC
Time:Wed Dec 3 23:01:12 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix is ongoing and we're continuing to monitor as it progresses.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, December 18, 2025, at 6:00 AM UTC
Time:Wed Nov 19 22:08:05 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We're continuing to monitor as the fix completes saturating throughout the affected environment to confirm it remains stable.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, December 4, 2025, at 6:00 AM UTC
Time:Wed Oct 29 23:52:50 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: While the fix deployment is taking longer than previously anticipated to complete, our service health telemetry indicates that the impact is resolved for the affected users. We’re continuing to monitor as the remainder of the fix propagates throughout the affected environment and to ensure that the impact is fully remediated.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, November 20, 2025, at 5:00 AM UTC
Time:Wed Oct 22 23:43:32 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix deployment has nearly completed and we anticipate that the issue is no longer occurring for affected users. We’re monitoring the remainder of the deployment to confirm that the environment remains stable and the impact is fully remediated prior to our next scheduled update.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, October 30, 2025, at 5:00 AM UTC
Time:Thu Oct 16 00:20:34 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: Our telemetry indicates that the fix has nearly completed. We're continuing to monitor as it progresses and anticipate providing a completion timeline at our next scheduled update.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, October 23, 2025, at 5:00 AM UTC
Time:Wed Oct 8 21:09:03 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: Our fix deployment is ongoing; however, we've yet to establish an updated completion timeline. We're continuing to monitor to ensure remediation and provide a timeline once one becomes available.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, October 16, 2025, at 5:00 AM UTC
Time:Wed Sep 10 22:48:35 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix deployment is ongoing and we're continuing to monitor as it progresses to establish a completion timeline.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, October 9, 2025, at 5:00 AM UTC
Time:Wed Aug 27 23:40:52 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix deployment has encountered a delay and won't complete by our initial anticipated projection. We're continuing to monitor as it progresses and will provide an updated timeline when one becomes available.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, September 11, 2025, at 5:00 AM UTC
Time:Wed Aug 13 22:53:06 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix deployment is ongoing and we're continuing to monitor as it progresses. We now anticipate it will have completed by the end of August 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, August 28, 2025, at 5:00 AM UTC
Time:Wed Aug 6 22:19:57 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix deployment is taking longer than anticipated, but is ongoing. We'll provide an updated completion timeline when one becomes available.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, August 14, 2025, at 5:00 AM UTC
Time:Wed Jul 16 23:58:02 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix deployment is ongoing, and we continue to estimate that it will complete by late July 2025, or early August 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, August 7, 2025, at 5:00 AM UTC
Time:Wed Jul 2 23:32:10 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: The fix is deploying to the impacted environments, and our monitoring indicates that the majority of affected tenants should be experiencing remediation. We estimate that the remainder of the deployment will complete by late July 2025, or early August 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, July 17, 2025, at 5:00 AM UTC
Time:Wed Jun 18 22:51:25 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've completed deploying the fix to our internal testing environment and validated that it successfully remediates impact. We've started deploying the fix to the impacted environments, and anticipate the deployment may complete by late July 2025, or early August 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, July 3, 2025, at 5:00 AM UTC
Time:Wed Jun 4 22:59:19 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've completed the development of our updated fix for the issue and are finalizing its validation within our internal testing environment in preparation for its widespread deployment.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, June 19, 2025, at 5:00 AM UTC
Time:Wed May 21 23:15:44 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've encountered an issue with our long-term fix during our internal testing and validation process. We're working to debug the issue to prepare the fix for deployment and anticipate this may push back our timeline for remediation by four to five weeks, meaning users may not see our changes in effect until late July 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, June 5, 2025, at 5:00 AM UTC
Time:Wed May 7 23:24:45 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've begun the initial validation and internal testing of the aforementioned long-term fix, and this process remains on track to complete by our previously communicated mid-June 2025 estimation.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 22, 2025, at 5:00 AM UTC
Time:Wed Apr 23 23:00:43 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We're focusing our efforts on developing and deploying a long-term fix to remove the incorrect inclusion of the "Content Freshness" template option, which remains on track to be completed by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, May 8, 2025, at 5:00 AM UTC
Time:Wed Apr 9 23:18:32 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues. Affected users may also see the option appear in List Settings or the Content Type editing panel.
Current status: We've identified an issue with our previously developed near-term fix to remove the template option and determined its deployment needs to be suspended. While we continue to assess our options for potential expedited solutions, we're working on a long-term fix that we're projecting may be released by mid-June 2025.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Thursday, January 16, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 24, 2025, at 5:00 AM UTC
Time:Wed Mar 26 21:38:32 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've completed validating our fix to remove the "Content Freshness" template and have initiated the deployment to the impacted environments. Based on the complexity of the fix, we're deploying it at a slow monitored pace to ensure it doesn't adversely impact other aspects of the service. We anticipate it may take approximately four weeks for the deployment to complete, and we'll aim to provide a resolution timeline once available.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, April 10, 2025, at 5:00 AM UTC
Time:Wed Mar 12 23:48:34 2025
Description:Title: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online
User impact: Users may see a new "Content Freshness" template option when creating pages in SharePoint Online.
More info: Selecting the "Content Freshness" template option has no functional impact. If users encounter the option for the template, they can ignore it and continue using other templates without issues.
Current status: We've identified an issue in which users may see a new "Content Freshness" template option when creating pages in SharePoint Online. We've determined a recent deployment incorrectly enabled this feature in the affected environment. We're developing a fix to remove the "Content Freshness" template and in the meantime, we advise users to ignore the "Content Freshness" template option.
Scope of impact: Users creating pages in SharePoint Online may be impacted.
Start time: Wednesday, February 5, 2025, at 12:00 AM UTC
Root cause: A recent deployment incorrectly enabled this feature in the affected environment.
Next update by: Thursday, March 27, 2025, at 5:00 AM UTC

CP1214610 - Some users in Europe may have been unable to launch Copilot Chat or use related functionality

Status:serviceRestored
Start Time:Wed Jan 7 03:40:00 2026
End Time:Wed Jan 7 09:30:00 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:incident
Last Updated:Wed Jan 7 11:11:06 2026
Root Cause:A recent update to the section of infrastructure, responsible for facilitating Copilot chat, introduced a regression that's resulted in traffic being routed incorrectly and service unavailability.
Next Update:N/A

Details

Time:Wed Jan 7 10:52:40 2026
Description:Title: Some users in Europe may have been unable to launch Copilot Chat or use related functionality
User impact: Users in Europe may have been unable to launch Copilot Chat or use related functionality.
Final status: We've further identified that a recent update to the section of infrastructure, responsible for facilitating Copilot chat, introduced a regression that's resulted in traffic being routed incorrectly and service unavailability. We've reverted the aforementioned update and optimized the routing configuration, which has remediated impact.
Scope of impact: Impact was specific to some users in Europe attempting to launch Copilot chat.
Start time: Wednesday, January 7, 2026, at 8:40 AM UTC
End time: Wednesday, January 7, 2026, at 2:30 PM UTC
Root cause: A recent update to the section of infrastructure, responsible for facilitating Copilot chat, introduced a regression that's resulted in traffic being routed incorrectly and service unavailability.
Next steps: - We're reviewing our update procedures to understand why traffic was routed incorrectly, in order to help prevent similar impact from reoccurring. - We'll continue to closely monitor the affected environment to ensure the service remains healthy, and we'll review our service resilience processes to help us reduce or avoid similar issues in the future.
This is the final update for the event.
Time:Wed Jan 7 09:30:12 2026
Description:Title: Some users in Europe may be unable to launch Copilot Chat or use related functionality
User impact: Users in Europe may be unable to launch Copilot Chat or use related functionality.
Current status: We've identified that a recent service update to the infrastructure that facilitates the Copilot chat functionality in one of our European data centers has inadvertently caused impact to the service. We have isolated the source of the issue and are determining next steps to mitigate impact.
Scope of impact: Impact is specific to some users in Europe attempting to launch Copilot chat.
Next update by: Wednesday, January 7, 2026, at 4:30 PM UTC
Time:Wed Jan 7 07:39:03 2026
Description:Title: Some users in Europe may be unable to start Microsoft Copilot chats
User impact: Users in Europe may be unable to start Microsoft Copilot chats.
Current status: We're reviewing service monitoring telemetry and systems logs to isolate the root cause, in order to develop a remediation plan.
Scope of impact: Impact is specific to some users in Europe attempting to start Microsoft Copilot chats.
Next update by: Wednesday, January 7, 2026, at 2:30 PM UTC

CP1203823 - We've detected a problem with endpoint configuration affecting the Agent Builder for the Microsoft 365 Copilot service

Status:investigationSuspended
Start Time:Tue Dec 23 14:54:11 2025
End Time:Tue Jan 6 16:03:10 2026
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Tue Jan 6 16:03:14 2026
Root Cause:N/A
Next Update:N/A

Details

Time:Tue Jan 6 16:03:14 2026
Description:Title: We've detected a problem with endpoint configuration affecting the Agent Builder for the Microsoft 365 Copilot service
User impact: If action isn’t taken, users may be unable to utilize the Copilot Agent Builder's features.
Final status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
Time:Tue Dec 23 15:45:26 2025
Description:Title: We've detected a problem with endpoint configuration affecting the Agent Builder for the Microsoft 365 Copilot service
User impact: If action isn’t taken, users may be unable to utilize the Copilot Agent Builder's features.
Current status: Our systems are reporting that networking requests leveraged for Copilot Agent Builder functionality are being blocked by your organization's endpoint configuration. If action isn't taken, Copilot Agent Builder functionality may be blocked.
This communication will expire in 14 days and is scheduled to remain active for the full duration.

EX1213757 - Users may see an English user interface for Outlook on the web on mobile when configured for a non-English language

Status:serviceRestored
Start Time:Mon Dec 22 19:00:00 2025
End Time:Tue Jan 6 00:32:00 2026
Service:Exchange Online
Feature Group:E-Mail and calendar access
Classification:advisory
Last Updated:Tue Jan 6 01:02:40 2026
Root Cause:A recent service update contained misconfigured localization data, resulting in impact.
Next Update:N/A

Details

Time:Tue Jan 6 01:02:40 2026
Description:Title: Users may see an English user interface for Outlook on the web on mobile when configured for a non-English language
User impact: Users may have seen an English user interface for Outlook on the web on mobile when configured for non-English language.
More info: Impacted users would see an English user interface for Outlook on the web when accessing the service through mobile devices on both Android and iOS, even when the user interface configuration was set to alternate languages.
Final status: We've identified that a recent service update contained misconfigured localization data, resulting in impact. We've rolled back the problematic changes throughout the affected environment and confirmed through internal testing that impact is remediated.
Scope of impact: Users accessing Outlook on the web through mobile devices with their user interface language set to non-English languages may have been impacted.
Start time: Tuesday, December 23, 2025, at 12:00 AM UTC
End time: Tuesday, January 6, 2026, at 5:32 AM UTC
Root cause: A recent service update contained misconfigured localization data, resulting in impact.
Next steps: - We're reviewing our update testing and validation methods to better identify issues such as this prior to deployment so we can prevent similar impact in the future.
This is the final update for the event.
Time:Mon Jan 5 23:55:52 2026
Description:Title: Users may see an English user interface for Outlook on the web on mobile when configured for a non-English language
User impact: Users may see an English user interface for Outlook on the web on mobile when configured for a non-English language.
More info: Impacted users report seeing an English user interface for Outlook on the web when accessing the service through mobile devices on both Android and iOS, even when the user interface configuration is set to Japanese.
Current status: We're reviewing contextual details provided by affected users together with data collected from an internal reproduction of the issue to gain insight into the underlying source of impact and determine our next steps.
Scope of impact: Users accessing Outlook on the web through mobile devices with their user interface language set to non-English languages may be impacted. This information may be updated as our investigation continues.
Next update by: Tuesday, January 6, 2026, at 6:30 AM UTC
Time:Mon Jan 5 23:36:26 2026
Description:Title: Users may see an English user interface for Outlook on the web on mobile when configured for a non-English language
User impact: Users may see an English user interface for Outlook on the web on mobile when configured for a non-English language.
More info: Impacted users would see an English user interface for Outlook on the web when accessing the service through mobile devices on both Android and iOS, even when the user interface configuration was set to alternate languages.
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.

EX1213231 - Users may be unable to send encrypted email

Status:serviceRestored
Start Time:Mon Jan 5 09:55:00 2026
End Time:Mon Jan 5 13:15:00 2026
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:incident
Last Updated:Mon Jan 5 15:41:06 2026
Root Cause:A large increase in requests for RMS encryption and decryption following an extended low traffic period due to December holidays resulted in resource throttling and this impact, as our processing resiliency didn't adapt in a timely manner.
Next Update:N/A

Details

Time:Mon Jan 5 15:01:57 2026
Description:Title: Users may be unable to send encrypted email
User impact: Users may have been unable to send encrypted email.
More info: Users receive a Non-Delivery Report (NDR) with an exception message of "Failed to bootstrap tenant."
Final status: A large increase in requests for RMS encryption and decryption following an extended low traffic period due to December holidays resulted in resource throttling and this impact, as our processing resiliency didn't adapt in a timely manner. We increased database request processing capability, redeployed the affected encryption and decryption service used by RMS, and reallocated traffic within the region to restore service functionality and resolve the impact.
Scope of impact: This issue may have affected any North America user of RMS trying to send encrypted email.
Start time: Monday, January 5, 2026, at 3:02 PM UTC
End time: Monday, January 5, 2026, at 6:12 PM UTC
Root cause: A large increase in requests for RMS encryption and decryption following an extended low traffic period due to December holidays resulted in resource throttling and this impact, as our processing resiliency didn't adapt in a timely manner.
Next steps: - We're reviewing our traffic throttling enforcement mechanisms following extended low-volume periods to protect users from similar future impact.
This is the final update for the event.
Time:Mon Jan 5 13:20:47 2026
Description:Title: Users may be unable to send encrypted email
User impact: Users may be unable to send encrypted email.
More info: Users receive a Non-Delivery Report (NDR) with an exception message of "Failed to bootstrap tenant."
Current status: We've identified an issue with an encryption and decryption service used by Rights Management Service (RMS) and are implementing a fix that we expect will address the issue. We'll provide more details on the problem and fix in our subsequent communication update.
Scope of impact: This issue may affect any North America user of RMS trying to send encrypted email.
Next update by: Monday, January 5, 2026, at 8:00 PM UTC
Time:Mon Jan 5 12:35:23 2026
Description:Title: Users can't send encrypted email
User impact: Users can't send encrypted email.
More info: Users receive a Non-Delivery Report (NDR) with an exception message of "Failed to bootstrap tenant."
Current status: We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 60 minutes.

EX1193588 - Users may be unable to upload attachments from Microsoft OneDrive in Outlook on the web and the new Outlook desktop app

Status:serviceRestored
Start Time:Tue Oct 7 13:12:00 2025
End Time:Mon Dec 22 12:00:00 2025
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Mon Jan 5 15:30:56 2026
Root Cause:A recent .NET framework update intended to improve performance for users introduced a misconfiguration, which caused an extremely large increase in requests from Outlook on the web when retrieving the OneDrive URL. This increase in traffic resulted in request queuing, timeouts, and throttling as a service protection measure, which caused impact.
Next Update:N/A

Details

Time:Mon Dec 29 12:32:43 2025
Description:Title: Users may be unable to upload attachments from Microsoft OneDrive in Outlook on the web and the new Outlook desktop app
User impact: Users may have been unable to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app.
More info: When users attempted to upload files from OneDrive, they may have received an error that stated: “We couldn’t retrieve the items you requested.” Additionally, the option to edit files in the browser was missing.
Final status: We've confirmed that the fix has completed releasing to all affected environments and validated this has remediated this issue using service telemetry.
Scope of impact: Any user attempting to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app may have been impacted.
Start time: Tuesday, October 7, 2025, at 5:12 PM UTC
End time: Monday, December 22, 2025, at 5:00 PM UTC
Root cause: A recent .NET framework update intended to improve performance for users introduced a misconfiguration, which caused an extremely large increase in requests from Outlook on the web when retrieving the OneDrive URL. This increase in traffic resulted in request queuing, timeouts, and throttling as a service protection measure, which caused impact.
Next steps: - We're continuing our analysis of the impacting .NET update to better identify and prevent similar issues in the future.
This is the final update for the event.
Time:Mon Dec 15 15:09:39 2025
Description:Title: Users may be unable to upload attachments from Microsoft OneDrive in Outlook on the web and the new Outlook desktop app
User impact: Users may be unable to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app.
More info: When users attempt to upload files from OneDrive, they may receive an error that states: “We couldn’t retrieve the items you requested.” Additionally, the option to edit files in the browser is missing.
Current status: Our deployment of a secondary fix to further improve traffic processing efficiency has progressed slower than initially anticipated, and we now expect deployment to be completed by Monday, December 29, 2025. This will allow us at that time to validate with a subset of affected users if impact is resolved.
Scope of impact: Any user attempting to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app may be impacted.
Start time: Wednesday, November 26, 2025, at 5:27 PM UTC
Root cause: A recent .NET framework update intended to improve performance for users introduced a misconfiguration, which is resulting in an extremely large increase in requests from Outlook on the web when retrieving the OneDrive URL. This increase in traffic is resulting in request queuing, timeouts, and throttling as a service protection measure, which is causing impact.
Next update by: Monday, December 29, 2025, at 9:30 PM UTC
Time:Wed Dec 10 14:57:12 2025
Description:Title: Users may be unable to upload attachments from Microsoft OneDrive in Outlook on the web and the new Outlook desktop app
User impact: Users may be unable to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app.
More info: When users attempt to upload files from OneDrive, they may receive an error that states: “We couldn’t retrieve the items you requested.” Additionally, the option to edit files in the browser is missing.
Current status: We've isolated that a recent .NET framework update intended to improve performance for users in India introduced a misconfiguration, which is resulting in an extremely large increase in requests from Outlook on the web when retrieving the OneDrive URL. This increase in traffic is resulting in request queuing and timeouts as well as throttling as a service protection measure and causing impact. We've rolled back the update and are deploying a secondary fix to further improve the traffic processing efficiency for this scenario to fully mitigate impact. We anticipate deployment will complete by our next scheduled update, which will allow us to test for impact resolution at that time.
Scope of impact: Any user in India attempting to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app may be impacted.
Start time: Wednesday, November 26, 2025, at 5:27 PM UTC
Root cause: A recent .NET framework update intended to improve performance for users in India introduced a misconfiguration, which is resulting in an extremely large increase in requests from Outlook on the web when retrieving the OneDrive URL. This increase in traffic is resulting in request queuing and timeouts as well as throttling as a service protection measure and causing impact.
Next update by: Monday, December 15, 2025, at 9:30 PM UTC
Time:Tue Dec 9 18:04:20 2025
Description:Title: Users may be unable to upload attachments from Microsoft OneDrive in Outlook on the web and the new Outlook desktop app
User impact: Users may be unable to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app.
More info: When users attempt to upload files from OneDrive, they may receive an error that states: “We couldn’t retrieve the items you requested.” Additionally, the option to edit files in the browser is missing.
Current status: Our initial analysis into Outlook service logging has isolated a processing restriction for calls between Outlook on the web and OneDrive. We're further analyzing this restriction to confirm if it's the source for this event, and to determine our next steps for remediating the impact.
Scope of impact: Any user in India attempting to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app may be impacted.
Next update by: Wednesday, December 10, 2025, at 9:30 PM UTC
Time:Tue Dec 9 11:45:43 2025
Description:Title: Users may be unable to upload attachments from Microsoft OneDrive in Outlook on the web and the new Outlook desktop app
User impact: Users may be unable to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app.
More info: When users attempt to upload files from OneDrive, they may receive an error that states: “We couldn’t retrieve the items you requested.” Additionally, the option to edit files in the browser is missing.
Current status: Our findings from the provided HAR logs remain inconclusive. We've enabled additional Outlook service logging on the service side to aid us in collecting additional data that will help us isolate the root cause.
Scope of impact: Any user in India attempting to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app may be impacted.
Next update by: Wednesday, December 10, 2025, at 12:30 AM UTC
Time:Tue Dec 9 09:57:36 2025
Description:Title: Users may be unable to upload attachments from Microsoft OneDrive in Outlook on the web and the new Outlook desktop app
User impact: Users may be unable to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app.
More info: When users attempt to upload files from OneDrive, they may receive an error that states: “We couldn’t retrieve the items you requested.” Additionally, the option to edit files in the browser is missing.
Current status: We’re reviewing HTTP Archive (HAR) files alongside API call patterns to help identify the root cause and next steps required to mitigate impact.
Scope of impact: Any user in India attempting to upload attachments from OneDrive in Outlook on the web and the new Outlook desktop app may be impacted.
Next update by: Tuesday, December 9, 2025, at 5:00 PM UTC

OO1202986 - Some users may have been intermittently unable to "Create a Copy" of files in Microsoft 365 apps for the web

Status:serviceRestored
Start Time:Tue Dec 9 19:00:00 2025
End Time:Mon Dec 29 08:30:00 2025
Service:Microsoft 365 for the web
Feature Group:Excel Online
Classification:advisory
Last Updated:Mon Dec 29 09:46:38 2025
Root Cause:A recent deployment to the Word web experience introduced a compatibility issue between various Microsoft 365 apps for the web and was preventing the "Create a Copy" function from working as expected.
Next Update:N/A

Details

Time:Mon Dec 29 09:46:38 2025
Description:Title: Some users may have been intermittently unable to "Create a Copy" of files in Microsoft 365 apps for the web
User impact: Users may have been intermittently unable to "Create a Copy" of files in Microsoft 365 apps for the web.
More info: This issue specifically affected the “Create a Copy” function when users selected an online save location that differed from the default location in Microsoft Word, Microsoft PowerPoint, and Microsoft Excel for the web.
Users encountered the error, “Copy could not be created… There was a problem creating a copy of this file. Please try again in some time.”
The impact was intermittent and retry attempts may have been successful.
As a workaround, users could open Microsoft OneDrive, navigate to the Files list, and use “Copy to” to create a duplicate.
Final status: We’ve confirmed that deployment of the Microsoft PowerPoint fix is complete, and our monitoring shows no further occurrences of the issue. Users who are running an older version of the application may still experience the issue; restarting PowerPoint will ensure they receive the updated build that contains the fix.
Scope of impact: Some users that are using the "Create a Copy" function in the Microsoft 365 apps for the web may have been impacted intermittently.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
End time: Monday, December 29, 2025, at 1:30 PM UTC
Root cause: A recent deployment to the Word web experience introduced a compatibility issue between various Microsoft 365 apps for the web and was preventing the "Create a Copy" function from working as expected.
Next steps: - We're reviewing our deployment procedures to help prevent similar problems in the future.
This is the final update for the event.
Time:Sun Dec 28 21:06:58 2025
Description:Title: Some users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps
User impact: Users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps.
More info: This issue specifically affects use of the create a copy online function and choosing a location that differs from the default location on Microsoft Word, Microsoft PowerPoint, and Microsoft Excel web apps. Users encounter an error that states, "Copy could not be created...There was a problem creating a copy of this file. Please try again in some time." Impact is intermittent and retries may be successful.
To avoid this issue, users can access Microsoft OneDrive and navigate to the files list, then click "Copy to" to create a copy; but if users open a file as a Word document and attempt to create a copy from it, it may fail.
Current status: We're continuing to monitor the Microsoft PowerPoint fix to ensure that it completes deployment successfully.
Scope of impact: Some users that are using the "Create a Copy" function in Microsoft 365 for the web apps may be intermittently impacted. This information may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Root cause: A recent deployment to the Word web experience introduced a compatibility issue between various Microsoft 365 for the web apps and is preventing the "Create a Copy" functionality from working as expected.
Next update by: Monday, December 29, 2025, at 3:00 PM UTC
Time:Sat Dec 27 21:40:36 2025
Description:Title: Some users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps
User impact: Users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps.
More info: This issue specifically affects use of the create a copy online function and choosing a location that differs from the default location on Microsoft Word, Microsoft PowerPoint, and Microsoft Excel web apps. Users encounter an error that states, "Copy could not be created...There was a problem creating a copy of this file. Please try again in some time." Impact is intermittent and retries may be successful.
To avoid this issue, users can access Microsoft OneDrive and navigate to the files list, then click "Copy to" to create a copy; but if users open a file as a Word document and attempt to create a copy from it, it may fail.
Current status: Our fix to address Microsoft Excel on the web app impact has completed deployment and we’ve observed from our service telemetry that the errors have reduced to zero, confirming impact is remediated. In parallel, the Microsoft PowerPoint fix is progressing through the final stages of deployment and we anticipate that this deployment process will complete by the end of Monday, December 29, 2025.
Scope of impact: Some users that are using the "Create a Copy" function in Microsoft 365 for the web apps may be intermittently impacted. This information may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Root cause: A recent deployment to the Word web experience introduced a compatibility issue between various Microsoft 365 for the web apps and is preventing the "Create a Copy" functionality from working as expected.
Next update by: Monday, December 29, 2025, at 4:00 AM UTC
Time:Wed Dec 24 21:29:13 2025
Description:Title: Some users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps
User impact: Users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps.
More info: This issue specifically affects use of the create a copy online function and choosing a location that differs from the default location on Microsoft Word, Microsoft PowerPoint, and Microsoft Excel web apps. Users encounter an error that states, "Copy could not be created...There was a problem creating a copy of this file. Please try again in some time." Impact is intermittent and retries may be successful.
To avoid this issue, users can access Microsoft OneDrive and navigate to the files list, then click "Copy to" to create a copy; but if users open a file as a Word document and attempt to create a copy from it, it may fail.
Current status: We've completed the deployment of our fix for the impact manifesting within the Microsoft Word on the web app. We're finalizing our fix deployment for Microsoft PowerPoint and Microsoft Excel, and we're anticipating impact may be fully remediated by the time of our next scheduled update, at which point we'll verify recovery through our internal telemetry.
Scope of impact: Some users that are using the "Create a Copy" function in Microsoft 365 for the web apps may be intermittently impacted. This information may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Root cause: A recent deployment to the Word web experience introduced a compatibility issue between various Microsoft 365 for the web apps and is preventing the "Create a Copy" functionality from working as expected.
Next update by: Sunday, December 28, 2025, at 4:00 AM UTC
Time:Tue Dec 23 21:20:14 2025
Description:Title: Some users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps
User impact: Users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps.
More info: This issue specifically affects use of the create a copy online function and choosing a location that differs from the default location. Users encounter an error that states, "Copy could not be created...There was a problem creating a copy of this file. Please try again in some time." Impact is intermittent and retries may be successful.
To avoid this issue, users can access Microsoft OneDrive and navigate to the files list, then click "Copy to" to create a copy; but if users open a file as a Word document and attempt to create a copy from it, it may fail.
Current status: We've begun deploying a set of code fixes that we're anticipating should resolve the impact within the Microsoft Word and Microsoft PowerPoint web apps. We're aiming to fully deploy these fixes by the time of our next scheduled update, and we'll provide a timeline for full remediation across the remaining impacted web apps as it becomes available.
Scope of impact: Some users that are using the "Create a Copy" function in Microsoft 365 for the web apps may be intermittently impacted. This information may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Root cause: A recent deployment to the Word web experience introduced a compatibility issue between various Microsoft 365 for the web apps and is preventing the "Create a Copy" functionality from working as expected.
Next update by: Thursday, December 25, 2025, at 4:00 AM UTC
Time:Mon Dec 22 22:04:40 2025
Description:Title: Users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps
User impact: Users may be unable to intermittently "Create a Copy" of files in Microsoft 365 for the web apps.
More info: This issue specifically affects use of the create a copy online function and choosing a location that differs from the default location. Users encounter an error that states, "Copy could not be created...There was a problem creating a copy of this file. Please try again in some time." Impact is intermittent and retries may be successful.
To avoid this issue, users can access Microsoft OneDrive and navigate to the files list, then click "Copy to" to create a copy; but if users open a file as a Word document and attempt to create a copy from it, it may fail.
Current status: We've identified a recent deployment to the Word web experience introduced a compatibility issue between various Microsoft 365 for the web apps and is preventing the "Create a Copy" functionality from working as expected. We're further reviewing the offending code to help develop a remediation plan which may consist of rolling back the deployment or creating a new code change.
Scope of impact: Some users that are using the "Create a Copy" function in Microsoft 365 for the web apps may be intermittently impacted. This information may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
Root cause: A recent deployment to the Word web experience introduced a compatibility issue between various Microsoft 365 for the web apps and is preventing the "Create a Copy" functionality from working as expected.
Next update by: Wednesday, December 24, 2025, at 4:00 AM UTC
Time:Mon Dec 22 19:00:02 2025
Description:Title: Users can't "Create a Copy" of files in Microsoft 365 for the web apps
User impact: Users can't "Create a Copy" of files in Microsoft 365 for the web apps.
More info: This issue specifically affects use of the create a copy online function and choosing a location that differs from the default location. Users encounter an error that states, "Copy could not be created...There was a problem creating a copy of this file. Please try again in some time."
Current status: We've collected diagnostic data for a session that encountered this error and are investigating the point of failure, which will direct us towards our next steps for identifying the cause of the problem and a solution.
Scope of impact: Your organization is affected by this event, and this issue affects users of the "Create a Copy" function in Microsoft 365 for the web apps. This information may be updated as our investigation continues.
Next update by: Tuesday, December 23, 2025, at 3:30 AM UTC
Time:Mon Dec 22 18:04:50 2025
Description:Title: Users can't "Create a Copy" of files in Microsoft 365 for the web apps
User impact: Users can't "Create a Copy" of files in Microsoft 365 for the web apps.
More info: This issue specifically affects use of the create a copy online function and choosing a location that differs from the default location. Users encounter an error that states, "Copy could not be created...There was a problem creating a copy of this file. Please try again in some time."
Current status: We're investigating a potential issue with Microsoft 365 for the web and checking for impact to your organization. We'll provide an update within 60 minutes.

SP1196502 - Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API

Status:serviceRestored
Start Time:Wed Dec 3 08:47:00 2025
End Time:Mon Dec 22 15:00:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Fri Dec 26 13:30:27 2025
Root Cause:A recent standard update to the service wasn’t properly deployed and was preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next Update:N/A

Details

Time:Fri Dec 26 13:29:50 2025
Description:Title: Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may have been unable to retrieve email addresses using the SharePoint Online CSOM API.
Final status: We've completed deployment throughout all affected environments and after monitoring the service, we've verified that this action has successfully remediated the problem.
Scope of impact: Any user attempting to retrieve email addresses via the SharePoint Online CSOM API may have been impacted.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
End time: Monday, December 22, 2025, at 8:00 PM UTC
Root cause: A recent standard update to the service wasn’t properly deployed and was preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next steps: - We're investigating how the recent standard update to the service wasn’t properly deployed and was preventing users from retrieving email addresses using the SharePoint Online CSOM API to prevent this problem from happening again.
This is the final update for the event.
Time:Mon Dec 22 13:55:15 2025
Description:Title: Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve email addresses using the SharePoint Online CSOM API.
Current status: Our deployment has saturated across 90% of affected environments and we're continuing to monitor for remediation as our deployment progresses.
Scope of impact: Any user attempting to retrieve email addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
Root cause: A recent standard update to the service wasn’t properly deployed and is preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next update by: Friday, December 26, 2025, at 8:00 PM UTC
Time:Fri Dec 19 13:23:42 2025
Description:Title: Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve email addresses using the SharePoint Online CSOM API.
Current status: We've started deploying the code fix, which has currently saturated 63 percent of the impacted environments. We expect users will experience remediation incrementally while the deployment progresses.
Scope of impact: Any user attempting to retrieve email addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
Root cause: A recent standard update to the service wasn’t properly deployed and is preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next update by: Monday, December 22, 2025, at 8:00 PM UTC
Time:Thu Dec 18 20:46:19 2025
Description:Title: Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve email addresses using the SharePoint Online CSOM API.
Current status: We've completed our validations and testing of our newly developed code fix and are preparing its deployment to all impacted environments. Additionally, we anticipate that the deployment will have taken place prior to our next scheduled update, at which point we’re aiming to gather a remediation timeline to be provided by our next scheduled communication update.
Scope of impact: Any user attempting to retrieve email addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
Root cause: A recent standard update to the service wasn’t properly deployed and is preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next update by: Friday, December 19, 2025, at 8:00 PM UTC
Time:Wed Dec 17 13:38:03 2025
Description:Title: Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve email addresses using the SharePoint Online CSOM API.
Current status: We've completed our validations and testing of our newly developed code fix and are preparing its deployment to all impacted environments. We'll actively monitor this deployment to ensure that it results in relief from this impact as expected. We’ll provide an update on the status of this deployment by our next scheduled communication.
Scope of impact: Any user attempting to retrieve email addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
Root cause: A recent update to the service is preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next update by: Friday, December 19, 2025, at 8:00 PM UTC
Time:Tue Dec 16 20:24:32 2025
Description:Title: Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve email addresses using the SharePoint Online CSOM API.
Current status: We're conducting additional validations and testing on our newly developed code fix to ensure it successfully remediates impact. Once complete, we'll then prepare to deploy the change to all impacted environments. We'll provide an estimate timeline for completion once one becomes available. In parallel, we're continuing to monitor the previously executed revert process; however, this is taking much longer than expected to complete.
Scope of impact: Any user attempting to retrieve email addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
Root cause: A recent update to the service is preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next update by: Wednesday, December 17, 2025, at 8:00 PM UTC
Time:Tue Dec 16 18:01:40 2025
Description:Title: Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve email addresses using the SharePoint Online CSOM API.
Current status: As we continue our efforts to revert the offending service update, we're preparing to deploy our code fix which is expected to remediate the impact. We'll provide an estimate for our mitigations and the remediation of impact once our deployment has begun and the timeline becomes available.
Scope of impact: Any user attempting to retrieve email addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
Root cause: A recent update to the service is preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next update by: Wednesday, December 17, 2025, at 1:30 AM UTC
Time:Tue Dec 16 16:25:25 2025
Description:Title: Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve email addresses using the SharePoint Online CSOM API.
Current status: The process of reverting the offending service update is progressing though taking longer than ideal to complete. To ensure we're addressing the problem as quickly as possible, we're also developing and subsequently deploying a code fix. Both solutions are viable and whichever completes first will successfully remediate the impact.
Scope of impact: Any user attempting to retrieve email addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
Root cause: A recent update to the service is preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next update by: Tuesday, December 16, 2025, at 11:30 PM UTC
Time:Tue Dec 16 13:45:41 2025
Description:Title: Some users may be unable to retrieve email addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve email addresses using the SharePoint Online CSOM API.
Current status: Our additional analysis has isolated a recent update to the service that's preventing users from retrieving email addresses using the SharePoint Online CSOM API. As we further review the impacting update, we're conducting our change reversion process to remove the recent service update and remediate the impact.
Scope of impact: Any user attempting to retrieve email addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
Root cause: A recent update to the service is preventing users from retrieving email addresses using the SharePoint Online CSOM API.
Next update by: Tuesday, December 16, 2025, at 9:30 PM UTC
Time:Tue Dec 16 04:38:23 2025
Description:Title: Some users may be unable to retrieve e-mail addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve e-mail addresses using the SharePoint Online CSOM API.
Current status: We’re continuing our investigation into the underlying cause of the issue and assessing next steps for mitigation.
Scope of impact: Users attempting to retrieve e-mail addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Next update by: Tuesday, December 16, 2025, at 7:30 PM UTC
Time:Tue Dec 16 01:37:21 2025
Description:Title: Some users may be unable to retrieve e-mail addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve e-mail addresses using the SharePoint Online CSOM API.
Current status: We've successfully reproduced the issue within our internal testing environment to gather additional data and trace logging from the impacted API flow. We're proceeding with further analysis to gain insight into the root cause and determine our options for remediation.
Scope of impact: Users attempting to retrieve e-mail addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Next update by: Tuesday, December 16, 2025, at 11:00 AM UTC
Time:Mon Dec 15 20:45:54 2025
Description:Title: Some users may be unable to retrieve e-mail addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve e-mail addresses using the SharePoint Online CSOM API.
Current status: We're continuing our effort to reproduce the issue within an internal testing environment that we're anticipating will allow us to better understand the underlying source of impact and inform our next steps.
Scope of impact: Users attempting to retrieve e-mail addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Next update by: Tuesday, December 16, 2025, at 7:00 AM UTC
Time:Mon Dec 15 19:00:57 2025
Description:Title: Some users may be unable to retrieve e-mail addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve e-mail addresses using the SharePoint Online CSOM API.
Current status: Our initial reproduction of this event doesn't allow us to gather the analytical data needed to review the calls made by the API that retrieves user email information. We're attempting an alternate reproduction method to gather the data we need to identify the root cause and a strategy that remediates impact.
Scope of impact: Users attempting to retrieve e-mail addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Next update by: Tuesday, December 16, 2025, at 3:30 AM UTC
Time:Mon Dec 15 17:02:29 2025
Description:Title: Some users may be unable to retrieve e-mail addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve e-mail addresses using the SharePoint Online CSOM API.
Current status: We've reproduced the issue internally to help analyze calls made by the API that retrieves user email information to isolate potential discrepancies that may contribute to impact, which will help determine our next troubleshooting steps.
Scope of impact: Users attempting to retrieve e-mail addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Next update by: Tuesday, December 16, 2025, at 12:00 AM UTC
Time:Mon Dec 15 11:22:04 2025
Description:Title: Some users may be unable to retrieve e-mail addresses using the SharePoint Online Client Side Object Model (CSOM) API
User impact: Users may be unable to retrieve e-mail addresses using the SharePoint Online CSOM API.
Current status: We’re analyzing calls made by the specific API utilized when retrieving user email information to isolate potential discrepancies pointing to why this information isn’t being sent to SharePoint Online, which will determine our next troubleshooting steps.
Scope of impact: Users attempting to retrieve e-mail addresses via the SharePoint Online CSOM API may be impacted. This section may be updated as the investigation progresses.
Next update by: Monday, December 15, 2025, at 10:00 PM UTC
Time:Mon Dec 15 07:53:08 2025
Description:Title: Some users may be unable to retrieve e-mail addresses using the SharePoint Online CSOM API
User impact: Users may be unable to retrieve e-mail addresses using the SharePoint Online CSOM API.
Current status: We’re working to identify the change that caused user email information to be missing when retrieving data from SharePoint Online.
Scope of impact: Users attempting to retrieve e-mail addresses via the SharePoint Online CSOM API may be impacted.
Next update by: Monday, December 15, 2025, at 4:30 PM UTC
Time:Mon Dec 15 05:40:23 2025
Description:Title: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected
User impact: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected.
Current status: We’ve successfully reproduced the issue and have determined that the expected user email information is missing when retrieving data from SharePoint Online. We’re reviewing log files to identify the root cause of the issue.
Scope of impact: Your organization is affected by this event, and users attempting to access some SharePoint Online sites are impacted. This information may be updated as our investigation continues.
Next update by: Monday, December 15, 2025, at 1:00 PM UTC
Time:Mon Dec 15 02:18:50 2025
Description:Title: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected
User impact: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected.
Current status: We're continuing to wait for your representatives to provide fresh logs from reproducing the issue to aid in the root cause investigation.
Scope of impact: Your organization is affected by this event, and users attempting to access some SharePoint Online sites are impacted. This information may be updated as our investigation continues.
Next update by: Monday, December 15, 2025, at 11:00 AM UTC
Time:Mon Dec 15 00:25:14 2025
Description:Title: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected
User impact: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected.
Current status: Our analysis into the correlation IDs has been inconclusive. We're reaching out to your representatives requesting fresh HTTP Archive format (HAR) files from users reproducing the issue to help with our investigation.
Scope of impact: Your organization is affected by this event, and users attempting to access some SharePoint Online sites are impacted. This information may be updated as our investigation continues.
Next update by: Monday, December 15, 2025, at 8:00 AM UTC
Time:Sun Dec 14 22:23:13 2025
Description:Title: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected
User impact: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected.
Current status: We're continuing to investigate the correlation IDs of some users that are impacted to help with isolating the source of the issue.
Scope of impact: Your organization is affected by this event, and users attempting to access some SharePoint Online sites are impacted. This information may be updated as our investigation continues.
Next update by: Monday, December 15, 2025, at 5:30 AM UTC
Time:Sun Dec 14 21:25:08 2025
Description:Title: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected
User impact: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected.
Current status: We're reviewing correlation IDs of some users that are impacted to help with the investigation and to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and users attempting to access some SharePoint Online sites are impacted. This information may be updated as our investigation continues.
Next update by: Monday, December 15, 2025, at 3:30 AM UTC
Time:Sun Dec 14 20:59:06 2025
Description:Title: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected
User impact: Users can't access some SharePoint Online sites and see that multiple applications can't be used as expected.
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.

EX1183224 - Some users may have been unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online

Status:serviceRestored
Start Time:Wed Oct 22 10:12:00 2025
End Time:Wed Dec 24 08:42:00 2025
Service:Exchange Online
Feature Group:Management and Provisioning
Classification:advisory
Last Updated:Fri Dec 26 09:33:16 2025
Root Cause:A recent backend change caused some add‑in management requests to fail, resulting in cached data becoming inconsistent and add‑ins appearing unavailable.
Next Update:N/A

Details

Time:Fri Dec 26 09:23:56 2025
Description:Title: Some users may have been unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may have been unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
Final status: We've identified that a recent backend change caused add‑in management requests to fail, resulting in inconsistent cached data and add‑ins appearing unavailable for some users. We've rolled back the change and refreshed the affected cached data to restore normal add‑in availability, and confirmed with some impacted users that this has successfully remediated the issue.
Scope of impact: The problem impacted some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Start time: Wednesday, October 22, 2025, at 2:12 PM UTC
End time: Wednesday, December 24, 2025, at 1:42 PM UTC
Root cause: A recent backend change caused some add‑in management requests to fail, resulting in cached data becoming inconsistent and add‑ins appearing unavailable.
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 Dec 24 09:17:46 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We’ve confirmed that the cache reset is nearly complete, and some impacted users have validated that this is successfully mitigating the issue. We expect this process to be completed by our next scheduled update.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Estimated time to resolve: Friday, December 26, 2025
Next update by: Friday, December 26, 2025, at 2:30 PM UTC
Time:Tue Dec 23 08:03:44 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: Our efforts to clear the cache is ongoing and expected to be completed by our next scheduled update. Whilst the clearing of the cache is progressing, we're continuing with our investigation into the internal server error that occurs during the validation process.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, December 24, 2025, at 2:30 PM UTC
Time:Fri Dec 19 11:20:31 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While we continue to investigate the internal server error occurring during our validation process, our efforts to clear the cached data for affected users is taking longer than initially anticipated. We expect that clearing the cache will restore access to the My Templates and Viva Insights Outlook and confirm our theory that the aforementioned error is the root cause. We'll provide a timeline for the completion of this as one becomes available.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, December 23, 2025, at 2:30 PM UTC
Time:Thu Dec 18 15:00:34 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We've continuing to analyze and dissect the internal error we suspect is the root cause of impact to determine our next troubleshooting actions. Simultaneously, we're working with a subset of affected users to validate if clearing the cache mitigates impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, December 19, 2025, at 5:30 PM UTC
Time:Wed Dec 17 15:06:33 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While we await reports from a subset of affected users regarding the cache clearing action, we're continuing to analyze the internal error which we suspect is the root cause of the impact to determine what's causing it. In parallel, we're reviewing changes which correlate with the impact timeline to determine whether there are any which could have introduced the error.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, December 18, 2025, at 9:00 PM UTC
Time:Wed Dec 17 10:08:24 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We’ve cleared the cached data for the affected users, though it’s not yet confirmed whether this will fully mitigate impact. Our investigation is ongoing, and we’re working to pinpoint what introduced the internal error so we can better understand the root cause and identify the most effective mitigation path.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, December 17, 2025, at 9:30 PM UTC
Time:Tue Dec 16 09:23:01 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We’ve identified that an internal error occurring during our validation process is likely contributing to the issue. As a mitigation step, we’re working to clear cached data for the affected users to help restore normal functionality. We’re still determining what introduced this error and will provide further updates as more information becomes available.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, December 17, 2025, at 3:30 PM UTC
Time:Mon Dec 15 10:13:24 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: Whilst we analyze the information in order to better understand the root cause, we can confirm that impact is specific to a select few affected. We're working to understand how many users are impacted and expect to have a better understanding by our next scheduled update.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, December 16, 2025, at 3:30 PM UTC
Time:Wed Dec 10 10:22:44 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: Whilst we're continuing to analyze the information in order to better understand the root cause, we can confirm that impact is specific to a select few affected. We're working to understand how many users are impacted and expect to have a better understanding by our next scheduled update.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Monday, December 15, 2025, at 3:30 PM UTC
Time:Wed Dec 10 03:24:30 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We've received the required HAR trace and information regarding whether the remaining affected users issues are linked to the aforementioned deployment. We're analysing the information and expect to have a better understanding of the root cause by our next scheduled update.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, December 10, 2025, at 3:30 PM UTC
Time:Wed Dec 10 01:29:01 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing our collaborative efforts with representatives to determine whether the remaining affected users issues are linked to the aforementioned deployment. Additionally, we’re awaiting confirmation from your support case owners on whether the HAR trace log for Outlook on the web has been collected so we can proceed with our root case analysis and subsequent troubleshooting steps.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, December 10, 2025, at 9:30 AM UTC
Time:Tue Dec 9 06:05:51 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're collaborating with representatives to determine whether the remaining affected users issues are linked to the deployment. As part of this investigation, we have requested that they install the relevant add-in and provide two or three additional email addresses experiencing the problem, along with HTTP Archive (HAR) trace for Outlook on the web. This information will enable us to isolate the root cause and formulate an effective mitigation plan.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, December 10, 2025, at 7:00 AM UTC
Time:Tue Dec 9 00:11:14 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're proceeding with further analysis of the API flow involved with the impacted add-ins to identify why a subset of users are continuing to see some instances of impact and determine our next steps.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, December 9, 2025, at 12:00 PM UTC
Time:Mon Dec 8 16:58:37 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While we've received confirmation from some users that the impact is remediated, we've received reports from a portion of affected users that the impact persists. We're continuing to check the sync status of the add-in data with Exchange Online to confirm whether the data is being synced as expected.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, December 9, 2025, at 4:30 AM UTC
Time:Fri Dec 5 17:53:47 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We've identified that the missing Templates and Viva Insights add-ins data were synced to Exchange Online. We recommend clearing the cache, refreshing the browser data, and providing the results with our representatives to validate if the synced data has remediated impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Monday, December 8, 2025, at 11:00 PM UTC
Time:Fri Dec 5 13:02:24 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We've gathered additional HAR captures of the event in progress and our analysis indicates that a component that facilitates My Templates and Viva Insights add-ins for Exchange Online isn't getting data from an upstream source. We're expanding our analysis to include logs from the data pipeline that we believe responsible for impact to confirm this as the root cause and develop a remediation strategy.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, December 5, 2025, at 10:00 PM UTC
Time:Thu Dec 4 17:01:33 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing our investigation of the HAR logs to determine why our previous fix didn't remediate impact for all users as expected.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, December 5, 2025, at 6:00 PM UTC
Time:Thu Dec 4 15:52:36 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We've identified that the affected add-ins should be available to affected users, according to the HAR logs, but we haven't yet identified why the remaining users still don't have access. We're continuing our investigation of the HAR logs to determine why our previous fix didn't remediate impact for all users as expected.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, December 5, 2025, at 12:00 AM UTC
Time:Thu Dec 4 13:00:05 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: It's taking longer than expected, but our investigation of the HAR logs continues in our attempt to determine why our previous fix didn't resolve this issue and a method of completely remediating impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, December 4, 2025, at 9:00 PM UTC
Time:Wed Dec 3 14:36:01 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing our review of the HAR logs to determine why our recent Admin API change reversion didn't completely resolve this issue.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, December 4, 2025, at 6:00 PM UTC
Time:Wed Dec 3 12:59:08 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We've collected fresh HTTP Archive format (HAR) from a small subset of users who continue to report impact and we're reviewing this data to determine why our recent Admin API change reversion didn't completely resolve this issue.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, December 3, 2025, at 8:00 PM UTC
Time:Tue Dec 2 12:40:28 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing to collect fresh diagnostic network data from the small subset of users who continue to report impact to determine why our recent Admin API change reversion hasn't remediated the impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, December 3, 2025, at 6:00 PM UTC
Time:Mon Dec 1 12:07:56 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While we've gotten verification from some affected users that impact is resolved, we've also been informed there is a small number of users who are still unable to access the My Templates add-in. We're requesting fresh data from these affected users to determine why the impact persists.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, December 2, 2025, at 6:00 PM UTC
Time:Tue Nov 25 12:47:39 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While we continue to review the provided Graph Explorer data and PowerShell outputs for Organization apps and add-ins to isolate the source of the cache issue, we've rolled back the offending Admin API change to mitigate impact. We're reaching out to a subset of affected users to validate if this action successfully resolved impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Monday, December 1, 2025, at 6:00 PM UTC
Time:Mon Nov 24 10:16:37 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing to review the provided Graph Explorer data and PowerShell outputs for Organization apps and add-ins to help us isolate the source of the mailbox cache issue.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, November 25, 2025, at 7:00 PM UTC
Time:Fri Nov 21 17:27:13 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're reviewing the provided Graph Explorer data and PowerShell outputs for Organization apps and add-ins to help us isolate the source of the mailbox cache issue.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Monday, November 24, 2025, at 4:00 PM UTC
Time:Fri Nov 21 15:19:06 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While we continue to review the code flows, we're requesting Graph Explorer data and PowerShell outputs for Organization apps and add-ins from a subset of reporting users to aid in our investigation.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, November 21, 2025, at 10:30 PM UTC
Time:Fri Nov 21 13:27:42 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing our efforts to pinpoint exactly which flow is causing the values to be missing or mismatched, so that we can determine a strategy to remediate the impact on a broad scale.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, November 21, 2025, at 8:30 PM UTC
Time:Thu Nov 20 12:04:26 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We’re continuing to analyze the recent offending change to the Admin API, to pinpoint the code in the recent change that's resulting in the cache problem, as this data will aid us in determining our next steps to resolve impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, November 21, 2025, at 6:30 PM UTC
Time:Wed Nov 19 13:33:22 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We've validated that the recent change to the Admin API is causing a mismatch in the data format of users' mailbox cache and is resulting in this issue. We're pinpointing the code in recent change that's resulting in the cache problem as this data will aid us in determining our next steps to resolve impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 20, 2025, at 6:30 PM UTC
Time:Wed Nov 19 06:31:12 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We’re suspecting that a recent change in Admin API may be causing a cache corruption in user mailboxes, leading to missing add-ins across multiple clients. We're reverting the change to validate our theory and are conducting in depth analysis to identify the origin of cache corruption.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 19, 2025, at 7:30 PM UTC
Time:Tue Nov 18 05:07:15 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We’re currently validating the commands that your organization's admins can use to reset the impacted add-ins. We anticipate being able to share these commands by our next scheduled update.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 19, 2025, at 11:30 AM UTC
Time:Mon Nov 17 14:20:26 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: Further review of the HAR trace logs confirmed that both add-ins are syncing within Exchange Online as expected. While we continue to review the HAR trace logs to progress our root cause investigation, we're preparing a set of commands that can be run by your organization's admins to reset both of the impacted add-ins, which has proven successful in remediating similar instances of impact in the past. We'll aim to provide a timeline for the commands to be prepared and validated by our next scheduled communications update.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, November 18, 2025, at 11:30 AM UTC
Time:Fri Nov 14 13:56:53 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We believe that the My Templates and Viva Insights Outlook add-ins may not have been properly synced in Exchange Online, resulting in impact. We're reviewing the sync process for these add-ins to substantiate this theory and identify a fix that remediates impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Monday, November 17, 2025, at 8:30 PM UTC
Time:Thu Nov 13 13:05:17 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: Our comparative analysis of HAR trace logs from affected and unaffected users is ongoing and is an essential action to determine our next troubleshooting steps.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, November 14, 2025, at 7:30 PM UTC
Time:Wed Nov 12 17:58:11 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're conducting a deeper comparative analysis of HAR trace logs from affected and unaffected users to aid our root cause investigation. We're continuing to review possible temporary mitigation strategies to help restore functionality while we develop a permanent solution.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 13, 2025, at 7:30 PM UTC
Time:Wed Nov 12 16:27:47 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're continuing our comparative analysis of HAR trace logs from affected and unaffected users to aid our investigation into this issue's root cause. We're also reviewing possible temporary mitigation strategies to help restore functionality while we develop a permanent solution.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 12, 2025, at 11:30 PM UTC
Time:Wed Nov 12 14:30:27 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: We're reviewing HAR trace logs from affected and unaffected users for comparative analysis to identify this issue's root cause. We've confirmed that the set of commands we provided and attempted with a subset of impacted users was unsuccessful in alleviating impact, and we’re working to develop other possible remediation strategies while we continue this root cause investigation.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 12, 2025, at 9:30 PM UTC
Time:Tue Nov 11 13:28:25 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights Outlook add-ins in Exchange Online.
Current status: While our review of the request IDs and HAR trace from a subset of affected users is underway, we're requesting a HAR trace from an unaffected user for comparative analysis in an effort to identify the source of the impact.
Scope of impact: The problem impacts some users trying to access the My Templates and Viva Insights Outlook add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 12, 2025, at 7:30 PM UTC
Time:Mon Nov 10 16:46:46 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We've collected request IDs and a HTTP Archive format (HAR) trace from a subset of impacted users and we're analyzing the provided logging to isolate potential failures to determine our next troubleshooting steps.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Tuesday, November 11, 2025, at 7:30 PM UTC
Time:Fri Nov 7 16:31:43 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We've received feedback that the manifest file download and subsequent command execution didn't allow the deploy add-ins action as we had anticipated. We've requested that the subset of users who tested this action collect logs from another attempt so that we can analyze them and pinpoint the origin of this issue.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Monday, November 10, 2025, at 10:30 PM UTC
Time:Thu Nov 6 14:44:18 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: After restarting an affected user's mailbox, we've confirmed impact persists. We've provided the testing subset of users a manifest file to be downloaded and a command to be run afterwards, with the intent that these two will allow the deployment of add-ins as needed as our investigation into the root cause of the issue continues.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Friday, November 7, 2025, at 10:30 PM UTC
Time:Thu Nov 6 12:23:33 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We received confirmation that the series of commands didn't alleviate impact as expected. We're restarting an affected user's mailbox to see if this has any effect in remediating the impact while we continue to progress our investigation into the potential synchronization issue.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 9:30 PM UTC
Time:Thu Nov 6 09:54:23 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: Our investigation into a potential synchronization issue is still in progress. In parallel, we're collaborating with the aforementioned users to execute a series of commands that we expect will resolve the problem.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses
Next update by: Thursday, November 6, 2025, at 7:00 PM UTC
Time:Thu Nov 6 01:18:30 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: As we continue our investigation into whether a synchronization issue may be responsible for the impact, we’re reaching out to a subset of impacted users with a set of commands which we anticipate may resolve the issue.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 4:00 PM UTC
Time:Wed Nov 5 20:46:02 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: Our investigation into whether a synchronization issue may be responsible for the impact is ongoing. Better understanding of how the add-ins have been synced to the mailboxes will help streamline our next investigative actions and determine the best path toward remediation.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 7:30 AM UTC
Time:Wed Nov 5 19:28:15 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We don't expect that the issue is the result the add-in deployment process and we're moving forward with investigating whether a sync issue may be responsible for the impact and to determine our next steps towards expedient remediation.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 2:30 AM UTC
Time:Wed Nov 5 17:22:03 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We're observed a discrepancy in the number of add-ins present in the mailboxes experiencing this impact and the ones functioning as expected. We're investigating the deployment of these add-ins, through further analysis of the provided screenshots and screen recordings of impact, to uncover further details about root cause and determine next steps toward remediation.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Thursday, November 6, 2025, at 12:30 AM UTC
Time:Wed Nov 5 16:20:36 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We're investigating documentation of this impact including screenshots, logs, and error message details from a subset of impacted users to determine the next steps in our remediation.
Scope of impact: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online. This section may be updated as our investigation progresses.
Next update by: Wednesday, November 5, 2025, at 10:30 PM UTC
Time:Wed Nov 5 15:57:05 2025
Description:Title: Some users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online
User impact: Users may be unable to access the My Templates and Viva Insights add-ins in Exchange Online.
Current status: We're investigating a potential issue with Exchange Online and checking for impact. We'll provide an update within 30 minutes.

TM1200517 - Users are seeing Microsoft Teams messaging delays and problems with other service functions

Status:postIncidentReviewPublished
Start Time:Fri Dec 19 14:03:00 2025
End Time:Fri Dec 19 14:16:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Wed Dec 24 15:46:25 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Wed Dec 24 15:46:25 2025
Description:A post-incident report has been published.
Time:Tue Dec 23 18:50:36 2025
Description:A post-incident report has been published.
Time:Fri Dec 19 15:30:17 2025
Description:Title: Users are seeing Microsoft Teams messaging delays and problems with other service functions
User impact: Users may have seen Microsoft Teams messaging delays and problems with other service functions.
More info: Users may have seen delays with the following actions within any Microsoft Teams client: - Loading, creating, and editing chats and channels. - Sending and editing messages. - Loading images in chats and channels. - Initiating and transferring calls. - Viewing call history.
Final status: We've clarified the affected scenarios and enumerated them in the more info section above. We've continued to observe persistent recovery without any manual intervention required, and we've received confirmation from some previously affected users that this issue is no longer occurring.
Scope of impact: Any users served through an affected portion of Microsoft Teams service infrastructure may have seen delays completing the actions identified in the more info section of this communication.
Start time: Friday, December 19, 2025, at 7:03 PM UTC
End time: Friday, December 19, 2025, at 7:16 PM UTC
Preliminary root cause: A portion of Microsoft Teams infrastructure became imbalanced and wasn't processing traffic as efficiently as expected.
Next steps: - We're continuing a concerted analysis of the affected infrastructure to identify any trending traffic processing issues necessitating refinement so we can avoid a reoccurrence of this issue.
We’ll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Fri Dec 19 14:55:20 2025
Description:Service telemetry and user reporting indicates we're now in a recovered state. We're pursuing a more detailed analysis so we can better understand which features are included in this incident and what actions may be required to prevent reoccurrence.
This quick update is designed to give the latest information on this issue.
Time:Fri Dec 19 14:47:10 2025
Description:Title: Users are experiencing Microsoft Teams messaging delays and problems with other service functions
User impact: Users are experiencing Microsoft Teams messaging delays and problems with other service functions.
More info: Users may see delays sending messages across chats and channels, as well as issues starting their Microsoft Teams clients.
Current status: We're observing recovery in the service health telemetry for an affected portion of Microsoft Teams infrastructure and are continuing our analysis to identify the impacted scenarios and determine the cause of this issue.
Scope of impact: Any users served through an affected portion of Microsoft Teams service infrastructure may see messaging delays and issues starting their Microsoft Teams clients.
Next update by: Friday, December 19, 2025, at 8:30 PM UTC
Time:Fri Dec 19 14:28:37 2025
Description:Title: We're looking into a potential problem impacting the Microsoft Teams service
User impact: Users are experiencing Microsoft Teams messaging delays and problems with other service functions.
Current status: We're investigating a potential issue with the Microsoft Teams service and checking for impact to your organization. We'll provide an update within 30 minutes.

MO1198797 - Users in the Asia Pacific region may be experiencing access and sign‑in issues with Microsoft 365 and Microsoft Copilot

Status:postIncidentReviewPublished
Start Time:Wed Dec 17 19:17:00 2025
End Time:Wed Dec 17 20:17:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Tue Dec 23 19:27:21 2025
Root Cause:N/A
Next Update:N/A

Details

Time:Tue Dec 23 19:27:21 2025
Description:A post-incident report has been published.
Time:Tue Dec 23 19:22:03 2025
Description:A post-incident report has been published.
Time:Mon Dec 22 18:21:39 2025
Description:A post-incident report has been published.
Time:Wed Dec 17 22:28:03 2025
Description:Title: Users in the Asia Pacific region may be experiencing access and sign‑in issues with Microsoft 365 and Microsoft Copilot
User impact: Users in Japan and China may have been experiencing access and sign‑in issues with Microsoft 365 and Microsoft Copilot.
Final status: We’ve confirmed that the issue has been resolved, and all services are now operating as expected.
Scope of impact: Your organization may have been affected by this event, and some users in the Asia Pacific region who attempted to access Microsoft 365 services including Copilot may have been impacted.
Start time: Thursday, December 18, 2025, at 12:17 AM UTC
End time: Thursday, December 18, 2025, at 1:17 AM UTC
Preliminary root cause: A traffic routing issue caused infrastructure in Japan to become unhealthy, which ultimately blocked users from successfully connecting to Microsoft 365 and Copilot services.
Next steps: - We’re evaluating our network traffic routing flows to improve overall performance and help reduce future service disruptions.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
Time:Wed Dec 17 21:53:23 2025
Description:Title: Users in the Asia Pacific region are experiencing access and sign‑in issues with Microsoft 365 and Microsoft Copilot
User impact: Users in the Asia Pacific region are experiencing access and sign‑in issues with Microsoft 365 and Microsoft Copilot.
Current status: The service health remains stable and users should now be experiencing improved access to Microsoft 365 and Copilot services. We're continuing to monitor for an extended period to ensure complete service recovery.
Scope of impact: Your organization may be affected by this event, and some users in the Asia Pacific region who are attempting to access Microsoft 365 services including Copilot may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, December 18, 2025, at 12:17 AM UTC
Preliminary root cause: A traffic routing issue caused infrastructure in Japan to become unhealthy, which ultimately blocked users from successfully connecting to Microsoft 365 and Copilot services.
Next update by: Thursday, December 18, 2025, at 4:00 AM UTC
Time:Wed Dec 17 21:39:57 2025
Description:Current status: We've confirmed that service health has largely recovered following our mitigative actions. We’ll maintain elevated monitoring to confirm full recovery.
This quick update is designed to give the latest information on this issue.
Time:Wed Dec 17 21:10:15 2025
Description:Title: Users in the Asia Pacific region are experiencing access and sign‑in issues with Microsoft 365 and Microsoft Copilot
User impact: Users in the Asia Pacific region are experiencing access and sign‑in issues with Microsoft 365 and Microsoft Copilot.
Current status: We’ve confirmed that service telemetry is showing a positive recovery following the applied mitigation. We’ll continue to monitor closely to confirm complete restoration.
Scope of impact: Your organization may be affected by this event, and some users in the Asia Pacific region who are attempting to access Microsoft 365 services including Copilot may be impacted. This information may be updated as our investigation continues.
Start time: Thursday, December 18, 2025, at 12:17 AM UTC
Preliminary root cause: A traffic routing issue caused infrastructure in Japan to become unhealthy, which ultimately blocked users from successfully connecting to Microsoft 365 and Copilot services.
Next update by: Thursday, December 18, 2025, at 3:00 AM UTC
Time:Wed Dec 17 20:34:09 2025
Description:Current status: We’ve identified that a portion of service infrastructure, supporting user traffic in Japan, became impacted at approximately 12:00 AM UTC due to a routing issue. We’ve taken mitigating actions to rebalance the traffic across healthy infrastructure to restore availability. We're working to confirm full recovery.
This quick update is designed to give the latest information on this issue.
Time:Wed Dec 17 20:13:50 2025
Description:Title: Users in the Japan region are currently experiencing access and sign‑in issues with Microsoft 365 and Microsoft Copilot
User impact: Users in the Japan region are currently experiencing access and sign‑in issues with Microsoft 365 and Microsoft Copilot.
Current status: We’re actively reviewing service telemetry to identify the underlying cause of the issue and determine appropriate mitigation actions.
Scope of impact: Your organization may be affected by this event, and some users attempting to access Microsoft 365 services including Copilot may be impacted.
Next update by: Thursday, December 18, 2025, at 2:00 AM UTC
Time:Wed Dec 17 19:50:56 2025
Description:Title: Investigating user reports of Microsoft 365 Services and Microsoft Copilot issues in Japan
User impact: We don't have detail on impact yet. We're seeing an increase in user reported issues above our alerting threshold.
Current status: We are reviewing service telemetry and available information to determine if there is an issue happening and we'll update this message shortly with our latest findings.

TM1199346 - Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client

Status:serviceRestored
Start Time:Wed Dec 17 10:34:00 2025
End Time:Fri Dec 19 15:00:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Tue Dec 23 12:42:19 2025
Root Cause:A recent service update that intended to address an unrelated service problem introduced an impacting code regression that was preventing users from answering PSTN calls from call queues using the Microsoft Teams client.
Next Update:N/A

Details

Time:Tue Dec 23 12:37:38 2025
Description:Title: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client
User impact: Users may have been unable to answer PSTN calls from call queues using any Microsoft Teams client.
More info: When answering PSTN calls from call queues, affected users experienced calls that remained stuck in a loading state, preventing connection establishment.
While we worked on a fix, non-Virtual Desktop Infrastructure (VDI) users could disable the setting (Settings, Devices, “Sync device buttons”) as a temporary remediation.
For optimized VDI users that didn't have the option to toggle the "Sync device buttons" setting, some users could work around this impact by accepting PSTN calls using a non-human interface device (HID).
Final status: We’ve deployed the fix to the affected environments and verified with affected users that this action successfully remediated the problem.
Scope of impact: Impact was specific to some users attempting to answer PSTN calls from call queues using any Microsoft Teams client.
Start time: Wednesday, December 17, 2025, at 3:34 PM UTC
End time: Friday, December 19, 2025, at 8:00 PM UTC
Root cause: A recent service update that intended to address an unrelated service problem introduced an impacting code regression that was preventing users from answering PSTN calls from call queues using the Microsoft Teams client.
Next steps: - We’re investigating how the recent service update intended to address an unrelated issue introduced a code regression that prevented users from answering PSTN calls from call queues using the Microsoft Teams client, to help prevent this problem from occurring again.
This is the final update for the event.
Time:Mon Dec 22 13:57:05 2025
Description:Title: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client
User impact: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client.
More info: When answering PSTN calls from call queues, affected users experience calls that remain stuck in a loading state, preventing connection establishment.
While we continue to work on a fix, non-Virtual Desktop Infrastructure (VDI) users can disable the setting (Settings, Devices, “Sync device buttons”) as a temporary remediation.
For optimized VDI users that don't have the option to toggle the "Sync device buttons" setting, some users can work around this impact by accepting PSTN calls using a non-human interface device (HID).
Current status: After verifying the validity of our fix with a subset of affected users, we've broadly deployed our fix, and our internal service telemetry is reporting that impact has been remediated as of December 19, 2025, at approximately 8:00 PM UTC. We're awaiting additional testing by affected users so we can ensure our deployment has addressed the isolated code regression and that impact has been resolved.
Scope of impact: Impact is specific to some users attempting to answer PSTN calls from call queues using any Microsoft Teams client.
Start time: Wednesday, December 17, 2025, at 3:34 PM UTC
Root cause: A recent service update that intended to address an unrelated service problem introduced an impacting code regression that is preventing users from answering PSTN calls from call queues using the Microsoft Teams client.
Next update by: Tuesday, December 23, 2025, at 7:00 PM UTC
Time:Fri Dec 19 13:20:55 2025
Description:Title: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client
User impact: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client.
More info: When answering PSTN calls from call queues, affected users experience calls that remain stuck in a loading state, preventing connection establishment.
While we continue to work on a fix, non-Virtual Desktop Infrastructure (VDI) users can disable the setting (Settings, Devices, “Sync device buttons”) as a temporary remediation.
For optimized VDI users that don't have the option to toggle the "Sync device buttons" setting, some users can workaround this impact by accepting PSTN calls using a non-human interface device (HID).
Current status: While investigating the aforementioned code path, we've identified a recent service change associated with it which may contain a misconfiguration that's causing the impact. To confirm this theory, we've developed a fix that corrects the misconfiguration and are enabling it for a subset of affected users to test its efficacy before deploying it more broadly.
Scope of impact: Impact is specific to some users attempting to answer PSTN calls from call queues using any Microsoft Teams client.
Next update by: Monday, December 22, 2025, at 7:00 PM UTC
Time:Thu Dec 18 14:10:32 2025
Description:Title: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client
User impact: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client.
More info: Affected users when answering PSTN calls from call queues experience calls that remain stuck in a loading state, preventing connection establishment.
We identified that disabling the setting (Settings → Devices → “Sync device buttons”) can mitigate the problem.
While root causing the issue that causes "users to be unable to answer PSTN calls from call queues using any Microsoft Teams client", we found that optimized VDI users are not able to toggle the "Sync device buttons" setting option. To provide a mitigation for optimized VDI environments, we're investigating other mitigation options to resolve the issue.
Current status: While we continue to validate with a subset of users if disabling "Sync device buttons" in the Microsoft Teams settings page resolves the issue, we're simultaneously analyzing the code path utilized when answering PSTN calls from call queues for potential discrepancies that may point to the underlying root cause of impact.
Scope of impact: Impact is specific to some users attempting to answer PSTN calls from call queues using any Microsoft Teams client.
Next update by: Friday, December 19, 2025, at 7:00 PM UTC
Time:Thu Dec 18 12:43:58 2025
Description:Title: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client
User impact: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client.
More info: Affected users when answering PSTN calls in call queues experience calls that remain stuck in a loading state, preventing connection establishment.
Current status: We've isolated that impact appears to only occur when utilizing third-party headsets to answer PSTN calls from call queues. We're working with a subset of affected users to validate if disabling "Sync device buttons" in the Microsoft Teams settings page resolves the issue and to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users attempting to answer PSTN calls from call queues using any Microsoft Teams client.
Next update by: Thursday, December 18, 2025, at 8:00 PM UTC
Time:Thu Dec 18 10:39:13 2025
Description:Title: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client
User impact: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client.
More info: Affected users when answering PSTN calls in call queues experience calls that remain stuck in a loading state, preventing connection establishment.
Current status: We're reviewing service and client logs to understand the underlying root cause of the issue and formulate a mitigation plan.
Scope of impact: Impact is specific to some users attempting to answer PSTN calls from call queues using any Microsoft Teams client.
Next update by: Thursday, December 18, 2025, at 6:00 PM UTC
Time:Thu Dec 18 08:50:30 2025
Description:Title: Users may be unable to answer Public Switched Telephone Network (PSTN) calls from call queues using any Microsoft Teams client
User impact: Users may be unable to answer PSTN calls from call queues using any Microsoft Teams client.
More info: Affected users when answering PSTN calls in call queues experience calls that remain stuck in a loading state, preventing connection establishment.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users attempting to answer PSTN calls from call queues using any Microsoft Teams client.
Next update by: Thursday, December 18, 2025, at 4:00 PM UTC
Time:Thu Dec 18 08:17:49 2025
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.

IS1202804 - Users may intermittently be unable to activate Microsoft Entra ID roles in Privileged Identity Management (PIM)

Status:serviceRestored
Start Time:Mon Dec 22 03:05:00 2025
End Time:Mon Dec 22 13:30:00 2025
Service:Microsoft Entra
Feature Group:Microsoft Entra
Classification:advisory
Last Updated:Mon Dec 22 15:29:31 2025
Root Cause:Resource constraints in the affected environment prevented user requests to activate Microsoft Entra ID roles in PIM from processing, resulting in impact.
Next Update:N/A

Details

Time:Mon Dec 22 15:29:31 2025
Description:Title: Users may intermittently be unable to activate Microsoft Entra ID roles in Privileged Identity Management (PIM)
User impact: Users may have intermittently been unable to activate Microsoft Entra ID roles in PIM.
More info: If impact occurred, we advised that users wait a few minutes and then try again, as subsequent attempts may have been successful.
Final status: We've completed reverting the build update and confirmed using our internal telemetry that impact is remediated. Our performance improvements to increase request processing rates may have also contributed to this remediation.
Scope of impact: Any user attempting to activate Microsoft Entra ID roles in PIM may have been intermittently impacted.
Start time: Monday, December 22, 2025, at 8:05 AM UTC
End time: Monday, December 22, 2025, at 6:30 PM UTC
Root cause: Resource constraints in the affected environment prevented user requests to activate Microsoft Entra ID roles in PIM from processing, resulting in impact.
Next steps: - We're reviewing our build update validation procedure to improve the detection and prevention of similar resource constraint issues in the future.
This is the final update for the event.
Time:Mon Dec 22 13:29:35 2025
Description:Title: Users may intermittently be unable to activate Microsoft Entra ID roles in Privileged Identity Management (PIM)
User impact: Users may intermittently be unable to activate Microsoft Entra ID roles in PIM.
More info: If impact occurs, we advise that users wait a few minutes and then try again, as subsequent attempts may be successful.
Current status: We've reverted the configuration update but telemetry indicates that impact persists. We've identified a recent build update that may be contributing to impact and we're reverting the service back to the last known good build as a potential method of resolving this issue. Additionally, we've implemented performance improvements to increase request processing rates and mitigate the risk of resource constraints as another possible remediation stream.
Scope of impact: Any user attempting to activate Microsoft Entra ID roles in PIM may be intermittently impacted.
Next update by: Monday, December 22, 2025, at 8:30 PM UTC
Time:Mon Dec 22 12:22:21 2025
Description:Title: Users intermittently can't activate Microsoft Entra ID roles in Privileged Identity Management (PIM)
User impact: Users intermittently can't activate Microsoft Entra ID roles in PIM.
More info: When impact occurs, we advise that users wait a few minutes and then try again as subsequent attempts may be successful.
Current status: We've discovered a recent infrastructure configuration update that occurred during the onset of this issue and we suspect it may be related to the reported impact. We're reverting this recent update as a potential method of remediating impact. In parallel, we're investigating performance issues stemming from resource constraints occurring in the subset of infrastructure that processes the requests to activate Microsoft Entra ID roles in PIM.
Scope of impact: Your organization is affected by this event, and any user attempting to activate Microsoft Entra ID roles in PIM are intermittently impacted.
Next update by: Monday, December 22, 2025, at 6:30 PM UTC
Time:Mon Dec 22 11:14:17 2025
Description:Title: Users can't activate Microsoft Entra ID roles in Privileged Identity Management (PIM)
User impact: Users can't activate Microsoft Entra ID roles in PIM.
Current status: We're investigating a potential issue with Microsoft Entra ID and checking for impact to your organization. We'll provide an update within 30 minutes.

EX1193572 - Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web

Status:serviceRestored
Start Time:Mon Oct 6 20:00:00 2025
End Time:Sat Dec 20 03:00:00 2025
Service:Exchange Online
Feature Group:Networking Issues
Classification:advisory
Last Updated:Mon Dec 22 15:08:24 2025
Root Cause:A recent upgrade to .NET Core caused cache failures, which prevented users from accessing Microsoft 365 apps through the app launcher in Outlook on the web.
Next Update:N/A

Details

Time:Mon Dec 22 15:08:07 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may have been unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Final status: We've confirmed that the deployment of the fix has completed, and we've validated with some users who initially reported the issue that the impact is remediated.
Scope of impact: Some users that attempted to access Microsoft 365 apps through the app launcher in Outlook on the web may have been impacted.
Start time: Wednesday, November 26, 2025, at 4:30 PM UTC
End time: Saturday, December 20, 2025, at 8:00 AM UTC
Root cause: A recent upgrade to .NET Core caused cache failures, which prevented users from accessing Microsoft 365 apps through the app launcher in Outlook on the web.
Next Steps: - We're further reviewing the recent upgrade to understand what specifically caused the cache failures, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future upgrades.
This is the final update for the event.
Time:Fri Dec 19 13:49:31 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: The deployment of the fix is 80 percent complete, and we've received positive feedback from some users who initially reported the issue that the impact is remediated. We're continuing to monitor while the deployment progresses, and we expect the majority of impacted users will experience remediation by our next scheduled update.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, November 26, 2025, at 4:30 PM UTC
Root cause: A recent upgrade to .NET Core is resulting in cache failures, preventing users from accessing Microsoft 365 apps through the app launcher in Outlook on the web.
Next update by: Monday, December 22, 2025, at 10:00 PM UTC
Time:Thu Dec 18 13:59:02 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: Deployment of the fix is progressing; however, taking longer than expected to complete. Our telemetry indicates that the rate of errors has significantly decreased and we suspect that the issue should be resolved for some affected users. We’re monitoring the ongoing deployment to ensure it completes and validating with affected users to confirm whether the issue is still occurring.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, November 26, 2025, at 4:30 PM UTC
Root cause: A recent upgrade to .NET Core is resulting in cache failures, preventing users from accessing Microsoft 365 apps through the app launcher in Outlook on the web.
Next update by: Friday, December 19, 2025, at 8:30 PM UTC
Time:Tue Dec 16 19:52:32 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: We've developed the fix build for the issue and are preparing the deployment. We anticipate that the fix deployment will take at least 24 hours to fully reach the affected environment and will provide updates on the deployment timeline as they become available.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, November 26, 2025, at 4:30 PM UTC
Root cause: A recent upgrade to .NET Core is resulting in cache failures, preventing users from accessing Microsoft 365 apps through the app launcher in Outlook on the web.
Next update by: Thursday, December 18, 2025, at 8:00 PM UTC
Time:Tue Dec 16 13:29:51 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: We've validated our targeted fix's efficacy in remediating the impact within our internal test environment, and we're preparing to deploy the fix to the affected environment. We'll aim to provide a timeline for the deployment to begin by our next scheduled communications update.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, November 26, 2025, at 4:30 PM UTC
Root cause: A recent upgrade to .NET Core is resulting in cache failures, preventing users from accessing Microsoft 365 apps through the app launcher in Outlook on the web.
Next update by: Wednesday, December 17, 2025, at 3:00 AM UTC
Time:Thu Dec 11 19:23:36 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: After additional review, we've determined that to safely remediate the issue for all users in the long-term, we'll need to implement a targeted fix rather than reverting the change, and we're preparing the fix for validation now. We're aiming to confirm a timeline for its deployment as it becomes available.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, November 26, 2025, at 4:30 PM UTC
Root cause: A recent upgrade to .NET Core is resulting in cache failures, preventing users from accessing Microsoft 365 apps through the app launcher in Outlook on the web.
Next update by: Tuesday, December 16, 2025, at 8:00 PM UTC
Time:Thu Dec 11 14:10:32 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: We've confirmed that the recent .NET Core upgrade is producing a cache failure, preventing some users from accessing Microsoft 365 apps through the app launcher in Outlook on the web. While we were previously exploring a targeted fix for the upgraded deployment, we've determined that reverting this change is the most appropriate mitigation action for users still impacted by this problem.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Start time: Wednesday, November 26, 2025, at 4:30 PM UTC
Root cause: A recent upgrade to .NET Core is resulting in cache failures, preventing users from accessing Microsoft 365 apps through the app launcher in Outlook on the web.
Next update by: Friday, December 12, 2025, at 2:00 AM UTC
Time:Wed Dec 10 16:51:27 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: We're analyzing a reproduction of impact in our internal testing environment to isolate the underlying causes of impact to validate the best path to creating a targeted fix that can be applied across affected environments.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, October 7, 2025, at 12:00 AM UTC
Next update by: Thursday, December 11, 2025, at 8:00 PM UTC
Time:Wed Dec 10 13:19:37 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: We've determined that this issue isn't specific to users in India and have updated the Title, User impact, and Scope of impact fields to reflect the updated scenario. We've confirmed that our validation of reverting the update to some users in India is effective in remediating the issue; however, this action may not be appropriate when applied broadly. We're assessing a broader rollback of the update while also continuing our analysis of the recent .NET version upgrade so that we can determine if a targeted fix is viable.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Start time: Tuesday, October 7, 2025, at 12:00 AM UTC
Next update by: Wednesday, December 10, 2025, at 11:30 PM UTC
Time:Tue Dec 9 20:33:25 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: We've confirmed our previous theory that a recent .NET version upgrade is contributing to impact. We've reverted the offending update for a small subset of users to verify its effectiveness in remediating the issue. Additionally, we're further investigating the offending update to understand what specific aspect of it is contributing to impact to help with understanding more details of the root cause and establishing a long-term fix.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Next update by: Wednesday, December 10, 2025, at 7:00 PM UTC
Time:Tue Dec 9 16:54:04 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: Our additional user provided data and service telemetry and update analysis have isolated a caching problem that we believe is associated with a recent .NET version upgrade. As we further analyze the change and confirm if it's the source for this event, we're reviewing available options for addressing the caching problems and for remediating the impact.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Next update by: Wednesday, December 10, 2025, at 3:00 AM UTC
Time:Tue Dec 9 13:32:36 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: Our analysis of user provided data relating to the impact scenario is ongoing while we're expanding our investigation to include service telemetry and recent updates which may be contributing to impact.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Next update by: Tuesday, December 9, 2025, at 11:00 PM UTC
Time:Tue Dec 9 09:14:47 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: We're continuing to review impact scenario information provided by some affected users to isolate the root cause and develop a mitigation plan.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Next update by: Tuesday, December 9, 2025, at 7:30 PM UTC
Time:Tue Dec 9 08:17:14 2025
Description:Title: Some users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web
User impact: Users may be unable to access Microsoft 365 apps through the app launcher in Outlook on the web.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Some users attempting to access Microsoft 365 apps through the app launcher in Outlook on the web may be impacted. This section may be updated as the investigation progresses.
Next update by: Tuesday, December 9, 2025, at 3:30 PM UTC

TM1202521 - Users may have seen a message "Classic Teams is no longer available" when opening Microsoft Teams in web applications

Status:serviceRestored
Start Time:Fri Dec 19 17:53:00 2025
End Time:Mon Dec 22 04:30:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Mon Dec 22 05:18:32 2025
Root Cause:A URL mismatch led to Microsoft Teams launching an outdated web page.
Next Update:N/A

Details

Time:Mon Dec 22 05:18:32 2025
Description:Title: Users may have seen a message "Classic Teams is no longer available" when opening Microsoft Teams in web applications
User impact: Users may have seen a message "Classic Teams is no longer available" when opening Microsoft Teams in web applications.
More info: Specifically, when users attempted to open Microsoft Teams through web apps such as Outlook, OneNote, or SharePoint Online, they may have been redirected and received the following message, "Classic Teams is no longer available". However, users could either click "Use Teams on the web" or directly open the Microsoft Teams app through their mobile, desktop or web app.
Final status: We've confirmed that a URL mismatch led to Microsoft Teams launching an outdated web page, which resulted in impact. We've changed the URL destination to the correct web page and confirmed through extensive testing, that impact has been remediated.
Scope of impact: Some users attempting to open Microsoft Teams through various web applications may have been impacted.
Start time: Friday, December 19, 2025, at 10:53 PM UTC
End time: Monday, December 22, 2025, at 9:30 AM UTC
Root cause: A URL mismatch led to Microsoft Teams launching an outdated web page.
Next steps: - We're analyzing Microsoft Teams URLs on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
Time:Mon Dec 22 03:27:33 2025
Description:Title: Users may see a message "Classic Teams is no longer available" when opening Microsoft Teams in web applications
User impact: Users may see a message "Classic Teams is no longer available" when opening Microsoft Teams in web applications.
More info: Specifically, when users attempt to open Microsoft Teams through web apps such as Outlook, OneNote, or SharePoint Online, they get redirected and receive the following message, "Classic Teams is no longer available". However, users can either click "Use Teams on the web" or directly open the Microsoft Teams app through their mobile, desktop or web app.
Current status: We've identified that the URL which redirects users to Microsoft Teams may be incorrect. We're reviewing the URL in depth and attempting to change the URL destination to mitigate impact.
Scope of impact: Some users attempting to open Microsoft Teams through various web applications may be impacted.
Next update by: Monday, December 22, 2025, at 10:30 AM UTC
Time:Mon Dec 22 02:21:18 2025
Description:Title: Users may see a message "Classic Teams is no longer available" when opening Microsoft Teams through web applications
User impact: Users may see a message "Classic Teams is no longer available" when opening Microsoft Teams through web applications.
More info: Specifically, when users attempt to open Microsoft Teams through web apps such as Outlook, OneNote, or SharePoint Online, they get redirected and receive the following message, "Classic Teams is no longer available". However, users can either click "Use Teams on the web" or directly open the Microsoft Teams app through their mobile, desktop or web app to open Microsoft Teams.
Current status: We're reviewing the error message users receive to help with the investigation and to determine our next troubleshooting steps.
Scope of impact: Some users attempting to open Microsoft Teams through various web applications may be impacted.
Next update by: Monday, December 22, 2025, at 9:30 AM UTC
Time:Mon Dec 22 02:01:36 2025
Description:Title: Users may see a message "Classic Teams is no longer available" when opening Microsoft Teams through web applications
User impact: Users may see a message "Classic Teams is no longer available" when opening Microsoft Teams through web applications.
More info: Specifically, when users attempt to open Microsoft Teams through web apps such as Outlook, OneNote, or SharePoint Online, they get redirected and receive the following message, "Classic Teams is no longer available". However, users can either click "Use Teams on the web" or directly open the Microsoft Teams app through their mobile, desktop or web app to open Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1200539 - Some Virtual Desktop Infrastructure (VDI) users were unable to share screen or video during Microsoft Teams meetings

Status:serviceRestored
Start Time:Thu Nov 20 05:18:00 2025
End Time:Fri Dec 19 19:39:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Sat Dec 20 04:36:48 2025
Root Cause:A recent update contained a change that set an incorrect configuration for a section of code that helps facilitate the sharing process in this scenario, which caused impact to occur.
Next Update:N/A

Details

Time:Sat Dec 20 04:36:48 2025
Description:Title: Some Virtual Desktop Infrastructure (VDI) users were unable to share screen or video during Microsoft Teams meetings
User impact: Users were unable to share their screen or video during Microsoft Teams meetings when using VDI with Omnissa devices.
More info: When users attempted to share their screen or video during Microsoft Teams meetings when using VDI with Omnissa devices, the participants may have only seen a blank screen.
Final status: We've re-enabled the correct code configuration and confirmed that impact has been resolved.
Scope of impact: Some users attempting to share their screen or video during Microsoft Teams meetings when using VDI with Omnissa devices may have been impacted.
Start time: Thursday, November 20, 2025, at 10:18 AM UTC
End time: Saturday, December 20, 2025, at 12:39 AM UTC
Root cause: A recent update contained a change that set an incorrect configuration for a section of code that helps facilitate the sharing process in this scenario, which caused impact to occur.
Next steps: - We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
Time:Fri Dec 19 16:02:11 2025
Description:Title: Some Virtual Desktop Infrastructure (VDI) users may be unable to share screen or video during Microsoft Teams meetings
User impact: Users may be unable to share their screen or video during Microsoft Teams meetings when using VDI with Omnissa devices.
More info: When users attempt to share their screen or video during Microsoft Teams meetings when using VDI with Omnissa devices, the participants may only see a blank screen.
Current status: We've identified a recent update contained a change that set an incorrect configuration for a portion of code that helps facilitate the sharing process in this scenario, causing the impact. We're reenabling the correct code configuration and expect that it'll be completed by the time of our next update.
Scope of impact: Some users that are attempting to share their screen or video during Microsoft Teams meetings when using VDI with Omnissa devices may be impacted.
Start time: Thursday, November 20, 2025, at 10:18 AM UTC
Root cause: A recent update contained a change that set an incorrect configuration for a portion of code that helps facilitate the sharing process in this scenario, causing the impact.
Next update by: Saturday, December 20, 2025, at 11:00 AM UTC
Time:Fri Dec 19 15:41:46 2025
Description:Title: Some Virtual Desktop Infrastructure (VDI) users may be unable to share screen or video during Microsoft Teams meetings
User impact: Users may be unable to share their screen or video during Microsoft Teams meetings when using VDI with Omnissa devices.
More info: When users attempt to share their screen or video during Microsoft Teams meetings when using VDI with Omnissa devices, the participants may only see a blank screen.
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.

TM1198666 - Admins are unable to remove members from Microsoft Teams channels using Graph API

Status:serviceRestored
Start Time:Mon Oct 13 04:00:00 2025
End Time:Thu Dec 18 20:00:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Fri Dec 19 17:12:41 2025
Root Cause:A service-side configuration validation issue was impacting the request flow when users were being removed from Teams channels through methods leveraging Graph API.
Next Update:N/A

Details

Time:Fri Dec 19 17:02:40 2025
Description:Title: Admins are unable to remove members from Microsoft Teams channels using Graph API
User impact: Admins were unable to remove members from Microsoft Teams channels using Graph API.
More info: Admins could manually remove users from Teams channels using any Microsoft Teams client.
Final status: We’ve validated the fix, applied it to the affected environments, and verified through our testing environments that this action has successfully remediated the problem.
Scope of impact: Your organization was impacted by this event, and admins were unable to remove members from Microsoft Teams channels using Graph API.
Start time: Monday, October 13, 2025, at 8:00 AM UTC
End time: Friday, December 19, 2025, at 1:00 AM UTC
Root cause: A service-side configuration validation issue was impacting the request flow when users were being removed from Teams channels through methods leveraging Graph API.
Next steps: - We're investigating how the service-side configuration validation issue was impacting the request flow when users were being removed from Teams channels through methods leveraging Graph API to better understand the underlying issue and to prevent this problem from happening again.
This is the final update for the event.
Time:Wed Dec 17 19:28:40 2025
Description:Title: Admins are unable to remove members from Microsoft Teams channels using Graph API
User impact: Admins are unable to remove members from Microsoft Teams channels using Graph API.
More info: Admins can manually remove users from Teams channels using any Microsoft Teams client.
Current status: We've completed the preliminary validation of our code fix, and we're aiming to begin deploying it throughout the affected environment by the time of our next scheduled update.
Scope of impact: Your organization is impacted by this event, and admins are unable to remove members from Microsoft Teams channels using Graph API. This information may be updated as our investigation continues.
Root cause: A service-side configuration validation issue is impacting the request flow when users are being removed from Teams channels through methods leveraging Graph API.
Next update by: Friday, December 19, 2025, at 11:00 PM UTC
Time:Wed Dec 17 13:46:42 2025
Description:Title: Admins are unable to remove members from Microsoft Teams channels using Graph API
User impact: Admins are unable to remove members from Microsoft Teams channels using Graph API.
More info: Admins can manually remove users from Teams channels using any Microsoft Teams client.
Current status: We've isolated that Microsoft Graph isn’t presenting necessary configuration checks to the third-party app your organization utilizes to remove users from Teams channels via API to facilitate removal requests. We're working on developing and validating a code change to address the missing configuration checks.
Scope of impact: Your organization is impacted by this event, and admins are unable to remove members from Microsoft Teams channels using Graph API.
Root cause: Microsoft Graph isn’t presenting necessary configuration checks to the third-party app your organization utilizes to remove users from Teams channels via API to facilitate removal requests.
Next update by: Thursday, December 18, 2025, at 2:00 AM UTC
Time:Wed Dec 17 13:04:48 2025
Description:Title: Admins are unable to remove members from Microsoft Teams channels using Graph API
User impact: Admins are unable to remove members from Microsoft Teams channels using Graph API.
More info: Admins can manually remove users from Teams channels using any Microsoft Teams 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.

TM1199570 - Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients

Status:serviceRestored
Start Time:Mon Dec 15 15:00:00 2025
End Time:Fri Dec 19 11:12:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:incident
Last Updated:Fri Dec 19 13:31:58 2025
Root Cause:A recent service update intended to facilitate location services contained a code error, resulting in impact.
Next Update:N/A

Details

Time:Fri Dec 19 12:58:56 2025
Description:Title: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients
User impact: Users may have been intermittently unable to place calls using the dial pad in Microsoft Teams desktop and web clients.
More info: Specifically, affected users were missing the dial pad option in Microsoft Teams clients, and a subset were unable to receive calls.
Admins could have de-provisioned and re-provisioned phone numbers to resolve the issue. Affected users could restart the Microsoft Teams client to receive an expedited fix.
Final status: We’ve confirmed the reversion process completed and verified through service monitoring and with affected users that this action successfully remediated the problem.
Scope of impact: Any user attempting to place calls using the dial pad in Microsoft Teams desktop or web clients was intermittently impacted, and a subset of users were unable to receive calls.
Start time: Monday, December 15, 2025, at 8:00 PM UTC
End time: Friday, December 19, 2025, at 4:12 PM UTC
Root cause: A recent service update intended to facilitate location services contained a code error, resulting in impact.
Next steps: - We're investigating how the recent service update intended to facilitate location services contained a code error to prevent this problem from happening again.
This is the final update for the event.
Time:Thu Dec 18 19:24:16 2025
Description:Title: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients
User impact: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients.
More info: Specifically, affected users may be missing the dial pad option in the Microsoft Teams clients, and only a subset of the affected users may be unable to receive calls.
While we're working to remediate impact, we've received reports that admins can de-provision and re-provision the phone numbers for affected users to resolve the issue. Affected users can restart their Microsoft Teams client to receive an expedited fix.
Affected users can restart their Microsoft Teams client to receive an expedited fix.
Current status: The reversion process is showing continued improvement and affected users will incrementally experience relief from impact as the change propagates throughout the affected environment. Additionally, we anticipate that the aforementioned process will be completed by our next scheduled update.
Scope of impact: Any user attempting to place calls using the dial pad using the Microsoft Teams desktop or web clients may be intermittently impacted, and a subset of users may be unable to receive calls. This information may be updated as our investigation continues.
Root cause: A recent service update intended to facilitate location services contains a code error, resulting in impact.
Next update by: Friday, December 19, 2025, at 6:00 PM UTC
Time:Thu Dec 18 17:26:53 2025
Description:Title: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients
User impact: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients.
More info: Specifically, affected users may be missing the dial pad option in the Microsoft Teams clients, and only a subset of the affected users may be unable to receive calls.
While we're working to remediate impact, we've received reports that admins can de-provision and re-provision the phone numbers for affected users to resolve the issue.
Current status: Our initial results from the reversion is showing improvement. We're continuing to monitor this process and will provide a remediation timeline once available.
Scope of impact: Any user attempting to place calls using the dial pad using the Microsoft Teams desktop or web clients may be intermittently impacted, and a subset of users may be unable to receive calls.
Next update by: Friday, December 19, 2025, at 12:30 AM UTC
Time:Thu Dec 18 15:23:08 2025
Description:Title: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients
User impact: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients.
More info: Specifically, affected users may be missing the dial pad option in the Microsoft Teams clients, and only a subset of the affected users may be unable to receive calls.
While we're working to remediate impact, we've received reports that admins can de-provision and re-provision the phone numbers for affected users to resolve the issue.
Current status: Our analysis of recent changes has found that a recent service update to convey location information with the Microsoft Teams service may contain an issue. We're working to revert this change in a test environment to validate this as the root cause and once confirmed, expand to all impacted environments.
Scope of impact: Any user attempting to place calls using the dial pad using the Microsoft Teams desktop or web clients may be intermittently impacted, and a subset of users may be unable to receive calls.
Next update by: Thursday, December 18, 2025, at 10:30 PM UTC
Time:Thu Dec 18 13:25:58 2025
Description:Title: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients
User impact: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients.
More info: Specifically, affected users may be missing the dial pad option in the Microsoft Teams clients, and only a subset of the affected users may be unable to receive calls.
While we're working to remediate impact, we've received reports that admins can de-provision and re-provision the phone numbers for affected users to resolve the issue.
Current status: Our investigation has identified a potential API issue preventing the users' licenses from being read as expected. We're also analyzing recent service updates which may be contributing to impact to further isolate the root cause of impact and develop a remediation strategy.
Scope of impact: Any user attempting to place calls using the dial pad using the Microsoft Teams desktop or web clients may be intermittently impacted, and a subset of users may be unable to receive calls.
Next update by: Thursday, December 18, 2025, at 8:30 PM UTC
Time:Thu Dec 18 11:57:13 2025
Description:Title: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients
User impact: Users may be intermittently unable to place calls using the dial pad from the Microsoft Teams desktop and web clients.
More info: Specifically, affected users are missing the dial pad option in the Microsoft Teams clients, and only a subset of the affected users can’t receive calls.
Current status: We're reviewing support case information and gathered client logs to assist in the investigation and determine our next steps.
Scope of impact: Any user attempting to place calls using the dial pad using the Microsoft Teams desktop or web clients may be intermittently impacted, and a subset of users may be unable to receive calls.
Next update by: Thursday, December 18, 2025, at 6:30 PM UTC
Time:Thu Dec 18 11:40:00 2025
Description:Title: Some users can't place or receive calls using the Microsoft Teams desktop and web connection methods
User impact: Users can't place or receive calls using the Microsoft Teams desktop and web connection methods.
More info: Specifically, some users are missing the dial pad option in the Microsoft Teams clients.
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.

TM1199560 - Admins may be unable to view the health status of Session Border Controllers (SBCs) in the Microsoft Teams admin center

Status:serviceRestored
Start Time:Thu Dec 18 06:43:00 2025
End Time:Thu Dec 18 11:15:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu Dec 18 11:46:56 2025
Root Cause:The portion of storage infrastructure responsible for communicating the SBC health status to the Microsoft Teams admin center was operating in a suboptimal state and causing impact.
Next Update:N/A

Details

Time:Thu Dec 18 11:46:56 2025
Description:Title: Admins may be unable to view the health status of Session Border Controllers (SBCs) in the Microsoft Teams admin center
User impact: Admins may have been unable to view the health status of SBCs in the Microsoft Teams admin center.
More info: When admins attempt to view the health status of SBCs under the Health Dashboard for Direct Routing in the Microsoft Teams admin center, they may have received an error that states: "No data was available."
Final status: We've completed redirecting the request traffic and confirmed through service health telemetry that the impact is remediated.
Scope of impact: Any admin attempting to view the health status of SBCs under the Health Dashboard for Direct Routing dashboard in the Microsoft Teams admin center may have been impacted.
Start time: Thursday, December 18, 2025, at 11:43 AM UTC
End time: Thursday, December 18, 2025, at 4:15 PM UTC
Root cause: The portion of storage infrastructure responsible for communicating the SBC health status to the Microsoft Teams admin center was operating in a suboptimal state and causing impact.
Next steps: - We're continuing to investigate the affected storage infrastructure to identify the reason it was operating in a suboptimal state, so that we can determine how to prevent similar impact from occurring in the future.
This is the final update for the event.
Time:Thu Dec 18 11:04:29 2025
Description:Title: Admins may be unable to view the health status of Session Border Controllers (SBCs) in the Microsoft Teams admin center
User impact: Admins may be unable to view the health status of SBCs in the Microsoft Teams admin center.
More info: When admins attempt to view the health status of SBCs under the Health Dashboard for Direct Routing in the Microsoft Teams admin center, they may receive an error that states: "No data is available."
Current status: We've identified that the portion of storage infrastructure responsible for communicating the SBC health status to the Microsoft Teams admin center is operating in a suboptimal state and causing impact. We're rebalancing request traffic to remediate the impact.
Scope of impact: Any admin attempting to view the health status of SBCs under the Health Dashboard for Direct Routing dashboard in the Microsoft Teams admin center may be impacted.
Start time: Thursday, December 18, 2025, at 11:43 AM UTC
Root cause: The portion of storage infrastructure responsible for communicating the SBC health status to the Microsoft Teams admin center is operating in a suboptimal state and causing impact.
Next update by: Thursday, December 18, 2025, at 5:30 PM UTC
Time:Thu Dec 18 10:53:05 2025
Description:Title: Admins may be unable to view the health status of Session Border Controllers (SBCs) in the Microsoft Teams admin center
User impact: Admins may be unable to view the health status of SBCs in the Microsoft Teams admin center.
More info: When admins attempt to view the health status of SBCs under the Health Dashboard for Direct Routing in the Microsoft Teams admin center, they may receive an error that states: "No data is available."
Current status: We're investigating a potential issue with the Microsoft Teams admin center and checking for impact to your organization. We'll provide an update within 30 minutes.

IT1197298 - Admins may receive inaccurate policy reports in Microsoft Intune admin center

Status:serviceRestored
Start Time:Sat Nov 8 07:00:00 2025
End Time:Wed Dec 17 22:15:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:advisory
Last Updated:Wed Dec 17 22:49:42 2025
Root Cause:A recent update to the service disabled a SQL connector that provides report policy data to the Intune admin center, which was resulting in this impact.
Next Update:N/A

Details

Time:Wed Dec 17 22:49:42 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may have received inaccurate policy reports in Microsoft Intune admin center.
Final status: We rolled back the change to the SQL connector responsible for report policy data in the affected environment and confirmed through telemetry that the impact is remediated.
Scope of impact: This event impacted any admin accessing reports in the Microsoft Intune admin center.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
End time: Thursday, December 18, 2025, at 3:15 AM UTC
Root cause: A recent update to the service disabled a SQL connector that provides report policy data to the Intune admin center, which was resulting in this impact.
Next steps: - We're reviewing our update procedures to continue developing better detection methods to prevent similar impact from occurring in the future.
This is the final update for the event.
Time:Wed Dec 17 20:11:18 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may receive inaccurate policy reports in Microsoft Intune admin center.
Current status: The rollback of the offending change has completed in the majority of the affected environment, but is taking longer than anticipated in the last phase due to other ongoing deployments. We anticipate that once the other deployments complete, the rollback will finish and the impact will be remediated. We'll provide updates on the deployment timeline as they become available.
Scope of impact: This event impacts any admin accessing reports in the Microsoft Intune admin center. This section may be updated as our investigation continues.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
Root cause: A recent update to the service disabled a SQL connector that provides report policy data to the Intune admin center, which is resulting in this impact.
Next update by: Thursday, December 18, 2025, at 7:30 AM UTC
Time:Wed Dec 17 13:27:40 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may receive inaccurate policy reports in Microsoft Intune admin center.
Current status: The reversion of the offending change is nearing completion, but the change was cancelled in one affected environment due to another ongoing deployment. We're restarting the reversion in that environment and expect it will complete by our next update.
Scope of impact: This event impacts any admin accessing reports in the Microsoft Intune admin center. This section may be updated as our investigation continues.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
Root cause: A recent update to the service disabled a SQL connector that provides report policy data to the Intune admin center, which is resulting in this impact.
Next update by: Thursday, December 18, 2025, at 2:30 AM UTC
Time:Tue Dec 16 23:40:52 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may receive inaccurate policy reports in Microsoft Intune admin center.
Current status: We're continuing to monitor as the offending change is being reverted, and we anticipate this will be complete and the impact remediated by our next scheduled update.
Scope of impact: This event impacts any admin accessing reports in the Microsoft Intune admin center. This section may be updated as our investigation continues.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
Root cause: A recent update to the service disabled a SQL connector that provides report policy data to the Intune admin center, which is resulting in this impact.
Next update by: Wednesday, December 17, 2025, at 8:00 PM UTC
Time:Tue Dec 16 15:50:44 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may receive inaccurate policy reports in Microsoft Intune admin center.
Current status: We've developed a solution to the impact created by the recent update to the service that disabled a SQL connector. This solution requires a staggered reversal of the offending change that will complete stage by stage to ensure that reversing this change won't impact the service as a whole. We're overseeing this process as it progresses to ensure that it goes smoothly and completes as anticipated.
Scope of impact: This event impacts any admin accessing reports in the Microsoft Intune admin center. This section may be updated as our investigation continues.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
Root cause: A recent update to the service disabled a SQL connector that provides report policy data to the Intune admin center, which is resulting in this impact.
Next update by: Wednesday, December 17, 2025, at 7:00 AM UTC
Time:Tue Dec 16 13:26:25 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may receive inaccurate policy reports in Microsoft Intune admin center.
Current status: We've completed the release of a fix and are in the process of confirming mitigation.
Scope of impact: This event impacts any admin accessing reports in the Microsoft Intune admin center. This section may be updated as our investigation continues.
Start time: Saturday, November 8, 2025, at 12:00 PM UTC
Root cause: A recent update to the service disabled an SQL connector that provides report policy data to the Intune admin center, which resulted in this impact.
Next update by: Tuesday, December 16, 2025, at 10:00 PM UTC
Time:Mon Dec 15 23:28:35 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may receive inaccurate policy reports in Microsoft Intune admin center.
Current status: We're initiating the process to revert the recent update in our test environment first to validate that the impact is remediated successfully. We'll provide an estimated timeline for full remediation once one becomes available.
Scope of impact: This event impacts any admin accessing reports in the Microsoft Intune admin center. This section may be updated as our investigation continues.
Root cause: A recent update to the service disabled an SQL connector that provides report policy data to the Intune admin center, which resulted in this impact.
Next update by: Tuesday, December 16, 2025, at 7:00 PM UTC
Time:Mon Dec 15 21:29:30 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may receive inaccurate policy reports in Microsoft Intune admin center.
Current status: We've assessed and determined that we'll move forward with reverting the recent update in an attempt to resolve impact. We'll monitor this process and validate in our test environment once the reversion process completes to see if impact has been successfully remediated.
Scope of impact: This event impacts any admin accessing reports in the Microsoft Intune admin center. This section may be updated as our investigation continues.
Root cause: A recent update to the service disabled an SQL connector that provides report policy data to the Intune admin center, which resulted in this impact.
Next update by: Tuesday, December 16, 2025, at 4:30 AM UTC
Time:Mon Dec 15 20:10:11 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may receive inaccurate policy reports in Microsoft Intune admin center.
Current status: We discovered that a recent update to the service disabled an SQL connector that provides report policy data to the Intune admin center, which resulted in this impact. We're determining if reverting this update is the best mitigation action as well as reviewing other options for resolving the issue.
Scope of impact: This event impacts any admin accessing reports in the Microsoft Intune admin center.
Root cause: A recent update to the service disabled an SQL connector that provides report policy data to the Intune admin center, which resulted in this impact.
Next update by: Tuesday, December 16, 2025, at 2:30 AM UTC
Time:Mon Dec 15 19:49:00 2025
Description:Title: Admins may receive inaccurate policy reports in Microsoft Intune admin center
User impact: Admins may receive inaccurate policy reports in Microsoft Intune admin center.
Current status: We're investigating a potential issue with Microsoft Intune and checking for impact to your organization. We'll provide an update within 30 minutes.

OO1198794 - Users can't open new files in Excel for the web or use the "Create a copy" function

Status:serviceRestored
Start Time:Wed Dec 17 10:00:00 2025
End Time:Wed Dec 17 14:00:00 2025
Service:Microsoft 365 for the web
Feature Group:Excel Online
Classification:advisory
Last Updated:Wed Dec 17 19:33:29 2025
Root Cause:A recent feature update resulted in malformed URLs in the file path process preventing a core resource that facilitates Excel on the web file loading from completing.
Next Update:N/A

Details

Time:Wed Dec 17 19:33:03 2025
Description:Title: Users can't open new files in Excel for the web or use the "Create a copy" function
User impact: Users couldn't open new files in Excel for the web or use the "Create a copy" function.
More info: Users likely would have encountered this scenario mostly when attempting to open a new file in Excel on the web from SharePoint Online or Microsoft OneDrive. Any scenario that included triggering an action to open a new file would have been affected also.
Users opening a file in Excel for the web would have encountered a blank white section where the data was expected to populate and would have seen a message in the bottom-right section indicating that the file was still loading.
Final status: We received reports of an issue in which users couldn't open new files in Excel for the web or use the "Create a copy" function and determined that a recent feature update resulted in malformed URLs in the file path process preventing a core resource that facilitates Excel on the web file loading from completing. We've disabled the portion of this update that resulted in the impact and confirmed through monitoring the log errors associated with the issue are no longer occurring.
Scope of impact: Your organization was affected by this event, and any user attempting to open a new file or use the "Create a copy" save feature in Excel for the web was impacted.
Start time: Wednesday, December 17, 2025, at 3:00 PM UTC
End time: Wednesday, December 17, 2025, at 7:00 PM UTC
Root cause: A recent feature update resulted in malformed URLs in the file path process preventing a core resource that facilitates Excel on the web file loading from completing.
Next steps: - We're reviewing our feature update testing and validation processes to better detect issues affecting Excel on the web file access prior to deployment.
This is the final update for the event.

MV1179108 - Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal

Status:serviceRestored
Start Time:Mon Jun 30 20:00:00 2025
End Time:Sun Dec 14 07:00:00 2025
Service:Microsoft Viva
Feature Group:Viva Insights
Classification:advisory
Last Updated:Wed Dec 17 17:04:25 2025
Root Cause:A change to event-based logic in data provided by Exchange Online contained a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next Update:N/A

Details

Time:Wed Dec 17 16:22:05 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may have noticed missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact was specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data didn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports were unaffected.
Final status: We've confirmed through testing with affected users that the impact has been remediated with the backfill operation completed.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal were affected.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
End time: Sunday, December 14, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contained a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next steps: - We're reviewing our deployment procedures to understand why the code error 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 testing processes.
This is the final update for the event.
Time:Tue Dec 16 17:06:22 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We've completed the backfill process and are reaching out to affected users to validate this has remediated impact.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected. This information may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Wednesday, December 17, 2025, at 11:00 PM UTC
Time:Fri Dec 12 16:30:33 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: The backfill operation is progressing as expected and we anticipate it will complete on Tuesday, December 16, 2025. Once the remaining data has been processed, we'll reach out to a subset of affected users to confirm the issue is resolved.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected. This information may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Tuesday, December 16, 2025, at 11:00 PM UTC
Time:Wed Dec 10 17:24:24 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We’re continuing to monitor the processing of the remaining affected data to ensure the job completes as expected to fully resolve this issue by Monday, December 15, 2025.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected. This information may be updated as our investigation continues. Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Friday, December 12, 2025, at 11:00 PM UTC
Time:Thu Dec 4 16:31:28 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: After completing data processing for email messages sent using Copilot trend data for September 2025 and November 2025, we're progressing with the remaining data processing to completely remediate the impact. We're expecting a more detailed timeline for our remaining data processing to be available by our next scheduled communication update.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected. This information may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Wednesday, December 10, 2025, at 11:00 PM UTC
Time:Mon Dec 1 15:58:06 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We've completed our data processing for email messages sent using Copilot trend data in October 2025 and have progressed to messages sent during September 2025. As we continue with our mitigations, we're working with affected users to determine if our data processing is remediating the impact or if any additional actions will be required.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected. This information may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Thursday, December 4, 2025, at 11:00 PM UTC
Time:Tue Nov 25 14:55:25 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We're continuing to monitor as the events are getting processed and will provide a remediation timeline once available.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected. This information may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Monday, December 1, 2025, at 10:00 PM UTC
Time:Mon Nov 24 20:54:25 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We're continuing to repopulate the remaining subset of affected data; however, due to a setback on the repopulating process, more time is needed to complete the process.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected. This information may be updated as our investigation continues.
Start time: Tuesday, July 1, 2025, at 12:00 AM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Tuesday, November 25, 2025, at 9:00 PM UTC
Time:Wed Nov 19 19:28:22 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025.
This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We’ve identified that the majority of missing data has been populated and is available, but the repopulation is ongoing for a subset of the affected data. We now anticipate that the remaining missing data will be available by our next scheduled update.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Tuesday, November 25, 2025, at 2:00 AM UTC
Time:Wed Nov 12 19:30:05 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025. This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value, and as such, those reports are unaffected.
Current status: We’ve determined that our previous estimates were inaccurate, and after reassessing, we now anticipate that the missing data will be available by the end of Thursday, November 19, 2025.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Thursday, November 20, 2025, at 2:00 AM UTC
Time:Mon Nov 10 03:35:16 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025. This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: The completion of the fix is taking longer than anticipated due to unforeseen circumstances. The process is actively ongoing and, provided there are no further blockers, we expect it to be completed by our next scheduled update.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Thursday, November 13, 2025, at 2:00 AM UTC
Time:Mon Nov 3 20:35:43 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025. This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: The completion of the aforementioned fix is taking longer than previously anticipated. We’ll provide a timeline for completion as one becomes available to us.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Monday, November 10, 2025, at 10:00 AM UTC
Time:Fri Oct 31 06:50:13 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025. This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: We anticipate that the completion of the fix should be fully deployed by our next scheduled update.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Tuesday, November 4, 2025, at 3:00 AM UTC
Time:Wed Oct 29 23:28:22 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025. This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: We've developed a fix to restore the missing data and are preparing to initiate its deployment. We'll provide a completion timeline when one becomes available.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Friday, October 31, 2025, at 11:00 AM UTC
Time:Wed Oct 29 14:35:52 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025. This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: We’re continuing our evaluation of possible pathways to restore the missing data and achieve full resolution. Once confirmed, we’ll provide a resolution timeline.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Thursday, October 30, 2025, at 4:00 AM UTC
Time:Mon Oct 27 17:25:08 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025. This data doesn't apply to Copilot Assisted Hours or Copilot Assisted Value so those reports are unaffected.
Current status: We've deployed a fix designed to adjust the code for event-based logic and confirmed that this allows the Copilot data to be accessed and passed to the Microsoft Viva Insights portal. This ensures that all new data is available, and we're evaluating possible options to restore the missing data.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Wednesday, October 29, 2025, at 8:00 PM UTC
Time:Fri Oct 24 15:35:59 2025
Description:Title: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal
User impact: Users may notice missing Microsoft Copilot impact trend data in the Microsoft Viva Insights portal.
More info: Impact is specific to the total email messages sent using Copilot trend data between Tuesday, July 1, 2025, and Tuesday, October 7, 2025. This metric does not feed into Copilot Assisted Hours or Copilot Assisted Value.
Current status: We've identified that a change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, which is resulting in impact. We're in the process of validating and releasing a fix and will provide a mitigation timeline when available.
Scope of impact: All users accessing Copilot trend data in the Microsoft Viva Insights portal are affected.
Start time: Tuesday, July 1, 2025, at 12:00 PM UTC
Root cause: A change to event-based logic in data provided by Exchange Online contains a code error, preventing the Viva Insights service from accessing the relevant data, resulting in impact.
Next update by: Friday, October 31, 2025, at 8:00 PM UTC

EX1183677 - Users may have been unable to delete a user from the contact list within Outlook on the web

Status:serviceRestored
Start Time:Mon Aug 4 14:32:00 2025
End Time:Tue Dec 16 19:00:00 2025
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:advisory
Last Updated:Wed Dec 17 07:51:10 2025
Root Cause:The Microsoft Entra ID contacts that were removed from active directory contained an X500 smtp address assigned to them, which prevented users from deleting the contacts from the contact list within Outlook on the web.
Next Update:N/A

Details

Time:Wed Dec 17 05:03:02 2025
Description:Title: Users may have been unable to delete a user from the contact list within Outlook on the web
User impact: Users may have been unable to delete a user from the contact list within Outlook on the web.
Final status: We've confirmed that the fix has been fully deployed and that impact is resolved. Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may have been impacted.
Start time: Monday, August 4, 2025, at 6:32 PM UTC
End time: Wednesday, December 17, 2025, at 12:00 AM UTC
Root cause: The Microsoft Entra ID contacts that were removed from active directory contained an X500 smtp address assigned to them, which prevented users from deleting the contacts from the contact list within Outlook on the web.
Next steps: - We're reviewing our Microsoft Entra ID contacts procedures to help prevent this problem from happening again.
This is the final update for the event.
Time:Mon Dec 15 06:34:24 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We've internally validated the fix and begun the deployment process. We anticipate this process and impact to be remediated by our next scheduled update.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Root cause: The Microsoft Entra ID contacts that were removed from active directory contain an X500 smtp address assigned to them, which is preventing users from deleting the contacts from the contact list within Outlook on the web.
Next update by: Wednesday, December 17, 2025, at 11:00 AM UTC
Time:Tue Dec 9 02:53:18 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: The process to test and validate the fix in our internal environment is taking longer than expected. We anticipate completing this process by the next scheduled update. Once the fix has been successfully validated, we'll proceed with deployment.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Root cause: The Microsoft Entra ID contacts that were removed from active directory contain an X500 smtp address assigned to them, which is preventing users from deleting the contacts from the contact list within Outlook on the web.
Next update by: Monday, December 15, 2025, at 11:00 AM UTC
Time:Mon Dec 8 06:06:00 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We're testing and validating the fix in our internal environment prior to deploying it to the affected infrastructure. We expect to provide deployment timeline by our next scheduled update.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Root cause: The Microsoft Entra ID contacts that were removed from active directory contained an X500 smtp address assigned to them, which prevented users to delete the contacts from the contact list within Outlook on the web.
Next update by: Tuesday, December 9, 2025, at 11:00 AM UTC
Time:Tue Nov 25 05:57:25 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’ve identified that the Microsoft Entra ID contacts that were removed from active directory contained an X500 smtp address assigned to them, which prevented users to delete the contacts from the contact list within Outlook on the web. We've developed a fix to address the issue, which we're testing and validating in our internal environment prior to deploying it to the affected infrastructure. We expect to provide deployment time line by our next scheduled update.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Root cause: The Microsoft Entra ID contacts that were removed from active directory contained an X500 smtp address assigned to them, which prevented users to delete the contacts from the contact list within Outlook on the web.
Next update by: Monday, December 8, 2025, at 11:00 AM UTC
Time:Tue Nov 11 06:03:05 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’ve identified that the issue relates to how certain email address formats are being processed. To help us better understand and resolve this, we’ve made changes to improve our diagnostic data and are waiting for these updates to fully apply across the service. This will allow us to obtain more detailed information to isolate the cause of impact and determine the next steps toward a fix.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Tuesday, November 25, 2025, at 11:00 AM UTC
Time:Mon Nov 10 06:22:52 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We're continuing to review the aforementioned logs to help with the root cause investigation and to determine our next troubleshooting steps.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Tuesday, November 11, 2025, at 11:00 AM UTC
Time:Mon Nov 10 00:01:59 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We've received the fresh HAR network trace logs and are analyzing them to help with the root cause investigation and to determine our next troubleshooting steps.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Monday, November 10, 2025, at 11:00 AM UTC
Time:Sun Nov 9 22:57:22 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We're continuing to wait for the fresh HTTP Archive format (HAR) network trace logs to help with the root cause investigation.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Monday, November 10, 2025, at 6:00 AM UTC
Time:Fri Nov 7 20:55:59 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We're continuing to reach out to a subset of impacted users to gather further HTTP Archive format (HAR) network trace logs and contextual details to assist us in gaining further insight into the impacted scenario and determining our next investigative steps.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Monday, November 10, 2025, at 4:00 AM UTC
Time:Fri Nov 7 15:53:42 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’ve requested HTTP Archive format (HAR) traces from affected users and reproduction logs to aid our ongoing investigation into the cause of this issue and to help isolate potential remediation actions.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Saturday, November 8, 2025, at 3:00 AM UTC
Time:Fri Nov 7 05:30:22 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’re acquiring HAR (HTTP Archive) logs from your representatives for us to identify the source of the issue and formulate a mitigation plan.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Friday, November 7, 2025, at 9:30 PM UTC
Time:Fri Nov 7 03:42:31 2025
Description:Title: Users may be unable to delete a user from the contact list within Outlook on the web
User impact: Users may be unable to delete a user from the contact list within Outlook on the web.
Current status: We’re reviewing associated support case details to understand more about the issue, and determine our next troubleshooting steps.
Scope of impact: Users attempting to remove users from the contact list within Outlook on the web may be impacted.
Next update by: Friday, November 7, 2025, at 10:30 AM UTC

TM1197326 - Some users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams

Status:serviceRestored
Start Time:Sat Dec 13 23:00:00 2025
End Time:Tue Dec 16 21:30:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Tue Dec 16 22:27:43 2025
Root Cause:A portion of infrastructure responsible for processing requests to create shared and private channels in Microsoft Teams was performing below the expected service threshold, resulting in impact.
Next Update:N/A

Details

Time:Tue Dec 16 22:27:43 2025
Description:Title: Some users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams
User impact: Users may have seen intermittent failures when attempting to create shared and private channels in Microsoft Teams.
Final status: We've confirmed that our targeted adjustments were successful in resolving the underlying processing delays and verified through internal telemetry that the impacted channel creation scenarios are no longer affected.
Scope of impact: Some users attempting to create shared channels or private channels in Microsoft Teams may have been intermittently impacted.
Start time: Sunday, December 14, 2025, at 4:00 AM UTC
End time: Wednesday, December 17, 2025, at 2:30 AM UTC
Root cause: A portion of infrastructure responsible for processing requests to create shared and private channels in Microsoft Teams was performing below the expected service threshold, resulting in impact.
Next steps: - We're continuing to monitor the affected infrastructure closely to gain further insight into the source of the underlying issue and identify ways we can better prevent similar impact in the future.
This is the final update for the event.
Time:Tue Dec 16 17:17:12 2025
Description:Title: Some users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams
User impact: Users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams.
Current status: We’re progressing with our targeted adjustments to address the processing delays and are reviewing updated telemetry to understand how those changes are affecting end-to-end performance. We’ll continue evaluating results to determine whether any additional remediation action is necessary.
Scope of impact: Some users attempting to create shared channels or private channels in Microsoft Teams may be intermittently impacted. This information may be updated as our investigation continues.
Start time: Sunday, December 14, 2025, at 4:00 AM UTC
Root cause: A portion of infrastructure responsible for processing requests to create shared and private channels in Microsoft Teams is performing below the expected service threshold, which is resulting in impact.
Next update by: Wednesday, December 17, 2025, at 7:30 PM UTC
Time:Tue Dec 16 12:53:24 2025
Description:Title: Some users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams
User impact: Users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams.
Current status: We're continuing to troubleshoot and implement changes to improve the request processing time and are monitoring service health telemetry as we implement these changes to determine their efficacy in remediating impact.
Scope of impact: Some users attempting to create shared channels or private channels in Microsoft Teams may be intermittently impacted. This information may be updated as our investigation continues.
Start time: Sunday, December 14, 2025, at 4:00 AM UTC
Root cause: A portion of infrastructure responsible for processing requests to create shared and private channels in Microsoft Teams is performing below the expected service threshold, which is resulting in impact.
Next update by: Tuesday, December 16, 2025, at 11:30 PM UTC
Time:Tue Dec 16 01:00:17 2025
Description:Title: Some users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams
User impact: Users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams.
Current status: We identified that a portion of infrastructure responsible for processing requests to create shared and private channels in Microsoft Teams is performing below the expected service threshold. We've implemented some changes to improve the request processing time and are monitoring the changes to validate that the impact remediates.
Scope of impact: Some users attempting to create shared channels or private channels in Microsoft Teams may be intermittently impacted. This information may be updated as our investigation continues.
Start time: Sunday, December 14, 2025, at 4:00 AM UTC
Root cause: A portion of infrastructure responsible for processing requests to create shared and private channels in Microsoft Teams is performing below the expected service threshold, causing impact.
Next update by: Tuesday, December 16, 2025, at 7:30 PM UTC
Time:Mon Dec 15 22:01:33 2025
Description:Title: Some users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams
User impact: Users may encounter intermittent failures when attempting to create shared and private channels in Microsoft Teams.
Current status: We've identified through internal monitoring that some users creating channels in Microsoft Teams may be encountering some intermittent impact. We're proceeding with further investigation to diagnose the underlying source of the issue and determine our options for remediation.
Scope of impact: Some users attempting to create shared channels or private channels in Microsoft Teams may be intermittently impacted. This information may be updated as our investigation continues.
Start time: Sunday, December 14, 2025, at 4:00 AM UTC
Next update by: Tuesday, December 16, 2025, at 7:30 AM UTC

MO1193013 - Users in Australia may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365

Status:postIncidentReviewPublished
Start Time:Sun Dec 7 18:11:00 2025
End Time:Sun Dec 7 18:28:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Tue Dec 16 13:37:19 2025
Root Cause:There are currently two connection paths between the Perth Edge site and the wider Microsoft network in Sydney. These connection paths are provided and managed by local ISPs and fiber cable providers in the region. On December 4, an undersea cable cut event occurred on one of the connection paths. Whilst we continue to work with the local third-party fiber cable provider to restore the connection path, the service has remained stable, as the services could still leverage the alternate connection path.
Next Update:N/A

Details

Time:Tue Dec 16 13:37:19 2025
Description:A post-incident report has been published.
Time:Thu Dec 11 19:32:27 2025
Description:A post-incident report has been published.
Time:Sun Dec 7 19:36:36 2025
Description:Title: Users in Australia may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Australia may have experienced issues accessing Microsoft services including Microsoft Teams and Microsoft 365.
Final status: While we were in the process of analyzing a possible networking issue in Australia, 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: Users in Australia attempting to access Microsoft 365 services including Microsoft Teams may have been impacted.
Start time: Sunday, December 7, 2025, at 11:11 PM UTC
End time: Sunday, December 7, 2025, at 11:28 PM UTC
Root cause: There are currently two connection paths between the Perth Edge site and the wider Microsoft network in Sydney. These connection paths are provided and managed by local ISPs and fiber cable providers in the region. On December 4, an undersea cable cut event occurred on one of the connection paths. Whilst we continue to work with the local third-party fiber cable provider to restore the connection path, the service has remained stable, as the services could still leverage the alternate connection path.
On two separate occasions, first on Sunday, December 7 and second on Wednesday, December 10, the remaining connection path experienced a short period of network interruption (including a fiber cut). Once this connection path became unavailable, requests from the Perth Edge site could not be connected to the wider Microsoft network in Sydney, resulting in impact to users. 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 (PIR) which combines both this incident and MO1193724. We'll provide the preliminary PIR by Thursday, December 11, 2025, and a final PIR by Tuesday, December 16, 2025.
Time:Sun Dec 7 19:13:28 2025
Description:Title: Users in Australia may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Australia may have experienced issues accessing Microsoft services including Microsoft Teams and Microsoft 365.
Current status: We've investigated a problem in which users may have experienced issues accessing Microsoft 365 services including Microsoft Teams and confirmed that service is now restored. We'll provide additional information in a closure summary within the "History" section of the "Service health" dashboard shortly.

MO1193724 - Users in Australia may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365

Status:postIncidentReviewPublished
Start Time:Tue Dec 9 21:48:00 2025
End Time:Tue Dec 9 21:57:00 2025
Service:Microsoft 365 suite
Feature Group:Portal
Classification:incident
Last Updated:Tue Dec 16 13:37:09 2025
Root Cause:There are currently two connection paths between the Perth Edge site and the wider Microsoft network in Sydney. These connection paths are provided and managed by local ISPs and fiber cable providers in the region. On December 4, an undersea cable cut event occurred on one of the connection paths. Whilst we continue to work with the local third-party fiber cable provider to restore the connection path, the service has remained stable, as the services could still leverage the alternate connection path.
Next Update:N/A

Details

Time:Tue Dec 16 13:37:09 2025
Description:A post-incident report has been published.
Time:Thu Dec 11 19:32:31 2025
Description:A post-incident report has been published.
Time:Wed Dec 10 00:48:46 2025
Description:Title: Users in Australia may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Australia may have experienced issues when accessing various Microsoft 365 services.
More info: Users may have experienced issues when attempting to access various Microsoft 365 services including but not limited to Microsoft Teams, SharePoint, OneDrive and Exchange Online services.
Final status: We’ve taken proactive action to reroute all traffic to prevent recurrence of this issue while we address the networking issue contributing to the problem. We monitored the service for an extended period and confirmed that the service was stable and the issue resolved.
Scope of impact: Any users served through the Australia region may have been affected by this issue if they attempted to access Microsoft services including but not limited to Microsoft Teams, Exchange Online, SharePoint and OneDrive.
Start time: Wednesday, December 10, 2025, at 2:48 AM UTC
End time: Wednesday, December 10, 2025, at 2:57 AM UTC
Root cause: There are currently two connection paths between the Perth Edge site and the wider Microsoft network in Sydney. These connection paths are provided and managed by local ISPs and fiber cable providers in the region. On December 4, an undersea cable cut event occurred on one of the connection paths. Whilst we continue to work with the local third-party fiber cable provider to restore the connection path, the service has remained stable, as the services could still leverage the alternate connection path.
On two separate occasions, first on Sunday, December 7 and second on Wednesday, December 10, the remaining connection path experienced a short period of network interruption (including a fiber cut). Once this connection path became unavailable, requests from the Perth Edge site could not be connected to the wider Microsoft network in Sydney, resulting in impact to users. 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:Wed Dec 10 00:01:07 2025
Description:Title: Users in Australia may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Australia may experience issues when accessing various Microsoft 365 services.
More info: Users may have experienced issues when attempting to access various Microsoft services including but not limited to Microsoft Teams, SharePoint, OneDrive and Exchange/Outlook services.
Current status: We’ve narrowed down the cause of impact to a portion of our networking infrastructure which became degraded and subsequently unreachable. This further resulted in networking failures preventing Microsoft services from being accessible. Our automatic recovery system quickly failed over traffic to healthy infrastructure to mitigate impact. We are continuing our efforts to restore the impacted networking infrastructure and ensure impact does not reoccur.
Scope of impact: Any users served through the Australia region may be affected by this issue if attempting to access Microsoft services including Microsoft Teams. This information may be updated as our investigation continues.
Start time: Wednesday, December 10, 2025, at 2:48 AM UTC
Preliminary root cause: A portion of our networking infrastructure which became degraded and subsequently unreachable which resulted in Microsoft services being inaccessible.
Next update by: Wednesday, December 10, 2025, at 6:30 AM UTC
Time:Tue Dec 9 23:24:08 2025
Description:All Microsoft services have been fully recovered. We’ll continue investigating the cause of impact and provide the information within our next updates.
This quick update is designed to give the latest information on this issue.
Time:Tue Dec 9 23:19:42 2025
Description:Title: Users in Australia may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Australia may experience issues when accessing various Microsoft 365 services.
Current status: We've confirmed from the onset of this incident that our automated recovery services successfully returned our service to a healthy state. We'll continue to monitor our Microsoft 365 services to ensure stability while we maintain focused on investigating the root cause of impact. We currently suspect that a networking failure may have contributed to the problem, resulting in customer impact.
Scope of impact: Any users served through the Australia region may be affected by this issue if attempting to access Microsoft services including Microsoft Teams. This information may be updated as our investigation continues.
Next update by: Wednesday, December 10, 2025, at 5:30 AM UTC
Time:Tue Dec 9 22:46:24 2025
Description:According to our telemetry, service health has mostly recovered. We're continuing to monitor recovery and in parallel investigate the initial cause of impact.
This quick update is designed to give the latest information on this issue.
Time:Tue Dec 9 22:35:50 2025
Description:Title: Users in Australia may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Australia may experience issues when accessing various Microsoft 365 services.
Current Status: We're reviewing available telemetry to determine the source of impact. In tandem, we're observing recovery within our service for some users. We’ll provide more information within the next update.
Scope of impact: Any users served through the Australia region may be affected by this issue if attempting to access Microsoft services including Microsoft Teams. This information may be updated as our investigation continues.
Next update by: Wednesday, December 10, 2025, at 4:30 AM UTC
Time:Tue Dec 9 22:09:20 2025
Description:Title: Users in Australia may experience issues accessing Microsoft services including Microsoft Teams and Microsoft 365
User impact: Users in Australia may experience issues when accessing various Microsoft 365 services.
Current status: We're investigating user reports of impact with various Microsoft 365 services, predominantly the Microsoft Teams service. We'll provide an update within 30 minutes.

PB1192344 - Users may have been unable to access the Microsoft Power BI and Microsoft Fabric services

Status:postIncidentReviewPublished
Start Time:Fri Dec 5 00:40:00 2025
End Time:Sat Dec 6 06:10:00 2025
Service:Power BI
Feature Group:PowerBI.com
Classification:incident
Last Updated:Fri Dec 12 18:59:00 2025
Root Cause:Microsoft Power BI and Fabric services experienced degraded performance due to a hardware thermal event in the Norway West region, which impacted nodes hosting service resources. Customers with tenants in Norway West may have encountered service interaction issues, while users in other regions experienced intermittent slowness when loading the Admin Portal, rendering the Capacity Metrics App, and accessing license information in Workspace settings. No further scenarios were impacted.
Next Update:N/A

Details

Time:Fri Dec 12 18:59:00 2025
Description:A post-incident report has been published.
Time:Tue Dec 9 20:04:46 2025
Description:A post-incident report has been published.
Time:Sat Dec 6 07:45:54 2025
Description:Title: Users may have been unable to access the Microsoft Power BI and Microsoft Fabric services
User impact: Users may have been unable to access the Microsoft Power BI and Microsoft Fabric services.
More info: Users hosted in the Norway West region that also had capacities in this region would have temporarily experienced read-only mode while remediation was in progress.
Previously, users located in other regions may have observed intermittent slowness loading the Admin Portal, rendering the Capacity Metrics App, and accessing license information in Workspace settings. This impact was mitigated as of Friday, December 5, 2025, at 9:50 PM UTC.
Final status: We've confirmed after a period of monitoring that the services are restored and the issue is no longer occurring.
Scope of impact: This issue may have potentially impacted any user accessing Power BI and Microsoft Fabric services.
Start time: Friday, December 5, 2025, at 5:40 AM UTC
End time: Saturday, December 6, 2025, at 11:10 AM UTC
Root cause: Microsoft Power BI and Fabric services experienced degraded performance due to a hardware thermal event in the Norway West region, which impacted nodes hosting service resources. Customers with tenants in Norway West may have encountered service interaction issues, while users in other regions experienced intermittent slowness when loading the Admin Portal, rendering the Capacity Metrics App, and accessing license information in Workspace settings. No further scenarios were impacted.
To maintain continuity, requests were redirected to secondary resources; however, global users experienced additional latency due to DNS resolution delays to Norway West endpoints, resulting in slower service interactions.
Next steps: -For a more comprehensive list of next steps and actions, please refer to the Post Incident Report document.
This is the final update for the event.
Time:Sat Dec 6 01:42:05 2025
Description:Title: Users may be unable to access the Microsoft Power BI and Microsoft Fabric services
User impact: Users may be unable to access the Power BI and Microsoft Fabric services.
More info: Users hosted in the Norway West region that also have capacities in this region will temporarily experience read-only mode while remediation is in progress.
Previously, users located in other regions may have observed intermittent slowness loading the Admin Portal, rendering the Capacity Metrics App, and accessing license information in Workspace settings. This impact has been mitigated of Friday, December 5, 2025, at 9:50 PM UTC.
Current status: The cooling system errors have been fixed and we're working to restore the full functionality for all users. According to telemetry, recovery is around 90 percent complete, and we anticipate that services will be nearing full restoration by the next update time.
Scope of impact: This issue may potentially impact any user accessing Power BI and Microsoft Fabric services.
Start time: Friday, December 5, 2025, at 5:40 AM UTC
Root cause: A cooling system failure in a section of infrastructure that supports timely access to the Power BI and Microsoft Fabric services is causing the section of infrastructure to run too hot and is leading to impact.
Next update by: Saturday, December 6, 2025, at 2:00 PM UTC
Time:Fri Dec 5 20:18:15 2025
Description:Title: Users may be unable to access the Microsoft Power BI and Microsoft Fabric services
User impact: Users may be unable to access the Power BI and Microsoft Fabric services.
More info: Users hosted in the Norway West region that also have capacities in this region will temporarily experience read-only mode while remediation is in progress.
Previously, users located in other regions may have observed intermittent slowness loading the Admin Portal, rendering the Capacity Metrics App, and accessing license information in Workspace settings. This impact has been mitigated of Friday, December 5, 2025, at 9:50 PM UTC.
Current status: We've successfully reapplied our traffic management processes to mitigate the intermittent impact to users located outside of the Norway West region. In tandem, we're continuing our work to address the cooling system errors and restore full functionality for all users.
Scope of impact: This issue may potentially impact any user accessing Power BI and Microsoft Fabric services.
Start time: Friday, December 5, 2025, at 5:40 AM UTC
Root cause: A cooling system failure in a section of infrastructure that supports timely access to the Power BI and Microsoft Fabric services is causing the section of infrastructure to run too hot and is leading to impact.
Next update by: Saturday, December 6, 2025, at 8:00 AM UTC
Time:Fri Dec 5 13:53:45 2025
Description:Title: Users may be unable to access the Microsoft Power BI and Microsoft Fabric services
User impact: Users may be unable to access the Power BI and Microsoft Fabric services.
More info: Users hosted in the Norway West region that also have capacities in this region will temporarily experience read-only mode while remediation is in progress.
Users located in other regions may notice intermittent slowness in the following areas: Admin Portal Capacity Metrics App Licensing Settings
Current status: While we're continuing to progress the final actions to restore the cooling system, some portions of affected infrastructure are taking longer than anticipated to ingest the changes. We've updated our estimation for full recovery to Saturday, December 6, 2025, at 3:00 AM UTC.
Scope of impact: This issue may potentially impact any user accessing Power BI and Microsoft Fabric services.
Start time: Friday, December 5, 2025, at 5:40 AM UTC
Estimated time to resolve: We anticipate the cooling system issue will be resolved and full write functionality restored by Saturday, December 6, 2025, at 3:00 AM UTC.
Root cause: A cooling system failure in a section of infrastructure that supports timely access to the Power BI and Microsoft Fabric services is causing the section of infrastructure to run too hot, is leading to impact.
Next update by: Saturday, December 6, 2025, at 3:00 AM UTC
Time:Fri Dec 5 11:59:57 2025
Description:Title: Users may be unable to access the Microsoft Power BI and Microsoft Fabric services
User impact: Users may be unable to access the Power BI and Microsoft Fabric services.
More info: Users hosted in the Norway West region that also have capacities in this region will temporarily experience read-only mode while remediation is in progress.
Users located in other regions may notice intermittent slowness in the following areas: Admin Portal Capacity Metrics App Licensing Settings
Current status: We're implementing the final actions to fix the cooling system and restore write functionality, and we anticipate this process will complete and remediate the impact by our next scheduled communications update.
Scope of impact: This issue may potentially impact any user accessing Power BI and Microsoft Fabric services.
Start time: Friday, December 5, 2025, at 5:40 AM UTC
Estimated time to resolve: We anticipate the cooling system issue will be resolved and full write functionality restored by Friday, December 5, 2025, at 9:30 PM UTC.
Root cause: A cooling system failure in a section of infrastructure that supports timely access to the Power BI and Microsoft Fabric services is causing the section of infrastructure to run too hot, is leading to impact.
Next update by: Friday, December 5, 2025, at 9:30 PM UTC
Time:Fri Dec 5 07:27:38 2025
Description:Title: Users may be unable to access the Microsoft Power BI and Microsoft Fabric services
User impact: Users may be unable to access the Power BI and Microsoft Fabric services.
More info: Users hosted in the Norway West region that also have capacities in this region will temporarily experience read-only mode while remediation is in progress.
Users located in other regions may notice intermittent slowness in the following areas: Admin Portal Capacity Metrics App Licensing Settings
Current status: We’re continuing to resolve the cooling system issue so that full write functionality will be restored. We’ll share a timeline for complete resolution as soon as it becomes available.
Scope of impact: This issue may potentially impact any user accessing the Power BI and Microsoft Fabric services.
Start time: Friday, December 5, 2025, at 5:40 AM UTC
Root cause: A cooling system failure in a section of infrastructure that supports timely access to the Power BI and Microsoft Fabric services is causing the section of infrastructure to run too hot, is leading to impact.
Next update by: Friday, December 5, 2025, at 6:30 PM UTC
Time:Fri Dec 5 04:39:47 2025
Description:Title: Users may be unable to access the Microsoft Power BI and Microsoft Fabric services
User impact: Users may be unable to access the Power BI and Microsoft Fabric services.
More info: This issue is mainly impacting access for users hosted in the Norway West region that also have capacities in this region.
Users located in other regions may notice intermittent slowness in the following areas: Admin Portal Capacity Metrics App Licensing Settings
Current status: We’ve successfully rerouted connections to alternate infrastructure, mitigating the impact on read operations. However, write operations remain affected. Once the cooling system issue is resolved, full write functionality will be restored. We’ll share a timeline for complete resolution as soon as it becomes available.
Scope of impact: This issue may potentially impact any user attempting to access the Power BI and Microsoft Fabric services.
Start time: Friday, December 5, 2025, at 5:40 AM UTC
Root cause: A cooling system failure in a section of infrastructure that supports timely access to the Power BI and Microsoft Fabric services, which is causing the section of infrastructure to run too hot, is leading to impact.
Next update by: Friday, December 5, 2025, at 1:30 PM UTC
Time:Fri Dec 5 02:31:58 2025
Description:Title: Users may be unable to access the Microsoft Power BI and Microsoft Fabric service
User impact: Users may be unable to access the Power BI and Fabric service.
More info: This issue is mainly impacting access for users hosted in the Norway West region that also have capacities in this region.
Users located in other regions may notice intermittent slowness in the following areas: Admin Portal Capacity Metrics App Licensing Settings
Current status: A cooling system failure in a portion of infrastructure that supports timely access to the Power BI and Fabric services is running too hot, causing impact. We're working to reroute connections to alternate infrastructure to remediate the impact.
Scope of impact: This issue may potentially impact any user attempting to access the Power BI and Fabric services.
Start time: Friday, December 5, 2025, at 5:40 AM UTC
Root cause: A cooling system failure in the portion of infrastructure that supports timely access to the Power BI and Fabric services, which is causing the portion of infrastructure to run too hot, leading to impact.
Next update by: Friday, December 5, 2025, at 10:00 AM UTC
Time:Fri Dec 5 01:56:14 2025
Description:Title: Users may be unable to access the Microsoft Power BI and Microsoft Fabric service
User impact: Users may be unable to access the Power BI and Fabric service.
Current status: We're investigating a potential issue with Power BI and Fabric and are checking for impact to your organization. We'll provide an update within 30 minutes.

MO1193675 - Admins may be unable to make changes to their organization information in the Microsoft 365 admin center

Status:serviceRestored
Start Time:Tue Dec 2 10:54:00 2025
End Time:Thu Dec 11 21:00:00 2025
Service:Microsoft 365 suite
Feature Group:Administration
Classification:advisory
Last Updated:Thu Dec 11 21:32:46 2025
Root Cause:A recent change intended to simplify the User Interface (UI) for the organization information page of the Microsoft 365 admin center introduced an issue causing admins' updates to fail to save.
Next Update:N/A

Details

Time:Thu Dec 11 21:21:14 2025
Description:Title: Admins may be unable to make changes to their organization information in the Microsoft 365 admin center
User impact: Admins may have been unable to make changes to their organization information in the Microsoft 365 admin center.
More info: Specifically, admins may have been unable to save while updating their technical contact and preferred language settings.
Final status: The deployment of the code fix has completed, and after a period of monitoring, we've confirmed impact was remediated.
Scope of impact: This issue may have affected any admin attempting to update their organization's technical contact and preferred language settings on the organization information page of the Microsoft 365 admin center.
Start time: Thursday, October 2, 2025, at 3:54 PM UTC
End time: Friday, December 12, 2025, at 2:00 AM UTC
Root cause: A recent change intended to simplify the User Interface (UI) for the organization information page of the Microsoft 365 admin center introduced an issue causing admins' updates to fail to save.
Next steps: - To help prevent similar impact in the future, we're further reviewing our update release procedures to identify issues before being deployed.
This is the final update for the event.
Time:Wed Dec 10 18:00:03 2025
Description:Title: Admins may be unable to make changes to their organization information in the Microsoft 365 admin center
User impact: Admins may be unable to make changes to their organization information in the Microsoft 365 admin center.
More info: Specifically, admins may be unable to save while updating their technical contact and preferred language settings.
Current status: We've created and are deploying a code fix that is expected to complete and remediate impact by the end of Thursday, December 11, 2025. Admins may be able to make changes to their organizations information in the Microsoft 365 admin center as this fix saturates the affected environment.
Scope of impact: This issue may affect any admin attempting to update their organization's technical contact and preferred language settings on the organization information page of the Microsoft 365 admin center.
Start time: Thursday, October 2, 2025, at 3:54 PM UTC
Root cause: A recent change intended to simplify the User Interface (UI) for the organization information page of the Microsoft 365 admin center introduced an issue causing admins' updates to fail to save.
Next update by: Friday, December 12, 2025, at 2:30 AM UTC
Time:Tue Dec 9 17:28:36 2025
Description:Title: Admins may be unable to make changes to their organization information in the Microsoft 365 admin center
User impact: Admins may be unable to make changes to their organization information in the Microsoft 365 admin center.
More info: Specifically, admins may be unable to save while updating their technical contact and preferred language settings.
Current status: We've identified that a recent change intended to simplify the User Interface (UI) for the organization information page of the Microsoft 365 admin center introduced an issue causing admins' updates to fail to save. We're investigating why these failures are occurring while, in parallel, we work to develop a fix to correct the issue and remediate impact.
Scope of impact: This issue may affect any admin attempting to update their organization's technical contact and preferred language settings on the organization information page of the Microsoft 365 admin center.
Start time: Thursday, October 2, 2025, at 3:54 PM UTC
Root cause: A recent change intended to simplify the User Interface (UI) for the organization information page of the Microsoft 365 admin center introduced an issue causing admins' updates to fail to save.
Next update by: Thursday, December 11, 2025, at 12:30 AM UTC
Time:Tue Dec 9 17:13:09 2025
Description:Title: Admins may be unable to make changes to their organization information in the Microsoft 365 admin center
User impact: Admins may be unable to make changes to their organization information in the Microsoft 365 admin center.
More info: Specifically, admins may be unable to save while updating their technical contact and preferred language settings.
Current status: We're investigating a potential issue with the Microsoft 365 admin center and checking for impact to your organization. We'll provide an update within 30 minutes.

TM1194397 - Some admins may be unable change settings in Microsoft Teams Rooms devices via the Pro Portal

Status:serviceRestored
Start Time:Tue Dec 9 19:00:00 2025
End Time:Thu Dec 11 12:00:00 2025
Service:Microsoft Teams
Feature Group:Teams Components
Classification:advisory
Last Updated:Thu Dec 11 15:22:34 2025
Root Cause:A code issue in the telemetry import logic was preventing settings from being applied to devices in the Teams Rooms Pro Portal.
Next Update:N/A

Details

Time:Thu Dec 11 14:22:55 2025
Description:Title: Some admins may be unable change settings in Microsoft Teams Rooms devices via the Pro Portal
User impact: Admins may have been unable to change settings in Microsoft Teams Rooms devices via the Pro Portal.
Final status: Our deployment has completed to address the offending code issue causing users to be unable to change settings in Microsoft Teams Rooms devices via the Pro Portal. We've validated that impact is now resolved.
Scope of impact: Some admins attempting to change Microsoft Teams Room peripherals via the Pro Portal may have been impacted.
Start time: Wednesday, December 10, 2025, at 12:00 AM UTC
End time: Thursday, December 11, 2025, at 5:00 PM UTC
Root cause: A code issue in the telemetry import logic was preventing settings from being applied to devices in the Teams Rooms Pro Portal.
Next steps: - We're analyzing the offending code issue to isolate why the potential for impact wasn't caught prior to being introduced to our service. This analysis will help us to bolster and improve our future code implementations to prevent similar impact from occurring in the future.
This is the final update for the event.
Time:Thu Dec 11 11:14:20 2025
Description:Title: Some admins may be unable change settings in Microsoft Teams Rooms devices via the Pro Portal
User impact: Admins may be unable to change settings in Microsoft Teams Rooms devices via the Pro Portal.
Current status: We've initiated our deployment to address the offending code issue, and we anticipate this deployment to be completed by the end of Thursday, December 11, 2025. We aim to provide updates on our timeline to resolution as the deployment progresses.
Scope of impact: Your organization is affected by this event, and all admins attempting to change Microsoft Teams Room peripherals via the Pro Portal are impacted.
Root cause: A code issue in the telemetry import logic is preventing settings from being applied to devices in the Teams Rooms Pro Portal.
Next update by: Thursday, December 11, 2025, at 8:30 PM UTC
Time:Thu Dec 11 10:38:49 2025
Description:Title: Some admins may be unable change settings in Microsoft Teams Rooms devices via the Pro Portal
User impact: Admins may be unable to change settings in Microsoft Teams Rooms devices via the Pro Portal.
Current status: We’ve identified a code issue in the telemetry import logic that is preventing settings from being applied to devices in the Teams Rooms Pro Portal. We’ve developed a fix to restore telemetry import functionality and ensure settings can be successfully applied to devices. The fix is currently pending deployment.
Scope of impact: Some admins attempting to change Microsoft Teams Room peripherals via the Pro Portal may be impacted.
Next update by: Thursday, December 11, 2025, at 5:30 PM UTC
Time:Thu Dec 11 08:58:28 2025
Description:Title: Some admins may be unable change settings in Microsoft Teams Rooms devices via the Pro Portal
User impact: Admins may be unable to change settings in Microsoft Teams Rooms devices via the Pro Portal.
Current status: We’re reviewing HTTP Archive (HAR) files alongside API call patterns to help identify the root cause and next steps required to mitigate impact.
Scope of impact: Some admins attempting to change Microsoft Teams Room peripherals via the Pro Portal may be impacted.
Next update by: Thursday, December 11, 2025, at 4:00 PM UTC

SP1194366 - Some users may be unable to execute the SharePoint 2013 'Assign a Task' action or 'Send an Email' workflows

Status:serviceRestored
Start Time:Wed Dec 3 08:47:00 2025
End Time:Thu Dec 11 13:21:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:advisory
Last Updated:Thu Dec 11 14:09:14 2025
Root Cause:A recent change intended to update the way requests are structured caused the workflows to send malformed requests and resulted in the workflows failing.
Next Update:N/A

Details

Time:Thu Dec 11 14:09:14 2025
Description:Title: Some users may be unable to execute the SharePoint 2013 'Assign a Task' action or 'Send an Email' workflows
User impact: Users may have been unable to execute the SharePoint 2013 'Assign a Task' action or 'Send an Email' workflows.
Final status: We've confirmed that the recent change, which was intended to update the way requests are structured, caused the workflows to send malformed requests and resulted in the workflows failing. After reversing this change for a subset of affected users was verified to be successful in resolving the issue, we've applied this action broadly and confirmed with additional affected users that this has remediated the impact.
Scope of impact: Some users attempting to execute the 'Assign a Task' action or 'Send an Email' workflows were impacted.
Start time: Wednesday, December 3, 2025, at 1:47 PM UTC
End time: Thursday, December 11, 2025, at 6:21 PM UTC
Root cause: A recent change intended to update the way requests are structured caused the workflows to send malformed requests and resulted in the workflows failing.
Next steps: - We're continuing to analyze this change to better understand how it caused the malformed requests so we can correct any issues and ensure this doesn't reoccur.
This is the final update for the event.
Time:Thu Dec 11 12:33:57 2025
Description:Title: Some users may be unable to execute the SharePoint 2013 'Assign a Task' action or 'Send an Email' workflows
User impact: Users may be unable to execute the SharePoint 2013 'Assign a Task' action or 'Send an Email' workflows.
Current status: We're disabling the change we suspect may be causing the impact for a subset of affected users to validate whether this resolves the issue.
Scope of impact: Impact is specific to some users attempting to execute the 'Assign a Task' action or 'Send an Email' workflows are impacted.
Next update by: Thursday, December 11, 2025, at 7:30 PM UTC
Time:Thu Dec 11 10:11:33 2025
Description:Title: Some SharePoint 2013 users may be unable to execute the 'Assign a Task' action or 'Send an Email' workflows
User impact: SharePoint 2013 users may be unable to execute the 'Assign a Task' action or 'Send an Email' workflows
Current status: We suspect a recent update may be linked to the issue. Our team is actively analysing workflow logs to verify and address the cause promptly.
Scope of impact: Impact is specific to some users attempting to execute the 'Assign a Task' action or 'Send an Email' workflows are impacted.
Next update by: Thursday, December 11, 2025, at 5:30 PM UTC
Time:Thu Dec 11 08:06:53 2025
Description:Title: Some SharePoint 2013 users may be unable to execute the 'Assign a Task' action or 'Send an Email' workflows
User impact: SharePoint 2013 users may be unable to execute the 'Assign a Task' action or 'Send an Email' workflows
Current status: We're continuing to analyze support provided information to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users attempting to execute the 'Assign a Task' action or 'Send an Email' workflows are impacted.
Next update by: Thursday, December 11, 2025, at 3:30 PM UTC
Time:Thu Dec 11 06:24:43 2025
Description:Title: Some SharePoint 2013 users may be unable to execute the 'Assign a Task' action or 'Send an Email' workflows
User impact: SharePoint 2013 users may be unable to execute the 'Assign a Task' action or 'Send an Email' workflows.
Current status: We're analyzing support provided information to determine our next troubleshooting steps.
Scope of impact: Impact is specific to some users attempting to execute the 'Assign a Task' action or 'Send an Email' workflows are impacted.
Next update by: Thursday, December 11, 2025, at 1:30 PM UTC

MM1194456 - Users can't access custom pages from model driven apps created within Microsoft Power Apps and receive an error

Status:serviceRestored
Start Time:Thu Dec 11 08:00:00 2025
End Time:Thu Dec 11 10:38:00 2025
Service:Power Apps in Microsoft 365
Feature Group:Service and web access issues
Classification:advisory
Last Updated:Thu Dec 11 13:07:38 2025
Root Cause:A recent feature update intended to improve API throughput contained a configuration error, resulting in impact.
Next Update:N/A

Details

Time:Thu Dec 11 11:44:04 2025
Description:Title: Users can't access custom pages from model driven apps created within Microsoft Power Apps and receive an error
User impact: Users couldn't access custom pages from model driven apps created within Microsoft Power Apps and received an error.
More info: Affected users saw a "AppNotFound" error.
Final status: We've identified that a recent feature update intended to improve API throughput contains a configuration error, resulting in impact. We've reverted this feature change and validated this has remediated impact using service telemetry.
Scope of impact: Your organization was impacted by this event and all users attempting to access custom pages from model driven apps created within Microsoft Power Apps were affected.
Start time: Thursday, December 11, 2025, at 1:00 PM UTC
End time: Thursday, December 11, 2025, at 3:38 PM UTC
Root cause: A recent feature update intended to improve API throughput contained a configuration error, resulting in impact.
Next steps: - We're continuing our analysis of the impacting API 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:Thu Dec 11 11:11:54 2025
Description:Title: Users can't access custom pages from model driven apps created within Microsoft Power Apps and receive an error
User impact: Users couldn't access custom pages from model driven apps created within Microsoft Power Apps and received an error.
Current status: We've investigated a problem in which users couldn't access custom pages from model driven apps created within Microsoft Power Apps 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.

IT1190248 - Users may be unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard

Status:serviceRestored
Start Time:Wed Nov 26 19:00:00 2025
End Time:Tue Dec 9 13:00:00 2025
Service:Microsoft Intune
Feature Group:Microsoft Intune
Classification:advisory
Last Updated:Wed Dec 10 14:54:32 2025
Root Cause:An unexpected code issue with the EPM readiness dashboard in Intune was allowing policy creation for users who are not licensed for EPM.
Next Update:N/A

Details

Time:Wed Dec 10 14:54:32 2025
Description:Title: Users may be unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard
User impact: Users may have been unable to utilize the EPM readiness dashboard.
Final status: We’ve determined that the deployment of our fix is complete, we’ve made the necessary changes to re-enable the readiness dashboard, and we’ve confirmed from service telemetry that this issue is resolved.
Scope of impact: This issue may have impacted any user attempting to utilize the EPM readiness dashboard.
Start time: Thursday, November 27, 2025, at 12:00 AM UTC
End time: Tuesday, December 9, 2025, at 6:00 PM UTC
Root cause: An unexpected code issue with the EPM readiness dashboard in Intune was allowing policy creation for users who are not licensed for EPM.
Next steps: - We’re continuing our investigation to determine the underlying cause of the offending code issue to better detect and prevent issues like this from occurring in the future.
This is the final update for the event.
Time:Mon Dec 8 14:55:53 2025
Description:Title: Users may be unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard
User impact: Users may be unable to utilize the EPM readiness dashboard.
Current status: We've begun the deployment of our permanent fix, which we expect to fully saturate the environment in 48 hours. In the meantime, we've rolled back a non-essential feature in the readiness dashboard to relieve this impact while this long-term fix goes into effect.
Scope of impact: This issue may impact any user attempting to utilize the EPM readiness dashboard.
Start time: Thursday, November 27, 2025, at 12:00 AM UTC
Root cause: An unexpected code issue with the EPM readiness dashboard in Intune is allowing policy creation for users who are not licensed for EPM.
Next update by: Wednesday, December 10, 2025, at 9:00 PM UTC
Time:Thu Dec 4 15:45:33 2025
Description:Title: Users may be unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard
User impact: Users may be unable to utilize the EPM readiness dashboard.
Current status: Validation is complete and we’re initiating the process of applying our fix to the affected environment. We anticipate that we’ll have an estimation for impact resolution by our next scheduled update.
Scope of impact: This issue may impact any user attempting to utilize the EPM readiness dashboard.
Start time: Thursday, November 27, 2025, at 12:00 AM UTC
Root cause: An unexpected code issue with the EPM readiness dashboard in Intune is allowing policy creation for users who are not licensed for EPM.
Next update by: Monday, December 8, 2025, at 9:00 PM UTC
Time:Mon Dec 1 14:29:13 2025
Description:Title: Users may be unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard
User impact: Users may be unable to utilize the EPM readiness dashboard.
Current status: During our preparation to implement our solution, we identified an additional issue which needed to be addressed by the fix. We've updated the fix to ensure this issue is attended to, and we're performing our final validations before we apply it and reenable the EPM readiness dashboard to resolve the issue. We'll provide a timeline for remediation as one becomes available.
Scope of impact: This issue may impact any user attempting to utilize the EPM readiness dashboard.
Start time: Thursday, November 27, 2025, at 12:00 AM UTC
Root cause: An unexpected code issue with the EPM readiness dashboard in Intune is allowing policy creation for users who are not licensed for EPM.
Next update by: Thursday, December 4, 2025, at 9:00 PM UTC
Time:Wed Nov 26 21:03:35 2025
Description:Title: Users may be unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard
User impact: Users may be unable to utilize the EPM readiness dashboard.
Current status: We encountered an unexpected issue with the EPM readiness dashboard in Intune that is allowing policy creation for users who are not licensed for EPM. We've identified a fix for the issue and are temporarily disabling the EPM readiness dashboard while we implement the fix. We anticipate that the EPM readiness dashboard will be fixed and available by the next scheduled update time.
Scope of impact: This issue may impact any user attempting to utilize the EPM readiness dashboard.
Start time: Thursday, November 27, 2025, at 12:00 AM UTC
Root cause: An unexpected code issue with the EPM readiness dashboard in Intune is allowing policy creation for users who are not licensed for EPM.
Next update by: Monday, December 1, 2025, at 9:00 PM UTC
Time:Wed Nov 26 20:51:29 2025
Description:Title: Users may be unable to utilize the Endpoint Privilege Management (EPM) readiness dashboard
User impact: Users may be unable to utilize the EPM readiness dashboard.
Current status: We're investigating a potential issue with the Intune service and checking for impact to your organization. We'll provide an update within 30 minutes.

OD1193855 - Some users intermittently may have been unable to access Microsoft OneDrive content

Status:serviceRestored
Start Time:Tue Dec 9 20:15:00 2025
End Time:Wed Dec 10 07:09:00 2025
Service:Microsoft OneDrive
Feature Group:OneDrive for Business
Classification:incident
Last Updated:Wed Dec 10 10:41:29 2025
Root Cause:A section of infrastructure that facilitates access to Microsoft OneDrive content was performing below acceptable performance thresholds.
Next Update:N/A

Details

Time:Wed Dec 10 08:52:48 2025
Description:Title: Some users intermittently may have been unable to access Microsoft OneDrive content
User impact: Users intermittently may have been unable to access OneDrive content.
Final status: We've identified that a section of infrastructure that facilitates access to Microsoft OneDrive content was performing below acceptable performance thresholds. We've optimized traffic and performance parameters on the affected infrastructure, which has remediated impact.
Scope of impact: Impact was specific to some users located in North America and Brazil attempting to access OneDrive content.
Start time: Wednesday, December 10, 2025, at 1:15 AM UTC
End time: Wednesday, December 10, 2025, at 12:09 PM UTC
Root cause: A section of infrastructure that facilitates access to Microsoft OneDrive content was performing below acceptable performance thresholds.
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:Wed Dec 10 07:07:31 2025
Description:Title: Some users intermittently may be unable to access Microsoft OneDrive content
User impact: Users intermittently may be unable to access Microsoft OneDrive content.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users located in North America and Brazil attempting to access OneDrive content.
Next update by: Wednesday, December 10, 2025, at 2:00 PM UTC

SP1193854 - Some users intermittently may have been unable to access SharePoint Online sites

Status:serviceRestored
Start Time:Tue Dec 9 20:15:00 2025
End Time:Wed Dec 10 07:09:00 2025
Service:SharePoint Online
Feature Group:SharePoint Features
Classification:incident
Last Updated:Wed Dec 10 10:41:09 2025
Root Cause:A section of infrastructure that facilitates access to SharePoint Online sites was performing below acceptable performance thresholds.
Next Update:N/A

Details

Time:Wed Dec 10 08:52:03 2025
Description:Title: Some users intermittently may have been unable to access SharePoint Online sites
User impact: Users intermittently may have been unable to access SharePoint Online sites.
Final status: We've identified that a section of infrastructure that facilitates access to SharePoint Online sites was performing below acceptable performance thresholds. We've optimized traffic and performance parameters on the affected infrastructure, which has remediated impact.
Scope of impact: Impact was specific to some users located in North America and Brazil attempting to access SharePoint Online sites.
Start time: Wednesday, December 10, 2025, at 1:15 AM UTC
End time: Wednesday, December 10, 2025, at 12:09 PM UTC
Root cause: A section of infrastructure that facilitates access to SharePoint Online sites was performing below acceptable performance thresholds.
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:Wed Dec 10 07:07:30 2025
Description:Title: Some users intermittently may be unable to access SharePoint Online sites
User impact: Users intermittently may be unable to access SharePoint Online sites.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users located in North America and Brazil attempting to access SharePoint Online sites.
Next update by: Wednesday, December 10, 2025, at 2:00 PM UTC

DZ1193516 - Some admins may encounter errors when accessing Microsoft Defender for Endpoint features

Status:serviceRestored
Start Time:Thu Dec 4 05:00:00 2025
End Time:Tue Dec 9 13:05:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:incident
Last Updated:Tue Dec 9 14:00:47 2025
Root Cause:A recent change to support a specific authentication component leveraged in the affected scenario resulted in the impact. Next steps: - We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
Next Update:N/A

Details

Time:Tue Dec 9 14:00:47 2025
Description:Title: Some admins may encounter errors when accessing Microsoft Defender for Endpoint features
User impact: Admins may have encountered errors when accessing Microsoft Defender for Endpoint features.
More info: Admins and security operators may have encountered errors and failures when accessing multiple pages specific to Microsoft Defender for Endpoint in the Microsoft Defender portal. Impacted experiences included but may not have been limited to:
- Device Inventory - Threat Analytics - Secure Score - Machines API - Other pages that depend on related APIs
In addition, API requests may have returned '431 Request Header Fields Too Large' errors.
Final status: We’ve determined that a recent change to support a specific authentication component leveraged in the affected scenario resulted in the impact. We’ve successfully reverted the offending change and confirmed with affected users that this issue is resolved.
Scope of impact: Admins and security operators attempting to access the Microsoft Defender for Endpoint experiences listed above via the Microsoft Defender portal, or to make MDE API calls, may have been impacted.
Start time: Thursday, December 4, 2025, at 10:00 AM UTC
End time: Tuesday, December 9, 2025, at 6:05 PM UTC
Root cause: A recent change to support a specific authentication component leveraged in the affected scenario resulted in the impact. Next steps: - We’re reviewing our validation and updating procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for the event.
Time:Tue Dec 9 11:01:18 2025
Description:Title: Some admins may encounter errors when accessing Microsoft Defender for Endpoint features
User impact: Admins may encounter errors when accessing Microsoft Defender for Endpoint features.
More info: Admins and security operators may encounter errors and failures when accessing multiple pages specific to Microsoft Defender for Endpoint in the Microsoft Defender portal. Impacted experiences include but may not be limited to:
- Device Inventory - Threat Analytics - Secure Score - Machines API - Other pages that depend on related APIs
In addition, API requests may return '431 Request Header Fields Too Large' errors.
Current status: Review of service health telemetry indicates the rollback failed to reach all of the affected infrastructure. We've initiated a new rollback to validate if the suspected service update is causing impact, and in parallel we're testing a fix within a portion of the affected service infrastructure as a secondary remediation plan in case the rollback doesn't resolve the impact. We anticipate the rollback will complete by our next scheduled communications update.
Scope of impact: Admins and security operators attempting to access the Microsoft Defender for Endpoint experiences listed above via the Microsoft Defender portal, or to make MDE API calls, may be impacted.
Start time: Thursday, December 4, 2025, at 10:00 AM UTC
Next update by: Tuesday, December 9, 2025, at 8:00 PM UTC
Time:Tue Dec 9 09:04:20 2025
Description:Title: Some admins may encounter errors when accessing Microsoft Defender for Endpoint features
User impact: Admins may encounter errors when accessing Microsoft Defender for Endpoint features.
More info: Admins and security operators may encounter errors and failures when accessing multiple pages specific to Microsoft Defender for Endpoint (MDE) in the Microsoft Defender portal. Impacted experiences include, but may not be limited to:
- Device Inventory - Threat Analytics - Secure Score - Machines API - Other pages that depend on related APIs.
In addition, API requests may return '431 Request Header Fields Too Large' errors.
Current status: We’ve rolled back the recent change and confirmed that the process is now complete. We're currently monitoring service telemetry to check whether this action has mitigated the issue.
Scope of impact: Admins and security operators attempting to access the MDE experiences listed above via the Microsoft Defender portal, or to make MDE API calls, may be impacted.
Start time: Thursday, December 4, 2025, at 10:00 AM UTC
Next update by: Tuesday, December 9, 2025, at 4:00 PM UTC
Time:Tue Dec 9 07:03:11 2025
Description:Title: Some admins may encounter errors when accessing Microsoft Defender for Endpoint features
User impact: Admins may encounter errors when accessing Microsoft Defender for Endpoint features.
More info: Admins and security operators may encounter errors and failures when accessing multiple pages specific to Microsoft Defender for Endpoint (MDE) in the Microsoft Defender portal. Impacted experiences include, but may not be limited to:
- Device Inventory - Threat Analytics - Secure Score - Machines API - Other pages that depend on related APIs.
In addition, API requests may return '431 Request Header Fields Too Large' errors.
Current status: We've determined that a recent MDE service update may be causing problems with how information is sent between systems, leading to errors. We’re working to revert this change in an attempt to mitigate impact and to validate our root cause theory.
Scope of impact: Admins and security operators attempting to access the MDE experiences listed above via the Microsoft Defender portal, or to make MDE API calls, may be impacted.
Start time: Thursday, December 4, 2025, at 10:00 AM UTC
Next update by: Tuesday, December 9, 2025, at 2:00 PM UTC
Time:Tue Dec 9 05:05:43 2025
Description:Title: Some admins may encounter errors when accessing Microsoft Defender for Endpoint features
User impact: Admins may encounter errors when accessing Microsoft Defender for Endpoint features.
More info: Admins and security operators may encounter errors and failures when accessing multiple pages specific to Microsoft Defender for Endpoint (MDE) in the Microsoft Defender portal. Impacted experiences include, but may not be limited to:
- Device Inventory - Threat Analytics - Secure Score - Machines API - Other pages that depend on related APIs.
In addition, API requests may return '431 Request Header Fields Too Large' errors.
Current status: We’re still trying to isolate the source of impact. We’re investigating system changes and data routing as possible causes for the issue. We’ll share more information as soon as it’s available.
Scope of impact: Admins and security operators attempting to access the MDE experiences listed above via the Microsoft Defender portal, or to make MDE API calls, may be impacted.
Start time: Thursday, December 4, 2025, at 10:00 AM UTC
Next update by: Tuesday, December 9, 2025, at 12:00 PM UTC
Time:Tue Dec 9 02:14:17 2025
Description:Title: Admins attempting to access the Device Inventory page on the Microsoft Defender portal may see devices not load
User impact: Admins attempting to access the Device Inventory page on the Microsoft Defender portal may see devices not load.
More info: Other pages impacted: - Threat Analytics
Current status: We've been alerted to an issue where admins attempting to access the Device Inventory page or Thread Analytics pages on the Microsoft Defender portal may not see them load. We're reviewing service health telemetry and error logs to isolate the source of impact and determine our next steps.
Scope of impact: Admins attempting to access the Device Inventory or Threat Analytics pages on the Microsoft Defender portal may be impacted.
Next update by: Tuesday, December 9, 2025, at 10:30 AM UTC
Time:Tue Dec 9 01:59:40 2025
Description:Title: Admins attempting to access the Device Inventory page on the Microsoft Defender portal may see devices not load
User impact: Admins attempting to access the Device Inventory page on the Microsoft Defender portal may see devices not load.
More info: Other pages impacted: - Threat Analytics
Current status: We're investigating a potential issue with Microsoft Defender for Endpoint and checking for impact to your organization. We'll provide an update within 30 minutes.

PB1193603 - Users may be unable to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric

Status:serviceRestored
Start Time:Mon Dec 8 16:50:00 2025
End Time:Tue Dec 9 11:38:00 2025
Service:Power BI
Feature Group:PowerBI.com
Classification:advisory
Last Updated:Tue Dec 9 12:56:14 2025
Root Cause:A maintenance action to disable specific features related to Git operations resulted in unintended impact.
Next Update:N/A

Details

Time:Tue Dec 9 12:53:58 2025
Description:Title: Users may be unable to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric
User impact: Users may have been unable to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric.
Final status: We’ve completed the deployment of our fix to re-enable these features and remediate impact and confirmed the issue is now resolved.
Scope of impact: This issue was affecting any user attempting to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric.
Start time: Monday, December 8, 2025, at 9:50 PM UTC
End time: Tuesday, December 9, 2025, at 4:38 PM UTC
Root cause: A maintenance action to disable specific features related to Git operations resulted in unintended impact.
Next steps: - We're investigating the maintenance process used to better understand what caused the issue and to prevent future impact.
This is the final update for the event.
Time:Tue Dec 9 12:18:23 2025
Description:Title: Users may be unable to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric
User impact: Users may be unable to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric.
Current status: We've initiated the deployment of our fix to re-enable these features and remediate impact. We expect this will complete, resolving the issue for all users, by our next scheduled communication update.
Scope of impact: This issue may affect any user attempting to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric.
Start time: Monday, December 8, 2025, at 9:50 PM UTC
Root cause: A recent maintenance action to disable specific features relating to Git operations is resulting in impact, which wasn’t an expected consequence of this maintenance action.
Next update by: Tuesday, December 9, 2025, at 7:30 PM UTC
Time:Tue Dec 9 11:08:10 2025
Description:Title: Users may be unable to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric
User impact: Users may be unable to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric.
More info: When attempting to use actions such as GET/POST/PUT that utilize APIs through Git integrations, users may receive a 403 error.
Current status: We've identified that a recent maintenance action to disable specific features relating to Git operations is resulting in impact, which wasn’t an expected consequence of this maintenance action. We've prepared a fix to re-enable these features and are working to establish a timeline for their enablement and impact remediation.
Scope of impact: This issue may affect any user attempting to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric.
Start time: Monday, December 8, 2025, at 9:50 PM UTC
Root cause: A recent maintenance action to disable specific features relating to Git operations is resulting in impact, which wasn’t an expected consequence of this maintenance action.
Next update by: Tuesday, December 9, 2025, at 5:30 PM UTC
Time:Tue Dec 9 10:54:54 2025
Description:Title: Users may be unable to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric
User impact: Users may be unable to use Git integrations utilizing APIs to perform multiple actions in Microsoft Fabric.
More info: When attempting to use actions such as GET/POST/PUT that utilize APIs through Git integrations, users may receive a 403 error.
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.

DZ1191468 - Multiple issues with the Microsoft Defender portal

Status:postIncidentReviewPublished
Start Time:Tue Dec 2 03:30:00 2025
End Time:Tue Dec 2 06:13:00 2025
Service:Microsoft Defender XDR
Feature Group:Microsoft Defender for Endpoint
Classification:incident
Last Updated:Tue Dec 9 10:12:10 2025
Root Cause:An increase in latency during requests to an internal service, responsible for verifying user permissions to access the Microsoft Defender portal, activated an aggressive retry mechanism for those requests. The persistence of this retry logic, together with additional requests entering the same state, led to a substantial spike in traffic and elevated CPU utilization across affected components. Although automated recovery systems identified the issue and initiated efforts to increase processing throughput, the infrastructure could not scale quickly enough to accommodate the surge in demand. As a result, CPU utilization reached operational limits, thread capacities were exceeded, and subsequent requests experienced timeouts as they could not be processed in a timely manner.
Next Update:N/A

Details

Time:Tue Dec 9 10:12:10 2025
Description:A post-incident report has been published.
Time:Thu Dec 4 13:34:27 2025
Description:A post-incident report has been published.
Time:Tue Dec 2 11:30:35 2025
Description:Title: Multiple issues with the Microsoft Defender portal
User impact: Users may have experienced multiple issues when trying to access or use features within the Microsoft Defender portal
More info: Impacted functionalities included, but were not limited to: - Advanced Threat Hunting tables and related alerts not appearing - Custom detections not appearing - Device Inventory not appearing - Settings not appearing
Final status: We’ve received confirmation from the additional organizations that the issue is resolved. Monitoring telemetry continued to show the service has remained stable for an extended period of time.
Scope of impact: This issue may have impacted users attempting to access or use features within the Microsoft Defender portal.
Start time: Tuesday, December 2, 2025, at 8:30 AM UTC
End time: Tuesday, December 2, 2025, at 11:13 AM UTC
Root cause: An increase in latency during requests to an internal service, responsible for verifying user permissions to access the Microsoft Defender portal, activated an aggressive retry mechanism for those requests. The persistence of this retry logic, together with additional requests entering the same state, led to a substantial spike in traffic and elevated CPU utilization across affected components. Although automated recovery systems identified the issue and initiated efforts to increase processing throughput, the infrastructure could not scale quickly enough to accommodate the surge in demand. As a result, CPU utilization reached operational limits, thread capacities were exceeded, and subsequent requests experienced timeouts as they could not be processed in a timely manner.
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 Dec 2 10:06:28 2025
Description:We've received the HAR traces and are currently analyzing them.
This quick update is designed to give the latest information on this issue.
Next update by: Tuesday, December 2, 2025, at 5:00 PM UTC
Time:Tue Dec 2 09:42:04 2025
Description:Title: Multiple issues with the Microsoft Defender portal
User impact: Users may experience multiple issues when trying to access or use functionalities within the Microsoft Defender portal
More info: Impacted functionalities include, but are not limited to: - Advanced Threat Hunting Alerts not appearing - Devices not appearing
Current status: We've received confirmation from additional organizations that the issue is resolved for them, and monitoring telemetry continues to show CPU utilization remains within acceptable thresholds. We're working with a small number of organizations who reported that the issue still persists and coordinating with them to collect additional client-side diagnostics and HTTP Archive format (HAR) traces to assist our investigation.
Scope of impact: This issue may impact users attempting to access or use features within the Microsoft Defender portal.
Next update by: Tuesday, December 2, 2025, at 5:00 PM UTC
Time:Tue Dec 2 08:25:49 2025
Description:Some of the customers who reported that the issue was still occurring have now confirmed resolution. Service telemetry continues to show that service remains healthy. We're continuing our period of extended monitoring and investigating the other isolated reports of impact.
This quick update is designed to give the latest information on this issue.
Next update by: Tuesday, December 2, 2025, at 3:00 PM UTC
Time:Tue Dec 2 07:55:22 2025
Description:Title: Multiple issues with the Microsoft Defender portal
User impact: Users may experience multiple issues when trying to access or use functionalities within the Microsoft Defender portal
More info: Impacted functionalities include, but are not limited to: - Advanced Threat Hunting Alerts not appearing - Devices not appearing
Current status: We've identified that a spike in traffic caused high Central Processing Unit (CPU) utilization on components that facilitate Microsoft Defender portal functionalities. We've applied a mitigation and added more processing throughput, and telemetry shows that availability has recovered. We've received multiple reports from organizations that the issue is resolved, however, there are a small number of isolated reports that the issue still persists. We're reviewing service error logs from those isolated reports to determine the next steps.
Scope of impact: This issue may impact users attempting to access or use features within the Microsoft Defender portal.
Next update by: Tuesday, December 2, 2025, at 3:00 PM UTC
Time:Tue Dec 2 07:32:54 2025
Description:We've received reports from some customers that the issue still persists. We're reviewing service telemetry and error logging for these customers to determine the next steps.
This quick update is designed to give the latest information on this issue.
Next update by: Tuesday, December 2, 2025, at 2:00 PM UTC
Time:Tue Dec 2 07:17:49 2025
Description:We've applied a mitigation and telemetry is showing the service is performing within expected thresholds. We're entering a period of extended monitoring to confirm resolution. We'll provide a full update with more details shortly.
This quick update is designed to give the latest information on this issue.
Time:Tue Dec 2 06:52:19 2025
Description:Title: Multiple issues with the Microsoft Defender portal
User impact: Users may experience multiple issues when trying to access or use functionalities within the Microsoft Defender portal.
More info: Impacted functionalities include, but are not limited to: - Advanced Threat Hunting - Devices
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: This issue may impact users attempting to access or use features within the Microsoft Defender portal.
Next update by: Tuesday, December 2, 2025, at 2:00 PM UTC
Time:Tue Dec 2 06:12:35 2025
Description:Title: We're looking into a potential problem impacting the Microsoft Defender XDR portal
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with the Microsoft Defender XDR portal and checking for impact to your organization. We'll provide an update within 60 minutes.

MV1193367 - Some users may be unable to access Viva Glint

Status:serviceRestored
Start Time:Mon Dec 8 14:58:00 2025
End Time:Mon Dec 8 16:27:00 2025
Service:Microsoft Viva
Feature Group:Viva Glint
Classification:incident
Last Updated:Mon Dec 8 17:43:18 2025
Root Cause:A recent service update triggered database locking which inhibited the service from processing request traffic.
Next Update:N/A

Details

Time:Mon Dec 8 17:10:19 2025
Description:Title: Some users may be unable to access Viva Glint
User impact: Users may have been unable to access Viva Glint.
Final status: Our service monitoring metrics alerted us to an availability drop for users in the United States who were unable to access Viva Glint. We investigated the issue and determined that a recent service update triggered database locking which inhibited the service from processing request traffic. We identified what caused the database locking, cleared the prohibiting issue, and confirmed that impact was remediated.
Scope of impact: Users in the United States may have been unable to access Viva Glint.
Start time: Monday, December 8, 2025, at 7:58 PM UTC
End time: Monday, December 8, 2025, at 9:43 PM UTC
Root cause: A recent service update triggered database locking which inhibited the service from processing request traffic.
Next steps: - We're analyzing the offending service update to determine why the potential for impact wasn't caught during the update testing and validation phases. This analysis will help us to improve the resilience of our future updates and to ensure similar impact doesn't occur in future.
This is the final update for the event.
Time:Mon Dec 8 16:50:12 2025
Description:Title: Some users may be unable to access Viva Glint
User impact: Users may have been unable to access Viva Glint.
Current status: We've investigated a problem in which users in the United States may have been unable to access Viva Glint, 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.

EX1192586 - Some users may be unable to open inbound Secure/Multipurpose Internet Mail Extensions (S/MIME) encrypted email messages

Status:serviceRestored
Start Time:Sat Nov 29 19:00:00 2025
End Time:Mon Dec 8 05:00:00 2025
Service:Exchange Online
Feature Group:E-Mail timely delivery
Classification:incident
Last Updated:Mon Dec 8 15:47:46 2025
Root Cause:A recent service update that intended to introduce a new Microsoft Defender for Office 365 feature incorrectly marked S/MIME messages for delivery, resulting in impact.
Next Update:N/A

Details

Time:Mon Dec 8 15:47:46 2025
Description:Title: Some users may be unable to open inbound Secure/Multipurpose Internet Mail Extensions (S/MIME) encrypted email messages
User impact: Users may have been unable to open some inbound S/MIME encrypted email messages in Exchange Online.
More info: This issue affected users with the Dynamic Delivery policy enabled. We previously disabled Dynamic Delivery "for S/MIME messages" while we worked to resolve this issue, which has since been re-enabled.
Final status: We've confirmed that the configuration has been updated and validated this action has remediated the impact using service telemetry.
Scope of impact: Some users with Dynamic Delivery enabled that were attempting to open S/MIME encrypted email messages may have been impacted.
Start time: Sunday, November 30, 2025, at 12:00 AM UTC
End time: Monday, December 8, 2025, at 10:00 AM UTC
Root cause: A recent service update that intended to introduce a new Microsoft Defender for Office 365 feature incorrectly marked S/MIME messages for delivery, resulting in impact.
Next steps: - We're continuing our analysis of the impacting configuration change to better identify and prevent similar issues in the future.
This is the final update for the event.
Time:Mon Dec 8 11:48:52 2025
Description:Title: Some users may be unable to open inbound Secure/Multipurpose Internet Mail Extensions (S/MIME) encrypted email messages
User impact: Users may be unable to open some inbound S/MIME encrypted email messages in Exchange Online.
More info: This issue strictly impacts users with the Dynamic Delivery policy enabled. We've disabled Dynamic Delivery "for S/MIME messages" while we work to resolve this issue. Additionally, some users see a "Safe Attachments Scan in Progress" message upon opening an encrypted inbound email message.
Current status: We've recovered the majority of impacted S/MIME encrypted email messages and are completing final validations that all messages have been recovered. While we verify, please raise a support case if your organization has any S/MIME encrypted email messages that are still impacted.
Scope of impact: Some users with Dynamic Delivery enabled that are attempting to open S/MIME encrypted email messages may be impacted.
Start time: Sunday, November 30, 2025, at 12:00 AM UTC
Root cause: A recent service update that intended to introduce a new Microsoft Defender for Office 365 feature incorrectly marked S/MIME messages for delivery, resulting in impact.
Next update by: Monday, December 8, 2025, at 10:00 PM UTC
Time:Sun Dec 7 15:45:21 2025
Description:Title: Some users may be unable to open inbound Secure/Multipurpose Internet Mail Extensions (S/MIME) encrypted email messages
User impact: Users may be unable to open some inbound S/MIME encrypted email messages in Exchange Online.
More info: This issue strictly impacts users with the Dynamic Delivery policy enabled.
We've disabled Dynamic Delivery "for S/MIME messages" while we work to resolve this issue.
Additionally, some users see a "Safe Attachments Scan in Progress" message upon opening an encrypted inbound email message.
Current status: Our internal service telemetry has validated that our fix is addressing the problems, and that users have been able to open all new inbound S/MIME encrypted email messages since Friday, December 5, at approximately 9:40 PM UTC. Following our completed fix deployment, we're enabling the recovery of the previously undelivered messages, which is expected to be complete by our next scheduled communication update.
Scope of impact: Some users with Dynamic Delivery enabled attempting to open S/MIME encrypted email messages may be impacted.
Start time: Sunday, November 30, 2025, at 12:00 AM UTC
Root cause: A recent service update that intended to introduce a new Microsoft Defender for Office 365 feature incorrectly marked S/MIME messages for delivery, resulting in impact.
Next update by: Monday, December 8, 2025, at 6:30 PM UTC
Time:Sun Dec 7 00:08:35 2025
Description:Title: Some users may be unable to open inbound Secure/Multipurpose Internet Mail Extensions (S/MIME) encrypted email messages
User impact: Users may intermittently be unable open some inbound S/MIME encrypted email messages in Exchange Online.
More info: This issue strictly impacts users with the Dynamic Delivery policy enabled.
We've temporarily disabled Dynamic Delivery "for S/MIME messages" while we work to resolve this issue
Additionally, some users see a "Safe Attachments Scan in Progress" message upon opening an encrypted inbound email message.
Current status: Our previously mentioned fix is continuing to deploy across the affected environments and is taking longer than initially expected to complete. As the deployment progresses, many of the affected users should start to see recovery and be able to open previously impacted S/MIME messages. Additionally, we’re exploring options available for expediting this fix deployment so that we can swiftly resolve the issue.
Scope of impact: Some users with Dynamic Delivery enabled attempting to open S/MIME encrypted email messages may be impacted.
Start time: Sunday, November 30, 2025, at 12:00 AM UTC
Next update by: Sunday, December 7, 2025, at 10:00 PM UTC
Time:Fri Dec 5 23:39:22 2025
Description:Title: Some users may be unable to open inbound Secure/Multipurpose Internet Mail Extensions (S/MIME) encrypted email messages
User impact: Users may intermittently be unable open some inbound S/MIME encrypted email messages in Exchange Online.
More info: This issue strictly impacts users with the Dynamic Delivery policy enabled.
We've temporarily disabled Dynamic Delivery "for S/MIME messages" while we work to resolve this issue
Additionally, some users see a "Safe Attachments Scan in Progress" message upon opening an encrypted inbound email message.
Current status: We’ve completed the aforementioned validations for our fix to allow the delivered S/MIME encrypted email messages to be viewed as expected and we’re deploying this fix to the affected environments. We anticipate that the fix will be fully saturated across the environments by our next scheduled communications update. In parallel, our review of the HAR network trace logs has led us to suspect a recent change may not be fully compatible with the Dynamic Delivery policy being enabled and we’re working on testing this theory in our internal environment.
Scope of impact: Some users with Dynamic Delivery enabled attempting to open S/MIME encrypted email messages may be impacted.
Start time: Sunday, November 30, 2025, at 12:00 AM UTC
Next update by: Sunday, December 7, 2025, at 6:30 AM UTC
Time:Fri Dec 5 17:23:26 2025
Description:Title: Some users may be unable to open inbound Secure/Multipurpose Internet Mail Extensions (S/MIME) encrypted email messages
User impact: Users may intermittently be unable open some inbound S/MIME encrypted email messages in Exchange Online.
More info: This issue strictly impacts users with the Dynamic Delivery policy enabled. We've temporarily disabled Dynamic Delivery while we work to resolve this issue. This action may result in potential delays of up to fifteen minutes for users to receive email messages with attachments. The length of the delay will depend on the attachments associated with the email message.
Additionally, some users see a "Safe Attachments Scan in Progress" message upon opening an encrypted inbound email message.
Current status: We're continuing our review of the HAR network trace logs to progress our root cause investigation while our efforts to validate the fix are ongoing. We'll aim to provide a timeline for the validations to complete by our next scheduled communications update.
Scope of impact: Some users with Dynamic Delivery enabled attempting to open S/MIME encrypted email messages may be impacted.
Start time: Sunday, November 30, 2025, at 12:00 AM UTC
Next update by: Saturday, December 6, 2025, at 6:00 AM UTC
Time:Fri Dec 5 15:27:42 2025
Description:Title: Some users may be unable to open inbound Secure/Multipurpose Internet Mail Extensions (S/MIME) encrypted email messages
User impact: Users may intermittently be unable open some inbound S/MIME encrypted email messages in Exchange Online.
More info: This issue strictly impacts users with the Dynamic Delivery policy enabled.
We've temporarily disabled Dynamic Delivery while we work to resolve this issue. This action may result in potential delays of up to fifteen minutes for users to receive email messages with attachments. The length of the delay will depend on the attachments associated with the email message.
Additionally, some users see a "Safe Attachments Scan in Progress" message upon opening an encrypted inbound email message.
Current status: While we review HTTP Archive format (HAR) network trace logs to isolate the underlying cause of impact, we've disabled Dynamic Delivery to avoid new email messages from becoming impacted. In parallel, we're in the process of validating a fix to allow delivered S/MIME encrypted email messages to be viewed as expected.
Scope of impact: Some users with Dynamic Delivery enabled attempting to open S/MIME encrypted email messages may be impacted.
Start time: Sunday, November 30, 2025, at 12:00 AM UTC
Next update by: Friday, December 5, 2025, at 10:30 PM UTC

CP1187825 - Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online

Status:serviceRestored
Start Time:Mon Nov 17 19:00:00 2025
End Time:Thu Nov 20 16:10:00 2025
Service:Microsoft Copilot (Microsoft 365)
Feature Group:Microsoft Copilot (Microsoft 365)
Classification:advisory
Last Updated:Mon Dec 8 14:09:24 2025
Root Cause:A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next Update:N/A

Details

Time:Fri Nov 21 17:38:30 2025
Description:Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may have seen Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting was disabled. If users attempt to access the Frontier agents, they will receive an error message.
Final status: We've confirmed that the fix has completed release and validated this issue has been remediated via internal testing and service telemetry.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
End time: Thursday, November 20, 2025, at 9:10 PM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next steps: - We're continuing our analysis of the impacting configuration change to better identify and prevent similar impact in the future.
This is the final update for the event.
Time:Fri Nov 21 13:24:07 2025
Description:Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled. If users attempt to access the Frontier agents, they will receive an error message.
Current status: The deployment is complete, and users should start seeing relief for this impact, though we're working to validate that the service has returned to a healthy state to ensure full remediation.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Saturday, November 22, 2025, at 12:00 AM UTC
Time:Thu Nov 20 21:39:07 2025
Description:Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents, they will receive an error message.
Current status: We’re continuing to monitor the deployment progression for the Microsoft Teams fix as it nears completion. We anticipate this deployment process will complete and the issue will be fully resolved by our next scheduled communications update.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Friday, November 21, 2025, at 8:00 PM UTC
Time:Thu Nov 20 15:02:23 2025
Description:Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents, they will receive an error message.
Current status: We’ve verified that the fix to address the impact in Exchange Online has completed successfully, and users will experience impact relief in Exchange Online. Additionally, we’ve initiated the secondary phase to address the impact in Microsoft Teams, and we’re monitoring the fix progression to ensure successful completion. Once available, we’ll provide a resolution timeline.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Friday, November 21, 2025, at 4:00 AM UTC
Time:Wed Nov 19 21:59:21 2025
Description:Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents, they will receive an error message.
Current status: We’ve halted the deployment of the fix in order to perform additional validations to ensure it successfully remediates impact. Additionally, we've identified that the fix will be released in two separate deployment phases. The first phase will address the impact in Exchange Online, which we anticipate will be fully deployed and the issue resolved by our next scheduled update. When that deployment is complete, we’ll initiate our deployment of the secondary phase to address the impact in Microsoft Teams, and we'll aim to provide a resolution timeline once available.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Thursday, November 20, 2025, at 9:30 PM UTC
Time:Wed Nov 19 16:07:33 2025
Description:Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents they will receive an error message.
Current status: We’ve validated the fix and initiated deployment to the affected environments. As the deployment progresses, some users may begin to see impact relief. Based on current estimates, we expect the deployment to complete by our next scheduled update.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Thursday, November 20, 2025, at 4:00 AM UTC
Time:Tue Nov 18 22:16:36 2025
Description:Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents they will receive an error message.
Current status: We're finalizing the validation of our fix in preparation for its deployment to the affected environment. We're anticipating this deployment should be underway, and may complete by the time of our next scheduled update.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Wednesday, November 19, 2025, at 10:30 PM UTC
Time:Tue Nov 18 17:22:19 2025
Description:Title: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online
User impact: Users may see Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
More info: Users may see Word, Excel, and PowerPoint agents within Microsoft Teams and any client of Exchange Online in specific situations, even when the Frontier setting is disabled.
If users attempt to access the Frontier agents they will receive an error message.
Current status: We’ve identified that a misconfiguration of a recent update resulted in some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online. We've developed and are internally validating a configuration fix to confirm it resolves the issue before deploying it to the affected environment. We anticipate that this fix will begin deployment to the affected environments on Wednesday, November 19, 2025.
Scope of impact: Any user in the affected environment that utilizes Microsoft Teams or Exchange Online may have been affected by this event.
Start time: Tuesday, November 18, 2025, at 12:00 AM UTC
Root cause: A misconfiguration of a recent update resulted in the some users seeing Frontier Copilot Agents for Word, Excel, and PowerPoint in Microsoft Teams and Exchange Online.
Next update by: Wednesday, November 19, 2025, at 5:00 AM UTC

MF1193288 - Users may be unable to create or modify connectors within Microsoft Power Automate

Status:serviceRestored
Start Time:Mon Dec 8 09:10:00 2025
End Time:Mon Dec 8 10:35:00 2025
Service:Microsoft Power Automate in Microsoft 365
Feature Group:Service and web access issues
Classification:advisory
Last Updated:Mon Dec 8 13:17:21 2025
Root Cause:An API that facilitates connector loading in Microsoft Power Automate wasn't responding to requests as expected, resulting in impact
Next Update:N/A

Details

Time:Mon Dec 8 13:17:21 2025
Description:Title: Users may be unable to create or modify connectors within Microsoft Power Automate
User impact: Users may have been unable to create or modify connectors within Microsoft Power Automate.
Final status: Our initial investigation determined that an API that facilitates connector loading in Microsoft Power Automate wasn't responding to requests as expected, resulting in impact. While we're continuing our analysis of service telemetry, our monitoring has identified that these errors are no longer occurring.
Scope of impact: Any user in the United States region may have been intermittently affected.
Start time: Monday, December 8, 2025, at 2:10 PM UTC
End time: Monday, December 8, 2025, at 3:35 PM UTC
Root cause: An API that facilitates connector loading in Microsoft Power Automate wasn't responding to requests as expected, resulting in impact
Next steps: - We're expanding our investigation to include API logs to better understand the underlying cause of impact and prevent similar issues in the future.
This is the final update for the event.
Time:Mon Dec 8 12:08:14 2025
Description:Title: Users may be unable to create or modify connectors within Microsoft Power Automate
User impact: Users may be unable to create or modify connectors within Microsoft Power Automate.
Current status: Our service monitoring has identified an increase in errors for users accessing connectors in Microsoft Power Automate. We're reviewing service telemetry to better understand the nature of impact and identify the cause of impact.
Scope of impact: Any user in the United States region may be intermittently affected.
Next update by: Monday, December 8, 2025, at 6:30 PM UTC
Time:Mon Dec 8 11:51:25 2025
Description:Title: Users may be unable to create or modify connectors within Microsoft Power Automate
User impact: Users may be unable to create or modify connectors within Microsoft Power Automate.
Current status: We're investigating a potential issue with connectors in Microsoft Power Automate and checking for impact to your organization. We'll provide an update within 30 minutes.

MM1193287 - Users may be unable to create or modify connectors within the Microsoft Power Apps Maker Portal

Status:serviceRestored
Start Time:Mon Dec 8 09:10:00 2025
End Time:Mon Dec 8 10:35:00 2025
Service:Power Apps in Microsoft 365
Feature Group:Service and web access issues
Classification:advisory
Last Updated:Mon Dec 8 13:17:20 2025
Root Cause:An API that facilitates connector loading in Microsoft Power Apps wasn't responding to requests as expected, resulting in impact
Next Update:N/A

Details

Time:Mon Dec 8 13:17:20 2025
Description:Title: Users may be unable to create or modify connectors within the Microsoft Power Apps Maker Portal
User impact: Users may have been unable to create or modify connectors within the Microsoft Power Apps Maker Portal.
Final status: Our initial investigation determined that an API that facilitates connector loading in Microsoft Power Apps wasn't responding to requests as expected, resulting in impact. While we're continuing our analysis of service telemetry, our monitoring has identified that these errors are no longer occurring.
Scope of impact: Any user in the United States region may have been intermittently affected.
Start time: Monday, December 8, 2025, at 2:10 PM UTC
End time: Monday, December 8, 2025, at 3:35 PM UTC
Root cause: An API that facilitates connector loading in Microsoft Power Apps wasn't responding to requests as expected, resulting in impact
Next steps: - We're expanding our investigation to include API logs to better understand the underlying cause of impact and prevent similar issues in the future.
This is the final update for the event.
Time:Mon Dec 8 12:08:06 2025
Description:Title: Users may be unable to create or modify connectors within the Microsoft Power Apps Maker Portal
User impact: Users may be unable to create or modify connectors within the Microsoft Power Apps Maker Portal.
Current status: Our service monitoring has identified an increase in errors for users accessing connectors in the Microsoft Power Apps Maker Portal. We're reviewing service telemetry to better understand the nature of impact and identify the cause of impact.
Scope of impact: Any user in the United States region may be intermittently affected.
Next update by: Monday, December 8, 2025, at 6:30 PM UTC
Time:Mon Dec 8 11:51:19 2025
Description:Title: Users may be unable to create or modify connectors within the Microsoft Power Apps Maker Portal
User impact: Users may be unable to create or modify connectors within the Microsoft Power Apps Maker Portal.
Current status: We're investigating a potential issue with connectors in Microsoft Power Apps Maker and checking for impact to your organization. We'll provide an update within 30 minutes.