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 Sat Nov 2 00:45:07 2024.
TM923745 - Some users may be intermittently unable to send messages to bots in Microsoft Teams
Status: | investigating |
Start Time: | Fri Nov 1 23:30:00 2024 |
End Time: | N/A |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Sat Nov 2 00:09:40 2024 |
Root Cause: | A portion of infrastructure that facilitates messaging requests to bot in Microsoft Teams that's performing below the expected service threshold. |
Next Update: | Saturday, November 2, 2024, at 5:30 AM UTC |
|
Details
Time: | Sat Nov 2 00:09:40 2024 |
Description: | Title: Some users may be intermittently unable to send messages to bots in Microsoft Teams
User impact: Users may be intermittently unable to send messages to bots in Microsoft Teams.
Current status: We identified an issue with a portion of infrastructure that facilitates messaging requests to bots in Microsoft Teams that's performing below the expected service threshold. Our automated recovery tools have taken action to reroute connections to alternate infrastructure and we're monitoring the telemetry to validate that the impact is remediated.
Scope of impact: This issue may intermittently impact some users sending messages to bots in Microsoft Teams.
Start time: Saturday, November 2, 2024, at 2:30 AM UTC
Root cause: A portion of infrastructure that facilitates messaging requests to bot in Microsoft Teams that's performing below the expected service threshold.
Next update by: Saturday, November 2, 2024, at 5:30 AM UTC
|
|
Time: | Fri Nov 1 23:42:22 2024 |
Description: | Title: Some users may be intermittently unable to send messages to bots in Microsoft Teams
User impact: Users may be intermittently unable to send messages to bots in Microsoft Teams.
Current status: We're investigating a potential issue with Microsoft Teams and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
SP861751 - Some users may be unable to edit some SharePoint Online classic site pages
Status: | serviceRestored |
Start Time: | Tue May 28 18:59:00 2024 |
End Time: | Fri Nov 1 16:49:00 2024 |
Service: | SharePoint Online |
Feature Group: | SharePoint Features |
Classification: | advisory |
Last Updated: | Fri Nov 1 20:10:37 2024 |
Root Cause: | A recent feature update, which enforced the disabling of custom scripts, introduced a regression. This led to custom scripts being unexpectedly disabled which caused users to lose the ability to edit some classic site pages. |
Next Update: | N/A |
|
Details
Time: | Fri Nov 1 20:10:37 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may have been unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may have seen the edit button greyed out or not visible at all. As a workaround, admins were able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Final status: The fix deployment was completed and we've confirmed with telemetry and previously affected users that impact was remediated.
Scope of impact: Impact was specific to some users, who were served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Start time: Tuesday, May 28, 2024, at 10:59 PM UTC
End time: Friday, November 1, 2024, at 8:49 PM UTC
Root cause: A recent feature update, which enforced the disabling of custom scripts, introduced a regression. This led to custom scripts being unexpectedly disabled which caused users to lose the ability to edit some classic site pages.
Next steps:
- To help prevent similar impact in the future, we're further reviewing how we can identify these types of regressions prior to feature deployment.
This is the final update for the event.
|
|
Time: | Wed Oct 30 13:52:53 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: The deployment of the fix is taking longer than anticipated to complete. We expect the majority of impacted users are already experiencing remediation, while the impact for the remaining affected users will be resolved by our next scheduled update.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Start time: Tuesday, May 28, 2024, at 10:59 PM UTC
Root cause: A recent feature update, which enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Saturday, November 2, 2024, at 1:00 AM UTC
|
|
Time: | Fri Oct 25 13:46:08 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: We're continuing to monitor the deployment as it progresses and expect mitigation for all users by the next scheduled update.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Start time: Tuesday, May 28, 2024, at 10:59 PM UTC
Estimated time to resolve: We expect the fix to complete deployment around Wednesday, October 30, 2024.
Root cause: A recent feature update, which enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Wednesday, October 30, 2024, at 7:30 PM UTC
|
|
Time: | Fri Oct 18 14:15:42 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: We've completed the validation of the fix and it's scheduled for release. We expect the fix to take approximately two weeks to complete deployment to all affected users.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Start time: Tuesday, May 28, 2024, at 10:59 PM UTC
Estimated time to resolve: We expect the fix to complete deployment around Thursday, October 31, 2024.
Root cause: A recent feature update, which enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Friday, October 25, 2024, at 7:30 PM UTC
|
|
Time: | Wed Oct 16 15:09:46 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: Our supplemental fix deployment is taking longer than previously estimated but progressing with validations with select affected customers, so we can ensure it is addressing the introduced code regression and remediating the impact as expected. We're expecting that an estimated timeline for the remaining fix deployment will be available by our next scheduled update.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Start time: Tuesday, May 28, 2024, at 10:59 PM UTC
Root cause: A recent feature update, which enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Friday, October 18, 2024, at 7:30 PM UTC
|
|
Time: | Wed Oct 9 13:58:34 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: Our supplemental fix is taking longer than initially estimated, and we now anticipate that it should complete deployment and resolve the issue on Wednesday, October 16, 2024, at 7:30 PM UTC.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Start time: Tuesday, May 28, 2024, at 10:59 PM UTC
Estimated time to resolve: We expect that our supplemental fix should complete deployment and resolve the issue on Wednesday, October 16, 2024, at 7:30 PM UTC.
Root cause: A recent feature update, which enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Wednesday, October 16, 2024, at 7:30 PM UTC
|
|
Time: | Wed Oct 2 14:25:26 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: The deployment of the supplemental fix has been initiated and we're monitoring as it progresses. We currently expect the fix to complete deployment by the next scheduled update, at which point we'll continue our work with affected users to confirm it has had the desired effect.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Start time: Tuesday, May 28, 2024, at 10:59 PM UTC
Root cause: A recent feature update, which enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Wednesday, October 9, 2024, at 7:30 PM UTC
|
|
Time: | Mon Sep 23 15:16:58 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: We've determined an additional fix is needed to resolve the issue identified during our previous fix testing where instead of rendering the expected site page, SharePoint Online is rendering the document library. We anticipate this new fix will begin deployment by our next scheduled update and will confirm a timeline for that deployment completion with that update.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Start time: Tuesday, May 28, 2024, at 10:59 PM UTC
Root cause: A recent feature update, that enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Wednesday, October 2, 2024, at 7:30 PM UTC
|
|
Time: | Fri Sep 20 14:31:11 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: As our fix was deploying, we performed some initial tests on multiple site pages. For some, we identified the pages displayed as expected and could be edited. For others, instead of rendering the page, SharePoint Online is rendering the document library. We've paused the deployment of our fix to identify why we're seeing scenarios where this occurs, determine why it's occurring, and confirm if the fix can continue to be rolled out or if adjustments are necessary.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Root cause: A recent feature update, that enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Monday, September 23, 2024, at 7:30 PM UTC
|
|
Time: | Thu Sep 12 14:13:00 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: The multi-phase deployment of our previously mentioned fix is entering its final stages. We anticipate that the fix will be fully deployed by our next scheduled update, at which time we'll monitor our service health telemetry to confirm that impact is remediated.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Estimated time to resolve: We anticipate that the fix will be fully deployed, remediating impact by Friday, September 20, 2024, at 7:30 PM UTC.
Root cause: A recent feature update, that enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Friday, September 20, 2024, at 7:30 PM UTC
|
|
Time: | Thu Aug 29 13:53:49 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: We've completed our validation of the previously mentioned fix, and we've initiated the first phase of our multi-stage operation to deploy this fix to the impacted service environments. We're aiming to provide a timeline for full deployment and remediation in our next scheduled update.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Root cause: A recent feature update, that enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Thursday, September 12, 2024, at 8:30 PM UTC
|
|
Time: | Fri Aug 23 14:23:28 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: We've completed the fix development which we’re deploying to our
internal testing environment for further validation prior to releasing to affected users. The validation process is expected to take an extended period of time to ensure that the fix will address the problem without causing additional impact. We’ll provide a better estimate on the process timeline as one becomes available and also look for methods for expediting the fix.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Root cause: A recent feature update, that enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Thursday, August 29, 2024, at 7:30 PM UTC
|
|
Time: | Wed Aug 21 13:23:14 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: We're continuing development of the fix which we expect to complete by the next scheduled update. Once completed, the fix will undergo validation and anticipate the fix releasing by Tuesday, August 27, 2024.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Root cause: A recent feature update, that enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Friday, August 23, 2024, at 7:30 PM UTC
|
|
Time: | Wed Aug 14 09:49:18 2024 |
Description: | Title: Some users may be unable to edit some SharePoint Online classic site pages
User impact: Users may be unable to edit some SharePoint Online classic site pages.
More info: Specifically, users may see the edit button greyed out or not visible at all. As a workaround, admins may be able to manually run the following script "Set-SPOSite -DenyAddAndCustomizePages 0", to re-enable custom script through PowerShell to mitigate impact.
Current status: We've identified that a recent feature update, that enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages. We're developing a fix to correct the regression and we're anticipating that the fix will be fully deployed by the end of August 2024.
Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to edit some SharePoint Online classic site pages.
Root cause: A recent feature update, that enforces the disabling of customs scripts, has introduced a regression leading to custom scripts being unexpectedly disabled and causing users to lose the ability to edit some classic site pages.
Next update by: Wednesday, August 21, 2024, at 6:30 PM UTC
|
|
MV923384 - Some users may be intermittently unable to access Microsoft Viva Engage communities
Status: | serviceRestored |
Start Time: | Fri Nov 1 17:29:00 2024 |
End Time: | Fri Nov 1 18:45:00 2024 |
Service: | Microsoft Viva |
Feature Group: | Viva Engage |
Classification: | advisory |
Last Updated: | Fri Nov 1 19:17:03 2024 |
Root Cause: | A recent update was preventing some users from accessing Viva Engage communities. |
Next Update: | N/A |
|
Details
Time: | Fri Nov 1 19:17:03 2024 |
Description: | Title: Some users may be intermittently unable to access Microsoft Viva Engage communities
User impact: Users may have been intermittently unable to access Viva Engage communities.
Final status: We've successfully rolled back the offending update in all affected infrastructure and verified the issue is fully mitigated by monitoring service health telemetry.
Scope of impact: This issue potentially affected some users intermittently when they attempted to access their Viva Engage communities.
Start time: Friday, November 1, 2024, at 8:30 PM UTC
End time: Friday, November 1, 2024, at 10:45 PM UTC
Root cause: A recent update was preventing some users from accessing Viva Engage communities.
Next steps:
- We're reassessing our service monitoring of this impact scenario to implement improvements for detecting similar events and reduce our time to identify and address this type of impact.
This is the final update for the event.
|
|
Time: | Fri Nov 1 18:40:24 2024 |
Description: | Title: Some users may be intermittently unable to access Microsoft Viva Engage communities
User impact: Users may be intermittently unable to access Viva Engage communities.
Current status: Our monitoring telemetry alerted us to an issue where some users may be intermittently unable to access their Viva Engage communities. We've isolated a recent service update that's causing access issues and we're reverting the offending update to restore service.
Scope of impact: This issue potentially affects some users intermittently when they attempt to access their Viva Engage communities.
Root cause: A recent update is preventing some users from accessing Viva Engage communities.
Next update by: Saturday, November 2, 2024, at 12:30 AM UTC
|
|
EX921449 - Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
Status: | serviceDegradation |
Start Time: | Wed Oct 30 06:24:09 2024 |
End Time: | N/A |
Service: | Exchange Online |
Feature Group: | E-Mail timely delivery |
Classification: | incident |
Last Updated: | Fri Nov 1 17:53:59 2024 |
Root Cause: | A recent rule set change in our automated anti-spam procedure is incorrectly blocking email messages containing certain types of URLs. This change is causing inbound email messages to be marked as phishing and quarantined because some signatures are being flagged as malicious. |
Next Update: | Saturday, November 2, 2024, at 9:00 PM UTC |
|
Details
Time: | Fri Nov 1 17:48:47 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
More info: The full list of affected URLs isn't available at this time.
Current status: While we've confirmed that the majority of the impacted email messages have successfully been released from quarantine, a small portion of affected email messages require additional mitigating actions. We're in the process of identifying and releasing the remaining affected email messages, and expect that this may complete by our next scheduled communications update.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Start time: Tuesday, October 29, 2024, at 5:39 PM UTC
Root cause: A recent rule set change in our automated anti-spam procedure is incorrectly blocking email messages containing certain types of URLs. This change is causing inbound email messages to be marked as phishing and quarantined because some signatures are being flagged as malicious.
Next update by: Saturday, November 2, 2024, at 9:00 PM UTC
|
|
Time: | Thu Oct 31 23:31:52 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
More info: The full list of affected URLs isn't available at this time.
Current status: We've released the bulk of the impacted email messages from quarantine and are monitoring to confirm any remaining messages are released as expected. We anticipate this process may be complete by the time of our next scheduled update.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Start time: Tuesday, October 29, 2024, at 5:39 PM UTC
Root cause: A recent rule set change in our automated anti-spam procedure is incorrectly blocking email messages containing certain types of URLs. This change is causing inbound email messages to be marked as phishing and quarantined because some signatures are being flagged as malicious.
Next update by: Friday, November 1, 2024, at 10:00 PM UTC
|
|
Time: | Thu Oct 31 20:53:43 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
More info: The full list of affected URLs isn't available at this time.
Current status: We're monitoring our script as it works to release the remaining impacted email messages from quarantine. We anticipate this process may be complete by the time of our next scheduled update.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Start time: Tuesday, October 29, 2024, at 5:39 PM UTC
Root cause: A recent rule set change in our automated anti-spam procedure is incorrectly blocking email messages containing certain types of URLs. This change is causing inbound email messages to be marked as phishing and quarantined because some signatures are being flagged as malicious.
Next update by: Friday, November 1, 2024, at 5:00 AM UTC
|
|
Time: | Thu Oct 31 12:55:19 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
More info: The full list of affected URLs isn't available at this time.
Current status: We've addressed some issues that were delaying the script and have confirmed that 50 percent of all affected email messages have been released from quarantine. We're continuing to monitor the script as it progresses towards completion.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Start time: Tuesday, October 29, 2024, at 5:39 PM UTC
Root cause: A recent rule set change in our automated anti-spam procedure is incorrectly blocking email messages containing certain types of URLs. This change is causing inbound email messages to be marked as phishing and quarantined because some signatures are being flagged as malicious.
Next update by: Friday, November 1, 2024, at 2:00 AM UTC
|
|
Time: | Wed Oct 30 23:41:39 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
More info: The full list of affected URLs isn't available at this time.
Current status: Our script to remove the previously affected messages from quarantine is ongoing though progressing more slowly than originally anticipated. We now expect that the majority of the affected messages will be removed from quarantine by our next scheduled update.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Start time: Tuesday, October 29, 2024, at 5:39 PM UTC
Root cause: A recent rule set change in our automated anti-spam procedure is incorrectly blocking email messages containing certain types of URLs. This change is causing inbound email messages to be marked as phishing and quarantined because some signatures are being flagged as malicious.
Next update by: Thursday, October 31, 2024, at 6:30 PM UTC
|
|
Time: | Wed Oct 30 23:35:09 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
More info: The full list of affected URLs isn't available at this time.
Current status: We've implemented our script to remove the previously affected messages from quarantine and anticipate the issue may be remediated by our next update.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Start time: Tuesday, October 29, 2024, at 5:39 PM UTC
Root cause: A recent rule set change in our automated anti-spam procedure is incorrectly blocking email messages containing certain types of URLs. This change is causing inbound email messages to be marked as phishing and quarantined because some signatures are being flagged as malicious.
Next update by: Thursday, October 31, 2024, at 5:00 AM UTC
|
|
Time: | Wed Oct 30 19:57:28 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
More info: The full list of affected URLs isn't available at this time.
Current status: We've implemented our script to remove the previously affected messages from quarantine and anticipate the issue may be remediated by our next update.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Start time: Tuesday, October 29, 2024, at 5:39 PM UTC
Root cause: A recent rule set change in our automated anti-spam procedure is incorrectly blocking email messages containing certain types of URLs. This change is causing inbound email messages to be marked as phishing and quarantined because some signatures are being flagged as malicious.
Next update by: Thursday, October 31, 2024, at 5:00 AM UTC
|
|
Time: | Wed Oct 30 16:49:42 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
More info: The full list of affected URLs isn't available at this time.
Current status: The process of replaying the previously affected messages to remove them from quarantine is taking longer than previously anticipated, but we've identified a way of utilizing a script to expedite this process. We'll provide a timeline for complete remediation should one become available.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Start time: Tuesday, October 29, 2024, at 5:39 PM UTC
Root cause: Our automated anti-spam procedure is incorrectly blocking email messages that contain specific URLs, which is causing inbound email messages to be marked as phishing and quarantined due to signatures which are flagged as malicious.
Next update by: Thursday, October 31, 2024, at 12:00 AM UTC
|
|
Time: | Wed Oct 30 14:11:09 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
More info: The full list of affected URLs isn't available at this time.
Current status: We've confirmed that removing the offending signatures has prevented additional email with the specific URLs from being quarantined. We're still in the process of replaying the previously affected messages to remove them from quarantine and completely remediate impact.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Root cause: Our automated anti-spam procedure is incorrectly blocking email messages that contain specific URLs, which is causing inbound email messages to be marked as phishing and quarantined due to signatures which are flagged as malicious.
Next update by: Wednesday, October 30, 2024, at 9:00 PM UTC
|
|
Time: | Wed Oct 30 12:31:32 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
Current status: We've removed the signatures that were causing our anti-spam process to quarantine the affected email messages, preventing additional inbound email from being incorrectly marked as phish. Subsequently, we're replaying the affected messages to remove them from quarantine and completely remediate impact.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Root cause: Our automated anti-spam procedure is incorrectly blocking email messages that contain specific URLs, which is causing inbound email messages to be marked as phishing and quarantined due to signatures which are flagged as malicious.
Next update by: Wednesday, October 30, 2024, at 6:30 PM UTC
|
|
Time: | Wed Oct 30 10:31:54 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
Current status: We've identified that our automated anti-spam procedures is incorrectly blocking email messages based on certain URLs, which is causing inbound email messages to be marked as phishing and quarantined due to a signature which is flagged as malicious. We're further reviewing the machine learning logic behind the quarantines to further assess our remediation options.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Root cause: Our automated anti-spam procedures is incorrectly blocking email messages that contain a specific URL, which is causing inbound email messages to be marked as phishing and quarantined due to a signature which is flagged as malicious.
Next update by: Wednesday, October 30, 2024, at 4:30 PM UTC
|
|
Time: | Wed Oct 30 08:56:42 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
Current status: We've identified that our automated anti-spam procedures is incorrectly blocking email messages that contain a specific URL, which is causing inbound email messages to be marked as phishing and quarantined due to a signature which is flagged as malicious. We're proceeding with implementing an override to prevent further false positive detections.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Root cause: Our automated anti-spam procedures is incorrectly blocking email messages that contain a specific URL, which is causing inbound email messages to be marked as phishing and quarantined due to a signature which is flagged as malicious.
Next update by: Wednesday, October 30, 2024, at 3:00 PM UTC
|
|
Time: | Wed Oct 30 06:42:46 2024 |
Description: | Title: Some users' inbound email messages containing some URLs may be unexpectedly marked as phishing
User impact: Users' inbound email messages containing some URLs may be unexpectedly marked as phishing.
Current status: We're reviewing support case provided data to isolate the root cause, and determine the next steps needed to resolve this issue.
Scope of impact: Impact is specific to some users who are expecting to receive inbound email messages that contain some URLs and are served through the affected infrastructure.
Next update by: Wednesday, October 30, 2024, at 1:00 PM UTC
|
|
Time: | Wed Oct 30 06:28:40 2024 |
Description: | Title: We're looking into a potential problem impacting the Exchange Online service
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with the Exchange Online service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
TM920952 - Some users without a Copilot license may see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
Status: | serviceRestored |
Start Time: | Thu Aug 29 14:23:00 2024 |
End Time: | Thu Oct 31 20:00:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Fri Nov 1 17:07:02 2024 |
Root Cause: | When users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change populated across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing due to the code for settings and preferences updates not including a license check. |
Next Update: | N/A |
|
Details
Time: | Fri Nov 1 15:51:46 2024 |
Description: | Title: Some users without a Copilot license may see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
User impact: Users without a Copilot license may have seen the Copilot app button within Microsoft Teams.
More info: This was a rare and intermittent issue. Affected users without Copilot licenses were not able to access Copilot in Teams, despite the UI button being present due to the issue. If an affected user attempted to click on the Copilot app button within Microsoft Teams, it failed and they were subsequently unable to navigate to other areas of Microsoft Teams, such as chats, calendar, and more. Users who entered this scenario could restart their Microsoft Teams session to mitigate the issue.
Final status: We've confirmed the deployment of the fix has reached 100 percent of affected environments and all customers will see remediation with Teams version 24100324914.
Scope of impact: This issue may have impacted users without Copilot licenses that updated their settings or preferences in Microsoft Teams mobile or web apps and then subsequently clicked the Copilot app button.
Start time: August 29, 2024, at 6:23 PM UTC
End time: November 1, 2024, at 12:00 AM UTC
Root cause: When users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change populated across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing due to the code for settings and preferences updates not including a license check.
Next steps:
- We're further reviewing how the impact scenario was introduced to identify opportunities to prevent similar issues in the future.
-
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|
Time: | Wed Oct 30 15:35:55 2024 |
Description: | Title: Some users without a Copilot license may see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
User impact: Users without a Copilot license may see the Copilot app button within Microsoft Teams.
More info: This is a rare and intermittent issue. Affected users without Copilot licenses are not able to access Copilot in Teams, despite the UI button being present due to the issue. If an affected user attempts to click on the Copilot app button within Microsoft Teams, it fails and they are subsequently unable to navigate to other areas of Microsoft Teams, such as chats, calendar, and more. Users who enter this scenario can restart their Microsoft Teams session to mitigate the issue.
Current status: We're continuing to monitor the deployment of the fix which has reached 30 percent of affected environments. Some customers may already begin seeing remediation with Teams version 24100324914. Customer reports and internal validation have confirmed the issue is resolved by the fix and we anticipate completing the deployment by Friday, November 1, 2024.
Scope of impact: This issue may impact users without Copilot licenses that update their setting or preferences in Microsoft Teams mobile or web apps and then subsequently click the Copilot app button.
Preliminary root cause: When users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change is populating across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing due to the code for settings and preferences updates not including a license check.
Next update by: Friday, November 1, 2024, at 10:00 PM UTC
|
|
Time: | Tue Oct 29 13:42:27 2024 |
Description: | Title: Some users without proper licenses may see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
User impact: Users without proper licenses may see the Copilot app button within Microsoft Teams.
More info: This is a rare and intermittent issue. Affected users without Copilot licenses are not able to access Copilot in Teams, despite the UI button being present due to the issue. If an affected user attempts to click on the Copilot app button within Microsoft Teams, it fails and they are subsequently unable to navigate to other areas of Microsoft Teams, such as chats, calendar, and more. Users who enter this scenario can restart their Microsoft Teams session to mitigate the issue.
Current status: We’ve investigated the problem and determined that when users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change populates across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing because the code for settings and preferences updates doesn’t include a license check. We’ve developed and started deploying a fix that adds a license check to resolve the issue. We're monitoring the deployment of the fix, and it’s proceeding as expected. Those within the Microsoft 365 Technology Adoption Program (TAP) and Preview channels may already begin seeing remediation, with Microsoft Teams version 24100324914. We’ll provide a more precise completion date for the fix once available.
Scope of impact: This issue may impact users without Copilot licenses that update their setting or preferences in in Microsoft Teams mobile or web apps and then subsequently click the Copilot app button.
Preliminary root cause: When users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change populates across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing because the code for settings and preferences updates doesn’t include a license check.
Next update by: Wednesday, October 30, 2024, at 10:00 PM UTC
|
|
CP918548 - Some users without a Copilot license may see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
Status: | serviceRestored |
Start Time: | Thu Aug 29 14:23:00 2024 |
End Time: | Thu Oct 31 20:00:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | advisory |
Last Updated: | Fri Nov 1 17:06:14 2024 |
Root Cause: | When users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change populated across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing due to the code for settings and preferences updates not including a license check. |
Next Update: | N/A |
|
Details
Time: | Fri Nov 1 15:50:12 2024 |
Description: | Title: Some users without a Copilot license may see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
User impact: Users without a Copilot license may have seen the Copilot app button within Microsoft Teams.
More info: This was a rare and intermittent issue. Affected users without Copilot licenses were not able to access Copilot in Teams, despite the UI button being present due to the issue. If an affected user attempted to click on the Copilot app button within Microsoft Teams, it failed and they were subsequently unable to navigate to other areas of Microsoft Teams, such as chats, calendar, and more. Users who entered this scenario could restart their Microsoft Teams session to mitigate the issue.
Final status: We've confirmed the deployment of the fix has reached 100 percent of affected environments and all customers will see remediation with Teams version 24100324914.
Scope of impact: This issue may have impacted users without Copilot licenses that updated their settings or preferences in Microsoft Teams mobile or web apps and then subsequently clicked the Copilot app button.
Start time: August 29, 2024, at 6:23 PM UTC
End time: November 1, 2024, at 12:00 AM UTC
Root cause: When users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change populated across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing due to the code for settings and preferences updates not including a license check.
Next steps:
- We're further reviewing how the impact scenario was introduced to identify opportunities to prevent similar issues in the future.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|
Time: | Wed Oct 30 15:34:47 2024 |
Description: | Title: Some users without a Copilot license may see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
User impact: Users without a Copilot license may see the Copilot app button within Microsoft Teams.
More info: This is a rare and intermittent issue. Affected users without Copilot licenses are not able to access Copilot in Teams, despite the UI button being present due to the issue. If an affected user attempts to click on the Copilot app button within Microsoft Teams, it fails and they are subsequently unable to navigate to other areas of Microsoft Teams, such as chats, calendar, and more. Users who enter this scenario can restart their Microsoft Teams session to mitigate the issue.
Current status: We're continuing to monitor the deployment of the fix which has reached 30 percent of affected environments. Some customers may already begin seeing remediation with Teams version 24100324914. Customer reports and internal validation have confirmed the issue is resolved by the fix and we anticipate completing the deployment by Friday, November 1, 2024.
Scope of impact: This issue may impact users without Copilot licenses that update their setting or preferences in Microsoft Teams mobile or web apps and then subsequently click the Copilot app button.
Preliminary root cause: When users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change is populating across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing due to the code for settings and preferences updates not including a license check.
Next update by: Friday, November 1, 2024, at 10:00 PM UTC
|
|
Time: | Mon Oct 28 19:14:26 2024 |
Description: | Title: Users without proper licenses are able to see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
User impact: Users without proper licenses are seeing the Copilot app button within Microsoft Teams.
More info: When users attempt to click on the Copilot app button within Microsoft Teams it fails and they are subsequently unable to navigate to other areas of Microsoft Teams, such as chats, calendar, and more. Users who enter this scenario can restart their Microsoft Teams session to mitigate.
Current status: We're continuing to monitor the deployment of the fix, and it’s proceeding as expected. Customers within the Microsoft 365 Technology Adoption Program (TAP) and Preview channels may already begin seeing remediation, with the Teams version 24100324914. Additionally, we’re reviewing options to expedite the deployment of the fix for all affected customers and we’ll provide a more precise completion date for the fix once available.
Scope of impact: This issue only affects users without proper Copilot licenses that are using Microsoft Teams.
Preliminary root cause: When users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change is populating across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing due to the code for settings and preferences updates not including a license check.
Next update by: Wednesday, October 30, 2024, at 10:00 PM UTC
|
|
Time: | Fri Oct 25 19:40:10 2024 |
Description: | Title: Users without proper licenses are able to see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
User impact: Users without proper licenses are seeing the Copilot app button within Microsoft Teams.
More info: When users attempt to click on the Copilot app button within Microsoft Teams it fails and they are subsequently unable to navigate to other areas of Microsoft Teams, such as chats, calendar, and more. Users who enter this scenario can restart their Microsoft Teams session to mitigate.
Current status: We've confirmed that the fix is deploying as expected, and based on current progress, we anticipate that it will complete during the week of November 4, 2024. We'll continue to monitor the progress and will aim to provide a more precise completion date once available.
Scope of impact: This issue only affects users without proper Copilot licenses that are using Microsoft Teams.
Preliminary root cause: When users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change is populating across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing due to the code for settings and preferences updates not including a license check.
Next update by: Monday, October 28, 2024, at 10:00 PM UTC
|
|
Time: | Fri Oct 25 18:28:11 2024 |
Description: | Title: Users without proper licenses are able to see the Microsoft Copilot (Microsoft 365) app button within Microsoft Teams
User impact: Users without proper licenses are seeing the Copilot app button within Microsoft Teams.
More info: Additionally, when users click on the Copilot app button within Microsoft Teams, they're unable to navigate to other areas of Microsoft Teams, such as chats, calendar, and more. Users who enter this scenario can restart their Microsoft Teams session to mitigate.
Additionally, users may be able to bypass impact before clicking on the chat icon by first accessing the calendar or other tabs prior to accessing the chat tab, although this only removes the Copilot app button temporarily.
Current status: We've received reports of an issue where users without proper licenses are seeing the Copilot app button within Microsoft Teams. We suspect that when users update their settings or preferences in Microsoft Teams mobile or web apps, the settings change is populating across to the Microsoft Teams desktop client as well, resulting in the Copilot app button appearing due to the code for settings and preferences updates not including a license check. We have a fix to add the license check to this code to resolve the issue. This fix is being deployed now and we expect to have a timeline for completion with our next scheduled update.
Scope of impact: This issue only affects users without proper Copilot licenses that are using Microsoft Teams.
Next update by: Monday, November 4, 2024, at 10:00 PM UTC
|
|
EX921969 - Users may be able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error
Status: | serviceDegradation |
Start Time: | Wed Oct 30 20:49:35 2024 |
End Time: | N/A |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | advisory |
Last Updated: | Fri Nov 1 15:29:38 2024 |
Root Cause: | A recent change intended to optimize the XML flow for certain EWS methods is resulting in impact. |
Next Update: | Wednesday, November 6, 2024, at 11:00 PM UTC |
|
Details
Time: | Thu Oct 31 17:34:18 2024 |
Description: | Title: Users may be able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error
User impact: Users may be unable to load email messages using the 'FindItems' method in Exchange Online and may encounter an error.
More info: Affected users are unable to use the Exchange Web Services (EWS) 'FindItems' method to load email messages, particularly calendar invite email notifications. When running Kusto queries, the function 'Get_AppointmentState()' returns the error "An internal server error occurred. The operation failed." While users may still be able to retrieve the subject of the affected email messages, errors are encountered upon attempting to load the message body.
For users utilizing a third-party email application that leverages EWS to retrieve email content, users may be prevented from accessing email messages and calendar invites.
Current status: We've completed validating the fix and have initiated the deployment to the impacted environments. We anticipate the deployment will complete and the impact will be remediated by our next scheduled update.
Scope of impact: Any user leveraging the EWS 'FindItems' method to load email messages in Exchange Online may be impacted.
Start time: Monday, October 28, 2024, at 12:00 AM UTC
Root cause: A recent change intended to optimize the XML flow for certain EWS methods is resulting in impact.
Next update by: Wednesday, November 6, 2024, at 11:00 PM UTC
|
|
Time: | Wed Oct 30 23:37:15 2024 |
Description: | Title: Users aren't able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error
User impact: Users aren't able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error.
More info: Affected users are unable to use the Exchange Web Services (EWS) 'FindItems' method to load email messages, particularly calendar invite emails. When running Kusto queries, the function 'Get_AppointmentState()' returns the error "An internal server error occurred. The operation failed." While users may still be able to retrieve the subject of the affected email messages, errors are encountered upon attempting to load the message body.
For users utilizing a third-party email application that leverages EWS to retrieve email content, users may be prevented from accessing email messages and calendar invites.
Current status: We're continuing to prepare our deployment to revert the offending changes. We're anticipating the initial validation process for our fix may be complete by the time of our next scheduled update, at which point we'll look to confirm a timeline for full remediation.
Scope of impact: Your organization is affected by this event, and users leveraging the EWS 'FindItems' method are impacted.
Root cause: A recent change intended to optimize the XML flow for certain EWS methods is resulting in impact.
Next update by: Thursday, October 31, 2024, at 10:00 PM UTC
|
|
Time: | Wed Oct 30 22:21:31 2024 |
Description: | Title: Users aren't able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error
User impact: Users aren't able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error.
More info: Affected users are unable to use the Exchange Web Services (EWS) 'FindItems' method to load email messages, particularly calendar invite emails. When running Kusto queries, the function 'Get_AppointmentState()' returns the error "An internal server error occurred. The operation failed." While users may still be able to retrieve the subject of the affected email messages, errors are encountered upon attempting to load the message body.
For users utilizing a third-party email application that leverages EWS to retrieve email content, users may be prevented from accessing email messages and calendar invites.
Current status: We identified a recent change intended to optimize the XML flow for certain EWS methods is resulting in impact. We're working on reverting the change. We anticipate we may be able to confirm a timeline for rolling back the change by our next update.
Scope of impact: Your organization is affected by this event, and users leveraging the EWS 'FindItems' method are impacted.
Root cause: A recent change intended to optimize the XML flow for certain EWS methods is resulting in impact.
Next update by: Thursday, October 31, 2024, at 4:30 AM UTC
|
|
Time: | Wed Oct 30 21:14:29 2024 |
Description: | Title: Users aren't able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error
User impact: Users aren't able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error.
More info: Affected users are unable to use the Exchange Web Services (EWS) 'FindItems' method to load email messages, particularly calendar invite emails. When running Kusto queries, the function 'Get_AppointmentState()' returns the error "An internal server error occurred. The operation failed." While users may still be able to retrieve the subject of the affected email messages, errors are encountered upon attempting to load the message body.
For users utilizing a third-party email application that leverages EWS to retrieve email content, users may be prevented from accessing email messages and calendar invites.
Current status: We're reviewing network trace logs and contextual information provided by affected 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 leveraging the EWS 'FindItems' method are impacted.
Next update by: Thursday, October 31, 2024, at 2:30 AM UTC
|
|
Time: | Wed Oct 30 21:01:32 2024 |
Description: | Title: Users aren't able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error
User impact: Users aren't able to load email messages using the 'FindItems' method in Exchange Online and may encounter an error.
More info: Affected users are unable to use the Exchange Web Services (EWS) FindItems method to load email messages, particularly calendar invite emails. When running Kusto queries, the function 'Get_AppointmentState()' returns the error "An internal server error occurred. The operation failed." While users may still be able to retrieve the subject of the affected email messages, errors are encountered upon attempting to load the message body.
For users utilizing a third-party email application that leverages EWS to retrieve email content, users may be prevented from accessing email messages and calendar invites.
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.
|
|
SP921623 - Some users may be unable to perform searches within SharePoint Online
Status: | postIncidentReviewPublished |
Start Time: | Wed Oct 30 07:30:00 2024 |
End Time: | Wed Oct 30 16:30:00 2024 |
Service: | SharePoint Online |
Feature Group: | SharePoint Features |
Classification: | incident |
Last Updated: | Fri Nov 1 13:33:42 2024 |
Root Cause: | A recent update to a subset of authentication configurations contained an error, resulting in impact. This update was intended to introduce general service improvements and was rolled out to approximately 10 percent of tenants. |
Next Update: | N/A |
|
Details
Time: | Fri Nov 1 13:33:42 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Wed Oct 30 16:42:26 2024 |
Description: | Title: Some users may be unable to perform searches within SharePoint Online
User impact: Users may have been unable to perform searches within SharePoint Online.
Final status: We've successfully reverted the offending update and verified the issue has been remediated by monitoring service health telemetry and confirming with previously affected customers.
Scope of impact: Any user performing searches within SharePoint Online may have been impacted. This issue affected approximately 10 percent of tenants.
Start time: Wednesday, October 30, 2024, at 11:30 AM UTC
End time: Wednesday, October 30, 2024, at 8:30 PM UTC
Root cause: A recent update to a subset of authentication configurations contained an error, resulting in impact. This update was intended to introduce general service improvements and was rolled out to approximately 10 percent of tenants.
Next steps:
- We're reviewing our code update testing procedures to determine what led to this impact and prevent similar issues from occurring in the future.
- We're reassessing our service monitoring of this impact scenario to implement improvements for detecting similar events and reduce our time to identify and address this type of impact.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|
Time: | Wed Oct 30 15:18:13 2024 |
Description: | Title: Some users may be unable to perform searches within SharePoint Online
User impact: Users may be unable to perform searches within SharePoint Online.
Current status: We're continuing to revert the offending update and we're monitoring as it progresses to ensure it completes successfully. We'll provide an ETA for completion as soon as one is available.
Scope of impact: Any user performing searches within SharePoint Online may be impacted. This issue affects approximately 10 percent of tenants.
Start time: Wednesday, October 30, 2024, at 11:30 AM UTC
Preliminary root cause: A recent update to a subset of authentication configurations contained an error, resulting in impact. This update was intended to introduce general service improvements and was rolled out to approximately 10 percent of tenants.
Next update by: Wednesday, October 30, 2024, at 9:00 PM UTC
|
|
Time: | Wed Oct 30 13:50:48 2024 |
Description: | Title: Users may be unable to perform searches within SharePoint Online
User impact: Users may be unable to perform searches within SharePoint Online.
Current status: We've completed the validation of the reverting process and are monitoring as it progresses. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Any user performing searches within SharePoint Online may be impacted.
Next update by: Wednesday, October 30, 2024, at 8:00 PM UTC
|
|
Time: | Wed Oct 30 12:10:09 2024 |
Description: | Title: Users may be unable to perform searches within SharePoint Online
User impact: Users may be unable to perform searches within SharePoint Online.
Current status: Our investigation indicates that a recent update to a subset of authentication configurations contained an error, resulting in impact. We're working to revert this change to confirm the root cause and remediate this issue.
Scope of impact: Any user performing searches within SharePoint Online may be impacted.
Next update by: Wednesday, October 30, 2024, at 6:00 PM UTC
|
|
Time: | Wed Oct 30 10:46:04 2024 |
Description: | Title: Users may be unable to perform searches within SharePoint Online
User impact: Users may be unable to perform searches within SharePoint Online.
Current status: We're reviewing support case details to determine our next troubleshooting steps.
Scope of impact: Any user performing searches within SharePoint Online may be impacted.
Next update by: Wednesday, October 30, 2024 at 5:00 PM UTC
|
|
Time: | Wed Oct 30 10:12:23 2024 |
Description: | Title: Possible delays or problems when accessing SharePoint Online
User impact: Some customers have reported issues with accessing the service, or using features in SharePoint Online.
Current status: We’re looking into your reported issue and checking for impact to your organization. We'll provide an update within one hour.
|
|
EX918851 - Some users may have been unable to receive or sync on-premises email messages on the Outlook mobile app
Status: | serviceRestored |
Start Time: | Sun Oct 13 20:00:00 2024 |
End Time: | Tue Oct 29 02:30:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail timely delivery |
Classification: | advisory |
Last Updated: | Fri Nov 1 05:14:09 2024 |
Root Cause: | A recent change to the Mailbox Replication Service (MRS) intended to enhance logging had resulted in sync issues for on-premises email messages on the Outlook mobile app. |
Next Update: | N/A |
|
Details
Time: | Fri Nov 1 05:14:09 2024 |
Description: | Title: Some users may have been unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may have been unable to receive or sync on-premises email messages on the Outlook mobile app.
Final status: The deployment has successfully completed and has resolved impact.
Scope of impact: Impact may have occured for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Start time: Monday, October 14, 2024, at 12:00 AM UTC
End time: Tuesday, October 29, 2024 at 6:00 AM UTC
Root cause: A recent change to the Mailbox Replication Service (MRS) intended to enhance logging had resulted in sync issues for on-premises email messages on the Outlook mobile app.
Next actions:
- We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
This is the final update for this event.
|
|
Time: | Wed Oct 30 08:55:35 2024 |
Description: | Title: Some users may be unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may be unable to receive or sync on-premises email messages on the Outlook mobile app.
Current status: The deployment of the fix is taking longer than initially anticipated and we're forecasting that it'll be complete by Friday, November 1, 2024.
Scope of impact: Impact may occur for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Start time: Monday, October 14, 2024, at 12:00 AM UTC
Root cause: A recent change to the Mailbox Replication Service (MRS) intended to enhance logging has resulted in sync issues for on-premises email messages on the Outlook mobile app.
Next update by: Friday, November 1, 2024, at 1:00 PM UTC
|
|
Time: | Mon Oct 28 08:48:44 2024 |
Description: | Title: Some users may be unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may be unable to receive or sync on-premises email messages on the Outlook mobile app.
Current status: We're continuing to implement the change and restart MRS to resolve impact for users.
Scope of impact: Impact may occur for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Start time: Monday, October 14, 2024, at 12:00 AM UTC
Root cause: A recent change to the Mailbox Replication Service (MRS) intended to enhance logging has resulted in sync issues for on-premises email messages on the Outlook mobile app.
Next update by: Wednesday, October 30, 2024, at 1:00 PM UTC
|
|
Time: | Sun Oct 27 10:25:54 2024 |
Description: | Title: Some users may be unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may be unable to receive or sync on-premises email messages on the Outlook mobile app.
Current status: We're proceeding to implement the change and restart MRS to fully resolve impact, which we anticipate will be complete by our next scheduled update.
Scope of impact: Impact may occur for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Start time: Monday, October 14, 2024, at 12:00 AM UTC
Root cause: A recent change to the Mailbox Replication Service (MRS) intended to enhance logging has resulted in sync issues for on-premises email messages on the Outlook mobile app.
Next update by: Monday, October 28, 2024, at 1:00 PM UTC
|
|
Time: | Sun Oct 27 08:52:25 2024 |
Description: | Title: Some users may be unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may be unable to receive or sync on-premises email messages on the Outlook mobile app.
Current status: We're continuing to implement the change and restart the MRS to fully remediate the issue.
Scope of impact: Impact may occur for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Start time: Monday, October 14, 2024, at 12:00 AM UTC
Root cause: A recent change to the Mailbox Replication Service (MRS) intended to enhance logging has resulted in sync issues for on-premises email messages on the Outlook mobile app.
Next update by: Sunday, October 27, 2024, at 3:00 PM UTC
|
|
Time: | Sun Oct 27 00:06:19 2024 |
Description: | Title: Some users may be unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may be unable to receive or sync on-premises email messages on the Outlook mobile app.
Current status: We've tested the configuration change to validate its efficacy and viability as a solution. We're implementing the change and are working on restarting the MRS to fully remediate the issue.
Scope of impact: Impact may occur for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Start time: Monday, October 14, 2024, at 12:00 AM UTC
Root cause: A recent change to the Mailbox Replication Service (MRS) intended to enhance logging has resulted in sync issues for on-premises email messages on the Outlook mobile app.
Next update by: Sunday, October 27, 2024, at 1:00 PM UTC
|
|
Time: | Sat Oct 26 18:52:25 2024 |
Description: | Title: Some users may be unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may be unable to receive or sync on-premises email messages on the Outlook mobile app.
Current status: We've determined that a potential configuration change may be needed to assist with the sync issue. We're testing the efficacy of this path to determine the viability of this solution.
Scope of impact: Impact may occur for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Start time: Monday, October 14, 2024, at 12:00 AM UTC
Root cause: A recent change to the Mailbox Replication Service (MRS) intended to enhance logging has resulted in sync issues for on-premises email messages on the Outlook mobile app.
Next update by: Sunday, October 27, 2024, at 4:30 AM UTC
|
|
Time: | Sat Oct 26 16:50:16 2024 |
Description: | Title: Some users may be unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may be unable to receive or sync on-premises email messages on the Outlook mobile app.
Current status: We've identified a recent change to the Mailbox Replication Service (MRS) intended to enhance logging has resulted in sync issues for on-premises email messages on the Outlook mobile app. We're assessing potential remediation actions to identify an appropriate solution.
Scope of impact: Impact may occur for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Start time: Monday, October 14, 2024, at 12:00 AM UTC
Root cause: A recent change to the Mailbox Replication Service (MRS) intended to enhance logging has resulted in sync issues for on-premises email messages on the Outlook mobile app.
Next update by: Saturday, October 26, 2024, at 11:00 PM UTC
|
|
Time: | Sat Oct 26 14:40:29 2024 |
Description: | Title: Some users may be unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may be unable to receive or sync on-premises email messages on the Outlook mobile app.
Current status: We've confirmed that the issue is isolated to the on-premises environment and have updated the Title, User impact, and Scope of impact sections to reflect this. We're continuing to review mobile client logs to isolate the source and determine appropriate remediation actions.
Scope of impact: Impact may occur for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Next update by: Saturday, October 26, 2024, at 9:00 PM UTC
|
|
Time: | Sat Oct 26 09:01:47 2024 |
Description: | Title: Some users may be unable to receive or sync on-premises email messages on the Outlook mobile app
User impact: Users may be unable to receive or sync on-premises email messages on the Outlook mobile app.
Current status: We’re reviewing details provided in the support case to determine the next steps needed to resolve this issue.
Scope of impact: Impact may occur for some users attempting to receive or sync on-premises email messages on the Outlook mobile app.
Next update by: Saturday, October 26, 2024, at 7:00 PM UTC
|
|
TM917749 - Users are experiencing various failures with Microsoft Teams service and functionality across multiple platforms
Status: | postIncidentReviewPublished |
Start Time: | Thu Oct 24 18:00:00 2024 |
End Time: | Thu Oct 24 21:24:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | incident |
Last Updated: | Thu Oct 31 19:45:09 2024 |
Root Cause: | A routine change is resulting in an unexpected behavior which is resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 31 19:45:09 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Tue Oct 29 00:19:37 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Thu Oct 24 23:04:45 2024 |
Description: | Title: Users are experiencing various failures with Microsoft Teams service and functionality across multiple platforms
User impact: Users were experiencing various failures with Microsoft Teams service and functionality across multiple platforms.
More info: Impact may have occurred in the following scenarios:
-Creating new group chats
-Creating new meetings
-Updating meetings
-Bots' ability to post messages
-Any Microsoft Teams Graph API which supports messages
-Creating Virtual Events such as Webinars or Town Halls in Microsoft Teams
-Escalating 1-1 calls
-Q&A in Microsoft Teams meetings
-Sending messages
-Failures using Flow bot for Microsoft Teams in Microsoft Power Automate
Final status: We completed redeploying the change successfully and confirmed through our monitoring telemetry that the issue is fully resolved.
Scope of impact: Any users attempting to leverage any of the affected scenarios detailed in the More info section may have been impacted by this event.
Start time: Thursday, October 24, 2024, at 10:00 PM UTC
End time: Friday, October 25, 2024, at 1:25 AM UTC
Preliminary root cause: Additional information on the root cause can be found in the Post Incident Report document
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: | Thu Oct 24 21:42:04 2024 |
Description: | Title: Users are experiencing various failures with Microsoft Teams service and functionality across multiple platforms
User impact: Users are experiencing various failures with Microsoft Teams service and functionality across multiple platforms.
More info: Impact may be occurring in the following scenarios:
-Creating new group chats
-Creating new meetings
-Updating meetings
-Bots' ability to post messages
-Any Microsoft Teams Graph API which supports messages
-Creating Virtual Events such as Webinars or Town Halls in Microsoft Teams
-Escalating 1-1 calls
-Q&A in Microsoft Teams meetings
-Sending messages
-Failures using Flow bot for Microsoft Teams in Microsoft Power Automate
Current status: We confirmed that the routine change encountered a deployment issue, which led to impact. We're redeploying the change to remediate the problem, and we've confirmed users are already experiencing relief as our change successfully deploys. We'll provide an estimated time to resolution in our next update.
Scope of impact: Any users attempting to leverage any of the affected scenarios detailed in the More info section may be impacted by this event.
Start time: Thursday, October 24, 2024, at 10:00 PM UTC
Preliminary root cause: A routine change experienced a deployment issue, which led to impact.
Next update by: Friday, October 25, 2024, at 4:00 AM UTC
|
|
Time: | Thu Oct 24 20:35:45 2024 |
Description: | Title: Users are experiencing various failures with Microsoft Teams service and functionality across multiple platforms
User impact: Users are experiencing various failures with Microsoft Teams service and functionality across multiple platforms.
More info: Impact may be occurring in the following scenarios:
-Sending messages
-Creating new group chats
-Creating new meetings
-Updating meetings
-Bots' ability to post messages
-Any Microsoft Teams Graph API which supports messages
-Creating Virtual Events such as Webinars or Town Halls in Microsoft Teams
-Escalating 1-1 calls
-Q&A in Microsoft Teams meetings
Current status: We've clarified the Title and User impact within this communication to better reflect the various impact scenarios. We've identified a routine change that we suspect is resulting in unexpected behavior and causing impact. We're determining the most effective way to alleviate impact and will update as our investigation progresses.
Scope of impact: Any users attempting to leverage any of the affected scenarios detailed in the More info section may be impacted by this event.
Start time: Thursday, October 24, 2024, at 10:00 PM UTC
Preliminary root cause: A routine change is resulting in an unexpected behavior associated with impact.
Next update by: Friday, October 25, 2024, at 2:00 AM UTC
|
|
Time: | Thu Oct 24 20:09:49 2024 |
Description: | Title: Users may not be able to create group chats and may see failures in specific scenarios in Microsoft Teams
User impact: Users may not be able to create group chats and may see failures in specific scenarios in Microsoft Teams.
More info: Impact may be occurring in the following scenarios:
-Sending messages
-Creating new group chats
-Creating new meetings
-Updating meetings
-Creating Virtual events
-Bots' ability to post messages
-Any Microsoft Teams Graph API which supports messages
-Creating Virtual Events such as Webinars or Town Halls in Microsoft Teams
-Escalating 1-1 Call
Current status: We've identified a routine change that we believe is causing the service to have an unexpected behavior. We're determining the most effective way to alleviate impact and will update as our investigation progresses.
Scope of impact: Users attempting to complete scenarios surrounding creating chats may be impacted by this event.
Start time: Thursday, October 24, 2024, at 10:00 PM UTC
Root cause: A routine change is resulting in an unexpected behavior which is resulting in impact.
Next update by: Friday, October 25, 2024, at 2:00 AM UTC
|
|
Time: | Thu Oct 24 19:31:15 2024 |
Description: | Title: Users may not be able to create group chats and may see failures in specific scenarios in Microsoft Teams
User impact: Users may not be able to create group chats and may see failures in specific scenarios in Microsoft Teams.
More info: Impact may be occurring in the following scenarios:
-Sending messages
-Creating new group chats
-Creating new meetings
-Updating meetings
-Creating Virtual events
-Bots' ability to post messages
-Any Teams Graph API which supports messages
Current status: We've identified additional impacted scenarios and listed them in the More Info section. We'll continue to review the affected service environment to help us identify any additional scenarios which may be affected, and we'll update the More info section accordingly. In parallel, we're analyzing the service health telemetry to pinpoint the origin of impact and determine our troubleshooting approach.
Scope of impact: Users attempting to complete scenarios surrounding creating chats may be impacted by this event.
Next update by: Friday, October 25, 2024, at 12:30 AM UTC
|
|
Time: | Thu Oct 24 18:59:52 2024 |
Description: | Title: Users may not be able to create group chats in Microsoft Teams
User impact: Users may not be able to create group chats in Microsoft Teams.
Current status: We're investigating a potential issue in which users may not be able to create group chats in Microsoft Teams. We'll provide an update within 30 minutes.
|
|
CP917795 - Users may be unable to interact with Microsoft Copilot in Microsoft Teams
Status: | postIncidentReviewPublished |
Start Time: | Thu Oct 24 18:00:00 2024 |
End Time: | Thu Oct 24 21:25:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | incident |
Last Updated: | Thu Oct 31 19:41:52 2024 |
Root Cause: | Additional information on root cause can be found in the Post Incident Report Document |
Next Update: | N/A |
|
Details
Time: | Thu Oct 31 19:41:52 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Tue Oct 29 00:27:03 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Thu Oct 24 23:11:23 2024 |
Description: | Title: Users may be unable to interact with Microsoft Copilot in Microsoft Teams
User impact: Users may have been unable to interact with Microsoft Copilot in Microsoft Teams.
Final status: We completed redeploying the change successfully and confirmed through our monitoring telemetry that the issue is fully resolved.
Scope of impact: Any users attempting to interact with Microsoft Copilot in Microsoft Teams may have been impacted.
Start time: Thursday, October 24, 2024, at 10:00 PM UTC
End time: Friday, October 25, 2024, at 1:25 AM UTC
Root cause: Additional information on root cause can be found in the Post Incident Report Document
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: | Thu Oct 24 21:44:29 2024 |
Description: | Title: Users may be unable to interact with Microsoft Copilot in Microsoft Teams
User impact: Users may be unable to interact with Microsoft Copilot in Microsoft Teams.
Current status: We confirmed that the routine change encountered a deployment issue, which led to impact. We're redeploying the change to remediate the problem, and we've confirmed users are already experiencing relief as our change successfully deploys. We'll provide an estimated time to resolution in our next update.
Scope of impact: Any users attempting to interact with Microsoft Copilot in Microsoft Teams may be unable to.
Start time: Thursday, October 24, 2024, at 10:00 PM UTC
Root cause: A routine change experienced a deployment issue, which led to impact.
Next update by: Friday, October 25, 2024, at 4:00 AM UTC
|
|
Time: | Thu Oct 24 21:16:29 2024 |
Description: | Title: Users may be unable to interact with Microsoft Copilot in Microsoft Teams
User impact: Users may be unable to interact with Microsoft Copilot in Microsoft Teams.
Current status: We've identified a routine change that we suspect is resulting in unexpected behavior and causing impact. We're determining the most effective way to alleviate impact and will update as our investigation progresses.
Scope of impact: Any users attempting to interact with Microsoft Copilot in Microsoft Teams may be unable to.
Start time: Thursday, October 24, 2024, at 10:00 PM UTC
Root cause: A routine change is resulting in an unexpected behavior associated with impact.
Next update by: Friday, October 25, 2024, at 3:30 AM UTC
|
|
Time: | Thu Oct 24 20:59:00 2024 |
Description: | Title: Users may be unable to interact with Microsoft Copilot in Microsoft Teams
User impact: Users may be unable to interact with Microsoft Copilot in Microsoft Teams.
Current status: We're investigating a potential issue with users' ability to interact Microsoft Copilot in Microsoft Teams. We'll provide an update within 30 minutes.
|
|
EX920072 - Some users may be unable to search their email in Outlook on the web and may get an error
Status: | serviceRestored |
Start Time: | Mon Oct 28 01:19:00 2024 |
End Time: | Thu Oct 31 12:35:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | advisory |
Last Updated: | Thu Oct 31 13:40:35 2024 |
Root Cause: | A recent configuration update to Outlook on the web wasn't applied to some users' Outlook on the web client. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 31 13:29:38 2024 |
Description: | Title: Some users may be unable to search their email in Outlook on the web and may get an error
User impact: Users may have been unable to search their email in Outlook on the web and may get an error.
More info: Affected users encountered a "Something went wrong. Please try again later." error message. Where possible, users could’ve bypassed the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Some users reported that the roaming signatures feature was missing in Outlook on the web.
Final status: We’ve confirmed that the rate of search errors has returned to normal as a result of resyncing the affected infrastructure. Affected users have reported that searches are now operating as expected and we’ve determined that this issue is resolved.
Scope of impact: Some users may have been unable to search their email in Outlook on the web.
Start time: Monday, October 28, 2024, at 5:19 AM UTC
End time: Thursday, October 31, 2024, at 4:35 PM UTC
Root cause: A recent configuration update to Outlook on the web wasn't applied to some users' Outlook on the web client.
Next steps:
- We’re reviewing our validation and configuration update procedures to better detect and prevent issues like this prior to deployment in the future.
This is the final update for this event.
|
|
Time: | Wed Oct 30 18:22:34 2024 |
Description: | Title: Some users may be unable to search their email in Outlook on the web and may get an error
User impact: Users may be unable to search their email in Outlook on the web and may get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Some users have reported that the roaming signatures feature is missing in Outlook on the web.
Current status: The process of resyncing our update on the remaining affected infrastructure is nearing completion, and while we suspect that this issue is largely resolved, we’ll continue monitoring to ensure the process completes to resolve this issue of all impacted users.
Scope of impact: Some users may be unable to search their email in Outlook on the web.
Start time: Monday, October 28, 2024, at 5:19 AM UTC
Root cause: A recent configuration update to Outlook on the web wasn't applied to some users' Outlook on the web client.
Next update by: Thursday, October 31, 2024, at 6:30 PM UTC
|
|
Time: | Wed Oct 30 13:08:53 2024 |
Description: | Title: Some users may be unable to search their email in Outlook on the web and may get an error
User impact: Users may be unable to search their email in Outlook on the web and may get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Some users have reported that the roaming signatures feature is missing in Outlook on the web.
Current status: We've received reports after the completion of our update that some users are still experiencing impact. After review, we've determined that a subset of Outlook on the web service infrastructure that impacted users utilize didn't receive the update we deployed earlier. We're resyncing our update on these portions of infrastructure to ensure impact is fully remediated.
Scope of impact: Some users attempting to search for email in Outlook on the web may be unable to.
Start time: Monday, October 28, 2024, at 5:19 AM UTC
Root cause: A recent configuration update to Outlook on the web wasn't applied to some users' Outlook on the web client.
Next update by: Thursday, October 31, 2024, at 12:00 AM UTC
|
|
Time: | Tue Oct 29 19:46:25 2024 |
Description: | Title: Some users may be unable to search their email in Outlook on the web and may get an error
User impact: Users may be unable to search their email in Outlook on the web and may get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Some users have reported that the roaming signatures feature is missing in Outlook on the web.
Current status: We've completed the update to refresh and implement the new configuration change for impacted users. We're reaching out to impacted users who reported this issue to validate if our actions have alleviated the impact.
Scope of impact: Some users attempting to search for email in Outlook on the web may be unable to.
Start time: Monday, October 28, 2024, at 5:19 AM UTC
Root cause: A recent configuration update to Outlook on the web that wasn't applied to some users Outlook on the web client.
Next update by: Wednesday, October 30, 2024, at 6:30 PM UTC
|
|
Time: | Tue Oct 29 15:36:18 2024 |
Description: | Title: Some users can't search their email in Outlook on the web and get an error
User impact: Users can't search their email in Outlook on the web and get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Some users have reported that the roaming signatures feature is missing in Outlook on the web.
Current status: Our update to refresh and push the new configuration change to impacted users is taking longer than anticipated but has reached 50 percent of impacted machines. We aim to provide an update timeline to mitigation at our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and this issue affects some users searching for email in Outlook on the web.
Start time: Monday, October 28, 2024, at 5:19 AM UTC
Root cause: A recent configuration update to Outlook on the web that wasn't applied to some users Outlook on the web client.
Next update by: Wednesday, October 30, 2024, at 1:00 AM UTC
|
|
Time: | Tue Oct 29 14:06:05 2024 |
Description: | Title: Some users can't search their email in Outlook on the web and get an error
User impact: Users can't search their email in Outlook on the web and get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Some users have reported that the roaming signatures feature is missing in Outlook on the web.
Current status: We've determined that the root cause of impact was a recent configuration update to Outlook on the web that wasn't applied to some users Outlook on the web client. We've started a new update to refresh and push the new configuration change to impacted users. We anticipate this refresh will be complete by the time of our next scheduled communications update.
Scope of impact: Your organization is affected by this event, and this issue affects some users searching for email in Outlook on the web.
Start time: Monday, October 28, 2024, at 5:19 AM UTC
Estimated time to resolve: We anticipate impact will be resolved by our next scheduled communications update on Monday, October 28, 2024, at 8:30 PM UTC.
Root cause: A recent configuration update to Outlook on the web that wasn't applied to some users Outlook on the web client
Next update by: Tuesday, October 29, 2024, at 8:30 PM UTC
|
|
Time: | Mon Oct 28 20:18:51 2024 |
Description: | Title: Some users can't search their email in Outlook on the web and get an error
User impact: Users can't search their email in Outlook on the web and get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Current status: We're continuing to investigate the potentially missing authorization component in our search for the root cause of impact. In addition, we're testing a mitigation strategy to see if it's successful in remediating impact.
Scope of impact: Your organization is affected by this event, and this issue affects some users searching for email in Outlook on the web.
Next update by: Tuesday, October 29, 2024, at 6:30 PM UTC
|
|
Time: | Mon Oct 28 17:59:41 2024 |
Description: | Title: Some users can't search their email in Outlook on the web and get an error
User impact: Users can't search their email in Outlook on the web and get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Current status: After reviewing the collected logging, we've determined an authorization component necessary for validating searches in Outlook on the web may be missing. We're investigating the missing component further, to determine if it is the root cause of impact.
Scope of impact: Your organization is affected by this event, and this issue affects some users searching for email in Outlook on the web.
Next update by: Tuesday, October 29, 2024, at 1:00 AM UTC
|
|
Time: | Mon Oct 28 16:45:34 2024 |
Description: | Title: Some users can't search their email in Outlook on the web and get an error
User impact: Users can't search their email in Outlook on the web and get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Current status: We're reviewing HTTP Archive format (HAR) files in tandem with previously collected Outlook on the web logging to assist in narrowing the scope of our investigation into the root cause.
Scope of impact: Your organization is affected by this event, and this issue affects some users searching for email in Outlook on the web.
Next update by: Monday, October 28, 2024, at 11:00 PM UTC
|
|
Time: | Mon Oct 28 14:49:09 2024 |
Description: | Title: Some users can't search their email in Outlook on the web and get an error
User impact: Users can't search their email in Outlook on the web and get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Current status: We've collected Outlook on the web logs and found a Uniform Resource Identifier (URI) format exception error is occurring, which we're investigating further to assess what's leading to this problem.
Scope of impact: Your organization is affected by this event, and this issue affects some users searching for email in Outlook on the web.
Next update by: Monday, October 28, 2024, at 9:00 PM UTC
|
|
Time: | Mon Oct 28 13:48:17 2024 |
Description: | Title: Some users can't search their email in Outlook on the web and get an error
User impact: Users can't search their email in Outlook on the web and get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
Current status: We're reviewing example users and trace logs capturing the impact to identify the source of the search failures.
Scope of impact: Your organization is affected by this event, and this issue affects some users searching for email in Outlook on the web.
Next update by: Monday, October 28, 2024, at 7:00 PM UTC
|
|
Time: | Mon Oct 28 12:53:49 2024 |
Description: | Title: Some users can't search their email in Outlook on the web and get an error
User impact: Users can't search their email in Outlook on the web and get an error.
More info: Users that have reported this problem encounter a "Something went wrong. Please try again later." error message. Where possible, users can bypass the problem by utilizing a different client to search for their email, such as the Outlook desktop app.
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.
|
|
TM912524 - We have identified a potential issue with the configuration of Microsoft AutoUpdate (MAU) affecting macOS devices
Status: | investigationSuspended |
Start Time: | Thu Oct 17 12:23:42 2024 |
End Time: | Thu Oct 31 13:26:51 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Thu Oct 31 13:26:57 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Thu Oct 31 13:26:57 2024 |
Description: | Title: We have identified a potential issue with the configuration of Microsoft AutoUpdate (MAU) affecting macOS devices
User impact: If action isn't taken, users’ Microsoft Teams clients may experience a suboptimal user experience.
Final Status: We're suspending this communication as the duration has surpassed the previously announced expiration period.
This is the final update for the event.
|
|
Time: | Thu Oct 17 12:31:42 2024 |
Description: | Title: We have identified a potential issue with the configuration of Microsoft AutoUpdate (MAU) affecting macOS devices
User impact: If action isn't taken, users’ Microsoft Teams clients may experience a suboptimal user experience.
Current Status: We've detected that some users in your organization's environment aren't updating the Microsoft Teams client for macOS. This may result in suboptimal user experience including warning banners, and eventually blocking usage of the Teams macOS client and the user will only have the option to use Teams on the web. Please review and follow the recommendation to prevent any service interruptions.
This communication will expire in 14 days and remain active for the duration.
|
|
CP921928 - Users can't utilize Microsoft Copilot (Microsoft 365) to summarize files with protection labels applied
Status: | serviceRestored |
Start Time: | Wed Oct 30 00:30:00 2024 |
End Time: | Wed Oct 30 19:02:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | advisory |
Last Updated: | Wed Oct 30 19:59:59 2024 |
Root Cause: | The RMS service wasn't processing requests as expected,
which resulted in
impact. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 30 19:59:59 2024 |
Description: | Title: Users can't utilize Microsoft Copilot (Microsoft 365) to summarize files with protection labels applied
User impact: Users couldn't utilize Copilot to summarize files with protection labels applied.
More info: This event impacted users who attempted to utilize Copilot to summarize files that have Microsoft Purview Information Protection (MIP) labels applied to them.
Affected users received the following response to their prompt when attempting to summarize a file with MIP labels applied:
"I am unable to summarize any data from the file titled as the result is protected. Is there anything else I can help you with?"
Final status: We've redirected traffic to an alternate, healthy portion of service infrastructure to resolve the impact and monitored our health dashboards to confirm the issue is remediated.
Scope of impact: Your organization was affected by this event, and any user who attempted to utilize Copilot to summarize files with MIP labels applied was impacted.
Start time: Wednesday, October 30, 2024, at 4:30 AM UTC
End time: Wednesday, October 30, 2024, at 11:02 PM UTC
Root cause: The RMS service wasn't processing requests as expected,
which resulted in
impact.
Next steps:
- We're further reviewing the RMS service to determine what caused it to fail to process requests so that we can proactively identify any potential refinements that may be necessary to prevent similar issues from happening again.
This is the final update for this event.
|
|
Time: | Wed Oct 30 19:32:07 2024 |
Description: | Title: Users can't utilize Microsoft Copilot (Microsoft 365) to summarize files with protection labels applied
User impact: Users can't utilize Copilot to summarize files with protection labels applied.
More info: This event impacts users attempting to utilize Copilot to summarize files that have Microsoft Purview Information Protection (MIP) labels applied to them.
Affected users receive the following response to their prompt when attempting to summarize a file with MIP labels applied:
"I am unable to summarize any data from the file titled as the result is protected. Is there anything else I can help you with?"
Current status: We've identified an issue in which the Rights Management Services (RMS) service isn't processing requests as expected, resulting in Copilot failing to summarize files with MIP labels applied. We're reviewing the RMS service to determine what's causing it to fail to process requests so we can determine our next steps regarding impact remediation.
Scope of impact: Your organization is affected by this event, and any user attempting to utilize Copilot to summarize files with MIP labels applied is impacted.
Start time: Wednesday, October 30, 2024, at 4:30 AM UTC
Root cause: The RMS service isn't processing requests as expected, resulting in impact.
Next update by: Thursday, October 31, 2024, at 1:00 AM UTC
|
|
CP908784 - Web search in Microsoft Copilot (Microsoft 365) may be enabled despite being disabled via cloud policy
Status: | serviceRestored |
Start Time: | Fri Oct 11 02:58:00 2024 |
End Time: | Mon Oct 14 06:30:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | advisory |
Last Updated: | Wed Oct 30 18:19:47 2024 |
Root Cause: | A traffic management misconfiguration was causing a portion of service infrastructure, responsible for facilitating Copilot's ability to retrieve policies such as OCE, to operate below acceptable performance thresholds, resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 11 20:38:42 2024 |
Description: | Title: Web search in Microsoft Copilot (Microsoft 365) may be enabled despite being disabled via cloud policy
User impact: Users' web search functionality in Copilot may have been enabled despite Optional Connected Experiences being disabled.
Final status: After further evaluation, we opted to allocate additional resource capacity in both the US and EU regions to help process requests. Once the resource capacity was functional, we monitored our telemetry to validate the the errors were no longer occurring and that the impact was remediated.
Scope of impact: Any user hosted within the Europe or North America regions may have had web search functionality in Copilot enabled despite Optional Connected Experiences (OCE) being disabled through cloud policy.
Start time: Thursday, October 10, 2024, at 6:58 AM UTC
End time: Monday, October 14, 2024, at 10:30 AM UTC
Root cause: A traffic management misconfiguration was causing a portion of service infrastructure, responsible for facilitating Copilot's ability to retrieve policies such as OCE, to operate below acceptable performance thresholds, resulting in impact.
Next steps:
- We're continuing to analyze the impacted section of infrastructure to gain further insight into what triggered the errors, which will help us prevent similar impact in the future.
- We're working to allocate additional resource capacity in both the US and EU regions to further improve the robustness of the service.
This is the final update for the event.
|
|
Time: | Fri Oct 11 16:59:36 2024 |
Description: | Title: Web search in Microsoft Copilot (Microsoft 365) may be enabled despite being disabled via cloud policy
User impact: Users' web search functionality in Copilot may be enabled despite Optional Connected Experiences (OCE) being disabled.
Current status: We've identified the portion of service infrastructure within the North America region that's operating below acceptable performance thresholds, and we're routing service traffic from the problematic infrastructure to a healthy portion. In parallel, our mitigation efforts to restore the Europe service infrastructure are progressing as expected. We'll aim to provide a timeline for service requests within the US region to be routed to healthy service infrastructure by our next scheduled update.
Scope of impact: Any user hosted within the Europe or North America regions may have web search functionality in Copilot enabled despite OCE being disabled through cloud policy.
Start time: Thursday, October 10, 2024, at 6:58 AM UTC
Root cause: A traffic management misconfiguration is causing a portion of service infrastructure, responsible for facilitating Copilot's ability to retrieve policies such as OCE, to operate below acceptable performance thresholds, resulting in impact.
Next update by: Saturday, October 12, 2024, at 1:00 AM UTC
|
|
Time: | Fri Oct 11 14:53:44 2024 |
Description: | Title: Web search in Microsoft Copilot (Microsoft 365) may be enabled despite being disabled via cloud policy
User impact: Users' web search functionality in Copilot may be enabled despite Optional Connected Experiences (OCE) being disabled.
User impact: Users' web search functionality in Copilot may be enabled despite Optional Connected Experiences (OCE) being disabled.
Current status: We've identified some service requests within the North America region that are failing, and are reviewing the supporting service infrastructure to understand why these requests aren't succeeding. In parallel, we're continuing our efforts to restore the service infrastructure for Europe to expected functionality.
Scope of impact: Any user hosted within the Europe or North America regions may have web search functionality in Copilot enabled despite OCE being disabled through cloud policy.
Start time: Thursday, October 10, 2024, at 6:58 AM UTC
Root cause: A traffic management misconfiguration is causing a portion of service infrastructure, responsible for facilitating Copilot's ability to retrieve policies such as OCE, to operate below acceptable performance thresholds, resulting in impact.
Next update by: Friday, October 11, 2024, at 9:00 PM UTC
|
|
Time: | Fri Oct 11 14:10:32 2024 |
Description: | Title: Web search in Microsoft Copilot (Microsoft 365) may be enabled despite being disabled via cloud policy
User impact: Users' web search functionality in Copilot may be enabled despite Optional Connected Experiences (OCE) being disabled.
Current status: The process of rebalancing traffic to healthy service infrastructure within Europe is taking longer than initially anticipated, but we're continuing these efforts to ensure service is fully restored.
Scope of impact: Any user hosted within the Europe region may have web search functionality in Copilot enabled despite OCE being disabled through cloud policy.
Start time: Thursday, October 10, 2024, at 6:58 AM UTC
Root cause: A traffic management misconfiguration is causing a portion of service infrastructure, responsible for facilitating Copilot's ability to retrieve policies such as OCE, to operate below acceptable performance thresholds, resulting in impact.
Next update by: Friday, October 11, 2024, at 8:00 PM UTC
|
|
Time: | Fri Oct 11 11:52:58 2024 |
Description: | Title: Web search in Microsoft Copilot (Microsoft 365) may be enabled despite being disabled via cloud policy
User impact: Users' web search functionality in Copilot may be enabled despite Optional Connected Experiences (OCE) being disabled.
Current status: We've identified a traffic management misconfiguration that's causing a section of service infrastructure, responsible for facilitating Copilot's ability to retrieve policies such as OCE, to operate below acceptable performance thresholds, resulting in impact. We've rebalanced service traffic in all regions excluding the Europe region, and we're in the process of rebalancing our service infrastructure within Europe to fully resolve this issue. We'll aim to provide a timeline for this process to complete by our next scheduled update.
Scope of impact: Any user hosted within the Europe region may have web search functionality in Copilot enabled despite OCE being disabled through cloud policy.
Start time: Thursday, October 10, 2024, at 6:58 AM UTC
Root cause: A traffic management misconfiguration is causing a portion of service infrastructure, responsible for facilitating Copilot's ability to retrieve policies such as OCE, to operate below acceptable performance thresholds, resulting in impact.
Next update by: Friday, October 11, 2024, at 6:00 PM UTC
|
|
TM910923 - Admins may be unable to view call reporting data for Microsoft Teams calls
Status: | serviceRestored |
Start Time: | Fri Oct 11 20:00:00 2024 |
End Time: | Fri Oct 18 15:00:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Wed Oct 30 13:32:35 2024 |
Root Cause: | A recently implemented change to fix an unrelated issue by recovering temporarily missing data was preventing a portion infrastructure responsible for facilitating call reporting data from efficiently processing requests, leading to impact. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 18 15:34:18 2024 |
Description: | Title: Admins may be unable to view call reporting data for Microsoft Teams calls
User impact: Admins may have been unable to view call reporting data for Microsoft Teams calls.
More info: This impact affected, but may not have been limited to, the following services:
- Call Analytics in the Teams admin center
- Call quality data within the Call Quality Dashboard
- Any service that uses the CallRecord Graph API
Data between Monday, August 5, 2024, and Wednesday, August 16, 2024, was unable to be reprocessed and therefore will be unavailable within Microsoft Teams call reporting data.
Final status: We've completed our operation to process the remaining backlogged requests, and we've monitored our service health telemetry to confirm that the affected call reporting data is now being delivered as expected and impact is remediated.
Scope of impact: Any admin attempting to view call reporting data using one of the affected methods may have been impacted.
Start time: Saturday, October 12, 2024, at 12:00 AM UTC
End time: Friday, October 18, 2024, at 7:00 PM UTC
Root cause: A recently implemented change to fix an unrelated issue by recovering temporarily missing data was preventing a portion infrastructure responsible for facilitating call reporting data from efficiently processing requests, leading to impact.
Next steps:
- We're reviewing our Microsoft Teams infrastructure configuration change procedures pertaining to the components responsible for facilitating call reporting data to prevent similar impact during future mitigation efforts.
This is the final update for the event.
|
|
Time: | Thu Oct 17 19:37:05 2024 |
Description: | Title: Admins may be unable to view call reporting data for Microsoft Teams calls
User impact: Admins may be unable to view call reporting data for Microsoft Teams calls.
More info: The following services may be impacted, but impact isn’t limited to:
- CallRecord Graph API
- Teams admin center - Call Analytics
- Call Quality Dashboard
Current status: We've confirmed that the backlog has fully processed; however, a small amount of requests need to be re-processed to fully resolve the issue. We expect this to complete by our next scheduled update.
Scope of impact: Any admin attempting to view call reporting data using one of the affected methods may be impacted.
Start time: Saturday, October 12, 2024, at 12:00 AM UTC
Root cause: A recently implemented change to fix an unrelated issue by recovering temporarily missing data is preventing the portion infrastructure responsible for facilitating call reporting data from efficiently processing requests.
Next update by: Friday, October 18, 2024, at 9:00 PM UTC
|
|
Time: | Thu Oct 17 13:29:07 2024 |
Description: | Title: Admins may be unable to view call reporting data for Microsoft Teams calls
User impact: Admins may be unable to view call reporting data for Microsoft Teams calls.
More info: The following services may be impacted, but impact isn’t limited to:
- CallRecord Graph API
- Teams admin center - Call Analytics
- Call Quality Dashboard
Current status: We've determined that the vast majority of the backlog has completed processing, and that impact has been resolved for most affected admins. We're monitoring the processing of the remaining backlog, which our updated timelines expect will have completed by our next scheduled update.
Scope of impact: Any admin attempting to view call reporting data using one of the affected methods may be impacted.
Start time: Saturday, October 12, 2024, at 12:00 AM UTC
Root cause: A recently implemented change to fix an unrelated issue by recovering temporarily missing data is preventing the portion infrastructure responsible for facilitating call reporting data from efficiently processing requests.
Next update by: Friday, October 18, 2024, at 1:00 AM UTC
|
|
Time: | Wed Oct 16 20:10:28 2024 |
Description: | Title: Admins may be unable to view call reporting data for Microsoft Teams calls
User impact: Admins may be unable to view call reporting data for Microsoft Teams calls.
More info: The following services may be impacted, but impact isn’t limited to:
- callRecord Graph API
- Teams admin center - Call Analytics
- Call Quality Dashboard
Current status: We're continuing to monitor the progress of the backlog in tandem with gathering an updated remediation timeline, which we anticipate will be available by our next scheduled update.
Scope of impact: Any admin attempting to view call reporting data using one of the affected methods may be impacted.
Start time: Saturday, October 12, 2024, at 12:00 AM UTC
Root cause: A recently implemented change to fix an unrelated issue by recovering temporarily missing data is preventing the portion infrastructure responsible for facilitating call reporting data from efficiently processing requests.
Next update by: Thursday, October 17, 2024, at 6:00 PM UTC
|
|
Time: | Tue Oct 15 14:03:48 2024 |
Description: | Title: Admins may be unable to view call reporting data for Microsoft Teams calls
User impact: Admins may be unable to view call reporting data for Microsoft Teams calls.
More info: The following services may be impacted, but impact isn’t limited to:
- callRecord Graph API
- Teams admin center - Call Analytics
- Call Quality Dashboard
Current status: We’ve completed the rebalancing of the request traffic, and we're monitoring as the backlog of stale data processes and new data populates. Admins will experience remediation incrementally while the backlog of data continues to process, which we anticipate may complete by our next scheduled communications update.
Scope of impact: Any admin attempting to view call reporting data using one of the affected methods may be impacted.
Start time: Saturday, October 12, 2024, at 12:00 AM UTC
Root cause: A recently implemented change to fix an unrelated issue by recovering temporarily missing data is preventing the portion infrastructure responsible for facilitating call reporting data from efficiently processing requests.
Next update by: Thursday, October 17, 2024, at 1:00 AM UTC
|
|
Time: | Mon Oct 14 17:46:27 2024 |
Description: | Title: Admins may be unable to view call reporting data for Microsoft Teams calls
User impact: Admins may be unable to view call reporting data for Microsoft Teams calls.
More info: The following services may be impacted, but impact isn’t limited to:
- callRecord Graph API
- Teams admin center - Call Analytics
- Call Quality Dashboard
Current status: After our service health monitors alerted us to delays in delivery of call reporting data, we determined that a recently implemented change to fix an unrelated issue by recovering temporarily missing data is preventing the portion infrastructure responsible for facilitating call reporting data from efficiently processing requests. We've rebalanced the request traffic to remediate the impact and expect that some admins may begin to see remediation as the data is processed.
Scope of impact: Any admin attempting to view call reporting data using one of the affected methods may be impacted.
Start time: Saturday, October 12, 2024, at 12:00 AM UTC
Root cause: A recently implemented change to fix an unrelated issue by recovering temporarily missing data is preventing the portion infrastructure responsible for facilitating call reporting data from efficiently processing requests.
Next update by: Tuesday, October 15, 2024, at 6:30 PM UTC
|
|
Time: | Mon Oct 14 17:09:40 2024 |
Description: | Title: Users leveraging Graph API for call record data for Microsoft Teams aren't receiving the data
User impact: Users leveraging Graph API for call record data for Microsoft Teams aren't receiving the data.
More info: This issue could also impact third-party apps that rely on Graph API for call record data.
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.
|
|
PP920505 - Copilot Studio – Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
Status: | serviceRestored |
Start Time: | Tue Oct 22 22:26:00 2024 |
End Time: | Wed Oct 30 03:13:00 2024 |
Service: | Power Platform |
Feature Group: | Other |
Classification: | advisory |
Last Updated: | Wed Oct 30 11:26:18 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Wed Oct 30 11:26:18 2024 |
Description: | Title: Copilot Studio – Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
User impact: Users may have been unable to switch back to classic mode after having switched to Generative AI (Preview).
Final Status: We have completed the deployment of the hotfix to your environment, restoring expected functionality.
This is the final update for this incident.
Preliminary Root Cause: A recent service update to introduce the public preview of Generative AI contained a misconfiguration.
Next Steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
|
|
Time: | Tue Oct 29 23:28:13 2024 |
Description: | Title: Copilot Studio – Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
User impact: Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
More Info: Users may additionally experience an agent published using “Generative” orchestration reverting to “Classic”. If this occurs you can create a new agent with the same content and re-publish it.
Current Status: The hotfix deployment is ongoing.
Next Update: Wednesday, October 30, 2024, at 5:00 PM UTC
|
|
Time: | Tue Oct 29 18:25:45 2024 |
Description: | Title: Copilot Studio – Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
User impact: Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
More Info: Users may additionally experience an agent published using “Generative” orchestration reverting to “Classic”. If this occurs you can create a new agent with the same content and re-publish it.
Current Status: We have validated the hotfix and begun deploying it to your environment.
Next Update: Wednesday, October 30, 2024, at 7:00 AM UTC
|
|
Time: | Tue Oct 29 11:19:21 2024 |
Description: | Title: Copilot Studio – Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
User impact: Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
More Info: Users may additionally experience an agent published using “Generative” orchestration reverting to “Classic”. If this occurs you can create a new agent with the same content and re-publish it.
Current Status: We have completed the development of a hotfix for this issue, for which we are now performing final validations. Once complete, we will initiate deployment of this hotfix to correct the misconfiguration and restore classic mode access.
Next Update: Wednesday, October 30, 2024, at 12:00 AM UTC
|
|
Time: | Tue Oct 29 02:44:27 2024 |
Description: | Title: Copilot Studio – Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
User impact: Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
More Info: Users may additionally experience an agent published using “Generative” orchestration reverting to “Classic”. If this occurs you can create a new agent with the same content and re-publish it.
Current Status: We are working to develop and test a hotfix for this issue.
Next Update: Tuesday, October 29, 2024, at 5:00 PM UTC
|
|
Time: | Tue Oct 29 02:11:14 2024 |
Description: | Title: Copilot Studio – Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
User impact: Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
Current Status: After our investigation, we identified that a recent service update to introduce the public preview of Generative AI contained a misconfiguration, preventing some users from being able to switch back to Classic mode after having enabled the new Generative (Preview) mode. We are currently developing a hotfix for this issue.
Next Update: Tuesday, October 29, 2024, at 8:00 AM UTC
|
|
Time: | Tue Oct 29 02:08:50 2024 |
Description: | Title: Copilot Studio – Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
User impact: Users may be unable to switch back to classic mode after having switched to Generative AI (Preview)
Current Status: We are aware of an emerging issue where users may be experiencing failures to switch Generative AI back to Classic mode after having switched to Generative (Preview) mode. 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.
|
|
CP921290 - Some admins experienced delays in receiving Microsoft Copilot (Microsoft 365) usage reports from the admin center
Status: | serviceRestored |
Start Time: | Tue Oct 29 20:00:00 2024 |
End Time: | Wed Oct 30 02:10:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | advisory |
Last Updated: | Wed Oct 30 04:08:04 2024 |
Root Cause: | A section of the data movement system wasn't performing at expected thresholds, which resulted in impact. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 30 04:08:04 2024 |
Description: | Title: Some admins experienced delays in receiving Microsoft Copilot (Microsoft 365) usage reports from the admin center
User impact: Admins may have experienced delays in receiving Copilot usage reports from the admin center.
Final status: We've successfully reprocessed the impacted Microsoft Copilot (Microsoft 365) usage report data, which has remediated impact.
Scope of impact: Admins in the North America and Asia Pacific regions may have experienced delays in receiving Copilot usage reports from the admin center.
Start time: Wednesday, October 30, 2024, at 12:00 AM UTC
End time: Wednesday, October 30, 2024, at 6:10 AM UTC
Root cause: A section of the data movement system wasn't performing at expected thresholds, which resulted in impact.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|
Time: | Wed Oct 30 01:39:15 2024 |
Description: | Title: Some admins may experience delays in receiving Microsoft Copilot (Microsoft 365) usage reports from the admin center
User impact: Admins may experience delays in receiving Copilot usage reports from the admin center.
Current status: We've identified that a portion of the data movement system isn't performing at expected thresholds. We're reprocessing this data in an effort to alleviate impact.
Scope of impact: Admins in the North America and Asia Pacific regions may experience delays in receiving Copilot usage reports from the admin center.
Start time: Wednesday, October 30, 2024, at 12:00 AM UTC
Root cause: A portion of the data movement system isn't performing at expected thresholds, resulting in impact.
Next update by: Thursday, October 31, 2024, at 10:00 AM UTC
|
|
Time: | Wed Oct 30 01:19:09 2024 |
Description: | Title: We're looking into a potential problem impacting Microsoft Copilot (Microsoft 365)
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue impacting Microsoft Copilot (Microsoft 365) and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
FL917776 - Users may be experiencing failures using flow bot for Microsoft Teams
Status: | postIncidentReviewPublished |
Start Time: | Thu Oct 24 17:54:00 2024 |
End Time: | Thu Oct 24 21:03:00 2024 |
Service: | Microsoft Power Automate |
Feature Group: | Other |
Classification: | incident |
Last Updated: | Tue Oct 29 15:30:50 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Tue Oct 29 14:44:33 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Thu Oct 24 21:38:07 2024 |
Description: | Title: Users may be experiencing failures using flow bot for Microsoft Teams
User impact: Users may have been experiencing failures using flow bot for Microsoft Teams.
Final Status: We have completed the rollback and, following this, confirmed via service diagnostic analysis that user impact has been remediated.
A Post Incident Report will be published within five days.
Preliminary Root Cause: Impact occurred following a recent change applied to the service infrastructure responsible for Flow bot functionality.
Next Steps: We're reviewing our diagnostics of the impacted service infrastructure to find ways to prevent this problem from happening again.
|
|
Time: | Thu Oct 24 20:51:24 2024 |
Description: | Title: Users may be experiencing failures using flow bot for Microsoft Teams
User impact: Users may be experiencing failures using flow bot for Microsoft Teams.
Current Status: Upon investigation, we determined that this issue occurred following a recent change applied to the service infrastructure responsible for Flow bot functionality. We identified a change and are in the process of rolling it back.
Next Update: Friday, October 25, 2024, at 4:00 AM UTC
|
|
Time: | Thu Oct 24 20:13:36 2024 |
Description: | Title: Users may be experiencing failures using flow bot for Microsoft Teams
User impact: Users may be experiencing failures using flow bot for Microsoft Teams.
Current Status: We are aware of an emerging issue where users may be experiencing failures using flow bot for Microsoft Teams. 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.
|
|
CR917769 - Users may experience failures for multiple scenarios in Omnichannel for Customer Service
Status: | postIncidentReviewPublished |
Start Time: | Thu Oct 24 18:00:00 2024 |
End Time: | Thu Oct 24 22:20:00 2024 |
Service: | Dynamics 365 Apps |
Feature Group: | Components/Features |
Classification: | incident |
Last Updated: | Tue Oct 29 14:52:05 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Tue Oct 29 14:52:05 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Thu Oct 24 22:52:07 2024 |
Description: | Title: Users may experience failures for multiple scenarios in Omnichannel for Customer Service
User impact: Users may have experienced failures for multiple scenarios in Omnichannel for Customer Service.
More Info: This issue impacted the following scenarios:
Outbound calls
Voice call transcripts
Starting chats
Sending and receiving messages
Final Status: We have completed restarting the impacted service nodes and have confirmed via service diagnostic analysis that user impact has been remediated.
A Post Incident Report will be published within five days.
Preliminary Root Cause: A service dependency deployed an update that contained a misconfiguration, which impacted the underlying service infrastructure utilized by Omnichannel for Customer Service.
Next Steps: We're reviewing our update procedures to better identify similar issues during our development and testing cycles.
|
|
Time: | Thu Oct 24 22:14:33 2024 |
Description: | Title: Users may experience failures for multiple scenarios in Omnichannel for Customer Service
User impact: Users may experience failures for multiple scenarios in Omnichannel for Customer Service.
More Info: This issue is impacting the following scenarios:
Outbound calls
Voice call transcripts
Starting chats
Sending and receiving messages
Current Status: We are continuing our efforts to restart the impacted service nodes to ensure the hotfix is applied and are monitoring service diagnostics for recovery.
Next Update: October 25, 2024, at 3:30 AM UTC
|
|
Time: | Thu Oct 24 21:18:55 2024 |
Description: | Title: Users may experience failures for multiple scenarios in Omnichannel for Customer Service
User impact: Users may experience failures for multiple scenarios in Omnichannel for Customer Service.
More Info: This issue is impacting the following scenarios:
Outbound calls
Voice call transcripts
Starting chats
Sending and receiving messages
Current Status: We are continuing our efforts to restart the impacted service nodes to ensure the hotfix is applied and are monitoring service diagnostics for recovery.
Next Update: October 25, 2024, at 2:30 AM UTC
|
|
Time: | Thu Oct 24 20:11:05 2024 |
Description: | Title: Users may experience failures for multiple scenarios in Omnichannel for Customer Service
User impact: Users may experience failures for multiple scenarios in Omnichannel for Customer Service.
More Info: This issue is impacting the following scenarios:
Outbound calls
Voice call transcripts
Starting chats
Sending and receiving messages
Current Status: Following our investigation, we identified that a service dependency deployed an update that contained a misconfiguration, which impacted the underlying service infrastructure utilized by Omnichannel for Customer Service. We have created and deployed a hotfix to address this issue and are restarting the impacted service nodes to ensure the hotfix is applied.
Next Update: October 25, 2024, at 1:30 AM UTC
|
|
Time: | Thu Oct 24 19:58:09 2024 |
Description: | Title: Users may experience failures for multiple scenarios in Omnichannel for Customer Service
User impact: Users may experience failures for multiple scenarios in Omnichannel for Customer Service.
Users may experience failures for multiple scenarios in Omnichannel for Customer Service.
More Info: This issue is impacting the following scenarios:
Outbound calls
Voice call transcripts
Starting chats
Sending and receiving messages
Current Status: We are aware of an emerging issue where users are experiencing failures for multiple scenarios in Omnichannel for Customer Service. 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.
|
|
MV912202 - Some users may see inaccurate mail view metrics for some Microsoft Viva services
Status: | serviceDegradation |
Start Time: | Wed Oct 16 20:41:50 2024 |
End Time: | N/A |
Service: | Microsoft Viva |
Feature Group: | Viva Insights |
Classification: | advisory |
Last Updated: | Mon Oct 28 15:07:24 2024 |
Root Cause: | A build released in July contains refactored code that’s causing impact. |
Next Update: | Monday, November 4, 2024, at 7:30 PM UTC |
|
Details
Time: | Mon Oct 28 13:58:43 2024 |
Description: | Title: Some users may see inaccurate mail view metrics for some Microsoft Viva services
User impact: Users may see inaccurate mail view metrics in services that utilize metrics from the Classic Outlook desktop client.
More info: Impact is specific to Microsoft Viva services that rely on the mail view metrics from the classic Outlook desktop client, such as Microsoft Viva Amplify and Microsoft Viva Insights. Users may see inaccuracies in the Unique Viewers count in reports for publications sent to Outlook via Viva Amplify. Users of metrics from alternate Exchange Online connection methods should be unaffected.
Current status: The fix is saturating within the affected environments, and we anticipate it may take one to two more weeks for the saturation to complete based on the current rate of deployment within the deployment pipeline. We expect the remaining affected users will experience remediation incrementally as the deployment progresses.
Scope of impact: Some users may see inaccurate mail view metrics in products that utilize metrics from the classic Outlook desktop client, including Viva Amplify and Viva Insights.
Start time: Friday, October 18, 2024, at 9:53 PM UTC
Root cause: A build released in July contains refactored code that’s causing impact.
Next update by: Monday, November 4, 2024, at 7:30 PM UTC
|
|
Time: | Mon Oct 21 14:34:33 2024 |
Description: | Title: Some users may see inaccurate mail view metrics for some Microsoft Viva services
User impact: Users may see inaccurate mail view metrics in services that utilize metrics from the Classic Outlook desktop client.
More info: Impact is specific to Microsoft Viva services that rely on the mail view metrics from the classic Outlook desktop client, such as Microsoft Viva Amplify and Microsoft Viva Insights. Users may see inaccuracies in the Unique Viewers count in reports for publications sent to Outlook via Viva Amplify. Users of metrics from alternate Exchange Online connection methods should be unaffected.
Current status: We've completed our validation process and have started deploying the fix to the impacted environments. We've confirmed that the fix is currently 50 percent saturated, and we anticipate it may take one to three weeks for the saturation to complete based on the current rate of deployment within the deployment pipeline. We expect the remaining affected users will experience remediation incrementally as the deployment progresses.
Scope of impact: Some users may see inaccurate mail view metrics in products that utilize metrics from the classic Outlook desktop client, including Viva Amplify and Viva Insights.
Start time: Friday, October 18, 2024, at 9:53 PM UTC
Root cause: A build released in July contains refactored code that’s causing impact.
Next update by: Monday, October 28, 2024, at 7:30 PM UTC
|
|
Time: | Fri Oct 18 14:37:44 2024 |
Description: | Title: Some users may see inaccurate mail view metrics for some Microsoft Viva services
User impact: Users may see inaccurate mail view metrics in services that utilize metrics from the Classic Outlook desktop client.
More info: Impact is specific to Microsoft Viva services that rely on the mail view metrics from the classic Outlook desktop client, such as Microsoft Viva Amplify and Microsoft Viva Insights. Users may see inaccuracies in the Unique Viewers count in reports for publications sent to Outlook via Viva Amplify. Users of metrics from alternate Exchange Online connection methods should be unaffected.
Current status: We're continuing our development and validation process to correct the code and ensure efficacy before applying the solution to the affected environments. Once validated, we'll provide a resolution timeline.
Scope of impact: Some users may see inaccurate mail view metrics in products that utilize metrics from the classic Outlook desktop client, including Viva Amplify and Viva Insights.
Start time: Friday, October 18, 2024, at 9:53 PM UTC
Root cause: A build released in July contains refactored code that’s causing impact.
Next update by: Monday, October 21, 2024, at 7:30 PM UTC
|
|
Time: | Thu Oct 17 16:03:27 2024 |
Description: | Title: Some users may see inaccurate mail view metrics for some Microsoft Viva services
User impact: Users may see inaccurate mail view metrics in services that utilize metrics from the Classic Outlook desktop client.
More info: Impact is specific to Microsoft Viva services that rely on the mail view metrics from the classic Outlook desktop client, such as Microsoft Viva Amplify and Microsoft Viva Insights. Users may see inaccuracies in the Unique Viewers count in reports for publications sent to Outlook via Viva Amplify. Users of metrics from alternate Exchange Online connection methods should be unaffected.
Current status: Our investigation of the service telemetry and logs isolated a build released in July which contains refactored code that’s causing impact. We're developing a fix to correct the code, and we'll provide a timeline for the completion as one becomes available.
Scope of impact: Some users may see inaccurate mail view metrics in products that utilize metrics from the classic Outlook desktop client, including Viva Amplify and Viva Insights.
Root cause: A build released in July contains refactored code that’s causing impact.
Next update by: Friday, October 18, 2024, at 8:30 PM UTC
|
|
Time: | Wed Oct 16 20:45:00 2024 |
Description: | Title: Some users may see inaccurate mail view metrics for some Microsoft Viva services
User impact: Users may see inaccurate mail view metrics in services that utilize metrics from the Classic Outlook desktop client.
More info: Impact is specific to Microsoft Viva services that rely on the mail view metrics from the Classic Outlook desktop client, such as Microsoft Viva Amplify and Microsoft Viva Insights. Users may see inaccuracies in the Unique Viewers count in reports for publications sent to Outlook via Viva Amplify. Users utilizing metrics from alternate Exchange Online connection methods should be unaffected.
Current status: We've identified that an issue with the mail view metrics being gathered from the Classic Outlook desktop client is resulting in impact to features reliant on this data in both Microsoft Viva Amplify and Microsoft Viva Insights. We're reviewing service telemetry, relevant service logging, and recent changes made to the Classic Outlook desktop client to give us further insight into the underlying root cause and assist us in determining our next steps.
Scope of impact: Some users may see inaccurate mail view metrics in products that utilize metrics from the Classic Outlook desktop client, including Viva Amplify and Viva Insights.
Next update by: Thursday, October 17, 2024, at 9:30 PM UTC
|
|
TM920099 - Users are unable to use the Walkie Talkie app within Microsoft Teams
Status: | serviceRestored |
Start Time: | Mon Oct 28 11:28:00 2024 |
End Time: | Mon Oct 28 12:26:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Mon Oct 28 13:51:39 2024 |
Root Cause: | A subset of service infrastructure that helps facilitate access to the Walkie-Talkie app within Microsoft Teams had dropped below our manageable service performance thresholds, resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Mon Oct 28 13:51:39 2024 |
Description: | Title: Users are unable to use the Walkie Talkie app within Microsoft Teams
User impact: Users were unable to use the Walkie Talkie app within Microsoft Teams.
Final status: Our automated service monitoring isolated a subset of service infrastructure that had dropped below our manageable service performance thresholds, preventing users from using the Walkie Talkie app within Microsoft Teams. We've rerouted service traffic to an alternate subset of service infrastructure and confirmed this remediated the impact.
Scope of impact: Your organization was affected by this event, and all users were unable to use the Walkie-Talkie app within Microsoft Teams.
Start time: Monday, October 28, 2024, at 3:28 PM UTC
End time: Monday, October 28, 2024, at 4:26 PM UTC
Root cause: A subset of service infrastructure that helps facilitate access to the Walkie-Talkie app within Microsoft Teams had dropped below our manageable service performance thresholds, resulting in impact.
Next steps:
- We're further analyzing the affected subset of service infrastructure so we can isolate the source for the lower-than-expected performance levels to help prevent similar problems in the future.
This is the final update for the event.
|
|
Time: | Mon Oct 28 13:32:44 2024 |
Description: | Title: Users are unable to use the Walkie Talkie app within Microsoft Teams
User impact: Users were unable to use the Walkie Talkie app within Microsoft Teams.
Current status: We've investigated a problem in which users were unable to use\ the Walkie Talkie app within 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.
|
|
EX917719 - Some users see incorrect room availability information in the Room Finder within Exchange Online.
Status: | serviceRestored |
Start Time: | Mon Oct 21 11:52:00 2024 |
End Time: | Fri Oct 25 01:30:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | advisory |
Last Updated: | Mon Oct 28 12:46:01 2024 |
Root Cause: | A change contained within a recent service update altered the way certain time zone-related data were being handled by the service to resolve an unrelated issue resulted in impact. |
Next Update: | N/A |
|
Details
Time: | Mon Oct 28 12:46:01 2024 |
Description: | Title: Some users see incorrect room availability information in the Room Finder within Exchange Online.
User impact: Users saw incorrect room availability information in the Room Finder within Exchange Online.
More info: Affected users may have seen inconsistent information between Scheduling Assistant and Room Finder within Exchange Online, specific to room availability.
Impact may have manifested in any Exchange Online connection method, including but not limited to the Outlook desktop client and Outlook on the web.
Final status: We confirmed with a subset of affected users that impact is remediated following our rollback of the service update causing the issue.
Scope of impact: Some users serviced by the affected portions of infrastructure saw incorrect information when using the Room Finder within Exchange Online.
Start time: Monday, October 21, 2024, at 3:52 PM UTC
End time: Friday, October 25, 2024, at 5:30 AM UTC
Root cause: A change contained within a recent service update altered the way certain time zone-related data were being handled by the service to resolve an unrelated issue resulted in impact.
Next steps:
- We're reviewing and improving our service update validation procedures to prevent similar time zone-related issues from causing impact in the future.
This is the final update for the event.
|
|
Time: | Fri Oct 25 11:52:45 2024 |
Description: | Title: Some users see incorrect room availability information in the Room Finder within Exchange Online.
User impact: Users see incorrect room availability information in the Room Finder within Exchange Online.
More info: Affected users may see inconsistent information between Scheduling Assistant and Room Finder within Exchange Online, specific to room availability.
Impact may manifest in any Exchange Online connection method, including but not limited to the Outlook desktop client and Outlook on the web.
Current status: We're continuing to reach out to a subset of affected users to ensure that impact has been remediated.
Scope of impact: Some users serviced by the affected portions of infrastructure see incorrect information when using the Room Finder within Exchange Online.
Start time: Monday, October 21, 2024, at 3:52 PM UTC
Root cause: A change contained within a recent service update that's altering the way certain time zone-related data was being handled by the service to resolve an unrelated issue is resulting in impact.
Next update by: Monday, October 28, 2024, at 5:00 PM UTC
|
|
Time: | Fri Oct 25 01:35:53 2024 |
Description: | Title: Some users see incorrect room availability information in the Room Finder within Exchange Online
User impact: Users see incorrect room availability information in the Room Finder within Exchange Online.
More info: Affected users may see inconsistent information between Scheduling Assistant and Room Finder within Exchange Online, specific to room availability.
Impact may manifest in any Exchange Online connection method, including but not limited to the Outlook desktop client and Outlook on the web.
Current status: We've rolled back the offending service update and the service health telemetry appears to be stable after an extended period of monitoring. Additionally, we're reaching out to a subset of affected users to ensure that impact has been remediated.
Scope of impact: Some users serviced by the affected portions of infrastructure see incorrect information when using the Room Finder within Exchange Online.
Start time: Monday, October 21, 2024, at 3:52 PM UTC
Root cause: A change contained within a recent service update that's altering the way certain time zone-related data was being handled by the service to resolve an unrelated issue is resulting in impact.
Next update by: Friday, October 25, 2024, at 5:00 PM UTC
|
|
Time: | Thu Oct 24 22:20:23 2024 |
Description: | Title: Some users see incorrect information when using the Scheduling Assistant in Room Finder within Exchange Online
User impact: Users see incorrect information when using the Scheduling Assistant in Room Finder within Exchange Online.
More info: Affected users may see inconsistent information between Scheduling Assistant and Room Finder within Exchange Online, specific to room availability.
Impact may manifest in any Exchange Online connection method, including but not limited to the Outlook desktop client and Outlook on the web.
Current status: We've identified that a change contained within a recent service update that's altering the way certain time zone-related data was being handled by the service to resolve an unrelated issue is resulting in impact. We're moving to roll back the offending change throughout the affected environment and anticipate this process may complete by the time of our next scheduled update, at which point we'll test to confirm impact is resolved as expected.
Scope of impact: Some users serviced by the affected portions of infrastructure see incorrect information when using the Scheduling Assistant in Room Finder within Exchange Online.
Start time: Monday, October 21, 2024, at 3:52 PM UTC
Root cause: A change contained within a recent service update that's altering the way certain time zone-related data was being handled by the service to resolve an unrelated issue is resulting in impact.
Next update by: Friday, October 25, 2024, at 6:00 AM UTC
|
|
Time: | Thu Oct 24 21:27:51 2024 |
Description: | Title: Some users see incorrect information when using the Scheduling Assistant in Room Finder within Exchange Online
User impact: Users see incorrect information when using the Scheduling Assistant in Room Finder within Exchange Online.
More info: Affected users may see inconsistent information between Scheduling Assistant and Room Finder within Exchange Online, specific to room availability.
Impact may manifest in any Exchange Online connection method, including but not limited to the Outlook desktop client and Outlook on the web.
Current status: Our review of the provided network trace logs has been inconclusive. Additionally, after completing our preliminary investigation, we've identified that impact now appears to manifest in all clients, rather than just the Outlook desktop client. We're proceeding with further analysis of the latest updates to the Exchange Online service to identify any recent changes that may be contributing to impact.
Scope of impact: Some users serviced by the affected portions of infrastructure see incorrect information when using the Scheduling Assistant in Room Finder within Exchange Online.
Next update by: Friday, October 25, 2024, at 3:30 AM UTC
|
|
Time: | Thu Oct 24 20:56:36 2024 |
Description: | Title: Some users see incorrect information when using the Scheduling Assistant in Room Finder in the Outlook desktop client
User impact: Users see incorrect information when using the Scheduling Assistant in Room Finder in the Outlook desktop client.
More info: Room Finder functionality itself remains unaffected. As a workaround for this UI issue, users can access Outlook on the web to ensure accurate scheduling information.
Current status: Our review of the provided network trace logs has been inconclusive. We're proceeding with further analysis of the latest updates to the Outlook desktop client to identify any recent changes that may be contributing to impact.
Scope of impact: Your organization is impacted by this event, and some see incorrect information when using the Scheduling Assistant in Room Finder in the Outlook desktop client.
Next update by: Friday, October 25, 2024, at 3:00 AM UTC
|
|
Time: | Thu Oct 24 18:42:16 2024 |
Description: | Title: Some users see incorrect information when using the Scheduling Assistant in Room Finder in the Outlook desktop client
User impact: Users see incorrect information when using the Scheduling Assistant in Room Finder in the Outlook desktop client.
More info: Room Finder functionality itself remains unaffected. As a workaround for this UI issue, users can access Outlook on the web to ensure accurate scheduling information.
Current status: We're continuing with further review of the provided Fiddler network trace logs to gain further insight into the underlying source of impact and determine our next steps.
Scope of impact: Your organization is impacted by this event, and some see incorrect information when using the Scheduling Assistant in Room Finder in the Outlook desktop client.
Next update by: Friday, October 25, 2024, at 1:00 AM UTC
|
|
Time: | Thu Oct 24 17:45:36 2024 |
Description: | Title: Some users see incorrect information when using the Scheduling Assistant in Room Finder in the Outlook desktop client
User impact: Users see incorrect information when using the Scheduling Assistant in Room Finder in the Outlook desktop client.
More info: Room Finder functionality itself remains unaffected. As a workaround for this UI issue, users can access Outlook on the web to ensure accurate scheduling information.
Current status: We've received reports from your organization that a subset of users is encountering incorrect information in the Scheduling Assistant within Room Finder in the Outlook desktop client. To assess the issue and identify appropriate mitigation steps, we're currently reviewing the provided Fiddler traces.
Scope of impact: Your organization is impacted by this event, and some see incorrect information when using the Scheduling Assistant in Room Finder in the Outlook desktop client.
Next update by: Thursday, October 24, 2024, at 11:00 PM UTC
|
|
EX918572 - Some users may see intermittent delays or be unable to access Exchange Online through certain connection methods
Status: | serviceRestored |
Start Time: | Fri Oct 25 18:00:00 2024 |
End Time: | Fri Oct 25 20:10:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | incident |
Last Updated: | Fri Oct 25 20:23:09 2024 |
Root Cause: | Some portions of infrastructure responsible for facilitating reliable access to the Exchange Online service weren't processing certain types of requests as expected, resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 25 20:23:09 2024 |
Description: | Title: Some users may see intermittent delays or be unable to access Exchange Online through certain connection methods
User impact: Users may have seen intermittent delays or been unable to access Exchange Online through certain connection methods.
More info: Impact was specific to users attempting to access Exchange Online through Outlook on the web or connection methods reliant on Exchange ActiveSync (EAS) and Messaging Application Programming Interface (MAPI).
Final status: We've identified that some portions of infrastructure responsible for facilitating reliable access to the Exchange Online service weren't processing certain types of requests as expected, resulting in impact. We manually restarted the affected portions of infrastructure to resolve the issue and confirmed after an additional period of monitoring that impact was successfully remediated.
Scope of impact: Users serviced by the affected portion of infrastructure attempting to access Exchange Online may have been impacted.
Start time: Friday, October 25, 2024, at 10:00 PM UTC
End time: Saturday, October 26, 2024, at 12:10 AM UTC
Root cause: Some portions of infrastructure responsible for facilitating reliable access to the Exchange Online service weren't processing certain types of requests as expected, 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 to better prevent similar impact in the future.
This is the final update for the event.
|
|
Time: | Fri Oct 25 19:30:34 2024 |
Description: | Title: Some users may see intermittent delays or be unable to access Exchange Online through certain connection methods
User impact: Users may see intermittent delays or be unable to access Exchange Online through certain connection methods.
More info: Impact is specific to users attempting to access Exchange Online through Outlook on the web or connection methods reliant on Exchange ActiveSync (EAS) and Messaging Application Programming Interface (MAPI).
Current status: We've identified a potential issue with a portion of infrastructure responsible for reliable access to the Exchange Online service. We're further investigating and defining this issue to gain additional insight into the source of impact and determine our next steps.
Scope of impact: Users serviced by the affected portion of infrastructure attempting to access Exchange Online may be impacted.
Next update by: Saturday, October 26, 2024, at 1:00 AM UTC
|
|
Time: | Fri Oct 25 19:06:50 2024 |
Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|
TM917674 - Some users may be unable to see the meeting attendance report in Microsoft Teams
Status: | serviceRestored |
Start Time: | Thu Oct 24 13:52:00 2024 |
End Time: | Thu Oct 24 18:40:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Thu Oct 24 19:07:05 2024 |
Root Cause: | A recent update to Microsoft Teams, intended to update internal authorization components, introduced a code error where an authorization component needed to validate the attendance report was missing, resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 24 19:07:05 2024 |
Description: | Title: Some users may be unable to see the meeting attendance report in Microsoft Teams
User impact: Users may have been unable to see the meeting attendance report in Microsoft Teams.
More info: Impacted users who accessed the meeting attendance report saw a blank screen stating "Attendance info isn't available yet. Check again later".
Final status: We've confirmed with an internal testing account that the meeting attendance report is available again.
Scope of impact: Some users may have been unable to see the meeting attendance report in Microsoft Teams.
Start time: Thursday, October 24, 2024, at 5:52 PM UTC
End time: Thursday, October 24, 2024, at 10:40 PM UTC
Root cause: A recent update to Microsoft Teams, intended to update internal authorization components, introduced a code error where an authorization component needed to validate the attendance report was missing, resulting in impact.
Next steps:
- We're continuing with our investigation into the authorization errors that were being returned when attempting to access the attendance report to determine why impact persisted after the deployment of the fix was completed. This will help us proactively identify any potential refinements that may be necessary to help prevent similar issues from happening in the future.
This is the final update for this event.
|
|
Time: | Thu Oct 24 17:20:46 2024 |
Description: | Title: Some users may be unable to see the meeting attendance report in Microsoft Teams
User impact: Users may be unable to see the meeting attendance report in Microsoft Teams.
More info: Impacted users who access the meeting attendance report see a blank screen stating "Attendance info isn't available yet. Check again later".
Current status: We've completed the deployment of our update but we've confirmed that the meeting attendance report is still unavailable. We're investigating authorization errors being returned when attempting to access the attendance report to determine why impact is persisting.
Scope of impact: Some users may be unable to see the meeting attendance report in Microsoft Teams.
Start time: Thursday, October 24, 2024, at 5:52 PM UTC
Root cause: A recent update to Microsoft Teams, intended to update internal authorization components, introduced a code error where an authorization component needed to validate the attendance report was missing, resulting in impact.
Next update by: Thursday, October 24, 2024, at 11:30 PM UTC
|
|
Time: | Thu Oct 24 16:29:31 2024 |
Description: | Title: Some users may be unable to see the meeting attendance report in Microsoft Teams
User impact: Users may be unable to see the meeting attendance report in Microsoft Teams.
More info: Impacted users who access the meeting attendance report see a blank screen stating "Attendance info isn't available yet. Check again later".
Current status: We've determined that a recent update to Microsoft Teams, intended to update internal authorization components, introduced a code error where an authorization component needed to validate the attendance report was missing, resulting in impact. We're deploying a new update to restore the missing component to resolve impact and we estimate this update will be complete by the time of our next scheduled update.
Scope of impact: Some users may be unable to see the meeting attendance report in Microsoft Teams.
Start time: Thursday, October 24, 2024, at 5:52 PM UTC
Estimated time to resolve: We anticipate impact will be resolved by the time of our next scheduled update on Thursday, October 24, 2024, at 9:30 PM UTC.
Root cause: A recent update to Microsoft Teams, intended to update internal authorization components, introduced a code error where an authorization component needed to validate the attendance report was missing, resulting in impact.
Next update by: Thursday, October 24, 2024, at 9:30 PM UTC
|
|
Time: | Thu Oct 24 16:07:42 2024 |
Description: | Title: Some users may be unable to see the meeting attendance report in Microsoft Teams
User impact: Users may be unable to see the meeting attendance report in Microsoft Teams.
More info: Impacted users who access the meeting attendance report see a blank screen stating "Attendance info isn't available yet. Check again later".
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.
|
|
EX917072 - Some users may experience intermittent errors or failures when accessing their Exchange Online mailbox
Status: | serviceRestored |
Start Time: | Wed Oct 23 21:00:00 2024 |
End Time: | Wed Oct 23 23:40:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | advisory |
Last Updated: | Thu Oct 24 00:10:25 2024 |
Root Cause: | A portion of infrastructure that facilitates access to Exchange Online mailboxes was performing below the expected service threshold. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 24 00:10:25 2024 |
Description: | Title: Some users may experience intermittent errors or failures when accessing their Exchange Online mailbox
User impact: Users may have experienced intermittent errors or failures when accessing their Exchange Online mailbox.
More info: This issue impacted the following connection methods:
-Outlook on the web
-Connection methods leveraging Messaging Application Programming Interface (MAPI)
Final status: We rerouted connections to alternate infrastructure and monitored the environment to validate that service was restored.
Scope of impact: This issue may have potentially affected some users in North America attempting to access their Exchange Online mailbox through the affected connection methods.
Start time: Thursday, October 24, 2024, at 1:00 AM UTC
End time: Thursday, October 24, 2024, at 3:40 AM UTC
Root cause: A portion of infrastructure that facilitates access to Exchange Online mailboxes was performing below the expected service threshold.
Next steps:
- We're reviewing our monitoring and automated recovery tools to find ways to better detect and prevent similar issues from occurring in the future.
This is the final update for the event.
|
|
Time: | Wed Oct 23 23:57:26 2024 |
Description: | Title: Some users may experience intermittent errors or failures when accessing their Exchange Online mailbox
User impact: Users may experience intermittent errors or failures when accessing their Exchange Online mailbox.
More info: This issue impacts the following connection methods:
-Outlook on the web
-Connection methods leveraging Messaging Application Programming Interface (MAPI)
Current status: We've rerouted connections to an alternate portion of infrastructure and are monitoring the environment to confirm the failures are no longer occurring.
Scope of impact: This issue may potentially affect some users in North America attempting to access their Exchange Online mailbox through the affected connection methods.
Start time: Thursday, October 24, 2024, at 1:00 AM UTC
Root cause: A portion of infrastructure that facilitates access to Exchange Online mailboxes is performing below the expected service threshold.
Next update by: Thursday, October 24, 2024, at 6:00 AM UTC
|
|
Time: | Wed Oct 23 22:43:30 2024 |
Description: | Title: Some users may experience intermittent errors or failures when accessing their Exchange Online mailbox
User impact: Users may experience intermittent errors or failures when accessing their Exchange Online mailbox.
More info: This issue impacts the following connection methods:
-Outlook on the web
-Connection methods leveraging Messaging Application Programming Interface (MAPI)
Current status: We identified a portion of infrastructure that facilitates access to Exchange Online mailboxes that is performing below the expected service threshold. We're working to reroute connections to alternate infrastructure to remediate the impact.
Scope of impact: This issue may potentially affect some users in North America attempting to access their Exchange Online mailbox through the affected connection methods.
Start time: Thursday, October 24, 2024, at 1:00 AM UTC
Root cause: A portion of infrastructure that facilitates access to Exchange Online mailboxes is performing below the expected service threshold.
Next update by: Thursday, October 24, 2024, at 4:00 AM UTC
|
|
Time: | Wed Oct 23 21:56:26 2024 |
Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|
EX916505 - Users may be unable to send emails with attachments that trigger the Microsoft Purview Data Loss Prevention (DLP) policy
Status: | serviceRestored |
Start Time: | Sat Oct 12 02:30:00 2024 |
End Time: | Wed Oct 23 13:30:00 2024 |
Service: | Exchange Online |
Feature Group: | Networking Issues |
Classification: | advisory |
Last Updated: | Wed Oct 23 17:27:50 2024 |
Root Cause: | A recent service update which intended to improve our Microsoft Purview Data Loss Prevention introduced an impacting code regression. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 23 17:27:50 2024 |
Description: | Title: Users may be unable to send emails with attachments that trigger the Microsoft Purview Data Loss Prevention (DLP) policy
User impact: Users may have been unable to send emails with attachments that triggered the DLP policy via Outlook on the web.
More info: Affected messages were held in the 'drafts' folder.
Final status: Following our change reversion processes, our verifications with affected users has confirmed that impact has been remediated.
Scope of impact: Impact was specific to users sending email messages from Outlook on the web that included attachments that triggered the DLP policy.
Start time: Saturday, October 12, 2024, at 6:30 AM UTC
End time: Wednesday, October 23, 2024, at 5:30 PM UTC
Root cause: A recent service update which intended to improve our Microsoft Purview Data Loss Prevention introduced an impacting code regression.
Next steps:
- We're further analyzing the offending service update along with the introduced code regression to help us isolate similar problems during our pre-deployment testing and validation processes.
This is the final update for the event.
|
|
Time: | Wed Oct 23 12:19:39 2024 |
Description: | Title: Users may be unable to send emails with attachments that trigger the Microsoft Purview Data Loss Prevention (DLP) policy
User impact: Users may be unable to send emails with attachments that trigger the DLP policy via Outlook on the web.
More info: Affected messages are held in the 'drafts' folder.
Current status: We're reverting the impacting update and are monitoring as it progresses. We expect this process to complete by the next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, October 14, 2024, at 6:30 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression, which is resulting in impact.
Next update by: Wednesday, October 23, 2024, at 9:30 PM UTC
|
|
Time: | Wed Oct 23 08:35:15 2024 |
Description: | Title: Users may be unable to send emails with attachments that trigger the Microsoft Purview Data Loss Prevention (DLP) policy
User impact: Users may be unable to send emails with attachments that trigger the DLP policy via Outlook on the web.
Current status: We've determined that a recent standard service update inadvertently contains a code regression, which is resulting in impact. We've disabled the offending update and are reverting the change to remediate impact.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure.
Start time: Monday, October 14, 2024, at 6:30 AM UTC
Root cause: A recent standard service update inadvertently contains a code regression, which is resulting in impact.
Next update by: Wednesday, October 23, 2024, at 5:00 PM UTC
|
|
Time: | Wed Oct 23 07:58:33 2024 |
Description: | Title: Users cannot send email messages with attachments that trigger the Microsoft Purview Data Loss Prevention (DLP) policy
User impact: Users are unable to send email messages with attachments that trigger the DLP policy via Outlook on the web.
More info: As a workaround, users who have access may be able to send email messages with attachments that trigger the DLP policy via the Outlook desktop client.
Current status: We're proceeding with our investigation into the HTTP Archive format (HAR) network trace logs, in addition to diagnostic data to isolate the root cause and develop a mitigation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to send email messages with attachments that trigger DLP policy via Outlook on the web are impacted.
Next update by: Wednesday, October 23, 2024, at 2:00 PM UTC
|
|
Time: | Wed Oct 23 05:42:52 2024 |
Description: | Title: Users cannot send email messages with attachments that trigger the Microsoft Purview Data Loss Prevention (DLP) policy
User impact: Users are unable to send email messages with attachments that trigger the DLP policy via Outlook on the web.
More info: As a workaround, users may be able to send email messages with attachments that trigger the DLP policy via Outlook desktop client.
Current status: We're continuing to support provided information, specifically the HTTP Archive format (HAR) network trace logs provided by your representatives, to isolate the root cause and formulate a mitigation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to send email messages with attachments that trigger DLP policy via Outlook on the web are impacted.
Next update by: Wednesday, October 23, 2024, at 12:00 PM UTC
|
|
Time: | Wed Oct 23 03:56:27 2024 |
Description: | Title: Users cannot send email messages with attachments that trigger the Microsoft Purview Data Loss Prevention (DLP) policy
User impact: Users are unable to send email messages with attachments that trigger the DLP policy via Outlook on the web.
Current status: We're reviewing support provided information to determine our next troubleshooting steps.
Scope of impact: Your organization is affected by this event, and some users attempting to send email messages with attachments that trigger DLP policy via Outlook on the web are impacted.
Next update by: Wednesday, October 23, 2024, at 10:00 AM UTC
|
|
EX916901 - Users may encounter intermittent delays or timeouts when accessing Exchange Online using any connection method
Status: | serviceRestored |
Start Time: | Wed Oct 23 14:38:00 2024 |
End Time: | Wed Oct 23 14:42:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | advisory |
Last Updated: | Wed Oct 23 16:02:31 2024 |
Root Cause: | A portion of mailbox hosting infrastructure wasn't performing as efficiently as expected, resulted in impact. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 23 15:47:25 2024 |
Description: | Title: Users may encounter intermittent delays or timeouts when accessing Exchange Online using any connection method
User impact: Users may have encountered intermittent delays or timeouts when accessing Exchange Online using any connection method.
Final status: We've monitored the environment and validated this issue has been remediated with service telemetry.
Scope of impact: Any user hosted on the impacted infrastructure in North America may have been intermittently affected.
Start time: Wednesday, October 23, 2024, at 6:38 PM UTC
End time: Wednesday, October 23, 2024, at 6:42 PM UTC
Root cause: A portion of mailbox hosting infrastructure wasn't performing as efficiently as expected, resulted in impact.
Next steps:
- We're continuing our analysis of service telemetry to better identify and prevent similar impact in the future.
This is the final update for this event.
|
|
Time: | Wed Oct 23 15:25:25 2024 |
Description: | Title: Users may encounter intermittent delays or timeouts when accessing Exchange Online using any connection method
User impact: Users may encounter intermittent delays or timeouts when accessing Exchange Online using any connection method.
Current status: Our monitoring has identified that a portion of mailbox hosting infrastructure wasn't performing as efficiently as expected, resulting in impact. Our automated recovery services restarted the affected servers, restoring access. We're continuing to monitor the environment to validate remediation.
Scope of impact: Any user hosted on the impacted infrastructure in North America may be intermittently affected.
Start time: Wednesday, October 23, 2024, at 6:38 PM UTC
Root cause: A portion of mailbox hosting infrastructure wasn't performing as efficiently as expected, resulting in impact.
Next update by: Wednesday, October 23, 2024, at 8:30 PM UTC
|
|
Time: | Wed Oct 23 14:57:38 2024 |
Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|
TM910823 - Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app
Status: | serviceRestored |
Start Time: | Fri Sep 20 05:51:00 2024 |
End Time: | Tue Oct 22 16:00:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Wed Oct 23 13:30:16 2024 |
Root Cause: | An update to an Apple Intelligence component in iOS version 18.1 introduced a database configuration which was incompatible with the previous Microsoft Teams app and caused users to see incorrect names or profile pictures. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 23 13:02:48 2024 |
Description: | Title: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app
User impact: Users may have seen incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures were incorrect, the names and pictures were from users within your organization.
Impact was specific to devices that have Apple Intelligence with encryption enabled, and who are on the latest iOS version 18.1.
While we focused on remediation, some users may have been able to avoid impact by disabling Apple Intelligence for affected devices.
Final status: We've verified that the aforementioned fix is available in the App Store and users should check to see if they're on version 6.19.2 as this is the version that remediates impact. If impact persists after updating the app, users may have corrupted Microsoft Teams data and should delete their app. then reinstall version 6.19.2 from the App Store to resolve this issue.
Scope of impact: Any user who attempted to view chats and user profiles in the Microsoft Teams version 18.1 app, and who had Apple Intelligence with Encryptions enabled may have been impacted.
Start time: Friday, September 13, 2024, at 9:26 AM UTC
End time: Tuesday, October 22, 2024, at 8:00 PM UTC
Root cause: An update to an Apple Intelligence component in iOS version 18.1 introduced a database configuration which was incompatible with the previous Microsoft Teams app and caused users to see incorrect names or profile pictures.
Next steps:
- We're reviewing the previous version of the Microsoft Teams iOS app to determine why it was incompatible with the recent iOS update, so we can prevent similar impact from occurring in the future.
This is the final update for the event.
|
|
Time: | Tue Oct 22 17:15:43 2024 |
Description: | Title: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app
User impact: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Impact is specific to devices that have Apple Intelligence with encryption enabled, and who are on the latest iOS version 18.1.
While we're focused on remediation, some users may be able to avoid impact by disabling Apple Intelligence for affected devices.
Current status: We’ve confirmed that our fix to address this issue is available for download from the App Store. Affected users will need to manually download the fixed version of Microsoft Teams from the App Store. Users without corrupt Microsoft Teams data should experience impact resolution by manually downloading the fix. Affected users with corrupted Microsoft Teams data may need to delete the Microsoft Teams app and then reinstall it from the App Store to resolve this issue. We’re continuing to monitor this issue to ensure the fix is operating as expected.
Scope of impact: Any user attempting to view chats and user profiles in the Microsoft Teams iOS version 18.1 app, and who has Apple Intelligence with Encryptions enabled may be impacted.
Start time: Friday, September 20, 2024, at 9:51 AM UTC
Root cause: An update to an Apple Intelligence component has produced an impacting database configuration issue which may cause users to see incorrect names or profile pictures when using the Microsoft Teams iOS app.
Next update by: Wednesday, October 23, 2024, at 6:30 PM UTC
|
|
Time: | Tue Oct 22 13:27:01 2024 |
Description: | Title: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app
User impact: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Impact is specific to devices that have Apple Intelligence with encryption enabled, and who are on the latest iOS version 18.1.
While we're focused on remediation, some users may be able to avoid impact by disabling Apple Intelligence for affected devices.
Current status: After collecting updated verbose logging data, we've isolated a recent service update to an Apple Intelligence component which is causing incorrect names and profile pictures to be listed in chats when users are on the Microsoft Teams iOS app. We've disabled the recent service update and we're deploying a fix which is expected to remediate the impact.
Scope of impact: Any user attempting to view chats and user profiles in the Microsoft Teams iOS version 18.1 app, and who has Apple Intelligence with Encryptions enabled may be impacted.
Start time: Friday, September 20, 2024, at 9:51 AM UTC
Root cause: An update to an Apple Intelligence component has produced an impacting database configuration issue which may cause users to see incorrect names or profile pictures when using the Microsoft Teams iOS app.
Next update by: Wednesday, October 23, 2024, at 6:30 PM UTC
|
|
Time: | Mon Oct 21 13:32:32 2024 |
Description: | Title: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app
User impact: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Impact is specific to devices that have Apple Intelligence with encryption enabled, and who are on the latest iOS version 18.1.
While we're focused on remediation, some users may be able to avoid impact by disabling Apple Intelligence for affected devices.
Current status: Our analysis of the relevant service logging data has been inconclusive. We're creating a patch that will allow us to detect this issue when it occurs and gather logging data about the event to provide us more details regarding the root cause of impact that may inform our next steps.
Scope of impact: Any user attempting to view chats and user profiles in the Microsoft Teams iOS version 18.1 app, and who has Apple Intelligence with Encryptions enabled may be impacted.
Next update by: Tuesday, October 22, 2024, at 6:30 PM UTC
|
|
Time: | Fri Oct 18 20:33:03 2024 |
Description: | Title: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app
User impact: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Impact is specific to devices that have Apple Intelligence with encryption enabled, and who are on the latest iOS version 18.1.
While we're focused on remediation, some users may be able to avoid impact by disabling Apple Intelligence for affected devices.
Current status: We're continuing to test potential solutions to address the impact. In parallel, we're proceeding with additional analysis of relevant service logging to gain further insight into the underlying issue and inform our next steps.
Scope of impact: Any user attempting to view chats and user profiles in the Microsoft Teams iOS version 18.1 app, and who has Apple Intelligence with Encryptions enabled may be impacted.
Next update by: Monday, October 21, 2024, at 6:00 PM UTC
|
|
Time: | Fri Oct 18 17:59:34 2024 |
Description: | Title: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app
User impact: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Impact is specific to devices that have Apple Intelligence with encryption enabled, and who are on the latest iOS version 18.1.
Current status: We’re continuing to test potential mitigations and working with our third-party partners to isolate the origin of this issue and formulate a plan for impact remediation.
Scope of impact: Any user attempting to view chats and user profiles in the Microsoft Teams iOS version 18.1 app, and who has Apple Intelligence with Encryptions enabled may be impacted.
Next update by: Saturday, October 19, 2024, at 2:00 AM UTC
|
|
Time: | Fri Oct 18 13:29:26 2024 |
Description: | Title: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app
User impact: Users may see incorrect names and profile pictures listed in chats when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Impact is specific to devices that have Apple Intelligence with encryption enabled, and who are on the latest iOS version 18.1.
Current status: With additional validation, we've identified that our previous discussed code fix won’t address the issue as initially anticipated. Instead, we suspect the underlying issue is with the latest iOS version 18.1 and devices that have Apple intelligence with Encryptions enabled and we're working alongside Apple to further isolate the root cause of the impact.
Scope of impact: Any user attempting to view chats and user profiles in the Microsoft Teams iOS version 18.1 app, and who has Apple Intelligence with Encryptions enabled may be impacted.
Next update by: Friday, October 18, 2024, at 10:00 PM UTC
|
|
Time: | Thu Oct 17 14:05:58 2024 |
Description: | Title: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app
User impact: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Current status: We've validated internally that our code fix remediates the impact, and we're preparing it for deployment to the iOS app store to allow users to manually resolve the issue. In parallel, we're continuing to investigate the root cause of impact.
Scope of impact: Your organization is affected by this event, and any user attempting to view chats and user profiles in the Microsoft Teams iOS app is impacted.
Next update by: Friday, October 18, 2024, at 6:30 PM UTC
|
|
Time: | Wed Oct 16 18:42:10 2024 |
Description: | Title: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app
User impact: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Current status: The development of our solution is continuing to progress and we're integrating our fix for validation and testing deployments. As we continue our analysis into the root cause for the isolated error, we're determining if a targeted deployment is available as a more expedient option for remediating the impact.
Scope of impact: Your organization is affected by this event, and any user attempting to view chats and user profiles in the Microsoft Teams iOS app is impacted.
Next update by: Thursday, October 17, 2024, at 7:00 PM UTC
|
|
Time: | Tue Oct 15 18:44:28 2024 |
Description: | Title: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app
User impact: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Current status: We've reproduced the issue in our internal testing environment, and our review of the logs captured from this reproduction has identified an error occurring within the database responsible for delivering profile names and pictures that's potentially leading to impact. While our investigation to identify the root cause of this error is ongoing, we've additionally begun development of a fix to resolve the error and potentially remediate the issue. When this fix is complete, we'll validate it for efficacy before beginning deployment to the impacted service environment.
Scope of impact: Your organization is affected by this event, and any user attempting to view chats and user profiles in the Microsoft Teams iOS app is impacted.
Next update by: Thursday, October 17, 2024, at 12:00 AM UTC
|
|
Time: | Mon Oct 14 19:23:27 2024 |
Description: | Title: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app
User impact: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Current status: We're continuing to review the profile settings and relevant code flows for a subset of affected users to gain further insight into the underlying root cause. In parallel, we're working to test some configuration changes that may assist us in remediating the impact.
Scope of impact: Your organization is affected by this event, and any user attempting to view chats and user profiles in the Microsoft Teams iOS app is impacted.
Next update by: Wednesday, October 16, 2024, at 12:00 AM UTC
|
|
Time: | Mon Oct 14 15:11:15 2024 |
Description: | Title: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app
User impact: Users see incorrect names and profile pictures listed in chats and user profiles when using the Microsoft Teams iOS app.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
Current status: We're reviewing the profile settings for a subset of affected users to isolate the root cause and determine the next steps to remediate the impact.
Scope of impact: Your organization is affected by this event, and any user attempting to view chats and user profiles in the Microsoft Teams iOS app is impacted.
Next update by: Tuesday, October 15, 2024, at 1:00 AM UTC
|
|
Time: | Mon Oct 14 14:57:43 2024 |
Description: | Title: Users see incorrect names and profile pictures listed in Microsoft Teams chats and user profiles
User impact: Users see incorrect names and profile pictures listed in Microsoft Teams chats and user profiles.
More info: While profile names and profile pictures are incorrect, the names and pictures are from users within your organization.
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.
|
|
EX916349 - Some users may see intermittent delays or be unable to access Exchange Online through certain connection methods
Status: | serviceRestored |
Start Time: | Tue Oct 22 18:40:00 2024 |
End Time: | Wed Oct 23 00:45:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | advisory |
Last Updated: | Wed Oct 23 01:20:00 2024 |
Root Cause: | A portion of infrastructure responsible for reliable access to the Exchange Online service wasn't processing certain types of requests as expected, resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 23 01:20:00 2024 |
Description: | Title: Some users may see intermittent delays or be unable to access Exchange Online through certain connection methods
User impact: Users may have seen intermittent delays or been unable to access Exchange Online through certain connection methods.
More info: Impact was specific to users attempting to access Exchange Online through Outlook on the web or connection methods reliant on Representational State Transfer (REST).
Final status: We've successfully rerouted the affected requests to alternate healthy infrastructure and confirmed through an additional period of monitoring that impact was successfully remediated.
Scope of impact: Users serviced by the affected portion of infrastructure attempting to access Exchange Online may have been impacted.
Start time: Tuesday, October 22, 2024, at 10:40 PM UTC
End time: Wednesday, October 23, 2024, at 4:45 AM UTC
Root cause: A portion of infrastructure responsible for reliable access to the Exchange Online service wasn't processing certain types of requests as expected, 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 to better prevent similar impact in the future.
This is the final update for the event.
|
|
Time: | Wed Oct 23 00:16:50 2024 |
Description: | Title: Some users may see intermittent delays or be unable to access Exchange Online through certain connection methods
User impact: Users may see intermittent delays or be unable to access Exchange Online through certain connection methods.
More info: Impact is specific to users attempting to access Exchange Online through Outlook on the web or connection methods reliant on Representational State Transfer (REST).
Current status: We're continuing to work towards manually redirecting the affected requests to alternate healthy infrastructure. In parallel, we're proceeding with further analysis to gain further insight into the underlying source of impact and identify ways to more effectively address the issue.
Scope of impact: Users serviced by the affected portion of infrastructure attempting to access Exchange Online may be impacted.
Start time: Tuesday, October 22, 2024, at 10:40 PM UTC
Root cause: A portion of infrastructure responsible for reliable access to the Exchange Online service isn't processing certain types of requests as expected, resulting in impact.
Next update by: Wednesday, October 23, 2024, at 6:30 AM UTC
|
|
Time: | Tue Oct 22 23:06:05 2024 |
Description: | Title: Some users may see intermittent delays or be unable to access Exchange Online through certain connection methods
User impact: Users may see intermittent delays or be unable to access Exchange Online through certain connection methods.
More info: Impact is specific to users attempting to access Exchange Online through Outlook on the web or connection methods reliant on Representational State Transfer (REST.)
Current status: We've identified that a portion of infrastructure responsible for reliable access to the Exchange Online service isn't processing certain types of requests as expected, resulting in impact. We're working to manually redirect the affected requests to alternate healthy infrastructure to resolve the issue, and anticipate this may be complete by the time of our next scheduled update.
Scope of impact: Users serviced by the affected portion of infrastructure attempting to access Exchange Online may be impacted.
Start time: Tuesday, October 22, 2024, at 10:40 PM UTC
Root cause: A portion of infrastructure responsible for reliable access to the Exchange Online service isn't processing certain types of requests as expected, resulting in impact.
Next update by: Wednesday, October 23, 2024, at 4:30 AM UTC
|
|
Time: | Tue Oct 22 22:47:49 2024 |
Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|
EX915982 - Some admins may be unable to access the Exchange admin center (EAC) portal intermittently
Status: | serviceRestored |
Start Time: | Mon Oct 21 20:04:00 2024 |
End Time: | Tue Oct 22 10:50:00 2024 |
Service: | Exchange Online |
Feature Group: | Management and Provisioning |
Classification: | advisory |
Last Updated: | Tue Oct 22 11:55:40 2024 |
Root Cause: | A recent feature update contained an authentication issue that was intermittently preventing admins from accessing the EAC portal. |
Next Update: | N/A |
|
Details
Time: | Tue Oct 22 11:55:40 2024 |
Description: | Title: Some admins may be unable to access the Exchange admin center (EAC) portal intermittently
User impact: Admins may have been unable to access the EAC portal intermittently.
More info: Specifically, users may have seen an authentication loop when accessing the https://admin.exchange.microsoft.com/ URL.
Final status: We've identified that a recent feature update contained an authentication issue that was intermittently preventing admins from accessing the EAC portal. We've disabled this feature update and confirmed via internal monitoring that impact is remediated.
Scope of impact: Impact was specific to some admins attempting to access the EAC portal.
Start time: Tuesday, October 22, 2024, at 12:04 AM UTC
End time: Tuesday, October 22, 2024, at 2:50 PM UTC
Root cause: A recent feature update contained an authentication issue that was intermittently preventing admins from accessing the EAC portal.
Next steps:
- We're reviewing and improving our feature update validation procedure to prevent similar authentication issues from causing impact in the future.
This is the final update for the event.
|
|
Time: | Tue Oct 22 10:24:58 2024 |
Description: | Title: Some admins may be unable to access the Exchange admin center (EAC) portal
User impact: Admins may be unable to access the EAC portal.
More info: Specifically, users may see an authentication loop when using the https://admin.exchange.microsoft.com/ URL.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Impact is specific to some admins who are served through the affected infrastructure.
Next update by: Tuesday, October 22, 2024, at 4:30 PM UTC
|
|
EX915918 - Users may have been unable to access their mailbox via multiple Exchange Online connection methods
Status: | serviceRestored |
Start Time: | Tue Oct 22 06:15:00 2024 |
End Time: | Tue Oct 22 09:35:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | advisory |
Last Updated: | Tue Oct 22 10:10:45 2024 |
Root Cause: | A subsection of service infrastructure, that facilitates Exchange Online access requests, fell below our manageable service performance thresholds, which resulted in impact. |
Next Update: | N/A |
|
Details
Time: | Tue Oct 22 10:05:40 2024 |
Description: | Title: Users may have been unable to access their mailbox via multiple Exchange Online connection methods
User impact: Users may have been unable to access their mailbox via multiple Exchange Online connection methods.
More info: Impacted connection methods included, but wasn't limited to:
- Outlook on the web
- Representational State Transfer (REST)
Final status: We've determined that a subsection of service infrastructure, that facilitates Exchange Online access requests, fell below our manageable service performance thresholds and resulted in impact. We’ve placed the affected infrastructure into maintenance mode and confirmed that impact has been resolved.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure, attempting to access their Exchange Online mailbox via the affected connection methods.
Start time: Tuesday, October 22, 2024, at 10:15 AM UTC
End time: Tuesday, October 22, 2024, at 1:35 PM UTC
Root cause: A subsection of service infrastructure, that facilitates Exchange Online access requests, fell below our manageable service performance thresholds, which resulted in impact.
Next steps:
- We're analyzing performance data and trends on the affected infrastructure to help prevent this problem from happening again.
This is the final update for the event.
|
|
Time: | Tue Oct 22 09:13:42 2024 |
Description: | Title: Users may be unable to access their mailbox via multiple Exchange Online connection methods
User impact: Users may be unable to access their mailbox via multiple Exchange Online connection methods.
More info: Impacted connection methods include, but aren't limited to:
- Outlook on the web
- Representational State Transfer (REST)
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure, attempting to access their Exchange Online mailbox via the affected connection methods.
Next update by: Tuesday, October 22, 2024, at 3:30 PM UTC
|
|
Time: | Tue Oct 22 08:51:02 2024 |
Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|
SP904155 - Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience
Status: | serviceRestored |
Start Time: | Thu Oct 3 11:35:59 2024 |
End Time: | Sun Oct 20 20:00:00 2024 |
Service: | SharePoint Online |
Feature Group: | SharePoint Features |
Classification: | advisory |
Last Updated: | Mon Oct 21 01:15:20 2024 |
Root Cause: | The new SharePoint Online start experience didn't honor the configurations set to disable users from creating new SharePoint Online sites. |
Next Update: | N/A |
|
Details
Time: | Mon Oct 21 01:15:20 2024 |
Description: | Title: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience
User impact: Users may have seen a button to create a new SharePoint Online site in the new SharePoint Online start experience.
More info: Users may have seen the button to create a new SharePoint Online site, despite being configured otherwise. Clicking the button didn't allow users to create sites and no other actions occurred.
Final status: The fix deployment has saturated 100 percent throughout the affected environment. Additionally, we've monitored the service infrastructure and confirmed that impact has been remediated.
Scope of impact: Any user who attempted to create a new SharePoint Online site in the new SharePoint Online start experience may have been impacted.
Start time: Tuesday, July 9, 2024, at 12:00 AM UTC
End time: Monday, October 21, 2024, at 12:00 AM UTC
Root cause: The new SharePoint Online start experience didn't honor the configurations set to disable users from creating new SharePoint Online sites.
Next steps:
- We're validating and investigating further how the new SharePoint Online start experience will honor specific configurations to prevent similar impact from occurring in future.
This is the final update for the event.
|
|
Time: | Fri Oct 18 00:03:24 2024 |
Description: | Title: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience
User impact: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience.
More info: Users may see the button to create a new SharePoint Online site, despite being configured otherwise. Clicking the button doesn't allow users to create sites and no other actions occur.
Current status: The deployment of the code fix has reached 99 percent saturation, and we're continuing to monitor to ensure completion and confirm remediation.
Scope of impact: Any user attempting to create a new SharePoint Online site in the new SharePoint Online start experience may be impacted.
Start time: Tuesday, July 9, 2024, at 12:00 AM UTC
Root cause: The new SharePoint Online start experience doesn't honor the configurations set to disable users from creating new SharePoint Online sites.
Next update by: Monday, October 21, 2024, at 7:00 AM UTC
|
|
Time: | Wed Oct 16 23:41:21 2024 |
Description: | Title: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience
User impact: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience.
More info: Users may see the button to create a new SharePoint Online site, despite being configured otherwise. Clicking the button doesn't allow users to create sites and no other actions occur.
Current status: The deployment of the code fix has almost completed. We're continuing to monitor as it progresses to provide a completion timeline and confirm impact remediation.
Scope of impact: Any user attempting to create a new SharePoint Online site in the new SharePoint Online start experience may be impacted.
Start time: Tuesday, July 9, 2024, at 12:00 AM UTC
Root cause: The new SharePoint Online start experience doesn't honor the configurations set to disable users from creating new SharePoint Online sites.
Next update by: Friday, October 18, 2024, at 7:00 AM UTC
|
|
Time: | Wed Oct 9 22:36:57 2024 |
Description: | Title: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience
User impact: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience.
More info: Users may see the button to create a new SharePoint Online site, despite being configured otherwise. Clicking the button doesn't allow users to create sites and no other actions occur.
Current status: The deployment of the code fix is ongoing, and progressing as expected. We're continuing to monitor as it progresses to better determine an estimated completion timeline.
Scope of impact: Any user attempting to create a new SharePoint Online site in the new SharePoint Online start experience may be impacted.
Start time: Tuesday, July 9, 2024, at 12:00 AM UTC
Root cause: The new SharePoint Online start experience doesn't honor the configurations set to disable users from creating new SharePoint Online sites.
Next update by: Thursday, October 17, 2024, at 7:00 AM UTC
|
|
Time: | Thu Oct 3 12:21:12 2024 |
Description: | Title: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience
User impact: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience.
More info: Users may see the button to create a new SharePoint Online site, despite being configured otherwise. Clicking the button doesn't allow users to create sites and no other actions occur.
Current status: We've determined that the User Interface (UI) for the new SharePoint Online start experience doesn't honor the configurations set to disable users from creating new SharePoint Online sites. We've developed and begun deployment of a code fix to remove the button when the feature is disabled and we'll provide a timeline for the completion of the deployment as once becomes available.
Scope of impact: Any user attempting to create a new SharePoint Online site in the new SharePoint Online start experience may be impacted.
Root cause: The new SharePoint Online start experience doesn't honor the configurations set to disable users from creating new SharePoint Online sites.
Next update by: Thursday, October 10, 2024, at 7:00 AM UTC
|
|
Time: | Thu Oct 3 12:02:45 2024 |
Description: | Title: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience
User impact: Users may see a button to create a new SharePoint Online site in the new SharePoint Online start experience.
More info: Users may see the button to create a new SharePoint Online site, despite being configured otherwise. Clicking the button doesn't allow users to create sites and no other actions occur.
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.
|
|
CP913268 - Recently created users may not get individualized results when performing Microsoft Copilot (Microsoft 365) queries
Status: | serviceRestored |
Start Time: | Tue Sep 24 14:06:00 2024 |
End Time: | Fri Oct 18 20:00:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | incident |
Last Updated: | Fri Oct 18 21:22:42 2024 |
Root Cause: | A header used to facilitate the interoperability of user creation and Copilot results generation is missing from some requests due to a recent change to a portion of Microsoft Copilot service infrastructure intended to optimize the associated process. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 18 21:19:39 2024 |
Description: | Title: Recently created users may not get individualized results when performing Microsoft Copilot (Microsoft 365) queries
User impact: Recently created users may not have received individualized results when performing Copilot queries.
Final status: After further analysis, we've determined that a header used to facilitate the interoperability of user creation and Copilot results generation is missing from some requests due to a recent change to a portion of Microsoft Copilot service infrastructure intended to optimize the associated process. We've developed and rolled out a code fix to the affected environment to disable the offending change, which we've confirmed through monitoring our service health telemetry has successfully remediated the impact.
Scope of impact: Any user created since October 6, 2024, that performed Copilot queries may have been affected.
Start time: Tuesday, September 24, 2024, at 6:06 PM UTC
End time: Saturday, October 19, 2024, at 12:00 AM UTC
Root cause: A header used to facilitate the interoperability of user creation and Copilot results generation is missing from some requests due to a recent change to a portion of Microsoft Copilot service infrastructure intended to optimize the associated process.
Next steps:
- We're looking into ways that we can reimplement the change safely to the affected service infrastructure without causing any disruption to functionalities.
This is the final service update for this event.
|
|
Time: | Fri Oct 18 17:46:54 2024 |
Description: | Title: Recently created users may not get individualized results when performing Microsoft Copilot (Microsoft 365) queries
User impact: Recently created users may not get individualized results when performing Copilot queries.
Current status: Our review of gathered telemetry and logs indicates that a header used to facilitate the interoperability of user creation and Copilot results generation is missing from some requests, which we expect may be contributing to impact. We're continuing our analysis to further isolate the underlying cause of impact.
Scope of impact: Any user created since October 6, 2024, that’s performing Copilot queries may be affected.
Next update by: Saturday, October 19, 2024, at 1:00 AM UTC
|
|
Time: | Fri Oct 18 16:21:57 2024 |
Description: | Title: Recently created users may not get individualized results when performing Microsoft Copilot (Microsoft 365) queries
User impact: Recently created users may not get individualized results when performing Copilot queries.
Current status: We've identified that a process to create user indices isn't working as expected, preventing Copilot queries from accessing the user data needed to output individualized results and resulting in impact. We're reviewing service telemetry to determine our next steps.
Scope of impact: Any user created since October 6, 2024, that’s performing Copilot queries may be affected.
Next update by: Friday, October 18, 2024, at 9:30 PM UTC
|
|
Time: | Fri Oct 18 15:56:56 2024 |
Description: | Title: Recently created users may not get individualized results when performing Microsoft Copilot (Microsoft 365) queries
User impact: Recently created users may not get individualized results when performing Copilot queries.
We're investigating a potential issue with Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
TM907925 - Users may be unable to access the Question and Answers (Q&A) feature within Microsoft Teams meetings
Status: | serviceRestored |
Start Time: | Thu Oct 3 12:07:00 2024 |
End Time: | Fri Oct 18 15:05:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Fri Oct 18 19:51:23 2024 |
Root Cause: | An update to a portion of code that facilitates the Q&A feature contained an error in the way the meeting IDs were handled, resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 18 18:02:53 2024 |
Description: | Title: Users may be unable to access the Question and Answers (Q&A) feature within Microsoft Teams meetings
User impact: Users may have been unable to access the Q&A feature within meetings that were started from channels.
More info: The problem occurred within the Microsoft Teams desktop and web clients and happened during meetings that were started from channels as well as live events. Affected users were seeing the following message: "Q&A was not set up for this meeting".
Final status: The deployment of the fix has completed and we've confirmed through monitoring service telemetry that impact has been remediated.
Scope of impact: Any user opening the Q&A panel within Microsoft Teams meetings and channels may have been impacted.
Start time: Thursday, October 3, 2024, at 4:07 PM UTC
End time: Friday, October 18, 2024, at 7:15 PM UTC
Root cause: An update to a portion of code that facilitates the Q&A feature contained an error in the way the meeting IDs were handled, resulting in impact.
Next steps:
- We're reviewing our feature update testing and validation methods to better identify the potential for impact to Microsoft Teams meeting features prior to deployment to prevent similar impact in the future, and to improve our pre-deployment update testing processes.
This is the final update for the event.
|
|
Time: | Fri Oct 18 13:12:22 2024 |
Description: | Title: Users may be unable to access the Question and Answers (Q&A) feature within Microsoft Teams meetings
User impact: Users may be unable to access the Q&A feature within meetings started from channels.
More info: The problem occurs within the Microsoft Teams desktop and web clients and happens during meetings started from channels as well as live events. Affected users are seeing the following message: "Q&A was not set up for this meeting".
Current status: We're monitoring the deployment of the fix which we anticipate will complete by our next scheduled update.
Scope of impact: Any user opening the Q&A panel within Microsoft Teams meetings and channels may be impacted.
Start time: Friday, October 4, 2024, at 12:00 PM UTC
Estimated time to resolve: We expect the deployment to complete and remediate the issue on Friday, October 18, 2024, at 11:30 PM UTC
Root cause: An update to a portion of code that facilitates the Q&A feature contains an error in the way the meeting IDs are handled, resulting in impact.
Next update by: Friday, October 18, 2024, at 11:30 PM UTC
|
|
Time: | Wed Oct 16 12:13:32 2024 |
Description: | Title: Users may be unable to access the Question and Answers (Q&A) feature within Microsoft Teams meetings
User impact: Users may be unable to access the Q&A feature within meetings started from channels.
More info: The problem occurs within the Microsoft Teams desktop and web clients and happens during meetings started from channels as well as live events. Affected users are seeing the following message: "Q&A was not set up for this meeting".
Current status: We've completed the development and validation of the fix and initiated its deployment. We expect the deployment to complete and remediate the issue on Friday, October 18, 2024.
Scope of impact: Any user opening the Q&A panel within Microsoft Teams meetings and channels may be impacted.
Start time: Friday, October 4, 2024, at 12:00 PM UTC
Estimated time to resolve: We expect the deployment to complete and remediate the issue on Friday, October 18, 2024.
Root cause: An update to a portion of code that facilitates the Q&A feature contains an error in the way the meeting IDs are handled, resulting in impact.
Next update by: Friday, October 18, 2024, at 7:00 PM UTC
|
|
Time: | Fri Oct 11 13:54:43 2024 |
Description: | Title: Users may be unable to access the Question and Answers (Q&A) feature within Microsoft Teams meetings
User impact: Users may be unable to access the Q&A feature within meetings started from channels.
More info: The problem occurs within the Microsoft Teams desktop and web clients and happens during meetings started from channels as well as live events. Affected users are seeing the following message: "Q&A was not set up for this meeting".
Current status: We're continuing our development of the fix and expect to have a deployment timeline by the next scheduled update.
Scope of impact: Any user opening the Q&A panel within Microsoft Teams meetings and channels may be impacted.
Start time: Friday, October 4, 2024, at 12:00 PM UTC
Root cause: An update to a portion of code that facilitates the Q&A feature contains an error in the way the meeting IDs are handled, resulting in impact.
Next update by: Friday, October 18, 2024, at 7:00 PM UTC
|
|
Time: | Thu Oct 10 17:07:10 2024 |
Description: | Title: Users may be unable to access the Question and Answers (Q&A) feature within Microsoft Teams meetings
User impact: Users may be unable to access the Q&A feature within meetings started from channels.
More info: The problem occurs within the Microsoft Teams desktop and web clients and happens during meetings started from channels as well as live events. Affected users are seeing the following message: "Q&A was not set up for this meeting".
Current status: We've confirmed that an update to a portion of code that facilitates the Q&A feature contains an error in the way the meeting IDs are handled, resulting in impact. We're in the process of developing a fix to remediate impact. We’ll provide a deployment timeline once available.
Scope of impact: Any user opening the Q&A panel within Microsoft Teams meetings and channels may be impacted.
Root cause: An update to a portion of code that facilitates the Q&A feature contains an error in the way the meeting IDs are handled, resulting in impact.
Next update by: Friday, October 11, 2024, at 7:00 PM UTC
|
|
Time: | Thu Oct 10 15:52:41 2024 |
Description: | Title: Users may be unable to access the Question and Answers (Q&A) feature within Microsoft Teams meetings
User impact: Users may be unable to access the Q&A feature within meetings started from channels.
More info: The problem occurs within the Microsoft Teams desktop and web clients and happens during meetings started from channels as well as live events. Affected users are seeing the following message: "Q&A was not set up for this meeting".
Current status: We've successfully reproduced the issue internally and our gathered logs indicate that the meeting ID isn't being communicated to the Teams clients as expected. We're continuing our analysis of the ID while looking to determine if any recent service updates may be contributing to impact.
Scope of impact: Any user opening the Q&A panel within Microsoft Teams meetings and channels may be impacted.
Next update by: Thursday, October 10, 2024, at 9:30 PM UTC
|
|
Time: | Thu Oct 10 14:53:15 2024 |
Description: | Title: Users may be unable to access the Question and Answers (Q&A) feature within Microsoft Teams meetings
User impact: Users may be unable to access the Q&A feature within meetings started from channels.
More info: The problem occurs within the Microsoft Teams desktop and web clients and happens during meetings started from channels as well as live events. Affected users are seeing the following message: "Q&A was not set up for this meeting".
Current status: We're working to reproduce the issue internally and gather additional diagnostic data to progress the investigation and determine our next steps.
Scope of impact: Any user opening the Q&A panel within Microsoft Teams meetings and channels may be impacted.
Next update by: Thursday, October 10, 2024, at 8:00 PM UTC
|
|
Time: | Thu Oct 10 14:25:46 2024 |
Description: | Title: Users may be unable to access the Question and Answers (Q&A) feature within Microsoft Teams meetings
User impact: Users may be unable to access the Q&A feature within meetings started from channels.
More info: The problem occurs within the Microsoft Teams desktop and web clients and happens during meetings started from channels as well as live events. Affected users are seeing the following message: "Q&A was not set up for this 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
|
|
OO912415 - Some users may have been unable to filter using Excel on the web
Status: | serviceRestored |
Start Time: | Wed Oct 16 05:00:00 2024 |
End Time: | Thu Oct 17 03:30:00 2024 |
Service: | Microsoft 365 for the web |
Feature Group: | Excel Online |
Classification: | advisory |
Last Updated: | Thu Oct 17 09:42:36 2024 |
Root Cause: | A recent standard service update contained a change, intended to improve filter drop down list result fetching, which inadvertently caused a code regression and no filtering results to be shown. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 17 08:59:47 2024 |
Description: | Title: Some users may have been unable to filter using Excel on the web
User impact: Users may have been unable to filter using Excel on the web.
More info: Users may have seen no results and a continuous loading loop in the filter drop down list.
Final status: We've identified that a recent standard service update contained a change, intended to improve filter drop down list result fetching, which inadvertently caused a code regression and no filtering results to be shown. We've reverted the service update and received confirmation from affected users that impact is no longer occurring.
Scope of impact: Impact was specific to some users, who were served through the affected infrastructure, attempting to filter using Excel on the web.
Start time: Wednesday, October 16, 2024, at 9:00 AM UTC
End time: Thursday, October 17, 2024, at 7:30 AM UTC
Root cause: A recent standard service update contained a change, intended to improve filter drop down list result fetching, which inadvertently caused a code regression and no filtering results to be shown.
Next steps:
- We're reviewing our recent standard service update procedures to help prevent similar impact from happening again.
This is the final update for the event.
|
|
EX911789 - Some admins may have been unable to access the Exchange admin center (EAC)
Status: | serviceRestored |
Start Time: | Wed Oct 16 04:50:00 2024 |
End Time: | Wed Oct 16 05:51:00 2024 |
Service: | Exchange Online |
Feature Group: | Management and Provisioning |
Classification: | advisory |
Last Updated: | Wed Oct 16 07:15:14 2024 |
Root Cause: | A network authentication component configuration update inadvertently prevented users from accessing the Exchange admin center. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 16 07:15:14 2024 |
Description: | Title: Some admins may have been unable to access the Exchange admin center (EAC)
User impact: Admins may have been unable to access the Exchange admin center.
More info: Affected admins may have been unable to access the portal, observed a degraded performance in which the Exchange admin center took a long time to load, or received the following error: "Error: undefined".
Final status: We've determined that a network authentication component configuration update inadvertently prevented users from accessing the Exchange admin center. To mitigate impact, we've corrected the configuration and confirmed after a period of monitoring service telemetry, that impact is no longer occurring.
Scope of impact: Impact was specific to some admins who are served through the affected infrastructure.
Start time: Wednesday, October 16, 2024, at 8:50 AM UTC
End time: Wednesday, October 16, 2024, at 9:51 AM UTC
Root cause: A network authentication component configuration update inadvertently prevented users from accessing the Exchange admin center.
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: | Wed Oct 16 05:34:03 2024 |
Description: | Title: Some admins may be unable to access the Exchange Admin Center
User impact: Admins may be unable to access the Exchange Admin Center.
More info: Affected admins may be unable to access the portal, observe a degraded performance in which the Exchange Admin Center takes a long time to load, or receive the following error: "Error: undefined".
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 admins who are served through the affected infrastructure.
Next update by: Wednesday, October 16, 2024, at 11:30 AM UTC
|
|
CP911578 - Users may be unable to create chats using Microsoft Copilot (Microsoft 365) within some Microsoft 365 apps
Status: | serviceRestored |
Start Time: | Thu Oct 10 14:00:00 2024 |
End Time: | Tue Oct 15 19:30:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | incident |
Last Updated: | Tue Oct 15 20:35:34 2024 |
Root Cause: | A recent optimization update resulted in a part of the code that the Copilot chat creation process relied upon becoming disabled, which led to impact. |
Next Update: | N/A |
|
Details
Time: | Tue Oct 15 20:35:34 2024 |
Description: | Title: Users may be unable to create chats using Microsoft Copilot (Microsoft 365) within some Microsoft 365 apps
User impact: Users may have been unable to create chats using Copilot within some Microsoft 365 apps.
More info: Users may have experienced impact within Microsoft Teams (new and classic), Outlook desktop, Outlook on the web, and the Copilot web app.
Affected users saw a greyed out 'Start a new chat' button, which prevented them from starting a chat.
Users may have been able to refresh the page to remediate impact.
Final status: We've re-enabled the portion of code responsible for the impact, and we've confirmed through testing that the issue has been successfully remediated.
Scope of impact: Any user who attempted to start a new chat within Microsoft Teams, Outlook, or the Copilot web app may have been impacted by this event.
Start time: Thursday, October 10, 2024, at 6:00 PM UTC
End time: Tuesday, October 15, 2024, at 11:30 PM UTC
Root cause: A recent optimization update resulted in a part of the code that the Copilot chat creation process relied upon becoming disabled, which led to impact.
Next steps:
- We're reviewing our optimization processes so we can better identify similar code issues during our update testing and development cycles which will help us avoid comparable impact in the future.
This is the final update for the event.
|
|
Time: | Tue Oct 15 19:39:07 2024 |
Description: | Title: Users may be unable to create chats using Microsoft Copilot (Microsoft 365) within some Microsoft 365 apps
User impact: Users may be unable to create chats using Copilot within some Microsoft 365 apps.
More info: Users may experience impact within Microsoft Teams (new and classic), Outlook desktop, Outlook on the web, and the Copilot web app.
Affected users are seeing a greyed out 'Start a new chat' button, preventing them from starting a chat.
Users may be able to refresh the page to remediate impact.
Current status: Our internal reproduction of the issue, as well as our investigation into any recent changes made to the service, has identified that a recent optimization update resulted in a part of the code that the Copilot chat creation process relies upon becoming disabled, leading to impact. We've made a change to re-enable this portion of code and we're testing to ensure this resolves the issue.
Scope of impact: Any user attempting to start a new chat within Microsoft Teams, Outlook, or the Copilot web app may be impacted by this event.
Start time: Thursday, October 10, 2024, at 6:00 PM UTC
Root cause: A recent optimization update resulted in a part of the code that the Copilot chat creation process relies upon becoming disabled, leading to impact.
Next update by: Wednesday, October 16, 2024, at 1:30 AM UTC
|
|
Time: | Tue Oct 15 18:29:48 2024 |
Description: | Title: Users may be unable to create chats using Microsoft Copilot (Microsoft 365) within some Microsoft 365 apps
User impact: Users may be unable to create chats using Copilot within some Microsoft 365 apps.
More info: Users may experience impact within Microsoft Teams (new and classic), Outlook desktop, Outlook on the web, and the Copilot web app.
Affected users are seeing a greyed out 'Start a new chat' button, preventing them from starting a chat.
Users may be able to refresh the page to remediate impact.
Current status: We're working to reproduce the issue internally to gather additional diagnostic information to progress the investigation and determine our next steps.
Scope of impact: Any user attempting to start a new chat within Microsoft Teams, Outlook, or the Copilot web app may be impacted by this event.
Next update by: Tuesday, October 15, 2024, at 11:30 PM UTC
|
|
Time: | Tue Oct 15 18:04:01 2024 |
Description: | Title: Users may be unable to create chats using Microsoft Copilot (Microsoft 365) within some Microsoft 365 apps
User impact: Users may be unable to create chats using Copilot within some Microsoft 365 apps.
More info: Users may see impact within Microsoft Teams, Outlook desktop, Outlook on the web, and the Copilot web app.
Affected users are seeing a greyed out 'Start a new chat' button, preventing them from starting a chat. Users may be able to refresh the page to remediate impact.
Current status: We're investigating a potential issue with Copilot and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
OD902587 - We’ve detected a rendering issue with the latest Safari browser version 18.1 accessing OneDrive for Business
Status: | serviceRestored |
Start Time: | Tue Oct 1 13:18:56 2024 |
End Time: | Tue Oct 15 16:03:03 2024 |
Service: | OneDrive for Business |
Feature Group: | OneDrive for Business |
Classification: | advisory |
Last Updated: | Tue Oct 15 16:04:21 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Tue Oct 15 16:04:21 2024 |
Description: | Title: We’ve detected a rendering issue with the latest Safari browser version 18.1 accessing OneDrive for Business
User impact: Users may not see file names or icons when accessing OneDrive for Business using Safari browser version 18.1.
Final Status: Our partner organization has released an updated Safari version which contains a fix for this impact. We recommend affected users update their Safari to Version 18.1 (20619.2.5) to remediate this issue.
This is the final update for this event.
|
|
Time: | Tue Oct 8 15:32:57 2024 |
Description: | Title: We’ve detected a rendering issue with the latest Safari browser version 18.1 accessing OneDrive for Business
User impact: Users may not see file names or icons when accessing OneDrive for Business using Safari browser version 18.1.
Current Status: We’ve worked with our partner organization who have developed an update to Safari for iOS, iPad OS, and macOS which is currently being released. Users will see relief as the update progresses.
Next Update: Tuesday, October 15, 2024, at 9:00 PM UTC
|
|
Time: | Tue Oct 1 13:21:59 2024 |
Description: | Title: We’ve detected a rendering issue with the latest Safari browser version 18.1 accessing OneDrive for Business
User impact: Users may not see file names or icons when accessing OneDrive for Business using Safari browser version 18.1.
Current Status: We’ve received reports of users encountering issues with the OneDrive for Business experience on iOS and macOS devices using Safari browser version 18.1. We’re working with our partner organizations to develop a fix for this issue. We recommend affected users access OneDrive for Business using an alternate browser such as Microsoft Edge, Mozilla Firefox or Chrome on their device or the OneDrive for Business apps for iOS, iPadOS and macOS.
Next Update by: Tuesday, October 8, 2024, at 9:00 PM UTC
|
|
SP902588 - We’ve detected a rendering issue with the latest Safari browser version 18.1 viewing SharePoint Online lists
Status: | serviceRestored |
Start Time: | Tue Oct 1 13:19:11 2024 |
End Time: | Tue Oct 15 16:03:17 2024 |
Service: | SharePoint Online |
Feature Group: | SharePoint Features |
Classification: | advisory |
Last Updated: | Tue Oct 15 16:04:18 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Tue Oct 15 16:04:18 2024 |
Description: | Title: We’ve detected a rendering issue with the latest Safari browser version 18.1 viewing SharePoint Online lists
User impact: Users may not see file names or icons when viewing SharePoint Online lists using Safari browser version 18.1.
Final Status: Our partner organization has released an updated Safari version which contains a fix for this impact. We recommend affected users update their Safari to Version 18.1 (20619.2.5) to remediate this issue.
This is the final update for this event.
|
|
Time: | Tue Oct 8 15:32:59 2024 |
Description: | Title: We’ve detected a rendering issue with the latest Safari browser version 18.1 viewing SharePoint Online lists
User impact: Users may not see file names or icons when viewing SharePoint Online lists using Safari browser version 18.1.
Current Status: We’ve worked with our partner organization who have developed an update to Safari for iOS, iPad OS, and macOS which is currently being released. Users will see relief as the update progresses.
Next Update: Tuesday, October 15, 2024, at 9:00 PM UTC
|
|
Time: | Tue Oct 1 13:22:02 2024 |
Description: | Title: We’ve detected a rendering issue with the latest Safari browser version 18.1 viewing SharePoint Online lists
User impact: Users may not see file names or icons when viewing SharePoint Online lists using Safari browser version 18.
More Information: Lists in Microsoft Teams may also be affected by this event.
Current Status: We’ve received reports of users encountering issues with the SharePoint Online experience on iOS and macOS devices using Safari browser version 18. We’re working with our partner organizations to develop a fix for this issue. We recommend affected users access SharePoint Online using an alternate browser such as Microsoft Edge, Mozilla Firefox or Chrome on their device or the SharePoint Online and Microsoft Teams apps for iOS, iPadOS and macOS.
Next Update by: Tuesday, October 8, 2024, at 9:00 PM UTC
|
|
TM911266 - Users' recordings of Townhall meetings might've not contained all video feeds of spotlighted participants
Status: | serviceRestored |
Start Time: | Thu Oct 3 00:42:00 2024 |
End Time: | Wed Oct 9 14:27:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Tue Oct 15 07:20:04 2024 |
Root Cause: | A standard service update to the Call Recorder service, intended to introduce a new feature, inadvertently resulted in impact due to a dependent service misconfiguration. |
Next Update: | N/A |
|
Details
Time: | Tue Oct 15 07:04:39 2024 |
Description: | Title: Users' recordings of Townhall meetings might've not contained all video feeds of spotlighted participants
User impact: Users' recordings of Townhall meetings might've not contained all video feeds of spotlighted participants.
Final status: We've determined that a standard service update to the Call Recorder service, intended to introduce a new feature, inadvertently resulted in impact due to a dependent service misconfiguration. We've repaired the configuration and confirmed impact is no longer occurring after a period of monitoring.
Scope of impact: Impact was specific to any user served through the affected infrastructure attempting to record Microsoft Teams Townhall meetings.
Start time: Thursday, October 3, 2024, at 4:42 AM UTC
End time: Wednesday, October 9, 2024, at 6:27 PM UTC
Root cause: A standard service update to the Call Recorder service, intended to introduce a new feature, inadvertently resulted in impact due to a dependent service misconfiguration.
Next steps:
- We're reviewing our standard service update procedures to help prevent similar impact from happening again.
This is the final update for the event.
|
|
TM911203 - Some users may have seen an incorrect presence state using any Microsoft Teams client
Status: | serviceRestored |
Start Time: | Tue Oct 15 04:00:00 2024 |
End Time: | Tue Oct 15 05:08:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | incident |
Last Updated: | Tue Oct 15 06:34:39 2024 |
Root Cause: | An unexpected issue occurring in a section of database infrastructure, responsible for regulating Microsoft Teams presence information, was responsible for causing impact. |
Next Update: | N/A |
|
Details
Time: | Tue Oct 15 06:27:43 2024 |
Description: | Title: Some users may have seen an incorrect presence state using any Microsoft Teams client
User impact: Users may have seen an incorrect presence state using any Microsoft Teams client.
More info: Users may have showed as offline, status unknown, or their presence may have been outdated.
Final status: We've identified that an unexpected issue occurring in a section of database infrastructure, responsible for regulating Microsoft Teams presence information, was responsible for causing impact. We've restarted the affected infrastructure, and confirmed following a monitoring period that impact to end users has been remediated.
Scope of impact: Impact was specific to some users who were served through the affected infrastructure.
Start time: Tuesday, October 15, 2024, at 8:00 AM UTC
End time: Tuesday, October 15, 2024, at 9:08 AM UTC
Root cause: An unexpected issue occurring in a section of database infrastructure, responsible for regulating Microsoft Teams presence information, was responsible for causing impact.
Next steps:
- We're analyzing data and trends on the affected infrastructure to locate the source of the issue.
- We're reviewing our code for improved performance and potential automated recovery options, to reduce or avoid similar impact in the future.
This is the final update for the event.
|
|
Time: | Tue Oct 15 05:00:41 2024 |
Description: | Title: Some users may see an incorrect presence state using any Microsoft Teams client
User impact: Users may see an incorrect presence state using any Microsoft Teams client.
More info: Users may show as offline, status unknown, or their presence may be outdated.
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.
Next update by: Tuesday, October 15, 2024, at 11:00 AM UTC
|
|
Time: | Tue Oct 15 04:41:53 2024 |
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.
|
|
MV910662 - Users may be unable to access the Microsoft Viva Engage service
Status: | serviceRestored |
Start Time: | Mon Oct 14 09:00:00 2024 |
End Time: | Mon Oct 14 10:08:00 2024 |
Service: | Microsoft Viva |
Feature Group: | Viva Engage |
Classification: | incident |
Last Updated: | Mon Oct 14 11:25:39 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Mon Oct 14 11:25:39 2024 |
Description: | Title: Users may be unable to access the Microsoft Viva Engage service
User impact: Users may have been unable to access the Microsoft Viva Engage service.
Final status: While we were in the process of analyzing service telemetry for Viva Engage, system monitoring indicated that the service had returned to normal health. We've confirmed that the issue is no longer occurring, and we'll continue to monitor the service to ensure that the problem doesn't happen again.
Scope of impact: Impact was specific to users who were served through the affected infrastructure in North America.
Start time: Monday, October 14, 2024, at 1:00 PM UTC
End time: Monday, October 14, 2024, at 2:08 PM UTC
This is the final update for the event.
|
|
Time: | Mon Oct 14 10:23:16 2024 |
Description: | Title: Users may be unable to access the Microsoft Viva Engage service
User impact: Users may be unable to access the Microsoft Viva Engage service.
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 users who are served through the affected infrastructure in North America.
Next update by: Monday, October 14, 2024, at 4:30 PM UTC
|
|
Time: | Mon Oct 14 10:13:29 2024 |
Description: | Title: We're looking into a potential problem impacting the Microsoft Viva Engage service
User impact: We're checking for potential impact to your users.
Current status: We're investigating a potential issue with the Viva Engage service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
CP910595 - Web search in Microsoft Copilot (Microsoft 365) may have been enabled despite being disabled via cloud policy
Status: | serviceRestored |
Start Time: | Mon Oct 14 01:00:00 2024 |
End Time: | Mon Oct 14 06:35:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | advisory |
Last Updated: | Mon Oct 14 08:03:37 2024 |
Root Cause: | A preventative networking configuration change, intended to improve service traffic efficiency, inadvertently resulted in impact. |
Next Update: | N/A |
|
Details
Time: | Mon Oct 14 07:59:38 2024 |
Description: | Title: Web search in Microsoft Copilot (Microsoft 365) may have been enabled despite being disabled via cloud policy
User impact: Users' web search functionality in Copilot may have been enabled despite Optional Connected Experiences being disabled.
Final status: We've received some reports that impact associated with CP908784 reoccurred. We identified that a preventative networking configuration change, intended to improve service traffic efficiency, inadvertently resulted in impact. We've reverted the change and received feedback from affected users that impact is no longer occurring.
Scope of impact: Any user hosted within the Europe region may have had web search functionality in Copilot enabled despite Optional Connected Experiences (OCE) being disabled through cloud policy.
Start time: Monday, October 14, 2024, at 5:00 AM UTC
End time: Monday, October 14, 2024, at 10:35 AM UTC
Root cause: A preventative networking configuration change, intended to improve service traffic efficiency, inadvertently resulted in impact.
Next steps:
- We're reviewing our networking configuration change procedures to help prevent similar impact from happening again.
This is the final update for the event.
|
|
CP908270 - Admins' Copilot Readiness reports may have been delayed in the Microsoft 365 admin center
Status: | serviceRestored |
Start Time: | Thu Oct 10 20:00:00 2024 |
End Time: | Sat Oct 12 05:00:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | advisory |
Last Updated: | Sat Oct 12 09:27:16 2024 |
Root Cause: | An issue affecting our data analytics system's upstream pipeline was resulting in delays for certain reports in the Microsoft 365 admin center. |
Next Update: | N/A |
|
Details
Time: | Sat Oct 12 09:23:49 2024 |
Description: | Title: Admins' Copilot Readiness reports may have been delayed in the Microsoft 365 admin center
User impact: Admins' Copilot Readiness reports may have been delayed in the Microsoft 365 admin center.
More info: Impacted reports may have been delayed for 72 hours or more.
Final status: We've confirmed after a period of monitoring that the issue has been remediated.
Scope of impact: Admins serviced by the affected portions of infrastructure attempting to view Copilot Readiness reports in the Microsoft 365 admin center may have been impacted.
Start time: Friday, October 11, 2024, at 12:00 AM UTC
End time: Saturday, October 12, 2024, at 9:00 AM UTC
Root cause: An issue affecting our data analytics system's upstream pipeline was resulting in delays for certain reports in the Microsoft 365 admin center.
Next steps:
- We're reviewing our data analytics system's upstream procedures to better identify similar issues during our development and testing cycles.
This is the final update for the event.
|
|
Time: | Sat Oct 12 00:56:24 2024 |
Description: | Title: Admins' Copilot Readiness reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Copilot Readiness reports may be delayed in the Microsoft 365 admin center.
More info: Impacted reports may be delayed 72 hours or more.
Current status: We're continuing to work towards restoring the upstream data pipeline to a healthy state to prevent further impact. We're anticipating the issue may be resolved by the time of our next scheduled update, at which point we'll monitor the backlogged queue to confirm the remaining delays are resolved as expected.
Scope of impact: Admins serviced by the affected portions of infrastructure attempting to view Copilot Readiness reports in the Microsoft 365 admin center may be impacted.
Start time: Friday, October 11, 2024, at 12:00 AM UTC
Root cause: An issue affecting our data analytics system's upstream pipeline is resulting in delays for certain reports in the Microsoft 365 admin center.
Next update by: Saturday, October 12, 2024, at 2:00 PM UTC
|
|
Time: | Fri Oct 11 00:38:42 2024 |
Description: | Title: Admins' Copilot Readiness reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Copilot Readiness reports may be delayed in the Microsoft 365 admin center.
More info: Impacted reports may be delayed 72 hours or more.
Current status: We've determined that an issue affecting our data analytics system's upstream pipeline is resulting in delays for certain reports in the Microsoft 365 admin center. We're working to restore the affected pipeline to prevent further delays.
Scope of impact: Admins serviced by the affected portions of infrastructure attempting to view Copilot Readiness reports in the Microsoft 365 admin center may be impacted.
Start time: Friday, October 11, 2024, at 12:00 AM UTC
Root cause: An issue affecting our data analytics system's upstream pipeline is resulting in delays for certain reports in the Microsoft 365 admin center.
Next update by: Saturday, October 12, 2024, at 5:00 AM UTC
|
|
Time: | Fri Oct 11 00:24:54 2024 |
Description: | Title: Admins' Copilot Readiness reports may be delayed in the Microsoft 365 admin center
User impact: Admins' Copilot Readiness reports may be delayed in the Microsoft 365 admin center.
More info: Impacted reports may be delayed 72 hours or more.
Current status: We're investigating a potential issue with Microsoft Copilot Readiness reports and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
IT909214 - Users may be unable to check their devices into the Microsoft Intune service and may experience failures
Status: | serviceRestored |
Start Time: | Fri Oct 11 17:07:00 2024 |
End Time: | Fri Oct 11 21:32:00 2024 |
Service: | Microsoft Intune |
Feature Group: | Microsoft Intune |
Classification: | incident |
Last Updated: | Fri Oct 11 22:15:30 2024 |
Root Cause: | A recent routine update made to our Microsoft Intune service infrastructure, intended to optimize the service's functions, caused impact. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 11 22:15:30 2024 |
Description: | Title: Users may be unable to check their devices into the Microsoft Intune service and may experience failures
User impact: Users may have been unable to check their devices into the Microsoft Intune service and may have experienced failures.
More info: These failures may have also resulted in delays for admins sending new policies and actions to devices, as well as delays updating reporting and compliance data from the affected devices.
Additionally, users may have experienced the following impacted scenarios but may not have been limited to:
- Unable to enroll new devices or see the compliance state for their existing devices.
- Unable to use other Information Worker (IW) scenarios, such as seeing their devices' list or apps list.
- Unable to install or download Win32 apps.
Final status: We've identified a recent routine update made to our Microsoft Intune service infrastructure, intended to optimize the service's functions, caused impact. We've implemented a change to address the issue and confirmed with our service telemetry that impact is remediated.
Scope of impact: Users and admins serviced by the affected infrastructure who were attempting to check in their devices into the Microsoft Intune service may have been impacted.
Start time: Friday, October 11, 2024, at 9:07 PM UTC
End time: Saturday, October 12, 2024, at 1:32 AM UTC
Root cause: A recent routine update made to our Microsoft Intune service infrastructure, intended to optimize the service's functions, caused impact.
Next steps:
- We're investigating further into the impacting update to establish how it caused impact. The results of this investigation will help us improve our update processes and help establish ways to improve the service.
This is the final update for this event.
|
|
Time: | Fri Oct 11 21:11:23 2024 |
Description: | Title: Users may be unable to check their devices into the Microsoft Intune service and may experience failures
User impact: Users may be unable to check their devices into the Microsoft Intune service and may experience failures.
More info: These failures may also result in delays for admins sending new policies and actions to devices, as well as delays updating reporting and compliance data from the affected devices.
Additionally, users may be experience the following impacted scenarios but may not be limited to:
- Unable to enroll new devices or see the compliance state for their existing devices.
- Unable to use other Information Worker (IW) scenarios, such as seeing their devices' list or apps list.
- Unable to install or download Win32 apps.
Current status: We're continuing to analyze the previously mentioned logs, along with assessing any recent deployments that may be contributing to impact, so we can identify the root cause and formulate a remediation plan.
Scope of impact: Users and admins serviced by the affected infrastructure who are attempting to check in their devices into the Microsoft Intune service may be impacted.
Next update by: Saturday, October 12, 2024, at 3:30 AM UTC
|
|
Time: | Fri Oct 11 20:20:03 2024 |
Description: | Title: Users may be unable to check their devices into the Microsoft Intune service and may experience failures
User impact: Users may be unable to check their devices into the Microsoft Intune service and may experience failures.
More info: These failures may also result in delays for admins sending new policies and actions to devices, as well as delays updating reporting and compliance data from the affected devices.
Current status: We're analyzing logs from a portion of our Microsoft Intune service infrastructure that facilitates the authentication process to isolate the root cause and identify our next troubleshooting steps.
Scope of impact: Users and admins serviced by the affected infrastructure who are attempting to check in their devices into the Microsoft Intune service may be impacted.
Next update by: Saturday, October 12, 2024, at 1:30 AM UTC
|
|
Time: | Fri Oct 11 19:55:58 2024 |
Description: | Title: Users may be unable to check their devices into the Intune service and may experience failures
User impact: Users may be unable to check their devices into the Intune service and may experience failures.
More info: These failures may also result in delays for admins sending new policy and actions to devices, as well as delays updating reporting and compliance data from the affected devices.
Current status: We're investigating a potential issue in which users may experience failures checking their devices into the Intune service. We're checking for impact to your organization and we'll provide an update within 30 minutes.
|
|
TM898004 - Users may not receive subsequent notifications for urgent Microsoft Teams messages
Status: | serviceRestored |
Start Time: | Thu Jul 11 09:00:00 2024 |
End Time: | Fri Oct 11 15:55:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Fri Oct 11 16:45:19 2024 |
Root Cause: | A feature update intended to regulate the duplication mechanism for the urgent message notifications was preventing users from receiving subsequent notifications for urgent messages. |
Next Update: | Friday, October 11, 2024, at 10:00 PM UTC |
|
Details
Time: | Fri Oct 11 16:45:19 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not have received subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may have received the first-time notification for the urgent messages, but the subsequent notifications may not have been delivered as expected.
Current status: We've confirmed that the fix has completed deployment and validated remediation with service telemetry.
Scope of impact: Impact was specific to some users who are served through the affected infrastructure that expected to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
End time: Friday, October 11, 2024, at 7:55 PM UTC
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications was preventing users from receiving subsequent notifications for urgent messages.
Next steps:
- We're continuing our analysis of the impacting update to better understand the underlying cause of impact and prevent similar issues in the future.
|
|
Time: | Fri Oct 11 13:43:16 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first-time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: The deployment of our fix is ongoing and we estimate it will complete today, Friday, October 11, 2024, by 10:00 PM UTC.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
Estimated time to resolve: We estimate that the deployment will complete, resolving impact for all users, by our next update on Friday, October 11, 2024, by 10:00 PM UTC.
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Friday, October 11, 2024, at 10:00 PM UTC
|
|
Time: | Wed Oct 9 14:09:29 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first-time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: We've addressed the deployment blocker and estimate that the deployment will complete, resolving impact for all users, by our next update on Friday, October 11, 2024, at 7:30 PM UTC.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
Estimated time to resolve: We estimate that the deployment will complete, resolving impact for all users, by our next update on October 11, 2024, at 7:30 PM UTC.
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Friday, October 11, 2024, at 7:30 PM UTC
|
|
Time: | Tue Oct 8 15:06:57 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first-time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: Following the deployment of our fix to a majority of affected regions, a deployment blocker is preventing it from completing as expected. While impact for a majority of users has been resolved, we're addressing the block to the deployment and expect an updated timeline for the remediation of impact for all users will be available once our deployment has resumed.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Wednesday, October 9, 2024, at 7:30 PM UTC
|
|
Time: | Mon Oct 7 13:56:58 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first-time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: The deployment of our fix has completed to the majority of users, but is ongoing for the remaining environment where it hasn't yet saturated. At this time, most users may experience remediation from impact. We anticipate the deployment will complete, remediating impact for all users, by our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
Estimated time to resolve: We anticipate the deployment of our fix will complete, remediating impact for all users, by our next scheduled update on Tuesday, October 8, 2024 at 7:30 PM UTC.
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Tuesday, October 8, 2024, at 7:30 PM UTC
|
|
Time: | Wed Oct 2 14:16:19 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first-time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: Due to unrelated issues, the deployment of the fix was temporarily paused. We've resumed the deployment of the fix and anticipate it'll complete and remediate impact by Monday, October 8, 2024. We'll confirm the deployment of the fix remains on track in our next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Monday, October 7, 2024, at 7:00 PM UTC
|
|
Time: | Tue Oct 1 18:25:21 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first-time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: The deployment of the fix is ongoing and we're monitoring as it progresses. We expect to have a remediation timeline by the next scheduled update.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Wednesday, October 2, 2024, at 7:00 PM UTC
|
|
Time: | Tue Oct 1 11:29:59 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first-time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: We're monitoring our fix deployment as it progresses and saturates across the affected environment. Determining an estimated timeline for the fix deployment and the remediation of impact is requiring more time than originally estimated, and we'll provide our updated estimate once it's available.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Wednesday, October 2, 2024, at 12:00 AM UTC
|
|
Time: | Mon Sep 30 11:38:52 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first-time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: We've started the deployment of our solution and are monitoring as it saturates the environment to ensure that impact is remediated. We're expecting that an accurate fix deployment timeline will be available by our next scheduled updated.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Tuesday, October 1, 2024, at 5:00 PM UTC
|
|
Time: | Thu Sep 26 11:30:14 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: We've validated our fix with a subset of affected users and are preparing it for deployment to the affected environment. We anticipate the deployment will begin by our next scheduled update, at which time we'll provide a timeline for deployment completion and impact resolution.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Start time: Thursday, July 11, 2024, at 1:00 PM UTC
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Monday, September 30, 2024, at 5:00 PM UTC
|
|
Time: | Wed Sep 25 12:15:49 2024 |
Description: | Title: Users may not receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may not receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: We've contacted a subset of affected users to validate if our fix to disable the feature update has completely remediated impact before deploying it to all affected users.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure that expect to receive notifications for urgent Microsoft Teams messages.
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications is preventing users from receiving subsequent notifications for urgent messages.
Next update by: Thursday, September 26, 2024, at 5:00 PM UTC
|
|
Time: | Wed Sep 25 10:41:29 2024 |
Description: | Title: Users may be unable to receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may be unable to receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: We've identified that a feature update intended to regulate the duplication mechanism for the urgent message notifications, is unexpectedly preventing users from receiving subsequent notifications for urgent messages. We've deployed a fix to disable the feature for some of the affected users, to ensure its efficiency prior to deploying the fix to the remaining affected infrastructure.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure, expecting to receive notifications for urgent Microsoft Teams messages.
Root cause: A feature update intended to regulate the duplication mechanism for the urgent message notifications, is unexpectedly preventing users from receiving subsequent notifications for urgent messages.
Next update by: Wednesday, September 25, 2024, at 4:30 PM UTC
|
|
Time: | Wed Sep 25 09:27:00 2024 |
Description: | Title: Users may be unable to receive subsequent notifications for urgent Microsoft Teams messages
User impact: Users may be unable to receive subsequent notifications for urgent Microsoft Teams messages.
More info: Affected users may receive the first time notification for the urgent messages, but the subsequent notifications may not be delivered as expected.
Current status: We're reviewing service monitoring telemetry to isolate the source of the issue and establish a fix.
Scope of impact: Impact is specific to some users who are served through the affected infrastructure expecting to receive notifications for urgent Microsoft Teams messages.
Next update by: Wednesday, September 25, 2024, at 3:30 PM UTC
|
|
SP907551 - Some users may see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms
Status: | serviceRestored |
Start Time: | Fri Sep 27 08:00:00 2024 |
End Time: | Thu Oct 10 13:00:00 2024 |
Service: | SharePoint Online |
Feature Group: | SharePoint Features |
Classification: | advisory |
Last Updated: | Fri Oct 11 15:10:59 2024 |
Root Cause: | A recent service update intended to improve service functionality contained a code regression which was preventing users from seeing correctly aligned and sized screens for SharePoint Online and Power Apps custom forms. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 11 15:01:29 2024 |
Description: | Title: Some users may see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms
User impact: Users saw incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms.
More info: There was no impact to SharePoint Online custom forms functionality, and this was an UI-only problem. The affected forms were centered instead of right justified and have larger-than-expected sizing which results in needing to use scroll bars instead of all fields and data appearing on the screen.
Final status: We've confirmed with affected users that the issue has been successfully resolved following the deployment of our targeted solution.
Scope of impact: Some users utilizing SharePoint Online and Power Apps custom forms may have been impacted by this issue.
Start time: Friday, September 27, 2024, at 12:00 PM UTC
End time: Thursday, October 10, 2024, at 5:00 PM UTC
Root cause: A recent service update intended to improve service functionality contained a code regression which was preventing users from seeing correctly aligned and sized screens for SharePoint Online and Power Apps custom forms.
Next steps:
- We're investigating how the recent service update intended to improve service functionality contained a code regression which was preventing users from seeing correctly aligned and sized screens for SharePoint Online and Power Apps custom forms to prevent this problem from happening again.
This is the final update for the event.
|
|
Time: | Thu Oct 10 18:52:09 2024 |
Description: | Title: Some users may see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms
User impact: Users may see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms.
More info: There’s no impact to SharePoint Online custom forms functionality and this is a UI-only problem. The affected forms are centered instead of right justified and have larger-than-expected sizing which results in needing to use scroll bars instead of all fields and data appearing on the screen.
Current status: We're continuing to validate with affected users that the underlying issue has been resolved following the deployment of our targeted solution.
Scope of impact: Some users utilizing SharePoint Online and Power Apps custom forms may be impacted by this issue.
Start time: Friday, September 27, 2024, at 12:00 PM UTC
Root cause: A recent service update intending to improve service functionality contains a code regression which is preventing users from seeing correctly aligned and sized screens for SharePoint Online and Power Apps custom forms.
Next update by: Friday, October 11, 2024, at 11:00 PM UTC
|
|
Time: | Thu Oct 10 14:54:58 2024 |
Description: | Title: Some users may see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms
User impact: Users may see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms.
More info: There’s no impact to SharePoint Online custom forms functionality and this is a UI-only problem. The affected forms are centered instead of right justified and have larger-than-expected sizing which results in needing to use scroll bars instead of all fields and data appearing on the screen.
Current status: After the deployment of our targeted solution, we're validating with affected users to determine if impact has been remediated.
Scope of impact: Some users utilizing SharePoint Online and Power Apps custom forms may be impacted by this issue.
Start time: Friday, September 27, 2024, at 12:00 PM UTC
Root cause: A recent service update intending to improve service functionality contains a code regression which is preventing users from seeing correctly aligned and sized screens for SharePoint Online and Power Apps custom forms.
Next update by: Thursday, October 10, 2024, at 11:00 PM UTC
|
|
Time: | Wed Oct 9 22:29:46 2024 |
Description: | Title: Some users may see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms
User impact: Users may see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms.
More info: There is no impact to SharePoint Online custom forms functionality and this is a UI only problem. The affected forms are centered instead of right justified, and have larger-than-expected sizing which results in needing to use scroll bars instead of all fields and data appearing on the screen.
Current status: Our investigation has determined that a standard service update contains a code regression, resulting in impact. We're in the process of developing a targeted fix to correct the regression and remediate impact.
Scope of impact: Some users utilizing SharePoint Online and Power Apps custom forms may be impacted by this issue.
Start time: Friday, September 27, 2024, at 12:00 PM UTC
Root cause: A recent service update intending to improve service functionality contains a code regression which is preventing users from seeing correctly aligned and sized screens for SharePoint Online and Power Apps custom forms.
Next update by: Thursday, October 10, 2024, at 7:00 PM UTC
|
|
Time: | Wed Oct 9 20:19:53 2024 |
Description: | Title: Users see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms
User impact: Users see incorrectly aligned and sized screens for SharePoint Online custom forms, including Power Apps forms.
More info: There is no impact to SharePoint Online custom forms functionality and this is a UI only problem. The affected forms are centered instead of right justified, and have larger-than-expected sizing which results in needing to use scroll bars instead of all fields and data appearing on the screen.
Current status: We're reviewing recent updates to our services to determine what the root cause of this issue.
Scope of impact: Some users utilizing SharePoint Online and Power Apps custom forms may be impacted by this issue.
Next update by: Thursday, October 10, 2024, at 2:30 AM UTC
|
|
TM907891 - Users' calls routed through Auto attendants and Call queues within Microsoft Teams may fail
Status: | serviceRestored |
Start Time: | Thu Oct 10 11:51:00 2024 |
End Time: | Thu Oct 10 13:50:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | incident |
Last Updated: | Thu Oct 10 14:24:04 2024 |
Root Cause: | Auto attendant and Call queue call routed call requests were being routed to an unhealthy portion of service infrastructure, resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 10 14:07:09 2024 |
Description: | Title: Users' calls routed through Auto attendants and Call queues within Microsoft Teams may fail
User impact: Users' calls routed through Auto attendants and Call queues within Microsoft Teams may have failed.
Final status: We've routed the affected call requests to a healthy portion of service infrastructure and confirmed through monitoring service telemetry that impact has been remediated.
Scope of impact: Any user who attempted to make calls routed through Auto attendants and Call queues within Microsoft Teams may have been impacted.
Start time: Thursday, October 10, 2024, at 3:51 PM UTC
End time: Thursday, October 10, 2024, at 5:50 PM UTC
Root cause: Auto attendant and Call queue call routed call requests were being routed to an unhealthy portion of service infrastructure, 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 better prevent similar impact in the future.
- We’re assessing our automated recovery mechanisms in conjunction with our findings into the underlying problem to identify areas for improvement to reduce the time to mitigate similar future issues.
This is the final update for the event.
|
|
Time: | Thu Oct 10 13:36:15 2024 |
Description: | Title: Users' calls routed through Auto attendants and Call queues within Microsoft Teams may fail
User impact: Users' calls routed through Auto attendants and Call queues within Microsoft Teams may fail.
Current status: We've identified an issue in which traffic for Auto attendant and Call queue calls is being routed to an unhealthy portion of service infrastructure, resulting in impact. We're re-routing traffic to a healthy portion of service infrastructure, and we'll aim to provide a timeline for this process to complete by our next scheduled update.
Scope of impact: Any user attempting to make calls routed through Auto attendants and Call queues within Microsoft Teams may be impacted.
Start time: Thursday, October 10, 2024, at 3:51 PM UTC
Root cause: Auto attendant and Call queue call routed call requests are being routed to an unhealthy portion of service infrastructure, resulting in impact.
Next update by: Thursday, October 10, 2024, at 8:00 PM UTC
|
|
Time: | Thu Oct 10 13:14:48 2024 |
Description: | Title: Users' calls routed through Auto Attendant and Call Queue within Microsoft Teams may fail
User impact: Users' calls routed through Auto Attendant and Call Queue within Microsoft Teams may fail.
Current status: We're investigating a potential issue with users' Auto Attendant and Call Queue calls failing within Microsoft Teams, and we're checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
TM907799 - Some users may intermittently see an incorrect presence state using any Microsoft Teams client
Status: | serviceRestored |
Start Time: | Thu Oct 10 11:00:00 2024 |
End Time: | Thu Oct 10 12:05:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | incident |
Last Updated: | Thu Oct 10 14:15:09 2024 |
Root Cause: | The CPU usage spiked for the portion of database caching infrastructure that facilitates presence status updates. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 10 12:43:37 2024 |
Description: | Title: Some users may intermittently see an incorrect presence state using any Microsoft Teams client
User impact: Users may have intermittently seen an incorrect presence state using any Microsoft Teams client.
More info: This issue potentially impacted users who are based in Europe, Middle East and Africa, the United Kingdom, or North America. Users may have shown as offline, status unknown, or their presence may have been outdated.
Final status: After redirecting request traffic to a healthy portion of infrastructure, we've confirmed through our service health monitoring that the impact is remediated.
Scope of impact: Any user based in Europe, Middle East and Africa, the United Kingdom, or North America may have been intermittently impacted.
Start time: Thursday, October 10, 2024, at 3:00 PM UTC
End time: Thursday, October 10, 2024, at 4:05 PM UTC
Root cause: The CPU usage spiked for the portion of database caching infrastructure that facilitates presence status updates.
Next steps:
- We're reviewing recent service changes to identify whether any may have contributed to the spike in CPU usage, so we can prevent similar impact from occurring in the future.
This is the final update for the event.
|
|
Time: | Thu Oct 10 12:18:16 2024 |
Description: | Title: Some users may intermittently see an incorrect presence state using any Microsoft Teams client
User impact: Users may intermittently see an incorrect presence state using any Microsoft Teams client.
More info: This issue can potentially impact users who are based in Europe, Middle East and Africa, the United Kingdom, or North America. Users may show as offline, status unknown, or their presence may be outdated.
Current status: Our service health telemetry indicates that the CPU usage has spiked for the portion of database caching infrastructure that facilitates presence status updates. We've redirected request traffic to a healthy portion of infrastructure and we're monitoring our service health telemetry to ensure that the impact is remediated.
Scope of impact: Any user based in Europe, Middle East and Africa, the United Kingdom, or North America may be intermittently impacted.
Start time: Wednesday, October 9, 2024, at 3:00 PM UTC
Root cause: The CPU usage has spiked for the portion of database caching infrastructure that facilitates presence status updates.
Next update by: Thursday, October 10, 2024, at 5:00 PM UTC
|
|
Time: | Thu Oct 10 11:57:20 2024 |
Description: | Title: Some users may intermittently see an incorrect presence state using any Microsoft Teams client
User impact: Users may intermittently see an incorrect presence state using any Microsoft Teams client.
More info: This issue can potentially impact users who are based in Europe, Middle East and Africa, the United Kingdom, or North America. Users may show as offline, status unknown, or their presence may be outdated.
Current status: Our monitoring systems indicate that impact associated with TM907341 is reoccurring. We're reviewing service health telemetry to determine if CPU usage has spiked again, or if a separate issue is causing the same impact. We'll provide an update within 30 minutes.
|
|
PP907558 - office365 connector flows and apps failing
Status: | serviceRestored |
Start Time: | Wed Oct 9 20:15:34 2024 |
End Time: | Wed Oct 9 22:18:58 2024 |
Service: | Power Platform |
Feature Group: | Service and web access issues |
Classification: | incident |
Last Updated: | Wed Oct 9 22:18:59 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Wed Oct 9 22:18:59 2024 |
Description: | Title: office365 connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the office365 connector.
Final status: After monitoring connector telemetry, it has been observed that functionality to flows and apps using office365 connectors has recovered.
Preliminary Root Cause: The external service used by the office365 connector was unable to handle requests from Microsoft’s connector services.
Next Steps: We continually review our monitoring to reduce detection time and notify customers of issues with external services.
|
|
Time: | Wed Oct 9 21:07:30 2024 |
Description: | Title: office365 connector flows and apps failing
User Impact: Users may receive errors when running flows and apps with the office365 connector.
Current Status: We are monitoring an external issue in which some users are receiving errors when using flows and apps with the office365 connector.
Users may have received HTTP 5xx errors. Users may have received an email notice that their flows failed. Users may have found that their apps were unresponsive.
|
|
EX907228 - Some users may see two browser tabs opening when clicking on URL links in Outlook
Status: | serviceRestored |
Start Time: | Sat Feb 10 14:58:00 2024 |
End Time: | Wed Oct 9 18:00:00 2024 |
Service: | Exchange Online |
Feature Group: | Networking Issues |
Classification: | advisory |
Last Updated: | Wed Oct 9 20:13:56 2024 |
Root Cause: | A service deployment to Outlook contained a code regression that was causing duplicate browser tabs to appear when URL links were opened. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 9 19:40:44 2024 |
Description: | Title: Some users may see two browser tabs opening when clicking on URL links in
Outlook
User impact: Users may have seen two browser tabs opening when clicking on URL links in
Outlook.
More info: Impact was specific to a portion of users clicking on URL links in Outlook on the web and the new Outlook for Windows.
Final status: We've identified that the impact was specific to a portion of users across both Outlook on the Web and the new Outlook for Windows, and we've edited the corresponding fields of this communication accordingly. The deployment of the fix has completed, and after a period of monitoring, we've confirmed impact was remediated.
Scope of impact: Some users that clicked on URL links in email messages on Outlook on the web or the new Outlook for Windows may have been impacted.
Start time: Saturday, February 10, 2024, at 7:58 PM UTC
End time: Wednesday, October 9, 2024, at 10:00 PM UTC
Root cause: A service deployment to Outlook contained a code regression that was causing duplicate browser tabs to appear when URL links were opened.
Next steps:
- To help prevent similar impact in the future, we're further reviewing our deployment release procedures to identify regressions before being released.
This is the final update for the event.
|
|
Time: | Wed Oct 9 15:19:07 2024 |
Description: | Title: Some users may see two tabs opening when clicking on URL links in Outlook on the web
User impact: Users may see two browser tabs opening when clicking on URL links in Outlook on the web.
Current status: We're continuing to monitor the progression of the deployment and anticipate it will be complete and the impact remediated by our next scheduled update.
Scope of impact: Some users that click on URL links in email messages on Outlook on the web may be impacted.
Start time: Saturday, February 10, 2024, at 7:58 PM UTC
Root cause: A recent service deployment to Outlook on the web contained a code regression that's causing duplicate browsers to appear when URL links are opened.
Next update by: Thursday, October 10, 2024, at 3:00 AM UTC
|
|
Time: | Wed Oct 9 03:15:22 2024 |
Description: | Title: Users may incorrectly have double browser tabs opening when clicking on Outlook on the web email URL links
User impact: Users may incorrectly have double browser tabs opening when clicking on Outlook on the web email URL links.
Current status: We've identified that a recent service deployment has inadvertently introduced a code regression and is resulting in impact. We're deploying a fix to correct the regression and remediate impact.
Scope of impact: Your organization is affected by this event, and any user clicking on email URL links in Outlook on the web may be impacted.
Root cause: A recent service deployment has inadvertently introduced a code regression and is resulting in impact.
Next update by: Wednesday, October 9, 2024, at 8:30 PM UTC
|
|
TM907441 - Users may be unable to make or receive calls, join meetings, or are dropped from meetings in Microsoft Teams
Status: | serviceRestored |
Start Time: | Wed Oct 9 14:00:00 2024 |
End Time: | Wed Oct 9 14:30:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | incident |
Last Updated: | Wed Oct 9 15:07:47 2024 |
Root Cause: | Some components of Microsoft Teams API infrastructure responsible for facilitating access to calls and meetings were operating below expected performance thresholds, leading to impact. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 9 15:07:47 2024 |
Description: | Title: Users may be unable to make or receive calls, join meetings, or are dropped from meetings in Microsoft Teams
User impact: Users may have been unable to make or receive calls, join meetings, or dropped from meetings in Microsoft Teams.
More info: This issue specifically impacted Microsoft Teams meetings and Public Switched Telephone Network (PSTN) calls.
Final status: Our investigation has determined that some components of Microsoft Teams API infrastructure responsible for facilitating access to calls and meetings were operating below expected performance thresholds, leading to impact. While our investigation into the affected components to isolate the origin of this performance degradation is ongoing, we've rerouted traffic through healthy infrastructure to resolve this issue, and we've subsequently monitored our service health telemetry to confirm that impact is remediated.
Scope of impact: Any user making or receiving PSTN calls or joining meetings in Microsoft Teams were impacted.
Start time: Wednesday, October 9, 2024, at 6:00 PM UTC
End time: Wednesday, October 9, 2024, at 6:30 PM UTC
Root cause: Some components of Microsoft Teams API infrastructure responsible for facilitating access to calls and meetings were operating below expected performance thresholds, leading to impact.
Next steps:
- We're continuing our investigation into the performance degradation that led to impact to identify what went wrong and to assist us in reinforcing our services against similar future issues.
This is the final update for the event.
|
|
Time: | Wed Oct 9 14:38:14 2024 |
Description: | Title: Users may be unable to join Microsoft Teams meetings or are dropped from meetings
User impact: Users may be unable to join Microsoft Teams meetings or are dropped from meetings.
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.
|
|
TM907341 - Some users may intermittently see an incorrect presence state using any Microsoft Teams client
Status: | serviceRestored |
Start Time: | Wed Oct 9 11:00:00 2024 |
End Time: | Wed Oct 9 13:38:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | incident |
Last Updated: | Wed Oct 9 14:24:28 2024 |
Root Cause: | A portion of database infrastructure that facilitates presence updates encountered an unexpected increase in CPU usage, resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 9 14:24:28 2024 |
Description: | Title: Some users may intermittently see an incorrect presence state using any Microsoft Teams client
User impact: Users may have intermittently seen an incorrect presence state using any Microsoft Teams client.
More info: Users may have shown as offline, status unknown, or their presence may have been outdated.
Final status: Further analysis has identified that the database infrastructure encountered an unexpected increase in CPU usage, resulting in impact. We've completed our rebalancing efforts and validated this has remediated impact with affected users and service telemetry.
Scope of impact: Any user serviced through the impacted infrastructure may have been intermittently affected.
Start time: Wednesday, October 9, 2024, at 3:00 PM UTC
End time: Wednesday, October 9, 2024, at 5:38 PM UTC
Root cause: A portion of database infrastructure that facilitates presence updates encountered an unexpected increase in CPU usage, resulting in impact.
Next steps:
- We're continuing our analysis of service telemetry to identify the underlying cause of the CPU utilization that resulted in impact to better identify and prevent similar impact in the future.
|
|
Time: | Wed Oct 9 13:12:27 2024 |
Description: | Title: Some users may intermittently see an incorrect presence state using any Microsoft Teams client
User impact: Users may intermittently see an incorrect presence state using any Microsoft Teams client.
More info: Users may show as offline, status unknown, or their presence may be outdated.
Current status: Our review of service telemetry has identified that a portion of database caching infrastructure that facilitates presence status updates isn't performing as efficiently as expected. We're in the process of rebalancing load while the investigation into the underlying cause of impact continues.
Scope of impact: Any user serviced through the impacted infrastructure may be intermittently impacted.
Start time: Wednesday, October 9, 2024, at 3:00 PM UTC
Next update by: Wednesday, October 9, 2024, at 7:30 PM UTC
|
|
Time: | Wed Oct 9 12:22:50 2024 |
Description: | Title: Some users may intermittently see an incorrect presence state using any Microsoft Teams client
User impact: Users may intermittently see an incorrect presence state using any Microsoft Teams client.
More info: Users may show as offline, status unknown, or their presence may be outdated.
Current status: We're reviewing service telemetry to better understand the impact scenario and determine our next steps.
Scope of impact: Any user serviced through the impacted infrastructure may be intermittently impacted.
Start time: Wednesday, October 9, 2024, at 3:00 PM UTC
Next update by: Wednesday, October 9, 2024, at 5:30 PM UTC
|
|
Time: | Wed Oct 9 12:04:51 2024 |
Description: | Title: Some users may see an incorrect presence state using any Microsoft Teams client
User impact: Users may see an incorrect presence state using any Microsoft Teams client.
More info: Users may show as offline, status unknown, or their presence may be outdated.
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.
|
|
CP898420 - Microsoft Copilot (Microsoft 365) may be unable to generate content during Microsoft Teams meetings
Status: | postIncidentReviewPublished |
Start Time: | Wed Sep 25 21:53:07 2024 |
End Time: | Wed Sep 25 23:21:00 2024 |
Service: | Microsoft Copilot (Microsoft 365) |
Feature Group: | Microsoft Copilot (Microsoft 365) |
Classification: | incident |
Last Updated: | Tue Oct 8 11:02:05 2024 |
Root Cause: | A recent change to the Microsoft Teams service introduced a misconfiguration which impacted Copilot functionality during Microsoft Teams Meetings. |
Next Update: | N/A |
|
Details
Time: | Tue Oct 8 11:02:05 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Wed Oct 2 17:51:33 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Wed Oct 2 17:51:13 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Fri Sep 27 18:41:17 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Fri Sep 27 18:40:34 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Wed Sep 25 23:55:40 2024 |
Description: | Title: Microsoft Copilot (Microsoft 365) may be unable to generate content during Microsoft Teams meetings
User impact: Copilot may have been unable to generate content during Microsoft Teams meetings.
Final status: We monitored telemetry for an extended period after reverting the change and confirmed that the issue is fully resolved.
Scope of impact: This issue may have potentially affected any user attempting to generate content during Microsoft Teams meetings.
Start time: Thursday, September 26, 2024, at 12:42 AM UTC
End time: Thursday, September 26, 2024, at 3:21 AM UTC
Root cause: A recent change to the Microsoft Teams service introduced a misconfiguration which impacted Copilot functionality during Microsoft Teams Meetings.
Next steps:
- We're analyzing our update validation methodology to ensure misconfigurations aren't introduced in future updates.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|
Time: | Wed Sep 25 23:00:19 2024 |
Description: | Title: Microsoft Copilot (Microsoft 365) may be unable to generate content during Microsoft Teams meetings
User impact: Copilot may be unable to generate content during Microsoft Teams meetings.
Current status: We reverted the impacting change, and we're analyzing telemetry to ensure this resolves the issue as expected.
Scope of impact: This issue may potentially affect any user attempting to generate content during Microsoft Teams meetings.
Start time: Thursday, September 26, 2024, at 12:42 AM UTC
Root cause: A recent change to the Microsoft Teams service is impacting Copilot functionality during Microsoft Teams meetings.
Next update by: Thursday, September 26, 2024, at 4:30 AM UTC
|
|
Time: | Wed Sep 25 22:19:03 2024 |
Description: | Title: Microsoft Copilot (Microsoft 365) may be unable to generate content during Microsoft Teams meetings
User impact: Copilot may be unable to generate content during Microsoft Teams meetings.
Current status: We identified a recent change to the Microsoft Teams service
which is impacting Copilot functionality during Microsoft Teams meetings. We're reviewing potential options to remediate impact.
Scope of impact: This issue may potentially affect any user attempting to generate content during Microsoft Teams meetings.
Start time: Thursday, September 26, 2024, at 12:42 AM UTC
Root cause: A recent change to the Microsoft Teams service is impacting Copilot functionality during Microsoft Teams meetings.
Next update by: Thursday, September 26, 2024, at 4:30 AM UTC
|
|
Time: | Wed Sep 25 21:55:10 2024 |
Description: | Title: Microsoft Copilot (Microsoft 365) may be unable to generate content during Microsoft Teams meetings
User impact: Copilot may be unable to generate content during Microsoft Teams meetings.
Current status: We're investigating a potential issue impacting Microsoft Copilot (Microsoft 365) service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
TM898421 - Users may be unable to utilize the recording services in Microsoft Teams meetings
Status: | postIncidentReviewPublished |
Start Time: | Wed Sep 25 21:55:55 2024 |
End Time: | Wed Sep 25 23:21:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | incident |
Last Updated: | Tue Oct 8 10:59:11 2024 |
Root Cause: | A recent change to the Microsoft Teams service introduced a misconfiguration which impacted recording services during Microsoft Teams meetings. |
Next Update: | N/A |
|
Details
Time: | Tue Oct 8 10:59:11 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Wed Oct 2 17:51:28 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Wed Oct 2 17:51:18 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Fri Sep 27 18:41:21 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Fri Sep 27 18:40:39 2024 |
Description: | A post-incident report has been published.
|
|
Time: | Wed Sep 25 23:54:12 2024 |
Description: | Title: Users may be unable to utilize the recording services in Microsoft Teams meetings
User impact: Users may have been unable to utilize the recording services in Microsoft Teams meetings.
More info: This may have potentially impacted the following scenarios:
-Meetings recordings
-Meetings transcriptions
-Live captions
-Speaker Coach
Final status: We monitored telemetry for an extended period after reverting the change and confirmed that the issue is fully resolved.
Scope of impact: This issue may have potentially affected any user attempting to utilize recording services during Microsoft Teams meetings.
Start time: Thursday, September 26, 2024, at 12:42 AM UTC
End time: Thursday, September 26, 2024, at 3:21 AM UTC
Root cause: A recent change to the Microsoft Teams service introduced a misconfiguration which impacted recording services during Microsoft Teams meetings.
Next steps:
- We're analyzing our update validation methodology to ensure misconfigurations aren't introduced in future updates.
We'll provide a preliminary Post-Incident Report within two business days and a final Post-Incident Report within five business days.
|
|
Time: | Wed Sep 25 22:59:08 2024 |
Description: | Title: Users may be unable to utilize the recording services in Microsoft Teams meetings
User impact: Users may be unable to utilize the recording services in Microsoft Teams meetings.
More info: This may potentially impact the following scenarios:
-Meetings recordings
-Meetings transcriptions
-Live captions
-Speaker Coach
Current status: We reverted the impacting change, and we're analyzing telemetry to ensure this resolves the issue as expected.
Scope of impact: This issue may potentially affect any user attempting to utilize recording services during Microsoft Teams meetings.
Start time: Thursday, September 26, 2024, at 12:42 AM UTC
Root cause: A recent change to the Microsoft Teams service is impacting recording services during Microsoft Teams meetings.
Next update by: Thursday, September 26, 2024, at 4:30 AM UTC
|
|
Time: | Wed Sep 25 22:19:27 2024 |
Description: | Title: Users may be unable to utilize the recording services in Microsoft Teams meetings
User impact: Users may be unable to utilize the recording services in Microsoft Teams meetings.
More info: This may potentially impact the following scenarios:
-Meetings recordings
-Meetings transcriptions
-Live captions
-Speaker Coach
Current status: A recent change to the Microsoft Teams service is impacting recording services during Microsoft Teams meetings.
Scope of impact: This issue may potentially affect any user attempting to utilize recording services during Microsoft Teams meetings.
Start time: Thursday, September 26, 2024, at 12:42 AM UTC
Root cause: A recent change to the Microsoft Teams service is impacting recording services during Microsoft Teams meetings.
Next update by: Thursday, September 26, 2024, at 4:30 AM UTC
|
|
Time: | Wed Sep 25 21:56:12 2024 |
Description: | Title: Users may be unable to utilize the recording services in Microsoft Teams meetings
User impact: Users may be to unable to utilize the recording services in Microsoft Teams meetings.
More info: This may potentially impact the following scenarios:
-Meetings recordings
-Meetings transcriptions
-Live captions
-Speaker Coach
Current status: We're investigating a potential issue with Microsoft Teams and are checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
EX906402 - Some users may experience intermittent errors or failures when accessing their mailbox es via Outlook on the web
Status: | serviceRestored |
Start Time: | Mon Oct 7 15:05:00 2024 |
End Time: | Mon Oct 7 16:55:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | incident |
Last Updated: | Mon Oct 7 17:32:05 2024 |
Root Cause: | A portion of infrastructure responsible for Outlook on the web traffic flow was performing below acceptable service thresholds, which led to impact. |
Next Update: | N/A |
|
Details
Time: | Mon Oct 7 17:21:14 2024 |
Description: | Title: Some users may experience intermittent errors or failures when accessing their mailbox es via Outlook on the web
User impact: Users may have experienced intermittent errors or failures when they accessed their mailbox es via Outlook on the web.
Final status: We've routed the affected Outlook on the web traffic to alternative healthy infrastructure, and we've confirmed through telemetry that this has remediated the issue.
Scope of impact: Some users who attempted to access their Exchange Online mailboxes through Outlook on the web may have been intermittently impacted if they were served through the affected infrastructure in North America.
Start time: Monday, October 7, 2024, at 7:05 PM UTC
End time: Monday, October 7, 2024, at 8:55 PM UTC
Root cause: A portion of infrastructure responsible for Outlook on the web traffic flow was performing below acceptable service thresholds, which led to impact.
Next steps:
- We're reviewing the portion of affected infrastructure to better understand how it came to be impacting so we can prevent similar issues from occurring in the future.
- We're optimizing our automated service recovery system so we can more quickly identify and address similar issues moving forward.
This is the final update for the event.
|
|
Time: | Mon Oct 7 16:23:51 2024 |
Description: | Title: Some users may experience intermittent errors or failures when accessing their mailbox via Outlook on the web
User impact: Users may experience intermittent errors or failures when accessing their mailbox via Outlook on the web.
Current status: We've identified a portion of infrastructure responsible for Outlook on the web traffic flow is performing below acceptable service thresholds and leading to impact. We're isolating and analyzing this portion of infrastructure to better understand the issue and determine our next troubleshooting steps.
Scope of impact: Some users attempting to access their Exchange Online mailboxes through Outlook on the web may be intermittently impacted if they are served through the affected infrastructure.
Start time: Monday, October 7, 2024, at 7:05 PM UTC
Root cause: A portion of infrastructure responsible for Outlook on the web traffic flow is performing below acceptable service thresholds and leading to impact.
Next update by: Monday, October 7, 2024, at 10:00 PM UTC
|
|
Time: | Mon Oct 7 15:29:55 2024 |
Description: | Title: Potential issues accessing mailboxes via one or more connection methods
User impact: Users may experience errors or failures when accessing their mailbox via one or more Exchange Online connection methods.
Current status: We're investigating a potential issue and checking for impact to your organization. We'll provide an update within 60 minutes.
|
|
TM901092 - Users may be unable to view meetings options for some shared mailboxes in Microsoft Teams
Status: | serviceRestored |
Start Time: | Mon Sep 9 20:00:00 2024 |
End Time: | Thu Oct 3 23:00:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Fri Oct 4 14:54:08 2024 |
Root Cause: | A code regression within the meeting options feature in a recent service update was preventing the viewing of meeting options for some shared mailboxes in Microsoft Teams. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 4 14:54:08 2024 |
Description: | Title: Users may be unable to view meetings options for some shared mailboxes in Microsoft Teams
User impact: Users may have been unable to view meetings options for some shared mailboxes in Microsoft Teams.
Final status: Our operation to deploy the previously mentioned fix is complete, and we've received confirmation from some previously affected users that impact is remediated.
Scope of impact: This issue may have affected any user who attempted to view meeting options for some shared mailboxes in Microsoft Teams.
Start time: Tuesday, September 10, 2024, at 12:00 AM UTC
End time: Friday, October 4, 2024, at 3:00 AM UTC
Root cause: A code regression within the meeting options feature in a recent service update was preventing the viewing of meeting options for some shared mailboxes in Microsoft Teams.
Next steps:
- We're reviewing our Microsoft Teams code update procedures pertaining to the code base responsible for displaying meeting options for shared mailboxes to prevent similar future impact.
This is the final update for the event.
|
|
Time: | Thu Oct 3 16:54:46 2024 |
Description: | Title: Users may be unable to view meetings options for some shared mailboxes in Microsoft Teams
User impact: Users may be unable to view meetings options for some shared mailboxes in Microsoft Teams.
Current status: The deployment of the fix is progressing slower than initially expected. We anticipate having a complete mitigation timeline by the next scheduled update.
Scope of impact: This issue may affect any user who attempts to view meeting options for some shared mailboxes in Microsoft Teams.
Start time: Tuesday, September 10, 2024, at 12:00 AM UTC
Root cause: A code regression of the meeting options feature in a recent service update is preventing the viewing of meeting options for some shared mailboxes in Microsoft Teams.
Next update by: Friday, October 4, 2024, at 9:30 PM UTC
|
|
Time: | Mon Sep 30 01:58:36 2024 |
Description: | Title: Users may be unable to view meetings options for some shared mailboxes in Microsoft Teams
User impact: Users may be unable to view meetings options for some shared mailboxes in Microsoft Teams.
Current status: This is a continuation of the impact previously communicated under TM894578. We've received reports that impact still remains, and after investigating our deployment logs, we discovered that the previous fix that we communicated had been fully deployed, is still progressing. We have a newly revised timeline and we now believe the fix will complete deployment to the affected environment by our next scheduled update.
Scope of impact: This issue may affect any user who attempts to view meeting options for some shared mailboxes in Microsoft Teams.
Start time: Tuesday, September 10, 2024, at 12:00 AM UTC
Estimated time to resolve: Thursday October 3, 2024, at 10:00 PM UTC
Root cause: A code regression of the meeting options feature in a recent service update is preventing the viewing of meeting options for some shared mailboxes in Microsoft Teams.
Next update by: Thursday, October 3, 2024, at 10:00 PM UTC
|
|
TM896583 - Users may be unable to change the 'Privacy' drop-down in teams details in Microsoft Teams desktop client and web app
Status: | serviceRestored |
Start Time: | Fri Sep 20 01:34:00 2024 |
End Time: | Thu Oct 3 10:00:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Fri Oct 4 13:50:08 2024 |
Root Cause: | A recent update, which provided a fix for an unrelated issue, introduced a regression that resulted in exceptions when users attempted to change the 'Privacy' drop-down menu choice in a team's details settings in Microsoft Teams desktop and web apps. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 4 13:33:59 2024 |
Description: | Title: Users may be unable to change the 'Privacy' drop-down in teams details in Microsoft Teams desktop client and web app
User impact: Users may have been unable to change the 'Privacy' drop-down in teams details in Microsoft Teams desktop and web apps.
Final status: We've completed deployment of the fix and confirmed through internal testing that the impact is remediated.
Scope of impact: This issue may have impacted any user attempting to change the 'Privacy' drop-down menu choice in a team's details settings in Microsoft Teams desktop and web apps.
Start time: Friday, September 20, 2024, at 5:34 AM UTC
End time: Thursday, October 3, 2024, at 2:00 PM UTC
Root cause: A recent update, which provided a fix for an unrelated issue, introduced a regression that resulted in exceptions when users attempted to change the 'Privacy' drop-down menu choice in a team's details settings in Microsoft Teams desktop and web apps.
Next steps:
- We're reviewing the recent update to determine why the fix contained a regression so we can prevent similar impact from occurring in the future.
This is the final update for the event.
|
|
Time: | Mon Sep 30 13:48:46 2024 |
Description: | Title: Users may be unable to change the 'Privacy' drop-down in teams details in Microsoft Teams desktop client and web app
User impact: Users may be unable to change the 'Privacy' drop-down in teams details in Microsoft Teams desktop and web apps.
Current status: We've completed the validation of the fix and initiated its release more broadly. We're monitoring as it progresses, and we expect the deployment to complete by the next scheduled update.
Scope of impact: This issue may impact any user attempting to change the 'Privacy' drop-down menu choice in a team's details settings in Microsoft Teams desktop and web apps.
Estimated time to resolve: We expect the fix to complete deployment by Friday, October 4, 2024.
Root cause: A recent update, which provided a fix for an unrelated issue, introduced a regression that’s resulting in exceptions occurring when attempting to change the 'Privacy' drop-down menu choice in a team's details settings in Microsoft Teams desktop and web apps.
Next update by: Friday, October 4, 2024, at 7:00 PM UTC
|
|
Time: | Mon Sep 23 17:26:43 2024 |
Description: | Title: Users may be unable to change the 'Privacy' drop-down in teams details in Microsoft Teams desktop client and web app
User impact: Users may be unable to change the 'Privacy' drop-down in teams details in Microsoft Teams desktop client and web app.
More info: This impact specifically affects team owners. To locate the referenced drop-down menu, a team owner can click the context menu next to the team, choose 'Manage team,' select the 'Settings' tab, and then click the 'Edit' button.
Current status: We've made changes to the Title, User impact, Scope of impact and Root cause fields to reflect that the impact is occurring in the 'Manage team' menu in teams; not in the channels themselves. Further, we've identified that a recent update which provided a fix for an unrelated issue introduced a regression which resulted in exceptions occurring when attempting to change the 'Privacy' drop-down in a team's details settings menu choice in the Microsoft Teams desktop client and web app. We've developed a fix for the issue and are initiating deployment to our internal testing environments for validation of the fix. We anticipate having a timeline for the deployment to the affected environment with our next scheduled update.
Scope of impact: This issue may impact any user attempting to change the 'Privacy' drop-down menu choice in a team's details settings in Microsoft Teams desktop client and web app.
Root cause: A recent update which provided a fix for an unrelated issue introduced a regression which resulted in exceptions occurring when attempting to change the 'Privacy' drop-down menu choice in a team's details settings in Microsoft Teams desktop client and web app.
Next update by: Monday, September 30, 2024, at 7:00 PM UTC
|
|
Time: | Mon Sep 23 17:09:20 2024 |
Description: | Title: Users may be unable to change public channels to private channels in Microsoft Teams desktop client and web app
User impact: Users may be unable to change public channels to private channels in Microsoft Teams desktop client and web app.
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.
|
|
TM904464 - Admins may be unable to save settings in the Teams Admin Center for Microsoft Teams Rooms devices
Status: | serviceRestored |
Start Time: | Thu Sep 26 10:00:00 2024 |
End Time: | Fri Oct 4 11:57:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Fri Oct 4 12:48:06 2024 |
Root Cause: | A recent service update to Microsoft Teams was causing impact to the Teams Admin Center due to a missing condition check in the code. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 4 12:48:06 2024 |
Description: | Title: Admins may be unable to save settings in the Teams Admin Center for Microsoft Teams Rooms devices
User impact: Admins may have been unable to save settings in the Teams Admin Center for Microsoft Teams Rooms devices.
More info: When editing the settings in the Teams Admin Center, the "apply" button will appear grayed out.
Final status: We've deployed our fix to correct the issue with the recent update and confirmed after testing with a subset of users that impact was successfully resolved.
Scope of impact: This issue may have potentially impact any admin attempting to save settings for Teams Meeting Room devices in the Teams Admin Center.
Start time: Thursday, September 26, 2024, at 2:00 PM UTC
End time: Friday, October 4, 2024, at 3:57 PM UTC
Root cause: A recent service update to Microsoft Teams was causing impact to the Teams Admin Center due to a missing condition check in the code.
Next steps:
- We're reviewing our update testing and validation procedures to identify opportunities to improve impact detection and better prevent similar future occurrences.
This is the final update for the event.
|
|
Time: | Fri Oct 4 05:57:13 2024 |
Description: | Title: Admins may be unable to save settings in the Teams Admin Center for Microsoft Teams Rooms devices
User impact: Admins may be unable to save settings in the Teams Admin Center for Microsoft Teams Rooms devices.
More info: When editing the settings in the Teams Admin Center, the "apply" button will appear grayed out.
Current status: We're making final preparations before deploying the proposed fix to the affected environment.
Scope of impact: This issue may potentially impact any admin attempting to save settings for Teams Meeting Room devices in the Teams Admin Center.
Root cause: A recent service update to Microsoft Teams is causing impact to the Teams Admin Center.
Next update by: Friday, October 4, 2024, at 5:00 PM UTC
|
|
Time: | Fri Oct 4 00:15:38 2024 |
Description: | Title: Admins may be unable to save settings in the Teams Admin Center for Microsoft Teams Rooms devices
User impact: Admins may be unable to save settings in the Teams Admin Center for Microsoft Teams Rooms devices.
More info: When editing the settings in the Teams Admin Center, the "apply" button will appear grayed out.
Current status: We identified that the issue is being caused by a recent service update to Microsoft Teams. We've developed a fix for the issue and are preparing to deploy it to the affected environment to remediate the impact. We'll provide an updated estimate on the mitigation timeline when one is available.
Scope of impact: This issue may potentially impact any admin attempting to save settings for Teams Meeting Room devices in the Teams Admin Center.
Root cause: A recent service update to Microsoft Teams is causing impact to the Teams Admin Center.
Next update by: Friday, October 4, 2024, at 10:00 AM UTC
|
|
Time: | Thu Oct 3 23:47:25 2024 |
Description: | Title: Admins may be unable to save settings in the Teams Admin Center for Microsoft Teams Rooms devices
User impact: Admins may be unable to save settings in the Teams Admin Center for Microsoft Teams Rooms devices.
More info: When editing the settings in the Teams Admin Center, the "apply" button will appear grayed out.
Current status: We're investigating a potential issue with Microsoft Teams service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
SV899597 - Users may be unable to access links in Stream (Classic)
Status: | serviceRestored |
Start Time: | Mon Sep 23 14:30:00 2024 |
End Time: | Thu Oct 3 09:30:00 2024 |
Service: | Microsoft Stream |
Feature Group: | Stream website |
Classification: | advisory |
Last Updated: | Fri Oct 4 11:34:39 2024 |
Root Cause: | The Stream link routing service, responsible for providing access to these links, was deprecated before the new routing service went live, resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 4 11:34:39 2024 |
Description: | Title: Users may be unable to access links in Stream (Classic)
User impact: Users may have been unable to access links in Stream.
Final status: We've confirmed that the fix has completed deployment to all affected infrastructure and validated this has remediated impact with service telemetry.
Scope of impact: Any user attempting to access links in Streams may have been impacted.
Start time: Monday, September 23, 2024, at 6:30 PM UTC
End time: Thursday, October 3, 2024, at 1:30 PM UTC
Root cause: The Stream link routing service, responsible for providing access to these links, was deprecated before the new routing service went live, resulting in impact.
Next steps:
- We're reviewing our deprecation procedures to better identify and prevent similar impact in the future.
This is the final update for the event.
|
|
Time: | Thu Oct 3 10:49:34 2024 |
Description: | Title: Users may be unable to access links in Stream (Classic)
User impact: Users may be unable to access links in Stream.
Current status: The completion of our deployment is requiring a bit more time than previously estimated, and our updated deployment timelines expect for it to have completed by our next scheduled update.
Scope of impact: Any user attempting to access links in Streams may be impacted.
Start time: Monday, September 23, 2024, at 6:30 PM UTC
Root cause: The Stream link routing service, responsible for providing access to these links, was deprecated before the new routing service has gone live, resulting in impact.
Next update by: Friday, October 4, 2024, at 5:30 PM UTC
|
|
Time: | Wed Oct 2 12:08:58 2024 |
Description: | Title: Users may be unable to access links in Stream (Classic)
User impact: Users may be unable to access links in Stream.
Current status: We've isolated a release blocker which has delayed our solution from completing necessary deployments and remediating the impact. We've addressed the blocker and resumed our deployment, and our updated deployment timelines expect for it to have completed and remediated the impact by Thursday, October 3, 2024.
Scope of impact: Any user attempting to access links in Streams may be impacted.
Start time: Monday, September 23, 2024, at 6:30 PM UTC
Root cause: The Stream link routing service, responsible for providing access to these links, was deprecated before the new routing service has gone live, resulting in impact.
Next update by: Thursday, October 3, 2024, at 5:30 PM UTC
|
|
Time: | Tue Oct 1 12:11:29 2024 |
Description: | Title: Users may be unable to access links in Stream (Classic)
User impact: Users may be unable to access links in Stream.
Current status: The fix has reached 45 percent of the impacted environment and we expect it to be fully saturated and remediate impact by the end of Tuesday, October 1, 2024. Once complete, we'll monitor service health telemetry to ensure the error rate has decreased as expected.
Scope of impact: Any user attempting to access links in Streams may be impacted.
Start time: Monday, September 23, 2024, at 6:30 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by the end of Tuesday, October 1, 2024.
Root cause: The Stream link routing service, responsible for providing access to these links, was deprecated before the new routing service has gone live, resulting in impact.
Next update by: Wednesday, October 2, 2024, at 5:30 PM UTC
|
|
Time: | Mon Sep 30 11:49:10 2024 |
Description: | Title: Users may be unable to access links in Stream (Classic)
User impact: Users may be unable to access links in Stream.
Current status: The fix has reached 15 percent of users and we’re expecting it to reach 50 percent of users by the end of today, September 30, 2024. We anticipate our new link routing service will reach 100 percent of users by the time of our next update on Tuesday, October 1, 2024.
Scope of impact: Any user attempting to access links in Streams may be impacted.
Start time: Monday, September 23, 2024, at 6:30 PM UTC
Estimated time to resolve: We anticipate impact to be resolved by the time of our next update on Tuesday, October 1, 2024, at 5:30 PM UTC.
Root cause: The Stream link routing service, responsible for providing access to these links, was deprecated before the new routing service has gone live, resulting in impact.
Next update by: Tuesday, October 1, 2024, at 5:30 PM UTC
|
|
Time: | Fri Sep 27 13:39:41 2024 |
Description: | Title: Users may be unable to access links in Stream (Classic)
User impact: Users may be unable to access links in Stream.
Current status: We've completed validation of the new link routing service and we've begun rollout. Some users may begin to see remediation and we expect the new service to reach 50% of users by the time of our next update. We'll provide a timeline for the completion of the rollout as one becomes available.
Scope of impact: Any user attempting to access links in Streams may be impacted.
Start time: Monday, September 23, 2024, at 6:30 PM UTC
Root cause: The Stream link routing service, responsible for providing access to these links, was deprecated before the new routing service has gone live, resulting in impact.
Next update by: Monday, September 30, 2024, at 5:30 PM UTC
|
|
Time: | Fri Sep 27 11:51:09 2024 |
Description: | Title: Users may be unable to access links in Stream (Classic)
User impact: Users may be unable to access links in Stream.
Current status: We received reports of an issue where users can't access links in Stream and determined that the link routing service was deprecated before the new routing service was ready to handle the traffic, resulting in impact. We've initiated the new link routing service for some users to validate that it properly serves traffic before initiating it for all affected users. We expect this validation process will complete by our next scheduled update.
Scope of impact: Any user attempting to access links in Streams may be impacted.
Start time: Monday, September 23, 2024, at 6:30 PM UTC
Root cause: The Stream link routing service, responsible for providing access to these links, was deprecated before the new routing service has gone live, resulting in impact.
Next update by: Friday, September 27, 2024, at 9:00 PM UTC
|
|
EX904408 - Users with editor permissions on shared calendars may have not been able to delete attachments from events
Status: | serviceRestored |
Start Time: | Thu Oct 3 10:20:00 2024 |
End Time: | Thu Oct 3 19:45:00 2024 |
Service: | Exchange Online |
Feature Group: | E-Mail and calendar access |
Classification: | advisory |
Last Updated: | Fri Oct 4 04:09:31 2024 |
Root Cause: | An update to improve some commands related to event attachment management resulted in impact. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 4 04:07:36 2024 |
Description: | Title: Users with editor permissions on shared calendars may have not been able to delete attachments from events
User impact: Users with editor permissions on shared calendars may have not been able to delete attachments from events.
Final status: We've finished reverting the offending change and can confirm after a period of monitoring that impact has been resolved.
Scope of impact: All users serviced by the affected infrastructure may have been impacted.
Start time: Thursday, October 3, 2024, at 2:20 PM UTC
End time: Thursday, October 3, 2024, at 11:45 PM UTC
Root cause: An update to improve some commands related to event attachment management resulted in impact.
Next steps:
- We're reviewing our standard service update procedures to better identify similar issues during our development and testing cycles.
This the final update for this event.
|
|
Time: | Thu Oct 3 19:39:33 2024 |
Description: | Title: Users with editor permissions on shared calendars may not be able to delete attachments from events
User impact: Users with editor permissions on shared calendars may not be able to delete attachments from events.
Current status: We were alerted to this issue through our internal monitors that detected a spike in errors within the affected infrastructure resulting in users being unable to delete attachments for events in some cases. After reviewing the service logs, we identified an update to improve some commands related to event attachment management that correlates with the increase in errors. We're reverting this change and we'll monitor the service health to ensure impact is sufficiently remediated.
Scope of impact: All users serviced by the affected infrastructure may be impacted.
Start time: Thursday, October 3, 2024, at 2:20 PM UTC
Root cause: An update to improve some commands related to event attachment management resulted in impact.
Next update by: Friday, October 4, 2024, at 9:00 AM UTC
|
|
TM904445 - Some users may be unable to create Microsoft Teams channel meetings through the Teams calendar
Status: | serviceRestored |
Start Time: | Thu Oct 3 12:03:00 2024 |
End Time: | Fri Oct 4 02:30:12 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | incident |
Last Updated: | Fri Oct 4 02:31:01 2024 |
Root Cause: | A recent update, which enabled a new feature in the affected environment, caused a configuration issue, leading to impact. |
Next Update: | N/A |
|
Details
Time: | Fri Oct 4 02:31:01 2024 |
Description: | Title: Some users may be unable to create Microsoft Teams channel meetings through the Teams calendar
User impact: Users may have been unable to create Microsoft Teams channel meetings through the Teams calendar.
Final status: After our review of the service logs, we identified a correlating update to the affected service that enabled new features in the environment which caused a configuration issue, leading to impact. We've reverted the update and, after a period of monitoring the service health, we've confirmed that impact has been successfully remediated.
Scope of impact: Users attempting to create Microsoft Teams channel meetings through the Teams calendar may have been impacted by this event.
Start time: Thursday, October 3, 2024, at 4:03 PM UTC
End time: Friday, October 4, 2024, at 6:30 AM UTC
Root cause: A recent update, which enabled a new feature in the affected environment, caused a configuration issue, leading to impact.
Next steps:
- We're reviewing the offending update to identify changes that can be made to prevent similar issues from occurring in the future.
This is the final update for the event.
|
|
Time: | Thu Oct 3 22:35:24 2024 |
Description: | Title: Some users may be unable to create Microsoft Teams channel meetings through the Teams calendar
User impact: Users may be unable to create Microsoft Teams channel meetings through the Teams calendar.
Current status: We're reviewing service logs and checking for any recent service updates that may be contributing to impact so we can cultivate our troubleshooting steps.
Scope of impact: Users attempting to create Microsoft Teams channel meetings through the Teams calendar are impacted by this event.
Next update by: Friday, October 4, 2024, at 6:30 AM UTC
|
|
Time: | Thu Oct 3 22:06:18 2024 |
Description: | Title: Some users may be unable to create Microsoft Teams channel meetings through the Teams calendar
User impact: Users may be unable to create Microsoft Teams channel meetings through the Teams calendar.
Current status: We're investigating a potential issue with Microsoft Teams service and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
TM904164 - Some users may intermittently be unable to create new Virtual Appointments in their Microsoft Teams calendar
Status: | serviceRestored |
Start Time: | Mon Sep 30 10:00:00 2024 |
End Time: | Thu Oct 3 13:05:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Thu Oct 3 14:46:44 2024 |
Root Cause: | An Authentication library used by the Virtual Appointment Graph API in Microsoft Teams was causing intermittent failures. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 3 14:30:46 2024 |
Description: | Title: Some users may intermittently be unable to create new Virtual Appointments in their Microsoft Teams calendar
User impact: Users may have intermittently been unable to create new Virtual Appointments in their Microsoft Teams calendar.
More info: This issue impacted the Microsoft Teams desktop client and web application. Virtual Appointment creation isn’t available to users in the Team mobile app and therefore couldn’t have been used as a potential method to bypass the impact.
Final status: We've rerouted traffic to an alternative, healthy infrastructure, and after monitoring the service, we've verified that this action successfully resolved the issue.
Scope of impact: Impact may have occurred intermittently for some users attempting to create new Virtual Appointments in their Microsoft Teams calendar.
Start time: Monday, September 30, 2024, at 2:00 PM UTC
End time: Thursday, October 3, 2024, at 5:05 PM UTC
Root cause: An Authentication library used by the Virtual Appointment Graph API in Microsoft Teams was causing intermittent failures.
Next steps:
- We're reviewing our authentication library configurations to better identify similar issues and help prevent similar problems in the future.
This is the final update for the event.
|
|
Time: | Thu Oct 3 13:12:11 2024 |
Description: | Title: Some users may intermittently be unable to create new Virtual Appointments in their Microsoft Teams calendar
User impact: Users may intermittently be unable to create new Virtual Appointments in their Microsoft Teams calendar.
More info: This issue impacts the Microsoft Teams desktop client and web application. Virtual Appointment creation isn't available in the Team mobile app.
Current status: We've identified that an authentication library used by the Virtual Appointment Graph API in Microsoft Teams is causing intermittent failures. To potentially remediate this, we're rerouting traffic to an alternative, healthy infrastructure and are actively monitoring the process to ensure it completes successfully and resolves the issue.
Scope of impact: Impact may occur intermittently for some users attempting to create new Virtual Appointments in their Microsoft Teams calendar.
Start time: Monday, September 30, 2024, at 2:00 PM UTC
Root cause: An Authentication library used by the Virtual Appointment Graph API in Microsoft Teams is causing intermittent failures.
Next update by: Thursday, October 3, 2024, at 7:30 PM UTC
|
|
Time: | Thu Oct 3 12:17:40 2024 |
Description: | Title: Some users may intermittently be unable to create new Virtual Appointments in their Microsoft Teams calendar
User impact: Users may intermittently be unable to create new Virtual Appointments in their Microsoft Teams calendar.
More info: This issue impacts the Microsoft Teams desktop client and web application. Virtual Appointment creation isn't available in the Team mobile app.
Current status: Our monitoring systems have identified that some users may intermittently be unable to create new Virtual Appointments in their Microsoft Teams calendar. We're reviewing service telemetry to assess the impact and determine a remediation pathway.
Scope of impact: Impact may occur intermittently for some users attempting to create new Virtual Appointments in their Microsoft Teams calendar.
Next update by: Thursday, October 3, 2024, at 5:30 PM UTC
|
|
OD867515 - Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in OneDrive for Business
Status: | serviceRestored |
Start Time: | Wed Jul 31 00:30:00 2024 |
End Time: | Thu Oct 3 12:00:00 2024 |
Service: | OneDrive for Business |
Feature Group: | OneDrive for Business |
Classification: | advisory |
Last Updated: | Thu Oct 3 13:20:47 2024 |
Root Cause: | A necessary short-term fix for an unrelated issue was implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in OneDrive for Business. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 3 13:20:47 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in OneDrive for Business
User impact: Users may have received a security warning when opening Word, Excel or PowerPoint files in OneDrive for Business.
More info: More specifically, users may have incorrectly received a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within OneDrive for Business. Also, affected users may have seen the following message "This content presents a potential issue".
While we worked to remediate impact, we recommended that users update their Microsoft 365 Office clients by accessing an Office app such as Word and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Final status: Following our extensive service monitoring, we've confirmed that our fix deployment has remediated impact for a majority of users. For users that may continue to experience impact, updating the Microsoft 365 Office client has been confirmed to remediate the impact, the steps of which have been outlined in the More info statement of this communication.
Scope of impact: Impact was specific to some users who were served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective OneDrive for Business web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
End time: Thursday, October 3, 2024, at 4:00 PM UTC
Root cause: A necessary short-term fix for an unrelated issue was implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in OneDrive for Business.
Next steps:
- We're further analyzing the offending short-term fix that resulted in impact to help us isolate similar issues during our pre-deployment testing and validation processes.
This is the final update for the event.
|
|
Time: | Wed Oct 2 14:23:41 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in OneDrive for Business
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in OneDrive for Business.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within OneDrive for Business. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: We're continuing with our extensive monitoring so we can ensure that impact is resolved. For immediate mitigation, users can update their Microsoft 365 Office clients to remediate the impact.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective OneDrive for Business web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in OneDrive for Business.
Next update by: Thursday, October 3, 2024, at 6:30 PM UTC
|
|
Time: | Wed Sep 18 13:19:09 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in OneDrive for Business
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in OneDrive for Business.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within OneDrive for Business. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: We've identified extensive monitoring is needed to ensure the prompts continue to reduce as expected, remediating impact for all users. Additionally, we're continuing to request that users update their Microsoft 365 Office clients to the latest version as an immediate mitigation.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective OneDrive for Business web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in OneDrive for Business.
Next update by: Wednesday, October 2, 2024, at 6:30 PM UTC
|
|
Time: | Wed Sep 4 12:59:49 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in OneDrive for Business
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in OneDrive for Business.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within OneDrive for Business. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: After our initial period of monitoring service health telemetry after the previous completion of our fix deployments, we've confirmed prompts have reduced as expected. We're continuing to monitor for a period of time to ensure a majority of users upgrade to the latest build to fully resolve the issue.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective OneDrive for Business web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in OneDrive for Business.
Next update by: Wednesday, September 18, 2024, at 6:30 PM UTC
|
|
Time: | Mon Aug 26 13:27:59 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in OneDrive for Business
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in OneDrive for Business.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within OneDrive for Business. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: We've confirmed the deployments of our fixes have completed and users can update to the latest Microsoft 365 Office clients to receive the fix and resolve impact. We're monitoring service health telemetry to confirm users are updating to the latest client and prompts are reducing as expected.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective OneDrive for Business web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in OneDrive for Business.
Next update by: Wednesday, September 4, 2024, at 6:30 PM UTC
|
|
Time: | Fri Aug 23 14:31:10 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in OneDrive for Business
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in OneDrive for Business.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within OneDrive for Business. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: We've confirmed that our deployment of the fix for Semi-Annual Channels is not progressing as expected and are investigating the underlying source of the slow saturation.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective OneDrive for Business web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in OneDrive for Business.
Next update by: Monday, August 26, 2024, at 6:30 PM UTC
|
|
Time: | Wed Aug 21 15:21:33 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in OneDrive for Business
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in OneDrive for Business.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within OneDrive for Business. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: The fix deployment is progressing slower than anticipated and we're looking into methods to expedite this process. We've also identified that this warning prompt is displaying when known safe links are selected and are investigating ways to streamline this process and prevent extraneous alerts going forward.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective OneDrive for Business web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in OneDrive for Business.
Next update by: Friday, August 23, 2024, at 8:00 PM UTC
|
|
Time: | Tue Aug 20 15:57:02 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in OneDrive for Business
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in OneDrive for Business.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within SharePoint Online. Also, affected users may see the following message "This content presents a potential issue".
Current status: This is a continuation of the event previously communicated via SP861520.
We've determined that a small number of users are still impacted by this event. Impact is isolated to those still operating under the Semi-Annual Channel update from January 2024 - 16.0.17328.20452.
The fix is progressing throughout the remaining infrastructure, and we expect to have a remediation timeline.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective OneDrive for Business web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in OneDrive for Business.
Next update by: Wednesday, August 21, 2024, at 8:00 PM UTC
|
|
SP867513 - Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in SharePoint Online
Status: | serviceRestored |
Start Time: | Wed Jul 31 00:30:00 2024 |
End Time: | Thu Oct 3 12:00:00 2024 |
Service: | SharePoint Online |
Feature Group: | SharePoint Features |
Classification: | advisory |
Last Updated: | Thu Oct 3 13:19:57 2024 |
Root Cause: | A necessary short-term fix for an unrelated issue was implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in SharePoint Online. |
Next Update: | N/A |
|
Details
Time: | Thu Oct 3 13:19:57 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in SharePoint Online
User impact: Users may have received a security warning when opening Word, Excel, or PowerPoint files in SharePoint Online.
More info: More specifically, users may have incorrectly received a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within SharePoint Online. Also, affected users may have seen the following message "This content presents a potential issue".
While we worked to remediate impact, we recommended that users update their Microsoft 365 Office clients by accessing
an Office app such as Word and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Final status: Following our extensive service monitoring, we've confirmed that our fix deployment has remediated impact for a majority of users. For users that may continue to experience impact, updating the Microsoft 365 Office client has been confirmed to remediate the impact, the steps of which have been outlined in the More info statement of this communication.
Scope of impact: Impact was specific to some users who were served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective SharePoint Online web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
End time: Thursday, October 3, 2024, at 4:00 PM UTC
Root cause: A necessary short-term fix for an unrelated issue was implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in SharePoint Online.
Next steps:
- We're further analyzing the offending short-term fix that resulted in impact to help us isolate similar issues during our pre-deployment testing and validation processes.
This is the final update for the event.
|
|
Time: | Wed Oct 2 14:22:49 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in SharePoint Online
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in SharePoint Online.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within SharePoint Online. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: We're continuing with our extensive monitoring so we can ensure that impact is resolved. For immediate mitigation, users can update their Microsoft 365 Office clients to remediate the impact.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective SharePoint Online web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in SharePoint Online.
Next update by: Thursday, October 3, 2024, at 6:30 PM UTC
|
|
Time: | Wed Sep 18 13:19:44 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in SharePoint Online
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in SharePoint Online.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within SharePoint Online. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: We've identified extensive monitoring is needed to ensure the prompts continue to reduce as expected, remediating impact for all users. Additionally, we're continuing to request that users update their Microsoft 365 Office clients to the latest version as an immediate mitigation.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective SharePoint Online web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in SharePoint Online.
Next update by: Wednesday, October 2, 2024, at 6:30 PM UTC
|
|
Time: | Wed Sep 4 12:59:34 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in SharePoint Online
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in SharePoint Online.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within SharePoint Online. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: After our initial period of monitoring service health telemetry after the previous completion of our fix deployments, we've confirmed prompts have reduced as expected. We're continuing to monitor for a period of time to ensure a majority of users upgrade to the latest build to fully resolve the issue.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective SharePoint Online web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in SharePoint Online.
Next update by: Wednesday, September 18, 2024, at 6:30 PM UTC
|
|
Time: | Mon Aug 26 13:28:10 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in SharePoint Online
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in SharePoint Online.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within SharePoint Online. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: We've confirmed the deployments of our fixes have completed and users can update to the latest Microsoft 365 Office clients to receive the fix and resolve impact. We're monitoring service health telemetry to confirm users are updating to the latest client and prompts are reducing as expected.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective SharePoint Online web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in SharePoint Online.
Next update by: Wednesday, September 4, 2024, at 6:30 PM UTC
|
|
Time: | Fri Aug 23 14:31:02 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in SharePoint Online
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in SharePoint Online.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within SharePoint Online. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: We've confirmed that our deployment of the fix for Semi-Annual Channels is not progressing as expected and are investigating the underlying source of the slow saturation.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective SharePoint Online web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in SharePoint Online.
Next update by: Monday, August 26, 2024, at 6:30 PM UTC
|
|
Time: | Wed Aug 21 15:21:30 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in SharePoint Online
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in SharePoint Online.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within SharePoint Online. Also, affected users may see the following message "This content presents a potential issue".
While we're working to remediate impact, we recommend that users update their Microsoft 365 Office clients by accessing an application and selecting the following options:
File > Account > Microsoft 365 and Office Updates > Update Options > Update Now
Current status: The fix deployment is progressing slower than anticipated and we're looking into methods to expedite this process. We've also identified that this warning prompt is displaying when known safe links are selected and are investigating ways to streamline this process and prevent extraneous alerts going forward.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective SharePoint Online web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in SharePoint Online.
Next update by: Friday, August 23, 2024, at 8:00 PM UTC
|
|
Time: | Tue Aug 20 15:56:59 2024 |
Description: | Title: Some users may incorrectly receive a security warning when opening Excel or PowerPoint files in SharePoint Online
User impact: Users may incorrectly receive a security warning when opening Word, Excel or PowerPoint files in SharePoint Online.
More info: More specifically, users may incorrectly receive a security prompt when opening Word, Excel or PowerPoint files in their respective web apps within SharePoint Online. Also, affected users may see the following message "This content presents a potential issue".
Current status: This is a continuation of the event previously communicated via SP861520.
We've determined that a small number of users are still impacted by this event. Impact is isolated to those still operating under the Semi-Annual Channel update from January 2024 - 16.0.17328.20452.
The fix is progressing throughout the remaining infrastructure, and we expect to have a remediation timeline.
Scope of impact: Impact is specific to some users who are served through infrastructure attempting to open Word, Excel or PowerPoint files in their respective SharePoint Online web app.
Start time: Wednesday, July 31, 2024, at 4:30 AM UTC
Root cause: A necessary short-term fix for an unrelated issue was recently implemented, producing a security warning prompt when opening Excel, PowerPoint, or Word files in SharePoint Online.
Next update by: Wednesday, August 21, 2024, at 8:00 PM UTC
|
|
MV903480 - Users may not receive translations for Microsoft Viva Engage posts in different languages
Status: | serviceRestored |
Start Time: | Wed Oct 2 02:00:00 2024 |
End Time: | Wed Oct 2 19:46:00 2024 |
Service: | Microsoft Viva |
Feature Group: | Viva Engage |
Classification: | advisory |
Last Updated: | Wed Oct 2 20:16:35 2024 |
Root Cause: | A recently implemented service update which introduced a misconfiguration with the translator policies was resulting in impact. |
Next Update: | N/A |
|
Details
Time: | Wed Oct 2 20:16:35 2024 |
Description: | Title: Users may not receive translations for Microsoft Viva Engage posts in different languages
User impact: Users may have not received translations for Viva Engage posts in different languages.
More info: When users attempted to receive translations, users may have received an error which stated the following:
"Sorry, translation wasn't working right now. Please try again."
Final status: After testing within our internal testing environment and an extended period of monitoring the service health infrastructure, we've determined that impact has been remediated for all affected users.
Scope of impact: Any user who attempted to translate Viva Engage posts in different languages may have been impacted.
Start time: Wednesday, October 2, 2024, at 6:00 AM UTC
End time: Wednesday, October 2, 2024, at 11:46 PM UTC
Root cause: A recently implemented service update which introduced a misconfiguration with the translator policies was resulting in impact.
Next steps:
- We'll continue to monitor our service update validation process to ensure similar instances aren't replicated in the future.
This is the final update for the event.
|
|
Time: | Wed Oct 2 19:58:55 2024 |
Description: | Title: Users may not receive translations for Microsoft Viva Engage posts in different languages
User impact: Users may not receive translations for Viva Engage posts in different languages.
More info: When attempting to receive translations, users may receive an error which states the following:
"Sorry, translation isn't working right now. Please try again."
Current status: After adjusting the aforementioned policies and monitoring the service's health, we've determined that some users are no longer impacted and as the fix progresses, more users may experience service restoration. Additionally, we're in the process of gathering a full remediation timeline which we anticipate will be provided by our next scheduled update.
Scope of impact: Any user attempting to translate Viva Engage posts in different languages may be impacted.
Start time: Wednesday, October 2, 2024, at 6:00 AM UTC
Root cause: A recently implemented service update which introduced a misconfiguration with the translator policies that's resulting in impact.
Next update by: Thursday, October 3, 2024, at 1:30 AM UTC
|
|
Time: | Wed Oct 2 16:45:16 2024 |
Description: | Title: Users may not receive translations for Microsoft Viva Engage posts in different languages
User impact: Users may not receive translations for Viva Engage posts in different languages.
More info: When attempting to receive translations, users may receive an error which states the following:
"Sorry, translation isn't working right now. Please try again."
Current status: We've identified a recently implemented service update which introduced a misconfiguration with the translator policies that's causing impact. We're adjusting the policies to correct the misconfiguration and remediate the impact.
Scope of impact: Any user attempting to translate Viva Engage posts in different languages may be impacted.
Start time: Wednesday, October 2, 2024, at 6:00 AM UTC
Next update by: Wednesday, October 2, 2024, at 11:30 PM UTC
|
|
Time: | Wed Oct 2 15:47:02 2024 |
Description: | Title: Users may not receive translations for Microsoft Viva Engage posts in different languages
User impact: Users may not receive translations for Viva Engage posts in different languages.
More info: When attempting to receive translations, users may receive an error which states the following:
"Sorry, translation isn't working right now. Please try again."
Current status: We're reviewing our service telemetry to identify any errors relating to text translation and checking recent service changes that may indicate the root cause.
Scope of impact: Any user attempting to translate Viva Engage posts in different languages may be impacted.
Next update by: Wednesday, October 2, 2024, at 9:00 PM UTC
|
|
Time: | Wed Oct 2 15:31:34 2024 |
Description: | Title: Users aren’t receiving translations for Microsoft Viva Engage posts in different languages
User impact: Users aren’t receiving translations for Viva Engage posts in different languages.
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.
|
|
SP901205 - Users may have been unable to use the "Move To/Copy To" function for some files and folders in SharePoint Online
Status: | serviceRestored |
Start Time: | Tue Sep 24 04:34:00 2024 |
End Time: | Mon Sep 30 14:10:00 2024 |
Service: | SharePoint Online |
Feature Group: | SharePoint Features |
Classification: | advisory |
Last Updated: | Tue Oct 1 05:37:40 2024 |
Root Cause: | A portion of code related to a recently enabled feature was contributing to the impact. |
Next Update: | N/A |
|
Details
Time: | Tue Oct 1 05:37:40 2024 |
Description: | Title: Users may have been unable to use the "Move To/Copy To" function for some files and folders in SharePoint Online
User impact: Users may have been unable to use the "Move To/Copy To" function for some files and folders in SharePoint Online.
More info: Users were reportedly encountering this issue with file or folder path names that were unusually long; although the exact path name length causing this issue to occur is unknown. Users would have likely seen the following error when selecting the "Move To/Copy To" action: "Sorry, something went wrong. An unexpected error has occurred."
Final status: We've finished disabling and reverting the offending code change which has been confirmed to be the root cause of impact. Additionally, we've validated that impact is no longer occurring after a period of monitoring.
Scope of impact: Impact was specific to users hosted through the affected infrastructure and this issue may have impacted users selecting the "Move To/Copy To" action for files and folders with unusually long path names in SharePoint Online.
Start time: Tuesday, September 24, 2024 at 8:34 AM UTC
End time: Monday, September 30, 2024 at 6:10 PM UTC
Root cause: A portion of code related to a recently enabled feature was contributing to the impact.
Next steps:
- We’re reviewing our feature deployment procedures to better identify similar code issues during our development and testing cycles.
This is the final update for this event.
|
|
Time: | Mon Sep 30 14:57:14 2024 |
Description: | Title: Users can't use the "Move To/Copy To" function for some files and folders in SharePoint Online
User impact: Users can't use the "Move To/Copy To" function for some files and folders in SharePoint Online.
More info: Users are reportedly encountering this issue with file or folder path names that are unusually long; although the exact path name length causing this issue to occur is unknown. Users will likely see the following error when selecting the "Move To/Copy To" action: "Sorry, something went wrong. An unexpected error has occurred."
Current status: We've identified a portion of code related to a recently enabled feature that's likely contributing to the impact. We've disabled this code portion to remediate the impact and are monitoring service health telemetry to determine the efficacy of the fix.
Scope of impact: Your organization is affected by this event and this issue impacts users selecting the "Move To/Copy To" action for files and folders with unusually long path names in SharePoint Online.
Next update by: Tuesday, October 1, 2024 at 7:30 PM UTC
|
|
Time: | Mon Sep 30 06:53:22 2024 |
Description: | Title: Users may encounter a timeout error when clicking on a file "Move To/Copy To" with a long path within SharePoint Online
User impact: Users may encounter a timeout error when clicking on a file "Move To/Copy To" with a long path within SharePoint Online.
Current status: We're analyzing any recent changes made to the service which could be contributing to impact to assist with the investigation into the root cause of impact.
Scope of impact: Your organization is affected by this event and may impact some users.
Next update by: Monday, September 30, 2024 at 7:30 PM UTC
|
|
Time: | Mon Sep 30 04:59:35 2024 |
Description: | Title: Users may encounter a timeout error when clicking on a file "Move To/Copy To" with a long path within SharePoint Online
User impact: Users may encounter a timeout error when clicking on a file "Move To/Copy To" with a long path within SharePoint Online.
Current status: We're reviewing service telemetry to locate the root cause of impact and determine our next steps.
Scope of impact: Your organization is affected by this event and some users may be impacted.
Next update by: Monday, September 30, 2024 at 11:00 AM UTC
|
|
CR898173 - A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
Status: | serviceRestored |
Start Time: | Thu Sep 19 20:00:00 2024 |
End Time: | Sat Sep 28 18:00:00 2024 |
Service: | Dynamics 365 Apps |
Feature Group: | Other |
Classification: | advisory |
Last Updated: | Mon Sep 30 13:38:49 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Mon Sep 30 13:38:32 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
User impact: A subset of environments may not have appeared in environment lists and selectors or may have experienced permissions issues.
Final Status: The fix has been deployed to your environment, and we have validated via service health diagnostics, that functionality is restored.
This is the final update on the incident.
Preliminary Root Cause: A regression introduced in a recent service update led to a capacity issue
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|
Time: | Fri Sep 27 13:49:34 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues.
More info: Missing environments may take up to 24 hours to reappear in environment lists and selectors.
As a workaround, affected environments can be accessed directly if the environment Id or URL is known.
Current Status: The fix deployments are in progress.
Next Update: Monday, September 30, 2024, 7:00 PM UTC
|
|
Time: | Thu Sep 26 19:44:22 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues.
More info: Missing environments may take up to 24 hours to reappear in environment lists and selectors.
As a workaround, affected environments can be accessed directly if the environment Id or URL is known.
Current Status: We have validated the fix in a test environment and have initiated deployment of the fix to your environment. In parallel, we are validating an additional fix to help further reduce the latency your environment may be experiencing.
Next Update: Friday, September 27, 2024, 7:00 PM UTC
|
|
Time: | Wed Sep 25 19:33:20 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues.
More info: Missing environments may take up to 24 hours to reappear in environment lists and selectors.
As a workaround, affected environments can be accessed directly if the environment Id or URL is known.
Current Status: We have developed a hotfix to address the regression, and currently, we are working to validate the fix in a test environment prior to scheduling the deployment of the fix to your environment. In parallel, we are continuing to investigate other ways to reduce the latency your environment may be experiencing.
Next Update: Friday, September 27, 2024, 1:00 AM UTC
|
|
Time: | Wed Sep 25 14:10:54 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors or experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors or experience permissions issues.
More info: Missing environments may take up to 24 hours to reappear in environment lists and selectors.
As a workaround, affected environments can be accessed directly via if the environment Id or URL is known.
Current Status: After our investigation we determined that a portion of the service infrastructure responsible for processing data has reached a capacity issue due to a regression contained in a recent service update, causing a subset of requests related to environment listing and newly created environment to experience latency. We are currently developing a hotfix to correct this issue.
Next Update: Thursday, September 26, 2024, 1:00 AM UTC
|
|
Time: | Wed Sep 25 13:44:53 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors or experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors or experience permissions issues.
More info: Affected environments can be accessed directly via if the environment Id or URL is known.
Current Status: We are aware of an emerging issue where users may observe that a subset of environments are missing in Power Platform admin center environment lists and Maker portal environment pickers. In addition, newly-created environments may temporarily disappear from environment lists.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|
MF898190 - Admins may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
Status: | serviceRestored |
Start Time: | Thu Sep 19 20:00:00 2024 |
End Time: | Sat Sep 28 18:00:00 2024 |
Service: | Microsoft Power Automate in Microsoft 365 |
Feature Group: | Service and web access issues |
Classification: | advisory |
Last Updated: | Mon Sep 30 13:38:04 2024 |
Root Cause: | A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency, resulting in sync delays. |
Next Update: | N/A |
|
Details
Time: | Mon Sep 30 13:32:42 2024 |
Description: | Title: Admins may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Admins may have experienced delays seeing environments in the Microsoft Power Platform admin center environment lists.
Final status: We've confirmed that the deployment of the fix completed and validated with internal monitoring that the impact is remediated.
Scope of impact: This issue may have affected any admin that attempted to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
End time: Saturday, September 28, 2024, at 10:00 PM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency, resulting in sync delays.
Next steps:
- We're further reviewing the service update to understand how the code regression was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|
Time: | Fri Sep 27 14:45:07 2024 |
Description: | Title: Admins may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Admins may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We've improved the fix to optimize the affected request flow and have observed improved latency for a portion of affected users. We've also validated the efficacy of another fix designed to improve the processing of requests which is expected to significantly improve the latency. We'll provide a timeline for the deployment of the fixes as one becomes available.
Scope of impact: This issue may affect any admin attempting to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays.
Next update by: Monday, September 30, 2024, at 7:00 PM UTC
|
|
Time: | Thu Sep 26 20:47:22 2024 |
Description: | Title: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We've observed that the aforementioned changes to optimize the request flow has alleviated impact for some affected users. Additionally, we're in our final stages of developing and subsequently deploying our long-term fix.
Scope of impact: This issue may affect any user attempting to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays.
Next update by: Friday, September 27, 2024, at 8:00 PM UTC
|
|
Time: | Wed Sep 25 19:38:08 2024 |
Description: | Title: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We're continuing to prepare a fix to resolve the underlying issue and prevent further impact. In parallel, we're rolling out some changes to optimize the affected request flow throughout the impacted environment that we anticipate may assist in reducing delays and alleviating impact in the near-term.
Scope of impact: This issue may affect any user attempting to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays.
Next update by: Friday, September 27, 2024, at 1:00 AM UTC
|
|
Time: | Wed Sep 25 14:19:51 2024 |
Description: | Title: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We've identified that a recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays. We're developing a fix to correct the regression and restore sync operations to optimal performance.
Scope of impact: This issue may affect any user attempting to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays.
Next update by: Thursday, September 26, 2024, at 1:00 AM UTC
|
|
Time: | Wed Sep 25 14:08:56 2024 |
Description: | Title: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We're investigating a potential issue with the Microsoft Power Platform admin center and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
MM898191 - Admins may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
Status: | serviceRestored |
Start Time: | Thu Sep 19 20:00:00 2024 |
End Time: | Sat Sep 28 18:00:00 2024 |
Service: | Power Apps in Microsoft 365 |
Feature Group: | Service and web access issues |
Classification: | advisory |
Last Updated: | Mon Sep 30 13:37:08 2024 |
Root Cause: | A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency, resulting in sync delays. |
Next Update: | N/A |
|
Details
Time: | Mon Sep 30 13:31:40 2024 |
Description: | Title: Admins may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Admins may have experienced delays seeing environments in the Microsoft Power Platform admin center environment lists.
Final status: We've confirmed that the deployment of the fix completed and validated with internal monitoring that the impact is remediated.
Scope of impact: This issue may have affected any admin that attempted to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
End time: Saturday, September 28, 2024, at 10:00 PM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency, resulting in sync delays.
Next steps:
- We're further reviewing the service update to understand how the code regression was introduced, and to understand what prevented it from being detected in our update testing and validation procedures, which will allow us to prevent similar issues in future updates.
This is the final update for the event.
|
|
Time: | Fri Sep 27 14:45:31 2024 |
Description: | Title: Admins may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Admins may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We've improved the fix to optimize the affected request flow and have observed improved latency for a portion of affected users. We've also validated the efficacy of another fix designed to improve the processing of requests which is expected to significantly improve the latency. We'll provide a timeline for the deployment of the fixes as one becomes available.
Scope of impact: This issue may affect any admin attempting to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays.
Next update by: Monday, September 30, 2024, at 7:00 PM UTC
|
|
Time: | Thu Sep 26 20:47:32 2024 |
Description: | Title: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We've observed that the aforementioned changes to optimize the request flow has alleviated impact for some affected users. Additionally, we're in our final stages of developing and subsequently deploying our long-term fix.
Scope of impact: This issue may affect any user attempting to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays.
Next update by: Friday, September 27, 2024, at 8:00 PM UTC
|
|
Time: | Wed Sep 25 19:38:05 2024 |
Description: | Title: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We're continuing to prepare a fix to resolve the underlying issue and prevent further impact. In parallel, we're rolling out some changes to optimize the affected request flow throughout the impacted environment that we anticipate may assist in reducing delays and alleviating impact in the near-term.
Scope of impact: This issue may affect any user attempting to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays.
Next update by: Friday, September 27, 2024, at 1:00 AM UTC
|
|
Time: | Wed Sep 25 14:19:59 2024 |
Description: | Title: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We've identified that a recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays. We're developing a fix to correct the regression and restore sync operations to optimal performance.
Scope of impact: This issue may affect any user attempting to view newly created or recently updated environments in the Microsoft Power Platform admin center environment lists.
Start time: Friday, September 20, 2024, at 12:00 AM UTC
Root cause: A recent service update introduced a regression which caused a subset of requests related to environment listing and newly created environments to experience latency resulting in sync delays.
Next update by: Thursday, September 26, 2024, at 1:00 AM UTC
|
|
Time: | Wed Sep 25 14:09:14 2024 |
Description: | Title: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists
User impact: Users may experience delays seeing environments in the Microsoft Power Platform admin center environment lists.
More info: This issue may impact newly created and recently updated environments. Missing environments may take up to 24 hours to reappear in environment lists and selectors.
Affected users can navigate directly to affected environments if the environment ID or URL is known.
Current status: We're investigating a potential issue with the Microsoft Power Platform admin center and checking for impact to your organization. We'll provide an update within 30 minutes.
|
|
FL898171 - A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
Status: | serviceRestored |
Start Time: | Thu Sep 19 20:00:00 2024 |
End Time: | Sat Sep 28 18:00:00 2024 |
Service: | Microsoft Power Automate |
Feature Group: | Other |
Classification: | advisory |
Last Updated: | Mon Sep 30 13:36:50 2024 |
Root Cause: | N/A |
Next Update: | N/A |
|
Details
Time: | Mon Sep 30 13:36:34 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
User impact: A subset of environments may not have appeared in environment lists and selectors or may have experienced permissions issues.
Final Status: The fix has been deployed to your environment, and we have validated via service health diagnostics, that functionality is restored.
This is the final update on the incident.
Preliminary Root Cause: A regression introduced in a recent service update led to a capacity issue
Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.
|
|
Time: | Fri Sep 27 13:49:13 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues.
More info: Missing environments may take up to 24 hours to reappear in environment lists and selectors.
As a workaround, affected environments can be accessed directly if the environment Id or URL is known.
Current Status: The fix deployments are in progress.
Next Update: Monday, September 30, 2024, 7:00 PM UTC
|
|
Time: | Thu Sep 26 19:44:17 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues.
More info: Missing environments may take up to 24 hours to reappear in environment lists and selectors.
As a workaround, affected environments can be accessed directly if the environment Id or URL is known.
Current Status: We have validated the fix in a test environment and have initiated deployment of the fix to your environment. In parallel, we are validating an additional fix to help further reduce the latency your environment may be experiencing.
Next Update: Friday, September 27, 2024, 7:00 PM UTC
|
|
Time: | Wed Sep 25 19:33:23 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors, or may experience permissions issues.
More info: Missing environments may take up to 24 hours to reappear in environment lists and selectors.
As a workaround, affected environments can be accessed directly if the environment Id or URL is known.
Current Status: We have developed a hotfix to address the regression, and currently, we are working to validate the fix in a test environment prior to scheduling the deployment of the fix to your environment. In parallel, we are continuing to investigate other ways to reduce the latency your environment may be experiencing.
Next Update: Friday, September 27, 2024, 1:00 AM UTC
|
|
Time: | Wed Sep 25 14:10:05 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors or experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors or experience permissions issues.
More info: Missing environments may take up to 24 hours to reappear in environment lists and selectors.
As a workaround, affected environments can be accessed directly via if the environment Id or URL is known.
Current Status: After our investigation we determined that a portion of the service infrastructure responsible for processing data has reached a capacity issue due to a regression contained in a recent service update, causing a subset of requests related to environment listing and newly created environment to experience latency. We are currently developing a hotfix to correct this issue.
Next Update: Thursday, September 26, 2024, 1:00 AM UTC
|
|
Time: | Wed Sep 25 13:41:16 2024 |
Description: | Title: A subset of environments may not appear in environment lists and selectors or experience permissions issues
User impact: A subset of environments may not appear in environment lists and selectors or experience permissions issues.
More info: Affected environments can be accessed directly via if the environment Id or URL is known.
Current Status: We are aware of an emerging issue where users may observe that a subset of environments are missing in Power Platform admin center environment lists and Maker portal environment pickers. In addition, newly-created environments may temporarily disappear from environment lists.
This information is preliminary and may be subject to changes, corrections, and updates.
|
|
TM897962 - Some users are unable to share or send email messages to Microsoft Teams channels
Status: | serviceRestored |
Start Time: | Thu Jul 25 18:01:00 2024 |
End Time: | Fri Sep 27 13:29:00 2024 |
Service: | Microsoft Teams |
Feature Group: | Teams Components |
Classification: | advisory |
Last Updated: | Mon Sep 30 11:42:18 2024 |
Root Cause: | An unexpected increase in the volume of requests to post email messages to Microsoft Teams channels, combined with a performance reduction in the components of infrastructure responsible for facilitating these messages, caused email-to-chat message failures, which led to impact. |
Next Update: | N/A |
|
Details
Time: | Mon Sep 30 11:27:49 2024 |
Description: | Title: Some users are unable to share or send email messages to Microsoft Teams channels
User impact: Users were unable to share or send email messages to Microsoft Teams channels.
More info: Users reported that they weren't receiving or seeing the email messages displayed in Microsoft Teams channels.
Final status: We've completed the deployment of our fix, and we've verified with some affected users that the issue has been fully remediated.
Scope of impact: Your organization was affected by this event, and some users who attempted to share or send email messages to Microsoft Teams channels were impacted.
Start time: Thursday, July 25, 2024, at 10:01 PM UTC
End time: Friday, September 27, 2024, at 5:29 PM UTC
Root cause: An unexpected increase in the volume of requests to post email messages to Microsoft Teams channels, combined with a performance reduction in the components of infrastructure responsible for facilitating these messages, caused email-to-chat message failures, which led to impact.
Next steps:
- We're continuing to analyze the unexpected increase in the volume of requests to post email messages to Teams channels, and the performance of the related infrastructure which facilitates those messages, to better understand how these factors led to impact so we can prevent similar issues from occurring in the future.
This is the final update for the event.
|
|
Time: | Thu Sep 26 14:07:52 2024 |
Description: | Title: Some users are unable to share or send email messages to Microsoft Teams channels
User impact: Users are unable to share or send email messages to Microsoft Teams channels.
More info: Users have reported that they aren't receiving or seeing the email messages displayed in Microsoft Teams channels.
Current status: We've completed development of our previously mentioned fix, and we're proceeding with validation before beginning deployment to the impacted service environments. We anticipate that the fix will be fully deployed by our next scheduled communication update, at which time we'll monitor our service health telemetry to confirm that the impact is remediated.
Scope of impact: Your organization is affected by this event, and some users attempting to share or send email messages to Microsoft Teams channels are impacted.
Estimated time to resolve: We anticipate that our fix will be fully deployed, remediating impact by Monday, September 30, 2024, at 3:00 PM UTC.
Root cause: An unexpected increase in the volume of requests to post email messages to Teams channels, combined with a performance reduction in the components of infrastructure responsible for facilitating these messages, is causing email-to-chat message failures that lead to impact.
Next update by: Monday, September 30, 2024, at 3:30 PM UTC
|
|
Time: | Thu Sep 26 06:34:01 2024 |
Description: | Title: Some users are unable to share or send email messages to Microsoft Teams channels
User impact: Users are unable to share or send email messages to Microsoft Teams channels.
More info: Users have reported that they aren't receiving or seeing the email messages displayed in Microsoft Teams channels.
Current status: We're continuing our efforts to develop and validate the fix in our internal environments, before proceeding with deployment and anticipate having a remediation timeline by our next scheduled update.
Scope of impact: Your organization is affected by this event, and some users attempting to share or send email messages to Microsoft Teams channels are impacted.
Root cause: A traffic processing issue paired with an increased traffic volume is causing some email to chat message failures.
Next update by: Thursday, September 26, 2024, at 7:30 PM UTC
|
|
Time: | Thu Sep 26 01:49:40 2024 |
Description: | Title: Some users are unable to share or send email messages to Microsoft Teams channels
User impact: Users are unable to share or send email messages to Microsoft Teams channels.
More info: Users have reported that they aren't receiving or seeing the email messages displayed in Microsoft Teams channels.
Current status: We've identified a traffic processing issue paired with an increased traffic volume, which is causing some email to chat message failures. We're further investigating why this traffic processing issue is happening and in the initial stages of developing a fix to remediate impact.
Scope of impact: Your organization is affected by this event, and some users attempting to share or send email messages to Microsoft Teams channels are impacted.
Next update by: Thursday, September 26, 2024, at 11:30 AM UTC
|
|
Time: | Wed Sep 25 14:38:48 2024 |
Description: | Title: Some users are unable to share or send email messages to Microsoft Teams channels
User impact: Users are unable to share or send email messages to Microsoft Teams channels.
More info: Users have reported that they aren't receiving or seeing the email messages displayed in Microsoft Teams channels.
Current status: We're proceeding with our investigation of the newly collected NDRs capturing the impact scenario, along with errors found within our service telemetry that correlate to this reported problem, to isolate the root cause of impact and identify a path to remediation.
Scope of impact: Your organization is affected by this event, and some users attempting to share or send email messages to Microsoft Teams channels are impacted.
Next update by: Thursday, September 26, 2024, at 8:00 AM UTC
|
|
Time: | Wed Sep 25 09:41:38 2024 |
Description: | Title: Some users are unable to share or send email messages to Microsoft Teams channels
User impact: Users are unable to share or send email messages to Microsoft Teams channels.
More info: Users have reported that they aren't receiving or seeing the email messages displayed in Microsoft Teams channels.
Current status: We're continuing to review service monitoring telemetry and collected Non-Delivery Reports (NDR)s to aid our investigation into the source of the issue.
Scope of impact: Your organization is affected by this event, and some users attempting to share or send email messages to Microsoft Teams channels are impacted.
Next update by: Wednesday, September 25, 2024, at 8:00 PM UTC
|
|
Time: | Wed Sep 25 08:04:22 2024 |
Description: | Title: Some users are unable to share or send email messages to Microsoft Teams channels
User impact: Users are unable to share or send email messages to Microsoft Teams channels.
More info: Users have reported that they aren't receiving or seeing the email messages displayed in Microsoft Teams channels.
Current status: We're reviewing service monitoring telemetry to isolate the root cause and develop a remediation plan.
Scope of impact: Your organization is affected by this event, and some users attempting to share or send email messages to Microsoft Teams channels are impacted.
Next update by: Wednesday, September 25, 2024, at 2:00 PM UTC
|
|
|